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
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
d5c4c9a3342f6952211f2a8f5fd1a1cc6fb4c515 | 1,113 | md | Markdown | README.md | TheVillageDev/mumbleSniff | 145268ea75edb9c4c05af6ec6124259ecbcb1b8d | [
"BSD-2-Clause"
] | null | null | null | README.md | TheVillageDev/mumbleSniff | 145268ea75edb9c4c05af6ec6124259ecbcb1b8d | [
"BSD-2-Clause"
] | 1 | 2019-05-07T08:51:48.000Z | 2020-10-28T19:13:37.000Z | README.md | TheVillageDev/mumbleSniff | 145268ea75edb9c4c05af6ec6124259ecbcb1b8d | [
"BSD-2-Clause"
] | null | null | null | # How to get it working
1. Clone the repo and get into the folder.
2. Create a certificate for the mumble connection and save them to `key.pem` and `cert.pem`:
openssl req -x509 -newkey rsa:2048 -nodes -keyout key.pem -out cert.pem
3. Edit the environment file:
cp default.env .env
vi .env
4. Add the Telegram Bot Token to the environment. Ask @BotFather for an API token and paste it after the __=__ char.
5. Change the Server-URL and the Mumble Username to whatever you desire.
6. Close the file.
7. Run `npm install` to recieve the required packages.
# Start the script
I ran best with loading `index.js` into an interactive shell:
```bash
~/mumbleSniff $ node
> .load ./index.js
```
After that, you can import prior Telegram message ids with `fs.readFileSync("loggedInUsers.log", "utf-8").split("\n").forEach((i)=>{botUsers.push(i)});`. Then, check the botUsers array for new contents. (This is an [issue](https://github.com/jeyemwey/mumbleSniff/1), and _$soon_, the application should do this by itself.)
# Contribute
If you want to, you can surely contribute to this project. Just send a PR!
| 34.78125 | 322 | 0.733154 | eng_Latn | 0.978572 |
d5c51801d511f247ae82790dceda5244aa9f1960 | 3,680 | md | Markdown | wdk-ddi-src/content/wdm/nf-wdm-excanceltimer.md | Cloud-Writer/windows-driver-docs-ddi | 6ac33c6bc5649df3e1b468a977f97c688486caab | [
"CC-BY-4.0",
"MIT"
] | null | null | null | wdk-ddi-src/content/wdm/nf-wdm-excanceltimer.md | Cloud-Writer/windows-driver-docs-ddi | 6ac33c6bc5649df3e1b468a977f97c688486caab | [
"CC-BY-4.0",
"MIT"
] | null | null | null | wdk-ddi-src/content/wdm/nf-wdm-excanceltimer.md | Cloud-Writer/windows-driver-docs-ddi | 6ac33c6bc5649df3e1b468a977f97c688486caab | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
UID: NF:wdm.ExCancelTimer
title: ExCancelTimer function (wdm.h)
description: The ExCancelTimer routine cancels a timer that was set by a previous call to the ExSetTimer routine.
old-location: kernel\excanceltimer.htm
tech.root: kernel
ms.assetid: 5E52550D-0A81-4C72-9A82-7C13BC3EFE00
ms.date: 04/30/2018
ms.keywords: ExCancelTimer, ExCancelTimer routine [Kernel-Mode Driver Architecture], kernel.excanceltimer, wdm/ExCancelTimer
ms.topic: function
req.header: wdm.h
req.include-header: Wdm.h, Ntddk.h, Ntifs.h
req.target-type: Universal
req.target-min-winverclnt: Available starting with Windows 8.1.
req.target-min-winversvr:
req.kmdf-ver:
req.umdf-ver:
req.ddi-compliance:
req.unicode-ansi:
req.idl:
req.max-support:
req.namespace:
req.assembly:
req.type-library:
req.lib: Ntoskrnl.lib
req.dll:
req.irql: "<= DISPATCH_LEVEL"
topic_type:
- APIRef
- kbSyntax
api_type:
- LibDef
api_location:
- ntoskrnl.lib
- ntoskrnl.dll
api_name:
- ExCancelTimer
product:
- Windows
targetos: Windows
req.typenames:
---
# ExCancelTimer function
## -description
The <b>ExCancelTimer</b> routine cancels a timer that was set by a previous call to the <a href="https://msdn.microsoft.com/library/windows/hardware/dn265188">ExSetTimer</a> routine.
## -parameters
### -param Timer [in, out]
A pointer to an <a href="https://docs.microsoft.com/windows-hardware/drivers/kernel/exxxxtimer-routines-and-ex-timer-objects">EX_TIMER</a> structure. This structure is a timer object that was previously allocated by the <a href="https://msdn.microsoft.com/library/windows/hardware/dn265179">ExAllocateTimer</a> routine.
### -param Parameters [in, optional]
Drivers must set this parameter to <b>NULL</b>.
## -returns
This routine returns <b>TRUE</b> if the timer was canceled. Otherwise, the routine returns <b>FALSE</b>.
## -remarks
After your driver calls the <a href="https://msdn.microsoft.com/library/windows/hardware/dn265188">ExSetTimer</a> routine to set the timer, the timer might be canceled before it expires. The driver can call the <b>ExCancelTimer</b> routine to explicitly cancel a pending timer. Also, if the driver calls the <b>ExSetTimer</b> routine to set a new timer on a timer object before a previously set timer on this object expires, this <b>ExSetTimer</b> call implicitly cancels the previous timer and then starts the new timer.
A return value of <b>TRUE</b> indicates that the timer was set when <b>ExCancelTimer</b> was called. In this case, the routine cancels the timer. A return value of <b>FALSE</b> indicates that the timer was not set, which might mean that the timer was never set, that the timer had already been canceled, or that the timer had already expired.
When a timer expires, the operating system signals the timer object. As an option, a driver can supply an <a href="https://msdn.microsoft.com/library/windows/hardware/dn265190">ExTimerCallback</a> callback routine that is called when the timer expires. If the driver supplies this callback routine, this routine is guaranteed to be called if the timer object is signaled. If the timer is canceled before it expires, the timer object is not signaled and the callback routine is not called.
For more information, see <a href="https://msdn.microsoft.com/library/windows/hardware/dn265198">ExXxxTimer Routines and EX_TIMER Objects</a>.
## -see-also
<a href="https://docs.microsoft.com/windows-hardware/drivers/kernel/exxxxtimer-routines-and-ex-timer-objects">EX_TIMER</a>
<a href="https://msdn.microsoft.com/library/windows/hardware/dn265179">ExAllocateTimer</a>
<a href="https://msdn.microsoft.com/library/windows/hardware/dn265188">ExSetTimer</a>
| 33.454545 | 521 | 0.767391 | eng_Latn | 0.899165 |
d5c57d7940de9c4601384f6b43312d27c4e63576 | 1,592 | md | Markdown | docs/api/teamsfx-api.istatictab.md | zhenjiao-ms/TeamsFx | 946cdd5d048f7493629f0ed185b1875df381c89a | [
"MIT"
] | 127 | 2021-05-10T04:59:45.000Z | 2022-03-19T00:25:23.000Z | docs/api/teamsfx-api.istatictab.md | zhenjiao-ms/TeamsFx | 946cdd5d048f7493629f0ed185b1875df381c89a | [
"MIT"
] | 740 | 2021-05-10T06:15:23.000Z | 2022-03-31T07:45:14.000Z | docs/api/teamsfx-api.istatictab.md | zhenjiao-ms/TeamsFx | 946cdd5d048f7493629f0ed185b1875df381c89a | [
"MIT"
] | 73 | 2021-05-10T05:08:45.000Z | 2022-03-29T12:08:43.000Z | <!-- Do not edit this file. It is automatically generated by API Documenter. -->
[Home](./index.md) > [@microsoft/teamsfx-api](./teamsfx-api.md) > [IStaticTab](./teamsfx-api.istatictab.md)
## IStaticTab interface
<b>Signature:</b>
```typescript
export interface IStaticTab
```
## Properties
| Property | Type | Description |
| --- | --- | --- |
| [contentUrl?](./teamsfx-api.istatictab.contenturl.md) | string | <i>(Optional)</i> The url which points to the entity UI to be displayed in the Teams canvas. |
| [context?](./teamsfx-api.istatictab.context.md) | ("personalTab" \| "channelTab")\[\] | <i>(Optional)</i> The set of contextItem scopes that a tab belong to |
| [entityId](./teamsfx-api.istatictab.entityid.md) | string | A unique identifier for the entity which the tab displays. |
| [name?](./teamsfx-api.istatictab.name.md) | string | <i>(Optional)</i> The display name of the tab. |
| [objectId?](./teamsfx-api.istatictab.objectid.md) | string | <i>(Optional)</i> |
| [scopes](./teamsfx-api.istatictab.scopes.md) | ("team" \| "personal")\[\] | Specifies whether the tab offers an experience in the context of a channel in a team, or an experience scoped to an individual user alone. These options are non-exclusive. Currently static tabs are only supported in the 'personal' scope. |
| [searchUrl?](./teamsfx-api.istatictab.searchurl.md) | string | <i>(Optional)</i> The url to direct a user's search queries. |
| [websiteUrl?](./teamsfx-api.istatictab.websiteurl.md) | string | <i>(Optional)</i> The url to point at if a user opts to view in a browser. |
| 61.230769 | 318 | 0.690955 | eng_Latn | 0.901644 |
d5c692809b42380886163ad0b2919d5bc2cdf3ab | 941 | md | Markdown | README.md | DeveloperShed/Empty-Project | 10a8cea096abef4619abf0310fe1f16154e09988 | [
"MIT"
] | null | null | null | README.md | DeveloperShed/Empty-Project | 10a8cea096abef4619abf0310fe1f16154e09988 | [
"MIT"
] | null | null | null | README.md | DeveloperShed/Empty-Project | 10a8cea096abef4619abf0310fe1f16154e09988 | [
"MIT"
] | null | null | null | # <<Project Name>>
<<Project description>>
* Source: [http://forums.devshed.com/path/to/thread](http://forums.devshed.com/path/to/thread)
## Features
* List some features
* List some more
## Browser support
* Chrome *(latest)*
* Edge *(latest)*
* Firefox *(latest)*
* Internet Explorer 8+
* Opera *(latest)*
* Safari *(latest)*
*Special comments about compatibility*
## Usage
Nicely formatted usage instructions.
## Support
Personal support requests should be made at the [Dev Shed Forums](http://forums.devshed.com).
## Contributing
This code is made freely available. Anyone and everyone is welcome to [contribute](CONTRIBUTING.md). If you would like to get involved, please review the [guidelines](CONTRIBUTING.md):
* [Bug reports](CONTRIBUTING.md#bugs)
* [Feature requests](CONTRIBUTING.md#features)
* [Pull requests](CONTRIBUTING.md#pull-requests)
## License
The code is available under the [MIT license](LICENSE). | 20.021277 | 184 | 0.729012 | eng_Latn | 0.888007 |
d5c7e55af001562bb5b64a3232f913813c1b7e53 | 51 | md | Markdown | _includes/03-links.md | ailenelung/markdown-portfolio | 2472e98e9dcb217cc3570fae39364a3c19417fe1 | [
"MIT"
] | null | null | null | _includes/03-links.md | ailenelung/markdown-portfolio | 2472e98e9dcb217cc3570fae39364a3c19417fe1 | [
"MIT"
] | 5 | 2020-07-04T04:09:23.000Z | 2020-07-04T04:49:51.000Z | _includes/03-links.md | ailenelung/markdown-portfolio | 2472e98e9dcb217cc3570fae39364a3c19417fe1 | [
"MIT"
] | null | null | null | [Ailene's Old Lame Website](http://ailenelung.com)
| 25.5 | 50 | 0.745098 | yue_Hant | 0.386415 |
d5c889b543c02893342e374d841c77c92c5c6f31 | 4,262 | md | Markdown | content/school/samenvattingen/Geschiedenis_amerika.md | maantjemol/quartz | f71cf37ed9ad6ad5439df76cfe2054505fc32d0c | [
"MIT"
] | null | null | null | content/school/samenvattingen/Geschiedenis_amerika.md | maantjemol/quartz | f71cf37ed9ad6ad5439df76cfe2054505fc32d0c | [
"MIT"
] | null | null | null | content/school/samenvattingen/Geschiedenis_amerika.md | maantjemol/quartz | f71cf37ed9ad6ad5439df76cfe2054505fc32d0c | [
"MIT"
] | null | null | null | ---
title: "Geschiedenis_amerika"
---
**
# De Amerikaanse revolutie:
Houd eigenlijk in dat Amerikanen belasting betalen aan de Britten niet zo chill vinden, dus ze komen in opstand en worden onafhankelijk.
# De revolutie:
Hoewel Amerika geen contact had met europa volgde ze de discussies en verlichtingsideeën wel. De vrijheid sprak ze aan en ze begonnen zichzelf Amerikanen te noemen
De staten bestuurde zichzelf vooral, maar ze waren ondergeschikt aan de Britse koning, die gouverneurs, ambtenaren en soldaten had. Radicale verlichte denkers zorgde voor wantrouwen onder de Amerikanen. Ze wouden hun shit liever zelf gaan regelen.
De Amerikanen werden zich pijnlijk bewust van de Britse koning toen hij Belastingen wilde heffen. Deze had hij namelijk nodig om de Franse te verslaan en hij wou zijn rijke levenstijl niet opgeven. Het verzet in Amerika riep dat men maar moest gaan protesteren in de hoop dat daardoor de belastingen omlaag gingen.
Dit alles ging mis toen Britse soldaten in Boston (1770) werden bekogelt met ijsballen en sneeuwballen door het verzet. Het één leidt tot het ander en de soldaten schieten meerdere mensen van het verzet neer. Dit wordt later bekend als Het bloedbad van Boston
2 jaar later (1772) vormde de verzetsleiders in Boston een verzet comité tegen het Britse bestuur. Ze hadden een paar belangrijke punten:
Iedereen heeft recht op
- Leven (behalve slaven)
- Bezit (behalve slaven)
- Vrijheid (behalve slaven)
Dit soort verzets comités kwamen in alle 13 koloniën.
De Britse koning was ondertussen echt wel toe aan geld, dus er kwamen in 1773 belastingen op thee. Hier waren de Amerikanen als oud britten echt niet blij mee. Er ontstond opnieuw een fel verzet in Boston. Opstandelingen verkleedde zich als slaven om vervolgens thee van Britse schepen af te gooien en het daarna te blamen op de slaven. Dit werd uiteindelijk de Boston tea party genoemd.
De britse koning was inmiddels echt wel pissig. Hij besloot de ongehoorzame amerikanen te straffen:
- De haven werd gesloten
- Zelfbestuur werd afgeschaft
- Beroepsmillitaire werden ingekwartiert
Dit vonden de rebellen echt niet cool. Ze vormde in 1774 een parlement in Philadelphia met afgevaardigde van alle kolonienen. Zij besloten op 14 juli 1776 dat Amerika onafhankelijk was. Er werd ook een onafhankelijkheidsverklaring geschreven.
Een jaar eerder (1775) was er een leger gevormd onder generaal George Washington. Hij was vooral goed in oorlogsstrategie. Hij gaf pamfletten en speeches aan zijn soldaten om ze moed in te spreken. Het pamflet Common Sense van Thomas Paine bracht de rebelse gedachten naar de rest van Amerika.
Na veel oorlog met de Britten en nog meer hulp van de Fransen won Amerika in 1783 de revolutie en werden ze als onafhankelijk herkend.
# Wat erna gebeurde:
Er werd een grondwet geschreven in 1787 die nog steeds geldig en inmiddels best wel verouderd is. De macht werd verdeeld tussen
- Het congres, bestaande uit afgevaardigde uit de staten
- het Hooggerechtshof met meerdere opperrechters
- De president, op dat moment George Washington omdat ie zo goed z’n best had gedaan in de oorlog
Volgens de grondwet hadden alle burgers gelijke rechten. Burgers is in deze context witte mannen met een groot bezit. De indianen werden gevangen als slaven of vermoord.
De noordelijke staten hadden de slavenhandel in 1787 afgeschaft, maar de zuidelijke staten waren er best wel afhankelijk van en wilden liever niet zelf werken. De VS was namelijk toch weer vriendjes met de geworden om zo katoen te verkopen voor de industriële revolutie in Engeland. De overheid zorgde voor een verbod op import van slaven. Slavenhouders begonnen slavinnen veel kinderen te laten krijgen om zo hun slavenhandel te kunnen onderhouden. Dit zorgde ervoor dat de hoeveelheid slaven steeg van ½ miljoen in 1790 tot 4 miljoen in 1860.
In 1860 werd Abraham Lincoln president van Amerika. Hier was het westen echt niet blij mee dus ze splitste zich af. Vijf jaar(1865) en 1 burgeroorlog later won het noorden en werd slavernij afgeschaft.
**
[directory](moc/directory.md)
[SamenvattingenIndex](school/SamenvattingenIndex.md)
| 43.938144 | 545 | 0.78672 | nld_Latn | 1.000005 |
d5c8dde03e59a3388d6ac963f860a55e777b0c74 | 79 | md | Markdown | README.md | awkure/ogls | eabc1532e6922192fca718fc12f05f6950ba09cd | [
"MIT"
] | null | null | null | README.md | awkure/ogls | eabc1532e6922192fca718fc12f05f6950ba09cd | [
"MIT"
] | null | null | null | README.md | awkure/ogls | eabc1532e6922192fca718fc12f05f6950ba09cd | [
"MIT"
] | 1 | 2018-03-01T07:11:48.000Z | 2018-03-01T07:11:48.000Z | ## OpenGL Showcase 0.0.1.1
nothing to see here
| 13.166667 | 27 | 0.670886 | eng_Latn | 0.738097 |
d5cace2dfd9c68401ae37207bad965390ef98836 | 17,104 | md | Markdown | mdop/mbam-v25/understanding-mbam-25-stand-alone-reports.md | MicrosoftDocs/mdop-docs-pr.ru-ru | 568383949ef8ece1cef50567fcfac4bf4ee323c4 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-04-20T21:13:51.000Z | 2021-04-20T21:13:51.000Z | mdop/mbam-v25/understanding-mbam-25-stand-alone-reports.md | MicrosoftDocs/mdop-docs-pr.ru-ru | 568383949ef8ece1cef50567fcfac4bf4ee323c4 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-07-08T05:52:53.000Z | 2020-07-08T15:40:31.000Z | mdop/mbam-v25/understanding-mbam-25-stand-alone-reports.md | MicrosoftDocs/mdop-docs-pr.ru-ru | 568383949ef8ece1cef50567fcfac4bf4ee323c4 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-11-04T12:30:46.000Z | 2021-11-04T12:30:46.000Z | ---
title: Общие сведения об изолированных отчетах MBAM 2.5
description: Общие сведения об изолированных отчетах MBAM 2.5
author: dansimp
ms.assetid: 78b5aaf4-8257-4722-8eb9-e0de48db6a11
ms.reviewer: ''
manager: dansimp
ms.author: dansimp
ms.pagetype: mdop, security
ms.mktglfcycl: manage
ms.sitesec: library
ms.prod: w10
ms.date: 06/16/2016
ms.openlocfilehash: 45e84c7c3b2bcb1602890c7c5a09592324da691e
ms.sourcegitcommit: 354664bc527d93f80687cd2eba70d1eea024c7c3
ms.translationtype: MT
ms.contentlocale: ru-RU
ms.lasthandoff: 06/26/2020
ms.locfileid: "10812776"
---
# Общие сведения об изолированных отчетах MBAM 2.5
В этой статье описаны отчеты, доступные при работе с администрированием и мониторингом Microsoft BitLocker (MBAM) в изолированной топологии.
**Примечание.**
Если вы используете MBAM с топологией интеграции Configuration Manager, вы создаете отчеты из Configuration Manager, а не из MBAM. Дополнительные сведения об этих отчетах можно найти [в разделе Просмотр отчетов MBAM 2,5 для топологии интеграции Configuration Manager](viewing-mbam-25-reports-for-the-configuration-manager-integration-topology.md) .
## Общие сведения об изолированных отчетах о топологии MBAM
MBAM предоставляет три типа отчетов, которые можно использовать для отслеживания соответствия требованиям BitLocker для вашей организации.
- [Отчет о соответствии требованиям предприятия](#bkmk-enterprisecompliance)
- [Отчет о соответствии компьютера](#bkmk-compliance)
- [Отчет об аудите восстановления](#bkmk-recovery)
Чтобы получить доступ к отчетам MBAM при запуске MBAM в изолированной топологии, откройте веб-браузер и откройте веб-сайт администрирования и наблюдения. В левой строке меню выберите пункт **отчеты** . В верхней строке меню выберите отчет, который требуется создать. Дополнительные сведения о создании этих отчетов можно найти в разделе [Создание автономных отчетов MBAM 2,5](generating-mbam-25-stand-alone-reports.md).
### <a href="" id="bkmk-enterprisecompliance"></a>Отчет о соответствии требованиям предприятия
Этот тип отчета используется для сбора сведений о соответствии общего соответствия требованиям BitLocker в вашей организации. С помощью фильтров можно сузить результаты поиска, чтобы узнать больше о состоянии соответствия требованиям и состоянии ошибки на компьютерах в Организации.
**Общие сведения о корпоративном соответствии**
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Имя столбца</th>
<th align="left">Описание</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Управляемые компьютеры</p></td>
<td align="left"><p>Количество компьютеров, которым MBAM управлять.</p></td>
</tr>
<tr class="even">
<td align="left"><p>% Соответствия требованиям</p></td>
<td align="left"><p>Процент соответствия требованиям компьютеров в масштабах предприятия.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>% Не соответствует требованиям</p></td>
<td align="left"><p>Процент несоответствующих требованиям компьютеров в масштабах предприятия.</p></td>
</tr>
<tr class="even">
<td align="left"><p>% Исключении</p></td>
<td align="left"><p>Процент компьютеров, исключаемых из требования шифрования BitLocker.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>% Без исключения</p></td>
<td align="left"><p>Процент компьютеров без исключения из требования шифрования BitLocker.</p></td>
</tr>
<tr class="even">
<td align="left"><p>SDMI</p></td>
<td align="left"><p>Процент соответствия требованиям компьютеров в масштабах предприятия.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Не соответствует требованиям</p></td>
<td align="left"><p>Процент несоответствующих требованиям компьютеров в масштабах предприятия.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Облагаемый</p></td>
<td align="left"><p>Общее количество компьютеров, исключаемых из требования шифрования BitLocker.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Без исключения</p></td>
<td align="left"><p>Общее количество компьютеров без исключения из требований шифрования BitLocker.</p></td>
</tr>
</tbody>
</table>
**Сведения о компьютере в соответствии с требованиями предприятия**
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Имя столбца</th>
<th align="left">Описание</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Имя компьютера</p></td>
<td align="left"><p>Указанное пользователем DNS-имя, управляемое MBAM.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Доменное имя</p></td>
<td align="left"><p>Полное доменное имя, в котором находится клиентский компьютер и управляется MBAM.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Состояние соответствия требованиям</p></td>
<td align="left"><p>Состояние соответствия для компьютера согласно политике, указанной для компьютера. Состояния не соответствуют требованиям и не соответствуют требованиям. Дополнительные сведения о том, как интерпретировать состояние соответствия требованиям, можно найти в следующей таблице "требования соответствия требованиям предприятия".</p></td>
</tr>
<tr class="even">
<td align="left"><p>Исключение</p></td>
<td align="left"><p>Состояние, указывающее на то, исключен ли этот компьютер из политики BitLocker.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Сведения о статусе соответствия требованиям</p></td>
<td align="left"><p>Сообщения об ошибках и состоянии, связанные с состоянием соответствия компьютера согласно указанной политике.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Последний контакт</p></td>
<td align="left"><p>Дата и время последнего обращения компьютера к серверу для отправки отчета о состоянии соответствия требованиям. Частота контактов настраивается. Дополнительные сведения можно найти в разделе Параметры групповой политики MBAM.</p></td>
</tr>
</tbody>
</table>
### <a href="" id="bkmk-compliance"></a>Отчет о соответствии компьютера
Этот тип отчета используется для сбора сведений, относящихся к компьютеру или пользователю.
Чтобы просмотреть этот отчет, щелкните имя компьютера в отчете соответствие требованиям предприятия или введите имя компьютера в отчете соответствие требованиям к компьютеру. Этот отчет содержит подробные сведения о шифровании каждого диска (операционной системы и несъемных дисков с данными) на компьютере. Кроме того, она указывает политику, которая применяется к каждому типу дисков на компьютере. Чтобы просмотреть сведения о каждом диске, разверните элемент имя компьютера.
**Примечание.**
Состояние шифрования тома съемных данных не отображается в этом отчете.
**Поля отчета о соответствии компьютера**
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Имя столбца</th>
<th align="left">Описание</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Имя компьютера</p></td>
<td align="left"><p>Указанное пользователем DNS-имя компьютера, управляемое с помощью MBAM.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Доменное имя</p></td>
<td align="left"><p>Полное доменное имя, в котором находится клиентский компьютер и управляется MBAM.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Тип компьютера</p></td>
<td align="left"><p>Тип компьютера. Допустимые типы не являются переносимыми и переносимыми.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Операционная система</p></td>
<td align="left"><p>Тип операционной системы находится на клиентском компьютере, управляемом MBAM.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Состояние соответствия требованиям</p></td>
<td align="left"><p>Общее состояние соответствия требованиям для компьютера, управляемого с помощью MBAM. Допустимые состояния соответствуют требованиям и не соответствуют требованиям.</p>
<p>Обратите внимание, что состояние соответствия для каждого устройства (в приведенной ниже таблице) может указывать на разные состояния соответствия требованиям. Однако это поле представляет это состояние соответствия согласно указанной политике.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Стойкость шифра политики</p></td>
<td align="left"><p>Стойкость шифра, выбранная администратором во время MBAM политики (например, 128-bit с диффузором).</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Диск с операционной системой политики</p></td>
<td align="left"><p>Указывает, требуется ли шифрование для операционной системы, и отображается соответствующий тип предохранителя.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Политика — фиксированный диск с данными</p></td>
<td align="left"><p>Указывает, требуется ли шифрование для фиксированного диска с данными.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Съемный диск с данными политики</p></td>
<td align="left"><p>Указывает, требуется ли шифрование для съемного диска.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Пользователи устройств</p></td>
<td align="left"><p>Известные пользователи на компьютере, управляемом с помощью MBAM.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Исключение</p></td>
<td align="left"><p>Состояние, указывающее на то, исключен ли этот компьютер из политики BitLocker.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Изготовитель</p></td>
<td align="left"><p>Название изготовителя компьютера, которое отображается в BIOS компьютера.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Модель</p></td>
<td align="left"><p>Название модели изготовителя компьютера, как оно отображается в BIOS компьютера.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Сведения о статусе соответствия требованиям</p></td>
<td align="left"><p>Сообщения об ошибках и состоянии, связанные с состоянием соответствия компьютера согласно указанной политике.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Последний контакт</p></td>
<td align="left"><p>Дата и время последнего обращения компьютера к серверу для отправки отчета о состоянии соответствия требованиям. Частота контактов настраивается. Дополнительные сведения можно найти в разделе Параметры групповой политики MBAM.</p></td>
</tr>
</tbody>
</table>
**Поля "диск" для отчета о соответствии компьютера**
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Имя столбца</th>
<th align="left">Описание</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Буква диска</p></td>
<td align="left"><p>Буква диска компьютера, назначенная пользователем на определенный диск.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Тип диска</p></td>
<td align="left"><p>Тип диска. Допустимые значения: диск операционной системы и фиксированный диск с данными. Это физические диски, а не логические тома.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Стойкость шифра</p></td>
<td align="left"><p>Стойкость шифра, выбранная администратором в течение MBAM политики.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Тип предохранителя</p></td>
<td align="left"><p>Тип предохранителя, выбранный с помощью параметра групповой политики, используемого для шифрования операционной системы или фиксированного объема данных.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Состояние предохранителя</p></td>
<td align="left"><p>Указывает на то, что компьютер, управляемый MBAM, включил Тип предохранителя, указанный в политике. Допустимые состояния: ON и OFF.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Состояние шифрования</p></td>
<td align="left"><p>Состояние шифрования диска. Допустимые состояния шифруются, а не шифруются и шифруются.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Состояние соответствия требованиям</p></td>
<td align="left"><p>Состояние, указывающее, соответствует ли диск требованиям политики. Состояния не соответствуют требованиям и не соответствуют требованиям.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Сведения о статусе соответствия требованиям</p></td>
<td align="left"><p>Сообщения об ошибках и состоянии соответствия требованиям компьютера согласно указанной политике.</p></td>
</tr>
</tbody>
</table>
### <a href="" id="bkmk-recovery"></a>Отчет об аудите восстановления
Этот тип отчета используется для аудита пользователей, которые запросили доступ к ключам восстановления BitLocker. В отчете есть несколько фильтров, основанных на нужных критериях фильтрации. Вы можете отфильтровать по определенному типу пользователя (в службе поддержки пользователей или для конечного пользователя), о том, что запрос завершился сбоем или был успешно, определен требуемый тип ключа и диапазон дат, в течение которого произошло извлечение.
**Поля отчета аудита восстановления**
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Имя столбца</th>
<th align="left">Описание</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Дата и время запроса</p></td>
<td align="left"><p>Дата и время, когда запрос на получение ключа был выполнен конечным пользователем или пользователем службы поддержки.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Источник запросов аудита</p></td>
<td align="left"><p>Сайт, с которого был инициирован запрос. У этого элемента может быть одно из двух значений: <strong> портал самообслуживания </strong> или служба <strong> поддержки </strong> .</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Состояние запроса</p></td>
<td align="left"><p>Состояние запроса. Допустимые состояния успешно установлены (ключ был получен) или завершился сбоем (ключ не был получен).</p></td>
</tr>
<tr class="even">
<td align="left"><p>Пользователь службы поддержки</p></td>
<td align="left"><p>Пользователь службы поддержки, который инициировал запрос на получение ключа.</p>
<div class="alert">
<strong>Примечание.</strong><br/><p>Если пользователь расширенной справочной службы возводит ключ, не указывая конечного пользователя, <strong> поле конечного пользователя </strong> будет пустым. Пользователь службы поддержки должен указать конечного пользователя, и этот пользователь будет отображаться в этом поле.</p>
<p>При восстановлении с помощью портала самообслуживания будет указан конечный пользователь в этом поле и в <strong> поле конечных пользователей </strong> .</p>
</div>
<div>
</div></td>
</tr>
<tr class="odd">
<td align="left"><p>Конечный пользователь</p></td>
<td align="left"><p>Конечный пользователь, который инициировал запрос на получение ключа.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Компьютер</p></td>
<td align="left"><p>Имя компьютера, на котором был восстановлен компьютер.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Тип ключа</p></td>
<td align="left"><p>Тип ключа, запрошенный пользователем службы технической поддержки или конечным пользователем. Ниже перечислены три типа ключей, которые MBAM собирает.</p>
<ul>
<li><p>Пароль ключа восстановления (используется для восстановления компьютера в режиме восстановления)</p></li>
<li><p>ИД ключа восстановления (используется для восстановления компьютера в режиме восстановления от имени другого пользователя)</p></li>
<li><p>Хеш пароля TPM (используется для восстановления компьютера с заблокированным доверенным платформенным модулем)</p></li>
</ul></td>
</tr>
<tr class="even">
<td align="left"><p>Описание причины</p></td>
<td align="left"><p>Причина, по которой указанный тип ключа запрашивался пользователем службы поддержки или конечным пользователем. Причины указаны в разделе Восстановление диска и управление функциями доверенного платформенного модуля на веб-сайте администрирования и мониторинга. Допустимые значения — это введенный пользователем текст или один из указанных ниже кодов причин.</p>
<ul>
<li><p>Порядок загрузки операционной системы изменился</p></li>
<li><p>BIOS изменилась</p></li>
<li><p>Изменены файлы операционной системы</p></li>
<li><p>Потерянный ключ запуска</p></li>
<li><p>Потерянный ПИН-код</p></li>
<li><p>Сброс доверенного платформенного модуля</p></li>
<li><p>Утеряна парольная фраза</p></li>
<li><p>Потерялась смарт-карта</p></li>
<li><p>Сброс блокировки ПИН-кода</p></li>
<li><p>Включить доверенный платформенный модуль</p></li>
<li><p>Отключение доверенного платформенного модуля</p></li>
<li><p>Изменение пароля доверенного платформенного модуля</p></li>
<li><p>Очистить доверенный платформенный модуль</p></li>
</ul></td>
</tr>
</tbody>
</table>
**Примечание.**
Результаты отчета можно сохранить в файл, нажав кнопку " **Экспорт** " в строке меню " **отчеты** ".
## Статьи по теме
[Мониторинг и создание отчетов по соответствию BitLocker с помощью MBAM 2.5](monitoring-and-reporting-bitlocker-compliance-with-mbam-25.md)
[Создание изолированных отчетов MBAM 2.5](generating-mbam-25-stand-alone-reports.md)
## У вас есть предложение MBAM?
- Здесь вы можете добавить предложения и проголосовать [здесь](http://mbam.uservoice.com/forums/268571-microsoft-bitlocker-administration-and-monitoring).
- Для MBAM проблемы используйте [MBAM Форум TechNet](https://social.technet.microsoft.com/Forums/home?forum=mdopmbam).
| 43.521628 | 478 | 0.746024 | rus_Cyrl | 0.881839 |
d5cb5d81b73b466e19b80694a7d358dd2e124fe7 | 278 | md | Markdown | add/metadata/System.Web.UI.WebControls/GridViewPageEventArgs.meta.md | loreley-larisa/dotnet-api-docs | d42d6e7178e293d24939d4a3bd5b2f43973c82ba | [
"CC-BY-4.0",
"MIT"
] | null | null | null | add/metadata/System.Web.UI.WebControls/GridViewPageEventArgs.meta.md | loreley-larisa/dotnet-api-docs | d42d6e7178e293d24939d4a3bd5b2f43973c82ba | [
"CC-BY-4.0",
"MIT"
] | null | null | null | add/metadata/System.Web.UI.WebControls/GridViewPageEventArgs.meta.md | loreley-larisa/dotnet-api-docs | d42d6e7178e293d24939d4a3bd5b2f43973c82ba | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-03-27T19:35:47.000Z | 2019-03-27T19:35:47.000Z | ---
uid: System.Web.UI.WebControls.GridViewPageEventArgs
ms.author: "riande"
---
---
uid: System.Web.UI.WebControls.GridViewPageEventArgs.#ctor(System.Int32)
ms.author: "riande"
---
---
uid: System.Web.UI.WebControls.GridViewPageEventArgs.NewPageIndex
ms.author: "riande"
---
| 18.533333 | 72 | 0.744604 | yue_Hant | 0.606706 |
d5cbcbcd9b6118a51eca1231857fb1bd874f8ebb | 651 | md | Markdown | docs/api/nn/conv.md | marcelroed/equinox | 3804a8d60217bde685bee0a893a7bd55b1e63c26 | [
"Apache-2.0"
] | null | null | null | docs/api/nn/conv.md | marcelroed/equinox | 3804a8d60217bde685bee0a893a7bd55b1e63c26 | [
"Apache-2.0"
] | null | null | null | docs/api/nn/conv.md | marcelroed/equinox | 3804a8d60217bde685bee0a893a7bd55b1e63c26 | [
"Apache-2.0"
] | null | null | null | # Convolutional
::: equinox.nn.Conv
selection:
members:
- __init__
- __call__
---
::: equinox.nn.ConvTranspose
selection:
members:
- __init__
- __call__
---
::: equinox.nn.Conv1d
selection:
members: false
---
::: equinox.nn.Conv2d
selection:
members: false
---
::: equinox.nn.Conv3d
selection:
members: false
---
::: equinox.nn.ConvTranspose1d
selection:
members: false
---
::: equinox.nn.ConvTranspose2d
selection:
members: false
---
::: equinox.nn.ConvTranspose3d
selection:
members: false
| 12.519231 | 30 | 0.545315 | eng_Latn | 0.43974 |
d5cbcffb5d4dcfcb2224e17f20969f3dbe880da3 | 2,809 | md | Markdown | _posts/2020-06-26-leetcode-interview-0201.md | codeFarmer1118/qilixiang.github.io | c94d7becfc1590049a9919547c74029f16e45eed | [
"Apache-2.0"
] | 7 | 2017-09-24T11:53:14.000Z | 2017-12-25T10:09:07.000Z | _posts/2020-06-26-leetcode-interview-0201.md | whvixd/qilixiang.github.io | ee4d26f94ab08850b92188d605aec2e01246e2d2 | [
"Apache-2.0"
] | null | null | null | _posts/2020-06-26-leetcode-interview-0201.md | whvixd/qilixiang.github.io | ee4d26f94ab08850b92188d605aec2e01246e2d2 | [
"Apache-2.0"
] | null | null | null | ---
layout: post
title: leetcode interview 0201
subtitle: 移除重复节点
date: 2020-06-26
author: Static
header-img:
catalog: true
tags:
- leetcode之每日一题
---
> 题目链接:[https://leetcode-cn.com/problems/remove-duplicate-node-lcci/](https://leetcode-cn.com/problems/remove-duplicate-node-lcci/)
## 题目描述
<html>
<img src="/img/leetcode/leetcode-interview-0201.png" width="700" height="700" />
</html>
---
## 分析
#### 1. 双重循环
---
## 代码实现
```java
public enum QInterview0201 {
instance;
public ListNode removeDuplicateNodes(ListNode head) {
ListNode p=head;
while (p!=null){
ListNode r=p;
while (r.next!=null){
if(p.val==r.next.val){
// 删除重复节点
r.next=r.next.next;
continue;
}
r=r.next;
}
p=p.next;
}
return head;
}
public static void main(String[] args) {
ListNode node1 = ListNode.createByArray(new int[]{1, 2, 3, 3, 2, 1});
QInterview0201.instance.removeDuplicateNodes(node1);
// assert [1, 2, 3]
ListNode.print(node1);
ListNode node2 = ListNode.createByArray(new int[]{1, 1, 1, 1, 2});
QInterview0201.instance.removeDuplicateNodes(node2);
// assert [1, 2]
ListNode.print(node2);
}
}
```
> **ListNode.java**
```java
public class ListNode {
public int val;
public ListNode next;
public ListNode(){}
public ListNode(int x) {
val = x;
}
public static void print(ListNode l, String preMessage, String postMessage) {
preMessage=preMessage==null?"":preMessage;
postMessage=postMessage==null?"":postMessage;
ListNode head = l;
StringBuilder sb = new StringBuilder();
sb.append(preMessage);
while (head != null) {
sb.append(head.val);
head = head.next;
if (head != null) {
sb.append("->");
}
}
sb.append(postMessage);
System.out.println(sb);
}
public static void print(ListNode l) {
print(l, null, null);
}
public static void print(String preMessage, ListNode l) {
print(l, preMessage, null);
}
public static void print(ListNode l, String postMessage) {
print(l, null, postMessage);
}
public static ListNode createByArray(int[] array){
if(array.length==0) return null;
ListNode head =new ListNode(0);
ListNode point=head;
for(int e:array){
point=point.next=new ListNode(e);
}
return head.next;
}
}
```
**If you want to live in happiness,you should love your life. (Britain)Johnson**
> 要想生活快乐，就必须热爱生活。-- \[英] 约翰逊 | 22.837398 | 131 | 0.555714 | kor_Hang | 0.200635 |
d5cbd6d9c9c1e1657c7da744665b6e07b7f1195b | 16,119 | md | Markdown | Agile_process.md | kbase/project_guides | 2973668ebf5278f7b78f0811e45d0721d5dcaf25 | [
"MIT"
] | 8 | 2015-04-15T22:07:14.000Z | 2020-11-03T15:43:02.000Z | Agile_process.md | kbase/project_guides | 2973668ebf5278f7b78f0811e45d0721d5dcaf25 | [
"MIT"
] | 69 | 2015-04-02T01:30:06.000Z | 2020-05-11T20:15:59.000Z | Agile_process.md | kbase/project_guides | 2973668ebf5278f7b78f0811e45d0721d5dcaf25 | [
"MIT"
] | 41 | 2015-04-02T00:40:14.000Z | 2020-11-01T01:45:04.000Z | ## Overview
In an Agile development process requirements and solutions evolve
through collaboration between cross-functional teams. It promotes
adaptive planning, evolutionary development, early delivery, continuous
improvement, and encourages rapid and flexible response to change. In
addition, it promotes ownership, accountability and transparency by
requiring all members to contribute and visibly communicating the
current priorities and progress on active priorities.
The KBase Executive Committee will prioritize Campaigns (one to two
month long development efforts for 3-5 people) that can be completed in
one or more Sprints (two weeks of effort for 3-5 people). KBase will run
2-week Sprint sessions with four teams. Each team would have 3-5
members. A Sprint team would have a product owner (the person
responsible for ensuring the product is done right as a whole); the
product owner could change from Sprint to Sprint based on what is being
targeted. The Sprint Teams may also change composition, but we would try
to avoid too much change since building up a strong functional team is
an important component of Agile.
A key principle of Agile is iterative improvement. This applies to the
process, as well as development. Consequently, the process should evolve
based on experience and feedback. The proposal below should be thought
of as a starting point that will be improved through an explicit
Retrospective process that improves after every 2 week Sprint cycle.
## Team Configurations
Fundamentally, co-localization supports high bandwidth discussion and
communication. However, because of the distributed nature of the KBase
project, we will have some teams with members that are from multiple
sites. We will aim for a balance. The team compositions can and will
change, but we will aim for continuity as much as possible since this
helps build familiarity and camaraderie. The LRM (Fernando Perez) and
Production Lead (Shane Canon) will be responsible for balancing team
composition before each Sprint.
Members of a Sprint should be working on the Sprint tasks for at least
60% time during the Sprint window (i.e. 6/10 days) and available for
discussion throughout. Staff that are at fractional effort or have a
small amount of effort allocated to “Sprint-able” Teams should
consolidate time and communicate when they will be available.
Product Owners may be chosen from outside the Production boxes, for
example, when a person has a firm understanding of what needs to be
delivered for a specific item.
As described below, each sprint will start with a team meeting to decide
on scoping, roles and task breakdown. Each sprint team will have a
designated representative that attends a Sprint Oversight meeting. These
will occur one to two times a week and are meant to identify any
conflicts between Sprint teams. However, it is likely that the
Production Lead and LRM will attempt to select Sprints such that the
tasks are non-overlapping/interacting.
Depending on the sprint goals, we will experiment with having members of
the UE documentation team be part of the sprint teams to help create
documentation and tutorials.
### Non-Sprint Personnel
Some team members posses critical science knowledge. These members may
be assigned to specific teams or designated as product owners when a
deliverable aligns with their expertise. For KBase developers who are
very low percent effort, or are otherwise unable to join a Sprint, they
will coordinate with their box lead to identify tasks.
## Sprint Cycle
We will use a two week Sprint Cycle. At first we will include a one week
period between each Sprint or every two Sprints to capture cleanup
items, maintenance, and other tasks that don’t neatly fit into a Sprint
model. Over time we will try to reduce these.
- Each Sprint will start with a two hour planning meeting with the
Product Owner and Team members (described below).
- Each Sprint Team should have a short (15 minutes) daily meeting to
cover what was done the previous day, what is on deck for that day,
and any critical blockers.
- The Sprints will end with a Retrospective. This will be used to
assess how much of the Campaign the Sprint accomplished, remaining
or incomplete items will return to the Campaigns backlog. New items
that come up during the Sprint will also be added to the backlog.
The Retrospective will also be used to discuss any lessons learned
during the Sprint and suggest changes.
<table>
<tbody>
<tr class="odd">
<td align="left"></td>
<td align="left">Monday</td>
<td align="left">Tuesday</td>
<td align="left">Wednesday</td>
<td align="left">Thursday</td>
<td align="left">Friday</td>
</tr>
<tr class="even">
<td align="left">Week 1</td>
<td align="left">Planning Meeting</td>
<td align="left">Daily</td>
<td align="left">Daily</td>
<td align="left">Daily</td>
<td align="left">Daily</td>
</tr>
<tr class="odd">
<td align="left">Week 2</td>
<td align="left">Daily</td>
<td align="left">Daily</td>
<td align="left">Daily</td>
<td align="left">Daily</td>
<td align="left"><p>Sprint</p>
<p>Retrospective</p></td>
</tr>
<tr class="even">
<td align="left"><p>Week 3</p>
<p>[maintenance & steady state activities]</p></td>
<td align="left">Report out to all@kbase</td>
<td align="left">E.C. evaluation</td>
<td align="left">E.C. reprioritization</td>
<td align="left">Team and Product Owner assignments</td>
<td align="left"></td>
</tr>
</tbody>
</table>
## Deliverables: Sprints and Campaigns
Deliverables will be split into Sprints and Campaigns. A deliverable
(Sprint or Campaign) should result in a complete “product” that,
usually, results in a user visible item (i.e. a new feature or
component). However, some items may be more internal (i.e. architecture
changes, refactoring). For deliverables that are too big for a Sprint,
they will be organized in Campaigns which can include multiple Sprints.
However, Campaigns shouldn’t exceed four Sprints. This is to avoid
having deliverables that take too long to provide a finished product
which delays feedback.
Problems that require long-term thinking and effort, such as the repayment of
technical debt, architectural evolution or the replacement of a major
component, should still be able to break down the long-term problem into
campaigns and then further into sprints. This encourages a focus of these
efforts into cycles where concrete feedback and outcomes can be attained.
## Priority List (Product Backlog)
The project will maintain a global publicly visible priority list of
deliverables. This list will be maintained by the EC with input from the
Production Leads, Science Engagement, and User Engagement. This list is
a living document that will be updated periodically both to reflect
completed work but also changing priorities. Prior to each Sprint, the
Production Leads and LRM will determine which major Sprints or Campaigns
will be tackled during the next Sprint cycle. This selection will be
shared with the entire project. In general, the highest priorities will
be selected, but conflicts, resource balancing or critical maintenance
items may influence the selection. Deferring an item shouldn’t be
problematic since the item will likely get prioritized in subsequent
sprints.
## Coordination with Science Engagement
The Science Engagement team will also participate in the Sprint process.
After some initial prototyping is done with the selected collaborators,
the collaboration lead will write a campaign doc and submit it to the
E.C. for scheduling/prioritization. These campaigns can be for hardening
the prototype services, data models and visualizations and pushing the
functionality out to the live site. There may also be some situations
where SE will need sprints to create the initial prototypes.
## Coordination with User Engagement
User Engagement will also be able to create Sprints and Campaigns. There
will be situations where UE, based on feedback from users or upcoming
outreach events, will initiate campaigns around tutorials or user
requested functionality. For example, based on user feedback, UE may
determine that by adding a new narrative tree algorithm we could capture
a significant number of new users. They would write up a Campaign and
submit it to the EC. In another case, UE may determine that they need
new material for an upcoming workshop, and this would be a Sprint
requiring effort from developers and scientists working with the UE.
## Coordination with Release Engineering
We expect that most Sprints will create deployable functionality that
will be immediately deployed on CI and next.kbase.us and will eventually
move to production in a rapid time-frame (weeks). Some Campaigns may
have more disruptive changes (e.g., format changes) that require more
significant deployment; those migration and deployment activities should
be integrated into the Campaign and include Sprints to address those
changes.
## Pre-Sprint Planning
After a campaign is selected, the product owner will meet with the
sprint team to plan the sprint. During this process, the sprint team and
product owner will generate user stories, discuss what the deliverables
of each user story entails and select a set of stories to complete
during the sprint. At this point, each user story will be broken down
into tasks. The user stories can then be shared with the project and
individual tasks can be added to JIRA for tracking.
The sprint-planning team will be responsible for evaluating each task in
the context of KBase wide integration to prevent redundancy, silos and
inconsistencies.
## Coordination between Sprint Teams and Box Leads
For Sprints that directly impact areas controlled by a box lead, we
expect that the Sprint team will include the box lead and/or members of
that box. Once or twice a week, there will be a Sprint Oversight
meeting. During this meeting the selected representative from each
Sprint will meet with the Production Lead, LRM and Box Leads. At this
meeting both direct and indirect impacts on Box Areas will be discussed
and activity from the Sprints can be reviewed to ensure that design and
implementation choices align with the broader project principles and
goals.
## Reporting and Tracking
The priority list is
[maintained and publicly visible here](https://docs.google.com/spreadsheets/d/1RYqniwN816QkaJqRJgsHXqkuIkFZ3S90dVD0RjR4jxk/edit?usp=sharing). As
Campaigns are selected for a Sprint Cycle and the planning is completed, the
team will create and assign JIRA tickets to track tasks, and below we describe
the process for proposing new sprints and campaigns.
At the end of each Sprint, the teams will create a formal summary and present
the results of their Retrospective on the Monday Report Out Meeting (this
summary should be linked into the original Sprint issue that was created when
the Sprint was approved). These results may also include lessons learned for
improving future Sprints. Each Sprint team will have a half an hour for
presentation and discussion. All KBase personnel are invited to attend. These
reports can then be used for creating progress reports to DOE.
## Management
The primary role of the EC and PIs will be to maintain the
prioritization list and provide feedback to the Production Lead and LRM.
The Production Lead and LRM are responsible for sequencing Sprints and
managing the Sprint Teams. The EC and PI will have opportunities to
adjust the priorities during the Sprint-Free week and quarterly Project
Planning Meetings.
We can also allocate fixed number of sprints per cycle for specific
areas. For instance, management may determine that there should always
be a UI campaign.
## Process for proposing new sprints or campaigns
To propose a new sprint, the process to follow is:
1. Open a new issue on JIRA, and assign to it the issue type "Proposed Sprint"
(we don't have a separate type for sprints and campaigns):
2. Provide in the *Summary* field a one sentece description of the sprint.
2. Fill out the *Description* field with a body of text according to the
template in the section immediately below. It should be relatively concise,
but try to answer each of these questions clearly, so that the group leads
and KBase executive committee can use this information to decide whether to
accept your proposal and put it into the sprint pipeline.
2. Assign it to Shane Canon, the production lead.
2. List any components you may think it impacts, if you know in advance.
2. At this time, don't bother adding Epic/Theme or Sprint labels yet, as those
will be added if the sprint is actually accepted for execution later on.
### Template
**Why it’s important:** Explain why KBase should do this. How will it
help make KBase unique, bring in users, improve the system, etc. Why is
it more important for KBase to do this compared to other priorities.
**What needs to be done?** Provide a brief paragraph describing what has
to be done including new data types, new UI pieces, example, etc. Be
complete but avoid going into implementation details. This is more
about understanding the scope of the activity versus exactly how it will
be done.
**Estimated Number of Sprints:** X sprints
**Key Staff:** List important staff needed for the Sprint and what
specific skills and knowledge they provide.
**Dependencies:** List any other campaigns, sprints, or activities
that impact your proposed sprint or campaign.
### Evaluation of sprint proposals
Once a sprint/campaign proposal is submitted, there may be discussion and
questions about it directly on the JIRA ticket. The members of the KBase
Executive Committee, who ultimately will make the decisions on which sprints to
put into the implementation pipeline, will be added as watchers to the ticket
so they have a chance to comment.
Then, during the next maintenance week, the EC will include in its evaluation
and re-prioritization decisions (that normally consider the outcome of the
just-finished sprint cycle) any new proposals that have arrived. This will
allow the EC to weigh these proposals in the context of the outcomes and
feedback of the recently concluded sprint cycle.
The EC can decide to assign the proposals either to immediate execution in the
next cycle, to be put in the queue for a later cycle, or it can decline the
proposal.
If a proposal is accepted, it will be given a sprint label and an epic/theme in
JIRA so it can be sorted accordingly, and it will be re-assigned to its
ultimate product owner.
If a proposal is rejected, the rejection type will be one of:
* *Reject*: As written, this proposal is not going to happen, and the reasons
why will be communicated.
* *Reconsider*: We foresee doing this, but it needs to wait for N sprint cycles
to be re-evaluated. The resolution should specify what is blocking and how
many cycles to wait before resubmission (point at which, there may be new
information to consider).
* *Not discussed*: We didn't get around to talking about it; we will get to it
next time. This is not ideal, but realistically it will happen sometimes.
This information will be recorded in the proposal ticket, so the submitter will
have a record of the decision.
# Remaining questions
These are a few questions that arose in the previous PR regarding how the Agile
development process and decisions are made. We should at least clarify some of
them:
* A request for more transparency from EC on decision process: agenda and
outcomes, as they pertain to the development process, should be shared with
the team.
* How is work outside of the sprint cycles reported, managed, or decided on?
* Does the Executive committee review work that is not part of the sprint
cycles?
* How do the working teams get a finer-granularity and updated description of
priorities and project vision? This seems critically necessary to have clear
objectives and goals that to plan against. Basically, a dynamic, living
version of the project high-level roadmap that is updated periodically by the
EC.
| 45.792614 | 144 | 0.791426 | eng_Latn | 0.999662 |
d5cbea5817950cfc3a294023af21e2add1855fb4 | 1,974 | md | Markdown | docs/extend/reference/client/context.md | geverghe/vsts-docs | e5047a149ea3e93e52ab49c7e6d653b418e817a5 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-03-03T18:57:40.000Z | 2020-03-03T18:57:40.000Z | docs/extend/reference/client/context.md | geverghe/vsts-docs | e5047a149ea3e93e52ab49c7e6d653b418e817a5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/extend/reference/client/context.md | geverghe/vsts-docs | e5047a149ea3e93e52ab49c7e6d653b418e817a5 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-02-06T06:41:54.000Z | 2021-07-14T10:42:31.000Z | ---
ms.prod: devops
ms.technology: devops-ecosystem
title: Web Context | Extensions for Azure DevOps Services
description: Context data available in your web extensions
ms.assetid: b926a050-1e70-4907-8963-e4f2ee9939e5
ms.manager: mijacobs
ms.author: chcomley
author: chcomley
ms.topic: article
monikerRange: '>= tfs-2017'
ms.date: 08/04/2016
---
# Web context
The `core SDK` provides an API for getting context information, for example the current project's ID (if your extension is operating at a project or team level).
### Usage
#### Example
```json
{
"id": "my-extension",
...
"baseUri": "https://{{account.name}}.myservice.com/my-extension/{{project.id}}"
}
```
### Full JSON example
```json
{
"user": {
"id": "d6245f20-2af8-44f4-9451-8107cb2767db",
"name": "Norman Paulk",
"email": "[email protected]",
"uniqueName": "[email protected]"
},
"team": {
"id": "a63ff425-76b0-4dac-9b81-b265fb361da4",
"name": "Quality assurance",
"userIsMember": true,
"userIsAdmin": true
},
"project": {
"id": "c501f0f0-9dca-40a3-ac5a-4d2d9a4a1825",
"name": "Fabrikam-Fiber-Git"
},
"collection": {
"id": "7696cd7b-25fd-4378-b5f2-7c97228ee542",
"name": "DefaultCollection",
"uri": "https://dev.azure.com/fabrikam/DefaultCollection/",
"relativeUri": "/DefaultCollection/"
},
"account": {
"id": "dab4b99d-4317-4b8a-98b8-f02ecaceb5b4",
"name": "fabrikam",
"uri": "https://dev.azure.com/fabrikam/",
"relativeUri": "/"
},
"host": {
"id": "7696cd7b-25fd-4378-b5f2-7c97228ee542",
"name": "DefaultCollection",
"uri": "https://dev.azure.com/fabrikam/DefaultCollection/",
"relativeUri": "/DefaultCollection/",
"hostType": "projectCollection",
"scheme": "https",
"authority": "dev.azure.com/fabrikam"
}
}
```
| 25.307692 | 161 | 0.609422 | yue_Hant | 0.151483 |
d5cc3b4685295664577e4e46b6af9e04e5689e5c | 500 | md | Markdown | errors/no-color.md | zicht/zss | 97d0d7f57fad7c5d59c294d644d0e57767d26dac | [
"MIT"
] | 18 | 2017-09-12T11:55:24.000Z | 2022-03-08T10:20:38.000Z | errors/no-color.md | zicht/zss | 97d0d7f57fad7c5d59c294d644d0e57767d26dac | [
"MIT"
] | 28 | 2017-09-14T09:18:25.000Z | 2021-09-10T12:20:47.000Z | errors/no-color.md | zicht/zss | 97d0d7f57fad7c5d59c294d644d0e57767d26dac | [
"MIT"
] | 4 | 2017-12-12T13:14:36.000Z | 2021-07-26T17:23:34.000Z | # No color
#### Why this error occurred
The mixin `get-color` is called with a color name that is not defined in `$zss--colors`.
#### Possible ways to fix it
The error message contains the name of the invalid color. Check the definition of `$zss--colors` and either:
- find the invalid call in your Sass source code and change the parameter of `get-color` to a value that
_is_ defined in `$zss--colors`.
- add the missing name as a key/value pair to the `$zss--colors` map, e.g. `orange: #f90`.
| 35.714286 | 108 | 0.718 | eng_Latn | 0.998504 |
d5ccf2e9271624258fdd3fba96d56671fd4a0a63 | 31,655 | md | Markdown | articles/virtual-machines/workloads/sap/sap-high-availability-installation-wsfc-shared-disk.md | fuatrihtim/azure-docs.tr-tr | 6569c5eb54bdab7488b44498dc4dad397d32f1be | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/virtual-machines/workloads/sap/sap-high-availability-installation-wsfc-shared-disk.md | fuatrihtim/azure-docs.tr-tr | 6569c5eb54bdab7488b44498dc4dad397d32f1be | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/virtual-machines/workloads/sap/sap-high-availability-installation-wsfc-shared-disk.md | fuatrihtim/azure-docs.tr-tr | 6569c5eb54bdab7488b44498dc4dad397d32f1be | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Azure 'da SAP ASCS/SCS örneği için Windows Yük devretme kümesine ve paylaşılan diske SAP NetWeaver HA 'yi yüklemeyin | Microsoft Docs
description: SAP NetWeaver HA 'yi bir Windows Yük devretme kümesine ve paylaşılan diske bir SAP ASCS/SCS örneği için nasıl yükleyeceğinizi öğrenin.
services: virtual-machines-windows,virtual-network,storage
documentationcenter: saponazure
author: rdeltcheva
manager: juergent
editor: ''
tags: azure-resource-manager
keywords: ''
ms.assetid: 6209bcb3-5b20-4845-aa10-1475c576659f
ms.service: virtual-machines-sap
ms.topic: article
ms.tgt_pltfrm: vm-windows
ms.workload: infrastructure-services
ms.date: 08/12/2020
ms.author: radeltch
ms.custom: H1Hack27Feb2017
ms.openlocfilehash: 12cfd39cf1358dcef79c3843627f0b45dc688c9e
ms.sourcegitcommit: 910a1a38711966cb171050db245fc3b22abc8c5f
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 03/20/2021
ms.locfileid: "101667943"
---
# <a name="install-sap-netweaver-ha-on-a-windows-failover-cluster-and-shared-disk-for-an-sap-ascsscs-instance-in-azure"></a>Azure 'da SAP ASCS/SCS örneği için Windows Yük devretme kümesine ve paylaşılan diske SAP NetWeaver HA 'yi yüklemeyin
[1928533]:https://launchpad.support.sap.com/#/notes/1928533
[1999351]:https://launchpad.support.sap.com/#/notes/1999351
[2015553]:https://launchpad.support.sap.com/#/notes/2015553
[2178632]:https://launchpad.support.sap.com/#/notes/2178632
[2243692]:https://launchpad.support.sap.com/#/notes/2243692
[sap-installation-guides]:http://service.sap.com/instguides
[azure-resource-manager/management/azure-subscription-service-limits]:../../../azure-resource-manager/management/azure-subscription-service-limits.md
[azure-resource-manager/management/azure-subscription-service-limits-subscription]:../../../azure-resource-manager/management/azure-subscription-service-limits.md
[dbms-guide]:../../virtual-machines-windows-sap-dbms-guide.md
[deployment-guide]:deployment-guide.md
[dr-guide-classic]:https://go.microsoft.com/fwlink/?LinkID=521971
[getting-started]:get-started.md
[ha-guide]:sap-high-availability-guide.md
[sap-high-availability-architecture-scenarios]:sap-high-availability-architecture-scenarios.md
[sap-high-availability-guide-wsfc-shared-disk]:sap-high-availability-guide-wsfc-shared-disk.md
[sap-high-availability-guide-wsfc-file-share]:sap-high-availability-guide-wsfc-file-share.md
[sap-ascs-high-availability-multi-sid-wsfc]:sap-ascs-high-availability-multi-sid-wsfc.md
[sap-high-availability-infrastructure-wsfc-shared-disk]:sap-high-availability-infrastructure-wsfc-shared-disk.md
[sap-high-availability-installation-wsfc-shared-disk]:sap-high-availability-installation-wsfc-shared-disk.md
[sap-ha-guide-8.9]:high-availability-guide.md#fe0bd8b5-2b43-45e3-8295-80bee5415716
[sap-ha-guide-8.11]:high-availability-guide.md#661035b2-4d0f-4d31-86f8-dc0a50d78158
[sap-hana-ha]:sap-hana-high-availability.md
[sap-suse-ascs-ha]:high-availability-guide-suse.md
[planning-guide]:planning-guide.md
[planning-guide-11]:planning-guide.md
[planning-guide-2.1]:planning-guide.md#1625df66-4cc6-4d60-9202-de8a0b77f803
[planning-guide-2.2]:planning-guide.md#f5b3b18c-302c-4bd8-9ab2-c388f1ab3d10
[planning-guide-microsoft-azure-networking]:planning-guide.md#61678387-8868-435d-9f8c-450b2424f5bd
[planning-guide-storage-microsoft-azure-storage-and-data-disks]:planning-guide.md#a72afa26-4bf4-4a25-8cf7-855d6032157f
[sap-high-availability-infrastructure-wsfc-shared-disk]:sap-high-availability-infrastructure-wsfc-shared-disk.md
[sap-ha-guide-figure-1000]:./media/virtual-machines-shared-sap-high-availability-guide/1000-wsfc-for-sap-ascs-on-azure.png
[sap-ha-guide-figure-1001]:./media/virtual-machines-shared-sap-high-availability-guide/1001-wsfc-on-azure-ilb.png
[sap-ha-guide-figure-1002]:./media/virtual-machines-shared-sap-high-availability-guide/1002-wsfc-sios-on-azure-ilb.png
[sap-ha-guide-figure-2000]:./media/virtual-machines-shared-sap-high-availability-guide/2000-wsfc-sap-as-ha-on-azure.png
[sap-ha-guide-figure-2001]:./media/virtual-machines-shared-sap-high-availability-guide/2001-wsfc-sap-ascs-ha-on-azure.png
[sap-ha-guide-figure-2003]:./media/virtual-machines-shared-sap-high-availability-guide/2003-wsfc-sap-dbms-ha-on-azure.png
[sap-ha-guide-figure-2004]:./media/virtual-machines-shared-sap-high-availability-guide/2004-wsfc-sap-ha-e2e-archit-template1-on-azure.png
[sap-ha-guide-figure-2005]:./media/virtual-machines-shared-sap-high-availability-guide/2005-wsfc-sap-ha-e2e-arch-template2-on-azure.png
[sap-ha-guide-figure-3000]:./media/virtual-machines-shared-sap-high-availability-guide/3000-template-parameters-sap-ha-arm-on-azure.png
[sap-ha-guide-figure-3001]:./media/virtual-machines-shared-sap-high-availability-guide/3001-configuring-dns-servers-for-Azure-vnet.png
[sap-ha-guide-figure-3002]:./media/virtual-machines-shared-sap-high-availability-guide/3002-configuring-static-IP-address-for-network-card-of-each-vm.png
[sap-ha-guide-figure-3003]:./media/virtual-machines-shared-sap-high-availability-guide/3003-setup-static-ip-address-ilb-for-ascs-instance.png
[sap-ha-guide-figure-3004]:./media/virtual-machines-shared-sap-high-availability-guide/3004-default-ascs-scs-ilb-balancing-rules-for-azure-ilb.png
[sap-ha-guide-figure-3005]:./media/virtual-machines-shared-sap-high-availability-guide/3005-changing-ascs-scs-default-ilb-rules-for-azure-ilb.png
[sap-ha-guide-figure-3006]:./media/virtual-machines-shared-sap-high-availability-guide/3006-adding-vm-to-domain.png
[sap-ha-guide-figure-3007]:./media/virtual-machines-shared-sap-high-availability-guide/3007-config-wsfc-1.png
[sap-ha-guide-figure-3008]:./media/virtual-machines-shared-sap-high-availability-guide/3008-config-wsfc-2.png
[sap-ha-guide-figure-3009]:./media/virtual-machines-shared-sap-high-availability-guide/3009-config-wsfc-3.png
[sap-ha-guide-figure-3010]:./media/virtual-machines-shared-sap-high-availability-guide/3010-config-wsfc-4.png
[sap-ha-guide-figure-3011]:./media/virtual-machines-shared-sap-high-availability-guide/3011-config-wsfc-5.png
[sap-ha-guide-figure-3012]:./media/virtual-machines-shared-sap-high-availability-guide/3012-config-wsfc-6.png
[sap-ha-guide-figure-3013]:./media/virtual-machines-shared-sap-high-availability-guide/3013-config-wsfc-7.png
[sap-ha-guide-figure-3014]:./media/virtual-machines-shared-sap-high-availability-guide/3014-config-wsfc-8.png
[sap-ha-guide-figure-3015]:./media/virtual-machines-shared-sap-high-availability-guide/3015-config-wsfc-9.png
[sap-ha-guide-figure-3016]:./media/virtual-machines-shared-sap-high-availability-guide/3016-config-wsfc-10.png
[sap-ha-guide-figure-3017]:./media/virtual-machines-shared-sap-high-availability-guide/3017-config-wsfc-11.png
[sap-ha-guide-figure-3018]:./media/virtual-machines-shared-sap-high-availability-guide/3018-config-wsfc-12.png
[sap-ha-guide-figure-3019]:./media/virtual-machines-shared-sap-high-availability-guide/3019-assign-permissions-on-share-for-cluster-name-object.png
[sap-ha-guide-figure-3020]:./media/virtual-machines-shared-sap-high-availability-guide/3020-change-object-type-include-computer-objects.png
[sap-ha-guide-figure-3021]:./media/virtual-machines-shared-sap-high-availability-guide/3021-check-box-for-computer-objects.png
[sap-ha-guide-figure-3022]:./media/virtual-machines-shared-sap-high-availability-guide/3022-set-security-attributes-for-cluster-name-object-on-file-share-quorum.png
[sap-ha-guide-figure-3023]:./media/virtual-machines-shared-sap-high-availability-guide/3023-call-configure-cluster-quorum-setting-wizard.png
[sap-ha-guide-figure-3024]:./media/virtual-machines-shared-sap-high-availability-guide/3024-selection-screen-different-quorum-configurations.png
[sap-ha-guide-figure-3025]:./media/virtual-machines-shared-sap-high-availability-guide/3025-selection-screen-file-share-witness.png
[sap-ha-guide-figure-3026]:./media/virtual-machines-shared-sap-high-availability-guide/3026-define-file-share-location-for-witness-share.png
[sap-ha-guide-figure-3027]:./media/virtual-machines-shared-sap-high-availability-guide/3027-successful-reconfiguration-cluster-file-share-witness.png
[sap-ha-guide-figure-3028]:./media/virtual-machines-shared-sap-high-availability-guide/3028-install-dot-net-framework-35.png
[sap-ha-guide-figure-3029]:./media/virtual-machines-shared-sap-high-availability-guide/3029-install-dot-net-framework-35-progress.png
[sap-ha-guide-figure-3030]:./media/virtual-machines-shared-sap-high-availability-guide/3030-sios-installer.png
[sap-ha-guide-figure-3031]:./media/virtual-machines-shared-sap-high-availability-guide/3031-first-screen-sios-data-keeper-installation.png
[sap-ha-guide-figure-3032]:./media/virtual-machines-shared-sap-high-availability-guide/3032-data-keeper-informs-service-be-disabled.png
[sap-ha-guide-figure-3033]:./media/virtual-machines-shared-sap-high-availability-guide/3033-user-selection-sios-data-keeper.png
[sap-ha-guide-figure-3034]:./media/virtual-machines-shared-sap-high-availability-guide/3034-domain-user-sios-data-keeper.png
[sap-ha-guide-figure-3035]:./media/virtual-machines-shared-sap-high-availability-guide/3035-provide-sios-data-keeper-license.png
[sap-ha-guide-figure-3036]:./media/virtual-machines-shared-sap-high-availability-guide/3036-data-keeper-management-config-tool.png
[sap-ha-guide-figure-3037]:./media/virtual-machines-shared-sap-high-availability-guide/3037-tcp-ip-address-first-node-data-keeper.png
[sap-ha-guide-figure-3038]:./media/virtual-machines-shared-sap-high-availability-guide/3038-create-replication-sios-job.png
[sap-ha-guide-figure-3039]:./media/virtual-machines-shared-sap-high-availability-guide/3039-define-sios-replication-job-name.png
[sap-ha-guide-figure-3040]:./media/virtual-machines-shared-sap-high-availability-guide/3040-define-sios-source-node.png
[sap-ha-guide-figure-3041]:./media/virtual-machines-shared-sap-high-availability-guide/3041-define-sios-target-node.png
[sap-ha-guide-figure-3042]:./media/virtual-machines-shared-sap-high-availability-guide/3042-define-sios-synchronous-replication.png
[sap-ha-guide-figure-3043]:./media/virtual-machines-shared-sap-high-availability-guide/3043-enable-sios-replicated-volume-as-cluster-volume.png
[sap-ha-guide-figure-3044]:./media/virtual-machines-shared-sap-high-availability-guide/3044-data-keeper-synchronous-mirroring-for-SAP-gui.png
[sap-ha-guide-figure-3045]:./media/virtual-machines-shared-sap-high-availability-guide/3045-replicated-disk-by-data-keeper-in-wsfc.png
[sap-ha-guide-figure-3046]:./media/virtual-machines-shared-sap-high-availability-guide/3046-dns-entry-sap-ascs-virtual-name-ip.png
[sap-ha-guide-figure-3046-ers2]:./media/virtual-machines-shared-sap-high-availability-guide/3046-dns-entry-sap-ers2-virtual-name-ip.png
[sap-ha-guide-figure-3047]:./media/virtual-machines-shared-sap-high-availability-guide/3047-dns-manager.png
[sap-ha-guide-figure-3048]:./media/virtual-machines-shared-sap-high-availability-guide/3048-default-cluster-probe-port.png
[sap-ha-guide-figure-3049]:./media/virtual-machines-shared-sap-high-availability-guide/3049-cluster-probe-port-after.png
[sap-ha-guide-figure-3050]:./media/virtual-machines-shared-sap-high-availability-guide/3050-service-type-ers-delayed-automatic.png
[sap-ha-guide-figure-5000]:./media/virtual-machines-shared-sap-high-availability-guide/5000-wsfc-sap-sid-node-a.png
[sap-ha-guide-figure-5001]:./media/virtual-machines-shared-sap-high-availability-guide/5001-sios-replicating-local-volume.png
[sap-ha-guide-figure-5002]:./media/virtual-machines-shared-sap-high-availability-guide/5002-wsfc-sap-sid-node-b.png
[sap-ha-guide-figure-5003]:./media/virtual-machines-shared-sap-high-availability-guide/5003-sios-replicating-local-volume-b-to-a.png
[sap-ha-guide-figure-6003]:./media/virtual-machines-shared-sap-high-availability-guide/6003-sap-multi-sid-full-landscape.png
[sap-templates-3-tier-multisid-xscs-marketplace-image]:https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fsap-3-tier-marketplace-image-multi-sid-xscs%2Fazuredeploy.json
[sap-templates-3-tier-multisid-xscs-marketplace-image-md]:https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fsap-3-tier-marketplace-image-multi-sid-xscs-md%2Fazuredeploy.json
[sap-templates-3-tier-multisid-db-marketplace-image]:https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fsap-3-tier-marketplace-image-multi-sid-db%2Fazuredeploy.json
[sap-templates-3-tier-multisid-db-marketplace-image-md]:https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fsap-3-tier-marketplace-image-multi-sid-db-md%2Fazuredeploy.json
[sap-templates-3-tier-multisid-apps-marketplace-image]:https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fsap-3-tier-marketplace-image-multi-sid-apps%2Fazuredeploy.json
[sap-templates-3-tier-multisid-apps-marketplace-image-md]:https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fsap-3-tier-marketplace-image-multi-sid-apps-md%2Fazuredeploy.json
[virtual-machines-azure-resource-manager-architecture-benefits-arm]:../../../azure-resource-manager/management/overview.md#the-benefits-of-using-resource-manager
[virtual-machines-manage-availability]:../../virtual-machines-windows-manage-availability.md
Bu makalede, bir SAP ASCS/SCS örneğini Kümelendirmek için bir Windows Server yük devretme kümesi ve Küme Paylaşılan diski kullanılarak Azure 'da yüksek kullanılabilirliğe sahip bir SAP sisteminin nasıl yükleneceği ve yapılandırılacağı açıklanmaktadır. [Mimari kılavuzunda açıklandığı gibi: Küme Paylaşılan diski kullanarak bir Windows Yük devretme KÜMESINDE SAP ASCS/SCS örneği kümeleme][sap-high-availability-guide-wsfc-shared-disk]küme paylaşılan *diski* için iki alternatif vardır:
- [Azure paylaşılan diskleri](../../disks-shared.md)
- Kümelenmiş paylaşılan diskin benzetimini yapan yansıtılmış depolama alanı oluşturmak için [SIOS Dataman küme sürümünü](https://us.sios.com/products/datakeeper-cluster/) kullanma
## <a name="prerequisites"></a>Önkoşullar
Yüklemeye başlamadan önce şu belgeleri gözden geçirin:
* [Mimari Kılavuzu: Küme Paylaşılan diski kullanarak bir Windows Yük devretme kümesinde SAP yoks/SCS örneği oluşturma][sap-high-availability-guide-wsfc-shared-disk]
* [SAP Ass/SCS örneği için Windows Yük devretme kümesi ve paylaşılan disk kullanarak SAP HA için Azure altyapısını hazırlama][sap-high-availability-infrastructure-wsfc-shared-disk]
Bu makaledeki DBMS kurulumunu açıklamamız, çünkü ayarlar kullandığınız DBMS sistemine bağlı olarak değişir. DBMS ile ilgili yüksek kullanılabilirliğe sahip olan sorunların, Azure için farklı DBMS satıcılarının desteklediği işlevlere değinilmesi gerektiğini varsaydık. Oracle veritabanları için SQL Server ve Oracle Data Guard için AlwaysOn veya veritabanı yansıtma örnekleri verilmiştir. DBMS için yüksek kullanılabilirlik senaryoları Bu makalede ele alınmıyor.
Farklı DBMS Hizmetleri, Azure 'daki kümelenmiş SAP Ass veya SCS yapılandırmasıyla etkileşen özel önemli noktalar yoktur.
> [!NOTE]
> SAP NetWeaver ABAP Systems, Java sistemleri ve ABAP + Java sistemlerinin yükleme yordamları neredeyse aynıdır. En önemli fark, SAP ABAP sisteminin bir ASCS örneğine sahip olması gerektiğidir. SAP Java sisteminde bir SCS örneği vardır. SAP ABAP + Java sisteminde bir ASCS örneği ve aynı Microsoft yük devretme kümesi grubunda çalışan bir SCS örneği vardır. Her SAP NetWeaver yükleme yığını için herhangi bir yükleme farkı açıkça bahsedilir. Adımların geri kalanının aynı olduğunu varsayabilirsiniz.
## <a name="install-sap-with-a-high-availability-ascsscs-instance"></a><a name="31c6bd4f-51df-4057-9fdf-3fcbc619c170"></a>Yüksek kullanılabilirliğe sahip bir ASCS/SCS örneğiyle SAP 'yi yükler
> [!IMPORTANT]
> Paylaşılan disk sunmak için SIOS kullanırsanız, sayfa dosyanızı SIOS veri kullanımı yansıtılmış birimlerine yerleştirmeyin. Sayfa dosyanızı, varsayılan olan bir Azure sanal makinesinin geçici sürücüsünde bırakabilirsiniz. Henüz orada yoksa, Windows sayfa dosyasını Azure sanal makinenizin D sürücüsüne taşıyın.
SAP 'yi yüksek kullanılabilirliğe sahip bir ASCS/SCS örneğiyle yüklemek şu görevleri içerir:
* Kümelenmiş SAP ASCS/SCS örneği için bir sanal ana bilgisayar adı oluşturun.
* İlk küme düğümüne SAP 'yi yükler.
* ASCS/SCS örneğinin SAP profilini değiştirin.
* Araştırma bağlantı noktası ekleyin.
* Windows Güvenlik Duvarı araştırma bağlantı noktasını açın.
### <a name="create-a-virtual-host-name-for-the-clustered-sap-ascsscs-instance"></a><a name="a97ad604-9094-44fe-a364-f89cb39bf097"></a>Kümelenmiş SAP Ass/SCS örneği için sanal ana bilgisayar adı oluşturma
1. Windows DNS Yöneticisi 'nde, yoks/SCS örneğinin sanal ana bilgisayar adı için bir DNS girişi oluşturun.
> [!IMPORTANT]
> ASCS/SCS örneğinin sanal ana bilgisayar adına atadığınız IP adresi, Azure Load Balancer atadığınız IP adresiyle aynı olmalıdır.
![Şekil 1: SAP ASCS/SCS kümesi sanal adı ve TCP/IP adresi için DNS girişi tanımlama][sap-ha-guide-figure-3046]
_SAP ASCS/SCS kümesi sanal adı ve TCP/IP adresi için DNS girişi tanımlayın_
2. Ayrıca kümelenmiş örnek olan yeni SAP sıraya alma çoğaltma sunucusu 2 ' yi kullanıyorsa, DNS 'de ERS2 için bir sanal ana bilgisayar adı da ayırmanız gerekir.
> [!IMPORTANT]
> ERS2 örneğinin sanal ana bilgisayar adına atadığınız IP adresi, Azure Load Balancer atadığınız ikinci IP adresi olmalıdır.
![Şekil 1A: SAP ASCS/SCS kümesi sanal adı ve TCP/IP adresi için DNS girişi tanımlama][sap-ha-guide-figure-3046-ers2]
_SAP ERS2 kümesi sanal adı ve TCP/IP adresi için DNS girişi tanımlama_
3. Sanal ana bilgisayar adına atanan IP adresini tanımlamak için **DNS Yöneticisi** > **etki alanı**' nı seçin.
![Şekil 2: SAP Ass/SCS küme yapılandırması için yeni sanal ad ve TCP/IP adresi][sap-ha-guide-figure-3047]
_SAP Ass/SCS küme yapılandırması için yeni sanal ad ve TCP/IP adresi_
### <a name="install-the-sap-first-cluster-node"></a><a name="eb5af918-b42f-4803-bb50-eff41f84b0b0"></a> SAP ilk küme düğümünü yükler
1. Küme düğümü A 'da ilk küme düğümü seçeneğini yürütün. şunu seçin:
* **ABAP sistemi**: **ascs** örnek numarası **00**
* **Java sistemi**: **SCS** örnek numarası **01**
* **ABAP + Java sistemi**: **Ass** örnek numarası **00** ve **SCS** örnek numarası **01**
> [!IMPORTANT]
> Azure iç yük dengeleyici Yük Dengeleme kurallarında (temel SKU kullanılıyorsa) yapılandırmanın ve seçili SAP örnek numaralarının eşleşmesi gerektiğini unutmayın.
2. Tanımlanan SAP yükleme yordamını izleyin. "Ilk küme düğümü" yükleme başlatma seçeneğinde, "küme paylaşılan disk" öğesini yapılandırma seçeneği olarak seçmek için emin olun.
> [!TIP]
> SAP yükleme belgeleri, ilk ASCS/SCS küme düğümünün nasıl yükleneceğini açıklar.
### <a name="modify-the-sap-profile-of-the-ascsscs-instance"></a><a name="e4caaab2-e90f-4f2c-bc84-2cd2e12a9556"></a> ASCS/SCS örneğinin SAP profilini değiştirme
Sıraya alma çoğaltma sunucusu 1 varsa, aşağıda açıklandığı gibi SAP profili parametresi ekleyin `enque/encni/set_so_keepalive` . Profil parametresi, SAP iş işlemleriyle sıraya alma sunucusu arasındaki bağlantıları çok uzun süre boşta kaldığında kapatmadan önler. SAP parametresi ERS2 için gerekli değildir.
1. ERS1 kullanılıyorsa, bu profile parametresini SAP ASCS/SCS örnek profiline ekleyin.
```
enque/encni/set_so_keepalive = true
```
Hem ERS1 hem de ERS2 için, `keepalive` işletim sistemi PARAMETRELERININ SAP note [1410736](https://launchpad.support.sap.com/#/notes/1410736)' de açıklandığı gibi ayarlandığından emin olun.
2. SAP profili parametre değişikliklerini uygulamak için SAP ASCS/SCS örneğini yeniden başlatın.
### <a name="add-a-probe-port"></a><a name="10822f4f-32e7-4871-b63a-9b86c76ce761"></a> Araştırma bağlantı noktası ekle
Tüm küme yapılandırmasının Azure Load Balancer ile çalışmasını sağlamak için iç yük dengeleyicinin araştırma işlevini kullanın. Azure iç yük dengeleyici, genellikle katılan sanal makineler arasında eşit olarak gelen iş yükünü dağıtır.
Ancak, yalnızca bir örnek etkin olduğundan, bazı küme yapılandırmalarında bu çalışmaz. Diğer örnek pasif ve iş yükünün hiçbirini kabul edemiyor. Bir araştırma işlevselliği, Azure iç yük dengeleyicinin hangi Örneğin etkin olduğunu algılayarak ve yalnızca etkin örneği hedeflemeye yardımcı olur.
> [!IMPORTANT]
> Bu örnek yapılandırmada, **Probeport** 620 **NR** olarak ayarlanır. **00** NUMARALı BIR SAP ascs örneği için 620 **00**' dır. Yapılandırmayı SAP örnek numaralarınız ve SAP SID 'niz ile eşleşecek şekilde ayarlamanız gerekecektir.
Bir araştırma bağlantı noktası eklemek için, bu PowerShell modülünü küme VM 'lerinden birinde çalıştırın:
- SAP ASC/SCS örneği söz konusu olduğunda
```powershell
Set-AzureLoadBalancerHealthCheckProbePortOnSAPClusterIPResource -SAPSID SID -ProbePort 62000
```
- ERS2 kullanıyorsanız, kümelenmiş. Kümelenmemiş olduğundan, ERS1 için araştırma bağlantı noktasını yapılandırmaya gerek yoktur.
```powershell
Set-AzureLoadBalancerHealthCheckProbePortOnSAPClusterIPResource -SAPSID SID -ProbePort 62001 -IsSAPERSClusteredInstance $True
```
İşlevin kodu `Set-AzureLoadBalancerHealthCheckProbePortOnSAPClusterIPResource` şöyle görünür:
```powershell
function Set-AzureLoadBalancerHealthCheckProbePortOnSAPClusterIPResource {
<#
.SYNOPSIS
Set-AzureLoadBalancerHealthProbePortOnSAPClusterIPResource will set a new Azure Load Balancer Health Probe Port on 'SAP $SAPSID IP' cluster resource.
.DESCRIPTION
Set-AzureLoadBalancerHealthProbePortOnSAPClusterIPResource will set a new Azure Load Balancer Health Probe Port on 'SAP $SAPSID IP' cluster resource.
It will also restart SAP Cluster group (default behavior), to activate the changes.
You need to run it on one of the SAP ASCS/SCS Windows cluster nodes.
Expectation is that SAP group is installed with official SWPM installation tool, which will set default expected naming convention for:
- SAP Cluster Group: 'SAP $SAPSID'
- SAP Cluster IP Address Resource: 'SAP $SAPSID IP'
.PARAMETER SAPSID
SAP SID - 3 characters staring with letter.
.PARAMETER ProbePort
Azure Load Balancer Health Check Probe Port.
.PARAMETER RestartSAPClusterGroup
Optional parameter. Default value is '$True', so SAP cluster group will be restarted to activate the changes.
.PARAMETER IsSAPERSClusteredInstance
Optional parameter.Default value is '$False'.
If set to $True , then handle clsutered new SAP ERS2 instance.
.EXAMPLE
# Set probe port to 62000, on SAP cluster resource 'SAP AB1 IP', and restart the SAP cluster group 'SAP AB1', to activate the changes.
Set-AzureLoadBalancerHealthCheckProbePortOnSAPClusterIPResource -SAPSID AB1 -ProbePort 62000
.EXAMPLE
# Set probe port to 62000, on SAP cluster resource 'SAP AB1 IP'. SAP cluster group 'SAP AB1' IS NOT restarted, therefore changes are NOT active.
# To activate the changes you need to manualy restart 'SAP AB1' cluster group.
Set-AzureLoadBalancerHealthCheckProbePortOnSAPClusterIPResource -SAPSID AB1 -ProbePort 62000 -RestartSAPClusterGroup $False
.EXAMPLE
# Set probe port to 62001, on SAP cluster resource 'SAP AB1 ERS IP'. SAP cluster group 'SAP AB1 ERS' IS restarted, to activate the changes.
Set-AzureLoadBalancerHealthCheckProbePortOnSAPClusterIPResource -SAPSID AB1 -ProbePort 62000 -IsSAPERSClusteredInstance $True
#>
[CmdletBinding()]
param(
[Parameter(Mandatory=$True)]
[ValidateNotNullOrEmpty()]
[ValidateLength(3,3)]
[string]$SAPSID,
[Parameter(Mandatory=$True)]
[ValidateNotNullOrEmpty()]
[int] $ProbePort,
[Parameter(Mandatory=$False)]
[bool] $RestartSAPClusterGroup = $True,
[Parameter(Mandatory=$False)]
[bool] $IsSAPERSClusteredInstance = $False
)
BEGIN{}
PROCESS{
try{
if($IsSAPERSClusteredInstance){
#Handle clustered SAP ERS Instance
$SAPClusterRoleName = "SAP $SAPSID ERS"
$SAPIPresourceName = "SAP $SAPSID ERS IP"
}else{
#Handle clustered SAP ASCS/SCS Instance
$SAPClusterRoleName = "SAP $SAPSID"
$SAPIPresourceName = "SAP $SAPSID IP"
}
$SAPIPResourceClusterParameters = Get-ClusterResource $SAPIPresourceName | Get-ClusterParameter
$IPAddress = ($SAPIPResourceClusterParameters | Where-Object {$_.Name -eq "Address" }).Value
$NetworkName = ($SAPIPResourceClusterParameters | Where-Object {$_.Name -eq "Network" }).Value
$SubnetMask = ($SAPIPResourceClusterParameters | Where-Object {$_.Name -eq "SubnetMask" }).Value
$OverrideAddressMatch = ($SAPIPResourceClusterParameters | Where-Object {$_.Name -eq "OverrideAddressMatch" }).Value
$EnableDhcp = ($SAPIPResourceClusterParameters | Where-Object {$_.Name -eq "EnableDhcp" }).Value
$OldProbePort = ($SAPIPResourceClusterParameters | Where-Object {$_.Name -eq "ProbePort" }).Value
$var = Get-ClusterResource | Where-Object { $_.name -eq $SAPIPresourceName }
Write-Output "Current configuration parameters for SAP IP cluster resource '$SAPIPresourceName' are:"
Get-ClusterResource -Name $SAPIPresourceName | Get-ClusterParameter
Write-Output " "
Write-Output "Current probe port property of the SAP cluster resource '$SAPIPresourceName' is '$OldProbePort'."
Write-Output " "
Write-Output "Setting the new probe port property of the SAP cluster resource '$SAPIPresourceName' to '$ProbePort' ..."
Write-Output " "
$var | Set-ClusterParameter -Multiple @{"Address"=$IPAddress;"ProbePort"=$ProbePort;"Subnetmask"=$SubnetMask;"Network"=$NetworkName;"OverrideAddressMatch"=$OverrideAddressMatch;"EnableDhcp"=$EnableDhcp}
Write-Output " "
if($RestartSAPClusterGroup){
Write-Output ""
Write-Output "Activating changes..."
Write-Output " "
Write-Output "Taking SAP cluster IP resource '$SAPIPresourceName' offline ..."
Stop-ClusterResource -Name $SAPIPresourceName
sleep 5
Write-Output "Starting SAP cluster role '$SAPClusterRoleName' ..."
Start-ClusterGroup -Name $SAPClusterRoleName
Write-Output "New ProbePort parameter is active."
Write-Output " "
Write-Output "New configuration parameters for SAP IP cluster resource '$SAPIPresourceName':"
Write-Output " "
Get-ClusterResource -Name $SAPIPresourceName | Get-ClusterParameter
}else
{
Write-Output "SAP cluster role '$SAPClusterRoleName' is not restarted, therefore changes are not activated."
}
}
catch{
Write-Error $_.Exception.Message
}
}
END {}
}
```
### <a name="open-the-windows-firewall-probe-port"></a><a name="4498c707-86c0-4cde-9c69-058a7ab8c3ac"></a> Windows Güvenlik Duvarı araştırma bağlantı noktasını açın
Her iki küme düğümünde bir Windows Güvenlik Duvarı araştırması bağlantı noktası açın. Windows Güvenlik Duvarı araştırması bağlantı noktasını açmak için aşağıdaki betiği kullanın. Ortamınız için PowerShell değişkenlerini güncelleştirin.
ERS2 kullanıyorsanız, ERS2 araştırma bağlantı noktası için güvenlik duvarı bağlantı noktasını da açmanız gerekir.
```powershell
$ProbePort = 62000 # ProbePort of the Azure internal load balancer
New-NetFirewallRule -Name AzureProbePort -DisplayName "Rule for Azure Probe Port" -Direction Inbound -Action Allow -Protocol TCP -LocalPort $ProbePort
```
## <a name="install-the-database-instance"></a><a name="85d78414-b21d-4097-92b6-34d8bcb724b7"></a> Veritabanı örneğini yükler
Veritabanı örneğini yüklemek için SAP yükleme belgelerinde açıklanan işlemi izleyin.
## <a name="install-the-second-cluster-node"></a><a name="8a276e16-f507-4071-b829-cdc0a4d36748"></a> İkinci küme düğümünü yükler
İkinci kümeyi yüklemek için, SAP yükleme kılavuzunda açıklanan adımları izleyin.
## <a name="install-the-sap-primary-application-server"></a><a name="2477e58f-c5a7-4a5d-9ae3-7b91022cafb5"></a> SAP birincil uygulama sunucusunu yükler
PAS 'yi barındırmak için belirlediğiniz sanal makinede birincil uygulama sunucusu (PAS) örneği \<SID\> -dı-0 ' yı yükler. Azure üzerinde hiçbir bağımlılık yoktur. SIOS kullanıyorsanız, hiçbir veri ve özel ayar yoktur.
## <a name="install-the-sap-additional-application-server"></a><a name="0ba4a6c1-cc37-4bcf-a8dc-025de4263772"></a> SAP ek uygulama sunucusunu yükler
SAP uygulama sunucusu örneğini barındırmak için belirlediğiniz tüm sanal makinelere bir SAP ek uygulama sunucusu (AAS) yükleyebilirsiniz.
## <a name="test-the-sap-ascsscs-instance-failover"></a><a name="18aa2b9d-92d2-4c0e-8ddd-5acaabda99e9"></a> SAP ASCS/SCS örneği yük devretmesini test etme
Seviyelendirilmiş yük devretme testleri için SAP Ass 'nin A düğümünde etkin olduğunu varsaytık.
1. SAP sisteminin A düğümünden A düğümüne başarılı bir şekilde yük devredebildiğini doğrulayın \<SID\> a küme düğümünden b KÜMESINE SAP kümesi grubu yük devretmesi başlatmak için şu seçeneklerden birini seçin:
- Yük Devretme Kümesi Yöneticisi
- Yük devretme kümesi PowerShell
```powershell
$SAPSID = "PR1" # SAP <SID>
$SAPClusterGroup = "SAP $SAPSID"
Move-ClusterGroup -Name $SAPClusterGroup
```
2. Windows Konuk işletim sisteminin içindeki küme düğümünü yeniden başlatın. Bu, \<SID\> A düğümünden B DÜĞÜMÜNE SAP küme grubunun otomatik yük devretmesini başlatır.
3. Azure portal küme düğümünü yeniden başlatın. Bu, \<SID\> A düğümünden B DÜĞÜMÜNE SAP küme grubunun otomatik yük devretmesini başlatır.
4. Azure PowerShell kullanarak küme düğümünü yeniden başlatın. Bu, \<SID\> A düğümünden B DÜĞÜMÜNE SAP küme grubunun otomatik yük devretmesini başlatır.
5. Doğrulama
- Yük devretmeden sonra, SAP \<SID\> küme grubunun B küme düğümünde çalıştığını doğrulayın.
![Şekil 8: Yük Devretme Kümesi Yöneticisi, SAP \< SID \> kümesi grubu B kümesi düğümünde çalışıyor][sap-ha-guide-figure-5002]
_Yük Devretme Kümesi Yöneticisi, SAP \<SID\> kümesi grubu B kümesi düğümünde çalışıyor_
- Yük devretmeden sonra paylaşılan diskin B küme düğümüne takılı olduğundan emin olun.
- Yük devretmenin ardından, SIOS kullanıyorsanız, SIOS veri tutan özelliğinin, küme düğümü B 'deki kaynak birim sürücüsünden gelen verileri, A küme düğümü üzerinde hedef birim sürücüleri olarak çoğaltmakta olduğunu doğrulayın.
![Şekil 9: SIOS Dataman yerel birimi B küme düğümünden A 'ya çoğaltır][sap-ha-guide-figure-5003]
_SIOS Dataman, yerel birimi B küme düğümünden A kümesine çoğaltır_ | 70.18847 | 501 | 0.766925 | tur_Latn | 0.909697 |
d5cd60a959abc99959b0c32cb4950f2446fcf7b6 | 919 | md | Markdown | includes/data-explorer-limits.md | fuatrihtim/azure-docs.tr-tr | 6569c5eb54bdab7488b44498dc4dad397d32f1be | [
"CC-BY-4.0",
"MIT"
] | null | null | null | includes/data-explorer-limits.md | fuatrihtim/azure-docs.tr-tr | 6569c5eb54bdab7488b44498dc4dad397d32f1be | [
"CC-BY-4.0",
"MIT"
] | null | null | null | includes/data-explorer-limits.md | fuatrihtim/azure-docs.tr-tr | 6569c5eb54bdab7488b44498dc4dad397d32f1be | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
author: ilayrn
ms.service: data-explorer
ms.topic: include
ms.date: 01/20/2020
ms.author: ilayr
ms.openlocfilehash: d9e23e74cd980ecf44cd04ad2b6f89dc6a4cf868
ms.sourcegitcommit: 867cb1b7a1f3a1f0b427282c648d411d0ca4f81f
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 03/19/2021
ms.locfileid: "76548243"
---
Aşağıdaki tabloda Azure Veri Gezgini kümelerine yönelik en fazla sınır açıklanmaktadır.
| Kaynak | Sınır |
| --- | --- |
| Abonelik başına bölge başına küme sayısı | 20 |
| Küme başına örnek | 1000 |
| Bir kümedeki veritabanlarının sayısı | 10,000 |
| Bir kümedeki ekli veritabanı yapılandırmalarının sayısı | 70 |
Aşağıdaki tabloda, Azure Veri Gezgini kümelerinde gerçekleştirilen yönetim işlemlerinin sınırları açıklanmaktadır.
| Kapsam | İşlem | Sınır |
| --- | --- | --- |
| Küme | Oku (örneğin, küme al) | 5 dakikada 500 |
| Küme | yazma (örneğin, veritabanı oluşturma) | 1000/saat |
| 30.633333 | 114 | 0.752992 | tur_Latn | 0.99831 |
d5cd949dcc1f5604426b9dc48e66ab3c82896b90 | 3,961 | md | Markdown | README.md | vanlid/guacamole-auth-hmac | 1ce6c8a09b73c4b29c19243fc36f777ac89f6a6e | [
"MIT"
] | 1 | 2021-07-05T09:43:57.000Z | 2021-07-05T09:43:57.000Z | README.md | frenkiesp/guacamole-url-auth | 9dc2e0c1401e2c6d4bfd22421492d51bb990ee5b | [
"MIT"
] | null | null | null | README.md | frenkiesp/guacamole-url-auth | 9dc2e0c1401e2c6d4bfd22421492d51bb990ee5b | [
"MIT"
] | null | null | null | # guacamole-auth-hmac [](https://travis-ci.org/grncdr/guacamole-auth-hmac)
## Description
This project is a plugin for [Guacamole](http://guac-dev.org), an HTML5 based
remote desktop solution supporting VNC/RFB, RDP, and SSH.
This plugin is an _authentication provider_ that enables stateless, on-the-fly
configuration of remote desktop connections that are authorized using a
pre-shared key. It is most appropriate for scenarios where you have an existing
user authentication & authorization mechanism.
## Building
guacamole-auth-hmac uses Maven for managing builds. After installing Maven you can build a
suitable jar for deployment with `mvn package`.
The resulting jar file will be placed in `target/guacamole-auth-hmac-<version>.jar`.
## Deployment & Configuration
**Warning** This plugin relies on API's introduced in Guacamole 0.8.3, so you must be running
at least that version before using this plugin.
Copy `guacamole-auth-hmac.jar` to the location specified by
[`lib-directory`][config-classpath] in `guacamole.properties`. Then set the
`auth-provider` property to `com.stephensugden.guacamole.net.hmac.HmacAuthenticationProvider`.
`guacamole-auth-hmac` adds two new config keys to `guacamole.properties`:
* `secret-key` - The key that will be used to verify URL signatures.
Whatever is generating the signed URLs will need to share this value.
* `timestamp-age-limit` - A numeric value (in milliseconds) that determines how long
a signed request should be valid for.
[config-classpath]: http://guac-dev.org/doc/gug/configuring-guacamole.html#idp380240
## Usage
To generate a signed URL for usage with this plugin, simply use the path to
Guacamole's built-in `/client.xhtml` as a base, and append the following query
parameters:
* `id` - A connection ID that must be unique per user session.
* `timestamp` - A unix timestamp in milliseconds. (E.G. `time() * 1000` in PHP).
This is used to prevent replay attacks.
* `signature` - The [request signature][#request-signing]
* `guac.protocol` - One of `vnc`, `rdp`, or `ssh`.
* `guac.hostname` - The hostname of the remote desktop server to connect to.
* `guac.port` - The port number to connect to.
* `guac.username` - (_optional_)
* `guac.password` - (_optional_)
* `guac.*` - (_optional_) Any other configuration parameters recognized by
Guacamole can be by prefixing them with `guac.`.
## Request Signing
Requests must be signed with an HMAC, where the message content is generated
from the request parameters as follows:
1. The parameters `timestamp`, and `guac.protocol` are concatenated.
2. For each of `guac.username`, `guac.password`, `guac.hostname`, and `guac.port`;
if the parameter was included in the request, append it's unprefixed name
(e.g. - `guac.username` becomes `username`) followed by it's value.
### Request Signing - Example
Given a request for the following URL:
`client.xhtml?id=example&guac.protocol=rdp&guac.hostname=myserver.internal&guac.port=3389×tamp=1377143741000`
The message to be signed will be the concatenation of the following strings:
- `"1377143741000"`
- `"rdp"`
- `"hostname"`
- `"myserver.internal"`
- `"port"`
- `"3389"`
Assuming a secret key of `"secret"`, a `signature` parameter should be appended
with a value that is the base-64 encoded value of the hash produced by signing
the message `"1377143741000rdphostnamemyserver.internalport3389"` with the key
`"secret"`, or `"Iost5ouayLzpKLgx607kY1QUVwY="`. How
this signature is produced is dependent on your programming language/platform,
but with recent versions of PHP it looks like this:
base64_encode(hash_hmac('sha1', $message, $secret));
An [example PHP implementation][example-php] is included in `src/example/php`.
[example-php]: https://github.com/grncdr/guacamole-auth-hmac/blob/master/src/example/php
## License
MIT License
| 40.418367 | 157 | 0.75183 | eng_Latn | 0.989691 |
d5cddffbf847f87eaf59cd87d4b5cb7f5cc23fcf | 1,366 | md | Markdown | vault/lexicon/G41040.md | mandolyte/uw-obsidian | 39e987c4cdc49d2a68e3af6b4e3fc84d1cda916d | [
"MIT"
] | null | null | null | vault/lexicon/G41040.md | mandolyte/uw-obsidian | 39e987c4cdc49d2a68e3af6b4e3fc84d1cda916d | [
"MIT"
] | null | null | null | vault/lexicon/G41040.md | mandolyte/uw-obsidian | 39e987c4cdc49d2a68e3af6b4e3fc84d1cda916d | [
"MIT"
] | null | null | null | # πιστόω, ῶ.
<!-- Status: S2=NeedsReview -->
<!-- Lexica used for edits: BDAG, FFM, LN, A-S -->
## Word data
* Strongs: G41040.
* Alternate spellings:
* Principle Parts:
* Part of speech:
[Verb](http://ugg.readthedocs.io/en/latest/verb.html).
* Instances in the New Testament: 1.
* All Scriptures cited: Yes
## Etymology:
[πιστός]()),
* LXX/Hebrew glosses:
* Time Period/Ancient Authors:
* Related words:
* Antonyms for all senses
* Synonyms for all senses:
## Senses:
### Sense 1.0:
#### Definition:
to believe, be assured of, be persuaded or confident (in the New Testament, used in the passive voice, when the action is happening to the subject of the sentence. In the active voice, when the subject is doing the action of the sentence, meaning "to make trustworthy")
#### Glosses:
to believe, be assured of, be persuaded or confident
#### Explanation:
#### Citations:
to make trustworthy (Thuc., [III Ki 1:36](1Ki 1:36)), hence, to establish ([I Ch 17:14](1Ch 17:14)). Pass. and mid., to be assured of: c. acc. rei,
; [σὺ](../G47710/01.md) [δὲ](../G11610/01.md) [μένε](../G33060/01.md) [ἐν](../G17220/01.md) [οἷς](../G37390/01.md) [ἔμαθες](../G31290/01.md) [καὶ](../G25320/01.md) ἐπιστώθης,
; "You, however, continue in the things that you have learned and have firmly believed," (ULT):
[II Ti 3:14](2Ti 3:14).† | 21.68254 | 270 | 0.658126 | eng_Latn | 0.900229 |
d5ce90400a595e50a577936976a3be04ea6ac84f | 17,544 | md | Markdown | security-updates/SecurityBulletins/2015/ms15-057.md | MicrosoftDocs/security-updates.de-de | 38a2d4f22cfaacc722fb19ea2e9485d86d538c8f | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-05-19T20:15:48.000Z | 2020-05-19T20:15:48.000Z | security-updates/SecurityBulletins/2015/ms15-057.md | MicrosoftDocs/security-updates.de-de | 38a2d4f22cfaacc722fb19ea2e9485d86d538c8f | [
"CC-BY-4.0",
"MIT"
] | 518 | 2017-10-12T11:56:08.000Z | 2019-12-06T22:49:34.000Z | security-updates/SecurityBulletins/2015/ms15-057.md | MicrosoftDocs/security-updates.de-de | 38a2d4f22cfaacc722fb19ea2e9485d86d538c8f | [
"CC-BY-4.0",
"MIT"
] | 4 | 2018-05-10T19:44:54.000Z | 2021-11-15T11:25:49.000Z | ---
TOCTitle: 'MS15-057'
Title: 'Microsoft Security Bulletin MS15-057 – Kritisch'
ms:assetid: 'ms15-057'
ms:contentKeyID: 65883200
ms:mtpsurl: 'https://technet.microsoft.com/de-DE/library/ms15-057(v=Security.10)'
---
Microsoft Security Bulletin MS15-057 – Kritisch
===============================================
Sicherheitsanfälligkeit in Windows Media Player kann Remotecodeausführung ermöglichen (3033890)
-----------------------------------------------------------------------------------------------
Veröffentlicht: 9. Juni 2015
**Version:** 1.0
Kurzzusammenfassung
-------------------
Dieses Sicherheitsupdate behebt eine Sicherheitsanfälligkeit in Microsoft Windows. Die Sicherheitsanfälligkeit kann Remotecodeausführung ermöglichen, wenn in Windows Media Player Medieninhalte geöffnet werden, die auf einer in böswilliger Absicht erstellten Webseite gehostet werden. Nutzt ein Angreifer diese Sicherheitsanfälligkeit erfolgreich aus, kann er die vollständige Kontrolle über das betroffene System erlangen. Benutzer mit Konten, die über weniger Systemrechte verfügen, sind davon möglicherweise weniger betroffen als Benutzer mit Administratorrechten.
Dieses Sicherheitsupdate wird für Windows Media Player 10 unter Windows Server 2003, für Windows Media Player 11 unter Windows Vista oder Windows Server 2008 und für Windows Media Player 12 unter Windows 7 oder Windows Server 2008 R2 als Kritisch eingestuft. Weitere Informationen finden Sie im Abschnitt **Betroffene Software**.
Das Update behebt die Sicherheitsanfälligkeit, indem korrigiert wird, wie Windows Media Player DataObject-Objekte verarbeitet. Weitere Informationen zu dieser Sicherheitsanfälligkeit finden Sie im Abschnitt **Informationen zu Sicherheitsanfälligkeiten**.
Weitere Informationen zu diesem Update finden Sie im [Microsoft Knowledge Base-Artikel 3033890](https://support.microsoft.com/de-de/kb/3033890).
Betroffene Software
-------------------
Die folgenden Softwareversionen oder -Editionen sind betroffen. Versionen oder Editionen, die nicht aufgeführt sind, haben entweder das Ende ihres Supportlebenszyklus überschritten oder sind nicht betroffen. Besuchen Sie die Website [Microsoft Support Lifecycle](https://support.microsoft.com/lifecycle), um den Supportlebenszyklus für Ihre Softwareversion oder Edition zu ermitteln.
<p> </p>
<table style="border:1px solid black;">
<tr>
<td style="border:1px solid black;">
**Betriebssystem**
</td>
<td style="border:1px solid black;">
**Komponente**
</td>
<td style="border:1px solid black;">
**Maximale Sicherheitsauswirkung**
</td>
<td style="border:1px solid black;">
**Bewertung des Gesamtschweregrads**
</td>
<td style="border:1px solid black;">
**Ersetzte Updates**\*
</td>
</tr>
<tr>
<td style="border:1px solid black;" colspan="5">
**Windows Server 2003**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2003 Service Pack 2
</td>
<td style="border:1px solid black;">
[Windows Media Player 10](https://www.microsoft.com/de-de/download/details.aspx?id=47415)
(3033890)
</td>
<td style="border:1px solid black;">
Remotecodeausführung
</td>
<td style="border:1px solid black;">
Kritisch
</td>
<td style="border:1px solid black;">
2378111 in [MS10-082](https://technet.microsoft.com/de-de/security/bulletin/ms10-082)
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2003 x64 Edition Service Pack 2
</td>
<td style="border:1px solid black;">
[Windows Media Player 10](https://www.microsoft.com/de-de/download/details.aspx?id=47370)
(3033890)
</td>
<td style="border:1px solid black;">
Remotecodeausführung
</td>
<td style="border:1px solid black;">
Kritisch
</td>
<td style="border:1px solid black;">
2378111 in [MS10-082](https://technet.microsoft.com/de-de/security/bulletin/ms10-082)
</td>
</tr>
<tr>
<td style="border:1px solid black;" colspan="5">
**Windows Vista**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Vista Service Pack 2
</td>
<td style="border:1px solid black;">
[Windows Media Player 11](https://www.microsoft.com/de-de/download/details.aspx?id=47394)
(3033890)
</td>
<td style="border:1px solid black;">
Remotecodeausführung
</td>
<td style="border:1px solid black;">
Kritisch
</td>
<td style="border:1px solid black;">
2378111 in [MS10-082](https://technet.microsoft.com/de-de/security/bulletin/ms10-082)
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Vista x64 Edition Service Pack 2
</td>
<td style="border:1px solid black;">
[Windows Media Player 11](https://www.microsoft.com/de-de/download/details.aspx?id=47386)
(3033890)
</td>
<td style="border:1px solid black;">
Remotecodeausführung
</td>
<td style="border:1px solid black;">
Kritisch
</td>
<td style="border:1px solid black;">
2378111 in [MS10-082](https://technet.microsoft.com/de-de/security/bulletin/ms10-082)
</td>
</tr>
<tr>
<td style="border:1px solid black;" colspan="5">
**Windows Server 2008**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2008 für 32-Bit-Systeme Service Pack 2
</td>
<td style="border:1px solid black;">
[Windows Media Player 11](https://www.microsoft.com/de-de/download/details.aspx?id=47425)
(3033890)
</td>
<td style="border:1px solid black;">
Remotecodeausführung
</td>
<td style="border:1px solid black;">
Kritisch
</td>
<td style="border:1px solid black;">
2378111 in [MS10-082](https://technet.microsoft.com/de-de/security/bulletin/ms10-082)
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2008 für x64-basierte Systeme Service Pack 2
</td>
<td style="border:1px solid black;">
[Windows Media Player 11](https://www.microsoft.com/de-de/download/details.aspx?id=47392)
(3033890)
</td>
<td style="border:1px solid black;">
Remotecodeausführung
</td>
<td style="border:1px solid black;">
Kritisch
</td>
<td style="border:1px solid black;">
2378111 in [MS10-082](https://technet.microsoft.com/de-de/security/bulletin/ms10-082)
</td>
</tr>
<tr>
<td style="border:1px solid black;" colspan="5">
**Windows 7**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows 7 für 32-Bit-Systeme Service Pack 1
</td>
<td style="border:1px solid black;">
[Windows Media Player 12](https://www.microsoft.com/de-de/download/details.aspx?id=47385)
(3033890)
</td>
<td style="border:1px solid black;">
Remotecodeausführung
</td>
<td style="border:1px solid black;">
Kritisch
</td>
<td style="border:1px solid black;">
Keine
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows 7 für x64-basierte Systeme Service Pack 1
</td>
<td style="border:1px solid black;">
[Windows Media Player 12](https://www.microsoft.com/de-de/download/details.aspx?id=47401)
(3033890)
</td>
<td style="border:1px solid black;">
Remotecodeausführung
</td>
<td style="border:1px solid black;">
Kritisch
</td>
<td style="border:1px solid black;">
Keine
</td>
</tr>
<tr>
<td style="border:1px solid black;" colspan="5">
**Windows Server 2008 R2**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2008 R2 für x64-basierte Systeme Service Pack 1
</td>
<td style="border:1px solid black;">
[Windows Media Player 12](https://www.microsoft.com/de-de/download/details.aspx?id=47428)
(3033890)
</td>
<td style="border:1px solid black;">
Remotecodeausführung
</td>
<td style="border:1px solid black;">
Kritisch
</td>
<td style="border:1px solid black;">
Keine
</td>
</tr>
</table>
\*Die Spalte „Ersetzte Updates‟ enthält nur das letzte Update einer Reihe ersetzter Updates. Eine umfassende Liste der ersetzten Updates finden Sie, wenn Sie zum [Microsoft Update-Katalog](https://catalog.update.microsoft.com/v7/site/home.aspx) wechseln, nach der Update-KB-Nummer suchen und dann die Updatedetails betrachten (die Informationen zu ersetzten Updates befinden sich auf der Registerkarte „Paketdetails‟).
Bewertungen des Schweregrads und Kennungen der Sicherheitsanfälligkeiten
------------------------------------------------------------------------
Bei der folgenden Bewertung des Schweregrads wird die potenzielle maximale Auswirkung der Sicherheitsanfälligkeit angenommen. Informationen zur Wahrscheinlichkeit der Ausnutzung der Sicherheitsanfälligkeit in Bezug auf die Bewertung des Schweregrads und die Sicherheitsauswirkung innerhalb von 30 Tagen nach Veröffentlichung dieses Security Bulletins finden Sie im Ausnutzbarkeitsindex im [Bulletin Summary für Juni](https://technet.microsoft.com/de-de/library/security/ms15-jun).
<p> </p>
<table style="border:1px solid black;">
<tr>
<td style="border:1px solid black;" colspan="3">
**Bewertung des Schweregrads und maximale Sicherheitsauswirkung nach betroffener Software**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
**Betroffene Software**
</td>
<td style="border:1px solid black;">
[**Sicherheitsanfälligkeit in Windows Media Player bezüglich Remotecodeausführung über DataObject – CVE-2015-1728**](https://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2015-1728)
</td>
<td style="border:1px solid black;">
**Bewertung des Gesamtschweregrads**
</td>
</tr>
<tr>
<td style="border:1px solid black;" colspan="3">
**Windows Server 2003**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2003 Service Pack 2
(3033890)
</td>
<td style="border:1px solid black;">
**Kritisch**
Remotecodeausführung
</td>
<td style="border:1px solid black;">
Kritisch
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2003 x64 Edition Service Pack 2
(3033890)
</td>
<td style="border:1px solid black;">
**Kritisch**
Remotecodeausführung
</td>
<td style="border:1px solid black;">
Kritisch
</td>
</tr>
<tr>
<td style="border:1px solid black;" colspan="3">
**Windows Vista**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Vista Service Pack 2
(3033890)
</td>
<td style="border:1px solid black;">
**Kritisch**
Remotecodeausführung
</td>
<td style="border:1px solid black;">
Kritisch
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Vista x64 Edition Service Pack 2
(3033890)
</td>
<td style="border:1px solid black;">
**Kritisch**
Remotecodeausführung
</td>
<td style="border:1px solid black;">
Kritisch
</td>
</tr>
<tr>
<td style="border:1px solid black;" colspan="3">
**Windows Server 2008**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2008 für 32-Bit-Systeme Service Pack 2
(3033890)
</td>
<td style="border:1px solid black;">
**Kritisch**
Remotecodeausführung
</td>
<td style="border:1px solid black;">
Kritisch
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2008 für x64-basierte Systeme Service Pack 2
(3033890)
</td>
<td style="border:1px solid black;">
**Kritisch**
Remotecodeausführung
</td>
<td style="border:1px solid black;">
Kritisch
</td>
</tr>
<tr>
<td style="border:1px solid black;" colspan="3">
**Windows 7**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows 7 für 32-Bit-Systeme Service Pack 1
(3033890)
</td>
<td style="border:1px solid black;">
**Kritisch**
Remotecodeausführung
</td>
<td style="border:1px solid black;">
Kritisch
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows 7 für x64-basierte Systeme Service Pack 1
(3033890)
</td>
<td style="border:1px solid black;">
**Kritisch**
Remotecodeausführung
</td>
<td style="border:1px solid black;">
Kritisch
</td>
</tr>
<tr>
<td style="border:1px solid black;" colspan="3">
**Windows Server 2008 R2**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2008 R2 für x64-basierte Systeme Service Pack 1
(3033890)
</td>
<td style="border:1px solid black;">
**Kritisch**
Remotecodeausführung
</td>
<td style="border:1px solid black;">
Kritisch
</td>
</tr>
</table>
Informationen zu Sicherheitsanfälligkeiten
------------------------------------------
Sicherheitsanfälligkeit in Windows Media Player bezüglich Remotecodeausführung über DataObject – CVE-2015-1728
--------------------------------------------------------------------------------------------------------------
In Windows Media Player liegt eine Sicherheitsanfälligkeit in der Verarbeitung speziell gestalteter DataObject-Objekte vor, die Remotecodeausführung ermöglichen kann. Nutzt ein Angreifer diese Sicherheitsanfälligkeit erfolgreich aus, kann er die vollständige Kontrolle über das betroffene System erlangen. Ein Angreifer kann dann Programme installieren, Daten anzeigen, ändern oder löschen oder neue Konten mit sämtlichen Benutzerrechten erstellen. Benutzer mit Konten, die über weniger Systemrechte verfügen, sind davon möglicherweise weniger betroffen als Benutzer mit Administratorrechten.
Um diese Sicherheitsanfälligkeit auszunutzen, muss ein Benutzer ein speziell gestaltetes DataObject-Objekt in Windows Media Player öffnen. Das Update behebt die Sicherheitsanfälligkeit, indem korrigiert wird, wie Windows Media Player DataObject-Objekte verarbeitet.
Microsoft hat durch eine koordinierte Offenlegung der Sicherheitsanfälligkeit Informationen zu dieser Sicherheitsanfälligkeit erhalten. Zum Zeitpunkt der Erstveröffentlichung dieses Security Bulletins lagen Microsoft keine Informationen vor, dass diese Sicherheitsanfälligkeit öffentlich für Angriffe auf Benutzer ausgenutzt wurde.
### Schadensbegrenzende Faktoren
Für diese Sicherheitsanfälligkeit gibt es noch keine [schadensbegrenzenden Faktoren](https://technet.microsoft.com/de-de/library/security/dn848375.aspx).
### Problemumgehungen
Die folgenden [Problemumgehungen](https://technet.microsoft.com/de-de/library/security/dn848375.aspx) könnten hilfreich für Sie sein:
- **Entfernen Sie „wmplayer.exe‟ aus Internet Explorer-ElevationPolicy**
**Achtung:** Die unkorrekte Verwendung des Registrierungs-Editors kann schwerwiegende Probleme verursachen, die das gesamte System betreffen und eine Neuinstallation des Betriebssystems erforderlich machen. Microsoft kann nicht garantieren, dass Probleme, die von einer falschen Verwendung des Registrierungs-Editors herrühren, behoben werden können. Sie verwenden den Registrierungs-Editor auf eigene Gefahr.
Gehen Sie wie folgt vor, um Windows Media Player aus dem Registrierungseintrag ElevationPolicy für Internet Explorer zu entfernen:
1. Führen Sie „regedit.exe‟ aus, und erweitern Sie den folgenden Registrierungsunterschlüssel:
```
HKEY_LOCAL_MACHINE\Software\Microsoft\Internet Explorer\Low Rights\ElevationPolicy
```
2. Wählen Sie **{6bf52a52-394a-11d3-b153-00c04f79faa6}** aus.
3. Klicken Sie auf das Menü **Datei** und dann auf **Exportieren**.
4. Geben Sie im Dialogfeld **Registrierungsdatei exportieren** die Zeichenfolge **wmplayer.exe\_backup.reg** ein, und klicken Sie dann auf **Speichern**.
5. Klicken Sie auf das Menü **Datei**, wählen Sie **Löschen**, und klicken Sie dann auf **Ja**.
6. Melden Sie sich ab und erneut an, oder starten Sie den Computer neu.
**So machen Sie die Problemumgehung rückgängig**
1. Führen Sie „regedit.exe‟ aus.
2. Klicken Sie auf das Menü **Datei** und dann auf **Importieren**.
3. Wählen Sie im Dialogfeld **Registrierungsdatei importieren** die Datei **wmplayer.exe\_backup.reg** aus, und klicken Sie dann auf **Öffnen**.
### Häufig gestellte Fragen (FAQ)
**Auf welche Weise können Angreifer die Sicherheitsanfälligkeit ausnutzen?**
Diese Sicherheitsanfälligkeit erfordert, dass ein Benutzer ein speziell gestaltetes DataObject-Objekt in Windows Media Player öffnet.
In einem webbasierten Angriffsszenario muss ein Angreifer eine Website mit einem speziell gestalteten DataObject-Objekt einrichten, durch das diese Sicherheitsanfälligkeit ausgenutzt wird. Ein Angreifer kann Benutzer nicht zum Besuch einer speziell gestalteten Website zwingen. Der Angreifer muss stattdessen die Benutzer zum Besuch dieser Website verleiten, z. B. indem er sie dazu auffordert, in einer E-Mail oder einer Instant Messenger-Nachricht auf einen Link zur Website des Angreifers zu klicken.
**Für welche Systeme stellt diese Sicherheitsanfälligkeit hauptsächlich ein Risiko dar?**
Jedes System, auf dem eine betroffene Version von Windows Media Player verwendet wird, ist durch diese Sicherheitsanfälligkeit gefährdet.
Danksagung
----------
Microsoft würdigt die Bemühungen derjenigen Benutzer der Sicherheitscommunity, die uns dabei helfen, Kunden durch eine koordinierte Offenlegung von Sicherheitsanfälligkeiten zu schützen. Weitere Informationen finden Sie unter [Danksagung](https://technet.microsoft.com/de-de/library/security/dn903755.aspx).
Haftungsausschluss
------------------
Die Informationen in der Microsoft Knowledge Base werden wie besehen und ohne jede Gewährleistung bereitgestellt. Microsoft schließt alle anderen Garantien, gleich ob ausdrücklich oder konkludent, einschließlich der Garantien der Handelsüblichkeit oder Eignung für einen bestimmten Zweck aus. In keinem Fall kann Microsoft Corporation und/oder deren jeweilige Lieferanten haftbar gemacht werden für Schäden irgendeiner Art, einschließlich direkter, indirekter, zufällig entstandener Schäden, Folgeschäden, Folgen entgangenen Gewinns oder spezieller Schäden, selbst dann nicht, wenn Microsoft Corporation und/oder deren jeweilige Lieferanten auf die mögliche Entstehung dieser Schäden hingewiesen wurde. Weil in einigen Staaten/Rechtsordnungen der Ausschluss oder die Beschränkung einer Haftung für zufällig entstandene Schäden oder Folgeschäden nicht gestattet ist, gilt die obige Einschränkung eventuell nicht für Sie.
Revisionen
----------
- V1.0 (9. Juni 2015): Bulletin veröffentlicht.
*Seite generiert am 04.06.2015 um 9:11Z-07:00.*
| 35.95082 | 919 | 0.744243 | deu_Latn | 0.884156 |
d5cebb0c4dc2ece1a3cf6c873a115df2e2f0c977 | 1,839 | md | Markdown | README.md | alemagio/vue-clickout-handler | 284983f0af3d048b50a9965398fd1abbe42405d0 | [
"MIT"
] | 2 | 2020-09-10T10:34:08.000Z | 2020-09-10T15:58:32.000Z | README.md | alemagio/vue-clickout-handler | 284983f0af3d048b50a9965398fd1abbe42405d0 | [
"MIT"
] | 1 | 2021-06-03T09:03:20.000Z | 2021-06-03T09:03:20.000Z | README.md | alemagio/vue-clickout-handler | 284983f0af3d048b50a9965398fd1abbe42405d0 | [
"MIT"
] | 1 | 2021-06-03T08:49:58.000Z | 2021-06-03T08:49:58.000Z | ## Description
This is a simple directive to react when a click happens outside of a certain element.
## Installation
```
npm install vue-clickout-handler --save
```
```
yarn add vue-clickout-handler
```
## Basic Usage
```js
// main.js
import { VueClickOut } from 'vue-clickout-handler';
Vue.directive('click-out', VueClickOut)
```
You can pass just a callback and it will be used as handler
```vue
<template>
<div v-click-out="onClickOut">
...
</div>
</template>
<script>
export default {
methods: {
onClickOut () {
// do something
}
}
}
</script>
```
Or you can pass an object to include more options:
```vue
<template>
<div id="my-div">
</div>
<div v-click-out="{ handler: onClickOut, excluded: ['#my-div'], disabled: disabled}">
...
</div>
</template>
<script>
export default {
data () {
return {
disabled: false
}
},
methods: {
onClickOut () {
// do something
}
}
}
</script>
```
## Options
<table class="options">
<thead>
<tr>
<th>Option</th>
<th>Type</th>
<th>Required</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>handler</td>
<td>Function</td>
<td>true</td>
<td>The function invoked on click-outside event.</td>
</tr>
<tr>
<td>excluded</td>
<td>Array</td>
<td>false</td>
<td>A list of excluded elements, the handler will not be executed if any of these elements are clicked.</td>
</tr>
<tr>
<td>disabled</td>
<td>boolean</td>
<td>false</td>
<td>If true the handler will never be executed.</td>
</tr>
</tbody>
</table>
| 17.682692 | 120 | 0.520935 | eng_Latn | 0.812534 |
d5ceea7f52febdf857d0f0e33e489cad85e835ed | 537 | md | Markdown | Profile/README.md | nikitawootten-nist/ATICC | bc5606b0ef56e78a3be8e3dc55bb60e7ab2b066d | [
"Unlicense"
] | null | null | null | Profile/README.md | nikitawootten-nist/ATICC | bc5606b0ef56e78a3be8e3dc55bb60e7ab2b066d | [
"Unlicense"
] | null | null | null | Profile/README.md | nikitawootten-nist/ATICC | bc5606b0ef56e78a3be8e3dc55bb60e7ab2b066d | [
"Unlicense"
] | null | null | null | # Example InSpec Profile
This example shows the implementation of an InSpec profile.
Controls Architecture:
- 3 Controls for each section of the TIC 3.0 Network PEP Requirements:
1. Tests on the Good Guy Client (ggc)
2. Tests on the Bad Guy Client (bgc)
3. Tests on the SDP Controller (sdp)
4. *Tests on the SDP Gateway (gw)
- TIC Sections:
1. Access Control (ac)
2. IP Deny-listing (ip)
3. Host Containment (hc)
4. Network Segmentations (ns)
5. Micro Segmentation (ms)
6. ** AC/IA Controls **
| 28.263158 | 70 | 0.679702 | eng_Latn | 0.780289 |
d5cf08f72a905d2c3046b9d064d2265f05678dc2 | 18,740 | md | Markdown | TEDx/Titles_starting_P_to_Z/Race_Space_and_Time_in_the_Making_of_Urban_America_Paul_Lawrie_TEDxUniversityofWinnipeg.md | gt-big-data/TEDVis | 328a4c62e3a05c943b2a303817601aebf198c1aa | [
"MIT"
] | 91 | 2018-01-24T12:54:48.000Z | 2022-03-07T21:03:43.000Z | cleaned_tedx_data/Titles_starting_P_to_Z/Race_Space_and_Time_in_the_Making_of_Urban_America_Paul_Lawrie_TEDxUniversityofWinnipeg.md | nadaataiyab/TED-Talks-Nutrition-NLP | 4d7e8c2155e12cb34ab8da993dee0700a6775ff9 | [
"MIT"
] | null | null | null | cleaned_tedx_data/Titles_starting_P_to_Z/Race_Space_and_Time_in_the_Making_of_Urban_America_Paul_Lawrie_TEDxUniversityofWinnipeg.md | nadaataiyab/TED-Talks-Nutrition-NLP | 4d7e8c2155e12cb34ab8da993dee0700a6775ff9 | [
"MIT"
] | 18 | 2018-01-24T13:18:51.000Z | 2022-01-09T01:06:02.000Z |
today the world is urban we live in a
decidedly urban world for the first time
in human history more people live in
cities than do not much of this process
has been taking place in the Western
world for a little bit over a century
and a half but now the main point of
urban growth in the world is taking
place in the global south particularly
in China portions of China India
Southeast Asia and also Africa as well
this shift to the urban has
fundamentally changed the ways in which
we live it's changed the ways in which
we work in which we play in which we
love it's even changed our mental and
physical makeups it's also fundamentally
I would argue informed the way in which
we understand space and place I want to
just take a minute to unpack those terms
what do we mean by what we're talking
about space and place one of the most
influential thinkers on how we think
about race and space I should say space
and place is John Locke the English
philosopher now you know cue rolling of
eyes I know people didn't show up on a
Friday night to hear me talk at length
about it long dead English philosopher
but I think it's important because Locke
really illuminates some interesting
things about space and place for Locke
he argues that space pre-exists our
knowledge of it he believed that space
was only visible and only comprehensible
by the position of points objects and
bodies within it so the point at which
two or more of these bodies or objects
are at rest is what Locke calls place
space and place then are dependent on
each other but Locke takes it even
further he says that if you understand
race as related to place if it's
something that you can measure if you
can plot if it becomes as we see here a
location it can also be commodified or
monetized so for Locke place is a site
of property and at the turn of the 20th
century the rise of the modern city
through issues of place space and
property into sharp relief questions
over who can access these space the
right to acquire property where to live
where to work how you move through
cities and as we all know throughout
much of Western history the rights to
the rights to place have largely been
the purview of those peoples deemed
white the challenges of these new urban
realities were also especially important
or especially difficult for people's who
only a few generations prior had been
property themselves that being
african-americans so how were they to
negotiate these new and unfamiliar
spaces ultimately issues of urban space
place and race were not simply questions
of where but also of when urbanization
didn't just change the way people
thought about space and place it changed
the ways that people thought about time
and since the rise of the modern city
it's been the pace of life the flow the
rhythm of the modern city that struck
people the most now the old world was a
known world
it was governed by the rhythms and
seasons of the land by planting by
harvest by dawn dusk even by the tides
it's a known world it's where one's
ancestors are buried and there was a
deep connection between notions of space
and place and most people whether you
came from the American South or whether
you came from the shadows of Eastern
Europe were born lived and died within
about the same 10-mile radius yet all
this change with a mass migration to
cities it unmoored people from the
rhythms of the natural world how they
understood time as being something
instinctive through things such as time
standardization through electrification
that turned night in today and rapid
industrialization all conspired to
dramatically alter everyday temporal
realities so just as space came to be
quantified so too did time with
ever-increasing precision in the city
time truly became money and the modern
urban environment as we see here was
awash in these symbols of time whether
they be public clocks whether it be the
punch clock of factories or the whistles
signaling the beginning and end of work
and modernity also in many ways which
can be defined by speed by pace also had
really profound physiological reasons of
physiological impacts I should say I
just want to read you a brief quote from
a jazz historian Joel Dennis Dean who
recounts how after spending his
undergrad
years in Buffalo New York he's from New
York City to begin with he returns to
New York one spring day only to find
himself knocked off his feet by the
Russian crowds so after retiring to a
coffee shop to collect himself he
realized that he simply was not in gear
as he described it so we resolved to
kick himself into a higher gear in order
to get himself home and make his way
through the city and this is really an
example of how space and particularly
pace of the urban environment can be
embodied can be something physiological
in how people adapt this notion of the
pace of life as the flow or movement of
experience that people undergo in the
urban environment when we talk of the
New York minute that's a measure or
perception of pace
New York's diamond ISM flows from the
rapid flow of human capital and
financial capital if you stand in the
middle of Times Square for 48 hours you
can feel this pace right in your bones
and all those cities may vary in their
real and imagined rhythms the
hyperkinetic character of a New York
City of Chicago or the shall we say
somewhat less Placid pace of a place
such as Winnipeg or Buffalo New York
most cities do seem to conform to a
general temple rhythm of the five-day
workweek and 9:00 to 5:00 daily grind
which informs activity in certain areas
of the city at the end of the workday
most of these places empty out as
hundreds of thousands of people make
their way back to the surrounding
suburbs in American cities and I would
argue in some Canadian cities this is
only interrupted by a weekend pilgrimage
back to the city core in order to take
advantage of cultural events or sporting
events but it's in these spaces between
it's in these spaces and times between
that we find the poor the homeless the
indigent disabled disproportionately
peoples of color people who are largely
disconnected from the schedules of the
larger labor market disproportionately
dependent on social services with
erratic hours and often inaccessible
locations for people of limited means
all of which gives these areas a
decidedly different pace a different
rhythm populated by a decidedly
different set of people's so what does
it mean when we speak of
urban spaces as dead or dynamic is it
the volume of people is it the
particular type of people is a specific
time and how can the living inhabit an
area which is said to be dead to better
understand these context I would argue
that we need to see cities as
collections not just of spaces but as
collections of time as a landscape of
shifting temporal geographies and
there's some really interesting work
being done on this notion of how could
we perhaps overlay a temporal map of the
rhythms of cities over a physical map
and you'll see here an attempt to do so
by University by researchers I should
say at the federal university in Rio de
Janeiro who have done some amazing work
in mapping these urban temporal
geographies in this case they're
focusing on what they say are the
spatial and temporal conditions of
formation of social networks namely on
encounters as they call it as a key
social event they have really
interesting ways in which they're trying
to chart that through social classes and
through various other social markers so
if time is relative then different
peoples must experience time differently
and in urban America the fault line of
difference is race now there was a time
when this issue could be seen as black
and white urban inner city being seen as
a synonym in many ways for blackness but
since the dawn of the millennium we've
seen a real shift in this Elizabeth knee
born who is a fellow at the Brookings
Institute I'll just read you a couple of
quick quick statistics as she looked at
numbers from 2010 to 2014 in the
American Community Survey and found that
39 percent of African Americans live in
the suburbs 36 percent live in cities 15
percent live in small metropolitan areas
and 10 percent live in rural communities
just over 7 percent of all African
Americans nationwide now live in
traditional ghettos much too I'm sure
would be the amazement of the current
occupant of the White House who
continually describes the inner cities
as sites of carnage exclusively occupied
by African Americans and people of color
so when speaking of inner city residents
the dominant characteristic is often
poverty rather than strictly just race
or at least more a broadly based
understanding of color so what then are
the temporal geographies of the average
inner city resident I want to just look
at three main elements of this beginning
with housing as I'm sure many of you
know for the first part of the post-war
era housing projects were the dominant
form of housing available to inner city
residents that consisted is one
consisted of one or more concentrated
blocks of low-rise or high-rise
apartment buildings they were intended
to provide housing to low-income
residents at below market rates and they
were operated by the US Department of
Housing and Urban Development or HUD
more than 1.2 million households
currently live in public housing of some
kind most of these houses most of this
form of housing public housing are the
projects as they were called were built
under the architectural notion of
defensible space defensible spaces
encourages us two of the key elements of
this were to encourage a sense of
territoriality to provide residents with
a sense of ownership and to provide
clear sight lines for optimal visual
surveillance needed to enforce vagrancy
and curfew bylaws these spatial and
temporal imperatives were built into the
very bricks and mortar with the various
forms of sight lines the way angles were
utilized the kinds of materials that
were used when you pair these with the
various curfew and vagrancy statutes it
created a unique form of spatial and
temporal surveillance and discipline
ostensibly of course this was designed
to provide residents from safety from
perceived external threats but it ended
up creating an internal sense of
discipline and surveillance for the
residents for many residents of the
project's their time and space was very
clearly not their own what happens then
when people's move out make their way
out of the projects down into the
streets into the city streets they often
found themselves facing a similar form
of ten
Perle and spatial discipline with
joblessness rates in high-poverty urban
areas nearly three times the national
average and limited substandard
educational opportunities and the jobs
that were available to people being of
unskilled low wage but temporary jobs in
the retail and service sector thousands
of young men made their way into the
streets to make a living
often involved in street level drug
economies I don't say alternate I don't
say alternative or underground because
in many of these communities the drug
trade is the economy and this is a drug
trade predicated on the violent
acquisition of territory or corners or
turf which were then monetized through
the sale of drugs these same corners
were spaces subject to constant
surveillance and discipline not only
from rival gangs but from law
enforcement as well who often use
long-neglected vagrancy and curfew
statutes to clear corners at certain
times of day and place black bodies
under a strict temporal and spatial
discipline to keep black bodies in their
place this can't be separated from the
skyrocketing prison population the you
have in the US which as we know is the
largest jailer in the world it holds the
greatest amount of prisoners on earth a
disproportionate number of them of
course being black men this chilling
statistic here provided by Michelle
Alexander the author of the new Jim Crow
that there are more black men in prison
today than there were enslaved in 1850
absolutely mind-blowing and while black
women are the fastest-growing sector of
the prison population this this is very
much a ghetto to Prison Pipeline as many
scholars have described it and for many
residents this connection between this
the temporal and spatial discipline they
face at their homes in the streets is
then replicated or mirrored in what they
experienced when they often make the
inevitable trip to prison very much what
the scholar eduardo and Edith notes it
as we can see the ghetto as prison and
the prison as ghetto one of the key
aspects of defensible space was
situating housing projects proximate to
so-called desirable neighbor
however as you can see here often this
proximity was physically impeded by the
establishment of massive multi Lane
arterial roads coincidentally of course
which were designed to expediency
bourbon heights through the city at the
greatest possible rate not to any points
within the city but to make their way
through the city so you can see the
Robert Taylor homes I don't know if you
can make that out in Chicago here which
are bounded by the Dan Ryan Expressway
on one side and other larger two of
roads or a very explicit example here in
Syracuse in New York this is a turn
towards a car centric urban environment
and this made residents of the projects
often who lack the capital of course to
invest in a vehicle disproportionately
reliant on public transit which as we
know at the turn of the 20th century is
facing severe cases of underfunding in
the face in particularly United States
of suburban control of regional councils
and ultimate disinterest in facilitating
regional transit authorities in the
words of the infamous Albert's Paterson
one of the most vociferous advocates of
suburban sprawl in the United States
he's the chief executive of Oakland
County a very wealthy affluent suburb
that bounds Detroit and being very clear
about his intention for how the suburbs
should relate to the city what we're
going to do is turn Detroit into an
Indian Reservation where we heard all
the Indians into the city build a fence
around it and then throw in the blankets
and corn and quote definitive means to
try and confine and restrict racial
undesirables to keep black people's poor
peoples of color in their proper place
totally cut off from the rhythms of
mainstream society fewer buses and
trains on the street and erratic or
intermediate scheduling hampers many
inner city residents attempts to move
freely within the city beyond their
immediate space and so as the temporal
and spatial isolation of the city's most
vulnerable peoples increases and as
researchers at the Brookings Institute
have again in a similar study proven
proximity to jobs and commute times can
affect the employment outcome of a
city's most vulnerable citizens between
two
thousand 2012 residents of high poverty
and majority minority neighborhoods
experienced particularly pronounced
declines in job proximity sometimes
spending over three hours on return
trips to low-paying retail and service
industry work now this matters because
people who live closer to jobs are more
likely to work they face shorter job
searches and spells of joblessness
proximity to employment proves
particularly important to certain kinds
of workers and residents for instance
the duration of joblessness among black
female or older workers tends to be more
sensitive to job accessibility than it
is for other kinds of workers for poor
residents living closer to jobs
increases the likelihood of working and
leaving welfare so from the project to
the streets to work to the simple
ability to move through the city to make
one's way through the city poor people's
of color find themselves confronted with
what's been termed a carceral lang logic
at every turn
a logic of punishment and confinement
that's rooted in specific malice
manifestations of time and space
so in conclusion even when we turn to
the language of urban renewal or
gentrification it's often weighted with
certain assumptions of race space and
time too often the peoples we wish to
renew or more accurately remove are seen
as impediments to progress given our
linear understanding of progress this
places these people as peoples literally
out of time we're one set of people's
mainly peoples of color come to
represent renewal while others as you
can see in this advertisement here for a
redevelopment in Dalston square in
London are seen as representative of
best and forgotten and regrettable past
whose physical presence must be removed
from these renewed or rejuvenated spaces
as Locke reminds us place is not neutral
it's a site of property it's a
socio-economic construction place is
constantly being contested
by socio-economic cultural and political
forces forces that I would argue can be
better understood through a temporal
lens and that we see that time and place
are functions of power plain and simple
time and place are rooted in power to
determine who can access it who can own
it
who can monetize it and more importantly
who cannot time reveals the contours of
urban inequality it links the micro
inequalities of the day-to-day life of
people the daily minutia of bus
schedules vagrancy statutes curfew
violations work shift work to the macro
systems of racial inequality and
structural racism and of course this is
not an American exclusively American
problem I've talked at length today
about specifically American issues but
this is something that defines urban
environments across the globe we see how
difference and inequality are mediated
by spatial and temporal dynamics if
nothing else conceiving of the city not
simply as a collection of places but
also as a collection of times a set of
flows of rhythms can help denaturalize
the seemingly natural entities we think
of of time and space that we don't
really give too much thought as to how
they develop it can help architects city
planners and citizens and the like
conceive of the way that temple and flow
can inform or impact on social equality
or inequality the temporal geography is
which shape and constrain intercept
inner city residents are not accidental
they are the result of historical design
and while we wait may not be able to
make up for the mistakes of the past
well we may not be able to make the
decisions of the past
unmade if we adopt new ways of looking
at spatial and temporal dynamics of
urban inequality it can perhaps better
inform the making of more equitable
urban environments that do not hold its
most vulnerable citizens hostages to
times past thank you
you
[Applause]
| 37.48 | 48 | 0.818303 | eng_Latn | 0.99999 |
d5d00ae317797d500a8f49232f596e6034ab27c0 | 937 | md | Markdown | README.md | noteasytodoit/noteasytodoit.github.io | f3f45688eb506487a991623f6e9931b4efa605f9 | [
"MIT"
] | null | null | null | README.md | noteasytodoit/noteasytodoit.github.io | f3f45688eb506487a991623f6e9931b4efa605f9 | [
"MIT"
] | null | null | null | README.md | noteasytodoit/noteasytodoit.github.io | f3f45688eb506487a991623f6e9931b4efa605f9 | [
"MIT"
] | null | null | null | # 깃 블로그 만들기
## 1. username.github.io라는 repo 생성
## 2. jekyll의 테마를 찾아 깃에서 fork를 통해 가져온 뒤 username.github.io에 저장
## 3. 적용한 테마에 맞게 `_config.yml`을 변경
## 4. 배운 내용에 대한 Post를 작성
[제작된 깃 블로그](https://noteasytodoit.github.io)
| 58.5625 | 146 | 0.724653 | kor_Hang | 0.350843 |
d5d0b398d311d6cfc48824157b9b32af82a43481 | 8,639 | md | Markdown | fortios/r/fortios_dnsfilter_profile.md | chrisjaimon2012/tfwriter | 1ea629ed386bbe6a8f21617a430dae19ba536a98 | [
"MIT"
] | 78 | 2021-01-15T14:10:30.000Z | 2022-02-14T09:17:40.000Z | fortios/r/fortios_dnsfilter_profile.md | chrisjaimon2012/tfwriter | 1ea629ed386bbe6a8f21617a430dae19ba536a98 | [
"MIT"
] | 5 | 2021-04-09T15:21:28.000Z | 2022-01-28T19:02:05.000Z | fortios/r/fortios_dnsfilter_profile.md | chrisjaimon2012/tfwriter | 1ea629ed386bbe6a8f21617a430dae19ba536a98 | [
"MIT"
] | 30 | 2021-01-17T13:16:57.000Z | 2022-03-21T12:52:08.000Z | # fortios_dnsfilter_profile
[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_dnsfilter_profile" {
source = "./modules/fortios/r/fortios_dnsfilter_profile"
# block_action - (optional) is a type of string
block_action = null
# block_botnet - (optional) is a type of string
block_botnet = null
# comment - (optional) is a type of string
comment = null
# dynamic_sort_subtable - (optional) is a type of string
dynamic_sort_subtable = null
# log_all_domain - (optional) is a type of string
log_all_domain = null
# name - (required) is a type of string
name = null
# redirect_portal - (optional) is a type of string
redirect_portal = null
# redirect_portal6 - (optional) is a type of string
redirect_portal6 = null
# safe_search - (optional) is a type of string
safe_search = null
# sdns_domain_log - (optional) is a type of string
sdns_domain_log = null
# sdns_ftgd_err_log - (optional) is a type of string
sdns_ftgd_err_log = null
# youtube_restrict - (optional) is a type of string
youtube_restrict = null
dns_translation = [{
addr_type = null
dst = null
dst6 = null
id = null
netmask = null
prefix = null
src = null
src6 = null
status = null
}]
domain_filter = [{
domain_filter_table = null
}]
external_ip_blocklist = [{
name = null
}]
ftgd_dns = [{
filters = [{
action = null
category = null
id = null
log = null
}]
options = null
}]
}
```
[top](#index)
### Variables
```terraform
variable "block_action" {
description = "(optional)"
type = string
default = null
}
variable "block_botnet" {
description = "(optional)"
type = string
default = null
}
variable "comment" {
description = "(optional)"
type = string
default = null
}
variable "dynamic_sort_subtable" {
description = "(optional)"
type = string
default = null
}
variable "log_all_domain" {
description = "(optional)"
type = string
default = null
}
variable "name" {
description = "(required)"
type = string
}
variable "redirect_portal" {
description = "(optional)"
type = string
default = null
}
variable "redirect_portal6" {
description = "(optional)"
type = string
default = null
}
variable "safe_search" {
description = "(optional)"
type = string
default = null
}
variable "sdns_domain_log" {
description = "(optional)"
type = string
default = null
}
variable "sdns_ftgd_err_log" {
description = "(optional)"
type = string
default = null
}
variable "youtube_restrict" {
description = "(optional)"
type = string
default = null
}
variable "dns_translation" {
description = "nested block: NestingList, min items: 0, max items: 0"
type = set(object(
{
addr_type = string
dst = string
dst6 = string
id = number
netmask = string
prefix = number
src = string
src6 = string
status = string
}
))
default = []
}
variable "domain_filter" {
description = "nested block: NestingList, min items: 0, max items: 1"
type = set(object(
{
domain_filter_table = number
}
))
default = []
}
variable "external_ip_blocklist" {
description = "nested block: NestingList, min items: 0, max items: 0"
type = set(object(
{
name = string
}
))
default = []
}
variable "ftgd_dns" {
description = "nested block: NestingList, min items: 0, max items: 1"
type = set(object(
{
filters = list(object(
{
action = string
category = number
id = number
log = string
}
))
options = string
}
))
default = []
}
```
[top](#index)
### Resource
```terraform
resource "fortios_dnsfilter_profile" "this" {
# block_action - (optional) is a type of string
block_action = var.block_action
# block_botnet - (optional) is a type of string
block_botnet = var.block_botnet
# comment - (optional) is a type of string
comment = var.comment
# dynamic_sort_subtable - (optional) is a type of string
dynamic_sort_subtable = var.dynamic_sort_subtable
# log_all_domain - (optional) is a type of string
log_all_domain = var.log_all_domain
# name - (required) is a type of string
name = var.name
# redirect_portal - (optional) is a type of string
redirect_portal = var.redirect_portal
# redirect_portal6 - (optional) is a type of string
redirect_portal6 = var.redirect_portal6
# safe_search - (optional) is a type of string
safe_search = var.safe_search
# sdns_domain_log - (optional) is a type of string
sdns_domain_log = var.sdns_domain_log
# sdns_ftgd_err_log - (optional) is a type of string
sdns_ftgd_err_log = var.sdns_ftgd_err_log
# youtube_restrict - (optional) is a type of string
youtube_restrict = var.youtube_restrict
dynamic "dns_translation" {
for_each = var.dns_translation
content {
# addr_type - (optional) is a type of string
addr_type = dns_translation.value["addr_type"]
# dst - (optional) is a type of string
dst = dns_translation.value["dst"]
# dst6 - (optional) is a type of string
dst6 = dns_translation.value["dst6"]
# id - (optional) is a type of number
id = dns_translation.value["id"]
# netmask - (optional) is a type of string
netmask = dns_translation.value["netmask"]
# prefix - (optional) is a type of number
prefix = dns_translation.value["prefix"]
# src - (optional) is a type of string
src = dns_translation.value["src"]
# src6 - (optional) is a type of string
src6 = dns_translation.value["src6"]
# status - (optional) is a type of string
status = dns_translation.value["status"]
}
}
dynamic "domain_filter" {
for_each = var.domain_filter
content {
# domain_filter_table - (optional) is a type of number
domain_filter_table = domain_filter.value["domain_filter_table"]
}
}
dynamic "external_ip_blocklist" {
for_each = var.external_ip_blocklist
content {
# name - (optional) is a type of string
name = external_ip_blocklist.value["name"]
}
}
dynamic "ftgd_dns" {
for_each = var.ftgd_dns
content {
# options - (optional) is a type of string
options = ftgd_dns.value["options"]
dynamic "filters" {
for_each = ftgd_dns.value.filters
content {
# action - (optional) is a type of string
action = filters.value["action"]
# category - (optional) is a type of number
category = filters.value["category"]
# id - (optional) is a type of number
id = filters.value["id"]
# log - (optional) is a type of string
log = filters.value["log"]
}
}
}
}
}
```
[top](#index)
### Outputs
```terraform
output "block_action" {
description = "returns a string"
value = fortios_dnsfilter_profile.this.block_action
}
output "block_botnet" {
description = "returns a string"
value = fortios_dnsfilter_profile.this.block_botnet
}
output "id" {
description = "returns a string"
value = fortios_dnsfilter_profile.this.id
}
output "log_all_domain" {
description = "returns a string"
value = fortios_dnsfilter_profile.this.log_all_domain
}
output "redirect_portal" {
description = "returns a string"
value = fortios_dnsfilter_profile.this.redirect_portal
}
output "redirect_portal6" {
description = "returns a string"
value = fortios_dnsfilter_profile.this.redirect_portal6
}
output "safe_search" {
description = "returns a string"
value = fortios_dnsfilter_profile.this.safe_search
}
output "sdns_domain_log" {
description = "returns a string"
value = fortios_dnsfilter_profile.this.sdns_domain_log
}
output "sdns_ftgd_err_log" {
description = "returns a string"
value = fortios_dnsfilter_profile.this.sdns_ftgd_err_log
}
output "youtube_restrict" {
description = "returns a string"
value = fortios_dnsfilter_profile.this.youtube_restrict
}
output "this" {
value = fortios_dnsfilter_profile.this
}
```
[top](#index) | 22.915119 | 71 | 0.637458 | eng_Latn | 0.793352 |
d5d1660bd32434f905b75031aaec45ed4580a869 | 7,087 | md | Markdown | docs/standard/assembly/friend.md | Jteve-Sobs/docs.de-de | 06092136f031dda8715cfe6928a4fdc0ec6c0899 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/standard/assembly/friend.md | Jteve-Sobs/docs.de-de | 06092136f031dda8715cfe6928a4fdc0ec6c0899 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/standard/assembly/friend.md | Jteve-Sobs/docs.de-de | 06092136f031dda8715cfe6928a4fdc0ec6c0899 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Friend-Assemblys
ms.date: 08/20/2019
ms.assetid: b65ea7de-0801-477a-a39c-e914c2cc107c
dev_langs:
- csharp
- vb
ms.openlocfilehash: a74d4b74ead8492028a092e090f9281231802a87
ms.sourcegitcommit: 7588136e355e10cbc2582f389c90c127363c02a5
ms.translationtype: HT
ms.contentlocale: de-DE
ms.lasthandoff: 03/15/2020
ms.locfileid: "74348169"
---
# <a name="friend-assemblies"></a>Friend-Assemblys
Eine *Friend-Assembly* ist eine Assembly, die auf die [Friend-](../../visual-basic/language-reference/modifiers/friend.md) (Visual Basic) oder [internen](../../csharp/language-reference/keywords/internal.md) (C#) Typen und Member einer anderen Assembly zugreifen kann. Wenn Sie eine Assembly als Friend-Assembly identifizieren, müssen Sie Typen und Member nicht mehr als öffentlich markieren, damit andere Assemblys auf sie zugreifen können. Dies ist insbesondere in folgenden Szenarios nützlich:
- Wenn der Testcode bei Komponententests in einer separaten Assembly ausgeführt wird, aber Zugriff auf Member in der getesteten Assembly benötigt, die als `internal` in C# oder `Friend` in Visual Basic markiert sind.
- Wenn beim Entwickeln einer Klassenbibliothek die Ergänzungen der Bibliothek in separaten Assemblys enthalten sind, aber Zugriff auf Member in vorhandenen Assemblys erfordern, die als `internal` in C# oder `Friend` in Visual Basic markiert sind.
## <a name="remarks"></a>Hinweise
Sie können das Attribut <xref:System.Runtime.CompilerServices.InternalsVisibleToAttribute> verwenden, um eine oder mehrere Friend-Assemblys für eine angegebene Assembly zu identifizieren. Im folgenden Beispiel wird das Attribut <xref:System.Runtime.CompilerServices.InternalsVisibleToAttribute> in *Assembly A* verwendet, und *Assembly B* wird als Friend-Assembly angegeben. Dadurch erhält *Assembly B* Zugriff auf alle Typen und Member in *Assembly A*, die als `internal` (C#) oder `Friend` (Visual Basic) markiert sind.
> [!NOTE]
> Wenn Sie eine Assembly wie *Assembly B* kompilieren, die auf interne Typen oder Member einer anderen Assembly wie *Assembly A* zugreift, müssen Sie den Namen der Ausgabedatei ( *.exe* oder *.dll*) explizit mithilfe der Compileroption **-out** festlegen. Dies ist erforderlich, da der Compiler den Namen für die Assembly, die er erstellt, noch nicht generiert hat, wenn er Bindungen an externe Referenzen vornimmt. Weitere Informationen hierzu finden Sie unter [-out (C#)](../../csharp/language-reference/compiler-options/out-compiler-option.md) oder [-out (Visual Basic)](../../visual-basic/reference/command-line-compiler/out.md).
```csharp
using System.Runtime.CompilerServices;
using System;
[assembly: InternalsVisibleTo("AssemblyB")]
// The class is internal by default.
class FriendClass
{
public void Test()
{
Console.WriteLine("Sample Class");
}
}
// Public class that has an internal method.
public class ClassWithFriendMethod
{
internal void Test()
{
Console.WriteLine("Sample Method");
}
}
```
```vb
Imports System.Runtime.CompilerServices
<Assembly: InternalsVisibleTo("AssemblyB")>
' Friend class.
Friend Class FriendClass
Public Sub Test()
Console.WriteLine("Sample Class")
End Sub
End Class
' Public class with a Friend method.
Public Class ClassWithFriendMethod
Friend Sub Test()
Console.WriteLine("Sample Method")
End Sub
End Class
```
Nur Assemblys, die Sie explizit als Friends angeben, können auf die Typen und Member `internal` (C#) oder `Friend` (Visual Basic) zugreifen. Wenn *Assembly B* beispielsweise ein Friend von *Assembly A* ist und *Assembly C* auf *Assembly B* verweist, verfügt *Assembly C* nicht über Zugriff auf die Typen `internal` (C#) oder `Friend` (Visual Basic) in *Assembly A*.
Der Compiler führt eine grundlegende Prüfung des Namens der Friend-Assembly durch, der an das Attribut <xref:System.Runtime.CompilerServices.InternalsVisibleToAttribute> übergeben wird. Wenn *Assembly A* die *Assembly B* als Friend-Assembly deklariert, lauten die Validierungsregeln wie folgt:
- Wenn *Assembly A* einen starken Namen hat, muss *Assembly B* auch einen starken Namen haben. Der Name der Friend-Assembly, der an das Attribut übergeben wird, muss aus dem Namen der Assembly und dem öffentlichen Schlüssel der Schlüsseldatei mit starkem Namen bestehen, der zum Signieren von *Assembly B* verwendet wird.
Der Name der Friend-Assembly, der an das <xref:System.Runtime.CompilerServices.InternalsVisibleToAttribute>-Attribut übergeben wird, kann nicht der starke Name der *Assembly B* sein. Fügen Sie keine Assemblyversion, Kultur, Architektur und kein öffentliches Schlüsseltoken ein.
- Wenn *Assembly A* keinen starken Namen hat, sollte der Name der Friend-Assembly nur aus dem Assemblynamen bestehen. Weitere Informationen finden Sie unter [Vorgehensweise: Erstellen von unsignierten Friend-Assemblys](create-unsigned-friend.md).
- Wenn *Assembly B* einen starken Namen hat, müssen Sie die Schlüsseldatei mit starkem Namen für *Assembly B* über die Projekteinstellung oder über die Compileroption `/keyfile` in der Befehlszeile angeben. Weitere Informationen finden Sie unter [Vorgehensweise: Erstellen von signierten Friend-Assemblys](create-signed-friend.md).
Die Klasse <xref:System.Security.Permissions.StrongNameIdentityPermission> bietet auch die Möglichkeit zur Freigabe von Typen mit folgenden Unterschieden:
- <xref:System.Security.Permissions.StrongNameIdentityPermission> gilt für einen einzelnen Typ, während eine Friend-Assembly für die gesamte Assembly gilt.
- Wenn Hunderte Typen in *Assembly A* vorliegen, die Sie für *Assembly B* freigeben möchten, müssen Sie <xref:System.Security.Permissions.StrongNameIdentityPermission> zu allen Typen hinzufügen. Wenn Sie eine Friend-Assembly verwenden, müssen Sie die Friend-Beziehung nur einmal deklarieren.
- Bei Verwendung von <xref:System.Security.Permissions.StrongNameIdentityPermission> müssen die Typen, die Sie freigeben möchten, als öffentlich deklariert werden. Wenn Sie eine Friend-Assembly verwenden, werden die freigegebenen Typen in `internal` (C#) oder `Friend` (Visual Basic) deklariert.
Informationen darüber, wie Sie über eine Moduldatei (eine Datei mit der Dateierweiterung *.netmodule*) auf die Typen und Methoden `internal` (C#) oder `Friend` (Visual Basic) zugreifen, finden Sie unter [-moduleassemblyname (C#)](../../csharp/language-reference/compiler-options/moduleassemblyname-compiler-option.md) oder [-moduleassemblyname (Visual Basic)](../../visual-basic/reference/command-line-compiler/moduleassemblyname.md).
## <a name="see-also"></a>Siehe auch
- <xref:System.Runtime.CompilerServices.InternalsVisibleToAttribute>
- <xref:System.Security.Permissions.StrongNameIdentityPermission>
- [How to: Erstellen von unsignierten Friend-Assemblys](create-unsigned-friend.md)
- [How to: Erstellen von signierten Friend-Assemblys](create-signed-friend.md)
- [Assemblys in .NET](index.md)
- [C#-Programmierhandbuch](../../csharp/programming-guide/index.md)
- [Programmierkonzepte (Visual Basic)](../../visual-basic/programming-guide/concepts/index.md)
| 66.858491 | 633 | 0.786793 | deu_Latn | 0.971536 |
d5d211e890968bb8dfce2dfc7e3f2997fba1f9ff | 1,658 | md | Markdown | README.md | benoitc/erlzmq2 | a3c572061e58732ac0144bc91da22e36592c37a3 | [
"MIT"
] | 1 | 2020-01-21T11:10:53.000Z | 2020-01-21T11:10:53.000Z | README.md | benoitc/erlzmq2 | a3c572061e58732ac0144bc91da22e36592c37a3 | [
"MIT"
] | null | null | null | README.md | benoitc/erlzmq2 | a3c572061e58732ac0144bc91da22e36592c37a3 | [
"MIT"
] | null | null | null | erlzmq2
====
NIF based Erlang bindings for the ZeroMQ messaging library.
Copyright (c) 2011 Yurii Rashkovskii, Evax Software and Michael Truog
Overview
========
The erlzmq2 application provides high-performance NIF based Erlang bindings
for the ZeroMQ messaging library.
Downloading
===========
The erlzmq2 source code can be found on [GitHub](https://github.com/yrashk/erlzmq2)
$ git clone http://github.com/zeromq/erlzmq2.git
It is also available on [Agner](http://erlagner.org/):
$ agner build erlzmq
In order to build erlzmq2 against a specific version of ZeroMQ (not `v2.1.11`), use this:
$ ZEROMQ_VERSION=v<VERSION> agner build erlzmq
Building
========
Build the code
$ make
If you want to build against a specific version of ZeroMQ (not `v2.1.11`), use this:
$ ZEROMQ_VERSION=v<VERSION> make
Build the docs
$ make docs
Run the test suite
$ make test
Run the benchmarks (requires [python](http://www.python.org) and [matplotlib](http://matplotlib.sourceforge.net/))
$ make bench
This will run performance tests and output png graphs in the graphs directory.
Please note that to behave properly on your system ZeroMQ might require [some tuning](http://www.zeromq.org/docs:tuning-zeromq).
Architecture
============
The bindings use Erlang's [NIF (native implemented functions)](http://www.erlang.org/doc/man/erl_nif.html) interface to achieve the best performance. One extra OS thread and one pair of inproc sockets by context are used to simulate blocking recv calls without affecting the Erlang virtual machine's responsiveness.
License
=======
The project is released under the MIT license.
| 25.507692 | 315 | 0.736429 | eng_Latn | 0.904811 |
d5d28943be205a83c3b27b064bcd4943abaeb54c | 4,718 | md | Markdown | articles/cosmos-db/cassandra-secondary-index.md | julianosaless/azure-docs.pt-br | 461791547c9cc2b4df751bb3ed881ce57796f1e4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/cosmos-db/cassandra-secondary-index.md | julianosaless/azure-docs.pt-br | 461791547c9cc2b4df751bb3ed881ce57796f1e4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/cosmos-db/cassandra-secondary-index.md | julianosaless/azure-docs.pt-br | 461791547c9cc2b4df751bb3ed881ce57796f1e4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Indexação na conta de API do Cassandra Azure Cosmos DB
description: Saiba como a indexação secundária funciona no Azure Azure Cosmos DB conta de API do Cassandra.
author: TheovanKraay
ms.service: cosmos-db
ms.topic: conceptual
ms.date: 04/04/2020
ms.author: thvankra
ms.reviewer: sngun
ms.openlocfilehash: 7de38097acdbfa1f9c9b90f3051c68dec5465b32
ms.sourcegitcommit: 849bb1729b89d075eed579aa36395bf4d29f3bd9
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 04/28/2020
ms.locfileid: "80758021"
---
# <a name="secondary-indexing-in-azure-cosmos-db-cassandra-api"></a>Indexação secundária no Azure Cosmos DB API do Cassandra
O API do Cassandra no Azure Cosmos DB aproveita a infraestrutura de indexação subjacente para expor a força de indexação que é inerente à plataforma. No entanto, ao contrário da API do SQL principal, API do Cassandra em Azure Cosmos DB não indexa todos os atributos por padrão. Em vez disso, ele dá suporte à indexação secundária para criar um índice em determinados atributos, que se comportam da mesma forma que o Apache Cassandra.
Em geral, não é recomendável executar consultas de filtro nas colunas que não estão particionadas. Você deve usar a sintaxe permitir filtragem explicitamente, o que resulta em uma operação que pode não ter um bom desempenho. No Azure Cosmos DB você pode executar essas consultas em atributos de baixa cardinalidade porque elas se descobrem entre partições para recuperar os resultados.
Não é recomendável criar um índice em uma coluna atualizada com frequência. É prudente criar um índice quando você define a tabela. Isso garante que os dados e índices estejam em um estado consistente. Caso você crie um novo índice nos dados existentes, no momento, não é possível rastrear a alteração de progresso do índice para a tabela. Se você precisar acompanhar o progresso dessa operação, precisará solicitar a alteração de progresso por meio de um [tíquete de suporte]( https://docs.microsoft.com/azure/azure-portal/supportability/how-to-create-azure-support-request).
> [!NOTE]
> Não há suporte para o índice secundário nos seguintes objetos:
> - tipos de dados como tipos de coleção congelado, decimal e tipos variantes.
> - Colunas estáticas
> - Chaves de clustering
## <a name="indexing-example"></a>Exemplo de indexação
Primeiro, crie uma tabela e um keyspace de exemplo executando os seguintes comandos no prompt do Shell CQL:
```shell
CREATE KEYSPACE sampleks WITH REPLICATION = {'class' : 'SimpleStrategy'};
CREATE TABLE sampleks.t1(user_id int PRIMARY KEY, lastname text) WITH cosmosdb_provisioned_throughput=400;
```
Em seguida, insira dados de usuário de exemplo com os seguintes comandos:
```shell
insert into sampleks.t1(user_id,lastname) values (1, 'nishu');
insert into sampleks.t1(user_id,lastname) values (2, 'vinod');
insert into sampleks.t1(user_id,lastname) values (3, 'bat');
insert into sampleks.t1(user_id,lastname) values (5, 'vivek');
insert into sampleks.t1(user_id,lastname) values (6, 'siddhesh');
insert into sampleks.t1(user_id,lastname) values (7, 'akash');
insert into sampleks.t1(user_id,lastname) values (8, 'Theo');
insert into sampleks.t1(user_id,lastname) values (9, 'jagan');
```
Se você tentar executar a instrução a seguir, encontrará um erro que solicita que você use `ALLOW FILTERING`:
```shell
select user_id, lastname from sampleks.t1 where lastname='nishu';
```
Embora o API do Cassandra ofereça suporte à filtragem de permitir, conforme mencionado na seção anterior, não é recomendável. Em vez disso, você deve criar um índice no conforme mostrado no exemplo a seguir:
```shell
CREATE INDEX ON sampleks.t1 (lastname);
```
Depois de criar um índice no campo "LastName", agora você pode executar a consulta anterior com êxito. Com API do Cassandra no Azure Cosmos DB, você não precisa fornecer um nome de índice. Um índice padrão com formato `tablename_columnname_idx` é usado. Por exemplo, ` t1_lastname_idx` é o nome do índice para a tabela anterior.
## <a name="dropping-the-index"></a>Descartando o índice
Você precisa saber qual é o nome do índice para descartar o índice. Execute o `desc schema` comando para obter a descrição da tabela. A saída desse comando inclui o nome do índice no formato `CREATE INDEX tablename_columnname_idx ON keyspacename.tablename(columnname)`. Em seguida, você pode usar o nome do índice para descartar o índice, conforme mostrado no exemplo a seguir:
```shell
drop index sampleks.t1_lastname_idx;
```
## <a name="next-steps"></a>Próximas etapas
* Saiba como funciona a [indexação automática](index-overview.md) no Azure Cosmos DB
* [Recursos do Apache Cassandra compatíveis com a API do Cassandra do Azure Cosmos DB](cassandra-support.md)
| 61.272727 | 576 | 0.78847 | por_Latn | 0.997179 |
d5d32326656eafb61e4c4b143ad54d840ef1e035 | 5,315 | md | Markdown | docs/framework/data/adonet/implement-copytodatatable-where-type-not-a-datarow.md | felpasl/docs.pt-br | 1b47adcbc2e400f937650f9de1cd0c511e80738e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/data/adonet/implement-copytodatatable-where-type-not-a-datarow.md | felpasl/docs.pt-br | 1b47adcbc2e400f937650f9de1cd0c511e80738e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/data/adonet/implement-copytodatatable-where-type-not-a-datarow.md | felpasl/docs.pt-br | 1b47adcbc2e400f937650f9de1cd0c511e80738e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'Como: Implementar CopyToDataTable<T> onde o tipo genérico T não é um DataRow'
ms.date: 03/30/2017
dev_langs:
- csharp
- vb
ms.assetid: b27b52cf-6172-485f-a75c-70ff9c5a2bd4
ms.openlocfilehash: 1f79bd421d4c504556074468f8ab7e032d3eca43
ms.sourcegitcommit: 14355b4b2fe5bcf874cac96d0a9e6376b567e4c7
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 01/30/2019
ms.locfileid: "55288152"
---
# <a name="how-to-implement-copytodatatablet-where-the-generic-type-t-is-not-a-datarow"></a>Como: Implementar CopyToDataTable\<T > em que o tipo genérico T não é um DataRow
O objeto de <xref:System.Data.DataTable> é freqüentemente usado para associação de dados. O método <xref:System.Data.DataTableExtensions.CopyToDataTable%2A> recebe os resultados de uma consulta e copia os dados em um <xref:System.Data.DataTable>, que podem ser usados para vinculação de dados. Os métodos de <xref:System.Data.DataTableExtensions.CopyToDataTable%2A> , no entanto, somente operam em uma fonte de <xref:System.Collections.Generic.IEnumerable%601> onde o parâmetro genérico `T` é do tipo <xref:System.Data.DataRow>. Embora isso é útil, não permite que as tabelas são criadas de uma sequência de tipos escalares, as consultas que o projeto tipos anônimos, ou de consultas que executam a tabela join.
Este tópico descreve como implementar dois métodos personalizados de extensão de `CopyToDataTable<T>` que aceita um parâmetro genérico `T` de um tipo diferente <xref:System.Data.DataRow>. A lógica para criar <xref:System.Data.DataTable> de uma fonte de <xref:System.Collections.Generic.IEnumerable%601> está contida na classe de `ObjectShredder<T>` , que é empacotada em dois métodos sobrecarregados de extensão de `CopyToDataTable<T>` . O método de `Shred` da classe de `ObjectShredder<T>` retorna <xref:System.Data.DataTable> preenchido e três aceita parâmetros de entrada: uma fonte de <xref:System.Collections.Generic.IEnumerable%601> , um <xref:System.Data.DataTable>, e uma enumeração de <xref:System.Data.LoadOption> . O esquema inicial de <xref:System.Data.DataTable> retornado é baseado no esquema de tipo `T`. Se uma tabela existente é fornecida como entrada, o esquema deve ser consistente com o esquema de tipo `T`. Cada propriedade pública e campo de tipo `T` são convertidos na tabela a <xref:System.Data.DataColumn> retornado. Se a sequência de origem contiver um tipo derivado de `T`, o esquema retornado da tabela é expandido para todas as propriedades públicas e campos adicionais.
Para obter exemplos de como usar os métodos `CopyToDataTable<T>` personalizados, confira [Criando uma DataTable com base em uma consulta](../../../../docs/framework/data/adonet/creating-a-datatable-from-a-query-linq-to-dataset.md).
### <a name="to-implement-the-custom-copytodatatablet-methods-in-your-application"></a>Para implementar os métodos CopyToDataTable\<T> personalizados no aplicativo
1. Implementar a classe de `ObjectShredder<T>` para criar <xref:System.Data.DataTable> de uma fonte de <xref:System.Collections.Generic.IEnumerable%601> :
[!code-csharp[DP Custom CopyToDataTable Examples#ObjectShredderClass](../../../../samples/snippets/csharp/VS_Snippets_ADO.NET/DP Custom CopyToDataTable Examples/CS/Program.cs#objectshredderclass)]
[!code-vb[DP Custom CopyToDataTable Examples#ObjectShredderClass](../../../../samples/snippets/visualbasic/VS_Snippets_ADO.NET/DP Custom CopyToDataTable Examples/VB/Module1.vb#objectshredderclass)]
O exemplo anterior pressupõe que as propriedades da `DataColumn` não sejam tipos que permitem valor nulo. Para manipular propriedades com tipos que permitem valor nulo, use o seguinte código:
```csharp
DataColumn dc = table.Columns.Contains(p.Name) ? table.Columns[p.Name] : table.Columns.Add(p.Name, Nullable.GetUnderlyingType(p.PropertyType) ?? p.PropertyType);
```
2. Implementar métodos personalizados de extensão de `CopyToDataTable<T>` em uma classe:
[!code-csharp[DP Custom CopyToDataTable Examples#CustomCopyToDataTableMethods](../../../../samples/snippets/csharp/VS_Snippets_ADO.NET/DP Custom CopyToDataTable Examples/CS/Program.cs#customcopytodatatablemethods)]
[!code-vb[DP Custom CopyToDataTable Examples#CustomCopyToDataTableMethods](../../../../samples/snippets/visualbasic/VS_Snippets_ADO.NET/DP Custom CopyToDataTable Examples/VB/Module1.vb#customcopytodatatablemethods)]
3. Adicionar a classe de `ObjectShredder<T>` e métodos de extensão de `CopyToDataTable<T>` ao seu aplicativo.
```vb
Module Module1
Sub Main()
' Your application code using CopyToDataTable<T>.
End Sub
End Module
Public Module CustomLINQtoDataSetMethods
…
End Module
Public Class ObjectShredder(Of T)
…
End Class
```
```csharp
class Program
{
static void Main(string[] args)
{
// Your application code using CopyToDataTable<T>.
}
}
public static class CustomLINQtoDataSetMethods
{
…
}
public class ObjectShredder<T>
{
…
}
```
## <a name="see-also"></a>Consulte também
- [Criando um DataTable de uma consulta](../../../../docs/framework/data/adonet/creating-a-datatable-from-a-query-linq-to-dataset.md)
- [Guia de Programação](../../../../docs/framework/data/adonet/programming-guide-linq-to-dataset.md)
| 67.278481 | 1,202 | 0.762747 | por_Latn | 0.851137 |
d5d3953c311e73b944906f948847c21796bfbb97 | 1,754 | md | Markdown | articles/supply-chain/warehousing/tasks/create-mobile-device-license-plate-consolidation.md | tradotto/dynamics-365-unified-operations-public | 06b4dbaadf8063c41bf25889720675b98c0ba0c5 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-10-09T07:56:12.000Z | 2020-10-09T07:56:12.000Z | articles/supply-chain/warehousing/tasks/create-mobile-device-license-plate-consolidation.md | tradotto/dynamics-365-unified-operations-public | 06b4dbaadf8063c41bf25889720675b98c0ba0c5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/supply-chain/warehousing/tasks/create-mobile-device-license-plate-consolidation.md | tradotto/dynamics-365-unified-operations-public | 06b4dbaadf8063c41bf25889720675b98c0ba0c5 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-09-17T06:18:23.000Z | 2021-09-17T06:18:23.000Z | ---
# required metadata
title: Create a mobile device menu item for license plate consolidation
description: This procedure shows you how to create a mobile device menu item for license plate consolidation work.
author: ShylaThompson
manager: AnnBe
ms.date: 08/29/2018
ms.topic: business-process
ms.prod:
ms.service: dynamics-ax-applications
ms.technology:
# optional metadata
ms.search.form: WHSRFMenuItem
audience: Application User
# ms.devlang:
ms.reviewer: josaw
ms.search.scope: Core, Operations
# ms.tgt_pltfrm:
# ms.custom:
ms.search.region: Global
ms.search.industry: Distribution
ms.author: mirzaab
ms.search.validFrom: 2016-06-30
ms.dyn365.ops.version: Version 7.0.0
---
# Create a mobile device menu item for license plate consolidation
[!include [task guide banner](../../includes/task-guide-banner.md)]
This procedure shows you how to create a mobile device menu item for license plate consolidation work. This enables warehouse workers to consolidate items on one license plate with items on another license place within the same location. For example, they might use this if subsequent staging steps were the same on both work orders, so that the work only needs to be performed once for the merged items. You can use this procedure in demo data company USMF. The task would typically be carried out by a warehouse manager. This procedure is for a feature that was added in Dynamics 365 for Operations, version 1611.
1. Go to Warehouse management > Setup > Mobile device > Mobile device menu items.
2. Click New.
3. In the Menu item name field, type a value.
4. In the Title field, type a value.
5. In the Mode field, select 'Indirect'.
6. In the Activity code field, select 'Consolidate license plates'.
| 41.761905 | 615 | 0.77195 | eng_Latn | 0.98716 |
d5d3cb2578759d8c23385d289c35dab29565567a | 5,075 | md | Markdown | articles/commerce/default-customer.md | MicrosoftDocs/Dynamics-365-Operations.pl-pl | fabc82553d43158349e740e44634860e5c927b6d | [
"CC-BY-4.0",
"MIT"
] | 5 | 2020-05-18T17:14:43.000Z | 2022-03-02T03:47:15.000Z | articles/commerce/default-customer.md | MicrosoftDocs/Dynamics-365-Operations.pl-pl | fabc82553d43158349e740e44634860e5c927b6d | [
"CC-BY-4.0",
"MIT"
] | 8 | 2017-12-12T13:01:05.000Z | 2021-01-17T16:41:42.000Z | articles/commerce/default-customer.md | MicrosoftDocs/Dynamics-365-Operations.pl-pl | fabc82553d43158349e740e44634860e5c927b6d | [
"CC-BY-4.0",
"MIT"
] | 4 | 2019-10-12T18:17:43.000Z | 2021-01-17T16:37:51.000Z | ---
title: Tworzenie domyślnego odbiorcy
description: W tym temacie opisano sposób tworzenia domyślnego odbiorcy używanego podczas tworzenia kanału w Microsoft Dynamics 365 Commerce.
author: samjarawan
ms.date: 01/27/2020
ms.topic: article
ms.prod: ''
ms.technology: ''
audience: Application User
ms.reviewer: v-chgri
ms.custom: ''
ms.assetid: ''
ms.search.region: Global
ms.author: samjar
ms.search.validFrom: 2020-01-20
ms.dyn365.ops.version: Release 10.0.8
ms.openlocfilehash: ff9e5665ffd82982e09f63e34b30ae6937666231855587ad2f27c5231ead8419
ms.sourcegitcommit: 42fe9790ddf0bdad911544deaa82123a396712fb
ms.translationtype: HT
ms.contentlocale: pl-PL
ms.lasthandoff: 08/05/2021
ms.locfileid: "6720966"
---
# <a name="create-a-default-customer"></a>Tworzenie domyślnego odbiorcy
[!include [banner](includes/banner.md)]
W tym temacie opisano sposób tworzenia domyślnego odbiorcy używanego podczas tworzenia kanału w Microsoft Dynamics 365 Commerce.
Podczas tworzenia kanału lub online konieczne jest podanie odbiorcy domyślnego. Domyślny odbiorca można łatwo utworzyć po uprzednim utworzeniu grupy odbiorców i książki adresowej klienta.
## <a name="create-a-customer-group"></a>Tworzenie grupy odbiorców
Jeśli nie istnieją jeszcze grupy odbiorców, można ją utworzyć. Przykładami mogą być grupy odpowiadające różnym grupom odbiorców, takim jak hurtownie, handel detaliczny, Internet, pracownicy itd.
Aby utworzyć grupę odbiorców, należy wykonać poniższe kroki.
1. W okienku nawigacji przejdź do **Moduły \> Retail i Commerce \> Pracownicy etatpwi \> Grupy uprawnień**.
1. W okienku akcji wybierz opcję **Nowy**.
1. W okienku **Grupa odbiorców** wprowadź identyfikator grupy odbiorców.
1. W razie potrzeby w polu **Opis** wprowadź opis.
1. W razie potrzeby w polu **Warunki płatności** wprowadź wartość.
1. W polu **czas między datą płatności faktury i datą** płatności wprowadź odpowiednią wartość.
1. W polu **Domyślna grupa podatków** wprowadź grupę podatków, jeśli ma ona być stosowana.
1. To pole wyboru **Ceny zawierają podatek**, jeśli ma być stosowane.
1. W polu **Domyślna przyczyna odpisu** wprowadź odpowiednią wartość, jeśli ma zastosowanie.
Poniższy obraz pokazuje kilku skonfigurowanych grup odbiorców.
## <a name="create-a-customer-address-book"></a>Tworzenie książki adresowej odbiorców
Odbiorca musi być skojarzony z książką adresową. Jeśli jeszcze nie została utworzona, należy ją utworzyć.
Aby utworzyć książkę adresową odbiorcy należy wykonać poniższe kroki.
1. W okienku nawigacji kliknij kolejno opcje **Moduły \> Retail i commerce \> Ustawienia kanału \> Książki adresowe**.
1. W okienku akcji wybierz opcję **Nowy**.
1. W polu **Nazwa** wprowadź nazwę.
1. W polu **Opis** wprowadź opis.
1. Na okienku akcji wybierz opcję **Zapisz**.
Poniższy obraz przedstawia przykład książki adresowej.
## <a name="create-a-default-customer"></a>Tworzenie domyślnego odbiorcy
Aby utworzyć domyślnego odbiorcę, należy wykonać poniższe kroki.
1. W okienku nawigacji przejdź do **Moduły \> Retail i Commerce \> Pracownicy etatpwi \> Wszyscy odbiorcy**.
1. W okienku akcji wybierz opcję **Nowy**.
1. Z listy rozwijanej **Typ** wybierz „Osoba”.
1. Z listy rozwijanej **Konto odbiorcy** wybierz lub wprowadź numer konta (na przykład „100001”).
1. Z listy rozwijanej **Imię** wybierz lub wprowadź nazwę (na przykład „domyślna”).
1. Z listy rozwijanej **Drugie imię** wybierz lub wprowadź nazwę (na przykład „Retail”).
1. Z listy rozwijanej **Nazwisko** wybierz lub wprowadź nazwę (na przykład „Odbiorca”).
1. Z listy rozwijanej **Waluta** wybierz lub wprowadź walutę (na przykład „USD”).
1. Z listy rozwijanej **Waluta** Wybierz utworzoną wcześniej grupę odbiorców.
1. Z listy rozwijanej **Książki adresowe** wybierz istniejącą książkę adresową klienta.
1. Wybierz opcję **Zapisz**, aby zapisać i powrócić do ekranu szczegółów odbiorcy dla nowego odbiorcy.
> [!NOTE]
> Nie trzeba dodawać adresu dla domyślnego odbiorcy.
Poniższy obraz przedstawia przykład tworzenia odbiorcy.
Poniższy rysunek przedstawia domyślną konfigurację klienta.
Większość wartości domyślnych na ekranie szczegóły odbiorcy może pozostać, ale dwie wartości powinny zostać zmienione.
1. Na ekranie szczegóły odbiorcy rozwiń węzeł **Ustawienia domyślne zamówienia sprzedaży**.
1. Z listy rozwijanej **Witryna** wybierz lub wprowadź wstępnie skonfigurowany oddział.
1. Z listy rozwijanej **Magazyn** wybierz lub wprowadź wstępnie skonfigurowany magazyn.
Poniższy obraz przedstawia przykład konfiguracji tworzenia odbiorcy.
## <a name="additional-resources"></a>Dodatkowe zasoby
[Omówienie kanałów](channels-overview.md)
[Wymagania wstępne dotyczące konfiguracji kanału](channels-prerequisites.md)
[!INCLUDE[footer-include](../includes/footer-banner.md)]
| 44.911504 | 194 | 0.788177 | pol_Latn | 0.999888 |
d5d3d512f3c441114235128d806378de29f4b4ac | 61 | md | Markdown | README.md | kasworld/wxpy-stopwatch | e623d0146b5550288b46ef97367653c814321d2e | [
"Apache-2.0"
] | null | null | null | README.md | kasworld/wxpy-stopwatch | e623d0146b5550288b46ef97367653c814321d2e | [
"Apache-2.0"
] | null | null | null | README.md | kasworld/wxpy-stopwatch | e623d0146b5550288b46ef97367653c814321d2e | [
"Apache-2.0"
] | null | null | null | # simple stopwatch
## requirements
python 2.x
wxpython
| 7.625 | 19 | 0.704918 | eng_Latn | 0.965707 |
d5d3dcfafee808be08680ae890401ec0cd367910 | 643 | md | Markdown | content/ecomerce/problemStatement/index.md | josueal1/v4 | bfe01fa939d1ef88320249d6587cb35c7494f1a8 | [
"MIT"
] | null | null | null | content/ecomerce/problemStatement/index.md | josueal1/v4 | bfe01fa939d1ef88320249d6587cb35c7494f1a8 | [
"MIT"
] | 3 | 2021-05-16T05:15:34.000Z | 2021-06-05T20:26:56.000Z | content/ecomerce/problemStatement/index.md | josueal1/v4 | bfe01fa939d1ef88320249d6587cb35c7494f1a8 | [
"MIT"
] | null | null | null | ---
title: 'Eco-Merce'
avatar: './problem-statement.png'
---
<h3>What?</h3>
This is an online marketplace that allows users to buy and sell eco-friendly, 'green' products. Every item listed on the website is guaranteed to be made of sustainable materials and ethical labor practices. This vision includes the core principles of convenience, affordability, and variety.
<hr/>
<h3>Why?</h3>
Every year we produce over 300 million tons of plastic -- that’s equivalent to 200 million Toyota Corollas -- with just half of that going to single-use plastic. If we continue in this direction, we’ll have more plastic in the ocean than fish by 2050.
| 53.583333 | 292 | 0.765163 | eng_Latn | 0.998498 |
d5d4551b62d6ad74601fee70372a0207297f1b41 | 22,436 | md | Markdown | articles/azure-monitor/samples/powershell-samples.md | tsunami416604/azure-docs.hu-hu | aeba852f59e773e1c58a4392d035334681ab7058 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-monitor/samples/powershell-samples.md | tsunami416604/azure-docs.hu-hu | aeba852f59e773e1c58a4392d035334681ab7058 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-monitor/samples/powershell-samples.md | tsunami416604/azure-docs.hu-hu | aeba852f59e773e1c58a4392d035334681ab7058 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: PowerShell-minták Azure Monitor
description: A PowerShell használatával férhet hozzá olyan Azure Monitor-funkciókhoz, mint például az autoscale, a riasztások, a webhookok és a keresési tevékenységek naplói.
ms.subservice: ''
ms.topic: sample
author: bwren
ms.author: bwren
ms.date: 2/14/2018
ms.custom: devx-track-azurepowershell
ms.openlocfilehash: 4f7ddf94bbd077912cf0d7c2adef2eac548274ca
ms.sourcegitcommit: 5b93010b69895f146b5afd637a42f17d780c165b
ms.translationtype: MT
ms.contentlocale: hu-HU
ms.lasthandoff: 12/02/2020
ms.locfileid: "96532278"
---
# <a name="azure-monitor-powershell-samples"></a>PowerShell-minták Azure Monitor
Ebből a cikkből megtudhatja, hogyan érheti el Azure Monitor szolgáltatásait a PowerShell-parancsok segítségével.
> [!NOTE]
> A Azure Monitor az "Azure-betekintő" nevű új név, 2016. szeptember 25-én. Azonban a névterek és így a következő parancsok továbbra is tartalmazzák a Word- *ismereteket*.
[!INCLUDE [updated-for-az](../../../includes/updated-for-az.md)]
## <a name="set-up-powershell"></a>A PowerShell beállítása
Ha még nem tette meg, állítsa be a PowerShellt úgy, hogy a számítógépen fusson. További információ: [a PowerShell telepítése és konfigurálása](/powershell/azure/).
## <a name="examples-in-this-article"></a>Példák ebben a cikkben
A cikkben szereplő példák bemutatják, hogyan használhatja Azure Monitor parancsmagokat. Áttekintheti Azure Monitor PowerShell-parancsmagok teljes listáját Azure Monitor (betekintő [) parancsmagok](/powershell/module/az.applicationinsights)esetén is.
## <a name="sign-in-and-use-subscriptions"></a>Bejelentkezés és előfizetés használata
Először jelentkezzen be az Azure-előfizetésbe.
```powershell
Connect-AzAccount
```
Ekkor megjelenik a bejelentkezési képernyő. Miután bejelentkezett a fiókjába, a TenantID és az alapértelmezett előfizetés-azonosító megjelenik. Az összes Azure-parancsmag az alapértelmezett előfizetés kontextusában működik. A következő parancs használatával tekintheti meg az Ön számára elérhető előfizetések listáját:
```powershell
Get-AzSubscription
```
A következő parancs futtatásával megtekintheti a munkakörnyezetét (mely előfizetéssel futtatja a parancsokat):
```powershell
Get-AzContext
```
Ha módosítani szeretné a munkakörnyezetét egy másik előfizetésre, használja a következő parancsot:
```powershell
Set-AzContext -SubscriptionId <subscriptionid>
```
## <a name="retrieve-activity-log"></a>Tevékenység naplójának beolvasása
Használja a [Get-AzLog](/powershell/module/az.monitor/get-azlog) parancsmagot. Az alábbiakban néhány gyakori példát talál. A Tevékenységnapló az elmúlt 90 nap műveleteit tárolja. Az idő előtti dátumok használata hibaüzenetet eredményez.
Az alábbi parancsokban megtekintheti, hogy az aktuális dátum/idő milyen időpontot használjon:
```powershell
Get-Date
```
Naplóbejegyzések beolvasása ebből az időpontból/dátumból:
```powershell
Get-AzLog -StartTime 2019-03-01T10:30
```
Naplóbejegyzések beolvasása egy idő/dátumtartomány között:
```powershell
Get-AzLog -StartTime 2019-01-01T10:30 -EndTime 2015-01-01T11:30
```
Naplóbejegyzések beolvasása egy adott erőforráscsoporthoz:
```powershell
Get-AzLog -ResourceGroup 'myrg1'
```
A naplóbejegyzések beolvasása egy adott erőforrás-szolgáltatótól egy idő/dátumtartomány között:
```powershell
Get-AzLog -ResourceProvider 'Microsoft.Web' -StartTime 2015-01-01T10:30 -EndTime 2015-01-01T11:30
```
Minden naplóbejegyzés beolvasása egy megadott hívóval:
```powershell
Get-AzLog -Caller '[email protected]'
```
A következő parancs lekéri az utolsó 1000 eseményt a tevékenység naplójából:
```powershell
Get-AzLog -MaxRecord 1000
```
`Get-AzLog` számos más paramétert is támogat. `Get-AzLog`További információért tekintse meg a referenciát.
> [!NOTE]
> `Get-AzLog` csak 15 napos előzményt biztosít. 15 napon túl a **-MaxRecords** paraméterrel kérdezheti le az utolsó N eseményt. A 15 napnál régebbi események eléréséhez használja a REST API-t vagy az SDK-t (C#-példa az SDK-t használva). Ha nem adja meg a **StartTime** értékét, akkor az alapértelmezett érték az **EndTime** értéke mínusz egy óra. Ha nem adja meg az **EndTime** értékét, akkor az alapértelmezett érték az aktuális időpont. Minden időpont a UTC időzónában van megadva.
>
>
## <a name="retrieve-alerts-history"></a>Riasztások előzményeinek beolvasása
Az összes riasztási esemény megtekintéséhez a következő példákkal kérdezheti le a Azure Resource Manager naplókat.
```powershell
Get-AzLog -Caller "Microsoft.Insights/alertRules" -DetailedOutput -StartTime 2015-03-01
```
Egy adott riasztási szabály előzményeinek megtekintéséhez használhatja a `Get-AzAlertHistory` parancsmagot, amely a riasztási szabály erőforrás-azonosítójában adható meg.
```powershell
Get-AzAlertHistory -ResourceId /subscriptions/s1/resourceGroups/rg1/providers/microsoft.insights/alertrules/myalert -StartTime 2016-03-1 -Status Activated
```
A `Get-AzAlertHistory` parancsmag a különböző paramétereket támogatja. További információ: [Get-AlertHistory](/previous-versions/azure/mt282453(v=azure.100)).
## <a name="retrieve-information-on-alert-rules"></a>Riasztási szabályokkal kapcsolatos információk lekérése
A következő parancsok mindegyike egy "legszélesebb" nevű erőforráscsoport esetében működik.
A riasztási szabály összes tulajdonságának megtekintése:
```powershell
Get-AzAlertRule -Name simpletestCPU -ResourceGroup montest -DetailedOutput
```
Egy erőforráscsoport összes riasztásának beolvasása:
```powershell
Get-AzAlertRule -ResourceGroup montest
```
A célként megadott erőforráshoz beállított összes riasztási szabály beolvasása. Például a virtuális gépen beállított összes riasztási szabály.
```powershell
Get-AzAlertRule -ResourceGroup montest -TargetResourceId /subscriptions/s1/resourceGroups/montest/providers/Microsoft.Compute/virtualMachines/testconfig
```
`Get-AzAlertRule` más paramétereket is támogat. További információ: [Get-AlertRule](/previous-versions/azure/mt282459(v=azure.100)) .
## <a name="create-metric-alerts"></a>Metrikákhoz kapcsolódó riasztások létrehozása
A `Add-AlertRule` parancsmag használatával riasztási szabályt hozhat létre, frissíthet vagy tilthatja le.
E-mailek és webhook-tulajdonságok a és a használatával is létrehozhatók `New-AzAlertRuleEmail` `New-AzAlertRuleWebhook` . A riasztási szabály parancsmagban ezeket a tulajdonságokat adja hozzá műveletként a riasztási szabály **műveletek** tulajdonságához.
A következő táblázat a riasztások metrika használatával történő létrehozásához használt paramétereket és értékeket ismerteti.
| parameter | value |
| --- | --- |
| Név |simpletestdiskwrite |
| A riasztási szabály helye |USA keleti régiója |
| ResourceGroup |legtöbbször |
| Targetresourceid azonosítója |/subscriptions/s1/resourceGroups/montest/providers/Microsoft.Compute/virtualMachines/testconfig |
| A létrehozott riasztás MetricName |\PhysicalDisk (_Total) \ írás gyakorisága (művelet/s). Tekintse `Get-MetricDefinitions` meg a pontos metrikák nevének beolvasását ismertető parancsmagot. |
| operátor |GreaterThan |
| Küszöbérték (darabszám/mp a metrika esetében) |1 |
| WindowSize (óó: PP: SS formátum) |00:05:00 |
| gyűjtő (a metrika statisztikája, amely az átlagot használja, ebben az esetben) |Átlag |
| Egyéni e-mailek (karakterlánc-tömb) |'[email protected]','[email protected]' |
| e-mail küldése a tulajdonosoknak, közreműködőknek és olvasóknak |-SendToServiceOwners |
E-mail művelet létrehozása
```powershell
$actionEmail = New-AzAlertRuleEmail -CustomEmail [email protected]
```
Webhook-művelet létrehozása
```powershell
$actionWebhook = New-AzAlertRuleWebhook -ServiceUri https://example.com?token=mytoken
```
Riasztási szabály létrehozása a CPU% metrika szolgáltatásban klasszikus virtuális gépen
```powershell
Add-AzMetricAlertRule -Name vmcpu_gt_1 -Location "East US" -ResourceGroup myrg1 -TargetResourceId /subscriptions/s1/resourceGroups/myrg1/providers/Microsoft.ClassicCompute/virtualMachines/my_vm1 -MetricName "Percentage CPU" -Operator GreaterThan -Threshold 1 -WindowSize 00:05:00 -TimeAggregationOperator Average -Action $actionEmail, $actionWebhook -Description "alert on CPU > 1%"
```
A riasztási szabály beolvasása
```powershell
Get-AzAlertRule -Name vmcpu_gt_1 -ResourceGroup myrg1 -DetailedOutput
```
A riasztás hozzáadása parancsmag szintén frissíti a szabályt, ha már létezik riasztási szabály a megadott tulajdonságokhoz. A riasztási szabályok letiltásához adja meg a **-DisableRule** paramétert.
## <a name="get-a-list-of-available-metrics-for-alerts"></a>A riasztásokhoz elérhető metrikák listájának beolvasása
A `Get-AzMetricDefinition` parancsmag segítségével megtekintheti az adott erőforráshoz tartozó összes metrika listáját.
```powershell
Get-AzMetricDefinition -ResourceId <resource_id>
```
Az alábbi példa egy táblázatot hoz létre a metrika nevével és a hozzá tartozó egységgel.
```powershell
Get-AzMetricDefinition -ResourceId <resource_id> | Format-Table -Property Name,Unit
```
A rendelkezésre álló lehetőségek teljes listája a `Get-AzMetricDefinition` [Get-MetricDefinitions](/previous-versions/azure/mt282458(v=azure.100))címen érhető el.
## <a name="create-and-manage-activity-log-alerts"></a>Műveletnapló-riasztások létrehozása és kezelése
A `Set-AzActivityLogAlert` parancsmag segítségével beállíthatja a műveletnapló riasztását. A műveletnapló riasztásához először meg kell határoznia a feltételeket szótárként, majd létre kell hoznia egy riasztást, amely ezeket a feltételeket használja.
```powershell
$condition1 = New-AzActivityLogAlertCondition -Field 'category' -Equal 'Administrative'
$condition2 = New-AzActivityLogAlertCondition -Field 'operationName' -Equal 'Microsoft.Compute/virtualMachines/write'
$additionalWebhookProperties = New-Object "System.Collections.Generic.Dictionary``2[System.String,System.String]"
$additionalWebhookProperties.Add('customProperty', 'someValue')
$actionGrp1 = New-AzActionGroup -ActionGroupId '/subscriptions/<subid>/providers/Microsoft.Insights/actiongr1' -WebhookProperty $additionalWebhookProperties
Set-AzActivityLogAlert -Location 'Global' -Name 'alert on VM create' -ResourceGroupName 'myResourceGroup' -Scope '/subscriptions/<subid>' -Action $actionGrp1 -Condition $condition1, $condition2
```
A további webhook-tulajdonságok nem kötelezőek. Egy műveletnapló-riasztás tartalmát a használatával kérheti vissza `Get-AzActivityLogAlert` .
## <a name="create-and-manage-autoscale-settings"></a>Az autoskálázási beállítások létrehozása és kezelése
> [!NOTE]
> Cloud Services (Microsoft. ClassicCompute) esetében az autoskálázás 5 perces időtartamot (PT5M) támogat. A többi szolgáltatás esetében az autoscale legalább 1 perces időtartamot támogat (PT1M)
Egy erőforrás (webalkalmazás, virtuális gép, felhőalapú szolgáltatás vagy virtuálisgép-méretezési csoport) csak egy, a számára konfigurált méretezési beállítással rendelkezhet.
Az egyes autoskálázási beállítások azonban több profillal is rendelkezhetnek. Például egy a teljesítmény-alapú méretezési profilhoz, egy másik pedig egy ütemezett profilhoz. Minden profilhoz több szabály is konfigurálható. Az autoscale használatával kapcsolatos további információkért lásd az [alkalmazások autoskálázását](../../cloud-services/cloud-services-how-to-scale-portal.md)ismertető témakört.
A következő lépéseket kell használni:
1. Szabály (ok) létrehozása.
2. Profil (ok) létrehozása a korábban létrehozott szabályoknak a profilokhoz való hozzárendelésével.
3. Nem kötelező: értesítések létrehozása az autoskálázáshoz webhook és e-mail-tulajdonságok konfigurálásával.
4. Az előző lépésekben létrehozott profilok és értesítések leképezésével hozzon létre egy, a cél erőforrásban található névvel rendelkező autoskálázási beállítást.
Az alábbi példák bemutatják, hogyan hozhat létre egy virtuálisgép-méretezési csoportra vonatkozó, a CPU-kihasználtság metrikája alapján egy Windows operációs rendszerhez készült, a virtuális gépek méretezésére szolgáló beállítást.
Először hozzon létre egy szabályt a felskálázáshoz, és növelje a példányszámot.
```powershell
$rule1 = New-AzAutoscaleRule -MetricName "Percentage CPU" -MetricResourceId /subscriptions/s1/resourceGroups/big2/providers/Microsoft.Compute/virtualMachineScaleSets/big2 -Operator GreaterThan -MetricStatistic Average -Threshold 60 -TimeGrain 00:01:00 -TimeWindow 00:10:00 -ScaleActionCooldown 00:10:00 -ScaleActionDirection Increase -ScaleActionValue 1
```
Ezután hozzon létre egy, a skálázáshoz használandó szabályt a példányszám csökkenésével.
```powershell
$rule2 = New-AzAutoscaleRule -MetricName "Percentage CPU" -MetricResourceId /subscriptions/s1/resourceGroups/big2/providers/Microsoft.Compute/virtualMachineScaleSets/big2 -Operator GreaterThan -MetricStatistic Average -Threshold 30 -TimeGrain 00:01:00 -TimeWindow 00:10:00 -ScaleActionCooldown 00:10:00 -ScaleActionDirection Decrease -ScaleActionValue 1
```
Ezután hozzon létre egy profilt a szabályokhoz.
```powershell
$profile1 = New-AzAutoscaleProfile -DefaultCapacity 2 -MaximumCapacity 10 -MinimumCapacity 2 -Rules $rule1,$rule2 -Name "My_Profile"
```
Hozzon létre egy webhook-tulajdonságot.
```powershell
$webhook_scale = New-AzAutoscaleWebhook -ServiceUri "https://example.com?mytoken=mytokenvalue"
```
Hozza létre az értesítési tulajdonságot az autoskálázási beállításhoz, beleértve az e-maileket és a korábban létrehozott webhookot.
```powershell
$notification1= New-AzAutoscaleNotification -CustomEmails [email protected] -SendEmailToSubscriptionAdministrators SendEmailToSubscriptionCoAdministrators -Webhooks $webhook_scale
```
Végül hozza létre az autoskálázási beállítást a korábban létrehozott profil hozzáadásához.
```powershell
Add-AzAutoscaleSetting -Location "East US" -Name "MyScaleVMSSSetting" -ResourceGroup big2 -TargetResourceId /subscriptions/s1/resourceGroups/big2/providers/Microsoft.Compute/virtualMachineScaleSets/big2 -AutoscaleProfiles $profile1 -Notifications $notification1
```
Az autoscale-beállítások kezelésével kapcsolatos további információkért lásd: [Get-AutoscaleSetting](/previous-versions/azure/mt282461(v=azure.100)).
## <a name="autoscale-history"></a>Az autoskálázás előzményei
Az alábbi példa bemutatja, hogyan tekintheti meg a legutóbbi méretezési és riasztási eseményeket. A tevékenység naplójának keresési funkciójának használatával megtekintheti az autoskálázási előzményeket.
```powershell
Get-AzLog -Caller "Microsoft.Insights/autoscaleSettings" -DetailedOutput -StartTime 2015-03-01
```
A `Get-AzAutoScaleHistory` parancsmag használatával lekérheti az automatikusan méretezhető előzményeket.
```powershell
Get-AzAutoScaleHistory -ResourceId /subscriptions/s1/resourceGroups/myrg1/providers/microsoft.insights/autoscalesettings/myScaleSetting -StartTime 2016-03-15 -DetailedOutput
```
További információ: [Get-AutoscaleHistory](/previous-versions/azure/mt282464(v=azure.100)).
### <a name="view-details-for-an-autoscale-setting"></a>Egy autoskálázási beállítás részleteinek megtekintése
A `Get-Autoscalesetting` parancsmaggal további információkat kérhet le az automatikusan méretezhető beállításról.
Az alábbi példa a "myrg1" erőforráscsoport összes autoskálázási beállításának részleteit mutatja be.
```powershell
Get-AzAutoscalesetting -ResourceGroup myrg1 -DetailedOutput
```
Az alábbi példa a "myrg1" erőforráscsoport összes autoskálázási beállításának részleteit mutatja be, pontosabban a "MyScaleVMSSSetting" nevű autoskálázási beállítást.
```powershell
Get-AzAutoscalesetting -ResourceGroup myrg1 -Name MyScaleVMSSSetting -DetailedOutput
```
### <a name="remove-an-autoscale-setting"></a>Egy autoskálázási beállítás eltávolítása
A `Remove-Autoscalesetting` parancsmag használatával törölheti az egy autoskálázási beállítást.
```powershell
Remove-AzAutoscalesetting -ResourceGroup myrg1 -Name MyScaleVMSSSetting
```
## <a name="manage-log-profiles-for-activity-log"></a>A műveletnapló profiljainak kezelése
Létrehozhat egy log- *profilt* , és exportálhatja az adatait a tevékenység naplójából egy Storage-fiókba, és beállíthatja az adatmegőrzést. Igény szerint továbbíthatja az adatait az Event hub-ba is. Ez a szolgáltatás jelenleg előzetes verzióban érhető el, és előfizetéshez csak egy naplózási profilt hozhat létre. A következő parancsmagokat használhatja a jelenlegi előfizetésével a log profilok létrehozásához és kezeléséhez. Kiválaszthat egy adott előfizetést is. Habár a PowerShell alapértelmezés szerint a jelenlegi előfizetést használja, bármikor módosíthatja a következőt: `Set-AzContext` . A műveletnapló konfigurálásával az adott előfizetésen belül bármely Storage-fiókra vagy Event hub-ra irányíthatja az adatútvonalat. Az adatfájlok JSON formátumú blob-fájlként íródnak.
### <a name="get-a-log-profile"></a>Log-profil beolvasása
A meglévő log-profilok beolvasásához használja a `Get-AzLogProfile` parancsmagot.
### <a name="add-a-log-profile-without-data-retention"></a>Adatmegőrzés nélküli log-profil hozzáadása
```powershell
Add-AzLogProfile -Name my_log_profile_s1 -StorageAccountId /subscriptions/s1/resourceGroups/myrg1/providers/Microsoft.Storage/storageAccounts/my_storage -Location global,westus,eastus,northeurope,westeurope,eastasia,southeastasia,japaneast,japanwest,northcentralus,southcentralus,eastus2,centralus,australiaeast,australiasoutheast,brazilsouth,centralindia,southindia,westindia
```
### <a name="remove-a-log-profile"></a>Log-profil eltávolítása
```powershell
Remove-AzLogProfile -name my_log_profile_s1
```
### <a name="add-a-log-profile-with-data-retention"></a>Adatmegőrzést biztosító log-profil hozzáadása
Megadhatja a **-RetentionInDays** tulajdonságot a napok számával, pozitív egészként, ahol az adat megmarad.
```powershell
Add-AzLogProfile -Name my_log_profile_s1 -StorageAccountId /subscriptions/s1/resourceGroups/myrg1/providers/Microsoft.Storage/storageAccounts/my_storage -Location global,westus,eastus,northeurope,westeurope,eastasia,southeastasia,japaneast,japanwest,northcentralus,southcentralus,eastus2,centralus,australiaeast,australiasoutheast,brazilsouth,centralindia,southindia,westindia -RetentionInDays 90
```
### <a name="add-log-profile-with-retention-and-eventhub"></a>Naplózási profil hozzáadása a megőrzéssel és a EventHub
Az adatok Storage-fiókba való továbbítása mellett azt is megteheti, hogy egy Event hub-ba is továbbíthatja azt. Ebben az előzetes kiadásban a Storage-fiók konfigurációja kötelező, de az Event hub konfigurációja nem kötelező.
```powershell
Add-AzLogProfile -Name my_log_profile_s1 -StorageAccountId /subscriptions/s1/resourceGroups/myrg1/providers/Microsoft.Storage/storageAccounts/my_storage -serviceBusRuleId /subscriptions/s1/resourceGroups/Default-ServiceBus-EastUS/providers/Microsoft.ServiceBus/namespaces/mytestSB/authorizationrules/RootManageSharedAccessKey -Location global,westus,eastus,northeurope,westeurope,eastasia,southeastasia,japaneast,japanwest,northcentralus,southcentralus,eastus2,centralus,australiaeast,australiasoutheast,brazilsouth,centralindia,southindia,westindia -RetentionInDays 90
```
## <a name="configure-diagnostics-logs"></a>Diagnosztikai naplók konfigurálása
Számos Azure-szolgáltatás további naplókat és telemetria biztosít, amelyek a következők közül választhatnak:
- konfigurálható az Azure Storage-fiókban tárolt adatmentéshez
- elküldve Event Hubs
- elküldjük egy Log Analytics munkaterületre.
A műveletet csak erőforrás szintjén lehet végrehajtani. A Storage-fióknak vagy az Event hub-nek ugyanabban a régióban kell lennie, mint a diagnosztikai beállítást futtató célként megadott erőforrásnak.
### <a name="get-diagnostic-setting"></a>Diagnosztikai beállítás beolvasása
```powershell
Get-AzDiagnosticSetting -ResourceId /subscriptions/s1/resourceGroups/myrg1/providers/Microsoft.Logic/workflows/andy0315logicapp
```
Diagnosztikai beállítások letiltása
```powershell
Set-AzDiagnosticSetting -ResourceId /subscriptions/s1/resourceGroups/myrg1/providers/Microsoft.Logic/workflows/andy0315logicapp -StorageAccountId /subscriptions/s1/resourceGroups/Default-Storage-WestUS/providers/Microsoft.Storage/storageAccounts/mystorageaccount -Enable $false
```
Diagnosztikai beállítás engedélyezése megőrzés nélkül
```powershell
Set-AzDiagnosticSetting -ResourceId /subscriptions/s1/resourceGroups/myrg1/providers/Microsoft.Logic/workflows/andy0315logicapp -StorageAccountId /subscriptions/s1/resourceGroups/Default-Storage-WestUS/providers/Microsoft.Storage/storageAccounts/mystorageaccount -Enable $true
```
Diagnosztikai beállítás engedélyezése megőrzéssel
```powershell
Set-AzDiagnosticSetting -ResourceId /subscriptions/s1/resourceGroups/myrg1/providers/Microsoft.Logic/workflows/andy0315logicapp -StorageAccountId /subscriptions/s1/resourceGroups/Default-Storage-WestUS/providers/Microsoft.Storage/storageAccounts/mystorageaccount -Enable $true -RetentionEnabled $true -RetentionInDays 90
```
Diagnosztikai beállítás engedélyezése egy adott naplózási kategória megőrzésével
```powershell
Set-AzDiagnosticSetting -ResourceId /subscriptions/s1/resourceGroups/insights-integration/providers/Microsoft.Network/networkSecurityGroups/viruela1 -StorageAccountId /subscriptions/s1/resourceGroups/myrg1/providers/Microsoft.Storage/storageAccounts/sakteststorage -Categories NetworkSecurityGroupEvent -Enable $true -RetentionEnabled $true -RetentionInDays 90
```
Diagnosztikai beállítás engedélyezése Event Hubs
```powershell
Set-AzDiagnosticSetting -ResourceId /subscriptions/s1/resourceGroups/insights-integration/providers/Microsoft.Network/networkSecurityGroups/viruela1 -serviceBusRuleId /subscriptions/s1/resourceGroups/Default-ServiceBus-EastUS/providers/Microsoft.ServiceBus/namespaces/mytestSB/authorizationrules/RootManageSharedAccessKey -Enable $true
```
Diagnosztikai beállítás engedélyezése Log Analytics
```powershell
Set-AzDiagnosticSetting -ResourceId /subscriptions/s1/resourceGroups/insights-integration/providers/Microsoft.Network/networkSecurityGroups/viruela1 -WorkspaceId /subscriptions/s1/resourceGroups/insights-integration/providers/providers/microsoft.operationalinsights/workspaces/myWorkspace -Enabled $true
```
Vegye figyelembe, hogy a munkaterület azonosítója tulajdonság a munkaterület *erőforrás-azonosítóját* veszi át. A Log Analytics munkaterület erőforrás-AZONOSÍTÓját a következő paranccsal szerezheti be:
```powershell
(Get-AzOperationalInsightsWorkspace).ResourceId
```
Ezek a parancsok kombinálhatók több célhelyre történő adatküldéshez is.
| 55.672457 | 780 | 0.824791 | hun_Latn | 0.999456 |
d5d4c19718c9b58a75441d238d95a0e01409b239 | 46 | md | Markdown | _src/cabinets_2/README.md | brainsandspace/brainsandspaceweekly | 17cf07dde04436d80bd2efc54c3e2e80bce82228 | [
"MIT"
] | null | null | null | _src/cabinets_2/README.md | brainsandspace/brainsandspaceweekly | 17cf07dde04436d80bd2efc54c3e2e80bce82228 | [
"MIT"
] | 1 | 2017-02-07T03:29:03.000Z | 2017-02-07T03:29:49.000Z | _src/cabinets_2/README.md | brainsandspace/brainsandspaceweekly-frontend | 17cf07dde04436d80bd2efc54c3e2e80bce82228 | [
"MIT"
] | null | null | null | ## Nice to Haves
- Update reviews in real time | 23 | 29 | 0.73913 | eng_Latn | 0.965971 |
d5d5511c5aebe97557f6835ff148ac76b63a860e | 1,018 | md | Markdown | sdk/js/README.md | CyberEyeResearchLabs/lorawan-stack | 35106a064a5794e9d0f1e74da688a6762e09c6c2 | [
"Apache-2.0"
] | 2 | 2021-04-30T20:40:23.000Z | 2021-06-10T14:57:42.000Z | sdk/js/README.md | CyberEyeResearchLabs/lorawan-stack | 35106a064a5794e9d0f1e74da688a6762e09c6c2 | [
"Apache-2.0"
] | 1 | 2021-05-11T22:33:13.000Z | 2021-05-11T22:33:13.000Z | sdk/js/README.md | CyberEyeResearchLabs/lorawan-stack | 35106a064a5794e9d0f1e74da688a6762e09c6c2 | [
"Apache-2.0"
] | null | null | null | # The Things Stack for LoRaWAN JavaScript SDK
This is the official SDK for the The Things Stack for LoRaWAN.
## Installation
```bash
$ yarn add ttn
```
## Usage
### Basic Setup
```javascript
import TTN from 'ttn'
const token = 'paste-your-token-here'
const ttn = new TTN(token, {
connectionType: 'http',
baseURL: 'http://localhost:1885/api/v3',
defaultUserId: 'testuser',
})
```
### Creating Applications
```javascript
const appData = {
ids: {
application_id: 'first-app',
},
name: 'Test App',
description: 'Some description',
}
// Via Applications object.
const firstApp = await ttn.Applications.create('testuser', appData)
// Via Application class.
const secondApp = new ttn.Application(appData)
await secondApp.save()
```
## Development
### Building
```bash
$ yarn run build
```
This will transpile the source to `/dist`
### Watching Changes
```bash
$ yarn run watch
```
### Testing
```bash
$ yarn run jest
```
## Examples
There are some basic usage examples in `/src/examples`
| 14.970588 | 67 | 0.681729 | eng_Latn | 0.6534 |
d5d60696d4d5c5b9b09a2ff3784a486434380041 | 732 | md | Markdown | _posts/2018-08-28-newmembers.md | suchestoncampbelllab/suchestoncampbelllab.github.io | a9f8619553965ecf51b5a2ca6b350a3c67698b9d | [
"MIT"
] | null | null | null | _posts/2018-08-28-newmembers.md | suchestoncampbelllab/suchestoncampbelllab.github.io | a9f8619553965ecf51b5a2ca6b350a3c67698b9d | [
"MIT"
] | null | null | null | _posts/2018-08-28-newmembers.md | suchestoncampbelllab/suchestoncampbelllab.github.io | a9f8619553965ecf51b5a2ca6b350a3c67698b9d | [
"MIT"
] | 1 | 2018-06-20T23:34:39.000Z | 2018-06-20T23:34:39.000Z | ---
layout: post
title: The lab grows
subtitle: Welcome Yiwen and Hancong!
#bigimg: /img/path.jpg
#tags: [Fall2018, newmembers]
date: 2018-08-28 09:45
---
As the school year starts we are delighted to welcome two new members to the lab. Yiwen Wang who is coming to us from Georgetown University where she got a MS in Biostatistics. She will be pursuing a PhD in Epidemiology in [The College of Public Health](https://cph.osu.edu/epi). Hancong Tang, who recently transferred into the Division of Pharmaceutics and Pharmaceutical Chemistry in the College of Pharmacy, will be pursuing her dissertation research in conjunction with collaborators in the Department of Statistics at Ohio State. Welcome, we are thrilled you are here!
| 66.545455 | 575 | 0.786885 | eng_Latn | 0.997758 |
d5d78f7c2724670dd3850ef84eb758f346b46a82 | 6,646 | md | Markdown | WindowsServerDocs/virtualization/hyper-v/learn-more/Generation-2-virtual-machine-security-settings-for-Hyper-V.md | McSpooder/windowsserverdocs | dac52260fdcc3721daf7e32cd45760a0ced96de7 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-11-04T09:57:10.000Z | 2020-11-04T09:57:10.000Z | WindowsServerDocs/virtualization/hyper-v/learn-more/Generation-2-virtual-machine-security-settings-for-Hyper-V.md | McSpooder/windowsserverdocs | dac52260fdcc3721daf7e32cd45760a0ced96de7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | WindowsServerDocs/virtualization/hyper-v/learn-more/Generation-2-virtual-machine-security-settings-for-Hyper-V.md | McSpooder/windowsserverdocs | dac52260fdcc3721daf7e32cd45760a0ced96de7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Generation 2 virtual machine security settings for Hyper-V
description: Describes the security settings available in Hyper-V Manager for generation 2 virtual machines
ms.topic: article
ms.assetid: 06ab4f5f-6b8e-4058-8108-76785aa93d4c
ms.author: benarm
author: BenjaminArmstrong
ms.date: 10/04/2016
---
# Generation 2 virtual machine security settings for Hyper-V
>Applies To: Windows Server 2016, Microsoft Hyper-V Server 2016, Windows Server 2019, Microsoft Hyper-V Server 2019
Use the virtual machine security settings in Hyper-V Manager to help protect the data and state of a virtual machine. You can protect virtual machines from inspection, theft, and tampering from both malware that may run on the host, and datacenter administrators. The level of security you get depends on the host hardware you run, the virtual machine generation, and whether you set up the service, called the Host Guardian Service, that authorizes hosts to start shielded virtual machines.
The Host Guardian Service is a new role in Windows Server 2016. It identifies legitimate Hyper-V hosts and allows them to run a given virtual machine. You'd most commonly set up the Host Guardian Service for a datacenter. But you can create a shielded virtual machine to run it locally without setting up a Host Guardian Service. You can later distribute the shielded virtual machine to a Host Guardian Fabric.
If you haven't set up the Host Guardian Service or are running it in local mode on the Hyper-V host and the host has the virtual machine owner's guardian key, you can change the settings described in this topic. An owner of a guardian key is an organization that creates and shares a private or public key to own all virtual machines created with that key.
To learn how you can make your virtual machines more secure with the Host Guardian Service, see the following resources.
- [Harden the Fabric: Protecting Tenant Secrets in Hyper-V (Ignite video)](https://go.microsoft.com/fwlink/?LinkId=746379)
- [Guarded Fabric and Shielded VMs](https://go.microsoft.com/fwlink/?LinkId=746381)
## Secure Boot setting in Hyper-V Manager
Secure Boot is a feature available with generation 2 virtual machines that helps prevent unauthorized firmware, operating systems, or Unified Extensible Firmware Interface (UEFI) drivers (also known as option ROMs) from running at boot time. Secure Boot is enabled by default. You can use secure boot with generation 2 virtual machines that run Windows or Linux distribution operating systems.
The templates described in the following table refer to the certificates that you need to verify the integrity of the boot process.
|Template name|Description|
|-----------------|---------------|
|Microsoft Windows|Select to secure boot the virtual machine for a Windows operating system.|
|Microsoft UEFI Certificate Authority|Select to secure boot the virtual machine for a Linux distribution operating system.|
|Open Source Shielded VM|This template is leveraged to secure boot for [Linux-based shielded VMs](../../../security/guarded-fabric-shielded-vm/guarded-fabric-create-a-linux-shielded-vm-template.md).|
For more information, see the following topics.
- [Windows 10 Security Overview](/windows/security/threat-protection/overview-of-threat-mitigations-in-windows-10)
- [Should I create a generation 1 or 2 virtual machine in Hyper-V?](../plan/Should-I-create-a-generation-1-or-2-virtual-machine-in-Hyper-V.md)
- [Linux and FreeBSD Virtual Machines on Hyper-V](../Supported-Linux-and-FreeBSD-virtual-machines-for-Hyper-V-on-Windows.md)
## Encryption support settings in Hyper-V Manager
You can help protect the data and state of the virtual machine by selecting the following encryption support options.
- **Enable Trusted Platform Module** - This setting makes a virtualized Trusted Platform Module (TPM) chip available to your virtual machine. This allows the guest to encrypt the virtual machine disk by using BitLocker.
- If your Hyper-V host is running Windows 10 1511, you have to enable Isolated User Mode.
- **Encrypt State and VM migration traffic** - Encrypts the virtual machine saved state and live migration traffic.
### Enable Isolated User Mode
If you select **Enable Trusted Platform Module** on Hyper-V hosts that run versions of Windows earlier than Windows 10 Anniversary Update, you must enable Isolated User Mode. You don't need to do this for Hyper-V hosts that run Windows Server 2016 or Windows 10 Anniversary Update or later.
Isolated User Mode is the runtime environment that hosts security applications inside Virtual Secure Mode on the Hyper-V host. Virtual Secure Mode is used to secure and protect the state of the virtual TPM chip.
To enable Isolated User Mode on the Hyper-V host that run earlier versions of Windows 10,
1. Open Windows PowerShell as an administrator.
2. Run the following commands:
```
Enable-WindowsOptionalFeature -Feature IsolatedUserMode -Online
New-Item -Path HKLM:\SYSTEM\CurrentControlSet\Control\DeviceGuard -Force
New-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Control\DeviceGuard -Name EnableVirtualizationBasedSecurity -Value 1 -PropertyType DWord -Force
```
You can migrate a virtual machine with virtual TPM enabled to any host that runs Windows Server 2016, Windows 10 build 10586 or higher versions. But if you migrate it to another host, you may not be able to start it. You must update the Key Protector for that virtual machine to authorize the new host to run the virtual machine. For more information, see [Guarded Fabric and Shielded VMs](https://go.microsoft.com/fwlink/?LinkId=746381) and [System requirements for Hyper-V on Windows Server](../System-requirements-for-Hyper-V-on-Windows.md).
## Security Policy in Hyper-V Manager
For more virtual machine security, use the **Enable Shielding** option to disable management features like console connection, PowerShell Direct, and some integration components. If you select this option, **Secure Boot**, **Enable Trusted Platform Module**, and **Encrypt State and VM migration traffic** options are selected and enforced.
You can run the shielded virtual machine locally without setting up a Host Guardian Service. But if you migrate it to another host, you may not be able to start it. You must update the Key Protector for that virtual machine to authorize the new host to run the virtual machine. For more information, see [Guarded Fabric and Shielded VMs](https://go.microsoft.com/fwlink/?LinkId=746381).
For more information about security in Windows Server, see [Security and Assurance](../../../security/Security-and-Assurance.yml). | 86.311688 | 544 | 0.791604 | eng_Latn | 0.985926 |
d5d7bac042a73f3eef86397888f0c8ee13ebedee | 424 | md | Markdown | README.md | chao0716/learn_dig_grasp_site | d4d4c43c1bb1f41ebfe01eb1f8f56aeddd62f8f5 | [
"Apache-2.0"
] | null | null | null | README.md | chao0716/learn_dig_grasp_site | d4d4c43c1bb1f41ebfe01eb1f8f56aeddd62f8f5 | [
"Apache-2.0"
] | null | null | null | README.md | chao0716/learn_dig_grasp_site | d4d4c43c1bb1f41ebfe01eb1f8f56aeddd62f8f5 | [
"Apache-2.0"
] | 2 | 2021-09-01T08:57:42.000Z | 2021-09-01T08:59:05.000Z | ## Learning to Grasp by Digging: Data-Driven Dig-Grasping for BinPicking from Clutter
**Abstract**. Robotic manipulation can
___
### Video
todo
### Paper
You can view the supplemental material [here] (link soon).
### Code and Extras
You can find additional resources on [Github]. (Coming Soon) Includes:
- The Benchmark
- Paper code (architectures, losses, dataloaders, etc.)
- Model weights
| 18.434783 | 95 | 0.695755 | eng_Latn | 0.924332 |
d5d8873767e71e781977739de1b1204b98409901 | 12,797 | md | Markdown | wdk-ddi-src/content/d3dkmddi/ne-d3dkmddi-_dxgk_queryadapterinfotype.md | hsebs/windows-driver-docs-ddi | d655ca4b723edeff140ca2d9cc1bfafd72fcda97 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | wdk-ddi-src/content/d3dkmddi/ne-d3dkmddi-_dxgk_queryadapterinfotype.md | hsebs/windows-driver-docs-ddi | d655ca4b723edeff140ca2d9cc1bfafd72fcda97 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | wdk-ddi-src/content/d3dkmddi/ne-d3dkmddi-_dxgk_queryadapterinfotype.md | hsebs/windows-driver-docs-ddi | d655ca4b723edeff140ca2d9cc1bfafd72fcda97 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-04-22T21:40:43.000Z | 2021-04-22T21:40:43.000Z | ---
UID: NE:d3dkmddi._DXGK_QUERYADAPTERINFOTYPE
title: _DXGK_QUERYADAPTERINFOTYPE (d3dkmddi.h)
description: The DXGK_QUERYADAPTERINFOTYPE enumeration indicates the type of information to retrieve.
old-location: display\dxgk_queryadapterinfotype.htm
ms.assetid: 5cceffb1-853c-4635-b855-d0e3f107c23d
ms.date: 04/16/2018
ms.keywords: DXGKQAITYPE_ALLOCATIONGROUP, DXGKQAITYPE_DISPLAY_DRIVERCAPS_EXTENSION, DXGKQAITYPE_DRIVERCAPS, DXGKQAITYPE_GPUMMUCAPS, DXGKQAITYPE_HISTORYBUFFERPRECISION, DXGKQAITYPE_INTEGRATED_DISPLAY_DESCRIPTOR, DXGKQAITYPE_NUMPOWERCOMPONENTS, DXGKQAITYPE_PAGETABLELEVELDESC, DXGKQAITYPE_PHYSICALADAPTERCAPS, DXGKQAITYPE_POWERCOMPONENTINFO, DXGKQAITYPE_POWERCOMPONENTPSTATEINFO, DXGKQAITYPE_PREFERREDGPUNODE, DXGKQAITYPE_QUERYCOLORIMETRYOVERRIDES, DXGKQAITYPE_QUERYSEGMENT, DXGKQAITYPE_QUERYSEGMENT2, DXGKQAITYPE_QUERYSEGMENT3, DXGKQAITYPE_QUERYSEGMENT4, DXGKQAITYPE_SEGMENTMEMORYSTATE, DXGKQAITYPE_UEFIFRAMEBUFFERRANGES, DXGKQAITYPE_UMDRIVERPRIVATE, DXGK_QUERYADAPTERINFOTYPE, DXGK_QUERYADAPTERINFOTYPE enumeration [Display Devices], DmEnums_c4637ac2-b8e0-4c30-a709-5a8ff1ee3fdc.xml, _DXGK_QUERYADAPTERINFOTYPE, d3dkmddi/DXGKQAITYPE_ALLOCATIONGROUP, d3dkmddi/DXGKQAITYPE_DISPLAY_DRIVERCAPS_EXTENSION, d3dkmddi/DXGKQAITYPE_DRIVERCAPS, d3dkmddi/DXGKQAITYPE_GPUMMUCAPS, d3dkmddi/DXGKQAITYPE_HISTORYBUFFERPRECISION, d3dkmddi/DXGKQAITYPE_INTEGRATED_DISPLAY_DESCRIPTOR, d3dkmddi/DXGKQAITYPE_NUMPOWERCOMPONENTS, d3dkmddi/DXGKQAITYPE_PAGETABLELEVELDESC, d3dkmddi/DXGKQAITYPE_PHYSICALADAPTERCAPS, d3dkmddi/DXGKQAITYPE_POWERCOMPONENTINFO, d3dkmddi/DXGKQAITYPE_POWERCOMPONENTPSTATEINFO, d3dkmddi/DXGKQAITYPE_PREFERREDGPUNODE, d3dkmddi/DXGKQAITYPE_QUERYCOLORIMETRYOVERRIDES, d3dkmddi/DXGKQAITYPE_QUERYSEGMENT, d3dkmddi/DXGKQAITYPE_QUERYSEGMENT2, d3dkmddi/DXGKQAITYPE_QUERYSEGMENT3, d3dkmddi/DXGKQAITYPE_QUERYSEGMENT4, d3dkmddi/DXGKQAITYPE_SEGMENTMEMORYSTATE, d3dkmddi/DXGKQAITYPE_UEFIFRAMEBUFFERRANGES, d3dkmddi/DXGKQAITYPE_UMDRIVERPRIVATE, d3dkmddi/DXGK_QUERYADAPTERINFOTYPE, display.dxgk_queryadapterinfotype
f1_keywords:
- "d3dkmddi/ DXGK_QUERYADAPTERINFOTYPE"
req.header: d3dkmddi.h
req.include-header: D3dkmddi.h
req.target-type: Windows
req.target-min-winverclnt: Available starting with Windows Vista.
req.target-min-winversvr:
req.kmdf-ver:
req.umdf-ver:
req.ddi-compliance:
req.unicode-ansi:
req.idl:
req.max-support:
req.namespace:
req.assembly:
req.type-library:
req.lib:
req.dll:
req.irql: PASSIVE_LEVEL
topic_type:
- APIRef
- kbSyntax
api_type:
- HeaderDef
api_location:
- d3dkmddi.h
api_name:
- DXGK_QUERYADAPTERINFOTYPE
product:
- Windows
targetos: Windows
tech.root: display
req.typenames: DXGK_QUERYADAPTERINFOTYPE
dev_langs:
- c++
ms.custom: 19H1
---
# _DXGK_QUERYADAPTERINFOTYPE enumeration
## -description
The DXGK_QUERYADAPTERINFOTYPE enumeration indicates the type of information to retrieve.
## -syntax
```cpp
typedef enum _DXGK_QUERYADAPTERINFOTYPE {
DXGKQAITYPE_UMDRIVERPRIVATE = 0,
DXGKQAITYPE_DRIVERCAPS = 1,
DXGKQAITYPE_QUERYSEGMENT = 2,
#if (DXGKDDI_INTERFACE_VERSION >= DXGKDDI_INTERFACE_VERSION_WIN7)
DXGKQAITYPE_ALLOCATIONGROUP = 3,
DXGKQAITYPE_QUERYSEGMENT2 = 4,
#endif
#if (DXGKDDI_INTERFACE_VERSION >= DXGKDDI_INTERFACE_VERSION_WIN8)
DXGKQAITYPE_QUERYSEGMENT3 = 5,
DXGKQAITYPE_NUMPOWERCOMPONENTS = 6,
DXGKQAITYPE_POWERCOMPONENTINFO = 7,
DXGKQAITYPE_PREFERREDGPUNODE = 8,
#endif
#if (DXGKDDI_INTERFACE_VERSION >= DXGKDDI_INTERFACE_VERSION_WDDM1_3)
DXGKQAITYPE_POWERCOMPONENTPSTATEINFO = 9,
DXGKQAITYPE_HISTORYBUFFERPRECISION = 10,
#endif
#if (DXGKDDI_INTERFACE_VERSION >= DXGKDDI_INTERFACE_VERSION_WDDM2_0)
DXGKQAITYPE_QUERYSEGMENT4 = 11,
DXGKQAITYPE_SEGMENTMEMORYSTATE = 12,
DXGKQAITYPE_GPUMMUCAPS = 13,
DXGKQAITYPE_PAGETABLELEVELDESC = 14,
DXGKQAITYPE_PHYSICALADAPTERCAPS = 15,
DXGKQAITYPE_DISPLAY_DRIVERCAPS_EXTENSION = 16,
#endif
#if (DXGKDDI_INTERFACE_VERSION >= DXGKDDI_INTERFACE_VERSION_WDDM2_2)
DXGKQAITYPE_INTEGRATED_DISPLAY_DESCRIPTOR = 17,
DXGKQAITYPE_UEFIFRAMEBUFFERRANGES = 18,
DXGKQAITYPE_QUERYCOLORIMETRYOVERRIDES = 19
} DXGK_QUERYADAPTERINFOTYPE;
```
## -enum-fields
### -field DXGKQAITYPE_UMDRIVERPRIVATE
Indicates private data for the user-mode display driver.
### -field DXGKQAITYPE_DRIVERCAPS
Indicates the driver capabilities in a [DXGK_DRIVERCAPS](ns-d3dkmddi-_dxgk_drivercaps.md) structure.
### -field DXGKQAITYPE_QUERYSEGMENT
Indicates memory-segment information in a [DXGK_QUERYSEGMENTOUT](ns-d3dkmddi-_dxgk_querysegmentout.md) structure.
### -field DXGKQAITYPE_RESERVED
Reserved for system use. Do not use in your driver. Note that this constant occurs starting with Windows 7.
### -field DXGKQAITYPE_QUERYSEGMENT2
Reserved for system use. Do not use in your driver.
Note that this constant occurs starting with Windows 7.
### -field DXGKQAITYPE_QUERYSEGMENT3
Indicates memory-segment information in a [DXGK_QUERYSEGMENTOUT3](ns-d3dkmddi-_dxgk_querysegmentout3.md) structure.
Supported starting with Windows 8.
### -field DXGKQAITYPE_NUMPOWERCOMPONENTS
Indicates the number of power components used by the display miniport driver. For more information, see Remarks.
Supported starting with Windows 8.
### -field DXGKQAITYPE_POWERCOMPONENTINFO
Indicates information about power components used by the display miniport driver. For more information, see Remarks.
Supported starting with Windows 8.
### -field DXGKQAITYPE_PREFERREDGPUNODE
Reserved for system use. Do not use in your driver.
Supported starting with Windows 8.
### -field DXGKQAITYPE_POWERCOMPONENTPSTATEINFO
Reserved for system use. Do not use in your driver.
Supported starting with Windows 8.1.
### -field DXGKQAITYPE_HISTORYBUFFERPRECISION
Indicates info about the precision of history buffer data used by the display miniport driver. For more information, see Remarks.
Supported starting with Windows 8.1.
### -field DXGKQAITYPE_QUERYSEGMENT4
Indicates memory-segment information in a [DXGK_QUERYSEGMENTOUT4](ns-d3dkmddi-_dxgk_querysegmentout4.md) structure.
Supported starting with Windows 10.
### -field DXGKQAITYPE_SEGMENTMEMORYSTATE
Indicates bad memory ranges in a [DXGK_MEMORYRANGE](ns-d3dkmddi-_dxgk_memoryrange.md) structure.
Supported starting with Windows 10.
### -field DXGKQAITYPE_GPUMMUCAPS
Indicates physical adapter GPU capabilities.
Supported starting with Windows 10.
### -field DXGKQAITYPE_PAGETABLELEVELDESC
Reserved for system use. Do not use in your driver.
### -field DXGKQAITYPE_PHYSICALADAPTERCAPS
Reserved for system use. Do not use in your driver.
### -field DXGKQAITYPE_DISPLAY_DRIVERCAPS_EXTENSION
Reserved for system use. Do not use in your driver.
### -field DXGKQAITYPE_INTEGRATED_DISPLAY_DESCRIPTOR
Indicates a request for an integrated panel descriptor where the input buffer to the query will be a DXGK_QUERYINTEGRATEDDISPLAYIN structure and the output buffer is a DXGK_QUERYINTEGRATEDDISPLAYOUT structure.
Although this function addresses a target, only DxgKrnl adapter locks are taken over this call, not child device locks. In practice, since this call will be made before the child device is exposed, there should be no concurrent DDI calls which address the same target.
> [!NOTE]
> Unlike most QueryAdapterInfo calls, the output buffer size is variable although it is still known in advance from the DescriptorLength field of the DXGK_INTEGRATED_DISPLAY_CHILD structure for the target id. The size of the output buffer is:
DescriptorLength + FIELD_OFFSET( DXGK_QUERYINTEGRATEDDISPLAYOUT, Descriptor )
### -field DXGKQAITYPE_UEFIFRAMEBUFFERRANGES
Indicates request for the UEFI frame buffer ranges.
### -field DXGKQAITYPE_QUERYCOLORIMETRYOVERRIDES
Indicates a request for colorimetry overrides for an external display where the input buffer to the query will be a DXGK_QUERYCOLORIMETRYOVERRIDESIN structure, containing only the target id being addressed and the output buffer is a DXGK_COLORIMETRY structure into which the driver writes overrides for the monitor attached to the target.
Although this function addresses a target, only DxgKrnl adapter locks are taken over this call, not child device locks. Since this call will be made before the child device is exposed, there should be no concurrent DDI calls which address the same target.
The output buffer is zeroed when passed to the driver. If the driver has no overrides for the monitor, it should return STATUS_SUCCESS and leave the output buffer zeroed. If the driver has overrides, it fill in all fields of the DXGK_COLORIMETRY to describe the monitor capabilities as the OS will not accept partial overrides.
### -field DXGKQAITYPE_DISPLAYID_DESCRIPTOR
Indicates a request for an integrated panel descriptor where the input buffer to the query will be a DXGK_QAITARGETIN structure and the output buffer is a DXGK_QUERYINTEGRATEDDISPLAYOUT structure.
### -field DXGKQAITYPE_FRAMEBUFFERSAVESIZE
The size of the frame buffer to save to system memory during power transitions.
### -field DXGKQAITYPE_HARDWARERESERVEDRANGES
Reserved ranges.
### -field DXGKQAITYPE_INTEGRATED_DISPLAY_DESCRIPTOR2
Indicates a request for an integrated panel descriptor where the input buffer to the query will be a DXGK_QAITARGETIN structure and the output buffer is a [DXGK_QUERYINTEGRATEDDISPLAYOUT2](ns-d3dkmddi-_dxgk_queryintegrateddisplayout2.md) structure. This query replaces use of the DXGKQAITYPE_INTEGRATED_DISPLAY_DESCRIPTOR query for WDDM 2.4 drivers.
TypeIntegratedDisplay child devices are reported by calling [DXGKDDI_QUERYADAPTERINFO](nc-d3dkmddi-dxgkddi_queryadapterinfo.md) with the *Type* set to this value.
### -field DXGKQAITYPE_NODEPERFDATA
Represents performance data collected per engine from an adapter on an interval basis.
### -field DXGKQAITYPE_ADAPTERPERFDATA
Represents performance data collected per adapter on an interval basis.
### -field DXGKQAITYPE_ADAPTERPERFDATA_CAPS
Represents data caps that are static and queried once per GPU during initialization.
### -field DXGKQAITYPE_GPUVERSION
Used to collect the bios version and GPU architecture name once during GPU initialization.
### -field DXGKQAITYPE_DEVICE_TYPE_CAPS
The device type capabilities.
### -field DXGKQAITYPE_WDDMDEVICECAPS
The device capabilities that are queried by the OS during device initialization.
### -field DXGKQAITYPE_GPUPCAPS
The GPU capabilities for a kernel mode display driver.
## -remarks
The display miniport driver must fill the buffer pointed to by the **pOutputData** member of the [DXGKARG_QUERYADAPTERINFO](ns-d3dkmddi-_dxgkarg_queryadapterinfo.md) structure as follows:
| DXGKARG_QUERYADAPTERINFO.Type Value| Contents of output buffer pointed to by DXGKARG_QUERYADAPTERINFO.pOutputData |
|--|--|
| DXGKQAITYPE_UMDRIVERPRIVATE | Proprietary buffer |
| DXGKQAITYPE_DRIVERCAPS | Populated [DXGK_DRIVERCAPS](ns-d3dkmddi-_dxgk_drivercaps.md) structure |
| DXGKQAITYPE_QUERYSEGMENT | Populated [DXGK_QUERYSEGMENTOUT](ns-d3dkmddi-_dxgk_querysegmentout.md) structure |
| DXGKQAITYPE_QUERYSEGMENT3 | Populated [DXGK_QUERYSEGMENTOUT3](ns-d3dkmddi-_dxgk_querysegmentout3.md) structure |
| DXGKQAITYPE_NUMPOWERCOMPONENTS | A UINT value that specifies the number of power components used by the display miniport driver |
| DXGKQAITYPE_POWERCOMPONENTINFO | Populated [DXGK_POWER_RUNTIME_COMPONENT](ns-d3dkmddi-_dxgk_power_runtime_component.md) structure that provides information about the nth power component, where n is the component index specified by [DXGKARG_QUERYADAPTERINFO](ns-d3dkmddi-_dxgkarg_queryadapterinfo.md).pInputData in a call to the [DxgkDdiQueryAdapterInfo](ns-d3dkmddi-_dxgkarg_queryadapterinfo.md) function |
| DXGKQAITYPE_HISTORYBUFFERPRECISION | Populated [DXGKARG_HISTORYBUFFERPRECISION](ns-d3dkmddi-_dxgkarg_historybufferprecision.md) structure |
## -see-also
[DXGK_DRIVERCAPS](ns-d3dkmddi-_dxgk_drivercaps.md)
[DXGK_POWER_RUNTIME_COMPONENT](ns-d3dkmddi-_dxgk_power_runtime_component.md)
[DXGK_QUERYSEGMENTOUT](ns-d3dkmddi-_dxgk_querysegmentout.md)
[DXGK_QUERYSEGMENTOUT3](ns-d3dkmddi-_dxgk_querysegmentout3.md)
[DXGKARG_HISTORYBUFFERPRECISION](ns-d3dkmddi-_dxgkarg_historybufferprecision.md)
[DXGKARG_QUERYADAPTERINFO](ns-d3dkmddi-_dxgkarg_queryadapterinfo.md)
[DxgkDdiQueryAdapterInfo](nc-d3dkmddi-dxgkddi_queryadapterinfo.md)
| 46.198556 | 1,699 | 0.799484 | yue_Hant | 0.404482 |
d5d8bf592af92386541d9279b14fad032d0e4e18 | 4,833 | md | Markdown | docs/build/dlls-in-visual-cpp.md | a1043710306/cpp-docs.zh-cn | 9296fe0d678d41b279e57a9aacb68b67497bbc0c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/build/dlls-in-visual-cpp.md | a1043710306/cpp-docs.zh-cn | 9296fe0d678d41b279e57a9aacb68b67497bbc0c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/build/dlls-in-visual-cpp.md | a1043710306/cpp-docs.zh-cn | 9296fe0d678d41b279e57a9aacb68b67497bbc0c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 在 Visual Studio 中创建 C/C++ DLL
description: 概述在 Visual Studio 中使用 C++ 创建和使用 DLL 的原因和方法。
ms.date: 01/27/2020
helpviewer_keywords:
- executable files [C++]
- dynamic linking [C++]
- linking [C++], dynamic vs. static
- DLLs [C++]
- DLLs [C++], about DLLs
ms.assetid: 5216bca4-51e2-466b-b221-0e3e776056f0
ms.openlocfilehash: 7083924f137fa9283da40404c7d15183e59c0b1c
ms.sourcegitcommit: 7ecd91d8ce18088a956917cdaf3a3565bd128510
ms.translationtype: HT
ms.contentlocale: zh-CN
ms.lasthandoff: 03/16/2020
ms.locfileid: "79422828"
---
# <a name="create-cc-dlls-in-visual-studio"></a>在 Visual Studio 中创建 C/C++ DLL
在 Windows 中，动态链接库 (DLL) 是作为函数和资源的共享库的一种可执行文件。 动态链接是操作系统功能。 它可使执行文件调用函数或使用存储在单独文件中的资源。 可从使用这些函数和资源的可执行文件中对其分别进行编译和部署。
DLL 不是独立的可执行文件。 DLL 在调用它们的应用程序的上下文中运行。 操作系统将 DLL 加载到应用程序的内存空间中。 此操作要么在加载应用程序时（隐式链接）完成，要么在运行时按需（显式链接）完成 。 DLL 还可以在可执行文件之间轻松共享函数和资源。 多个应用程序可同时访问内存中单个 DLL 副本的内容。
## <a name="differences-between-dynamic-linking-and-static-linking"></a>动态链接和静态链接之间的差异
静态链接将静态库中的所有对象代码复制到生成时使用它的可执行文件中。 动态链接仅包括 Windows 在运行时用于查找和加载含有数据项或函数的 DLL 所需的信息。 创建 DLL 时，还将创建包含此信息的导入库。 生成调用 DLL 的可执行文件时，链接器会使用导入库中的导出符号来为 Windows 加载程序存储此信息。 当加载程序加载 DLL 时，该 DLL 会映射到你的应用程序的内存空间中。 如果存在，则调用 DLL 中的特殊函数 `DllMain`，以执行 DLL 所需的任何初始化。
<a name="differences-between-applications-and-dlls"></a>
## <a name="differences-between-applications-and-dlls"></a>应用程序和 DLL 之间的区别
尽管 DLL 和应用程序都是可执行文件模块，但它们之间也存在很多不同之处。 对用户来说，最明显的区别在于不能直接运行 DLL。 从系统的角度来看，应用程序和 Dll 之间有两个基本差异：
- 一是应用程序可以在系统中同时运行其自身的多个实例。 而 DLL 只能有一个实例。
- 二是应用程序可以作为进程进行加载。 它可以管理诸如堆栈、执行线程、全局内存、文件句柄和消息队列之类的资源。 而 DLL 不能管理这些资源。
<a name="advantages-of-using-dlls"></a>
## <a name="advantages-of-using-dlls"></a>使用 DLL 的优点
与静态链接相比，动态链接到代码和资源有几个优点：
- 动态链接可节省内存，减少交换。 许多进程可以同时使用 DLL，并在内存中共享 DLL 只读部分的单个副本。 相反，使用静态链接库构建的每个应用程序都有一个完整的库代码副本，Windows 必须将其加载到内存中。
- 动态链接节省了磁盘空间和带宽。 许多应用程序可以在磁盘上共享 DLL 的单个副本。 相反，使用静态链接库构建的每个应用程序都是将库代码链接到其可执行映像中。 这会占用更多磁盘空间，并需要更多带宽来传输。
- 维护、安全修复和升级会更容易。 当应用程序在 DLL 中使用公共函数时，你可以实现 bug 修复并将更新部署到 DLL。 更新 DLL 时，不需要重新编译或重新链接使用它们的应用程序。 一旦部署了新的 DLL，应用程序就可以使用这些新的 DLL。 相反，当你在静态链接的对象代码中进行修复时，必须重新链接并重新部署使用 DLL 的每个应用程序。
- 可以使用 DLL 提供售后支持。 例如，可以修改显示驱动程序 DLL 以支持应用程序发布时不可用的显示。
- 可以使用显式链接在运行时发现和加载 DLL。 例如，无需重新生成或重新部署就可将新功能添加到你的应用的应用程序扩展。
- 对于用不同编程语言编写的应用程序，使用动态链接可以更轻松地对其提供支持。 用不同编程语言编写的程序只要遵循函数调用约定，就可以调用相同的 DLL 函数。 程序和 DLL 函数必须在以下方面兼容：函数期望将其参数推送到堆栈上的顺序。 函数或应用程序是否负责清理堆栈。 以及，是否有参数在寄存器中传递。
- 动态链接提供了一种扩展 Microsoft 基础类库 (MFC) 类的机制。 可以从现有的 MFC 类派生类，并将它们放在 MFC 扩展 DLL 中供 MFC 应用程序使用。
- 动态链接使创建应用程序的国际版本更容易。 DLL 是一种提供特定于区域设置的资源的便捷方式，使用这种方式创建应用程序的国际版本会更加容易。 你可以将每种语言的字符串和映像放在一个单独的资源 DLL 中，而不是发布应用程序的许多本地化版本。 然后应用程序可以在运行时加载该区域设置的适当资源。
使用 DLL 的潜在缺点是，应用程序不是自包含的。 它依赖于一个独立的 DLL 模块的存在：在安装过程中必须亲自部署或验证的模块。
## <a name="more-information-on-how-to-create-and-use-dlls"></a>关于如何创建和使用 DLL 的详细信息
以下文章提供了有关如何在 Visual Studio 中创建 C/C++ DLL 的详细信息。
[演练：创建和使用动态链接库 (C++)](walkthrough-creating-and-using-a-dynamic-link-library-cpp.md)\
介绍如何使用 Visual Studio 创建和使用 DLL。
[DLL 类型](kinds-of-dlls.md)\
提供有关可生成的不同类型的 DLL 的信息。
[DLL 常见问题](dll-frequently-asked-questions.md)\
提供有关 DLL 的常见问题解答。
[将可执行文件链接到 DLL](linking-an-executable-to-a-dll.md)\
描述与 DLL 的显式链接和隐式链接。
[初始化 DLL](run-time-library-behavior.md#initializing-a-dll)\
介绍加载 DLL 时必须执行的 DLL 初始化代码。
[DLL 和 Visual C++ 运行时库行为](run-time-library-behavior.md)\
描述运行库 DLL 启动序列。
[LoadLibrary 和 AfxLoadLibrary](loadlibrary-and-afxloadlibrary.md)\
介绍如何在运行时使用 `LoadLibrary` 和 `AfxLoadLibrary` 显式链接到 DLL。
[GetProcAddress](getprocaddress.md)\
介绍如何使用 `GetProcAddress` 获取 DLL 中导出函数的地址。
[FreeLibrary 和 AfxFreeLibrary](freelibrary-and-afxfreelibrary.md)\
介绍当不再需要 DLL 模块时如何使用 `FreeLibrary` 和 `AfxFreeLibrary`。
[动态链接库搜索顺序](/windows/win32/Dlls/dynamic-link-library-search-order)\
描述 Windows 操作系统用来定位系统上的 DLL 的搜索路径。
[动态链接到 MFC 的规则 MFC DLL 的模块状态](module-states-of-a-regular-dll-dynamically-linked-to-mfc.md)\
描述动态链接到 MFC 的规则 MFC DLL 的模块状态。
[MFC 扩展 DLL](extension-dlls-overview.md)\
解释通常实现从现有 MFC 类派生的可重用类的 DLL。
[创建纯资源 DLL](creating-a-resource-only-dll.md)\
讨论只包含资源（如图标、位图、字符串和对话框等）的纯资源 DLL。
[MFC 应用程序中已本地化的资源：附属 DLL](localized-resources-in-mfc-applications-satellite-dlls.md)\
提供对附属 DLL 的增强支持，该功能有助于创建针对多种语言进行本地化的应用程序。
[导入和导出](importing-and-exporting.md)\
描述如何将公共符号导入应用程序或从 DLL 导出函数。
[Active 技术和 DLL](active-technology-and-dlls.md)\
使对象服务器得以在 DLL 内实现。
[DLL 中的自动化](automation-in-a-dll.md)\
描述“MFC DLL 向导”中的“自动化”选项提供的内容。
[MFC DLL 命名约定](../mfc/mfc-library-versions.md#mfc-static-library-naming-conventions)\
讨论 MFC 中包含的 DLL 和库如何遵循结构化命名约定。
[从 Visual Basic 应用程序调用 DLL 函数](calling-dll-functions-from-visual-basic-applications.md)\
描述如何从 Visual Basic 应用程序中调用 DLL 函数。
## <a name="related-sections"></a>相关章节
[将 MFC 用作 DLL 的一部分](../mfc/tn011-using-mfc-as-part-of-a-dll.md)\
描述使你可以将 MFC 库作为 Windows 动态链接库的一部分来使用的规则 MFC DLL。
[MFC 的 DLL 版本](../mfc/tn033-dll-version-of-mfc.md)\
描述如何将 MFCxx.dll 和 MFCxxD.dll（其中 x 是 MFC 版本号）共享动态链接库用于 MFC 应用程序和 MFC 扩展 DLL。
| 36.89313 | 245 | 0.786675 | yue_Hant | 0.925858 |
d5d92948c623906757df7e902a5763b8f9e506c5 | 1,447 | md | Markdown | README.md | jalispran/react-day-picker | ecd49ae5c92ba94c0519a6a00037730952b67c77 | [
"MIT"
] | 1 | 2020-12-01T16:43:54.000Z | 2020-12-01T16:43:54.000Z | README.md | jalispran/react-day-picker | ecd49ae5c92ba94c0519a6a00037730952b67c77 | [
"MIT"
] | null | null | null | README.md | jalispran/react-day-picker | ecd49ae5c92ba94c0519a6a00037730952b67c77 | [
"MIT"
] | 1 | 2022-01-07T13:48:29.000Z | 2022-01-07T13:48:29.000Z | # react-day-picker
Lightweight date picker component for [React.js](http://reactjs.org).
<a href="https://www.npmjs.com/package/react-day-picker">
<img src="https://img.shields.io/npm/v/react-day-picker.svg?style=flat-square" alt="npm version">
</a>
<a href="http://npm-stat.com/charts.html?package=react-day-picker">
<img src="https://img.shields.io/npm/dm/react-day-picker.svg?style=flat-square" alt="npm downloads">
</a>
## Get started
```bash
npm install react-day-picker
```
```jsx
import DayPicker from "react-day-picker";
import "react-day-picker/lib/style.css";
export default function Hello() {
return <DayPicker />;
}
```
### Documentation
- [Website](http://react-day-picker.js.org)
- [Examples](http://react-day-picker.js.org/examples/basic)
- [API](http://react-day-picker.js.org/api/DayPicker)
- [Changelog](http://react-day-picker.js.org/changelog)
- In stuck? [Get support](http://react-day-picker.js.org/support)
### v8 is coming!
The next version will be a rewrite in TypeScript. Read more [here](https://github.com/gpbl/react-day-picker/issues/942) or follow the [project status](https://github.com/gpbl/react-day-picker/projects/7).
- [master branch](https://github.com/gpbl/react-day-picker/tree/master) is for the upcoming v8 release.
- [v7 branch](https://github.com/gpbl/react-day-picker/tree/v7) to send PR for the v7 version.
See [packages/react-day-picker](packages/react-day-picker) for more details.
| 33.651163 | 204 | 0.722184 | yue_Hant | 0.372514 |
d5d97b520602bf01c2ce79863edcb230c8c22c3f | 24 | md | Markdown | README.md | vikasdwivedi/az204demo | 631b99fc8bd297a13e12b5c1d41a8a0d72adb176 | [
"MIT"
] | null | null | null | README.md | vikasdwivedi/az204demo | 631b99fc8bd297a13e12b5c1d41a8a0d72adb176 | [
"MIT"
] | null | null | null | README.md | vikasdwivedi/az204demo | 631b99fc8bd297a13e12b5c1d41a8a0d72adb176 | [
"MIT"
] | null | null | null | # az204demo
az 204 demo
| 8 | 11 | 0.75 | epo_Latn | 0.726177 |
d5d995ec5760afe2e7bf6e15792a04808d9ce1e7 | 4,184 | md | Markdown | _posts/2011-01-16-cmmi.md | javiergamarra/nhpatt.github.io | b0bd69bbc425e2cd39f5b58b7f8d206511a2f8ae | [
"MIT"
] | 1 | 2016-05-09T09:34:35.000Z | 2016-05-09T09:34:35.000Z | _posts/2011-01-16-cmmi.md | javiergamarra/nhpatt.github.io | b0bd69bbc425e2cd39f5b58b7f8d206511a2f8ae | [
"MIT"
] | 2 | 2017-07-05T06:28:18.000Z | 2021-09-27T21:56:40.000Z | _posts/2011-01-16-cmmi.md | javiergamarra/nhpatt.github.io | b0bd69bbc425e2cd39f5b58b7f8d206511a2f8ae | [
"MIT"
] | null | null | null | ---
id: 78
title: CMMI
date: 2011-01-16T01:25:30+00:00
author: nhpatt
layout: post
guid: http://nhpatt.com/cmmi
permalink: /cmmi/
jabber_published:
- 1295137533
categories:
- CMMI
- documentación
---
Esta semana, por motivos educativos, he preparado una pequeña charla introductoria sobre CMMI.
Para algunos la simple mención de este término servirá para produciros sudores fríos, grupo al que pertenezco. De todas formas me ha resultado interesante aprender más sobre CMMI y, sobre todo, la segunda parte de la charla (CMMI y Agile) que comentaré en otro post. Para que mi búsqueda de información y la lectura de [CMMI: guidelines for process…](http://books.google.es/books?id=EUZsqueGeXoC&printsec=frontcover&dq=cmmi&hl=es&ei=0TEyTam4FI3o4Aa9w_HNCg&sa=X&oi=book_result&ct=result&resnum=1&ved=0CDAQ6AEwAA#v=onepage&q&f=false) no hayan sido en vano, pongo a disposición pública la presentación realizada en [Prezi](https://prezi.com/gpmt8pehkvle/cmmi/).
Las dos presentaciones tienen grandes defectos formales (demasiado texto, pocas imágenes) pero servían al fin al que estaban destinadas. Si podéis, os recomiendo que veáis la **presentación en [prezi](https://prezi.com/gpmt8pehkvle/cmmi/)** porque me parece una herramienta fabulosa (pese a que sea Flash), la única pega que le veo es que sólo puedes pasar de “diapositiva” con el control habilitado (un click en el espacio de presentación aumenta el zoom pero no pasa a la siguiente). Todas las transiciones son en realidad efectos de zoom realizados automáticamente. Prezi permite, además, exportar tu presentación a varios formatos.
Sobre el tema en sí, decir que tengo fobia a las cantidades de **documentación que normalmente se utilizan para aplicar CMMI** (cómo bien ha señalado [@jezis](https://twitter.com/jezis) no son requeridas, son sugeridas pero no obligatorias) pero las ventajas en grandes corporaciones son indiscutibles, los datos son de libre disposición. En el mundo de las PYME, con pocos ‘procesos’, en el que CMMI se ve cómo un requisito para un contrato o una ventaja comparativa, las ventajas desaparecen. Todo esto teniendo en cuenta que las mejoras en productividad (de un 15%-60% en los mejores casos) **son mejoras de “herramientas”** (aludiendo a _Peopleware_ o a _Facts and Fallacies_…), las **mejoras producidas por tener y cuidar a las personas** adecuadas son **mucho más importantes**.
Me sorprenden varios datos, el primero que en España seamos el segundo país de Europa con **[mayor implantación de CMMI](http://www.javiergarzas.com/2009/04/cmmi-en-espana-marzo-2009.html)** (el resto buscan [SPICE](http://en.wikipedia.org/wiki/ISO/IEC_15504)). En empresas con mercado en EEUU es comprensible porque allí es un requisito imprescindible para muchos contratos importantes pero aún así es difícil de explicar el gusto nacional por CMMI. Otro dato, más evidente, es que las pequeñas compañías se quedan en el nivel 2-3 mientras que más del 70% de grandes multinacionales son CMMI 5, el coste de conseguir CMMI 5 es inalcanzable para empresas pequeñas.
Un hecho curioso es la **eliminación de los niveles de capacidad 4 y 5** en la versión 1.3 de CMMI que salió en Noviembre. La principal razón es por desuso, la mayor parte de compañías apuestan por los niveles de madurez que permiten **comparar más fácilmente entre empresas** (otra muestra más de que lo importante es el nivel en sí y no mejorar los procesos).
Si alguien está utilizando (o sufriendo) CMMI en su empresa, que comparta su visión :)
Los dos enlaces a las presentaciones son los siguientes (de momento sin CMMI y Agile):
* [Presentación en Prezi](https://prezi.com/gpmt8pehkvle/cmmi/)
* [Presentación en Google Docs](https://prezi.com/gpmt8pehkvle/cmmi/)
Podéis encontrar información sobre CMMI en el siguiente libro (la mayoría de libre disposición): [_CMMI_: _guidelines_ for process integration and product improvement](http://books.google.fr/books?id=EUZsqueGeXoC&printsec=frontcover&dq=CMMI+guidelines&hl=es&ei=zjkyTebXF-OH4gbxscnSCg&sa=X&oi=book_result&ct=result&redir_esc=y) y en [cmmi-dev](<http://www.sei.cmu.edu/library/assets/cmmi-dev-v12-spanish.pdf>)
| 113.081081 | 814 | 0.786568 | spa_Latn | 0.982811 |
d5da088c2ade38bd9bb70a3aad2635e174d4799a | 1,723 | md | Markdown | content/portfolio/Sentiment.md | VIMALRANJEEV/vimal_portfolio_2 | b1ba0503b8b74b48cc8d36ef627b83faf325eacf | [
"MIT"
] | null | null | null | content/portfolio/Sentiment.md | VIMALRANJEEV/vimal_portfolio_2 | b1ba0503b8b74b48cc8d36ef627b83faf325eacf | [
"MIT"
] | null | null | null | content/portfolio/Sentiment.md | VIMALRANJEEV/vimal_portfolio_2 | b1ba0503b8b74b48cc8d36ef627b83faf325eacf | [
"MIT"
] | null | null | null | ---
title: IMDB Movie Reviews
date: 2019-12-23T15:44:46.000+06:00
image: images/projects/IMDB.jpg
category:
- Sentiment analysis(NLP)
project_images:
- images/projects/Sentiment-1.png
- images/projects/sentiment-2.png
---
ABOUT THE DATASET
The Dataset of 50,000 movie reviews from IMDB, labelled by sentiment (positive/negative). Reviews have been preprocessed, and each review is encoded as a sequence of word indexes (integers). For convenience, the words are indexed by their frequency in the dataset, meaning the for that has index 1 is the most frequent word. Use the first 20 words from each review to speed up training, using a max vocab size of 10,000. As a convention, "0" does not stand for a specific word, but instead is used to encode any unknown word
ABOUT IMDB
IMDb (an acronym for Internet Movie Database) is an online database of information related to films, television programs, home videos, video games, and streaming content online – including cast, production crew and personal biographies, plot summaries, trivia, ratings, and fan and critical reviews. An additional fan feature, message boards, was abandoned in February 2017. Originally a fan-operated website, the database is now owned and operated by IMDb.com, Inc., a subsidiary of Amazon.
As of December 2020, IMDb has approximately 7.5 million titles (including episodes) and 10.4 million personalities in its database, as well as 83 million registered users.
\[[Code](https://github.com/VIMALRANJEEV/my_work/blob/master/Greatlearning/Sentiment%20analysis/Sequential_Models_in_NLP_assignment.ipynb)\]\[[PDF](https://github.com/VIMALRANJEEV/my_work/blob/master/Greatlearning/Sentiment%20analysis/Sequential_Models_in_NLP_assignment.pdf)\] | 78.318182 | 524 | 0.799768 | eng_Latn | 0.974714 |
d5da8cdf623c418068dd182a7a414fc52eb58fd6 | 2,246 | md | Markdown | coding/python/day01/README.md | dkapanidis/my-tutorials | f3b72c35487782609b556016aba03b275cc6b105 | [
"MIT"
] | null | null | null | coding/python/day01/README.md | dkapanidis/my-tutorials | f3b72c35487782609b556016aba03b275cc6b105 | [
"MIT"
] | null | null | null | coding/python/day01/README.md | dkapanidis/my-tutorials | f3b72c35487782609b556016aba03b275cc6b105 | [
"MIT"
] | null | null | null |
# Day 1 - Basic Intro
Posted [here](https://www.codingholygrail.com/learn-python-in-10-mins)
Learning the basics of python and how it works in less than 10 mins. Python is a great language for web development, data science and scripting.
## Hello World
Let's just print a simple hello world message:
```python
# hello.py
print('hello world')
```
Type `python hello.py` to execute.
## Primitive Types
Python has four primitive types: int, float, bool, str.
```python
# primitives.py
ten = 10 # int
pi = 3.14159265359 # float
yes = True # bool
no = False # bool
name = "John Wick" # str
print(ten, pi, yes, no, name, len(name))
```
```shellsession
$ python primitives.py
10 3.14159265359 True False John Wick 9
```
## Data Types
Apart from the primitive types python has the following data types:
- Sequence Types: list, tuple, range
- Mapping Types: dict
- Set Types: set, frozenset
```python
# dataTypes.py
fruitsList = ["apple", "banana", "cherry"]
fruitsTuple = ("apple", "banana", "cherry")
fruitsSet = {"apple", "banana", "cherry"}
fruitsFrozenSet = frozenset({"apple", "banana", "cherry"})
x = range(6)
print ("list", fruitsList)
print ("tuple", fruitsTuple)
print ("set", fruitsSet)
print ("frozenSet", fruitsFrozenSet)
print ("range", x)
```
## Operations
```python
# operations.py
add = 3+2
print (add)
subtract = 3-2
print (subtract)
multiply = 3*2
print (multiply)
division = 3/2
print (division)
modulus = 3%2
print (modulus)
lessThan = 3<2
print (lessThan)
greaterThan = 3>2
print(greaterThan)
equals = 3==3
print (equals)
logicalAnd = (2==2) and (3==3) and (4==4)
print (logicalAnd)
logicalOr = (2==1) or (2==2) or (2==3)
print (logicalOr)
logicalNot = not (3==2)
print (logicalNot)
```
## Loops
```python
# loops.py
fruits = ["apple", "banana", "cherry"]
for x in fruits:
print(x)
# 0,1,2,3,4,5
for x in range(6):
print(x)
# 5,6,7,8,9,10
for x in range(5,11):
print(x)
```
## Decision Making
```python
# decisions.py
x = int(input("Enter a number: "))
if x > 0:
print(x)
else:
print(-x)
```
## Functions
```python
# functions.py
def printme( str ):
"This prints a passed string into this function"
print(str)
return
printme("hello")
```
| 15.929078 | 144 | 0.654942 | eng_Latn | 0.624057 |
d5dafa4a7ea5b5c087683d383c06e1fee7e9c99a | 20,241 | md | Markdown | docs/examples/multi-model-gpt2-triton-pipeline/README.md | outerbounds/tempo | 0878ae32ed6163a1c5115f20167d991a28535364 | [
"Apache-2.0"
] | 75 | 2021-02-15T09:49:02.000Z | 2022-03-31T02:06:38.000Z | docs/examples/multi-model-gpt2-triton-pipeline/README.md | outerbounds/tempo | 0878ae32ed6163a1c5115f20167d991a28535364 | [
"Apache-2.0"
] | 106 | 2021-02-13T09:25:19.000Z | 2022-03-25T16:18:00.000Z | docs/examples/multi-model-gpt2-triton-pipeline/README.md | outerbounds/tempo | 0878ae32ed6163a1c5115f20167d991a28535364 | [
"Apache-2.0"
] | 21 | 2021-02-12T17:12:50.000Z | 2022-03-04T02:09:26.000Z | # Tempo GPT2 Triton ONNX Example
### Workflow Overview
In this example we will be doing the following:
* Download & optimize pre-trained artifacts
* Deploy GPT2 Model and Test in Docker
* Deploy GPT2 Pipeline and Test in Docker
* Deploy GPT2 Pipeline & Model to Kuberntes and Test
### Install Dependencies
```python
%%writefile requirements-dev.txt
transformers==4.5.1
torch==1.8.1
tokenizers==0.10.3
tensorflow==2.4.1
tf2onnx==1.8.5
```
```python
pip install -r requirements-dev.txt
```
## Download & Optimize pre-trained artifacts
```python
!mkdir artifacts/
```
mkdir: cannot create directory ‘artifacts/’: File exists
```python
from transformers import GPT2Tokenizer, TFGPT2LMHeadModel
tokenizer = GPT2Tokenizer.from_pretrained("gpt2")
model = TFGPT2LMHeadModel.from_pretrained(
"gpt2", from_pt=True, pad_token_id=tokenizer.eos_token_id
)
```
All PyTorch model weights were used when initializing TFGPT2LMHeadModel.
All the weights of TFGPT2LMHeadModel were initialized from the PyTorch model.
If your task is similar to the task the model of the checkpoint was trained on, you can already use TFGPT2LMHeadModel for predictions without further training.
```python
model.save_pretrained("./artifacts/gpt2-model", saved_model=True)
tokenizer.save_pretrained("./artifacts/gpt2-transformer")
```
WARNING:tensorflow:The parameters `output_attentions`, `output_hidden_states` and `use_cache` cannot be updated when calling a model.They have to be set to True/False in the config object (i.e.: `config=XConfig.from_pretrained('name', output_attentions=True)`).
WARNING:tensorflow:AutoGraph could not transform <bound method Socket.send of <zmq.sugar.socket.Socket object at 0x7faebec9aad0>> and will run it as-is.
Please report this to the TensorFlow team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output.
Cause: module, class, method, function, traceback, frame, or code object was expected, got cython_function_or_method
To silence this warning, decorate the function with @tf.autograph.experimental.do_not_convert
WARNING: AutoGraph could not transform <bound method Socket.send of <zmq.sugar.socket.Socket object at 0x7faebec9aad0>> and will run it as-is.
Please report this to the TensorFlow team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output.
Cause: module, class, method, function, traceback, frame, or code object was expected, got cython_function_or_method
To silence this warning, decorate the function with @tf.autograph.experimental.do_not_convert
WARNING:tensorflow:The parameter `return_dict` cannot be set in graph mode and will always be set to `True`.
WARNING:tensorflow:The parameters `output_attentions`, `output_hidden_states` and `use_cache` cannot be updated when calling a model.They have to be set to True/False in the config object (i.e.: `config=XConfig.from_pretrained('name', output_attentions=True)`).
WARNING:tensorflow:The parameter `return_dict` cannot be set in graph mode and will always be set to `True`.
WARNING:tensorflow:The parameters `output_attentions`, `output_hidden_states` and `use_cache` cannot be updated when calling a model.They have to be set to True/False in the config object (i.e.: `config=XConfig.from_pretrained('name', output_attentions=True)`).
WARNING:tensorflow:The parameter `return_dict` cannot be set in graph mode and will always be set to `True`.
WARNING:tensorflow:The parameters `output_attentions`, `output_hidden_states` and `use_cache` cannot be updated when calling a model.They have to be set to True/False in the config object (i.e.: `config=XConfig.from_pretrained('name', output_attentions=True)`).
WARNING:tensorflow:The parameter `return_dict` cannot be set in graph mode and will always be set to `True`.
WARNING:tensorflow:The parameters `output_attentions`, `output_hidden_states` and `use_cache` cannot be updated when calling a model.They have to be set to True/False in the config object (i.e.: `config=XConfig.from_pretrained('name', output_attentions=True)`).
WARNING:tensorflow:The parameter `return_dict` cannot be set in graph mode and will always be set to `True`.
WARNING:tensorflow:The parameters `output_attentions`, `output_hidden_states` and `use_cache` cannot be updated when calling a model.They have to be set to True/False in the config object (i.e.: `config=XConfig.from_pretrained('name', output_attentions=True)`).
WARNING:tensorflow:The parameter `return_dict` cannot be set in graph mode and will always be set to `True`.
WARNING:tensorflow:The parameters `output_attentions`, `output_hidden_states` and `use_cache` cannot be updated when calling a model.They have to be set to True/False in the config object (i.e.: `config=XConfig.from_pretrained('name', output_attentions=True)`).
WARNING:tensorflow:The parameter `return_dict` cannot be set in graph mode and will always be set to `True`.
WARNING:tensorflow:The parameters `output_attentions`, `output_hidden_states` and `use_cache` cannot be updated when calling a model.They have to be set to True/False in the config object (i.e.: `config=XConfig.from_pretrained('name', output_attentions=True)`).
WARNING:tensorflow:The parameter `return_dict` cannot be set in graph mode and will always be set to `True`.
WARNING:absl:Found untraced functions such as wte_layer_call_and_return_conditional_losses, wte_layer_call_fn, dropout_layer_call_and_return_conditional_losses, dropout_layer_call_fn, ln_f_layer_call_and_return_conditional_losses while saving (showing 5 of 735). These functions will not be directly callable after loading.
WARNING:absl:Found untraced functions such as wte_layer_call_and_return_conditional_losses, wte_layer_call_fn, dropout_layer_call_and_return_conditional_losses, dropout_layer_call_fn, ln_f_layer_call_and_return_conditional_losses while saving (showing 5 of 735). These functions will not be directly callable after loading.
INFO:tensorflow:Assets written to: ./artifacts/gpt2-model/saved_model/1/assets
INFO:tensorflow:Assets written to: ./artifacts/gpt2-model/saved_model/1/assets
('./artifacts/gpt2-transformer/tokenizer_config.json',
'./artifacts/gpt2-transformer/special_tokens_map.json',
'./artifacts/gpt2-transformer/vocab.json',
'./artifacts/gpt2-transformer/merges.txt',
'./artifacts/gpt2-transformer/added_tokens.json')
```python
!mkdir -p artifacts/gpt2-onnx-model/gpt2-model/1/
```
```python
!python -m tf2onnx.convert --saved-model ./artifacts/gpt2-model/saved_model/1 --opset 11 --output ./artifacts/gpt2-onnx-model/gpt2-model/1/model.onnx
```
2021-09-07 08:43:11.186716: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudart.so.11.0
/home/alejandro/miniconda3/lib/python3.7/runpy.py:125: RuntimeWarning: 'tf2onnx.convert' found in sys.modules after import of package 'tf2onnx', but prior to execution of 'tf2onnx.convert'; this may result in unpredictable behaviour
warn(RuntimeWarning(msg))
2021-09-07 08:43:12.886148: I tensorflow/compiler/jit/xla_cpu_device.cc:41] Not creating XLA devices, tf_xla_enable_xla_devices not set
2021-09-07 08:43:12.886345: W tensorflow/stream_executor/platform/default/dso_loader.cc:60] Could not load dynamic library 'libcuda.so.1'; dlerror: libcuda.so.1: cannot open shared object file: No such file or directory
2021-09-07 08:43:12.886376: W tensorflow/stream_executor/cuda/cuda_driver.cc:326] failed call to cuInit: UNKNOWN ERROR (303)
2021-09-07 08:43:12.886392: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:156] kernel driver does not appear to be running on this host (DESKTOP-CSLUJOT): /proc/driver/nvidia/version does not exist
2021-09-07 08:43:12.888970: I tensorflow/compiler/jit/xla_gpu_device.cc:99] Not creating XLA devices, tf_xla_enable_xla_devices not set
2021-09-07 08:43:12,892 - WARNING - '--tag' not specified for saved_model. Using --tag serve
2021-09-07 08:43:19,256 - INFO - Signatures found in model: [serving_default].
2021-09-07 08:43:19,256 - WARNING - '--signature_def' not specified, using first signature: serving_default
2021-09-07 08:43:19,256 - INFO - Output names: ['logits', 'past_key_values']
2021-09-07 08:43:19.306853: I tensorflow/core/grappler/devices.cc:69] Number of eligible GPUs (core count >= 8, compute capability >= 0.0): 0
2021-09-07 08:43:19.307167: I tensorflow/core/grappler/clusters/single_machine.cc:356] Starting new session
2021-09-07 08:43:19.307630: I tensorflow/compiler/jit/xla_gpu_device.cc:99] Not creating XLA devices, tf_xla_enable_xla_devices not set
2021-09-07 08:43:19.316142: I tensorflow/core/platform/profile_utils/cpu_utils.cc:112] CPU Frequency: 2400005000 Hz
2021-09-07 08:43:19.501937: I tensorflow/core/grappler/optimizers/meta_optimizer.cc:928] Optimization results for grappler item: graph_to_optimize
function_optimizer: Graph size after: 3213 nodes (3060), 4128 edges (3974), time = 99.635ms.
function_optimizer: function_optimizer did nothing. time = 1.408ms.
2021-09-07 08:43:27.473999: I tensorflow/compiler/jit/xla_gpu_device.cc:99] Not creating XLA devices, tf_xla_enable_xla_devices not set
WARNING:tensorflow:From /home/alejandro/miniconda3/lib/python3.7/site-packages/tf2onnx/tf_loader.py:603: extract_sub_graph (from tensorflow.python.framework.graph_util_impl) is deprecated and will be removed in a future version.
Instructions for updating:
Use `tf.compat.v1.graph_util.extract_sub_graph`
2021-09-07 08:43:29,277 - WARNING - From /home/alejandro/miniconda3/lib/python3.7/site-packages/tf2onnx/tf_loader.py:603: extract_sub_graph (from tensorflow.python.framework.graph_util_impl) is deprecated and will be removed in a future version.
Instructions for updating:
Use `tf.compat.v1.graph_util.extract_sub_graph`
2021-09-07 08:43:29.353446: I tensorflow/core/grappler/devices.cc:69] Number of eligible GPUs (core count >= 8, compute capability >= 0.0): 0
2021-09-07 08:43:29.353640: I tensorflow/core/grappler/clusters/single_machine.cc:356] Starting new session
2021-09-07 08:43:29.353974: I tensorflow/compiler/jit/xla_gpu_device.cc:99] Not creating XLA devices, tf_xla_enable_xla_devices not set
2021-09-07 08:43:36.123024: I tensorflow/core/grappler/optimizers/meta_optimizer.cc:928] Optimization results for grappler item: graph_to_optimize
constant_folding: Graph size after: 2720 nodes (-318), 3646 edges (-319), time = 4489.73486ms.
function_optimizer: function_optimizer did nothing. time = 2.24ms.
constant_folding: Graph size after: 2720 nodes (0), 3646 edges (0), time = 1504.76294ms.
function_optimizer: function_optimizer did nothing. time = 13.628ms.
2021-09-07 08:43:39,251 - INFO - Using tensorflow=2.4.0, onnx=1.9.0, tf2onnx=1.8.5/50049d
2021-09-07 08:43:39,252 - INFO - Using opset <onnx, 11>
2021-09-07 08:43:51,608 - INFO - Computed 0 values for constant folding
2021-09-07 08:44:27,844 - INFO - Optimizing ONNX model
2021-09-07 08:44:38,170 - INFO - After optimization: Cast -123 (311->188), Concat -37 (126->89), Const -1854 (2032->178), Gather +12 (2->14), GlobalAveragePool +50 (0->50), Identity -76 (76->0), ReduceMean -50 (50->0), Shape -37 (112->75), Slice -74 (235->161), Squeeze -198 (223->25), Transpose -12 (61->49), Unsqueeze -361 (435->74)
2021-09-07 08:44:39,069 - INFO -
2021-09-07 08:44:39,069 - INFO - Successfully converted TensorFlow model ./artifacts/gpt2-model/saved_model/1 to ONNX
2021-09-07 08:44:39,069 - INFO - Model inputs: ['attention_mask:0', 'input_ids:0']
2021-09-07 08:44:39,070 - INFO - Model outputs: ['logits', 'past_key_values']
2021-09-07 08:44:39,070 - INFO - ONNX model is saved at ./artifacts/gpt2-onnx-model/gpt2-model/1/model.onnx
## Deploy GPT2 ONNX Model in Triton
```python
import os
ARTIFACT_FOLDER = os.getcwd() + "/artifacts"
```
```python
import numpy as np
from tempo.serve.metadata import ModelFramework, ModelDataArgs, ModelDataArg
from tempo.serve.model import Model
from tempo.serve.pipeline import Pipeline, PipelineModels
from tempo.serve.utils import pipeline, predictmethod
```
#### Define as tempo model
```python
gpt2_model = Model(
name="gpt2-model",
platform=ModelFramework.ONNX,
local_folder=ARTIFACT_FOLDER + "/gpt2-onnx-model",
uri="s3://tempo/gpt2/model",
description="GPT-2 ONNX Triton Model",
)
```
Insights Manager not initialised as empty URL provided.
#### Deploy gpt2 model to docker
```python
from tempo.serve.deploy import deploy_local
remote_gpt2_model = deploy_local(gpt2_model)
```
#### Send predictions
```python
input_ids = tokenizer.encode("This is a test", return_tensors="tf")
attention_mask = np.ones(input_ids.shape.as_list(), dtype=np.int32)
gpt2_inputs = {
"input_ids:0": input_ids.numpy(),
"attention_mask:0": attention_mask
}
print(gpt2_inputs)
gpt2_outputs = remote_gpt2_model.predict(**gpt2_inputs)
```
{'input_ids:0': array([[1212, 318, 257, 1332]], dtype=int32), 'attention_mask:0': array([[1, 1, 1, 1]], dtype=int32)}
#### Print single next token generated
```python
logits = gpt2_outputs["logits"]
# take the best next token probability of the last token of input ( greedy approach)
next_token = logits.argmax(axis=2)[0]
next_token_str = tokenizer.decode(
next_token[-1:], skip_special_tokens=True, clean_up_tokenization_spaces=True
).strip()
print(next_token_str)
```
of
## Define Transformer Pipeline
```python
@pipeline(
name="gpt2-transformer",
uri="s3://tempo/gpt2/transformer",
local_folder=ARTIFACT_FOLDER + "/gpt2-transformer/",
models=PipelineModels(gpt2_model=gpt2_model),
description="A pipeline to use either an sklearn or xgboost model for Iris classification",
)
class GPT2Transformer:
def __init__(self):
try:
self.tokenizer = GPT2Tokenizer.from_pretrained("/mnt/models/")
except:
self.tokenizer = GPT2Tokenizer.from_pretrained(ARTIFACT_FOLDER + "/gpt2-transformer/")
@predictmethod
def predict(self, payload: str) -> str:
count = 0
# TODO: Update to allow this to be passed as parameters
max_gen_len = 10
# TODO: Update to work for multiple sentences
gen_sentence = payload
while count < max_gen_len:
input_ids = self.tokenizer.encode(gen_sentence, return_tensors="tf")
attention_mask = np.ones(input_ids.shape.as_list(), dtype=np.int32)
gpt2_inputs = {
"input_ids:0": input_ids.numpy(),
"attention_mask:0": attention_mask
}
gpt2_outputs = self.models.gpt2_model.predict(**gpt2_inputs)
logits = gpt2_outputs["logits"]
# take the best next token probability of the last token of input ( greedy approach)
next_token = logits.argmax(axis=2)[0]
next_token_str = self.tokenizer.decode(
next_token[-1:], skip_special_tokens=True, clean_up_tokenization_spaces=True
).strip()
gen_sentence += " " + next_token_str
count += 1
return gen_sentence
```
INFO:tempo:Initialising Insights Manager with Args: ('', 1, 1, 3, 0)
WARNING:tempo:Insights Manager not initialised as empty URL provided.
#### Test locally against deployed model
```python
gpt2_transformer = GPT2Transformer()
```
```python
gpt2_output = gpt2_transformer.predict("I love artificial intelligence")
```
```python
print(gpt2_output)
```
I love artificial intelligence , but I 'm not sure if it 's worth
## Deploy GPT2 Transformer to Docker and Test
* In preparation for running our models we save the Python environment needed for the orchestration to run as defined by a `conda.yaml` in our project.
```python
%%writefile artifacts/gpt2-transformer/conda.yaml
name: tempo-gpt2
channels:
- defaults
dependencies:
- python=3.7.10
- pip:
- transformers==4.5.1
- tokenizers==0.10.3
- tensorflow==2.4.1
- dill
- mlops-tempo
- mlserver
- mlserver-tempo
```
Overwriting artifacts/gpt2-transformer/conda.yaml
#### Save environment and pipeline artifact
```python
from tempo.serve.loader import save
save(GPT2Transformer)
```
INFO:tempo:Initialising Insights Manager with Args: ('', 1, 1, 3, 0)
WARNING:tempo:Insights Manager not initialised as empty URL provided.
INFO:tempo:Saving environment
INFO:tempo:Saving tempo model to /home/alejandro/Programming/kubernetes/seldon/tempo/docs/examples/multi-model-gpt2-triton-pipeline/artifacts/gpt2-transformer/model.pickle
INFO:tempo:Using found conda.yaml
INFO:tempo:Creating conda env with: conda env create --name tempo-cb69ce65-9d45-4683-bdfd-592f735994f1 --file /tmp/tmp1vsizgk7.yml
INFO:tempo:packing conda environment from tempo-cb69ce65-9d45-4683-bdfd-592f735994f1
Collecting packages...
Packing environment at '/home/alejandro/miniconda3/envs/tempo-cb69ce65-9d45-4683-bdfd-592f735994f1' to '/home/alejandro/Programming/kubernetes/seldon/tempo/docs/examples/multi-model-gpt2-triton-pipeline/artifacts/gpt2-transformer/environment.tar.gz'
[########################################] | 100% Completed | 49.2s
INFO:tempo:Removing conda env with: conda remove --name tempo-cb69ce65-9d45-4683-bdfd-592f735994f1 --all --yes
#### Deploy locally on Docker
* Here we test our models using production images but running locally on Docker. This allows us to ensure the final production deployed model will behave as expected when deployed.
```python
from tempo import deploy_local
remote_transformer = deploy_local(gpt2_transformer)
```
```python
remote_transformer.predict("I love artificial intelligence")
```
"I love artificial intelligence , but I 'm not sure if it 's worth"
```python
remote_transformer.undeploy()
```
INFO:tempo:Undeploying gpt2-transformer
INFO:tempo:Undeploying gpt2-model
## Deploy to Kubernetes
* Here we illustrate how to run the final models in "production" on Kubernetes by using Tempo to deploy
### Prerequisites
Create a Kind Kubernetes cluster with Minio and Seldon Core installed using Ansible as described [here](https://tempo.readthedocs.io/en/latest/overview/quickstart.html#kubernetes-cluster-with-seldon-core).
```python
!kubectl create ns production
!kubectl apply -f k8s/rbac -n production
```
Error from server (AlreadyExists): namespaces "production" already exists
secret/minio-secret configured
serviceaccount/tempo-pipeline unchanged
role.rbac.authorization.k8s.io/tempo-pipeline unchanged
rolebinding.rbac.authorization.k8s.io/tempo-pipeline-rolebinding unchanged
```python
from tempo.examples.minio import create_minio_rclone
import os
create_minio_rclone(os.getcwd()+"/rclone.conf")
```
```python
from tempo.serve.loader import upload
upload(gpt2_transformer)
upload(gpt2_model)
```
INFO:tempo:Uploading /home/alejandro/Programming/kubernetes/seldon/tempo/docs/examples/multi-model-gpt2-triton-pipeline/artifacts/gpt2-transformer/ to s3://tempo/gpt2/transformer
INFO:tempo:Uploading /home/alejandro/Programming/kubernetes/seldon/tempo/docs/examples/multi-model-gpt2-triton-pipeline/artifacts/gpt2-onnx-model to s3://tempo/gpt2/model
```python
from tempo.serve.metadata import SeldonCoreOptions
runtime_options = SeldonCoreOptions(**{
"remote_options": {
"namespace": "production",
"authSecretName": "minio-secret"
}
})
```
```python
from tempo import deploy_remote
remote_gpt2_transformer = deploy_remote(gpt2_transformer, options=runtime_options)
```
```python
remote_gpt2_transformer.predict("I love artificial intelligence")
```
"I love artificial intelligence , but I 'm not sure if it 's worth"
```python
remote_gpt2_transformer.undeploy()
```
INFO:tempo:Undeploying gpt2-transformer
INFO:tempo:Undeploying gpt2-model
```python
```
| 41.562628 | 338 | 0.743837 | eng_Latn | 0.736779 |
d5db1f2cf775caf8f8e76df7130029247e85cf73 | 13,500 | md | Markdown | articles/azure-app-configuration/use-key-vault-references-dotnet-core.md | eltociear/azure-docs.fr-fr | 3302b8be75f0872cf7d7a5e264850849ac36e493 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-app-configuration/use-key-vault-references-dotnet-core.md | eltociear/azure-docs.fr-fr | 3302b8be75f0872cf7d7a5e264850849ac36e493 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-app-configuration/use-key-vault-references-dotnet-core.md | eltociear/azure-docs.fr-fr | 3302b8be75f0872cf7d7a5e264850849ac36e493 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Tutoriel concernant l’utilisation de références Key Vault avec Azure App Configuration dans une application ASP.NET Core | Microsoft Docs
description: Dans ce tutoriel, vous apprenez à utiliser les références Key Vault avec Azure App Configuration depuis une application ASP.NET Core
services: azure-app-configuration
documentationcenter: ''
author: lisaguthrie
manager: maiye
editor: ''
ms.assetid: ''
ms.service: azure-app-configuration
ms.workload: tbd
ms.devlang: csharp
ms.topic: tutorial
ms.date: 04/08/2020
ms.author: lcozzens
ms.custom: mvc
ms.openlocfilehash: 4641c50f0579e2a8db514df58c0401eb2173d793
ms.sourcegitcommit: 58faa9fcbd62f3ac37ff0a65ab9357a01051a64f
ms.translationtype: HT
ms.contentlocale: fr-FR
ms.lasthandoff: 04/29/2020
ms.locfileid: "81309050"
---
# <a name="tutorial-use-key-vault-references-in-an-aspnet-core-app"></a>Tutoriel : Utiliser des références Key Vault dans une application ASP.NET Core
Dans ce tutoriel, vous apprenez à utiliser le service Azure App Configuration avec Azure Key Vault. App Configuration et Key Vault sont des services complémentaires utilisés côte à côte dans la plupart des déploiements d’applications.
App Configuration vous aide à utiliser ces services ensemble en créant des clés qui référencent des valeurs stockées dans Key Vault. Lorsque le service App Configuration crée de telles clés, il stocke les URI des valeurs Key Vault plutôt que les valeurs elles-mêmes.
Votre application utilise le fournisseur client de App Configuration pour récupérer les références Key Vault, tout comme pour toutes les autres clés stockées dans App Configuration. Dans ce cas, les valeurs stockées dans App Configuration sont des URI qui référencent les valeurs dans le coffre de clés. Elles ne sont pas des valeurs de coffre de clés ou des informations d’identification. Étant donné que le fournisseur client reconnaît les clés comme des références Key Vault, il utilise Key Vault pour récupérer leurs valeurs.
Votre application est chargée de s’authentifier correctement auprès d’App Configuration et auprès de Key Vault. Les deux services ne communiquent pas directement.
Ce tutoriel vous montre comment implémenter des références Key Vault dans votre code. Il s’appuie sur l’application web introduite dans les guides de démarrage rapide. Avant de continuer, terminez d’abord l’étape [Créer une application ASP.NET Core avec App Configuration](./quickstart-aspnet-core-app.md).
Vous pouvez utiliser l’éditeur de code de votre choix pour exécuter les étapes de ce tutoriel. Par exemple, [Visual Studio Code](https://code.visualstudio.com/) est un éditeur de code multiplateforme qui est disponible pour les systèmes d’exploitation Windows, macOS et Linux.
Dans ce tutoriel, vous allez apprendre à :
> [!div class="checklist"]
> * Créer une clé App Configuration qui référence une valeur stockée dans Key Vault.
> * Accéder à la valeur de cette clé à partir d’une application web ASP.NET Core.
## <a name="prerequisites"></a>Prérequis
Avant d’effectuer ce tutoriel, installez le [kit SDK .NET Core](https://dotnet.microsoft.com/download).
[!INCLUDE [quickstarts-free-trial-note](../../includes/quickstarts-free-trial-note.md)]
## <a name="create-a-vault"></a>Création d'un coffre
1. Sélectionnez l’option **Créer une ressource** dans le coin supérieur gauche du Portail Azure :
1. Dans la zone de recherche, entrez **Key Vault**.
1. Dans la liste des résultats, sélectionnez **Coffres de clés** sur la gauche.
1. Dans **Coffres de clés**, sélectionnez **Ajouter**.
1. Sur la droite, dans **Créer un coffre de clés**, renseignez les informations suivantes :
- Sélectionnez **Abonnement** pour choisir un abonnement.
- Dans **Groupe de ressources**, sélectionnez **Créer un nouveau** et entrez un nom de groupe de ressources.
- Dans **Nom du coffre de clés**, un nom unique est requis. Pour ce tutoriel, entrez **Contoso-vault2**.
- Dans la liste déroulante **Région**, choisissez un emplacement.
1. Conservez les valeurs par défaut des autres options **Création d’un coffre de clés**.
1. Sélectionnez **Create** (Créer).
À ce stade, votre compte Azure est le seul autorisé à accéder à ce nouveau coffre.
## <a name="add-a-secret-to-key-vault"></a>Ajouter un secret au coffre de clés
Pour ajouter un secret au coffre, vous n’avez qu’à effectuer deux autres étapes. Dans ce cas, ajoutez un message que vous pouvez utiliser pour tester la récupération de Key Vault. Le message est appelé **Message** et vous stockez la valeur « Hello from Key Vault » dedans.
1. Depuis les pages des propriétés Key Vault, sélectionnez **Secrets**.
1. Sélectionnez **Générer/Importer**.
1. Dans le volet **Créer un secret**, saisissez les valeurs suivantes :
- **Options de chargement** : Entrez **Manuel**.
- **Name** : Entrez **Message**.
- **Valeur** : Entrez **Hello from Key Vault**.
1. Conservez les valeurs par défaut des autres propriétés **Créer un secret**.
1. Sélectionnez **Create** (Créer).
## <a name="add-a-key-vault-reference-to-app-configuration"></a>Ajouter une référence Key Vault à App Configuration
1. Connectez-vous au [portail Azure](https://portal.azure.com). Sélectionnez **Toutes les ressources**, puis sélectionnez l’instance du magasin App Configuration que vous avez créée dans le guide de démarrage rapide.
1. Sélectionnez **Explorateur de configuration**.
1. Sélectionnez **+ Créer** > **Référence Key Vault**, puis choisissez les valeurs suivantes :
- **Clé** : Sélectionnez **TestApp:Settings:KeyVaultMessage**.
- **Étiquette** : Laissez cette valeur vide.
- **Abonnement**, **Groupe de ressources** et **Key Vault** : Entrez les valeurs correspondant au coffre de clés que vous avez créé à la section précédente.
- **Secret** : Sélectionnez le secret nommé **Message** que vous avez créé dans la section précédente.
## <a name="connect-to-key-vault"></a>Se connecter à Key Vault
1. Dans ce tutoriel, vous utilisez un principal de service pour l’authentification auprès de KeyVault. Pour créer ce principal de service, utilisez la commande Azure CLI [az ad sp create-for-rbac](/cli/azure/ad/sp?view=azure-cli-latest#az-ad-sp-create-for-rbac) :
```azurecli
az ad sp create-for-rbac -n "http://mySP" --sdk-auth
```
Cette opération retourne une série de paires clé/valeur :
```console
{
"clientId": "7da18cae-779c-41fc-992e-0527854c6583",
"clientSecret": "b421b443-1669-4cd7-b5b1-394d5c945002",
"subscriptionId": "443e30da-feca-47c4-b68f-1636b75e16b3",
"tenantId": "35ad10f1-7799-4766-9acf-f2d946161b77",
"activeDirectoryEndpointUrl": "https://login.microsoftonline.com",
"resourceManagerEndpointUrl": "https://management.azure.com/",
"sqlManagementEndpointUrl": "https://management.core.windows.net:8443/",
"galleryEndpointUrl": "https://gallery.azure.com/",
"managementEndpointUrl": "https://management.core.windows.net/"
}
```
1. Exécutez la commande suivante pour autoriser le principal du service à accéder à votre coffre de clés :
```cmd
az keyvault set-policy -n <your-unique-keyvault-name> --spn <clientId-of-your-service-principal> --secret-permissions delete get list set --key-permissions create decrypt delete encrypt get list unwrapKey wrapKey
```
1. Ajoutez des variables d’environnement pour stocker les valeurs de *clientId*, *clientSecret* et *tenantId*.
#### <a name="windows-command-prompt"></a>[Invite de commandes Windows](#tab/cmd)
```cmd
setx AZURE_CLIENT_ID <clientId-of-your-service-principal>
setx AZURE_CLIENT_SECRET <clientSecret-of-your-service-principal>
setx AZURE_TENANT_ID <tenantId-of-your-service-principal>
```
#### <a name="powershell"></a>[PowerShell](#tab/powershell)
```PowerShell
$Env:AZURE_CLIENT_ID = <clientId-of-your-service-principal>
$Env:AZURE_CLIENT_SECRET = <clientSecret-of-your-service-principal>
$Env:AZURE_TENANT_ID = <tenantId-of-your-service-principal>
```
#### <a name="bash"></a>[Bash](#tab/bash)
```bash
export AZURE_CLIENT_ID = <clientId-of-your-service-principal>
export AZURE_CLIENT_SECRET = <clientSecret-of-your-service-principal>
export AZURE_TENANT_ID = <tenantId-of-your-service-principal>
```
---
> [!NOTE]
> Ces informations d’identification Key Vault sont utilisées uniquement dans votre application. Votre application s’authentifie directement auprès de Key Vault à l’aide de ces informations d’identification. Elles ne sont jamais transmises au service App Configuration.
1. Redémarrez votre terminal pour charger ces nouvelles variables d’environnement.
## <a name="update-your-code-to-use-a-key-vault-reference"></a>Mettre à jour votre code pour utiliser une référence Key Vault
1. Ajoutez une référence aux packages NuGet requis en exécutant la commande suivante :
```dotnetcli
dotnet add package Azure.Identity
```
1. Ouvrez *Program.cs* et ajoutez des références aux packages requis suivants :
```csharp
using Azure.Identity;
```
1. Mettez à jour la méthode `CreateWebHostBuilder` pour utiliser App Configuration en appelant la méthode `config.AddAzureAppConfiguration`. Incluez l’option `ConfigureKeyVault` et transmettez les informations d’identification correctes à votre coffre de clés.
#### <a name="net-core-2x"></a>[.NET Core 2.x](#tab/core2x)
```csharp
public static IWebHostBuilder CreateWebHostBuilder(string[] args) =>
WebHost.CreateDefaultBuilder(args)
.ConfigureAppConfiguration((hostingContext, config) =>
{
var settings = config.Build();
config.AddAzureAppConfiguration(options =>
{
options.Connect(settings["ConnectionStrings:AppConfig"])
.ConfigureKeyVault(kv =>
{
kv.SetCredential(new DefaultAzureCredential());
});
});
})
.UseStartup<Startup>();
```
#### <a name="net-core-3x"></a>[.NET Core 3.x](#tab/core3x)
```csharp
public static IHostBuilder CreateHostBuilder(string[] args) =>
Host.CreateDefaultBuilder(args)
.ConfigureWebHostDefaults(webBuilder =>
webBuilder.ConfigureAppConfiguration((hostingContext, config) =>
{
var settings = config.Build();
config.AddAzureAppConfiguration(options =>
{
options.Connect(settings["ConnectionStrings:AppConfig"])
.ConfigureKeyVault(kv =>
{
kv.SetCredential(new DefaultAzureCredential());
});
});
})
.UseStartup<Startup>());
```
1. Quand vous avez initialisé la connexion à App Configuration, vous avez configuré la connexion à Key Vault en appelant la méthode `ConfigureKeyVault`. Après l’initialisation, vous pouvez accéder aux valeurs des références Key Vault de la même façon que vous accédez aux valeurs des clés App Configuration normales.
Pour voir ce processus en action, ouvrez *Index.cshtml* dans **Affichages** > **Dossier de base**. Remplacez son contenu par le code ci-dessous :
```html
@using Microsoft.Extensions.Configuration
@inject IConfiguration Configuration
<style>
body {
background-color: @Configuration["TestApp:Settings:BackgroundColor"]
}
h1 {
color: @Configuration["TestApp:Settings:FontColor"];
font-size: @Configuration["TestApp:Settings:FontSize"]px;
}
</style>
<h1>@Configuration["TestApp:Settings:Message"]
and @Configuration["TestApp:Settings:KeyVaultMessage"]</h1>
```
Vous accédez à la valeur de la référence Key Vault **TestApp:Settings:KeyVaultMessage** de la même façon que vous accédez à la valeur de configuration **TestApp:Settings:Message**.
## <a name="build-and-run-the-app-locally"></a>Générer et exécuter l’application localement
1. Pour générer l’application à l’aide de l’interface CLI .NET Core, exécutez la commande suivante dans l’interpréteur de commandes :
```dotnetcli
dotnet build
```
1. Une fois la génération terminée, utilisez la commande suivante pour exécuter l’application web localement :
```dotnetcli
dotnet run
```
1. Ouvrez une fenêtre de navigateur, puis accédez à `http://localhost:5000`, qui est l’URL par défaut de l’application web hébergée localement.
## <a name="clean-up-resources"></a>Nettoyer les ressources
[!INCLUDE [azure-app-configuration-cleanup](../../includes/azure-app-configuration-cleanup.md)]
## <a name="next-steps"></a>Étapes suivantes
Dans ce tutoriel, vous créez une clé App Configuration qui référence une valeur stockée dans Key Vault. Pour savoir comment ajouter une identité de service gérée par Azure qui simplifie l’accès à App Configuration et à Key Vault, passez au tutoriel suivant.
> [!div class="nextstepaction"]
> [Intégration des identités managées](./howto-integrate-azure-managed-service-identity.md)
| 50.185874 | 529 | 0.717556 | fra_Latn | 0.874262 |
d5dc6de0cc820397709ec939efd8e33f12f57486 | 2,300 | md | Markdown | _posts/2007/2007-08-31-summer-2007-post-mortem.md | gvwilson/thirdb | 4a78ed7aef83c97d0ce95e73f20372a3482e1dd2 | [
"CC-BY-4.0"
] | 14 | 2016-07-23T02:36:15.000Z | 2021-11-01T20:13:03.000Z | _posts/2007/2007-08-31-summer-2007-post-mortem.md | gvwilson/thirdb | 4a78ed7aef83c97d0ce95e73f20372a3482e1dd2 | [
"CC-BY-4.0"
] | 102 | 2015-12-30T09:38:08.000Z | 2021-11-02T11:34:33.000Z | _posts/2007/2007-08-31-summer-2007-post-mortem.md | gvwilson/thirdb | 4a78ed7aef83c97d0ce95e73f20372a3482e1dd2 | [
"CC-BY-4.0"
] | 8 | 2018-01-07T14:36:47.000Z | 2021-02-23T07:33:57.000Z | ---
title: "Summer 2007 Post Mortem"
date: 2007-08-31 14:16:17
year: 2007
---
We held the post-mortem for the summer's projects yesterday. It went well---the summer, I mean, not just the post-mortem. Here are the main points:
<table>
<tr>
<td align="center"><strong>Good</strong></td>
<td align="center"><strong>Bad</strong></td>
</tr>
<tr>
<td valign="top">
<ul>
<li>Industry/prof visits</li>
<li>Learned a lot (group work)</li>
<li>Learning the internals of a large system</li>
<li>Making friends</li>
<li>Excellent office space</li>
<li>Learned that software engineering can actually be interesting</li>
<li>Doing something new (building real code!)</li>
<li>Martin + Tony worked independently very well</li>
<li>Had a good OLM deployment plan</li>
<li>No personality clashes</li>
<li>Good data model for new ticketing system</li>
<li>Group lunches</li>
<li>Speed Scrabble</li>
<li>Python</li>
<li>Learning (self-)discipline</li>
<li>The Google podcast</li>
<li>Self-administration of machines (fun to do, fun to learn)</li>
<li>Hardware was good</li>
<li>Regular status meetings were useful and a good learning experience</li>
<li>OLM testing</li>
<li>Talk with Jay Goldman</li>
<li>Sharing problems on the mailing list</li>
<li>Jeff Balogh's visit</li>
<li>We did it!</li>
</ul>
</td>
<td valign="top">
<ul>
<li>Working solo on UTest</li>
<li>Dealing with Ant</li>
<li>Falling behind on collaboration with partner</li>
<li>No real time plan for the last month (before deployment)</li>
<li>Hardware problems that were never resolved</li>
<li>No contact with previous teams</li>
<li>Python and Eclipse</li>
<li>Too much time spent in email</li>
<li>Supervisors were too hands off</li>
<li>Didn't get deployed on schedule</li>
<li>Didn't get in the habit of "talking tickets"</li>
<li>Status meetings didn't turn in to design meetings</li>
<li>Interface to new ticketing system</li>
<li>Greg's absence (length and timing)</li>
<li>The old dashboard code</li>
<li>Should have had bi-weekly demos</li>
<li>Initial nervousness (a.k.a. "startup shakes")</li>
<li>Having meetings at 9:00 AM</li>
<li>Not enough documentation (but we haven't done any better)</li>
<li>Supervisors couldn't cover for each other during absences</li>
</ul>
</td>
</tr>
</table>
| 34.328358 | 149 | 0.706522 | eng_Latn | 0.875214 |
d5dd941006ed249ffea342245d2024027d91317b | 843 | md | Markdown | README.md | Univesp-Computacao/bot_help | 153e79c1a60698ed94b9758ef5a926f83b12cf43 | [
"MIT"
] | null | null | null | README.md | Univesp-Computacao/bot_help | 153e79c1a60698ed94b9758ef5a926f83b12cf43 | [
"MIT"
] | null | null | null | README.md | Univesp-Computacao/bot_help | 153e79c1a60698ed94b9758ef5a926f83b12cf43 | [
"MIT"
] | null | null | null | # Bot Helper
@botheper_bot
### O que este bot faz?
Este bot exibe os comandos das principais tecnologias da informação, começando por Git, Linux e Docker.
Desenvolvido em Python com a biblioteca python-telegram-bot e hospedado no railway.app.
## Proximos passos do Projeto
+ Menu interativos - Nivel Iniciante + - [python Telegram bot](https://github.com/python-telegram-bot/python-telegram-bot) - Domingo 03/04/2022
+ API Gitub - Busca commits + - [API github](https://docs.github.com/pt/rest/guides/getting-started-with-the-rest-api)
+ Suporte a Markdown - Nivel Iniciante + - [python Telegram bot](https://github.com/python-telegram-bot/python-telegram-bot)
+ Retorna arquivos PDF - Nivel Iniciante + - [python Telegram bot](https://github.com/python-telegram-bot/python-telegram-bot)
+ CI/CD - Futuramente
+ Testes - Furutamente | 40.142857 | 143 | 0.754448 | por_Latn | 0.651228 |
d5dddf0c8cfda599672c29e561f5039ff7e072ae | 2,588 | md | Markdown | configs/twins/README.md | littleSunlxy/mmsegmentation | 9e4d74def0bc570c719fb3605caca82a2648a111 | [
"Apache-2.0"
] | null | null | null | configs/twins/README.md | littleSunlxy/mmsegmentation | 9e4d74def0bc570c719fb3605caca82a2648a111 | [
"Apache-2.0"
] | null | null | null | configs/twins/README.md | littleSunlxy/mmsegmentation | 9e4d74def0bc570c719fb3605caca82a2648a111 | [
"Apache-2.0"
] | null | null | null | # Twins: Revisiting the Design of Spatial Attention in Vision Transformers
## Introduction
<!-- [ALGORITHM] -->
<a href="https://github.com/Meituan-AutoML/Twins">Official Repo</a>
<details>
<summary align="right"><a href="https://arxiv.org/pdf/2104.13840.pdf">Twins (arXiv'2021)</a></summary>
```latex
@article{liu2021Swin,
title={Swin Transformer: Hierarchical Vision Transformer using Shifted Windows},
author={Liu, Ze and Lin, Yutong and Cao, Yue and Hu, Han and Wei, Yixuan and Zhang, Zheng and Lin, Stephen and Guo, Baining},
journal={arXiv preprint arXiv:2103.14030},
year={2021}
}
```
</details>
## Usage
``pip install timm==0.3.2``
#### Training
To train Twins-SVT-B on ImageNet using 8 gpus for 300 epochs, run
```python
python -m torch.distributed.launch --nproc_per_node=8 --use_env main.py --model alt_gvt_base --batch-size 128 --data-path path_to_imagenet --dist-eval --drop-path 0.3
```
#### Evaluation
To evaluate the performance of Twins-SVT-L on ImageNet using one GPU, run
```python
python main.py --eval --resume alt_gvt_large.pth --model alt_gvt_large --data-path path_to_imagenet
```
This script convert model from `PRETRAIN_PATH` and store the converted model in `STORE_PATH`.
## Results and models
### ADE20K
| Model | Alias in the paper | mIoU(ss/ms) | FLOPs(G)|#Params (M) | URL | Log |
| --- | --- | --- | --- | --- |--- |---|
| PCPVT-Small| Twins-PCPVT-S | 46.2/47.5 | 234 | 54.6 | [pcpvt_small.pth](https://drive.google.com/file/d/1PkkBULZZUhIkFKq_D9db1DXUIHwIPlvp/view?usp=sharing) | [pcpvt_s.txt](/logs/upernet_pcpvt_s.txt)
| PCPVT-Base | Twins-PCPVT-B | 47.1/48.4 | 250 | 74.3 | [pcpvt_base.pth](https://drive.google.com/file/d/16sCd0slLLz6xt3C2ma3TkS9rpMS9eezT/view?usp=sharing) | [pcpvt_b.txt](/logs/upernet_pcpvt_b.txt)
| PCPVT-Large| Twins-PCPVT-L | 48.6/49.8 | 269 | 91.5 | [pcpvt_large.pth](https://drive.google.com/file/d/1wsU9riWBiN22fyfsJCHDFhLyP2c_n8sk/view?usp=sharing) | [pcpvt_l.txt](/logs/upernet_pcpvt_l.txt)
| ALTGVT-Small | Twins-SVT-S | 46.2/47.1 | 228 | 54.4 | [alt_gvt_small.pth](https://drive.google.com/file/d/18OhG0sbAJ5okPj0zn-8YTydKG9jS8TUx/view?usp=sharing) |[svt_s.txt](/logs/upernet_svt_s.txt)
| ALTGVT-Base | Twins-SVT-B | 47.4/48.9 | 261 | 88.5 | [alt_gvt_base.pth](https://drive.google.com/file/d/1LNtdvACihmKO6XyBPoJDxbrd6AuHVVvq/view?usp=sharing)|[svt_b.txt](/logs/upernet_svt_b.txt)
| ALTGVT-Large | Twins-SVT-L | 48.8/50.2 | 297 | 133 | [alt_gvt_large.pth](https://drive.google.com/file/d/1xS91hytfzuMZ5Rgb-W-cOJ9G7ptjVwlO/view?usp=sharing)|[svt_l.txt](/logs/upernet_svt_l.txt)
| 44.62069 | 202 | 0.711747 | yue_Hant | 0.350244 |
d5df3d15952501b87c29e6832b65494f782e01a0 | 1,712 | md | Markdown | README.md | colleencancel/Eye-Exercise | 7ec4c9b0e40f26d76edbd29bc7c2bb6c2f9a733e | [
"Unlicense"
] | null | null | null | README.md | colleencancel/Eye-Exercise | 7ec4c9b0e40f26d76edbd29bc7c2bb6c2f9a733e | [
"Unlicense"
] | null | null | null | README.md | colleencancel/Eye-Exercise | 7ec4c9b0e40f26d76edbd29bc7c2bb6c2f9a733e | [
"Unlicense"
] | null | null | null | # Eye Exercise
MIT xPRO
This project was part of the course work required in the MIT xPRO Full-Stack development course.
#### Description
A project to track the movement of the mouse. When the mouse pointer is moved there are two eyes which follow the movement of the mouse on the screen. This projects uses mouse movement detection.
#### How to Run
Download the files that are in the Eye Exercise directory. Open a new tab in your browser window. Drag and drop the index.html file onto the new tab. Move mouse around on browser to see eyes move.
#### Future improvements
Adding additional detail to the page to make it more visually interesting
#### MIT License
Copyright (c) 2021
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
| 74.434783 | 460 | 0.793808 | eng_Latn | 0.937263 |
d5df5c73c586bcdc5f5b67f6c35aaad7a19796b6 | 1,730 | md | Markdown | README.md | SniperCZE/sms-gateway | 22339d59326336b198c8b86aa9098c4925cfbafc | [
"MIT"
] | 2 | 2021-04-06T13:49:29.000Z | 2021-04-18T09:55:40.000Z | README.md | SniperCZE/sms-gateway | 22339d59326336b198c8b86aa9098c4925cfbafc | [
"MIT"
] | null | null | null | README.md | SniperCZE/sms-gateway | 22339d59326336b198c8b86aa9098c4925cfbafc | [
"MIT"
] | null | null | null | # sms-gateway
Open source / open hardware multiline SMS gateway with HTTP api and RabbitMQ consumer, enclosed in nice 1U custom case.
## Work in progress!
This repo is under development. There is no guarantee that any part of it will not change in the future. Models, schemas and part lists are not final.
## Idea
I would like to have SMS gateway for sending SMS, which:
- receives messages with HTTP API or RabbitMQ queue
- works without active Internet connection
- can be scaled up, can be HA
- looks good
- is not expensive
## Electronics
Whole idea is based on raspberry pi minicomputers with SIM800L GSM modules and some custom PCBs. All schematics are KiCAD (https://kicad.org/) projects.
### Power
I'am using one input of 230V AC, converted to 5V DC for every components. There is custom designed PDU board inside of gateway interconnecting all components. Ethernet switch, thermometer and raspberries are powered directly with 5V, GSM module SIM800L must be powered with 4.3V, so I'm using basic diode 1N4007 to drop 5V to 4.3V.
## Mechanics
I will have to build custom 1U rack case for this project. You can find here models ad FreeCAD (https://www.freecadweb.org/) project.
FreeCAD workbenches needed:
- `KiCadStepUp` - integration of KiCAD
- `Fasteners` - screws and nuts
- `Sheet metal` - Support of metal sheet bending
- `Exploded assembly` - Generation of assembly animation
## Software
Every piece of software for my gateway is written in python with some bash scripts and systemd units.
| 42.195122 | 331 | 0.775145 | eng_Latn | 0.986273 |
d5dfa329e36c73d7a20fa3394c09beae1392546c | 938 | md | Markdown | README.md | diegoportela99/Job-Scraper | 1f400f366cb3c7116632b76b0749e3d9a68992ab | [
"MIT"
] | 1 | 2021-08-19T15:12:11.000Z | 2021-08-19T15:12:11.000Z | README.md | diegoportela99/Job-Scraper | 1f400f366cb3c7116632b76b0749e3d9a68992ab | [
"MIT"
] | 2 | 2021-08-19T14:59:36.000Z | 2021-08-19T21:43:01.000Z | README.md | diegoportela99/Job-Scraper | 1f400f366cb3c7116632b76b0749e3d9a68992ab | [
"MIT"
] | 1 | 2021-08-19T15:12:47.000Z | 2021-08-19T15:12:47.000Z | # Job-Scraper 🕸️
Designed for the data extraction on the indeed job hosted website [Indeed.com.au](https://au.indeed.com/), however scalable to be used on other websites
The program is written in python 3.
## Features 🌟
* Active Proxy Hopping
* Multi-Threaded Proxy Checking
* CSV Local Data Store
## How to run the code 🚀
```diff
+ THIS PROGRAM IS ONLY FOR EDUCATIONAL PURPOSES AND WAS NOT INTENDED FOR MALICIOUS OR SPITEFUL PURPOSES
```
It's very easy you just need to do the following below!
1. Run requirements.txt
```
python install -r requirements.txt
```
2. run python indeed_scraper
```
python indeed_scraper.py
```
### Current Issues
The program does not currently work for other hosted websites as it is hard coded to pull date from indeed, future requirements would be to add an automated version for extrating the text from each endpoint.
| 27.588235 | 208 | 0.733475 | eng_Latn | 0.957739 |
d5e073c808357221d02ebfec9d7f72cd369db886 | 459 | md | Markdown | ed/r/rpc/README.md | cn007b/stash | bae604d3056f09b9b6c6b3e0282f02c829801f5c | [
"MIT"
] | null | null | null | ed/r/rpc/README.md | cn007b/stash | bae604d3056f09b9b6c6b3e0282f02c829801f5c | [
"MIT"
] | null | null | null | ed/r/rpc/README.md | cn007b/stash | bae604d3056f09b9b6c6b3e0282f02c829801f5c | [
"MIT"
] | 1 | 2021-11-26T05:40:08.000Z | 2021-11-26T05:40:08.000Z | RPC (Remote Procedure Call)
-
RPC - interprocess communication technique.
May work over TCP, HTTP, etc.
Problems:
* How should the client react if there are no servers running or RPC server is down for a long time?
* Should a client have some kind of timeout for the RPC?
* If the server malfunctions and raises an exception, should it be forwarded to the client?
* Protecting against invalid incoming messages (eg checking bounds, type) before processing.
| 38.25 | 100 | 0.779956 | eng_Latn | 0.997215 |
d5e0857bbe2c8fedbd7f13e4803207501f416d66 | 190 | md | Markdown | episodes/327.md | BoyanTodorov/Ognena-Pustinya | 8a184c1c5894a81049e9fef999a95cca92384804 | [
"WTFPL"
] | null | null | null | episodes/327.md | BoyanTodorov/Ognena-Pustinya | 8a184c1c5894a81049e9fef999a95cca92384804 | [
"WTFPL"
] | null | null | null | episodes/327.md | BoyanTodorov/Ognena-Pustinya | 8a184c1c5894a81049e9fef999a95cca92384804 | [
"WTFPL"
] | null | null | null | ## 327.
Замаян от гъстите облаци лютив пушек, падаш на земя пред
пламтящата гора. Последното, което чуваш, са злобни крясъци на
войниците.
Загиваш тук и задачата ти ще остава неизпълнена.
| 23.75 | 62 | 0.784211 | bul_Cyrl | 0.999952 |
d5e17c7af97e466a60b75044d4762212e6d0ccfc | 4,526 | md | Markdown | articles/storage/common/storage-account-manage.md | ianychoi/azure-docs.ko-kr | e8831792859f1af945f9036f5ff75292892cdc88 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/storage/common/storage-account-manage.md | ianychoi/azure-docs.ko-kr | e8831792859f1af945f9036f5ff75292892cdc88 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/storage/common/storage-account-manage.md | ianychoi/azure-docs.ko-kr | e8831792859f1af945f9036f5ff75292892cdc88 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Azure Portal - Azure Storage에서 스토리지 계정 설정 관리 | Microsoft Docs
description: Azure Portal에서 액세스 제어 설정 구성, 계정 액세스 키 재생성, 액세스 계층 변경 또는 계정에서 사용하는 복제 유형 수정을 포함하여 저장소 계정 설정을 관리하는 방법에 대해 알아봅니다. 또한 포털에서 저장소 계정을 삭제하는 방법도 알아봅니다.
services: storage
author: tamram
ms.service: storage
ms.topic: article
ms.date: 03/05/2019
ms.author: tamram
ms.openlocfilehash: fa574558afeec5a7706482a142c0187e6a34bdb3
ms.sourcegitcommit: 3102f886aa962842303c8753fe8fa5324a52834a
ms.translationtype: MT
ms.contentlocale: ko-KR
ms.lasthandoff: 04/23/2019
ms.locfileid: "61484277"
---
# <a name="manage-storage-account-settings-in-the-azure-portal"></a>Azure Portal에서 저장소 계정 설정 관리
저장소 계정에 대한 다양한 설정은 [Azure Portal](https://portal.azure.com)에서 사용할 수 있습니다. 이 문서에서는 이러한 설정 및 해당 설정을 사용하는 방법에 대해 설명합니다.
## <a name="access-control"></a>액세스 제어
Azure Storage Blob storage 및 Queue storage를 통해 역할 기반 액세스 제어 (RBAC)에 대 한 Azure Active Directory를 사용 하 여 인증을 지원합니다. Azure AD로 인증 하는 방법에 대 한 자세한 내용은 참조 하세요. [Authenticate 권한을 Azure blob 및 Azure Active Directory를 사용 하 여 큐](storage-auth-aad.md)합니다.
Azure Portal의 **액세스 제어** 설정은 RBAC 역할을 사용자, 그룹, 서비스 주체 및 관리 ID에 할당하는 간단한 방법을 제공합니다. RBAC 역할을 할당 하는 방법에 대 한 자세한 내용은 참조 하세요. [RBAC 사용 하 여 blob 및 큐 데이터에 대 한 관리 액세스 권한을](storage-auth-aad-rbac.md)합니다.
> [!NOTE]
> Azure AD 자격 증명을 통한 사용자 또는 애플리케이션 권한 부여는 다른 인증 수단보다 보안 수준이 높고 사용이 간편합니다. 애플리케이션에서 공유 키 인증을 계속 사용할 수 있는 동안 Azure AD를 사용하면 코드에서 계정 액세스 키를 저장하지 않아도 됩니다. SAS(공유 액세스 서명)를 계속 사용하여 저장소 계정의 리소스에 세분화된 액세스 권한을 부여할 수도 있습니다. 하지만 Azure AD에서는 SAS 토큰을 관리하거나 손상된 SAS를 해지하는 방법을 걱정할 필요 없이 유사한 기능을 제공합니다.
## <a name="tags"></a>태그들
Azure Storage는 사용자 지정된 분류를 사용하여 Azure 리소스 구성을 위한 Azure Resource Manager 태그를 지원합니다. 저장소 계정에 태그를 적용하여 논리적 방식으로 구독 내에서 그룹화할 수 있습니다.
저장소 계정에서 태그 이름은 128자로 제한되며 태그 값은 256자로 제한됩니다.
자세한 내용은 [태그를 사용하여 Azure 리소스 구성](../../azure-resource-manager/resource-group-using-tags.md)을 참조하세요.
## <a name="access-keys"></a>액세스 키
저장소 계정을 만들 때 Azure는 두 개의 512비트 저장소 계정 액세스 키를 생성합니다. 이러한 키를 사용하여 공유 키를 통해 저장소 계정에 대한 액세스 권한을 부여할 수 있습니다. 애플리케이션을 중단하지 않고 키를 회전 및 다시 생성할 수 있으며 정기적으로 그렇게 하는 것이 좋습니다.
[!INCLUDE [storage-account-key-note-include](../../../includes/storage-account-key-note-include.md)]
### <a name="view-and-copy-access-keys"></a>액세스 키 보기 및 복사
저장소 계정 자격 증명을 보려면:
1. [Azure Portal](https://portal.azure.com)로 이동합니다.
2. 저장소 계정을 찾습니다.
3. 저장소 계정 개요의 **설정** 섹션에서 **액세스 키**를 선택합니다. 계정 액세스 키는 물론 각 키의 전체 연결 문자열이 나타납니다.
4. **key1** 아래에서 **키** 값을 찾고, **복사** 단추를 클릭하여 계정 키를 복사합니다.
5. 또는 전체 연결 문자열을 복사할 수 있습니다. **key1** 아래에서 **연결 문자열** 값을 찾고, **복사** 단추를 클릭하여 연결 문자열을 복사합니다.
### <a name="regenerate-access-keys"></a>액세스 키 다시 생성
저장소 계정을 안전하게 유지하려면 액세스 키를 정기적으로 다시 생성하는 것이 좋습니다. 키를 회전할 수 있도록 두 개의 액세스 키가 할당됩니다. 키를 회전할 경우, 애플리케이션이 프로세스 전체에 대해 Azure Storage에 대한 액세스를 유지하는지 확인해야 합니다.
> [!WARNING]
> 액세스 키를 다시 생성하면 저장소 계정 키에 종속된 모든 애플리케이션과 Azure 서비스에 영향을 미칠 수 있습니다. 계정 키를 사용하여 스토리지 계정에 액세스하는 모든 클라이언트는 미디어 서비스, 클라우드, 데스크톱 및 모바일 응용 프로그램, Azure Storage용 그래픽 사용자 인터페이스 응용 프로그램(예: [Azure Storage Explorer](https://azure.microsoft.com/features/storage-explorer/))을 포함하여 새로운 키를 사용하도록 업데이트되어야 합니다.
저장소 계정 키를 회전하려면 다음 프로세스를 따릅니다.
1. 보조 키를 사용 하도록 응용 프로그램 코드에서 연결 문자열을 업데이트합니다.
2. 저장소 계정의 기본 액세스 키를 다시 생성합니다. Azure Portal의 **액세스 키** 블레이드에서 **Key1 다시 생성**을 클릭하고 **예**를 클릭하여 새 키를 생성하려는 것을 확인합니다.
3. 새 기본 액세스 키를 참조하도록 코드의 연결 문자열을 업데이트합니다.
4. 같은 방식으로 보조 액세스 키를 다시 생성합니다.
## <a name="account-configuration"></a>계정 구성
저장소 계정을 만든 후 해당 구성을 수정할 수 있습니다. 예를 들어, 데이터를 복제하는 방식을 변경하거나 계정의 액세스 계층을 핫(Hot)에서 쿨(Cool)로 변경할 수 있습니다. [Azure Portal](https://portal.azure.com)에서 저장소 계정으로 이동하고 **설정**에서 **구성**을 클릭하여 계정 구성을 확인하거나 변경합니다.
저장소 계정 구성 변경으로 추가 비용이 발생할 수 있습니다. 자세한 내용은 [Azure Storage 가격 책정](https://azure.microsoft.com/pricing/details/storage/) 페이지를 참조하세요.
## <a name="delete-a-storage-account"></a>저장소 계정 삭제
더 이상 사용하지 않는 저장소 계정을 제거하려면 [Azure 포털](https://portal.azure.com)의 저장소 계정으로 이동하여 **삭제**를 클릭합니다. 저장소 계정 삭제는 계정의 모든 데이터를 포함한 전체 계정을 삭제합니다.
> [!WARNING]
> 삭제된 저장소 계정을 복원할 수 없거나 삭제 전에 포함된 콘텐츠를 검색할 수 없습니다. 계정을 삭제하기 전에 저장할 내용을 백업했는지 확인합니다. 또한 해당 계정의 리소스에 대해 true를 유지합니다. Blob, 테이블, 큐 또는 파일을 삭제하면 영구적으로 삭제됩니다.
>
Azure 가상 머신과 연결된 저장소 계정을 삭제하려고 하는 경우 아직 사용 중인 저장소 계정에 대한 오류가 발생할 수 있습니다. 이 오류의 문제를 해결하는 도움말은 [저장소 계정을 삭제할 때 오류 문제 해결](../common/storage-resource-manager-cannot-delete-storage-account-container-vhd.md)을 참조하세요.
## <a name="next-steps"></a>다음 단계
- [Azure Storage 계정 개요](storage-account-overview.md)
- [저장소 계정을 만드는](storage-quickstart-create-account.md)
| 50.853933 | 293 | 0.717852 | kor_Hang | 1.00001 |
d5e24230c272e27577bccc8894d274467a8d0c19 | 781 | md | Markdown | README.md | lksengineer/premios-platzi | 9a6156846aaf56d60caead2715540fddbb8a52c9 | [
"OML"
] | 2 | 2022-03-05T00:17:18.000Z | 2022-03-16T15:55:23.000Z | README.md | lksengineer/premios-platzi | 9a6156846aaf56d60caead2715540fddbb8a52c9 | [
"OML"
] | null | null | null | README.md | lksengineer/premios-platzi | 9a6156846aaf56d60caead2715540fddbb8a52c9 | [
"OML"
] | null | null | null | # Platzi adwards web app
Platzi awards is an web app in which users can vote for favorite courses, teachers and school within the web platform
## Installation
Can **_clone_** the repository with **SSH**
`$ git clone [email protected]:lksengineer/premios-platzi.git`
Or **_clone_** the repository with **HTTPS**
`$ git clone https://github.com/lksengineer/premios-platzi.git`
Or **_donwload_** in **.zip** format.
`https://github.com/lksengineer/premios-platzi/archive/refs/heads/master.zip`
## How to use
Select one of the answer options for each question. Click vote. And you will have already voted for your favorite school, teacher and course in the Platzi Awards
## How to contribute
You can **_create_** a **pull request** to the project
## Licencia
Open Sourcee
| 24.40625 | 161 | 0.743918 | eng_Latn | 0.975495 |
d5e3244e0d649306a82c58a06f93718ba93f6bfe | 15,151 | md | Markdown | articles/traffic-manager/traffic-manager-endpoint-types.md | OpenLocalizationTestOrg/azure-docs-pr16_de-DE | bf18172a4f9060051b3861ff8930d9f0303f7f10 | [
"CC-BY-3.0",
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/traffic-manager/traffic-manager-endpoint-types.md | OpenLocalizationTestOrg/azure-docs-pr16_de-DE | bf18172a4f9060051b3861ff8930d9f0303f7f10 | [
"CC-BY-3.0",
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/traffic-manager/traffic-manager-endpoint-types.md | OpenLocalizationTestOrg/azure-docs-pr16_de-DE | bf18172a4f9060051b3861ff8930d9f0303f7f10 | [
"CC-BY-3.0",
"CC-BY-4.0",
"MIT"
] | null | null | null | <properties
pageTitle="Typen von Datenverkehr Manager Endpunkt | Microsoft Azure"
description="Dieser Artikel erläutert die verschiedene Arten von Endpunkten, die mit Azure Datenverkehr Manager verwendet werden können"
services="traffic-manager"
documentationCenter=""
authors="sdwheeler"
manager="carmonm"
editor=""
/>
<tags
ms.service="traffic-manager"
ms.devlang="na"
ms.topic="article"
ms.tgt_pltfrm="na"
ms.workload="infrastructure-services"
ms.date="10/11/2016"
ms.author="sewhee"
/>
# <a name="traffic-manager-endpoints"></a>Datenverkehr Manager Endpunkte
Microsoft Azure Datenverkehr-Manager können Sie steuern, wie Netzwerkdatenverkehr an Anwendung Bereitstellungen in verschiedenen Rechenzentren ausgeführt verteilt ist. Sie konfigurieren jede Anwendung Bereitstellung als 'Endpunkt' in den Datenverkehr Manager. Wenn Datenverkehr Manager eine DNS-eingeht, wählt es einen Endpunkt in der DNS-Antwort zurückgegeben. Datenverkehr Manager basiert die Auswahl auf den aktuellen Status der Endpunkt und den Datenverkehr-routing Methode. Weitere Informationen finden Sie unter [Funktionsweise von Datenverkehr-Manager](traffic-manager-how-traffic-manager-works.md).
Es gibt drei Arten von Endpunkt von Datenverkehr Manager unterstützt:
- **Azure Endpunkte** werden für in Azure gehostete Dienste verwendet.
- **Externe Endpunkte** werden für außerhalb Azure, entweder lokal oder mit einem anderen Hostinganbieter gehostet Dienste verwendet.
- **Endpunkte geschachtelt** werden verwendet, um die Datenverkehr Manager Profile zum Erstellen von flexibler Datenverkehr-routing Phishingversuchen zur Unterstützung von der Anforderungen größere und komplexere Bereitstellungen kombinieren.
Es ist keine Einschränkung wie die Endpunkte des verschiedene Typen in einem einzigen Datenverkehr Manager Profil kombiniert werden. Jedes Profil kann beliebige Kombination von Endpunkttypen enthalten.
Den folgenden Abschnitten wird jeder Endpunkttyp ausführlicher beschrieben.
## <a name="azure-endpoints"></a>Azure Endpunkte
Azure Endpunkte werden zur Azure-basierte Dienste in den Datenverkehr Manager verwendet. Die folgenden Azure Ressourcentypen werden unterstützt:
- 'Klassisch' IaaS virtuellen Computern und PaaS cloud Services.
- Web Apps
- Öffentl.IP Ressourcen (die mit virtuellen Computern verbunden werden direkt oder über ein Lastenausgleich Azure). Die Öffentl.IP müssen einen DNS-Namen zugewiesen, in einem Manager Datenverkehr Profil verwendet werden soll.
Öffentl.IP Ressourcen sind Azure Ressourcenmanager Ressourcen. Sie sind nicht in der klassischen Bereitstellungsmodell vorhanden. Daher sind nur in unterstützten Datenverkehr Vorgesetzten Azure Ressourcenmanager Erfahrung. Andere Endpunkttypen werden per Ressourcenmanager, und das Bereitstellungsmodell klassischen unterstützt.
Bei der Verwendung von Azure Endpunkte erkennt Datenverkehr Manager, wenn eine 'Klassisch' IaaS VM, Cloud-Dienst oder eine Web App angehalten und gestartet wird. Dieser Status wird in den Endpunkt Status angezeigt. Details finden Sie unter [den Datenverkehr Manager Endpunkt überwachen](traffic-manager-monitoring.md#endpoint-and-profile-status) . Der zugrunde liegenden angehalten ist, führt den Datenverkehr Manager keine integritätsprüfungen Endpunkt oder direkte Datenverkehr an den Endpunkt aus. Kein Datenverkehr-Manager der angehaltenen Instanz Abrechnung Ereignisse auftreten. Wenn der Dienst neu gestartet wird, ist Abrechnung Lebensläufe und den Endpunkt zum Empfangen von Datenverkehr berechtigt. Diese Erkennung gilt nicht für Öffentl.IP Endpunkte.
## <a name="external-endpoints"></a>Externe Endpunkte
Externe Endpunkte sind für Dienste außerhalb Azure verwendet. Beispielsweise ein Dienst lokal gehostet oder mit einem anderen Anbieter. Externe Endpunkte können einzeln verwendet oder mit Azure Endpunkten in demselben Datenverkehr Manager Profil kombiniert werden. Kombinieren von Azure Endpunkte mit externen Endpunkten ermöglicht verschiedenen Szenarios:
- Verwenden Sie entweder eine aktive oder Aktiv / Passiv Failover-Modell Azure höhere Redundanz für eine vorhandene Anwendung lokal bereitgestellt.
- Erweitern Sie zum Verringern der Anwendung Wartezeit für Benutzer auf der ganzen Welt eine vorhandene lokale Anwendung zu zusätzlichen geografischen Standorten in Azure ein. Weitere Informationen finden Sie unter [Datenverkehr Manager "Leistung" Daten-routing](traffic-manager-routing-methods.md#performance-traffic-routing-method).
- Verwenden von Azure Bereitstellung von zusätzlicher Kapazität für eine vorhandene lokale Anwendung, fortlaufend oder als 'Burst Cloud' Lösung für eine Sammlung Nachfrage entsprechen.
In bestimmten Fällen, es ist sinnvoll, externe Endpunkte verwenden, um Azure Dienste verweisen (Beispiele finden Sie in den [häufig gestellte Fragen](#faq)). In diesem Fall sind integritätsprüfungen bei der Azure Endpunkte Tarifs nicht externe Endpunkte in Rechnung gestellt. Jedoch im Gegensatz zu Azure Endpunkte, wenn Sie beenden oder löschen den zugrunde liegenden Dienst Gesundheit überprüfen Abrechnung verwendet, bis Sie deaktivieren oder löschen Sie den Endpunkt im Datenverkehr-Manager.
## <a name="nested-endpoints"></a>Geschachtelte Endpunkte
Geschachtelte Endpunkte Kombinieren mehrerer Datenverkehr Manager Profile um flexible Datenverkehr-routing Phishingversuchen erstellen und die Anforderungen größeren, komplexen Bereitstellungen unterstützen. Mit Endpunkten geschachtelt wird ein Profil 'Kind' als Endpunkt eines Profils 'Parent' hinzugefügt. Das untergeordnete und das übergeordnete Profile können andere Endpunkte eines beliebigen Typs, einschließlich andere geschachtelte Profile enthalten. Weitere Informationen finden Sie unter [geschachtelte Datenverkehr-Manager-Profilen](traffic-manager-nested-profiles.md).
## <a name="web-apps-as-endpoints"></a>Web Apps als Endpunkte
Einige weitere Aspekte sollten bei Web Apps als Endpunkte in den Datenverkehr Manager konfigurieren:
1. Nur Web Apps auf "Standard" SKU oder höher, die für die Verwendung mit den Datenverkehr Manager berechtigt sind. Hinzufügen einer Web-App von einer niedrigere SKU Versuche fehl. Herunterstufen von der SKUs einer vorhandenen Web App führt in den Datenverkehr Manager Datenverkehr in die Web App nicht mehr zu senden.
2. Wenn Sie ein Endpunkt eine HTTP-Anforderung empfängt, wird 'Host' Header in der Besprechungsanfrage um zu bestimmen, welche Web App die Anfrage service sollte. Der Host-Header enthält den DNS-Namen verwendet, um die Anfrage, beispielsweise 'contosoapp.azurewebsites.net' einleiten. Wenn Sie einen anderen Namen für die DNS-Web-App verwenden zu können, muss der DNS-Name als einen benutzerdefinierten Domänennamen für die App registriert sein. Wenn Sie einen Endpunkt Web App als Azure Endpunkt hinzufügen, wird der DNS-Manager Datenverkehr Profilname automatisch für die App registriert. Diese Registrierung wird automatisch entfernt, wenn Sie der Endpunkt gelöscht wird.
3. Jedes Profil Datenverkehr Manager kann jeder Region Azure höchstens eine Web App-Endpunkt aufweisen. Wenn Sie für diese Einschränkung umgehen können Sie eine Web App als externe Endpunkt konfigurieren. Weitere Informationen finden Sie unter den [häufig gestellte Fragen](#faq).
## <a name="enabling-and-disabling-endpoints"></a>Aktivieren und Deaktivieren von Endpunkten
Deaktivieren von außen liegenden Tabellenblättern in den Datenverkehr Manager kann nützlich sein, den Datenverkehr vorübergehend von außen liegenden Tabellenblättern zu entfernen, die Wartungsmodus oder, die erneut bereitgestellt wird. Nachdem Sie der Endpunkt erneut ausgeführt wird, kann es wieder aktiviert werden.
Endpunkte können aktiviert und deaktiviert, über den Datenverkehr Manager-Portal PowerShell, CLI oder REST-API, die sowohl Ressourcenmanager und das Bereitstellungsmodell klassischen unterstützt werden.
>[AZURE.NOTE] Deaktivieren einen Endpunkt Azure hat nichts mit Bereitstellungszustand in Azure. Ein Azure Service (z. B. bleibt eines virtuellen Computers oder Web App ausgeführt wird und zum Empfang von Datenverkehr, auch wenn in den Datenverkehr Manager deaktiviert. Datenverkehr kann direkt an die Instanz des Diensts und nicht über die DNS-Manager Datenverkehr Profilname berücksichtigt werden. Weitere Informationen finden Sie unter [Funktionsweise der Datenverkehr-Manager](traffic-manager-how-traffic-manager-works.md).
Die aktuelle Berechtigung jedes Endpunkts Datenverkehr empfangen hängt die folgenden Faktoren aus:
- Das Profil Status (aktiviert/deaktiviert)
- Der Endpunkt Status (aktiviert/deaktiviert)
- Die Ergebnisse der Gesundheit für diesen Endpunkt überprüft
Details finden Sie unter [den Datenverkehr Manager Endpunkt überwachen](traffic-manager-monitoring.md#endpoint-and-profile-status).
>[AZURE.NOTE] Da Ebene der DNS-Manager Datenverkehr funktioniert, kann es nicht vorhandene Verbindungen an einem beliebigen Endpunkt beeinflussen. Wenn Sie ein Endpunkt nicht verfügbar ist, weist Datenverkehr Manager neue Verbindungen mit einem anderen Endpunkt aus. Der Host hinter den Endpunkt deaktiviert oder fehlerhaft kann jedoch weiterhin Verkehr über vorhandene Verbindungen erhalten, bis Sie diese Sitzungen beendet werden. Applikationen sollte die Sitzungsdauer, um den Datenverkehr in abzuleiten aus vorhandene Verbindungen zulassen beschränken.
Wenn alle Endpunkte in einem Profil deaktiviert sind, oder wenn das Profil selbst deaktiviert ist, klicken Sie dann den Datenverkehr Manager eine 'NXDOMAIN' Antwort an eine neue DNS-Abfrage sendet.
## <a name="faq"></a>Häufig gestellte Fragen
### <a name="can-i-use-traffic-manager-with-endpoints-from-multiple-subscriptions"></a>Kann ich den Datenverkehr Manager mit Endpunkten aus mehrere Abonnements verwenden?
Es ist nicht möglich, mit Azure Web Apps, Endpunkte aus mehrere Abonnements verwenden. Azure Web Apps erfordert, dass alle benutzerdefinierten Domänennamen mit Web Apps verwendet nur innerhalb eines einzelnen Abonnements verwendet wird. Es ist nicht möglich, Web Apps aus mehreren Abonnements mit dem gleichen Domänennamen zu verwenden.
Für andere Endpunkttypen ist es möglich, den Datenverkehr Manager mit Endpunkten aus mehr als einem Abonnement verwenden. Wie Sie den Datenverkehr Manager konfigurieren, hängt davon ab, ob Sie das Bereitstellungsmodell klassischen oder die Ressourcenmanager Oberfläche verwenden.
- In der Ressourcenmanager Endpunkte aus einem beliebigen Abonnement können als nach den Datenverkehr Manager hinzugefügt werden, solange die Person, die Konfiguration des Profils Datenverkehr Manager Lesezugriff auf den Endpunkt verfügt. Diese Berechtigungen können mit [Azure Ressourcenmanager rollenbasierte Access-Steuerelements (RBAC)](../active-directory/role-based-access-control-configure.md)erteilt werden.
- In der klassischen Bereitstellung Modell-Schnittstelle erfordert Datenverkehr Manager an, dass Cloud Services oder Web Apps konfiguriert als Azure Endpunkte im selben Abonnement als den Datenverkehr-Manager-Profil befinden. Cloud-Dienstendpunkte in anderen Abonnements können mit den Datenverkehr Manager als 'externe' Endpunkte hinzugefügt werden. Diese externen Endpunkte als Azure Endpunkte, anstatt die externe Rate in Rechnung gestellt werden.
### <a name="can-i-use-traffic-manager-with-cloud-service-staging-slots"></a>Kann ich den Datenverkehr Manager mit der Cloud-Dienst 'Staging' verwenden?
Ja. Cloud-Dienst staging' Steckplätze kann in den Datenverkehr Manager als externe Endpunkte konfiguriert sein. Integritätsprüfungen werden weiterhin Rate Azure Endpunkte belastet. Da der externe Endpunkttyp verwendet wird, werden Änderungen an der zugrunde liegenden Dienst nicht automatisch übernommen. Mit externen Endpunkten kann nicht Datenverkehr Manager erkennen, wenn die Cloud-Dienst beendet oder gelöscht wird. Daher weiterhin den Datenverkehr-Manager für integritätsprüfungen Abrechnung bis der Endpunkt deaktiviert oder gelöscht wird.
### <a name="does-traffic-manager-support-ipv6-endpoints"></a>Unterstützt den Datenverkehr Manager IPv6 Endpunkte?
Datenverkehr Manager bietet aktuell keine IPv6 addressible Namenserver. Datenverkehr Manager kann jedoch weiterhin von IPv6-Clients Herstellen einer Verbindung mit IPv6 Endpunkte verwendet werden. Ein Client werden keine DNS-Anfragen direkt auf den Datenverkehr Manager gestellt. In diesem Fall verwendet der Client einen rekursive DNS-Dienst an. Ein reine IPv6-Client sendet Anfragen an die rekursive DNS-Dienst mit IPv6. Klicken Sie dann sollte der Dienst rekursive wenden Sie sich an den Datenverkehr Manager Namenserver IPv4 verwenden können.
Datenverkehr Manager reagiert mit der DNS-Name des Endpunkts an. Um einen Endpunkt IPv6 unterstützen, muss der Endpunkt DNS-Name auf die IPv6-Adresse zeigen DNS AAAA Datensatz vorhanden. Integritätsprüfungen Datenverkehr Manager unterstützt nur IPv4-Adressen. Der Dienst muss einen Endpunkt IPv4 auf dem gleichen DNS-Namen verfügbar zu machen.
### <a name="can-i-use-traffic-manager-with-more-than-one-web-app-in-the-same-region"></a>Kann ich den Datenverkehr Manager mit mehr als einem Web-App in der gleichen Region verwenden?
Normalerweise ist Datenverkehr Manager verwendet, um den Datenverkehr in die Anwendung bereitgestellt, die in unterschiedlichen Regionen direkte. Allerdings können sie auch verwendet werden, wo eine Anwendung mehrere Bereitstellung in derselben Region hat. Die Endpunkte Datenverkehr Manager Azure lässt nicht mehr als eine Web App-Endpunkt aus derselben Azure Region das gleiche Datenverkehr Manager Profil hinzugefügt werden.
Die folgenden Schritte bieten für diese Einschränkung umgehen:
1. Überprüfen Sie, dass Ihre Endpunkte in anderen Web app'skalieren Einheiten' sind. Ein Domänenname muss einer einzelnen Website in einem angegebenen Mengen Einheit zuordnen. Daher freigeben nicht zwei Web Apps in derselben Skala Einheit Datenverkehr Manager Profil.
2. Fügen Sie Ihres Domänennamens Eitelkeit als eine benutzerdefinierte Hostname bei jeder Web App an hinzu. Jede Web-App muss sich in einer anderen Maßstab Einheit. Alle Web Apps müssen den gleichen Abonnement gehören.
3. Hinzufügen einer (und nur eine) Web App-Endpunkt zu Ihrem Profil Datenverkehr Manager als Azure Endpunkt.
4. Hinzufügen von jede zusätzliche Web App-Endpunkt zu Ihrem Profil Datenverkehr Manager als externe Endpunkt. Externe Endpunkte können nur in das Modell zur Bereitstellung von Ressourcenmanager hinzugefügt werden.
5. Erstellen Sie einen DNS-CNAME-Eintrag in Ihrer Eitelkeit-Domäne, die auf Ihre Datenverkehr Manager DNS-Profilname verweist (<>.... trafficmanager.net).
6. Zugriff auf Ihre Website über den Eitelkeit Domänennamen nicht den Datenverkehr Manager DNS-Profilnamen ein.
## <a name="next-steps"></a>Nächste Schritte
- Erfahren Sie, [den Datenverkehr Manager wie funktioniert](traffic-manager-how-traffic-manager-works.md).
- Informationen Sie zu den Datenverkehr Manager [Endpunkt Überwachung und automatisches Failover](traffic-manager-monitoring.md).
- Informationen Sie zu den Datenverkehr Manager [Datenverkehr Weiterleitung Methoden](traffic-manager-routing-methods.md).
| 117.449612 | 760 | 0.830506 | deu_Latn | 0.99896 |
d5e415b890696ea1b1efc64ee7428bd72c7dec75 | 6,173 | md | Markdown | windows/client-management/mdm/enterprisedesktopappmanagement2-xsd.md | alhopper-msft/windows-itpro-docs | aa750cb58f34fe45770d24f13648ada9a3100f5b | [
"CC-BY-4.0",
"MIT"
] | null | null | null | windows/client-management/mdm/enterprisedesktopappmanagement2-xsd.md | alhopper-msft/windows-itpro-docs | aa750cb58f34fe45770d24f13648ada9a3100f5b | [
"CC-BY-4.0",
"MIT"
] | null | null | null | windows/client-management/mdm/enterprisedesktopappmanagement2-xsd.md | alhopper-msft/windows-itpro-docs | aa750cb58f34fe45770d24f13648ada9a3100f5b | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: EnterpriseDesktopAppManagement XSD
description: This topic contains the XSD schema file for the EnterpriseDesktopAppManagement configuration service provider’s DownloadInstall parameter.
ms.assetid: 60980257-4F48-4A68-8E8E-1EF0A3F090E2
ms.author: maricia
ms.topic: article
ms.prod: w10
ms.technology: windows
author: nickbrower
---
# EnterpriseDesktopAppManagement XSD
This topic contains the XSD schema file for the EnterpriseDesktopAppManagement configuration service provider’s DownloadInstall parameter.
``` syntax
<?xml version="1.0" encoding="utf-8"?>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="Data">
<xs:complexType>
<xs:sequence>
<xs:element name="MsiInstallJob">
<xs:complexType>
<xs:sequence>
<xs:element name="Product">
<xs:complexType>
<xs:sequence>
<xs:element name="Download">
<xs:complexType>
<xs:sequence>
<xs:element name="ContentURLList">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="ContentURL" type="xs:string" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Validation">
<xs:complexType>
<xs:sequence>
<xs:element name="FileHash" type="xs:string" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Enforcement">
<xs:complexType>
<xs:sequence>
<xs:element name="CommandLine" type="xs:string" />
<xs:element name="TimeOut" type="xs:unsignedByte" />
<xs:element name="RetryCount" type="xs:unsignedByte" />
<xs:element name="RetryInterval" type="xs:unsignedByte" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="Version" type="xs:string" use="required" />
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="id" type="xs:string" use="required" />
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
```
The following table describes the various elements and attributes of the XSD file:
| Name | Description |
|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| MsiInstallJob | Root element |
| id | The application identifier for the application being installed. |
| Product | Child element of MsiInstallJob |
| Version | String representation of the application version |
| Download | Child element of Product. Container for download configuration information. |
| ContentURLList | Child element of Download. Contains list of one or more content download URL locators in the form of ContentURL elements. |
| ContentURL | Location that content should be downloaded from. Must be a property formatted URL that points to the MSI file. |
| Validation | Contains information used to validate content authenticity. |
| FileHash | SHA256 hash value of file content. |
| Enforcement | Installation properties to be used when installing this MSI |
| CommandLine | Command-line options to be used when calling MSIEXEC.exe |
| Timeout | Amount of time in minutes that the installation process can run before the installer considers the installation may have failed and no longer monitors the installation operation. |
| RetryCount | Number of times the download and installation operation will be retried before the installation will be marked as failed. |
| RetryInterval | Amount of time in minutes between retry operations. |
| 58.790476 | 199 | 0.409687 | eng_Latn | 0.822848 |
d5e45904d6467bb49b4d6f9c6ad9f22f59d0eb9a | 8,359 | md | Markdown | docs/vs-2015/data-tools/data-user-interface-elements.md | Ash-Shaun/visualstudio-docs | 787c3856e6cbfc65d97612854fc093785dc5573a | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-04-06T02:01:40.000Z | 2019-04-06T02:01:40.000Z | docs/vs-2015/data-tools/data-user-interface-elements.md | Ash-Shaun/visualstudio-docs | 787c3856e6cbfc65d97612854fc093785dc5573a | [
"CC-BY-4.0",
"MIT"
] | 1 | 2018-10-08T17:51:50.000Z | 2018-10-08T17:51:50.000Z | docs/vs-2015/data-tools/data-user-interface-elements.md | Ash-Shaun/visualstudio-docs | 787c3856e6cbfc65d97612854fc093785dc5573a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "Data User Interface Elements | Microsoft Docs"
ms.custom: ""
ms.date: "2018-06-30"
ms.prod: "visual-studio-dev14"
ms.reviewer: ""
ms.suite: ""
ms.tgt_pltfrm: ""
ms.topic: "article"
f1_keywords:
- "vs.data.tablemappings"
- "vs.datasource.choosebindingsourcedialog"
- "vs.datasource.choosedatasourceinstancedlg"
- "vs.data.editrelation"
- "DSD_EditMultiKey"
- "vs.datasource.RealtionBuilder"
- "vs.xmldesigner.editkey"
- "vs.xmldesigner.choosekey"
- "vs.data.generatedataset"
- "vs.data.configurationerror"
- "vs.data.DSD_MissingConnections_Message"
- "vs.datasource.choosedesigndatasourcedlg"
- "vs.data.datapreview"
- "vs.data.editforeignkeyconstraint"
- "vs.datasource.choosedataconectordialog"
- "vs.data.dataadapterpreview"
- "vs.data.configurationwizard"
- "vs.data.datapreviewdialog"
- "DSD_EditMultiKeyHelpID"
- "vs.data.advancedoptions"
- "vs.data.previewscript"
- "vs.data.datasourcelogin"
- "vs.syncdesigner.syncnowconflictiondialog"
dev_langs:
- "VB"
- "CSharp"
- "C++"
- "aspx"
helpviewer_keywords:
- "dialog boxes, data"
- "data [Visual Studio], dialog boxes"
ms.assetid: 90943baf-5bd1-4eef-927f-f82485979fde
caps.latest.revision: 18
author: gewarren
ms.author: gewarren
manager: "ghogen"
robots: noindex,nofollow
---
# Data User Interface Elements
[!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
This section contains information about all the dialog boxes and wizards that you use when designing data access in your [!INCLUDE[vbprvb](../includes/vbprvb-md.md)] or Visual C# applications.
[!INCLUDE[note_settings_general](../includes/note-settings-general-md.md)]
## In This Section
[Data Smart Tags](http://msdn.microsoft.com/en-us/1e0a848f-c57b-47ab-b884-eaaa40726f43)
Provides information on some smart tag commands that are available for data.
[Add Dataset Dialog Box](http://msdn.microsoft.com/en-us/0e03c0ff-212b-4bfa-ac51-3c2adb71ead0)
Puts an existing typed dataset or a new untyped dataset (an instance of the **System.Data.Dataset** class) onto a form or component.
[Advanced SQL Generation Options Dialog Box](http://msdn.microsoft.com/en-us/41420450-1ff4-4a1a-b85b-6f6901538fef)
Allows you to control how SQL statements or stored procedures are created for a data adapter by specifying options for updates, optimistic concurrency, and refreshing the dataset.
[Choose a Data Source Instance Dialog Box](http://msdn.microsoft.com/en-us/51c47f06-fdc5-453e-9178-0a5a2c5c9f34)
Allows you to select the desired dataset from a list of datasets in your project.
[Choose a Data Source to Merge with Dialog Box](http://msdn.microsoft.com/en-us/accafff7-f6bd-481c-a121-fe8a76cd681d)
Allows you to select which data source to merge with when multiple data sources are available.
[Choose Key Dialog Box](http://msdn.microsoft.com/en-us/4ddbfbb7-a80a-412a-b80d-291d86376ca3)
Allows you select a key when a column participates in a multi-key constraint.
[Collection Editors](http://msdn.microsoft.com/library/030095bd-fb9a-4b21-b628-fc1cc5985bb7)
Provides links to topics about different collection editors that allow you to create and edit individual members of a collection.
[Connections Missing](http://msdn.microsoft.com/en-us/bb9b2e12-7f76-4ee5-acbb-5d20116ee044)
Informs you when a dataset contains a reference to a connection string that is not in application settings.
[Data Adapter Configuration Error Dialog Box](http://msdn.microsoft.com/en-us/9ce65cd2-0c7d-4f51-8685-d68be5f3009b)
Displays one or more errors that occurred while Visual Studio was attempting to create an instance of a data adapter and set its properties.
[Data Adapter Configuration Wizard](http://msdn.microsoft.com/en-us/efff90cb-0e4c-4eb3-87dc-65dd9d418809)
Configures SQL commands or stored procedures that a data adapter uses to read data into a dataset from a database and write it back again. The topic describes how to run the wizard and what to do after the wizard has completed.
[Data Adapter Preview Dialog Box](http://msdn.microsoft.com/en-us/1f614cd3-4530-457e-84af-00ccbaea08cc)
Allows you to see how data will be filled into a dataset by a data adapter, which is useful for testing that the adapter is returning the data you expect, that table mappings work properly, and the effect of different parameter values.
[Data Source Login Dialog Box](http://msdn.microsoft.com/en-us/6f2d9a57-53c3-4841-bd37-a3643eb68d2e)
Allows you to request access to a data source (typically a database) for which you have not already been authenticated.
[DataSet Tab, Toolbox](http://msdn.microsoft.com/en-us/fa5f2d6f-924d-4262-ba1b-e9e7f90e7764)
Displays the objects you can add to a typed dataset.
[Do you want to include the password in the connection string Dialog Box](http://msdn.microsoft.com/en-us/193696a7-5213-4396-8328-05ac2df6ee94)
Allows you to control whether a password is embedded into the connection string.
[Edit Key Dialog Box](http://msdn.microsoft.com/en-us/f5c80e39-3a42-4284-b222-6ca009fd9675)
Allows you to define and edit keys.
[Foreign Key Constraint Dialog Box](http://msdn.microsoft.com/en-us/45d15629-1f4d-40a7-8708-c9ddfebedc1e)
Allows you to place a foreign key constraint on one or more columns in a dataset table that is related to another table.
[Generate Dataset Dialog Box](http://msdn.microsoft.com/en-us/c0efdbaf-13b1-4ee8-ade6-f8a784126cdc)
Allows you to generate a new typed dataset from information provided by one or more data adapters and to add tables to an existing dataset.
[Multiple BindingSources Dialog Box](http://msdn.microsoft.com/en-us/db76f70c-4fb5-479d-9b64-a67158d48f97)
Allows you to select which <xref:System.Windows.Forms.BindingSource> to use when more than one <xref:System.Windows.Forms.BindingSource> is available.
[Preview Data Dialog Box](http://msdn.microsoft.com/en-us/aa4f0d04-2695-4bb8-946d-54a97ae7287f)
Allows you to review the data returned by queries in your project.
[Preview SQL Script Dialog Box](http://msdn.microsoft.com/en-us/e9571e8b-821c-492d-9bc8-b44eba898bdd)
Appears as part of the [Data Adapter Configuration Wizard](http://msdn.microsoft.com/en-us/efff90cb-0e4c-4eb3-87dc-65dd9d418809) to allow you to see the SQL script the wizard will use to create stored procedures to read and write data.
[Relation Dialog Box](http://msdn.microsoft.com/en-us/ab8f4b0e-af4c-4725-a550-e2b2ebe43a02)
Allows you to create a relationship (a **DataRelation** object) that maintains information about parent-child records in two data tables in a dataset.
[Search Criteria Builder Dialog Box](http://msdn.microsoft.com/library/0b306b92-f35e-45ef-a4be-3f653cd00c3d)
Allows you to create a parameterized query on a data-bound Windows Form, and automatically add the controls required to run the query.
[Table Mappings Dialog Box](http://msdn.microsoft.com/en-us/fb4cec1e-f3c8-4773-b409-c2de15293fea)
Allows you to specify which columns in a database table or other data source are equivalent to columns in a dataset table.
[Unique Constraint Dialog Box](http://msdn.microsoft.com/en-us/e71a60d7-fae2-4bd0-a1e8-43aae351707d)
Allows you to place a unique constraint on one or more columns in a table in an untyped dataset.
## Related Sections
[Accessing Data](../data-tools/accessing-data-in-visual-studio.md)
Provides links to topics that describe how to access data in your Visual Basic and Visual C# applications.
## See Also
[Overview of Data Applications in Visual Studio](../data-tools/overview-of-data-applications-in-visual-studio.md)
[Connecting to Data in Visual Studio](../data-tools/connecting-to-data-in-visual-studio.md)
[Preparing Your Application to Receive Data](http://msdn.microsoft.com/library/c17bdb7e-c234-4f2f-9582-5e55c27356ad)
[Fetching Data into Your Application](../data-tools/fetching-data-into-your-application.md)
[Bind controls to data in Visual Studio](../data-tools/bind-controls-to-data-in-visual-studio.md)
[Editing Data in Your Application](../data-tools/editing-data-in-your-application.md)
[Validating Data](http://msdn.microsoft.com/library/b3a9ee4e-5d4d-4411-9c56-c811f2b4ee7e)
[Saving Data](../data-tools/saving-data.md) | 59.283688 | 238 | 0.76301 | eng_Latn | 0.796925 |
d5e56127eaff04dc3dacafc0998941b72889d54c | 121 | md | Markdown | README.md | Bingxuebao/MyWeather | 8c1cf7461a0c019b36dfd94beb82fed331fd7429 | [
"MIT"
] | null | null | null | README.md | Bingxuebao/MyWeather | 8c1cf7461a0c019b36dfd94beb82fed331fd7429 | [
"MIT"
] | null | null | null | README.md | Bingxuebao/MyWeather | 8c1cf7461a0c019b36dfd94beb82fed331fd7429 | [
"MIT"
] | null | null | null | # MyWeather
个人天气应用：
利用开放API获取网络数据，本地解析加载呈现再应用界面上。
使用的知识：android基本组建及UI的使用，http协议，json数据解析，Asynctask异步加载，listview的优化
| 20.166667 | 67 | 0.842975 | yue_Hant | 0.23527 |
d5e566d6238ef891d189522df6803d0d177125ab | 104,652 | md | Markdown | assets/lagda/Cubical.Foundations.Equiv.md | anqurvanillapy/ice1000.github.io | 3ce31eb9c483e36e8a1b087c85cbd9eeb55cfac9 | [
"MIT"
] | null | null | null | assets/lagda/Cubical.Foundations.Equiv.md | anqurvanillapy/ice1000.github.io | 3ce31eb9c483e36e8a1b087c85cbd9eeb55cfac9 | [
"MIT"
] | null | null | null | assets/lagda/Cubical.Foundations.Equiv.md | anqurvanillapy/ice1000.github.io | 3ce31eb9c483e36e8a1b087c85cbd9eeb55cfac9 | [
"MIT"
] | null | null | null | ---
layout: page
permalink: /lagda/Cubical.Foundations.Equiv.html
inline_latex: true
agda: true
---
<body>
{% raw %}
<pre class="Agda">
<a id="1" class="Comment">{-
Theory about equivalences
Definitions are in Core/Glue.agda but re-exported by this module
- isEquiv is a proposition ([isPropIsEquiv])
- Any isomorphism is an equivalence ([isoToEquiv])
There are more statements about equivalences in Equiv/Properties.agda:
- if f is an equivalence then (cong f) is an equivalence
- if f is an equivalence then precomposition with f is an equivalence
- if f is an equivalence then postcomposition with f is an equivalence
-}</a>
<a id="469" class="Symbol">{-#</a> <a id="473" class="Keyword">OPTIONS</a> <a id="481" class="Pragma">--cubical</a> <a id="491" class="Pragma">--safe</a> <a id="498" class="Symbol">#-}</a>
<a id="502" class="Keyword">module</a> <a id="509" href="Cubical.Foundations.Equiv.html" class="Module">Cubical.Foundations.Equiv</a> <a id="535" class="Keyword">where</a>
<a id="542" class="Keyword">open</a> <a id="547" class="Keyword">import</a> <a id="554" href="Cubical.Foundations.Function.html" class="Module">Cubical.Foundations.Function</a>
<a id="583" class="Keyword">open</a> <a id="588" class="Keyword">import</a> <a id="595" href="Cubical.Foundations.Prelude.html" class="Module">Cubical.Foundations.Prelude</a>
<a id="623" class="Keyword">open</a> <a id="628" class="Keyword">import</a> <a id="635" href="Cubical.Foundations.Isomorphism.html" class="Module">Cubical.Foundations.Isomorphism</a>
<a id="667" class="Keyword">open</a> <a id="672" class="Keyword">import</a> <a id="679" href="Cubical.Foundations.GroupoidLaws.html" class="Module">Cubical.Foundations.GroupoidLaws</a>
<a id="713" class="Keyword">open</a> <a id="718" class="Keyword">import</a> <a id="725" href="Cubical.Core.Glue.html" class="Module">Cubical.Core.Glue</a> <a id="743" class="Keyword">public</a>
<a id="752" class="Keyword">using</a> <a id="758" class="Symbol">(</a> <a id="760" href="Agda.Builtin.Cubical.Glue.html#868" class="Record">isEquiv</a> <a id="768" class="Symbol">;</a> <a id="770" href="Agda.Builtin.Cubical.Glue.html#971" class="Field">equiv-proof</a> <a id="782" class="Symbol">;</a> <a id="784" href="Agda.Builtin.Cubical.Glue.html#1051" class="Function Operator">_≃_</a> <a id="788" class="Symbol">;</a> <a id="790" href="Agda.Builtin.Cubical.Glue.html#1143" class="Function">equivFun</a> <a id="799" class="Symbol">;</a> <a id="801" href="Agda.Builtin.Cubical.Glue.html#1455" class="Function">equivProof</a> <a id="812" class="Symbol">)</a>
<a id="815" class="Keyword">private</a>
<a id="825" class="Keyword">variable</a>
<a id="838" href="Cubical.Foundations.Equiv.html#838" class="Generalizable">ℓ</a> <a id="840" href="Cubical.Foundations.Equiv.html#840" class="Generalizable">ℓ'</a> <a id="843" href="Cubical.Foundations.Equiv.html#843" class="Generalizable">ℓ''</a> <a id="848" class="Symbol">:</a> <a id="850" href="Agda.Primitive.html#423" class="Postulate">Level</a>
<a id="860" href="Cubical.Foundations.Equiv.html#860" class="Generalizable">A</a> <a id="862" href="Cubical.Foundations.Equiv.html#862" class="Generalizable">B</a> <a id="864" href="Cubical.Foundations.Equiv.html#864" class="Generalizable">C</a> <a id="866" class="Symbol">:</a> <a id="868" href="Cubical.Core.Primitives.html#957" class="Function">Type</a> <a id="873" href="Cubical.Foundations.Equiv.html#838" class="Generalizable">ℓ</a>
<a id="fiber"></a><a id="876" href="Cubical.Foundations.Equiv.html#876" class="Function">fiber</a> <a id="882" class="Symbol">:</a> <a id="884" class="Symbol">∀</a> <a id="886" class="Symbol">{</a><a id="887" href="Cubical.Foundations.Equiv.html#887" class="Bound">A</a> <a id="889" class="Symbol">:</a> <a id="891" href="Cubical.Core.Primitives.html#957" class="Function">Type</a> <a id="896" href="Cubical.Foundations.Equiv.html#838" class="Generalizable">ℓ</a><a id="897" class="Symbol">}</a> <a id="899" class="Symbol">{</a><a id="900" href="Cubical.Foundations.Equiv.html#900" class="Bound">B</a> <a id="902" class="Symbol">:</a> <a id="904" href="Cubical.Core.Primitives.html#957" class="Function">Type</a> <a id="909" href="Cubical.Foundations.Equiv.html#840" class="Generalizable">ℓ'</a><a id="911" class="Symbol">}</a> <a id="913" class="Symbol">(</a><a id="914" href="Cubical.Foundations.Equiv.html#914" class="Bound">f</a> <a id="916" class="Symbol">:</a> <a id="918" href="Cubical.Foundations.Equiv.html#887" class="Bound">A</a> <a id="920" class="Symbol">→</a> <a id="922" href="Cubical.Foundations.Equiv.html#900" class="Bound">B</a><a id="923" class="Symbol">)</a> <a id="925" class="Symbol">(</a><a id="926" href="Cubical.Foundations.Equiv.html#926" class="Bound">y</a> <a id="928" class="Symbol">:</a> <a id="930" href="Cubical.Foundations.Equiv.html#900" class="Bound">B</a><a id="931" class="Symbol">)</a> <a id="933" class="Symbol">→</a> <a id="935" href="Cubical.Core.Primitives.html#957" class="Function">Type</a> <a id="940" class="Symbol">(</a><a id="941" href="Agda.Primitive.html#636" class="Primitive">ℓ-max</a> <a id="947" href="Cubical.Foundations.Equiv.html#838" class="Generalizable">ℓ</a> <a id="949" href="Cubical.Foundations.Equiv.html#840" class="Generalizable">ℓ'</a><a id="951" class="Symbol">)</a>
<a id="953" href="Cubical.Foundations.Equiv.html#876" class="Function">fiber</a> <a id="959" class="Symbol">{</a><a id="960" class="Argument">A</a> <a id="962" class="Symbol">=</a> <a id="964" href="Cubical.Foundations.Equiv.html#964" class="Bound">A</a><a id="965" class="Symbol">}</a> <a id="967" href="Cubical.Foundations.Equiv.html#967" class="Bound">f</a> <a id="969" href="Cubical.Foundations.Equiv.html#969" class="Bound">y</a> <a id="971" class="Symbol">=</a> <a id="973" href="Cubical.Core.Primitives.html#5705" class="Function">Σ[</a> <a id="976" href="Cubical.Foundations.Equiv.html#976" class="Bound">x</a> <a id="978" href="Cubical.Core.Primitives.html#5705" class="Function">∈</a> <a id="980" href="Cubical.Foundations.Equiv.html#964" class="Bound">A</a> <a id="982" href="Cubical.Core.Primitives.html#5705" class="Function">]</a> <a id="984" href="Cubical.Foundations.Equiv.html#967" class="Bound">f</a> <a id="986" href="Cubical.Foundations.Equiv.html#976" class="Bound">x</a> <a id="988" href="Agda.Builtin.Cubical.Path.html#381" class="Function Operator">≡</a> <a id="990" href="Cubical.Foundations.Equiv.html#969" class="Bound">y</a>
<a id="equivIsEquiv"></a><a id="993" href="Cubical.Foundations.Equiv.html#993" class="Function">equivIsEquiv</a> <a id="1006" class="Symbol">:</a> <a id="1008" class="Symbol">∀</a> <a id="1010" class="Symbol">{</a><a id="1011" href="Cubical.Foundations.Equiv.html#1011" class="Bound">A</a> <a id="1013" class="Symbol">:</a> <a id="1015" href="Cubical.Core.Primitives.html#957" class="Function">Type</a> <a id="1020" href="Cubical.Foundations.Equiv.html#838" class="Generalizable">ℓ</a><a id="1021" class="Symbol">}</a> <a id="1023" class="Symbol">{</a><a id="1024" href="Cubical.Foundations.Equiv.html#1024" class="Bound">B</a> <a id="1026" class="Symbol">:</a> <a id="1028" href="Cubical.Core.Primitives.html#957" class="Function">Type</a> <a id="1033" href="Cubical.Foundations.Equiv.html#840" class="Generalizable">ℓ'</a><a id="1035" class="Symbol">}</a> <a id="1037" class="Symbol">(</a><a id="1038" href="Cubical.Foundations.Equiv.html#1038" class="Bound">e</a> <a id="1040" class="Symbol">:</a> <a id="1042" href="Cubical.Foundations.Equiv.html#1011" class="Bound">A</a> <a id="1044" href="Agda.Builtin.Cubical.Glue.html#1051" class="Function Operator">≃</a> <a id="1046" href="Cubical.Foundations.Equiv.html#1024" class="Bound">B</a><a id="1047" class="Symbol">)</a> <a id="1049" class="Symbol">→</a> <a id="1051" href="Agda.Builtin.Cubical.Glue.html#868" class="Record">isEquiv</a> <a id="1059" class="Symbol">(</a><a id="1060" href="Agda.Builtin.Cubical.Glue.html#1143" class="Function">equivFun</a> <a id="1069" href="Cubical.Foundations.Equiv.html#1038" class="Bound">e</a><a id="1070" class="Symbol">)</a>
<a id="1072" href="Cubical.Foundations.Equiv.html#993" class="Function">equivIsEquiv</a> <a id="1085" href="Cubical.Foundations.Equiv.html#1085" class="Bound">e</a> <a id="1087" class="Symbol">=</a> <a id="1089" href="Agda.Builtin.Sigma.html#264" class="Field">snd</a> <a id="1093" href="Cubical.Foundations.Equiv.html#1085" class="Bound">e</a>
<a id="equivCtr"></a><a id="1096" href="Cubical.Foundations.Equiv.html#1096" class="Function">equivCtr</a> <a id="1105" class="Symbol">:</a> <a id="1107" class="Symbol">∀</a> <a id="1109" class="Symbol">{</a><a id="1110" href="Cubical.Foundations.Equiv.html#1110" class="Bound">A</a> <a id="1112" class="Symbol">:</a> <a id="1114" href="Cubical.Core.Primitives.html#957" class="Function">Type</a> <a id="1119" href="Cubical.Foundations.Equiv.html#838" class="Generalizable">ℓ</a><a id="1120" class="Symbol">}</a> <a id="1122" class="Symbol">{</a><a id="1123" href="Cubical.Foundations.Equiv.html#1123" class="Bound">B</a> <a id="1125" class="Symbol">:</a> <a id="1127" href="Cubical.Core.Primitives.html#957" class="Function">Type</a> <a id="1132" href="Cubical.Foundations.Equiv.html#840" class="Generalizable">ℓ'</a><a id="1134" class="Symbol">}</a> <a id="1136" class="Symbol">(</a><a id="1137" href="Cubical.Foundations.Equiv.html#1137" class="Bound">e</a> <a id="1139" class="Symbol">:</a> <a id="1141" href="Cubical.Foundations.Equiv.html#1110" class="Bound">A</a> <a id="1143" href="Agda.Builtin.Cubical.Glue.html#1051" class="Function Operator">≃</a> <a id="1145" href="Cubical.Foundations.Equiv.html#1123" class="Bound">B</a><a id="1146" class="Symbol">)</a> <a id="1148" class="Symbol">(</a><a id="1149" href="Cubical.Foundations.Equiv.html#1149" class="Bound">y</a> <a id="1151" class="Symbol">:</a> <a id="1153" href="Cubical.Foundations.Equiv.html#1123" class="Bound">B</a><a id="1154" class="Symbol">)</a> <a id="1156" class="Symbol">→</a> <a id="1158" href="Cubical.Foundations.Equiv.html#876" class="Function">fiber</a> <a id="1164" class="Symbol">(</a><a id="1165" href="Agda.Builtin.Cubical.Glue.html#1143" class="Function">equivFun</a> <a id="1174" href="Cubical.Foundations.Equiv.html#1137" class="Bound">e</a><a id="1175" class="Symbol">)</a> <a id="1177" href="Cubical.Foundations.Equiv.html#1149" class="Bound">y</a>
<a id="1179" href="Cubical.Foundations.Equiv.html#1096" class="Function">equivCtr</a> <a id="1188" href="Cubical.Foundations.Equiv.html#1188" class="Bound">e</a> <a id="1190" href="Cubical.Foundations.Equiv.html#1190" class="Bound">y</a> <a id="1192" class="Symbol">=</a> <a id="1194" href="Cubical.Foundations.Equiv.html#1188" class="Bound">e</a> <a id="1196" class="Symbol">.</a><a id="1197" href="Agda.Builtin.Sigma.html#264" class="Field">snd</a> <a id="1201" class="Symbol">.</a><a id="1202" href="Agda.Builtin.Cubical.Glue.html#971" class="Field">equiv-proof</a> <a id="1214" href="Cubical.Foundations.Equiv.html#1190" class="Bound">y</a> <a id="1216" class="Symbol">.</a><a id="1217" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a>
<a id="equivCtrPath"></a><a id="1222" href="Cubical.Foundations.Equiv.html#1222" class="Function">equivCtrPath</a> <a id="1235" class="Symbol">:</a> <a id="1237" class="Symbol">∀</a> <a id="1239" class="Symbol">{</a><a id="1240" href="Cubical.Foundations.Equiv.html#1240" class="Bound">A</a> <a id="1242" class="Symbol">:</a> <a id="1244" href="Cubical.Core.Primitives.html#957" class="Function">Type</a> <a id="1249" href="Cubical.Foundations.Equiv.html#838" class="Generalizable">ℓ</a><a id="1250" class="Symbol">}</a> <a id="1252" class="Symbol">{</a><a id="1253" href="Cubical.Foundations.Equiv.html#1253" class="Bound">B</a> <a id="1255" class="Symbol">:</a> <a id="1257" href="Cubical.Core.Primitives.html#957" class="Function">Type</a> <a id="1262" href="Cubical.Foundations.Equiv.html#840" class="Generalizable">ℓ'</a><a id="1264" class="Symbol">}</a> <a id="1266" class="Symbol">(</a><a id="1267" href="Cubical.Foundations.Equiv.html#1267" class="Bound">e</a> <a id="1269" class="Symbol">:</a> <a id="1271" href="Cubical.Foundations.Equiv.html#1240" class="Bound">A</a> <a id="1273" href="Agda.Builtin.Cubical.Glue.html#1051" class="Function Operator">≃</a> <a id="1275" href="Cubical.Foundations.Equiv.html#1253" class="Bound">B</a><a id="1276" class="Symbol">)</a> <a id="1278" class="Symbol">(</a><a id="1279" href="Cubical.Foundations.Equiv.html#1279" class="Bound">y</a> <a id="1281" class="Symbol">:</a> <a id="1283" href="Cubical.Foundations.Equiv.html#1253" class="Bound">B</a><a id="1284" class="Symbol">)</a> <a id="1286" class="Symbol">→</a>
<a id="1290" class="Symbol">(</a><a id="1291" href="Cubical.Foundations.Equiv.html#1291" class="Bound">v</a> <a id="1293" class="Symbol">:</a> <a id="1295" href="Cubical.Foundations.Equiv.html#876" class="Function">fiber</a> <a id="1301" class="Symbol">(</a><a id="1302" href="Agda.Builtin.Cubical.Glue.html#1143" class="Function">equivFun</a> <a id="1311" href="Cubical.Foundations.Equiv.html#1267" class="Bound">e</a><a id="1312" class="Symbol">)</a> <a id="1314" href="Cubical.Foundations.Equiv.html#1279" class="Bound">y</a><a id="1315" class="Symbol">)</a> <a id="1317" class="Symbol">→</a> <a id="1319" href="Cubical.Core.Primitives.html#1694" class="Function">Path</a> <a id="1324" class="Symbol">_</a> <a id="1326" class="Symbol">(</a><a id="1327" href="Cubical.Foundations.Equiv.html#1096" class="Function">equivCtr</a> <a id="1336" href="Cubical.Foundations.Equiv.html#1267" class="Bound">e</a> <a id="1338" href="Cubical.Foundations.Equiv.html#1279" class="Bound">y</a><a id="1339" class="Symbol">)</a> <a id="1341" href="Cubical.Foundations.Equiv.html#1291" class="Bound">v</a>
<a id="1343" href="Cubical.Foundations.Equiv.html#1222" class="Function">equivCtrPath</a> <a id="1356" href="Cubical.Foundations.Equiv.html#1356" class="Bound">e</a> <a id="1358" href="Cubical.Foundations.Equiv.html#1358" class="Bound">y</a> <a id="1360" class="Symbol">=</a> <a id="1362" href="Cubical.Foundations.Equiv.html#1356" class="Bound">e</a> <a id="1364" class="Symbol">.</a><a id="1365" href="Agda.Builtin.Sigma.html#264" class="Field">snd</a> <a id="1369" class="Symbol">.</a><a id="1370" href="Agda.Builtin.Cubical.Glue.html#971" class="Field">equiv-proof</a> <a id="1382" href="Cubical.Foundations.Equiv.html#1358" class="Bound">y</a> <a id="1384" class="Symbol">.</a><a id="1385" href="Agda.Builtin.Sigma.html#264" class="Field">snd</a>
<a id="1390" class="Comment">-- The identity equivalence</a>
<a id="idIsEquiv"></a><a id="1418" href="Cubical.Foundations.Equiv.html#1418" class="Function">idIsEquiv</a> <a id="1428" class="Symbol">:</a> <a id="1430" class="Symbol">∀</a> <a id="1432" class="Symbol">(</a><a id="1433" href="Cubical.Foundations.Equiv.html#1433" class="Bound">A</a> <a id="1435" class="Symbol">:</a> <a id="1437" href="Cubical.Core.Primitives.html#957" class="Function">Type</a> <a id="1442" href="Cubical.Foundations.Equiv.html#838" class="Generalizable">ℓ</a><a id="1443" class="Symbol">)</a> <a id="1445" class="Symbol">→</a> <a id="1447" href="Agda.Builtin.Cubical.Glue.html#868" class="Record">isEquiv</a> <a id="1455" class="Symbol">(</a><a id="1456" href="Cubical.Foundations.Function.html#177" class="Function">idfun</a> <a id="1462" href="Cubical.Foundations.Equiv.html#1433" class="Bound">A</a><a id="1463" class="Symbol">)</a>
<a id="1465" href="Agda.Builtin.Cubical.Glue.html#971" class="Field">equiv-proof</a> <a id="1477" class="Symbol">(</a><a id="1478" href="Cubical.Foundations.Equiv.html#1418" class="Function">idIsEquiv</a> <a id="1488" href="Cubical.Foundations.Equiv.html#1488" class="Bound">A</a><a id="1489" class="Symbol">)</a> <a id="1491" href="Cubical.Foundations.Equiv.html#1491" class="Bound">y</a> <a id="1493" class="Symbol">=</a>
<a id="1497" class="Symbol">((</a><a id="1499" href="Cubical.Foundations.Equiv.html#1491" class="Bound">y</a> <a id="1501" href="Agda.Builtin.Sigma.html#236" class="InductiveConstructor Operator">,</a> <a id="1503" href="Cubical.Foundations.Prelude.html#856" class="Function">refl</a><a id="1507" class="Symbol">)</a> <a id="1509" href="Agda.Builtin.Sigma.html#236" class="InductiveConstructor Operator">,</a> <a id="1511" class="Symbol">λ</a> <a id="1513" href="Cubical.Foundations.Equiv.html#1513" class="Bound">z</a> <a id="1515" href="Cubical.Foundations.Equiv.html#1515" class="Bound">i</a> <a id="1517" class="Symbol">→</a> <a id="1519" href="Cubical.Foundations.Equiv.html#1513" class="Bound">z</a> <a id="1521" class="Symbol">.</a><a id="1522" href="Agda.Builtin.Sigma.html#264" class="Field">snd</a> <a id="1526" class="Symbol">(</a><a id="1527" href="Cubical.Core.Primitives.html#549" class="Primitive Operator">~</a> <a id="1529" href="Cubical.Foundations.Equiv.html#1515" class="Bound">i</a><a id="1530" class="Symbol">)</a> <a id="1532" href="Agda.Builtin.Sigma.html#236" class="InductiveConstructor Operator">,</a> <a id="1534" class="Symbol">λ</a> <a id="1536" href="Cubical.Foundations.Equiv.html#1536" class="Bound">j</a> <a id="1538" class="Symbol">→</a> <a id="1540" href="Cubical.Foundations.Equiv.html#1513" class="Bound">z</a> <a id="1542" class="Symbol">.</a><a id="1543" href="Agda.Builtin.Sigma.html#264" class="Field">snd</a> <a id="1547" class="Symbol">(</a><a id="1548" href="Cubical.Core.Primitives.html#549" class="Primitive Operator">~</a> <a id="1550" href="Cubical.Foundations.Equiv.html#1515" class="Bound">i</a> <a id="1552" href="Cubical.Core.Primitives.html#500" class="Primitive Operator">∨</a> <a id="1554" href="Cubical.Foundations.Equiv.html#1536" class="Bound">j</a><a id="1555" class="Symbol">))</a>
<a id="idEquiv"></a><a id="1559" href="Cubical.Foundations.Equiv.html#1559" class="Function">idEquiv</a> <a id="1567" class="Symbol">:</a> <a id="1569" class="Symbol">∀</a> <a id="1571" class="Symbol">(</a><a id="1572" href="Cubical.Foundations.Equiv.html#1572" class="Bound">A</a> <a id="1574" class="Symbol">:</a> <a id="1576" href="Cubical.Core.Primitives.html#957" class="Function">Type</a> <a id="1581" href="Cubical.Foundations.Equiv.html#838" class="Generalizable">ℓ</a><a id="1582" class="Symbol">)</a> <a id="1584" class="Symbol">→</a> <a id="1586" href="Cubical.Foundations.Equiv.html#1572" class="Bound">A</a> <a id="1588" href="Agda.Builtin.Cubical.Glue.html#1051" class="Function Operator">≃</a> <a id="1590" href="Cubical.Foundations.Equiv.html#1572" class="Bound">A</a>
<a id="1592" href="Cubical.Foundations.Equiv.html#1559" class="Function">idEquiv</a> <a id="1600" href="Cubical.Foundations.Equiv.html#1600" class="Bound">A</a> <a id="1602" class="Symbol">=</a> <a id="1604" class="Symbol">(</a><a id="1605" href="Cubical.Foundations.Function.html#177" class="Function">idfun</a> <a id="1611" href="Cubical.Foundations.Equiv.html#1600" class="Bound">A</a> <a id="1613" href="Agda.Builtin.Sigma.html#236" class="InductiveConstructor Operator">,</a> <a id="1615" href="Cubical.Foundations.Equiv.html#1418" class="Function">idIsEquiv</a> <a id="1625" href="Cubical.Foundations.Equiv.html#1600" class="Bound">A</a><a id="1626" class="Symbol">)</a>
<a id="1629" class="Comment">-- Proof using isPropIsContr. This is slow and the direct proof below is better</a>
<a id="isPropIsEquiv'"></a><a id="1710" href="Cubical.Foundations.Equiv.html#1710" class="Function">isPropIsEquiv'</a> <a id="1725" class="Symbol">:</a> <a id="1727" class="Symbol">(</a><a id="1728" href="Cubical.Foundations.Equiv.html#1728" class="Bound">f</a> <a id="1730" class="Symbol">:</a> <a id="1732" href="Cubical.Foundations.Equiv.html#860" class="Generalizable">A</a> <a id="1734" class="Symbol">→</a> <a id="1736" href="Cubical.Foundations.Equiv.html#862" class="Generalizable">B</a><a id="1737" class="Symbol">)</a> <a id="1739" class="Symbol">→</a> <a id="1741" href="Cubical.Foundations.Prelude.html#5588" class="Function">isProp</a> <a id="1748" class="Symbol">(</a><a id="1749" href="Agda.Builtin.Cubical.Glue.html#868" class="Record">isEquiv</a> <a id="1757" href="Cubical.Foundations.Equiv.html#1728" class="Bound">f</a><a id="1758" class="Symbol">)</a>
<a id="1760" href="Agda.Builtin.Cubical.Glue.html#971" class="Field">equiv-proof</a> <a id="1772" class="Symbol">(</a><a id="1773" href="Cubical.Foundations.Equiv.html#1710" class="Function">isPropIsEquiv'</a> <a id="1788" href="Cubical.Foundations.Equiv.html#1788" class="Bound">f</a> <a id="1790" href="Cubical.Foundations.Equiv.html#1790" class="Bound">u0</a> <a id="1793" href="Cubical.Foundations.Equiv.html#1793" class="Bound">u1</a> <a id="1796" href="Cubical.Foundations.Equiv.html#1796" class="Bound">i</a><a id="1797" class="Symbol">)</a> <a id="1799" href="Cubical.Foundations.Equiv.html#1799" class="Bound">y</a> <a id="1801" class="Symbol">=</a>
<a id="1805" href="Cubical.Foundations.Prelude.html#7778" class="Function">isPropIsContr</a> <a id="1819" class="Symbol">(</a><a id="1820" href="Cubical.Foundations.Equiv.html#1790" class="Bound">u0</a> <a id="1823" class="Symbol">.</a><a id="1824" href="Agda.Builtin.Cubical.Glue.html#971" class="Field">equiv-proof</a> <a id="1836" href="Cubical.Foundations.Equiv.html#1799" class="Bound">y</a><a id="1837" class="Symbol">)</a> <a id="1839" class="Symbol">(</a><a id="1840" href="Cubical.Foundations.Equiv.html#1793" class="Bound">u1</a> <a id="1843" class="Symbol">.</a><a id="1844" href="Agda.Builtin.Cubical.Glue.html#971" class="Field">equiv-proof</a> <a id="1856" href="Cubical.Foundations.Equiv.html#1799" class="Bound">y</a><a id="1857" class="Symbol">)</a> <a id="1859" href="Cubical.Foundations.Equiv.html#1796" class="Bound">i</a>
<a id="1862" class="Comment">-- Direct proof that computes quite ok (can be optimized further if</a>
<a id="1930" class="Comment">-- necessary, see:</a>
<a id="1949" class="Comment">-- https://github.com/mortberg/cubicaltt/blob/pi4s3_dimclosures/examples/brunerie2.ctt#L562</a>
<a id="isPropIsEquiv"></a><a id="2042" href="Cubical.Foundations.Equiv.html#2042" class="Function">isPropIsEquiv</a> <a id="2056" class="Symbol">:</a> <a id="2058" class="Symbol">(</a><a id="2059" href="Cubical.Foundations.Equiv.html#2059" class="Bound">f</a> <a id="2061" class="Symbol">:</a> <a id="2063" href="Cubical.Foundations.Equiv.html#860" class="Generalizable">A</a> <a id="2065" class="Symbol">→</a> <a id="2067" href="Cubical.Foundations.Equiv.html#862" class="Generalizable">B</a><a id="2068" class="Symbol">)</a> <a id="2070" class="Symbol">→</a> <a id="2072" href="Cubical.Foundations.Prelude.html#5588" class="Function">isProp</a> <a id="2079" class="Symbol">(</a><a id="2080" href="Agda.Builtin.Cubical.Glue.html#868" class="Record">isEquiv</a> <a id="2088" href="Cubical.Foundations.Equiv.html#2059" class="Bound">f</a><a id="2089" class="Symbol">)</a>
<a id="2091" href="Agda.Builtin.Cubical.Glue.html#971" class="Field">equiv-proof</a> <a id="2103" class="Symbol">(</a><a id="2104" href="Cubical.Foundations.Equiv.html#2042" class="Function">isPropIsEquiv</a> <a id="2118" href="Cubical.Foundations.Equiv.html#2118" class="Bound">f</a> <a id="2120" href="Cubical.Foundations.Equiv.html#2120" class="Bound">p</a> <a id="2122" href="Cubical.Foundations.Equiv.html#2122" class="Bound">q</a> <a id="2124" href="Cubical.Foundations.Equiv.html#2124" class="Bound">i</a><a id="2125" class="Symbol">)</a> <a id="2127" href="Cubical.Foundations.Equiv.html#2127" class="Bound">y</a> <a id="2129" class="Symbol">=</a>
<a id="2133" class="Keyword">let</a> <a id="2137" href="Cubical.Foundations.Equiv.html#2137" class="Bound">p2</a> <a id="2140" class="Symbol">=</a> <a id="2142" href="Cubical.Foundations.Equiv.html#2120" class="Bound">p</a> <a id="2144" class="Symbol">.</a><a id="2145" href="Agda.Builtin.Cubical.Glue.html#971" class="Field">equiv-proof</a> <a id="2157" href="Cubical.Foundations.Equiv.html#2127" class="Bound">y</a> <a id="2159" class="Symbol">.</a><a id="2160" href="Agda.Builtin.Sigma.html#264" class="Field">snd</a>
<a id="2170" href="Cubical.Foundations.Equiv.html#2170" class="Bound">q2</a> <a id="2173" class="Symbol">=</a> <a id="2175" href="Cubical.Foundations.Equiv.html#2122" class="Bound">q</a> <a id="2177" class="Symbol">.</a><a id="2178" href="Agda.Builtin.Cubical.Glue.html#971" class="Field">equiv-proof</a> <a id="2190" href="Cubical.Foundations.Equiv.html#2127" class="Bound">y</a> <a id="2192" class="Symbol">.</a><a id="2193" href="Agda.Builtin.Sigma.html#264" class="Field">snd</a>
<a id="2199" class="Keyword">in</a> <a id="2202" href="Cubical.Foundations.Equiv.html#2137" class="Bound">p2</a> <a id="2205" class="Symbol">(</a><a id="2206" href="Cubical.Foundations.Equiv.html#2122" class="Bound">q</a> <a id="2208" class="Symbol">.</a><a id="2209" href="Agda.Builtin.Cubical.Glue.html#971" class="Field">equiv-proof</a> <a id="2221" href="Cubical.Foundations.Equiv.html#2127" class="Bound">y</a> <a id="2223" class="Symbol">.</a><a id="2224" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a><a id="2227" class="Symbol">)</a> <a id="2229" href="Cubical.Foundations.Equiv.html#2124" class="Bound">i</a>
<a id="2234" href="Agda.Builtin.Sigma.html#236" class="InductiveConstructor Operator">,</a> <a id="2236" class="Symbol">λ</a> <a id="2238" href="Cubical.Foundations.Equiv.html#2238" class="Bound">w</a> <a id="2240" href="Cubical.Foundations.Equiv.html#2240" class="Bound">j</a> <a id="2242" class="Symbol">→</a> <a id="2244" href="Cubical.Core.Primitives.html#667" class="Primitive">hcomp</a> <a id="2250" class="Symbol">(λ</a> <a id="2253" href="Cubical.Foundations.Equiv.html#2253" class="Bound">k</a> <a id="2255" class="Symbol">→</a> <a id="2257" class="Symbol">λ</a> <a id="2259" class="Symbol">{</a> <a id="2261" class="Symbol">(</a><a id="2262" href="Cubical.Foundations.Equiv.html#2124" class="Bound">i</a> <a id="2264" class="Symbol">=</a> <a id="2266" href="Agda.Primitive.Cubical.html#143" class="InductiveConstructor">i0</a><a id="2268" class="Symbol">)</a> <a id="2270" class="Symbol">→</a> <a id="2272" href="Cubical.Foundations.Equiv.html#2137" class="Bound">p2</a> <a id="2275" href="Cubical.Foundations.Equiv.html#2238" class="Bound">w</a> <a id="2277" href="Cubical.Foundations.Equiv.html#2240" class="Bound">j</a>
<a id="2307" class="Symbol">;</a> <a id="2309" class="Symbol">(</a><a id="2310" href="Cubical.Foundations.Equiv.html#2124" class="Bound">i</a> <a id="2312" class="Symbol">=</a> <a id="2314" href="Agda.Primitive.Cubical.html#171" class="InductiveConstructor">i1</a><a id="2316" class="Symbol">)</a> <a id="2318" class="Symbol">→</a> <a id="2320" href="Cubical.Foundations.Equiv.html#2170" class="Bound">q2</a> <a id="2323" href="Cubical.Foundations.Equiv.html#2238" class="Bound">w</a> <a id="2325" class="Symbol">(</a><a id="2326" href="Cubical.Foundations.Equiv.html#2240" class="Bound">j</a> <a id="2328" href="Cubical.Core.Primitives.html#500" class="Primitive Operator">∨</a> <a id="2330" href="Cubical.Core.Primitives.html#549" class="Primitive Operator">~</a> <a id="2332" href="Cubical.Foundations.Equiv.html#2253" class="Bound">k</a><a id="2333" class="Symbol">)</a>
<a id="2363" class="Symbol">;</a> <a id="2365" class="Symbol">(</a><a id="2366" href="Cubical.Foundations.Equiv.html#2240" class="Bound">j</a> <a id="2368" class="Symbol">=</a> <a id="2370" href="Agda.Primitive.Cubical.html#143" class="InductiveConstructor">i0</a><a id="2372" class="Symbol">)</a> <a id="2374" class="Symbol">→</a> <a id="2376" href="Cubical.Foundations.Equiv.html#2137" class="Bound">p2</a> <a id="2379" class="Symbol">(</a><a id="2380" href="Cubical.Foundations.Equiv.html#2170" class="Bound">q2</a> <a id="2383" href="Cubical.Foundations.Equiv.html#2238" class="Bound">w</a> <a id="2385" class="Symbol">(</a><a id="2386" href="Cubical.Core.Primitives.html#549" class="Primitive Operator">~</a> <a id="2388" href="Cubical.Foundations.Equiv.html#2253" class="Bound">k</a><a id="2389" class="Symbol">))</a> <a id="2392" href="Cubical.Foundations.Equiv.html#2124" class="Bound">i</a>
<a id="2422" class="Symbol">;</a> <a id="2424" class="Symbol">(</a><a id="2425" href="Cubical.Foundations.Equiv.html#2240" class="Bound">j</a> <a id="2427" class="Symbol">=</a> <a id="2429" href="Agda.Primitive.Cubical.html#171" class="InductiveConstructor">i1</a><a id="2431" class="Symbol">)</a> <a id="2433" class="Symbol">→</a> <a id="2435" href="Cubical.Foundations.Equiv.html#2238" class="Bound">w</a> <a id="2437" class="Symbol">})</a>
<a id="2459" class="Symbol">(</a><a id="2460" href="Cubical.Foundations.Equiv.html#2137" class="Bound">p2</a> <a id="2463" href="Cubical.Foundations.Equiv.html#2238" class="Bound">w</a> <a id="2465" class="Symbol">(</a><a id="2466" href="Cubical.Foundations.Equiv.html#2124" class="Bound">i</a> <a id="2468" href="Cubical.Core.Primitives.html#500" class="Primitive Operator">∨</a> <a id="2470" href="Cubical.Foundations.Equiv.html#2240" class="Bound">j</a><a id="2471" class="Symbol">))</a>
<a id="equivEq"></a><a id="2475" href="Cubical.Foundations.Equiv.html#2475" class="Function">equivEq</a> <a id="2483" class="Symbol">:</a> <a id="2485" class="Symbol">(</a><a id="2486" href="Cubical.Foundations.Equiv.html#2486" class="Bound">e</a> <a id="2488" href="Cubical.Foundations.Equiv.html#2488" class="Bound">f</a> <a id="2490" class="Symbol">:</a> <a id="2492" href="Cubical.Foundations.Equiv.html#860" class="Generalizable">A</a> <a id="2494" href="Agda.Builtin.Cubical.Glue.html#1051" class="Function Operator">≃</a> <a id="2496" href="Cubical.Foundations.Equiv.html#862" class="Generalizable">B</a><a id="2497" class="Symbol">)</a> <a id="2499" class="Symbol">→</a> <a id="2501" class="Symbol">(</a><a id="2502" href="Cubical.Foundations.Equiv.html#2502" class="Bound">h</a> <a id="2504" class="Symbol">:</a> <a id="2506" href="Cubical.Foundations.Equiv.html#2486" class="Bound">e</a> <a id="2508" class="Symbol">.</a><a id="2509" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a> <a id="2513" href="Agda.Builtin.Cubical.Path.html#381" class="Function Operator">≡</a> <a id="2515" href="Cubical.Foundations.Equiv.html#2488" class="Bound">f</a> <a id="2517" class="Symbol">.</a><a id="2518" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a><a id="2521" class="Symbol">)</a> <a id="2523" class="Symbol">→</a> <a id="2525" href="Cubical.Foundations.Equiv.html#2486" class="Bound">e</a> <a id="2527" href="Agda.Builtin.Cubical.Path.html#381" class="Function Operator">≡</a> <a id="2529" href="Cubical.Foundations.Equiv.html#2488" class="Bound">f</a>
<a id="2531" href="Cubical.Foundations.Equiv.html#2475" class="Function">equivEq</a> <a id="2539" href="Cubical.Foundations.Equiv.html#2539" class="Bound">e</a> <a id="2541" href="Cubical.Foundations.Equiv.html#2541" class="Bound">f</a> <a id="2543" href="Cubical.Foundations.Equiv.html#2543" class="Bound">h</a> <a id="2545" class="Symbol">=</a> <a id="2547" class="Symbol">λ</a> <a id="2549" href="Cubical.Foundations.Equiv.html#2549" class="Bound">i</a> <a id="2551" class="Symbol">→</a> <a id="2553" class="Symbol">(</a><a id="2554" href="Cubical.Foundations.Equiv.html#2543" class="Bound">h</a> <a id="2556" href="Cubical.Foundations.Equiv.html#2549" class="Bound">i</a><a id="2557" class="Symbol">)</a> <a id="2559" href="Agda.Builtin.Sigma.html#236" class="InductiveConstructor Operator">,</a> <a id="2561" href="Cubical.Foundations.Prelude.html#7591" class="Function">isProp→PathP</a> <a id="2574" class="Symbol">(λ</a> <a id="2577" href="Cubical.Foundations.Equiv.html#2577" class="Bound">i</a> <a id="2579" class="Symbol">→</a> <a id="2581" href="Cubical.Foundations.Equiv.html#2042" class="Function">isPropIsEquiv</a> <a id="2595" class="Symbol">(</a><a id="2596" href="Cubical.Foundations.Equiv.html#2543" class="Bound">h</a> <a id="2598" href="Cubical.Foundations.Equiv.html#2577" class="Bound">i</a><a id="2599" class="Symbol">))</a> <a id="2602" class="Symbol">(</a><a id="2603" href="Cubical.Foundations.Equiv.html#2539" class="Bound">e</a> <a id="2605" class="Symbol">.</a><a id="2606" href="Agda.Builtin.Sigma.html#264" class="Field">snd</a><a id="2609" class="Symbol">)</a> <a id="2611" class="Symbol">(</a><a id="2612" href="Cubical.Foundations.Equiv.html#2541" class="Bound">f</a> <a id="2614" class="Symbol">.</a><a id="2615" href="Agda.Builtin.Sigma.html#264" class="Field">snd</a><a id="2618" class="Symbol">)</a> <a id="2620" href="Cubical.Foundations.Equiv.html#2549" class="Bound">i</a>
<a id="2623" class="Keyword">module</a> <a id="2630" href="Cubical.Foundations.Equiv.html#2630" class="Module">_</a> <a id="2632" class="Symbol">(</a><a id="2633" href="Cubical.Foundations.Equiv.html#2633" class="Bound">w</a> <a id="2635" class="Symbol">:</a> <a id="2637" href="Cubical.Foundations.Equiv.html#860" class="Generalizable">A</a> <a id="2639" href="Agda.Builtin.Cubical.Glue.html#1051" class="Function Operator">≃</a> <a id="2641" href="Cubical.Foundations.Equiv.html#862" class="Generalizable">B</a><a id="2642" class="Symbol">)</a> <a id="2644" class="Keyword">where</a>
<a id="2652" href="Cubical.Foundations.Equiv.html#2652" class="Function">invEq</a> <a id="2658" class="Symbol">:</a> <a id="2660" href="Cubical.Foundations.Equiv.html#2641" class="Bound">B</a> <a id="2662" class="Symbol">→</a> <a id="2664" href="Cubical.Foundations.Equiv.html#2637" class="Bound">A</a>
<a id="2668" href="Cubical.Foundations.Equiv.html#2652" class="Function">invEq</a> <a id="2674" href="Cubical.Foundations.Equiv.html#2674" class="Bound">y</a> <a id="2676" class="Symbol">=</a> <a id="2678" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a> <a id="2682" class="Symbol">(</a><a id="2683" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a> <a id="2687" class="Symbol">(</a><a id="2688" href="Agda.Builtin.Sigma.html#264" class="Field">snd</a> <a id="2692" href="Cubical.Foundations.Equiv.html#2633" class="Bound">w</a> <a id="2694" class="Symbol">.</a><a id="2695" href="Agda.Builtin.Cubical.Glue.html#971" class="Field">equiv-proof</a> <a id="2707" href="Cubical.Foundations.Equiv.html#2674" class="Bound">y</a><a id="2708" class="Symbol">))</a>
<a id="2714" href="Cubical.Foundations.Equiv.html#2714" class="Function">secEq</a> <a id="2720" class="Symbol">:</a> <a id="2722" href="Cubical.Foundations.Isomorphism.html#471" class="Function">section</a> <a id="2730" href="Cubical.Foundations.Equiv.html#2652" class="Function">invEq</a> <a id="2736" class="Symbol">(</a><a id="2737" href="Cubical.Foundations.Equiv.html#2633" class="Bound">w</a> <a id="2739" class="Symbol">.</a><a id="2740" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a><a id="2743" class="Symbol">)</a>
<a id="2747" href="Cubical.Foundations.Equiv.html#2714" class="Function">secEq</a> <a id="2753" href="Cubical.Foundations.Equiv.html#2753" class="Bound">x</a> <a id="2755" class="Symbol">=</a> <a id="2757" class="Symbol">λ</a> <a id="2759" href="Cubical.Foundations.Equiv.html#2759" class="Bound">i</a> <a id="2761" class="Symbol">→</a> <a id="2763" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a> <a id="2767" class="Symbol">(</a><a id="2768" href="Agda.Builtin.Sigma.html#264" class="Field">snd</a> <a id="2772" class="Symbol">(</a><a id="2773" href="Agda.Builtin.Sigma.html#264" class="Field">snd</a> <a id="2777" href="Cubical.Foundations.Equiv.html#2633" class="Bound">w</a> <a id="2779" class="Symbol">.</a><a id="2780" href="Agda.Builtin.Cubical.Glue.html#971" class="Field">equiv-proof</a> <a id="2792" class="Symbol">(</a><a id="2793" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a> <a id="2797" href="Cubical.Foundations.Equiv.html#2633" class="Bound">w</a> <a id="2799" href="Cubical.Foundations.Equiv.html#2753" class="Bound">x</a><a id="2800" class="Symbol">))</a> <a id="2803" class="Symbol">(</a><a id="2804" href="Cubical.Foundations.Equiv.html#2753" class="Bound">x</a> <a id="2806" href="Agda.Builtin.Sigma.html#236" class="InductiveConstructor Operator">,</a> <a id="2808" class="Symbol">(λ</a> <a id="2811" href="Cubical.Foundations.Equiv.html#2811" class="Bound">j</a> <a id="2813" class="Symbol">→</a> <a id="2815" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a> <a id="2819" href="Cubical.Foundations.Equiv.html#2633" class="Bound">w</a> <a id="2821" href="Cubical.Foundations.Equiv.html#2753" class="Bound">x</a><a id="2822" class="Symbol">))</a> <a id="2825" href="Cubical.Foundations.Equiv.html#2759" class="Bound">i</a><a id="2826" class="Symbol">)</a>
<a id="2831" href="Cubical.Foundations.Equiv.html#2831" class="Function">retEq</a> <a id="2837" class="Symbol">:</a> <a id="2839" href="Cubical.Foundations.Isomorphism.html#586" class="Function">retract</a> <a id="2847" href="Cubical.Foundations.Equiv.html#2652" class="Function">invEq</a> <a id="2853" class="Symbol">(</a><a id="2854" href="Cubical.Foundations.Equiv.html#2633" class="Bound">w</a> <a id="2856" class="Symbol">.</a><a id="2857" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a><a id="2860" class="Symbol">)</a>
<a id="2864" href="Cubical.Foundations.Equiv.html#2831" class="Function">retEq</a> <a id="2870" href="Cubical.Foundations.Equiv.html#2870" class="Bound">y</a> <a id="2872" class="Symbol">=</a> <a id="2874" class="Symbol">λ</a> <a id="2876" href="Cubical.Foundations.Equiv.html#2876" class="Bound">i</a> <a id="2878" class="Symbol">→</a> <a id="2880" href="Agda.Builtin.Sigma.html#264" class="Field">snd</a> <a id="2884" class="Symbol">(</a><a id="2885" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a> <a id="2889" class="Symbol">(</a><a id="2890" href="Agda.Builtin.Sigma.html#264" class="Field">snd</a> <a id="2894" href="Cubical.Foundations.Equiv.html#2633" class="Bound">w</a> <a id="2896" class="Symbol">.</a><a id="2897" href="Agda.Builtin.Cubical.Glue.html#971" class="Field">equiv-proof</a> <a id="2909" href="Cubical.Foundations.Equiv.html#2870" class="Bound">y</a><a id="2910" class="Symbol">))</a> <a id="2913" href="Cubical.Foundations.Equiv.html#2876" class="Bound">i</a>
<a id="equivToIso"></a><a id="2916" href="Cubical.Foundations.Equiv.html#2916" class="Function">equivToIso</a> <a id="2927" class="Symbol">:</a> <a id="2929" class="Symbol">∀</a> <a id="2931" class="Symbol">{</a><a id="2932" href="Cubical.Foundations.Equiv.html#2932" class="Bound">ℓ</a> <a id="2934" href="Cubical.Foundations.Equiv.html#2934" class="Bound">ℓ'</a><a id="2936" class="Symbol">}</a> <a id="2938" class="Symbol">{</a><a id="2939" href="Cubical.Foundations.Equiv.html#2939" class="Bound">A</a> <a id="2941" class="Symbol">:</a> <a id="2943" href="Cubical.Core.Primitives.html#957" class="Function">Type</a> <a id="2948" href="Cubical.Foundations.Equiv.html#2932" class="Bound">ℓ</a><a id="2949" class="Symbol">}</a> <a id="2951" class="Symbol">{</a><a id="2952" href="Cubical.Foundations.Equiv.html#2952" class="Bound">B</a> <a id="2954" class="Symbol">:</a> <a id="2956" href="Cubical.Core.Primitives.html#957" class="Function">Type</a> <a id="2961" href="Cubical.Foundations.Equiv.html#2934" class="Bound">ℓ'</a><a id="2963" class="Symbol">}</a> <a id="2965" class="Symbol">→</a> <a id="2967" href="Cubical.Foundations.Equiv.html#2939" class="Bound">A</a> <a id="2969" href="Agda.Builtin.Cubical.Glue.html#1051" class="Function Operator">≃</a> <a id="2971" href="Cubical.Foundations.Equiv.html#2952" class="Bound">B</a> <a id="2973" class="Symbol">→</a> <a id="2975" href="Cubical.Foundations.Isomorphism.html#673" class="Record">Iso</a> <a id="2979" href="Cubical.Foundations.Equiv.html#2939" class="Bound">A</a> <a id="2981" href="Cubical.Foundations.Equiv.html#2952" class="Bound">B</a>
<a id="2983" href="Cubical.Foundations.Equiv.html#2916" class="Function">equivToIso</a> <a id="2994" class="Symbol">{</a><a id="2995" class="Argument">A</a> <a id="2997" class="Symbol">=</a> <a id="2999" href="Cubical.Foundations.Equiv.html#2999" class="Bound">A</a><a id="3000" class="Symbol">}</a> <a id="3002" class="Symbol">{</a><a id="3003" class="Argument">B</a> <a id="3005" class="Symbol">=</a> <a id="3007" href="Cubical.Foundations.Equiv.html#3007" class="Bound">B</a><a id="3008" class="Symbol">}</a> <a id="3010" href="Cubical.Foundations.Equiv.html#3010" class="Bound">e</a> <a id="3012" class="Symbol">=</a> <a id="3014" href="Cubical.Foundations.Isomorphism.html#751" class="InductiveConstructor">iso</a> <a id="3018" class="Symbol">(</a><a id="3019" href="Cubical.Foundations.Equiv.html#3010" class="Bound">e</a> <a id="3021" class="Symbol">.</a><a id="3022" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a><a id="3025" class="Symbol">)</a> <a id="3027" class="Symbol">(</a><a id="3028" href="Cubical.Foundations.Equiv.html#2652" class="Function">invEq</a> <a id="3034" href="Cubical.Foundations.Equiv.html#3010" class="Bound">e</a> <a id="3036" class="Symbol">)</a> <a id="3038" class="Symbol">(</a><a id="3039" href="Cubical.Foundations.Equiv.html#2831" class="Function">retEq</a> <a id="3045" href="Cubical.Foundations.Equiv.html#3010" class="Bound">e</a><a id="3046" class="Symbol">)</a> <a id="3048" class="Symbol">(</a><a id="3049" href="Cubical.Foundations.Equiv.html#2714" class="Function">secEq</a> <a id="3055" href="Cubical.Foundations.Equiv.html#3010" class="Bound">e</a><a id="3056" class="Symbol">)</a>
<a id="invEquiv"></a><a id="3059" href="Cubical.Foundations.Equiv.html#3059" class="Function">invEquiv</a> <a id="3068" class="Symbol">:</a> <a id="3070" href="Cubical.Foundations.Equiv.html#860" class="Generalizable">A</a> <a id="3072" href="Agda.Builtin.Cubical.Glue.html#1051" class="Function Operator">≃</a> <a id="3074" href="Cubical.Foundations.Equiv.html#862" class="Generalizable">B</a> <a id="3076" class="Symbol">→</a> <a id="3078" href="Cubical.Foundations.Equiv.html#862" class="Generalizable">B</a> <a id="3080" href="Agda.Builtin.Cubical.Glue.html#1051" class="Function Operator">≃</a> <a id="3082" href="Cubical.Foundations.Equiv.html#860" class="Generalizable">A</a>
<a id="3084" href="Cubical.Foundations.Equiv.html#3059" class="Function">invEquiv</a> <a id="3093" href="Cubical.Foundations.Equiv.html#3093" class="Bound">f</a> <a id="3095" class="Symbol">=</a> <a id="3097" href="Cubical.Foundations.Isomorphism.html#2598" class="Function">isoToEquiv</a> <a id="3108" class="Symbol">(</a><a id="3109" href="Cubical.Foundations.Isomorphism.html#751" class="InductiveConstructor">iso</a> <a id="3113" class="Symbol">(</a><a id="3114" href="Cubical.Foundations.Equiv.html#2652" class="Function">invEq</a> <a id="3120" href="Cubical.Foundations.Equiv.html#3093" class="Bound">f</a><a id="3121" class="Symbol">)</a> <a id="3123" class="Symbol">(</a><a id="3124" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a> <a id="3128" href="Cubical.Foundations.Equiv.html#3093" class="Bound">f</a><a id="3129" class="Symbol">)</a> <a id="3131" class="Symbol">(</a><a id="3132" href="Cubical.Foundations.Equiv.html#2714" class="Function">secEq</a> <a id="3138" href="Cubical.Foundations.Equiv.html#3093" class="Bound">f</a><a id="3139" class="Symbol">)</a> <a id="3141" class="Symbol">(</a><a id="3142" href="Cubical.Foundations.Equiv.html#2831" class="Function">retEq</a> <a id="3148" href="Cubical.Foundations.Equiv.html#3093" class="Bound">f</a><a id="3149" class="Symbol">))</a>
<a id="invEquivIdEquiv"></a><a id="3153" href="Cubical.Foundations.Equiv.html#3153" class="Function">invEquivIdEquiv</a> <a id="3169" class="Symbol">:</a> <a id="3171" class="Symbol">(</a><a id="3172" href="Cubical.Foundations.Equiv.html#3172" class="Bound">A</a> <a id="3174" class="Symbol">:</a> <a id="3176" href="Cubical.Core.Primitives.html#957" class="Function">Type</a> <a id="3181" href="Cubical.Foundations.Equiv.html#838" class="Generalizable">ℓ</a><a id="3182" class="Symbol">)</a> <a id="3184" class="Symbol">→</a> <a id="3186" href="Cubical.Foundations.Equiv.html#3059" class="Function">invEquiv</a> <a id="3195" class="Symbol">(</a><a id="3196" href="Cubical.Foundations.Equiv.html#1559" class="Function">idEquiv</a> <a id="3204" href="Cubical.Foundations.Equiv.html#3172" class="Bound">A</a><a id="3205" class="Symbol">)</a> <a id="3207" href="Agda.Builtin.Cubical.Path.html#381" class="Function Operator">≡</a> <a id="3209" href="Cubical.Foundations.Equiv.html#1559" class="Function">idEquiv</a> <a id="3217" href="Cubical.Foundations.Equiv.html#3172" class="Bound">A</a>
<a id="3219" href="Cubical.Foundations.Equiv.html#3153" class="Function">invEquivIdEquiv</a> <a id="3235" class="Symbol">_</a> <a id="3237" class="Symbol">=</a> <a id="3239" href="Cubical.Foundations.Equiv.html#2475" class="Function">equivEq</a> <a id="3247" class="Symbol">_</a> <a id="3249" class="Symbol">_</a> <a id="3251" href="Cubical.Foundations.Prelude.html#856" class="Function">refl</a>
<a id="compEquiv"></a><a id="3257" href="Cubical.Foundations.Equiv.html#3257" class="Function">compEquiv</a> <a id="3267" class="Symbol">:</a> <a id="3269" href="Cubical.Foundations.Equiv.html#860" class="Generalizable">A</a> <a id="3271" href="Agda.Builtin.Cubical.Glue.html#1051" class="Function Operator">≃</a> <a id="3273" href="Cubical.Foundations.Equiv.html#862" class="Generalizable">B</a> <a id="3275" class="Symbol">→</a> <a id="3277" href="Cubical.Foundations.Equiv.html#862" class="Generalizable">B</a> <a id="3279" href="Agda.Builtin.Cubical.Glue.html#1051" class="Function Operator">≃</a> <a id="3281" href="Cubical.Foundations.Equiv.html#864" class="Generalizable">C</a> <a id="3283" class="Symbol">→</a> <a id="3285" href="Cubical.Foundations.Equiv.html#860" class="Generalizable">A</a> <a id="3287" href="Agda.Builtin.Cubical.Glue.html#1051" class="Function Operator">≃</a> <a id="3289" href="Cubical.Foundations.Equiv.html#864" class="Generalizable">C</a>
<a id="3291" href="Cubical.Foundations.Equiv.html#3257" class="Function">compEquiv</a> <a id="3301" href="Cubical.Foundations.Equiv.html#3301" class="Bound">f</a> <a id="3303" href="Cubical.Foundations.Equiv.html#3303" class="Bound">g</a> <a id="3305" class="Symbol">=</a> <a id="3307" href="Cubical.Foundations.Isomorphism.html#2598" class="Function">isoToEquiv</a>
<a id="3336" class="Symbol">(</a><a id="3337" href="Cubical.Foundations.Isomorphism.html#751" class="InductiveConstructor">iso</a> <a id="3341" class="Symbol">(λ</a> <a id="3344" href="Cubical.Foundations.Equiv.html#3344" class="Bound">x</a> <a id="3346" class="Symbol">→</a> <a id="3348" href="Cubical.Foundations.Equiv.html#3303" class="Bound">g</a> <a id="3350" class="Symbol">.</a><a id="3351" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a> <a id="3355" class="Symbol">(</a><a id="3356" href="Cubical.Foundations.Equiv.html#3301" class="Bound">f</a> <a id="3358" class="Symbol">.</a><a id="3359" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a> <a id="3363" href="Cubical.Foundations.Equiv.html#3344" class="Bound">x</a><a id="3364" class="Symbol">))</a>
<a id="3390" class="Symbol">(λ</a> <a id="3393" href="Cubical.Foundations.Equiv.html#3393" class="Bound">x</a> <a id="3395" class="Symbol">→</a> <a id="3397" href="Cubical.Foundations.Equiv.html#2652" class="Function">invEq</a> <a id="3403" href="Cubical.Foundations.Equiv.html#3301" class="Bound">f</a> <a id="3405" class="Symbol">(</a><a id="3406" href="Cubical.Foundations.Equiv.html#2652" class="Function">invEq</a> <a id="3412" href="Cubical.Foundations.Equiv.html#3303" class="Bound">g</a> <a id="3414" href="Cubical.Foundations.Equiv.html#3393" class="Bound">x</a><a id="3415" class="Symbol">))</a>
<a id="3441" class="Symbol">(λ</a> <a id="3444" href="Cubical.Foundations.Equiv.html#3444" class="Bound">y</a> <a id="3446" class="Symbol">→</a> <a id="3448" class="Symbol">(</a><a id="3449" href="Cubical.Foundations.Prelude.html#1057" class="Function">cong</a> <a id="3454" class="Symbol">(</a><a id="3455" href="Cubical.Foundations.Equiv.html#3303" class="Bound">g</a> <a id="3457" class="Symbol">.</a><a id="3458" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a><a id="3461" class="Symbol">)</a> <a id="3463" class="Symbol">(</a><a id="3464" href="Cubical.Foundations.Equiv.html#2831" class="Function">retEq</a> <a id="3470" href="Cubical.Foundations.Equiv.html#3301" class="Bound">f</a> <a id="3472" class="Symbol">(</a><a id="3473" href="Cubical.Foundations.Equiv.html#2652" class="Function">invEq</a> <a id="3479" href="Cubical.Foundations.Equiv.html#3303" class="Bound">g</a> <a id="3481" href="Cubical.Foundations.Equiv.html#3444" class="Bound">y</a><a id="3482" class="Symbol">)))</a> <a id="3486" href="Cubical.Foundations.Prelude.html#1705" class="Function Operator">∙</a> <a id="3488" class="Symbol">(</a><a id="3489" href="Cubical.Foundations.Equiv.html#2831" class="Function">retEq</a> <a id="3495" href="Cubical.Foundations.Equiv.html#3303" class="Bound">g</a> <a id="3497" href="Cubical.Foundations.Equiv.html#3444" class="Bound">y</a><a id="3498" class="Symbol">))</a>
<a id="3524" class="Symbol">(λ</a> <a id="3527" href="Cubical.Foundations.Equiv.html#3527" class="Bound">y</a> <a id="3529" class="Symbol">→</a> <a id="3531" class="Symbol">(</a><a id="3532" href="Cubical.Foundations.Prelude.html#1057" class="Function">cong</a> <a id="3537" class="Symbol">(</a><a id="3538" href="Cubical.Foundations.Equiv.html#2652" class="Function">invEq</a> <a id="3544" href="Cubical.Foundations.Equiv.html#3301" class="Bound">f</a><a id="3545" class="Symbol">)</a> <a id="3547" class="Symbol">(</a><a id="3548" href="Cubical.Foundations.Equiv.html#2714" class="Function">secEq</a> <a id="3554" href="Cubical.Foundations.Equiv.html#3303" class="Bound">g</a> <a id="3556" class="Symbol">(</a><a id="3557" href="Cubical.Foundations.Equiv.html#3301" class="Bound">f</a> <a id="3559" class="Symbol">.</a><a id="3560" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a> <a id="3564" href="Cubical.Foundations.Equiv.html#3527" class="Bound">y</a><a id="3565" class="Symbol">)))</a> <a id="3569" href="Cubical.Foundations.Prelude.html#1705" class="Function Operator">∙</a> <a id="3571" class="Symbol">(</a><a id="3572" href="Cubical.Foundations.Equiv.html#2714" class="Function">secEq</a> <a id="3578" href="Cubical.Foundations.Equiv.html#3301" class="Bound">f</a> <a id="3580" href="Cubical.Foundations.Equiv.html#3527" class="Bound">y</a><a id="3581" class="Symbol">)))</a>
<a id="compEquivIdEquiv"></a><a id="3586" href="Cubical.Foundations.Equiv.html#3586" class="Function">compEquivIdEquiv</a> <a id="3603" class="Symbol">:</a> <a id="3605" class="Symbol">{</a><a id="3606" href="Cubical.Foundations.Equiv.html#3606" class="Bound">A</a> <a id="3608" href="Cubical.Foundations.Equiv.html#3608" class="Bound">B</a> <a id="3610" class="Symbol">:</a> <a id="3612" href="Cubical.Core.Primitives.html#957" class="Function">Type</a> <a id="3617" href="Cubical.Foundations.Equiv.html#838" class="Generalizable">ℓ</a><a id="3618" class="Symbol">}</a> <a id="3620" class="Symbol">(</a><a id="3621" href="Cubical.Foundations.Equiv.html#3621" class="Bound">e</a> <a id="3623" class="Symbol">:</a> <a id="3625" href="Cubical.Foundations.Equiv.html#3606" class="Bound">A</a> <a id="3627" href="Agda.Builtin.Cubical.Glue.html#1051" class="Function Operator">≃</a> <a id="3629" href="Cubical.Foundations.Equiv.html#3608" class="Bound">B</a><a id="3630" class="Symbol">)</a> <a id="3632" class="Symbol">→</a> <a id="3634" href="Cubical.Foundations.Equiv.html#3257" class="Function">compEquiv</a> <a id="3644" class="Symbol">(</a><a id="3645" href="Cubical.Foundations.Equiv.html#1559" class="Function">idEquiv</a> <a id="3653" href="Cubical.Foundations.Equiv.html#3606" class="Bound">A</a><a id="3654" class="Symbol">)</a> <a id="3656" href="Cubical.Foundations.Equiv.html#3621" class="Bound">e</a> <a id="3658" href="Agda.Builtin.Cubical.Path.html#381" class="Function Operator">≡</a> <a id="3660" href="Cubical.Foundations.Equiv.html#3621" class="Bound">e</a>
<a id="3662" href="Cubical.Foundations.Equiv.html#3586" class="Function">compEquivIdEquiv</a> <a id="3679" href="Cubical.Foundations.Equiv.html#3679" class="Bound">e</a> <a id="3681" class="Symbol">=</a> <a id="3683" href="Cubical.Foundations.Equiv.html#2475" class="Function">equivEq</a> <a id="3691" class="Symbol">_</a> <a id="3693" class="Symbol">_</a> <a id="3695" href="Cubical.Foundations.Prelude.html#856" class="Function">refl</a>
<a id="LiftEquiv"></a><a id="3701" href="Cubical.Foundations.Equiv.html#3701" class="Function">LiftEquiv</a> <a id="3711" class="Symbol">:</a> <a id="3713" class="Symbol">{</a><a id="3714" href="Cubical.Foundations.Equiv.html#3714" class="Bound">A</a> <a id="3716" class="Symbol">:</a> <a id="3718" href="Cubical.Core.Primitives.html#957" class="Function">Type</a> <a id="3723" href="Cubical.Foundations.Equiv.html#838" class="Generalizable">ℓ</a><a id="3724" class="Symbol">}</a> <a id="3726" class="Symbol">→</a> <a id="3728" href="Cubical.Foundations.Equiv.html#3714" class="Bound">A</a> <a id="3730" href="Agda.Builtin.Cubical.Glue.html#1051" class="Function Operator">≃</a> <a id="3732" href="Cubical.Foundations.Prelude.html#8638" class="Record">Lift</a> <a id="3737" class="Symbol">{</a><a id="3738" class="Argument">i</a> <a id="3740" class="Symbol">=</a> <a id="3742" href="Cubical.Foundations.Equiv.html#838" class="Generalizable">ℓ</a><a id="3743" class="Symbol">}</a> <a id="3745" class="Symbol">{</a><a id="3746" class="Argument">j</a> <a id="3748" class="Symbol">=</a> <a id="3750" href="Cubical.Foundations.Equiv.html#840" class="Generalizable">ℓ'</a><a id="3752" class="Symbol">}</a> <a id="3754" href="Cubical.Foundations.Equiv.html#3714" class="Bound">A</a>
<a id="3756" href="Cubical.Foundations.Equiv.html#3701" class="Function">LiftEquiv</a> <a id="3766" class="Symbol">=</a> <a id="3768" href="Cubical.Foundations.Isomorphism.html#2598" class="Function">isoToEquiv</a> <a id="3779" class="Symbol">(</a><a id="3780" href="Cubical.Foundations.Isomorphism.html#751" class="InductiveConstructor">iso</a> <a id="3784" href="Cubical.Foundations.Prelude.html#8701" class="InductiveConstructor">lift</a> <a id="3789" href="Cubical.Foundations.Prelude.html#8718" class="Field">lower</a> <a id="3795" class="Symbol">(λ</a> <a id="3798" href="Cubical.Foundations.Equiv.html#3798" class="Bound">_</a> <a id="3800" class="Symbol">→</a> <a id="3802" href="Cubical.Foundations.Prelude.html#856" class="Function">refl</a><a id="3806" class="Symbol">)</a> <a id="3808" class="Symbol">(λ</a> <a id="3811" href="Cubical.Foundations.Equiv.html#3811" class="Bound">_</a> <a id="3813" class="Symbol">→</a> <a id="3815" href="Cubical.Foundations.Prelude.html#856" class="Function">refl</a><a id="3819" class="Symbol">))</a>
<a id="3823" class="Comment">-- module _ {ℓ ℓ'} {A : Type ℓ} {B : Type ℓ'} where</a>
<a id="3876" class="Comment">-- invEquivInvol : (f : A ≃ B) → invEquiv (invEquiv f) ≡ f</a>
<a id="3937" class="Comment">-- invEquivInvol f i .fst = fst f</a>
<a id="3973" class="Comment">-- invEquivInvol f i .snd = propIsEquiv (fst f) (snd (invEquiv (invEquiv f))) (snd f) i</a>
<a id="Contr→Equiv"></a><a id="4064" href="Cubical.Foundations.Equiv.html#4064" class="Function">Contr→Equiv</a> <a id="4076" class="Symbol">:</a> <a id="4078" href="Cubical.Foundations.Prelude.html#5524" class="Function">isContr</a> <a id="4086" href="Cubical.Foundations.Equiv.html#860" class="Generalizable">A</a> <a id="4088" class="Symbol">→</a> <a id="4090" href="Cubical.Foundations.Prelude.html#5524" class="Function">isContr</a> <a id="4098" href="Cubical.Foundations.Equiv.html#862" class="Generalizable">B</a> <a id="4100" class="Symbol">→</a> <a id="4102" href="Cubical.Foundations.Equiv.html#860" class="Generalizable">A</a> <a id="4104" href="Agda.Builtin.Cubical.Glue.html#1051" class="Function Operator">≃</a> <a id="4106" href="Cubical.Foundations.Equiv.html#862" class="Generalizable">B</a>
<a id="4108" href="Cubical.Foundations.Equiv.html#4064" class="Function">Contr→Equiv</a> <a id="4120" href="Cubical.Foundations.Equiv.html#4120" class="Bound">Actr</a> <a id="4125" href="Cubical.Foundations.Equiv.html#4125" class="Bound">Bctr</a> <a id="4130" class="Symbol">=</a> <a id="4132" href="Cubical.Foundations.Isomorphism.html#2598" class="Function">isoToEquiv</a> <a id="4143" class="Symbol">(</a><a id="4144" href="Cubical.Foundations.Isomorphism.html#751" class="InductiveConstructor">iso</a> <a id="4148" class="Symbol">(λ</a> <a id="4151" href="Cubical.Foundations.Equiv.html#4151" class="Bound">_</a> <a id="4153" class="Symbol">→</a> <a id="4155" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a> <a id="4159" href="Cubical.Foundations.Equiv.html#4125" class="Bound">Bctr</a><a id="4163" class="Symbol">)</a> <a id="4165" class="Symbol">(λ</a> <a id="4168" href="Cubical.Foundations.Equiv.html#4168" class="Bound">_</a> <a id="4170" class="Symbol">→</a> <a id="4172" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a> <a id="4176" href="Cubical.Foundations.Equiv.html#4120" class="Bound">Actr</a><a id="4180" class="Symbol">)</a> <a id="4182" class="Symbol">(</a><a id="4183" href="Agda.Builtin.Sigma.html#264" class="Field">snd</a> <a id="4187" href="Cubical.Foundations.Equiv.html#4125" class="Bound">Bctr</a><a id="4191" class="Symbol">)</a> <a id="4193" class="Symbol">(</a><a id="4194" href="Agda.Builtin.Sigma.html#264" class="Field">snd</a> <a id="4198" href="Cubical.Foundations.Equiv.html#4120" class="Bound">Actr</a><a id="4202" class="Symbol">))</a>
<a id="PropEquiv→Equiv"></a><a id="4206" href="Cubical.Foundations.Equiv.html#4206" class="Function">PropEquiv→Equiv</a> <a id="4222" class="Symbol">:</a> <a id="4224" class="Symbol">(</a><a id="4225" href="Cubical.Foundations.Equiv.html#4225" class="Bound">Aprop</a> <a id="4231" class="Symbol">:</a> <a id="4233" href="Cubical.Foundations.Prelude.html#5588" class="Function">isProp</a> <a id="4240" href="Cubical.Foundations.Equiv.html#860" class="Generalizable">A</a><a id="4241" class="Symbol">)</a> <a id="4243" class="Symbol">(</a><a id="4244" href="Cubical.Foundations.Equiv.html#4244" class="Bound">Bprop</a> <a id="4250" class="Symbol">:</a> <a id="4252" href="Cubical.Foundations.Prelude.html#5588" class="Function">isProp</a> <a id="4259" href="Cubical.Foundations.Equiv.html#862" class="Generalizable">B</a><a id="4260" class="Symbol">)</a> <a id="4262" class="Symbol">(</a><a id="4263" href="Cubical.Foundations.Equiv.html#4263" class="Bound">f</a> <a id="4265" class="Symbol">:</a> <a id="4267" href="Cubical.Foundations.Equiv.html#860" class="Generalizable">A</a> <a id="4269" class="Symbol">→</a> <a id="4271" href="Cubical.Foundations.Equiv.html#862" class="Generalizable">B</a><a id="4272" class="Symbol">)</a> <a id="4274" class="Symbol">(</a><a id="4275" href="Cubical.Foundations.Equiv.html#4275" class="Bound">g</a> <a id="4277" class="Symbol">:</a> <a id="4279" href="Cubical.Foundations.Equiv.html#862" class="Generalizable">B</a> <a id="4281" class="Symbol">→</a> <a id="4283" href="Cubical.Foundations.Equiv.html#860" class="Generalizable">A</a><a id="4284" class="Symbol">)</a> <a id="4286" class="Symbol">→</a> <a id="4288" class="Symbol">(</a><a id="4289" href="Cubical.Foundations.Equiv.html#860" class="Generalizable">A</a> <a id="4291" href="Agda.Builtin.Cubical.Glue.html#1051" class="Function Operator">≃</a> <a id="4293" href="Cubical.Foundations.Equiv.html#862" class="Generalizable">B</a><a id="4294" class="Symbol">)</a>
<a id="4296" href="Cubical.Foundations.Equiv.html#4206" class="Function">PropEquiv→Equiv</a> <a id="4312" href="Cubical.Foundations.Equiv.html#4312" class="Bound">Aprop</a> <a id="4318" href="Cubical.Foundations.Equiv.html#4318" class="Bound">Bprop</a> <a id="4324" href="Cubical.Foundations.Equiv.html#4324" class="Bound">f</a> <a id="4326" href="Cubical.Foundations.Equiv.html#4326" class="Bound">g</a> <a id="4328" class="Symbol">=</a> <a id="4330" href="Cubical.Foundations.Isomorphism.html#2598" class="Function">isoToEquiv</a> <a id="4341" class="Symbol">(</a><a id="4342" href="Cubical.Foundations.Isomorphism.html#751" class="InductiveConstructor">iso</a> <a id="4346" href="Cubical.Foundations.Equiv.html#4324" class="Bound">f</a> <a id="4348" href="Cubical.Foundations.Equiv.html#4326" class="Bound">g</a> <a id="4350" class="Symbol">(λ</a> <a id="4353" href="Cubical.Foundations.Equiv.html#4353" class="Bound">b</a> <a id="4355" class="Symbol">→</a> <a id="4357" href="Cubical.Foundations.Equiv.html#4318" class="Bound">Bprop</a> <a id="4363" class="Symbol">(</a><a id="4364" href="Cubical.Foundations.Equiv.html#4324" class="Bound">f</a> <a id="4366" class="Symbol">(</a><a id="4367" href="Cubical.Foundations.Equiv.html#4326" class="Bound">g</a> <a id="4369" href="Cubical.Foundations.Equiv.html#4353" class="Bound">b</a><a id="4370" class="Symbol">))</a> <a id="4373" href="Cubical.Foundations.Equiv.html#4353" class="Bound">b</a><a id="4374" class="Symbol">)</a> <a id="4376" class="Symbol">λ</a> <a id="4378" href="Cubical.Foundations.Equiv.html#4378" class="Bound">a</a> <a id="4380" class="Symbol">→</a> <a id="4382" href="Cubical.Foundations.Equiv.html#4312" class="Bound">Aprop</a> <a id="4388" class="Symbol">(</a><a id="4389" href="Cubical.Foundations.Equiv.html#4326" class="Bound">g</a> <a id="4391" class="Symbol">(</a><a id="4392" href="Cubical.Foundations.Equiv.html#4324" class="Bound">f</a> <a id="4394" href="Cubical.Foundations.Equiv.html#4378" class="Bound">a</a><a id="4395" class="Symbol">))</a> <a id="4398" href="Cubical.Foundations.Equiv.html#4378" class="Bound">a</a><a id="4399" class="Symbol">)</a>
<a id="homotopyNatural"></a><a id="4402" href="Cubical.Foundations.Equiv.html#4402" class="Function">homotopyNatural</a> <a id="4418" class="Symbol">:</a> <a id="4420" class="Symbol">{</a><a id="4421" href="Cubical.Foundations.Equiv.html#4421" class="Bound">f</a> <a id="4423" href="Cubical.Foundations.Equiv.html#4423" class="Bound">g</a> <a id="4425" class="Symbol">:</a> <a id="4427" href="Cubical.Foundations.Equiv.html#860" class="Generalizable">A</a> <a id="4429" class="Symbol">→</a> <a id="4431" href="Cubical.Foundations.Equiv.html#862" class="Generalizable">B</a><a id="4432" class="Symbol">}</a> <a id="4434" class="Symbol">(</a><a id="4435" href="Cubical.Foundations.Equiv.html#4435" class="Bound">H</a> <a id="4437" class="Symbol">:</a> <a id="4439" class="Symbol">∀</a> <a id="4441" href="Cubical.Foundations.Equiv.html#4441" class="Bound">a</a> <a id="4443" class="Symbol">→</a> <a id="4445" href="Cubical.Foundations.Equiv.html#4421" class="Bound">f</a> <a id="4447" href="Cubical.Foundations.Equiv.html#4441" class="Bound">a</a> <a id="4449" href="Agda.Builtin.Cubical.Path.html#381" class="Function Operator">≡</a> <a id="4451" href="Cubical.Foundations.Equiv.html#4423" class="Bound">g</a> <a id="4453" href="Cubical.Foundations.Equiv.html#4441" class="Bound">a</a><a id="4454" class="Symbol">)</a> <a id="4456" class="Symbol">{</a><a id="4457" href="Cubical.Foundations.Equiv.html#4457" class="Bound">x</a> <a id="4459" href="Cubical.Foundations.Equiv.html#4459" class="Bound">y</a> <a id="4461" class="Symbol">:</a> <a id="4463" href="Cubical.Foundations.Equiv.html#860" class="Generalizable">A</a><a id="4464" class="Symbol">}</a> <a id="4466" class="Symbol">(</a><a id="4467" href="Cubical.Foundations.Equiv.html#4467" class="Bound">p</a> <a id="4469" class="Symbol">:</a> <a id="4471" href="Cubical.Foundations.Equiv.html#4457" class="Bound">x</a> <a id="4473" href="Agda.Builtin.Cubical.Path.html#381" class="Function Operator">≡</a> <a id="4475" href="Cubical.Foundations.Equiv.html#4459" class="Bound">y</a><a id="4476" class="Symbol">)</a> <a id="4478" class="Symbol">→</a>
<a id="4498" href="Cubical.Foundations.Equiv.html#4435" class="Bound">H</a> <a id="4500" href="Cubical.Foundations.Equiv.html#4457" class="Bound">x</a> <a id="4502" href="Cubical.Foundations.Prelude.html#1705" class="Function Operator">∙</a> <a id="4504" href="Cubical.Foundations.Prelude.html#1057" class="Function">cong</a> <a id="4509" href="Cubical.Foundations.Equiv.html#4423" class="Bound">g</a> <a id="4511" href="Cubical.Foundations.Equiv.html#4467" class="Bound">p</a> <a id="4513" href="Agda.Builtin.Cubical.Path.html#381" class="Function Operator">≡</a> <a id="4515" href="Cubical.Foundations.Prelude.html#1057" class="Function">cong</a> <a id="4520" href="Cubical.Foundations.Equiv.html#4421" class="Bound">f</a> <a id="4522" href="Cubical.Foundations.Equiv.html#4467" class="Bound">p</a> <a id="4524" href="Cubical.Foundations.Prelude.html#1705" class="Function Operator">∙</a> <a id="4526" href="Cubical.Foundations.Equiv.html#4435" class="Bound">H</a> <a id="4528" href="Cubical.Foundations.Equiv.html#4459" class="Bound">y</a>
<a id="4530" href="Cubical.Foundations.Equiv.html#4402" class="Function">homotopyNatural</a> <a id="4546" href="Cubical.Foundations.Equiv.html#4546" class="Bound">H</a> <a id="4548" href="Cubical.Foundations.Equiv.html#4548" class="Bound">p</a> <a id="4550" class="Symbol">=</a> <a id="4552" href="Cubical.Foundations.Equiv.html#4593" class="Function">homotopyNatural'</a> <a id="4569" href="Cubical.Foundations.Equiv.html#4546" class="Bound">H</a> <a id="4571" href="Cubical.Foundations.Equiv.html#4548" class="Bound">p</a> <a id="4573" href="Cubical.Foundations.Prelude.html#1705" class="Function Operator">∙</a> <a id="4575" href="Cubical.Foundations.Prelude.html#3125" class="Function">□≡∙</a> <a id="4579" class="Symbol">_</a> <a id="4581" class="Symbol">_</a>
<a id="4585" class="Keyword">where</a>
<a id="4593" href="Cubical.Foundations.Equiv.html#4593" class="Function">homotopyNatural'</a> <a id="4610" class="Symbol">:</a> <a id="4612" class="Symbol">{</a><a id="4613" href="Cubical.Foundations.Equiv.html#4613" class="Bound">f</a> <a id="4615" href="Cubical.Foundations.Equiv.html#4615" class="Bound">g</a> <a id="4617" class="Symbol">:</a> <a id="4619" href="Cubical.Foundations.Equiv.html#860" class="Generalizable">A</a> <a id="4621" class="Symbol">→</a> <a id="4623" href="Cubical.Foundations.Equiv.html#862" class="Generalizable">B</a><a id="4624" class="Symbol">}</a> <a id="4626" class="Symbol">(</a><a id="4627" href="Cubical.Foundations.Equiv.html#4627" class="Bound">H</a> <a id="4629" class="Symbol">:</a> <a id="4631" class="Symbol">∀</a> <a id="4633" href="Cubical.Foundations.Equiv.html#4633" class="Bound">a</a> <a id="4635" class="Symbol">→</a> <a id="4637" href="Cubical.Foundations.Equiv.html#4613" class="Bound">f</a> <a id="4639" href="Cubical.Foundations.Equiv.html#4633" class="Bound">a</a> <a id="4641" href="Agda.Builtin.Cubical.Path.html#381" class="Function Operator">≡</a> <a id="4643" href="Cubical.Foundations.Equiv.html#4615" class="Bound">g</a> <a id="4645" href="Cubical.Foundations.Equiv.html#4633" class="Bound">a</a><a id="4646" class="Symbol">)</a> <a id="4648" class="Symbol">{</a><a id="4649" href="Cubical.Foundations.Equiv.html#4649" class="Bound">x</a> <a id="4651" href="Cubical.Foundations.Equiv.html#4651" class="Bound">y</a> <a id="4653" class="Symbol">:</a> <a id="4655" href="Cubical.Foundations.Equiv.html#860" class="Generalizable">A</a><a id="4656" class="Symbol">}</a> <a id="4658" class="Symbol">(</a><a id="4659" href="Cubical.Foundations.Equiv.html#4659" class="Bound">p</a> <a id="4661" class="Symbol">:</a> <a id="4663" href="Cubical.Foundations.Equiv.html#4649" class="Bound">x</a> <a id="4665" href="Agda.Builtin.Cubical.Path.html#381" class="Function Operator">≡</a> <a id="4667" href="Cubical.Foundations.Equiv.html#4651" class="Bound">y</a><a id="4668" class="Symbol">)</a> <a id="4670" class="Symbol">→</a>
<a id="4693" href="Cubical.Foundations.Equiv.html#4627" class="Bound">H</a> <a id="4695" href="Cubical.Foundations.Equiv.html#4649" class="Bound">x</a> <a id="4697" href="Cubical.Foundations.Prelude.html#1705" class="Function Operator">∙</a> <a id="4699" href="Cubical.Foundations.Prelude.html#1057" class="Function">cong</a> <a id="4704" href="Cubical.Foundations.Equiv.html#4615" class="Bound">g</a> <a id="4706" href="Cubical.Foundations.Equiv.html#4659" class="Bound">p</a> <a id="4708" href="Agda.Builtin.Cubical.Path.html#381" class="Function Operator">≡</a> <a id="4710" href="Cubical.Foundations.Prelude.html#1057" class="Function">cong</a> <a id="4715" href="Cubical.Foundations.Equiv.html#4613" class="Bound">f</a> <a id="4717" href="Cubical.Foundations.Equiv.html#4659" class="Bound">p</a> <a id="4719" href="Cubical.Foundations.Prelude.html#3058" class="Function Operator">□</a> <a id="4721" href="Cubical.Foundations.Equiv.html#4627" class="Bound">H</a> <a id="4723" href="Cubical.Foundations.Equiv.html#4651" class="Bound">y</a>
<a id="4727" href="Cubical.Foundations.Equiv.html#4593" class="Function">homotopyNatural'</a> <a id="4744" class="Symbol">{</a><a id="4745" class="Argument">f</a> <a id="4747" class="Symbol">=</a> <a id="4749" href="Cubical.Foundations.Equiv.html#4749" class="Bound">f</a><a id="4750" class="Symbol">}</a> <a id="4752" class="Symbol">{</a><a id="4753" class="Argument">g</a> <a id="4755" class="Symbol">=</a> <a id="4757" href="Cubical.Foundations.Equiv.html#4757" class="Bound">g</a><a id="4758" class="Symbol">}</a> <a id="4760" href="Cubical.Foundations.Equiv.html#4760" class="Bound">H</a> <a id="4762" class="Symbol">{</a><a id="4763" href="Cubical.Foundations.Equiv.html#4763" class="Bound">x</a><a id="4764" class="Symbol">}</a> <a id="4766" class="Symbol">{</a><a id="4767" href="Cubical.Foundations.Equiv.html#4767" class="Bound">y</a><a id="4768" class="Symbol">}</a> <a id="4770" href="Cubical.Foundations.Equiv.html#4770" class="Bound">p</a> <a id="4772" href="Cubical.Foundations.Equiv.html#4772" class="Bound">i</a> <a id="4774" href="Cubical.Foundations.Equiv.html#4774" class="Bound">j</a> <a id="4776" class="Symbol">=</a>
<a id="4782" href="Cubical.Core.Primitives.html#667" class="Primitive">hcomp</a> <a id="4788" class="Symbol">(λ</a> <a id="4791" href="Cubical.Foundations.Equiv.html#4791" class="Bound">k</a> <a id="4793" class="Symbol">→</a> <a id="4795" class="Symbol">λ</a> <a id="4797" class="Symbol">{</a> <a id="4799" class="Symbol">(</a><a id="4800" href="Cubical.Foundations.Equiv.html#4772" class="Bound">i</a> <a id="4802" class="Symbol">=</a> <a id="4804" href="Agda.Primitive.Cubical.html#143" class="InductiveConstructor">i0</a><a id="4806" class="Symbol">)</a> <a id="4808" class="Symbol">→</a> <a id="4810" href="Cubical.Foundations.Prelude.html#1526" class="Function">compPath-filler</a> <a id="4826" class="Symbol">(</a><a id="4827" href="Cubical.Foundations.Equiv.html#4760" class="Bound">H</a> <a id="4829" href="Cubical.Foundations.Equiv.html#4763" class="Bound">x</a><a id="4830" class="Symbol">)</a> <a id="4832" class="Symbol">(</a><a id="4833" href="Cubical.Foundations.Prelude.html#1057" class="Function">cong</a> <a id="4838" href="Cubical.Foundations.Equiv.html#4757" class="Bound">g</a> <a id="4840" href="Cubical.Foundations.Equiv.html#4770" class="Bound">p</a><a id="4841" class="Symbol">)</a> <a id="4843" href="Cubical.Foundations.Equiv.html#4791" class="Bound">k</a> <a id="4845" href="Cubical.Foundations.Equiv.html#4774" class="Bound">j</a>
<a id="4866" class="Symbol">;</a> <a id="4868" class="Symbol">(</a><a id="4869" href="Cubical.Foundations.Equiv.html#4772" class="Bound">i</a> <a id="4871" class="Symbol">=</a> <a id="4873" href="Agda.Primitive.Cubical.html#171" class="InductiveConstructor">i1</a><a id="4875" class="Symbol">)</a> <a id="4877" class="Symbol">→</a> <a id="4879" href="Cubical.Foundations.Prelude.html#2874" class="Function">compPath'-filler</a> <a id="4896" class="Symbol">(</a><a id="4897" href="Cubical.Foundations.Prelude.html#1057" class="Function">cong</a> <a id="4902" href="Cubical.Foundations.Equiv.html#4749" class="Bound">f</a> <a id="4904" href="Cubical.Foundations.Equiv.html#4770" class="Bound">p</a><a id="4905" class="Symbol">)</a> <a id="4907" class="Symbol">(</a><a id="4908" href="Cubical.Foundations.Equiv.html#4760" class="Bound">H</a> <a id="4910" href="Cubical.Foundations.Equiv.html#4767" class="Bound">y</a><a id="4911" class="Symbol">)</a> <a id="4913" href="Cubical.Foundations.Equiv.html#4791" class="Bound">k</a> <a id="4915" href="Cubical.Foundations.Equiv.html#4774" class="Bound">j</a>
<a id="4936" class="Symbol">;</a> <a id="4938" class="Symbol">(</a><a id="4939" href="Cubical.Foundations.Equiv.html#4774" class="Bound">j</a> <a id="4941" class="Symbol">=</a> <a id="4943" href="Agda.Primitive.Cubical.html#143" class="InductiveConstructor">i0</a><a id="4945" class="Symbol">)</a> <a id="4947" class="Symbol">→</a> <a id="4949" href="Cubical.Foundations.Prelude.html#1057" class="Function">cong</a> <a id="4954" href="Cubical.Foundations.Equiv.html#4749" class="Bound">f</a> <a id="4956" href="Cubical.Foundations.Equiv.html#4770" class="Bound">p</a> <a id="4958" class="Symbol">(</a><a id="4959" href="Cubical.Foundations.Equiv.html#4772" class="Bound">i</a> <a id="4961" href="Cubical.Core.Primitives.html#451" class="Primitive Operator">∧</a> <a id="4963" class="Symbol">(</a><a id="4964" href="Cubical.Core.Primitives.html#549" class="Primitive Operator">~</a> <a id="4966" href="Cubical.Foundations.Equiv.html#4791" class="Bound">k</a><a id="4967" class="Symbol">))</a>
<a id="4989" class="Symbol">;</a> <a id="4991" class="Symbol">(</a><a id="4992" href="Cubical.Foundations.Equiv.html#4774" class="Bound">j</a> <a id="4994" class="Symbol">=</a> <a id="4996" href="Agda.Primitive.Cubical.html#171" class="InductiveConstructor">i1</a><a id="4998" class="Symbol">)</a> <a id="5000" class="Symbol">→</a> <a id="5002" href="Cubical.Foundations.Prelude.html#1057" class="Function">cong</a> <a id="5007" href="Cubical.Foundations.Equiv.html#4757" class="Bound">g</a> <a id="5009" href="Cubical.Foundations.Equiv.html#4770" class="Bound">p</a> <a id="5011" class="Symbol">(</a><a id="5012" href="Cubical.Foundations.Equiv.html#4772" class="Bound">i</a> <a id="5014" href="Cubical.Core.Primitives.html#500" class="Primitive Operator">∨</a> <a id="5016" href="Cubical.Foundations.Equiv.html#4791" class="Bound">k</a><a id="5017" class="Symbol">)</a> <a id="5019" class="Symbol">})</a>
<a id="5032" class="Symbol">(</a><a id="5033" href="Cubical.Foundations.Equiv.html#4760" class="Bound">H</a> <a id="5035" class="Symbol">(</a><a id="5036" href="Cubical.Foundations.Equiv.html#4770" class="Bound">p</a> <a id="5038" href="Cubical.Foundations.Equiv.html#4772" class="Bound">i</a><a id="5039" class="Symbol">)</a> <a id="5041" href="Cubical.Foundations.Equiv.html#4774" class="Bound">j</a><a id="5042" class="Symbol">)</a>
<a id="Hfa≡fHa"></a><a id="5045" href="Cubical.Foundations.Equiv.html#5045" class="Function">Hfa≡fHa</a> <a id="5053" class="Symbol">:</a> <a id="5055" class="Symbol">∀</a> <a id="5057" class="Symbol">{</a><a id="5058" href="Cubical.Foundations.Equiv.html#5058" class="Bound">A</a> <a id="5060" class="Symbol">:</a> <a id="5062" href="Cubical.Core.Primitives.html#957" class="Function">Type</a> <a id="5067" href="Cubical.Foundations.Equiv.html#838" class="Generalizable">ℓ</a><a id="5068" class="Symbol">}</a> <a id="5070" class="Symbol">(</a><a id="5071" href="Cubical.Foundations.Equiv.html#5071" class="Bound">f</a> <a id="5073" class="Symbol">:</a> <a id="5075" href="Cubical.Foundations.Equiv.html#5058" class="Bound">A</a> <a id="5077" class="Symbol">→</a> <a id="5079" href="Cubical.Foundations.Equiv.html#5058" class="Bound">A</a><a id="5080" class="Symbol">)</a> <a id="5082" class="Symbol">→</a> <a id="5084" class="Symbol">(</a><a id="5085" href="Cubical.Foundations.Equiv.html#5085" class="Bound">H</a> <a id="5087" class="Symbol">:</a> <a id="5089" class="Symbol">∀</a> <a id="5091" href="Cubical.Foundations.Equiv.html#5091" class="Bound">a</a> <a id="5093" class="Symbol">→</a> <a id="5095" href="Cubical.Foundations.Equiv.html#5071" class="Bound">f</a> <a id="5097" href="Cubical.Foundations.Equiv.html#5091" class="Bound">a</a> <a id="5099" href="Agda.Builtin.Cubical.Path.html#381" class="Function Operator">≡</a> <a id="5101" href="Cubical.Foundations.Equiv.html#5091" class="Bound">a</a><a id="5102" class="Symbol">)</a> <a id="5104" class="Symbol">→</a> <a id="5106" class="Symbol">∀</a> <a id="5108" href="Cubical.Foundations.Equiv.html#5108" class="Bound">a</a> <a id="5110" class="Symbol">→</a> <a id="5112" href="Cubical.Foundations.Equiv.html#5085" class="Bound">H</a> <a id="5114" class="Symbol">(</a><a id="5115" href="Cubical.Foundations.Equiv.html#5071" class="Bound">f</a> <a id="5117" href="Cubical.Foundations.Equiv.html#5108" class="Bound">a</a><a id="5118" class="Symbol">)</a> <a id="5120" href="Agda.Builtin.Cubical.Path.html#381" class="Function Operator">≡</a> <a id="5122" href="Cubical.Foundations.Prelude.html#1057" class="Function">cong</a> <a id="5127" href="Cubical.Foundations.Equiv.html#5071" class="Bound">f</a> <a id="5129" class="Symbol">(</a><a id="5130" href="Cubical.Foundations.Equiv.html#5085" class="Bound">H</a> <a id="5132" href="Cubical.Foundations.Equiv.html#5108" class="Bound">a</a><a id="5133" class="Symbol">)</a>
<a id="5135" href="Cubical.Foundations.Equiv.html#5045" class="Function">Hfa≡fHa</a> <a id="5143" class="Symbol">{</a><a id="5144" class="Argument">A</a> <a id="5146" class="Symbol">=</a> <a id="5148" href="Cubical.Foundations.Equiv.html#5148" class="Bound">A</a><a id="5149" class="Symbol">}</a> <a id="5151" href="Cubical.Foundations.Equiv.html#5151" class="Bound">f</a> <a id="5153" href="Cubical.Foundations.Equiv.html#5153" class="Bound">H</a> <a id="5155" href="Cubical.Foundations.Equiv.html#5155" class="Bound">a</a> <a id="5157" class="Symbol">=</a>
<a id="5161" href="Cubical.Foundations.Equiv.html#5153" class="Bound">H</a> <a id="5163" class="Symbol">(</a><a id="5164" href="Cubical.Foundations.Equiv.html#5151" class="Bound">f</a> <a id="5166" href="Cubical.Foundations.Equiv.html#5155" class="Bound">a</a><a id="5167" class="Symbol">)</a> <a id="5194" href="Cubical.Foundations.Prelude.html#2574" class="Function Operator">≡⟨</a> <a id="5197" href="Cubical.Foundations.GroupoidLaws.html#431" class="Function">rUnit</a> <a id="5203" class="Symbol">(</a><a id="5204" href="Cubical.Foundations.Equiv.html#5153" class="Bound">H</a> <a id="5206" class="Symbol">(</a><a id="5207" href="Cubical.Foundations.Equiv.html#5151" class="Bound">f</a> <a id="5209" href="Cubical.Foundations.Equiv.html#5155" class="Bound">a</a><a id="5210" class="Symbol">))</a> <a id="5213" href="Cubical.Foundations.Prelude.html#2574" class="Function Operator">⟩</a>
<a id="5217" href="Cubical.Foundations.Equiv.html#5153" class="Bound">H</a> <a id="5219" class="Symbol">(</a><a id="5220" href="Cubical.Foundations.Equiv.html#5151" class="Bound">f</a> <a id="5222" href="Cubical.Foundations.Equiv.html#5155" class="Bound">a</a><a id="5223" class="Symbol">)</a> <a id="5225" href="Cubical.Foundations.Prelude.html#1705" class="Function Operator">∙</a> <a id="5227" href="Cubical.Foundations.Prelude.html#856" class="Function">refl</a> <a id="5250" href="Cubical.Foundations.Prelude.html#2574" class="Function Operator">≡⟨</a> <a id="5253" href="Cubical.Foundations.Prelude.html#1057" class="Function">cong</a> <a id="5258" class="Symbol">(</a><a id="5259" href="Cubical.Foundations.Prelude.html#1705" class="Function Operator">_∙_</a> <a id="5263" class="Symbol">(</a><a id="5264" href="Cubical.Foundations.Equiv.html#5153" class="Bound">H</a> <a id="5266" class="Symbol">(</a><a id="5267" href="Cubical.Foundations.Equiv.html#5151" class="Bound">f</a> <a id="5269" href="Cubical.Foundations.Equiv.html#5155" class="Bound">a</a><a id="5270" class="Symbol">)))</a> <a id="5274" class="Symbol">(</a><a id="5275" href="Cubical.Foundations.Prelude.html#893" class="Function">sym</a> <a id="5279" class="Symbol">(</a><a id="5280" href="Cubical.Foundations.GroupoidLaws.html#1702" class="Function">rCancel</a> <a id="5288" class="Symbol">(</a><a id="5289" href="Cubical.Foundations.Equiv.html#5153" class="Bound">H</a> <a id="5291" href="Cubical.Foundations.Equiv.html#5155" class="Bound">a</a><a id="5292" class="Symbol">)))</a> <a id="5296" href="Cubical.Foundations.Prelude.html#2574" class="Function Operator">⟩</a>
<a id="5300" href="Cubical.Foundations.Equiv.html#5153" class="Bound">H</a> <a id="5302" class="Symbol">(</a><a id="5303" href="Cubical.Foundations.Equiv.html#5151" class="Bound">f</a> <a id="5305" href="Cubical.Foundations.Equiv.html#5155" class="Bound">a</a><a id="5306" class="Symbol">)</a> <a id="5308" href="Cubical.Foundations.Prelude.html#1705" class="Function Operator">∙</a> <a id="5310" href="Cubical.Foundations.Equiv.html#5153" class="Bound">H</a> <a id="5312" href="Cubical.Foundations.Equiv.html#5155" class="Bound">a</a> <a id="5314" href="Cubical.Foundations.Prelude.html#1705" class="Function Operator">∙</a> <a id="5316" href="Cubical.Foundations.Prelude.html#893" class="Function">sym</a> <a id="5320" class="Symbol">(</a><a id="5321" href="Cubical.Foundations.Equiv.html#5153" class="Bound">H</a> <a id="5323" href="Cubical.Foundations.Equiv.html#5155" class="Bound">a</a><a id="5324" class="Symbol">)</a> <a id="5333" href="Cubical.Foundations.Prelude.html#2574" class="Function Operator">≡⟨</a> <a id="5336" href="Cubical.Foundations.GroupoidLaws.html#3414" class="Function">assoc</a> <a id="5342" class="Symbol">_</a> <a id="5344" class="Symbol">_</a> <a id="5346" class="Symbol">_</a> <a id="5348" href="Cubical.Foundations.Prelude.html#2574" class="Function Operator">⟩</a>
<a id="5352" class="Symbol">(</a><a id="5353" href="Cubical.Foundations.Equiv.html#5153" class="Bound">H</a> <a id="5355" class="Symbol">(</a><a id="5356" href="Cubical.Foundations.Equiv.html#5151" class="Bound">f</a> <a id="5358" href="Cubical.Foundations.Equiv.html#5155" class="Bound">a</a><a id="5359" class="Symbol">)</a> <a id="5361" href="Cubical.Foundations.Prelude.html#1705" class="Function Operator">∙</a> <a id="5363" href="Cubical.Foundations.Equiv.html#5153" class="Bound">H</a> <a id="5365" href="Cubical.Foundations.Equiv.html#5155" class="Bound">a</a><a id="5366" class="Symbol">)</a> <a id="5368" href="Cubical.Foundations.Prelude.html#1705" class="Function Operator">∙</a> <a id="5370" href="Cubical.Foundations.Prelude.html#893" class="Function">sym</a> <a id="5374" class="Symbol">(</a><a id="5375" href="Cubical.Foundations.Equiv.html#5153" class="Bound">H</a> <a id="5377" href="Cubical.Foundations.Equiv.html#5155" class="Bound">a</a><a id="5378" class="Symbol">)</a> <a id="5385" href="Cubical.Foundations.Prelude.html#2574" class="Function Operator">≡⟨</a> <a id="5388" href="Cubical.Foundations.Prelude.html#1057" class="Function">cong</a> <a id="5393" class="Symbol">(λ</a> <a id="5396" href="Cubical.Foundations.Equiv.html#5396" class="Bound">x</a> <a id="5398" class="Symbol">→</a> <a id="5401" href="Cubical.Foundations.Equiv.html#5396" class="Bound">x</a> <a id="5403" href="Cubical.Foundations.Prelude.html#1705" class="Function Operator">∙</a> <a id="5405" class="Symbol">(</a><a id="5406" href="Cubical.Foundations.Prelude.html#893" class="Function">sym</a> <a id="5410" class="Symbol">(</a><a id="5411" href="Cubical.Foundations.Equiv.html#5153" class="Bound">H</a> <a id="5413" href="Cubical.Foundations.Equiv.html#5155" class="Bound">a</a><a id="5414" class="Symbol">)))</a> <a id="5418" class="Symbol">(</a><a id="5419" href="Cubical.Foundations.Equiv.html#4402" class="Function">homotopyNatural</a> <a id="5435" href="Cubical.Foundations.Equiv.html#5153" class="Bound">H</a> <a id="5437" class="Symbol">(</a><a id="5438" href="Cubical.Foundations.Equiv.html#5153" class="Bound">H</a> <a id="5440" href="Cubical.Foundations.Equiv.html#5155" class="Bound">a</a><a id="5441" class="Symbol">))</a> <a id="5444" href="Cubical.Foundations.Prelude.html#2574" class="Function Operator">⟩</a>
<a id="5448" class="Symbol">(</a><a id="5449" href="Cubical.Foundations.Prelude.html#1057" class="Function">cong</a> <a id="5454" href="Cubical.Foundations.Equiv.html#5151" class="Bound">f</a> <a id="5456" class="Symbol">(</a><a id="5457" href="Cubical.Foundations.Equiv.html#5153" class="Bound">H</a> <a id="5459" href="Cubical.Foundations.Equiv.html#5155" class="Bound">a</a><a id="5460" class="Symbol">)</a> <a id="5462" href="Cubical.Foundations.Prelude.html#1705" class="Function Operator">∙</a> <a id="5464" href="Cubical.Foundations.Equiv.html#5153" class="Bound">H</a> <a id="5466" href="Cubical.Foundations.Equiv.html#5155" class="Bound">a</a><a id="5467" class="Symbol">)</a> <a id="5469" href="Cubical.Foundations.Prelude.html#1705" class="Function Operator">∙</a> <a id="5471" href="Cubical.Foundations.Prelude.html#893" class="Function">sym</a> <a id="5475" class="Symbol">(</a><a id="5476" href="Cubical.Foundations.Equiv.html#5153" class="Bound">H</a> <a id="5478" href="Cubical.Foundations.Equiv.html#5155" class="Bound">a</a><a id="5479" class="Symbol">)</a> <a id="5481" href="Cubical.Foundations.Prelude.html#2574" class="Function Operator">≡⟨</a> <a id="5484" href="Cubical.Foundations.Prelude.html#893" class="Function">sym</a> <a id="5488" class="Symbol">(</a><a id="5489" href="Cubical.Foundations.GroupoidLaws.html#3414" class="Function">assoc</a> <a id="5495" class="Symbol">_</a> <a id="5497" class="Symbol">_</a> <a id="5499" class="Symbol">_)</a> <a id="5502" href="Cubical.Foundations.Prelude.html#2574" class="Function Operator">⟩</a>
<a id="5506" href="Cubical.Foundations.Prelude.html#1057" class="Function">cong</a> <a id="5511" href="Cubical.Foundations.Equiv.html#5151" class="Bound">f</a> <a id="5513" class="Symbol">(</a><a id="5514" href="Cubical.Foundations.Equiv.html#5153" class="Bound">H</a> <a id="5516" href="Cubical.Foundations.Equiv.html#5155" class="Bound">a</a><a id="5517" class="Symbol">)</a> <a id="5519" href="Cubical.Foundations.Prelude.html#1705" class="Function Operator">∙</a> <a id="5521" href="Cubical.Foundations.Equiv.html#5153" class="Bound">H</a> <a id="5523" href="Cubical.Foundations.Equiv.html#5155" class="Bound">a</a> <a id="5525" href="Cubical.Foundations.Prelude.html#1705" class="Function Operator">∙</a> <a id="5527" href="Cubical.Foundations.Prelude.html#893" class="Function">sym</a> <a id="5531" class="Symbol">(</a><a id="5532" href="Cubical.Foundations.Equiv.html#5153" class="Bound">H</a> <a id="5534" href="Cubical.Foundations.Equiv.html#5155" class="Bound">a</a><a id="5535" class="Symbol">)</a> <a id="5539" href="Cubical.Foundations.Prelude.html#2574" class="Function Operator">≡⟨</a> <a id="5542" href="Cubical.Foundations.Prelude.html#1057" class="Function">cong</a> <a id="5547" class="Symbol">(</a><a id="5548" href="Cubical.Foundations.Prelude.html#1705" class="Function Operator">_∙_</a> <a id="5552" class="Symbol">(</a><a id="5553" href="Cubical.Foundations.Prelude.html#1057" class="Function">cong</a> <a id="5558" href="Cubical.Foundations.Equiv.html#5151" class="Bound">f</a> <a id="5560" class="Symbol">(</a><a id="5561" href="Cubical.Foundations.Equiv.html#5153" class="Bound">H</a> <a id="5563" href="Cubical.Foundations.Equiv.html#5155" class="Bound">a</a><a id="5564" class="Symbol">)))</a> <a id="5568" class="Symbol">(</a><a id="5569" href="Cubical.Foundations.GroupoidLaws.html#1702" class="Function">rCancel</a> <a id="5577" class="Symbol">_)</a> <a id="5580" href="Cubical.Foundations.Prelude.html#2574" class="Function Operator">⟩</a>
<a id="5584" href="Cubical.Foundations.Prelude.html#1057" class="Function">cong</a> <a id="5589" href="Cubical.Foundations.Equiv.html#5151" class="Bound">f</a> <a id="5591" class="Symbol">(</a><a id="5592" href="Cubical.Foundations.Equiv.html#5153" class="Bound">H</a> <a id="5594" href="Cubical.Foundations.Equiv.html#5155" class="Bound">a</a><a id="5595" class="Symbol">)</a> <a id="5597" href="Cubical.Foundations.Prelude.html#1705" class="Function Operator">∙</a> <a id="5599" href="Cubical.Foundations.Prelude.html#856" class="Function">refl</a> <a id="5617" href="Cubical.Foundations.Prelude.html#2574" class="Function Operator">≡⟨</a> <a id="5620" href="Cubical.Foundations.Prelude.html#893" class="Function">sym</a> <a id="5624" class="Symbol">(</a><a id="5625" href="Cubical.Foundations.GroupoidLaws.html#431" class="Function">rUnit</a> <a id="5631" class="Symbol">_)</a> <a id="5634" href="Cubical.Foundations.Prelude.html#2574" class="Function Operator">⟩</a>
<a id="5638" href="Cubical.Foundations.Prelude.html#1057" class="Function">cong</a> <a id="5643" href="Cubical.Foundations.Equiv.html#5151" class="Bound">f</a> <a id="5645" class="Symbol">(</a><a id="5646" href="Cubical.Foundations.Equiv.html#5153" class="Bound">H</a> <a id="5648" href="Cubical.Foundations.Equiv.html#5155" class="Bound">a</a><a id="5649" class="Symbol">)</a> <a id="5651" href="Cubical.Foundations.Prelude.html#2780" class="Function Operator">∎</a>
<a id="equivPi"></a><a id="5654" href="Cubical.Foundations.Equiv.html#5654" class="Function">equivPi</a>
<a id="5664" class="Symbol">:</a> <a id="5666" class="Symbol">∀{</a><a id="5668" href="Cubical.Foundations.Equiv.html#5668" class="Bound">F</a> <a id="5670" class="Symbol">:</a> <a id="5672" href="Cubical.Foundations.Equiv.html#860" class="Generalizable">A</a> <a id="5674" class="Symbol">→</a> <a id="5676" class="PrimitiveType">Set</a> <a id="5680" href="Cubical.Foundations.Equiv.html#838" class="Generalizable">ℓ</a><a id="5681" class="Symbol">}</a> <a id="5683" class="Symbol">{</a><a id="5684" href="Cubical.Foundations.Equiv.html#5684" class="Bound">G</a> <a id="5686" class="Symbol">:</a> <a id="5688" href="Cubical.Foundations.Equiv.html#860" class="Generalizable">A</a> <a id="5690" class="Symbol">→</a> <a id="5692" class="PrimitiveType">Set</a> <a id="5696" href="Cubical.Foundations.Equiv.html#840" class="Generalizable">ℓ'</a><a id="5698" class="Symbol">}</a>
<a id="5702" class="Symbol">→</a> <a id="5704" class="Symbol">((</a><a id="5706" href="Cubical.Foundations.Equiv.html#5706" class="Bound">x</a> <a id="5708" class="Symbol">:</a> <a id="5710" href="Cubical.Foundations.Equiv.html#860" class="Generalizable">A</a><a id="5711" class="Symbol">)</a> <a id="5713" class="Symbol">→</a> <a id="5715" href="Cubical.Foundations.Equiv.html#5668" class="Bound">F</a> <a id="5717" href="Cubical.Foundations.Equiv.html#5706" class="Bound">x</a> <a id="5719" href="Agda.Builtin.Cubical.Glue.html#1051" class="Function Operator">≃</a> <a id="5721" href="Cubical.Foundations.Equiv.html#5684" class="Bound">G</a> <a id="5723" href="Cubical.Foundations.Equiv.html#5706" class="Bound">x</a><a id="5724" class="Symbol">)</a> <a id="5726" class="Symbol">→</a> <a id="5728" class="Symbol">(((</a><a id="5731" href="Cubical.Foundations.Equiv.html#5731" class="Bound">x</a> <a id="5733" class="Symbol">:</a> <a id="5735" href="Cubical.Foundations.Equiv.html#860" class="Generalizable">A</a><a id="5736" class="Symbol">)</a> <a id="5738" class="Symbol">→</a> <a id="5740" href="Cubical.Foundations.Equiv.html#5668" class="Bound">F</a> <a id="5742" href="Cubical.Foundations.Equiv.html#5731" class="Bound">x</a><a id="5743" class="Symbol">)</a> <a id="5745" href="Agda.Builtin.Cubical.Glue.html#1051" class="Function Operator">≃</a> <a id="5747" class="Symbol">((</a><a id="5749" href="Cubical.Foundations.Equiv.html#5749" class="Bound">x</a> <a id="5751" class="Symbol">:</a> <a id="5753" href="Cubical.Foundations.Equiv.html#860" class="Generalizable">A</a><a id="5754" class="Symbol">)</a> <a id="5756" class="Symbol">→</a> <a id="5758" href="Cubical.Foundations.Equiv.html#5684" class="Bound">G</a> <a id="5760" href="Cubical.Foundations.Equiv.html#5749" class="Bound">x</a><a id="5761" class="Symbol">))</a>
<a id="5764" href="Cubical.Foundations.Equiv.html#5654" class="Function">equivPi</a> <a id="5772" href="Cubical.Foundations.Equiv.html#5772" class="Bound">k</a> <a id="5774" class="Symbol">.</a><a id="5775" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a> <a id="5779" href="Cubical.Foundations.Equiv.html#5779" class="Bound">f</a> <a id="5781" href="Cubical.Foundations.Equiv.html#5781" class="Bound">x</a> <a id="5783" class="Symbol">=</a> <a id="5785" href="Cubical.Foundations.Equiv.html#5772" class="Bound">k</a> <a id="5787" href="Cubical.Foundations.Equiv.html#5781" class="Bound">x</a> <a id="5789" class="Symbol">.</a><a id="5790" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a> <a id="5794" class="Symbol">(</a><a id="5795" href="Cubical.Foundations.Equiv.html#5779" class="Bound">f</a> <a id="5797" href="Cubical.Foundations.Equiv.html#5781" class="Bound">x</a><a id="5798" class="Symbol">)</a>
<a id="5800" href="Cubical.Foundations.Equiv.html#5654" class="Function">equivPi</a> <a id="5808" href="Cubical.Foundations.Equiv.html#5808" class="Bound">k</a> <a id="5810" class="Symbol">.</a><a id="5811" href="Agda.Builtin.Sigma.html#264" class="Field">snd</a> <a id="5815" class="Symbol">.</a><a id="5816" href="Agda.Builtin.Cubical.Glue.html#971" class="Field">equiv-proof</a> <a id="5828" href="Cubical.Foundations.Equiv.html#5828" class="Bound">f</a>
<a id="5832" class="Symbol">.</a><a id="5833" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a> <a id="5837" class="Symbol">.</a><a id="5838" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a> <a id="5842" href="Cubical.Foundations.Equiv.html#5842" class="Bound">x</a> <a id="5844" class="Symbol">=</a> <a id="5846" href="Cubical.Foundations.Equiv.html#1096" class="Function">equivCtr</a> <a id="5855" class="Symbol">(</a><a id="5856" href="Cubical.Foundations.Equiv.html#5808" class="Bound">k</a> <a id="5858" href="Cubical.Foundations.Equiv.html#5842" class="Bound">x</a><a id="5859" class="Symbol">)</a> <a id="5861" class="Symbol">(</a><a id="5862" href="Cubical.Foundations.Equiv.html#5828" class="Bound">f</a> <a id="5864" href="Cubical.Foundations.Equiv.html#5842" class="Bound">x</a><a id="5865" class="Symbol">)</a> <a id="5867" class="Symbol">.</a><a id="5868" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a>
<a id="5872" href="Cubical.Foundations.Equiv.html#5654" class="Function">equivPi</a> <a id="5880" href="Cubical.Foundations.Equiv.html#5880" class="Bound">k</a> <a id="5882" class="Symbol">.</a><a id="5883" href="Agda.Builtin.Sigma.html#264" class="Field">snd</a> <a id="5887" class="Symbol">.</a><a id="5888" href="Agda.Builtin.Cubical.Glue.html#971" class="Field">equiv-proof</a> <a id="5900" href="Cubical.Foundations.Equiv.html#5900" class="Bound">f</a>
<a id="5904" class="Symbol">.</a><a id="5905" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a> <a id="5909" class="Symbol">.</a><a id="5910" href="Agda.Builtin.Sigma.html#264" class="Field">snd</a> <a id="5914" href="Cubical.Foundations.Equiv.html#5914" class="Bound">i</a> <a id="5916" href="Cubical.Foundations.Equiv.html#5916" class="Bound">x</a> <a id="5918" class="Symbol">=</a> <a id="5920" href="Cubical.Foundations.Equiv.html#1096" class="Function">equivCtr</a> <a id="5929" class="Symbol">(</a><a id="5930" href="Cubical.Foundations.Equiv.html#5880" class="Bound">k</a> <a id="5932" href="Cubical.Foundations.Equiv.html#5916" class="Bound">x</a><a id="5933" class="Symbol">)</a> <a id="5935" class="Symbol">(</a><a id="5936" href="Cubical.Foundations.Equiv.html#5900" class="Bound">f</a> <a id="5938" href="Cubical.Foundations.Equiv.html#5916" class="Bound">x</a><a id="5939" class="Symbol">)</a> <a id="5941" class="Symbol">.</a><a id="5942" href="Agda.Builtin.Sigma.html#264" class="Field">snd</a> <a id="5946" href="Cubical.Foundations.Equiv.html#5914" class="Bound">i</a>
<a id="5948" href="Cubical.Foundations.Equiv.html#5654" class="Function">equivPi</a> <a id="5956" href="Cubical.Foundations.Equiv.html#5956" class="Bound">k</a> <a id="5958" class="Symbol">.</a><a id="5959" href="Agda.Builtin.Sigma.html#264" class="Field">snd</a> <a id="5963" class="Symbol">.</a><a id="5964" href="Agda.Builtin.Cubical.Glue.html#971" class="Field">equiv-proof</a> <a id="5976" href="Cubical.Foundations.Equiv.html#5976" class="Bound">f</a>
<a id="5980" class="Symbol">.</a><a id="5981" href="Agda.Builtin.Sigma.html#264" class="Field">snd</a> <a id="5985" class="Symbol">(</a><a id="5986" href="Cubical.Foundations.Equiv.html#5986" class="Bound">g</a> <a id="5988" href="Agda.Builtin.Sigma.html#236" class="InductiveConstructor Operator">,</a> <a id="5990" href="Cubical.Foundations.Equiv.html#5990" class="Bound">p</a><a id="5991" class="Symbol">)</a> <a id="5993" href="Cubical.Foundations.Equiv.html#5993" class="Bound">i</a> <a id="5995" class="Symbol">.</a><a id="5996" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a> <a id="6000" href="Cubical.Foundations.Equiv.html#6000" class="Bound">x</a> <a id="6002" class="Symbol">=</a> <a id="6004" href="Cubical.Foundations.Equiv.html#1222" class="Function">equivCtrPath</a> <a id="6017" class="Symbol">(</a><a id="6018" href="Cubical.Foundations.Equiv.html#5956" class="Bound">k</a> <a id="6020" href="Cubical.Foundations.Equiv.html#6000" class="Bound">x</a><a id="6021" class="Symbol">)</a> <a id="6023" class="Symbol">(</a><a id="6024" href="Cubical.Foundations.Equiv.html#5976" class="Bound">f</a> <a id="6026" href="Cubical.Foundations.Equiv.html#6000" class="Bound">x</a><a id="6027" class="Symbol">)</a> <a id="6029" class="Symbol">(</a><a id="6030" href="Cubical.Foundations.Equiv.html#5986" class="Bound">g</a> <a id="6032" href="Cubical.Foundations.Equiv.html#6000" class="Bound">x</a> <a id="6034" href="Agda.Builtin.Sigma.html#236" class="InductiveConstructor Operator">,</a> <a id="6036" class="Symbol">λ</a> <a id="6038" href="Cubical.Foundations.Equiv.html#6038" class="Bound">j</a> <a id="6040" class="Symbol">→</a> <a id="6042" href="Cubical.Foundations.Equiv.html#5990" class="Bound">p</a> <a id="6044" href="Cubical.Foundations.Equiv.html#6038" class="Bound">j</a> <a id="6046" href="Cubical.Foundations.Equiv.html#6000" class="Bound">x</a><a id="6047" class="Symbol">)</a> <a id="6049" href="Cubical.Foundations.Equiv.html#5993" class="Bound">i</a> <a id="6051" class="Symbol">.</a><a id="6052" href="Agda.Builtin.Sigma.html#252" class="Field">fst</a>
<a id="6056" href="Cubical.Foundations.Equiv.html#5654" class="Function">equivPi</a> <a id="6064" href="Cubical.Foundations.Equiv.html#6064" class="Bound">k</a> <a id="6066" class="Symbol">.</a><a id="6067" href="Agda.Builtin.Sigma.html#264" class="Field">snd</a> <a id="6071" class="Symbol">.</a><a id="6072" href="Agda.Builtin.Cubical.Glue.html#971" class="Field">equiv-proof</a> <a id="6084" href="Cubical.Foundations.Equiv.html#6084" class="Bound">f</a>
<a id="6088" class="Symbol">.</a><a id="6089" href="Agda.Builtin.Sigma.html#264" class="Field">snd</a> <a id="6093" class="Symbol">(</a><a id="6094" href="Cubical.Foundations.Equiv.html#6094" class="Bound">g</a> <a id="6096" href="Agda.Builtin.Sigma.html#236" class="InductiveConstructor Operator">,</a> <a id="6098" href="Cubical.Foundations.Equiv.html#6098" class="Bound">p</a><a id="6099" class="Symbol">)</a> <a id="6101" href="Cubical.Foundations.Equiv.html#6101" class="Bound">i</a> <a id="6103" class="Symbol">.</a><a id="6104" href="Agda.Builtin.Sigma.html#264" class="Field">snd</a> <a id="6108" href="Cubical.Foundations.Equiv.html#6108" class="Bound">j</a> <a id="6110" href="Cubical.Foundations.Equiv.html#6110" class="Bound">x</a> <a id="6112" class="Symbol">=</a> <a id="6114" href="Cubical.Foundations.Equiv.html#1222" class="Function">equivCtrPath</a> <a id="6127" class="Symbol">(</a><a id="6128" href="Cubical.Foundations.Equiv.html#6064" class="Bound">k</a> <a id="6130" href="Cubical.Foundations.Equiv.html#6110" class="Bound">x</a><a id="6131" class="Symbol">)</a> <a id="6133" class="Symbol">(</a><a id="6134" href="Cubical.Foundations.Equiv.html#6084" class="Bound">f</a> <a id="6136" href="Cubical.Foundations.Equiv.html#6110" class="Bound">x</a><a id="6137" class="Symbol">)</a> <a id="6139" class="Symbol">(</a><a id="6140" href="Cubical.Foundations.Equiv.html#6094" class="Bound">g</a> <a id="6142" href="Cubical.Foundations.Equiv.html#6110" class="Bound">x</a> <a id="6144" href="Agda.Builtin.Sigma.html#236" class="InductiveConstructor Operator">,</a> <a id="6146" class="Symbol">λ</a> <a id="6148" href="Cubical.Foundations.Equiv.html#6148" class="Bound">k</a> <a id="6150" class="Symbol">→</a> <a id="6152" href="Cubical.Foundations.Equiv.html#6098" class="Bound">p</a> <a id="6154" href="Cubical.Foundations.Equiv.html#6148" class="Bound">k</a> <a id="6156" href="Cubical.Foundations.Equiv.html#6110" class="Bound">x</a><a id="6157" class="Symbol">)</a> <a id="6159" href="Cubical.Foundations.Equiv.html#6101" class="Bound">i</a> <a id="6161" class="Symbol">.</a><a id="6162" href="Agda.Builtin.Sigma.html#264" class="Field">snd</a> <a id="6166" href="Cubical.Foundations.Equiv.html#6108" class="Bound">j</a>
<a id="6169" class="Comment">-- Some helpful notation:</a>
<a id="_≃⟨_⟩_"></a><a id="6195" href="Cubical.Foundations.Equiv.html#6195" class="Function Operator">_≃⟨_⟩_</a> <a id="6202" class="Symbol">:</a> <a id="6204" class="Symbol">(</a><a id="6205" href="Cubical.Foundations.Equiv.html#6205" class="Bound">X</a> <a id="6207" class="Symbol">:</a> <a id="6209" href="Cubical.Core.Primitives.html#957" class="Function">Type</a> <a id="6214" href="Cubical.Foundations.Equiv.html#838" class="Generalizable">ℓ</a><a id="6215" class="Symbol">)</a> <a id="6217" class="Symbol">→</a> <a id="6219" class="Symbol">(</a><a id="6220" href="Cubical.Foundations.Equiv.html#6205" class="Bound">X</a> <a id="6222" href="Agda.Builtin.Cubical.Glue.html#1051" class="Function Operator">≃</a> <a id="6224" href="Cubical.Foundations.Equiv.html#862" class="Generalizable">B</a><a id="6225" class="Symbol">)</a> <a id="6227" class="Symbol">→</a> <a id="6229" class="Symbol">(</a><a id="6230" href="Cubical.Foundations.Equiv.html#862" class="Generalizable">B</a> <a id="6232" href="Agda.Builtin.Cubical.Glue.html#1051" class="Function Operator">≃</a> <a id="6234" href="Cubical.Foundations.Equiv.html#864" class="Generalizable">C</a><a id="6235" class="Symbol">)</a> <a id="6237" class="Symbol">→</a> <a id="6239" class="Symbol">(</a><a id="6240" href="Cubical.Foundations.Equiv.html#6205" class="Bound">X</a> <a id="6242" href="Agda.Builtin.Cubical.Glue.html#1051" class="Function Operator">≃</a> <a id="6244" href="Cubical.Foundations.Equiv.html#864" class="Generalizable">C</a><a id="6245" class="Symbol">)</a>
<a id="6247" class="Symbol">_</a> <a id="6249" href="Cubical.Foundations.Equiv.html#6195" class="Function Operator">≃⟨</a> <a id="6252" href="Cubical.Foundations.Equiv.html#6252" class="Bound">f</a> <a id="6254" href="Cubical.Foundations.Equiv.html#6195" class="Function Operator">⟩</a> <a id="6256" href="Cubical.Foundations.Equiv.html#6256" class="Bound">g</a> <a id="6258" class="Symbol">=</a> <a id="6260" href="Cubical.Foundations.Equiv.html#3257" class="Function">compEquiv</a> <a id="6270" href="Cubical.Foundations.Equiv.html#6252" class="Bound">f</a> <a id="6272" href="Cubical.Foundations.Equiv.html#6256" class="Bound">g</a>
<a id="_■"></a><a id="6275" href="Cubical.Foundations.Equiv.html#6275" class="Function Operator">_■</a> <a id="6278" class="Symbol">:</a> <a id="6280" class="Symbol">(</a><a id="6281" href="Cubical.Foundations.Equiv.html#6281" class="Bound">X</a> <a id="6283" class="Symbol">:</a> <a id="6285" href="Cubical.Core.Primitives.html#957" class="Function">Type</a> <a id="6290" href="Cubical.Foundations.Equiv.html#838" class="Generalizable">ℓ</a><a id="6291" class="Symbol">)</a> <a id="6293" class="Symbol">→</a> <a id="6295" class="Symbol">(</a><a id="6296" href="Cubical.Foundations.Equiv.html#6281" class="Bound">X</a> <a id="6298" href="Agda.Builtin.Cubical.Glue.html#1051" class="Function Operator">≃</a> <a id="6300" href="Cubical.Foundations.Equiv.html#6281" class="Bound">X</a><a id="6301" class="Symbol">)</a>
<a id="6303" href="Cubical.Foundations.Equiv.html#6275" class="Function Operator">_■</a> <a id="6306" class="Symbol">=</a> <a id="6308" href="Cubical.Foundations.Equiv.html#1559" class="Function">idEquiv</a>
<a id="6317" class="Keyword">infixr</a> <a id="6325" class="Number">0</a> <a id="6327" href="Cubical.Foundations.Equiv.html#6195" class="Function Operator">_≃⟨_⟩_</a>
<a id="6334" class="Keyword">infix</a> <a id="6342" class="Number">1</a> <a id="6344" href="Cubical.Foundations.Equiv.html#6275" class="Function Operator">_■</a>
</pre>
{% endraw %}
</body> | 584.648045 | 2,478 | 0.680006 | yue_Hant | 0.440049 |
d5e5970b37e5d5b55e69109223fdd0b59bd28728 | 1,036 | md | Markdown | estimate/add_medicine_estimate.md | trananhchuong/learn-js | 17ed5e16ac09334d89b65b317a17271482921367 | [
"MIT"
] | null | null | null | estimate/add_medicine_estimate.md | trananhchuong/learn-js | 17ed5e16ac09334d89b65b317a17271482921367 | [
"MIT"
] | null | null | null | estimate/add_medicine_estimate.md | trananhchuong/learn-js | 17ed5e16ac09334d89b65b317a17271482921367 | [
"MIT"
] | null | null | null |
# Feature "Medicine Management" Estimate: (13 days)
### Upload file CSV (3 days)
1. Form update file CSV (2 days)
2. Integrate API update (1 day)
### Medicine setting (2 days)
1. Build UI & form edit (1 days)
2. Integrate API update (1 day)
### Add Medicine (3 days)
1. Form add medicine (3 days):
- Build UI (1 day)
- Validate form (1 day)
- Integrate API save (1 day)
### Show list medicine (4 days):
1. Build UI display list of medicine (2 days)
2. Pagination function (1 day)
3. Update/delete medicine function (1 day)
### Testing & bug fixing (1 day)
### Medicine api backend support
#### function save medicine csv:
- Api save csv (excel) list medicine:
- detail: save list medicine in file csv
- function download template prototype
#### function CRUD medicine:
- Api get list units of medicine
- Api add medicine
- Api update medicine
- Api delete medicine
-
#### function display list medicine to dashboard
- Api get medicine list
| 25.268293 | 51 | 0.646718 | eng_Latn | 0.589929 |
d5e5f86abef0b3edbd719227b4036f7d5280b121 | 589 | md | Markdown | api/Visio.Application.Visible.md | RichardCory/VBA-Docs | 1240462311fb77ee051d4e8b7d7a434d7d020dd3 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-03-09T13:24:12.000Z | 2020-03-09T16:19:11.000Z | api/Visio.Application.Visible.md | MarkFern/VBA-Docs | b84627cc8e24acfd336d1e9761a9ddd58f19d352 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | api/Visio.Application.Visible.md | MarkFern/VBA-Docs | b84627cc8e24acfd336d1e9761a9ddd58f19d352 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Application.Visible property (Visio)
keywords: vis_sdr.chm10014650
f1_keywords:
- vis_sdr.chm10014650
ms.prod: visio
api_name:
- Visio.Application.Visible
ms.assetid: 48b0a402-3655-b6aa-19da-145d2c7ceadf
ms.date: 06/08/2017
localization_priority: Normal
---
# Application.Visible property (Visio)
Determines whether an object is visible. Read/write.
## Syntax
_expression_.**Visible**
_expression_ A variable that represents an [Application](./Visio.Application.md) object.
## Return value
Boolean
[!include[Support and feedback](~/includes/feedback-boilerplate.md)] | 19 | 89 | 0.777589 | eng_Latn | 0.63003 |
d5e7e2c3845eff851d55a86f4e6bce0e04ffa1bc | 1,563 | md | Markdown | AplicatieThread/Readme.md | newparts/Android | f5c89a9da7b9b778de08d6f335004fdaca0c56ed | [
"MIT"
] | null | null | null | AplicatieThread/Readme.md | newparts/Android | f5c89a9da7b9b778de08d6f335004fdaca0c56ed | [
"MIT"
] | null | null | null | AplicatieThread/Readme.md | newparts/Android | f5c89a9da7b9b778de08d6f335004fdaca0c56ed | [
"MIT"
] | 23 | 2020-01-15T15:02:39.000Z | 2020-01-15T17:23:03.000Z | Nume proiect: AplicatieThread
Autor: Iuliu Bakcsi
Descriere:
Executarea de operatii de rulare indelungata pe firul principal al aplicatiei poate provoca inghetarea interfetei aplicatiei in cateva secunde fortandu-ne sa inchidem aplicatia. Pentru a evita acest lucru trebuie sa mutam operatiile de acest tip pe un thread separat.
In Android pentru a realiza acest demers avem la indemana mai multe modalitati de executie. Fie cream o clasa care extinde Thread si inlocuieste metoda rulata, fie implementam o interfata Runnable apoi implementam interfata la un nou obiect Thread.
Aceste clase Java de bază construiesc bazele pentru clase precum AsyncTask, HandlerThread și ThreadPoolExecutor.
O alta varianta de trimitere a codului din thread de fundal inapoi la threadul UI se poate printr-un handler care trimite un runnable la MessageQueue din threadul UI.
Pentru a asocia Handlerul cu Looperul threadului principal il punem la dispozitie pe firul principal sau il transmitem pe Looper.getMainLooper la constructor. In loc sa cream un handler, putem folosi, de asemenea, metoda View classes post sau metoda runOnUiThread, care utilizeaza handler-ul principal in interiorul aplicatiei.
Tehnologii folosite (inclusiv biblioteci externe):
Android Studio, Java
Cum se compileaza / ruleaza:
AplicatieThread ruleaza un Thread in background setat la secunda. Pentru a testa functionalitatea aplicatiei am setat schimbarea aspectului unui buton dupa 5 secunde. Pentru verificarea rularii aplicatiei in timp ce este activ threadul am folosit un buton switch.
| 71.045455 | 327 | 0.829814 | ron_Latn | 0.999043 |
d5e8f10c1b6e8715ef66655ded265f7768b4850e | 2,774 | md | Markdown | documentation/3.1ReleaseNotes.md | extratone/bilge | 475769a4aa338183b3ee8ca8e2e2be2c27eec29b | [
"Unlicense"
] | 21 | 2020-11-23T16:09:03.000Z | 2022-03-26T01:53:45.000Z | documentation/3.1ReleaseNotes.md | extratone/bilge | 475769a4aa338183b3ee8ca8e2e2be2c27eec29b | [
"Unlicense"
] | 272 | 2020-11-22T08:24:38.000Z | 2022-03-31T00:21:37.000Z | documentation/3.1ReleaseNotes.md | extratone/bilge | 475769a4aa338183b3ee8ca8e2e2be2c27eec29b | [
"Unlicense"
] | 1 | 2021-09-14T08:18:13.000Z | 2021-09-14T08:18:13.000Z | # Bilge 3.1 Release Notes
Howdy Writeas/WriteFreely people!
In this release, I hope I have finally delivered a fairly-polished, relatively thoroughly-tested, and _even somewhat intuitively personalizable_ style configuration for you!
I'm going to (at least this once) be excruciatingly thorough in my presentation of what changes I've decided worth this release, why I set about modifying them, and precisely how they were implemented.
Largely to demonstrate in-depth CSS configuration within our particular/somewhat niche CMS environment in a visual/semi-chronological medium.
## Changes
* #49 - Added a super-cropped, sortolf web-optimized capture of @taroyabuki's [single-page Unicode project](https://github.com/taroyabuki/onepage-unicode-chars).
* #61 - With Write.as's addition of [Rich Media Embed support](https://discuss.write.as/t/rich-media-embeds/2425) via Embedly, I originally started this Issue with the intention of going back through *the entire* *Psalms* archive and converting every supported HTML embed into the raw URL of the targets. I made some significant progress, but ultimately decided to use my time doing something else and wait to apply this treatment to older posts until/unless I have another reason to edit a given post in the future. To track the state of embeds on Writeas, going forward, see: [the embedas repo](https://github.com/embedas/go-embed), [the Gist I created](https://gist.github.com/extratone/750847103dd5cd9da52fbd51b1c2e378) (and will do my best to keep regularly updated) and *The Psalms*' updated [public test page](https://bilgel.world/test).
* #24 - The Hypothes.is sidebar was being a pain in the ass because I accidentally configured it to expand immediately upon anyone landing on the page... That's been resolved.
* #54 - Added CSS for code blocks including syntax highlighting. Here's how it should look:
* #39 - Added CSS for Tables as well. (Not quite satisfied with the look but it's certainly better than it was.)
* #125 - Added CSS for GitHub Gists since they are explicitly supported by the new media embed integration. *Definitely* have more to do, but the result should suffice for a while.
***
**For the next release**, I *really will* take care of #52 Footnotes... But it's going to be a hot minute.
 | 89.483871 | 844 | 0.785508 | eng_Latn | 0.981834 |
d5e97c2e9f736531ed9c9a8f99f7a9fcca1e893d | 688 | md | Markdown | shared/README.md | vam-google/gapic-generator-ruby | ec712cc717307d94bfbd14085aafeed8809c7041 | [
"Apache-2.0"
] | 26 | 2018-10-29T20:07:46.000Z | 2022-03-10T15:52:04.000Z | shared/README.md | vam-google/gapic-generator-ruby | ec712cc717307d94bfbd14085aafeed8809c7041 | [
"Apache-2.0"
] | 365 | 2018-11-02T21:56:39.000Z | 2022-03-08T03:59:20.000Z | shared/README.md | vam-google/gapic-generator-ruby | ec712cc717307d94bfbd14085aafeed8809c7041 | [
"Apache-2.0"
] | 23 | 2018-10-31T23:45:28.000Z | 2022-02-16T18:14:46.000Z | # Shared files and tasks for Ruby API Client Generator gems
This directory contains the tasks and files used for the gapic generator gems.
Including the repository for the shared protos and their binary files, as well
as the mechanism to generate new binary files.
## Usage
### Generating Binary Input files
The binary input files can be generated using the `gen` rake task:
```sh
$ cd shared
$ bundle update
$ bundle exec rake gen
```
## Showcase Tests
This project includes a functional test suite for the Ruby GAPIC generator. See
[Showcase](https://github.com/googleapis/gapic-showcase) for more details.
```sh
$ cd shared
$ bundle update
$ bundle exec rake test:showcase
```
| 23.724138 | 79 | 0.761628 | eng_Latn | 0.98496 |
d5e9a63eaa4c8ec1aad00862704fedff8946ec4c | 16,032 | md | Markdown | docs/vs-2015/modeling/add-custom-architecture-validation-to-layer-diagrams.md | rfakhouri/visualstudio-docs.cs-cz | 3d540a168c09a23b855f746696062fd9954b8dd5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vs-2015/modeling/add-custom-architecture-validation-to-layer-diagrams.md | rfakhouri/visualstudio-docs.cs-cz | 3d540a168c09a23b855f746696062fd9954b8dd5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vs-2015/modeling/add-custom-architecture-validation-to-layer-diagrams.md | rfakhouri/visualstudio-docs.cs-cz | 3d540a168c09a23b855f746696062fd9954b8dd5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Přidání ověřování vlastní architektury do diagramů vrstev | Dokumentace Microsoftu
ms.date: 11/15/2016
ms.prod: visual-studio-dev14
ms.technology: vs-ide-modeling
ms.topic: conceptual
helpviewer_keywords:
- layer diagrams, adding custom validation
ms.assetid: fed7bc08-295a-46d6-9fd8-fb537f1f75f1
caps.latest.revision: 44
author: gewarren
ms.author: gewarren
manager: jillfra
ms.openlocfilehash: 920b15d1cd4f7ed0ec11614a50f5dd32e050995a
ms.sourcegitcommit: 47eeeeadd84c879636e9d48747b615de69384356
ms.translationtype: HT
ms.contentlocale: cs-CZ
ms.lasthandoff: 04/23/2019
ms.locfileid: "63432399"
---
# <a name="add-custom-architecture-validation-to-layer-diagrams"></a>Přidání ověření vlastní architektury do diagramů vrstev
[!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
V sadě Visual Studio uživatelé mohou ověřit zdrojový kód v projektu proti vrstvě modelu, tak, aby mohli ověřit, že zdrojový kód odpovídá závislostem na diagramu vrstvy. Existuje standardní ověřovací algoritmus, ale můžete definovat vlastní rozšíření ověřování.
Když uživatel vybere **ověřit architekturu** příkaz na diagramu vrstvy, je vyvolána metoda standardního ověření, následovaný všemi rozšířeními ověření, které byly nainstalovány.
> [!NOTE]
> Ověření v diagramu vrstvy není stejné jako ověření v diagramech UML. V diagramu vrstev je hlavním účelem porovnat diagram pomocí programového kódu v dalších částech tohoto řešení.
Rozšíření ověření vrstvy můžete zabalit do Visual Studio integrace rozšíření (VSIX), které můžete distribuovat ostatním uživatelům aplikace Visual Studio. V rozšíření VSIX můžete umístit svůj validátor buď samostatně, nebo ho můžete zkombinovat ve stejném souboru VSIX jako další rozšíření. Měli byste psát kód validátoru ve svém vlastním projektu sady Visual Studio, není ve stejném projektu jako další rozšíření.
> [!WARNING]
> Po vytvoření projektu ověření zkopírujte [ukázkový kód](#example) na konci tohoto tématu a upravte, vlastních potřeb.
## <a name="requirements"></a>Požadavky
Zobrazit [požadavky](../modeling/extend-layer-diagrams.md#prereqs).
## <a name="defining-a-layer-validator-in-a-new-vsix"></a>Definování ověřování vrstvy v novém souboru VSIX
Nejrychlejší způsob vytváření validátoru je použití šablony projektu. To umístí kód a VSIX manifest do stejného projektu.
#### <a name="to-define-an-extension-by-using-a-project-template"></a>Definování rozšíření pomocí šablony projektu
1. Vytvoření projektu v novém řešení pomocí **nový projekt** příkaz **souboru** nabídky.
2. V **nový projekt** dialogovém okně **projekty modelování**vyberte **rozšíření ověřování návrháře vrstev**.
Šablona vytvoří projekt, který obsahuje malý příklad.
> [!WARNING]
> Do šablony makethe fungovat správně:
>
> - Upravte volání `LogValidationError` odebrat volitelné argumenty `errorSourceNodes` a `errorTargetNodes`.
> - Pokud používáte vlastní vlastnosti, použijte aktualizace uvedené v [přidání vlastních vlastností do diagramů vrstev](../modeling/add-custom-properties-to-layer-diagrams.md).
3. Upravte kód, aby definoval vaše ověření. Další informace najdete v tématu [programování ověření](#programming).
4. Chcete-li otestovat rozšíření, naleznete v tématu [ladění ověřování vrstev](#debugging).
> [!NOTE]
> Vaše metoda bude volána pouze za zvláštních okolností a zarážky nebudou fungovat automaticky. Další informace najdete v tématu [ladění ověřování vrstev](#debugging).
5. Chcete-li nainstalovat rozšíření v instanci hlavní aplikace [!INCLUDE[vsprvs](../includes/vsprvs-md.md)], nebo v jiném počítači, vyhledejte **VSIX** ve *bin\\* . Zkopírujte ho do počítače, ve které chcete nainstalovat a poklepejte na něj. Chcete-li ho odinstalovat, použijte **rozšíření a aktualizace** na **nástroje** nabídky.
## <a name="adding-a-layer-validator-to-a-separate-vsix"></a>Přidání validátoru vrstvy do samostatného souboru VSIX
Pokud chcete vytvořit jeden VSIX, který obsahuje validátory vrstvy, příkazy a další rozšíření, doporučujeme vytvořit jeden projekt k definování VSIX a samostatné projekty pro obslužné rutiny. Informace o dalších typech rozšíření modelu naleznete v tématu [modelů a diagramů UML rozšířit](../modeling/extend-uml-models-and-diagrams.md).
#### <a name="to-add-layer-validation-to-a-separate-vsix"></a>Přidání ověření vrstvy do samostatného souboru VSIX
1. Vytvořte projekt knihovny tříd v nové nebo existující řešení sady Visual Studio. V **nový projekt** dialogové okno, klikněte na tlačítko **Visual C#** a potom klikněte na tlačítko **knihovny tříd**. Tento projekt bude obsahovat třídu ověřování vrstvy.
2. Určete nebo vytvořte VSIX projekt ve vašem řešení. Projekt VSIX obsahuje soubor s názvem **source.extension.vsixmanifest**. Pokud budete muset přidat projekt VSIX, postupujte podle těchto kroků:
1. V **nový projekt** dialogového okna zvolte **Visual C#** , **rozšiřitelnost**, **projekt VSIX**.
2. V **Průzkumníka řešení**, v místní nabídce projektu VSIX **nastavit jako spouštěný projekt**.
3. V **source.extension.vsixmanifest**v části **prostředky**, přidejte vrstvu ověřování projektu jako komponentu MEF:
1. Zvolte **nové**.
2. V **přidat nové aktivum** dialogovém okně nastavení:
**Type** = **Microsoft.VisualStudio.MefComponent**
**Zdroj** = **projekt v aktuálním řešení**
**Projekt** = *projektu program pro ověření*
4. Musíte taky přidat ji jako vrstvu ověřování:
1. Zvolte **nové**.
2. V **přidat nové aktivum** dialogovém okně nastavení:
**Type** = **Microsoft.VisualStudio.ArchitectureTools.Layer.Validator**. To však není jednou z možností v rozevíracím seznamu. Je nutné zadat z klávesnice.
**Zdroj** = **projekt v aktuálním řešení**
**Projekt** = *projektu program pro ověření*
5. Vraťte se do projektu ověření vrstvy a přidejte následující odkazy projektu:
|**Referenční informace**|**To umožňuje provést**|
|-------------------|------------------------------------|
|Microsoft.VisualStudio.GraphModel.dll|Přečtěte si graf architektury|
|Microsoft.VisualStudio.ArchitectureTools.Extensibility.CodeSchema.dll|Přečtěte si, že v modelu DOM kódu spojený s vrstvami|
|Microsoft.VisualStudio.ArchitectureTools.Extensibility.Layer.dll|Přečtěte si model vrstva|
|Microsoft.VisualStudio.ArchitectureTools.Extensibility|Číst a aktualizovat tvary a diagramy.|
|System.ComponentModel.Composition|Definovat součást ověřování pomocí Managed Extensibility Framework (MEF)|
|Microsoft.VisualStudio.Modeling.Sdk.[version]|Definovat rozšíření modelování|
6. Zkopírujte ukázkový kód na konci tohoto tématu do souboru třídy v projektu knihovny ověřování tak, aby obsahovala kód pro ověření. Další informace najdete v tématu [programování ověření](#programming).
7. Chcete-li otestovat rozšíření, naleznete v tématu [ladění ověřování vrstev](#debugging).
> [!NOTE]
> Vaše metoda bude volána pouze za zvláštních okolností a zarážky nebudou fungovat automaticky. Další informace najdete v tématu [ladění ověřování vrstev](#debugging).
8. Chcete-li nainstalovat VSIX v instanci hlavní aplikace [!INCLUDE[vsprvs](../includes/vsprvs-md.md)], nebo v jiném počítači, vyhledejte **VSIX** ve **bin** adresáře projektu VSIX. Zkopírujte ho do počítače, ve které chcete nainstalovat VSIX. Poklikejte na soubor VSIX v Průzkumníku Windows. (Průzkumník souborů v systému Windows 8.)
Chcete-li ho odinstalovat, použijte **rozšíření a aktualizace** na **nástroje** nabídky.
## <a name="programming"></a> Ověření programování
K definování ověření přípony vrstvy definujete třídu, která má následující vlastnosti:
- Celková forma deklarace je následující:
```
using System.ComponentModel.Composition;
using Microsoft.VisualStudio.ArchitectureTools.Extensibility.CodeSchema;
using Microsoft.VisualStudio.ArchitectureTools.Extensibility.Layer;
using Microsoft.VisualStudio.GraphModel;
...
[Export(typeof(IValidateArchitectureExtension))]
public partial class Validator1Extension :
IValidateArchitectureExtension
{
public void ValidateArchitecture(Graph graph)
{
GraphSchema schema = graph.DocumentSchema;
...
} }
```
- Pokud zjistíte chybu, můžete ji ohlásit pomocí `LogValidationError()`.
> [!WARNING]
> Nepoužívejte volitelné parametry `LogValidationError`.
Pokud uživatel vyvolá **ověřit architekturu** příkaz nabídky, systém modulu runtime vrstvy zanalyzuje vrstvy a jejich artefakty k vytvoření grafu. Graf má čtyři části:
- Modely vrstvy [!INCLUDE[vsprvs](../includes/vsprvs-md.md)] řešení, které jsou reprezentovány jako uzly a odkazy v grafu.
- Kód, položky projektu a další artefakty, které jsou definovány v řešení a reprezentovány jako uzly a odkazy, které představují závislosti zjištěné v procesu analýzy.
- Propojení z uzlů vrstvy do uzlů kódových artefaktů.
- Uzly, které představují chyby zjištěné validátorem.
Pokud byl vytvořen graf, je volána metoda standardního ověření. Po jejím dokončení, všechny metody nainstalovaných rozšíření ověřování jsou zavolány v nespecifikovaném pořadí. Graf je předán pro každou `ValidateArchitecture` metodu, která může prohledávat graf a podávat zprávy o chybách, které nalezne.
> [!NOTE]
> Toto není stejný jako proces ověření, který je použit pro diagramy UML a není stejný jako proces ověření, který lze použít v jazycích specifické pro doménu.
Metody ověřování by neměly měnit model vrstvy nebo kód, který se ověřuje.
Model grafu je definován v <xref:Microsoft.VisualStudio.GraphModel>. Jeho hlavní třídy jsou <xref:Microsoft.VisualStudio.GraphModel.GraphNode> a <xref:Microsoft.VisualStudio.GraphModel.GraphLink>.
Každý uzel a každý odkaz má jednu nebo více kategorií, které určují typ prvku nebo vztahu, který představuje. Uzly typického grafu jsou následující kategorie:
- Dsl.LayerModel
- Dsl.Layer
- Dsl.Reference
- CodeSchema_Type
- CodeSchema_Namespace
- CodeSchema_Type
- CodeSchema_Method
- CodeSchema_Field
- CodeSchema_Property
Propojení z vrstev do prvků v kódu mají kategorii "Představuje".
## <a name="debugging"></a> Ladění ověřování
Chcete-li ladit rozšíření ověřování vrstvy, stiskněte CTRL + F5. Experimentální instanci [!INCLUDE[vsprvs](../includes/vsprvs-md.md)] otevře. V tomto případě otevřete nebo vytvořte model vrstev. Tento model musí být přidružen ke kódu a musí mít alespoň jednu závislost.
### <a name="test-with-a-solution-that-contains-dependencies"></a>Otestujte řešení, která obsahuje závislosti
Ověření není provedena, pokud jsou k dispozici následující vlastnosti:
- Na diagramu vrstvy je alespoň jeden odkaz závislosti.
- Existují vrstvy v modelu, které jsou spojeny s prvky kódu.
Při prvním spuštění experimentální instance [!INCLUDE[vsprvs](../includes/vsprvs-md.md)] k testování rozšíření ověřování otevřete nebo vytvořte řešení, které má tyto vlastnosti.
### <a name="run-clean-solution-before-validate-architecture"></a>Spusťte čisté řešení před ověřením architektury
Pokaždé, když aktualizujete kód pro ověření, použijte **Vyčistit řešení** příkaz **sestavení** nabídky v experimentálním řešení před otestováním příkazu ověřit. To je nezbytné, protože výsledky ověření jsou ukládány do mezipaměti. Pokud jste neaktualizovali diagram testovací vrstvy nebo jeho kód, nebude provedeno metody ověřování.
### <a name="launch-the-debugger-explicitly"></a>Spustit ladicí program explicitně
Ověřování je spuštěno v samostatném procesu. Zarážky ve vaší metodě ověřování tedy nebudou aktivovány. Je nutné připojit ladicí program k procesu explicitně po spuštění ověření.
Chcete-li připojit ladicí program k procesu ověřování, vložte volání `System.Diagnostics.Debugger.Launch()` na začátku své metody ověřování. Jakmile se zobrazí dialogové okno ladění, vyberte hlavní instanci [!INCLUDE[vsprvs](../includes/vsprvs-md.md)].
Alternativně můžete vložit volání do `System.Windows.Forms.MessageBox.Show()`. Když se objeví okno zpráv, přejděte na hlavní instanci [!INCLUDE[vsprvs](../includes/vsprvs-md.md)] a na **ladění** klikněte na nabídku **připojit k procesu**. Vyberte proces, který je pojmenován **Graphcmd.exe**.
Experimentální instanci vždy spusťte stisknutím kombinace kláves CTRL + F5 (**spustit bez ladění**).
### <a name="deploying-a-validation-extension"></a>Nasazení rozšíření ověřování
Chcete-li nainstalovat rozšíření ověřování v počítači, na kterém je nainstalován vhodnou verzi sady Visual Studio, otevřete soubor VSIX v cílovém počítači. K instalaci na počítač, na kterém [!INCLUDE[esprbuild](../includes/esprbuild-md.md)] je nainstalovaný, musíte ručně extrahovat obsah souboru VSIX do složky Extensions. Další informace najdete v tématu [nasazení rozšíření pro modelování vrstev](../modeling/deploy-a-layer-model-extension.md).
## <a name="example"></a> Příklad kódu
```csharp
using System;
using System.ComponentModel.Composition;
using System.Globalization;
using System.Linq;
using System.Text.RegularExpressions;
using Microsoft.VisualStudio.ArchitectureTools.Extensibility.CodeSchema;
using Microsoft.VisualStudio.ArchitectureTools.Extensibility.Layer;
using Microsoft.VisualStudio.GraphModel;
namespace Validator3
{
[Export(typeof(IValidateArchitectureExtension))]
public partial class Validator3Extension : IValidateArchitectureExtension
{
/// <summary>
/// Validate the architecture
/// </summary>
/// <param name="graph">The graph</param>
public void ValidateArchitecture(Graph graph)
{
if (graph == null) throw new ArgumentNullException("graph");
// Uncomment the line below to debug this extension during validation
// System.Windows.Forms.MessageBox.Show("Attach 2 to GraphCmd.exe with process id " + System.Diagnostics.Process.GetCurrentProcess().Id);
// Get all layers on the diagram
foreach (GraphNode layer in graph.Nodes.GetByCategory("Dsl.Layer"))
{
System.Threading.Thread.Sleep(100);
// Get the required regex property from the layer node
string regexPattern = "^[a-zA-Z]+$"; //layer[customPropertyCategory] as string;
if (!string.IsNullOrEmpty(regexPattern))
{
Regex regEx = new Regex(regexPattern);
// Get all referenced types in this layer including those from nested layers so each
// type is validated against all containing layer constraints.
foreach (GraphNode containedType in layer.FindDescendants().Where(node => node.HasCategory("CodeSchema_Type")))
{
// Check the type name against the required regex
CodeGraphNodeIdBuilder builder = new CodeGraphNodeIdBuilder(containedType.Id, graph);
string typeName = builder.Type.Name;
if (!regEx.IsMatch(typeName))
{
// Log an error
string message = string.Format(CultureInfo.CurrentCulture, Resources.InvalidTypeNameMessage, typeName);
this.LogValidationError(graph, typeName + "TypeNameError", message, GraphErrorLevel.Error, layer);
}
}
}
}
}
}
}
```
## <a name="see-also"></a>Viz také
[Rozšíření diagramů vrstev](../modeling/extend-layer-diagrams.md)
| 56.650177 | 450 | 0.722867 | ces_Latn | 0.999718 |
d5e9f850412ab4aea66f15996fc31040aab09ead | 3,924 | md | Markdown | Labs/L02_Entropy.md | nikcleju/IT20172018 | e23bcb9edff230db236c3d1d342699d95b5f7564 | [
"CC-BY-4.0"
] | 1 | 2019-06-23T05:23:21.000Z | 2019-06-23T05:23:21.000Z | Labs/L02_Entropy.md | nikcleju/IT20172018 | e23bcb9edff230db236c3d1d342699d95b5f7564 | [
"CC-BY-4.0"
] | null | null | null | Labs/L02_Entropy.md | nikcleju/IT20172018 | e23bcb9edff230db236c3d1d342699d95b5f7564 | [
"CC-BY-4.0"
] | 2 | 2019-06-23T05:23:13.000Z | 2021-04-02T05:13:27.000Z | ---
title: Computing entropy of data
subtitle: Information Theory Lab 2
documentclass: scrartcl
fontsize: 12pt
---
## Objective
Understand the concepts of entropy and discrete memoryless source.
Model a data file as a sequence of independent 1-byte random variables and compute its entropy.
# Theoretical notions
The entropy of a discrete memoryless source is defined as:
$$H(S) = \sum_i p(s_i) \cdot \log_2 (p(s_i))$$
See the lecture notes for more details.
# Practical issues
A file is a sequence of 1-byte values (i.e. between 0 and 255).
If we ignore all interdependencies in the data, we can consider the bytes
as **independently drawn from a discrete memoryless source** with 256 different possible messages.
* Note: this is a (simplifying) model, in reality the data values
are not independent, but depending strongly on the surrounding values.
The distribution of the source can be estimated by counting the number of apparitions of every
byte value in the file, and dividing to the total number of bytes. For example, if the byte value 55
appears 1000 times in a 9000-byte file, its probability is $1/9$.
# Exercises
1. Write a C program to compute the entropy of a file.
* The program shall receive the name of the file as a command-line argument:
`entropy.exe myfile.txt`
* The program should follow the following steps:
* Open the file for reading (in binary format)
* Count the number of apparitions of every byte value:
* hold an array of 256 counters, one for every possibly byte value
* repeatedly read one byte from the file
* increment the counter corresponding to the byte read
* also store and increment a counter for the total number of bytes
* Compute the probability of every byte value: divide each byte counter to the global counter
* Compute the entropy, based on the probabilities
* Show the result
1. Use the program to estimate the entropy of the following data files:
- a Romanian language text (`textRO.txt`);
- an English language text (`textRO.txt`);
- an executable file (*.exe)
- a JPG image file
3. Considering the computed entropy for `textRO.txt`, estimate how many bits would be sufficient to encode the file,
and compare with the actual file size. Archive the file in the *.zip* format and compare the resulting size
with your estimated size.
4. Modify the program to list the probabilities of the letters `a` to `z`.
Compare the probabilities for Romanian and English. Are they different? For what letters?
## Implementation hints
* The counters can be implemented as a vector of integers, with size 256,
such that `counter[i]` is the counter for the byte value `i`.
When the value `i` is read from the file, incrementing the corresponding counter is done easily with `counter[i]++`.
* You will need another vector for probabilities (real values).
* The following C functions may be used for file-based operations.
Look up their documentation on the Internet (e.g. *cplusplus.com*, or Google search).
* `fopen(...)`, to open a file for reading;
* `fread(...)`, to read byte data from the file;
* `fclose()`, to close the file when finished.
* There is no function in C for computing $\log_2(x)$. You can compute this using the logarithm conversion formula:
$$\log_2(x) = \frac{\log_b(x)}{\log_b(2)},$$
using one of the existing logarithms in C: `log()` (natural logarithm) or `log10()` (logartithm base 10).
# Final questions
1. Suppose we consider pairs of two consecutive bytes as the messages of the source.
What are the drawbacks of this implementation? How will the computed entropy be in this case?
2. Repeatedly reading 1 byte from a file on the disk is inefficient. Can we improve the program by
reading data in larger chunks? Think / describe what needs to be changed.
| 43.6 | 117 | 0.7263 | eng_Latn | 0.998916 |
d5ea7bf299e48c6ab77e0aeb3b3a49805078d960 | 137 | md | Markdown | pages/activities/twelve-bar-blues.md | music-practice-tools/music-practice-tools | 183a90e3ac0b3ca05277674db9ec10758aa56fae | [
"MIT"
] | 3 | 2020-06-28T22:10:39.000Z | 2021-08-20T03:35:08.000Z | pages/activities/twelve-bar-blues.md | music-practice-tools/music-practice-tools | 183a90e3ac0b3ca05277674db9ec10758aa56fae | [
"MIT"
] | 1 | 2020-06-28T14:36:00.000Z | 2020-06-29T16:39:27.000Z | pages/activities/twelve-bar-blues.md | music-practice-tools/music-practice-tools | 183a90e3ac0b3ca05277674db9ec10758aa56fae | [
"MIT"
] | null | null | null | ---
title: Twelve Bar Blues
date: 2020-09-29
order: 2
tags:
---
| I | IV | I | I |
| IV | IV | I | I |
| V | IV | I | V |
| 12.454545 | 23 | 0.416058 | yue_Hant | 0.433595 |
d5eae12d97175be0d461b62f5f39065cf1b9dbda | 10,121 | md | Markdown | docs/src/integrators/rk.md | JuliaGNI/GeometricIntegrators.jl | bf1ca810d75e43c1d89e4981beea35451858155a | [
"MIT"
] | 6 | 2020-12-29T10:41:35.000Z | 2022-03-21T11:48:39.000Z | docs/src/integrators/rk.md | JuliaGNI/GeometricIntegrators.jl | bf1ca810d75e43c1d89e4981beea35451858155a | [
"MIT"
] | 15 | 2020-11-16T16:45:50.000Z | 2022-03-09T17:51:11.000Z | docs/src/integrators/rk.md | michakraus/GeometricIntegrators.jl | fcca462f25a1f9d5ff0954d5d71ef7cd1389ab3e | [
"MIT"
] | 2 | 2021-05-05T12:54:38.000Z | 2021-12-17T18:19:13.000Z | ```@meta
CurrentModule = GeometricIntegrators.Tableaus
```
# Runge-Kutta Methods
Runge-Kutta methods exploit the **Fundamental Theorem of Calculus**, which states that the solution of an initial-value problem
```math
\begin{aligned}
\dot{x} (t) &= f(t, x(t)) , &
x(t_{n}) &= x_{n} ,
\end{aligned}
```
at time $t_{n+1}$ is given by
```math
x (t_{n+1}) = x (t_{n}) + \int \limits_{t_{n}}^{t_{n+1}} \dot{x} (t) \, dt .
```
Runge-Kutta methods are constructed by approximating the integral by some quadrature formula with $s$ nodes $c_{i}$ and corresponding weights $b_{i}$ to obtain $x_{n+1} \approx x (t_{n+1})$ by
```math
\begin{aligned}
x_{n+1} &= x_{n} + h \sum \limits_{i=1}^{s} b_{i} \dot{X}_{n,i} , &
\dot{X}_{n,i} &= f(t_{n} + c_{i} h, X_{n,i}) ,
\end{aligned}
```
where the internal stage values $X_{n,i} \approx x(t_{n} + c_{i} h)$ for $i = 1, ..., s$ are determined by another quadrature formula, approximating the integral
```math
x(t_{n} + c_{i} h) = x (t_{n}) + \int \limits_{t_{n}}^{t_{n} + c_i h} \dot{x} (t) \, dt ,
```
namely
```math
X_{n,i} = x_{n} + h \sum \limits_{j=1}^{s} a_{ij} \dot{X}_{n,j} ,
```
with the same vector field values $\dot{X}_{n,j}$ used for the computation of $x_{n+1}$.
**Definition:** Runge-Kutta methods are numerical one-step methods
```math
\begin{aligned}
X_{n,i} &= x_{n} + h \sum \limits_{j=1}^{s} a_{ij} \, f(t_{n} + c_{j} h, X_{n,j}) , \\
x_{n+1} &= x_{n} + h \sum \limits_{j=1}^{s} b_{j} \, f(t_{n} + c_{j} h, X_{n,j}) ,
\end{aligned}
```
defined by a set of nodes $c_i$, weights $b_i$ and coefficients $a_{ij}$ with $i,j = 1, ..., s$, summarized in the Butcher tableau
```math
\begin{array}{c|c}
c & a \\
\hline
& b^{T} \\
\end{array}
=
\begin{array}{c|cccc}
c_{1} & a_{11} & a_{12} & \dots & a_{1s} \\
c_{2} & a_{21} & a_{22} & \dots & a_{2s} \\
\vdots & \vdots & \vdots & \ddots & \vdots \\
c_{s} & a_{s1} & a_{s2} & \dots & a_{ss} \\
\hline
& b_{1} & b_{2} & \dots & b_{s} \\
\end{array}
```
Most properties of the methods, such as order or stability, can be analysed just by posing conditions on the Butcher tableau.
## Common Runge-Kutta Methods
GeometricIntegrators.jl provides various explicit and implicit (both diagonally and fully implicit) Runge-Kutta methods.
For many methods, tabulated coefficients are included, namely
| Function and Aliases | Stages | Order |
|:---------------------------------------------------------------|:-------|:------|
| **Explicit Methods** | | |
| [`TableauExplicitEuler`](@ref), [`TableauForwardEuler`](@ref) | 1 | 1 |
| [`TableauExplicitMidpoint`](@ref) | 2 | 2 |
| [`TableauHeun2`](@ref) | 2 | 2 |
| [`TableauHeun3`](@ref) | 3 | 3 |
| [`TableauKutta`](@ref), [`TableauKutta3`](@ref) | 3 | 3 |
| [`TableauRalston2`](@ref) | 2 | 2 |
| [`TableauRalston3`](@ref) | 3 | 3 |
| [`TableauRunge`](@ref), [`TableauRunge2`](@ref) | 2 | 2 |
| [`TableauRK416`](@ref), [`TableauRK4`](@ref) | 4 | 4 |
| [`TableauRK438`](@ref) | 4 | 4 |
| [`TableauSSPRK3`](@ref) | 3 | 3 |
| **Diagonally Implicit Methods** | | |
| [`TableauCrankNicolson`](@ref) | 2 | 2 |
| [`TableauCrouzeix`](@ref) | 2 | 3 |
| [`TableauKraaijevangerSpijker`](@ref) | 2 | 2 |
| [`TableauQinZhang`](@ref) | 2 | 2 |
| **Fully Implicit Methods** | | |
| [`TableauImplicitEuler`](@ref), [`TableauBackwardEuler`](@ref) | 1 | 1 |
| [`TableauImplicitMidpoint`](@ref) | 2 | 2 |
| [`TableauSRK3`](@ref) | 3 | 4 |
The coefficients of other methods are computed on-the-fly as described in the following.
## Simplifying Assumptions
The construction of many Runge-Kutte methods, in particular the Gauß, Lobatto and Radau methods, relies on the so-called simplifying assumptions:
```math
\begin{aligned}
B(\sigma): & \sum \limits_{i=1}^{s} b_{i} c_{i}^{k-1} = \frac{1}{k} , &
k = 1 , \, ... , \, \sigma , \\
%
C(\eta): & \sum \limits_{j=1}^{s} a_{ij} c_{j}^{k-1} = \frac{c_{i}^{k}}{k} , &
i = 1, \, ... , \, s , \; k = 1 , \, ... , \, \eta , \\
%
D(\zeta): & \sum \limits_{i=1}^{s} b_{i} c_{i}^{k-1} a_{ij} = \frac{b_{j}}{k} ( 1 - c_{j}^{k} ) , &
j = 1, \, ... , \, s , \; k = 1 , \, ... , \, \zeta .
\end{aligned}
```
These assumptions provide order conditions for a Runge-Kutta method given by $(a_{ij}, b_{i}, c_{i})$.
The condition $B(p)$ implies that the quadrature rule $(b_{i}, c_{i})$ is of order $p$.
Furthermore, the following theorem holds:
**Theorem (Butcher 1964)**: If the coefficients $(a_{ij}, b_{i}, c_{i})$ of a Runge-Kutta method satisfy $B(\sigma)$, $C(\eta)$, $D(\zeta)$ with $\sigma \le \eta + \zeta + 1$ and $\sigma \le 2 \eta + 2$, then the method is of order $\sigma$.
## Gauß, Lobatto and Radau Methods
Gauß methods are collocation methods using the nodes and weights of Gaußian quadrature formulas.
The nodes are the zeros of the shifted Legendre polynomials of degree $s$,
```math
\frac{d^{s}}{dx^{s}} \big( x^{s} (x-1)^{s} \big) .
```
In a similar fashion, the nodes of the Radau I and II and the Lobatto III methods are defined as the roots of the polynomials
```math
\begin{aligned}
& \frac{d^{s-1}}{dx^{s-1}} \big( x^s (x-1)^{s-1} \big) && \text{(Radau I)} , \\
& \frac{d^{s-1}}{dx^{s-1}} \big( x^{s-1} (x-1)^s \big) && \text{(Radau II)} , \\
& \frac{d^{s-2}}{dx^{s-2}} \big( x^{s-1} (x-1)^{s-1} \big) && \text{(Lobatto III)} .
\end{aligned}
```
The weights $b_{1}, ..., b_{s}$ are chosen such that the methods satisfy $B(\sigma)$, that is $B(s)$, for the Gauß methods, $B(s-1)$ for the Radau methods, and $B(s-2)$ for the Lobatto methods.
The coefficients $a_{ij}$ for $i,j = 1, ..., s$ are obtained by the simplifying assumption $C(s)$ for the Gauß, Radau IIA and Lobatto IIIA methods, and by the simplifying assumption $D(s)$ for the Radau IA and Lobatto IIIB methods.
The coefficients of the Lobatto IIIC methods are determined by setting $a_{i,1} = b_1$ for $i = 1, ..., s$ and solving the simplifying assumption $C(s-1)$, while the coefficients of the Lobatto IIIC̄ methods are determined by setting $a_{i,s} = 0$ and solving $C(s-1)$. Note that the Lobatto IIIC̄ methods are sometimes also called Lobatto III or Lobatto III*. For reasons of code symmetry we chose to stick with the less common name Lobatto IIIC̄.
The Lobatto IIID and IIIE methods are obtained by combining the tableaus of the Lobatto IIIC and IIIC̄ and the Lobatto IIIA and IIIB methods, respectively, i.e.,
```math
\begin{aligned}
a_{ij}^{D} &= \tfrac{1}{2} ( a_{ij}^{C} + a_{ij}^{C̄} ) &
& \text{and} &
a_{ij}^{E} &= \tfrac{1}{2} ( a_{ij}^{A} + a_{ij}^{B} ) .
\end{aligned}
```
While the Lobatto IIIA, IIIB, IIIC and IIIC̄ methods are not symplectic on their own (although the Lobatto IIIA-IIIB and IIIC-IIIC̄ pairs constitute symplectic partitioned Runge-Kutta methods), the Lobatto IIID and IIIE methods are each symplectic by themselves.
The Gauß methods are of order $2s$, the Radau methods or order $2s-1$ and the Lobatto methods are of order $2s-2$, with the exception of the Lobatto IIIF method. This method has been specifically constructed to be of order $2s$ as described in [[Fangzong:2016](@cite)].
The Lobatto IIIG method is constructed in a similar fashion as the Lobatto IIID and IIIE methods by averaging the coefficients of the Lobatto IIIF method with its symplectic complement, i.e.,
```math
a_{ij}^{G} = \tfrac{1}{2} ( a_{ij}^{F} + \bar{a}_{ij}^{F} ) ,
```
where the coffiecients $\bar{a}_{ij}^{F}$ are determined by
```math
\begin{aligned}
b_{i} \bar{a}^{F}_{ij} + \bar{b}_{j} a^{F}_{ji} &= b_{i} \bar{b}_{j} &
& \text{and} &
\bar{b}_{i} &= b_{i} .
\end{aligned}
```
The tableaus of all of the above methods can be computed for an arbitrary number of stages $s$ and thus to arbitrary order.
### Constructors
The following methods are provided for the construction of the tableaus for the previously described methods:
| Function | Method |
|:--------------------------------------------|:----------------------------|
| [`TableauGauss(s, T=Float64)`](@ref) | Gauß-Legendre with s stages |
| [`TableauLobattoIIIA(s, T=Float64)`](@ref) | Lobatto IIIA with s stages |
| [`TableauLobattoIIIB(s, T=Float64)`](@ref) | Lobatto IIIB with s stages |
| [`TableauLobattoIIIC(s, T=Float64)`](@ref) | Lobatto IIIC with s stages |
| [`TableauLobattoIIIC̄(s, T=Float64)`](@ref) | Lobatto IIIC̄ with s stages |
| [`TableauLobattoIIID(s, T=Float64)`](@ref) | Lobatto IIID with s stages |
| [`TableauLobattoIIIE(s, T=Float64)`](@ref) | Lobatto IIIE with s stages |
| [`TableauLobattoIIIF(s, T=Float64)`](@ref) | Lobatto IIIF with s stages |
| [`TableauLobattoIIIG(s, T=Float64)`](@ref) | Lobatto IIIG with s stages |
| [`TableauRadauIA(s, T=Float64)`](@ref) | Radau IA with s stages |
| [`TableauRadauIB(s, T=Float64)`](@ref) | Radau IB with s stages |
| [`TableauRadauIIA(s, T=Float64)`](@ref) | Radau IIA with s stages |
| [`TableauRadauIIB(s, T=Float64)`](@ref) | Radau IIB with s stages |
The first argument `s` refers to the number of stages ($s \ge 1$ for Gauß and $s \ge 2$ for all other methods).
The second argument specifies the number type of the coefficients. Internally, all coefficients are computed using `BigFloat` and then converted to the requested number type, defaulting to `Float64`.
## Implicit Equations
**TODO**
| 52.440415 | 448 | 0.570596 | eng_Latn | 0.912031 |
d5eb22580225fde0189ceeb09cf5900db4959f71 | 1,344 | md | Markdown | miniprogram/src/article/0-0.md | viewerw/harmonicaHomeCloud | 878c0935f70668fe8b474b0b912ce8e2fe034efc | [
"MIT"
] | null | null | null | miniprogram/src/article/0-0.md | viewerw/harmonicaHomeCloud | 878c0935f70668fe8b474b0b912ce8e2fe034efc | [
"MIT"
] | 2 | 2021-03-09T15:30:51.000Z | 2021-05-10T08:57:40.000Z | miniprogram/src/article/0-0.md | viewerw/harmonicaHomeCloud | 878c0935f70668fe8b474b0b912ce8e2fe034efc | [
"MIT"
] | null | null | null | 简谱起源于 18 世纪的法国，在中国得到了最广泛的传播和使用。\n\n 简谱是一种简易的记谱法，即利用一些数字记号或符号，将音的长短、高低、强弱、顺序记录下来。\n\n 一份用简谱记录的谱子，应该包括调号、拍号、音符和小节、小节线、终止线等最基本的记号或符号。下面我们以贝多芬的《欢乐颂》为例来认识简谱的基本构成。\n\n 欢乐颂\n\n ## 一、简谱的基本构成\n\n
#### 1.调号\n\n
调号是用以确定歌曲、乐曲音高的符号。调号写在简谱的左上方。它表示该曲应该用哪个“调”来演唱或演奏（关于调的内容，在本书第七章《调与调式》会有详细讲解）。
\n\n
不同的调用不同的调号标记。如《欢乐颂》的调号 1 = C，表示这是一首用 C 调演奏的曲子。同理，当一首简谱曲子为 D 调时，其调号就为 1 = D。一首简谱曲子为 E 调时，其调号就为 1 = E。以此类推。
\n\n
#### 2.拍号
\n\n
拍号就是节拍记号，用分数的形式来标记，通常写在简谱首页左上角调号之后。
\n\n
如：《欢乐颂》简谱拍号为 4/4。拍号的读法是先读分母，再读分子，分母表示以几分音符为一拍，分子表示每一小节有几拍（关于节拍、拍子的内容，在本书第四章《节拍与节奏》会有详细讲解）。
\n\n
拍号的位置还有另一种写法，在乐曲中间需要变换拍子的时候，则需要在所变换拍子的那一小节写出新的拍号，直到再次变换拍子。
\n\n
例：
\n\n
\n\n
#### 3.音符
\n\n
音符是记录音的高低、长短的符号，在简谱中用阿拉伯数字 1、 2、 3、 4、 5、 6、 7 来表示。音符之间通过一定的节奏、节拍组织起来，便构成了一段具有音乐形象的旋律。（关于音符的内容，在本书第三章《音符与休止符》会有详细讲解。）
\n\n
#### 4.小节、小节线
\n\n
音乐按照一定的规律组成的最小的节拍组织就是小节，这个有规律的节拍组织依次循环往复组成了一首乐曲。在两个小节之间的竖线叫小节线。（关于小节、小节线的内容，在本书第四章《节拍与节奏》会有详细讲解。）
\n\n
#### 5.常用记号
\n\n
为了更科学、规范地记谱，简谱中有很多常用的记号，如省略记号、反复记号等。在《欢乐颂》里的连线记号就是在简谱中经常出现的记号之一。（关于常用记号的内容，在本书第八章《常用记号》会有讲解。）
\n\n
当连线记号记在相同音高的音符上时，称为“延音线”，表示只需要唱、奏第一个音，时值为连线内所有音符的时值总和。当连线记号记在不同音高的音符上时，称为“圆滑线”，表示连线内的音符要唱、奏得连贯。
\n\n
| 30.545455 | 263 | 0.764881 | yue_Hant | 0.295214 |
d5eb7cecac582a67499bfe60644e2cf5c8fc85f8 | 796 | md | Markdown | content/user-manual/app-service-manage/service-rollback.md | lxm/rainbond-docs | ef88a8b9de6d868ab32deb960bbaba4d56bda2c2 | [
"CC-BY-4.0"
] | null | null | null | content/user-manual/app-service-manage/service-rollback.md | lxm/rainbond-docs | ef88a8b9de6d868ab32deb960bbaba4d56bda2c2 | [
"CC-BY-4.0"
] | null | null | null | content/user-manual/app-service-manage/service-rollback.md | lxm/rainbond-docs | ef88a8b9de6d868ab32deb960bbaba4d56bda2c2 | [
"CC-BY-4.0"
] | null | null | null | ---
title: 服务版本管理
description: Rainbond服务版本的管理和版本回滚文档
hidden: true
weight: 5018
---
### 服务版本管理
服务每次成功部署后，都会生成一个服务版本，每个版本对应一次代码提交（基于源码创建），或者一个镜像版本（Docker 镜像创建）
通过 `构建版本管理` 功能，可以将服务回滚到指定版本，Rainbond 默认保留服务构建成功的版本。
<img src="https://static.goodrain.com/images/docs/3.6/user-manual/manage/app-rollback01.png" width="100%" />
版本管理中可以查询当前运行的版本，构建的历史版本和版本构建成功率。每一个版本都可以追溯代码提交记录或源镜像记录。
### 版本回滚
### <img src="https://static.goodrain.com/images/docs/3.6/user-manual/manage/app-rollback02.png" width="100%" />
服务可以随时回滚到历史构建成功的版本，Rainbond回滚操作与升级类似，采用滚动的方式进行。
{{% notice info %}}
- 多节点服务回滚操作采用滚动升级方式，因此时不会影响服务，但会有较短的时间同时存在 2 种版本的情况。
- Rainbond 5.X版本中对于服务回滚只会回滚代码和镜像运行环境，对服务配置（端口、环境变量、内存设置等）不会回滚到历史状态。
- 若你需要将应用整体回滚到历史的状态，包括持久化数据，请使用[应用备份与恢复机制](/user-manual/app-manage/app-backup/)
{{% /notice %}} | 24.875 | 112 | 0.767588 | yue_Hant | 0.736702 |
d5ebedd553458676ae69cb0f509a7e7666f898bb | 3,825 | md | Markdown | docs/_code/profiling.md | tsmanner/cpp-conditional-stream | 48191b17e83db7a3113dcd0c5ba7965d26562235 | [
"MIT"
] | null | null | null | docs/_code/profiling.md | tsmanner/cpp-conditional-stream | 48191b17e83db7a3113dcd0c5ba7965d26562235 | [
"MIT"
] | 3 | 2021-05-19T16:40:32.000Z | 2021-05-22T00:27:44.000Z | docs/_code/profiling.md | tsmanner/cpp-conditional-stream | 48191b17e83db7a3113dcd0c5ba7965d26562235 | [
"MIT"
] | null | null | null | ---
title: Profiling Results
classes: wide
---
| System | CPU | Memory | Disk | `ofstream`<br>`prof.txt` | `ofstream`<br>`/dev/null` | `ostringstream` | "blackhole"<br>`streambuf` | `ofstream`<br>failbit | `ConditionalOStream`
|-------------|---------------|--------|------------------------------|--------------------------|---------------------------|-----------------|----------------------------|-----------------------|----------------------
| WSL2 Debian | i7-8565U | 32GB | Intel M.2 SSDPEKK- F512G8L | 10.7935s | 7.78622s | 7.37819s | 5.94589s | 2.66578s | 0.538241s
| WSL2 Debian | Ryzen 7 3800X | 32GB | Sabrent M.2 Rocket 4.0 500GB | 7.74714s | 6.69068s | 5.84889s | 4.17527s | 2.11662s | 0.550667s
| NixOS 20.09 | Ryzen 7 1700 | 32GB | PNY CS1311 240GB SSD | 9.88139s | 7.96852s | 7.35156s | 5.09152s | 2.67259s | 0.684588s
## Test Function
**tests/profiling/profile.h**
```cpp
#include <chrono>
#include <iostream>
// 100,000,000
constexpr unsigned iterations = 100000000;
template <typename StreamType>
void time_streaming(StreamType &stream) {
auto value = "hello world\n";
auto t0 = std::chrono::steady_clock::now();
for (unsigned i = 0; i < iterations; ++i) {
stream << i << ": " << value;
}
auto t1 = std::chrono::steady_clock::now();
std::chrono::duration<long double> dt = t1 - t0;
std::cout << "Streaming took " << dt.count() << "s\n";
}
```
## Stream to a file
**tests/profiling/ofstream.cpp**
```cpp
#include <iostream>
#include <fstream>
#include "conditional_ostream.h"
#include "profile.h"
int main() {
auto stream = std::ofstream("ofstream.cpp.txt", std::ios::trunc);
time_streaming(stream);
return 0;
}
```
## Stream to `/dev/null`
**tests/profiling/devnull.cpp**
```cpp
#include <iostream>
#include <fstream>
#include "conditional_ostream.h"
#include "profile.h"
int main() {
auto stream = std::ofstream("/dev/null", std::ios::out);
time_streaming(stream);
return 0;
}
```
## Stream to a `std::ostringstream`
**tests/profiling/ostringstream.cpp**
```cpp
#include <iostream>
#include <sstream>
#include "conditional_ostream.h"
#include "profile.h"
int main() {
std::ostringstream stream;
time_streaming(stream);
return 0;
}
```
## Stream to a "blackhole"
This includes an implementation of a `std::streambuf` that ignores all input, borrowed from [Deduplicator on the Code Review Stack Exchange](https://codereview.stackexchange.com/a/260936).
**tests/profiling/nullbuffer.cpp**
```cpp
#include <iostream>
#include <iterator>
#include <streambuf>
#include "conditional_ostream.h"
#include "profile.h"
class blackhole_buf final : public std::streambuf {
char_type target[64];
std::streamsize xsputn(const char_type*, std::streamsize n) { return n; }
int_type overflow(int_type = traits_type::eof()) {
setp(target, std::end(target));
return 0;
}
};
int main() {
blackhole_buf buf {};
std::ostream stream { &buf };
time_streaming(stream);
return 0;
}
```
## Stream with failbit set
**tests/profiling/failbit.cpp**
```cpp
#include <iostream>
#include <fstream>
#include "conditional_ostream.h"
#include "profile.h"
int main() {
auto stream = std::ofstream();
stream.setstate(std::ios::failbit);
time_streaming(stream);
return 0;
}
```
## Stream to a `ConditionalOStream`
**tests/profiling/conditional.cpp**
```cpp
#include <iostream>
#include "conditional_ostream.h"
#include "profile.h"
int main() {
ConditionalOStream stream {};
time_streaming(stream);
return 0;
}
```
| 25.331126 | 219 | 0.583007 | eng_Latn | 0.466153 |
d5ec6f17d857abf547cc40343f30596aaf0962ca | 2,466 | md | Markdown | articles/automation/change-tracking/manage-scope-configurations.md | doracpphp/azure-docs.ja-jp | 92d3ca6b9bf4bdae67568790c3c429c0533ca9e9 | [
"CC-BY-4.0",
"MIT"
] | 161 | 2017-08-28T07:45:11.000Z | 2022-03-01T06:53:52.000Z | articles/automation/change-tracking/manage-scope-configurations.md | doracpphp/azure-docs.ja-jp | 92d3ca6b9bf4bdae67568790c3c429c0533ca9e9 | [
"CC-BY-4.0",
"MIT"
] | 6,139 | 2017-06-27T14:43:19.000Z | 2022-01-14T05:54:35.000Z | articles/automation/change-tracking/manage-scope-configurations.md | doracpphp/azure-docs.ja-jp | 92d3ca6b9bf4bdae67568790c3c429c0533ca9e9 | [
"CC-BY-4.0",
"MIT"
] | 456 | 2017-06-27T13:57:03.000Z | 2022-03-30T08:41:01.000Z | ---
title: Azure Automation の Change Tracking とインベントリのデプロイのスコープを制限する
description: この記事では、スコープ構成を使用して、Change Tracking とインベントリのデプロイのスコープを制限する方法について説明します。
services: automation
ms.subservice: change-inventory-management
ms.date: 10/14/2020
ms.topic: conceptual
ms.openlocfilehash: 6eb9a20920f0a340491459f0875fc85b90dfa193
ms.sourcegitcommit: f28ebb95ae9aaaff3f87d8388a09b41e0b3445b5
ms.translationtype: HT
ms.contentlocale: ja-JP
ms.lasthandoff: 03/29/2021
ms.locfileid: "92209170"
---
# <a name="limit-change-tracking-and-inventory-deployment-scope"></a>Change Tracking とインベントリのデプロイのスコープを制限する
この記事では、[Change Tracking とインベントリ](overview.md)機能を使用して VM に変更をデプロイする際のスコープ構成の操作方法について説明します。 詳細については、「[Azure Monitor での監視ソリューションのターゲット設定 (プレビュー)](../../azure-monitor/insights/solution-targeting.md)」を参照してください。
## <a name="about-scope-configurations"></a>スコープ構成について
スコープ構成は、Change Tracking とインベントリのスコープを特定のコンピューターに限定するために使用される、1 つ以上の保存された検索条件 (クエリ) のグループです。 スコープ構成は、有効にするコンピューターを対象として設定するために、Log Analytics ワークスペース内で使用されます。 この機能から変更にコンピューターを追加すると、ワークスペース内の保存した検索条件にも、そのコンピューターが追加されます。
## <a name="set-the-scope-limit"></a>スコープの制限を設定する
Change Tracking とインベントリのデプロイのスコープを制限するには、次のようにします。
1. [Azure portal](https://portal.azure.com) にサインインします。
2. Azure Portal で **[すべてのサービス]** を選択します。 リソースの一覧で、「**Automation**」と入力します。 入力を始めると、入力内容に基づいて一覧から候補が絞り込まれます。 **[Automation アカウント]** を選択します。
3. Automation アカウントの一覧で、変更履歴とインベントリを有効にしたときに選択したアカウントを選択します。
4. お使いの Automation アカウントで、 **[関連リソース]** の下にある **[リンクされたワークスペース]** を選択します。
5. **[ワークスペースに移動]** をクリックします。
6. **[Workspace Data Sources]\(ワークスペース データ ソース\)** の下の **[Scope Configurations (Preview)]\(スコープ構成 (プレビュー)\)** を選択します。
7. `MicrosoftDefaultScopeConfig-ChangeTracking` スコープ構成の右側にある省略記号を選択し、 **[編集]** をクリックします。
8. 編集ペインで **[コンピューター グループの選択]** を選択します。 [コンピューター グループ] ペインに、スコープ構成を作成するために使用された、保存された検索条件が表示されます。 Change Tracking とインベントリで使用される保存済みの検索条件は次のとおりです。
|名前 |カテゴリ |エイリアス |
|---------|---------|---------|
|MicrosoftDefaultComputerGroup | ChangeTracking | ChangeTracking__MicrosoftDefaultComputerGroup |
9. 保存した検索条件を選択して、グループの設定に使用されるクエリを表示および編集します。 次の図は、クエリとその結果を示しています。
## <a name="next-steps"></a>次のステップ
* 変更履歴とインベントリの操作については、[変更履歴とインベントリの管理](manage-change-tracking.md)に関するページを参照してください。
* この機能に関する一般的な問題のトラブルシューティングについては、「[Change Tracking と Inventory に関する問題のトラブルシューティング](../troubleshoot/change-tracking.md)」を参照してください。
| 44.836364 | 217 | 0.784672 | yue_Hant | 0.756323 |
d5ecd06ee78b1e8baddc21ab52a78038cc3dfea9 | 20 | md | Markdown | contributions/hoggerel.md | 20172104246/ncov-report | ccb62054d580e2bbe95ef6d5593fbbe84d13d657 | [
"Apache-2.0"
] | 3 | 2020-12-03T06:55:47.000Z | 2020-12-20T12:36:54.000Z | contributions/hoggerel.md | 20172104246/ncov-report | ccb62054d580e2bbe95ef6d5593fbbe84d13d657 | [
"Apache-2.0"
] | null | null | null | contributions/hoggerel.md | 20172104246/ncov-report | ccb62054d580e2bbe95ef6d5593fbbe84d13d657 | [
"Apache-2.0"
] | null | null | null | This is my first pr
| 10 | 19 | 0.75 | eng_Latn | 1.00001 |
d5ecfdfc2de4e57af43bcb21218107da5b37f176 | 386 | md | Markdown | README.md | FrauBSD/ssd_report | f30ad0feceb257ca874dc8c0a0a508c1a1defb2a | [
"BSD-2-Clause"
] | 10 | 2018-06-18T03:41:44.000Z | 2022-02-24T17:51:42.000Z | README.md | FrauBSD/ssd_report | f30ad0feceb257ca874dc8c0a0a508c1a1defb2a | [
"BSD-2-Clause"
] | 3 | 2018-09-04T08:52:35.000Z | 2022-02-05T21:26:40.000Z | README.md | FrauBSD/ssd_report | f30ad0feceb257ca874dc8c0a0a508c1a1defb2a | [
"BSD-2-Clause"
] | null | null | null | [//]: # ($FrauBSD: ssd_report/README.md 2018-07-04 06:46:46 +0000 freebsdfrau $)
# Welcome to [FrauBSD.org/ssd\_report](https://fraubsd.org/ssd_report)!
Report SSD health by looking at SMART data
## Foreword
The following is required before using `git commit` in this project.
> `$ .git-hooks/install.sh`
This will ensure the FrauBSD keyword is expanded/updated for each commit.
| 25.733333 | 80 | 0.735751 | eng_Latn | 0.955191 |
d5ed294b45c8490aae585834b5677cf76aea011c | 2,400 | md | Markdown | Cryptography/We want Nudes instead of Nukes/README.md | Nhaatj/CTFlearn-Writeups | 5defbc3357fec0699552cec4e9e508896af04075 | [
"MIT"
] | 1 | 2021-03-23T07:24:53.000Z | 2021-03-23T07:24:53.000Z | Cryptography/We want Nudes instead of Nukes/README.md | Nhaatj/CTFlearn-Writeups | 5defbc3357fec0699552cec4e9e508896af04075 | [
"MIT"
] | null | null | null | Cryptography/We want Nudes instead of Nukes/README.md | Nhaatj/CTFlearn-Writeups | 5defbc3357fec0699552cec4e9e508896af04075 | [
"MIT"
] | null | null | null | ## We want Nudes instead of Nukes
The main idea of getting the flag is to alter the IV before the decryption happens, so it gives a different, altered result of our choice.
#### Step-1:
The description of the challenge:
```
Donald has gone completely crazy. To prevent world chaos, you kidnapped him. Right before the kidnapping he tried to send one encrypted message to his wife Melania. Luckily you intercepted the message. Donald admits that he used AES-CBC encryption - a block cipher operating with a block length of 16 bytes. (here represented by 32 characters).
The message was: {391e95a15847cfd95ecee8f7fe7efd66,8473dcb86bc12c6b6087619c00b6657e}
The format contains first the Initialization vector(IV) and then the cipher text(c) separated by a colon all wrapped in curly braces. {IV,c} After torturing him by stealing his hairpiece, he tells you the plain text of the message is:
FIRE_NUKES_MELA!
As a passionate hacker you of course try to take advantage of this message. To get the flag alter the message that Melania will read: SEND_NUDES_MELA!
Submit the flag in the format: flag{IV,c}
The characters are hexlified, and one byte is represented by two characters; e.g. the string "84" represents the character "F" of the message and so on.
```
#### Step-2:
We know the IV (Initialization Vector) and the original plaintext, so if we reverse the `XOR` operation, the state of the ciphertext can be known right before it being finally decrypted with the IV.
The main idea being
`(Output) XOR (Initial Vector) = Plaintext` (Where Output is AES' output right before the XOR)
#### Step-3:
I wrote this script `exploit.py` that does the XOR operation with the given hashes to us.
```py
IV = bytearray.fromhex("391e95a15847cfd95ecee8f7fe7efd66")
CT = bytearray.fromhex("8473dcb86bc12c6b6087619c00b6657e")
# Hashes from the description of challenge
ORIGINAL_MESSAGE = bytearray.fromhex(
"464952455f4e554b45535f4d454c4121") # FIRE_NUKES_MELA!
ALTERED_MESSAGE = bytearray.fromhex(
"53454e445f4e554445535f4d454c4121") # SEND_NUDES_MELA!
ALTERED_IV = bytearray()
# XOR
for i in range(16):
ALTERED_IV.append(ALTERED_MESSAGE[i] ^ ORIGINAL_MESSAGE[i] ^ IV[i])
print(f'Flag: flag{{{ALTERED_IV.hex()},{CT.hex()}}}')
```
When we run this as `python3 exploit.py`
#### Step-4:
Finally, the flag becomes:
`flag{2c1289a05847cfd65ecee8f7fe7efd66,8473dcb86bc12c6b6087619c00b6657e}` | 46.153846 | 345 | 0.77375 | eng_Latn | 0.989675 |
d5ee98e7e9786ade75b184c584fc567b33d203dd | 6,849 | md | Markdown | README.md | wakakajp/LefexWork | b76739681abadc0dacc5f33d42dd63a3dfd8d9d6 | [
"MIT"
] | 1 | 2018-08-20T06:45:00.000Z | 2018-08-20T06:45:00.000Z | README.md | wakakajp/LefexWork | b76739681abadc0dacc5f33d42dd63a3dfd8d9d6 | [
"MIT"
] | null | null | null | README.md | wakakajp/LefexWork | b76739681abadc0dacc5f33d42dd63a3dfd8d9d6 | [
"MIT"
] | null | null | null | [@Lefe_x](https://weibo.com/5953150140) 就是我，正在做 [#iOS知识小集#](https://github.com/southpeak/iOS-tech-set) ，喜欢分享，努力做一名极客。喜欢分享写作。一名 **iOSer**。**喜欢 Node，微信小程序和前端**。一旦有新的文章，我会第一时间同步到这里和微博。
### iOS
* [为什么我还在写 CocoaPods 的教程](https://github.com/lefex/LefexWork/blob/master/blog/iOS/%E4%B8%BA%E4%BB%80%E4%B9%88%E6%88%91%E8%BF%98%E5%9C%A8%E5%86%99-CocoaPods-%E7%9A%84%E6%95%99%E7%A8%8B.md)
* [以不一样的方式理解SDWebImage](https://github.com/lefex/LefexWork/blob/master/blog/iOS/%E4%BB%A5%E4%B8%8D%E4%B8%80%E6%A0%B7%E7%9A%84%E6%96%B9%E5%BC%8F%E7%90%86%E8%A7%A3SDWebImage.md)
* [导出微信iOS数据库](https://github.com/lefex/LefexWork/blob/master/blog/iOS/%E5%AF%BC%E5%87%BA%E5%BE%AE%E4%BF%A1iOS%E6%95%B0%E6%8D%AE%E5%BA%93.md)
* [读懂「 唱吧KTVHTTPCache 」设计思想](https://github.com/lefex/LefexWork/blob/master/blog/iOS/%E8%AF%BB%E6%87%82%E3%80%8C-%E5%94%B1%E5%90%A7KTVHTTPCache-%E3%80%8D%E8%AE%BE%E8%AE%A1%E6%80%9D%E6%83%B3.md)
* [给 iOS 开发者的 RxSwift（一）](https://github.com/lefex/LefexWork/blob/master/blog/iOS/%E7%BB%99-iOS-%E5%BC%80%E5%8F%91%E8%80%85%E7%9A%84-RxSwift%EF%BC%88%E4%B8%80%EF%BC%89.md)
* [【iOS-国际化】如何把国际化时需要3天的工作量缩减到10分钟](https://github.com/lefex/LefexWork/blob/master/blog/iOS/%E3%80%90iOS-%E5%9B%BD%E9%99%85%E5%8C%96%E3%80%91%E5%A6%82%E4%BD%95%E6%8A%8A%E5%9B%BD%E9%99%85%E5%8C%96%E6%97%B6%E9%9C%80%E8%A6%813%E5%A4%A9%E7%9A%84%E5%B7%A5%E4%BD%9C%E9%87%8F%E7%BC%A9%E5%87%8F%E5%88%B010%E5%88%86%E9%92%9F.md)
* [使用 Xcode 工具更快的发现 Bug](https://github.com/lefex/LefexWork/blob/master/blog/iOS/%E4%BD%BF%E7%94%A8-Xcode-%E5%B7%A5%E5%85%B7%E6%9B%B4%E5%BF%AB%E7%9A%84%E5%8F%91%E7%8E%B0-Bug.md)
* [iOS 11 这个特性你知道吗？](https://github.com/lefex/LefexWork/blob/master/blog/iOS/iOS-11-%E8%BF%99%E4%B8%AA%E7%89%B9%E6%80%A7%E4%BD%A0%E7%9F%A5%E9%81%93%E5%90%97%EF%BC%9F.md)
* [iOS 11 适配看这篇还不够？](https://github.com/lefex/LefexWork/blob/master/blog/iOS/iOS-11-%E9%80%82%E9%85%8D%E7%9C%8B%E8%BF%99%E7%AF%87%E8%BF%98%E4%B8%8D%E5%A4%9F%EF%BC%9F.md)
* [使用 Promise 优雅滴避免回调地狱](https://github.com/lefex/LefexWork/blob/master/blog/iOS/Promise.md)
* [事件响应](https://github.com/lefex/LefexWork/blob/master/blog/iOS-tips/%E4%BA%8B%E4%BB%B6%E5%93%8D%E5%BA%94.md)
* [+ (void)load 和 + (void)initialize](https://github.com/lefex/LefexWork/blob/master/blog/iOS-tips/%2B-(void)load-%E5%92%8C-%2B-(void)initialize.md)
* [密语项目的一点思考，可能会帮到你](https://github.com/lefex/LefexWork/blob/master/blog/iOS/%E5%AF%86%E8%AF%AD%E9%A1%B9%E7%9B%AE%E7%9A%84%E4%B8%80%E7%82%B9%E6%80%9D%E8%80%83%EF%BC%8C%E5%8F%AF%E8%83%BD%E4%BC%9A%E5%B8%AE%E5%88%B0%E4%BD%A0.md)
* [工作中常用的工具](https://github.com/lefex/LefexWork/blob/master/blog/common/%E5%B7%A5%E4%BD%9C%E4%B8%AD%E5%B8%B8%E7%94%A8%E7%9A%84%E5%B7%A5%E5%85%B7.md)
* [Block 是如何实现的？如何避免循环引用？](https://github.com/lefex/LefexWork/blob/master/blog/iOS/Block-%E6%98%AF%E5%A6%82%E4%BD%95%E5%AE%9E%E7%8E%B0%E7%9A%84%EF%BC%9F%E5%A6%82%E4%BD%95%E9%81%BF%E5%85%8D%E5%BE%AA%E7%8E%AF%E5%BC%95%E7%94%A8%EF%BC%9F.md)
* [Block-使用总结](https://github.com/lefex/LefexWork/blob/master/blog/iOS/Block-%E4%BD%BF%E7%94%A8%E6%80%BB%E7%BB%93.md)
* [Sqlite的使用](https://github.com/lefex/LefexWork/blob/master/blog/common/Sqlite%E7%9A%84%E4%BD%BF%E7%94%A8.md)
* [JSPatch 使用中遇到的问题汇总](https://github.com/lefex/LefexWork/blob/master/blog/iOS/JSPatch-%E4%BD%BF%E7%94%A8%E4%B8%AD%E9%81%87%E5%88%B0%E7%9A%84%E9%97%AE%E9%A2%98%E6%B1%87%E6%80%BB.md)
### 微信小程序
* [从零开始部署小程序服务器（腾讯云）](https://github.com/lefex/LefexWork/blob/master/blog/miniProgram/%E4%BB%8E%E9%9B%B6%E5%BC%80%E5%A7%8B%E9%83%A8%E7%BD%B2%E5%B0%8F%E7%A8%8B%E5%BA%8F%E6%9C%8D%E5%8A%A1%E5%99%A8%EF%BC%88%E8%85%BE%E8%AE%AF%E4%BA%91%EF%BC%89.md)
* [从iOS来看微信小程序](https://github.com/lefex/LefexWork/blob/master/blog/miniProgram/%E4%BB%8EiOS%E6%9D%A5%E7%9C%8B%E5%BE%AE%E4%BF%A1%E5%B0%8F%E7%A8%8B%E5%BA%8F.md)
* [微信小程序开发遇到的坑](http://www.jianshu.com/p/c75333656eae)
* [从微信小程序看待FlexBox布局](https://github.com/lefex/LefexWork/blob/master/blog/miniProgram/%E4%BB%8E%E5%BE%AE%E4%BF%A1%E5%B0%8F%E7%A8%8B%E5%BA%8F%E7%9C%8B%E5%BE%85FlexBox%E5%B8%83%E5%B1%80.md)
* [微信小程序开发遇到的坑](https://github.com/lefex/LefexWork/blob/master/blog/miniProgram/%E5%BE%AE%E4%BF%A1%E5%B0%8F%E7%A8%8B%E5%BA%8F%E5%BC%80%E5%8F%91%E9%81%87%E5%88%B0%E7%9A%84%E5%9D%91.md)
* [微信小程序开发(一)：准备](https://github.com/lefex/LefexWork/blob/master/blog/miniProgram/%E5%BE%AE%E4%BF%A1%E5%B0%8F%E7%A8%8B%E5%BA%8F%E5%BC%80%E5%8F%91(%E4%B8%80)%EF%BC%9A%E5%87%86%E5%A4%87.md)
### Python
* [更人性化的找出 iOS 中未使用的图](https://github.com/lefex/LefexWork/blob/master/blog/python/%E6%9B%B4%E4%BA%BA%E6%80%A7%E5%8C%96%E7%9A%84%E6%89%BE%E5%87%BA-iOS-%E4%B8%AD%E6%9C%AA%E4%BD%BF%E7%94%A8%E7%9A%84%E5%9B%BE.md)
* [如何 【1秒】找出国际化文件(en.lproj/Localizable.strings)语法错误](https://github.com/lefex/LefexWork/blob/master/blog/python/%E5%A6%82%E4%BD%95%20%E3%80%901%E7%A7%92%E3%80%91%E6%89%BE%E5%87%BA%E5%9B%BD%E9%99%85%E5%8C%96%E6%96%87%E4%BB%B6.md)
* [如何找出国际化文件(xxxx.strings)中未国际化的文件](https://github.com/lefex/LefexWork/blob/master/blog/python/%E5%A6%82%E4%BD%95%E6%89%BE%E5%87%BA%E5%9B%BD%E9%99%85%E5%8C%96%E6%96%87%E4%BB%B6(xxxx.strings)%E4%B8%AD%E6%9C%AA%E5%9B%BD%E9%99%85%E5%8C%96%E7%9A%84%E6%96%87%E4%BB%B6.md)
### Node
* [MongoDB数据库](https://github.com/lefex/LefexWork/blob/master/blog/node/MongoDB%E6%95%B0%E6%8D%AE%E5%BA%93.md)
* [MySQL](https://github.com/lefex/LefexWork/blob/master/blog/node/MySQL.md)
* [Node 开篇介绍](https://github.com/lefex/LefexWork/blob/master/blog/node/Node-%E5%BC%80%E7%AF%87%E4%BB%8B%E7%BB%8D.md)
### C++
* [iOS 开发者应该掌握些 C++ 知识](https://github.com/lefex/LefexWork/blob/master/blog/C%2B%2B/iOS%20%E5%BC%80%E5%8F%91%E8%80%85%E5%BA%94%E8%AF%A5%E6%8E%8C%E6%8F%A1%E4%BA%9B%20C%2B%2B%20%E7%9F%A5%E8%AF%86.md)
### 其它
* [Linux 命令与 Shell 脚本](https://github.com/lefex/LefexWork/blob/master/blog/shell/Linux%20%E4%B8%8E%20Shell%20%E8%84%9A%E6%9C%AC.md)
* [JS Tips](https://github.com/lefex/LefexWork/blob/master/blog/node/JS-Tips.md)
* [RN开发(一)：准备](https://github.com/lefex/LefexWork/blob/master/blog/reactNative/RN%E5%BC%80%E5%8F%91(%E4%B8%80)%EF%BC%9A%E5%87%86%E5%A4%87.md)
* [你已经会用 Git 了吗？](https://github.com/lefex/LefexWork/blob/master/blog/git/%E4%BD%A0%E5%B7%B2%E7%BB%8F%E4%BC%9A%E7%94%A8-Git-%E4%BA%86%E5%90%97%EF%BC%9F.md)
* [Git的使用](https://github.com/lefex/LefexWork/blob/master/blog/git/Git%E7%9A%84%E4%BD%BF%E7%94%A8.md)
* [iOS git 规范](https://github.com/lefex/LefexWork/blob/master/blog/git/iOS%20git%20%E8%A7%84%E8%8C%83.md)
* [【图片+例子】学习正则表达式](http://www.jianshu.com/p/75115e9b2101)
* [iTerm 提高你的开发效率](https://github.com/lefex/LefexWork/blob/master/blog/common/iTerm--%E6%8F%90%E9%AB%98%E4%BD%A0%E7%9A%84%E5%BC%80%E5%8F%91%E6%95%88%E7%8E%87.md)
### 开源项目
* [TCZLocalizableTool](https://github.com/lefex/TCZLocalizableTool)
* [PMFMDB的使用](https://github.com/lefex/LefexWork/blob/master/blog/iOS/PMFMDB%E7%9A%84%E4%BD%BF%E7%94%A8.md)
### 总结
* [其实可以走的更远](https://github.com/lefex/LefexWork/blob/master/blog/summary/%E5%85%B6%E5%AE%9E%E5%8F%AF%E4%BB%A5%E8%B5%B0%E7%9A%84%E6%9B%B4%E8%BF%9C.md)
| 96.464789 | 319 | 0.712075 | yue_Hant | 0.605416 |
6aceeb9cfdd05cddc4ed3f9e2b979e26cc273267 | 479 | md | Markdown | HTM/ProgrGuide/Functions/ICurrentView/MovePrevious.md | LianaKh/as4x-docs | 08a6b99daf956442c3cf534596767568982462b2 | [
"MIT"
] | null | null | null | HTM/ProgrGuide/Functions/ICurrentView/MovePrevious.md | LianaKh/as4x-docs | 08a6b99daf956442c3cf534596767568982462b2 | [
"MIT"
] | 14 | 2019-05-30T10:47:31.000Z | 2022-03-29T14:11:37.000Z | HTM/ProgrGuide/Functions/ICurrentView/MovePrevious.md | LianaKh/as4x-docs | 08a6b99daf956442c3cf534596767568982462b2 | [
"MIT"
] | 13 | 2019-05-30T07:27:22.000Z | 2022-03-29T13:59:56.000Z | ---
layout: page
title: "ICurrentView/MovePrevious"
---
# MovePrevious մեթոդ
[См. также](../ICurrentView.md) Օրինակ [Применяется к](../ICurrentView.md)
Նշորդը տեղափոխում է նախորդ տող։ Մեթոդը առաջին տողի վրա կանչելուց [BOF](BOF.md)-ը դառնում է `True`, իսկ [BOF](BOF.md)-ի `True` արժեքի դեպքում կանչելուց առաջանում է սխալ։
## Շարահյուսություն
``` vb
object.MovePrevious
```
Բաղադրիչներն են՝
| Պարամետր | Նկարագրություն |
|--|--|
| object | Ընթացիկ դիտելու ձևի հղում։ |
| 18.423077 | 168 | 0.701461 | hye_Armn | 0.945912 |
6acf8082f1b951f6a1c1c956c9afe51a5aa16385 | 61 | md | Markdown | README.md | wcrbrm/k8s-golang-template | 6f3cfd86ff18ccdf6de9b7f533551a1e144d75c5 | [
"MIT"
] | null | null | null | README.md | wcrbrm/k8s-golang-template | 6f3cfd86ff18ccdf6de9b7f533551a1e144d75c5 | [
"MIT"
] | null | null | null | README.md | wcrbrm/k8s-golang-template | 6f3cfd86ff18ccdf6de9b7f533551a1e144d75c5 | [
"MIT"
] | null | null | null | # k8s-golang-template
Golang application helm charts for K8s
| 20.333333 | 38 | 0.819672 | eng_Latn | 0.685797 |
6acfae3050ae7737ff89e0806fd2424f44f49e91 | 897 | md | Markdown | AlchemyInsights/activate-microsoft-forms.md | isabella232/OfficeDocs-AlchemyInsights-pr.pt-PT | 90231c80c97b1b9ed11265c724351335698b74e2 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-05-19T19:07:32.000Z | 2020-05-19T19:07:32.000Z | AlchemyInsights/activate-microsoft-forms.md | MicrosoftDocs/OfficeDocs-AlchemyInsights-pr.pt-PT | 0ab4044e197cacbe672dd3619523546c471d53c2 | [
"CC-BY-4.0",
"MIT"
] | 4 | 2020-06-02T23:16:58.000Z | 2022-02-09T06:59:55.000Z | AlchemyInsights/activate-microsoft-forms.md | isabella232/OfficeDocs-AlchemyInsights-pr.pt-PT | 90231c80c97b1b9ed11265c724351335698b74e2 | [
"CC-BY-4.0",
"MIT"
] | 4 | 2019-10-09T20:26:06.000Z | 2021-10-09T10:39:37.000Z | ---
title: Ativar o Microsoft Forms
ms.author: pebaum
author: pebaum
manager: scotv
ms.audience: Admin
ms.topic: article
ms.service: o365-administration
ROBOTS: NOINDEX, NOFOLLOW
localization_priority: Normal
ms.collection: Adm_O365
ms.custom:
- "2544"
- "9000672"
ms.openlocfilehash: 7b6e76994ae9fe0f95cb8ebcb1ea18bcb373b2bc4ed22c63ef17f7a896b6b5c6
ms.sourcegitcommit: b5f7da89a650d2915dc652449623c78be6247175
ms.translationtype: MT
ms.contentlocale: pt-PT
ms.lasthandoff: 08/05/2021
ms.locfileid: "53937940"
---
# <a name="activate-microsoft-forms-for-an-organization"></a>Ativar o Microsoft Forms para uma organização
Um administrador pode ativos ou desligá-los para a organização. Saiba como [verificar a ativação da licença e o estado do Azure CollabDBService](https://support.office.com/article/Turn-off-or-turn-on-Microsoft-Forms-8dcbf3ab-f2d6-459a-b8be-8d9892132a43) para o seu inquilino. | 37.375 | 275 | 0.816054 | por_Latn | 0.450402 |
6acfbf53c4240466e069a233ba3fac52cbf8d789 | 10,337 | md | Markdown | articles/data-lake-store/data-lake-store-archive-eventhub-capture.md | changeworld/azure-docs.it- | 34f70ff6964ec4f6f1a08527526e214fdefbe12a | [
"CC-BY-4.0",
"MIT"
] | 1 | 2017-06-06T22:50:05.000Z | 2017-06-06T22:50:05.000Z | articles/data-lake-store/data-lake-store-archive-eventhub-capture.md | changeworld/azure-docs.it- | 34f70ff6964ec4f6f1a08527526e214fdefbe12a | [
"CC-BY-4.0",
"MIT"
] | 41 | 2016-11-21T14:37:50.000Z | 2017-06-14T20:46:01.000Z | articles/data-lake-store/data-lake-store-archive-eventhub-capture.md | changeworld/azure-docs.it- | 34f70ff6964ec4f6f1a08527526e214fdefbe12a | [
"CC-BY-4.0",
"MIT"
] | 7 | 2016-11-16T18:13:16.000Z | 2017-06-26T10:37:55.000Z | ---
title: Acquisire i dati da Hub eventi a Azure Data Lake Storage Gen1
description: Informazioni su come usare Azure Data Lake Storage Gen1 per acquisire i dati ricevuti da Hub eventi di Azure. Per iniziare, verificare i prerequisiti.
author: twooley
ms.service: data-lake-store
ms.topic: how-to
ms.date: 05/29/2018
ms.author: twooley
ms.openlocfilehash: 8be242369ecae2c809a38428284c9ddcad440e3f
ms.sourcegitcommit: f28ebb95ae9aaaff3f87d8388a09b41e0b3445b5
ms.translationtype: MT
ms.contentlocale: it-IT
ms.lasthandoff: 03/29/2021
ms.locfileid: "91578241"
---
# <a name="use-azure-data-lake-storage-gen1-to-capture-data-from-event-hubs"></a>Usare Azure Data Lake Storage Gen1 per acquisire dati da Hub eventi
Informazioni su come usare Azure Data Lake Storage Gen1 per acquisire i dati ricevuti da Hub eventi di Azure.
## <a name="prerequisites"></a>Prerequisiti
* **Una sottoscrizione di Azure**. Vedere [Ottenere una versione di prova gratuita di Azure](https://azure.microsoft.com/pricing/free-trial/).
* **Un account Azure Data Lake Storage Gen1**. Per istruzioni su come crearne uno, vedere [Iniziare a usare Azure Data Lake Storage Gen1](data-lake-store-get-started-portal.md).
* **Uno spazio dei nomi di hub eventi**. Per istruzioni, vedere [Creare uno spazio dei nomi di Hub eventi](../event-hubs/event-hubs-create.md#create-an-event-hubs-namespace). Assicurarsi che l'account Data Lake Storage Gen1 e lo spazio dei nomi di Hub eventi si trovino nella stessa sottoscrizione di Azure.
## <a name="assign-permissions-to-event-hubs"></a>Assegnare autorizzazioni a Hub eventi
In questa sezione si crea una cartella nell'account in cui si vuole acquisire i dati da Hub eventi. È anche possibile assegnare autorizzazioni a Hub eventi, in modo da consentire la scrittura di dati in un account Data Lake Storage Gen1.
1. Aprire l'account Data Lake Storage Gen1 in cui si desidera acquisire i dati da Hub eventi e quindi fare clic su **Esplora dati**.
1. Fare clic su **Nuova cartella** e quindi immettere un nome per la cartella in cui si vuole acquisire i dati.
1. Assegnare le autorizzazioni alla radice di Data Lake Storage Gen1.
a. Fare clic su **Esplora dati**, selezionare la radice dell'account Data Lake Storage Gen1 e quindi fare clic su **Accesso**.
b. In **Accesso** fare clic su **Aggiungi**, fare clic su **Selezionare l'utente o il gruppo** e quindi cercare `Microsoft.EventHubs`.
Fare clic su **Seleziona**.
c. In **Assegna autorizzazioni** fare clic su **Selezionare le autorizzazioni**. Impostare **Autorizzazioni** su **Esegui**. Impostare **Aggiungi a** su **Questa cartella e tutti gli elementi figlio**. Impostare **Aggiungi come** su **Una voce di autorizzazione di accesso e una voce di autorizzazione predefinita**.
> [!IMPORTANT]
> Questo è un semplice metodo per garantire l'accesso alla cartella di destinazione quando si crea una nuova gerarchia di cartelle per l'acquisizione dei dati ricevuti da Hub eventi di Azure. Tuttavia, l'aggiunta delle autorizzazioni a tutti gli elementi figlio di una cartella di livello principale con molti file e cartelle figlio può richiedere molto tempo. Se la cartella radice contiene un numero elevato di file e cartelle, potrebbe essere più veloce aggiungere le autorizzazioni di **esecuzione** per `Microsoft.EventHubs` singolarmente a ogni cartella nel percorso della cartella di destinazione finale.
Fare clic su **OK**.
1. Assegnare le autorizzazioni per la cartella nell'account Data Lake Storage Gen1 in cui si desidera acquisire i dati.
a. Fare clic su **Esplora dati**, selezionare la cartella nell'account Data Lake Storage Gen1 e quindi fare clic su **Accesso**.
b. In **Accesso** fare clic su **Aggiungi**, fare clic su **Selezionare l'utente o il gruppo** e quindi cercare `Microsoft.EventHubs`.
Fare clic su **Seleziona**.
c. In **Assegna autorizzazioni** fare clic su **Selezionare le autorizzazioni**. Impostare **Autorizzazioni** su **Leggi, Scrivi** ed **Esegui**. Impostare **Aggiungi a** su **Questa cartella e tutti gli elementi figlio**. Impostare infine **Aggiungi come** su **Una voce di autorizzazione di accesso e una voce di autorizzazione predefinita**.
Fare clic su **OK**.
## <a name="configure-event-hubs-to-capture-data-to-data-lake-storage-gen1"></a>Configurare Hub eventi per acquisire i dati in Data Lake Storage Gen1
In questa sezione si crea un hub eventi in uno spazio dei nomi di Hub eventi. È anche possibile configurare l'Hub eventi per acquisire i dati in un account Azure Data Lake Storage Gen1. Questa sezione presuppone che sia già stato creato uno spazio dei nomi di Hub eventi.
1. Dal riquadro **Panoramica** dello spazio dei nomi di Hub eventi fare clic su **+ Hub eventi**.
1. Fornire i valori seguenti per configurare Hub eventi per acquisire i dati in Data Lake Storage Gen1.
a. Specificare un nome per l'hub eventi.
b. Per questa esercitazione, impostare **Numero di partizioni** e **Conservazione messaggi** sui valori predefiniti.
c. Impostare **Acquisisci** su **Sì**. Impostare **Intervallo di tempo** (frequenza di acquisizione) e **Intervallo dimensioni** (dimensioni dei dati da acquisire).
d. Per **Provider di acquisizione** selezionare **Azure Data Lake Store** e quindi selezionare l'account di Data Lake Storage Gen1 creato in precedenza. Per il **Percorso Data Lake**, immettere il nome della cartella creata nell'account Data Lake Storage Gen1. È sufficiente fornire il percorso relativo della cartella.
e. Lasciare il valore predefinito per **Formati dei nomi file di acquisizione di esempio**. Questa opzione controlla la struttura di cartelle che viene creata nella cartella di acquisizione.
f. Fare clic su **Crea**.
## <a name="test-the-setup"></a>Testare la configurazione
È ora possibile testare la soluzione inviando i dati all'hub di eventi di Azure. Seguire le istruzioni in [Inviare eventi a Hub eventi di Azure](../event-hubs/event-hubs-dotnet-framework-getstarted-send.md). Una volta avviato l'invio dei dati, verranno visualizzati i dati riflessi in Data Lake Storage Gen1 con la struttura di cartelle specificata. Ad esempio, viene visualizzata in Data Lake Storage Gen 1 una struttura di cartelle,come illustrato nello screenshot seguente.
> [!NOTE]
> Anche se non ci sono messaggi in arrivo in Hub eventi, Hub eventi scrive file vuoti con solo le intestazioni nell'account Data Lake Storage Gen1. I file vengono scritti con lo stesso intervallo di tempo specificato durante la creazione di Hub di eventi.
>
>
## <a name="analyze-data-in-data-lake-storage-gen1"></a>Analizzare i dati in Data Lake Storage Gen1
Una volta che i dati si trovano in Data Lake Storage Gen1, è possibile eseguire processi di analisi per elaborarli ed esaminarli. Vedere l'[esempio USQL Avro](https://github.com/Azure/usql/tree/master/Examples/AvroExamples) relativo a come eseguire questa operazione usando Azure Data Lake Analytics.
## <a name="see-also"></a>Vedi anche
* [Proteggere i dati in Data Lake Storage Gen1](data-lake-store-secure-data.md)
* [Copiare i dati dai BLOB di Archiviazione di Azure a Data Lake Storage Gen1](data-lake-store-copy-data-azure-storage-blob.md)
| 84.04065 | 618 | 0.774983 | ita_Latn | 0.996185 |
6acfd637218829d00debb957571ff3721fd6d7ff | 35,849 | md | Markdown | frameworks/cassandra/README.md | krisis/dcos-commons | 715d27f3e43a5e25b8ecb4beed97333b136fdd9a | [
"Apache-2.0"
] | 1 | 2021-01-06T21:14:00.000Z | 2021-01-06T21:14:00.000Z | frameworks/cassandra/README.md | krisis/dcos-commons | 715d27f3e43a5e25b8ecb4beed97333b136fdd9a | [
"Apache-2.0"
] | null | null | null | frameworks/cassandra/README.md | krisis/dcos-commons | 715d27f3e43a5e25b8ecb4beed97333b136fdd9a | [
"Apache-2.0"
] | null | null | null | # DC/OS Apache Cassandra Service Documentation
## Table of Contents
- [Overview](#overview)
- Features
- [Quick Start](#quick-start)
- [Installing and Customizing](#installing-and-customizing)
- Prerequisites
- Installation from the DC/OS CLI
- Installation from the DC/OS Web Interface
- Service Settings
- Service Name
- Data Center
- Rack
- Remote Seeds
- Backup/Restore Strategy
- Cassandra Settings
- Node Settings
- Node Count
- CPU
- Memory
- JMX Port
- Storage Port
- SSL Storage Port
- Native Transport Port
- RPC Port
- Disk Type
- Placement Constraints
- [Uninstalling](#uninstalling)
- [Connecting Clients](#connecting-clients)
- Discovering Endpoints
- Connecting Clients to Endpoints
- [Managing](#managing)
- Updating Configuration
- Adding a Node
- Resizing a Node
- Updating Placement Constraints
- Restarting a Node
- Replacing a Node
- Configuring Multi-data-center Deployments
- [Disaster Recovery](#disaster-recovery)
- Backup
- Restore
- [Troubleshooting](#troubleshooting)
- Accessing Logs
- [Limitations](#limitations)
- Accessibility of nodes in multi-data-center deployments
- [Support](#support)
- Supported Versions
<a name="overview"></a>
# Overview
DC/OS Apache Cassandra is an automated service that makes it easy to deploy and manage Apache Cassandra on [DC/OS](https://mesosphere.com/product/). Apache Cassandra is a distributed NoSQL database offering high availability, fault tolerance and scalability across data centers.
For more information on Apache Cassandra, see the Apache Cassandra [documentation](http://cassandra.apache.org/doc/latest/).
<a name="features"></a>
## Features
* Easy installation
* Simple horizontal scaling of Cassandra nodes
* Straightforward backup and restore of data out of the box
* Multi-datacenter replication support
* Rack-aware scheduling with placement constraints
<a name="quick-start"></a>
# Quick Start
1. Install DC/OS on your cluster. See [the documentation](https://docs.mesosphere.com/latest/administration/installing/) for instructions.
1. If you are using open source DC/OS, install DC/OS Apache Cassandra with the following command from the DC/OS CLI. If you are using Enterprise DC/OS, you may need to follow additional instructions. See the Install and Customize section for more information.
```
dcos package install beta-cassandra
```
You can also install DC/OS Apache Cassandra from [the DC/OS web interface](https://docs.mesosphere.com/latest/usage/webinterface/).
1. The service will now deploy with a default configuration. You can monitor its deployment via the Services UI in the DC/OS Dashboard.
1. Connect a client to the DC/OS Apache Cassandra service.
```
dcos beta-cassandra endpoints
["node"]
dcos beta-cassandra endpoints node
{
"address": [
"10.0.1.125:9042",
"10.0.2.152:9042",
"10.0.1.22:9042"
],
"dns": [
"node-1-server.cassandra.mesos:9042",
"node-0-server.cassandra.mesos:9042",
"node-2-server.cassandra.mesos:9042"
],
"vip": "node.cassandra.l4lb.thisdcos.directory:9042"
}
```
1. Write some data to your cluster:
```
dcos node ssh --master-proxy --leader
core@ip-10-0-6-153 ~ docker run -it cassandra:3.0.13 cqlsh node-0-server.cassandra.mesos
> CREATE KEYSPACE space1 WITH REPLICATION = { 'class' : 'SimpleStrategy', 'replication_factor' : 3 };
> USE space1;
> CREATE TABLE testtable1 (key varchar, value varchar, PRIMARY KEY(key));
> INSERT INTO space1.testtable1(key, value) VALUES('testkey1', 'testvalue1');
> SELECT * FROM testtable1;
```
<a name="installing-and-customizing"></a>
# Installing and Customizing
The default DC/OS Apache Cassandra installation provides reasonable defaults for trying out the service, but may not be sufficient for production use. You may require different configurations depending on the context of the deployment.
## Prerequisities
- If you are using Enterprise DC/OS, you may [need to provision a service account](https://docs.mesosphere.com/1.9/security/service-auth/custom-service-auth/) before installing DC/OS Apache Cassandra. Only someone with `superuser` permission can create the service account.
- `strict` [security mode](https://docs.mesosphere.com/1.9/administration/installing/custom/configuration-parameters/#security) requires a service account.
- In `permissive` security mode a service account is optional.
- `disabled` security mode does not require a service account.
- Your cluster must have at least 3 private nodes.
## Installation from the DC/OS CLI
To start a basic test cluster, run the following command on the DC/OS CLI. Enterprise DC/OS users must follow additional instructions. [More information about installing DC/OS Apache Cassandra on Enterprise DC/OS](https://docs.mesosphere.com/1.9/security/service-auth/custom-service-auth/).
```shell
dcos package install beta-cassandra
```
You can specify a custom configuration in an `options.json` file and pass it to `dcos package install` using the `--options` parameter.
```
$ dcos package install beta-cassandra --options=<options>.json
```
For more information about building the `options.json` file, see the [DC/OS documentation](https://docs.mesosphere.com/latest/usage/managing-services/config-universe-service/) for service configuration access.
## Installation from the DC/OS Web Interface
You can [install DC/OS Apache Cassandra from the DC/OS web interface](https://docs.mesosphere.com/1.9/usage/managing-services/install/). If you install DC/OS Apache Cassandra from the web interface, you must install the DC/OS Apache Cassandra CLI subcommands separately. From the DC/OS CLI, enter:
```bash
dcos package install beta-cassandra --cli
```
Choose `ADVANCED INSTALLATION` to perform a custom installation.
<a name="service-settings"></a>
## Service Settings
<a name="service-name"></a>
### Service Name
You must configure each instance of DC/OS Apache Cassandra in a given DC/OS cluster with a different service name. You can configure the service name in the **service** section of the advanced installation section of the DC/OS web interface. The default service name (used in many examples here) is `cassandra`.
* **In DC/OS CLI options.json**: `name`: string (default: `cassandra`)
* **DC/OS web interface**: The service name cannot be changed after the cluster has started.
<a name="data-center"></a>
### Data Center
You can configure the name of the logical data center that this Cassandra cluster runs in. This sets the `dc` property in the `cassandra-rackdc.properties` file.
* **In DC/OS CLI options.json**: `data_center`: string (default: `dc1`)
* **DC/OS web interface**: `CASSANDRA_LOCATION_DATA_CENTER`: `string`
<a name="rack"></a>
### Rack
You can configure the name of the rack that this Cassandra cluster runs in. This sets the `rack` property in the `cassandra-rackdc.properties` file.
* **In DC/OS CLI options.json**: `rack`: string (default: `rac1`)
* **DC/OS web interface**: `CASSANDRA_LOCATION_RACK`: `string`
<a name="remote-seeds"></a>
### Remote Seeds
You can configure the remote seeds from another Cassandra cluster that this cluster should communicate with to establish cross-data-center replication. This should be a comma-separated list of node hostnames, such as `node-0-server.cassandra.mesos,node-1-server.cassandra.mesos`. For more information on multi-data-center configuration, see [Configuring Multi-data-center Deployments](#configuring-multi-data-center-deployments).
* **In DC/OS CLI options.json**: `remote_seeds`: string (default: `""`)
* **DC/OS web interface**: `TASKCFG_ALL_REMOTE_SEEDS`: `string`
<a name="backup-restore-strategy"></a>
### Backup/Restore Strategy
You can configure whether the creation, transfer, and restoration of backups occurs in serial or in parallel across nodes. This option must be set to either `serial` or `parallel`. Running backups and restores in parallel has the potential to saturate your network. For this reason, we recommend that you use the default configuration for backup strategy.
* **In DC/OS CLI options.json**: `backup_restore_strategy`: string (default: `"serial"`)
* **DC/OS web interface**: `BACKUP_RESTORE_STRATEGY`: `string`
<a name="cassandra-settings"></a>
## Cassandra Settings
You can configure most of the settings exposed in Apache Cassandra's `cassandra.yaml` configuration file in DC/OS Apache Cassandra. For information about these settings, see the Apache Cassandra [documentation](http://cassandra.apache.org/doc/latest/configuration/cassandra_config_file.html). Settings that you can configure include:
* `cluster_name`
* `num_tokens`
* `hinted_handoff_enabled`
* `max_hint_window_in_ms`
* `hinted_handoff_throttle_in_kb`
* `max_hints_delivery_threads`
* `hints_flush_period_in_ms`
* `max_hints_file_size_in_mb`
* `batchlog_replay_throttle_in_kb`
* `authenticator`
* `authorizer`
* `partitioner`
* `key_cache_save_period`
* `row_cache_size_in_mb`
* `row_cache_save_period`
* `commitlog_sync_period_in_ms`
* `commitlog_segment_size_in_mb`
* `commitlog_total_space_in_mb`
* `concurrent_reads`
* `concurrent_writes`
* `concurrent_counter_writes`
* `concurrent_materialized_view_writes`
* `memtable_allocation_type`
* `index_summary_resize_interval_in_minutes`
* `storage_port`
* `ssl_storage_port`
* `start_native_transport`
* `native_transport_port`
* `start_rpc`
* `rpc_port`
* `rpc_keepalive`
* `thrift_framed_transport_size_in_mb`
* `tombstone_warn_threshold`
* `tombstone_failure_threshold`
* `column_index_size_in_kb`
* `batch_size_warn_threshold_in_kb`
* `batch_size_fail_threshold_in_kb`
* `compaction_throughput_mb_per_sec`
* `sstable_preemptive_open_interval_in_mb`
* `read_request_timeout_in_ms`
* `range_request_timeout_in_ms`
* `write_request_timeout_in_ms`
* `counter_write_request_timeout_in_ms`
* `internode_compression`
* `cas_contention_timeout_in_ms`
* `truncate_request_timeout_in_ms`
* `request_timeout_in_ms`
* `dynamic_snitch_update_interval_in_ms`
* `dynamic_snitch_reset_interval_in_ms`
* `dynamic_snitch_badness_threshold`
* `roles_update_interval_in_ms`
* `permissions_update_interval_in_ms`
* `key_cache_keys_to_save`
* `row_cache_keys_to_save`
* `counter_cache_keys_to_save`
* `file_cache_size_in_mb`
* `memtable_heap_space_in_mb`
* `memtable_offheap_space_in_mb`
* `memtable_cleanup_threshold`
* `memtable_flush_writers`
* `listen_on_broadcast_address`
* `internode_authenticator`
* `native_transport_max_threads`
* `native_transport_max_frame_size_in_mb`
* `native_transport_max_concurrent_connections`
* `native_transport_max_concurrent_connections_per_ip`
* `rpc_min_threads`
* `rpc_max_threads`
* `rpc_send_buff_size_in_bytes`
* `rpc_recv_buff_size_in_bytes`
* `concurrent_compactors`
* `stream_throughput_outbound_megabits_per_sec`
* `inter_dc_stream_throughput_outbound_megabits_per_sec`
* `streaming_socket_timeout_in_ms`
* `phi_convict_threshold`
* `buffer_pool_use_heap_if_exhausted`
* `disk_optimization_strategy`
* `max_value_size_in_mb`
* `otc_coalescing_strategy`
<a name="node-settings"></a>
## Node Settings
Adjust the following settings to customize the amount of resources allocated to each node. DC/OS Apache Cassandra's [system requirements](http://cassandra.apache.org/doc/latest/operating/hardware.html) must be taken into consideration when adjusting these values. Reducing these values below those requirements may result in adverse performance and/or failures while using the service.
Each of the following settings can be customized under the **node** configuration section.
<a name="node-count"></a>
### Node Count
Customize the `Node Count` setting (default 3) under the **node** configuration section. Consult the Apache Cassandra documentation for minimum node count requirements.
* **In DC/OS CLI options.json**: `count`: integer (default: `3`)
* **DC/OS web interface**: `NODES`: `integer`
<a name="cpu"></a>
### CPU
You can customize the amount of CPU allocated to each node. A value of `1.0` equates to one full CPU core on a machine. Change this value by editing the **cpus** value under the **node** configuration section. Turning this too low will result in throttled tasks.
* **In DC/OS CLI options.json**: `cpus`: number (default: `0.5`)
* **DC/OS web interface**: `CASSANDRA_CPUS`: `number`
<a name="memory"></a>
### Memory
You can customize the amount of RAM allocated to each node. Change this value by editing the **mem** value (in MB) under the **node** configuration section. Turning this too low will result in out of memory errors. The `heap.size` setting must also be less than this value to prevent out of memory errors resulting from the Java Virtual Machine attempting to allocate more memory than is available to the Cassandra process.
* **In DC/OS CLI options.json**: `mem`: integer (default: `10240`)
* **DC/OS web interface**: `CASSANDRA_MEMORY_MB`: `integer`
<a name="jmx-port"></a>
### JMX Port
You can customize the port that Apache Cassandra listens on for JMX requests, such as those issued by `nodetool`.
* **In DC/OS CLI options.json**: `jmx_port`: integer (default: `7199`)
* **DC/OS web interface**: `TASKCFG_ALL_JMX_PORT`: `integer`
<a name="storage-port"></a>
### Storage Port
You can customize the port that Apache Cassandra listens on for inter-node communication.
* **In DC/OS CLI options.json**: `storage_port`: integer (default: `7000`)
* **DC/OS web interface**: `TASKCFG_ALL_CASSANDRA_STORAGE_PORT`: `integer`
<a name="ssl-storage-port"></a>
### SSL Storage Port
You can customize the port that Apache Cassandra listens on for inter-node communication over SSL.
* **In DC/OS CLI options.json**: `ssl_storage_port`: integer (default: `7001`)
* **DC/OS web interface**: `TASKCFG_ALL_CASSANDRA_SSL_STORAGE_PORT`: `integer`
<a name="native-transport-port"></a>
### Native Transport Port
You can customize the port that Apache Cassandra listens on for CQL queries.
* **In DC/OS CLI options.json**: `native_transport_port`: integer (default: `9042`)
* **DC/OS web interface**: `TASKCFG_ALL_CASSANDRA_NATIVE_TRANSPORT_PORT`: `integer`
<a name="rpc-port"></a>
### RPC Port
You can customize the port that Apache Cassandra listens on for Thrift RPC requests.
* **In DC/OS CLI options.json**: `rpc_port`: integer (default: `9160`)
* **DC/OS web interface**: `TASKCFG_ALL_CASSANDRA_RPC_PORT`: `integer`
<a name="disk-type"></a>
### Disk Type
The service supports two volume types:
- `ROOT` volumes are effectively an isolated directory on the root volume, sharing IO/spindles with the rest of the host system.
- `MOUNT` volumes are a dedicated device or partition on a separate volume, with dedicated IO/spindles.
Using `MOUNT` volumes requires [additional configuration on each DC/OS agent system](https://docs.mesosphere.com/1.9/storage/mount-disk-resources/), so the service currently uses `ROOT` volumes by default. To ensure reliable and consistent performance in a production environment, you should configure `MOUNT` volumes on the machines that will run the service in your cluster and then configure the following as `MOUNT` volumes:
To configure the disk type:
* **In DC/OS CLI options.json**: `disk_type`: string (default: `ROOT`)
* **DC/OS web interface**: `CASSANDRA_DISK_TYPE`: `string`
<a name="placement-constraints"></a>
### Placement Constraints
Placement constraints allow you to customize where Apache Cassandra nodes are deployed in the DC/OS cluster. Placement constraints support all [Marathon operators](http://mesosphere.github.io/marathon/docs/constraints.html) with this syntax: `field:OPERATOR[:parameter]`. For example, if the reference lists `[["hostname", "UNIQUE"]]`, use `hostname:UNIQUE`.
* **In DC/OS CLI options.json**: `placement_constraint`: string (default: `""`)
* **DC/OS web interface**: `PLACEMENT_CONSTRAINT`: `string`
<a name="uninstalling"></a>
# Uninstalling
Follow these steps to uninstall the service.
1. Uninstall the service. From the DC/OS CLI, enter `dcos package uninstall`.
1. Clean up remaining reserved resources with the framework cleaner script, `janitor.py`. [More information about the framework cleaner script](https://docs.mesosphere.com/1.9/deploying-services/uninstall/#framework-cleaner).
To uninstall an instance named `cassandra` (the default), run:
```
MY_SERVICE_NAME=cassandra
dcos package uninstall --app-id=$MY_SERVICE_NAME beta-cassandra
dcos node ssh --master-proxy --leader "docker run mesosphere/janitor /janitor.py \
-r $MY_SERVICE_NAME-role \
-p $MY_SERVICE_NAME-principal \
-z dcos-service-$MY_SERVICE_NAME"
```
<a name="connecting-clients"></a>
# Connecting Clients
Clients communicating with Apache Cassandra use the Cassandra Query Language (CQL) to issue queries and write data to the cluster. CQL client libraries exist in many languages, and Apache Cassandra ships with a utility called `cqlsh` that enables you to issue queries against an Apache Cassandra cluster from the command line.
<a name="discovering-endpoints"></a>
## Discovering Endpoints
Once the service is running, you may view information about its endpoints via either of the following methods:
- CLI:
- List endpoint types: `dcos beta-cassandra endpoints`
- View endpoints for an endpoint type: `dcos beta-cassandra endpoints <endpoint>`
- Web:
- List endpoint types: `<dcos-url>/service/cassandra/v1/endpoints`
- View endpoints for an endpoint type: `<dcos-url>/service/cassandra/v1/endpoints/<endpoint>`
The DC/OS Apache Cassandra Service currently exposes only the `node` endpoint type, which shows the locations for all Cassandra nodes in the cluster. To see node addresses, run `dcos beta-cassandra endpoints node`. A typical response will look like the following:
```json
{
"address": [
"10.0.0.49:9042",
"10.0.2.253:9042",
"10.0.1.27:9042"
],
"dns": [
"node-2-server.cassandra.mesos:9042",
"node-0-server.cassandra.mesos:9042",
"node-1-server.cassandra.mesos:9042"
],
"vip": "node.cassandra.l4lb.thisdcos.directory:9042"
}
```
In general, the `.mesos` endpoints will only work from within the same DC/OS cluster. From outside the cluster you can either use the direct IPs, or set up a proxy service that acts as a frontend to your DC/OS Apache Cassandra instance. For development and testing purposes, you can use [DC/OS Tunnel](https://docs.mesosphere.com/latest/administration/access-node/tunnel/) to access services from outside the cluster, but this option is not suitable for production use.
<a name="connecting-clients-to-endpoints"></a>
## Connecting Clients to Endpoints
To connect to a DC/OS Apache Cassandra cluster using `cqlsh`, first SSH into a host in your DC/OS cluster:
```
dcos node ssh --leader --master-proxy
```
Then, use the `cassandra` Docker image to run `cqlsh`, passing as an argument the address of one of the Apache Cassandra nodes in the cluster:
```
docker run cassandra:3.0.13 cqlsh node-0-server.cassandra.mesos
```
This will open an interactive shell from which you can issue queries and write to the cluster. To ensure that the `cqlsh` client and your cluster are using the same CQL version, be sure to use the version of the `cassandra` Docker image that corresponds to the version of Apache Cassandra being run in your cluster. The version installed by the DC/OS Apache Cassandra Service is 3.0.13.
<a name="managing"></a>
# Managing
<a name="updating-configuration"></a>
## Updating Configuration
Edit the runtime environment of the scheduler to make configuration changes. After making a change, the scheduler will be restarted, and it will automatically deploy any detected changes to the service, one node at a time. For example, a given change will first be applied to the `node-0` pod, then `node-1`, and so on.
Nodes are configured with a "Readiness check" to ensure that the underlying service appears to be in a healthy state before continuing with applying a given change to the next node in the sequence. However, this basic check is not foolproof and reasonable care should be taken to ensure that a given configuration change will not negatively affect the behavior of the service.
Some changes, such as decreasing the number of nodes or changing volume requirements, are not supported after initial deployment. See [Limitations](#limitations).
To see a full listing of available options, run `dcos package describe --config beta-cassandra` in the CLI, or browse the DC/OS Apache Cassandra Service install dialog in the DC/OS Dashboard.
<a name="adding-a-node"></a>
### Adding a Node
The service deploys 3 nodes by default. This may be customized at initial deployment or after the cluster is already running via the `NODES` environment variable. Shrinking the cluster is not supported. If you decrease this value, the scheduler will complain about the configuration change until it's reverted back to its original value or a larger one.
<a name="resizing-a-node"></a>
### Resizing a Node
The CPU and Memory requirements of each node may be increased or decreased as follows:
- CPU (1.0 = 1 core): `CASSANDRA_CPUS`
- Memory (in MB): `CASSANDRA_MEMORY_MB`. To prevent out of memory errors, you must ensure that the `TASKCFG_ALL_CASSANDRA_HEAP_SIZE` environment variable is less than `$CASSANDRA_MEMORY_MB`.
Note: volume requirements (type and/or size) can not be changed after initial deployment.
<a name="updating-placement-constraints"></a>
### Updating Placement Constraints
Placement constraints may be updated after initial deployment using the following procedure. See [Service Settings](#service-settings) above for more information on placement constraints.
Let's say we have the following deployment of our nodes
- Placement constraint of: `hostname:LIKE:10.0.10.3|10.0.10.8|10.0.10.26|10.0.10.28|10.0.10.84`
- Tasks:
```
10.0.10.3: node-0
10.0.10.8: node-1
10.0.10.26: node-2
10.0.10.28: empty
10.0.10.84: empty
```
`10.0.10.8` is being decommissioned and we should move away from it. Steps:
1. Remove the decommissioned IP and add a new IP to the placement rule whitelist by editing `PLACEMENT_CONSTRAINT`:
```
hostname:LIKE:10.0.10.3|10.0.10.26|10.0.10.28|10.0.10.84|10.0.10.123
```
1. Redeploy `node-1` from the decommissioned node to somewhere within the new whitelist: `dcos beta-cassandra pods replace node-1`
1. Wait for `node-1` to be up and healthy before continuing with any other replacement operations.
<a name="restarting-a-node"></a>
## Restarting a Node
This operation will restart a node, while keeping it at its current location and with its current persistent volume data. This may be thought of as similar to restarting a system process, but it also deletes any data that is not on a persistent volume.
1. Run `dcos beta-cassandra pods restart node-<NUM>`, e.g. `node-2`.
<a name="replacing-a-node"></a>
## Replacing a Node
This operation will move a node to a new system and will discard the persistent volumes at the prior system to be rebuilt at the new system. Perform this operation if a given system is about to be offlined or has already been offlined.
**Note:** Nodes are not moved automatically. You must perform the following steps manually to move nodes to new systems. You canbuild your own automation to perform node replacement automatically according to your own preferences.
1. Run `dcos beta-cassandra pods replace node-<NUM>` to halt the current instance with id `<NUM>` (if still running) and launch a new instance elsewhere.
For example, let's say `node-2`'s host system has died and `node-2` needs to be moved.
```
dcos beta-cassandra pods replace node-2
```
<a name="configuring-multi-data-center-deployments"></a>
## Configuring Multi-data-center Deployments
To replicate data across data centers, Apache Cassandra requires that you configure each cluster with the addresses of the seed nodes from every remote cluster. Here's what starting a multi-data-center Apache Cassandra deployment would like, running inside of a single DC/OS cluster.
Launch the first cluster with the default configuration:
```
dcos package install beta-cassandra
```
Create an `options.json` file for the second cluster that specifies a different service name and data center name:
```json
{
"service": {
"name": "cassandra2",
"data_center": "dc2"
}
}
```
Launch the second cluster with these custom options:
```
dcos package install beta-cassandra --options=<options>.json
```
Get the list of seed node addresses for the first cluster from the scheduler HTTP API:
```json
DCOS_AUTH_TOKEN=$(dcos config show core.dcos_acs_token)
DCOS_URL=$(dcos config show core.dcos_url)
curl -H "authorization:token=$DCOS_AUTH_TOKEN" $DCOS_URL/service/cassandra/v1/seeds
{"seeds": ["10.0.0.1", "10.0.0.2"]}
```
In the DC/OS UI, go to the configuration dialog for the second cluster (whose service name is `cassandra2`) and update the `TASKCFG_ALL_REMOTE_SEEDS` environment variable to `10.0.0.1,10.0.0.2`. This environment variable may not already be present in a fresh install. To add it, click the plus sign at the bottom of the list of environment variables, and then fill in its name and value in the new row that appears.
Get the seed node addresses for the second cluster the same way:
```
curl -H "authorization:token=$DCOS_AUTH_TOKEN" $DCOS_URL/service/cassandra2/v1/seeds
{"seeds": ["10.0.0.3", "10.0.0.4"]}
```
In the DC/OS UI, go to the configuration dialog for the first cluster (whose service name is `cassandra`) and update the `TASKCFG_ALL_REMOTE_SEEDS` environment variable to `10.0.0.3,10.0.0.4`, again adding the variable with the plus sign if it's not already present.
Both schedulers will restart after the configuration update, and each cluster will communicate with the seed nodes from the other cluster to establish a multi-data-center topology. Repeat this process for each new cluster you add, appending a comma-separated list of that cluster's seeds to the `TASKCFG_ALL_REMOTE_SEEDS` environment variable for each existing cluster, and adding a comma-separated list of each existing cluster's seeds to the newly-added cluster's `TASKCFG_ALL_REMOTE_SEEDS` environment variable.
<a name="disaster-recovery"></a>
# Disaster Recovery
<a name="backup"></a>
## Backup
### Backing Up to S3
You can backup an entire cluster's data and schema to Amazon S3 using the `backup-s3` plan. This plan requires the following parameters to run:
- `SNAPSHOT_NAME`: the name of this snapshot. Snapshots for individual nodes will be stored as S3 folders inside of a top level `snapshot` folder.
- `CASSANDRA_KEYSPACES`: the Cassandra keyspaces to backup. The entire keyspace, as well as its schema, will be backed up for each keyspace specified.
- `AWS_ACCESS_KEY_ID`: the access key ID for the AWS IAM user running this backup.
- `AWS_SECRET_ACCESS_KEY`: the secret access key for the AWS IAM user running this backup.
- `AWS_REGION`: the region of the S3 bucket being used to store this backup.
- `S3_BUCKET_NAME`: the name of the S3 bucket to store this backup in.
Make sure that you provision your nodes with enough disk space to perform a backup. Apache Cassandra backups are stored on disk before being uploaded to S3, and will take up as much space as the data currently in the tables, so you'll need half of your total available space to be free to backup every keyspace at once.
As noted in the documentation for the [backup/restore strategy configuration option](#backup-restore-strategy), it is possible to run transfers to S3 either in serial or in parallel, but care must be taken not to exceed any throughput limits you may have in your cluster. Throughput depends on a variety of factors, including uplink speed, proximity to region where the backups are being uploaded and downloaded, and the performance of the underlying storage infrastructure. You should perform periodic tests in your local environment to understand what you can expect from S3.
You can configure whether snapshots are created and uploaded in serial, the default, or in parallel (see [backup/restore strategy](#backup-restore-strategy)), but the serial backup/restore strategy is recommended.
You can initiate this plan from the command line:
```
SNAPSHOT_NAME=<my_snapshot>
CASSANDRA_KEYSPACES="space1 space2"
AWS_ACCESS_KEY_ID=<my_access_key_id>
AWS_SECRET_ACCESS_KEY=<my_secret_access_key>
AWS_REGION=us-west-2
S3_BUCKET_NAME=backups
dcos cassandra plan start backup-s3 -p SNAPSHOT_NAME=$SNAPSHOT_NAME -p "CASSANDRA_KEYSPACES=$CASSANDRA_KEYSPACES" -p AWS_ACCESS_KEY_ID=$AWS_ACCESS_KEY_ID -p AWS_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY -p AWS_REGION=$AWS_REGION -p S3_BUCKET_NAME=$S3_BUCKET_NAME
```
If you're backing up multiple keyspaces, they must be separated by spaces and wrapped in quotation marks when supplied to the `plan start` command, as in the example above. If the `CASSANDRA_KEYSPACES` parameter isn't supplied, then every keyspace in your cluster will be backed up.
**IMPORTANT**: To ensure that sensitive information, such as your AWS secret access key, remains secure, make sure that you've set the `core.dcos_url` configuration property in the DC/OS CLI to an HTTPS URL.
### Backing up to Azure
You can also back up to Microsoft Azure using the `backup-azure` plan. This plan requires the following parameters to run:
- `SNAPSHOT_NAME`: the name of this snapshot. Snapshots for individual nodes will be stored as gzipped tarballs with the name `node-<POD_INDEX>.tar.gz`.
- `CASSANDRA_KEYSPACES`: the Cassandra keyspaces to backup. The entire keyspace, as well as its schema, will be backed up for each keyspace specified.
- `CLIENT_ID`: the client ID for the Azure service principal running this backup.
- `TENANT_ID`: the tenant ID for the tenant that the service principal belongs to.
- `CLIENT_SECRET`: the service principal's secret key.
- `AZURE_STORAGE_ACCOUNT`: the name of the storage account that this backup will be sent to.
- `AZURE_STORAGE_KEY`: the secret key associated with the storage account.
- `CONTAINER_NAME`: the name of the container to store this backup in.
You can initiate this plan from the command line in the same way as the Amazon S3 backup plan:
```
dcos cassandra plan start backup-azure -p SNAPSHOT_NAME=$SNAPSHOT_NAME -p "CASSANDRA_KEYSPACES=$CASSANDRA_KEYSPACES" -p CLIENT_ID=$CLIENT_ID -p TENANT_ID=$TENANT_ID -p CLIENT_SECRET=$CLIENT_SECRET -p AZURE_STORAGE_ACCOUNT=$AZURE_STORAGE_ACCOUNT -p AZURE_STORAGE_KEY=$AZURE_STORAGE_KEY -p CONTAINER_NAME=$CONTAINER_NAME
```
<a name="restore"></a>
## Restore
All restore plans will restore the schema from every keyspace backed up with the backup plan and populate those keyspaces with the data they contained at the time the snapshot was taken. Downloading and restoration of backups will use the configured backup/restore strategy. This plan assumes that the keyspaces being restored do not already exist in the current cluster, and will fail if any keyspace with the same name is present.
### Restoring From S3
Restoring cluster data is similar to backing it up. The `restore-s3` plan assumes that your data is stored in an S3 bucket in the format that `backup-s3` uses. The restore plan has the following parameters:
- `SNAPSHOT_NAME`: the snapshot name from the `backup-s3` plan.
- `AWS_ACCESS_KEY_ID`: the access key ID for the AWS IAM user running this restore.
- `AWS_SECRET_ACCESS_KEY`: the secret access key for the AWS IAM user running this restore.
- `AWS_REGION`: the region of the S3 bucket being used to store the backup being restored.
- `S3_BUCKET_NAME`: the name of the S3 bucket where the backup is stored.
To initiate this plan from the command line:
```
SNAPSHOT_NAME=<my_snapshot>
AWS_ACCESS_KEY_ID=<my_access_key_id>
AWS_SECRET_ACCESS_KEY=<my_secret_access_key>
AWS_REGION=us-west-2
S3_BUCKET_NAME=backups
dcos beta-cassandra plan start backup-s3 "SNAPSHOT_NAME=$SNAPSHOT_NAME,AWS_ACCESS_KEY_ID=$AWS_ACCESS_KEY_ID,AWS_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY,AWS_REGION=$AWS_REGION,S3_BUCKET_NAME=$S3_BUCKET_NAME"
```
### Restoring From Azure
You can restore from Microsoft Azure using the `restore-azure` plan. This plan requires the following parameters to run:
- `SNAPSHOT_NAME`: the name of this snapshot. Snapshots for individual nodes will be stored as gzipped tarballs with the name `node-<POD_INDEX>.tar.gz`.
- `CLIENT_ID`: the client ID for the Azure service principal running this backup.
- `TENANT_ID`: the tenant ID for the tenant that the service principal belongs to.
- `CLIENT_SECRET`: the service principal's secret key.
- `AZURE_STORAGE_ACCOUNT`: the name of the storage account that this backup will be sent to.
- `AZURE_STORAGE_KEY`: the secret key associated with the storage account.
- `CONTAINER_NAME`: the name of the container to store this backup in.
You can initiate this plan from the command line in the same way as the Amazon S3 restore plan:
```
dcos cassandra plan start restore-azure -p SNAPSHOT_NAME=$SNAPSHOT_NAME -p CLIENT_ID=$CLIENT_ID -p TENANT_ID=$TENANT_ID -p CLIENT_SECRET=$CLIENT_SECRET -p AZURE_STORAGE_ACCOUNT=$AZURE_STORAGE_ACCOUNT -p AZURE_STORAGE_KEY=$AZURE_STORAGE_KEY -p CONTAINER_NAME=$CONTAINER_NAME
```
<a name="troubleshooting"></a>
# Troubleshooting
<a name="accessing-logs"></a>
## Accessing Logs
Logs for the scheduler and all service nodes can be viewed from the DC/OS web interface.
- Scheduler logs are useful for determining why a node isn't being launched (this is under the purview of the Scheduler).
- Node logs are useful for examining problems in the service itself.
In all cases, logs are generally piped to files named `stdout` and/or `stderr`.
To view logs for a given node, perform the following steps:
1. Visit <dcos-url> to access the DC/OS web interface.
1. Navigate to `Services` and click on the service to be examined (default `cassandra`).
1. In the list of tasks for the service, click on the task to be examined (scheduler is named after the service, nodes are each `node-<NUM>-server`).
1. In the task details, click on the `Logs` tab to go into the log viewer. By default, you will see `stdout`, but `stderr` is also useful. Use the pull-down in the upper right to select the file to be examined.
You can also access the logs via the Mesos UI:
1. Visit <dcos-url>/mesos to view the Mesos UI.
1. Click the `Frameworks` tab in the upper left to get a list of services running in the cluster.
1. Navigate into the correct framework for your needs. The scheduler runs under `marathon` with a task name matching the service name (default _`PKGNAME`_). Service nodes run under a framework whose name matches the service name (default _`PKGNAME`_).
1. You should now see two lists of tasks. `Active Tasks` are tasks currently running, and `Completed Tasks` are tasks that have exited. Click the `Sandbox` link for the task you wish to examine.
1. The `Sandbox` view will list files named `stdout` and `stderr`. Click the file names to view the files in the browser, or click `Download` to download them to your system for local examination. Note that very old tasks will have their Sandbox automatically deleted to limit disk space usage.
<a name="limitations"></a>
# Limitations
- For multi-data-center configurations, the hostnames for the seed nodes in each cluster must be routable from every other cluster. Typically, DC/OS hosts are members of a private subnet that is not routable from external hosts, so further network configuration is required to achieve this.
<a name="support"></a>
# Support
## Supported Versions
The DC/OS Apache Cassandra Service runs Cassandra v3.0.13. It supports DC/OS version 1.8 and later.
| 52.258017 | 577 | 0.763982 | eng_Latn | 0.965984 |
6ad195289d6c257d68fd03a42e38641c9055fefd | 87 | md | Markdown | import-back/README.md | Xuanwo/openacid.github.io | 6e347aff98b25f6cd02acf7acb81ede98c78f6fa | [
"MIT"
] | 2 | 2021-11-09T21:04:56.000Z | 2022-01-03T14:50:22.000Z | import-back/README.md | Xuanwo/openacid.github.io | 6e347aff98b25f6cd02acf7acb81ede98c78f6fa | [
"MIT"
] | 24 | 2019-02-01T05:40:37.000Z | 2022-02-09T16:55:35.000Z | import-back/README.md | Xuanwo/openacid.github.io | 6e347aff98b25f6cd02acf7acb81ede98c78f6fa | [
"MIT"
] | 1 | 2021-11-09T21:04:57.000Z | 2021-11-09T21:04:57.000Z | This folder contains articles imported from web as markdown, with all medias
uploaded.
| 29 | 76 | 0.827586 | eng_Latn | 0.999927 |
6ad2004d71a0dcf31cb71c18b5b686ff13ff1014 | 5,362 | md | Markdown | docs/onsite/version-history.md | SuperOfficeDocs/superoffice-docs | 6696af195598bf1baebada1c0624b5d833cd68e3 | [
"MIT"
] | 2 | 2022-02-15T22:41:17.000Z | 2022-03-30T07:17:15.000Z | docs/onsite/version-history.md | acdavidh/superoffice-docs | 873de11300c32857c73c4131b8fb50152931ac28 | [
"MIT"
] | 155 | 2021-04-20T11:50:13.000Z | 2022-03-30T11:23:26.000Z | docs/onsite/version-history.md | SuperOfficeDocs/superoffice-docs | 6696af195598bf1baebada1c0624b5d833cd68e3 | [
"MIT"
] | 8 | 2021-05-14T15:14:04.000Z | 2022-03-31T08:07:12.000Z | ---
title: Onsite version history
uid: version_history
description: SuperOffice version history overview
author: {github-id}
keywords: onsite, version, history, release
so.topic: reference
so.envir: onsite
# so.client:
---
# SuperOffice Onsite version history
An overview of Release names, with Release number, Date, and Build number.
It does not contain Red Alerts or [CRM Online release versions][1].
| Onsite Release Name | Release number | Date | Build number |
|-----|-----|-----|-----|
| 6.1 Main Release | 6.1.1.540 | 2007/06/21 | |
| 6.1 SR1 | 6.1.2.70 | 2008/02/16 | |
| 6.2 Release | 6.2.1.550 | 2008/12/18 | |
| 6.3 Release | 6.3.1.110 | 2009/09/16 | |
| 7.0 Beta 1 | 7.0.3832b.1100 | 2010/06/30 | |
| 6.3 SR1 | 6.3.2.528 | 2010/09/14 | |
| 7.0 Beta 2 | 7.0.3923.000 | 2010/09/28 | |
| 7.0 RC | 7.0.3974.000 | 2010/11/18 | |
| 7.0 | 7.0.4003.1200 (a) | 2010/12/17 | |
| 6.3 SR2 (with 7.0 MailLink) | 6.3.3.700 | 2011/02/18 | |
| 7.0 SR1 RC | 7.0.4145.0 | 2011/05/10 | |
| 7.0 SR1 | 7.0.4167.1700 | 2011/06/01 | |
| 7.0 SR2 | 7.0.4265.1600 | 2011/09/05 | |
| 7.0 SR3 | 7.0.4421.0 | 2012/02/10 | |
| 7.0 SR3 actually released | 7.0.4465.a | 2012/03/23 | |
| 7.1 Beta 1 | 7.1.4364.a | 2011/12/14 | |
| 7.1 Beta 2 | 7.1.4394.b | 2012/01/13 | |
| 7.1 Beta 3 | 7.1.4433.b | 2012/02/20 | |
| 7.1 Beta 3 - 2 | 7.1.4437.a | 2012/02/24 | |
| 7.1 RC | 7.1.4472 | 2012/03/30 | |
| 7.1 RC SO internal w invitations | 7.1.4484.a | 2012/04/11 | |
| 7.1 | 7.1.4507.a | 2012/05/04 | |
| 7.1 SR1 | 7.1.4724.100 | 2012/12/14 | |
| 7.1 SR1.b | 7.1.4760.100 | 15.01.2013 | |
| 7.1 SR2 | 7.1.4816.100 | 14.03.2013 | |
| 7.2 Visma.Net | 7.2.4680 web | 24.10.2012 | |
| 7.2 SR1 | 7.2.4919.100 web | 20.06.2013 | |
| 7.5 Alpha (Quote & EIS) | 7.5.4924 | 25.06.2013 | |
| 7.5 Beta 1 | 7.5.5021.b | 01.10.2013 | |
| 7.5 Beta 2 | 7.5.5055 | 04.11.2013 | |
| 7.5 Beta 2 Internal | 7.5.5080 | 28.11.2013 | |
| 7.5 RC1 | 7.5.5098 | 16.12.2014 | |
| 7.5 RC2 | 7.5.5141.a, CS 7.5.5142.a | 28.01.2014 | |
| 7.5 | 7.5.5154.a | 10.02.2014 | |
| 7.5 HotFix 1 | 7.5.5163.a | 19.02.2014 | |
| 7.5 Patch 1 | 7.5.5199.a | 07.04.2014 | |
| 7.5 Patch 2 | 7.5.5253 | 20.05.2014 | |
| 7.5 SR1 | 7.5.5543 | 06.03.2015 | |
| 7.5 SR2 | 7.5.5885.b | 11.02.2016 | |
| 8.0 Beta 2 | 8.0.5752.b | 01.10.2016 | |
| 8.0 Beta 3 | 8.0.5767 | 16.10.2015 | |
| 8.0 RC1 | 8.0.5781.c | 30.10.2015 | |
| 8.0 RC2 | 8.0.5795 | 13.11.2015 | |
| 8.0 FRC | 8.0.5816 | 04.12.2015 | |
| 8.0 | 8.0.5828.a | 16.12.2015 | |
| 8.0 SR1 | 8.0.5893.a | 22.02.2016 | |
| 8.0 SR2 | 8.0.6004 | 09.06.2016 | 2016-22 |
| 8.0 SR2 Patch1 | 8.0.6018 | 23.06.2016 | |
| 8.0 SR3 | 8.0.6102.c | 15.09.2016 | 2016-35.5 |
| 8.0 SR4 | 8.0.6144 | 28.10.2016 | |
| 8.0 SR5 | 8.0.6352 | 23.05.2017 | |
| 8.0 SR6 | 8.0.6465 | 15.09.2017 | |
| 8.1 R01 | 8.0.6499 | 19.10.2017 | 2017.10.17-3 |
| 8.1 R02 | 8.1.6514.1619 | 15.11.2017 | 2017.11.01-3 |
| 8.1 R03 | 8.1.6536.16 | 27.11.2017 | 2017.11.23-01 |
| 8.2 R01 | 8.2.6550.1025 | 18.12.2017 | 2017.12.07-03 |
| 8.2 R02 | (Onsite skipped) | 16.01.2018 | |
| 8.2 R03 | 8.2.6617.1308 | 14.02.2018 | 2018.02.12-03 |
| 8.2 R04 | | 13.03.2018 | 2018.03.09-05 |
| 8.2 R05 | (Onsite skipped) | | |
| 8.2 R06 | 8.2.6689.1603 | | 2018.04.25-01 |
| 8.3 R01 | 8.3.6718.18 | 24.05.2018 | |
| 8.3 R02 | | 21.06.2018 | 2018.06.21-01 |
| 8.3 R03 | (Onsite skipped) | | |
| 8.3 R04 | | 28.08.2018 | 2018.08.24-01 |
| 8.4 R01 | | 21.09.2018 | 2018.09.20-03 |
| 8.4 R02 | | 09.10.2018 | 2018.10.03-01 |
| 8.4 R03 | | 06.11.2018 | 2018.11.05-03 |
| 8.4 R04 | | 11.12.2018 | 2018.12.07-01 |
| 8.4 R05 | | 29.01.2019 | 2019.01.25 |
| 8.4 R06 | | 18.02.2019 | 2019.02.11-01 |
| 8.4 R07 | | 15.03.2019 | 2019.03.15-01 |
| 8.4 R08 | | 10.04.2019 | 2019.04.09-01 |
| 8.5 R01 | | 14.05.2019 | 2019.05.13-02 |
| 8.5 R02 | | 06.06.2019 | 2019.06.03-01 |
| 8.5 R03 | | 03.07.2019 | 2019.07.01-01 |
| 8.5 R04 | | 04.09.2019 | 2019.09.03-01 |
| 8.5 R05 | | 02.10.2019 | 2019.10.02-01 |
| 8.5 R06 | | 23.10.2019 | 2019.10.15-01 |
| 8.5 R07 | | 13.11.2019 | 2019.11.05-02 |
| 8.5 R08 | (Onsite skipped) | | |
| 8.5 R09 | 08.01.2020 | 2020.01.09-03 |
| 8.5 R10 | | 12.02.2020 | 2020.02.11-04 |
| 8.5 R11 | | 05.03.2020 | 2020.02.27-02 |
| 8.5 R12 | | 25.03.2020 | 2020.03.25-01 |
| 8.5 R13 | | 15.04.2020 | 2020.04.15-01 |
| 8.5 R14 | | 13.05.2020 | 2020.05.12-01 |
| 8.5 R15 | | 03.06.2020 | 2020.06.02-01 |
| 8.5 R15 Hotfix | Web hotfix only | 12.10.2020 | |
| 8.5 R16 | | 16.12.2020 | 2020.12.15-02 |
| 9.1 R01 | (Onsite skipped) | | |
| 9.1 R02 | | 27.08.2020 | 2020.08.26-03 |
| 9.1 R03 | | 08.10.2020 | 2020.10.06-03 |
| 9.2 R01 | (Onsite skipped) | | |
| 9.2 R02 | (Onsite skipped) | | |
| 9.2 R03 | | 16.12.2020 | 2020.12.15-04 |
| 9.2 R04 | (Onsite skipped) | | |
| 9.2 R05 | (Onsite skipped) | | |
| 9.2 R06 | (Onsite skipped) | | |
| 9.2 R07 | | 16.04.2021 | 2021.04.27-02 |
| 9.2 R08 | (Onsite skipped) | | |
| 9.2 R09 | | 27.05.2021 | 2021.05.25-04 |
| 9.2 R10 | | 07.07.2021 | 2021-07.02-02 |
| 9.2 R11 | (Onsite skipped) | | |
| 9.2 R12 | | 23.09.2021 | 2021.09.22-01 |
| 10.0.1 | (Onsite skipped) | | |
| 10.0.2 | | 11.11.2021 | 2021.11.11-03 |
| 10.0.3 | (Onsite skipped) | | |
| 10.0.4 | (Onsite skipped) | | |
<!-- Referenced links -->
[1]: ../online/version-history.md
| 40.621212 | 75 | 0.536367 | yue_Hant | 0.084555 |
6ad237e25b2848b4d7ae3bf3211669735d01d4ba | 9,259 | md | Markdown | articles/storage/tables/table-storage-design-modeling.md | gliljas/azure-docs.sv-se-1 | 1efdf8ba0ddc3b4fb65903ae928979ac8872d66e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/storage/tables/table-storage-design-modeling.md | gliljas/azure-docs.sv-se-1 | 1efdf8ba0ddc3b4fb65903ae928979ac8872d66e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/storage/tables/table-storage-design-modeling.md | gliljas/azure-docs.sv-se-1 | 1efdf8ba0ddc3b4fb65903ae928979ac8872d66e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Modellerings relationer i Azure Table Storage design | Microsoft Docs
description: Förstå modell processen när du utformar din lösning för tabell lagring.
services: storage
author: MarkMcGeeAtAquent
ms.service: storage
ms.topic: article
ms.date: 04/23/2018
ms.author: sngun
ms.subservice: tables
ms.openlocfilehash: 25082c107fbc0feeb533aa2b4fc56cff960e778d
ms.sourcegitcommit: 849bb1729b89d075eed579aa36395bf4d29f3bd9
ms.translationtype: MT
ms.contentlocale: sv-SE
ms.lasthandoff: 04/28/2020
ms.locfileid: "75457560"
---
# <a name="modeling-relationships"></a>Modellera relationer
I den här artikeln beskrivs modell processen som hjälper dig att utforma dina lagrings lösningar för Azure-tabeller.
Att skapa domän modeller är ett viktigt steg i utformningen av komplexa system. Normalt använder du modellerings processen för att identifiera entiteter och relationerna mellan dem som ett sätt att förstå företags domänen och informera utformningen av ditt system. Det här avsnittet fokuserar på hur du kan översätta några av de vanliga Relations typerna i domän modeller till design för Table service. Processen för att mappa från en logisk data modell till en fysisk NoSQL-baserad data modell skiljer sig från den som användes när du skapar en Relations databas. Design av Relations databaser förutsätter vanligt vis en data normaliserings process som är optimerad för att minimera redundans – och en deklarativ fråge funktion som sammanfattar hur databasen fungerar.
## <a name="one-to-many-relationships"></a>En-till-många-relationer
En-till-många-relationer mellan företags domän objekt inträffar ofta: till exempel är en avdelning många anställda. Det finns flera sätt att implementera en-till-många-relationer i Table service var och en med-och nack delar som kan vara relevanta för det specifika scenariot.
Överväg exemplet på ett stort företag med flera nationella organisationer med tusentals avdelningar och personal enheter där varje avdelning har många anställda och varje medarbetare som är kopplad till en speciell avdelning. En metod är att lagra separata avdelnings-och anställdas enheter, till exempel följande:
Det här exemplet visar en implicit en-till-många-relation mellan typerna baserat på **PartitionKey** -värdet. Varje avdelning kan ha många anställda.
I det här exemplet visas även en avdelnings enhet och dess relaterade anställdas entiteter i samma partition. Du kan välja att använda olika partitioner, tabeller eller till och med lagrings konton för de olika enhets typerna.
En annan metod är att avnormalisera dina data och lagra endast anställdas enheter med avnormaliserade avdelnings data som visas i följande exempel. I det här scenariot kanske det här avnormaliserade tillvägagångs sättet inte är det bästa om du har ett krav för att kunna ändra informationen om en avdelnings hanterare, eftersom du måste uppdatera varje anställd på avdelningen för att göra detta.
Mer information finns i avsnittet om [avnormaliserings mönster](table-storage-design-patterns.md#denormalization-pattern) senare i den här hand boken.
I följande tabell sammanfattas de olika metoderna och nack delar med var och en av de metoder som beskrivs ovan för att lagra personal-och avdelnings enheter som har en en-till-många-relation. Du bör också fundera över hur ofta du förväntar dig att utföra olika åtgärder: det kan vara acceptabelt att ha en design som innehåller en dyr åtgärd om åtgärden bara sker sällan.
<table>
<tr>
<th>Metod</th>
<th>Fördelar</th>
<th>Nackdelar</th>
</tr>
<tr>
<td>Separata entitetstyper, samma partition, samma tabell</td>
<td>
<ul>
<li>Du kan uppdatera en avdelnings enhet med en enda åtgärd.</li>
<li>Du kan använda en EGT för att upprätthålla konsekvens om du har ett krav på att ändra en avdelnings enhet när du uppdaterar/infogar/tar bort en anställds entitet. Om du till exempel underhåller ett antal anställda för varje avdelning.</li>
</ul>
</td>
<td>
<ul>
<li>Du kan behöva hämta både en anställd och en avdelnings enhet för vissa klient aktiviteter.</li>
<li>Lagrings åtgärder sker i samma partition. På hög transaktions volymer kan detta resultera i ett hotspot-område.</li>
<li>Du kan inte flytta en medarbetare till en ny avdelning med hjälp av en EGT.</li>
</ul>
</td>
</tr>
<tr>
<td>Separata entitetstyper, olika partitioner eller tabeller eller lagrings konton</td>
<td>
<ul>
<li>Du kan uppdatera en avdelnings enhet eller en anställds entitet med en enda åtgärd.</li>
<li>På hög transaktions volymer kan detta hjälpa till att sprida belastningen över flera partitioner.</li>
</ul>
</td>
<td>
<ul>
<li>Du kan behöva hämta både en anställd och en avdelnings enhet för vissa klient aktiviteter.</li>
<li>Du kan inte använda EGTs för att upprätthålla konsekvens när du uppdaterar/infogar/tar bort en medarbetare och uppdaterar en avdelning. Du kan till exempel uppdatera ett antal anställda i en avdelnings enhet.</li>
<li>Du kan inte flytta en medarbetare till en ny avdelning med hjälp av en EGT.</li>
</ul>
</td>
</tr>
<tr>
<td>Avnormalisera till en enhets typ</td>
<td>
<ul>
<li>Du kan hämta all information som du behöver med en enskild begäran.</li>
</ul>
</td>
<td>
<ul>
<li>Det kan vara dyrt att upprätthålla konsekvens om du behöver uppdatera avdelnings information (Detta kräver att du uppdaterar alla anställda på en avdelning).</li>
</ul>
</td>
</tr>
</table>
Hur du väljer mellan dessa alternativ och vilka av-och nack delar som är mest signifikanta beror på dina specifika program scenarier. Till exempel hur ofta ändrar du avdelnings enheter. behöver alla dina anställda-frågor ytterligare avdelnings information. hur nära är du på skalbarhets gränserna för dina partitioner eller ditt lagrings konto?
## <a name="one-to-one-relationships"></a>En-till-en-relationer
Domän modeller kan innehålla en-till-en-relationer mellan entiteter. Om du behöver implementera en en-till-en-relation i Table service måste du också välja hur du länkar de två relaterade entiteterna när du behöver hämta dem. Den här länken kan vara antingen implicit, baserat på en konvention i nyckel värden eller explicit genom att en länk lagras i form av **PartitionKey** -och **RowKey** -värden i varje entitet till dess relaterade entitet. En beskrivning av huruvida du bör lagra relaterade entiteter i samma partition finns i avsnittet [en-till-många-relationer](#one-to-many-relationships).
Det finns också implementerings överväganden som kan leda till att du implementerar en-till-en-relationer i Table service:
* Hantering av stora entiteter (mer information finns i [mönster för stora entiteter](table-storage-design-patterns.md#large-entities-pattern)).
* Implementera åtkomst kontroller (mer information finns i kontrol lera åtkomst med signaturer för delad åtkomst).
## <a name="join-in-the-client"></a>Anslut till klienten
Även om det finns olika sätt att modellera relationer i Table service bör du inte glömma att de två huvudsakliga orsakerna till att använda Table service är skalbarhet och prestanda. Om du hittar flera relationer som äventyrar prestanda och skalbarhet för din lösning, bör du fråga dig själv om det är nödvändigt att bygga alla data relationer i tabell designen. Du kanske kan förenkla designen och förbättra skalbarheten och prestandan för din lösning om du låter klient programmet utföra alla nödvändiga kopplingar.
Om du till exempel har små tabeller som innehåller data som inte ändras ofta kan du hämta dessa data en gång och cachelagra den på klienten. Detta kan undvika upprepade turer för att hämta samma data. I exemplen som vi har tittat på i den här hand boken är en uppsättning avdelningar i en liten organisation troligt vis liten och ändra sällan så att det blir en bra kandidat för data som klient programmet kan ladda ned en gång och cachelagra som att slå upp data.
## <a name="inheritance-relationships"></a>Arvs relationer
Om klient programmet använder en uppsättning klasser som utgör en del av en arvs relation som representerar affär senheter, kan du enkelt spara dessa entiteter i Table service. Du kan till exempel ha följande uppsättning klasser definierade i klient programmet där **personen** är en abstrakt klass.
Du kan spara instanser av de två konkreta klasserna i Table service med hjälp av en enda person tabell med hjälp av entiteter i som ser ut så här:
Mer information om hur du arbetar med flera olika entitetstyper i samma tabell i klient koden finns i avsnittet arbeta med heterogena entitetstyper senare i den här hand boken. Detta ger exempel på hur du kan identifiera enhets typen i klient koden.
## <a name="next-steps"></a>Nästa steg
- [Mönster för tabelldesign](table-storage-design-patterns.md)
- [Utforma för frågor](table-storage-design-for-query.md)
- [Kryptera tabell data](table-storage-design-encrypt-data.md)
- [Utforma för dataändring](table-storage-design-for-modification.md)
| 71.775194 | 771 | 0.799222 | swe_Latn | 0.999983 |
6ad3de0dded0c366f0755fe6cc2bb07ca19aa723 | 39 | md | Markdown | Prerequisite.md | vineeth-cnbr/SLAC-2018 | 338adf5ddcd3b03d713c6b143c3e9dcec27f0af1 | [
"MIT"
] | 1 | 2018-03-09T08:21:17.000Z | 2018-03-09T08:21:17.000Z | Prerequisite.md | vineeth-cnbr/SLAC-2018 | 338adf5ddcd3b03d713c6b143c3e9dcec27f0af1 | [
"MIT"
] | 9 | 2021-03-21T16:31:06.000Z | 2022-01-12T20:52:50.000Z | Prerequisite.md | vineeth-cnbr/slac2018 | 338adf5ddcd3b03d713c6b143c3e9dcec27f0af1 | [
"MIT"
] | 3 | 2020-05-26T07:38:36.000Z | 2021-03-21T16:34:00.000Z | Details in [package.json](package.json) | 39 | 39 | 0.794872 | eng_Latn | 0.367213 |
6ad47e47df4a51819d518405b7214f0cb10a5d19 | 760 | md | Markdown | _posts/Python/F/filecmp/filecmp/2021-01-01-filecmp.md | w3api/w3api | 681462ece7265723031a88bec5285209d0e125bf | [
"MIT"
] | 1 | 2021-09-15T20:32:10.000Z | 2021-09-15T20:32:10.000Z | _posts/Python/F/filecmp/filecmp/2021-01-01-filecmp.md | w3api/w3api | 681462ece7265723031a88bec5285209d0e125bf | [
"MIT"
] | 20 | 2021-01-17T01:13:46.000Z | 2021-06-20T21:16:02.000Z | _posts/Python/F/filecmp/filecmp/2021-01-01-filecmp.md | w3api/w3api | 681462ece7265723031a88bec5285209d0e125bf | [
"MIT"
] | 2 | 2021-09-15T20:32:08.000Z | 2022-02-20T16:57:46.000Z | ---
title: filecmp.filecmp
permalink: /Python/filecmp/filecmp/
date: 2021-01-01
key: Python.F.filecmp.filecmp
category: python
tags: ['clase python', 'filecmp']
sidebar:
nav: python
---
{% include w3api/datos.html clase=site.data.Python.F.filecmp.filecmp.metodos valor="filecmp/filecmp" %}
## Descripción
{{site.data.Python.F.filecmp.filecmp.description }}
## Sintaxis
~~~python
{{ site.data.Python.F.filecmp.filecmp.sintaxis }}~~~
## Atributos
* [DEFAULT_IGNORES](/Python/filecmp/filecmp/DEFAULT_IGNORES/)
## Ejemplo
~~~python
{{ site.data.Python.F.filecmp.filecmp.code}}
~~~
## Artículos
<ul>
{%- for _ldc in site.data.Python.F.filecmp.filecmp.ldc -%}
<li>
<a href="{{_ldc['url'] }}">{{ _ldc['nombre'] }}</a>
</li>
{%- endfor -%}
</ul>
| 20.540541 | 103 | 0.672368 | yue_Hant | 0.521344 |
6ad49270f79dee439c9e441287532bbb57a2ddf1 | 11,963 | md | Markdown | _posts/2020-10-27-kubernetes-webhooks-made-easy-with-openfaas.md | iboonox/openfaas.github.io | c5e9d8e21456159190fe7778a9889c5a51d1edf3 | [
"MIT"
] | null | null | null | _posts/2020-10-27-kubernetes-webhooks-made-easy-with-openfaas.md | iboonox/openfaas.github.io | c5e9d8e21456159190fe7778a9889c5a51d1edf3 | [
"MIT"
] | null | null | null | _posts/2020-10-27-kubernetes-webhooks-made-easy-with-openfaas.md | iboonox/openfaas.github.io | c5e9d8e21456159190fe7778a9889c5a51d1edf3 | [
"MIT"
] | null | null | null | ---
title: "Kubernetes Webhooks made easy with OpenFaaS"
description: "In this post you'll learn how to write Kubernetes Admission webhooks using OpenFaaS functions"
date: 2020-10-27
image: /images/2020-10-27-k8s-validatingwebhook-openfaas/puzzle.jpg
categories:
- arkade
- kubectl
- faas-cli
- admissionwebhooks
- validatingadmissionwebhooks
- k8s extensibility
author_staff_member: batuhan
dark_background: true
---
In this post you'll learn how to write Kubernetes Admission webhooks using OpenFaaS functions
<p align="center">
<img height="128" src="/images/openfaas/kubernetes.png">
</p>
## Introduction to Kubernetes Admission webhooks
Admission webhooks are HTTP callbacks that receive admission requests and do something with them. You can define two types of admission webhooks, validating admission webhook and mutating admission webhook. Mutating admission webhooks are invoked first, and can modify objects sent to the API server to enforce custom defaults. After all object modifications are complete, and after the incoming object is validate by the API server, validating admission webhooks are invoked and can reject requests to enforce custom policies.
Using OpenFaaS in this design, we can focus on our core logic more than designing the microservice itself and simply create application without being worry about how to build and deploy.
## The Scenario
Let's assume, in our company, we have some requirements that we must meet while deploying applications onto the Kubernetes cluster. We need to set some required labels to our Kubernetes manifest. Unless we specify the required labels our request will reject.
So, in order to apply those requirements to the Kubernetes cluster to ensure the best practices, we can use Kubernetes [ValidatingAdmissionWebhook](https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#validatingadmissionwebhook) and [OpenFaaS](https://www.openfaas.com) together. Since ValidatingAdmissionWebhooks intercepts requests to the apiserver, OpenFaaS functions includes a little code to check required labels and determines the request either allowed or not.
Webhook Admission Server is just plain http server that adhere to Kubernetes API. For each Pod create request to the apiserver(I said Pod because we specify which kind of resources that we consider while registering our webhook to the apiserver using [ValidatingWebhookConfiguration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.19/#validatingwebhookconfiguration-v1-admissionregistration-k8s-io) resource) the ValidatingAdmissionWebhook sends an admissionReview([API](https://github.com/kubernetes/kubernetes/blob/release-1.19/pkg/apis/admission/types.go) for reference) to the relevant webhook admission server. The webhook admission server gathers information like object, oldobject, and userInfo from admissionReview's AdmissionRequest and sends AdmissionRequest to the serverless function through the OpenFaaS Gateway. The function checks the required labels exist on Pod and determines the request either valid or not and then sends back the AdmissionResponse whose Allowed and Result fields are filled with the admission decision to the webhook admission server then the webhook admission servers sends back a admissionReview to the apiserver.
* Kubernetes API -> Webhook (w/TLS) -> OpenFaaS Gateway (w/HTTP) -> OpenFaaS Function
> Credit: [https://kubernetes.io/blog/2019/03/21/a-guide-to-kubernetes-admission-controllers/](https://kubernetes.io/blog/2019/03/21/a-guide-to-kubernetes-admission-controllers/)
Supporting TLS for external webhook server is also required because admission is a high security operation. As part of the process, we need to create a TLS certificate signed by the Kubernetes CA to secure the communication between the webhook server and apiserver.
### Prerequisites
##### Arkade
* [arkade](https://get-arkade.dev) is The OpenFaaS community built tool for Kubernetes developers, with arkade you can easily install all necessary cli tools to your host and deploy apps to the cluster.
```sh
$ curl -sLS https://dl.get-arkade.dev | sudo sh
```
##### KinD (Kubernetes in Docker)
* Kubernetes is our recommendation for teams running at scale, but in this demo we will be using [KinD](https://kind.sigs.k8s.io/docs/user/quick-start/) for the sake of simplicity.
```sh
$ arkade get kind
```
##### kubectl
* You can control your cluster using [kubectl](https://github.com/kubernetes/kubectl) CLI.
```sh
$ arkade get kubectl
```
##### faas-cli
* [faas-cli](https://github.com/openfaas/faas-cli) is an official CLI for OpenFaaS , with "faas-cli" you can build and deploy functions easily.
```sh
$ arkade get faas-cli
```
### Setup
### 1. Setup a Kubernetes Cluster with KinD
You can start a Kubernetes cluster with KinD if you don't have one already
```bash
$ arkade get kind
$ kind create cluster
```
### 2. Deploy OpenFaaS to our local Kubernetes Cluster with arkade:
* Install a OpenFaaS
```sh
$ arkade install openfaas
```
Read the output from the installation and run the commands given to you.
You can access them again at any time with `arkade info openfaas`
### 3. Clone the project
* Clone the sample from GitHub
```sh
$ git clone https://github.com/developer-guy/admission-webhook-example-with-openfaas
$ cd admission-webhook-example-with-openfaas
```
* Let's explore the structure of the project.
```
deployment/ --> includes necessary manifests and scripts for the deployment of the project
functions/ --> includes templates and the requiredlabel function itself
Dockerfile --> includes instructions to build an image of the project
build --> automated way to build and push an image of the project
```
### 4. Deploy ValidatingAdmissionWebhook
* We will generate the TLS certificates required for the ValidatingAdmissionWebhook using the following: [Kubernetes TLS Certificates Management](https://kubernetes.io/docs/tasks/tls/managing-tls-in-a-cluster/)
```sh
$ cd deployment
$ sh webhook-create-signed-cert.sh
```
* Get the Certificate Authority (CA) from the local cluster
```sh
$ export CA_BUNDLE=$(kubectl config view --minify --flatten -o json | jq -r '.clusters[] | select(.name == "'$(kubectl config current-context)'") | .cluster."certificate-authority-data"')
$ sed -e "s|\${CA_BUNDLE}|${CA_BUNDLE}|g" validatingwebhook.yaml | kubectl apply -f -
$ cd ..
```
* Build the project
```sh
$ export DOCKER_USER="docker-hub-username"
$ ./build
```
Now edit `deployment.yaml` and set 'DOCKER_USER' to the above.
* Deploy it project
```sh
$ cd deployment
$ kubectl apply -f rbac.yaml,service.yaml,deployment.yaml
```
### 5. Build and Deploy OpenFaaS Function (Optional)
* Pull the [golang-middleware](https://github.com/openfaas-incubator/golang-http-template) template from [OpenFaaS Official Template Store](https://github.com/openfaas/store)
```sh
$ faas-cli template store list # check available templates in store
$ faas-cli template store describe golang-middleware # describe the specific template
$ faas-cli template store pull golang-middleware
```
* Create the function
```sh
$ export OPENFAAS_PREFIX=$DOCKER_USER
$ faas-cli new requiredlabel --lang go-middleware
$ cd requiredlabel
$ go mod init requiredlabel
$ # fill the handler.go with the corresponding code
$ go get
```
* Deploy the function
```sh
$ cd functions
$ faas-cli up -f requiredlabel.yml --build-arg GO111MODULE=on # (build-push-deploy) make sure you are using your docker hub username. i.e: devopps
```
* Verify the functions that are working in `openfaas-fn` namespace
```sh
$ kubectl get pods --namespace openfaas-fn
```
### 6. Test the whole workflow
* The purpose of this PoC is that to validate that pods has required `labels`. Which means you must have that labels:
```yaml
app.kubernetes.io/name: sleep
app.kubernetes.io/instance: sleep
app.kubernetes.io/version: "0.1"
app.kubernetes.io/component: dummy
app.kubernetes.io/part-of: admission-webhook-example
app.kubernetes.io/managed-by: kubernetes
```
* Any Pod who have above labels is valid for us.
```sh
`deployment/sleep.yaml` -> Incorrect, not-valid (We should deny this creation request.)
`deployment/sleep-no-validation.yaml` -> Skip-validation (Based on `admission-webhook-example.qikqiak.com/validate: "false"` annotation, we skipped validation.)
`deployment/sleep-with-labels.yaml` -> Correct, valid (We should accept this creation request.)
```
### 7. A way of extend the operation event and function
In this demo, we only consider the Pod create request by specifying _operations_ at the ValidatingWebhookConfiguration's [matching request rules](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/#matching-requests-rules) section in the [deployment/validatingwebhook.yaml](https://github.com/developer-guy/admission-webhook-example-with-openfaas/blob/master/deployment/validatingwebhook.yaml) file.
If we want to extend the operations, we can add a new [operation](https://github.com/kubernetes/kubernetes/blob/release-1.19/pkg/apis/admission/types.go#L158) for the Pods like _DELETE_, _UPDATE_, _CONNECT_ etc. By specifying a new operation, now apiserver being started to send a new event for this operation additional to create request.
Now we can specify more than one serverless function for the operation types by checking request operation type. For [example](https://github.com/developer-guy/admission-webhook-example-with-openfaas/blob/master/functions/requiredlabel/handler.go#L109):
```go
switch req.Kind.Kind {
case "Pod":
switch req.Operation {
case v1beta1.Create:
// do something for create operation
case v1beta1.Delete:
// do something for delete operation
}
}
```
Also you can specify function name and namespace that you want to use while deploying the webhook server using these environment variables:
```yaml
env:
- name: FUNCTION_NAME
value: requiredlabel
- name: FUNCTION_NAMESPACE
value: openfaas-fn
```
### Taking it further
* Mutating webhooks
You could take this example and convert it from validating webhooks to mutating webhooks. This is useful when a user wants to upgrade or modify objects that are created, such as adding which user created them, or adding a compulsory memory limit.
* Adding more functions
In the example I used a single function, however, you could register more than one function, so that you can then have a function for validating memory limits, and a separate one for checking that a minimum set of labels are present
### Join the community
Do you have questions, comments or suggestions? Tweet to [@openfaas](https://twitter.com/openfaas).
> Want to support our work? You can become a sponsor as an individual or a business via GitHub Sponsors with tiers to suit every budget and benefits for you in return. [Check out our GitHub Sponsors Page](https://github.com/sponsors/openfaas/)
### Acknowledgements
* Special Thanks to [Alex Ellis](https://twitter.com/alexellisuk) for all guidance and for merging changes into OpenFaaS to better support this workflow.
* Special Thanks to [Furkan Türkal](https://twitter.com/furkanturkaI) for all the support.
### References
* [https://medium.com/ibm-cloud/diving-into-kubernetes-mutatingadmissionwebhook-6ef3c5695f74](https://medium.com/ibm-cloud/diving-into-kubernetes-mutatingadmissionwebhook-6ef3c5695f74)
* [https://blog.alexellis.io/get-started-with-openfaas-and-kind/](https://blog.alexellis.io/get-started-with-openfaas-and-kind/)
* [https://github.com/morvencao/kube-mutating-webhook-tutorial](https://github.com/morvencao/kube-mutating-webhook-tutorial)
* [https://github.com/developer-guy/admission-webhook-example-with-openfaas](https://github.com/developer-guy/admission-webhook-example-with-openfaas)
| 45.835249 | 1,170 | 0.774304 | eng_Latn | 0.9502 |
6ad4ab36fa4e9811546c12b967ad5b933c994713 | 14,274 | md | Markdown | gan/README.md | sarthakpati/Red-GAN | 45cee4ca73fb2c0665b76e3df049184511d18bc6 | [
"MIT"
] | 20 | 2020-04-24T08:52:37.000Z | 2022-01-23T15:05:50.000Z | gan/README.md | sarthakpati/Red-GAN | 45cee4ca73fb2c0665b76e3df049184511d18bc6 | [
"MIT"
] | null | null | null | gan/README.md | sarthakpati/Red-GAN | 45cee4ca73fb2c0665b76e3df049184511d18bc6 | [
"MIT"
] | 4 | 2020-05-11T20:18:23.000Z | 2021-03-18T19:06:14.000Z | [](https://raw.githubusercontent.com/nvlabs/SPADE/master/LICENSE.md)
# Red-GAN
The implementation is in large adopted from SPADE-GAN (https://github.com/NVlabs/SPADE)
### Installation
The following requirements should be installed for training the GAN code:
```torch>=1.0.0
torchvision
dominate>=2.3.1
dill
scikit-image
```
### Help
#### Train
The train.py script is used for training. Executing the help statement `python3 train.py -h` shows available training options:
````
usage: train.py [-h] [--gpu_ids GPU_IDS]
[--checkpoints_dir CHECKPOINTS_DIR] [--model MODEL]
[--norm_G NORM_G] [--norm_D NORM_D] [--norm_E NORM_E] [--batchSize BATCHSIZE]
[--preprocess_mode {resize_and_crop,crop,scale_width,scale_width_and_crop,scale_shortside,scale_shortside_and_crop,fixed,none}]
[--load_size LOAD_SIZE] [--crop_size CROP_SIZE]
[--aspect_ratio ASPECT_RATIO] [--label_nc LABEL_NC]
[--contain_dontcare_label] [--dataroot DATAROOT]
[--dataset_mode DATASET_MODE] [--serial_batches] [--no_flip]
[--nThreads NTHREADS] [--max_dataset_size MAX_DATASET_SIZE]
[--load_from_opt_file] [--cache_filelist_write]
[--cache_filelist_read] [--display_winsize DISPLAY_WINSIZE]
[--netG NETG] [--ngf NGF] [--init_type INIT_TYPE]
[--init_variance INIT_VARIANCE] [--z_dim Z_DIM] --segmentator
SEGMENTATOR [--instance] [--nef NEF] [--use_vae]
[--display_freq DISPLAY_FREQ] [--print_freq PRINT_FREQ]
[--save_latest_freq SAVE_LATEST_FREQ]
[--save_epoch_freq SAVE_EPOCH_FREQ] [--no_html] [--debug]
[--tf_log] [--continue_train] [--which_epoch WHICH_EPOCH]
[--niter NITER] [--niter_decay NITER_DECAY]
[--optimizer OPTIMIZER] [--beta1 BETA1] [--beta2 BETA2]
[--lr LR] [--D_steps_per_G D_STEPS_PER_G] [--ndf NDF]
[--lambda_feat LAMBDA_FEAT] [--lambda_vgg LAMBDA_VGG]
[--no_ganFeat_loss] [--vgg_loss] [--gan_mode GAN_MODE]
[--netD NETD] [--no_TTUR] [--lambda_kld LAMBDA_KLD]
optional arguments:
-h, --help show this help message and exit
--name NAME name of the experiment. It decides where to store
samples and models (default: label2coco)
--gpu_ids GPU_IDS gpu ids: e.g. 0 0,1,2, 0,2. use -1 for CPU (default:
0)
--checkpoints_dir CHECKPOINTS_DIR
models are saved here (default: ./checkpoints)
--model MODEL which model to use (default: pix2pix)
--norm_G NORM_G instance normalization or batch normalization
(default: spectralinstance)
--norm_D NORM_D instance normalization or batch normalization
(default: spectralinstance)
--norm_E NORM_E instance normalization or batch normalization
(default: spectralinstance)
--phase PHASE train, val, test, etc (default: train)
--batchSize BATCHSIZE
input batch size (default: 1)
--preprocess_mode {resize_and_crop,crop,scale_width,scale_width_and_crop,scale_shortside,scale_shortside_and_crop,fixed,none}
scaling and cropping of images at load time. (default:
none)
--load_size LOAD_SIZE
Scale images to this size. The final image will be
cropped to --crop_size. (default: 1024)
--crop_size CROP_SIZE
Crop to the width of crop_size (after initially
scaling the images to load_size.) (default: 512)
--aspect_ratio ASPECT_RATIO
The ratio width/height. The final height of the load
image will be crop_size/aspect_ratio (default: 1.0)
--label_nc LABEL_NC # of input label classes without unknown class. If you
have unknown class as class label, specify
--contain_dopntcare_label. (default: 182)
--contain_dontcare_label
if the label map contains dontcare label
(dontcare=255) (default: False)
--dataroot DATAROOT
--dataset_mode DATASET_MODE
--serial_batches if true, takes images in order to make batches,
otherwise takes them randomly (default: False)
--no_flip if specified, do not flip the images for data
argumentation (default: False)
--nThreads NTHREADS # threads for loading data (default: 0)
--max_dataset_size MAX_DATASET_SIZE
Maximum number of samples allowed per dataset. If the
dataset directory contains more than max_dataset_size,
only a subset is loaded. (default:
9223372036854775807)
--load_from_opt_file load the options from checkpoints and use that as
default (default: False)
--cache_filelist_write
saves the current filelist into a text file, so that
it loads faster (default: False)
--cache_filelist_read
reads from the file list cache (default: False)
--display_winsize DISPLAY_WINSIZE
display window size (default: 400)
--netG NETG selects model to use for netG (pix2pixhd | spade)
(default: spade)
--ngf NGF # of gen filters in first conv layer (default: 64)
--init_type INIT_TYPE
network initialization
[normal|xavier|kaiming|orthogonal] (default: xavier)
--init_variance INIT_VARIANCE
variance of the initialization distribution (default:
0.02)
--z_dim Z_DIM dimension of the latent z vector (default: 256)
--segmentator SEGMENTATOR
path to the segmentator network (default: None)
--instance if specified, add instance map as input (default:
False)
--nef NEF # of encoder filters in the first conv layer (default:
16)
--use_vae enable training with an image encoder. (default:
False)
--display_freq DISPLAY_FREQ
frequency of showing training results on screen
(default: 100)
--print_freq PRINT_FREQ
frequency of showing training results on console
(default: 100)
--save_latest_freq SAVE_LATEST_FREQ
frequency of saving the latest results (default: 5000)
--save_epoch_freq SAVE_EPOCH_FREQ
frequency of saving checkpoints at the end of epochs
(default: 10)
--no_html do not save intermediate training results to
[opt.checkpoints_dir]/[opt.name]/web/ (default: False)
--debug only do one epoch and displays at each iteration
(default: False)
--tf_log if specified, use tensorboard logging. Requires
tensorflow installed (default: False)
--continue_train continue training: load the latest model (default:
False)
--which_epoch WHICH_EPOCH
which epoch to load? set to latest to use latest
cached model (default: latest)
--niter NITER # of iter at starting learning rate. This is NOT the
total #epochs. Totla #epochs is niter + niter_decay
(default: 50)
--niter_decay NITER_DECAY
# of iter to linearly decay learning rate to zero
(default: 0)
--optimizer OPTIMIZER
--beta1 BETA1 momentum term of adam (default: 0.5)
--beta2 BETA2 momentum term of adam (default: 0.999)
--lr LR initial learning rate for adam (default: 0.0002)
--D_steps_per_G D_STEPS_PER_G
number of discriminator iterations per generator
iterations. (default: 1)
--ndf NDF # of discrim filters in first conv layer (default: 64)
--lambda_feat LAMBDA_FEAT
weight for feature matching loss (default: 10.0)
--lambda_vgg LAMBDA_VGG
weight for vgg loss (default: 10.0)
--no_ganFeat_loss if specified, do *not* use discriminator feature
matching loss (default: False)
--vgg_loss if specified, use VGG feature matching loss (default:
False)
--gan_mode GAN_MODE (ls|original|hinge) (default: hinge)
--netD NETD (n_layers|multiscale|image) (default: multiscale)
--no_TTUR Use TTUR training scheme (default: False)
--lambda_kld LAMBDA_KLD
````
#### Example command
````bash
python3 train.py --name isic_training --dataset_mode isic --label_dir ./datasets/isic/fold_2/train/segmentation_masks --image_dir ./datasets/isic/fold_2/train/images --dataroot ./datasets/isic/fold_2/train --batchSize 8 --niter 100 --no_pairing_check --gpu_ids=0 --segmentator ./checkpoints/isic_fold_2/model_epochs100_percent100_isic_256
````
test.py script is used for evaluation. Executing the statement `python3 test.py -h`, outputs:
````
usage: test.py [-h] [--name NAME] [--gpu_ids GPU_IDS]
[--checkpoints_dir CHECKPOINTS_DIR] [--model MODEL]
[--norm_G NORM_G] [--norm_D NORM_D] [--norm_E NORM_E]
[--phase PHASE] [--batchSize BATCHSIZE]
[--preprocess_mode {resize_and_crop,crop,scale_width,scale_width_and_crop,scale_shortside,scale_shortside_and_crop,fixed,none}]
[--load_size LOAD_SIZE] [--crop_size CROP_SIZE]
[--aspect_ratio ASPECT_RATIO] [--label_nc LABEL_NC]
[--contain_dontcare_label] [--dataroot DATAROOT]
[--dataset_mode DATASET_MODE] [--serial_batches] [--no_flip]
[--nThreads NTHREADS] [--max_dataset_size MAX_DATASET_SIZE]
[--load_from_opt_file] [--cache_filelist_write]
[--cache_filelist_read] [--display_winsize DISPLAY_WINSIZE]
[--netG NETG] [--ngf NGF] [--init_type INIT_TYPE]
[--init_variance INIT_VARIANCE] [--z_dim Z_DIM] --segmentator
SEGMENTATOR [--instance] [--nef NEF] [--use_vae]
[--results_dir RESULTS_DIR] [--which_epoch WHICH_EPOCH]
[--how_many HOW_MANY] [--condition_class CONDITION_CLASS]
optional arguments:
-h, --help show this help message and exit
--name NAME name of the experiment. It decides where to store
samples and models (default: label2coco)
--gpu_ids GPU_IDS gpu ids: e.g. 0 0,1,2, 0,2. use -1 for CPU (default:
0)
--checkpoints_dir CHECKPOINTS_DIR
models are saved here (default: ./checkpoints)
--model MODEL which model to use (default: pix2pix)
--norm_G NORM_G instance normalization or batch normalization
(default: spectralinstance)
--norm_D NORM_D instance normalization or batch normalization
(default: spectralinstance)
--norm_E NORM_E instance normalization or batch normalization
(default: spectralinstance)
--phase PHASE train, val, test, etc (default: train)
--batchSize BATCHSIZE
input batch size (default: 1)
--preprocess_mode {resize_and_crop,crop,scale_width,scale_width_and_crop,scale_shortside,scale_shortside_and_crop,fixed,none}
scaling and cropping of images at load time. (default:
scale_width_and_crop)
--load_size LOAD_SIZE
Scale images to this size. The final image will be
cropped to --crop_size. (default: 256)
--crop_size CROP_SIZE
Crop to the width of crop_size (after initially
scaling the images to load_size.) (default: 256)
--aspect_ratio ASPECT_RATIO
The ratio width/height. The final height of the load
image will be crop_size/aspect_ratio (default: 1.0)
--label_nc LABEL_NC # of input label classes without unknown class. If you
have unknown class as class label, specify
--contain_dopntcare_label. (default: 182)
````
#### Example command
```bash
python3 test.py --name BRATS_training --dataset_mode brats --label_dir ./datasets/BRATS_dataset_splices/fold_4/train_label_full --image_dir_t1ce ./datasets/BRATS_dataset_splices/fold_4/train_t1ce_img_full --image_dir_t1 ./datasets/BRATS_dataset_splices/fold_4/train_t1_img_full --image_dir_t2 ./datasets/BRATS_dataset_splices/fold_4/train_t2_img_full --image_dir_flair ./datasets/BRATS_dataset_splices/fold_4/train_flair_img_full --dataroot ./datasets/BRATS_dataset_splices/fold_4 --batchSize 16 --no_pairing_check --gpu_ids=0 --segmentator ./checkpoints/fold_4/model_epochs100_percent0_pure_vis --results_dir /home/qasima/venv_spade/SPADE/results/BRATS_training_scanner_4/fold_4/ --condition_class 0
```
### Additional Note:
If the parameter `--segmentator` is not set (by specifying the segmentor path), then the third player is not included in the architecture, which results in the vanilla [SPADE](https://github.com/NVlabs/SPADE/blob/master/README.md) architecture.
| 59.475 | 700 | 0.598431 | eng_Latn | 0.691767 |
6ad4cc2d11362b852fca244fbd1504aed15f3538 | 293 | md | Markdown | _pages/navigation/database.md | Atercatus/Atercatus.github.io | 5889b1d00aadd999476e1ec9e2d05ebfaaf5a9cb | [
"MIT"
] | null | null | null | _pages/navigation/database.md | Atercatus/Atercatus.github.io | 5889b1d00aadd999476e1ec9e2d05ebfaaf5a9cb | [
"MIT"
] | 9 | 2020-01-04T17:07:34.000Z | 2020-01-06T08:57:47.000Z | _pages/navigation/database.md | Atercatus/Atercatus.github.io | 5889b1d00aadd999476e1ec9e2d05ebfaaf5a9cb | [
"MIT"
] | 2 | 2020-02-16T16:24:05.000Z | 2021-02-17T06:31:58.000Z | ---
title: Database
layout: collection
permalink: /database/
collection: database
author_profile: true
entries_layout: grid
classes: wide
sort_by: date # date (default) title
sort_order: forward # forward (default), reverse
header:
# overlay_image: /assets/images/boost-tv/boostcamp.png
---
| 20.928571 | 56 | 0.771331 | eng_Latn | 0.391246 |
6ad5e2599d1b983ecc06df448f068ed53129d2cf | 23 | md | Markdown | README.md | mmarcec007/mark-marcec.github.io | 76fc4b08f84258d3dff438519d3f60bdeceedb45 | [
"MIT"
] | null | null | null | README.md | mmarcec007/mark-marcec.github.io | 76fc4b08f84258d3dff438519d3f60bdeceedb45 | [
"MIT"
] | null | null | null | README.md | mmarcec007/mark-marcec.github.io | 76fc4b08f84258d3dff438519d3f60bdeceedb45 | [
"MIT"
] | null | null | null | # mark-marcec.github.io | 23 | 23 | 0.782609 | vie_Latn | 0.173534 |
6ad690af5c81d938389d42fc19f1bdd20e9c60c2 | 1,962 | md | Markdown | _drafts/2015-05-xx-usb-hub-check.md | kazuhito-m/kazuhito-m.github.io | 3df8137ef0d630985ea3c7731829e1f311593973 | [
"MIT"
] | null | null | null | _drafts/2015-05-xx-usb-hub-check.md | kazuhito-m/kazuhito-m.github.io | 3df8137ef0d630985ea3c7731829e1f311593973 | [
"MIT"
] | null | null | null | _drafts/2015-05-xx-usb-hub-check.md | kazuhito-m/kazuhito-m.github.io | 3df8137ef0d630985ea3c7731829e1f311593973 | [
"MIT"
] | 1 | 2018-05-13T11:58:50.000Z | 2018-05-13T11:58:50.000Z | ---
published: false
layout: post
title: RaspberryPIで無線LAN設定
category: tech
tags: [raspberrypi,usb,linux]
---
ラズパイを「一台一仕事のサーバ」として運用していきたい三浦としては…「何処に置いても動作する」にしておきたいわけです。
ということで、RaspberryPIに無線LANを設定します。
## 使う道具
+ RaspberryPI(マーク1)
+ USB無線LANユニット - WLI-UC-GNM
## 参考にしたサイト
+ http://denshikousaku.net/raspberry-pi-wifi-lan-usb
…上のLANユニット…「力いっぱい地雷認定」されてんじゃねーかｗ
## やったこと
### ラズパイにログインして、認識してるか確認。
```bash
pi@raspberrypi ~ $ lsusb | grep -i LAN
Bus 001 Device 004: ID 0411:01a2 BUFFALO INC. (formerly MelCo., Inc.) WLI-UC-GNM Wireless LAN Adapter [Ralink RT8070]
```
### 設定を吐き出させる。
```
pi@raspberrypi ~ $ wpa_passphrase Your_SSID Your_Passphrase
network={
ssid="Your_SSID"
#psk="Your_Passphrase"
psk=なんかなんか
}
pi@raspberrypi ~
```
### /etc の設定ファイルに付け加える。
```bash
pi@raspberrypi ~ $ sudo vim /etc/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
# ここから以下が追加
network={
ssid="Your_SSID"
#psk="Your_Passphrase"
psk=なんかなんか
}
```
参考にしたサイトには、上記のpsk=の下に「WPA-PSKの設定」があったのだが…追加すると繋がらなかったので、ただssidとpskだけにした。
※恐らく「セキュリティ的にガバガバ」なんだろうと思うけど、本気でやりたかったら以下サイトをしらべながら設定すべし。(TODO)
[http://www.youchikurin.com/blog/2007/06/linuxlan_1.html](http://www.youchikurin.com/blog/2007/06/linuxlan_1.html)
### ネットワークカードの設定を追加。
```
pi@raspberrypi ~ $ sudo cp -a /etc/network/interfaces /etc/network/interfaces.org
pi@raspberrypi ~ $ sudo vi /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
allow-hotplug eth0
iface eth0 inet manual
auto wlan0
allow-hotplug wlan0
# 以下、コメントアウト＆追加
# iface wlan0 inet manual
iface wlan0 inet static
address 192.168.1.32
netmask 255.255.255.0
gateway 192.168.1.1
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
```
### ネットワークの再起動
```bash
pi@raspberrypi ~ $ sudo service networking restart
```
あとは、無線LAN側のIPにLAN内からsshして、繋がったら有線を抜くべし。
## やってみて
+ USBの無線LANユニットが(記事の地雷指定どおり)目玉焼き焼けそうな発熱
+ セキュリティ設定が甘い(と思われる)
ので、ココらへんをTODOにして、もうちょい改善していくつもりです。 | 18.509434 | 117 | 0.752803 | yue_Hant | 0.445822 |
6ad6e75e289da514d4f855d77dadc5a0ffc96102 | 4,867 | md | Markdown | Skype/SfbServer/manage/health-and-monitoring/conference-summary-subreport.md | isabella232/OfficeDocs-SkypeForBusiness.de-DE | 36002f4e7303a572fe24c40db59e1ae6c48207d0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | Skype/SfbServer/manage/health-and-monitoring/conference-summary-subreport.md | isabella232/OfficeDocs-SkypeForBusiness.de-DE | 36002f4e7303a572fe24c40db59e1ae6c48207d0 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-10-09T18:09:59.000Z | 2021-10-09T18:09:59.000Z | Skype/SfbServer/manage/health-and-monitoring/conference-summary-subreport.md | isabella232/OfficeDocs-SkypeForBusiness.de-DE | 36002f4e7303a572fe24c40db59e1ae6c48207d0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Zusammenfassender Konferenzunterbericht in Skype for Business Server
ms.reviewer: ''
ms.author: v-cichur
author: cichur
manager: serdars
audience: ITPro
ms.topic: article
ms.prod: skype-for-business-itpro
f1.keywords:
- NOCSH
ms.localizationpriority: medium
ms.assetid: 2fc1d2bf-34f5-4093-a6e2-250ec1f1b004
description: 'Zusammenfassung: Erfahren Sie mehr über den zusammenfassenden Konferenzunterbericht in Skype for Business Server.'
ms.openlocfilehash: 66ca2c80bb20026540e74c0ffd28c32be7f7343a
ms.sourcegitcommit: 556fffc96729150efcc04cd5d6069c402012421e
ms.translationtype: MT
ms.contentlocale: de-DE
ms.lasthandoff: 08/26/2021
ms.locfileid: "58630599"
---
# <a name="conference-summary-subreport-in-skype-for-business-server"></a>Zusammenfassender Konferenzunterbericht in Skype for Business Server
**Zusammenfassung:** Erfahren Sie mehr über den zusammenfassenden Konferenzunterbericht in Skype for Business Server.
Der zusammenfassende Konferenzunterbericht stellt eine Gesamtübersicht zu gescheiterten Konferenzsitzungen bereit, bei denen Fehler aufgetreten sind. Diese gescheiterten Sitzungen sind weiter nach Sitzungstyp unterteilt: Konferenzzustandsobjekt-Sitzungen und MCU-Sitzungen.
## <a name="filters"></a>Filter
Mithilfe von Filtern können Sie eine gezieltere Datenauswahl erreichen oder die zurückgegebenen Daten auf unterschiedliche Weise anzeigen. In der folgenden Tabelle werden die Filter aufgelistet, die Sie im zusammenfassenden Konferenzunterbericht verwenden können.
**Filter im zusammenfassenden Konferenzunterbericht**
|**Name**|**Beschreibung**|
|:-----|:-----|
|**From** <br/> |Anfangsdatum und -uhrzeit für den Zeitraum. Wenn die Daten nach Stunden angezeigt werden sollen, geben Sie Anfangsdatum und -uhrzeit wie folgt ein: <br/> 7.07.2015 13:00 Uhr <br/> Wenn Sie keinen Anfangszeitpunkt eingeben, beginnt der Bericht automatisch am angegebenen Tag um 12:00 Uhr. Zum Anzeigen der Daten nach Tag geben Sie nur das Datum ein: <br/> 7/7/2015 <br/> Sollen die Daten nach Woche oder Monat angezeigt werden, geben Sie irgendein Datum ein, das in die anzuzeigende Woche oder den anzuzeigenden Monat fällt (Sie müssen nicht den ersten Tag der Woche oder des Monats eingeben): <br/> 7/3/2015 <br/> Eine Woche läuft immer von Sonntag bis einschließlich Samstag. <br/> |
|**Ziel** <br/> |Enddatum und -uhrzeit für den Zeitraum. Wenn die Daten nach Stunden angezeigt werden sollen, geben Sie Enddatum und -uhrzeit wie folgt ein: <br/> 7.07.2015 13:00 Uhr <br/> Wenn Sie keinen Endzeitpunkt eingeben, endet der Bericht automatisch am angegebenen Tag um 12:00 Uhr. Zum Anzeigen der Daten nach Tag geben Sie nur das Datum ein: <br/> 7/7/2015 <br/> Sollen die Daten nach Woche oder Monat angezeigt werden, geben Sie irgendein Datum ein, das in die anzuzeigende Woche oder den anzuzeigenden Monat fällt (Sie müssen nicht den ersten Tag der Woche oder des Monats eingeben): <br/> 7/3/2015 <br/> Eine Woche läuft immer von Sonntag bis einschließlich Samstag. <br/> |
|**Pool** <br/> |Vollqualifizierter Domänenname (FQDN) des Registrierungsstellenpools oder Edgeservers. Sie können einen einzelnen Pool auswählen, oder auf **[Alle]** klicken, um die Daten für alle Pools anzuzeigen. Diese Dropdownliste wird basierend auf den Datensätzen in der Datenbank automatisch ausgefüllt.<br/> |
## <a name="metrics"></a>Metriken
In der folgenden Tabelle sind die Metriken aufgelistet, die im zusammenfassenden Konferenzunterbericht angegeben werden.
**Metriken im zusammenfassenden Konferenzunterbericht**
|**Name**|**Kann nach dieser Metrik sortiert werden?**|**Beschreibung**|
|:-----|:-----|:-----|
|**Konferenzen insgesamt** <br/> |Nein <br/> |Gesamtzahl der Konferenzen, die durchgeführt wurden. <br/> |
|**Konferenzsitzungen insgesamt** <br/> |Nein <br/> |Gesamtzahl der Konferenzsitzungen. Eine einzelne Konferenz kann mehrere Sitzungen haben. Beispielsweise kann eine Konferenz sowohl eine Konferenzzustandsobjekt-Sitzung als auch eine MCU-Sitzung umfassen. <br/> |
|**Sitzungsfehlerrate insgesamt** <br/> |Nein <br/> |Prozentsatz aller gescheiterten Konferenzen. <br/> |
|**Konferenzzustandsobjekt-Sitzungen** <br/> |Nein <br/> |Gesamtanzahl der Konferenzzustandsobjekt-Sitzungen. <br/> |
|**Fehlerrate für Konferenzzustandsobjekt** <br/> |Nein <br/> |Prozentsatz der gescheiterten Konferenzzustandsobjekt-Sitzungen. <br/> |
|MCU-Sitzungen <br/> |Nein <br/> |Gesamtanzahl der MCU-Sitzungen. <br/> |
|**MCU-Fehlerrate** <br/> |Nein <br/> |Prozentsatz der gescheiterten MCU-Sitzungen. <br/> |
|**MCU-Sitzungen nach Modalität** <br/> |Nein <br/> |Gesamtanzahl der MCU-Sitzungen, gruppiert nach Modalität (z. B. Chatkonferenz). <br/> |
|**Fehlerrate nach Modalität** <br/> |Nein <br/> |Prozentsatz der gescheiterten MCU-Sitzungen, gruppiert nach Modalität (z. B. Chatkonferenz). <br/> |
| 82.491525 | 708 | 0.770495 | deu_Latn | 0.994693 |
6ad74138043f58f1a9c5c324ad2ecb85cc7a9a91 | 1,845 | markdown | Markdown | _posts/2017/2017-11-19-hello-blog.markdown | raw-coder/raw-coder.github.io | a3d67e58fcdd26c490dacf2c76501ab4d2d5ba48 | [
"MIT"
] | 1 | 2021-06-10T14:26:52.000Z | 2021-06-10T14:26:52.000Z | _posts/2017/2017-11-19-hello-blog.markdown | raw-coder/raw-coder.github.io | a3d67e58fcdd26c490dacf2c76501ab4d2d5ba48 | [
"MIT"
] | null | null | null | _posts/2017/2017-11-19-hello-blog.markdown | raw-coder/raw-coder.github.io | a3d67e58fcdd26c490dacf2c76501ab4d2d5ba48 | [
"MIT"
] | null | null | null | ---
layout: post
title: "블로그를 시작하다"
summary: "블로그를 시작하다"
author: raw-coder
date: '2017-11-19 00:00:00 +0900'
category: life
thumbnail: /assets/img/blog.jpg
keywords: life
permalink: /blog/hello-blog/
usemathjax: false
---
## 블로그를 시작하며
> 나는 좀더 많은 사람들의 삶에 도움을 주는 사람이 되고 싶었다. 그래서 개발자가 되기로 결심했다.
개발자로서 커리어를 시작하기 전, 나는 어느 대기업 부설 생산기술연구소의 연구원이었다.
거대한 공장의 생산관리 혹은 일정관리와 관련된 몇 가지 시스템의 새로운 기능을 제안하고, 만들고, 개선하는 일을 했다. 연구 제안을 하고, 하청을 주고 프로토타입 시스템을 만들어보고(감독하고), 좋은 효과가 있었음을 논문을 쓰거나 자료를 작성하여 증명하는 일을 하는 사람들 중에 하나였다.
좋은 회사였고 의미있는 일이었지만, 난 솔직히 좀 재미없었다. 내가 하고 있는 일은 좁은 시각으로 보자면, 사무실에 앉아서 생산계획을 수립하고, 노동자들에게 업무지시를 하는 관리자 몇 명을 위한 일이었다. 난 좀더 많은 사람들의 삶에 도움을 줄 수 있는 일이 하고 싶어졌다.
그래서 30살이 넘어 퇴사를 했다.
> 세상이 학교 다닐때처럼 녹록하지는 않았지만, 그래도 개발자는 될 수 있었다. 운이 좋았다.
대책도 없이 잘 다니던 좋은 회사를 그만두고 고생도 많이 했다.
몇 달 쉬면서 여행도 다니고, 어학공부도 하면서 가고 싶었던 회사에 입사원서를 몇 군데 넣으면 이직이 쉽게 될 지 알았지만, 그렇지 않았다.
참 오래동안 취뽀와 영어학원을 전전한 끝에 간신히 개발자는 될 수 있었다.
사실 운이 좋았다. 개발자가 되려는 컴퓨터 전공자들은 다 기피한다는 악성 대형 SI 프로젝트들이 수많은 신입 개발자들을 블랙홀처럼 빨아들이고 있었다. 내가 입사한 그 회사는 그해 신입 개발자로 300명 이상을 채용했다. 그중에 나도 하나였다.
> 첫 프로젝트는 엉망이었지만, 나는 그저 감사하기만 했다. 그리고 열심히 했다.
개발자로서 나의 커리어의 첫 줄을 장식하게 된 프로젝트는 국가의 세금과 관련된 시스템을 대대적으로 새롭게(!) 만드는 초대형 SI 프로젝트였다.
공공 SI 프로젝트에 처음 투입된 초보 개발자는 문서로 정의된 비즈니스 로직(주로 단순 CRUD)을 구현하고 물량을 뽑아내는 역할을 하게 되는데, 나는 그중 하나였다.
사용할 수 있는 기술은 이미 정해져있었고, 수많은 가이드 문서가 코드의 자유를 옥죄어 오는 환경이었다. 닭장 같은 사무실에 앉아 하루종일 비슷한 화면을 찍어내야하는 일이었지만, 나는 초보 개발자였다. 모든 것이 새로웠고 하루하루 배우고 새로운 경험을 하는 일이 반복되었다. 물론 두, 세달 정도 지나니 반복작업, 노가다가 시작되긴 했었다.
그럼에도 불구하고, 나 정도의 일천한 경험과 실력을 가진 초보 개발자가 개발자로서 커리어를 시작할 수 있음에 감사하면서 나는 3년 가까운 프로젝트 투입 기간동안 정말 열심히 개발(컨트롤 + C, V)했다.
열심히 배워서 다음 프로젝트에서는 더 잘하고 싶었다. 더 좋은 코드를 작성하고 싶었다.
> 블로그를 시작하자.
첫 프로젝트를 마치고, 본사에 복귀하여 4개 정도의 프로젝트를 경험하고, 이제 경력 4년을 가진 개발자가 되었다.
연말이 되어 나 자신을 되돌아 보게 되면서 생각했다. 슬프지만 난 여전히 초보 개발자를 벗어나지 못했다.
생각없이 열심히만 하지 말자. 야매는 싫다. 정말 잘하고 싶다고 생각했다.
그리고 결심했다!
조금씩 나아지는 모습을 만들자. 그래서 블로그를 시작하게 된다.
| 31.271186 | 189 | 0.704065 | kor_Hang | 1.00001 |
6ad75133cd097e2160bb320abd4aa7dbe5d1e0f2 | 347 | md | Markdown | docs/CONTRIBUTING.md | cwerm/npmify | 86472cfd830f004ed8c04b77b577633ad473e02a | [
"MIT"
] | 1 | 2019-07-16T14:24:08.000Z | 2019-07-16T14:24:08.000Z | docs/CONTRIBUTING.md | cwerm/npmify | 86472cfd830f004ed8c04b77b577633ad473e02a | [
"MIT"
] | 6 | 2019-07-16T20:24:32.000Z | 2019-07-23T23:34:47.000Z | docs/CONTRIBUTING.md | cwerm/npmify | 86472cfd830f004ed8c04b77b577633ad473e02a | [
"MIT"
] | 1 | 2019-07-21T22:54:40.000Z | 2019-07-21T22:54:40.000Z | # Contributing to NPMify
Keep in mind that this is a living document, and in the _very_ early stages. The goal is to keep the process as easy and open as possible.
- To contribute code, fork this repo and make your changes. When you're done implementing your feature/bug fix, simply open a PR.
- To open an issue, just open an issue. Easy peasy.
| 57.833333 | 138 | 0.766571 | eng_Latn | 0.999524 |
6ad7a80ba88badf096515e03e29729ca06cfbd17 | 4,362 | md | Markdown | articles/supply-chain/procurement/procurement-sourcing-workflows.md | MicrosoftDocs/Dynamics-365-Operations.th-th | 027178e956d20941008e2a21ceb7eab33a166bb1 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-04-20T21:13:46.000Z | 2021-04-20T21:13:46.000Z | articles/supply-chain/procurement/procurement-sourcing-workflows.md | MicrosoftDocs/Dynamics-365-Operations.th-th | 027178e956d20941008e2a21ceb7eab33a166bb1 | [
"CC-BY-4.0",
"MIT"
] | 7 | 2017-12-13T13:15:10.000Z | 2019-04-30T11:45:57.000Z | articles/supply-chain/procurement/procurement-sourcing-workflows.md | MicrosoftDocs/Dynamics-365-Operations.th-th | 027178e956d20941008e2a21ceb7eab33a166bb1 | [
"CC-BY-4.0",
"MIT"
] | 11 | 2018-06-19T08:33:55.000Z | 2021-10-13T09:20:34.000Z | ---
title: ลำดับงานการจัดซื้อและการจัดหา
description: องค์กรบางองค์กรต้องการให้ใบขอซื้อและใบสั่งซื้อ ได้รับการอนุมัติโดยผู้ใช้อื่นที่ไม่ใช่บุคคลที่ป้อนธุรกรรม เพื่อตั้งค่ากระบวนการอนุมัติ คุณสามารถสร้างลำดับงานได้
author: Henrikan
ms.date: 12/01/2020
ms.topic: article
ms.prod: ''
ms.technology: ''
ms.search.form: WorkflowTableListPageRnr
audience: Application User
ms.reviewer: kamaybac
ms.custom: 2074
ms.assetid: e54a1d59-b9fb-421b-821d-01f32878aa9b
ms.search.region: Global
ms.author: henrikan
ms.search.validFrom: 2016-02-28
ms.dyn365.ops.version: AX 7.0.0
ms.openlocfilehash: a819093d9ee6f999e637281e54905968fe361566
ms.sourcegitcommit: 3b87f042a7e97f72b5aa73bef186c5426b937fec
ms.translationtype: HT
ms.contentlocale: th-TH
ms.lasthandoff: 09/29/2021
ms.locfileid: "7575547"
---
# <a name="procurement-and-sourcing-workflows"></a>ลำดับงานการจัดซื้อและการจัดหา
[!include [banner](../includes/banner.md)]
องค์กรบางองค์กรต้องการให้ใบขอซื้อและใบสั่งซื้อ ได้รับการอนุมัติโดยผู้ใช้อื่นที่ไม่ใช่บุคคลที่ป้อนธุรกรรม เพื่อตั้งค่ากระบวนการอนุมัติ คุณสามารถสร้างลำดับงานได้
ลำดับงานแสดงถึงกระบวนการทางธุรกิจ โดยจะกำหนดวิธีการที่เอกสารหมุนเวียนในระบบ และระบุว่าใครต้องทำงานให้เสร็จสมบูรณ์หรืออนุมัติเอกสาร มีประโยชน์มากมายสำหรับการใช้ระบบลำดับงานในองค์กรของคุณดังต่อไปนี้
- **กระบวนการที่สอดคล้องกัน** — คุณสามารถกำหนดกระบวนการอนุมัติสำหรับเอกสารเฉพาะ เช่น ใบขอซื้อและรายงานค่าใช้จ่าย การใช้ระบบลำดับงานช่วยให้แน่ใจว่าเอกสารจะได้รับการประมวลผลและอนุมัติในลักษณะที่สอดคล้องกันและมีประสิทธิภาพ
- **การติดตามกระบวนการ** — คุณสามารถติดตามสถานะ ประวัติ และเมตริกประสิทธิภาพของอินสแตนซ์ลำดับงานเฉพาะ ซึ่งจะช่วยคุณกำหนดว่าควรทำการเปลี่ยนแปลงกับลำดับงานเพื่อปรับปรุงประสิทธิภาพหรือไม่
- **รายการงานส่วนกลาง**— ผู้ใช้สามารถดูรายการงานส่วนกลางเพื่อดูงานในลำดับงานและการอนุมัติที่กำหนดให้ลำดับงานทั้งหมดที่จะเข้าร่วมในระหว่างนั้น ซึ่งพร้อมใช้งานในหน้ารายการงาน
## <a name="the-types-of-workflows-that-you-can-create"></a>ชนิดของลำดับงานที่คุณสามารถสร้างได้
ชนิดลำดับงานต่อไปนี้จะพร้อมใช้งานสำหรับการจัดซื้อและการจัดหา
| ชนิดข้อมูล | ใช้ชนิดนี้กับ |
|---|---|
| การตรวจทานใบขอซื้อ | สร้างการทบทวนและลำดับงานการอนุมัติสำหรับใบขอซื้อ |
| การตรวจทานรายการใบขอซื้อ | สร้างการทบทวนและลำดับงานการอนุมัติสำหรับรายการใบขอซื้อ |
| ลำดับงานใบสั่งซื้อ | สร้างลำดับงานการตรวจทานและการอนุมัติสำหรับใบสั่งซื้อ |
| ลำดับงานรายการใบสั่งซื้อ | สร้างลำดับงานการตรวจทานและการอนุมัติสำหรับรายการใบสั่งซื้อ |
| ลำดับงานการเพิ่มใบสมัครของผู้จัดจำหน่าย | สร้างการทบทานและลำดับงานการอนุมัติสำหรับการเพิ่มผู้จัดจำหน่ายใหม่ โดยใช้คำขอของผู้จัดจำหน่าย |
> [!IMPORTANT]
> เมื่อคุณกำลังเพิ่มลำดับงานใหม่ คุณอาจจะเห็นลำดับงานที่ล้าสมัยต่อไปนี้แสดงรายการอยู่ในกล่องโต้ตอบ **สร้างลำดับงาน** ข้อมูลเหล่านี้เกี่ยวข้องกับฟังก์ชัน *การยืนยันการรับสินค้า* ที่พร้อมใช้งานใน [Dynamics AX 2012](/dynamicsax-2012/appuser-itpro/set-up-procurement-and-sourcing-workflows) แต่ขณะนี้ไม่สนับสนุน ลำดับงานเหล่านี้ไม่ได้รับการสนับสนุนในขณะนี้
>
> - ลำดับงานการแจ้งเตือนวันที่ครบกำหนดจัดส่ง
> - ลำดับงานการแจ้งเตือนใบแจ้งหนี้ที่ได้รับ
> - ลำดับงานการแจ้งเตือนใบรับสินค้าล้มเหลว
> - ลำดับงานการแจ้งเตือนการปฏิเสธใบรับสินค้าที่ยังไม่ได้ยืนยัน
## <a name="creating-a-workflow"></a>การสร้างแผนงาน
เมื่อต้องการสร้างลำดับงาน ให้ไปที่การจัดซื้อและการจัดหา > การตั้งค่า > การจัดซื้อและการจัดหาลำดับงาน และสร้างลำดับงานใหม่โดยการเลือกชนิดของลำดับงานที่คุณต้องการสร้าง
ในผืนผ้าใบลำดับงาน คุณสามารถลากองค์ประกอบลำดับงานลงในโปรแกรมออกแบบ และลิงค์องค์ประกอบไปยังขั้นตอน ควรตั้งค่าคอนฟิกองค์ประกอบลำดับงาน สำหรับการอนุมัติและองค์ประกอบลำดับงาน คุณสามารถตั้งค่าคอนฟิกที่ผู้เข้าร่วมควรดำเนินการ
## <a name="types-of-participants"></a>ชนิดของผู้เข้าร่วม
คุณสามารถกำหนดขั้นตอนการอนุมัติให้กลุ่มหรือผู้เข้าร่วมต่อไปนี้
| กลุ่มผู้ใช้ | คำอธิบาย |
|---|---|
| ผู้เข้าร่วม | กำหนดขั้นตอนการอนุมัติให้กับสมาชิกของกลุ่มหรือบทบาท |
| ลำดับชั้น | กำหนดขั้นตอนการอนุมัติให้กับผู้ใช้ในลำดับชั้นขององค์กรเฉพาะ |
| ผู้ใช้ลำดับงาน | กำหนดขั้นตอนการอนุมัติให้กับผู้ใช้ของลำดับงานนี้ |
| คิว | กำหนดขั้นตอนการอนุมัติให้กับคิวรายการงาน |
| ผู้ใช้ | กำหนดขั้นตอนการอนุมัติให้กับผู้ใช้เฉพาะ |
## <a name="additional-resources"></a>ทรัพยากรเพิ่มเติม
- [การกำหนดลำดับงานของกระบวนการทางธุรกิจสำหรับใบขอซื้อ](https://www.microsoft.com/download/details.aspx?id=101821)
- [ลำดับงานของใบขอซื้อ](purchase-requisitions-workflow.md)
- [เตรียมความพร้อมผู้จัดจำหน่าย](vendor-onboarding.md)
[!INCLUDE[footer-include](../../includes/footer-banner.md)] | 53.195122 | 352 | 0.739798 | tha_Thai | 0.998939 |
6ad8921c26f83fdaee7416f98390ad7e740a8251 | 5,148 | md | Markdown | msteams-platform/troubleshoot/faq.md | vule-msft/msteams-docs | f033ebf510acc57c9a906a85691c99de60a2536c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | msteams-platform/troubleshoot/faq.md | vule-msft/msteams-docs | f033ebf510acc57c9a906a85691c99de60a2536c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | msteams-platform/troubleshoot/faq.md | vule-msft/msteams-docs | f033ebf510acc57c9a906a85691c99de60a2536c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Frequently asked questions
description: Answers to frequently asked questions about developing apps for Microsoft Teams
keywords: teams apps faq faqs
ms.date: 12/07/2018
---
# Frequently asked questions (Microsoft Teams developer platform)
## Setting up
### What technology should I use to build my bot or tab?
Tabs are web content that you build and deploy, so you can use any technology you want.
Because bots must be built with the Bot Framework, we recommend you use one of the languages supported by the Bot Builder SDK: .NET/C# or Node.js. Although the Bot Framework also provides REST APIs usable by any language you choose, the SDK provides additional functionality and helper functions to simplify the development process.
We also provide Teams-specific .NET and Node.js [extensions for the Bot Builder SDK](~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk) to make integration with the Teams platform even easier.
### Where do I sign up to start building Teams apps?
1. You must have access to Microsoft Teams via an Office 365 subscription
2. If you are building a bot you must [register it with Bot Framework](~/concepts/bots/bots-create)
3. App publishing requires you [register as a Microsoft app developer](//developer.microsoft.com/en-us/store/register)
## Teams apps and authentication with guest users and Microsoft Teams free
On July 12, 2018, Microsoft announced a new edition of Microsoft Teams: *Microsoft Teams free*. This allows users to create their own Teams organizations of up to 300 users for free (not a free trial; free, period). You can find more information about Microsoft Teams free [here](https://support.office.com/article/6d79a648-6913-4696-9237-ed13de64ae3c).
There are no significant limitations in Microsoft Teams free in terms of how many apps you can use, what they can do or, for the most part, which apps are available. Some of the Teams apps are not available, for example, because they are designed to work with Office 365 services that aren't included in Microsoft Teams free.
Most apps will work in Microsoft Teams free with no modifications. However, apps which require users to log into Azure Active Directory (Azure AD) may need to make some minor changes. If you want to ensure your app works with Microsoft Teams free, and your app requires users to log into Azure AD, here's what to do:
* Ensure that the endpoint you call is in the form [http://login.microsoftonline.com/**TENANT_ID**/oauth2/authorize?...]()
and **not** [https://login.microsoftonline.com/**common**/oauth2/authorize?...]()
* To obtain **TENANT_ID**, use the [bot context](~/concepts/bots/bots-context) or the [tab context](~/concepts/tabs/tabs-context) APIs
* This will also ensure [Guest users](https://docs.microsoft.com/en-us/MicrosoftTeams/guest-access) can login using your app
For a more exhaustive discussion, see [Azure AD tab authentication](~/concepts/authentication/auth-tab-aad) and [Azure AD bot authentication](~/concepts/authentication/auth-bot-aad). For a Node.js source code example of an app that does Azure AD authentication and will work on with Microsoft Teams free, see the [Microsoft Teams Authentication Sample](https://github.com/OfficeDev/microsoft-teams-sample-auth-node) app.
## Bots
### How can my bot access the ID of a user in personal chat?
To can obtain the profile information of the user who is chatting with your bot, see [Fetching user profile in personal chat](~/concepts/bots/bots-context#fetching-user-profile-in-11-chat). (The process is almost identical to [Fetching the team roster](~/concepts/bots/bots-context#fetching-the-team-roster).)
### How can my bot access or listen to all messages in a channel?
Bots in channels receive messages only when they are explicitly @mentioned. There is no way to grant your bot access to conversations in which they are not mentioned.
## Distribution
### How can I distribute my Microsoft Teams app?
Microsoft Teams apps can be distributed to end users via AppSource and the in-product app-discovery system. For more information, see [Publish your Microsoft Teams app to AppSource](~/publishing/apps-publish).
Microsoft Teams app packages can be manually distributed to your colleagues or other end users and uploaded by them via the [uploading process](~/concepts/apps/apps-upload). Please note that apps distributed in this format are not tested, validated, or trusted by Microsoft.
### What account do I use to create an AppSource or Dev Center account?
An AppSource developer account is based on a [Microsoft account](https://account.microsoft.com/account), so you should use an existing Microsoft account or create one for this purpose.
If you already have a Windows Store developer account, you must use the original owner Microsoft account for the Seller Dashboard experience. Although the Windows Store portal allows Azure Active Directory association, the Seller Dashboard is a separate system that works only with your original Microsoft account.
---
>Not seeing your question? Submit your own; we listen to the developer community across [several channels](~/feedback).
| 76.835821 | 420 | 0.784965 | eng_Latn | 0.997523 |
6ad927ef162041af859bbcdbfd6987372a2ecd3d | 1,573 | md | Markdown | doc/models/loyalty-event-filter.md | Chetan-Gemini/square-ruby-sdk | 883bab8c56adcea93d428fbcfa24201194b7bdaa | [
"Apache-2.0"
] | null | null | null | doc/models/loyalty-event-filter.md | Chetan-Gemini/square-ruby-sdk | 883bab8c56adcea93d428fbcfa24201194b7bdaa | [
"Apache-2.0"
] | null | null | null | doc/models/loyalty-event-filter.md | Chetan-Gemini/square-ruby-sdk | 883bab8c56adcea93d428fbcfa24201194b7bdaa | [
"Apache-2.0"
] | null | null | null | ## Loyalty Event Filter
The filtering criteria. If the request specifies multiple filters,
the endpoint uses a logical AND to evaluate them.
### Structure
`LoyaltyEventFilter`
### Fields
| Name | Type | Tags | Description |
| --- | --- | --- | --- |
| `loyalty_account_filter` | [`Loyalty Event Loyalty Account Filter Hash`](/doc/models/loyalty-event-loyalty-account-filter.md) | Optional | Filter events by loyalty account. |
| `type_filter` | [`Loyalty Event Type Filter Hash`](/doc/models/loyalty-event-type-filter.md) | Optional | Filter events by event type. |
| `date_time_filter` | [`Loyalty Event Date Time Filter Hash`](/doc/models/loyalty-event-date-time-filter.md) | Optional | Filter events by date time range. |
| `location_filter` | [`Loyalty Event Location Filter Hash`](/doc/models/loyalty-event-location-filter.md) | Optional | Filter events by location. |
| `order_filter` | [`Loyalty Event Order Filter Hash`](/doc/models/loyalty-event-order-filter.md) | Optional | Filter events by the order associated with the event. |
### Example (as JSON)
```json
{
"loyalty_account_filter": {
"loyalty_account_id": "loyalty_account_id8"
},
"type_filter": {
"types": [
"REDEEM_REWARD",
"DELETE_REWARD",
"ADJUST_POINTS"
]
},
"date_time_filter": {
"created_at": {
"start_at": "start_at0",
"end_at": "end_at2"
}
},
"location_filter": {
"location_ids": [
"location_ids0",
"location_ids1",
"location_ids2"
]
},
"order_filter": {
"order_id": "order_id2"
}
}
```
| 29.679245 | 176 | 0.664336 | eng_Latn | 0.454508 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.