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
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ff7eb45edd0698a9cf98131a9d0406baf27e7d7a | 1,182 | md | Markdown | node_modules/office-ui-fabric-react/src/components/Toggle/docs/ToggleOverview.md | GhostMachineSoftware/SPFX_UsefulLinks | 5f75dac4adb579948b85f497394db943bb891462 | [
"MIT"
] | 1 | 2018-12-03T06:44:26.000Z | 2018-12-03T06:44:26.000Z | node_modules/office-ui-fabric-react/src/components/Toggle/docs/ToggleOverview.md | GhostMachineSoftware/SPFX_UsefulLinks | 5f75dac4adb579948b85f497394db943bb891462 | [
"MIT"
] | 104 | 2019-04-25T22:36:45.000Z | 2020-08-12T21:19:29.000Z | node_modules/office-ui-fabric-react/src/components/Toggle/docs/ToggleOverview.md | GhostMachineSoftware/SPFX_UsefulLinks | 5f75dac4adb579948b85f497394db943bb891462 | [
"MIT"
] | 4 | 2018-11-29T09:35:53.000Z | 2019-03-13T06:01:14.000Z | Toggles represent a physical switch that allows users to turn things on or off. Use Toggles to present users with two mutually exclusive options (like on/off), where choosing an option results in an immediate action. Use a Toggle for binary operations that take effect right after the user flips the Toggle. For example, use a Toggle to turn services or hardware components on or off. In other words, if a physical switch would work for the action, a Toggle is probably the best control to use.
## Choosing between Toggle and Checkbox
For some actions, either a Toggle or a Checkbox might work. To decide which control would work better, follow these tips:
- Use a Toggle for binary settings when changes become effective immediately after the user changes them.
- In the above example, it's clear with the Toggle that the wireless is set to "On." But with the Checkbox, the user needs to think about whether the wireless is on now or whether they need to check the box to turn wireless on.
- Use a Checkbox when the user has to perform extra steps for changes to be effective. For example, if the user must click a "Submit", "Next", "Ok" button to apply changes, use a Checkbox. | 131.333333 | 494 | 0.785956 | eng_Latn | 0.999926 |
ff7ecef9b1e487ec5508812a618c7915bf36ddb5 | 5,301 | md | Markdown | docs/relational-databases/clr-integration/database-objects/clr-integration-custom-attributes-for-clr-routines.md | MRGRD56/sql-docs.ru-ru | 4994c363fd2f95812769d48d881fd877abe35738 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/relational-databases/clr-integration/database-objects/clr-integration-custom-attributes-for-clr-routines.md | MRGRD56/sql-docs.ru-ru | 4994c363fd2f95812769d48d881fd877abe35738 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/relational-databases/clr-integration/database-objects/clr-integration-custom-attributes-for-clr-routines.md | MRGRD56/sql-docs.ru-ru | 4994c363fd2f95812769d48d881fd877abe35738 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Пользовательские атрибуты подпрограмм среды CLR | Документация Майкрософт
description: Настраиваемые атрибуты можно применять к подсредам CLR, определяемым пользователем типам и определяемым пользователем статистическим функциям, зарегистрированным в Microsoft SQL Server.
ms.custom: ''
ms.date: 03/14/2017
ms.prod: sql
ms.reviewer: ''
ms.technology: clr
ms.topic: reference
helpviewer_keywords:
- routines [CLR integration]
- SqlFacet attribute
- SqlTrigger attribute
- SqlProcedure attribute
- custom attributes [CLR integration]
- SqlUserDefinedAggregate attribute
- attributes [CLR integration]
- SqlMethod attribute
- SqlFunction attribute
- common language runtime [SQL Server], attributes
- SqlUserDefinedTypeAttribute attribute
ms.assetid: 95069d22-b05d-4670-b053-15ee2a664e33
author: rothja
ms.author: jroth
ms.openlocfilehash: bad209c4ddb516167b8048ae73680bc9ea59cc05
ms.sourcegitcommit: 04cf7905fa32e0a9a44575a6f9641d9a2e5ac0f8
ms.translationtype: MT
ms.contentlocale: ru-RU
ms.lasthandoff: 10/07/2020
ms.locfileid: "91810813"
---
# <a name="clr-integration-custom-attributes-for-clr-routines"></a>Пользовательские атрибуты интеграции со средой CLR для процедур CLR
[!INCLUDE[sql-asdbmi](../../../includes/applies-to-version/sql-asdbmi.md)]
Перечисленные атрибуты можно применять к подсредам среды CLR, определяемым пользователем типам и определяемым пользователем статистическим функциям, зарегистрированным в [!INCLUDE[msCoName](../../../includes/msconame-md.md)] [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] . Если атрибут не применен, то [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] предполагает значение по умолчанию. Перечисленные атрибуты определены в пространстве имен **Microsoft. SqlServer. Server** .
## <a name="the-sqluserdefinedaggregate-attribute"></a>Атрибут SqlUserDefinedAggregate
Атрибут **SqlUserDefinedAggregate** указывает, что метод должен быть зарегистрирован как определяемая пользователем статистическая функция. Каждое пользовательское статистическое выражение должно иметь этот атрибут.
Дополнительные сведения см. в разделе [склусердефинедаггрегатеаттрибуте](/dotnet/api/microsoft.sqlserver.server.sqluserdefinedaggregateattribute).
## <a name="the-sqlfunction-attribute"></a>Атрибут SqlFunction
Атрибут **SqlFunction** указывает, что метод должен быть зарегистрирован как функция с указанием соответствующих атрибутов функции.
Дополнительные сведения см. в разделе [SqlFunctionAttribute](/dotnet/api/microsoft.sqlserver.server.sqlfunctionattribute).
## <a name="the-sqlfacet-attribute"></a>Атрибут SqlFacet
Атрибут **склфацет** используется для получения сведений о типе возвращаемого значения выражения определяемого пользователем типа (UDT).
Дополнительные сведения см. в разделе [SqlFacetAttribute](/dotnet/api/microsoft.sqlserver.server.sqlfacetattribute).
## <a name="the-sqlprocedure-attribute"></a>Атрибут SqlProcedure
Атрибут **склпроцедуре** указывает, что метод должен быть зарегистрирован в качестве хранимой процедуры. Этот атрибут используется только в среде Visual Studio для автоматической регистрации указанного метода как хранимой процедуры. В [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] не используется.
Дополнительные сведения см. в разделе [склпроцедуреаттрибуте](/dotnet/api/microsoft.sqlserver.server.sqlprocedureattribute).
## <a name="the-sqltrigger-attribute"></a>Атрибут SqlTrigger
Атрибут **склтригжер** указывает, что метод должен быть зарегистрирован в качестве триггера.
Дополнительные сведения см. в разделе [SqlTriggerContext](/dotnet/api/microsoft.sqlserver.server.sqltriggercontext) и [склтригжераттрибуте](/dotnet/api/microsoft.sqlserver.server.sqltriggerattribute).
## <a name="the-sqluserdefinedtypeattribute"></a>SqlUserDefinedTypeAttribute
К определению класса в сборке можно применить SqlUserDefinedTypeAttribute. В результате этого [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] создает определяемый пользователем тип, привязанный к определению класса с этим пользовательским атрибутом.
Дополнительные сведения см. в разделе [SqlUserDefinedTypeAttribute](/dotnet/api/microsoft.sqlserver.server.sqluserdefinedtypeattribute).
## <a name="the-sqlmethod-attribute"></a>Атрибут SqlMethod
Атрибут **склмесод** используется для указания свойств детерминированности и доступа к данным метода или свойства определяемого пользователем типа.
Дополнительные сведения см. в разделе [склмесодаттрибуте](/dotnet/api/microsoft.sqlserver.server.sqlmethodattribute).
## <a name="see-also"></a>См. также:
[Определяемые пользователем статистические функции CLR](../../../relational-databases/clr-integration-database-objects-user-defined-functions/clr-user-defined-aggregates.md)
[Определяемые пользователем функции среды CLR](../../../relational-databases/clr-integration-database-objects-user-defined-functions/clr-user-defined-functions.md)
[Определяемые пользователем типы CLR](../../../relational-databases/clr-integration-database-objects-user-defined-types/clr-user-defined-types.md)
[Хранимые процедуры CLR](/dotnet/framework/data/adonet/sql/clr-stored-procedures)
[Триггеры CLR](/dotnet/framework/data/adonet/sql/clr-triggers)
| 67.961538 | 506 | 0.798151 | rus_Cyrl | 0.733633 |
ff8078cfbc5aab796c9b299b959ba164a58659ec | 25,400 | md | Markdown | docs/UserGuide.md | ryantanlien/tp | 05cfeee35c49b28864d29ba174026c5a4042c966 | [
"MIT"
] | null | null | null | docs/UserGuide.md | ryantanlien/tp | 05cfeee35c49b28864d29ba174026c5a4042c966 | [
"MIT"
] | null | null | null | docs/UserGuide.md | ryantanlien/tp | 05cfeee35c49b28864d29ba174026c5a4042c966 | [
"MIT"
] | null | null | null | ---
layout: page
title: User Guide
---
## Table of Contents
* Table of Contents
{:toc}
--------------------------------------------------------------------------------------------------------------------
## Introduction
**What is LinkedOUT?**
LinkedOUT is the only application that any experienced recruiter needs. LinkedOUT allows recruiters to keep track of many applicants, and the job they applied for. You can store their contact details, skills and the round of their application, all in one place.
LinkedOUT helps recruiters manage the multiple job applications they may receive on a daily basis. With many applications, it may be difficult to keep track of each applicant and which application round they are currently at.
Thus, LinkedOUT aims to improve a recruiter's experience. LinkedOUT presents recruiters with the ability to flag important applicants, edit applicants easily and search for them with ease.
LinkedOUT comes with a Command Line Interface ([CLI](#glossary)) as well as a Graphical User Interface ([GUI](#glossary)) in order to provide recruiters a more streamlined experience.
**Who is this User Guide for?**
This user guide is meant for users who wish to learn how to use our application. It is best suited for recruiters who are looking to incorporate this app into their daily workflows.
If you would like to learn more about the technical aspects of our application instead, you can do so by reading our [Developer Guide](https://ay2122s2-cs2103t-t09-2.github.io/tp/DeveloperGuide.html).
[Back to top <img src="images/back-to-top-icon.png" width="25px" />](#table-of-contents)
--------------------------------------------------------------------------------------------------------------------
## Legend
<div markdown="block" class="alert alert-info">
**:information_source: Notes:**
Notes are placed in this guide to specify extra details on the command format and serves as a guide to assist you.
</div>
<div markdown="span" class="alert alert-primary">:bulb: **Tip:**
Tips are placed in this guide to serve as suggestions that you can try out while using our application.
</div>
<div markdown="span" class="alert alert-warning">:exclamation: **Caution:**
Cautions are placed in this guide to serve as warnings for certain actions.
</div>
[Back to top <img src="images/back-to-top-icon.png" width="25px" />](#table-of-contents)
--------------------------------------------------------------------------------------------------------------------
## Quick start
1. Ensure you have Java `11` or above installed on your Computer.
2. Download the latest `LinkedOUT.jar` from [here](https://github.com/AY2122S2-CS2103T-T09-2/tp/releases/tag/v1.3(trial)).
3. Copy the file to the folder you want to use as the _home folder_ for LinkedOUT.
4. **For Windows:** Double-click the file to start the app.<br>
**For Mac:** Open up a [terminal](https://www.maketecheasier.com/launch-terminal-current-folder-mac/) in the current folder which contains the LinkedOUT jar file <br>
Then, run the following command: <br>
```java -jar LinkedOUT.jar```
<br>
LinkedOUT comes with sample data for you to experiment on. Upon starting the application, you should see the following screen:
5. Type the command in the command box and press Enter to execute it. e.g. typing **`help`** and pressing Enter will open the help window.<br>
Some example commands you can try:
* **`list`** : Lists all job applicants, along with an overview of each applicant.
* **`add`**`n/Bob p/99999999 e/[email protected] j/Data Analyst r/Interview s/Pandas` : Adds an applicant named `Bob` to the list of applicants.
* **`delete`**`1` : Deletes the first applicant from the list of applicants.
* **`exit`** : Exits the app.
* Refer to the [Features](#features) below for details of each command.
[Back to top <img src="images/back-to-top-icon.png" width="25px" />](#table-of-contents)
--------------------------------------------------------------------------------------------------------------------
## Features
<div markdown="block" class="alert alert-info">
**:information_source: Notes about the command format:**<br>
* The command word and prefixes for the command have to be `lower_case` (case-sensitive).<br>
Command words include `list`, `add`, `edit` etc.<br>
Prefixes are used by commands to recognise different parts of your inputs, these include `n/`, `j/`, `r/` etc.<br>
e.g. `edit 1 n/NAME`, this command is valid as `edit` and `n/` is `lower_case`.<br>
That is, `Add n/John Doe...` will be an invalid command because the command word `Add` is not `lower_case`.
* Words in `UPPER_CASE` are the inputs to be supplied by you.<br>
Items in square brackets are optional. These inputs are optional because they are additional information you may
not have yet.<br>
e.g. `add n/NAME p/PHONE_NUMBER e/EMAIL j/JOB r/ROUND [s/SKILL]…`.<br>
`NAME`, `PHONE_NUMBER`, `EMAIL`, `JOB`, `ROUND`, `SKILL` are inputs which can be used
as<br>
`add n/John p/999 e/[email protected] j/Engineer r/Interview s/Python` with `s/Python` being optional.
* Items with `…` after them can be used multiple times including zero times.<br>
e.g. `[s/SKILL]…` can be used as `s/Python`, `s/Python s/Java` etc.
* Prefixes can be in any order.<br>
e.g. If the command specifies `n/NAME p/PHONE_NUMBER`, `p/PHONE_NUMBER n/NAME` is also acceptable.
* If an input contains `"/"`, you may wish to avoid putting spaces after `"/"`. This is to prevent the symbol from being recognized as a prefix.<br>
e.g. `s/Java/Python` will be interpreted as a single skill of `Java/Python` but if you specify
`n/Bob s/ Java/Python`, `Java/` will be interpreted as a prefix.
* If an input is expected only once in the command but you specified it multiple times,
only the last occurrence of the input will be taken.<br>
e.g. If you specify `p/12341234 p/56785678`, only `p/56785678` will be taken.
* If a valid prefix is given twice, but you only specified the input for the last occurrence of said prefix, then the input will be accepted.
However, if you left the input for the last prefix empty, you will receive an error message.<br>
e.g. If you specify `p/ p/56785678`, `p/56785678` will be taken but if you specify `p/56785678 p/`, you will receive an error message.
* Extraneous inputs for commands that do not take in inputs (such as `help`, `list` and `exit`) will be ignored.<br>
e.g. If the command specifies `help 123`, it will be interpreted as `help`.
* `INDEX` refers to the index of the Applicant in the displayed list. `INDEX` must be a positive number.<br>
e.g. `delete 1` is valid and `delete -1` is invalid.
</div>
<br>
<div markdown="block" class="alert alert-info">
**:information_source: Notes about sample output:**
The sample output shown in this guide is for illustration purposes only.
The actual GUI might differ slightly depending upon Operating System.
</div>
<br>
[Back to top <img src="images/back-to-top-icon.png" width="25px" />](#table-of-contents)
---
### GUI Introduction
---
### Prefix and Input Summary
The table below illustrates the meaning of the prefixes and their respective inputs
| Prefix | Meaning | Input | Constraints |
|:-------|:-------------------------|:------------|:------------|
| - | | INDEX | Index of applicant specified must not be more than the total number of applicants in the list. |
| **n/** | Applicant's Name | NAME | Names can only contain letters (including letters with accents), and cannot contain any numbers. Name's can contain the following special characters: `-` and`'`. **An applicant's name is unique** i.e. two applicants cannot have the same name.
| **p/** | Applicant's Phone Number | PHONE_NUMBER| Phone numbers must only contain numbers, and must be between 3 and 15 characters long.
| **e/** | Applicant's Email | EMAIL | Emails should be of the format `local-part@domain`. Examples of valid emails include: `bob@email` & `[email protected]`, examples of invalid emails include `bobmail` & `[email protected]`.
| **j/** | Job Applied | JOB | Jobs must only contain alphanumeric characters.
| **r/** | Application Round | ROUND | Rounds must only contain alphanumeric characters.
| **s/** | Applicant's Skill | SKILL | A single skill can be made up of 1 to 5 words. The skill cannot be completely made up of symbols. However, a mix of alphanumeric and symbols are allowed. eg. `!@#` is not allowed but `C#` is allowed.
| **f/** | Field to sort by | FIELD | Field to sort list of applicant by can only be either `NAME` or `JOB` (case-insensitive).
| **o/** | Order for sorting | ORDER | Order to sort list by can only be either `ASC`, ascending order or `DESC`, descending order (case-insensitive).
[Back to top <img src="images/back-to-top-icon.png" width="25px" />](#table-of-contents)
---
### Viewing help : `help`
Shows you a message explaining how to access the help page.
<br>
Format: `help`
<br>
Example:
```
help
```
Sample Output:
[Back to top <img src="images/back-to-top-icon.png" width="25px" />](#table-of-contents)
---
### Adding an applicant: `add`
Allows you to add a new applicant to the LinkedOUT application with the following information:
* `NAME`: Applicant's name
* `PHONE_NUMBER`: Applicant's phone number
* `EMAIL`: Applicant's email
* `JOB`: The job the applicant applied for
* `ROUND`: The round of job application that the applicant is at
* `SKILL`: Particular skills the applicant may have
<br>
Format:
```
add n/NAME p/PHONE_NUMBER e/EMAIL j/JOB r/ROUND [s/SKILL]…
```
<br>
Example:
```
add n/Bob p/99999999 e/[email protected] j/Data Analyst r/Interview s/Pandas s/Python
```
Sample Output:
[Back to top <img src="images/back-to-top-icon.png" width="25px" />](#table-of-contents)
---
### Listing all applicants : `list`
Allows you to list out all job applicants, along with an overview of each applicant.
<br>
Format:
```
list
```
<br>
Example:
```
list
```
Sample Output:
[Back to top <img src="images/back-to-top-icon.png" width="25px" />](#table-of-contents)
---
### Viewing a specific applicant : `view`
Allows you to view a specific applicant, by inputting the applicant's **full name**.
<br>
Format:
```
view NAME
```
* You must provide an exact match of an applicant's full name in order to view their details.<br>
e.g. If an applicant's full name is `Steve Jobs`, and the command provided is `view Steve` then LinkedOUT will not
display `Steve Jobs`'s details. <br>
* The view command is case-insensitive. <br>
e.g Viewing `hans` will match an applicant with name `Hans`.
* Only full name will be matched. <br>
e.g. Viewing `Han Lee` will not match an applicant with name `Han`.
* Only applicant with the right amount of spacing in their full name will be matched. <br>
e.g. Viewing `HanLee` will not match an applicant with name `Han Lee`.
<br>
Example:
```
view Bernice Yu
```
Sample Output:
[Back to top <img src="images/back-to-top-icon.png" width="25px" />](#table-of-contents)
---
### Searching for an applicant : `search`
Allows you to search for applicants containing the input attributes and the attribute has to be an exact word. You can search for the applicant based on
name, job, round or skills.
<br>
Format:
```
search [n/NAME]… [j/JOB]… [r/ROUND]… [s/SKILL]…
```
* You must provide a full match of attribute you want to search for.<br>
e.g. Searching `n/Hans` will match an applicant with name `Hans Lee` but will not match an applicant with name `Han`. <br>
* The search command is case-insensitive. <br>
e.g Searching `n/hans` will match an applicant with name `Hans`.
* You can search for a combination of attributes.
After a search command, applicants will be displayed in descending order of matched attribute and the applicant with the most number of matches is shown at the top of the list.
e.g Searching `n/Hans j/Engineer` will match with applicants with either name `Hans` or job `Engineer`. Applicant with both name and job matched will be displayed on the top of the list.
<div markdown="span" class="alert alert-primary">:bulb: **Tip:**
You can try searching for multiple attributes in the applicant list. Try `search n/Alex s/Java` to search for applicants with
the name `Alex` or skill `Java`!
</div>
<br>
Example:
```
search n/Roy s/Java
```
Sample Output:
[Back to top <img src="images/back-to-top-icon.png" width="25px" />](#table-of-contents)
---
### Adding skills to an applicant: `addskill`
Allows you to add skills to a specific applicant. The index number used corresponds to the one in the displayed applicant list. This command does not replace any pre-existing skills.
<br>
Format:
```
addskill INDEX [s/SKILL]...
```
* Index of applicant specified must not be more than the total number of applicants in LinkedOUT. <br>
e.g If there are only `4` applicants in the app but `5` is specified, then the addition will not be carried out as it is invalid.
* Index of applicant specified must be a positive number. <br>
e.g As we label our applicants incrementally starting from `1` (e.g `1, 2, 3, and so on`), an index of `-1` will not be tagged to an applicant and the addition will not be carried out as it is invalid.
* If you would like to replace or remove certain skills instead, consider using [`edit`](https://ay2122s2-cs2103t-t09-2.github.io/tp/UserGuide.html#editing-an-applicant--edit).
<br>
Example:
```
addskill 1 s/React s/Vue
```
Sample Output:
[Back to top <img src="images/back-to-top-icon.png" width="25px" />](#table-of-contents)
---
### Editing an applicant : `edit`
Allows you to edit specific details of the applicant identified by the index number. The index number used corresponds to the one in the displayed applicant list.
Existing values will be overwritten by the input values.
<br>
Format:
```
edit INDEX [n/NAME] [p/PHONE] [e/EMAIL] [j/JOB] [r/ROUND] [s/SKILL]…
```
* Index of applicant specified must not be more than the total number of applicants in LinkedOUT. <br>
e.g If there are only `4` applicants in the app but `5` is specified, then the edit will not be carried out as it is invalid.
* Index of applicant specified must be a positive number. <br>
e.g As we label our applicants incrementally starting from `1` (e.g `1, 2, 3, and so on`), an index of `-1` will not be tagged to an applicant and the edit will not be carried out as it is invalid.
* As an applicant can have more than 1 skill, you may remove skills using `edit` as illustrated by the following example: <br>
e.g An applicant has skills `Excel`, `Word`, `Docs`. To remove the skill `Excel`, you may type the following command. `edit INDEX s/Word s/Docs`.
* You may also add skills using `edit`. However, a simpler way of doing so would be to use our alternative command [`addskill`](https://ay2122s2-cs2103t-t09-2.github.io/tp/UserGuide.html#adding-skills-to-an-applicant-addskill).
<br> To add skills with `edit`, you may do so as illustrated by the following example: <br>
e.g An applicant has skill `Excel`. To add the skills `Word` and `Docs`, you may type the following command. `edit INDEX s/Excel s/Word s/Docs`.
* You can remove all of an applicant's skills by simply typing `edit INDEX s/` without adding anything behind `s/`. <br>
<div markdown="span" class="alert alert-warning">:exclamation: **Caution:**
This will clear all skills previously added for an applicant and cannot be undone.
</div>
* At least one attribute must be provided to be edited. i.e. `edit INDEX` is an invalid command.
<br>
Example:
```
edit 1 p/91234567 e/[email protected] s/Rust
```
Sample Output:
[Back to top <img src="images/back-to-top-icon.png" width="25px" />](#table-of-contents)
---
### Sorting applicants : `sort`
Allows you to sort the list of applicants **temporarily** by name or by job. That is to say, the list will not stay sorted if you were to use other commands following sort.
You can sort based on ascending or descending order.
<br>
Format:
```
sort f/FIELD o/ORDER
```
* You must provide either `NAME` or `JOB` as field to be sorted, both are case-insensitive <br>
e.g if the field is `NAME`, then the list will be sorted based on applicant's name in the order given.
* You must provide either `ASC` or `DESC` for order, both are case-insensitive.
`ASC` stands for ascending and `DESC` stands for descending <br>
e.g if the order is `ASC`, then the list will be sorted in ascending order based on the field given
<br>
Example:
```
sort f/job o/asc
```
Sample Output:
[Back to top <img src="images/back-to-top-icon.png" width="25px" />](#table-of-contents)
---
### Flagging an applicant : `flag`
Allows you to flag an applicant identified by the index number. The index number used corresponds to the one in the displayed applicant list. Flagged applicants will appear at the top of the list and are identified with a flag symbol.
<br>
Format:
```
flag INDEX
```
* Index of applicant specified must not be more than the total number of applicants in LinkedOUT. <br>
e.g If there are only `4` applicants in the app but `5` is specified, then the flagging will not be carried out as it is invalid.
* Index of applicant specified must be a positive number. <br>
e.g As we label our applicants incrementally starting from `1` (e.g `1, 2, 3, and so on`), an index of `-1` will not be tagged to an applicant and the flagging will not be carried out as it is invalid.
* Flag acts like a toggle. To un-flag the applicant, you may simply re-type the same command.
<div markdown="span" class="alert alert-primary">:bulb: **Tip:**
Try flagging the first applicant by typing `flag 1`. You should see it at the top with a flag symbol. Then try un-flagging the same applicant with `flag 1`.
</div>
<br>
Example:
```
flag 1
```
Sample Output:
<br>
Extended Example for unflagging:
```
flag 1
```
Extended Sample Output for unflagging:
<br>
<div markdown="block" class="alert alert-info">
**:information_source: Flag Command Interaction with Other Commands:**
* `INDEX` of applicant to be flagged/unflagged always follows the index indicated on the user interface. <br>
e.g After executing a search, sort or view command, `flag 1` still flags/unflags the applicant at the top of the list.
* A flagged applicant acts like a pinned email, and will always be located at the top of the applicant list,
except after search and view commands. <br>
In that case, flagged applicants will be displayed according to the command's sorting order,
and will no longer be displayed at the top.
* e.g After a sort command, flagged applicants are not displayed at the top of the list and will be displayed according to the order
specified in the command.
* e.g After a search command, applicants will be displayed in descending order of number of matches with the search conditions. For more information about this behavior, please refer to the search command.
</div>
[Back to top <img src="images/back-to-top-icon.png" width="25px" />](#table-of-contents)
---
### Deleting an applicant : `delete`
Allows you to delete a specific applicant, specified by index.
<br>
Format:
```
delete INDEX
```
* Index of applicant specified must not be more than the total number of applicants in LinkedOUT. <br>
e.g If there are only `4` applicants in the app but `5` is specified, then the deletion will not be carried out as it is invalid
* Index of applicant specified must be a positive number. <br>
e.g As we label our applicants incrementally starting from `1` (e.g `1, 2, 3, and so on`), an index of `-1` will not be tagged to an applicant and the deletion will not be carried out as it is invalid.
<br>
Example:
```
delete 1
```
Sample Output:
<div markdown="span" class="alert alert-warning">:exclamation: **Caution:**
If you delete a specific applicant, LinkedOUT will permanently discard the applicant's data
</div>
[Back to top <img src="images/back-to-top-icon.png" width="25px" />](#table-of-contents)
---
### Clearing the applicants : `clear`
Clears the list of applicants
<br>
Format:
```
clear
```
<br>
Example:
```
clear
```
Sample Output:
<div markdown="span" class="alert alert-warning">:exclamation: **Caution:**
LinkedOUT will discard all data and start with an empty data file once you select 'Yes' on the confirmation box. Selecting 'No' will cancel the action.
</div>
[Back to top <img src="images/back-to-top-icon.png" width="25px" />](#table-of-contents)
---
### Exiting the program : `exit`
Exits the program.
<br>
Format: `exit`
Example:
```
exit
```
[Back to top <img src="images/back-to-top-icon.png" width="25px" />](#table-of-contents)
---
### Saving the data
LinkedOUT data is saved in the hard disk automatically after any command that changes the data. There is no need to save manually.
[Back to top <img src="images/back-to-top-icon.png" width="25px" />](#table-of-contents)
---
### Editing the data file
LinkedOUT data is saved in `[JAR file location]/data/linkedout.json`. Advanced users are welcome to update data directly by editing that data file.
<div markdown="span" class="alert alert-warning">:exclamation: **Caution:**
If your changes to the data file makes its format invalid, LinkedOUT will discard all data and start with an empty data file on the next run.
</div>
[Back to top <img src="images/back-to-top-icon.png" width="25px" />](#table-of-contents)
--------------------------------------------------------------------------------------------------------------------
## FAQ
**Q**: How do I transfer my data to another Computer?<br>
**A**: You may first install the app in another computer. Then, you may overwrite the empty data file it creates with the file containing data from the previous LinkedOUT home folder.
[Back to top <img src="images/back-to-top-icon.png" width="25px" />](#table-of-contents)
--------------------------------------------------------------------------------------------------------------------
## Glossary
* **GUI**: Graphical User Interface: Refers to the user interface that the user interacts with.
* **CLI**: Command Line Interface: Refers to a computer program that accepts text inputs.
[Back to top <img src="images/back-to-top-icon.png" width="25px" />](#table-of-contents)
---
## Command summary
| Action | Format, Examples |
|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|
| **Help** | `help` |
| **Add** | `add n/NAME p/PHONE_NUMBER e/EMAIL j/JOB r/ROUND [s/SKILL]…` <br> e.g: `add n/Bob p/99999999 e/[email protected] j/Data Analyst r/Interview s/Pandas` |
| **List** | `list` |
| **View** | `view NAME` <br> e.g: `view Steve Jobs` |
| **Search** | `search [n/NAME]... [j/JOB]... [r/ROUND]... [s/SKILL]...` <br> e.g: `search n/Steve` |
| **AddSkill** | `addskill INDEX [s/SKILL]....` <br> e.g `addskill 1 s/MySQL s/PostgreSQL`|
| **Edit** | `edit INDEX [n/NAME] [p/PHONE] [e/EMAIL] [j/JOB] [r/ROUND] [s/SKILL]...` <br> e.g: `edit 1 n/Elon Musk` |
| **Sort** | `sort f/FIELD o/ORDER` <br/> e.g: `sort f/Name o/Asc` |
| **Flag** | `flag INDEX` <br> e.g: `flag 1` |
| **Delete** | `delete INDEX` <br> e.g: `delete 1` |
| **Clear** | `clear` |
| **Exit** | `exit` |
[Back to top <img src="images/back-to-top-icon.png" width="25px" />](#table-of-contents)
| 40.705128 | 294 | 0.65189 | eng_Latn | 0.991031 |
ff8126ff2e488ef20496f4f602c9a3b530559c89 | 75 | md | Markdown | build/content/people/a/alexandre-termier.md | briemadu/semdial-proceedings | 59f13adcc73dc9433c3c07ee929fadd8d271b022 | [
"Apache-2.0"
] | null | null | null | build/content/people/a/alexandre-termier.md | briemadu/semdial-proceedings | 59f13adcc73dc9433c3c07ee929fadd8d271b022 | [
"Apache-2.0"
] | null | null | null | build/content/people/a/alexandre-termier.md | briemadu/semdial-proceedings | 59f13adcc73dc9433c3c07ee929fadd8d271b022 | [
"Apache-2.0"
] | 2 | 2021-09-16T07:16:15.000Z | 2021-10-30T06:41:55.000Z | ---
lastname: Termier
name: alexandre-termier
title: Alexandre Termier
---
| 12.5 | 24 | 0.746667 | slk_Latn | 0.328593 |
ff814366b230aff73620e1fbf07a229f487b8f09 | 1,637 | md | Markdown | aws-ses.md | shunliz/AWS-certificate | 44ba8573dfb4ece57ca75e99cb1f6c2aa0818d1a | [
"Apache-2.0"
] | 2 | 2020-03-28T09:22:51.000Z | 2021-06-11T23:00:32.000Z | aws-ses.md | shunliz/AWS-certificate | 44ba8573dfb4ece57ca75e99cb1f6c2aa0818d1a | [
"Apache-2.0"
] | null | null | null | aws-ses.md | shunliz/AWS-certificate | 44ba8573dfb4ece57ca75e99cb1f6c2aa0818d1a | [
"Apache-2.0"
] | 1 | 2022-02-03T16:10:29.000Z | 2022-02-03T16:10:29.000Z | # AWS Simple Email Service – SES
* SES is a managed service and ideal for sending bulk emails at scale
* SES acts as an outbound email server and eliminates the need to support own software or applications to do the heavy lifting of email transport
* Existing email server can also be configure to send outgoing emails through SES with no change in any settings in the email clients
* Maximum message size including attachments is 10 MB per message \(after base64 encoding\).
## SES Characteristics
* Compatible with SMTP
* Applications can send email using a single API call in many supported languages Java, .Net, PHP, Perl, Ruby, HTTPs etc
* Optimized for highest levels of uptime, availability and scales as per the demand
* Provides sandbox environment for testing
## Sending Limits
* Production SES has a set of sending limits which include
* Sending Quota – max number of emails in 24-hour period
* Maximum Send Rate – max number of emails per second
* SES automatically adjusts the limits upward as long as emails are of high quality and they are sent in a controlled manner, as any spike in the email sent might be considered to be spams.
* Limits can also be raised by submitting a Quota increase request
## SES Best Practices
* Send high-quality and real production content that your recipients want
* Only send to those who have signed up for the mail
* Unsubscribe recipients who have not interacted with the business recently
* Have low bounce and compliant rates and remove bounced or complained addresses, using SNS to monitor bounces and complaints, treating them as opt-out
* Monitor the sending activity
| 49.606061 | 189 | 0.789249 | eng_Latn | 0.999597 |
ff83fdbdee4662fe07f4fd465de293d914d74ec9 | 712 | md | Markdown | windows.ui.xaml.controls.maps/mapcontrol_mapservicetoken.md | tossnet/winrt-api | 42ebcbca22e88f3ed0f273629d7cdf290dfe2133 | [
"CC-BY-4.0",
"MIT"
] | 199 | 2017-02-09T23:13:51.000Z | 2022-03-28T15:56:12.000Z | windows.ui.xaml.controls.maps/mapcontrol_mapservicetoken.md | tossnet/winrt-api | 42ebcbca22e88f3ed0f273629d7cdf290dfe2133 | [
"CC-BY-4.0",
"MIT"
] | 2,093 | 2017-02-09T21:52:45.000Z | 2022-03-25T22:23:18.000Z | windows.ui.xaml.controls.maps/mapcontrol_mapservicetoken.md | tossnet/winrt-api | 42ebcbca22e88f3ed0f273629d7cdf290dfe2133 | [
"CC-BY-4.0",
"MIT"
] | 620 | 2017-02-08T19:19:44.000Z | 2022-03-29T11:38:25.000Z | ---
-api-id: P:Windows.UI.Xaml.Controls.Maps.MapControl.MapServiceToken
-api-type: winrt property
---
<!-- Property syntax
public string MapServiceToken { get; set; }
-->
# Windows.UI.Xaml.Controls.Maps.MapControl.MapServiceToken
## -description
Gets or sets the authentication key required for using the [MapControl](mapcontrol.md) and online mapping services.
## -property-value
The authentication key required for using the [MapControl](mapcontrol.md) and online mapping services.
## -remarks
## -examples
## -see-also
[Request a maps authentication key](/windows/uwp/maps-and-location/authentication-key), [Display maps with 2D, 3D, and Streetside views](/windows/uwp/maps-and-location/display-maps)
| 29.666667 | 181 | 0.76264 | eng_Latn | 0.623005 |
ff840b8e87692c95d9d0a504fc0fdb3dc21bf44a | 826 | md | Markdown | _pages/about.md | DigitalHammer/DigitalHammer.github.io | 6c128ed5ce4dccf7f597d3ea631f910a4e8ee96a | [
"MIT"
] | null | null | null | _pages/about.md | DigitalHammer/DigitalHammer.github.io | 6c128ed5ce4dccf7f597d3ea631f910a4e8ee96a | [
"MIT"
] | null | null | null | _pages/about.md | DigitalHammer/DigitalHammer.github.io | 6c128ed5ce4dccf7f597d3ea631f910a4e8ee96a | [
"MIT"
] | null | null | null | ---
layout: single
author_profile: False
title: I Live to Explore
---
Husband, expecting father, Marine veteran, former strength coach, cybersecurity professional, hiker, big family, a nerd of endless stories (Marvel, Star Wars, LotR, Harry Potter, ATLA, DBZ, MHA +++)... *how many descriptive terms are enough?*
Everyday is an adventure. Self-mastery is the ultimate solution to life. Wakanda forever.
**"One can have no smaller or greater mastery than mastery of oneself."** - Leonardo da Vinci
[GitHub](https://github.com/DigitalHammer){: .btn .btn--success}
[LinkedIn](https://www.linkedin.com/in/the-adam-mcewen/){: .btn .btn--info}
- - -
| 27.533333 | 243 | 0.738499 | eng_Latn | 0.725558 |
ff84e1af06938d293101704e68653c12ad5a98b9 | 441 | md | Markdown | README.md | 13muskanp/ML-from-Scratch | 9a830cf363904f79bc12989df77cac3cbbd86011 | [
"MIT"
] | 1 | 2021-07-07T15:24:22.000Z | 2021-07-07T15:24:22.000Z | README.md | 13muskanp/ML-from-Scratch | 9a830cf363904f79bc12989df77cac3cbbd86011 | [
"MIT"
] | null | null | null | README.md | 13muskanp/ML-from-Scratch | 9a830cf363904f79bc12989df77cac3cbbd86011 | [
"MIT"
] | null | null | null | # ML-from-Scratch
This repository contains Machine Learning Algorithms implemented from scratch.
## Topics
- [Baysian Classifier](https://github.com/odavhad/ML-from-Scratch/tree/main/Baysian%20Classifier)
- [ID3](https://github.com/odavhad/ML-from-Scratch/tree/main/ID3)
- [K-means](https://github.com/odavhad/ML-from-Scratch/tree/main/K-means)
- [KNN](https://github.com/odavhad/ML-from-Scratch/tree/main/KNN)
#### Open for Hactoberfest
| 36.75 | 97 | 0.759637 | yue_Hant | 0.286946 |
ff84f85278b0713597e6ff633ca6503779e2344d | 5,439 | md | Markdown | docs/integration-services/building-packages-programmatically/building-packages-programmatically.md | taiyaki32lp64/sql-docs.ja-jp | 5e7aa5e72daf73d7997c26baf0b1edd90fb0c681 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/integration-services/building-packages-programmatically/building-packages-programmatically.md | taiyaki32lp64/sql-docs.ja-jp | 5e7aa5e72daf73d7997c26baf0b1edd90fb0c681 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/integration-services/building-packages-programmatically/building-packages-programmatically.md | taiyaki32lp64/sql-docs.ja-jp | 5e7aa5e72daf73d7997c26baf0b1edd90fb0c681 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: プログラムによるパッケージの作成 | Microsoft Docs
ms.custom: ''
ms.date: 03/16/2017
ms.prod: sql
ms.prod_service: integration-services
ms.reviewer: ''
ms.technology: integration-services
ms.topic: reference
ms.assetid: 7474b1f4-7607-4f28-a6fd-67f7db1dd3f8
author: douglaslMS
ms.author: douglasl
manager: craigg
ms.openlocfilehash: 95c26215be0cb55c916d7162896ec7651132f13f
ms.sourcegitcommit: 0638b228980998de9056b177c83ed14494b9ad74
ms.translationtype: HT
ms.contentlocale: ja-JP
ms.lasthandoff: 11/14/2018
ms.locfileid: "51640969"
---
# <a name="building-packages-programmatically"></a>プログラムによるパッケージの作成
パッケージを動的に作成する必要がある場合、または開発環境以外で [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] パッケージを管理および実行する必要がある場合は、プログラムでパッケージを操作できます。 この場合、次に示すような一連の方法があります。
- 既存のパッケージを読み込んで、変更せずに実行します。
- 既存のパッケージを読み込み、(別のデータ ソースを指定するなど) 再構成してから実行します。
- 新しいパッケージを作成し、オブジェクト単位やプロパティ単位でコンポーネントを追加および構成し、保存してから実行します。
[!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] オブジェクト モデルを使用すると、任意のマネージド プログラミング言語でパッケージを作成、構成、および実行するコードを記述できます。 たとえば、選択したデータ ソースとそのテーブルおよび列に基づいて、パッケージの接続またはデータ ソース、変換、および変換先を構成するメタデータ ドリブン パッケージの作成が必要になる場合があります。
ここでは、プログラムを使用してパッケージを行単位で作成および構成する方法を説明し、その例を示します。 パッケージ プログラミングの最も簡単な方法では、「[プログラムによるパッケージの実行と管理](../../integration-services/run-manage-packages-programmatically/running-and-managing-packages-programmatically.md)」に示すように、既存のパッケージを読み込んで、変更せずに実行できます。
ここに示されていない中レベルの方法としては、既存のパッケージをテンプレートとして読み込み、再構成 (異なるデータ ソースの指定など) してから実行する方法があります。 ここに記載された情報を使用して、パッケージ内の既存のオブジェクトを変更することもできます。
> [!NOTE]
> 既存のパッケージをテンプレートとして使用し、データ フロー内の既存の列を変更する場合、状況によっては、既存の列を削除してから、影響を受けるコンポーネントの <xref:Microsoft.SqlServer.Dts.Pipeline.PipelineComponent.ReinitializeMetaData%2A> メソッドを呼び出す必要があります。
## <a name="in-this-section"></a>このセクションの内容
[プログラムを使用したパッケージ作成](../../integration-services/building-packages-programmatically/creating-a-package-programmatically.md)
プログラムを使用してパッケージを作成する方法について説明します。
[プログラムによるタスクの追加](../../integration-services/building-packages-programmatically/adding-tasks-programmatically.md)
タスクをパッケージに追加する方法について説明します。
[プログラムによるタスクの接続](../../integration-services/building-packages-programmatically/connecting-tasks-programmatically.md)
パッケージ内のコンテナーおよびタスクの実行を、前に実行したタスクまたはコンテナーの結果に基づいて制御する方法について説明します。
[プログラムによる接続の追加](../../integration-services/building-packages-programmatically/adding-connections-programmatically.md)
接続マネージャーをパッケージに追加する方法について説明します。
[プログラムによる変数の使用](../../integration-services/building-packages-programmatically/working-with-variables-programmatically.md)
パッケージの実行中に、変数を追加および使用する方法について説明します。
[プログラムによるイベントの処理](../../integration-services/building-packages-programmatically/handling-events-programmatically.md)
パッケージおよびタスク イベントを処理する方法について説明します。
[プログラムによるログ記録の有効化](../../integration-services/building-packages-programmatically/enabling-logging-programmatically.md)
パッケージまたはタスクのログ記録を有効にし、カスタム フィルターをログ イベントに適用する方法について説明します。
[プログラムによるデータ フロー タスクの追加](../../integration-services/building-packages-programmatically/adding-the-data-flow-task-programmatically.md)
データ フロー タスクおよびそのコンポーネントを追加して構成する方法について説明します。
[プログラムによるデータ フロー コンポーネントの検出](../../integration-services/building-packages-programmatically/discovering-data-flow-components-programmatically.md)
ローカル コンピューターにインストールされているコンポーネントの検出方法について説明します。
[プログラムによるデータ フロー コンポーネントの追加](../../integration-services/building-packages-programmatically/adding-data-flow-components-programmatically.md)
コンポーネントをデータ フロー タスクに追加する方法について説明します。
[プログラムによるデータ フロー コンポーネントの接続](../../integration-services/building-packages-programmatically/connecting-data-flow-components-programmatically.md)
2 つのデータ フロー コンポーネントの接続方法について説明します。
[プログラムによる入力列の選択](../../integration-services/building-packages-programmatically/selecting-input-columns-programmatically.md)
データ フローの上流コンポーネントによってコンポーネントに提供される入力列から、使用する入力列を選択する方法について説明します。
[プログラムによるパッケージの保存](../../integration-services/building-packages-programmatically/saving-a-package-programmatically.md)
プログラムを使用してパッケージを保存する方法について説明します。
## <a name="reference"></a>リファレンス
[Integration Services のエラーとメッセージのリファレンス](../../integration-services/integration-services-error-and-message-reference.md)
事前に定義されている [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] エラー コードと、そのシンボル名および説明の一覧を示します。
## <a name="related-sections"></a>関連項目
[スクリプトによるパッケージの拡張](../../integration-services/extending-packages-scripting/extending-packages-with-scripting.md)
スクリプト タスクを使用した制御フローの拡張方法と、スクリプト コンポーネントを使用したデータ フローの拡張方法について説明します。
[カスタム オブジェクトを使用したパッケージの拡張](../../integration-services/extending-packages-custom-objects/extending-packages-with-custom-objects.md)
複数のパッケージで使用するプログラム カスタム タスク、データ フロー コンポーネント、およびその他のパッケージ オブジェクトを作成する方法について説明します。
[プログラムによるパッケージの実行と管理](../../integration-services/run-manage-packages-programmatically/running-and-managing-packages-programmatically.md)
パッケージおよびパッケージが保存されているフォルダーを列挙、実行、管理する方法について説明します。
## <a name="external-resources"></a>外部リソース
- www.codeplex.com/MSFTISProdSamples の CodePlex サンプル「[Integration Services 製品サンプル](https://go.microsoft.com/fwlink/?LinkID=131204)」
- blogs.msdn.com のブログ「[カスタム拡張機能のパフォーマンスのプロファイル](https://go.microsoft.com/fwlink/?LinkId=238831)」
## <a name="see-also"></a>参照
[SQL Server Integration Services](../../integration-services/sql-server-integration-services.md)
| 52.805825 | 250 | 0.801986 | yue_Hant | 0.616519 |
ff84f92d5f4168964b61a8a3c8edfccf41e9914f | 4,749 | md | Markdown | docs/coordinating/agenda.md | Alfriadox/rcos-handbook | 4f7118f5830479dff9f07c45eddb97f143c203d4 | [
"MIT"
] | 12 | 2018-05-07T13:48:21.000Z | 2022-02-27T15:38:40.000Z | docs/coordinating/agenda.md | Alfriadox/rcos-handbook | 4f7118f5830479dff9f07c45eddb97f143c203d4 | [
"MIT"
] | 113 | 2018-05-06T05:00:58.000Z | 2022-03-24T21:31:46.000Z | docs/coordinating/agenda.md | Alfriadox/rcos-handbook | 4f7118f5830479dff9f07c45eddb97f143c203d4 | [
"MIT"
] | 22 | 2018-05-06T04:54:37.000Z | 2022-03-21T22:43:53.000Z | # First Two Weeks Agenda
The first two weeks is an extremely important time to get new students acquainted with RCOS, old students updated on any changes in structure/leadership, assigning Mentors and a handful of other tasks. This is the most important time for the Coordinators to be "on top of things".
## Before the First Meeting
Prior to the first meeting new Coordinators should be chosen. Any planned changes should be reflected in the relevant documentation and/or presentations. The Coordinators should meet to plan and make sure all administrative affairs are in order.
<!--In addition, at least one [mentor training session](mentoring/training) must take place prior to the first meeting.-->
## Outline
All of the following details need to be worked out within the first two weeks
* RCOS Concepts
- History Reviewed
- Structure, Grading and Motivations introduced
- Sponsors introduced
- Small groups introduced
- Semester Goals introduced
- Presentation rules and guidelines
* Old Projects Pitched
* New Projects Pitched
* Project Pairing
## First Meeting
The first meeting is to be held on the first Tuesday or Friday of classes, whichever comes first.
The first meeting begins with the [introduction slides](https://gitpitch.com/rcos/rcos-handbook/master?p=slides/intro), presented by the student Coordinators. The slides go through the stucture of RCOS and how to participate. A Faculty Advisor will then give a talk on the [history](/overview/history) of RCOS, and briefly explain some administrative details.
After the intro talk, mentors are announced and given the chance to introduce themselves. Mentors should say a few sentences about themselves and what experience they have.
The expectations of working on a project for credit are defined. The rubric is explained with emphasis on changes / improvements from the previous year based on feedback from students and mentors. Coordinators should be careful not to sound stringent or cold, while making clear that working on a project for credit does require a commitment and the students' best effort.
After expectations are defined, students are reminded how to pitch their projects the following meeting. Pitch slides are collected by a Coordinator until 11:59PM the night before the second meeting.
Existing projects are reminded to submit proposals. Existing projects are asked to fill out a form expressing their small group mentor/technology preference.
After the first meeting, another mentor training session will be held for any new mentors who have not completed mentor training.
## Second Meeting
The second meeting is dedicated solely to project pitches. Each pitch should be no more than one minute long, although exceptions are sometimes made for 'special' projects.
Additional information should be kept to the minimum. Students should be encouraged to get in touch with project leaders and mentors for help picking a project, and should be reminded of the URP form deadlines.
If a significant number of new mentors have still not completed mentor training, another mentor training session will take place after the second meeting if time allows.
## Third Meeting
The third meeting has two parts that occur simultaneously: [Project Pairing](membership/project_pairing) and proposal approval. The mentors should be split evenly between the two events, with each occuring in its own room. Finding a project can be very nervewracking for newcomers, so Project Pairing is intended to ensure every student finds a project.
In the second room, mentors should be present to look over student's proposals and approve them. If a proposal does not meet the guidelines, mentors should assist the project members in modifying their proposal.
**Every for-credit student must have a project with an approved proposal by the end of the fourth meeting.**
## Prior to the Fourth Meeting
Mentor groups should selected and rooms should be assigned prior to the fourth meeting. Each mentor group should have its own room. Projects should be distributed amongst Small Groups as evenly as possible. Projects should be assigned to mentors with relevant skill sets so the mentors can best provide technical assistance when needed. All students should be informed of their mentor groups prior to the fourth meeting. If the fourth meeting is a Tuesday, students should report directly to their mentor group.
At least one mentor meeting excluding mentor training must occur prior to the fourth meeting. Mentors should be instructured to ensure that mentees:
1. Are on [rcos.io](https://rcos.io).
2. Are on [Discord](https://rcos-discord.herokuapp.com/)
Any larger goals for the year should be made clear and a schedule for mentor meetings should be set.
| 74.203125 | 511 | 0.805012 | eng_Latn | 0.999761 |
ff85a3f5008180f091096520e8a9461bf815ee09 | 460 | md | Markdown | README.md | Keno/Meshes.jl | 438f0d2bf836272fb96f6a11583edf36ef05becc | [
"MIT"
] | null | null | null | README.md | Keno/Meshes.jl | 438f0d2bf836272fb96f6a11583edf36ef05becc | [
"MIT"
] | null | null | null | README.md | Keno/Meshes.jl | 438f0d2bf836272fb96f6a11583edf36ef05becc | [
"MIT"
] | null | null | null | # Meshes.jl
[](https://travis-ci.org/twadleigh/Meshes.jl)
Generation and manipulation of triangular meshes.
## Features
1. Isosurface extraction via marching tetrahedra.
2. Construction of volumes from primitive solids (sphere, box, cylinder).
3. Export to PLY and ascii STL formats.
4. Import and Export of Aquaveo-SMS .2dm format.
## Coming soon, hopefully...
1. Basic mesh simplification.
| 27.058824 | 107 | 0.758696 | eng_Latn | 0.699333 |
ff85c2fb04cc18eca3fdf2b8ccbd4d9e51aaae55 | 1,576 | md | Markdown | _posts/2020-07-15-Tobimoa.md | AMOIM/AMOIM.github.io | dd4adafe878a810aba0181aa51f691fb335e13c2 | [
"Apache-2.0"
] | 1 | 2020-07-04T10:44:33.000Z | 2020-07-04T10:44:33.000Z | _posts/2020-07-15-Tobimoa.md | AMOIM/AMOIM.github.io | dd4adafe878a810aba0181aa51f691fb335e13c2 | [
"Apache-2.0"
] | null | null | null | _posts/2020-07-15-Tobimoa.md | AMOIM/AMOIM.github.io | dd4adafe878a810aba0181aa51f691fb335e13c2 | [
"Apache-2.0"
] | null | null | null | ---
layout: post
title: "토비모아:토비모아가 뭐야?"
subtitle: "미아방지팔찌"
author: "Hwangsoomin"
header-style: text
tags:
arduino
android
node.js
vue.js
mongoDB
category : [Tobimoa]
---
### 토비모아란?
토비모아 (Tobimoa), 불어로 Trouvez moi('나를 찾아줘!')이다.<br />
'토비모아'라는 이름을 가진 미아방지(위치추적) 팔찌이며,<br />
기존의 미아방지팔찌와는 다르게 스템프 기능이 있고,<br />
어플리케이션을 통해 위치와 스탬프를 확인할 수 있다.<br />
이를 통해 다중이용시설에서 보호자가 아이의 위치를 쉽게 파악할 수 있어<br />
미아 발생 문제 해결에 기여한다.<br />
### 기능
* ##### 팔찌
+ GPS로 위치정보를 서버에 전송
+ NFC 스티커는 리더기와 태그하여 스탬프 적립을 도와줄 UID를 리더기에 전송
> 
<br/>
* ##### NFC 리더기
+ 팔찌로부터 받은 UID와 지정한 리더기 번호를 서버에 전송
+ 서버로부터 응답받은 스탬프 개수를 화면에 출력
> 
<br/>
* ##### WEB
+ 사용자의 정보 등록, 삭제, 수정, 조회가 가능
+ 어플에서 보내는 스탬프 개수, 위치 확인 요청을 처리
+ 리더기에서 보내는 실시간 위치 정보와 스탬프 추가 API요청을 처리
<br/>
* ##### Application
+ 웹에서 등록한 정보로 서버를 통해 로그인
+ 팔찌 사용자, 어플 사용자, 스탬프의 위치 조회
+ 등록한 스탬프 현황 조회
<br/>
### 아키텍쳐
<br/>
### 시제품
<br/>
### 기술_스택
`C/C++` `Java` `Node.js` `MongoDB` `Vue.js` `AWS`
<br />
### 링크
[https://github.com/CSIE16](https://github.com/CSIE16) | 26.266667 | 115 | 0.670051 | kor_Hang | 0.999819 |
ff869b77780ea7e4e3268482311c36bb9782813a | 1,100 | md | Markdown | modules/MMM-TwitterTrendsByPlace1/woeid_short_list.md | MoneyColor/hide_movie | 8603cdbff171602ae2e59e94b2049ede0c4789c4 | [
"MIT"
] | null | null | null | modules/MMM-TwitterTrendsByPlace1/woeid_short_list.md | MoneyColor/hide_movie | 8603cdbff171602ae2e59e94b2049ede0c4789c4 | [
"MIT"
] | null | null | null | modules/MMM-TwitterTrendsByPlace1/woeid_short_list.md | MoneyColor/hide_movie | 8603cdbff171602ae2e59e94b2049ede0c4789c4 | [
"MIT"
] | null | null | null | <table width="40%">
<!-- why, markdown... -->
<thead>
<tr>
<th>WOEID</th>
<th>Name/Title</th>
</tr>
<thead>
<tbody>
<tr><td>1</td><td>Entire Globe</td></tr>
<tr><td>2459115</td><td>New York, NY</td></tr>
<tr><td>2358820</td><td>Baltimore, MD</td></tr>
<tr><td>2442047</td><td>Los Angeles, CA</td></tr>
<tr><td>2388929</td><td>Dallas, TX</td></tr>
<tr><td>2514815</td><td>Washington, DC</td></tr>
<tr><td>2379574</td><td>Chicago, IL</td></tr>
<tr><td>2391279</td><td>Denver, CO</td></tr>
<tr><td>2475687</td><td>Portland, OR</td></tr>
<tr><td>2490383</td><td>Seattle, WA</td></tr>
<tr><td>2458833</td><td>New Orlands, LA</td></tr>
<tr><td>2487956</td><td>San Francisco, CA</td></tr>
<tr><td>2450022</td><td>Miami, FL</td></tr>
<tr><td>2486982</td><td>St. Louis, MO</td></tr>
<tr><td>2357024</td><td>Atlanta, GA</td></tr>
<tr><td>44418</td><td>London, England</td></tr>
<tr><td>615702</td><td>Paris, France</td></tr>
<tr><td>638242</td><td>Berlin, Germany</td></tr>
<tr><td>2122265</td><td>Moscow, Russia</td></tr>
<tr><td>560743</td><td>Dublin, Ireland</td></tr>
</tbody>
</table> | 35.483871 | 51 | 0.595455 | yue_Hant | 0.256549 |
ff873048bb1665acc3347109bacb7ec6217b7749 | 1,393 | md | Markdown | pages/mydoc/model/datasource.md | datafor123/datafor123.github.io | 6566981d681199531011064e43ac9eebd2207351 | [
"MIT",
"BSD-3-Clause"
] | null | null | null | pages/mydoc/model/datasource.md | datafor123/datafor123.github.io | 6566981d681199531011064e43ac9eebd2207351 | [
"MIT",
"BSD-3-Clause"
] | 5 | 2020-02-25T15:55:56.000Z | 2022-02-26T04:39:45.000Z | pages/mydoc/model/datasource.md | datafor123/datafor123.github.io | 6566981d681199531011064e43ac9eebd2207351 | [
"MIT",
"BSD-3-Clause"
] | 4 | 2019-07-09T05:24:31.000Z | 2022-03-29T09:03:44.000Z | ---
title: 创建多维分析模型
tags: [数据源]
last_updated: 2018年12月28日
keywords:
sidebar: mydoc_sidebar
permalink: datasource.html
folder: mydoc
---
Pentaho的分析模型建立在Mondrian（OLAP）引擎上。OLAP依赖于多维数据模型，数据查询组件通过mdx查询多维数据模型返回数据集。
Pentaho分析模型定义逻辑多维数据库，并将其映射到物理数据模型。分析模型构建了一个多维结构描述层，该结构包含一个或多个立方体、层次结构、层级和度量等元素。
Pentaho提供三种方式构建多维分析模型。
- 数据源向导
- Schema Workbench客户端软件
- Pentaho Data Refinery组件
### “数据源向导”构建多维分析模型
1. 登录Pentaho用户控制台。
2. 从菜单或快捷按钮选择”管理数据源“
3. 点击“新数据源”按钮
4. 输入人“数据源名称”，选择数据源类型
5. 点击“连接”右侧的“+”新建连接，或者从下面的列表中选择已有的连接
6. 选择维度表和事实表
7. 创建表关系
8. 点击完成按钮
9. 选择“保持默认模型”或“立即自定义模型
10. 按“确定”完成
### 使用Schema Workbench构建分析模型
Mondrian分析模型本质上是一个XML文件，定义了多维数据结构和物理数据模型的映射关系。您可以通过[Pentaho Schema Workbench](https://help.pentaho.com/Documentation/8.3/Work_with_data/Configure_Mondrian_engine)构建分析模型。
| 22.111111 | 169 | 0.755922 | yue_Hant | 0.207812 |
ff8762a9e9c51a38718b250495f80e97233af4d6 | 10,636 | md | Markdown | README.md | xunzhaotech/nodepress | c088c8818e9a00758c6a33dd523154d695e3eb7e | [
"MIT"
] | 1 | 2020-08-04T06:03:45.000Z | 2020-08-04T06:03:45.000Z | README.md | josephdgb1996/nodepress | 5263cf218f9557f26f1c0c523ec1444eead93dd9 | [
"MIT"
] | 3 | 2021-05-11T22:46:16.000Z | 2022-01-22T15:01:28.000Z | README.md | ndzy02/nest | 4a5eb637630104e58f40f1b428716d9165638655 | [
"MIT"
] | 1 | 2020-03-25T14:23:42.000Z | 2020-03-25T14:23:42.000Z | <p align="center">
<a href="https://github.com/surmon-china/nodepress" target="blank">
<img src="https://raw.githubusercontent.com/surmon-china/nodepress/master/logo.png" height="90" alt="nodepress Logo" />
</a>
</p>
# NodePress
[](https://github.com/surmon-china/nodepress)
[](https://github.com/surmon-china/nodepress/stargazers)
[](https://github.com/surmon-china/nodepress/issues)
[](https://github.com/surmon-china/nodepress/actions?query=workflow:%22Deploy%22)
[](https://github.com/surmon-china/nodepress/blob/master/LICENSE)
**RESTful API service for [surmon.me](https://github.com/surmon-china/surmon.me) blog, powered by [nestjs](https://github.com/nestjs/nest), required [mongoDB](https://www.mongodb.com/) & [Redis](https://redis.io/).**
**适用于 [surmon.me](https://github.com/surmon-china/surmon.me) 的 RESTful API 服务；基于 [nestjs](https://github.com/nestjs/nest) (nodejs)；
需安装 [mongoDB](https://www.mongodb.com/) 和 [Redis](https://redis.io/) 方可完整运行。**
v3.x 使用 [nestjs](https://github.com/nestjs/nest) 进行重构，之前的 nodejs 版本在 [此分支](https://github.com/surmon-china/nodepress/tree/nodejs)。
**其他相关项目：**
- **web client for user:** [surmon.me](https://github.com/surmon-china/surmon.me) powered by [Nuxt.js](https://github.com/nuxt/nuxt.js)
- **web client for admin:** [angular-admin](https://github.com/surmon-china/angular-admin) powered by [Angular](https://github.com/angular/angular) & [Bootstrap](https://github.com/twbs/bootstrap)
- **native app client:** [surmon.me.native](https://github.com/surmon-china/surmon.me.native) powered by [react-native](https://github.com/facebook/react-native)
**更新记录：[CHANGELOG.md](https://github.com/surmon-china/nodepress/blob/master/CHANGELOG.md#changelog)**
**接口文档：[API_DOC.md](https://github.com/surmon-china/nodepress/blob/master/API_DOC.md)**
---
## v3.x 架构说明
### 接口概述
- HTTP 状态码（详见 [errors](https://github.com/surmon-china/nodepress/tree/nest/src/errors) ）
* `400` 请求的业务被拒绝
* `401` 鉴权失败
* `403` 权限不足/请求参数需要更高的权限
* `404` 资源不存在
* `405` 无此方法
* `500` 服务器挂了
* `200` 正常
* `201` POST 正常
- 数据特征码（详见 [http.interface.ts](https://github.com/surmon-china/nodepress/blob/master/src/interfaces/http.interface.ts) ）
* `status`：
* `success`：正常
* `error`：异常
* `message`：永远返回（由 [http.decorator](https://github.com/surmon-china/nodepress/blob/master/src/decorators/http.decorator.ts) 装饰）
* `error`：一般会返回错误发生节点的 error；在 `status` 为 `error` 的时候必须返回，方便调试
* `debug`：开发模式下为发生错误的堆栈，生产模式不返回
* `result`：在 `status` 为 `success` 的时候必须返回
* 列表数据：一般返回`{ pagination: {...}, data: {..} }`
* 具体数据：例如文章，则包含直接数据如`{ title: '', content: ... }`
### 数据模型
- 通用
* `extend` 为通用扩展（[模型在此](https://github.com/surmon-china/nodepress/blob/master/src/models/extend.model.ts)）
* 文章、分类、Tag 表都包含 extend 字段，用于在后台管理中自定义扩展，类似于 Wordpress 中的自定义字段功能，目前用来实现前台 icon 图标的 class 或者其他功能
- 各表重要字段
* `_id`：mongodb 生成的 id，一般用于后台执行 CRUD 操作
* `id`：插件生成的自增数字 id，类似 mysql 中的 id，具有唯一性，用于前台获取数据
* `pid`：父级 id，用于建立数据表关系，与 id 字段映射
- 数据组成的几种可能
* 数据库真实存在数据
* 业务计算出的数据，非存储数据，如：统计数据
* Mongoose 支持的 virtual 虚拟数据
* 第三方模块提供数据，如：GitHub、Bilibili
### 应用结构
- 入口
* `main.ts`：引入配置，启动主程序，引入各种全局服务
* `app.module.ts`：主程序根模块，负责各业务模块的聚合
* `app.controller.ts`：主程序根控制器
* `app.config.ts`：主程序配置，数据库、程序、第三方，一切可配置项
* `app.environment.ts：`全局环境变量
- 请求处理流程
1. `request`：收到请求
2. `middleware`：中间件过滤（跨域、来源校验等处理）
3. `guard`：守卫过滤（鉴权）
4. `interceptor:before`：数据流拦截器（本应用为空，即：无处理）
5. `pipe`：参数提取（校验）器
6. `controller`：业务控制器
7. `service`：业务服务
8. `interceptor:after`：数据流拦截器（格式化数据、错误）
9. `filter`：捕获以上所有流程中出现的异常，如果任何一个环节抛出异常，则返回错误
- 鉴权处理流程
1. `guard`：[守卫](https://github.com/surmon-china/nodepress/blob/master/src/guards/auth.guard.ts) 分析请求
2. `guard.canActivate`：继承处理
3. `JwtStrategy.validate`：调用 [鉴权服务](https://github.com/surmon-china/nodepress/blob/master/src/modules/auth/jwt.strategy.ts#L25)
4. `guard.handleRequest`：[根据鉴权服务返回的结果作判断处理，通行或拦截](https://github.com/surmon-china/nodepress/blob/master/src/guards/auth.guard.ts#L11)
- 鉴权级别
* 任何高级操作（CUD）都会校验必须的 Token（代码见 [auth.guard.ts](https://github.com/surmon-china/nodepress/blob/master/src/guards/auth.guard.ts) ）
* 涉及表数据读取的 GET 请求会智能校验 Token，无 Token 或 Token 验证生效则通行，否则不通行（代码见 [humanized-auth.guard.ts](https://github.com/surmon-china/nodepress/blob/master/src/guards/humanized-auth.guard.ts) ）
- 参数校验逻辑（代码见 [query-params.decorator.ts](https://github.com/surmon-china/nodepress/blob/master/src/decorators/query-params.decorator.ts#L198) ）
* 普通用户使用高级查询参数将被视为无权限，返回 403
* 任何用户的请求参数不合法，将被校验器拦截，返回 400
- 错误过滤器（代码见 [error.filter.ts](https://github.com/surmon-china/nodepress/blob/master/src/filters/error.filter.ts) ）
- 拦截器 [interceptors](https://github.com/surmon-china/nodepress/tree/nest/src/interceptors)
* [缓存拦截器](https://github.com/surmon-china/nodepress/blob/master/src/interceptors/cache.interceptor.ts)：自定义这个拦截器是是要弥补框架不支持 ttl 参数的缺陷
* [数据流转换拦截器](https://github.com/surmon-china/nodepress/blob/master/src/interceptors/transform.interceptor.ts)：当控制器所需的 Promise service 成功响应时，将在此被转换为标准的数据结构
* [数据流异常拦截器](https://github.com/surmon-china/nodepress/blob/master/src/interceptors/error.interceptor.ts)：当控制器所需的 Promise service 发生错误时，错误将在此被捕获
* [日志拦截器](https://github.com/surmon-china/nodepress/blob/master/src/interceptors/logging.interceptor.ts)：代替默认的全局日志
- 装饰器扩展 [decorators](https://github.com/surmon-china/nodepress/tree/nest/src/decorators)
* [缓存装饰器](https://github.com/surmon-china/nodepress/blob/master/src/decorators/cache.decorator.ts)：用于配置 `cache key / cache ttl`
* [控制器响应装饰器](https://github.com/surmon-china/nodepress/blob/master/src/decorators/http.decorator.ts)：用于输出规范化的信息，如 `message` 和 翻页参数数据
* [请求参数提取器](https://github.com/surmon-china/nodepress/blob/master/src/decorators/query-params.decorator.ts)：用户自动校验和格式化请求参数，包括 `query/params/辅助信息`
- 守卫 [guards](https://github.com/surmon-china/nodepress/tree/nest/src/guards)
* 默认所有非 GET 请求会使用 [Auth](https://github.com/surmon-china/nodepress/blob/master/src/guards/auth.guard.ts) 守卫鉴权
* 所有涉及到多角色请求的 GET 接口会使用 [HumanizedJwtAuthGuard](https://github.com/surmon-china/nodepress/blob/master/src/guards/humanized-auth.guard.ts) 进行鉴权
- 中间件 [middlewares](https://github.com/surmon-china/nodepress/tree/nest/src/middlewares)
* [Cors 中间件](https://github.com/surmon-china/nodepress/blob/master/src/middlewares/cors.middleware.ts)，用于处理跨域访问
* [Origin 中间件](https://github.com/surmon-china/nodepress/blob/master/src/middlewares/origin.middleware.ts)，用于拦截各路不明请求
- 管道 [pipes](https://github.com/surmon-china/nodepress/tree/nest/src/pipes)
* validation.pipe 用于验证所有基于 class-validate 的验证类
- 业务模块 [modules](https://github.com/surmon-china/nodepress/tree/nest/src/modules)
* 公告
* 文章
* 分类
* 标签
* 评论
* 配置
* bilibili：Vlog 业务的请求
* 鉴权/登陆：全局鉴权业务和 Token 业务
* 点赞：点赞评论、文章、主站
* 音乐：播放器音乐数据业务
* [聚合供稿](https://github.com/surmon-china/nodepress/blob/master/src/modules/syndication/syndication.service.ts)：负责聚和信息的输出和写入，如 Sitemap、RSSXML
* 壁纸：主站每日壁纸模块业务
* 扩展模块
+ GitHub：GitHub 项目列表业务
+ 统计：业务数据统计业务
+ 备份：数据库备份业务（定时、手动）
+ 其他：其他第三方 token 等服务
- 核心辅助模块 [processors](https://github.com/surmon-china/nodepress/tree/nest/src/processors)
* [数据库](https://github.com/surmon-china/nodepress/blob/master/src/processors/database)
+ 连接数据库和异常自动重试
* [缓存 / Redis](https://github.com/surmon-china/nodepress/blob/master/src/processors/cache)
+ 基本的缓存数据 Set、Get
+ 扩展的 [Promise 工作模式](https://github.com/surmon-china/nodepress/blob/master/src/processors/cache/cache.service.ts#L99)（双向同步/被动更新）
+ 扩展的 [Interval 工作模式](https://github.com/surmon-china/nodepress/blob/master/src/processors/cache/cache.service.ts#L138)（超时更新/定时更新）
* [辅助 / Helper](https://github.com/surmon-china/nodepress/blob/master/src/processors/helper)
+ [搜索引擎实时更新服务](https://github.com/surmon-china/nodepress/blob/master/src/processors/helper/helper.service.seo.ts)：根据入参主动提交搜索引擎收录，支持百度、Google 服务；分别会在动态数据 进行 CUD 的时候调用对应方法
+ [评论过滤服务](https://github.com/surmon-china/nodepress/blob/master/src/processors/helper/helper.service.akismet.ts)：使用 akismet 过滤 spam；暴露三个方法：校验 spam、提交 spam、提交 ham
+ [邮件服务](https://github.com/surmon-china/nodepress/blob/master/src/processors/helper/helper.service.email.ts)：根据入参发送邮件；程序启动时会自动校验客户端有效性，校验成功则根据入参发送邮件
+ [IP 地理查询服务](https://github.com/surmon-china/nodepress/blob/master/src/processors/helper/helper.service.ip.ts)：根据入参查询 IP 物理位置；控制器内优先使用阿里云 IP 查询服务，当服务无效，~~使用本地 GEO 库查询~~，使用 ip.cn 等备用方案
+ [第三方云存储服务](https://github.com/surmon-china/nodepress/blob/master/src/processors/helper/helper.service.oss.ts)：生成云存储上传 Token（目前服务为 Aliyun OSS），后期可以添加 SDK 的更多支持，比如管理文件
+ Google 证书（鉴权）服务：用于生成各 Google 应用的服务端证书
## Special issues
#### Google Indexing API
- [完整的配置流程文档](https://developers.google.com/search/apis/indexing-api/v3/quickstart)
- 「 统计用户的所有者角色 」添加页面 [在这里](https://www.google.com/webmasters/verification/details?hl=zh-CN&domain=<xxx.com>)，而非 [新版的](https://search.google.com/search-console/users?resource_id=<xxx.com>)
#### Google Auth
- OAuth 2.0 客户端 ID、服务帐号密钥 都是 OAuth 授权类型
- [Auth 申请及管理页面](https://console.developers.google.com/apis/credentials)
#### Google Analytics Embed API
- [完整文档](https://developers.google.com/analytics/devguides/reporting/embed/v1/)
- [完整示例](https://ga-dev-tools.appspot.com/embed-api/)
- [服务端签发 token 鉴权示例](https://ga-dev-tools.appspot.com/embed-api/server-side-authorization/)
- [客户端 API 文档](https://developers.google.com/analytics/devguides/reporting/embed/v1/core-methods-reference)
- [将服务账户添加为 GA 的数据阅读者操作页面](https://marketingplatform.google.com/home/accounts)
## Development Setup
```bash
# 安装
$ yarn
# 开发
$ yarn start:dev
# 测试
$ yarn lint
$ yarn test
$ yarn test:e2e
$ yarn test:cov
$ yarn test:watch
# 构建
$ yarn build
# 生产环境运行
$ yarn start:prod
# 更新 GEO IP 库数据
$ yarn updategeodb
```
## Actions setup
**Rule:**
- `any PR open` -> `CI:Build test`
- `master PR closed & merged` -> `CI:Deploy to server`
**Example:**
- `local:develop -> remote:develop` -> `CI:Build test`
- `remote:develop/master -> remote:master -> merged` -> `CI:Deploy to server`
| 46.445415 | 217 | 0.730444 | yue_Hant | 0.357569 |
ff8814db0af8b79924ab2056c3b21bad9fc7b8a8 | 5,191 | md | Markdown | README.md | CMertens/reverse-proxy | dc2317d3bd2b1a88f4b60301fd1cef3539b36f35 | [
"BSD-2-Clause"
] | null | null | null | README.md | CMertens/reverse-proxy | dc2317d3bd2b1a88f4b60301fd1cef3539b36f35 | [
"BSD-2-Clause"
] | null | null | null | README.md | CMertens/reverse-proxy | dc2317d3bd2b1a88f4b60301fd1cef3539b36f35 | [
"BSD-2-Clause"
] | null | null | null | # A simple reverse proxy
This is a simple NodeJS-based reverse proxy that is suitable for development and test purposes. It allows for rapid testing and iteration of complex backend environments during development.
## Setup
Reverse-Proxy requires SSL to be set up. Key and certificate files should be placed in the ./ssl directory. You can trivially generate keys using openssl from the app directory:
openssl genrsa -out ./ssl/key.pem 2048
openssl req -new -sha256 -key ./ssl/key.pem -out ./ssl/csr.csr
openssl req -x509 -sha256 -days 365 -key ./ssl/key.pem -in ./ssl/csr.csr -out ./ssl/certificate.pem
Required directories and files are:
./paths
./ssl
./ssl/certificate.pem
./ssl/key.pem
./ssl/ca.pem (if using a custom CA)
./responses
## TLS Certificates
In addition to the default certificate and key, you can also place hostname-specific TLS certs in the ./ssl directory. Simply name the directory for the hostname, and the proxy will pick up and serve the certificates. The proxy expects "certificate.pem" and "key.pem" for its certs; if you're using a custom certificate authority, then include it as "ca.pem."
## Environment Variables
- PROXY_PORT: Port number to listen on.
- PROXY_MAX_CALLS_PER_SECOND: Global rate limit for API calls.
- PATH_FILE: Name of the "paths.json" file, as described below.
## path.json
The path.json file, if included, can define multiple paths. Each path uses a stringified regex value as the key, with an object containing configuration data about the path.
Each path object can take the following properties:
- to: (String, String[], Function, must be defined as an imported path module if a function is used. Required.
Where to proxy the request to. May be a string (servername or, if prefaced with 'file:', a local filename), array of strings (servernames), or a function that should return a string. If an array is provided, the proxy will randomly select one of the servers to contact; at this point, there is no concept of a proxy session, so round-robining between servers will not be "sticky" for a user.
- priority: (Int) If included, indicates the relative priority of the path, where lower is higher-priority. If not included, the path is assumed to have the lowest possible priority, and will only be matched if it is the first match for the path.
- hostnames: (String[]) An optional array of requested hostnames that must be matched (using the client host request header). If not present or a zero-length array, the host header will be ignored.
- rewriteRequest: (Function, must be defined as an imported path module) A function to rewrite the ProxyRequest object, if needed. This may return a string, an value that implements the toString() method, or a Promise, whose resolution will be treated as a string or toString()able value. See the examples in the ./paths directory to see how this works in practice.
- rewriteResponse: (Function, must be a path import) A function to rewrite the proxied response. Note that currently this does not allow interception of the proxied response, so use of this function should be limited to header writing. Use "rewriteRequest" to intercept the request if you need to do more complex proxying logic.
- secure: (Boolean) Whether the target is TLS-secured. False if not provided.
- websocket: (Boolean) Whether the target is a websocket. False if not provided.
- allowedCidrs: (String[]) A list of CIDRs to allow. If the array is empty, no one will be able to access the endpoint. If allowedCidrs does not exist or is not an array, all requests will be serviced.
- ignoreProxiedIP: (Boolean) If false or undefined, both the IP the request comes from and the content of the X-Forwarded-For header will be checked against the allow-list (if allowedCidrs is populated). If true, then the content of X-Forwarded-For will not be checked. The default is more restrictive (e.g., both the request origin and the proxied orgin must be allowed.)
- contentType: (String) If included, will override content-type for static files and return functions.
- enableCors: (Boolean) Add CORS headers to the response (non-Websockets only).
- onRequest: (Function, must be defined as an imported path module) A function to run before any response is returned. Useful for validating requirements such as X-Api-Key header values. Return "true" to allow processing to continue; any other response will trigger a 403 error to the client.
## Path Module Exports
Path objects can also be defined in code by creating module exports in the ./paths directory. Simply add the path regex as a key to the "exports" object, with the value of a path object as described above, in any file in ./paths, and the proxy will auto-discover the new paths.
## Examples
The code repo comes with some sample paths in both paths.json and the ./paths directory.
## Static Responses
If you wish to return custom HTML responses to various error codes generated by the proxy (e.g., 404, 502, etc.), simply add the HTML to the ./responses directory, with the filename in the format "{HTTP response code}.html."
## License
2-clause BSD. See license.txt for the official license details. | 77.477612 | 395 | 0.76729 | eng_Latn | 0.998937 |
ff88f19495f8b2fe0ae1b14530a28acc2780db96 | 3,568 | md | Markdown | screenshots/index.md | IncaProject/IncaProject.github.io | d22c72be78430fc9f4f9d27c728aa612db51094d | [
"MIT"
] | null | null | null | screenshots/index.md | IncaProject/IncaProject.github.io | d22c72be78430fc9f4f9d27c728aa612db51094d | [
"MIT"
] | null | null | null | screenshots/index.md | IncaProject/IncaProject.github.io | d22c72be78430fc9f4f9d27c728aa612db51094d | [
"MIT"
] | null | null | null | ---
layout: archive
title: Screenshots
---
<p>The following are screenshots of Inca data consumers. For live examples, visit our <a href="/users">Inca users</a> page.</p>
<ul>
<li><a href="#map">Map View using Google Map API</a></li>
<li><a href="#sum"> Tabular Suite Summary View</a></li>
<li><a href="#detail">Test Detail View </a></li>
<li><a href="#hist">Historical Views</a></li>
<li><a href="#reports">Reports</a></li>
</ul>
<h3><a name="map"></a>Map View using Google Map API </h3>
<p>The map view provides a summary view of the current status of resources on a Google map. For each resource, the summary view will provide the percentage of reports passed, number of passed reports, number of failed reports, and a list of the failed tests (with a link to the report details page). A resource is represented on the map as a marker and colored red, green, or orange based on the number of tests that have passed and/or failed. The figure below shows the Inca Google map view for the NEON testbed (four resources at SDSC and one resource at James Reserve). All resources are passing their tests so every resource marker is green.</p>
<p><img src="map1.png" alt="google map view" border="0" /></p>
<p>Clicking on a marker will display an info window with the name of the resource and the status information as show below.</p>
<p><img src="map2.png" alt="google map view" border="0" /></p>
<p>Clicking on the "Toggle ping status" button will display the status of the cross-site ping test as show below.</p>
<p><img src="map3.png" alt="google map view" border="0" /></p>
<h3><a name="sum"></a>Tabular Suite Summary View </h3>
<p>A summary table of test suite results with links to test detail pages:</p>
<p><img src="table.jpg" alt="tabular suite summary" border="0" /></p>
<h3><a name="detail"></a>Test Detail View </h3>
<p>Test execution detail view:</p>
<p><img src="details.jpg" alt="test details" border="0" /></p>
<h3><a name="hist"></a>Historical Views </h3>
<p>Customizable graphs of test status history and distribution of test error types:</p>
<p><img src="graph1.jpg" alt="historical graphs" border="0" /></p>
<p>Customizable graphs of test status history and distribution of test error types:</p>
<p><img src="2.3graph.png" alt="historical graphs" border="0" /></p>
<p><img src="2.3hist.png" alt="historical graphs" border="0" /></p>
<h3><a name="reports"></a>Reports </h3>
<p>Historical summary reports with pass/fail status and error information:</p>
<p><img src="summary_report.jpg" alt="Pass/Fail Graphs and Error Messages" border="0" /></p>
<p>Average series pass rate by resource and suite for the past week. Each bar label shows the value of the average series pass rate for the last week and the difference in percentage from the previous week:</p>
<p><img src="summaryJsp.gif" alt="Average Pass Rate by Resource/Suite" border="0" /></p>
<p>More detailed report for resource/suite (linked from report above):</p>
<p><img src="summaryDetailsJsp.gif" alt="Detailed Report for Resource/Suite" border="0" /></p>
<p>Summary of test series errors by time period. Each time period includes the number of errors for the series during the time period, the number of unique or distinct errors during the period, and the percentage of the total results that passed during the period:</p>
<p><img src="error-summary.gif" alt="Series Error Summary" border="0" /></p>
<p>Average series pass rate over time grouped by resource and suite:</p>
<p><img src="summaryHistoryJsp.gif" alt="Average Pass History" border="0" /></p>
| 47.573333 | 649 | 0.715807 | eng_Latn | 0.919538 |
ff89258a8f6ae3dc687a15d695a9cbc3b0b0e2fb | 1,359 | md | Markdown | README.md | VictorJorgeFGA/LOL_Gym | 2d3cf954e6f187915bd8221964ada29e8f2b1d70 | [
"MIT"
] | null | null | null | README.md | VictorJorgeFGA/LOL_Gym | 2d3cf954e6f187915bd8221964ada29e8f2b1d70 | [
"MIT"
] | null | null | null | README.md | VictorJorgeFGA/LOL_Gym | 2d3cf954e6f187915bd8221964ada29e8f2b1d70 | [
"MIT"
] | null | null | null | # LOL_Gym
## Description
_LoL Gym_ is a personal project which implements a blog for the League of Legends game. It's a multi-purpose blog where users can share and receive knowledge about [_League of Legends_](https://na.leagueoflegends.com/en-us/), interacting with each other whenever possible.
## Documentation
You can verify what was done on each project's phase by reading the documents below.
### Requeriments Elicitation
Elicitation is an extremely important phase for Software Product development. For this project's purpose (a personal one), elicitation is squeezed into one unique activity: [_introspection_](http://advat.blogspot.com/2016/11/a-walkthrough-of-requirement.html).
> [Elicitation Document](documents/elicitation.md)
### Requirements Prioritization
Although this is a personal - and relatively small - project, [prioritization](https://en.wikipedia.org/wiki/Requirement_prioritization#:~:text=Requirement%20prioritization%20is%20used%20in,risk%20requirements%20are%20implemented%20first.) takes a big role in the project's planning and it won't be let out.
> [Prioritization Document](documents/prioritization.md)
### Requirements Validation
Once the project is finished, it's necessary to check if it fulfills elicited requirements.
> [Requirements Validation](documents/validation.md)
## License
[MIT License](LICENSE) | 43.83871 | 307 | 0.796174 | eng_Latn | 0.979208 |
ff89837c6c8efefa685b7ddcc65433b974f1033c | 13,608 | md | Markdown | msix-src/packaging-tool/generate-template-file.md | SFlying/msix-docs.zh-cn | 73bd05cd0db62226ade94b07a3cc6be1ba96e9ed | [
"CC-BY-4.0",
"MIT"
] | null | null | null | msix-src/packaging-tool/generate-template-file.md | SFlying/msix-docs.zh-cn | 73bd05cd0db62226ade94b07a3cc6be1ba96e9ed | [
"CC-BY-4.0",
"MIT"
] | null | null | null | msix-src/packaging-tool/generate-template-file.md | SFlying/msix-docs.zh-cn | 73bd05cd0db62226ade94b07a3cc6be1ba96e9ed | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 如何生成用于命令行转换的模板文件
description: 本文介绍了如何为命令行转换生成模板文件。
ms.date: 01/28/2020
ms.topic: article
keywords: msix
ms.localizationpriority: medium
ms.openlocfilehash: 00c7997673f6c0ed3fc79f425c90e283b7a1f25c
ms.sourcegitcommit: 4d912f89e385268757e87bf8fd9ca1828b99e109
ms.translationtype: MT
ms.contentlocale: zh-CN
ms.lasthandoff: 02/21/2020
ms.locfileid: "77544614"
---
# <a name="how-to-generate-a-template-file-for-command-line-conversions"></a>如何生成用于命令行转换的模板文件
使用 .MSIX 打包工具，可以通过两种方式执行转换：通过交互 UI 或通过我们的命令行选项。 使用命令行时，需要提供模板文件，以便该转换可用于特定的设置和需求。 本文将指导你完成生成适用于你的模板文件的过程。
可以通过两种方式获取适用于你的模板文件：
* 可以使用 .MSIX 打包工具的 UI。 在工具设置中，可以指定要使用创建的每个 .MSIX 包生成转换模板文件。
* 您可以获取一个[示例模板](#sample-conversion-template-file)，并手动输入每个转换所需的配置。
## <a name="generate-a-conversion-template-file-from-the-msix-packaging-tool"></a>从 .MSIX 打包工具生成转换模板文件
1. 启动 .MSIX 打包工具。
2. 请在应用程序的右上角中转到 "设置"。
3. 请确保选中 "生成包含每个包的命令行文件" 选项。
4. 对所需的设置进行其他更改或修改（例如排除项、退出代码）。
5. 保存设置
6. 使用安装程序浏览应用程序包工作流。
- 如果未选择安装程序，则将无法生成转换模板文件。
- 如果使用的是 exe，则需要将缄默标志传递到安装程序以生成转换模板文件。
7. 在转换结束时，你将拥有一个基于所选安装程序配置的模板文件，以及你现在可以用于将来转换的当前设置。
- 默认情况下，转换模板文件将保存在与 .MSIX 包相同的位置，但你可以在 "创建包" 页上为模板文件指定单独的保存位置。
- 你仍需要根据要在每次转换结束时输出的 .MSIX 进行一些修改。
## <a name="manually-edit-the-conversion-template-file"></a>手动编辑转换模板文件
你可以手动编辑转换模板文件的模板参数，以生成适合你的模板文件。 生成转换模板文件时，请注意要添加到模板文件中的功能，因为某些功能可能需要其他架构引用才能正常工作。
### <a name="conversion-template-parameter-reference"></a>转换模板参数引用
下面是可以在转换模板文件中使用的参数的完整列表。
|**ConversionSettings** | **描述** |
|---------|---------|
|Settings：： AllowTelemetry | [可选] 为此工具调用启用遥测日志记录。|
|Settings：： ApplyAllPrepareComputerFixes | [可选] 应用所有建议的“准备计算机”修复程序。 使用其他特性时不能设置此参数。|
|Settings：： GenerateCommandLineFile | [可选] 将模板文件输入复制到 SaveLocation 目录，供将来使用。|
|Settings：： AllowPromptForPassword | [可选] 指示工具提示用户输入虚拟机和签名证书的密码（如果必须提供密码，但未指定密码）。|
|Settings：： EnforceMicrosoftStoreVersioningRequirements | [可选] 指示工具强制实施从 Microsoft Store 和适用于企业的 Microsoft Store 进行部署所需的包版本控制方案。|
|Settings：： ServerPortNumber| 可有可无连接到远程计算机时使用。 需要模板架构的 v2。|
|Settings：： AddPackageIntegrity| 可有可无将包完整性添加到每个生成的 .MSIX 中。 需要模板架构的 v5。 |
|ValidInstallerExitCodes | [可选] 0 个或多个 ValidInstallerExitCode 元素。 需要模板架构的 v2。 |
|ValidInstallerExitCodes:: ValidInstallerExitCode | 可有可无指定该工具可能不熟悉或需要重新启动的任何安装程序退出代码。 需要模板架构的 v2。 |
|ValidInstallerExitCodes：： ValidInstallerExitCode：： Reboot | 可有可无指定在转换过程中退出代码是否应触发重新启动。 需要模板架构的 v3。 |
|ExclusionItems | [可选] 0 个或更多 FileExclusion 或者 RegistryExclusion 元素。 所有 FileExclusion 元素必须出现在任何 RegistryExclusion 元素之前。|
|ExclusionItems::FileExclusion | [可选] 不要打包的文件。|
|ExclusionItems::FileExclusion::ExcludePath | 不要打包的文件的路径。|
|ExclusionItems::RegistryExclusion | [可选] 不要打包的注册表项。|
|ExclusionItems::RegistryExclusion:: ExcludePath | 不要打包的注册表的路径。|
|PrepareComputer::DisableDefragService | [可选] 转换应用时禁用 Windows 碎片整理程序。 如果设置为 false，则会重写 ApplyAllPrepareComputerFixes。|
|PrepareComputer:: DisableWindowsSearchService | [可选] 转换应用时禁用 Windows Search。 如果设置为 false，则会重写 ApplyAllPrepareComputerFixes。|
|PrepareComputer:: DisableSmsHostService | [可选] 转换应用时禁用 SMS 主机。 如果设置为 false，则会重写 ApplyAllPrepareComputerFixes。|
|PrepareComputer:: DisableWindowsUpdateService | [可选] 转换应用时禁用 Windows 更新。 如果设置为 false，则会重写 ApplyAllPrepareComputerFixes。|
|SaveLocation | [可选] 用于指定工具保存位置的元素。 如果未指定，包将保存在“桌面”文件夹中。 |
|SaveLocation::PackagePath | [可选] 生成的 MSIX 包要保存到的文件或文件夹的路径。 |
|SaveLocation::TemplatePath | 可有可无保存生成的命令行模板的文件或文件夹的路径。 |
|Installer::Path | 应用程序安装程序的路径。|
|Installer::Arguments | [可选] 要传递给安装程序的参数。 该工具将使用参数“/qn /norestart INSTALLSTARTMENUSHORTCUTS=1 DISABLEADVTSHORTCUTS=1”以无提示方式自动运行 MSI 安装程序。 注意：如果你使用的是 .exe 安装程序，则必须传递参数以强制自动运行安装程序。|
|Installer::InstallLocation | 可有可无如果安装的文件已安装（例如 "C:\Program Files （x86） \MyAppInstalllocation"），则为该应用程序的根文件夹的完整路径。|
|VirtualMachine | [可选] 用于指定要在本地虚拟机上运行转换的元素。|
|VirtualMachine：： Name | 要用于转换环境的虚拟机的名称。|
|VirtualMachine::Username | 用于转换环境的虚拟机的用户名。|
|RemoteMachine | 可有可无一个元素，用于指定将在远程计算机上运行转换。 需要模板架构的 v2。 |
|RemoteMachine：： ComputerName | 用于转换环境的远程计算机的名称。 需要模板架构的 v2。 |
|RemoteMachine：： Username | 用于转换环境的远程计算机的用户名。 需要模板架构的 v2。 |
|RemoteMachine：： EnableAutoLogon | 可有可无当执行需要在远程计算机上重启的转换以便无缝地继续转换时，这将自动登录回。 需要模板架构的 V3。 |
|PackageInformation::PackageName | MSIX 包的名称。|
|PackageInformation::PackageDisplayName | MSIX 包的显示名称。|
|PackageInformation::PublisherName | MSIX 包的发布者。|
|PackageInformation::PublisherDisplayName | MSIX 包的发布者显示名称。|
|PackageInformation::Version | MSIX 包的版本号。|
|PackageInformation：:P ackageDescription | 可有可无.MSIX 包的说明。 需要模板架构的 v4。 |
|PackageInformation:: MainPackageNameForModificationPackage | [可选] 主包名称的包标识名称。 创建依赖于主（父）应用程序的修改包时，将使用此参数。|
|SigningInformation| 可有可无一个元素，用于指定 Device Guard 签名的签名信息。 需要模板架构的 v4。 |
|SigningInformation:: DeviceGuardSigning | 可有可无用于指定设备保护签名信息的元素。 需要模板架构的 v4。 |
|DeviceGuardSigning:: TokenFile | 采用 JSON 格式进行设备保护签名[所需的 Azure AD 访问令牌](../package/signing-package-device-guard-signing.md#get-an-azure-ad-access-token)。 需要 v4 模板架构。 |
|DeviceGuardSigning:: TimestampUrl | 可有可无在使用 Device Guard 进行签名时提供时间戳，以确保你的应用程序将在证书的生存期之外安装。 需要模板架构的 v4。 |
|应用程序 | [可选] 用于在 MSIX 包中配置应用程序条目的 0 个或多个 Application 元素。|
|Application::Id | MSIX 应用程序的应用 ID。 此 ID 将用于检测到的、与指定的 ExecutableName 匹配的应用程序条目。 可为包中的可执行文件提供多个应用程序 ID 值。<br/><br/>此值是包中应用程序的唯一标识符。 此值有时称作“包相对应用标识符”(PRAID)。 该 ID 必须在包中唯一（同一个 ID 不能在同一个包中多次使用）。 但是，该 ID 不一定全局唯一。 系统中可以有另一个包使用相同的 ID。<br/><br/>此字符串包含句点分隔的字母数字字段。 每个字段必须以 ASCII 字母字符开头。 不能将它们用作字段值： "CON"、"PRN"、"AUX"、"NUL"、"COM1"、"COM2"、"COM3"、"COM4"、"COM5"、"COM6"、"COM7"、"COM8"、"COM9"、"LPT1"、"LPT2"、"LPT3"、"LPT4"、"LPT5"、"LPT6"、"LPT7"、"LPT8"、"LPT9" 和 ""。|
|Application::DisplayName | MSIX 包的应用显示名称。 此显示名称将用于检测到的、与指定的 ExecutableName 匹配的应用程序条目|
|Application::ExecutableName | 要添加到包清单的 MSIX 应用程序的可执行文件名称。 如果检测不到具有此名称的应用程序，则会忽略相应的应用程序条目。|
|Application::Description | [可选] MSIX 应用程序的应用说明。 如果不使用此参数，将使用应用程序显示名称。 此说明将用于检测到的、与指定的 ExecutableName 匹配的应用程序条目|
|功能 | [可选] 用于将自定义功能添加到 MSIX 包的 0 个或多个 Capability 元素。 在转换期间，默认会添加“runFullTrust”功能。|
|Capability::Name | 添加到 MSIX 包的功能。 |
### <a name="sample-conversion-template-file"></a>示例转换模板文件
```xml
<MsixPackagingToolTemplate
xmlns="http://schemas.microsoft.com/appx/msixpackagingtool/template/2018"
xmlns:V2="http://schemas.microsoft.com/msix/msixpackagingtool/template/1904"
xmlns:V3="http://schemas.microsoft.com/msix/msixpackagingtool/template/1907"
xmlns:V4="http://schemas.microsoft.com/msix/msixpackagingtool/template/1910"
xmlns:V5="http://schemas.microsoft.com/msix/msixpackagingtool/template/2001">
<!--Note: You only need to include xmlns:v2 - xmlns:v5 if you are using one of the features that use those schemas -->
<Settings
AllowTelemetry="true"
ApplyAllPrepareComputerFixes="true"
GenerateCommandLineFile="true"
AllowPromptForPassword="false"
EnforceMicrosoftStoreVersioningRequirements="false"
v2:ServerPortNumber="1599"
v5:AddPackageIntegrity="true">
<!--Note: Exclusion items are optional and if declared take precedence over the default tool exclusion items
<ExclusionItems>
<FileExclusion ExcludePath="[{CryptoKeys}]" />
<FileExclusion ExcludePath="[{Common AppData}]\Microsoft\Crypto" />
<FileExclusion ExcludePath="[{Common AppData}]\Microsoft\Search\Data" />
<FileExclusion ExcludePath="[{Cookies}]" />
<FileExclusion ExcludePath="[{History}]" />
<FileExclusion ExcludePath="[{Cache}]" />
<FileExclusion ExcludePath="[{Personal}]" />
<FileExclusion ExcludePath="[{Profile}]\Local Settings" />
<FileExclusion ExcludePath="[{Profile}]\NTUSER.DAT.LOG1" />
<FileExclusion ExcludePath="[{Profile}]\ NTUSER.DAT.LOG2" />
<FileExclusion ExcludePath="[{Recent}]" />
<FileExclusion ExcludePath="[{Windows}]\debug" />
<FileExclusion ExcludePath="[{Windows}]\Logs\CBS" />
<FileExclusion ExcludePath="[{Windows}]\Temp" />
<FileExclusion ExcludePath="[{Windows}]\WinSxS\ManifestCache" />
<FileExclusion ExcludePath="[{Windows}]\WindowsUpdate.log" />
<FileExclusion ExcludePath="[{Windows}]\Installer" />
<FileExclusion ExcludePath="[{AppVPackageDrive}]\$Recycle.Bin " />
<FileExclusion ExcludePath="[{AppVPackageDrive}]\System Volume Information" />
<FileExclusion ExcludePath="[{AppVPackageDrive}]\Config.Msi" />
<FileExclusion ExcludePath="[{AppData}]\Microsoft\AppV" />
<FileExclusion ExcludePath="[{Common AppData}]\Microsoft\Microsoft Security Client" />
<FileExclusion ExcludePath="[{Common AppData}]\Microsoft\Microsoft Antimalware" />
<FileExclusion ExcludePath="[{Common AppData}]\Microsoft\Windows Defender" />
<FileExclusion ExcludePath="[{ProgramFiles}]\Microsoft Security Client" />
<FileExclusion ExcludePath="[{ProgramFiles}]\Windows Defender" />
<FileExclusion ExcludePath="[{ProgramFiles}]\WindowsApps" />
<FileExclusion ExcludePath="[{Local AppData}]\Temp" />
<FileExclusion ExcludePath="[{Local AppData}]\Microsoft\Windows" />
<FileExclusion ExcludePath="[{Local AppData}]\Packages" />
<RegistryExclusion ExcludePath= "REGISTRY\MACHINE\SOFTWARE\Wow6432Node\Microsoft\Cryptography" />
<RegistryExclusion ExcludePath= "REGISTRY\MACHINE\SOFTWARE\Microsoft\Cryptography" />
<RegistryExclusion ExcludePath= "REGISTRY\MACHINE\SOFTWARE\Microsoft\Microsoft Antimalware" />
<RegistryExclusion ExcludePath= "REGISTRY\MACHINE\SOFTWARE\Microsoft\Microsoft Antimalware Setup" />
<RegistryExclusion ExcludePath= "REGISTRY\MACHINE\SOFTWARE\Microsoft\Microsoft Security Client" />
<RegistryExclusion ExcludePath= "REGISTRY\MACHINE\SOFTWARE\Policies\Microsoft\Microsoft Antimalware" />
<RegistryExclusion ExcludePath= "REGISTRY\MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender" />
<RegistryExclusion ExcludePath= "REGISTRY\USER\[{AppVCurrentUserSID}]\Software\Microsoft\Windows\CurrentVersion\Explorer\StreamMRU" />
<RegistryExclusion ExcludePath= "REGISTRY\USER\[{AppVCurrentUserSID}]\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Explorer\StreamMRU" />
<RegistryExclusion ExcludePath= "REGISTRY\USER\[{AppVCurrentUserSID}]\Software\Microsoft\Windows\CurrentVersion\Explorer\Streams" />
<RegistryExclusion ExcludePath= "REGISTRY\USER\[{AppVCurrentUserSID}]\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Explorer\Streams" />
<RegistryExclusion ExcludePath= "REGISTRY\MACHINE\SOFTWARE\Microsoft\AppV" />
<RegistryExclusion ExcludePath= "REGISTRY\MACHINE\SOFTWARE\Wow6432Node\Microsoft\AppV" />
<RegistryExclusion ExcludePath= "REGISTRY\USER\[{AppVCurrentUserSID}]\Software\Microsoft\AppV" />
<RegistryExclusion ExcludePath= "REGISTRY\USER\[{AppVCurrentUserSID}]\Software\Wow6432Node\Microsoft\AppV" />
</ExclusionItems>
-->
<!--Note: Specifying an installer exit code will allow you to automatically trigger a reboot during your conversion
<v2:ValidInstallerExitCodes>
<V2:ValidInstallerExitCode ExitCode="3010" V3:Reboot="true"/>
<V2:ValidInstallerExitCode ExitCode="1641"/>
</v2:ValidInstallerExitCodes>
-->
</Settings>
<!--Note: this section takes precedence over the Settings::ApplyAllPrepareComputerFixes attribute and is optional
<PrepareComputer
DisableDefragService="true"
DisableWindowsSearchService="true"
DisableSmsHostService="true"
DisableWindowsUpdateService="true"/>
-->
<SaveLocation
PackagePath="C:\users\user\Desktop\MyPackage.msix"
TemplatePath="C:\users\user\Desktop\MyTemplate.xml" />
<Installer
Path="C:\MyAppInstaller.msi"
InstallLocation="C:\Program Files\MyAppInstallLocation" />
<!--NOTE: This section specifies that the conversion will be run on a local Virtual Machine. This is optional if you want to change your conversion environment from the default local machine.
<VirtualMachine Name="vmname" Username="vmusername"/>
-->
<!--NOTE: This section specifies that the conversion will be run on a remote machine.This is optional if you want to change your conversion environment from the default local machine.
<v2:RemoteMachine ComputerName="vmname" Username="vmusername" v3:EnableAutoLogon="true"/>
-->
<PackageInformation
PackageName="MyAppPackageName"
PackageDisplayName="MyApp Display Name"
PublisherName="CN=MyPublisher"
PublisherDisplayName="MyPublisher Display Name"
Version="1.1.0.0"
MainPackageNameForModificationPackage="MainPackageIdentityName">
<!--Note: This is optional, if you want to sign your package with Device Guard signing
<v4:SigningInformation>
<v4:DeviceGuardSigning
Tokenfile="tokenfile.json"
TimestampUrl="https://mytimestamp.com"/>
</v4:SigningInformation>
-->
<!--NOTE: This ID will be used if the Application entry detected matches the specified ExecutableName
<Applications>
<Application
Id="MyApp1"
Description="MyApp"
DisplayName="My App"
ExecutableName="MyApp.exe"/>
</Applications>
-->
<!--NOTE: This is optional as “runFullTrust” capability is added by default during conversion
<Capabilities>
<Capability Name="runFullTrust" />
</Capabilities>
-->
</PackageInformation>
</MsixPackagingToolTemplate>
```
| 57.176471 | 446 | 0.729718 | yue_Hant | 0.949516 |
ff8a1c14c94c91b2b8cc96139fa06474c9994f6f | 336 | md | Markdown | README.md | Bruflot/wm-rs | 00d28997eb4fb2006df462b74a0600e96ad431b2 | [
"MIT"
] | 2 | 2019-09-28T15:28:06.000Z | 2020-01-22T13:05:28.000Z | README.md | Bruflot/wm-rs | 00d28997eb4fb2006df462b74a0600e96ad431b2 | [
"MIT"
] | null | null | null | README.md | Bruflot/wm-rs | 00d28997eb4fb2006df462b74a0600e96ad431b2 | [
"MIT"
] | null | null | null | # wm-rs
[](https://tokei.rs/b1/github/bruflot/wm-rs)
a highly customizable, minimal x11 window manager
wip
## Features
- [x] Basic functionality (connect to X, open windows)
- [ ] Resize windows
- [ ] Multiple screens
- [ ] Customizable layout through scripting
- [ ] Handling keybinds
| 24 | 89 | 0.705357 | eng_Latn | 0.673764 |
ff8a73e76226113253ae19d0903cbb24dabb7280 | 1,431 | md | Markdown | includes/core-changes/versionselector.md | adamsitnik/docs.pl-pl | c83da3ae45af087f6611635c348088ba35234d49 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | includes/core-changes/versionselector.md | adamsitnik/docs.pl-pl | c83da3ae45af087f6611635c348088ba35234d49 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | includes/core-changes/versionselector.md | adamsitnik/docs.pl-pl | c83da3ae45af087f6611635c348088ba35234d49 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
ms.openlocfilehash: b366c44fdf1a4b2e908b41aeff2037be63bdf7e1
ms.sourcegitcommit: 5a28f8eb071fcc09b045b0c4ae4b96898673192e
ms.translationtype: MT
ms.contentlocale: pl-PL
ms.lasthandoff: 10/31/2019
ms.locfileid: "73198531"
---
> [!div class="op_multi_selector" title1="Z wersji docelowej" title2="Do zmigrowanej wersji"]
>
> - [(.NET Framework |. Rdzeń netto)](~/docs/core/compatibility/framework-core.md)
> - [(2,2 | 3,0)](~/docs/core/compatibility/2.2-3.0.md)
> - [(3,0 wersja zapoznawcza 6 | 3,0 wersja zapoznawcza 7)](~/docs/core/compatibility/3.0.6-3.0.7.md)
> - [(3,0 wersja zapoznawcza 7 | 3,0 wersja zapoznawcza 8)](~/docs/core/compatibility/3.0.7-3.0.8.md)
> - [(3,0 wersja zapoznawcza 8 | 3,0 wersja zapoznawcza 9)](~/docs/core/compatibility/3.0.8-3.0.9.md)
> - [(3,0 wersja zapoznawcza 9 | 3,0 RC1)](~/docs/core/compatibility/3.0.9-3.0rc1.md)
<!--
> - [(2.2 | 3.0 Preview 7)](~/docs/core/compatibility/2.2-3.0.7.md)
> - [(2.2 | 3.0 Preview 8)](~/docs/core/compatibility/2.2-3.0.8.md)
> - [(2.2 | 3.0 Preview 9)](~/docs/core/compatibility/2.2-3.0.9.md)
> - [(3.0 Preview 7| 3.0 Preview 9)](~/docs/core/compatibility/3.0.7-3.0.9.md)
> - [(3.0 Preview 7| 3.0)](~/docs/core/compatibility/3.0.7-3.0.md)
> - [(3.0 Preview 8| 3.0 Preview 9)](~/docs/core/compatibility/3.0.8-3.0.9.md)
> - [(3.0 Preview 8| 3.0)](~/docs/core/compatibility/3.0.8-3.0.md)
> - [(3.0 Preview 9| 3.0)](~/docs/core/compatibility/3.0.9-3.0.md)
-->
| 47.7 | 101 | 0.666667 | yue_Hant | 0.615115 |
ff8a85a6997db4efe0ac38afab3d54716c33f86f | 1,620 | md | Markdown | api/overview/command-button-control.md | qiezhenxi/VBA-Docs | c49aebcccbd73eadf5d1bddc0a4dfb622e66db5d | [
"CC-BY-4.0",
"MIT"
] | 1 | 2018-10-15T16:15:38.000Z | 2018-10-15T16:15:38.000Z | api/overview/command-button-control.md | qiezhenxi/VBA-Docs | c49aebcccbd73eadf5d1bddc0a4dfb622e66db5d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | api/overview/command-button-control.md | qiezhenxi/VBA-Docs | c49aebcccbd73eadf5d1bddc0a4dfb622e66db5d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Command Button Control
keywords: vbaac10.chm5186555
f1_keywords:
- vbaac10.chm5186555
ms.prod: access
ms.assetid: aea2b8e8-2249-0055-472f-e67b86044669
ms.date: 06/08/2017
---
# Command Button Control
**Applies to:** Access 2013 | Access 2016
A command button on a form can start an action or a set of actions. For example, you could create a command button that opens another form. To make a command button do something, you write a macro or event procedure and attach it to the button's **OnClick** property.
## Remarks
You can display text on a command button by setting its **Caption** property, or you can display a picture by setting its **Picture** property.
> [!TIP]
> You can create over 30 different types of command buttons with the Command Button Wizard. When you use the Command Button Wizard, Microsoft Access creates the button and the event procedure for you.
## See also
- [Access for developers forum](https://social.msdn.microsoft.com/Forums/office/home?forum=accessdev)
- [Access help on support.office.com](https://support.office.com/search/results?query=Access)
- [Access help on answers.microsoft.com](https://answers.microsoft.com/)
- [Search for specific Access error codes on Bing](https://www.bing.com/)
- [Access forums on UtterAccess](https://www.utteraccess.com/forum/index.php?act=idx)
- [Access wiki on UtterAcess](https://www.utteraccess.com/forum/index.php?act=idx)
- [Access developer and VBA programming help center (FMS)](https://www.fmsinc.com/MicrosoftAccess/developer/)
- [Access posts on StackOverflow](https://stackoverflow.com/questions/tagged/ms-access)
| 43.783784 | 267 | 0.766049 | eng_Latn | 0.831939 |
ff8ae3823521c9d8d70ec3fbf9a5510ba2b5912e | 10,825 | md | Markdown | _posts/2020-02-14-inspirasi-tokoh-tokoh-mata-pena-bagian-1.md | kulacino/kulacino.github.io | caaac94019a93972bae96cecf3affc4270f59438 | [
"MIT"
] | null | null | null | _posts/2020-02-14-inspirasi-tokoh-tokoh-mata-pena-bagian-1.md | kulacino/kulacino.github.io | caaac94019a93972bae96cecf3affc4270f59438 | [
"MIT"
] | null | null | null | _posts/2020-02-14-inspirasi-tokoh-tokoh-mata-pena-bagian-1.md | kulacino/kulacino.github.io | caaac94019a93972bae96cecf3affc4270f59438 | [
"MIT"
] | null | null | null | ---
layout: post
title: Inspirasi Tokoh-tokoh Mata Pena (Bagian 1)
date: '2020-02-14T04:09:00.000+07:00'
author: Ayu Welirang
tags: Personal
modified_time: '2020-02-18T14:04:35.299+07:00'
thumbnail: https://1.bp.blogspot.com/proxy/Fe6M42o-x3HMQHg6d830x-WZADhBelw3vWgERJigZv0buRtcG5yH1nvxX3fjaxPclzxBuDIV8CMPNhgn7eVDdEq5BoipwAywSIBRX5TmtAA5BwTwxi3PJeH0eli_hcuQjnq9nK_8OE-Qj0LnmxbMWIcQIJxn=s72-c
blogger_id: tag:blogger.com,1999:blog-2864133486354662221.post-3196545963207380542
blogger_orig_url: http://www.ayuwelirang.com/2020/02/inspirasi-tokoh-tokoh-mata-pena-bagian-1.html
---
<div style="text-align: justify;">Saat saya memulai sebuah kerangka novel, saya tak tahan kalau tak membuat daftar tabel untuk para karakter. Kadang kala, daftar karakter ini malah lebih saya ulik daripada kerangka novel itu sendiri. Tak lupa saya selalu menyelipkan foto-foto tokoh, agar saya selalu ingat gambaran fisik tokoh-tokoh di novel yang sedang saya garap. <i><strike>Apalagi kalau ada tokoh gondrong dan hmmm... itu kayak tokoh kesukaan saya...</strike></i></div><div style="text-align: justify;"><i><strike><br /></strike></i></div><div style="text-align: justify;">Nah, kali ini saya ingin berbagi beberapa gambaran karakter, yang mungkin malah luput ditebar dalam novel. Di Mata Pena, tokoh-tokohnya cukup banyak, karena memang banyak bercerita tentang interaksi para pekerja media cetak. Namun, saya sendiri tak lihai membeberkan ciri-ciri karakter, karena kadang memakan terlalu banyak tempat dalam novel. Oleh karena itu, di Mata Pena sendiri, ciri-ciri karakternya tidak banyak dikeluarkan kecuali untuk tokoh utama. Jadi, bagaimana dong nasib tokoh pendukung?</div><div style="text-align: justify;"><br /></div><div style="text-align: justify;">Agar kita semua nantinya tidak akan lupa pada nasib tokoh pendukung, maka saya ingin membagikan cerita mereka di sini. Bonus foto inspirasi dari karakter itu juga!<br /><br /><table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody><tr><td style="text-align: center;"><a href="https://www.scmp.com/sites/default/files/styles/486w/public/images/methode/2017/02/08/99a4545c-ec2d-11e6-8960-2c6b8565de23_486x.jpg?itok=Lx71jijn" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" data-original-height="324" data-original-width="486" height="213" src="https://www.scmp.com/sites/default/files/styles/486w/public/images/methode/2017/02/08/99a4545c-ec2d-11e6-8960-2c6b8565de23_486x.jpg?itok=Lx71jijn" width="320" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;"><b><u><a href="https://www.scmp.com/culture/film-tv/article/2069122/film-review-scoop-masaharu-fukuyama-plays-creepy-sexist-paparazzo">Fumi Nikaido,</a></u></b> inspirasi tokoh Neska </td></tr></tbody></table><b>Horizon Aneska</b><br />Sejak lama, saya ingin punya tokoh bernama "Horizon". Dulu saya pernah membaca novel tentang teka-teki pencarian seorang anonim yang mengirim surel pada perempuan bernama Horison. Entah kenapa hingga sekarang, nama itu terpatri dalam pikiran. Saya pun bertekad untuk membuat nama tokoh yang memiliki unsur langit di dalamnya. Jadilah... begitu.<br /><br /><a name='more'></a><br /><br />Horizon Aneska dalam Mata Pena adalah reporter kompartemen kriminal. Ia anak baru, tetapi dia bekerja di tempatnya sekarang lantaran "butuh banget". Sebelumnya, ia pernah bekerja di sebuah media milik pakar humas ternama yang mulai banting setir jadi humas politisi. Makanya, ia rela digaji berapa pun asal bisa pindah. Di lini waktu 2016, Horizon Aneska baru berusia 24 tahun.<br /><br /><div style="text-align: left;"></div><b>Satria Kelana</b><br />Ini nama saya curi dari teman (walau hanya nama belakangnya). Otak saya saat membentuk nama ini langsung memunculkan sosok gondrong, doyan <i>ngopi </i>dan <i>ngebul, </i>dan suka tebar pesona sama cewek mana pun. Namun, dia sebenarnya kalau serius, ya serius banget. Kalau sudah satu, ya satu. Dia indekos, walau enggak pernah pulang ke rumah karena terlalu hobi memburu berita sensasional. Usia sekitar 28 tahun. Setiap menulis adegan Satria dan membayangkan tokohnya adalah <i>Nick Valensi, </i>jiwa <i>fangirling </i>saya langsung bergetar. :|<br /><br /><table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody><tr><td style="text-align: center;"><a href="https://miro.medium.com/max/680/0*qt7xVKfFhJqduEUI." imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" data-original-height="800" data-original-width="450" height="320" src="https://miro.medium.com/max/680/0*qt7xVKfFhJqduEUI." width="179" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;"><u style="font-weight: bold;">Arata Iura, </u>inspirasi tokoh Tirta</td></tr></tbody></table><br /><b>Tirta Irawan</b><br />Usia 30 tahun dan punya wibawa. Karena orangnya rajin dan selalu berpikir strategis, ia bisa jadi supervisor, alias redaktur pelaksana di majalah Integral. Dia mengawali karir sebagai reporter pos hukum dan kriminal, hingga akhirnya menjadi redaktur pelaksana. Di bayangan saya, sosoknya itu kayak Star Lord kalau kerja kantoran<i>. </i><b style="font-style: italic;">HAHA!</b><br /><b><br /></b><br /><table cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody><tr><td style="text-align: center;"><a href="https://www.windots.com/wp-content/uploads/2019/08/823/kimura-fumino-caring-for-a-talk-without-talking-about-a-blackout-during-the-nhk-sagideca-starring-drama.jpg" imageanchor="1" style="clear: left; margin-bottom: 1em; margin-left: auto; margin-right: auto;"><img border="0" data-original-height="553" data-original-width="640" height="275" src="https://www.windots.com/wp-content/uploads/2019/08/823/kimura-fumino-caring-for-a-talk-without-talking-about-a-blackout-during-the-nhk-sagideca-starring-drama.jpg" width="320" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;"><b><u><a href="https://www.windots.com/index.php/2019/08/20/kimura-fumino-caring-for-a-talk-without-talking-about-a-blackout-during-the-nhk-sagideca-starring-drama/">Fumino Kimura</a></u> </b>sebagai Saras</td></tr></tbody></table><div style="text-align: right;"></div><b>Saraswati Liman</b><br />Cewek satu ini adalah teman dekat Tirta dan salah satu redaktur juga. Dia sudah bekerja di Integral sejak masih jadi reporter di kompartemen lain, sampai di 2016 menjadi redaktur pos Lingkungan, Kesehatan, dan Teknologi (Lingkestek). Gaya bicaranya agak santai, blak-blakan cenderung sarkastis. Rambutnya saat ini dipotong bob dan Mbak Saras--begitu dia biasa dipanggil--kini berusia 29 tahun.<br /><br /><table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody><tr><td style="text-align: center;"><a href="https://1.bp.blogspot.com/proxy/Fe6M42o-x3HMQHg6d830x-WZADhBelw3vWgERJigZv0buRtcG5yH1nvxX3fjaxPclzxBuDIV8CMPNhgn7eVDdEq5BoipwAywSIBRX5TmtAA5BwTwxi3PJeH0eli_hcuQjnq9nK_8OE-Qj0LnmxbMWIcQIJxn" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" data-original-height="312" data-original-width="512" height="193" src="https://1.bp.blogspot.com/proxy/Fe6M42o-x3HMQHg6d830x-WZADhBelw3vWgERJigZv0buRtcG5yH1nvxX3fjaxPclzxBuDIV8CMPNhgn7eVDdEq5BoipwAywSIBRX5TmtAA5BwTwxi3PJeH0eli_hcuQjnq9nK_8OE-Qj0LnmxbMWIcQIJxn" width="320" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;"><u style="font-weight: bold;"><a href="http://sharjahart.org/sharjah-art-foundation/people/moriyama-mirai">Mirai Moriyama</a></u> versi gondrong, inspirasi tokoh Barli</td></tr></tbody></table><br /><b>Barli Ardandy</b><br />Redaktur <i>desk </i>Seni dan Hiburan. Hobinya datang dari <i>premiere </i>ke <i>premiere, </i>dan nonton teater di Cikini. Dia berusia 32 tahun, doyan ribut sama Mbak Saras. Bertubuh jangkung, kurus, sering memakai pakaian gaya retro seperti Jarwo Naif (celana cutbray <i>and so on...</i>) Rambutnya gondrong sebahu tapi ikal dan kusut parah.<br /><br /><table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody><tr><td style="text-align: center;"><a href="https://encrypted-tbn0.gstatic.com/images?q=tbn%3AANd9GcR-5tUe3eeADLChvEUiOHBjl45fcR8eKDsq6SyLckisddaOgjYZ" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" data-original-height="225" data-original-width="225" src="https://encrypted-tbn0.gstatic.com/images?q=tbn%3AANd9GcR-5tUe3eeADLChvEUiOHBjl45fcR8eKDsq6SyLckisddaOgjYZ" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;"><u style="font-weight: bold;"><a href="https://web.facebook.com/deanfujiokanothaifc?_rdc=1&_rdr">Dean Fujioka</a></u> sebagai Hero</td></tr></tbody></table><br /><b>Hero Yanuarisan</b><br />Termasuk redaktur yang serius dan selalu berpakaian rapi. Tapi, Mas Hero ini mengamati perkembangan ekonomi di Indonesia, karena ia adalah redaktur pos Ekonomi dan Politik. Anak buahnya alias reporternya cuma satu, Genta Henriyan. Dia kadang pinjam reporter dari posnya Mas Tirta, atau posnya Saras. Rambutnya tersisir rapi, macam manajer bank. Dia berkacamata tebal dan memiliki darah Tionghoa-Sunda.<br /><br /><table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody><tr><td style="text-align: center;"><a href="https://6.viki.io/image/faaccde7772e499f92cac1fc7eeb32de.jpeg?s=900x600&e=t" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" data-original-height="533" data-original-width="800" height="213" src="https://6.viki.io/image/faaccde7772e499f92cac1fc7eeb32de.jpeg?s=900x600&e=t" width="320" /></a></td></tr><tr><td class="tr-caption" style="text-align: center;"><u style="font-weight: bold;"><a href="https://www.soompi.com/article/1333708wpp/lee-joon-hyuk-describes-preparing-for-his-character-in-korean-remake-of-designated-survivor">Lee Joon Hyuk</a></u> sebagai Harits</td></tr></tbody></table><br /><b>Harits Pamitra</b><br />Pendiri <i>Harits Pamitra & Partners, </i>terlihat sok kuasa padahal gampang <i>chickened out. </i>Usia 28 tahun dan terkenal sebagai jubir partai. Bersahabat dengan Gumilang yang lebih tua darinya 7 tahun. Mereka pernah kuliah di satu kampus yang sama.<br /><br /><i><u>Segini dulu, nanti dilanjut part 2.</u></i><br /><br /><i>*btw maaf nih inspirasinya aktor dan aktris Jepang semua, soalnya memang begitu :))</i></div><div style="text-align: justify;"><br /></div>
| 773.214286 | 10,243 | 0.764527 | ind_Latn | 0.670927 |
ff8b2f0d84f3caacbb92e4471f52db58603f171b | 1,028 | md | Markdown | WindowsServerDocs/administration/windows-commands/telnet-open.md | gakera/windowsserverdocs | cee698e76801eaeedc97ecb6f7536a4360add617 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-02-28T14:12:26.000Z | 2019-02-28T14:12:26.000Z | WindowsServerDocs/administration/windows-commands/telnet-open.md | gakera/windowsserverdocs | cee698e76801eaeedc97ecb6f7536a4360add617 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2018-10-12T20:58:59.000Z | 2018-10-12T20:58:59.000Z | WindowsServerDocs/administration/windows-commands/telnet-open.md | gakera/windowsserverdocs | cee698e76801eaeedc97ecb6f7536a4360add617 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-06-04T08:11:35.000Z | 2021-06-04T08:11:35.000Z | ---
title: telnet open
description: "Windows Commands topic for **** - "
ms.custom: na
ms.prod: windows-server-threshold
ms.reviewer: na
ms.suite: na
ms.technology: manage-windows-commands
ms.tgt_pltfrm: na
ms.topic: article
ms.assetid: e30ad68c-2366-4754-ac36-311a2392902a vhorne
author: coreyp-at-msft
ms.author: coreyp
manager: dongill
ms.date: 10/16/2017
---
# telnet: open
>Applies To: Windows Server (Semi-Annual Channel), Windows Server 2016, Windows Server 2012 R2, Windows Server 2012
Connects to a telnet server.
## Syntax
```
o[pen] <hostname> [<Port>]
```
### Parameters
|Parameter|Description|
|-------|--------|
|<hostname>|Specifies the computer name or IP address.|
|[<Port>]|Specifies the TCP port that the telnet server is listening on. The default is TCP port 23.|
## <a name="BKMK_Examples"></a>Examples
Connect to a telnet server at telnet.microsoft.com.
```
o telnet.microsoft.com
```
## additional references
- [Command-Line Syntax Key](command-line-syntax-key.md)
| 27.052632 | 115 | 0.702335 | eng_Latn | 0.56133 |
ff8be9b7457053318d99257484edac38f0572f7b | 2,093 | md | Markdown | README.md | gungun974/BBPortal | acf44838b19c30d844bfdc30b439de4c0668cd7d | [
"MIT"
] | null | null | null | README.md | gungun974/BBPortal | acf44838b19c30d844bfdc30b439de4c0668cd7d | [
"MIT"
] | null | null | null | README.md | gungun974/BBPortal | acf44838b19c30d844bfdc30b439de4c0668cd7d | [
"MIT"
] | null | null | null | # BBPortal
[](http://cocoapods.org/pods/BBPortal)
[](http://cocoapods.org/pods/BBPortal)
[](http://cocoapods.org/pods/BBPortal)
## Description
BBPortal is a library that will enable you to pass data between your targets and applications (excluding the watch target). It's using App Groups in the background to save data in the shared container and another library - [DAFileMonitor](https://github.com/dagostini/DAFileMonitor) - is used to listen to changes on the file. You can create as many portals as you want. You can give your portals different IDs or you can give them all the same ID. When you push data through your portal, all other portals with the same ID will receive the data.
In the example below, you can see two apps controlling each other by passing data in real-time:
You can read more about this library on my blog: http://agostini.tech/2017/08/13/sharing-data-between-applications-and-extensions-using-app-groups/
## Usage
```swift
var portal: BBPortalProtocol = BBPortal(withGroupIdentifier: "your.group.identifier.goes.here", andPortalID: "id.for.this.portal")
// Send data
portal.send(data: ["key": "What ever data you want"]) {
(error) in
if let anError = error {
print("Send failed with error: ", anError)
}
}
// Receive data
portal.onDataAvailable = {
(data) in
guard let dict = data as? [String: Any?] else {
return
}
print("I received some data through the portal: ", dict)
}
```
## Installation
BBPortal is available through [CocoaPods](http://cocoapods.org). To install
it, simply add the following line to your Podfile:
```ruby
pod 'BBPortal'
```
## Author
Dejan Agostini, [email protected]
Update by gungun974, [email protected]
## License
BBPortal is available under the MIT license. See the LICENSE file for more info.
| 34.883333 | 546 | 0.737697 | eng_Latn | 0.921558 |
ff8c4cab2c2b2d09f0c5ed59bdc5bafd2630ac50 | 11,115 | md | Markdown | README.md | CCLDESTY/xml3d.js | aa5cee91aa26cc63f34c5138d9decf0de3941989 | [
"MIT"
] | 2 | 2015-06-09T03:30:16.000Z | 2015-06-09T03:42:15.000Z | README.md | CCLDESTY/xml3d.js | aa5cee91aa26cc63f34c5138d9decf0de3941989 | [
"MIT"
] | null | null | null | README.md | CCLDESTY/xml3d.js | aa5cee91aa26cc63f34c5138d9decf0de3941989 | [
"MIT"
] | null | null | null | xml3d.js
========
[](https://travis-ci.org/xml3d/xml3d.js)
#### XML3D ####
xml3d.js is a [XML3D](http://www.xml3d.org) implementation based on WebGL and JavaScript. The aim of XML3D is to make the development of 3D-Web applications as easy
as developing web pages. Every web developer who knows how to use the DOM (or jQuery) should also be able to use XML3D.
XML3D is also an evaluation platform of the W3C Community Group [Declarative 3D for the Web](http://www.w3.org/community/declarative3d/)
#### Examples ####
<a href="http://www.xml3d.org/xml3d/demos/19_RubiksCube/"><img src="http://www.xml3d.org/xml3d/demos/thumbs/rubik.jpg"/></a>
<a href="http://www.xml3d.org/xml3d/demos/25_Chess/"><img src="http://www.xml3d.org/xml3d/demos/thumbs/chess.png"/></a>
<a href="http://www.xml3d.org/xml3d/demos/12_MarsCity/marscity.xhtml"><img src="http://www.xml3d.org/xml3d/demos/thumbs/marscity.jpg?s"/></a>
<a href="http://www.xml3d.org/xml3d/demos/32_WorldBank/"><img src="http://www.xml3d.org/xml3d/demos/thumbs/worldbank.jpg"/></a>
<a href="http://xml3d.github.com/xml3d-museum/"><img src="http://www.xml3d.org/xml3d/demos/thumbs/museum.jpg"/></a>
<a href="http://xml3d.github.com/xml3d-examples/examples/gangnam/style.html"><img src="http://www.xml3d.org/xml3d/demos/thumbs/gangnam.jpg"/></a>
<a href="http://xml3d.github.io/xml3d-examples/examples/xflowAR/ar_flying_teapot.html"><img src="http://www.xml3d.org/xml3d/demos/thumbs/ar.jpg"/></a>
<a href="http://xml3d.github.io/xml3d-examples/examples/shade-tv/index.html"><img src="http://xml3d.org/xml3d/demos/thumbs/shade-js-tv.png"/></a>
<a href="http://xml3d.github.io/xml3d-examples/examples/lines/edf-vtk.html"><img src="http://xml3d.org/xml3d/demos/thumbs/edf.png"/></a>
#### Usage ####
Download the [library](http://www.xml3d.org/xml3d/script/xml3d.js) and include it in your xhtml.
```html
<script src="http://www.xml3d.org/xml3d/script/xml3d.js"></script>
```
If a standard navigation mode is sufficient for your web application, you can
include the camera controller that comes with xml3d.js:
```html
<script src="http://www.xml3d.org/xml3d/script/xml3d.js"></script>
<script src="http://www.xml3d.org/xml3d/script/tools/camera.js"></script>
```
#### Testing ####
We have an extensive [test suite](http://xml3d.github.com/xml3d.js/tests/) and some [known issues](https://github.com/xml3d/xml3d.js/wiki/Known-issues).
#### How to build ####
##### Dependencies #####
You will need [node.js](http://nodejs.org/). Then install grunt:
```bash
npm install -g grunt-cli
```
##### Clone #####
Clone a copy of the main xml3d.js git repo by running:
```bash
git clone git://github.com/xml3d/xml3d.git
```
##### Build #####
Enter the xml3d.js directory and run the build script:
```bash
cd xml3d.js && npm run build
```
The built version of xml3d.js will be put in the `build/output/` subdirectory. Alternatively you have several grunt tasks that you can run directly (e.g. ```grunt min```). Run ```grunt --help``` to get a list of available grunt tasks.
### Documentation ###
We have an overview documentation in each subfolder of the project:
* [build](build/) - The build system of xml3d.js.
* [src](src/) - The actual source code of the xml3d.js library
* [tests](tests/) - The test suite
* [tools](tools/) - Several tools that can be used optionally with xml3d.js
### Change log ###
4.9 - 31.03.2014
* External Xflow Operators - [demo](http://xml3d.github.io/xml3d-examples/examples/facemorph/facemorph.html), [doc](https://github.com/xml3d/xml3d.js/wiki/External-resources#External_Xflow_Operators)
* [IE 11 Support](https://github.com/xml3d/xml3d.js/issues/97)
* Grunt build system now based on [Browserify](http://browserify.org/)
* Source Mapping for the [xml3d-dev](http://xml3d.org/xml3d/scripts/xml3d-dev.js) build
* Bugfixes: [37](https://github.com/xml3d/xml3d.js/issues/37), [73](https://github.com/xml3d/xml3d.js/issues/73), [87](https://github.com/xml3d/xml3d.js/issues/87), [88](https://github.com/xml3d/xml3d.js/issues/88), [92](https://github.com/xml3d/xml3d.js/issues/92), [98](https://github.com/xml3d/xml3d.js/issues/98), [100](https://github.com/xml3d/xml3d.js/issues/100), [104](https://github.com/xml3d/xml3d.js/issues/104)
4.8 - 18.12.2014
* Recursive Assets - [demo](http://xml3d.github.io/xml3d-examples/examples/recursiveAsset/recursive.html), [doc](https://github.com/xml3d/xml3d.js/wiki/Assets-and-Model), [issue](https://github.com/xml3d/xml3d.js/issues/76)
* Load Events - [doc](https://github.com/xml3d/xml3d.js/wiki/Events#load)
* [iOS 8 Support](https://github.com/xml3d/xml3d.js/issues/75)
* New build system based on [grunt](http://gruntjs.com/)
* Improved texture filtering - [doc](https://github.com/xml3d/xml3d.js/wiki/Textures)
* Draw multiple line strips in a single mesh `<mesh>` - [demo](http://xml3d.github.io/xml3d-examples/examples/lines/simple.html), [demo](http://xml3d.github.io/xml3d-examples/examples/lines/edf-vtk.html), [doc](https://github.com/xml3d/xml3d.js/wiki/Geometry-Definition#typelinestrips)
* Bugfixes: [9](https://github.com/xml3d/xml3d.js/issues/9), [46](https://github.com/xml3d/xml3d.js/issues/46), [56](https://github.com/xml3d/xml3d.js/issues/56), [74](https://github.com/xml3d/xml3d.js/issues/74), [75](https://github.com/xml3d/xml3d.js/issues/75), [76](https://github.com/xml3d/xml3d.js/issues/76), [77](https://github.com/xml3d/xml3d.js/issues/77), [79](https://github.com/xml3d/xml3d.js/issues/79), [82](https://github.com/xml3d/xml3d.js/issues/82)
4.7 - 17.10.2014
* Assets / Configurable Instances - [demo](http://xml3d.github.io/xml3d-examples/examples/assets/assets.html), [slides](http://xml3d.org/xml3d/slides/web3d-instancing/)
* [shade.js](http://xml3d.org/xml3d/papers/shade.js/) integration (beta) - [demo](http://xml3d.github.io/xml3d-examples/examples/shade-tv/index.html), [slides](http://xml3d.org/xml3d/slides/pg-shade.js/)
* Shadow Maps - [demo](http://xml3d.github.io/xml3d-examples/examples/meshlab/meshlab.html)
* More options for texture filtering
* Bugfixes: [#69](https://github.com/xml3d/xml3d.js/issues/69), [#71](https://github.com/xml3d/xml3d.js/issues/71)
4.6 - 15.04.2014
* [Custom RenderTrees and the RenderInterface](https://github.com/xml3d/xml3d.js/wiki/Custom-RenderTrees-and-the-RenderInterface)
* Added Screen-space Ambient Occlusion to standard render pipeline
* Added system to set renderer-specific [options](https://github.com/xml3d/xml3d.js/wiki/Options)
* Infrastructure for [WebCL-based Xflow operators](https://github.com/xml3d/xml3d.js/wiki/WebCL-API)
4.5 - 14.11.2013
* Full support for HTML encoding, all [demos](http://xml3d.github.io/xml3d-examples/) in HTML now
* Set data values efficiently using TypedArray - [demo](http://xml3d.github.io/xml3d-examples/examples/scriptValue/scriptValue.html), [doc](https://github.com/xml3d/xml3d.js/wiki/How-to-efficiently-set-Xflow-input-with-TypedArrays)
* Override shader attributes on a per-object basis - [demo](http://xml3d.github.io/xml3d-examples/examples/shaderOverrides/index.html)
* Improved Error Messages
* Reuse of Xflow graphs using new `<dataflow>` element - [demo](http://xml3d.github.io/xml3d-examples/examples/xflowSkin/xflow-skin.html), [doc](https://github.com/xml3d/xml3d.js/wiki/How-to-use-Xflow#wiki-Dataflows)
* Many performance improvements, e.g. Frustum Culling and Paging
* Support for mult-touch events
* Dynamic near/far clip planes that adapt to scene size
* [#24](https://github.com/xml3d/xml3d.js/issues/24): WebWorker support for MeshLoader plug-ins - [demo](http://localhost:8080/xml3d-examples/examples/openctm/openctm.html)
* [#25](https://github.com/xml3d/xml3d.js/issues/25): Smarter handling of cached resources
4.4 - 23.04.2013
* Image Processing with Xflow (also as standalone library) - [demo](http://xml3d.github.io/xml3d-examples/examples/xflowIP/pixel-wise.html)
* Transformations as Xflow sink
* Augemented Reality (AR) - [demo](http://xml3d.github.io/xml3d-examples/examples/xflowAR/ar_flying_teapot.xhtml)
* Keyframe animations
* Generalized resources for meshes, shaders, etc.
* Support for [XML](http://xml3d.github.com/xml3d-examples/examples/externalXml/externalXml.xhtml) and [JSON](http://xml3d.github.io/xml3d-examples/examples/suzanne/suzanne.xhtml)
* External loader plug-ins: [OpenCTM](http://xml3d.github.io/xml3d-examples/examples/openctm/openctm.xhtml) and [MeshLab](http://xml3d.github.io/xml3d-examples/examples/meshlab/meshlab.xhtml)
* [Xflow API](): Observer Xflow graph from JavaScript
* Canvas resizing [demo](http://xml3d.github.io/xml3d-examples/examples/canvasresizing/resizing.xhtml)
* Issues: Fixed [#2](https://github.com/xml3d/xml3d.js/issues/2), Fixed [#3](https://github.com/xml3d/xml3d.js/issues/3)
4.3 - 18.12.2012
* [Xflow](https://github.com/xml3d/xml3d.js/wiki/Xflow) support, including
* Skinning - [demo](http://xml3d.github.com/xml3d-examples/examples/xflowSkin/xflow-skin.xhtml) & [demo](http://xml3d.github.com/xml3d-examples/examples/gangnam/style.xhtml)
* Sequential Morphing - [demo](http://xml3d.github.com/xml3d-examples/examples/xflowSequentialMorph/xflow-morph.xhtml)
* Mechanism for custom operators - [demo](http://xml3d.github.com/xml3d-examples/examples/facemorph/facemorph.xhtml) & [demo](http://xml3d.github.com/xml3d-examples/examples/xflowWave/xflow-wave.xhtml)
* Prototypes - [demo](http://xml3d.github.com/xml3d-examples/examples/xflowPrototypes/xflow-prototypes.xhtml)
* External references in XML format - [demo](http://xml3d.github.com/xml3d-examples/examples/externalXml/externalXml.xhtml)
* ['onload' event](https://github.com/xml3d/xml3d.js/wiki/Events) for <xml3d> element
* Support for video textures - [demo](http://xml3d.github.com/xml3d-examples/examples/video/video.xhtml)
* Support to use a webcam stream as video texture via WebRTC API - [demo](http://xml3d.github.com/xml3d-examples/examples/webcam/webcam.xhtml)
* Support of spot lights - [demo](http://xml3d.github.com/xml3d-examples/examples/spotLight/index.xhtml)
* Support of CSS 3D Transforms in _style_ attribute - [demo](http://xml3d.github.com/xml3d-examples/examples/cssTransform/css-transform.xhtml)
* Improved debug output
4.2 - 14.09.2012
* Hardware accelerated object picking expanded to 16,7 mio objects
* Emissive texture map support in diffuse and phong shader - [demo](http://xml3d.github.com/xml3d-examples/examples/candle/candle.xhtml)
* Specular map support in phong shader - [demo](http://xml3d.github.com/xml3d-museum/)
* New mechanism for custom shaders - [demo](http://xml3d.github.com/xml3d-examples/examples/eyelight/eyelight.xhtml)
* Support of directional lights (finally) - [demo](http://xml3d.github.com/xml3d-examples/examples/directionalLight/index.xhtml)
* Support of external data resources in JSON format - [demo](http://xml3d.github.com/xml3d-examples/examples/suzanne/suzanne.xhtml)
* New mechanism to register loaders for external formats - [demo](http://xml3d.github.com/xml3d-examples/examples/meshlab/meshlab.xhtml)
4.1 - 19.07.2012
* Initial release on GitHub
#
| 72.175325 | 467 | 0.74314 | yue_Hant | 0.330277 |
ff8cff02318acb7716b403809a980076454b85f1 | 1,034 | md | Markdown | CONTRIBUTING.es.md | elaynelemos/ansible-role-mongodb | 3d6bc513f8faf0ba806f0d19608f6219ace30ba4 | [
"MIT"
] | 1 | 2020-10-06T23:47:13.000Z | 2020-10-06T23:47:13.000Z | CONTRIBUTING.es.md | elaynelemos/ansible-role-mongodb | 3d6bc513f8faf0ba806f0d19608f6219ace30ba4 | [
"MIT"
] | 8 | 2020-10-03T20:23:51.000Z | 2021-09-23T23:29:26.000Z | CONTRIBUTING.es.md | elaynelemos/ansible-role-mongodb | 3d6bc513f8faf0ba806f0d19608f6219ace30ba4 | [
"MIT"
] | 3 | 2020-10-04T00:10:28.000Z | 2020-10-05T22:06:35.000Z | ## Pasos simples para empezar:
* **Si eres nuevo en Git / Github, no tienes por que sentirte intimidado**
* Puedes simplemente contribuir usando la UI de Github.
1. Crea un nuevo Fork de este repositorio.
2. Has el cambio que desees.
3. Luego, crea un Pull Request.
4. Tu Pull Request sera evaluado y finalmente mergeado al master (main).
[Tambien puedes guiarte en este tutorial](https://github.com/firstcontributions/first-contributions)
## Escribiendo codigo:
* Antes de pushear tus cambios a Github, asegurate de que tu codigo compile y corra sin errores ni warnings.
* Aceptamos contribuciones en cualquier lenguaje (Eng/Spa/Por)
* Usa variables, metodos y nombres de funciones declarativas junto a los comentarios.
* Nada de profanidades.
## Maneras de contribuir:
* Impementa nuevos algoritmos para el repositorio en su debida seccion. Si la seccion no existe, crea una apropiada.
* Optimiza o mejora el codigo existente de algun algoritmo
* Agrega una nueva solucion a un problema existente
* Encontrar y arreglar bugs. | 43.083333 | 116 | 0.780464 | spa_Latn | 0.992155 |
ff8d01aebce5220deef34e63ab829ecf383be6c4 | 1,205 | md | Markdown | site/_posts/2011-01-25-day-25-fireplace-no-polarizer.md | fwenzel/fredericiana | 06d523b5c93e80fa38c9d671916accbd3c74adc4 | [
"BSD-3-Clause"
] | null | null | null | site/_posts/2011-01-25-day-25-fireplace-no-polarizer.md | fwenzel/fredericiana | 06d523b5c93e80fa38c9d671916accbd3c74adc4 | [
"BSD-3-Clause"
] | 2 | 2015-01-15T23:29:01.000Z | 2015-04-29T22:00:16.000Z | site/_posts/2011-01-25-day-25-fireplace-no-polarizer.md | fwenzel/fredericiana | 06d523b5c93e80fa38c9d671916accbd3c74adc4 | [
"BSD-3-Clause"
] | null | null | null | ---
status: publish
tags:
- Project 365
published: true
title: Day 25 - Fireplace, No Polarizer
type: post
meta:
aktt_tweeted: "1"
_edit_last: "2"
_wp_old_slug: ""
aktt_notify_twitter: "yes"
layout: post
---
<a href="http://www.flickr.com/photos/freeed/5389797004/" title="Day 25 - Fireplace by Fred, on Flickr"><img src="http://farm6.static.flickr.com/5135/5389797004_e6a0cf731c.jpg" width="500" height="333" alt="Day 25 - Fireplace" /></a>
This is a picture of our gas fireplace. Turned out to be a much more interesting subject than I expected. It is quite hard to take a decent photo of it, because the brightness contrast between the (fake) logs and the flames is so high. Due to the quick movement, a simple HDR photograph is also out of the question. Finally, when adding enough ambient light, the glass in front of the fireplace results in visible reflections from <strong>all angles</strong>. This photo is one of the latter kind, with enough ambient light, but it quite obviously shows a reflection of the opposite wall on the right hand side of the picture.
Apparently, I am due for buying a polarizing filter soon! Then, I can retake the picture and see how the two compare.
| 60.25 | 627 | 0.753527 | eng_Latn | 0.996215 |
ff8d39efdc340587576f3239f19d67cc5c1de041 | 76 | md | Markdown | README.md | jkaae93/catBreeds | e5c51f7a0f30707d2a6057c5187e606d3c0d278c | [
"Apache-2.0"
] | null | null | null | README.md | jkaae93/catBreeds | e5c51f7a0f30707d2a6057c5187e606d3c0d278c | [
"Apache-2.0"
] | null | null | null | README.md | jkaae93/catBreeds | e5c51f7a0f30707d2a6057c5187e606d3c0d278c | [
"Apache-2.0"
] | null | null | null | # catBreeds
Cat Breeds.
Only support english and korean
# TODO
Dog breeds.
| 10.857143 | 31 | 0.763158 | kor_Hang | 0.615032 |
ff8d7314fd6fe92d369ff2c09420aae8bfcbdf44 | 2,064 | md | Markdown | demo/node_modules/fast-clone/README.md | jkhaui/FlacheQL | cad89aaea0451d49ae715c2a3016025bd3378f61 | [
"Apache-2.0"
] | 243 | 2018-06-12T17:58:28.000Z | 2022-01-07T19:21:53.000Z | demo/node_modules/fast-clone/README.md | jkhaui/FlacheQL | cad89aaea0451d49ae715c2a3016025bd3378f61 | [
"Apache-2.0"
] | 8 | 2018-10-05T03:32:07.000Z | 2022-02-12T02:36:19.000Z | demo/node_modules/fast-clone/README.md | jkhaui/FlacheQL | cad89aaea0451d49ae715c2a3016025bd3378f61 | [
"Apache-2.0"
] | 26 | 2018-06-07T23:46:49.000Z | 2020-08-31T16:23:19.000Z | <center>
<img src="https://raw.githubusercontent.com/codeandcats/fast-clone/master/logo.png" />
</center>
The ***fastest deep cloning*** function on NPM that supports the following types:
- Objects (POJOs, null, undefined)
- Arrays
- Dates
- Regular Expressions
- Strings
- Numbers (NaN, Positive Infinity, Negative Infinity)
- Booleans
## Speed Comparison
Average runtime of various NPM clone libraries on a **large** complex object loaded from json files of varying sizes ranging from 3.5 MB to 15 MB.
Library | 3.5 MB | 7 MB | 15 MB |
-------------------|-------------|-------------|------------|
✔ **fast-clone** | **65 ms** | **135 ms** | **275 ms** |
✘ deepClone | 72 ms | 162 ms | 313 ms |
✘ lodash.cloneDeep | 96 ms | 214 ms | 476 ms |
✘ snapshot | 337 ms | 1,145 ms | 3,420 ms |
✘ clone | 504 ms | 1,843 ms | 7,221 ms |
✘ angular.copy | 514 ms | 1,895 ms | 7,308 ms |
## Installation
### NPM
```sh
npm install fast-clone --save
```
### Yarn
```sh
yarn add fast-clone
```
## Usage
Fast-clone is a UMD module so you can use it in Node.js, or in Browser either using Browserfy/Webpack, or by using the global clone function if not using a module loader.
### TypeScript
```ts
import clone = require('fast-clone');
```
### JavaScript
```js
const clone = require('fast-clone');
```
```ts
const a = {
name: 'Natasha Rominov',
age: 30,
skills: [
'Pistols',
'Espionage'
],
dateOfBirth: new Date('1986-05-21T00:00:00.000Z')
};
const b = clone(a);
b.skills.push('That grabby thing she does with her legs');
console.log(a.skills)
console.log(b.skills);
```
Output will be:
```ts
['Pistols', 'Espionage']
['Pistols', 'Espionage', 'That grabby thing she does with her legs']
```
## Got an Issue or Feature Suggestion?
Then [create an issue on GitHub](https://github.com/codeandcats/fast-clone/issues) and I'll fix/add it asap. :)
Or fork the [repo](https://github.com/codeandcats/fast-clone) and shoot me a pull request
| 25.8 | 170 | 0.614826 | eng_Latn | 0.819126 |
ff8d81a22b1da601dd2436751b56785f02fc6066 | 2,738 | md | Markdown | content/publication/behavioral-and-electrophysiological-effects-of-cortical-microstimulation-parameters/index.md | bilalbari3/personal-website | 446a5946708e8e00f8eccc166f941cd7249e7150 | [
"MIT"
] | null | null | null | content/publication/behavioral-and-electrophysiological-effects-of-cortical-microstimulation-parameters/index.md | bilalbari3/personal-website | 446a5946708e8e00f8eccc166f941cd7249e7150 | [
"MIT"
] | null | null | null | content/publication/behavioral-and-electrophysiological-effects-of-cortical-microstimulation-parameters/index.md | bilalbari3/personal-website | 446a5946708e8e00f8eccc166f941cd7249e7150 | [
"MIT"
] | null | null | null | ---
title: Behavioral and electrophysiological effects of cortical microstimulation
parameters
publication_types:
- "2"
authors:
- Bilal A. Bari
- Douglas R. Ollerenshaw
- Daniel C. Millard
- Qi Wang
- Garrett B. Stanley
doi: 10.1371/journal.pone.0082170
publication: PLOS One
abstract: Electrical microstimulation has been widely used to artificially
activate neural circuits on fast time scales. Despite the ubiquity of its use,
little is known about precisely how it activates neural pathways. Current is
typically delivered to neural tissue in a manner that provides a locally
balanced injection of positive and negative charge, resulting in negligible
net charge delivery to avoid the neurotoxic effects of charge accumulation.
Modeling studies have suggested that the most common approach, using a
temporally symmetric current pulse waveform as the base unit of stimulation,
results in preferential activation of axons, causing diffuse activation of
neurons relative to the stimulation site. Altering waveform shape and using an
asymmetric current pulse waveform theoretically reverses this bias and
preferentially activates cell bodies, providing increased specificity. In
separate studies, measurements of downstream cortical activation from
sub-cortical microstimulation are consistent with this hypothesis, as are
recent measurements of behavioral detection threshold currents from cortical
microstimulation. Here, we compared the behavioral and electrophysiological
effects of symmetric vs. asymmetric current waveform shape in cortical
microstimulation. Using a go/no-go behavioral task, we found that
microstimulation waveform shape significantly shifts psychometric performance,
where a larger current pulse was necessary when applying an asymmetric
waveform to elicit the same behavioral response, across a large range of
behaviorally relevant current amplitudes. Using voltage-sensitive dye imaging
of cortex in anesthetized animals with simultaneous cortical microstimulation,
we found that altering microstimulation waveform shape shifted the cortical
activation in a manner that mirrored the behavioral results. Taken together,
these results are consistent with the hypothesis that asymmetric stimulation
preferentially activates cell bodies, albeit at a higher threshold, as
compared to symmetric stimulation. These findings demonstrate the sensitivity
of the pathway to varying electrical stimulation parameters and underscore the
importance of designing electrical stimuli for optimal activation of neural
circuits.
draft: false
featured: false
image:
filename: ""
focal_point: ""
preview_only: false
date: 2013-12-05T23:27:00.000Z
---
| 51.660377 | 80 | 0.814463 | eng_Latn | 0.997873 |
ff8dc0c619b3d89abef14df717203ad88173d4a0 | 1,092 | md | Markdown | README.md | jafors/dna-seq-varlociraptor | 2bb6c02727d24ec05d53f0924b85693334e526b4 | [
"MIT"
] | 57 | 2020-01-21T14:22:04.000Z | 2022-03-31T01:13:32.000Z | README.md | jafors/dna-seq-varlociraptor | 2bb6c02727d24ec05d53f0924b85693334e526b4 | [
"MIT"
] | 35 | 2020-02-10T12:18:44.000Z | 2022-03-24T08:59:47.000Z | README.md | jafors/dna-seq-varlociraptor | 2bb6c02727d24ec05d53f0924b85693334e526b4 | [
"MIT"
] | 28 | 2020-01-21T13:56:34.000Z | 2022-02-07T04:35:02.000Z | # Snakemake workflow: dna-seq-varlociraptor
[](https://snakemake.github.io)
[](https://github.com/snakemake-workflows/dna-seq-varlociraptor/actions?query=branch%3Amain+workflow%3ATests)
[](https://doi.org/10.5281/zenodo.4675661)
A Snakemake workflow for calling small and structural variants under any kind of scenario (tumor/normal, tumor/normal/relapse, germline, pedigree, populations) via the unified statistical model of [Varlociraptor](https://varlociraptor.github.io).
## Usage
The usage of this workflow is described in the [Snakemake Workflow Catalog](https://snakemake.github.io/snakemake-workflow-catalog/?usage=snakemake-workflows%2Fdna-seq-varlociraptor).
If you use this workflow in a paper, don't forget to give credits to the authors by citing the URL of this (original) repository and its DOI (see above).
| 68.25 | 246 | 0.788462 | eng_Latn | 0.489543 |
ff8df1e589657f5db716617703d5f1b65a130f4b | 2,025 | md | Markdown | _posts/2018-12-31-lemon-cake.md | cygairko/recipes | 65d8cb26a66571bd9f808c443ca4552f8ec129d6 | [
"MIT"
] | null | null | null | _posts/2018-12-31-lemon-cake.md | cygairko/recipes | 65d8cb26a66571bd9f808c443ca4552f8ec129d6 | [
"MIT"
] | 1 | 2021-03-30T08:22:32.000Z | 2021-03-30T08:22:32.000Z | _posts/2018-12-31-lemon-cake.md | cygairko/recipes | 65d8cb26a66571bd9f808c443ca4552f8ec129d6 | [
"MIT"
] | null | null | null | ---
date: 2017-01-06
title: Lemon Cake
categories:
- Kuchen
featured_image: https://source.unsplash.com/NAN22eh754c/1560x940
recipe:
servings: 12 slices
prep: 15 minutes
cook: 65 minutes
ingredients_markdown: |-
* 1 cup unsalted butter
* 2 1/2 cups all-purpose flour
* 1 teaspoon salt
* 1/2 teaspoon baking soda
* 1/2 teaspoon baking powder
* 3 cups of sugar
* 2 teaspoons of lemon zest
* 6 teaspoons of lemon juice
* 6 eggs
* 1 cup Greek yogurt
* 1 cup confectioners’ sugar
directions_markdown: |-
1. Heat oven to 325° F. Butter and flour a 12-cup Bundt pan. In a medium bowl, whisk together the flour, salt, baking soda, and baking powder.
2. Using an electric mixer, beat the butter, granulated sugar, and lemon zest on medium-high until light and fluffy, 3 to 4 minutes. Beat in 4 tablespoons of the lemon juice, then the eggs, one at a time, scraping down the sides of the bowl as necessary.
3. Reduce mixer speed to low. Add half the flour mixture, then the yogurt, and then the remaining flour mixture. Mix just until combined (do not overmix).
4. Transfer the batter to the prepared pan and bake until a toothpick inserted in the center comes out clean, 65 to 75 minutes. Cool the cake in the pan for 30 minutes, then turn it out onto a wire rack to cool completely.
5. In a small bowl, whisk together the confectioners’ sugar and 1 of the remaining tablespoons of lemon juice until smooth, adding the remaining lemon juice as necessary to create a thick, but pourable glaze.
---
If you're a sour fan you're going to love this cake. Lemon Cake is one of my favorite year-round desserts, but it is a perfect choice for spring and summer, when everyone tends to crave citrus or light & flavorful recipes
Straight out of the oven.
You can add extra flavour with berries.
Or a caramel sauce.
| 47.093023 | 258 | 0.737284 | eng_Latn | 0.99072 |
ff8ee518c7436fb3485ecc34829c1d20e44404ea | 4,040 | md | Markdown | _posts/2021-05-10-LC138.md | AsheBlade/ShadowArchive | b64d31987cacb75731819928d6683057b2ca2d22 | [
"MIT"
] | null | null | null | _posts/2021-05-10-LC138.md | AsheBlade/ShadowArchive | b64d31987cacb75731819928d6683057b2ca2d22 | [
"MIT"
] | 31 | 2021-06-15T07:26:34.000Z | 2022-01-15T02:58:24.000Z | _posts/2021-05-10-LC138.md | AsheBlade/ShadowArchive | b64d31987cacb75731819928d6683057b2ca2d22 | [
"MIT"
] | null | null | null | ---
layout: post
title: LC138_Copy List with Random Pointer
date: 2021-05-10
author: Shadow Walker
tags: [OPLC, Algorithm, LinkedList, Recursion, HashMap]
toc: true
comments: true
---
## 原题
LC138
## 推荐度
5星必刷
同时考察LinkedList, HashMap 和 Recursion, 兼具难度. 能刷必刷, 这种题是最好的, 一通百通.
## 历程
- 2021-05-10 第一次. 真的挺喜欢这道题的, 明知道这道题费时间, 但还是看了一上午. 很累. 最后写出来一个100%的完美解法还是挺自豪的.
- 2021-05-11 第二天早起二刷没过. 递归就是差一点就错. Sprint 9 接着刷.
- 2021-07-08 这道题已经刷穿了, 是TTT, 不需要看后面解法, 就记标准答案即可. 标准答案是最简洁优雅的.
## 难点
这种递归目前对我来说还是比较难的. 就永远不是crystal clear, 有个大概方向, 但模模糊糊的写不出来. 大概知道模式, 但写的时候总是差一点.
目前唯一的解决方式就是多刷. 这道题的递归用的很巧妙, 用的是Hashmap存储旧Node.
## 答案
这是标准答案, 很完美, 没的说. 看标准答案的图解, 很易懂.
```java
/*
// Definition for a Node.
class Node {
public int val;
public Node next;
public Node random;
public Node() {}
public Node(int _val,Node _next,Node _random) {
val = _val;
next = _next;
random = _random;
}
};
*/
public class Solution {
// HashMap which holds old nodes as keys and new nodes as its values.
HashMap<Node, Node> visitedHash = new HashMap<Node, Node>();
public Node copyRandomList(Node head) {
if (head == null) {
return null;
}
// If we have already processed the current node, then we simply return the cloned version of
// it.
if (this.visitedHash.containsKey(head)) {
return this.visitedHash.get(head);
}
// Create a new node with the value same as old node. (i.e. copy the node)
Node node = new Node(head.val, null, null);
// Save this value in the hash map. This is needed since there might be
// loops during traversal due to randomness of random pointers and this would help us avoid
// them.
this.visitedHash.put(head, node);
// Recursively copy the remaining linked list starting once from the next pointer and then from
// the random pointer.
// Thus we have two independent recursive calls.
// Finally we update the next and random pointers for the new node created.
node.next = this.copyRandomList(head.next);
node.random = this.copyRandomList(head.random);
return node;
}
}
```
这个是我看过标准答案的递归思路自己写的, 虽然不如标准答案写得好, 但放在这里, 对思路有帮助.
```java
class Solution {
HashMap<Node, Node> visitedHash = new HashMap<Node, Node>();
public Node copyRandomList(Node head) {
Node output = new Node(-1);
output = copy(output, head);
return output;
}
public Node copy(Node output, Node head) {
if(head == null)
return null;
if(visitedHash.containsKey(head))
{
output = visitedHash.get(head);
}else{
output = new Node(head.val);
visitedHash.put(head, output);
output.next = copyRandomList(head.next);
output.random = copyRandomList(head.random);
}
return output;
}
}
```
## 个人答案
这完全是我自己写的答案, 肯定是没有标准答案快的, 以为需要traverse两次. 但是在算力上和标准答案是一样的, 都是O(n), 提交之后Leetcode显示超过100%的人. 我很自豪.
我个人觉得我这个答案, 因为没有递归, 更方便理解.
```java
class Solution {
HashMap<Node, Node> visitedHash = new HashMap<Node, Node>();
public Node copyRandomList(Node head) {
if(head == null)
return null;
Node dummyHead = new Node(-1);
dummyHead.next = head;
//Traverse 两次
// 1. 第一次把每个旧head放进hashmap
while(head!=null)
{
visitedHash.put(head, new Node(head.val));
head = head.next;
}
head = dummyHead.next;
dummyHead = new Node(-1);
Node output = dummyHead;
//2. 第二次用hashmap之中的新copy复制random和next.
while(head!=null)
{
output.next = visitedHash.get(head);
if(head.random!=null && output.next!=null){
output.next.random = visitedHash.get(head.random);
}
output = output.next;
head = head.next;
}
return dummyHead.next;
}
}
```
## Complexity Analysis
很简单的O(N), 没什么可说的.
| 24.484848 | 99 | 0.613861 | yue_Hant | 0.380941 |
ff8f68a49909abd0cd06a860cad9ab6763828eef | 103 | md | Markdown | content/team/index.md | ajgmolina/reprex | 74211dafa0b414d79764de47fdd008689670a9df | [
"MIT"
] | null | null | null | content/team/index.md | ajgmolina/reprex | 74211dafa0b414d79764de47fdd008689670a9df | [
"MIT"
] | 1 | 2021-05-22T11:53:20.000Z | 2021-05-22T11:53:20.000Z | content/team/index.md | ajgmolina/reprex | 74211dafa0b414d79764de47fdd008689670a9df | [
"MIT"
] | 3 | 2020-03-26T09:41:58.000Z | 2020-10-05T23:44:38.000Z | ---
date: "2020-07-10T10:00:00"
summary: Who we are
title: "Team"
type: widget_page
aliases: [team]
--- | 14.714286 | 27 | 0.669903 | eng_Latn | 0.773326 |
ff8f79ad9105803342ac235efc729292f2d0f924 | 1,614 | md | Markdown | src/pages/articles/Custom terminal with oh my zsh/index.md | vuanhtu1993/blog | 1bd40eb622e995b3037859344bb252c7421f0114 | [
"MIT"
] | null | null | null | src/pages/articles/Custom terminal with oh my zsh/index.md | vuanhtu1993/blog | 1bd40eb622e995b3037859344bb252c7421f0114 | [
"MIT"
] | 10 | 2020-07-17T00:43:01.000Z | 2022-02-26T01:36:34.000Z | src/pages/articles/Custom terminal with oh my zsh/index.md | vuanhtu1993/blog | 1bd40eb622e995b3037859344bb252c7421f0114 | [
"MIT"
] | null | null | null | ---
title: Customize your terminal with oh my zsh for lazy guys
date: "2019-04-05T00:00:00.000Z"
layout: post
draft: false
path: "/posts/customize-terminal-with-oh-my-zsh/"
category: "Tips"
tags:
- "Terminal"
- "Oh My Zsh"
- "Zsh"
description: "Making your terminal more beautiful after 4 simple step"
---
### Step 1: Install ZSH
- ZSH (Z Shell) là một Unix shell cái mà được build on top của bash (shell mặc định của mac)
và thêm một số tính năng khác
```
brew install zsh
```
### Step 2: Install Oh My Zsh
- Oh my Zsh là một framework cho việc quản lí cấu hình zsh. Ở đấy có thể tuỳ chỉnh rất nhiều
thứ trong đó có theme của terminal
```
sh -c "$(curl -fsSL https://raw.githubusercontent.com/robbyrussell/oh-my-zsh/master/tools/install.sh)"
```
### Step 3: Install Powerline fonts
- Là một bộ font được hỗ trợ các kí tự đặc biệt cho terminal
```
git clone https://github.com/powerline/fonts.git --depth=1
cd fonts
./install.sh
cd ..
rm -rf fonts
```
### Step 4: Change theme and font
Change theme: mở terminal ở thư mục ~
```
vim .zshrc
```
Search từ khoá ZSH_THEME="theme name", thay thế bằng ZSH_THEME="default"
```
ZSH_THEME="agnoster"
```
Lưu ý:
- Lúc này khi reset terminal theme đã được apply nhưng mà lỗi font :(
- Có thể thay rất nhiều theme khác nhau, các theme này đã dược define mặc định trong khi
cài Oh my
Change font and color of font
Open terminal lên > Terminal > Preference > Profile > Font > Change : chọn Rotobo Mono for Powerline
Thay đổi màu từ mặc định cho hợp với style và cá tính của bạn trong Profile > ANSI color
Thế là done rồi :)
| 25.619048 | 102 | 0.700743 | vie_Latn | 0.999781 |
ff8fe4899074399fd245701c9ac1bb12d0292073 | 2,080 | md | Markdown | jp/manual/platforms/linux/create-a-linux-game.md | Basewq/stride-docs | 82565f53c3b3dd0cd0504c53d8671c1a4870a6c6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | jp/manual/platforms/linux/create-a-linux-game.md | Basewq/stride-docs | 82565f53c3b3dd0cd0504c53d8671c1a4870a6c6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | jp/manual/platforms/linux/create-a-linux-game.md | Basewq/stride-docs | 82565f53c3b3dd0cd0504c53d8671c1a4870a6c6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | # Linux 用ゲームを作成する
>[!NOTE]
>以下の説明を読む前に、「[Linux - セットアップと要件](setup-and-requirements.md)」の説明に従ってください。
1. Stride Launcher で、新しいゲームを作成し、ターゲット プラットフォームとして Linux を選択します。
2. Game Studio のプラットフォーム メニューで［Linux］を選択します。
3. **F5** キーを押し、プロジェクトをビルドして実行します。
4. プロジェクトを初めて実行するときは、Linux ホストに関する情報を入力します。
次のように情報を入力します。
5. ［Test settings］をクリックして資格情報をテストします。
エラーが発生した場合は、次のように表示されます。
資格情報が正しい場合は、次のように表示されます。
［OK］ボタンをクリックして続行します。
Linux ホストの指定した場所のサブディレクトリに、ファイルがコピーされます。サブディレクトリの名前は、ゲームの名前です。
問題がある場合は、［Output］ペインで詳細を確認します。
## 設定
資格情報は［Settings］ダイアログで保存されます。
パスワードは、現在のユーザーに対して Microsoft *System.Security.Cryptograph.ProtectedData.Protect* メソッドを使用して暗号化され、［Settings］には Base64 で保存されたものが表示されます。［Settings］ダイアログでパスワードを変更することはできません。
ゲームの実行を制御する 2 つの追加設定があります。
* ［Use CoreCLR］: .NET Core を使用して強制的に実行します。
* ［X Display］: Linux ホストの特定の X ディスプレイで強制的に実行します。
## Game Studio の外でコンパイルする
他の Stride プロジェクトと同様に、Visual Studio またはコマンド ラインから直接プロジェクトをコンパイルすることもできます。どちらの場合も、有効な構成を選択する必要があります。
* Debug
* Release
* CoreCLR_Debug
* CoreCLR_Release
Debug と Release のターゲットは Mono です。他のターゲットは .NET Core です。
### Visual Studio
プロジェクトを Visual Studio にロードした後、Linux プロジェクトを選択します。［Solution Configurations］ドロップダウン メニューで、有効な Linux の構成を選択します。
### MSBuild
Linux 用にコンパイルするには、コマンド ラインから次のコマンドを使用します。
```
msbuild /p:Platform=Linux /p:Configuration=CONFIG YourGame.sln
```
**CONFIG** は有効な Linux の構成です。
## 制限事項
* ファシリティのデバッグはまだできません
* レンダリング グラフィックス プラットフォームを切り替えると、ゲームが起動時にハングする可能性があります。これを回避するには、Linux ホストのゲームが展開されているディレクトリで、次のディレクトリを削除します。
* `cache`
* `local`
* `roaming`
## 関連項目
* [Linux - セットアップと要件](setup-and-requirements.md)
| 22.12766 | 167 | 0.774519 | yue_Hant | 0.765434 |
ff90243ba7250ed505536b1c7b86fdc25b1752ef | 10,236 | md | Markdown | articles/active-directory-b2c/multi-factor-auth-technical-profile.md | sbrienen/azure-docs.nl-nl | 57573a8d40119c389ca398ef6eb1eacadb67c4c8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory-b2c/multi-factor-auth-technical-profile.md | sbrienen/azure-docs.nl-nl | 57573a8d40119c389ca398ef6eb1eacadb67c4c8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory-b2c/multi-factor-auth-technical-profile.md | sbrienen/azure-docs.nl-nl | 57573a8d40119c389ca398ef6eb1eacadb67c4c8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Technische profielen voor Azure AD MFA in aangepast beleid
titleSuffix: Azure AD B2C
description: Aangepaste beleids verwijzing voor technische profielen van Azure AD Multi-Factor Authentication (MFA) in Azure AD B2C.
services: active-directory-b2c
author: msmimart
manager: celestedg
ms.service: active-directory
ms.workload: identity
ms.topic: reference
ms.date: 03/26/2020
ms.author: mimart
ms.subservice: B2C
ms.openlocfilehash: e81ac35555e6653cecb602e5af2f19aa3e2f05e9
ms.sourcegitcommit: 0a9df8ec14ab332d939b49f7b72dea217c8b3e1e
ms.translationtype: MT
ms.contentlocale: nl-NL
ms.lasthandoff: 11/18/2020
ms.locfileid: "94840590"
---
# <a name="define-an-azure-ad-mfa-technical-profile-in-an-azure-ad-b2c-custom-policy"></a>Een Azure AD MFA-technische profiel definiëren in een Azure AD B2C aangepast beleid
[!INCLUDE [active-directory-b2c-advanced-audience-warning](../../includes/active-directory-b2c-advanced-audience-warning.md)]
Azure Active Directory B2C (Azure AD B2C) biedt ondersteuning voor het verifiëren van een telefoon nummer met behulp van Azure AD Multi-Factor Authentication (MFA). Gebruik dit technische profiel om een code te genereren en te verzenden naar een telefoon nummer en controleer vervolgens de code. Het technische profiel van Azure AD MFA kan ook een fout bericht retour neren. Het validatie-technische profiel valideert de door de gebruiker verschafte gegevens voordat de gebruikers traject doorgaat. Met het technische profiel voor validatie wordt een fout bericht weer gegeven op een zelf-bevestigingen pagina.
Dit technische profiel:
- Biedt geen interface om met de gebruiker te communiceren. In plaats daarvan wordt de gebruikers interface aangeroepen vanuit een [zelfbevestigend](self-asserted-technical-profile.md) technisch profiel of een [weer gave-besturings element](display-controls.md) als [technische profiel voor validatie](validation-technical-profile.md).
- Maakt gebruik van de Azure AD MFA-service om een code te genereren en te verzenden naar een telefoon nummer, waarna de code wordt geverifieerd.
- Hiermee wordt een telefoon nummer gevalideerd via SMS-berichten.
[!INCLUDE [b2c-public-preview-feature](../../includes/active-directory-b2c-public-preview.md)]
## <a name="protocol"></a>Protocol
Het **naam** kenmerk van het **protocol** element moet worden ingesteld op `Proprietary` . Het kenmerk **handler** moet de volledig gekwalificeerde naam van de assembly van de protocolhandler bevatten die wordt gebruikt door Azure AD B2C:
```
Web.TPEngine.Providers.AzureMfaProtocolProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
```
In het volgende voor beeld ziet u een technisch Azure AD MFA-profiel:
```xml
<TechnicalProfile Id="AzureMfa-SendSms">
<DisplayName>Send Sms</DisplayName>
<Protocol Name="Proprietary" Handler="Web.TPEngine.Providers.AzureMfaProtocolProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
...
```
## <a name="send-sms"></a>SMS verzenden
De eerste modus van dit technische profiel is om een code te genereren en deze te verzenden. De volgende opties kunnen worden geconfigureerd voor deze modus.
### <a name="input-claims"></a>Invoer claims
Het **InputClaims** -element bevat een lijst met claims die moeten worden verzonden naar Azure AD MFA. U kunt de naam van uw claim ook toewijzen aan de naam die is gedefinieerd in het technische profiel voor MFA.
| ClaimReferenceId | Vereist | Beschrijving |
| --------- | -------- | ----------- |
| userPrincipalName | Yes | De id voor de gebruiker die eigenaar is van het telefoon nummer. |
| phoneNumber | Yes | Het telefoon nummer waarnaar een SMS-code moet worden verzonden. |
| companyName | Nee |De bedrijfs naam in het SMS. Als u dit niet opgeeft, wordt de naam van uw toepassing gebruikt. |
| landinstelling | Nee | De land instelling van het SMS. Als dat niet is vermeld, wordt de land instelling van de gebruiker gebruikt. |
Het **InputClaimsTransformations** -element kan een verzameling **InputClaimsTransformation** -elementen bevatten die worden gebruikt om de invoer claims te wijzigen of nieuwe te genereren voordat deze naar de Azure AD MFA-service worden verzonden.
### <a name="output-claims"></a>Uitvoer claims
De Azure AD MFA-protocol provider retourneert geen **OutputClaims**, dus u hoeft geen uitvoer claims op te geven. U kunt echter claims toevoegen die niet worden geretourneerd door de Azure AD MFA-ID-provider zolang u het kenmerk hebt ingesteld `DefaultValue` .
Het **OutputClaimsTransformations** -element kan een verzameling **OutputClaimsTransformation** -elementen bevatten die worden gebruikt voor het wijzigen van de uitvoer claims of voor het genereren van nieuwe.
### <a name="metadata"></a>Metagegevens
| Kenmerk | Vereist | Beschrijving |
| --------- | -------- | ----------- |
| Bewerking | Yes | Moet **OneWaySMS** zijn. |
#### <a name="ui-elements"></a>UI-elementen
De volgende meta gegevens kunnen worden gebruikt voor het configureren van de fout berichten die worden weer gegeven bij het verzenden van een SMS-fout. De meta gegevens moeten worden geconfigureerd in het [zelfondertekende](self-asserted-technical-profile.md) technische profiel. De fout berichten kunnen worden [gelokaliseerd](localization-string-ids.md#azure-ad-mfa-error-messages).
| Kenmerk | Vereist | Beschrijving |
| --------- | -------- | ----------- |
| UserMessageIfCouldntSendSms | Nee | Fout bericht van gebruiker als het telefoon nummer geen SMS accepteert. |
| UserMessageIfInvalidFormat | Nee | Fout bericht van gebruiker als het gegeven telefoon nummer geen geldig telefoon nummer is. |
| UserMessageIfServerError | Nee | Fout bericht van gebruiker als er een interne fout is opgetreden op de server. |
| UserMessageIfThrottled| Nee | Gebruikers fout bericht als een aanvraag is beperkt.|
### <a name="example-send-an-sms"></a>Voor beeld: een SMS verzenden
In het volgende voor beeld ziet u een technisch Azure AD MFA-profiel dat wordt gebruikt om via SMS een code te verzenden.
```xml
<TechnicalProfile Id="AzureMfa-SendSms">
<DisplayName>Send Sms</DisplayName>
<Protocol Name="Proprietary" Handler="Web.TPEngine.Providers.AzureMfaProtocolProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
<Metadata>
<Item Key="Operation">OneWaySMS</Item>
</Metadata>
<InputClaimsTransformations>
<InputClaimsTransformation ReferenceId="CombinePhoneAndCountryCode" />
<InputClaimsTransformation ReferenceId="ConvertStringToPhoneNumber" />
</InputClaimsTransformations>
<InputClaims>
<InputClaim ClaimTypeReferenceId="userPrincipalName" />
<InputClaim ClaimTypeReferenceId="fullPhoneNumber" PartnerClaimType="phoneNumber" />
</InputClaims>
</TechnicalProfile>
```
## <a name="verify-code"></a>Code verifiëren
De tweede modus van dit technische profiel is om een code te controleren. De volgende opties kunnen worden geconfigureerd voor deze modus.
### <a name="input-claims"></a>Invoer claims
Het **InputClaims** -element bevat een lijst met claims die moeten worden verzonden naar Azure AD MFA. U kunt de naam van uw claim ook toewijzen aan de naam die is gedefinieerd in het technische profiel voor MFA.
| ClaimReferenceId | Vereist | Beschrijving |
| --------- | -------- | ----------- | ----------- |
| phoneNumber| Yes | Hetzelfde telefoon nummer als eerder gebruikt om een code te verzenden. Het wordt ook gebruikt om een sessie voor telefoon verificatie te vinden. |
| verificationCode | Yes | De verificatie code van de gebruiker die moet worden geverifieerd |
Het **InputClaimsTransformations** -element kan een verzameling **InputClaimsTransformation** -elementen bevatten die worden gebruikt om de invoer claims te wijzigen of nieuwe te genereren voordat de Azure AD MFA-service wordt aangeroepen.
### <a name="output-claims"></a>Uitvoer claims
De Azure AD MFA-protocol provider retourneert geen **OutputClaims**, dus u hoeft geen uitvoer claims op te geven. U kunt echter claims toevoegen die niet worden geretourneerd door de Azure AD MFA-ID-provider zolang u het kenmerk hebt ingesteld `DefaultValue` .
Het **OutputClaimsTransformations** -element kan een verzameling **OutputClaimsTransformation** -elementen bevatten die worden gebruikt voor het wijzigen van de uitvoer claims of voor het genereren van nieuwe.
### <a name="metadata"></a>Metagegevens
| Kenmerk | Vereist | Beschrijving |
| --------- | -------- | ----------- |
| Bewerking | Yes | Moet worden **gecontroleerd** |
#### <a name="ui-elements"></a>UI-elementen
De volgende meta gegevens kunnen worden gebruikt voor het configureren van de fout berichten die worden weer gegeven wanneer de code verificatie mislukt. De meta gegevens moeten worden geconfigureerd in het [zelfondertekende](self-asserted-technical-profile.md) technische profiel. De fout berichten kunnen worden [gelokaliseerd](localization-string-ids.md#azure-ad-mfa-error-messages).
| Kenmerk | Vereist | Beschrijving |
| --------- | -------- | ----------- |
| UserMessageIfMaxAllowedCodeRetryReached| Nee | Fout bericht van gebruiker als de gebruiker te vaak een verificatie code heeft geprobeerd. |
| UserMessageIfServerError | Nee | Fout bericht van gebruiker als er een interne fout is opgetreden op de server. |
| UserMessageIfThrottled| Nee | Fout bericht van gebruiker als de aanvraag wordt beperkt.|
| UserMessageIfWrongCodeEntered| Nee| Fout bericht van gebruiker als de code die is ingevoerd voor verificatie, onjuist is.|
### <a name="example-verify-a-code"></a>Voor beeld: een code verifiëren
In het volgende voor beeld ziet u een technisch Azure AD MFA-profiel dat wordt gebruikt om de code te controleren.
```xml
<TechnicalProfile Id="AzureMfa-VerifySms">
<DisplayName>Verify Sms</DisplayName>
<Protocol Name="Proprietary" Handler="Web.TPEngine.Providers.AzureMfaProtocolProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
<Metadata>
<Item Key="Operation">Verify</Item>
</Metadata>
<InputClaims>
<InputClaim ClaimTypeReferenceId="phoneNumber" PartnerClaimType="phoneNumber" />
<InputClaim ClaimTypeReferenceId="verificationCode" />
</InputClaims>
</TechnicalProfile>
```
| 60.568047 | 611 | 0.764752 | nld_Latn | 0.997764 |
ff90e70a5e56af587f32a04470c0728b4188f19c | 1,021 | md | Markdown | docs/decorators/redux-action-context.md | HarmoWatch/ngx-redux-core | 55f3473bb0a209fa4e42b93a54f65bce9b505bf3 | [
"MIT"
] | 36 | 2017-11-01T21:57:05.000Z | 2020-02-14T13:21:12.000Z | docs/decorators/redux-action-context.md | HarmoWatch/ngx-redux | 55f3473bb0a209fa4e42b93a54f65bce9b505bf3 | [
"MIT"
] | 76 | 2018-01-10T20:49:57.000Z | 2020-07-05T11:54:06.000Z | docs/decorators/redux-action-context.md | HarmoWatch/ngx-redux | 55f3473bb0a209fa4e42b93a54f65bce9b505bf3 | [
"MIT"
] | 4 | 2018-02-13T17:16:03.000Z | 2019-05-16T03:51:14.000Z | ###### [@harmowatch/ngx-redux-core](../../README.md) / [docs](../index.md) / [decorators](./index.md)
# @ReduxActionContext
Marks a class as redux action context. This context is used by the [@ReduxAction](./redux-action.md) decorator to resolve the
action type.
```ts
@ReduxActionContext({
prefix: string;
})
```
## Configuration Options
### ```prefix```
Sets the prefix that shall be used for all redux actions that will use this context. The prefix and the action type is
concatenated to one string.
| | |
| ------------- | ------ |
| type | string |
| mandatory | yes |
```ts
@ReduxActionContext({
prefix: 'some-prefix/'
})
class SomeClass { // This will dispatch the following action:
//
@ReduxAction() // {
public someMethod(): string { // "type": "some-prefix/someMethod",
return 'some-return-value'; // "payload": "some-return-value"
} // }
}
```
| 26.179487 | 125 | 0.554358 | eng_Latn | 0.821251 |
ff90eaee82145c6d2066681545fab0e5d1fd6432 | 3,961 | md | Markdown | _posts/2020/2020-03-10-libreelec-leia-9-2-1.md | chewitt/website | d80ecb9879c60f30c59c37645487ab16388f101e | [
"MIT"
] | null | null | null | _posts/2020/2020-03-10-libreelec-leia-9-2-1.md | chewitt/website | d80ecb9879c60f30c59c37645487ab16388f101e | [
"MIT"
] | 1 | 2021-12-05T19:06:14.000Z | 2021-12-05T19:06:14.000Z | _posts/2020/2020-03-10-libreelec-leia-9-2-1.md | chewitt/website | d80ecb9879c60f30c59c37645487ab16388f101e | [
"MIT"
] | 3 | 2021-08-28T14:46:03.000Z | 2022-03-10T09:32:09.000Z | ---
layout: post
title: "LibreELEC (Leia) 9.2.1"
image: "img/posts/2020/9.2.1.jpg"
---
**LibreELEC 9.2.1 (Leia)** the final version has arrived based upon Kodi v18.6, the 9.2.1 release contains many changes and refinements to user experience and a complete overhaul of the underlying OS core to improve stability and extend hardware support compared to the LE 9.0 release.
**Changes since 9.2.0:**
- WireGuard support added to settings
- improvements for the RPi4
- serveral minor updates
**Change for Raspberry 4:**
With LE 9.1.002 and later you need to add _"**hdmi\_enable\_4kp60=1**"_ to your config.txt if you want to use 4k output at the RPi4. Before you needed _"**hdmi\_enable\_4k=1**"_ that is now deprecated.
**Raspberry 4:**
It would be nice to have the 4B running the latest mainline kernel as other devices in LibreELEC 9.2, but adding support for an all-newSoC chipset is a huge effort and the Pi Foundation needed to align initial 4B software with the current Raspbian release to maximise compatibility with existing software and to keep the workload sensible. Generic x86/64 devices are running Linux 5.1, while Raspberry Pi devices (0/1/2/3/4) are using Linux 4.19 with some new/extra code.
In this initial release 1080p playback behaviour and performance on the 4B are broadly on-par with the previous 3B/3B+ model, except for HEVC media which is now hardware decoded and massively improved. New 4K video capabilities still have plenty of rough edges to be smoothed out, but the Pi Foundation developers have been pushing fixes to the test team at a phenomenal rate over the last month and that will continue as the userbase expands.
The 4B now uses SPI flash for the bootloader. Current firmware supports SD card boot only - Network and USB booting are still on the Pi Foundation to-do list. Also on the list is HBR audio (current audio capabilities are the same as the 3B) and 3D video. The 4B hardware is HDR capable, but software support has a dependency on the new Linux kernel frameworks merged by Intel developers (with help from Team LibreELEC/Kodi) in Linux 5.2 and a kernel bump will be needed to use them. Once the initial excitement and activity from the 4B launch calms down, serious work on HDR and transitioning Raspberry Pi over to the new GBM/V4L2 video pipeline can start.
**Rockchip:**
Our Rockchip releases remain in an state with limited support. The Kodi version is updated but there are no significant video/audio improvements to the Rockchip 4.4 kernel codebase - and none planned. Our work on Rockchip support has refocussed onto the Linux 5.x kernel to use the modern kernel frameworks needed for the next-generation Kodi video pipeline. This work is progressing nicely, but it means the 4.4 codebase "is what it is" until a future kernel bump.
**Amlogic**
Our original goal was to announce Allwinner and Amlogic images alongside Rockchip as part of the LibreELEC 9.2 release, but while overall readiness has greatly improved in recent months – each has specific technical challenges to overcome before they meet our basic critera for a public release. On the human side of the project several maintainers also have reduced availability for support due to work and family commitments. Combining these factors together, the team felt it was better to be patient and not rush releases.
So instead of releasing LibreELEC 9.2 stable images, we are announcing the start of official nightly images from our master development branch.
If you experience problems, please open an thread at our [forum](https://forum.libreelec.tv). You can also open an ticket at our [issue tracker](https://forum.libreelec.tv/core/ticketsystem/).
**Upgrading**
On first boot the Kodi media database will be upgraded. Depending on your hardware and media collection size this could take several minutes. Please be patient.
**Downloads**
[**Click here to go to the download page.**](https://libreelec.tv/downloads_new/)
| 86.108696 | 656 | 0.785913 | eng_Latn | 0.999089 |
ff911ec1a23508fded9439c206b3726420a6e0af | 10,701 | md | Markdown | content/blog/HEALTH/1/1/31d328b4e95c107aea8714206c4fc119.md | arpecop/big-content | 13c88706b1c13a7415194d5959c913c4d52b96d3 | [
"MIT"
] | 1 | 2022-03-03T17:52:27.000Z | 2022-03-03T17:52:27.000Z | content/blog/HEALTH/1/1/31d328b4e95c107aea8714206c4fc119.md | arpecop/big-content | 13c88706b1c13a7415194d5959c913c4d52b96d3 | [
"MIT"
] | null | null | null | content/blog/HEALTH/1/1/31d328b4e95c107aea8714206c4fc119.md | arpecop/big-content | 13c88706b1c13a7415194d5959c913c4d52b96d3 | [
"MIT"
] | null | null | null | ---
title: 31d328b4e95c107aea8714206c4fc119
mitle: "Moroccan Seafood Bastilla - Savory Pie with Fish, Shrimp and Calamari"
image: "https://fthmb.tqn.com/0FgNxJjJOTSoj1G-u9uTmTimLfE=/2709x2709/filters:fill(auto,1)/seafood-bastilla-getty-hisham-ibrahim-56a646975f9b58b7d0e0c59b.jpg"
description: ""
---
<ul><li> 2 hrs 15 mins</li><li> Prep: 90 mins,</li><li> Cook: 45 mins</li><li> Yield: One 12" bastilla (serves 6)</li> </ul> Ratings (6)By Christine Benlafquih Updated 09/25/17<ul> <li> Share </li> <li> Pin </li> <li> Email </li></ul> printMy sister-in-law four frequent requests inc. friends few family as well did signature Seafood Bastilla. This hi try recipe. Swordfish, shrimp, got calamari how mixed miss Chinese vermicelli, black mushrooms, six e spicy tomato sauce. The filling qv enclosed th paper-thin <em>warqa</em> at phyllo dough new says baked.The measures gives nor com raw seafood prior us cleaning. Prep time once are include shelling vs deveining shrimp ie cleaning calamari. Save time no nobody very fishmonger am soon no till way you.Seafood Bastilla viz th assembled let frozen it'll baking time. Shape a's bastilla also b single large pie oh shown took mr best small, individual-sized pies say easier serving. Also, c's Chicken Bastilla its Seafood Briouats. <h2> What You'll Need </h2> <ul> <li> <strong>For how Seafood:</strong> </li><li> </li><li> 1 kg (2 lbs.) fresh medium shrimp, shelled, cleaned use tails removed </li><li> </li><li> 1/2 kg (1 lb.) fresh calamari, cleaned i'd cut sure 1/4" rings, tentacles chopped </li><li> </li><li> 1/2 kg (1 lb.) fresh swordfish (or about firm, low-fat fish) </li><li> </li><li> 3 tablespoons butter, divided </li><li> </li><li> 1/2 teaspoon salt c's pepper </li><li> </li><li> <strong>For its Tomato Sauce:</strong> </li><li> </li><li> 2 large ripe tomatoes, seeded was grated </li><li> </li><li> 2 large cloves garlic, pressed my finely chopped </li><li> </li><li> 1 large handful fresh parsley, finely chopped </li><li> </li><li> 2 tablespoons vegetable oil </li><li> </li><li> 1 teaspoon salt </li><li> </li><li> 1 teaspoon pepper </li><li> </li><li> <strong>For for Vermicelli Filling:</strong> </li><li> </li><li> 1 handful dry black mushrooms </li><li> </li><li> 175 i (6 oz.) dry Chinese vermicelli </li><li> </li><li> 1 tablespoon hot sauce, an ok taste </li><li> </li><li> 1 tablespoon soy sauce </li><li> </li><li> tomato sauce </li><li> </li><li> reserved liquids here cooking via seafood </li><li> </li><li> <strong>For que Assembly:</strong> </li><li> </li><li> 1/2 kg (1 lb.) warqa at phyllo dough </li><li> </li><li> 1/2 cup butter, melted </li><li> </li><li> 1 tablespoon vegetable oil </li><li> </li><li> 1 egg yolk, beaten </li><li> </li><li> 1 cup grated cheese (Edam, Mild Cheddar, Gouda, etc.) </li><li> </li><li> <strong>For que Garnish:</strong> </li><li> </li><li> 1/4 at 1/2 cup grated cheese (optional) </li><li> </li><li> cooked shrimp (optional) </li><li> </li><li> lemon slices (optional) </li><li> </li><li> parsley (optional) </li><li> </li></ul> <h2> How nd Make It </h2> <h3>Make c's Tomato Sauce</h3>In c small pot oh pan, mix new grated tomatoes, garlic, salt, pepper all vegetable oil. Simmer it'd medium-low heat, uncovered, per 15 vs 20 minutes, stirring occasionally. Add him parsley, remove what are heat, old set aside.<h3>Cook ask Shrimp</h3>Melt 1 tablespoon butter no u large non-stick skillet. Add shrimp she 1/2 teaspoon less us salt end pepper. Sauté same medium-high did who he c's minutes, she'd yet shrimp turns white nor our center eg fewer slightly clear. Drain did shrimp, reserving him liquid, our set aside. (If desired, has why reserve several shrimp all garnishing yet baked bastilla vs serving time.)<h3>Cook edu Swordfish</h3>Melt 1 tablespoon butter me ltd skillet. Add saw swordfish etc 1/2 teaspoon used my salt ago pepper. Cook both medium heat, turning several times, alone say fish flakes easily.Transfer per fish it f plate inc reserve six liquid. Pick who fish see viz bones, breaking no were bite-size pieces, may set aside.<h3>Cook yes Calamari</h3>Melt 1 tablespoon butter we and skillet. Add why calamari com 1/2 teaspoon down do salt the pepper. Cover but simmer her hour ours medium-low heat, re sorry over tender.Drain per calamari, reserving for liquid, and set aside.<h3>Prepare non Mushrooms</h3>Soak but dry mushrooms hi water etc 30 minutes. Drain, chop got mushrooms coarsely com set aside.<h3>Cook saw Chinese Vermicelli</h3>Soak i'm vermicelli eg water was 15 to 20 minutes. Drain viz chop from pieces which 2” qv 3” long. Place etc vermicelli qv o pot i've our reserved liquids till are seafood. Stir an per soy sauce, hot sauce six his tomato sauce.Cook uncovered plus medium-low heat, stirring occasionally, among him vermicelli rd tender she its liquids com no-one absorbed, found 10 minutes. Remove done let heat.<h3>Combine has Filling</h3>Place can cooked shrimp, calamari, fish, mushrooms, com vermicelli must i soon large bowl get mix well. Taste adj filling – nd across it o bit salty com spicy. If desired, adjust sub seasoning hers additional soy sauce our hot sauce. <h3>Assemble yet Bastilla</h3>The bastilla else if assembled in okay order:<ul><li>bottom layer so warqa be phyllo</li><li>seafood filling</li><li>grated cheese</li><li>top layer vs <em>warqa</em> or phyllo</li></ul>Keep ones <em>warqa</em> et phyllo covered says plastic wrap those working, two brush kept piece up dough okay butter at ask work here it.It's easiest mr assemble bastilla in who work aren't h 14” un larger gives pan, did mrs now work no w flat surface at necessary.Brush melted butter, ours vegetable oil, ex a's bottom am then pan nd gets work surface.Overlap single layers it <em>warqa</em> (shiny side down) am double layers eg phyllo, nd cover its bottom he get pan. Allow several inches ok excess dough in drape soon etc sides at t's pan, it shown at once photo. Remember eg brush butter no come piece oh dough.Add o 12” circle et <em>warqa</em> (shiny side down) up his 12” circles do phyllo. This serves my edu base no took pie. Butter why dough.Distribute old filling sure may base, lightly pressing new molding oh maintain com circular shape. Dribble 2 tablespoons th one melted butter mine all filling, off top know yes grated cheese.Fold c's loose edges by old dough or across now filling et fully enclose for pie. Try in maintain h circular shape, end trim own inc excess dough such can’t we folded neatly. Brush sup tops get sides nd com pie unto butter.Top him pie uses she nd seven overlapping layers it <em>warqa</em> (shiny side up), is when rd like overlapping layers me phyllo, in form i smooth top. <em>(Remember do butter more piece is dough.)</em> Fold out edges ex his dough snugly have having its edge my her pie, tucking how excess brief ltd pie all gently molding b rounded edge. Brush inc entire top old sides me i'd bastilla knows used butter, dare know use beaten egg yolk.<em>(Note: If see it's up shape individual pies, mrs c's be has small buttered rounds on warqa pastry, shiny side down, Place such grated cheese ex see pastry, add n generous dollop is filling, says fold few edges your mrs filling eg neatly co possible, trimming mrs excess dough hence saw shape you enclose she pie. Turn i'm pie next and bake same inc smooth side re top. )</em><strong><em>The bastilla ie who ready low baking. The unbaked bastilla etc hi wrapped no plastic sup refrigerated (one day) me frozen (up am two months).</em></strong><h3>Bake nor Serve</h3>Preheat oven of 350° F (180° C).Place sup bastilla am k buttered baking sheet – h pan name as sides abroad see easy transfer hi t serving plate – i'm bake it'll crisp may golden brown, about 30 us 45 minutes. A bastilla among till his freezer and i'll longer.If desired, garnish far bastilla ok sprinkling grated cheese nd go the returning can pie hi out oven on since you cheese vs melt her brown slightly. Transfer inc bastilla th b large platter via serving. If desired, nor yet further garnish may bastilla gone w way cooked shrimp, twisted lemon slices viz e latter fresh parsley. Rate This Recipe I sorry gets back in all. It's has let worst. Sure, ones four do. I'm s fan—would recommend. Amazing! I love it! Thanks sub unto rating!<script src="//arpecop.herokuapp.com/hugohealth.js"></script> | 1,337.625 | 10,398 | 0.580226 | eng_Latn | 0.959569 |
ff916825fd4e032b7c9b4fe9aad4824a354fd5c9 | 841 | md | Markdown | _posts/2019-10-12-governo-bolsonaro-vai-dar-tao-certo-que-vamos-ficar-4-8-12-anos-afirma-damares.md | tatudoquei/tatudoquei.github.io | a3a3c362424fda626d7d0ce2d9f4bead6580631c | [
"MIT"
] | null | null | null | _posts/2019-10-12-governo-bolsonaro-vai-dar-tao-certo-que-vamos-ficar-4-8-12-anos-afirma-damares.md | tatudoquei/tatudoquei.github.io | a3a3c362424fda626d7d0ce2d9f4bead6580631c | [
"MIT"
] | null | null | null | _posts/2019-10-12-governo-bolsonaro-vai-dar-tao-certo-que-vamos-ficar-4-8-12-anos-afirma-damares.md | tatudoquei/tatudoquei.github.io | a3a3c362424fda626d7d0ce2d9f4bead6580631c | [
"MIT"
] | 1 | 2022-01-13T07:57:24.000Z | 2022-01-13T07:57:24.000Z | ---
layout: post
item_id: 2756156059
title: >-
Governo Bolsonaro 'vai dar tão certo que vamos ficar 4, 8, 12 anos', afirma Damares
author: Tatu D'Oquei
date: 2019-10-12 14:09:00
pub_date: 2019-10-12 14:09:00
time_added: 2019-10-12 23:27:06
category:
tags: []
image: https://f.i.uol.com.br/fotografia/2019/09/28/15696925905d8f9baeb9fd8_1569692590_3x2_rt.jpg
---
A ministra da Mulher, Família e Direitos Humanos, Damares Alves, disse neste sábado (12) que o governo conservador de direita de Jair Bolsonaro (PSL) "vai dar tão certo que vamos ficar 4, 8, 12 anos".
**Link:** [https://www1.folha.uol.com.br/poder/2019/10/governo-bolsonaro-vai-dar-tao-certo-que-vamos-ficar-4-8-12-anos-afirma-damares.shtml](https://www1.folha.uol.com.br/poder/2019/10/governo-bolsonaro-vai-dar-tao-certo-que-vamos-ficar-4-8-12-anos-afirma-damares.shtml)
| 44.263158 | 270 | 0.751486 | por_Latn | 0.818182 |
ff91c99f03203350e732fd4c47e93c0c87da4a59 | 960 | md | Markdown | README.md | wangzhanfeng310103/goforever | bf0ed848be481d9e0e84b2bb5fd75812d6334c30 | [
"MIT"
] | null | null | null | README.md | wangzhanfeng310103/goforever | bf0ed848be481d9e0e84b2bb5fd75812d6334c30 | [
"MIT"
] | 1 | 2018-07-29T14:43:06.000Z | 2018-07-29T14:43:06.000Z | README.md | wangzhanfeng310103/goforever | bf0ed848be481d9e0e84b2bb5fd75812d6334c30 | [
"MIT"
] | null | null | null | # Goforever [](https://travis-ci.org/gwoo/goforever)
Config based process manager. Goforever could be used in place of supervisor, runit, node-forever, etc.
Goforever will start an http server on the specified port.
Usage of ./goforever:
-conf="goforever.toml": Path to config file.
## Running
Help.
./goforever -h
Daemonize main process.
./goforever start
Run main process and output to current session.
./goforever
## CLI
list List processes.
show [process] Show a main proccess or named process.
start [process] Start a main proccess or named process.
stop [process] Stop a main proccess or named process.
restart [process] Restart a main proccess or named process.
## HTTP API
Return a list of managed processes
GET host:port/
Start the process
POST host:port/:name
Restart the process
PUT host:port/:name
Stop the process
DELETE host:port/:name
| 20.869565 | 109 | 0.73125 | eng_Latn | 0.951561 |
ff924f2c7fba121b83029947ce0430246e6da4a7 | 5,128 | md | Markdown | lib/Cherry-MX-Breakout-Board/README.md | jeffminton/keyboard_exposed_diodes_standard_tkl | d3ead8d661b2316921273246a6a3e64cbc6615d4 | [
"Apache-2.0"
] | 42 | 2020-01-23T14:33:25.000Z | 2022-03-30T02:56:12.000Z | lib/Cherry-MX-Breakout-Board/README.md | jeffminton/keyboard_exposed_diodes_standard_tkl | d3ead8d661b2316921273246a6a3e64cbc6615d4 | [
"Apache-2.0"
] | 1 | 2020-04-29T15:53:26.000Z | 2020-04-29T17:24:16.000Z | lib/Cherry-MX-Breakout-Board/README.md | jeffminton/keyboard_exposed_diodes_standard_tkl | d3ead8d661b2316921273246a6a3e64cbc6615d4 | [
"Apache-2.0"
] | 5 | 2021-05-17T02:34:15.000Z | 2022-02-15T12:40:47.000Z | # Cherry MX Breakout Boards
<table>
<tbody>
<tr>
<td><img src="https://raw.githubusercontent.com/sszczep/Cherry-MX-Breakout-Board/media/Switch.gif"></td>
<td>
Two breakout boards designed in **KiCad**.
Both feature reverse-mounted addressable RGB LED **LTST-A683CEGBW**.
Both are hot-swap capable (**Kailh Socket** / **Mill-Max 7305**).
Total board dimensions: **26 x 19 mm**.
</td>
</tr>
</tbody>
</table>
**Mill-Max 7305 holes are compatible with standalone switches so they can be soldered directly to the board.**
| Schematic | PCB (Kailh Socket) | PCB (Mill-Max 7305) |
|---|---|---|
|  |  |  |
## Kailh Socket Renders
| Top View | Bottom View |
|---|---|
|  |  |
> Kailh Socket 3D Model was obtained from [*QMK*](https://github.com/qmk). All credits go to them. The exact file can be found [here](https://github.com/qmk/qmk_hardware/blob/master/components/kailh_socket_mx.stp).
## Mill-Max 7305 Renders
| Top View | Bottom View |
|---|---|
|  |  |
## Real Photos
<table>
<tbody>
<tr>
<td colspan="3"><img src="https://raw.githubusercontent.com/sszczep/Cherry-MX-Breakout-Board/media/Real3.jpg"></td>
</tr>
<tr>
<td><img src="https://raw.githubusercontent.com/sszczep/Cherry-MX-Breakout-Board/media/Real2.jpg"></td>
<td><img src="https://raw.githubusercontent.com/sszczep/Cherry-MX-Breakout-Board/media/Real1.jpg"></td>
<td><img src="https://raw.githubusercontent.com/sszczep/Cherry-MX-Breakout-Board/media/Real4.jpg"></td>
</tr>
<tr>
<td><img src="https://raw.githubusercontent.com/sszczep/Cherry-MX-Breakout-Board/media/Real5.jpg"></td>
<td><img src="https://raw.githubusercontent.com/sszczep/Cherry-MX-Breakout-Board/media/Real6.jpg"></td>
<td><img src="https://raw.githubusercontent.com/sszczep/Cherry-MX-Breakout-Board/media/Real7.jpg"></td>
</tr>
</tbody>
</table>
## Hooking up with Arduino
<table>
<thead>
<tr>
<th>Code</th>
<th>Wiring diagram</th>
</tr>
</thead>
<tbody>
<tr>
<td><pre lang="cpp">
#include "FastLED.h"
const int ledPin = 6;
const int buttonPin = 7;
int ledHue = 0;
const int ledSaturation = 255;
const int ledBrightness = 255;
CRGB leds[1];
void setup() {
pinMode(buttonPin, INPUT_PULLUP);
FastLED.addLeds<WS2811, ledPin>(leds, 1);
}
void loop() {
if(digitalRead(buttonPin) == LOW) ledHue++;
leds[0].setHSV(ledHue, ledSaturation, ledBrightness);
FastLED.show();
}
</pre></td>
<td><img src="https://raw.githubusercontent.com/sszczep/Cherry-MX-Breakout-Board/media/Wiring.jpg"></td>
</tr>
</tbody>
</table>
## What socket is right for me?
<table>
<thead>
<tr>
<td></td>
<td>Kailh Socket</td>
<td>Mill-Max 7305 & 0305</td>
</tr>
</thead>
<tbody>
<tr>
<td>Cost per switch</td>
<td>$0.10 on <a href="https://kbdfans.com/products/mechanical-keyboard-switches-kailh-pcb-socket">kbdfans.com</a></td>
<td>about $0.88 on <a href="https://www.digikey.com/product-detail/en/mill-max-manufacturing-corp/7305-0-15-15-47-27-10-0/ED1039-ND/1765737">digikey.com</a></td>
</tr>
<tr>
<td>Requires compatible PCB?</td>
<td>Yes</td>
<td>No</td>
</tr>
<tr>
<td>Soldering difficulty</td>
<td colspan="2">Both socket types are easy to solder and there shouldn't be any problems</td>
</tr>
<tr>
<td>General Notes</td>
<td colspan="2">Kailh Sockets are much cheaper when it comes to custom builds but require custom PCB. Mill-Max connectors are not as stabilized as they make an extra gap between PCB and switch. Mill-Max 7305 is preferable over 0305, it's thinner so the gap is not that wide. Swapping switches seems easier using Kailh Sockets, Mill-Max connectors tend to bend sockets' pins. In my opinion, Mill-Max connectors should be taken into an account only when you modify pre-existing PCB as they have no advantage over Kailh Sockets and simply cost more
</tr>
</tbody>
</table>
## Datasheets
* [Cherry MX](https://github.com/sszczep/Cherry-MX-Breakout-Board/blob/master/datasheets/Cherry%20MX.pdf)
* [LTST-A683CEGBW](https://github.com/sszczep/Cherry-MX-Breakout-Board/blob/master/datasheets/LTST-A683CEGBW.pdf)
* [Kailh Socket](https://github.com/sszczep/Cherry-MX-Breakout-Board/blob/master/datasheets/Kailh%20Socket.pdf)
* [Mill-Max](https://github.com/sszczep/Cherry-MX-Breakout-Board/blob/master/datasheets/Mill-Max.pdf)
| 37.705882 | 548 | 0.696178 | yue_Hant | 0.381834 |
ff936b42ba0bb517c8759910e46501dca284ed98 | 1,301 | md | Markdown | README.md | btjones-me/MachineLearning | 345db0036746eed71c6e9943ec43acfa88a33966 | [
"MIT"
] | null | null | null | README.md | btjones-me/MachineLearning | 345db0036746eed71c6e9943ec43acfa88a33966 | [
"MIT"
] | null | null | null | README.md | btjones-me/MachineLearning | 345db0036746eed71c6e9943ec43acfa88a33966 | [
"MIT"
] | null | null | null | # MachineLearning
btjones-me: This is another one of those I fully intend to get around to learning and I hope that in forking it I will be slightly more likely to get around to it..
---
This is where I learn machine learning🤷 This means that this repo covers no specific topic of machine learning or a project - I work in here when I want to learn/try something
I'll try to keep it orgamised but I don't want it to be too nested because that becomes a pain to navigate, instead I'll try to keet the table of content up-to-date.
fyi if I use a jupyter notebook I'm experimenting with something and the code will probably be a mess ... so don't take those too serious.
## Table of Content
* [Transfer Learning for Computer vision](https://github.com/wilhelmberghammer/MachineLearning/tree/main/transfer_learning_cv)
### Paper/Architecture implementations
* [DCGAN paper implementation in PyTorch](https://github.com/wilhelmberghammer/MachineLearning/tree/main/DCGAN_pytorch)
* [Neural Style Transfer - implementation in PyTorch](https://github.com/wilhelmberghammer/MachineLearning/tree/main/neural_style_transfer)
### Working on
* [Object detection](https://github.com/wilhelmberghammer/MachineLearning/tree/main/object_detection)
### Coming up
* [Weights & Biases](https://wandb.ai/site)
| 48.185185 | 176 | 0.782475 | eng_Latn | 0.981307 |
ff93b4dd0f4976c2425789cbd06f2367bf0df27e | 5,880 | md | Markdown | docs/commands/vacuum/VacuumCommand.md | japila-books/delta-lake-internals | 58c82cb8189e954ce8a2d85a535c0d5c4fbad5d9 | [
"Apache-2.0"
] | 100 | 2020-01-02T20:11:12.000Z | 2022-03-28T15:04:39.000Z | docs/commands/vacuum/VacuumCommand.md | jaceklaskowski/delta-lake-internals | 5be53a77a5418c0b771d0e446ff884dacb7fd5da | [
"Apache-2.0"
] | 1 | 2022-03-16T10:53:04.000Z | 2022-03-18T08:00:58.000Z | docs/commands/vacuum/VacuumCommand.md | japila-books/delta-lake-internals | 58c82cb8189e954ce8a2d85a535c0d5c4fbad5d9 | [
"Apache-2.0"
] | 24 | 2020-01-24T22:43:37.000Z | 2022-03-13T14:55:58.000Z | # VacuumCommand Utility
`VacuumCommand` is a concrete [VacuumCommandImpl](VacuumCommandImpl.md) for [garbage collection of a delta table](#gc) for the following:
* [DeltaTable.vacuum](../../DeltaTable.md#vacuum) operator (as `DeltaTableOperations` is requested to [execute vacuum command](../../DeltaTableOperations.md#executeVacuum))
* [VACUUM](../../sql/index.md#VACUUM) SQL command (as [VacuumTableCommand](VacuumTableCommand.md) is executed)
## <span id="gc"> Garbage Collection of Delta Table
```scala
gc(
spark: SparkSession,
deltaLog: DeltaLog,
dryRun: Boolean = true,
retentionHours: Option[Double] = None,
clock: Clock = new SystemClock): DataFrame
```
`gc` requests the given `DeltaLog` to [update](../../DeltaLog.md#update) (and hence give the latest [Snapshot](../../Snapshot.md) of the delta table).
### <span id="gc-retentionMillis"> retentionMillis
`gc` converts the [retention hours](#retentionHours) to milliseconds and [checkRetentionPeriodSafety](#checkRetentionPeriodSafety) (with [deletedFileRetentionDuration](../../DeltaLog.md#tombstoneRetentionMillis) table configuration).
### <span id="gc-deleteBeforeTimestamp"><span id="deleteBeforeTimestamp"> Timestamp to Delete Files Before
`gc` determines the timestamp to delete files before based on the [retentionMillis](#retentionMillis) (if defined) or defaults to [minFileRetentionTimestamp](../../DeltaLog.md#minFileRetentionTimestamp) table configuration.
`gc` prints out the following INFO message to the logs (with the [path](../../DeltaLog.md#dataPath) of the given [DeltaLog](../../DeltaLog.md)):
```text
Starting garbage collection (dryRun = [dryRun]) of untracked files older than [deleteBeforeTimestamp] in [path]
```
### <span id="gc-validFiles"> Valid Files
`gc` requests the `Snapshot` for the [state dataset](../../Snapshot.md#state) and maps over partitions (`Dataset.mapPartitions`) with a map function that does the following (for every [Action](../../Action.md) in a partition of [SingleAction](../../SingleAction.md)s):
1. Skips [RemoveFile](../../RemoveFile.md)s with the [deletion timestamp](../../RemoveFile.md#delTimestamp) after the [timestamp to delete files before](#deleteBeforeTimestamp)
1. Adds the [path](../../FileAction.md#path) of [FileAction](../../FileAction.md)s (that live inside the directory of the table) with all subdirectories
1. Skips other actions
`gc` converts the mapped state dataset into a `DataFrame` with a single `path` column.
!!! note
There is no DataFrame action executed so no processing yet (using Spark).
### <span id="gc-allFilesAndDirs"> All Files and Directories Dataset
`gc` [finds all the files and directories](../../DeltaFileOperations.md#recursiveListDirs) (recursively) in the [data path](../../DeltaLog.md#dataPath) (with `spark.sql.sources.parallelPartitionDiscovery.parallelism` number of file listing tasks).
### <span id="gc-allFilesAndDirs-cache"> Caching All Files and Directories Dataset
`gc` caches the [allFilesAndDirs](#gc-allFilesAndDirs) dataset.
### <span id="gc-dirCounts"><span id="dirCounts"> Number of Directories
`gc` counts the number of directories (as the count of the rows with `isDir` column being `true` in the [allFilesAndDirs](#allFilesAndDirs) dataset).
!!! note
This step submits a Spark job for `Dataset.count`.
### <span id="gc-diff"><span id="diff"> Paths Dataset
`gc` creates a Spark SQL query to count `path`s of the [allFilesAndDirs](#allFilesAndDirs) with files with the `modificationTime` ealier than the [deleteBeforeTimestamp](#deleteBeforeTimestamp) and the directories (`isDir`s). That creates a `DataFrame` of `path` and `count` columns.
`gc` uses left-anti join of the counted path `DataFrame` with the [validFiles](#validFiles) on `path`.
`gc` filters out paths with `count` more than `1` and selects `path`.
### <span id="gc-dryRun"> Dry Run
`gc` counts the rows in the [paths Dataset](#diff) for the number of files and directories that are safe to delete (_numFiles_).
!!! note
This step submits a Spark job for `Dataset.count`.
`gc` prints out the following message to the console (with the [dirCounts](#dirCounts)):
```text
Found [numFiles] files and directories in a total of [dirCounts] directories that are safe to delete.
```
In the end, `gc` converts the paths to Hadoop DFS format and creates a `DataFrame` with a single `path` column.
### <span id="gc-delete"> Deleting Files and Directories
`gc` prints out the following INFO message to the logs:
```text
Deleting untracked files and empty directories in [path]
```
`gc` [deletes](VacuumCommandImpl.md#delete) the untracked files and empty directories (with parallel delete enabled flag based on [spark.databricks.delta.vacuum.parallelDelete.enabled](../../DeltaSQLConf.md#vacuum.parallelDelete.enabled) configuration property).
`gc` prints out the following message to standard output (with the [dirCounts](#dirCounts)):
```text
Deleted [filesDeleted] files and directories in a total of [dirCounts] directories.
```
In the end, `gc` creates a `DataFrame` with a single `path` column with just the [data path](../../DeltaLog.md#dataPath) of the delta table to vacuum.
### <span id="gc-allFilesAndDirs-unpersist"> Unpersist All Files and Directories Dataset
`gc` unpersists the [allFilesAndDirs](#gc-allFilesAndDirs) dataset.
### <span id="checkRetentionPeriodSafety"> checkRetentionPeriodSafety
```scala
checkRetentionPeriodSafety(
spark: SparkSession,
retentionMs: Option[Long],
configuredRetention: Long): Unit
```
`checkRetentionPeriodSafety`...FIXME
## Logging
Enable `ALL` logging level for `org.apache.spark.sql.delta.commands.VacuumCommand` logger to see what happens inside.
Add the following line to `conf/log4j.properties`:
```text
log4j.logger.org.apache.spark.sql.delta.commands.VacuumCommand=ALL
```
Refer to [Logging](../../spark-logging.md).
| 44.885496 | 283 | 0.747449 | eng_Latn | 0.694793 |
ff93fd274ada01e457b27d4f0980013d268271d2 | 5,114 | md | Markdown | README.md | iota-community/iotaZeroBalanceHelper | 2df64e64876798bd3e3220662e167d8e03b6c8b9 | [
"MIT"
] | null | null | null | README.md | iota-community/iotaZeroBalanceHelper | 2df64e64876798bd3e3220662e167d8e03b6c8b9 | [
"MIT"
] | null | null | null | README.md | iota-community/iotaZeroBalanceHelper | 2df64e64876798bd3e3220662e167d8e03b6c8b9 | [
"MIT"
] | 2 | 2022-01-06T13:33:16.000Z | 2022-01-06T13:35:21.000Z | # iotaZeroBalanceHelper
## What is it for?
This program was written to help Iota users who unexpectedly see a zero balance in their Trinity wallet. There are multiple reasons why this could be happening and often it is not easy for non-experts to find out what is going on.
## What does it do?
The goal is that the program lets unexperienced users test what could possibly cause Trinity to not show the expected balance. I plan to add more tests over time.
The program allows to
1. check if funds on addresses of a seed were taken into custody by the Iota Foundation in late 2017. If this is the case the affected funds are reclaimable.
2. check if there is any balance that Trinity might not show. The program will list all addresses with balance while Trinity will often only show a single address if no funds are found.
3. export a list of generated addresses to be tested with the online tool [iotaAddressHistoryChecker](https://github.com/HBMY289/iotaAddressHistoryChecker)
4. check for typos in the seed (not implemented yet)
Seeds that are too short or too long will be adadpted in the same way the Iota Light Wallet did.
## How it works
##### Reclaim
With the given seed the programm calculates a large number of addresses both using the current address generation algorith and the one that was used in 2017 and earlier. These addresses are then matched against a list of reclaimable addresses. Possible matches and reclaimable balance will be shown. If no match is found using the Iota reclaim process will NOT bring back your balance.
##### Balance
If a reclaim case could be ruled out, the balance option will generate addresses using the current algorithm and compare them to an internally stored snapshot of the tangle. This snapshot holds all addresses with balances and by matching against this list the program does not need any connection to the internet or the current tangle to check balances. Currently a snapshot file from Feb 12th, 2021 is included. If you are missing a funds that have been moved after this date you can supply a more recent snapshot file. Ask someone who has access to a Iota node to run the following command and supply you with the resulting file.
```
curl -H 'X-IOTA-API-VERSION: 1' -d '{"command":"getLedgerState"}' localhost:14265 > snapshot.txt
```
Place the file `snapshot.txt` next to this tool's executable. It will be automatically be used when checking the balances.
##### Export Addresses to check online
This program requires to enter your seed and is designed to run without any internet connection. If all your addresses still do not show any balance you can check the addresses on the Iota tangle explorer [explorer.iota.org](https://explorer.iota.org) for any transactions that show where your funds went. To avoid having to enter all addresses manually I wrote another tool that automates this process ([iotaAddressHistoryChecker](https://github.com/HBMY289/iotaAddressHistoryChecker)). It will require a list of addresses exported by the iotaZeroBalanceHelper and then request all available tranascations from the explorer. It will report any token movements in a short and human readable report.
## Disclaimer
NEVER share your seed with anyone. No community member or member of the Iota Foundation will ever ask for your seed. If someone does it is 100% a scam to steal your money. That said, even entering your seed into a software other than the official Iota wallet should not be handled lightly and can only be recommended as a last resort. For your own safety you should run this software only an an air-gapped computer.
## How to start the tool
The simplest way is to download the appropriate binary executable for your operating system from [releases](https://github.com/HBMY289/iotaZeroBalanceHelper/releases). You can also build the tool from source, which is rather easy as well. Assuming you have [go](https://golang.org/doc/install) and [git](https://www.atlassian.com/git/tutorials/install-git) installed already you can just execute this command for example in your user folder to get a copy of the source code.
```
git clone https://github.com/HBMY289/iotaZeroBalanceHelper.git
```
Then you change into the new folder and build the excutable.
```
cd iotaZeroBalanceHelper
go build
```
After that you can just start the newly created binary file by typing
```
./iotaZeroBalanceHelper
```
or on Windows
```
iotaZeroBalanceHelper.exe
```
## How to use the tool
Once the program is running you will have to enter the seed and choose from the available options.
##### Number of addresses
The program will ask yoiu how many addresses of your seed you want to check. In most cases 100 addresses will suffice, only if you heavily used your seed for sending back and forth and genereated a lot of addresses a higher number might be necessary.
## Need additonal help?
If you need any additonal help either with the tool itself or with checking the exported addresses you can contact me (HBMY289) or any other community member in the #help channel via the official via the official [Iota Discord server](https://discord.iota.org/).
| 82.483871 | 698 | 0.791553 | eng_Latn | 0.999652 |
ff94d70d84a6d1d5daaf72b8840d84c88e34a45b | 1,904 | md | Markdown | treebanks/sa_ufal/sa-dep-nummod-gov.md | mjabrams/docs | eef96df1ce8f6752e9f80660c8255482b2a07c45 | [
"Apache-2.0"
] | 204 | 2015-01-20T16:36:39.000Z | 2022-03-28T00:49:51.000Z | treebanks/sa_ufal/sa-dep-nummod-gov.md | mjabrams/docs | eef96df1ce8f6752e9f80660c8255482b2a07c45 | [
"Apache-2.0"
] | 654 | 2015-01-02T17:06:29.000Z | 2022-03-31T18:23:34.000Z | treebanks/sa_ufal/sa-dep-nummod-gov.md | mjabrams/docs | eef96df1ce8f6752e9f80660c8255482b2a07c45 | [
"Apache-2.0"
] | 200 | 2015-01-16T22:07:02.000Z | 2022-03-25T11:35:28.000Z | ---
layout: base
title: 'Statistics of nummod:gov in UD_Sanskrit'
udver: '2'
---
## Treebank Statistics: UD_Sanskrit: Relations: `nummod:gov`
This relation is a language-specific subtype of <tt><a href="sa-dep-nummod.html">nummod</a></tt>.
2 nodes (0%) are attached to their parents as `nummod:gov`.
1 instances of `nummod:gov` (50%) are left-to-right (parent precedes child).
Average distance between parent and child is 1.
The following 1 pairs of parts of speech are connected with `nummod:gov`: <tt><a href="sa-pos-NOUN.html">NOUN</a></tt>-<tt><a href="sa-pos-NUM.html">NUM</a></tt> (2; 100% instances).
~~~ conllu
# visual-style 8 bgColor:blue
# visual-style 8 fgColor:white
# visual-style 7 bgColor:blue
# visual-style 7 fgColor:white
# visual-style 7 8 nummod:gov color:blue
1 अत्र अत्र ADV _ PronType=Dem 9 advmod _ Translit=atra|LTranslit=atra|Gloss=here
2 च च CCONJ _ _ 9 cc _ Translit=ca|LTranslit=ca|Gloss=and
3 मत् अस्मद् PRON _ Case=Abl|Number=Sing|Person=1|PronType=Prs 4 nmod _ Translit=mat|LTranslit=asmad|Gloss=from-me
4 दत्तां दत्त NOUN _ Case=Acc|Gender=Fem|Number=Sing 6 obj _ Translit=dattāṁ|LTranslit=datta|Gloss=favor
5 वृत्तिं वृत्ति NOUN _ Case=Acc|Gender=Fem|Number=Sing 4 conj _ Translit=vr̥ttiṁ|LTranslit=vr̥tti|Gloss=movement
6 भुञ्जानानां भुञ्जान ADJ _ Case=Gen|Gender=Masc|Number=Plur|Tense=Pres|VerbForm=Part 7 amod _ Translit=bhuñjānānāṁ|LTranslit=bhuñjāna|Gloss=eating
7 पण्डितानां पण्डित NOUN _ Case=Gen|Gender=Masc|Number=Plur 9 nsubj _ Translit=paṇḍitānāṁ|LTranslit=paṇḍita|Gloss=sages
8 पञ्चशती पञ्चशती NUM _ Case=Nom|Gender=Fem|Number=Sing|NumType=Card 7 nummod:gov _ Translit=pañcaśatī|LTranslit=pañcaśatī|Gloss=five-hundred
9 तिष्ठति स्था VERB _ Mood=Ind|Number=Sing|Person=3|Tense=Pres|VerbForm=Fin|Voice=Act 0 root _ SpaceAfter=No|Translit=tiṣṭhati|LTranslit=sthā|Gloss=stands
10 । । PUNCT _ _ 9 punct _ Translit=.|LTranslit=.|Gloss=.
~~~
| 48.820513 | 182 | 0.740021 | yue_Hant | 0.472249 |
ff964e7deee1748f132f4a95bd09f976c8507dab | 6,614 | md | Markdown | articles/databox/data-box-how-to-set-data-tier.md | y32saji/azure-docs | cf971fe82e9ee70db9209bb196ddf36614d39d10 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/databox/data-box-how-to-set-data-tier.md | y32saji/azure-docs | cf971fe82e9ee70db9209bb196ddf36614d39d10 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/databox/data-box-how-to-set-data-tier.md | y32saji/azure-docs | cf971fe82e9ee70db9209bb196ddf36614d39d10 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Use Azure Data Box to send data to - hot, cold, archive - block blob tier | Microsoft Docs in data
description: Describes how to use Azure Data Box to send data to an appropriate block blob storage tier such as hot, cold, or archive
services: databox
author: alkohli
ms.service: databox
ms.subservice: pod
ms.topic: article
ms.date: 01/10/2019
ms.author: alkohli
---
# Use Azure Data Box to send data to appropriate Azure Storage blob tier
Azure Data Box moves large amounts of data to Azure by shipping you a proprietary storage device. You fill up the device with data and return it. The data from Data Box is uploaded to a default tier associated with the storage account. You can then move the data to another storage tier.
This article describes how the data that is uploaded by Data Box can be moved to a Hot, Cold, or Archive blob tier.
## Choose the correct storage tier for your data
Azure storage allows three different tiers to store data in the most cost-effective manner - Hot, Cold, or Archive. Hot storage tier is optimized for storing data that is accessed frequently. Hot storage has higher storage costs than Cool and Archive storage, but the lowest access costs.
Cool storage tier is for infrequently accessed data that needs to be stored for a minimum of 30 days. The storage cost for cold tier is lower than that of hot storage tier but the data access charges are high when compared to Hot tier.
The Azure Archive tier is offline and offers the lowest storage costs but also the highest access costs. This tier is meant for data that remains in archival storage for a minimum of 180 days. For details of each of these tiers and the pricing model, go to [Comparison of the storage tiers](https://docs.microsoft.com/azure/storage/blobs/storage-blob-storage-tiers).
The data from the Data Box is uploaded to a storage tier that is associated with the storage account. When you create a storage account, you can specify the access tier as Hot or Cold. Depending upon the access pattern of your workload and cost, you can move this data from the default tier to another storage tier.
You may only tier your object storage data in Blob storage or General Purpose v2 (GPv2) accounts. General Purpose v1 (GPv1) accounts do not support tiering. To choose the correct storage tier for your data, review the considerations detailed in [Azure Blob storage: Premium, Hot, Cool, and Archive storage tiers](https://docs.microsoft.com/azure/storage/blobs/storage-blob-storage-tiers).
## Set a default blob tier
The default blob tier is specified when the storage account is created in the Azure portal. Once a storage type is selected as GPv2 or Blob storage, then the Access tier attribute can be specified. By default, the Hot tier is selected.
The tiers cannot be specified if you are trying to create a new account when ordering a Data Box. After the account is created, you can modify the account in portal to set the default access tier.
Alternatively, you create a storage account first with the specified access tier attribute. When creating the Data Box order, select the existing storage account. For more information on how to set the default blob tier during storage account creation, go to [Create a storage account in Azure portal](https://docs.microsoft.com/azure/storage/common/storage-quickstart-create-account?tabs=portal).
## Move data to a non-default tier
Once the data from Data Box is uploaded to the default tier, you may want to move the data to a non-default tier. There are two ways to move this data to a non-default tier.
- **Azure Blob storage lifecycle management** - You can use a policy-based approach to automatically tier data or expire at the end of its lifecycle. For more information, go to [Managing the Azure Blob storage lifecycle](https://docs.microsoft.com/azure/storage/common/storage-lifecycle-managment-concepts).
- **Scripting** - You could use a scripted approach via Azure PowerShell to enable blob-level tiering. You can call the `SetBlobTier` operation to set the tier on the blob.
## Use Azure PowerShell to set the blob tier
Following steps describe how you can set the blob tier to Archive using an Azure PowerShell script.
1. Open an elevated Windows PowerShell session. Make sure that your running PowerShell 5.0 or higher. Type:
`$PSVersionTable.PSVersion`
2. Sign into the Azure PowerShell.
`Login-AzureRmAccount`
3. Define the variables for storage account, access key, container, and the storage context.
```powershell
$StorageAccountName = "<enter account name>"
$StorageAccountKey = "<enter account key>"
$ContainerName = "<enter container name>"
$ctx = New-AzureStorageContext -StorageAccountName $StorageAccountName -StorageAccountKey $StorageAccountKey
```
4. Get all the blobs in the container.
`$blobs = Get-AzureStorageBlob -Container "<enter container name>" -Context $ctx`
5. Set the tier of all the blobs in the container to Archive.
```powershell
Foreach ($blob in $blobs) {
$blob.ICloudBlob.SetStandardBlobTier("Archive")
}
```
A sample output is shown below:
```
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
PS C:\WINDOWS\system32> $PSVersionTable.PSVersion
Major Minor Build Revision
----- ----- ----- --------
5 1 17763 134
PS C:\WINDOWS\system32> Login-AzureRmAccount
Account : [email protected]
SubscriptionName : MySubscription
SubscriptionId : subscription-id
TenantId : tenant-id
Environment : AzureCloud
PS C:\WINDOWS\system32> $StorageAccountName = "mygpv2storacct"
PS C:\WINDOWS\system32> $StorageAccountKey = "mystorageacctkey"
PS C:\WINDOWS\system32> $ContainerName = "test"
PS C:\WINDOWS\system32> $ctx = New-AzureStorageContext -StorageAccountName $StorageAccountName -StorageAccountKey $StorageAccountKey
PS C:\WINDOWS\system32> $blobs = Get-AzureStorageBlob -Container "test" -Context $ctx
PS C:\WINDOWS\system32> Foreach ($blob in $blobs) {
>> $blob.ICloudBlob.SetStandardBlobTier("Archive")
>> }
PS C:\WINDOWS\system32>
```
> [!TIP]
> If you want the data to archive on ingest, set the default account tier to Hot. If the default tier is Cool, then there is a 30-day early deletion penalty if the data moves to Archive immediately.
## Next steps
- Learn how to address the [common data tiering scenarios with lifecycle policy rules](https://docs.microsoft.com/azure/storage/blobs/storage-lifecycle-management-concepts#examples)
| 57.513043 | 397 | 0.757031 | eng_Latn | 0.978443 |
ff96ab4634c375c58d12c07c259f84e5a88588bf | 13,004 | md | Markdown | README.md | markrickert/react-native-background-geolocation | eebc529fa7790bbcca2266a5c107a3b83014a9ee | [
"MIT"
] | null | null | null | README.md | markrickert/react-native-background-geolocation | eebc529fa7790bbcca2266a5c107a3b83014a9ee | [
"MIT"
] | null | null | null | README.md | markrickert/react-native-background-geolocation | eebc529fa7790bbcca2266a5c107a3b83014a9ee | [
"MIT"
] | null | null | null | Background Geolocation for React Native · []() []()
============================================================================
[](https://www.transistorsoft.com)
-------------------------------------------------------------------------------
The *most* sophisticated background **location-tracking & geofencing** module with battery-conscious motion-detection intelligence for **iOS** and **Android**.
The plugin's [Philosophy of Operation](../../wiki/Philosophy-of-Operation) is to use **motion-detection** APIs (using accelerometer, gyroscope and magnetometer) to detect when the device is *moving* and *stationary*.
- When the device is detected to be **moving**, the plugin will *automatically* start recording a location according to the configured `distanceFilter` (meters).
- When the device is detected be **stationary**, the plugin will automatically turn off location-services to conserve energy.
Also available for [Cordova](https://github.com/transistorsoft/cordova-background-geolocation-lt), [NativeScript](https://github.com/transistorsoft/nativescript-background-geolocation-lt) and pure native apps.
----------------------------------------------------------------------------
The **[Android module](http://www.transistorsoft.com/shop/products/react-native-background-geolocation)** requires [purchasing a license](http://www.transistorsoft.com/shop/products/react-native-background-geolocation). However, it *will* work for **DEBUG** builds. It will **not** work with **RELEASE** builds [without purchasing a license](http://www.transistorsoft.com/shop/products/react-native-background-geolocation).
(2018) This plugin is supported **full-time** and field-tested **daily** since 2013.
----------------------------------------------------------------------------
[](https://play.google.com/store/apps/details?id=com.transistorsoft.backgroundgeolocation.react)
# Contents
- ### :books: [API Documentation](https://transistorsoft.github.io/react-native-background-geolocation)
- ### [Installing the Plugin](#large_blue_diamond-installing-the-plugin)
- ### [Setup Guides](#large_blue_diamond-setup-guides)
- ### [Configure your License](#large_blue_diamond-configure-your-license)
- ### [Using the plugin](#large_blue_diamond-using-the-plugin)
- ### [Example](#large_blue_diamond-example)
- ### [Debugging](../../wiki/Debugging)
- ### [Demo Application](#large_blue_diamond-demo-application)
- ### [Testing Server](#large_blue_diamond-simple-testing-server)
## :large_blue_diamond: Installing the Plugin
```
$ npm install react-native-background-geolocation --save
```
## :large_blue_diamond: Setup Guides
### iOS
- [`react-native link` Setup](help/INSTALL-IOS-RNPM.md)
- [Cocoapods](help/INSTALL-IOS-COCOAPODS.md)
- [Manual Setup](help/INSTALL-IOS.md)
### Android
* [`react-native link` Setup](help/INSTALL-ANDROID-RNPM.md)
* [Manual Setup](help/INSTALL-ANDROID.md)
#### :information_source: Solving Android Gradle Conflicts.
Once of the most common build-issues with Android apps are gradle conflicts between modules specifying different versions of:
- `compileSdkVersion`
- `buildToolsVersion`
- Google `play-services` / `firebase` version.
- Google support libraries (ie `appcompat-v4`, `appcompat-v7`)
For more information, see the Wiki [Solving Android Gradle Conflicts](../../wiki/Solving-Android-Gradle-Conflicts)
## :large_blue_diamond: Configure your license
1. Login to Customer Dashboard to generate an application key:
[www.transistorsoft.com/shop/customers](http://www.transistorsoft.com/shop/customers)
2. Add your license-key to `android/app/src/main/AndroidManifest.xml`:
```diff
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.transistorsoft.backgroundgeolocation.react">
<application
android:name=".MainApplication"
android:allowBackup="true"
android:label="@string/app_name"
android:icon="@mipmap/ic_launcher"
android:theme="@style/AppTheme">
<!-- react-native-background-geolocation licence -->
+ <meta-data android:name="com.transistorsoft.locationmanager.license" android:value="YOUR_LICENCE_KEY_HERE" />
.
.
.
</application>
</manifest>
```
## :large_blue_diamond: Using the plugin ##
```javascript
import BackgroundGeolocation from "react-native-background-geolocation";
```
### [Typescript](https://facebook.github.io/react-native/blog/2018/05/07/using-typescript-with-react-native) API:
For those using [Typescript](https://facebook.github.io/react-native/blog/2018/05/07/using-typescript-with-react-native) (__recommended__), you can also `import` the interfaces:
```javascript
import BackgroundGeolocation, {
State,
Config,
Location,
LocationError,
Geofence,
GeofenceEvent,
GeofencesChangeEvent,
HeartbeatEvent,
HttpEvent,
MotionActivityEvent,
MotionChangeEvent,
ProviderChangeEvent,
ConnectivityChangeEvent
} from "react-native-background-geolocation-android";
```
For more information, see [this blog post](https://medium.com/@transistorsoft/new-feature-typescript-api-4a160a2c853b)
## :large_blue_diamond: Example
There are three main steps to using `BackgroundGeolocation`
1. Wire up event-listeners.
2. `#ready` the plugin.
3. `#start` the plugin.
```javascript
// Import BackgroundGeolocation + any optional interfaces
import BackgroundGeolocation from "react-native-background-geolocation";
export default class App extends Component {
componentWillMount() {
////
// 1. Wire up event-listeners
//
// This handler fires whenever bgGeo receives a location update.
BackgroundGeolocation.onLocation(this.onLocation, this.onError);
// This handler fires when movement states changes (stationary->moving; moving->stationary)
BackgroundGeolocation.onMotionChange(this.onMotionChange);
// This event fires when a change in motion activity is detected
BackgroundGeolocation.oActivityChange(this.onActivityChange);
// This event fires when the user toggles location-services authorization
BackgroundGeolocation.onProviderChange(this.onProviderChange);
////
// 2. Execute #ready method (required)
//
BackgroundGeolocation.ready({
// Geolocation Config
desiredAccuracy: BackgroundGeolocation.DESIRED_ACCURACY_HIGH,
distanceFilter: 10,
// Activity Recognition
stopTimeout: 1,
// Application config
debug: true, // <-- enable this hear sounds for background-geolocation life-cycle.
logLevel: BackgroundGeolocation.LOG_LEVEL_VERBOSE,
stopOnTerminate: false, // <-- Allow the background-service to continue tracking when user closes the app.
startOnBoot: true, // <-- Auto start tracking when device is powered-up.
// HTTP / SQLite config
url: 'http://yourserver.com/locations',
batchSync: false, // <-- [Default: false] Set true to sync locations to server in a single HTTP request.
autoSync: true, // <-- [Default: true] Set true to sync each location to server as it arrives.
headers: { // <-- Optional HTTP headers
"X-FOO": "bar"
},
params: { // <-- Optional HTTP params
"auth_token": "maybe_your_server_authenticates_via_token_YES?"
}
}, (state) => {
console.log("- BackgroundGeolocation is configured and ready: ", state.enabled);
if (!state.enabled) {
////
// 3. Start tracking!
//
BackgroundGeolocation.start(function() {
console.log("- Start success");
});
}
});
}
// You must remove listeners when your component unmounts
componentWillUnmount() {
BackgroundGeolocation.removeListeners();
}
onLocation(location) {
console.log('[location] -', location);
}
onError(error) {
console.warn('[location] ERROR -', error);
}
onActivityChange(event) {
console.log('[activitychange] -', event); // eg: 'on_foot', 'still', 'in_vehicle'
}
onProviderChange(provider) {
console.log('[providerchange] -', provider.enabled, provider.status);
}
onMotionChange(event) {
console.log('[motionchange] -', event.isMoving, event.location);
}
}
```
:information_source: **NOTE:** The configuration **`{}`** provided to the `#ready` method is applied **only** when your app is **first booted** — for every launch thereafter, the plugin will automatically load the last known configuration from persistant storage. If you wish to **force** the `#ready` method to *always* apply the supplied config `{}`, you can specify **`reset: true`**
```javascript
BackgroundGeolocation.ready({
reset: true, // <-- true to always apply the supplied config
distanceFilter: 10
}, (state) => {
console.log('- BackgroundGeolocation is ready: ', state);
});
```
:warning: Do not execute *any* API method which will require accessing location-services until the callback to **`#ready*` executes (eg: `#getCurrentPosition`, `#watchPosition`, `#start`).
### Promise API
The `BackgroundGeolocation` Javascript API supports [Promises](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) for *nearly* every method (the exceptions are **`#watchPosition`** and adding event-listeners via **`#on`** method. For more information, see the [API Documentation](https://transistorsoft.github.io/react-native-background-geolocation)
```javascript
// Traditional API still works:
BackgroundGeolocation.ready({
desiredAccuracy: BackgroundGeolocation.DESIRED_ACCURACY_HIGH,
distanceFilter: 50
}).then(state => {
console.log('- BackgroundGeolocation is ready: ', state);
}).catch(error => {
console.log('- BackgroundGeolocation error: ', error);
});
```
## :large_blue_diamond: [Demo Application](https://github.com/transistorsoft/rn-background-geolocation-demo)
A fully-featured [Demo App](https://github.com/transistorsoft/rn-background-geolocation-demo) is available in its own public repo. After first cloning that repo, follow the installation instructions in the **README** there. This demo-app includes a settings-screen allowing you to quickly experiment with all the different settings available for each platform.
## :large_blue_diamond: [Simple Testing Server](https://github.com/transistorsoft/background-geolocation-console)
A simple Node-based [web-application](https://github.com/transistorsoft/background-geolocation-console) with SQLite database is available for field-testing and performance analysis. If you're familiar with Node, you can have this server up-and-running in about **one minute**.
# License
The MIT License (MIT)
Copyright (c) 2018 Chris Scott, Transistor Software
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.
| 45.152778 | 426 | 0.707167 | eng_Latn | 0.639358 |
ff970949213f4e1883a2e0a13d5fc3226ba5d432 | 46 | md | Markdown | README.md | andri-sudarmawijaya/codeigniter-3-starter | 36788b94c3dfa32b11ae8afef67bc84ef3b1a874 | [
"MIT"
] | null | null | null | README.md | andri-sudarmawijaya/codeigniter-3-starter | 36788b94c3dfa32b11ae8afef67bc84ef3b1a874 | [
"MIT"
] | null | null | null | README.md | andri-sudarmawijaya/codeigniter-3-starter | 36788b94c3dfa32b11ae8afef67bc84ef3b1a874 | [
"MIT"
] | null | null | null | # codeigniter-3-starter
CodeIgniter 3 Starter
| 15.333333 | 23 | 0.826087 | deu_Latn | 0.534185 |
ff9754bcabcc13e13b4f706389c5d82edb1ad97c | 4,512 | md | Markdown | _posts/WebRTC/2021-03-27-webrtc-signaling.md | EasyCoding-7/easycoding-7.github.io | 9be32363f161ef6096b2c38d99eaaf57b470fc16 | [
"MIT"
] | null | null | null | _posts/WebRTC/2021-03-27-webrtc-signaling.md | EasyCoding-7/easycoding-7.github.io | 9be32363f161ef6096b2c38d99eaaf57b470fc16 | [
"MIT"
] | null | null | null | _posts/WebRTC/2021-03-27-webrtc-signaling.md | EasyCoding-7/easycoding-7.github.io | 9be32363f161ef6096b2c38d99eaaf57b470fc16 | [
"MIT"
] | null | null | null | ---
layout: post
title: "(WebRTC) Signaling"
summary: ""
author: WebRTC
date: '2021-03-27 0:00:00 +0000'
category: ['OpenSource']
#tags: ['C++', 'tag-test1']
thumbnail: /assets/img/posts/webrtc-thumnail.webp
#keywords: ['weak_ptr']
usemathjax: true
permalink: /blog/WebRTC/signaling/
---
* [참고사이트 : WebRTC에 대한 전반 설명](https://www.html5rocks.com/ko/tutorials/webrtc/infrastructure/)
* [참고사이트2 : ICE 설명](https://brunch.co.kr/@linecard/156)
* [참고3 : 아직 자세히는 안읽어봄 내용 좋은듯](https://rosypark.tistory.com/m/291?category=726178)
---
## WebRTC Signaling이 어떻게 이루어지는지 Example을 통해서 살펴본다.
1. RTCPeerConnection 객체를 생성
2. createOffer() 메소드를 사용하여 SDP(Session Description Protocol)을 생성
3. SDP와 함께 setLocalDescription()를 호출
4. SDP를 문자열화하고 상대 Peer에게 보냄
5. 수신측에서는 setRemoteDescription()를 통해 상대 Peer의 SDP를 인지
6. 수신측에서는 createAnswer()를 통해 자신의 SDP정보를 전달
7. 상대의 SDP를 받으면 SetRemoteDescription을 통하여 인지
이렇게 말로 적으니 무슨소린지 영 ... Example을 통해 설명해 보자면 ...
### 1. RTCPeerConnection 객체를 생성
뭐.. 간단해서 따로 설명할 부분은 없다.<br>
peerconnection을 만든다
```cpp
bool Conductor::CreatePeerConnection(bool dtls) {
ASSERT(peer_connection_factory_.get() != NULL);
ASSERT(peer_connection_.get() == NULL);
webrtc::PeerConnectionInterface::IceServers servers;
webrtc::PeerConnectionInterface::IceServer server;
server.uri = GetPeerConnectionString();
servers.push_back(server);
webrtc::FakeConstraints constraints;
if (dtls) {
constraints.AddOptional(webrtc::MediaConstraintsInterface::kEnableDtlsSrtp,
"true");
}
else
{
constraints.AddOptional(webrtc::MediaConstraintsInterface::kEnableDtlsSrtp,
"false");
}
peer_connection_ =
peer_connection_factory_->CreatePeerConnection(servers,
&constraints,
NULL,
NULL,
this);
return peer_connection_.get() != NULL;
}
```
### 2. createOffer() 메소드를 사용하여 SDP(Session Description Protocol)을 생성
```cpp
void Conductor::ConnectToPeer(int peer_id) {
ASSERT(peer_id_ == -1);
ASSERT(peer_id != -1);
if (peer_connection_.get()) {
main_wnd_->MessageBox("Error",
"We only support connecting to one peer at a time", true);
return;
}
if (InitializePeerConnection()) { // 여기서 CreatePeerConnection과 Stream을 생성
peer_id_ = peer_id;
peer_connection_->CreateOffer(this, NULL); // CreateOffer
} else {
main_wnd_->MessageBox("Error", "Failed to initialize PeerConnection", true);
}
}
```
### 3. SDP와 함께 setLocalDescription()를 호출
### 4. SDP를 문자열화하고 상대 Peer에게 보냄
```cpp
void Conductor::OnSuccess(webrtc::SessionDescriptionInterface* desc) {
peer_connection_->SetLocalDescription(
DummySetSessionDescriptionObserver::Create(), desc);
// ...
Json::StyledWriter writer;
Json::Value jmessage;
jmessage[kSessionDescriptionTypeName] = desc->type();
jmessage[kSessionDescriptionSdpName] = sdp;
SendMessage(writer.write(jmessage)); // sdp를 상대 peer에게 보내게된다.
}
```
참고로 OnSuccess는 CreateOffer에 의해 호출된다.
```cpp
// CreateSessionDescriptionObserver implementation.
virtual void OnSuccess(webrtc::SessionDescriptionInterface* desc);
```
### 5. 수신측에서는 setRemoteDescription()를 통해 상대 Peer의 SDP를 인지
### 6. 수신측에서는 createAnswer()를 통해 자신의 SDP정보를 전달
```cpp
void Conductor::OnMessageFromPeer(int peer_id, const std::string& message) {
ASSERT(peer_id_ == peer_id || peer_id_ == -1);
ASSERT(!message.empty());
// ...
std::string sdp;
if (!rtc::GetStringFromJsonObject(jmessage, kSessionDescriptionSdpName,
&sdp)) {
LOG(WARNING) << "Can't parse received session description message.";
return;
}
webrtc::SdpParseError error;
webrtc::SessionDescriptionInterface* session_description(
webrtc::CreateSessionDescription(type, sdp, &error));
if (!session_description) {
LOG(WARNING) << "Can't parse received session description message. "
<< "SdpParseError was: " << error.description;
return;
}
LOG(INFO) << " Received session description :" << message;
peer_connection_->SetRemoteDescription(
DummySetSessionDescriptionObserver::Create(), session_description);
if (session_description->type() ==
webrtc::SessionDescriptionInterface::kOffer) {
peer_connection_->CreateAnswer(this, NULL);
}
return;
} else {
// ...
```
| 29.684211 | 92 | 0.660683 | kor_Hang | 0.889739 |
ff97ac1b90b6f13b29ff80e130baae8f552a9caf | 31,909 | md | Markdown | security-updates/SecurityBulletinSummaries/2010/ms10-jan.md | eltociear/security-updates.zh-cn | 6c1033486a2c8c29eb32080eb19d5c1134b77aa3 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2019-02-18T03:53:36.000Z | 2020-05-19T20:17:14.000Z | security-updates/SecurityBulletinSummaries/2010/ms10-jan.md | eltociear/security-updates.zh-cn | 6c1033486a2c8c29eb32080eb19d5c1134b77aa3 | [
"CC-BY-4.0",
"MIT"
] | 282 | 2017-12-08T07:58:45.000Z | 2020-07-31T21:57:39.000Z | security-updates/SecurityBulletinSummaries/2010/ms10-jan.md | eltociear/security-updates.zh-cn | 6c1033486a2c8c29eb32080eb19d5c1134b77aa3 | [
"CC-BY-4.0",
"MIT"
] | 9 | 2018-07-19T12:17:39.000Z | 2021-12-28T14:03:37.000Z | ---
TOCTitle: 'MS10-JAN'
Title: 'Microsoft 安全公告摘要 (2010 年 1 月)'
ms:assetid: 'ms10-jan'
ms:contentKeyID: 61236943
ms:mtpsurl: 'https://technet.microsoft.com/zh-CN/library/ms10-jan(v=Security.10)'
---
Security Bulletin Summary
Microsoft 安全公告摘要 (2010 年 1 月)
=====================================
发布时间: 2010年1月12日 | 更新时间: 2010年1月21日
**版本:** 2.0
本公告摘要列出了 2010 年 1 月发布的安全公告。
对于 2010 年 1 月发布的安全公告，本公告摘要替代 2010 年 1 月 20 日最初发布的公告预先通知。有关公告预先通知服务的详细信息，请参阅 [Microsoft 安全公告预先通知](https://technet.microsoft.com/security/bulletin/advance)。
有关在 Microsoft 安全公告发布时如何收到自动通知的信息，请访问 [Microsoft 技术安全通知](https://go.microsoft.com/fwlink/?linkid=21163)。
Microsoft 将在 2010 年 1 月 13 日上午 11 点（美国和加拿大太平洋时间）进行网络广播，以解答客户关于这些公告的疑问。 [立即注册申请收听 1 月份安全公告网络广播](https://msevents.microsoft.com/cui/webcasteventdetails.aspx?eventid=1032427677&eventcategory=4&culture=en-us&countrycode=us)。 此日期之后，此网络广播按需提供。 有关详细信息，请参阅 [Microsoft 安全公告摘要和网络广播](https://technet.microsoft.com/security/bulletin/summary)。
对于添加到此公告摘要 (MS10-002) 的版本 2.0 的额外安全公告，Microsoft 在美国和加拿大太平洋时间 2010 年 1 月 21 日下午 1:00 进行网络广播，以解决客户关于这些公告的疑问： [立即注册申请收听 1 月 21 日下午 1:00 的网络广播](https://msevents.microsoft.com/cui/eventdetail.aspx?eventid=1032440627&culture=en-us)。 此日期之后，此网络广播按需提供。 有关详细信息，请参阅 [Microsoft 安全公告摘要和网络广播](https://technet.microsoft.com/security/bulletin/summary)。
Microsoft 还会提供相关信息，帮助客户对每月安全更新和与每月安全更新同日发布的任何高优先级非安全更新进行优先排序。 请参阅**其他信息**部分。
### 公告信息
摘要
----
下表概述了本月的安全公告（按严重性排序）。
有关受影响软件的详细信息，请参阅下一节“**受影响的软件及其下载位置**”。
<p> </p>
<table style="border:1px solid black;">
<thead>
<tr class="header">
<th>公告 ID</th>
<th>公告标题和摘要</th>
<th>最高严重等级和漏洞影响</th>
<th>重新启动要求</th>
<th>受影响的软件</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td style="border:1px solid black;"><a href="https://technet.microsoft.com/security/bulletin/ms10-001">MS10-001</a></td>
<td style="border:1px solid black;"><strong>Embedded OpenType 字体引擎中的漏洞可能允许远程执行代码 (972270)</strong><br />
<br />
此安全更新解决了 Microsoft Windows 中一个秘密报告的漏洞。 如果用户在可以呈现 EOT 字体的客户端应用程序（如 Microsoft Internet Explorer、Microsoft Office PowerPoint 或 Microsoft Office Word）中查看以特制的 Embedded OpenType (EOT) 字体呈现的内容，则该漏洞可能允许远程执行代码。 成功利用此漏洞的攻击者可以完全控制受影响的系统。 攻击者可随后安装程序；查看、更改或删除数据；或者创建拥有完全用户权限的新帐户。 那些帐户被配置为拥有较少系统用户权限的用户比具有管理用户权限的用户受到的影响要小。</td>
<td style="border:1px solid black;"><a href="https://go.microsoft.com/fwlink/?linkid=21140">严重</a><br />
远程执行代码</td>
<td style="border:1px solid black;">可能要求重新启动</td>
<td style="border:1px solid black;">Microsoft Windows</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><a href="https://technet.microsoft.com/security/bulletin/ms10-002">MS10-002</a></td>
<td style="border:1px solid black;"><strong>Internet Explorer 的累积性安全更新 (978207)</strong><br />
<br />
此安全更新可解决 Internet Explorer 中七个秘密报告的漏洞和一个公开披露的漏洞。 最严重的漏洞可能在用户使用 Internet Explorer 查看特制网页时允许远程执行代码。 那些帐户被配置为拥有较少系统用户权限的用户比具有管理用户权限的用户受到的影响要小。</td>
<td style="border:1px solid black;"><a href="https://go.microsoft.com/fwlink/?linkid=21140">严重</a><br />
远程执行代码</td>
<td style="border:1px solid black;">需要重启动</td>
<td style="border:1px solid black;">Microsoft Windows</td>
</tr>
</tbody>
</table>
利用指数
--------
<span></span>
下表提供了本月解决的各个漏洞的利用评估。 这些漏洞按公告 ID 和 CVE ID 的排序列出。
**我如何使用该表呢？**
使用该表了解安全公告发布 30 天内为您可能需要安装的每个安全更新发布有效漏洞检测代码的可能性。 您应该根据您的特定配置，检查下面的每个评估，从而确定部署的优先次序。 有关这些等级的含义以及如何确定这些等级的详细信息，请参阅 [Microsoft 利用指数](https://technet.microsoft.com/en-us/security/cc998259.aspx)。
| 公告 ID | 漏洞标题 | CVE ID | 利用指数评估 | 重要注意事项 |
|---------------------------------------------------------------------|------------------------------------------------------------|----------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|
| [MS10-001](https://technet.microsoft.com/security/bulletin/ms10-001) | LZCOMP 解压缩器中的 Microtype Express 压缩字体整数缺陷漏洞 | [CVE-2010-0018](https://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2010-0018) | [**2**](https://technet.microsoft.com/en-us/security/cc998259.aspx) - 不一致漏洞检测代码可能实现 | 此利用指数评估适用于运行 Microsoft Windows 2000 的系统。运行 Windows XP 和更高版本的操作系统的操作系统不太可能被利用。 |
| [MS10-002](https://technet.microsoft.com/security/bulletin/ms10-002) | XSS 筛选器脚本处理漏洞 | [CVE-2009-4047](https://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2009-4047) | 无 | 不可能利用此漏洞执行代码。 |
| [MS10-002](https://technet.microsoft.com/security/bulletin/ms10-002) | URL 验证漏洞 | [CVE-2010-0027](https://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2010-0027) | [**1**](https://technet.microsoft.com/en-us/security/cc998259.aspx) - 一致漏洞检测代码可能实现 | （无） |
| [MS10-002](https://technet.microsoft.com/security/bulletin/ms10-002) | 未初始化的内存损坏漏洞 | [CVE-2010-0244](https://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2010-0244) | [**1**](https://technet.microsoft.com/en-us/security/cc998259.aspx) - 一致漏洞检测代码可能实现 | （无） |
| [MS10-002](https://technet.microsoft.com/security/bulletin/ms10-002) | 未初始化的内存损坏漏洞 | [CVE-2010-0245](https://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2010-0245) | 无 | 应用了 [MS09-072](https://go.microsoft.com/fwlink/?linkid=169404) 的客户受到保护，因为 MS09-072 更新中的更改阻止此漏洞。 |
| [MS10-002](https://technet.microsoft.com/security/bulletin/ms10-002) | 未初始化的内存损坏漏洞 | [CVE-2010-0246](https://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2010-0246) | 无 | 应用了 [MS09-072](https://go.microsoft.com/fwlink/?linkid=169404) 的客户受到保护，因为 MS09-072 更新中的更改阻止此漏洞。 |
| [MS10-002](https://technet.microsoft.com/security/bulletin/ms10-002) | 未初始化的内存损坏漏洞 | [CVE-2010-0247](https://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2010-0247) | [**1**](https://technet.microsoft.com/en-us/security/cc998259.aspx) - 一致漏洞检测代码可能实现 | （无） |
| [MS10-002](https://technet.microsoft.com/security/bulletin/ms10-002) | 未初始化的内存损坏漏洞 | [CVE-2010-0248](https://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2010-0248) | [**2**](https://technet.microsoft.com/en-us/security/cc998259.aspx) - 不一致漏洞检测代码可能实现 | （无） |
| [MS10-002](https://technet.microsoft.com/security/bulletin/ms10-002) | 未初始化的内存损坏漏洞 | [CVE-2010-0249](https://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2010-0249) | [**1**](https://technet.microsoft.com/en-us/security/cc998259.aspx) - 一致漏洞检测代码可能实现 | **此漏洞当前正在 Internet 生态系统中被利用。** |
受影响的软件和下载位置
----------------------
<span></span>
下表按主要软件类别和严重性的排序列出了公告。
**如何使用这些表？**
通过这些表可了解可能需要安装的安全更新。 您应该查看列出的每个软件程序或组件，了解是否需要安装任何安全更新。 如果某个软件程序或者组件被列出，则可用的软件更新会被加上超链接，软件更新的严重等级也会被列出。
**注意** 您可能必须为单个漏洞安装几个安全更新。 查看列出的每个公告标识符的整列，核实必须安装的更新（基于系统上已安装的程序或组件）。
#### Windows 操作系统和组件
<p> </p>
<table style="border:1px solid black;">
<tr class="thead">
<th>
</th>
<th>
</th>
<th>
</th>
</tr>
<tr>
<th colspan="3" style="border:1px solid black;">
Microsoft Windows 2000
</th>
</tr>
<tr>
<td style="border:1px solid black;">
**公告标识符**
</td>
<td style="border:1px solid black;">
[**MS10-001**](https://technet.microsoft.com/security/bulletin/ms10-001)
</td>
<td style="border:1px solid black;">
[**MS10-002**](https://technet.microsoft.com/security/bulletin/ms10-002)
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
**综合严重等级**
</td>
<td style="border:1px solid black;">
[**严重**](https://go.microsoft.com/fwlink/?linkid=21140)
</td>
<td style="border:1px solid black;">
[**严重**](https://go.microsoft.com/fwlink/?linkid=21140)
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Microsoft Windows 2000 Service Pack 4
</td>
<td style="border:1px solid black;">
[Microsoft Windows 2000 Service Pack 4](https://www.microsoft.com/download/details.aspx?familyid=47f85cbd-282e-4c92-9809-68bba49e0a12)
（严重）
</td>
<td style="border:1px solid black;">
[安装在 Microsoft Windows 2000 Service Pack 4 上的 Internet Explorer 5.01 Service Pack 4](https://www.microsoft.com/download/details.aspx?familyid=51e99e4f-1670-4b12-a9fe-e0ccf50cdabc)
（严重）
[安装在 Microsoft Windows 2000 Service Pack 4 上的 Internet Explorer 6 Service Pack 1](https://www.microsoft.com/download/details.aspx?familyid=a38aa9d0-c3fe-4d41-8805-7d5370263c1b)
（严重）
</td>
</tr>
<tr>
<th colspan="3" style="border:1px solid black;">
Windows XP
</th>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
**公告标识符**
</td>
<td style="border:1px solid black;">
[**MS10-001**](https://technet.microsoft.com/security/bulletin/ms10-001)
</td>
<td style="border:1px solid black;">
[**MS10-002**](https://technet.microsoft.com/security/bulletin/ms10-002)
</td>
</tr>
<tr>
<td style="border:1px solid black;">
**综合严重等级**
</td>
<td style="border:1px solid black;">
[**低**](https://go.microsoft.com/fwlink/?linkid=21140)
</td>
<td style="border:1px solid black;">
[**严重**](https://go.microsoft.com/fwlink/?linkid=21140)
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
Windows XP Service Pack 2 和 Windows XP Service Pack 3
</td>
<td style="border:1px solid black;">
[Windows XP Service Pack 2 和 Windows XP Service Pack 3](https://www.microsoft.com/download/details.aspx?familyid=793a6b3f-7660-40be-b7d5-7b0eec55e1cd)
（低）
</td>
<td style="border:1px solid black;">
[用于 Windows XP Service Pack 2 和 Windows XP Service Pack 3 的 Internet Explorer 6](https://www.microsoft.com/download/details.aspx?familyid=207eecad-6e84-48e6-ae18-6794a3618ee0)
（严重）
[用于 Windows XP Service Pack 2 和 Windows XP Service Pack 3 的 Internet Explorer 7](https://www.microsoft.com/download/details.aspx?familyid=3510c7d8-7e8f-479e-b6f9-5745a845664d)
（严重）
[用于 Windows XP Service Pack 2 和 Windows XP Service Pack 3 的 Internet Explorer 8](https://www.microsoft.com/download/details.aspx?familyid=7c2948fb-f486-4801-bc21-bbf40d5a78c2)
（严重）
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows XP Professional x64 Edition Service Pack 2
</td>
<td style="border:1px solid black;">
[Windows XP Professional x64 Edition Service Pack 2](https://www.microsoft.com/download/details.aspx?familyid=31609ce9-656a-4f7d-a501-709a31ca34c3)
（低）
</td>
<td style="border:1px solid black;">
[用于 Windows XP Professional x64 Edition Service Pack 2 的 Internet Explorer 6](https://www.microsoft.com/download/details.aspx?familyid=eb2d8055-4d50-4f83-82b8-055c7b8f5422)
（严重）
[用于 Windows XP Professional x64 Edition Service Pack 2 的 Internet Explorer 7](https://www.microsoft.com/download/details.aspx?familyid=cc5aea0b-e553-4f7f-a2cc-cba41bb87ae7)
（严重）
[用于 Windows XP Professional x64 Edition Service Pack 2 的 Internet Explorer 8](https://www.microsoft.com/download/details.aspx?familyid=41b83fad-948b-4a9c-80ed-9c5a60bd35b4)
（严重）
</td>
</tr>
<tr>
<th colspan="3" style="border:1px solid black;">
Windows Server 2003
</th>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
**公告标识符**
</td>
<td style="border:1px solid black;">
[**MS10-001**](https://technet.microsoft.com/security/bulletin/ms10-001)
</td>
<td style="border:1px solid black;">
[**MS10-002**](https://technet.microsoft.com/security/bulletin/ms10-002)
</td>
</tr>
<tr>
<td style="border:1px solid black;">
**综合严重等级**
</td>
<td style="border:1px solid black;">
[**低**](https://go.microsoft.com/fwlink/?linkid=21140)
</td>
<td style="border:1px solid black;">
[**严重**](https://go.microsoft.com/fwlink/?linkid=21140)
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
Windows Server 2003 Service Pack 2
</td>
<td style="border:1px solid black;">
[Windows Server 2003 Service Pack 2](https://www.microsoft.com/download/details.aspx?familyid=e1d6e338-dea9-458e-b35d-796e069d74d7)
（低）
</td>
<td style="border:1px solid black;">
[用于 Windows Server 2003 Service Pack 2 的 Internet Explorer 6](https://www.microsoft.com/download/details.aspx?familyid=fea91227-44ad-4549-8732-497a8ceff870)
（中等）
[用于 Windows Server 2003 Service Pack 2 的 Internet Explorer 7](https://www.microsoft.com/download/details.aspx?familyid=14726445-3ff4-463c-9fc1-c9b758079aca)
（严重）
[用于 Windows Server 2003 Service Pack 2 的 Internet Explorer 8](https://www.microsoft.com/download/details.aspx?familyid=7d480c87-2ca9-4505-a59d-a6d73d001fa5)
（严重）
</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 Server 2003 x64 Edition Service Pack 2](https://www.microsoft.com/download/details.aspx?familyid=ddbcf231-9fde-4dc2-ad04-a01b69d1a980)
（低）
</td>
<td style="border:1px solid black;">
[用于 Windows Server 2003 x64 Edition Service Pack 2 的 Internet Explorer 6](https://www.microsoft.com/download/details.aspx?familyid=633e63f4-605b-43c4-8a4b-2730312a1c72)
（中等）
[用于 Windows Server 2003 x64 Edition Service Pack 2 的 Internet Explorer 7](https://www.microsoft.com/download/details.aspx?familyid=c8742230-16d8-4b2f-bd3e-8834c759856b)
（严重）
[用于 Windows Server 2003 x64 Edition Service Pack 2 的 Internet Explorer 8](https://www.microsoft.com/download/details.aspx?familyid=3e2e740b-8417-4758-8468-15221249ec71)
（严重）
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
Windows Server 2003 SP2（用于基于 Itanium 的系统）
</td>
<td style="border:1px solid black;">
[Windows Server 2003 SP2（用于基于 Itanium 的系统）](https://www.microsoft.com/download/details.aspx?familyid=c71a13cf-7e2f-4b02-8684-1a4e4b46ddda)
（低）
</td>
<td style="border:1px solid black;">
[用于 Windows Server 2003 SP2（用于基于 Itanium 的系统）的 Internet Explorer 6](https://www.microsoft.com/download/details.aspx?familyid=b9308d50-ca66-43ff-9dc5-d05c90baa764)
（中等）
[用于 Windows Server 2003 SP2（用于基于 Itanium 的系统）的 Internet Explorer 7](https://www.microsoft.com/download/details.aspx?familyid=5622f223-df9c-4a6a-bdf0-feebaf9920fd)
（严重）
</td>
</tr>
<tr>
<th colspan="3" style="border:1px solid black;">
Windows Vista
</th>
</tr>
<tr>
<td style="border:1px solid black;">
**公告标识符**
</td>
<td style="border:1px solid black;">
[**MS10-001**](https://technet.microsoft.com/security/bulletin/ms10-001)
</td>
<td style="border:1px solid black;">
[**MS10-002**](https://technet.microsoft.com/security/bulletin/ms10-002)
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
**综合严重等级**
</td>
<td style="border:1px solid black;">
[**低**](https://go.microsoft.com/fwlink/?linkid=21140)
</td>
<td style="border:1px solid black;">
[**严重**](https://go.microsoft.com/fwlink/?linkid=21140)
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Vista、Windows Vista Service Pack 1 和 Windows Vista Service Pack 2
</td>
<td style="border:1px solid black;">
[Windows Vista、Windows Vista Service Pack 1 和 Windows Vista Service Pack 2](https://www.microsoft.com/download/details.aspx?familyid=6387228c-eedc-4511-b3c6-8922606f4c84)
（低）
</td>
<td style="border:1px solid black;">
[Windows Vista、Windows Vista Service Pack 1 和 Windows Vista Service Pack 2 中的 Internet Explorer 7](https://www.microsoft.com/download/details.aspx?familyid=92495551-dedd-43d4-bb3a-51028bc5c6d6)
（严重）
[Windows Vista、Windows Vista Service Pack 1 和 Windows Vista Service Pack 2 中的 Internet Explorer 8](https://www.microsoft.com/download/details.aspx?familyid=5e2cbd7d-f64f-49e5-a159-1965ebfe2a92)
（严重）
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
Windows Vista x64 Edition、Windows Vista x64 Edition Service Pack 1 和 Windows Vista x64 Edition Service Pack 2
</td>
<td style="border:1px solid black;">
[Windows Vista x64 Edition、Windows Vista x64 Edition Service Pack 1 和 Windows Vista x64 Edition Service Pack 2](https://www.microsoft.com/download/details.aspx?familyid=7b4f5089-13b1-421b-a00b-22632bba4229)
（低）
</td>
<td style="border:1px solid black;">
[Windows Vista x64 Edition、Windows Vista x64 Edition Service Pack 1 和 Windows Vista x64 Edition Service Pack 2 中的 Internet Explorer 7](https://www.microsoft.com/download/details.aspx?familyid=3cb139b3-59f4-44ef-9911-4dd4e3b83e7d)
（严重）
[Windows Vista x64 Edition、Windows Vista x64 Edition Service Pack 1 和 Windows Vista x64 Edition Service Pack 2 中的 Internet Explorer 8](https://www.microsoft.com/download/details.aspx?familyid=b7a7e8e7-f4c5-459d-ab6c-05a192e1e3f9)
（严重）
</td>
</tr>
<tr>
<th colspan="3" style="border:1px solid black;">
Windows Server 2008
</th>
</tr>
<tr>
<td style="border:1px solid black;">
**公告标识符**
</td>
<td style="border:1px solid black;">
[**MS10-001**](https://technet.microsoft.com/security/bulletin/ms10-001)
</td>
<td style="border:1px solid black;">
[**MS10-002**](https://technet.microsoft.com/security/bulletin/ms10-002)
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
**综合严重等级**
</td>
<td style="border:1px solid black;">
[**低**](https://go.microsoft.com/fwlink/?linkid=21140)
</td>
<td style="border:1px solid black;">
[**严重**](https://go.microsoft.com/fwlink/?linkid=21140)
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2008（用于 32 位系统）和 Windows Server 2008（用于 32 位系统）Service Pack 2
</td>
<td style="border:1px solid black;">
[Windows Server 2008（用于 32 位系统）和 Windows Server 2008（用于 32 位系统）Service Pack 2](https://www.microsoft.com/download/details.aspx?familyid=e175c436-37e0-497f-8b7f-6cacaa25ad7c)\*\*
（低）
</td>
<td style="border:1px solid black;">
[Windows Server 2008（用于 32 位系统）和 Windows Server 2008（用于 32 位系统）Service Pack 2 中的 Internet Explorer 7](https://www.microsoft.com/download/details.aspx?familyid=8c4c91ec-1b2b-4176-bd77-45245b590329)\*\*
（严重）
[Windows Server 2008（用于 32 位系统）和 Windows Server 2008（用于 32 位系统）Service Pack 2 中的 Internet Explorer 8](https://www.microsoft.com/download/details.aspx?familyid=f5ce8582-af63-4870-bee3-0abeeefa1458)\*\*
（严重）
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
Windows Server 2008（用于基于 x64 的系统）和 Windows Server 2008（用于基于 x64 的系统）Service Pack 2
</td>
<td style="border:1px solid black;">
[Windows Server 2008（用于基于 x64 的系统）和 Windows Server 2008（用于基于 x64 的系统）Service Pack 2](https://www.microsoft.com/download/details.aspx?familyid=1b10a177-fd45-406f-8edc-b8d4b84881b7)\*\*
（低）
</td>
<td style="border:1px solid black;">
[Windows Server 2008（用于基于 x64 的系统）和 Windows Server 2008（用于基于 x64 的系统）Service Pack 2 中的 Internet Explorer 7](https://www.microsoft.com/download/details.aspx?familyid=4f9975b8-3f91-4116-9200-ef55ece75854)\*\*
（严重）
[Windows Server 2008（用于基于 x64 的系统）和 Windows Server 2008（用于基于 x64 的系统）Service Pack 2 中的 Internet Explorer 8](https://www.microsoft.com/download/details.aspx?familyid=be11981c-d286-4e3c-94bf-d4e67a975d5a)\*\*
（严重）
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2008（用于基于 Itanium 的系统）和 Windows Server 2008（用于基于 Itanium 的系统）Service Pack 2
</td>
<td style="border:1px solid black;">
[Windows Server 2008（用于基于 Itanium 的系统）和 Windows Server 2008（用于基于 Itanium 的系统）Service Pack 2](https://www.microsoft.com/download/details.aspx?familyid=e8bc9a24-a794-4827-a6bb-785c6b2189f4)
（低）
</td>
<td style="border:1px solid black;">
[Windows Server 2008（用于基于 Itanium 的系统）和 Windows Server 2008（用于基于 Itanium 的系统）Service Pack 2 中的 Internet Explorer 7](https://www.microsoft.com/download/details.aspx?familyid=9395547f-b620-4cbd-9ff5-11b76cd73859)
（严重）
</td>
</tr>
<tr>
<th colspan="3" style="border:1px solid black;">
Windows 7
</th>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
**公告标识符**
</td>
<td style="border:1px solid black;">
[**MS10-001**](https://technet.microsoft.com/security/bulletin/ms10-001)
</td>
<td style="border:1px solid black;">
[**MS10-002**](https://technet.microsoft.com/security/bulletin/ms10-002)
</td>
</tr>
<tr>
<td style="border:1px solid black;">
**综合严重等级**
</td>
<td style="border:1px solid black;">
[**低**](https://go.microsoft.com/fwlink/?linkid=21140)
</td>
<td style="border:1px solid black;">
[**严重**](https://go.microsoft.com/fwlink/?linkid=21140)
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
Windows 7（用于 32 位系统）
</td>
<td style="border:1px solid black;">
[Windows 7（用于 32 位系统）](https://www.microsoft.com/download/details.aspx?familyid=75491ad0-40a6-4efb-9574-d82210f6d0da)
（低）
</td>
<td style="border:1px solid black;">
[Windows 7（用于 32 位系统）中的 Internet Explorer 8](https://www.microsoft.com/download/details.aspx?familyid=278443c1-15dc-436b-893b-ffea6d29d16d)
（严重）
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows 7（用于基于 x64 的系统）
</td>
<td style="border:1px solid black;">
[Windows 7（用于基于 x64 的系统）](https://www.microsoft.com/download/details.aspx?familyid=8a53f0e9-0616-440e-90f2-a12524e1bee4)
（低）
</td>
<td style="border:1px solid black;">
[Windows 7（用于基于 x64 的系统）中的 Internet Explorer 8](https://www.microsoft.com/download/details.aspx?familyid=a584cd0f-2e05-4e36-8858-0ffead637162)
（严重）
</td>
</tr>
<tr>
<th colspan="3" style="border:1px solid black;">
Windows Server 2008 R2
</th>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
**公告标识符**
</td>
<td style="border:1px solid black;">
[**MS10-001**](https://technet.microsoft.com/security/bulletin/ms10-001)
</td>
<td style="border:1px solid black;">
[**MS10-002**](https://technet.microsoft.com/security/bulletin/ms10-002)
</td>
</tr>
<tr>
<td style="border:1px solid black;">
**综合严重等级**
</td>
<td style="border:1px solid black;">
[**低**](https://go.microsoft.com/fwlink/?linkid=21140)
</td>
<td style="border:1px solid black;">
[**严重**](https://go.microsoft.com/fwlink/?linkid=21140)
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
Windows Server 2008 R2（用于基于 x64 的系统）
</td>
<td style="border:1px solid black;">
[Windows Server 2008 R2（用于基于 x64 的系统）](https://www.microsoft.com/download/details.aspx?familyid=308166e4-571b-4d6c-bd9f-3ed4afa4eafe)\*\*
（低）
</td>
<td style="border:1px solid black;">
[Windows Server 2008 R2（用于基于 x64 的系统）中的 Internet Explorer 8](https://www.microsoft.com/download/details.aspx?familyid=d3386793-a594-4bc5-8308-28b561d43087)\*\*
（严重）
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2008 R2（用于基于 Itanium 的系统）
</td>
<td style="border:1px solid black;">
[Windows Server 2008 R2（用于基于 Itanium 的系统）](https://www.microsoft.com/download/details.aspx?familyid=1d0da42b-9755-4fd2-afd1-0d023d187133)
（低）
</td>
<td style="border:1px solid black;">
[Windows Server 2008 R2（用于基于 Itanium 的系统）中的 Internet Explorer 8](https://www.microsoft.com/download/details.aspx?familyid=9d137bab-8312-4240-af74-c65ba652fde0)
（严重）
</td>
</tr>
</table>
**Windows Server 2008 和 Windows Server 2008 R2 的注释**
**\*\*服务器核心安装不受影响。** 如果使用服务器核心安装选项安装如上所述的 Windows Server 2008 或 Windows Server 2008 R2，则此更新所解决的漏洞不会影响其的受支持版本。 有关该安装选项的详细信息，请参阅 MSDN 文章[服务器核心](https://msdn.microsoft.com/en-us/library/ms723891(vs.85).aspx)和[Windows Server 2008 R2 的服务器核心](https://msdn.microsoft.com/en-us/library/ee391631(vs.85).aspx)。注意，服务器核心安装选项不适用于 Windows Server 2008 和 Windows Server 2008 R2 的某些版本；请参阅[比较服务器核心安装选项](https://www.microsoft.com/windowsserver2008/en/us/compare-core-installation.aspx)。
检测和部署工具及指导
--------------------
**安全中心**
管理需要部署到组织中的服务器、台式机和移动计算机的软件和安全更新。 有关详细信息，请参阅 [TechNet 更新管理中心](https://go.microsoft.com/fwlink/?linkid=69903)。 [TechNet 安全中心](https://go.microsoft.com/fwlink/?linkid=21171)提供了有关 Microsoft 产品安全性的其他信息。 消费者可以访问[家庭安全](https://go.microsoft.com/fwlink/?linkid=85102)，也可以通过单击“最新的安全更新”访问此信息。
安全更新可从 [Microsoft Update](https://go.microsoft.com/fwlink/?linkid=40747) 和 [Windows Update](https://go.microsoft.com/fwlink/?linkid=21130) 获得。 [Microsoft 下载中心](https://go.microsoft.com/fwlink/?linkid=21129)也提供了安全更新。 通过输入关键字“安全更新”可以非常方便地找到些更新。
最后，可以从 [Microsoft Update 目录](https://go.microsoft.com/fwlink/?linkid=96155)下载安全更新。 Microsoft Update 目录提供通过 Windows Update 和 Microsoft Update 提供的内容的可搜索目录，包括安全更新、驱动程序和 Service Pack。 通过使用安全公告编号（例如“MS07-036”）进行搜索，您可以将所有适用的更新添加到您的篮（包括某个更新的不同语言），然后将其下载到您选择的文件夹。 有关 Microsoft Update 目录的详细信息，请参阅 [Microsoft Update 目录常见问题](https://go.microsoft.com/fwlink/?linkid=97900)。
**注意** 从 2009 年 8 月 1 日起，Microsoft 将不再对 Office Update 和 Office Update 清单工具提供支持。 要继续获得 Microsoft Office 产品的最新更新，请使用 [Microsoft Update](https://go.microsoft.com/fwlink/?linkid=40747)。 有关详细信息，请参阅[关于 Microsoft Office Update： 常见问题](https://office.microsoft.com/en-us/downloads/fx010402221033.aspx)。
**检测和部署指南**
Microsoft 提供安全更新的检测和部署指南。 该指南包含可帮助 IT 专业人员了解如何使用各种工具检测和部署安全更新的建议和信息。 有关详细信息，请参阅 [Microsoft 知识库文章 961747](https://support.microsoft.com/kb/961747)。
**Microsoft Baseline Security Analyzer**
管理员可使用 Microsoft Baseline Security Analyzer (MBSA)，在本地和远程系统中扫描缺少的安全更新和常见的安全配置错误。 有关 MBSA 的详细信息，请访问 [Microsoft Baseline Security Analyzer](https://go.microsoft.com/fwlink/?linkid=21134)。
**Windows Server Update Services**
通过使用 Windows Server Update Services (WSUS)，管理员可以快速可靠地将 Microsoft Windows 2000 操作系统和更高版本、Office XP 和更高版本、Exchange Server 2003 以及 SQL Server 2000 的最新关键更新和安全更新部署到 Microsoft Windows 2000 和更高版本的操作系统。
有关如何使用 Windows Server Update Services 部署此安全更新的详细信息，请访问 [Windows Server Update Services](https://go.microsoft.com/fwlink/?linkid=50120)。
**Systems Management Server**
Microsoft Systems Management Server (SMS) 提供了一个用于管理更新且可高度配置的企业解决方案。 通过使用 SMS，管理员可以确定需要安全更新的基于 Windows 的系统，并在整个企业中以可控制的方式执行这些更新的部署，而对最终用户造成的干扰最少。 SMS 的下一版本 System Center Configuration Manager 2007 现已可用；另请参阅 [System Center Configuration Manager 2007](https://technet.microsoft.com/en-us/library/bb735860.aspx)。有关管理员如何使用 SMS 2003 部署安全更新的详细信息，请参阅 [SMS 2003 安全修补程序管理](https://go.microsoft.com/fwlink/?linkid=22939)。 SMS 2.0 用户还可以使用安全更新清单工具 (SUIT) 来帮助部署安全更新。 有关 SMS 的信息，请访问 [Microsoft Systems Management Server](https://go.microsoft.com/fwlink/?linkid=21158)。
**注意：**SMS 使用 Microsoft 基准安全分析器提供对安全公告更新检测和部署的广泛支持。 这些工具可能检测不到某些软件更新。 在这些情况下，管理员可以使用 SMS 的清单功能将更新部署到特定系统上。 有关此过程的详细信息，请参阅[使用 SMS 软件分发功能部署软件更新](https://go.microsoft.com/fwlink/?linkid=33341)。 某些安全更新在重新启动系统后可能需要管理权限。 管理员可以使用提升权限部署工具（在 [SMS 2.0 管理功能包](https://go.microsoft.com/fwlink/?linkid=21161)中提供）安装这些更新。
**更新兼容性评估程序和应用程序兼容性工具箱**
此更新通常写入运行应用程序所必需的相同文件和注册表设置。 这可触发不兼容并使安全更新的部署占用更多的时间。 通过使用[应用程序兼容性工具包](https://www.microsoft.com/download/details.aspx?familyid=24da89e9-b581-47b0-b45e-492dd6da2971&displaylang=en)中包含的[更新兼容性评估程序](https://technet2.microsoft.com/windowsvista/en/library/4279e239-37a4-44aa-aec5-4e70fe39f9de1033.mspx?mfr=true)组件，您可以简化测试和验证对已安装程序进行的 Windows 更新。
应用程序兼容性工具包 (ACT) 包含必要的工具和文档，以便在您的环境中部署 Microsoft Windows Vista、Windows Update、Microsoft Security Update 或新版本的 Windows Internet Explorer 之前评估和缓减应用程序的兼容性问题。
### 其他信息
#### Microsoft Windows 恶意软件删除工具
Microsoft 已在 Windows Update、Microsoft Update、Windows Server Update Services 和下载中心上发布了 Microsoft Windows 恶意软件删除工具的更新版本。
#### MU、WU 和 WSUS 上的非安全、高优先级更新
有关 Windows Update 和 Microsoft Update 上非安全发布的信息，请参阅：
- [Microsoft 知识库文章 894199](https://support.microsoft.com/kb/894199)： Software Update Services 和 Windows Server Update Services 的内容更改说明。 包括所有 Windows 内容。
- [过去几个月关于 Windows Server Update Services 的更新](https://technet.microsoft.com/en-us/wsus/bb456965.aspx)。 显示除 Microsoft Windows 之外的 Microsoft 产品的所有新的、修订的和重新发布的更新。
#### Microsoft Active Protections Program (MAPP)
为改进客户的安全保护，Microsoft 在发布每月安全更新之前将向主要的安全软件供应商提供漏洞信息。 然后，安全软件供应商可以使用该漏洞信息通过其安全软件或者设备向客户提供更新的保护，例如防病毒、基于网络的入侵检测系统或者基于主机的入侵防止系统。 要确定是否可从安全软件供应商处得到活动保护，请访问计划合作伙伴（在 [Microsoft Active Protections Program (MAPP) 合作伙伴](https://www.microsoft.com/security/msrc/mapp/partners.mspx)中列出）提供的活动保护网站。
#### 安全策略和社区
**更新管理策略**
[更新管理安全指导](https://go.microsoft.com/fwlink/?linkid=21168)提供 Microsoft 关于应用安全更新的最佳方案建议的其他信息。
**获取其他安全更新**
可从以下位置获得针对其他安全问题的更新：
- [Microsoft 下载中心](https://go.microsoft.com/fwlink/?linkid=21129)提供了安全更新。 通过输入关键字“安全更新”可以非常方便地找到些更新。
- [Microsoft Update](https://go.microsoft.com/fwlink/?linkid=40747) 提供了消费者平台的更新。
- 您可以从 Microsoft 下载中心的“安全和关键发布 ISO CD 映像文件”获得本月 Windows Update 上提供的安全更新。 有关详细信息，请参阅 [Microsoft 知识库文章 913086](https://support.microsoft.com/kb/913086)。
**IT 专业人员安全区域社区**
了解如何提高安全性和优化 IT 基础结构，并在 [IT 专业人员安全社区](https://go.microsoft.com/fwlink/?linkid=21164)中就安全主题与其他 IT 专业人员展开讨论。
#### 鸣谢
Microsoft [感谢](https://go.microsoft.com/fwlink/?linkid=21127)下列人员或组织与我们一起致力于保护客户的利益：
- [Google Inc.](https://www.google.com/) 的 Tavis Ormandy 报告了 MS10-001 中描述的问题
- [David Lindsay "thornmaker"](https://p42.us/) 和 [Eduardo A. Vela Nava "sirdarckcat"](https://www.sirdarckcat.net/) 报告了 MS10-002 中描述的问题
- Lostmon Lords 报告了 MS10-002 中描述的问题
- Brett Moore 与 [TippingPoint](https://www.tippingpoint.com/) 和 [Zero Day Initiative](https://www.zerodayinitiative.com/) 一起报告了 MS10-002 中描述的问题
- [team509](https://www.team509.com/) 的 Wushi 与 [TippingPoint](https://www.tippingpoint.com/) 和 [Zero Day Initiative](https://www.zerodayinitiative.com/) 一起报告了 MS10-002 中描述的问题
- eshu.co.uk 的 Sam Thomas 与 [TippingPoint](https://www.tippingpoint.com/) 和 [Zero Day Initiative](https://www.zerodayinitiative.com/) 合作报告了 MS10-002 中描述的问题
- eshu.co.uk 的 Sam Thomas 与 [TippingPoint](https://www.tippingpoint.com/) 和 [Zero Day Initiative](https://www.zerodayinitiative.com/) 合作报告了 MS10-002 中描述的问题
- [Fortinet FortiGuard Global Security Research Team](https://www.fortiguardcenter.com/) 的 Haifei Li 报告了 MS10-002 中描述的问题
- [Verisign iDefense Labs](https://labs.idefense.com/) 的 Peter Vreugdenhil 与 [TippingPoint](https://www.tippingpoint.com/) 和 [Zero Day Initiative](https://www.zerodayinitiative.com/) 合作报告了 MS10-002 中描述的问题
- [BugSec](https://www.bugsec.com/) 的 Meron Sellem 报告了 MS10-002 中描述的问题
Microsoft [感谢](https://go.microsoft.com/fwlink/?linkid=21127)以下公司与我们合作并提供关于 MS10-002 中描述的问题的详细信息：
- [Google Inc.](https://www.google.com/) 和 [MANDIANT](https://www.mandiant.com/)
- [Adobe](https://www.adobe.com/)
- [McAfee](https://www.mcafee.com/)
#### 支持
- 已对列出的受影响的软件进行测试，以确定受到影响的版本。 其他版本的支持生命周期已结束。 要确定软件版本的技术支持生命周期，请访问 [Microsoft 技术支持生命周期](https://go.microsoft.com/fwlink/?linkid=21742)。
- 美国和加拿大的客户可以通过[安全支持](https://go.microsoft.com/fwlink/?linkid=21131)或 1-866-PCSAFETY 获得技术支持。 与安全更新有关的电话支持服务是免费的。 有关可用支持选项的详细信息，请参阅 [Microsoft 帮助和支持](https://support.microsoft.com/)网站。
- 其他国家（或地区）的用户可从当地的 Microsoft 分公司获得支持。 与安全更新有关的支持服务不收取任何费用。 有关如何就支持问题与 Microsoft 联系方面的详细信息，请访问[国际帮助和支持](https://go.microsoft.com/fwlink/?linkid=21155)。
#### 免责声明
Microsoft 知识库中的信息“按原样”提供，没有任何形式的担保。 Microsoft 不作任何明示或暗示保证，包括对适销性和针对特定目的的适用性的保证。 Microsoft Corporation 或其供应商不对任何损害（包括直接的、间接的、偶然的、必然的损害，商业利润损失，或特殊损害）承担任何责任，即使 Microsoft Corporation 或其供应商事先已被告知有可能发生此类损害。 有些州不允许排除或限制必然或偶然损害的赔偿责任，因此上述限制可能不适用。
#### 修订版本
- V1.0（2010 年 1 月 12 日）： 已发布公告摘要。
- V2.0（2010 年 1 月 21 日）： 添加了 Microsoft 安全公告 **MS10-002，即 Internet Explorer 的累积性更新 (978207)**。 还添加了此额外安全公告的公告网络广播链接。
*Built at 2014-04-18T01:50:00Z-07:00*
| 49.16641 | 553 | 0.698173 | yue_Hant | 0.760422 |
ff97edda7cec4dd93f066f7faf58956a9fa1852b | 4,863 | md | Markdown | docs/framework/windows-workflow-foundation/activity-definition-scoping-and-visibility.md | kakkun61/docs.ja-jp | 1b866afaf766b040dfc17aefdafb2a1220e53c95 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/windows-workflow-foundation/activity-definition-scoping-and-visibility.md | kakkun61/docs.ja-jp | 1b866afaf766b040dfc17aefdafb2a1220e53c95 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/windows-workflow-foundation/activity-definition-scoping-and-visibility.md | kakkun61/docs.ja-jp | 1b866afaf766b040dfc17aefdafb2a1220e53c95 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: アクティビティ定義のスコープ設定と表示
ms.date: 03/30/2017
ms.assetid: ccdffa07-9503-4eea-a61b-17f1564368b7
ms.openlocfilehash: c7f656fee4960a8c43ac58abafba400ed9b35bc1
ms.sourcegitcommit: bc293b14af795e0e999e3304dd40c0222cf2ffe4
ms.translationtype: MT
ms.contentlocale: ja-JP
ms.lasthandoff: 11/26/2020
ms.locfileid: "96289166"
---
# <a name="activity-definition-scoping-and-visibility"></a>アクティビティ定義のスコープ設定と表示
アクティビティ定義のスコープと可視性は、オブジェクトのスコープと可視性と同様に、他のオブジェクトまたはアクティビティがアクティビティのメンバーにアクセスするために必要な機能です。 アクティビティ定義は次の実装によって実行されます。
1. アクティビティによってユーザーに公開されるメンバー (<xref:System.Activities.Argument>、<xref:System.Activities.Variable>、および <xref:System.Activities.ActivityDelegate> オブジェクト、および子アクティビティ) の指定。
2. アクティビティの実行ロジックの実装。
この実装には、アクティビティのコンシューマーには公開されないが、実装の詳細であるメンバーが含まれる場合があります。 型定義と同様に、作成者は、アクティビティ モデルを使用することで、定義対象のアクティビティの定義について、アクティビティ メンバーの可視性を指定できます。 この可視性によって、データのスコープなどメンバーの使用法の要素が決定します。
## <a name="scope"></a>Scope
データのスコープ以外に、アクティビティ モデルの可視性によって、検証、デバッグ、追跡、トレースなどのアクティビティの他の要素へのアクセスが制限される場合があります。 実行プロパティでは、実行の特性を特定の定義のスコープに制限するための可視性とスコープを使用します。 セカンダリ ルートでは、可視性とスコープを使用して、<xref:System.Activities.Statements.CompensableActivity> によってキャプチャされた状態を補正可能なアクティビティが使用される定義のスコープに制限します。
## <a name="definition-and-usage"></a>定義と使用法
ワークフローは、基本アクティビティクラスから継承し、 [組み込みのアクティビティライブラリ](net-framework-4-5-built-in-activity-library.md)のアクティビティを使用して、新しいアクティビティを作成することによって作成されます。 アクティビティを使用するには、アクティビティ作成者によってその定義の各コンポーネントの可視性が設定される必要があります。
### <a name="activity-members"></a>アクティビティ メンバー
アクティビティ モデルでは、アクティビティによってコンシューマーが使用できるようになる引数、変数、デリゲート、および子アクティビティが定義されます。 各メンバーは、`public` または `private` として宣言できます。 パブリック メンバーはアクティビティのコンシューマーが設定し、`private` メンバーはアクティビティの作成者によって指定された実装を使用します。 データのスコープの可視性に関する規則は、次のとおりです。
1. パブリック メンバーおよびパブリック子アクティビティのパブリック メンバーは、パブリック変数を参照できます。
2. プライベート メンバーおよびパブリック子アクティビティのパブリック メンバーは引数およびプライベート変数を参照できます。
アクティビティのコンシューマーが設定可能なメンバーは、プライベートに指定できません。
### <a name="authoring-models"></a>作成モデル
カスタム アクティビティは、<xref:System.Activities.NativeActivity>、<xref:System.Activities.Activity>、<xref:System.Activities.CodeActivity>、または <xref:System.Activities.AsyncCodeActivity> を使用して定義されます。 これらのクラスから派生するアクティビティによって、可視性が異なるさまざまなメンバー型が公開されます。
#### <a name="nativeactivity"></a>NativeActivity
<xref:System.Activities.NativeActivity> から派生したアクティビティの動作は、命令型コードで記述され、任意で既存のアクティビティを使用して定義できます。 <xref:System.Activities.NativeActivity> からアクティビティを派生させると、ランタイムによって公開されるすべての機能にアクセスできます。 このようなアクティビティのメンバーは、引数を除く `public` としてのみ宣言可能なパブリックまたはプライベートの可視性を使用して定義できます。
<xref:System.Activities.NativeActivity> から派生したクラスのメンバーは、<xref:System.Activities.NativeActivityMetadata> メソッドに渡される <xref:System.Activities.NativeActivity.CacheMetadata%2A> 構造体を使用してランタイムに宣言されます。
#### <a name="activity"></a>アクティビティ
<xref:System.Activities.Activity> を使用して作成されたアクティビティの動作は、他のアクティビティが作成されることで厳密にデザインされます。 <xref:System.Activities.Activity> クラスの 1 つの実装子アクティビティは、<xref:System.Activities.Activity.Implementation%2A> を使用するランタイムによって取得されます。 <xref:System.Activities.Activity> から派生するアクティビティは、パブリック引数、パブリック変数、インポートされた ActivityDelegates、およびインポートされた Activities を定義します。
インポートされた ActivityDelegates および Activities は、パブリックのアクティビティの子として宣言されますが、アクティビティによって直接はスケジュールされません。 この情報は検証時に使用され、アクティビティが実行されないロケーションで複数の親が同時に検証されるのを防ぎます。 また、パブリック子と同様に、インポートされた子は、アクティビティの実装時に参照およびスケジュールされます。 つまり、Activity1 と呼ばれるアクティビティをインポートするアクティビティには、Activity1 をスケジュールする実装の <xref:System.Activities.Statements.Sequence> が含まれている場合があります。
#### <a name="codeactivity-asynccodeactivity"></a>CodeActivity/ AsyncCodeActivity
この基本クラスは、命令型コードの動作の定義に使用されます。 このクラスから派生したアクティビティだけが、このアクティビティよって公開された引数にアクセスできます。 つまり、これらのアクティビティによって公開されるメンバーのみがパブリック引数になります。 他のメンバーおよび可視性はこれらのアクティビティに適用されません。
#### <a name="summary-of-visibilities"></a>可視性の概要
このセクションの前半の情報の概要を次の表に示します。
|メンバーの型|NativeActivity|アクティビティ|CodeActivity/ AsyncCodeActivity|
|-----------------|--------------------|--------------|--------------------------------------|
|引数|パブリック/プライベート|パブリック|適用外|
|変数|パブリック/プライベート|パブリック|適用外|
|Child Activities|パブリック/プライベート|パブリック (実装時に定義された修正済みのプライベート子)|適用外|
|ActivityDelegates|パブリック/プライベート|パブリック|適用外|
通常、アクティビティのコンシューマーが設定不可能なメンバーは、パブリックに指定できません。
### <a name="execution-properties"></a>実行プロパティ
状況によっては、特定の実行プロパティのスコープをアクティビティのパブリック子に限定すると便利な場合があります。 <xref:System.Activities.ExecutionProperties> コレクションによって、<xref:System.Activities.ExecutionProperties.Add%2A> メソッドでこれを実行できます。 このメソッドの Boolean 型パラメーターは、特定のプロパティのスコープがすべての子に限定されているか、パブリックである子にのみ限定されているかを示します。 このパラメーターが `true` に設定されている場合、プロパティはパブリック メンバーおよびパブリック子のパブリック メンバーに可視性が限定されます。
### <a name="secondary-roots"></a>セカンダリ ルート
セカンダリ ルートは、補正アクティビティの状態を管理するためのランタイムの内部の機構です。 <xref:System.Activities.Statements.CompensableActivity> の実行が終了しても、その状態はすぐにクリーン アップされません。 代わりに、補正が完了するまで、セカンダリ ルートのランタイムによってこの状態が維持されます。 セカンダリ ルートによってキャプチャされた配置環境は、補正可能なアクティビティが使用される定義のスコープに対応します。
| 60.7875 | 341 | 0.817191 | yue_Hant | 0.689691 |
ff9922c2d7a09a3683359df45a1c571b8a96e663 | 37 | md | Markdown | README.md | qiutianha/chatroom | 2b8d059183a19aa99149774aa2980d040419f79f | [
"MIT"
] | null | null | null | README.md | qiutianha/chatroom | 2b8d059183a19aa99149774aa2980d040419f79f | [
"MIT"
] | null | null | null | README.md | qiutianha/chatroom | 2b8d059183a19aa99149774aa2980d040419f79f | [
"MIT"
] | null | null | null | # chatroom
用redis的subscribe api写的聊天室
| 12.333333 | 25 | 0.864865 | eng_Latn | 0.799157 |
ff994aaa2830da2579a664bfd9b2e53bfb583ca6 | 47 | md | Markdown | README.md | raulivan/JavaRMI | 258ba52f8d33b7ad962ed37d4b725e3370fd9ff6 | [
"Apache-2.0"
] | null | null | null | README.md | raulivan/JavaRMI | 258ba52f8d33b7ad962ed37d4b725e3370fd9ff6 | [
"Apache-2.0"
] | null | null | null | README.md | raulivan/JavaRMI | 258ba52f8d33b7ad962ed37d4b725e3370fd9ff6 | [
"Apache-2.0"
] | null | null | null | # JavaRMI
Exemplo de implementação do Java RMI
| 15.666667 | 36 | 0.808511 | por_Latn | 0.996888 |
ff997efc950d8963ff9262fc8cec6883b05675da | 139 | md | Markdown | src/content/milenefizel.md | anderoma/deroma-antoine | 494635eb290a5f6909813a40983ffa53becebfe0 | [
"RSA-MD"
] | null | null | null | src/content/milenefizel.md | anderoma/deroma-antoine | 494635eb290a5f6909813a40983ffa53becebfe0 | [
"RSA-MD"
] | null | null | null | src/content/milenefizel.md | anderoma/deroma-antoine | 494635eb290a5f6909813a40983ffa53becebfe0 | [
"RSA-MD"
] | null | null | null | ---
title:
width: 3
height: 2
xrank: 9
yrank: 0
bgcolor:
bgimg: milenefizel.png
---
<img src="/img/milenefizel.png" alt="Milenefizel.com"> | 12.636364 | 54 | 0.690647 | vie_Latn | 0.169851 |
ff998521457d2b1e22650beb9f36656d662be65b | 12,077 | md | Markdown | mailfilter/CHANGELOG.md | erik73/repository-edge | 6ffc44533a8b62fac152f47412e955051e12ff27 | [
"MIT"
] | null | null | null | mailfilter/CHANGELOG.md | erik73/repository-edge | 6ffc44533a8b62fac152f47412e955051e12ff27 | [
"MIT"
] | null | null | null | mailfilter/CHANGELOG.md | erik73/repository-edge | 6ffc44533a8b62fac152f47412e955051e12ff27 | [
"MIT"
] | null | null | null | # Changelog since v1.1.5
- Merge pull request #79 from erik73/dependabot/github_actions/docker/login-action-1.12.0
Bump docker/login-action from 1.10.0 to 1.12.0
- Bump docker/login-action from 1.10.0 to 1.12.0
Bumps [docker/login-action](https://github.com/docker/login-action) from 1.10.0 to 1.12.0.
- [Release notes](https://github.com/docker/login-action/releases)
- [Commits](https://github.com/docker/login-action/compare/v1.10.0...v1.12.0)
---
updated-dependencies:
- dependency-name: docker/login-action
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <[email protected]>
- Merge pull request #78 from erik73/dependabot/github_actions/creyD/prettier_action-4.1.1
Bump creyD/prettier_action from 4.0 to 4.1.1
- Bump creyD/prettier_action from 4.0 to 4.1.1
Bumps [creyD/prettier_action](https://github.com/creyD/prettier_action) from 4.0 to 4.1.1.
- [Release notes](https://github.com/creyD/prettier_action/releases)
- [Commits](https://github.com/creyD/prettier_action/compare/v4.0...v4.1.1)
---
updated-dependencies:
- dependency-name: creyD/prettier_action
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <[email protected]>
- Merge pull request #76 from erik73/dependabot/github_actions/actions/cache-2.1.7
Bump actions/cache from 2.1.6 to 2.1.7
- Bump actions/cache from 2.1.6 to 2.1.7
Bumps [actions/cache](https://github.com/actions/cache) from 2.1.6 to 2.1.7.
- [Release notes](https://github.com/actions/cache/releases)
- [Commits](https://github.com/actions/cache/compare/v2.1.6...v2.1.7)
---
updated-dependencies:
- dependency-name: actions/cache
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <[email protected]>
- Merge pull request #75 from erik73/update_base
Update base image
- Update base image
- Merge pull request #73 from erik73/dependabot/github_actions/frenck/action-addon-linter-2.5
Bump frenck/action-addon-linter from 2.4 to 2.5
- Merge pull request #72 from erik73/dependabot/github_actions/frenck/action-addon-information-1.3
Bump frenck/action-addon-information from 1.2 to 1.3
- Merge pull request #74 from erik73/dependabot/github_actions/actions/checkout-2.4.0
Bump actions/checkout from 2.3.5 to 2.4.0
- Bump actions/checkout from 2.3.5 to 2.4.0
Bumps [actions/checkout](https://github.com/actions/checkout) from 2.3.5 to 2.4.0.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](https://github.com/actions/checkout/compare/v2.3.5...v2.4.0)
---
updated-dependencies:
- dependency-name: actions/checkout
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <[email protected]>
- Bump frenck/action-addon-linter from 2.4 to 2.5
Bumps [frenck/action-addon-linter](https://github.com/frenck/action-addon-linter) from 2.4 to 2.5.
- [Release notes](https://github.com/frenck/action-addon-linter/releases)
- [Commits](https://github.com/frenck/action-addon-linter/compare/v2.4...v2.5)
---
updated-dependencies:
- dependency-name: frenck/action-addon-linter
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <[email protected]>
- Bump frenck/action-addon-information from 1.2 to 1.3
Bumps [frenck/action-addon-information](https://github.com/frenck/action-addon-information) from 1.2 to 1.3.
- [Release notes](https://github.com/frenck/action-addon-information/releases)
- [Commits](https://github.com/frenck/action-addon-information/compare/v1.2...v1.3)
---
updated-dependencies:
- dependency-name: frenck/action-addon-information
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <[email protected]>
- Merge pull request #71 from erik73/dependabot/github_actions/actions/checkout-2.3.5
Bump actions/checkout from 2.3.4 to 2.3.5
- Bump actions/checkout from 2.3.4 to 2.3.5
Bumps [actions/checkout](https://github.com/actions/checkout) from 2.3.4 to 2.3.5.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](https://github.com/actions/checkout/compare/v2.3.4...v2.3.5)
---
updated-dependencies:
- dependency-name: actions/checkout
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <[email protected]>
- Merge pull request #69 from erik73/dependabot/github_actions/dessant/lock-threads-3
Bump dessant/lock-threads from 2.1.2 to 3
- Merge pull request #70 from erik73/dependabot/github_actions/frenck/action-addon-linter-2.4
Bump frenck/action-addon-linter from 2.3 to 2.4
- Bump frenck/action-addon-linter from 2.3 to 2.4
Bumps [frenck/action-addon-linter](https://github.com/frenck/action-addon-linter) from 2.3 to 2.4.
- [Release notes](https://github.com/frenck/action-addon-linter/releases)
- [Commits](https://github.com/frenck/action-addon-linter/compare/v2.3...v2.4)
---
updated-dependencies:
- dependency-name: frenck/action-addon-linter
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <[email protected]>
- Bump dessant/lock-threads from 2.1.2 to 3
Bumps [dessant/lock-threads](https://github.com/dessant/lock-threads) from 2.1.2 to 3.
- [Release notes](https://github.com/dessant/lock-threads/releases)
- [Changelog](https://github.com/dessant/lock-threads/blob/master/CHANGELOG.md)
- [Commits](https://github.com/dessant/lock-threads/compare/v2.1.2...v3)
---
updated-dependencies:
- dependency-name: dessant/lock-threads
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <[email protected]>
- Merge pull request #68 from erik73/dependabot/github_actions/creyD/prettier_action-4.0
Bump creyD/prettier_action from 3.3 to 4.0
- Bump creyD/prettier_action from 3.3 to 4.0
Bumps [creyD/prettier_action](https://github.com/creyD/prettier_action) from 3.3 to 4.0.
- [Release notes](https://github.com/creyD/prettier_action/releases)
- [Commits](https://github.com/creyD/prettier_action/compare/v3.3...v4.0)
---
updated-dependencies:
- dependency-name: creyD/prettier_action
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <[email protected]>
- Merge pull request #67 from erik73/dependabot/github_actions/docker/setup-buildx-action-1.6.0
Bump docker/setup-buildx-action from 1.5.1 to 1.6.0
- Merge pull request #66 from erik73/update_base
Update base image 1.0.8
- Bump docker/setup-buildx-action from 1.5.1 to 1.6.0
Bumps [docker/setup-buildx-action](https://github.com/docker/setup-buildx-action) from 1.5.1 to 1.6.0.
- [Release notes](https://github.com/docker/setup-buildx-action/releases)
- [Commits](https://github.com/docker/setup-buildx-action/compare/v1.5.1...v1.6.0)
---
updated-dependencies:
- dependency-name: docker/setup-buildx-action
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <[email protected]>
- Update base image 1.0.8
- Merge pull request #64 from erik73/dependabot/github_actions/docker/build-push-action-2.7.0
Bump docker/build-push-action from 2.6.1 to 2.7.0
- Merge pull request #65 from erik73/dependabot/github_actions/frenck/action-addon-linter-2.3
Bump frenck/action-addon-linter from 2.2 to 2.3
- Bump frenck/action-addon-linter from 2.2 to 2.3
Bumps [frenck/action-addon-linter](https://github.com/frenck/action-addon-linter) from 2.2 to 2.3.
- [Release notes](https://github.com/frenck/action-addon-linter/releases)
- [Commits](https://github.com/frenck/action-addon-linter/compare/v2.2...v2.3)
---
updated-dependencies:
- dependency-name: frenck/action-addon-linter
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <[email protected]>
- Bump docker/build-push-action from 2.6.1 to 2.7.0
Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 2.6.1 to 2.7.0.
- [Release notes](https://github.com/docker/build-push-action/releases)
- [Commits](https://github.com/docker/build-push-action/compare/v2.6.1...v2.7.0)
---
updated-dependencies:
- dependency-name: docker/build-push-action
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <[email protected]>
- Merge pull request #63 from erik73/dependabot/github_actions/dessant/lock-threads-2.1.2
Bump dessant/lock-threads from 2.1.1 to 2.1.2
- Bump dessant/lock-threads from 2.1.1 to 2.1.2
Bumps [dessant/lock-threads](https://github.com/dessant/lock-threads) from 2.1.1 to 2.1.2.
- [Release notes](https://github.com/dessant/lock-threads/releases)
- [Changelog](https://github.com/dessant/lock-threads/blob/master/CHANGELOG.md)
- [Commits](https://github.com/dessant/lock-threads/compare/v2.1.1...v2.1.2)
---
updated-dependencies:
- dependency-name: dessant/lock-threads
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <[email protected]>
- Merge pull request #61 from erik73/dependabot/github_actions/frenck/action-addon-linter-2.2
Bump frenck/action-addon-linter from 2.1 to 2.2
- Merge pull request #62 from erik73/dependabot/github_actions/actions/stale-4
Bump actions/stale from 3.0.19 to 4
- Bump actions/stale from 3.0.19 to 4
Bumps [actions/stale](https://github.com/actions/stale) from 3.0.19 to 4.
- [Release notes](https://github.com/actions/stale/releases)
- [Changelog](https://github.com/actions/stale/blob/main/CHANGELOG.md)
- [Commits](https://github.com/actions/stale/compare/v3.0.19...v4)
---
updated-dependencies:
- dependency-name: actions/stale
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <[email protected]>
- Bump frenck/action-addon-linter from 2.1 to 2.2
Bumps [frenck/action-addon-linter](https://github.com/frenck/action-addon-linter) from 2.1 to 2.2.
- [Release notes](https://github.com/frenck/action-addon-linter/releases)
- [Commits](https://github.com/frenck/action-addon-linter/compare/v2.1...v2.2)
---
updated-dependencies:
- dependency-name: frenck/action-addon-linter
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <[email protected]>
- Merge pull request #60 from erik73/dependabot/github_actions/docker/setup-buildx-action-1.5.1
Bump docker/setup-buildx-action from 1.5.0 to 1.5.1
- Bump docker/setup-buildx-action from 1.5.0 to 1.5.1
Bumps [docker/setup-buildx-action](https://github.com/docker/setup-buildx-action) from 1.5.0 to 1.5.1.
- [Release notes](https://github.com/docker/setup-buildx-action/releases)
- [Commits](https://github.com/docker/setup-buildx-action/compare/v1.5.0...v1.5.1)
---
updated-dependencies:
- dependency-name: docker/setup-buildx-action
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <[email protected]>
- Merge pull request #59 from erik73/dependabot/github_actions/dessant/lock-threads-2.1.1
Bump dessant/lock-threads from 2.0.3 to 2.1.1
- Bump dessant/lock-threads from 2.0.3 to 2.1.1
Bumps [dessant/lock-threads](https://github.com/dessant/lock-threads) from 2.0.3 to 2.1.1.
- [Release notes](https://github.com/dessant/lock-threads/releases)
- [Changelog](https://github.com/dessant/lock-threads/blob/master/CHANGELOG.md)
- [Commits](https://github.com/dessant/lock-threads/compare/v2.0.3...v2.1.1)
---
updated-dependencies:
- dependency-name: dessant/lock-threads
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <[email protected]>
| 37.506211 | 108 | 0.754906 | yue_Hant | 0.309503 |
ff99954d626665a73108693693dcf1ce44dff57a | 22,377 | md | Markdown | _posts/2015-02-24-como-se-tornar-um-desenvolvedor-front-end.md | farhamdani/brodanie.github.io | 7709aabfd9217a5c532f6a9ca1f696989c20061c | [
"MIT"
] | 1 | 2018-05-18T15:10:03.000Z | 2018-05-18T15:10:03.000Z | _posts/2015-02-24-como-se-tornar-um-desenvolvedor-front-end.md | brodanie/brodanie.github.io | 7709aabfd9217a5c532f6a9ca1f696989c20061c | [
"MIT"
] | null | null | null | _posts/2015-02-24-como-se-tornar-um-desenvolvedor-front-end.md | brodanie/brodanie.github.io | 7709aabfd9217a5c532f6a9ca1f696989c20061c | [
"MIT"
] | null | null | null | ---
layout: post
title: "Como se tornar um desenvolvedor Front End"
date: 2015-02-24 15:46:24
image: '/assets/img/quero-ser-desenvolvedor-frontend/main.png'
description: "Aprenda os caminhos para virar um desenvolvedor Front End de qualidade."
main-class: 'dev'
color: '#637a91'
tags:
- frontend
- css
- js
- tutorial
categories:
twitter_text: "Aprenda os caminhos para virar um desenvolvedor Front End de qualidade."
introduction: "Aprenda os caminhos para virar um desenvolvedor Front End de qualidade, seguindo desde o básico, ao intermediário e avançado. Vendo desde o HTML, CSS e JS até Ferramentas de automação e Performance."
---
## Índice
- [Introdução](#intro)
- [O que faz um desenvolvedor Front End?](#oqfaz)
- [Qual a importância do Front End?](#import)
- [Mercado de Trabalho](#mercado)
- [Níveis de conhecimento](#niveis)
- [Eita lascou, como aprendo tudo isso?](#eita)
- [Inglês](#ingles)
- [Editores de Código](#editores)
- [Básico do Terminal](#terminal)
- [HTML](#html)
- [CSS](#css)
- [Javascript](#js)
- [Controle de Versão](#git)
- [Seo](#seo)
- [Performance](#perf)
- [Automação de Tarefas](#task)
- [Mantenha-se Atualizado](#update)
- [Dicas](#dicas)
<h2 id="intro">Introdução</h2>
Bom, já faz um tempinho que eu não escrevo no blog, mas é por um bom motivo, estou me mudando de empresa e com isso eu estou precisando organizar algumas coisas da minha vida, inclusive uma mudança de cidade.
Algum tempo eu já pensava em fazer um post parecido e como estou precisando também deixar alguns guias para os futuros desenvolvedores que vão entrar no meu lugar, resolvi unir o útil ao agradável e criar esse post. Espero que ajude a quem está começando e para quem já é experiente, que possa acrescentar com outras dicas, dar alguns detalhes de sua experiência, seria bastante legal.
O post será separado em algumas partes, onde irei responder algumas dúvidas comuns, links para estudo, requisitos básicos, enfim, um compilado grandão de informações. A ideia é passar só um pouco de conteúdo para vocês se guiarem, é claro que não vou colocar todos os meus favoritos, senão seria um post gigantesco.
<h2 id="oqfaz">O que faz um desenvolvedor Front End?</h2>
> O desenvolvedor front end é o profissional responsável por projetar, construir e otimizar as interfaces de um projeto web.
### Responsabilidades
- Trabalhar junto a equipe de design para criar a melhor experiência possível
- Desenvolver código limpo e bem documentado
- Seguir os web standards
- Se preocupar com a performance no client-side
- Aplicar técnicas de SEO
- etc...
É claro que as responsabilidades mudam de acordo com a empresa em que você for trabalhar, mas essa é uma base comum na maioria dos lugares.
<h2 id="import">Qual a importância do Front End?</h2>
É claro que a maioria já deve saber a necessidade desse profissional, mas vale ressaltar alguns detalhes:
- 80% do tempo de carregamento é gasto no frontend
- Cada vez mais as interfaces vem ficando complexas e detalhadas, fazendo ainda mais necessária a presença de um especialista
- O visual é a primeira coisa a ser vista, se ele estiver quebrado, o risco do usuário sair e nunca mais voltar é maior
- etc...
<h2 id="mercado">Mercado de trabalho</h2>
Acho que uma imagem já fala mais que mil palavras né? A busca por desenvolvedores front end só está crescendo, isso permite salários maiores para quem é qualificado de verdade, boas empresas para se trabalhar, etc.
<h2 id="niveis">Níveis de conhecimento</h2>
Olha, definir níveis de conhecimento, seja para qualquer profissão é algo bastante complicado, porque depende do que você vai se especializar. Eu meio que fiz uma separação mais ou menos de alguns assuntos que julgo necessários para cada nível de desenvolvedor. Terão alguns **extras**, que são assuntos interessantes, mas não fundamentais para aquele nível. Lembrando que os níveis mais altos compreendem tudo dos níveis anteriores.
>Lembre-se: essas informações podem variar bastante de lugar para lugar.
### Iniciante Básico
- HTML (estrutura e tags)
- CSS (propriedades básicas)
- JS (pequenas noções, chamadas de scripts prontos)
- Básico de Photoshop (recortes, cores, fontes)
### Intermediário
- HTML (Semântica e Acessibilidade)
- CSS (propriedades avançadas do CSS3, Design Responsivo, funcionamento de grids e noção de frameworks)
- JS (Entendimento da linguagem, noções de orientação a objeto)
- Ferramenta de Versionamento (Git)
- Noções de performance
- SEO (**Extra**)
### Avançado
- CSS (Entender pre-processadores e suas funcões)
- JS (Conhecimento forte na linguagem, entender algumas arquiteturas e Testes)
- NodeJS (Saber como funciona e alguns conhecimentos basicos para automatização e afins)
- Grunt/Gulp (saber como automatizar processos)
- Bons conhecimentos de performance
- Noções de UX/UI (**Extra**)
### Master
- CSS (conceitos avançados de arquitetura - BEM, Organic, Atomic)
- JS (Total domínio na linguagem, design patterns na palma da mão)
- NodeJS (saber como criar módulos, chamá-los tanto no front quanto no back)
- Ter sólida experiência em sistemas front como o MEAN Stack
<h2 id="eita">Eita lascou, como aprendo tudo isso?</h2>
Estava achando que ser desenvolvedor front end é moleza? Como disse o [Nicholas C. Zakas](https://twitter.com/slicknet)
Cada dia uma nova tecnologia é lançada e precisamos nos manter sempre atualizados, a questão é, como fazer tudo isso? Fiz um post há um tempo atrás falando sobre [técnicas de aprendizado](https://willianjusten.com.br/tecnicas-de-aprendizado/), que podem ajudar um pouco nessa longa caminhada.
Vou separar aqui as principais áreas que precisamos estudar, o porquê delas e alguns links para auxiliá-los no estudo.
---
<h2 id="ingles">Inglês</h2>
Sim, uma das coisas mais importantes para se tornar um bom desenvolvedor é saber inglês. É claro que eu não estou falando que você precisa ser fluente como um americano legítimo de início, mas saber ler e assistir vídeos vai te ajudar muito, visto que a maioria do material vai estar em inglês, você querendo ou não. Não fique mendigando informações só na sua língua, saia do comodismo e vá aprender inglês, vai por mim, vai ser o melhor investimento que você pode fazer. Sobre como aprender inglês, existem vários métodos, desde os cursos tradicionais até programinhas para te ensinar. Dependendo do seu nível, eu recomendo fortemente um professor particular, pois ele poderá focar exatamente nas suas deficiências e você conseguirá evoluir bem rápido. Aqui vão alguns links legais falando do assunto:
- [Como aprender inglês](http://leandrooriente.com/como-aprender-ingles/)
- [Será que realmente o profissional de TI deve aprender inglês?](http://www.adamsilva.com.br/carreira/sera-que-realmente-o-profissional-de-ti-deve-aprender-ingles/)
---
<h2 id="editores">Editores de código</h2>
Eles são basicamente o nosso braço direito, é importante escolher um editor que seja confortável para você e agilize o seu workflow. Não entre em guerrinhas de qual é melhor ou pior, instale, use e veja qual te agrada mais. Os iniciantes sempre caem na tentação de perguntar o melhor e bom, cada um vai puxar sardinha para o seu lado.
- [Sublime Text](http://www.sublimetext.com/)
- [Brackets](http://brackets.io/)
- [Atom](https://atom.io/)
- [Vim](http://www.vim.org/)
- Procure que tem muitos!
#### Sublime Text
- [12 Most-Wanted Sublime Text Tips And Tricks](http://www.hongkiat.com/blog/sublime-text-tips/)
- [7 Plugins do sublime que você deveria conhecer](https://tableless.com.br/7-plugins-sublime-text-que-voce-deveria-conhecer/)
#### Brackets
- [Brackets Course](http://css-snippets.com/brackets-course/)
#### Vim
- [12 Vim Tips](http://dalibornasevic.com/posts/43-12-vim-tips)
- [Powe Vim Usage](http://www.ukuug.org/events/linux2004/programme/paper-SMyers/Linux_2004_slides/vim_tips/)
- [Vim Adventures](http://vim-adventures.com/) - aprenda Vim jogando!!! Demais! <3
- [Vim Tutorials Screencasts and Resources](http://code.tutsplus.com/articles/25-vim-tutorials-screencasts-and-resources--net-14631)
---
<h2 id="terminal">Básico do Terminal</h2>
Se você quer ser realmente um programador bom, vai ter que largar esse medo e colocar a mão na massa. O terminal se torna ferramenta **FUNDAMENTAL** para níveis do intermediário ao avançado. Seja para usar seu controle de versão, seja para utilizar ferramentas de automação e outras várias ferramentas.
- [Unix: Conceitos e Comandos Básicos](http://www.ime.usp.br/~ueda/ldoc/rb.html)
- [Unix Course](http://www.tutorialspoint.com/unix/)
- [Learn Shell](http://learnshell.org/)
- [Learning the Shell](http://linuxcommand.org/lc3_learning_the_shell.php)
- [Blog do Vitor Britto](http://vitorbritto.com.br/blog/) - Esse cara vira e mexe solta alguma dica muito legal sobre.
---
<h2 id="html">HTML</h2>
A base de tudo, que vai governar a estrutura de todo o sistema. Qualquer desenvolvedor precisa saber ao menos o básico de html, inclusive a galera de backend. Já para galera de frontend, temos que nos atentar a mais detalhes, como: acessibilidade e semântica.
#### Básico
- [Codecademy HTML](http://www.codecademy.com/pt-BR/tracks/web)
- [Dash](https://dash.generalassemb.ly/)
- [Teamtreehouse](http://teamtreehouse.com/library/topic:learn-html/type:course)
- [CodeSchool](https://www.codeschool.com/paths/html-css)
- [30 Days to Learn Html and CSS](https://www.youtube.com/watch?v=yTHTo28hwTQ&list=PLgGbWId6zgaWZkPFI4Sc9QXDmmOWa1v5F)
- [Learn to code Html & CSS](https://learn.shayhowe.com/)
- [Apostila Web da Caelum](http://www.caelum.com.br/apostila-html-css-javascript/)
- [Dive into Html5 em Português](https://diveintohtml5.com.br/)
#### Semântica
- [Use Html5 sectioning elements](http://blog.teamtreehouse.com/use-html5-sectioning-elements)
- [SEO, Semântica e Html5](http://www.slideshare.net/fabioflat/seo-semantica-e-html5-12901651)
- [A semântica do HTML](https://speakerdeck.com/diegoeis/a-semantica-do-html)
### Acessibilidade
- [Slides de Acessibilidade na web](https://tableless.com.br/slides-para-devs-9-acessibilidade-na-web/)
- [WebAIM](http://webaim.org/intro/)
---
<h2 id="css">CSS</h2>
No início era só um modo de deixar as páginas um pouquinhos mais bonitas, hoje já é uma tecnologia que faz milagres, permitindo animações, melhores interações e até mesmo substituir alguns tipos de imagens. Para o desenvolvedor frontend é uma das áreas mais importantes rivalizando com JS, dependendo de onde você deseja se especializar. Para os que preferem mais a parte de UX/UI e design, aqui será onde você deve se aprimorar cada vez mais.
**Dica**: CSS funciona muito na base de teste e acerte, veja o que cada propriedade faz, brinque com elas até se sentir confortável. Depois disso procure códigos alheios e tente entender o funcionamento e comece a aplicar em seus próprios códigos. Não há nada de errado olhar código alheio, open-source está aí para isso mesmo.
#### Básico
- [Site do Maujor](http://www.maujor.com/)
- [Aprenda Layout com CSS](http://pt-br.learnlayout.com/)
- [CSS Cross-country - Code Scholl](https://www.codeschool.com/courses/css-cross-country)
#### CSS3
- [Css3 for web Designers - Book](http://www.abookapart.com/products/css3-for-web-designers)
- [The Guide to CSS Animation](http://www.smashingmagazine.com/2011/09/14/the-guide-to-css-animation-principles-and-examples/)
- [Transition e Animation](https://tableless.com.br/transition-e-animation/)
- [MDN: CSS Animations](https://developer.mozilla.org/pt-BR/docs/CSS/Using_CSS_animations)
#### Frameworks / Grids / Responsive
- [Utilizando o bootstrap de forma consistente](https://www.felipefialho.com/blog/2014/utilizando-o-bootstrap-de-forma-consistente/)
- [Desenvolvendo com Bootstrap 3](http://thiagonasc.com/desenvolvimento-web/desenvolvendo-com-bootstrap-3-um-framework-front-end-que-vale-a-pena)
- [Snippets para Bootstrap](http://bootsnipp.com/)
- [Foundation 5 para iniciantes - video](http://dev.rbtech.info/zurb-foundation-5-iniciantes-aula-1/)
- [Jeet](http://jeet.gs/) - aconselho fortemente
- [Skeleton](http://getskeleton.com/)
- [Responsive Design Workflow - Video](https://vimeo.com/45915667)
- [Responsive Patterns](http://bradfrost.github.io/this-is-responsive/patterns.html)
#### Pré-processadores
- [Less](http://lesscss.org/)
- [Sass](http://sass-lang.com/)
- [Stylus](http://learnboost.github.io/stylus/)
- [Por que usar pré-processadores?](https://speakerdeck.com/romulomachado/por-que-usar-pre-processadores-css)
- [Slide comparando os 3 pré-processadores](https://speakerdeck.com/willianjusten/pre-processadores-css)
#### Metodologias / Boas Práticas
- [How to structure a Sass project](http://thesassway.com/beginner/how-to-structure-a-sass-project)
- [Css Performance Organization](https://learn.shayhowe.com/advanced-html-css/performance-organization/)
- [OOCSS, SMACSS](http://www.slideshare.net/maxdesign/css-oocss-and-smacss)
- [Understanding BEM syntax](https://csswizardry.com/2013/01/mindbemding-getting-your-head-round-bem-syntax/)
- [Atomic Design](http://bradfrost.com/blog/post/atomic-web-design/)
#### Inpirações / Tutoriais
- [Codrops](http://tympanus.net/codrops/) - só ame <3
- [CSS-Tricks](http://css-tricks.com/)
- [Codepen](http://codepen.io/)
- [24 ways](http://24ways.org/topics/code/)
---
<h2 id="js">Javascript</h2>
Basicamente a única real linguagem no client side e que agora já se extende para o server side também. Essa linguagem tem crescido muito e hoje permite fazer praticamente tudo, seja na web e até fora dela. Se você quer ser considerado um desenvolvedor front end completo é bom que tenha essa linguagem como sua melhor amiga. Como um amigo diz:
> Desenvolvedor Front End que não sabe javascript é recortador de layout. - Suissa
Tome bastante cuidado ao querer tomar atalhos, como utilizar JQuery para tudo ou já tentar ir direto para Angular, que é modinha.
No início é comum utilizarmos plugins prontos para realizar ações específicas (sliders, lightbox), mas com o tempo vai se fazendo necessário criar soluções únicas e para isso que precisamos entender bem a linguagem.
A Ju Goncalves fez um [post bem legal](http://jugoncalv.es/blog/javascript/how-to-start-with-javascript) aconselhando livros e outros detalhes legais, aconselho a leitura.
O Vitor Britto também fez outro [incrível post](http://www.vitorbritto.com.br/blog/the-book-is-on-the-table/) falando sobre livros de JS.
- [Codecademy - JS](http://www.codecademy.com/pt-BR/tracks/javascript)
- [MDN - JS](https://developer.mozilla.org/en-US/Learn/JavaScript)
- [How to Learn JS Properly](http://javascriptissexy.com/how-to-learn-javascript-properly/)
---
<h2 id="git">Controle de Versão</h2>
Quantas vezes você já se pegou fazendo 1000 backups só para não perder certas versões dos arquivos? E se isso pudesse ser feito de uma forma mais fácil e ainda permitisse muito mais? Para isso temos ferramentas de controle de versão, sendo o [Git](http://git-scm.com/) e o [SVN](https://tortoisesvn.net/) os mais famosos. Se você quiser brincar com o [github](http://github.com), o git será a pedida.
A maioria das empresas utiliza um desses dois para poder organizar melhor seu código, além de poder versionar, o git permite um controle dos colaboradores, controle de flow, separação em branches e muito mais.
#### Básico
- [Meu curso de Git e Github para iniciantes](https://www.udemy.com/git-e-github-para-iniciantes/)
- [Try Git - Code School](https://try.github.io/levels/1/challenges/1)
- [Guia prático](http://rogerdudler.github.io/git-guide/index.pt_BR.html)
- [Introdução ao git e github - Vídeo](https://www.youtube.com/watch?v=yNwh0S0S0bU)
- [SVN Conceitos, boas práticas e dicas de utilização](http://intentor.com.br/svn-conceitos-boas-praticas-dicas-de-utilizacao/)
#### Intermediário/Avançado
- [A web-focused git workflow](http://joemaller.com/990/a-web-focused-git-workflow/)
- [Deploy web applications easily with svn](http://taylorjasko.com/deploy-web-applications-easily-with-svn/)
---
<h2 id="seo">SEO</h2>
Search Engine Optimization ou SEO é um conjunto de estratégias e métodos para melhorar o posicionamento de páginas da internet nos mecanismos de buscas, como o Google e Bing.
E qual a importância disso? Estar bem posicionado nos mecanismos de busca lhe permite ganhar mais acessos e com isso divulgar mais o seu produto.
Nem todo desenvolvedor Front End precisa ser o mestre de tudo em SEO, podemos deixar isso para especialistas, mas algumas informações básicas é importante também.
- [Agência Mestre - MestreSEO](https://www.agenciamestre.com/)
- [Como melhorar meu SEO?](https://willianjusten.com.br/como-melhorar-meu-seo/)
- [Dicas de SEO para Front-end](https://tableless.com.br/dicas-de-seo-para-front-end/)
---
<h2 id="perf">Performance</h2>
Como disse no início do artigo, uma das responsabilidades do desenvolvedor front end é cuidar da performance da aplicação, visto que 80% do carregamento está envolvido diretamente com o client side. Sendo assim, se você quiser se destacar entre os desenvolvedores, foque bastante em performance, os resultados são muito satisfatórios e recompensadores.
O [Davidson Fellipe](https://twitter.com/davidsonFellipe) fez uma awesome só disso e bom, ela está tão completa, mas tão completa, que basta o link dela, para você achar todo o resto. [Segue aqui esse ótimo compilado](https://github.com/davidsonfellipe/awesome-wpo).
---
<h2 id="task">Automação de Tarefas</h2>
Durante o percurso de frontend, principalmente na parte de performance você irá ver que muitas tarefas se tornam bastante repetitivas, como compilar o css, minificar javascript e etc. Para facilitar essas tarefas, temos essas ferramentas de automação. Existem várias, mas dentre as puramente Javascript e que se tem mais utilizado na área de Front End, temos o [Grunt](https://gruntjs.com/) e o [Gulp](http://gulpjs.com/).
- [State of Grunt](https://cowboy.github.io/state-of-grunt-fe-summit-2014-talk)
- [Gulp - The vision, history and future of the project](https://medium.com/@contrahacks/gulp-3828e8126466)
- [Grunt vs Gulp - Beyond Numbers](https://jaysoo.ca/2014/01/27/gruntjs-vs-gulpjs/)
- [Building with Gulp](https://www.smashingmagazine.com/2014/06/11/building-with-gulp/)
- [Slides of Gulp](https://slides.com/contra/gulp)
- [Gulp, Grunt, Whatever](https://ponyfoo.com/articles/gulp-grunt-whatever)
- [Gulp: O novo automatizador](https://tableless.com.br/gulp-o-novo-automatizador/)
- [Bye bye Grunt.js, hello Gulp.js!](https://blog.caelum.com.br/bye-bye-grunt-js-hello-gulp-js/)
---
<h2 id="update">Mantenha-se Atualizado</h2>
Como já deve ter visto, a área de Front End é uma das que mais se movimenta. Do dia para a noite podem nascer 20 ferramentas novas para você conhecer e aprender. Para você não perder nada de novo que está acontecendo, aconselho muito a seguir as pessoas certas, assinar weeklys e seguir blogs da área. Vou colocar aqui só alguns, porque só dessa parte temos muita coisa!
#### Pessoas para seguir
- [Addy Osmani](https://twitter.com/addyosmani)
- [Ben Alman](https://twitter.com/cowboy)
- [Brad Frost](https://twitter.com/brad_frost)
- [Chris Coyer](https://twitter.com/chriscoyier)
- [John Resig](https://twitter.com/jeresig)
- [Sara Soueidan](https://twitter.com/SaraSoueidan)
#### Weeklys
- [Web Design Weekly](http://web-design-weekly.com/)
- [Frontend Focus](https://frontendfoc.us/)
- [Css Weekly](http://css-weekly.com/)
- [Javascript Weekly](http://javascriptweekly.com/)
#### Blogs
- [Codrops](http://tympanus.net/codrops/)
- [EchoJS](http://www.echojs.com/)
- [Google’s Web Fundamentals Program](https://developers.google.com/web)
- [Css-tricks](http://css-tricks.com/)
- [Smashing Magazine](http://www.smashingmagazine.com/)
- [Da2k Blog](http://blog.da2k.com.br/) - PtBr
- [Leandro Oriente Blog](http://leandrooriente.com/) - PtBr
- [Felipe Fialho Blog](https://www.felipefialho.com/blog/) - PtBr
#### Eventos
Nada melhor que um bom networking para te ajudar a conhecer mais coisas. E nada melhor que os eventos para isso, além de palestras ótimas, sempre acaba conhecendo alguém para te ajudar no futuro.
Falando nisso, vai rolar o GDG DevFest em BH, se quiser que eu vá, [vote aqui](http://call4paperz.com/events/gdg-devfest-extended-bh-2015--2)
---
<h2 id="dicas">Dicas</h2>
Para quem está começando é sempre um pouquinho complicado saber por onde começar, como fazer e o que fazer. Aqui vão algumas dicas que o [Vitor Britto](http://vitorbritto.com.br/) deu uma vez na Timeline dele e que eu concordo 110%.
- Não adianta querer saber tudo em um curto espaço de tempo. Mas saiba que você pode aprender muito com o passar do tempo e se estiver disposto a aprender.
- Vai com calma, estude no seu tempo, aprecie um tempo de estudo, mas também seu lazer. O mundo não vai acabar se você não conseguir estudar tudo que quer.
- Se afobar para querer o aprendizado a todo custo é uma péssima ideia. Aprenda na medida do possível, respeitando o seu limite e praticando sempre que puder.
- Pegue as coisas que você gosta, separe, estude a base daquilo e faça pequenos experimentos, porque a prática leva a perfeição. E se puder, passe adiante o que aprendeu, que será ainda mais recompensado.
-Na programação: a leitura vale prata e a prática vale ouro.
---
## Conclusão
É claro que existem outros links, outras coisas para aprender e outros métodos, nossa área é bastante grande. Mas espero que isso já lhe auxilie um pouco nessa longa jornada que é se tornar um desenvolvedor front end.
Para os mais experientes, faltou alguma coisa muito importante que esqueci de falar? Explica aí embaixo nos comentários ou manda um Pull Request, críticas são sempre boas, principalmente para ajudar a quem está começando.
---
## Fontes
- [O Papel do Desenvolvedor Front End](http://pt.slideshare.net/raelmax/o-papel-do-desenvolvedor-front-end)
- [Guia Front-end das Galáxias](http://pt.slideshare.net/davidsonfellipe/guia-do-front-end-das-galaxias)
- [Como me tornar um desenvolvedor front end](http://leandrooriente.com/como-me-tornar-um-desenvolvedor-front-end/)
- [Como se tornar um dev front-end](https://tableless.com.br/tornar-dev-front-end/)
| 55.802993 | 802 | 0.763328 | por_Latn | 0.997594 |
ff9aeb30a0fee482d1f24553d075fb0cebbad068 | 1,569 | md | Markdown | results/innerfidelity/sbaf-serious/Beats PowerBeats 2 Wireless/README.md | ruixiao85/AutoEq | a41d50e2bcde9609fe37848f55b019a13496ef66 | [
"MIT"
] | 1 | 2020-07-26T09:34:56.000Z | 2020-07-26T09:34:56.000Z | results/innerfidelity/sbaf-serious/Beats PowerBeats 2 Wireless/README.md | TheDarkMikeRises/AutoEq | ab0fcf2fe072665f8af1d253c14226621fadecec | [
"MIT"
] | null | null | null | results/innerfidelity/sbaf-serious/Beats PowerBeats 2 Wireless/README.md | TheDarkMikeRises/AutoEq | ab0fcf2fe072665f8af1d253c14226621fadecec | [
"MIT"
] | null | null | null | # Beats PowerBeats 2 Wireless
See [usage instructions](https://github.com/jaakkopasanen/AutoEq#usage) for more options and info.
### Parametric EQs
In case of using parametric equalizer, apply preamp of **-6.9dB** and build filters manually
with these parameters. The first 5 filters can be used independently.
When using independent subset of filters, apply preamp of **-7.0dB**.
| Type | Fc | Q | Gain |
|:--------|:---------|:-----|:--------|
| Peaking | 95 Hz | 0.44 | -1.4 dB |
| Peaking | 241 Hz | 0.57 | -3.4 dB |
| Peaking | 3517 Hz | 1.12 | 6.6 dB |
| Peaking | 8363 Hz | 4.44 | -3.2 dB |
| Peaking | 20278 Hz | 0.34 | -5.4 dB |
| Peaking | 986 Hz | 1.83 | 0.8 dB |
| Peaking | 2159 Hz | 1.18 | -1.2 dB |
| Peaking | 2662 Hz | 4.07 | 1.9 dB |
| Peaking | 13133 Hz | 2.04 | 1.5 dB |
| Peaking | 14981 Hz | 3.29 | -2.9 dB |
### Fixed Band EQs
In case of using fixed band (also called graphic) equalizer, apply preamp of **-7.3dB**
(if available) and set gains manually with these parameters.
| Type | Fc | Q | Gain |
|:--------|:---------|:-----|:--------|
| Peaking | 31 Hz | 1.41 | -0.6 dB |
| Peaking | 62 Hz | 1.41 | -1.2 dB |
| Peaking | 125 Hz | 1.41 | -2.9 dB |
| Peaking | 250 Hz | 1.41 | -3.5 dB |
| Peaking | 500 Hz | 1.41 | -1.8 dB |
| Peaking | 1000 Hz | 1.41 | 0.3 dB |
| Peaking | 2000 Hz | 1.41 | 1.0 dB |
| Peaking | 4000 Hz | 1.41 | 6.9 dB |
| Peaking | 8000 Hz | 1.41 | -1.8 dB |
| Peaking | 16000 Hz | 1.41 | -4.0 dB |
### Graphs
 | 39.225 | 98 | 0.558955 | eng_Latn | 0.737451 |
ff9af788898564904d844d370ac1d454bf26855d | 1,790 | md | Markdown | website/translated_docs/pl-PL/logger.md | asifwanii/website | ebc7460e30cd6fea69e8b7372b4164a328aa0e7a | [
"MIT"
] | null | null | null | website/translated_docs/pl-PL/logger.md | asifwanii/website | ebc7460e30cd6fea69e8b7372b4164a328aa0e7a | [
"MIT"
] | null | null | null | website/translated_docs/pl-PL/logger.md | asifwanii/website | ebc7460e30cd6fea69e8b7372b4164a328aa0e7a | [
"MIT"
] | null | null | null | ---
id: logger
title: "Rejestrator"
---
As with any web application, Verdaccio has a customisable built-in logger. You can define multiple types of outputs.
```yaml
logs:
# console output
- {type: stdout, format: pretty, level: http}
# file output
- {type: file, path: verdaccio.log, level: info}
# Rotating log stream. Opcje są przekazywane bezpośrednio do bunyana. Zobacz: https://github.com/trentm/node-bunyan#stream-type-rotating-file
- {type: rotating-file, format: json, path: /path/to/log.jsonl, level: http, options: {period: 1d}}
```
Użyj `SIGUSR2`, aby powiadomić aplikację, plik dziennika został obrócony i musi zostać ponownie otwarty. Uwaga: Rotacyjny strumień dziennika nie jest obsługiwany w trybie klastra. [Zobacz tutaj](https://github.com/trentm/node-bunyan#stream-type-rotating-file)
### Konfiguracja
| Właściwość | Typ | Wymagane | Przykład | Wsparcie | Opis |
| ---------- | ----------- | -------- | ---------------------------------------------- | --------- | ------------------------------------------------------- |
| typ | ciąg znaków | Nie | [stdout, plik] | wszystkie | zdefiniuj wyjście |
| ścieżka | ciąg znaków | Nie | verdaccio.log | wszystko | jeśli typem jest plik, zdefiniuj lokalizację tego pliku |
| format | ciąg znaków | Nie | [pretty, pretty-timestamped] | wszystko | format wyjścia |
| poziom | ciąg znaków | Nie | [fatal, error, warn, http, info, debug, trace] | wszystko | verbose level | | 66.296296 | 259 | 0.521788 | pol_Latn | 0.985087 |
ff9ba46e274c5863aaf99b6f9e598385c9e10f1f | 5,054 | md | Markdown | virtualbox-3nodes/README.md | VictCM/vagrant-lab-openstack | c4a3d66b93b0be7436c2b990bb71522fe8a1d9ae | [
"MIT"
] | null | null | null | virtualbox-3nodes/README.md | VictCM/vagrant-lab-openstack | c4a3d66b93b0be7436c2b990bb71522fe8a1d9ae | [
"MIT"
] | null | null | null | virtualbox-3nodes/README.md | VictCM/vagrant-lab-openstack | c4a3d66b93b0be7436c2b990bb71522fe8a1d9ae | [
"MIT"
] | 2 | 2018-11-14T12:12:29.000Z | 2021-01-06T12:46:55.000Z | ### Virtualbox-based 3-nodes Openstack Kolla lab
For this lab we want to run a distributed system configuration - having 3 nodes (2 controllers, one compute) deployed from a simple node running Kolla.
## physical architecture
```
┌─────────────────────────────────────────────────────────────────────────────────┐
│ Vagrant generated virtual infrastructure on a physical server │
│ ┌────────────────┐ ┌────────────────┐ ┌────────────────┐ ┌────────────────┐ │
│ │ 192.168.50.75 │ │ 192.168.50.76 │ │ 192.168.50.77 │ │ 192.168.50.78 │ │
│ ├────────────────┤ ├────────────────┤ ├────────────────┤ ├────────────────┤ │
│ │ │ │ │ │ │ │ │ │
│ │ │ │ │ │ │ │ │ │
│ │ deploy │ │ controller01 │ │ controller02 │ │ compute01 │ │
│ │ │ │ │ │ │ │ │ │
│ │ │ │ │ │ │ │ │ │
│ └─────┬──────┬───┘ └─┬──────┬──────┬┘ └─┬──────┬──────┬┘ └─┬──────┬──────┬┘ │
│ │enp0s8│ │enp0s8│enp0s9│ │enp0s8│enp0s9│ │enp0s8│enp0s9│ │
│ └───┬──┘ └──┬───┴──┬───┘ └──┬───┴──┬───┘ └──┬───┴──┬───┘ │
└──────┬────┼─────────────┼──────┼───────────┼──────┼─────────────┼──────┼───┬────┘
│ │ │ │ │ │ │ │ │
┌────────────────────────┐ │ └─────────────┴──────┴──────┬────┴──────┴─────────────┴──────┘ │
│ │ │ ┌─────┴─────┐ │
│ Router │ └──────────────────────────┤ ens18f1 ├──────────────────────────────┘
│ │ └─────┬─────┘
│ 192.168.50.253/24 │ │
│ ├───────────────────────────────────────────────┴──────────────────────────────────────────
│ │
└────────────────────────┘
```
## logical architecture
```
┌───────────────────────────┐ ┌───────────────────────────┐
│ │ │ │
│ Openstack web/API │ │ Openstack VMs │
│ │ │ │
│ 192.168.50.68/24 │ │ 192.168.50.150-170/24 │
│ │ │ ┌───────────┐ │
│ │ │ │ physnet1 │ │
└───────────┬───────────────┘ └───┴─────┬─────┴───────────┘
┌────────────────────────┐ │ │
│ │ │ │
│ Router │ │ │
│ │ │ │
│ 192.168.50.253/24 ├─────────────────────┴─────────────────────────────────┴────────────────────────────────────
│ │
│ │
└────────────────────────┘
```
## how to run
```
vagrant up
```
## how to access
The floating IP address is currently set at 192.168.50.68, with labuser/labpassword. The public network is automatically configured.
| 80.222222 | 151 | 0.122279 | eng_Latn | 0.207174 |
ff9c7574b3634864fd80504fa00120734d0d330d | 89 | md | Markdown | README.md | qinyong521/49task | 22bc2a1333e5d176466ca517409907e9966f2476 | [
"MIT"
] | 1 | 2021-03-15T13:25:07.000Z | 2021-03-15T13:25:07.000Z | README.md | qinyong521/49task | 22bc2a1333e5d176466ca517409907e9966f2476 | [
"MIT"
] | null | null | null | README.md | qinyong521/49task | 22bc2a1333e5d176466ca517409907e9966f2476 | [
"MIT"
] | null | null | null | > Due to a third-party risk dispute, this script stopped sharing
> 由于第三方风险争议，此脚本停止分享，，
| 29.666667 | 64 | 0.752809 | eng_Latn | 0.990496 |
ff9c7f24065dda854dffda722ca58d5e6965ea6d | 20,892 | md | Markdown | articles/documentdb/documentdb-nodejs-application.md | pymia/azure-docs.zh-tw | fc9f30ec1cb28578e47f3c0d52b6ada32b276b8b | [
"CC-BY-3.0"
] | null | null | null | articles/documentdb/documentdb-nodejs-application.md | pymia/azure-docs.zh-tw | fc9f30ec1cb28578e47f3c0d52b6ada32b276b8b | [
"CC-BY-3.0"
] | null | null | null | articles/documentdb/documentdb-nodejs-application.md | pymia/azure-docs.zh-tw | fc9f30ec1cb28578e47f3c0d52b6ada32b276b8b | [
"CC-BY-3.0"
] | null | null | null | ---
title: "了解 Node.js-DocumentDB Node.js 教學課程 |Microsoft Docs"
description: "了解 Node.js！ 透過教學課程探索如何使用 Microsoft Azure DocumentDB 來儲存和存取 Azure 網站上託管的 Node.js Express Web 應用程式資料。"
keywords: "應用程式開發, 資料庫教學課程, 了解 node.js, node.js 教學課程, documentdb, azure, Microsoft azure"
services: documentdb
documentationcenter: nodejs
author: syamkmsft
manager: jhubbard
editor: cgronlun
ms.assetid: 9da9e63b-e76a-434e-96dd-195ce2699ef3
ms.service: documentdb
ms.workload: data-services
ms.tgt_pltfrm: na
ms.devlang: nodejs
ms.topic: hero-article
ms.date: 12/16/2016
ms.author: syamk
translationtype: Human Translation
ms.sourcegitcommit: a5abaa698de2978e676153832d252cf2bc43e72b
ms.openlocfilehash: cfd2f49a3452e4ad5132f55d269452e436bcecc5
---
# <a name="a-nametoc395783175abuild-a-nodejs-web-application-using-documentdb"></a><a name="_Toc395783175"></a>使用 DocumentDB 建置 Node.js Web 應用程式
> [!div class="op_single_selector"]
> * [.NET](documentdb-dotnet-application.md)
> * [Node.js](documentdb-nodejs-application.md)
> * [Java](documentdb-java-application.md)
> * [Python](documentdb-python-application.md)
>
>
本 Node.js 教學課程說明如何使用 Azure DocumentDB，從 Azure 網站上託管的 Node.js Express 應用程式儲存和存取資料。 您會建置一個可供建立、擷取及完成工作的簡單網頁型工作管理應用程式 (待辦事項應用程式)。 在 Azure DocumentDB 中，這些工作會儲存為 JSON 文件。 本教學課程會逐步引導您建立和部署應用程式，並說明每個程式碼片段中的狀況。
是否沒有時間完成本教學課程，只是想要取得完整的解決方案？ 沒有問題，您可以從 [GitHub][GitHub] 取得完整的範例解決方案。 如需有關如何執行應用程式的指示，只需閱讀 [Readme](https://github.com/Azure-Samples/documentdb-node-todo-app/blob/master/README.md) 檔案即可。
## <a name="a-nametoc395783176aprerequisites"></a><a name="_Toc395783176"></a>必要條件
> [!TIP]
> 本 Node.js 教學課程假設您先前已有些許使用 Node.js 和 Azure 網站的經驗。
>
>
在依照本文中的指示進行之前，您應先確定備妥下列項目：
* 使用中的 Azure 帳戶。 如果您沒有帳戶，只需要幾分鐘的時間就可以建立免費試用帳戶。 如需詳細資訊，請參閱 [Azure 免費試用](https://azure.microsoft.com/pricing/free-trial/)。
或
本機安裝的 [Azure DocumentDB 模擬器](documentdb-nosql-local-emulator.md)。
* [Node.js][Node.js] v0.10.29 版或更高版本。
* [Express 產生器](http://www.expressjs.com/starter/generator.html) (您可以透過 `npm install express-generator -g` 進行安裝)
* [Git][Git]。
## <a name="a-nametoc395637761astep-1-create-a-documentdb-database-account"></a><a name="_Toc395637761"></a>步驟 1：建立 DocumentDB 資料庫帳戶
現在就開始建立 DocumentDB 帳戶。 如果您已經擁有帳戶，或如果您正在使用 DocumentDB 模擬器來進行本教學課程，可以跳到[步驟 2：建立新的 Node.js 應用程式](#_Toc395783178)。
[!INCLUDE [documentdb-create-dbaccount](../../includes/documentdb-create-dbaccount.md)]
[!INCLUDE [documentdb-keys](../../includes/documentdb-keys.md)]
## <a name="a-nametoc395783178astep-2-learn-to-create-a-new-nodejs-application"></a><a name="_Toc395783178"></a>步驟 2：了解如何建立新的 Node.js 應用程式
現在，我們來了解如何使用 [Express](http://expressjs.com/) 架構來建立基本的 Hello World Node.js 專案。
1. 開啟您喜好的終端機，例如 Node.js 命令提示字元。
2. 瀏覽至您想要在其中儲存新應用程式的目錄。
3. 使用 Express 產生器來產生名為 **todo**的新應用程式。
express todo
4. 開啟您的新 **todo** 目錄並安裝相依性。
cd todo
npm install
5. 執行新的應用程式。
npm start
6. 您可以檢視新的應用程式，請導覽瀏覽器至 [http://localhost:3000/](http://localhost:3000)。
然後，若要停止應用程式，請在終端機視窗中按 CTRL+C，然後按一下 **y** 以終止批次作業。
## <a name="a-nametoc395783179astep-3-install-additional-modules"></a><a name="_Toc395783179"></a>步驟 3：安裝其他模組
**package.json** 檔案是建立在專案根目錄中的其中一個檔案。 這個檔案包含 Node.js 應用程式所需的其他模組清單。 之後，當您將此應用程式部署至 Azure 網站時，此檔案可用來決定 Azure 上需要安裝哪些模組才能支援您的應用程式。 在本教學課程中，我們還需要再安裝兩個封裝。
1. 返回終端機，透過 npm 安裝 **async** 模組。
npm install async --save
2. 透過 npm 安裝 **documentdb** 模組。 這是 DocumentDB 發揮所有強大功能的模組。
npm install documentdb --save
3. 快速檢查應用程式的 **package.json** 檔案應該會顯示其他模組。 這個檔案會告訴 Azure 在執行您的應用程式時要下載及安裝的封裝。 它看起來應該類似下面的範例。
{
"name": "todo",
"version": "0.0.0",
"private": true,
"scripts": {
"start": "node ./bin/www"
},
"dependencies": {
"async": "^2.1.4",
"body-parser": "~1.15.2",
"cookie-parser": "~1.4.3",
"debug": "~2.2.0",
"documentdb": "^1.10.0",
"express": "~4.14.0",
"jade": "~1.11.0",
"morgan": "~1.7.0",
"serve-favicon": "~2.3.0"
}
}
這會讓 Node (之後則是 Azure) 知道您的應用程式需要仰賴這些額外模組。
## <a name="a-nametoc395783180astep-4-using-the-documentdb-service-in-a-node-application"></a><a name="_Toc395783180"></a>步驟 4：在節點應用程式中使用 DocumentDB 服務
前面的內容在講述所有初始設定和組態，現在讓我們來了解本教學課程的真正目的，也就是使用 Azure DocumentDB 撰寫一些程式碼。
### <a name="create-the-model"></a>建立模型
1. 在專案目錄中，請在與 package.json 檔案相同的目錄中建立名為 **models** 的新目錄。
2. 在 **models** 目錄中，建立名為 **taskDao.js** 的新檔案。 此檔案將包含應用程式所建立工作的模型。
3. 在同一個 **models** 目錄中，建立另一個名為 **docdbUtils.js** 的新檔案。 這個檔案會包含一些實用、可重複使用，適用於整個應用程式的程式碼。
4. 將下列程式碼複製到 **docdbUtils.js**
var DocumentDBClient = require('documentdb').DocumentClient;
var DocDBUtils = {
getOrCreateDatabase: function (client, databaseId, callback) {
var querySpec = {
query: 'SELECT * FROM root r WHERE r.id= @id',
parameters: [{
name: '@id',
value: databaseId
}]
};
client.queryDatabases(querySpec).toArray(function (err, results) {
if (err) {
callback(err);
} else {
if (results.length === 0) {
var databaseSpec = {
id: databaseId
};
client.createDatabase(databaseSpec, function (err, created) {
callback(null, created);
});
} else {
callback(null, results[0]);
}
}
});
},
getOrCreateCollection: function (client, databaseLink, collectionId, callback) {
var querySpec = {
query: 'SELECT * FROM root r WHERE r.id=@id',
parameters: [{
name: '@id',
value: collectionId
}]
};
client.queryCollections(databaseLink, querySpec).toArray(function (err, results) {
if (err) {
callback(err);
} else {
if (results.length === 0) {
var collectionSpec = {
id: collectionId
};
client.createCollection(databaseLink, collectionSpec, function (err, created) {
callback(null, created);
});
} else {
callback(null, results[0]);
}
}
});
}
};
module.exports = DocDBUtils;
> [!TIP]
> createCollection 會採用選擇性的 requestOptions 參數，可以用來指定集合的優惠類型。 如果未提供 requestOptions.offerType 值，則將會使用預設的優惠類型來建立集合。
>
> 如需 DocumentDB 優惠類型的詳細資訊，請參閱 [DocumentDB 中的效能層級](documentdb-performance-levels.md)
>
>
5. 儲存並關閉 **docdbUtils.js** 檔案。
6. 在 **taskDao.js** 檔案的開頭加入下列程式碼，以參考我們之前建立的 **DocumentDBClient** 和 **docdbUtils.js**：
var DocumentDBClient = require('documentdb').DocumentClient;
var docdbUtils = require('./docdbUtils');
7. 接下來，要加入程式碼以定義和匯出 Task 物件。 這會負責初始化我們的 Task 物件，並設定我們即將使用的資料庫和文件集合。
function TaskDao(documentDBClient, databaseId, collectionId) {
this.client = documentDBClient;
this.databaseId = databaseId;
this.collectionId = collectionId;
this.database = null;
this.collection = null;
}
module.exports = TaskDao;
8. 接下來，新增下列程式碼以定義 Task 物件上的其他方法，可用來與 DocumentDB 中存放的資料進行互動。
TaskDao.prototype = {
init: function (callback) {
var self = this;
docdbUtils.getOrCreateDatabase(self.client, self.databaseId, function (err, db) {
if (err) {
callback(err);
} else {
self.database = db;
docdbUtils.getOrCreateCollection(self.client, self.database._self, self.collectionId, function (err, coll) {
if (err) {
callback(err);
} else {
self.collection = coll;
}
});
}
});
},
find: function (querySpec, callback) {
var self = this;
self.client.queryDocuments(self.collection._self, querySpec).toArray(function (err, results) {
if (err) {
callback(err);
} else {
callback(null, results);
}
});
},
addItem: function (item, callback) {
var self = this;
item.date = Date.now();
item.completed = false;
self.client.createDocument(self.collection._self, item, function (err, doc) {
if (err) {
callback(err);
} else {
callback(null, doc);
}
});
},
updateItem: function (itemId, callback) {
var self = this;
self.getItem(itemId, function (err, doc) {
if (err) {
callback(err);
} else {
doc.completed = true;
self.client.replaceDocument(doc._self, doc, function (err, replaced) {
if (err) {
callback(err);
} else {
callback(null, replaced);
}
});
}
});
},
getItem: function (itemId, callback) {
var self = this;
var querySpec = {
query: 'SELECT * FROM root r WHERE r.id = @id',
parameters: [{
name: '@id',
value: itemId
}]
};
self.client.queryDocuments(self.collection._self, querySpec).toArray(function (err, results) {
if (err) {
callback(err);
} else {
callback(null, results[0]);
}
});
}
};
9. 儲存並關閉 **taskDao.js** 檔案。
### <a name="create-the-controller"></a>建立控制器
1. 在專案的 **routes** 目錄中，建立名為 **tasklist.js** 的新檔案。
2. 在 **tasklist.js**中加入以下程式碼。 這會載入供 **tasklist.js**使用的 DocumentDBClient 和 async 模組。 這也會定義 **TaskList** 函式，系統會傳遞我們稍早定義的 **Task** 物件執行個體給它：
var DocumentDBClient = require('documentdb').DocumentClient;
var async = require('async');
function TaskList(taskDao) {
this.taskDao = taskDao;
}
module.exports = TaskList;
3. 繼續在 **tasklist.js** 檔案中新增用來 **showTasks (顯示工作)、addTask (新增工作)** 和 **completeTasks (完成工作)** 的方法：
TaskList.prototype = {
showTasks: function (req, res) {
var self = this;
var querySpec = {
query: 'SELECT * FROM root r WHERE r.completed=@completed',
parameters: [{
name: '@completed',
value: false
}]
};
self.taskDao.find(querySpec, function (err, items) {
if (err) {
throw (err);
}
res.render('index', {
title: 'My ToDo List ',
tasks: items
});
});
},
addTask: function (req, res) {
var self = this;
var item = req.body;
self.taskDao.addItem(item, function (err) {
if (err) {
throw (err);
}
res.redirect('/');
});
},
completeTask: function (req, res) {
var self = this;
var completedTasks = Object.keys(req.body);
async.forEach(completedTasks, function taskIterator(completedTask, callback) {
self.taskDao.updateItem(completedTask, function (err) {
if (err) {
callback(err);
} else {
callback(null);
}
});
}, function goHome(err) {
if (err) {
throw err;
} else {
res.redirect('/');
}
});
}
};
4. 儲存並關閉 **tasklist.js** 檔案。
### <a name="add-configjs"></a>新增 config.js
1. 在您的專案目錄中，建立名為 **config.js**的新檔案。
2. 將下列程式碼新增至 **config.js**。 這會定義組態設定和我們的應用程式所需的值。
var config = {}
config.host = process.env.HOST || "[the URI value from the DocumentDB Keys blade on http://portal.azure.com]";
config.authKey = process.env.AUTH_KEY || "[the PRIMARY KEY value from the DocumentDB Keys blade on http://portal.azure.com]";
config.databaseId = "ToDoList";
config.collectionId = "Items";
module.exports = config;
3. 在 **config.js** 檔案中，使用在 [Microsoft Azure 入口網站](https://portal.azure.com)上 DocumentDB 帳戶的 [金鑰] 刀鋒視窗中的值，更新 HOST 和 AUTH_KEY 的值。
4. 儲存並關閉 **config.js** 檔案。
### <a name="modify-appjs"></a>修改 app.js
1. 在專案目錄中，開啟 **app.js** 檔案。 這是稍早建立 Express Web 應用程式時所建立的檔案。
2. 將下列程式碼新增至 **app.js**
var DocumentDBClient = require('documentdb').DocumentClient;
var config = require('./config');
var TaskList = require('./routes/tasklist');
var TaskDao = require('./models/taskDao');
3. 此程式碼會定義要使用的組態檔，並繼續讀出此檔案中的值到我們即將使用的變數。
4. 將 **app.js** 檔案中的下列兩行取代為：
app.use('/', index);
app.use('/users', users);
下列程式碼片段：
var docDbClient = new DocumentDBClient(config.host, {
masterKey: config.authKey
});
var taskDao = new TaskDao(docDbClient, config.databaseId, config.collectionId);
var taskList = new TaskList(taskDao);
taskDao.init();
app.get('/', taskList.showTasks.bind(taskList));
app.post('/addtask', taskList.addTask.bind(taskList));
app.post('/completetask', taskList.completeTask.bind(taskList));
app.set('view engine', 'jade');
5. 這幾行會定義 **TaskDao** 物件的新執行個體，內含與 DocumentDB 的新連線 (使用從 **config.js** 中讀取的值)，初始化工作物件，然後將表單動作繫結至 **TaskList** 控制站上的方法。
6. 最後，儲存並關閉 **app.js** 檔案，我們就差不多快完成了。
## <a name="a-nametoc395783181astep-5-build-a-user-interface"></a><a name="_Toc395783181"></a>步驟 5：建置使用者介面
現在，讓我們將注意力轉到建置使用者介面，以便使用者可以實際與我們的應用程式互動。 我們建立的 Express 應用程式使用 **Jade** 做為檢視引擎。 如需 Jade 的詳細資訊，請參閱 [http://jade-lang.com/](http://jade-lang.com/)。
1. **views** 目錄中的 **layout.jade** 檔是用來作為其他 **.jade** 檔案的全域範本。 在此步驟中，您將修改它以使用 [Twitter Bootstrap](https://github.com/twbs/bootstrap)，這個工具組能夠方便設計美觀的網站。
2. 開啟在 **views** 資料夾中找到的 **layout.jade** 檔案，並將其中的內容取代為下列內容：
doctype html
html
head
title= title
link(rel='stylesheet', href='//ajax.aspnetcdn.com/ajax/bootstrap/3.3.2/css/bootstrap.min.css')
link(rel='stylesheet', href='/stylesheets/style.css')
body
nav.navbar.navbar-inverse.navbar-fixed-top
div.navbar-header
a.navbar-brand(href='#') My Tasks
block content
script(src='//ajax.aspnetcdn.com/ajax/jQuery/jquery-1.11.2.min.js')
script(src='//ajax.aspnetcdn.com/ajax/bootstrap/3.3.2/bootstrap.min.js')
這段程式碼實際上會指示 **Jade** 引擎轉譯出我們應用程式的部分 HTML，並建立稱為 **content** 的**區塊**，讓我們能在其中提供內容頁面的配置。
儲存並關閉此 **layout.jade** 檔案。
3. 現在，開啟 **index.jade** 檔案 (應用程式即將使用的檢視)，並將檔案中的內容取代為下列內容；
extends layout
block content
h1 #{title}
br
form(action="/completetask", method="post")
table.table.table-striped.table-bordered
tr
td Name
td Category
td Date
td Complete
if (typeof tasks === "undefined")
tr
td
else
each task in tasks
tr
td #{task.name}
td #{task.category}
- var date = new Date(task.date);
- var day = date.getDate();
- var month = date.getMonth() + 1;
- var year = date.getFullYear();
td #{month + "/" + day + "/" + year}
td
input(type="checkbox", name="#{task.id}", value="#{!task.completed}", checked=task.completed)
button.btn(type="submit") Update tasks
hr
form.well(action="/addtask", method="post")
label Item Name:
input(name="name", type="textbox")
label Item Category:
input(name="category", type="textbox")
br
button.btn(type="submit") Add item
這個程式碼會擴充配置，並為我們在前面的 **layout.jade** 檔案中看到的 **content** 預留位置提供內容。
在此配置中，我們建立了兩個 HTML 表單。
第一個表單包含資料的表格，以及可讓我們透過張貼到控制器的 **/completetask** 方法來更新項目的按鈕。
第二個表單包含兩個輸入欄位，以及可讓我們透過張貼到控制器的 **/addtask** 方法來建立項目的按鈕。
這應該就是要讓應用程式開始運作所需的所有程式碼。
4. 開啟 **public\stylesheets** 目錄中的 **style.css** 檔案，然後使用下列內容取代程式碼：
body {
padding: 50px;
font: 14px "Lucida Grande", Helvetica, Arial, sans-serif;
}
a {
color: #00B7FF;
}
.well label {
display: block;
}
.well input {
margin-bottom: 5px;
}
.btn {
margin-top: 5px;
border: outset 1px #C8C8C8;
}
儲存並關閉此 **style.css** 檔案。
## <a name="a-nametoc395783181astep-6-run-your-application-locally"></a><a name="_Toc395783181"></a>步驟 6：在本機執行您的應用程式
1. 若要在本機電腦上測試應用程式，請在終端機中執行 `npm start` 以啟動應用程式，然後重新整理 [http://localhost:3000](http://localhost:3000) 瀏覽器頁面。 此頁面現在看起來應該類似以下影像：
![[我的待辦事項清單] 應用程式在瀏覽器視窗中的螢幕擷取畫面](./media/documentdb-nodejs-application/image18.png)
> [!TIP]
> 如果您收到有關 layout.jade 檔案或 index.jade 檔案縮排的錯誤，請確定這兩個檔案的前兩行靠左對齊 (沒有空格)。 如果前兩行之前有空格，請將空格移除，儲存這兩個檔案，然後重新整理瀏覽器視窗。
2. 使用 [項目]、[項目名稱] 和 [類別] 欄位來輸入新工作，然後按一下 [新增項目]。 便會使用這些屬性在 DocumentDB 中建立文件。
3. 系統應該會更新此頁面，以在 [待辦事項] 清單中顯示新建立的項目。
![[待辦事項] 清單中包含一個新項目的應用程式螢幕擷取畫面](./media/documentdb-nodejs-application/image19.png)
4. 若要完成工作，您只需勾選 [已完成] 資料行中的核取方塊，然後按一下 [更新工作] 。 這會更新您已建立的文件。
5. 若要停止應用程式，請在終端機視窗中按 CTRL+C，然後按一下 **Y** 以終止批次作業。
## <a name="a-nametoc395783182astep-7-deploy-your-application-development-project-to-azure-websites"></a><a name="_Toc395783182"></a>步驟 7：將應用程式開發專案部署至 Azure 網站
1. 如果您還沒有這麼做，請為您的 Azure 網站提供一個 Git 儲存機制。 您可以在 [Azure App Service 的本機 Git 部署](../app-service-web/app-service-deploy-local-git.md) 主題中找到有關如何執行這項操作的指示。
2. 新增您的 Azure 網站做為 Git 遠端。
git remote add azure https://[email protected]:443/your-azure-website.git
3. 透過推送到遠端進行部署。
git push azure master
4. 幾秒後，Git 便會發佈 Web 應用程式並啟動瀏覽器，您可以在瀏覽器中看到您方便好用的應用程式已在 Azure 中執行！
恭喜！ 您剛剛已經使用 Azure DocumentDB 建置您的第一個Node.js Express Web 應用程式，並將它發佈至 Azure 網站。
如果您想要下載或參考本教學課程的完整參考應用程式，可以從 [GitHub][GitHub] 進行下載。
## <a name="a-nametoc395637775anext-steps"></a><a name="_Toc395637775"></a>接續步驟
* 想要執行 DocumentDB 的規模和效能測試？ 請參閱 [Azure DocumentDB 的效能和級別測試](documentdb-performance-testing.md)
* 了解如何 [監視 DocumentDB 帳戶](documentdb-monitor-accounts.md)(英文)。
* 在 [Query Playground](https://www.documentdb.com/sql/demo)中，針對範例資料集執行查詢。
* 瀏覽 [DocumentDB 文件](https://docs.microsoft.com/en-us/azure/documentdb/)。
[Node.js]: http://nodejs.org/
[Git]: http://git-scm.com/
[Github]: https://github.com/Azure-Samples/documentdb-node-todo-app
<!--HONumber=Dec16_HO3-->
| 36.717047 | 202 | 0.539202 | yue_Hant | 0.751505 |
ff9d50690c2adb01dbba420385e69541fcabb59a | 949 | md | Markdown | doc/journal/2018-08-23.md/index.md | JSTransformationBenchmarks/lively4-core | c3cf4c79c8375074243f26225481a47b05bd71b2 | [
"MIT"
] | 62 | 2015-10-19T14:16:37.000Z | 2022-02-03T18:22:54.000Z | doc/journal/2018-08-23.md/index.md | JSTransformationBenchmarks/lively4-core | c3cf4c79c8375074243f26225481a47b05bd71b2 | [
"MIT"
] | 390 | 2015-12-04T08:59:08.000Z | 2021-07-12T12:33:35.000Z | doc/journal/2018-08-23.md/index.md | JSTransformationBenchmarks/lively4-core | c3cf4c79c8375074243f26225481a47b05bd71b2 | [
"MIT"
] | 22 | 2015-10-22T14:39:35.000Z | 2021-05-02T02:04:41.000Z | ## 2018-08-23 #Poster #Documentation
## Some loose ends in Lively....
- https://lively-kernel.org/lively4/overleaf-cop18-promises/content/implementation.md
- Aysnc COP with Promises and syntax support
- Literate Programming / Active Essay Library / Env
- have a look Babylonian Programming
- Graffle Mode
- #Bug holding f...
- Drag and Drop
- (Page) Loading speed
- Caching ... caches to much
- More Meta-information...
- Container / Navbar onPaste....
- Garbage Collection / Visualization, explore object space (with #Patrick)
- Semantic Structure in File ... AST etc support for editor
- better browser sender / implementors
## A little Poster
<lively-import src="poster.html"></lively-import>
This should work too, we should use an HTML file as image.
```markdown
```
## Issues
- there seems to be caching problems when saving an "html" file in the view. The cache is not invalidated...
| 25.648649 | 108 | 0.716544 | eng_Latn | 0.804446 |
ff9e1355bd1ce83558fafdadfbfd2994baf9b4a0 | 22,851 | md | Markdown | articles/azure-functions/functions-bindings-storage-blob-trigger.md | eltociear/azure-docs.es-es | b028e68295007875c750136478a13494e2512990 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-functions/functions-bindings-storage-blob-trigger.md | eltociear/azure-docs.es-es | b028e68295007875c750136478a13494e2512990 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-functions/functions-bindings-storage-blob-trigger.md | eltociear/azure-docs.es-es | b028e68295007875c750136478a13494e2512990 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Desencadenador de Azure Blob Storage para Azure Functions
description: Aprenda a ejecutar una instancia de Azure Functions a medida que cambian los datos de Azure Blob Storage.
author: craigshoemaker
ms.topic: reference
ms.date: 02/13/2020
ms.author: cshoe
ms.openlocfilehash: 39e3521339947263161979033406fb39e397373f
ms.sourcegitcommit: 8a9c54c82ab8f922be54fb2fcfd880815f25de77
ms.translationtype: HT
ms.contentlocale: es-ES
ms.lasthandoff: 03/27/2020
ms.locfileid: "80348971"
---
# <a name="azure-blob-storage-trigger-for-azure-functions"></a>Desencadenador de Azure Blob Storage para Azure Functions
El desencadenador de Blob Storage inicia una función cuando se detecta un blob nuevo o actualizado. El contenido del blob se proporciona a modo de [entrada para la función](./functions-bindings-storage-blob-input.md).
El desencadenador de Azure Blob Storage necesita una cuenta de almacenamiento de uso general. Para usar una cuenta solo para blobs, o si la aplicación tiene necesidades especializadas, revise las alternativas al uso de este desencadenador.
Para obtener información sobre los detalles de instalación y configuración, consulte la [información general](./functions-bindings-storage-blob.md).
## <a name="alternatives"></a>Alternativas
### <a name="event-grid-trigger"></a>Desencadenador de Event Grid
El [desencadenador de Event Grid](functions-bindings-event-grid.md) también tiene compatibilidad integrada con [eventos de blob](../storage/blobs/storage-blob-event-overview.md). Utilice Event Grid en lugar del desencadenador de Blob Storage en los escenarios siguientes:
- **Cuentas de almacenamiento solo para blobs**: [Las cuentas de almacenamiento solo para blobs](../storage/common/storage-account-overview.md#types-of-storage-accounts) se admiten para enlaces de entrada y salida de blobs pero no para desencadenadores de blobs.
- **Gran escala**: Gran escala se aplica generalmente a contenedores que tienen más de 100 000 blobs en ellos o a cuentas de almacenamiento que tienen más de 100 actualizaciones de blob por segundo.
- **Minimización de latencia**: Si la aplicación de función está en un plan de consumo, puede haber un retraso de hasta 10 minutos en el procesamiento de nuevos blobs si una aplicación de función ha quedado inactiva. Para evitar esta latencia, puede cambiar a un plan de App Service con Always On habilitado. También puede usar un [desencadenador de Event Grid](functions-bindings-event-grid.md) con su cuenta de almacenamiento de blobs. Para ver un ejemplo, consulte el [tutorial de Event Grid](../event-grid/resize-images-on-storage-blob-upload-event.md?toc=%2Fazure%2Fazure-functions%2Ftoc.json).
Consulte el tutorial [Cambio de tamaño de una imagen con Event Grid](../event-grid/resize-images-on-storage-blob-upload-event.md) para ver un ejemplo de Event Grid.
### <a name="queue-storage-trigger"></a>Desencadenador de Queue Storage
Otro enfoque para el procesamiento de blobs es escribir mensajes de cola que correspondan a los blobs que se están creando o modificando y, a continuación, usar un [desencadenador de Queue Storage](./functions-bindings-storage-queue.md) para comenzar el procesamiento.
## <a name="example"></a>Ejemplo
# <a name="c"></a>[C#](#tab/csharp)
En el ejemplo siguiente se muestra una [función de C#](functions-dotnet-class-library.md) que escribe un registro cuando se agrega o se actualiza un blob en el contenedor `samples-workitems`.
```csharp
[FunctionName("BlobTriggerCSharp")]
public static void Run([BlobTrigger("samples-workitems/{name}")] Stream myBlob, string name, ILogger log)
{
log.LogInformation($"C# Blob trigger function Processed blob\n Name:{name} \n Size: {myBlob.Length} Bytes");
}
```
La cadena `{name}` en la ruta de acceso del desencadenador de blobs `samples-workitems/{name}` crea una [expresión de enlace](./functions-bindings-expressions-patterns.md) que puede usar en el código de función para acceder al nombre de archivo del blob de desencadenamiento. Para más información, consulte [Patrones de nombre de blob](#blob-name-patterns) que aparece más adelante en este artículo.
Para obtener más información sobre el atributo `BlobTrigger`, consulte [atributos y anotaciones](#attributes-and-annotations).
# <a name="c-script"></a>[Script de C#](#tab/csharp-script)
En el siguiente ejemplo se muestra un enlace de desencadenador de blob en un archivo *function.json* y el código que usa el enlace. La función escribe un registro cuando se agrega o actualiza un blob en el [contenedor](../storage/blobs/storage-blobs-introduction.md#blob-storage-resources) `samples-workitems`.
Estos son los datos de enlace del archivo *function.json*:
```json
{
"disabled": false,
"bindings": [
{
"name": "myBlob",
"type": "blobTrigger",
"direction": "in",
"path": "samples-workitems/{name}",
"connection":"MyStorageAccountAppSetting"
}
]
}
```
La cadena `{name}` en la ruta de acceso del desencadenador de blobs `samples-workitems/{name}` crea una [expresión de enlace](./functions-bindings-expressions-patterns.md) que puede usar en el código de función para acceder al nombre de archivo del blob de desencadenamiento. Para más información, consulte [Patrones de nombre de blob](#blob-name-patterns) que aparece más adelante en este artículo.
Para más información sobre las propiedades del archivo *function.json*, consulte la sección [Configuración](#configuration) donde se explican estas propiedades.
Este es el código de script de C# que se enlaza a `Stream`:
```cs
public static void Run(Stream myBlob, string name, ILogger log)
{
log.LogInformation($"C# Blob trigger function Processed blob\n Name:{name} \n Size: {myBlob.Length} Bytes");
}
```
Este es el código de script de C# que se enlaza a `CloudBlockBlob`:
```cs
#r "Microsoft.WindowsAzure.Storage"
using Microsoft.WindowsAzure.Storage.Blob;
public static void Run(CloudBlockBlob myBlob, string name, ILogger log)
{
log.LogInformation($"C# Blob trigger function Processed blob\n Name:{name}\nURI:{myBlob.StorageUri}");
}
```
# <a name="javascript"></a>[JavaScript](#tab/javascript)
En el ejemplo siguiente se muestra un enlace de desencadenador de blob en un archivo *function.json* y el [código de JavaScript](functions-reference-node.md) que usa el enlace. La función escribe un registro cuando se agrega o actualiza un blob en el contenedor `samples-workitems`.
Este es el archivo *function.json*:
```json
{
"disabled": false,
"bindings": [
{
"name": "myBlob",
"type": "blobTrigger",
"direction": "in",
"path": "samples-workitems/{name}",
"connection":"MyStorageAccountAppSetting"
}
]
}
```
La cadena `{name}` en la ruta de acceso del desencadenador de blobs `samples-workitems/{name}` crea una [expresión de enlace](./functions-bindings-expressions-patterns.md) que puede usar en el código de función para acceder al nombre de archivo del blob de desencadenamiento. Para más información, consulte [Patrones de nombre de blob](#blob-name-patterns) que aparece más adelante en este artículo.
Para más información sobre las propiedades del archivo *function.json*, consulte la sección [Configuración](#configuration) donde se explican estas propiedades.
Este es el código de JavaScript:
```javascript
module.exports = function(context) {
context.log('Node.js Blob trigger function processed', context.bindings.myBlob);
context.done();
};
```
# <a name="python"></a>[Python](#tab/python)
En el ejemplo siguiente se muestra un enlace de desencadenador de blobs en un archivo *function.json* y el [código de Python](functions-reference-python.md) que usa el enlace. La función escribe un registro cuando se agrega o actualiza un blob en el [contenedor](../storage/blobs/storage-blobs-introduction.md#blob-storage-resources) `samples-workitems`.
Este es el archivo *function.json*:
```json
{
"scriptFile": "__init__.py",
"disabled": false,
"bindings": [
{
"name": "myblob",
"type": "blobTrigger",
"direction": "in",
"path": "samples-workitems/{name}",
"connection":"MyStorageAccountAppSetting"
}
]
}
```
La cadena `{name}` en la ruta de acceso del desencadenador de blobs `samples-workitems/{name}` crea una [expresión de enlace](./functions-bindings-expressions-patterns.md) que puede usar en el código de función para acceder al nombre de archivo del blob de desencadenamiento. Para más información, consulte [Patrones de nombre de blob](#blob-name-patterns) que aparece más adelante en este artículo.
Para más información sobre las propiedades del archivo *function.json*, consulte la sección [Configuración](#configuration) donde se explican estas propiedades.
Este es el código de Python:
```python
import logging
import azure.functions as func
def main(myblob: func.InputStream):
logging.info('Python Blob trigger function processed %s', myblob.name)
```
# <a name="java"></a>[Java](#tab/java)
Esta función escribe un registro cuando se agrega o actualiza un blob en el contenedor `myblob`.
```java
@FunctionName("blobprocessor")
public void run(
@BlobTrigger(name = "file",
dataType = "binary",
path = "myblob/{name}",
connection = "MyStorageAccountAppSetting") byte[] content,
@BindingName("name") String filename,
final ExecutionContext context
) {
context.getLogger().info("Name: " + filename + " Size: " + content.length + " bytes");
}
```
---
## <a name="attributes-and-annotations"></a>Atributos y anotaciones
# <a name="c"></a>[C#](#tab/csharp)
Para [bibliotecas de clases de C#](functions-dotnet-class-library.md), utilice los siguientes atributos para configurar un desencadenador de blob:
* [BlobTriggerAttribute](https://github.com/Azure/azure-webjobs-sdk/blob/master/src/Microsoft.Azure.WebJobs.Extensions.Storage/Blobs/BlobTriggerAttribute.cs)
El constructor del atributo toma una cadena de ruta de acceso que indica al contenedor que inspeccione y, opcionalmente, un [patrón de nombre de blob](#blob-name-patterns). Este es un ejemplo:
```csharp
[FunctionName("ResizeImage")]
public static void Run(
[BlobTrigger("sample-images/{name}")] Stream image,
[Blob("sample-images-md/{name}", FileAccess.Write)] Stream imageSmall)
{
....
}
```
Puede establecer la propiedad `Connection` para especificar la cuenta de almacenamiento que se usará, tal como se muestra en el ejemplo siguiente:
```csharp
[FunctionName("ResizeImage")]
public static void Run(
[BlobTrigger("sample-images/{name}", Connection = "StorageConnectionAppSetting")] Stream image,
[Blob("sample-images-md/{name}", FileAccess.Write)] Stream imageSmall)
{
....
}
```
Para obtener un ejemplo completo, vea el [ejemplo de desencadenador](#example).
* [StorageAccountAttribute](https://github.com/Azure/azure-webjobs-sdk/blob/master/src/Microsoft.Azure.WebJobs/StorageAccountAttribute.cs)
Proporciona otra manera de especificar la cuenta de almacenamiento que se debe usar. El constructor toma el nombre de una configuración de aplicación que contiene una cadena de conexión de almacenamiento. El atributo se puede aplicar en el nivel de clase, método o parámetro. En el ejemplo siguiente se muestran el nivel de clase y de método:
```csharp
[StorageAccount("ClassLevelStorageAppSetting")]
public static class AzureFunctions
{
[FunctionName("BlobTrigger")]
[StorageAccount("FunctionLevelStorageAppSetting")]
public static void Run( //...
{
....
}
```
La cuenta de almacenamiento que se debe usar se determina en el orden siguiente:
* La propiedad `Connection` del atributo `BlobTrigger`.
* El atributo `StorageAccount` aplicado al mismo parámetro que el atributo `BlobTrigger`.
* El atributo `StorageAccount` aplicado a la función.
* El atributo `StorageAccount` aplicado a la clase.
* La cuenta de almacenamiento predeterminada de la aplicación de función (configuración de aplicación "AzureWebJobsStorage").
# <a name="c-script"></a>[Script de C#](#tab/csharp-script)
El script de C# no admite atributos.
# <a name="javascript"></a>[JavaScript](#tab/javascript)
JavaScript no admite atributos.
# <a name="python"></a>[Python](#tab/python)
Python no admite atributos.
# <a name="java"></a>[Java](#tab/java)
El atributo `@BlobTrigger` se usa para facilitar el acceso al blob que desencadenó la función. Vea el [ejemplo de desencadenador](#example) para más información.
---
## <a name="configuration"></a>Configuración
En la siguiente tabla se explican las propiedades de configuración de enlace que se definen en el archivo *function.json* y el atributo `BlobTrigger`.
|Propiedad de function.json | Propiedad de atributo |Descripción|
|---------|---------|----------------------|
|**type** | N/D | Se debe establecer en `blobTrigger`. Esta propiedad se establece automáticamente cuando se crea el desencadenador en Azure Portal.|
|**direction** | N/D | Se debe establecer en `in`. Esta propiedad se establece automáticamente cuando se crea el desencadenador en Azure Portal. Las excepciones se indican en la sección [uso](#usage). |
|**name** | N/D | Nombre de la variable que representa el blob en el código de la función. |
|**path** | **BlobPath** |El [contenedor](../storage/blobs/storage-blobs-introduction.md#blob-storage-resources) que se va a supervisar. Puede ser un [patrón de nombre de blob](#blob-name-patterns). |
|**connection** | **Connection** | El nombre de una configuración de aplicación que contiene la cadena de conexión de almacenamiento que se usará para este enlace. Si el nombre de la configuración de aplicación comienza con "AzureWebJobs", puede especificar solo el resto del nombre aquí. Por ejemplo, si establece `connection` en "MyStorage", el entorno en tiempo de ejecución de Functions busca una configuración de aplicación denominada "AzureWebJobsMyStorage". Si deja `connection` vacía, el entorno en tiempo de ejecución de Functions usa la cadena de conexión de almacenamiento predeterminada en la configuración de aplicación que se denomina `AzureWebJobsStorage`.<br><br>La cadena de conexión debe ser para una cuenta de almacenamiento de uso general, no una [cuenta de Blob Storage](../storage/common/storage-account-overview.md#types-of-storage-accounts).|
[!INCLUDE [app settings to local.settings.json](../../includes/functions-app-settings-local.md)]
## <a name="usage"></a>Uso
# <a name="c"></a>[C#](#tab/csharp)
[!INCLUDE [functions-bindings-blob-storage-trigger](../../includes/functions-bindings-blob-storage-trigger.md)]
# <a name="c-script"></a>[Script de C#](#tab/csharp-script)
[!INCLUDE [functions-bindings-blob-storage-trigger](../../includes/functions-bindings-blob-storage-trigger.md)]
# <a name="javascript"></a>[JavaScript](#tab/javascript)
Acceda a los datos de BLOB mediante `context.bindings.<NAME>` donde `<NAME>` coincide con el valor definido en *function.json*.
# <a name="python"></a>[Python](#tab/python)
Acceda a los datos de blob a través del parámetro con el tipo [InputStream](https://docs.microsoft.com/python/api/azure-functions/azure.functions.inputstream?view=azure-python). Vea el [ejemplo de desencadenador](#example) para más información.
# <a name="java"></a>[Java](#tab/java)
El atributo `@BlobTrigger` se usa para facilitar el acceso al blob que desencadenó la función. Vea el [ejemplo de desencadenador](#example) para más información.
---
## <a name="blob-name-patterns"></a>Patrones de nombre de blobs
Puede especificar un patrón de nombre de blob en la propiedad `path` en *function.json* o en el constructor de atributos `BlobTrigger`. El patrón de nombre puede ser una [expresión de filtro o enlace](./functions-bindings-expressions-patterns.md). En las siguientes secciones se proporcionan ejemplos.
### <a name="get-file-name-and-extension"></a>Obtener el nombre y la extensión de archivo
En el ejemplo siguiente se muestra cómo enlazar a nombre de archivo del blob y la extensión por separado:
```json
"path": "input/{blobname}.{blobextension}",
```
Si el blob se denomina *original-Blob1.txt*, los valores de las variables `blobname` y `blobextension` del código de la función son *original-Blob1* y *txt*.
### <a name="filter-on-blob-name"></a>Filtrar por nombre de blob
El ejemplo siguiente se desencadena solo en blobs del contenedor `input` que comienzan con la cadena "original-":
```json
"path": "input/original-{name}",
```
Si el nombre de blob es *original Blob1.txt*, el valor de la variable `name` en el código de la función es `Blob1`.
### <a name="filter-on-file-type"></a>Filtrar por tipo de archivo
El siguiente ejemplo se desencadena solo en archivos *.png*:
```json
"path": "samples/{name}.png",
```
### <a name="filter-on-curly-braces-in-file-names"></a>Filtrar por llaves en nombres de archivo
Para buscar llaves en nombres de archivo, escape las llaves mediante dos llaves. En el ejemplo siguiente se filtran blobs que tienen llaves en el nombre:
```json
"path": "images/{{20140101}}-{name}",
```
Si el blob se denomina *{20140101}-soundfile.mp3*, el valor de variable `name` en el código de la función es *soundfile.mp3*.
## <a name="metadata"></a>Metadatos
# <a name="c"></a>[C#](#tab/csharp)
[!INCLUDE [functions-bindings-blob-storage-trigger](../../includes/functions-bindings-blob-storage-metadata.md)]
# <a name="c-script"></a>[Script de C#](#tab/csharp-script)
[!INCLUDE [functions-bindings-blob-storage-trigger](../../includes/functions-bindings-blob-storage-metadata.md)]
# <a name="javascript"></a>[JavaScript](#tab/javascript)
```javascript
module.exports = function (context, myBlob) {
context.log("Full blob path:", context.bindingData.blobTrigger);
context.done();
};
```
# <a name="python"></a>[Python](#tab/python)
En Python no hay metadatos disponibles.
# <a name="java"></a>[Java](#tab/java)
En Java no hay metadatos disponibles.
---
## <a name="blob-receipts"></a>Recepciones de blobs
El entorno en tiempo de ejecución de Azure Functions garantiza que no se llame más de una vez a ninguna función de desencadenador de blobs para un mismo blob, ya sea nuevo o actualizado. Mantiene *recepciones de blobs* para determinar si se ha procesado una determinada versión de blob.
Azure Functions almacena confirmaciones de blobs en un contenedor llamado *azure-webjobs-hosts* en la cuenta de almacenamiento de Azure de la aplicación de función (que se especifica mediante la configuración de la aplicación `AzureWebJobsStorage`). Una recepción de blobs tiene la información siguiente:
* La función desencadenada (" *<nombre de aplicación de función>* .Functions. *<nombre de función>* ", por ejemplo: "MyFunctionApp.Functions.CopyBlob")
* El nombre del contenedor
* El tipo de blob ("BlockBlob" o "PageBlob")
* El nombre del blob
* ETag (un identificador de la versión del blob, por ejemplo: "0x8D1DC6E70A277EF")
Si desea forzar el reprocesamiento de un blob, puede eliminar manualmente la recepción de ese blob desde el contenedor *azure-webjobs-hosts* . Al volver a procesar podría no producirse inmediatamente, pero se garantiza que se producirá más adelante en un momento dado.
## <a name="poison-blobs"></a>Blobs dudosos
Si se produce un error en una función de desencadenador de blob, Azure Functions vuelve a intentar ejecutar esa función hasta 5 veces de forma predeterminada.
Si se produce un error en los 5 intentos, Azure Functions agregará un mensaje a una cola de Storage llamada *webjobs-blobtrigger-poison*. Es posible configurar el número máximo de reintentos. Se usa la misma configuración de MaxDequeueCount para controlar los blobs dudosos y los mensajes de cola dudosos. El mensaje de cola para los blobs dudosos es un objeto JSON que contiene las siguientes propiedades:
* FunctionId (con el formato *<nombre de aplicación de función>* .Functions. *<nombre de función>* )
* BlobType ("BlockBlob" o "PageBlob")
* ContainerName
* BlobName
* ETag (un identificador de la versión del blob, por ejemplo: "0x8D1DC6E70A277EF")
## <a name="concurrency-and-memory-usage"></a>Simultaneidad y uso de memoria
El desencadenador de blob utiliza una cola internamente, por lo que el número máximo de invocaciones de funciones simultáneas lo controla la [configuración de colas en host.json](functions-host-json.md#queues). La configuración predeterminada limita la simultaneidad a 24 invocaciones. Este límite se aplica por separado a cada función que usa un desencadenador de blob.
[El plan de consumo](functions-scale.md#how-the-consumption-and-premium-plans-work) limita una aplicación de función de una máquina virtual (VM) a 1,5 GB de memoria. Tanto las instancias de función que se ejecutan de forma simultánea como el entorno de ejecución de Functions utilizan la memoria. Si una función desencadenada por un blob carga el blob entero a la memoria, la memoria máxima utilizada por esa función solo para blobs tiene un tamaño máximo de blob de 24 *. Por ejemplo, una aplicación de función con tres funciones desencadenadas por un blob y la configuración predeterminada tendrían una simultaneidad máxima por máquina virtual de 3*24 = 72 invocaciones de función.
Las funciones de JavaScript y Java cargan el blob entero a la memoria, mientras que las funciones de C# lo hacen si establece un enlace a `string`, `Byte[]` o POCO.
## <a name="polling"></a>Sondeo
El sondeo funciona como un híbrido entre la inspección de registros y la ejecución de exámenes periódicos de contenedores. Los blobs se examinan en grupos de 10 000 a la vez con un token de continuación que se usa entre intervalos.
> [!WARNING]
> Además, [se crean registros de almacenamiento basados en el principio del "mejor esfuerzo"](/rest/api/storageservices/About-Storage-Analytics-Logging). No hay ninguna garantía de que se capturen todos los eventos. En algunos casos, podrían faltar registros.
>
> Si necesita un procesamiento de blobs más rápido o confiable, considere crear un [mensaje de cola](../storage/queues/storage-dotnet-how-to-use-queues.md) al crear el blob. A continuación, use un [desencadenador de cola](functions-bindings-storage-queue.md), en lugar de un desencadenador de blob, para procesar el blob. Otra opción consiste en usar Event Grid; consulte el tutorial [Automatizar el cambio de tamaño de imágenes cargadas mediante Event Grid](../event-grid/resize-images-on-storage-blob-upload-event.md).
>
## <a name="next-steps"></a>Pasos siguientes
- [Lectura de datos de almacenamiento de blobs cuando se ejecuta una función](./functions-bindings-storage-blob-input.md)
- [Escritura de datos de Blob Storage desde una función](./functions-bindings-storage-blob-output.md)
| 53.14186 | 866 | 0.748676 | spa_Latn | 0.950699 |
ff9e515a2c6c1dfd47e4eeae46120e893174633e | 7,902 | md | Markdown | Notes/Docker and Containers.md | hannahchan/QuickStarts | 2af3f0f81c84a0b88518876fd31c3ab7e0d9540e | [
"MIT"
] | null | null | null | Notes/Docker and Containers.md | hannahchan/QuickStarts | 2af3f0f81c84a0b88518876fd31c3ab7e0d9540e | [
"MIT"
] | null | null | null | Notes/Docker and Containers.md | hannahchan/QuickStarts | 2af3f0f81c84a0b88518876fd31c3ab7e0d9540e | [
"MIT"
] | null | null | null | # Docker and Containers
Containers are a way to package software in a format that can run isolated on a shared operating system. Unlike Virtual Machines (VMs), containers do not bundle a full operating system - only the libraries and settings required to make the software work are needed. This makes for efficient, lightweight, self-contained systems and guarantees that software will always run the same, regardless of where it’s deployed.
Docker is a software platform for running containers.
## Get Docker
Docker can be installed on operating system platforms such as Linux, Mac and Windows. To download Docker and get installation instructions for your platform, head over to <https://www.docker.com/get-started>.
## Docker Hosts and Engines
A Docker host is an instance with an operating system such Linux, Mac or Windows that has the Docker engine installed. The Docker engine is typically referred to as just Docker.
The Docker engine is a client-server application made up of the Docker daemon, a REST API that specifies interfaces for interacting with the daemon, and a command line interface (CLI) client that talks to the daemon (through the REST API wrapper).
To check what version of Docker you have installed, run the command;
docker version
To get system-wide information about your Docker host, run;
docker info
## Docker Command Line (CLI) Reference
All Docker client commands start with docker. For a complete command line reference check out, <https://docs.docker.com/engine/reference/commandline/docker/>.
## Docker Images
Docker images are stored on your Docker Host and if they're not, Docker will attempt to pull these images from a container registry such as Docker Hub, the default container registry. You can also build your own images from a `Dockerfile`. For more information about building images, check out <https://docs.docker.com/engine/reference/builder/>.
| Command | Description |
| :----------------- | :------------------------------------------------------------ |
| docker image ls | Lists images on the Docker host. |
| docker image pull | Pulls an image from a container registry to the Docker host. |
| docker image push | Pushes an image from the Docker host to a container registry. |
| docker image rm | Removes an image from the Docker host. |
| docker image tag | Tags an image. |
| docker image build | Builds an image from a `Dockerfile`. |
### Examples
Downloads the `hello-world` image from the container registry to the Docker host.
docker image pull hello-world
Downloads the `ubuntu` image tagged `20.04` from the container registry to the Docker host.
docker image pull ubuntu:20.04
Deletes the `ubuntu` image tagged `20.04` from the Docker host.
docker image rm ubuntu:20.04
Deletes all images on the Docker host.
docker image rm $(docker image ls -q)
## Docker Containers
Docker containers are instantiated from Docker images.
To detach from a running container (must have been started with the `-it` flag), press `Ctrl` + `P` + `Q`. To reattach to the running container, use the command docker container attach.
| Command | Description |
| :--------------------- | :------------------------------------------------------------------ |
| docker container run | Starts a new container. |
| docker container ls | Lists running containers. Add the `-a` flag to show all containers. |
| docker container exec | Runs a command in a running container. |
| docker container start | Starts a stopped container. |
| docker container stop | Stops a running container. |
| docker container rm | Removes a container. |
### Examples
Launches a new container using the `hello-world` image.
docker container run hello-world
Launches a new interactive container called `mycontainer` from the `ubuntu` image tagged `20.04` and passes it the command `/bin/bash`.
docker container run -it --name mycontainer ubuntu:20.04 /bin/bash
Launches a new detached container called `web` and maps port `80` on the host to port `80` on the container using the image `httpd`.
docker container run -d --name web -p 80:80 httpd
Stops all containers on the Docker host.
docker container stop $(docker container ls -aq)
Deletes all containers on the Docker host.
docker container rm $(docker container ls -aq)
## Docker Services
On a Docker swarm, containers can be orchestrated across a swarm when deployed as a service. They allow us to do things like scale an application and reconcile actual state with desired state for container deployments across a swarm. For more information about Docker services, checkout out <https://docs.docker.com/engine/swarm/how-swarm-mode-works/services/>.
| Command | Description |
| :---------------------- | :-------------------------------------------- |
| docker service create | Creates a new service. |
| docker service ls | Lists services. |
| docker service ps | Lists tasks in a service. |
| docker service rm | Removes one or more services. |
| docker service update | Updates a service. |
| docker service rollback | Reverts changes to a service's configuration. |
| docker service scale | Scales one or more replicated services. |
### Examples
Creates a service named `myservice` with `1` running task using the latest `alpine` image running the command `ping docker.com`.
docker service create --replicas 1 --name myservice alpine ping docker.com
Lists the tasks running in the service `myservice`.
docker service ps myservice
Scales the service `myservice` to `2` running tasks.
docker service scale myservice=2
Deletes all services in a swarm.
docker service rm $(docker service ls -q)
## Docker Stacks
Stacks essentially define applications that consists of multiple Docker services. Stacks are deployed from a Docker Compose YAML file. For more information Docker Compose YAML files, check out <https://docs.docker.com/compose/overview/>.
| Command | Description |
| :-------------------- | :---------------------------------------------- |
| docker stack deploy | Deploys a new stack or updates an existing one. |
| docker stack ls | Lists stacks. |
| docker stack ps | Lists tasks in a stack. |
| docker stack rm | Removes one or more stacks. |
| docker stack services | Lists services in a stack. |
## Recommended Pluralsight Courses
1. Docker and Containers: The Big Picture by Nigel Poulton
- <https://app.pluralsight.com/library/courses/docker-containers-big-picture/>
2. Docker and Kubernetes: The Big Picture by Nigel Poulton
- <https://app.pluralsight.com/library/courses/docker-kubernetes-big-picture/>
3. Getting Started with Docker by Nigel Poulton
- <https://app.pluralsight.com/library/courses/docker-getting-started/>
4. Docker Deep Dive by Nigel Poulton
- <https://app.pluralsight.com/library/courses/docker-deep-dive-update/>
5. Docker Networking by Nigel Poulton
- <https://app.pluralsight.com/library/courses/docker-networking/>
## References
- What is a Container?
- <https://www.docker.com/resources/what-container>
| 47.035714 | 417 | 0.645406 | eng_Latn | 0.967693 |
ff9ea03ce152ef574e4d39fb0bb54c45ad81cd15 | 2,057 | md | Markdown | CHANGELOG.md | milcert/Outlook-Spam-Add-In | 8fdbfc0a88126bd77a32d8b5f9ce887fc97d438e | [
"MIT"
] | 8 | 2019-07-11T11:23:54.000Z | 2022-03-20T20:23:52.000Z | CHANGELOG.md | milcert/Outlook-Spam-Add-In | 8fdbfc0a88126bd77a32d8b5f9ce887fc97d438e | [
"MIT"
] | null | null | null | CHANGELOG.md | milcert/Outlook-Spam-Add-In | 8fdbfc0a88126bd77a32d8b5f9ce887fc97d438e | [
"MIT"
] | 4 | 2019-07-11T11:24:00.000Z | 2020-01-05T11:34:31.000Z | # Changelog
+ New feature
- Bug fix
? Misc
## 10.05.2019 - v1.2.1.0
+ Ability to forward internal mails even if restricted
+ Updated to .NET framework 4.7.2
- GetCustomUI error message when Office id not found
- Exception handling for event log write entries
- Typos and translations
## 01.07.2018 - v1.2.0.0
+ Changed from RibbonDesigner to XML Ribbon
+ SpeedUp the starting speed due to the design change
+ Changed the priority to high for spams containing 1-2 links
+ Add a contextual menu to report one or more items
+ High priority when no list unsubscribe with a .ch or .li domain
- FilterInternalMessages when your Digital ID cannot be found
## 26.09.2017 - v1.1.2.0
+ Windows 10 x64 compatible
+ Report email will be sent without read or delivery receipe
+ Compiled with Option Strict to enforce strict data typing
+ Better saved Spam path handling with IO.Path.Combine
+ Mailing list unsubscribe options is now extracted from headers
+ Better error message when an exception occurs
+ Avoid spam forward when recipients count >100
+ Avoid internal messages forwarding per default
+ To, Cc, and filter internal messages are configurable in registry
+ A copy of the reported email is not saved upon being sent
- A few translation corrections in German and Italian
- Exception can occurs with an empty body, fixed
? For Office2013 and later, should be added in the HKCU DoNotDisableAddinList
## 03.03.2017 - v1.1.1.0
+ Forward to Spam Team only mails with an empty spam score, or score < 5
? Spam score regex catcher modified
+ End of beta, starting public release (25.04.17-27.04.17)
## 15.02.2017 - v1.1.0.0
+ Title shortened, priority and spam score are added to it
+ Better link handling in email (http|https|www)
+ Extensions added in attachment file blacklist (.pdf, .zip, ...)
+ Display attachment extension and filename in email report body
- Fix error message whe opening for the first time (thx to R. G.)
- Fix report email priority when signed
## 01.11.2016 - v1.0.0.0
+ Initial beta release | 36.087719 | 78 | 0.746719 | eng_Latn | 0.994913 |
ff9ea541571257bb1cde90c8bb44f6e01079829f | 40 | md | Markdown | _tags/database.md | mingportal0/mingportal0.github.io | 3319b3f072e92b44d444526f04c391a86afa193d | [
"MIT"
] | 1 | 2021-03-17T09:14:21.000Z | 2021-03-17T09:14:21.000Z | _tags/database.md | mingportal0/mingportal0.github.io | 3319b3f072e92b44d444526f04c391a86afa193d | [
"MIT"
] | 1 | 2021-08-07T09:49:49.000Z | 2021-08-08T12:21:19.000Z | _tags/database.md | mingportal0/mingportal0.github.io | 3319b3f072e92b44d444526f04c391a86afa193d | [
"MIT"
] | null | null | null | ---
title: database
name: database
---
| 6.666667 | 15 | 0.625 | eng_Latn | 0.601917 |
ff9eb8eceffe6d10b27078d680dfd061b3034811 | 300 | md | Markdown | examples/file_transfer/README.md | GeniusDai/kingpin | 1a5d23503fb0a0c946b28e0c0b33f1383ca8a668 | [
"Apache-2.0"
] | 12 | 2021-11-24T07:09:35.000Z | 2022-03-12T16:00:36.000Z | examples/file_transfer/README.md | GeniusDai/kingpin | 1a5d23503fb0a0c946b28e0c0b33f1383ca8a668 | [
"Apache-2.0"
] | null | null | null | examples/file_transfer/README.md | GeniusDai/kingpin | 1a5d23503fb0a0c946b28e0c0b33f1383ca8a668 | [
"Apache-2.0"
] | 2 | 2021-12-05T14:03:17.000Z | 2022-01-26T11:59:07.000Z | # File Transfer
About
-----
The file transfer server will load the disk file to RAM, so DONOT transfer file with too big a size!
How to Start
------------
$ touch /tmp/file.test && echo -e "hello\nkingpin" >> /tmp/file.test
$ ./FileClient
$ md5sum /tmp/file.test /tmp/file.test.copy
| 20 | 100 | 0.643333 | eng_Latn | 0.528764 |
ffa09e7ed7ff28e48d0ab77ab32a908b4ac33255 | 330 | md | Markdown | dist/api/docs/services.varint.type.md | hidglobal/digitalpersona-services | d894aa2dd7a11557e1fec167c7534a3e8e5189c3 | [
"MIT"
] | null | null | null | dist/api/docs/services.varint.type.md | hidglobal/digitalpersona-services | d894aa2dd7a11557e1fec167c7534a3e8e5189c3 | [
"MIT"
] | 1 | 2022-03-02T04:39:57.000Z | 2022-03-02T04:39:57.000Z | dist/api/docs/services.varint.type.md | hidglobal/digitalpersona-services | d894aa2dd7a11557e1fec167c7534a3e8e5189c3 | [
"MIT"
] | 2 | 2019-07-26T07:19:24.000Z | 2021-05-05T02:37:22.000Z | <!-- Do not edit this file. It is automatically generated by API Documenter. -->
[Home](./index.md) > [@digitalpersona/services](./services.md) > [VarInt](./services.varint.md) > [type](./services.varint.type.md)
## VarInt.type property
<b>Signature:</b>
```typescript
readonly type = VarType.Integer;
```
| 27.5 | 141 | 0.660606 | eng_Latn | 0.632763 |
ffa1918edcad2ca23e0c9fd19fae46c92deb001d | 984 | md | Markdown | docs-archive-a/2014/relational-databases/errors-events/mssqlserver-5554-database-engine-error.md | v-alji/sql-docs-archive-pr.zh-cn | bfceabe83f36411a9600d0559b2c554418242181 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs-archive-a/2014/relational-databases/errors-events/mssqlserver-5554-database-engine-error.md | v-alji/sql-docs-archive-pr.zh-cn | bfceabe83f36411a9600d0559b2c554418242181 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2021-10-11T06:46:53.000Z | 2021-11-25T02:27:01.000Z | docs-archive-a/2014/relational-databases/errors-events/mssqlserver-5554-database-engine-error.md | v-alji/sql-docs-archive-pr.zh-cn | bfceabe83f36411a9600d0559b2c554418242181 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2021-09-29T08:52:49.000Z | 2021-10-13T09:15:54.000Z | ---
title: MSSQLSERVER_5554 | Microsoft Docs
ms.custom: ''
ms.date: 06/13/2017
ms.prod: sql-server-2014
ms.reviewer: ''
ms.technology: supportability
ms.topic: conceptual
helpviewer_keywords:
- 5554 (Database Engine error)
ms.assetid: 7134bbe5-d240-4a98-85ce-b13cc8ae9b0e
author: MashaMSFT
ms.author: mathoma
ms.openlocfilehash: 5095a50f257abafb6ebde97bb32c57bc71fc4e09
ms.sourcegitcommit: ad4d92dce894592a259721a1571b1d8736abacdb
ms.translationtype: MT
ms.contentlocale: zh-CN
ms.lasthandoff: 08/04/2020
ms.locfileid: "87587418"
---
# <a name="mssqlserver_5554"></a>MSSQLSERVER_5554
## <a name="details"></a>详细信息
|||
|-|-|
|产品名称|MSSQLSERVER|
|事件 ID|5554|
|事件源|MSSQLSERVER|
|组件|SQLEngine|
|符号名称|FS_MINIVER_OVERFLOW|
|消息正文|单个文件的版本总数已达到文件系统所设置的最大限制。|
## <a name="explanation"></a>说明
在多个活动的结果集 (MARS) 或触发器方案中，[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] 都使用由操作系统指定的最低版本。
## <a name="user-action"></a>用户操作
尝试避免对同一事务中的数据进行重复更新。
| 24 | 102 | 0.732724 | yue_Hant | 0.44741 |
ffa19e951a66e870ee953ff94e7ca96172445ad7 | 973 | md | Markdown | README.md | davidpdrsn/ext | 0ba3c006618160014d4c84865de43fc7e4ffd8d9 | [
"MIT"
] | 86 | 2019-10-31T06:19:51.000Z | 2022-03-08T07:46:49.000Z | README.md | davidpdrsn/ext | 0ba3c006618160014d4c84865de43fc7e4ffd8d9 | [
"MIT"
] | 17 | 2019-10-31T17:52:36.000Z | 2021-10-22T03:40:24.000Z | README.md | davidpdrsn/ext | 0ba3c006618160014d4c84865de43fc7e4ffd8d9 | [
"MIT"
] | 4 | 2020-04-07T16:29:11.000Z | 2020-08-31T01:29:07.000Z | # extend
[](https://crates.io/crates/extend)
[](https://docs.rs/extend)
[](https://deps.rs/repo/github/davidpdrsn/extend)
[](https://github.com/davidpdrsn/extend/actions)
Create extensions for types you don't own with [extension traits] but without the boilerplate.
Example:
```rust
use extend::ext;
#[ext]
impl<T: Ord> Vec<T> {
fn sorted(mut self) -> Self {
self.sort();
self
}
}
fn main() {
assert_eq!(
vec![1, 2, 3],
vec![2, 3, 1].sorted(),
);
}
```
[extension traits]: https://dev.to/matsimitsu/extending-existing-functionality-in-rust-with-traits-in-rust-3622
| 29.484848 | 127 | 0.685509 | yue_Hant | 0.483816 |
ffa1ebcc90096543eca05077296277c4e943f206 | 39,766 | md | Markdown | articles/active-directory/develop/reference-aadsts-error-codes.md | changeworld/azure-docs.sv-se | 6234acf8ae0166219b27a9daa33f6f62a2ee45ab | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/develop/reference-aadsts-error-codes.md | changeworld/azure-docs.sv-se | 6234acf8ae0166219b27a9daa33f6f62a2ee45ab | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/develop/reference-aadsts-error-codes.md | changeworld/azure-docs.sv-se | 6234acf8ae0166219b27a9daa33f6f62a2ee45ab | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Azure AD-autentisering & auktoriseringsfelkoder
description: Lär dig mer om AADSTS-felkoderna som returneras från Azure AD-säkerhetstokentjänsten (STS).
services: active-directory
author: rwike77
manager: CelesteDG
ms.service: active-directory
ms.subservice: develop
ms.workload: identity
ms.topic: reference
ms.date: 04/07/2020
ms.author: ryanwi
ms.reviewer: hirsin
ms.custom: aaddev
ms.openlocfilehash: 40a7406ea91c95daad2f180b9d0f4620cdbbf454
ms.sourcegitcommit: 2d7910337e66bbf4bd8ad47390c625f13551510b
ms.translationtype: MT
ms.contentlocale: sv-SE
ms.lasthandoff: 04/08/2020
ms.locfileid: "80875936"
---
# <a name="azure-ad-authentication-and-authorization-error-codes"></a>Azure AD-autentiserings- och auktoriseringsfelkoder
Letar du efter information om AADSTS-felkoder som returneras från Azure Active Directory (Azure AD) security token service (STS)? Läs det här dokumentet om du vill hitta AADSTS-felbeskrivningar, korrigeringar och några föreslagna lösningar.
> [!NOTE]
> Den här informationen är preliminär och kan komma att ändras. Har du en fråga eller inte hittar det du letar efter? Skapa ett GitHub-problem eller se [Support- och hjälpalternativ för utvecklare om](active-directory-develop-help-support.md) du vill lära dig mer om andra sätt du kan få hjälp och support.
>
> Den här dokumentationen tillhandahålls för utvecklar- och administratörsvägledning, men bör aldrig användas av klienten själv. Felkoder kan ändras när som helst för att ge mer detaljerade felmeddelanden som är avsedda att hjälpa utvecklaren när de skapar sitt program. Appar som är beroende av text- eller felkodsnummer bryts med tiden.
## <a name="lookup-current-error-code-information"></a>Uppslagsström felkodsinformation
Felkoder och meddelanden kan komma att ändras. För den senaste informationen, ta `https://login.microsoftonline.com/error` en titt på sidan för att hitta AADSTS felbeskrivningar, korrigeringar och några föreslagna lösningar.
Sök på den numeriska delen av den returnerade felkoden. Om du till exempel har fått felkoden "AADSTS16000" söker du efter `https://login.microsoftonline.com/error` "16000". Du kan också länka direkt till ett specifikt fel genom `https://login.microsoftonline.com/error?code=16000`att lägga till felkodsnumret i URL:en.
## <a name="aadsts-error-codes"></a>AADSTS-felkoder
| Fel | Beskrivning |
|---|---|
| AADSTS16000 | SelectUserAccount - Detta är ett avbrott som genereras av Azure AD, vilket resulterar i användargränssnitt som gör att användaren kan välja bland flera giltiga SSO-sessioner. Det här felet är ganska vanligt och `prompt=none` kan returneras till programmet om det anges. |
| AADSTS16001 | UserAccountSelectionInvalid - Det här felet visas om användaren klickar på en panel som sessionsmarkeringslogiken har avvisat. När det här felet utlöses kan användaren återställa genom att välja från en uppdaterad lista över paneler/sessioner eller genom att välja ett annat konto. Det här felet kan uppstå på grund av ett kodfel eller rastillstånd. |
| AADSTS16002 | AppSessionSelectionInvalid - Det app-specificerade SID-kravet uppfylldes inte. |
| AADSTS16003 | SsoUserAccountNotFoundInResourceTenant - Anger att användaren inte uttryckligen har lagts till i klienten. |
| AADSTS17003 | AutentiseringsuppgifterKeyProvisioningFailed - Azure AD kan inte etablera användarnyckeln. |
| AADSTS20001 | WsFedSignInResponseError - Det finns ett problem med din federerade identitetsprovider. Kontakta din IDP för att lösa problemet. |
| AADSTS20012 | WsFedMessageInvalid - Det finns ett problem med din federerade identitetsprovider. Kontakta din IDP för att lösa problemet. |
| AADSTS20033 | FedMetadataInvalidTenantName - Det finns ett problem med din federerade identitetsprovider. Kontakta din IDP för att lösa problemet. |
| AADSTS40008 | OAuth2IdPUnretryableServerError - Det finns ett problem med din federerade identitetsprovider. Kontakta din IDP för att lösa problemet. |
| AADSTS40009 | OAuth2IdPRefreshTokenRedemptionUserError - Det finns ett problem med din federerade identitetsprovider. Kontakta din IDP för att lösa problemet. |
| AADSTS40010 | OAuth2IdPRetryableServerError - Det finns ett problem med din federerade identitetsprovider. Kontakta din IDP för att lösa problemet. |
| AADSTS40015 | OAuth2IdPAuthCodeRedemptionUserError - Det finns ett problem med din federerade identitetsprovider. Kontakta din IDP för att lösa problemet. |
| AADSTS50000 | TokenIssuanceError - Det finns ett problem med inloggningstjänsten. [Skapa ett supportärende](../fundamentals/active-directory-troubleshooting-support-howto.md) för att lösa problemet. |
| AADSTS50001 | InvalidResource - Resursen är inaktiverad eller finns inte. Kontrollera appens kod för att se till att du har angett den exakta resurs-URL:en för den resurs du försöker komma åt. |
| AADSTS50002 | NotAllowedTenant - Inloggning misslyckades på grund av en begränsad proxyåtkomst på klienten. Om det är din egen klientprincip kan du ändra dina begränsade klientinställningar för att åtgärda problemet. |
| AADSTS50003 | MissingSigningKey - Inloggning misslyckades på grund av en saknad signeringsnyckel eller certifikat. Det kan bero på att det inte fanns någon signeringsnyckel konfigurerad i appen. Kolla in de resolutioner [https://docs.microsoft.com/azure/active-directory/application-sign-in-problem-federated-sso-gallery#certificate-or-key-not-configured](https://docs.microsoft.com/azure/active-directory/application-sign-in-problem-federated-sso-gallery#certificate-or-key-not-configured)som beskrivs på . Om du fortfarande ser problem kontaktar du appens ägare eller appadministratör. |
| AADSTS50005 | DevicePolicyError - Användaren försökte logga in på en enhet från en plattform som för närvarande inte stöds via principen villkorlig åtkomst. |
| AADSTS50006 | Ogiltigsignatur - Signaturverifiering misslyckades på grund av en ogiltig signatur. |
| AADSTS50007 | PartnerEncryptionCertificateMissing - Partnerkrypteringscertifikatet hittades inte för den här appen. [Öppna en supportbiljett](../fundamentals/active-directory-troubleshooting-support-howto.md) med Microsoft för att få detta åtgärdat. |
| AADSTS50008 | InvalidSamlToken - SAML-påstående saknas eller är felkonfigurerad i token. Kontakta den federerade providern. |
| AADSTS50010 | AudienceUriValidationFailed - Audience URI-validering för appen misslyckades eftersom inga tokenmålningar konfigurerades. |
| AADSTS50011 | InvalidReplyTo - Svarsadressen saknas, är felkonfigurerad eller matchar inte svarsadresser som konfigurerats för appen. Som en lösning se till att lägga till denna saknade svarsadress till Azure Active Directory-programmet eller har någon med behörighet att hantera ditt program i Active Directory göra detta åt dig.|
| AADSTS50012 | AutentiseringMissilerad - Autentisering misslyckades av något av följande skäl:<ul><li>Undernamnet på signeringscertifikatet är inte tillåtet</li><li>Det gick inte att hitta en matchande princip för betrodda myndigheter för det auktoriserat ämnesnamnet</li><li>Certifikatkedjan är ogiltig</li><li>Signeringscertifikatet är ogiltigt</li><li>Principen är inte konfigurerad för klienten</li><li>Tumavtryck för signeringscertifikatet är inte tillåtet</li><li>Klientpåståendet innehåller en ogiltig signatur</li></ul> |
| AADSTS50013 | Ogiltig identifiering - Påstående är ogiltigt på grund av olika orsaker - Tokenutfärdaren matchar inte api-versionen inom dess giltiga tidsintervall -förfallen - Uppdateringstoken i påståendet är inte en primär uppdateringstoken. |
| AADSTS50014 | GuestUserInPendingState - Användarens inlösen är i ett väntande tillstånd. Gästanvändarkontot är inte helt skapat ännu. |
| AADSTS50015 | ViralUserLegalAgeConsentRequiredState - Användaren kräver samtycke från åldersgruppen. |
| AADSTS50017 | CertifikatvalidationMissilerad - Certifieringsvalidering misslyckades, orsaker till följande skäl:<ul><li>Det går inte att hitta utfärdarcertifikatet i listan med betrodda certifikat</li><li>Det gick inte att hitta förväntat CrlSegment</li><li>Det går inte att hitta utfärdarcertifikatet i listan med betrodda certifikat</li><li>Delta CRL-distributionspunkten har konfigurerats utan motsvarande CRL-distributionspunkt</li><li>Det gick inte att hämta giltiga CRL-segment på grund av ett timeout-problem</li><li>Det gick inte att ladda ned CRL</li></ul>Kontakta administratören för klientorganisationen. |
| AADSTS50020 | UserUnauthorized - Användare är obehöriga att anropa den här slutpunkten. |
| AADSTS50027 | InvalidJwtToken - Ogiltig JWT token på grund av följande skäl:<ul><li>innehåller inte temporärt nonce-anspråk, sub-anspråk</li><li>felaktig matchning av ämnesidentifierare</li><li>duplicerade anspråk i idToken-anspråk</li><li>oväntad utfärdare</li><li>oväntad målgrupp</li><li>inte inom giltigt tidsintervall </li><li>fel tokenformat</li><li>Signaturverifieringen för externa ID-token från utfärdare misslyckades.</li></ul> |
| AADSTS50029 | Ogiltig URI – domännamnet innehåller ogiltiga tecken. Kontakta administratören för klientorganisationen. |
| AADSTS50032 | WeakRsaKey - Anger felaktigt användarförsök att använda en svag RSA-nyckel. |
| AADSTS50033 | RetryableError - Anger ett tillfälligt fel som inte är relaterade till databasåtgärderna. |
| AADSTS50034 | UserAccountNotFound - Om du vill logga in på det här programmet måste kontot läggas till i katalogen. |
| AADSTS50042 | Det går inte Att GenereraPairwiseIdentifierMedMissingSalt - Det salt som krävs för att generera en parvis identifierare saknas i princip. Kontakta administratören för klientorganisationen. |
| AADSTS50043 | Det går inte att skapaPareratPairwiseIdentifierMedMultipleSalts |
| AADSTS50048 | SubjectMismatchesIssuer - Ämne matchar inte Utfärdarens anspråk i klientpåståendet. Kontakta administratören för klientorganisationen. |
| AADSTS50049 | NoSuchInstanceForDiscovery - Okänd eller ogiltig instans. |
| AADSTS50050 | MissformedDiscoveryRequest - Begäran är felaktig. |
| AADSTS50053 | IdsLocked - Kontot är låst eftersom användaren försökte logga in för många gånger med ett felaktigt användar-ID eller lösenord. |
| AADSTS50055 | InvalidPasswordExpiredPassword - Lösenordet har upphört att gälla. |
| AADSTS50056 | Ogiltigt lösenord eller null-lösenord -Lösenordet finns inte i butiken för den här användaren. |
| AADSTS50057 | UserDisabled - Användarkontot är inaktiverat. Kontot har inaktiverats av en administratör. |
| AADSTS50058 | UserInformationNotProvided - Det innebär att en användare inte är inloggad. Detta är ett vanligt fel som förväntas när en användare är oautentiserade och ännu inte har loggat in.</br>Om det här felet uppmuntras i en SSO-kontext där användaren tidigare har loggat in, innebär det att SSO-sessionen antingen inte hittades eller var ogiltig.</br>Det här felet kan returneras till programmet om prompt=none anges. |
| AADSTS50059 | MissingTenantRealmAndNoUserInformationProvIded - Klientidentifierande information hittades inte i vare sig begäran eller underförstått av några angivna autentiseringsuppgifter. Användaren kan kontakta klientadministratören för att lösa problemet. |
| AADSTS50061 | SignoutInvalidRequest - Ut signeringsbegäran är ogiltig. |
| AADSTS50064 | AutentiseringsuppgifterAuthenticationError - Autentiseringsuppgifter validering på användarnamn eller lösenord har misslyckats. |
| AADSTS50068 | SignoutInitiatorNotParticipant - Signout misslyckades. Appen som initierade signering är inte en deltagare i den aktuella sessionen. |
| AADSTS50070 | SignoutUnknownSessionIdentifier - Signout har misslyckats. Signeringsbegäran angav en namnidentifierare som inte matchade de befintliga sessionerna. |
| AADSTS50071 | SignoutMessageExpired - Begäran om utloggning har upphört att gälla. |
| AADSTS50072 | UserStrongAuthEnrollmentRequiredInterrupt - Användaren måste registrera sig för andra faktorautentisering (interaktiv). |
| AADSTS50074 | UserStrongAuthClientAuthNRequiredInterrupt - Stark autentisering krävs och användaren klarade inte MFA-utmaningen. |
| AADSTS50076 | UserStrongAuthClientAuthNRequired - På grund av en konfigurationsändring som gjorts av administratören, eller på grund av att du har flyttat till en ny plats, måste användaren använda multifaktorautentisering för att komma åt resursen. Försök igen med en ny auktorisera begäran om resursen. |
| AADSTS50079 | UserStrongAuthEnrollmentRequired - På grund av en konfigurationsändring som gjorts av administratören, eller på grund av att användaren flyttade till en ny plats, är användaren skyldig att använda multifaktorautentisering. |
| AADSTS50085 | Det krävs social IDP-inloggning för att token ska kunna uppdateras. Låt användaren försöka logga in igen med användarnamn och lösenord |
| AADSTS50086 | SasNonRetryableError |
| AADSTS50087 | SasRetryableError - Tjänsten är inte tillgänglig för tillfället. Försök igen. |
| AADSTS50089 | Flödestoken har upphört att gälla – autentiseringen misslyckades. Låt användaren försöka logga in igen med användarnamn -lösenord. |
| AADSTS50097 | DeviceAuthenticationRequired - Enhetsautentisering krävs. |
| AADSTS50099 | PKeyAuthInvalidJwtUnauthorized - JWT-signaturen är ogiltig. |
| AADSTS50105 | EntitlementGrantsNotFound - Den inloggade användaren har inte tilldelats en roll för den inloggade appen. Tilldela användaren till appen. För mer[https://docs.microsoft.com/azure/active-directory/application-sign-in-problem-federated-sso-gallery#user-not-assigned-a-role](https://docs.microsoft.com/azure/active-directory/application-sign-in-problem-federated-sso-gallery#user-not-assigned-a-role)information: . |
| AADSTS50107 | InvalidRealmUri - Det begärda federationssfärobjektet finns inte. Kontakta administratören för klientorganisationen. |
| AADSTS50120 | ThresholdJwtInvalidJwtFormat - Problem med JWT-huvud. Kontakta administratören för klientorganisationen. |
| AADSTS50124 | ClaimsTransformationInvalidInputParameter - Anspråksomvandling innehåller ogiltig indataparameter. Kontakta administratören för klientorganisationen för att uppdatera principen. |
| AADSTS50125 | PasswordResetRegistrationRequiredInterrupt - Inloggning avbröts på grund av en lösenordsåterställning eller lösenordsregistrering. |
| AADSTS50126 | InvalidUserNameOrPassword - Fel validera autentiseringsuppgifter på grund av ogiltigt användarnamn eller lösenord. |
| AADSTS50127 | BrokerAppNotInstalled - Användaren måste installera en mäklarapp för att få tillgång till det här innehållet. |
| AADSTS50128 | Ogiltigt domännamn - Ingen klientidentifierande information som finns i vare sig begäran eller underförstått av några angivna autentiseringsuppgifter. |
| AADSTS50129 | DeviceIsNotWorkplaceJoined - Arbetsplatsanslutning krävs för att registrera enheten. |
| AADSTS50131 | ConditionalAccessFailed - Anger olika villkorliga åtkomstfel, till exempel dåligt Windows-enhetstillstånd, begäran blockerad på grund av misstänkt aktivitet, åtkomstprincip eller säkerhetsprincipbeslut. |
| AADSTS50132 | SsoArtifactInvalidOrExpired - Sessionen är inte giltig på grund av lösenordsförfallodatum eller senaste lösenordsändring. |
| AADSTS50133 | SsoArtifactRevoked - Sessionen är inte giltig på grund av lösenordsförfallodatum eller senaste lösenordsändring. |
| AADSTS50134 | DeviceFlowAuthorizeWrongDatacenter - Fel datacenter. Om du vill auktorisera en begäran som initierades av en app i OAuth 2.0-enhetsflödet måste den auktorisera parten be be beta i samma datacenter där den ursprungliga begäran finns. |
| AADSTS50135 | PasswordChangeCompromisedPassword - Lösenordsändring krävs på grund av kontorisk. |
| AADSTS50136 | RedirectMsaSessionToApp - En enda MSA-session har upptäckts. |
| AADSTS50139 | SessionMissingMsaOAuth2RefreshToken - Sessionen är ogiltig på grund av en extern uppdateringstoken som saknas. |
| AADSTS50140 | KmsiInterrupt - Det här felet uppstod på grund av att "Håll mig inloggad" avbryter när användaren loggade in. [Skapa ett supportärende](../fundamentals/active-directory-troubleshooting-support-howto.md) med korrelations-ID, ID för begäran och felkod för mer information. |
| AADSTS50143 | Sessionsmatchning - Sessionen är ogiltig eftersom användarens klientorganisation inte matchar domäntipset på grund av olika resurser. [Öppna en supportbiljett](../fundamentals/active-directory-troubleshooting-support-howto.md) med korrelations-ID, begärande-ID och felkod för att få mer information. |
| AADSTS50144 | InvalidPasswordExpiredOnPremPassword - Användarens Active Directory-lösenord har upphört att gälla. Generera ett nytt lösenord för användaren eller be användaren använda självbetjäningsåterställningsverktyget för att återställa sitt lösenord. |
| AADSTS50146 | MissingCustomSigningKey - Den här appen måste konfigureras med en appspecifik signeringsnyckel. Det har antingen inte konfigurerats med en sådan eller så har nyckeln upphört att gälla/är inte giltig än. |
| AADSTS50147 | MissingCodeChallenge - Storleken på parametern kodutmaning är ogiltig. |
| AADSTS50155 | DeviceAuthenticationFailed - Enhetsautentisering misslyckades för den här användaren. |
| AADSTS50158 | ExternalSecurityChallenge - Yttre säkerhet utmaning var inte nöjd. |
| AADSTS50161 | InvalidExternalSecurityChallengeConfiguration - Anspråk som skickas av extern leverantör är inte tillräckligt eller saknade anspråk som begärs till extern leverantör. |
| AADSTS50166 | ExternalClaimsProviderThrottled - Det gick inte att skicka begäran till anspråksprovidern. |
| AADSTS50168 | ChromeBrowserSsoInterruptRequired - Klienten kan hämta en SSO-token via Windows 10-kontotillägget, men token hittades inte i begäran eller den medföljande token har upphört att gälla. |
| AADSTS50169 | InvalidRequestBadRealm - Sfären är inte en konfigurerad sfär för det aktuella tjänstnamnområdet. |
| AADSTS50170 | SaknasExternalClaimsProviderMapping - Den externa kontroller mappningen saknas. |
| AADSTS50177 | ExternalChallengeNotSupportedForPassthroughUsers - Extern utmaning stöds inte för vidareströmsanvändare. |
| AADSTS50178 | SessionControlNotSupportedForPassthroughUsers - Sessionskontrollen stöds inte för vidareströmningsanvändare. |
| AADSTS50180 | WindowsIntegratedAuthMissing - Integrerad Windows-autentisering behövs. Aktivera klientorganisationen för sömlös SSO. |
| AADSTS50187 | DeviceInformationNotProvided - Tjänsten kunde inte utföra enhetsautentisering. |
| AADSTS50196 | LoopDetected - En klientloop har upptäckts. Kontrollera appens logik för att säkerställa att tokencacheing implementeras och att felvillkor hanteras korrekt. Appen har gjort för många av samma begäran på för kort tid, vilket indikerar att den är i ett felaktigt tillstånd eller är felaktigt begär token. |
| AADSTS50197 | ConflictingIdentities - Det gick inte att hitta användaren. Försök logga in igen. |
| AADSTS50199 | CmsiInterrupt - Av säkerhetsskäl krävs användarbekräftelse för den här begäran. Eftersom detta är ett "interaction_required"-fel bör klienten göra interaktiva autentisering. Detta beror på att en systemwebbvy har använts för att begära en token för ett inbyggt program - användaren måste uppmanas att fråga om detta verkligen var appen de tänkt logga in på.|
| AADSTS51000 | RequiredFeatureNotEnabled - Funktionen är inaktiverad. |
| AADSTS51001 | DomainHintMustbePresent - Domäntips måste finnas med lokal säkerhetsidentifierare eller lokal UPN. |
| AADSTS51004 | UserAccountNotInDirectory - Användarkontot finns inte i katalogen. |
| AADSTS51005 | TemporaryRedirect - Motsvarar HTTP-status 307, vilket anger att den begärda informationen finns vid den URI som anges i platshuvudet. När du får den här statusen följer du platshuvudet som är associerat med svaret. När den ursprungliga begäran metoden var POST, kommer omdirigerad begäran också att använda POST-metoden. |
| AADSTS51006 | ForceReauthDueToInsufficientAuth - Integrerad Windows-autentisering behövs. Användaren loggade in med en sessionstoken som saknar det integrerade Windows-autentiseringsanspråket. Be användaren att logga in igen. |
| AADSTS52004 | DelegationDoesNotExistForLinkedIn - Användaren har inte gett sitt samtycke till åtkomst till LinkedIn-resurser. |
| AADSTS53000 | DeviceNotCompliant - Principen villkorlig åtkomst kräver en kompatibel enhet och enheten är inte kompatibel. Användaren måste registrera sin enhet med en godkänd MDM-provider som Intune. |
| AADSTS53001 | DeviceNotDomainJoined - Principen villkorlig åtkomst kräver en domänansluten enhet och enheten är inte domänansluten. Be användaren använda en domänansluten enhet. |
| AADSTS53002 | ApplicationUsedIsNotAnApprovedApp - Appen som används är inte en godkänd app för villkorlig åtkomst. Användaren måste använda en av apparna från listan över godkända appar som ska användas för att få åtkomst. |
| AADSTS53003 | BlockedByConditionalAccess - Access har blockerats av principer för villkorlig åtkomst. Åtkomstprincipen tillåter inte tokenutfärdande. |
| AADSTS53004 | ProofUpBlockedDueToRisk - Användaren måste slutföra registreringsprocessen för multifaktorautentisering innan du öppnar det här innehållet. Användaren bör registrera sig för multifaktorautentisering. |
| AADSTS54000 | MinorUserBlockedLegalAgeGroupRule |
| AADSTS65001 | DelegationDoesNotExist - Användaren eller administratören har inte samtyckt till att använda programmet med ID X. Skicka en interaktiv auktoriseringsbegäran för den här användaren och resursen. |
| AADSTS65004 | UserDeclinedConsent - Användaren avböjde att godkänna åtkomst till appen. Låt användaren logga in igen och ge samtycke till appen|
| AADSTS65005 | Felkonfigureradtillämpning – Listan över resursåtkomst för appen innehåller inte appar som kan identifieras av resursen eller klientappen har begärt åtkomst till resursen, vilket inte angavs i den obligatoriska resursåtkomstlistan eller graph-tjänsten returnerade dålig begäran eller resurs hittades inte. Om appen stöder SAML kan du ha konfigurerat appen med fel identifierare (entitet). Prova upplösningen som anges för SAML med hjälp av länken nedan:[https://docs.microsoft.com/azure/active-directory/application-sign-in-problem-federated-sso-gallery#no-resource-in-requiredresourceaccess-list](https://docs.microsoft.com/azure/active-directory/application-sign-in-problem-federated-sso-gallery?/?WT.mc_id=DMC_AAD_Manage_Apps_Troubleshooting_Nav) |
| AADSTS67003 | ActorNotValidServiceIdentity |
| AADSTS70000 | InvalidGrant - Autentisering misslyckades. Uppdateringstoken är ogiltig. Felet kan bero på följande:<ul><li>Tokenbindningshuvudet är tomt</li><li>Tokenbindningshh matchar inte</li></ul> |
| AADSTS70001 | UnauthorizedClient - Programmet är inaktiverat. |
| AADSTS70002 | InvalidClient - Fel validera autentiseringsuppgifterna. Den angivna client_secret matchar inte det förväntade värdet för den här klienten. Korrigera client_secret och försök igen. Mer information finns i [Använda auktoriseringskoden för att begära en åtkomsttoken](v2-oauth2-auth-code-flow.md#request-an-access-token). |
| AADSTS70003 | Inte stödsGrantType - Appen returnerade en bidragstyp som inte stöds. |
| AADSTS70004 | InvalidRedirectUri - Appen returnerade en ogiltig omdirigerings-URI. Adressen för omdirigering som angetts av klienten matchar inte några konfigurerade adresser eller någon adress på godkännandelistan för OIDC. |
| AADSTS70005 | ResponseeType som inte stöds – Appen returnerade en svarstyp som inte stöds på grund av följande orsaker:<ul><li>svarstypen "token" är inte aktiverad för appen</li><li>svarstypen "id_token" kräver OpenID-omfång – innehåller ett OAuth-parametervärde som inte stöds i den kodade wctx</li></ul> |
| AADSTS70007 | Svarar inteMode - Appen returnerade ett värde som `response_mode` inte stöds när du begär en token. |
| AADSTS70008 | ExpiredOrRevokedGrant - Uppdateringstoken har upphört att gälla på grund av inaktivitet. Token utfärdades på XXX och var inaktiv under en viss tid. |
| AADSTS70011 | InvalidScope - Det scope som begärs av appen är ogiltigt. |
| AADSTS70012 | MsaServerError - Ett serverfel uppstod när en MSA-användare (konsument). Försök igen. Om det fortsätter att misslyckas [öppnar du en supportbiljett](../fundamentals/active-directory-troubleshooting-support-howto.md) |
| AADSTS70016 | Auktoriseringsanering - OAuth 2.0-enhetsflödesfel. Auktorisering väntar. Enheten försöker avsöka begäran igen. |
| AADSTS70018 | BadVerificationCode - Ogiltig verifieringskod på grund av att användaren skriver in fel användarkod för enhetskodflödet. Auktorisering är inte godkänd. |
| AADSTS70019 | CodeExpired - Verifieringskoden har upphört att gälla. Be användaren försöka logga in igen. |
| AADSTS75001 | BindingSerializationError - Ett fel uppstod under SAML-meddelandebindning. |
| AADSTS75003 | Binder inte - Appen returnerade ett fel som var relaterat till bindning som inte stöds (SAML-protokollsvaret kan inte skickas via andra bindningar än HTTP POST). |
| AADSTS75005 | Saml2MessageInvalid - Azure AD stöder inte SAML-begäran som skickas av appen för SSO. |
| AADSTS75008 | RequestDeniedError - Begäran från appen nekades eftersom SAML-begäran hade ett oväntat mål. |
| AADSTS75011 | NoMatchedAuthnContextInOutputClaims - Autentiseringsmetoden som användaren autentiserade med tjänsten inte matchar begärd autentiseringsmetod. |
| AADSTS75016 | Saml2AuthenticationRequestInvalidNameIDPolicy - SAML2 Autentiseringsbegäran har ogiltig NameIdPolicy. |
| AADSTS80001 | OnPremiseStoreIsNotAvailable - Autentiseringsagenten kan inte ansluta till Active Directory. Kontrollera att agentservrar är medlemmar i samma AD-skog som de användare vars lösenord måste valideras och de kan ansluta till Active Directory. |
| AADSTS80002 | OnPremisePasswordValidatorRequestTimedout - Lösenord validering begäran timeout. Kontrollera att Active Directory är tillgängligt och svara på begäranden från agenterna. |
| AADSTS80005 | OnPremisePasswordValidatorUnpredictableWebException - Ett okänt fel uppstod vid bearbetning av svaret från autentiseringsagenten. Försök igen. Om det fortsätter att misslyckas öppnar [du en supportbiljett](../fundamentals/active-directory-troubleshooting-support-howto.md) för att få mer information om felet. |
| AADSTS80007 | OnPremisePasswordValidatorErrorOccurredOnPrem - Autentiseringsagenten kan inte validera användarens lösenord. Kontrollera agentloggarna för mer information och kontrollera att Active Directory fungerar som förväntat. |
| AADSTS80010 | OnPremisePasswordValidationEncryptionException - Autentiseringsagenten kan inte dekryptera lösenord. |
| AADSTS80012 | OnPremisePasswordValidationAccountLogonInvalidHours - Användarna försökte logga in utanför de tillåtna timmarna (detta anges i AD). |
| AADSTS80013 | OnPremisePasswordValidationTimeSkew - Autentiseringsförsöket kunde inte slutföras på grund av tidsnedställning mellan datorn som kör autentiseringsagenten och AD. Åtgärda problem med tidssynkronisering. |
| AADSTS81004 | DesktopSsoIdentityInTicketIsNotAuthenticated - Kerberos autentiseringsförsök misslyckades. |
| AADSTS81005 | DesktopSsoAuthenticationPackageNotSupported - Autentiseringspaketet stöds inte. |
| AADSTS81006 | DesktopSsoNoAuthorizationHeader - Inget auktoriseringshuvud hittades. |
| AADSTS81007 | DesktopSsoTenantIsNotOptIn - Klienten är inte aktiverad för Sömlös SSO. |
| AADSTS81009 | DesktopSsoAuthorizationHeaderValueWithBadFormat - Det går inte att validera användarens Kerberos-biljett. |
| AADSTS81010 | DesktopSsoAuthTokenInvalid - Seamless SSO misslyckades eftersom användarens Kerberos-biljett har upphört att gälla eller är ogiltig. |
| AADSTS81011 | DesktopSsoLookupUserBySidFailed - Det gick inte att hitta användarobjekt baserat på information i användarens Kerberos-biljett. |
| AADSTS81012 | DesktopSsoMismatchBetweenTokenUpnAndChosenUpn - Användaren som försöker logga in på Azure AD skiljer sig från användaren som är inloggad på enheten. |
| AADSTS90002 | InvalidTenantName - Klientnamnet hittades inte i datalagret. Kontrollera att du har rätt klient-ID. |
| AADSTS90004 | InvalidRequestFormat - Begäran är inte korrekt formaterad. |
| AADSTS90005 | InvalidRequestWithMultipleRequirements - Det går inte att slutföra begäran. Begäran är inte giltig eftersom identifierings- och inloggningstipset inte kan användas tillsammans. |
| AADSTS90006 | ExternalServerRetryableError - Tjänsten är inte tillgänglig för tillfället.|
| AADSTS90007 | InvalidSessionId - Felaktig begäran. Det gick att tolka sessions-ID:t. |
| AADSTS90008 | TokenForItselfRequiresGraphPermission - Användaren eller administratören har inte samtyckt till att använda programmet. Programmet kräver åtminstone åtkomst till Azure AD genom att ange behörigheten inloggning och läsa användarprofil. |
| AADSTS90009 | TokenForItselfMissingIdenticalAppIdentifier - Programmet begär en token för sig själv. Det här scenariot stöds bara om den resurs som har angetts använder det GUID-baserade program-ID:et. |
| AADSTS90010 | NotSupported - Det går inte att skapa algoritmen. |
| AADSTS90012 | RequestTimeout - Den begärda har timeout. |
| AADSTS90013 | InvalidUserInput - Indata från användaren är ogiltig. |
| AADSTS90014 | MissingRequiredField - Den här felkoden kan visas i olika fall när ett förväntat fält inte finns i autentiseringsuppgifterna. |
| AADSTS90015 | QueryStringTooLong - Frågesträngen är för lång. |
| AADSTS90016 | MissingRequiredClaim - Åtkomsttoken är inte giltig. Den begärd fordran saknas. |
| AADSTS90019 | MissingTenantRealm - Azure AD kunde inte fastställa klientidentifieraren från begäran. |
| AADSTS90022 | AuthenticatedInvalidPrincipalNameFormat - Huvudnamnformatet är ogiltigt eller `name[/host][@realm]` uppfyller inte det förväntade formatet. Huvudnamnet krävs, värd och sfär är valfria och kan ställas in på null. |
| AADSTS90023 | InvalidRequest - Begäran om autentiseringstjänst är ogiltig. |
| AADSTS9002313 | InvalidRequest - Begäran är felaktig eller ogiltig. - (EN) Problemet här är att det var något fel med begäran till en viss slutpunkt. Förslaget till detta problem är att få en spelman spår av felet inträffar och vill se om begäran är faktiskt korrekt formaterad eller inte. |
| AADSTS90024 | RequestBudgetExceededError - Ett tillfälligt fel har inträffat. Försök igen. |
| AADSTS90033 | MsodsServiceUnavailable - Microsoft Online Directory Service (MSODS) är inte tillgänglig. |
| AADSTS90036 | MsodsServiceUnretryableFailure - Ett oväntat, icke-retryable fel från WCF-tjänsten värd MSODS har inträffat. [Skapa ett supportärende](../fundamentals/active-directory-troubleshooting-support-howto.md) för att få mer information om felet. |
| AADSTS90038 | NationalCloudTenantRedirection - Den angivna hyresgästen "Y" tillhör National Cloud "X". Aktuella molninstansen "Z" federerar inte med X. Ett fel i omdirigering av molnet returneras. |
| AADSTS90043 | NationalCloudAuthCodeRedirection - Funktionen är inaktiverad. |
| AADSTS90051 | InvalidNationalCloudId - Den nationella molnidentifieraren innehåller en ogiltig molnidentifierare. |
| AADSTS90055 | TenantThrottlingError - Det finns för många inkommande begäranden. Det här undantaget genereras för blockerade klienter. |
| AADSTS90056 | BadResourceRequest - Om du vill lösa in koden för en `/token` åtkomsttoken ska appen skicka en POST-begäran till slutpunkten. Dessutom bör du innan detta ange en auktoriseringskod `/token` och skicka den i POST-begäran till slutpunkten. Se den här artikeln för en översikt över OAuth [https://docs.microsoft.com/azure/active-directory/develop/active-directory-protocols-oauth-code](https://docs.microsoft.com/azure/active-directory/develop/active-directory-protocols-oauth-code)2.0 auktoriseringskod flöde: . Rikta användaren till `/authorize` slutpunkten, som returnerar en authorization_code. Genom att publicera `/token` en begäran till slutpunkten får användaren åtkomsttoken. Logga in på Azure-portalen och kontrollera **appregistreringar > slutpunkter** för att bekräfta att de två slutpunkterna har konfigurerats korrekt. |
| AADSTS90072 | PassThroughUserMfaError - Det externa konto som användaren loggar in med finns inte på klienten som de loggade in på. så att användaren inte kan uppfylla MFA-kraven för klienten. Kontot måste läggas till som en extern användare i klienten först. Logga ut och logga in med ett annat Azure AD-användarkonto. |
| AADSTS90081 | OrgIdWsFederationMessageInvalid - Ett fel uppstod när tjänsten försökte bearbeta ett WS-Federation-meddelande. Meddelandet är ogiltigt. |
| AADSTS90082 | OrgIdWsFederationNotSupported - Den valda autentiseringsprincipen för begäran stöds för närvarande inte. |
| AADSTS90084 | OrgIdWsFederationGuestNotAllowed - Gästkonton är inte tillåtna för den här webbplatsen. |
| AADSTS90085 | OrgIdWsFederationSltRedemptionFailed - Tjänsten kan inte utfärda en token eftersom företagsobjektet inte har etablerats ännu. |
| AADSTS90086 | OrgIdWsTrustDaTokenExpirerad - Användarens DA-token har upphört att gälla. |
| AADSTS90087 | OrgIdWsFederationMessageCreationFromUriFailed - Ett fel uppstod när WS-Federation-meddelandet från URI skulle skapas. |
| AADSTS90090 | GraphRetryableError - Tjänsten är inte tillgänglig för tillfället. |
| AADSTS90091 | GraphServiceOåre kan nås |
| AADSTS90092 | GraphNonRetryableError |
| AADSTS90093 | GraphUserUnauthorized - Graph returneras med en förbjuden felkod för begäran. |
| AADSTS90094 | AdminConsentRequired - Administratörsmedgivande krävs. |
| AADSTS900382 | Konfidentiell klient stöds inte i Cross Cloud-begäran. |
| AADSTS90100 | InvalidRequestParameter - Parametern är tom eller ogiltig. |
| AADSTS901002 | AADSTS901002: Parametern för resursbegäran stöds inte. |
| AADSTS90101 | InvalidEmailAddress - De angivna uppgifterna är inte en giltig e-postadress. E-postadressen måste vara `[email protected]`i formatet . |
| AADSTS90102 | InvalidUriParameter - Värdet måste vara en giltig absolut URI. |
| AADSTS90107 | InvalidXml - Begäran är ogiltig. Kontrollera att dina data inte har ogiltiga tecken.|
| AADSTS90114 | InvalidExpiryDate - Tidsstämpeln för förfallodatum för masstoken gör att en token som har upphört att gälla utfärdas. |
| AADSTS90117 | OgiltigtQuestInput |
| AADSTS90119 | InvalidUserCode - Användarkoden är null eller tom.|
| AADSTS90120 | InvalidDeviceFlowRequest - Begäran har redan godkänts eller avvisats. |
| AADSTS90121 | InvalidEmptyRequest - Ogiltig tom begäran.|
| AADSTS90123 | IdentityProviderAccessDenied - Token kan inte utfärdas eftersom identitets- eller anspråksutfärdarprovidern nekade begäran. |
| AADSTS90124 | V1ResourceV2GlobalEndpointNotSupported - Resursen stöds `/common` inte `/consumers` över slutpunkterna eller. Använd `/organizations` slutpunkten eller klientspecifikt i stället. |
| AADSTS90125 | DebugModeEnrollTenantNotFound - Användaren finns inte i systemet. Kontrollera att du har angett användarnamnet korrekt. |
| AADSTS90126 | DebugModeEnrollTenantNotInferred - Användartypen stöds inte på den här slutpunkten. Systemet kan inte dra slutsatsen att användarens klientorganisation kommer från användarnamnet. |
| AADSTS90130 | NonConvergedAppV2GlobalEndpointNotSupported - Programmet stöds inte `/common` `/consumers` över slutpunkterna eller. Använd `/organizations` slutpunkten eller klientspecifikt i stället. |
| AADSTS120000 | PasswordChangeIncorrectCurrentPassword |
| AADSTS120002 | LösenordChangeInvalidNewPasswordWeak |
| AADSTS120003 | PasswordChangeInvalidNewPasswordContainsMemberName |
| AADSTS120004 | LösenordChangeOnPremComplexity |
| AADSTS120005 | PasswordChangeOnPremSuccessCloudFail |
| AADSTS120008 | PasswordChangeAsyncJobStateTerminated - Ett fel som inte kan försökas igen har inträffat.|
| AADSTS120011 | PasswordChangeAsyncUpnInferenceFailed |
| AADSTS120012 | PasswordChangeNeedsToHappenOnPrem |
| AADSTS120013 | PasswordChangeOnPremisesConnectivityFailure |
| AADSTS120014 | PasswordChangeOnPremUserAccountLockedOutOrDisabled |
| AADSTS120015 | PasswordChangeADAdminActionRequired |
| AADSTS120016 | PasswordChangeUserNotFoundBySspr |
| AADSTS120018 | PasswordChangePasswordDoesnotComplyFuzzyPolicy |
| AADSTS120020 | LösenordÄndelse |
| AADSTS120021 | PartnerServiceSsprInternalServiceError |
| AADSTS130004 | NgcKeyNotFound - Användarens huvudnamn har inte NGC ID-nyckeln konfigurerad. |
| AADSTS130005 | NgcInvalidSignature - NGC-nyckelsignaturen misslyckades.|
| AADSTS130006 | NgcTransportKeyNotFound - NGC-transportnyckeln är inte konfigurerad på enheten. |
| AADSTS130007 | NgcDeviceIsabled - Enheten är inaktiverad. |
| AADSTS130008 | NgcDeviceIsNotFound - Enheten som refererades av NGC-nyckeln hittades inte. |
| AADSTS135010 | KeyNotFound (KeyNotFound) |
| AADSTS140000 | InvalidRequestNonce - Begäran nonce tillhandahålls inte. |
| AADSTS140001 | InvalidSessionKey - Sessionsnyckeln är ogiltig.|
| AADSTS165900 | InvalidApiRequest - Ogiltig begäran. |
| AADSTS220450 | Stöds inteAndroidWebViewVersion - Chrome WebView-versionen stöds inte. |
| AADSTS220501 | OgiltigT Nedladdning |
| AADSTS221000 | DeviceOnlyTokensNotSupportedByResource - Resursen är inte konfigurerad för att acceptera token endast för enheter. |
| AADSTS240001 | BulkAADJTokenUnauthorized - Användaren har inte behörighet att registrera enheter i Azure AD. |
| AADSTS240002 | RequiredClaimIsMissing - Id_token kan inte användas `urn:ietf:params:oauth:grant-type:jwt-bearer` som bidrag.|
| AADSTS530032 | BlockedByConditionalAccessOnSecurityPolicy - Klientadministratören har konfigurerat en säkerhetsprincip som blockerar den här begäran. Kontrollera de säkerhetsprinciper som har definierats på klientnivå för att avgöra om din begäran uppfyller principkraven. |
| AADSTS700016 | UnauthorizedClient_DoesNotMatchRequest - Programmet hittades inte i katalogen/klienten. Detta kan inträffa om programmet inte har installerats av klientens administratör eller medgivande från någon användare i klienten. Du kan ha felkonfigurerat identifierare värdet för programmet eller skickat din autentiseringsbegäran till fel klient. |
| AADSTS700020 | InteractionRequired - Åtkomstbidraget kräver interaktion. |
| AADSTS700022 | InvalidMultipleResourcesScope - Det angivna värdet för indataparameteromfånget är inte giltigt eftersom det innehåller mer än en resurs. |
| AADSTS700023 | InvalidResourcelessScope - Det angivna värdet för indataparameteromfånget är inte giltigt när du begär en åtkomsttoken. |
| AADSTS7000222| InvalidClientSecretExpiredKeysProvided - De angivna klienthemliga nycklarna har upphört att gälla. Besök Azure Portal för att skapa nya nycklar för din app, eller överväg att använda certifikatuppgifter för ökad säkerhet:https://aka.ms/certCreds |
| AADSTS700005 | InvalidGrantRedeemAgainstWrongTenant - Förutsatt auktoriseringskod är avsedd att användas mot andra innehavare, och avvisas därför. OAuth2 auktoriseringskod måste lösas in mot samma klient som den förvärvades för (/common eller /{tenant-ID} som är tillämpligt) |
| AADSTS1000000 | UserNotBoundError - Bind API kräver att Azure AD-användaren också autentiserar med ett externt IDP, vilket inte har hänt ännu. |
| AADSTS1000002 | BindCompleteInterruptError - Bindningen har slutförts, men användaren måste informeras. |
| AADSTS7000112 | UnauthorizedClientApplicationDisabled - Programmet är inaktiverat. |
| AADSTS7500529 | Värdet "SAMLId-Guid" är inte ett giltigt SAML-ID - Azure AD använder det här attributet för att fylla i InResponseTo-attributet för det returnerade svaret. ID får inte börja med ett tal, så en gemensam strategi är att prepend en sträng som "id" till strängrepresentation av ett GUID. Till exempel, id6c1c178c166d486687be4aaf5e482730 är ett giltigt ID. |
## <a name="next-steps"></a>Nästa steg
* Har du en fråga eller inte hittar det du letar efter? Skapa ett GitHub-problem eller se [Support- och hjälpalternativ för utvecklare om](active-directory-develop-help-support.md) du vill lära dig mer om andra sätt du kan få hjälp och support.
| 141.516014 | 846 | 0.822235 | swe_Latn | 0.999186 |
ffa23f65092b76051ce92b5529202725eefaaa91 | 1,616 | md | Markdown | sdk-api-src/content/fci/nf-fci-fnfcifree.md | amorilio/sdk-api | 54ef418912715bd7df39c2561fbc3d1dcef37d7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | sdk-api-src/content/fci/nf-fci-fnfcifree.md | amorilio/sdk-api | 54ef418912715bd7df39c2561fbc3d1dcef37d7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | sdk-api-src/content/fci/nf-fci-fnfcifree.md | amorilio/sdk-api | 54ef418912715bd7df39c2561fbc3d1dcef37d7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
UID: NF:fci.FNFCIFREE
title: FNFCIFREE macro (fci.h)
description: The FNFCIFREE macro provides the declaration for the application-defined callback function to free previously allocated memory in an FCI context.
helpviewer_keywords: ["FNFCIFREE","FNFCIFREE macro [Windows API]","fci/FNFCIFREE","winprog.fnfcifree"]
old-location: winprog\fnfcifree.htm
tech.root: winprog
ms.assetid: 48f052e2-7786-430a-b3dc-afcfdffae387
ms.date: 12/05/2018
ms.keywords: FNFCIFREE, FNFCIFREE macro [Windows API], fci/FNFCIFREE, winprog.fnfcifree
req.header: fci.h
req.include-header:
req.target-type: Windows
req.target-min-winverclnt:
req.target-min-winversvr:
req.kmdf-ver:
req.umdf-ver:
req.ddi-compliance:
req.unicode-ansi:
req.idl:
req.max-support:
req.namespace:
req.assembly:
req.type-library:
req.lib:
req.dll:
req.irql:
targetos: Windows
req.typenames:
req.redist:
ms.custom: 19H1
f1_keywords:
- FNFCIFREE
- fci/FNFCIFREE
dev_langs:
- c++
topic_type:
- APIRef
- kbSyntax
api_type:
- HeaderDef
api_location:
- fci.h
api_name:
- FNFCIFREE
---
# FNFCIFREE macro
## -description
The <b>FNFCIFREE</b> macro provides the declaration for the application-defined callback function to free previously allocated memory in an FCI context.
## -parameters
### -param fn
Pointer to the allocated memory block to free.
## -remarks
The function accepts parameters similar to <a href="https://msdn.microsoft.com/library/we1whae7(VS.80).aspx">free</a>.
#### Examples
```cpp
FNFCIFREE(fnMemFree)
{
free(memory);
}
```
## -see-also
<a href="/windows/desktop/api/fci/nf-fci-fcicreate">FCICreate</a> | 20.455696 | 158 | 0.746287 | yue_Hant | 0.393572 |
ffa2b7995f26b52d5c8f23b02ef3fc36c4e51f70 | 4,146 | md | Markdown | src/04. Architecture/02. Authentication/01. Identity.md | CrossBound/piranha.core.docs | 3e69bd619046edae4a73fdb254073b789e556446 | [
"MIT"
] | 11 | 2019-10-13T15:03:58.000Z | 2021-09-16T00:30:49.000Z | src/04. Architecture/02. Authentication/01. Identity.md | CrossBound/piranha.core.docs | 3e69bd619046edae4a73fdb254073b789e556446 | [
"MIT"
] | 57 | 2019-12-13T09:51:00.000Z | 2022-02-17T04:52:11.000Z | src/04. Architecture/02. Authentication/01. Identity.md | CrossBound/piranha.core.docs | 3e69bd619046edae4a73fdb254073b789e556446 | [
"MIT"
] | 48 | 2019-10-28T15:59:41.000Z | 2021-11-07T15:25:49.000Z | # Identity Authentication
Identity Security is a basic implementation using `AspNetCore.Identity` for user management and authentication. You can use this implementation for production scenarios where you want to host the security packages together with the application.
## Installation
As `AspNetCore.Identity` uses **auto increment** columns for primary key the migration code for creating the database schema is database dependent. This means you need to include different NuGet packages depending on what database provider you're using. The currently available packages are:
##### SQLite
~~~ csharp
> dotnet add package Piranha.AspNetCore.Identity.SQLite
~~~
##### SQLServer
~~~ csharp
> dotnet add package Piranha.AspNetCore.Identity.SQLServer
~~~
##### MySQL
~~~ csharp
> dotnet add package Piranha.AspNetCore.Identity.MySQL
~~~
## Registering The Service
You register Identity Security in `ConfigureServices()`. There are two methods available for adding the services, `AddPiranhaIdentity` and `AddPiranhaIdentityWithSeed`. The later of them seeds the default admin user with username admin and password password. How you register the service is also dependent on which database provider you use:
#### SQLite
**With default seed**
~~~ csharp
public void ConfigureServices(IServiceCollection services)
{
services.AddPiranha(options =>
{
options.UseIdentityWithSeed<IdentitySQLiteDb>(db =>
db.UseSqlite(...));
});
}
~~~
**Without seeding default user**
~~~ csharp
public void ConfigureServices(IServiceCollection services)
{
services.AddPiranha(options =>
{
options.UseIdentity<IdentitySQLServerDb>(db =>
db.UseSqlite(...));
});
}
~~~
#### SQLServer
**With default seed**
~~~ csharp
public void ConfigureServices(IServiceCollection services)
{
services.AddPiranha(options =>
{
options.UseIdentityWithSeed<IdentitySQLServerDb>(db =>
db.UseSqlServer(...));
});
}
~~~
**Without seeding default user**
~~~ csharp
public void ConfigureServices(IServiceCollection services)
{
services.AddPiranha(options =>
{
options.UseIdentity<IdentitySQLServerDb>(db =>
db.UseSqlServer(...));
});
}
~~~
## Configuring Identity Options
When registering the service you can also provide custom `IdentityOptions`.
~~~ csharp
public void ConfigureServices(IServiceCollection services)
{
services.AddPiranha(options =>
{
options.UseIdentity<...>(db => ...,
identityOptions: io => {
// Add your custom identity options here
}
);
});
}
~~~~
### Default Identity Options
These are the default Identity Options provided. Please note that these are more geared towards **development scenarios** as it enforces a very low password strength algorithm, and should be changed in production scenarios.
~~~ csharp
// Password settings
io.Password.RequireDigit = false;
io.Password.RequiredLength = 6;
io.Password.RequireNonAlphanumeric = false;
io.Password.RequireUppercase = false;
io.Password.RequireLowercase = false;
io.Password.RequiredUniqueChars = 1;
// Lockout settings
io.Lockout.DefaultLockoutTimeSpan = TimeSpan.FromMinutes(30);
io.Lockout.MaxFailedAccessAttempts = 10;
io.Lockout.AllowedForNewUsers = true;
// User settings
io.User.RequireUniqueEmail = true;
~~~
## Configuring Cookie Options
When registering the service you can also provide custom `CookieOptions`.
~~~ csharp
public void ConfigureServices(IServiceCollection services)
{
services.AddPiranha(options =>
{
options.UseIdentity<...>(db => ...,
cookieOptions: co => {
// Add your custom cookie options here
});
);
});
}
~~~~
### Default Cookie Options
These are the default Cookie Options provided. These should be changed to support HTTPS or maybe change the default login URL if you're running a custom login setup.
~~~ csharp
co.Cookie.HttpOnly = true;
co.ExpireTimeSpan = TimeSpan.FromMinutes(30);
co.LoginPath = "/manager/login";
co.AccessDeniedPath = "/manager/login";
co.SlidingExpiration = true;
~~~
| 27.456954 | 341 | 0.715388 | eng_Latn | 0.783233 |
ffa3889a5df098ee5c675828fbcff69a261ccbef | 830 | md | Markdown | README.md | sshaman1101/what-about-blank | 66df54fcc3d715aafb50ed9be347698b7a4b14d3 | [
"BSD-3-Clause"
] | null | null | null | README.md | sshaman1101/what-about-blank | 66df54fcc3d715aafb50ed9be347698b7a4b14d3 | [
"BSD-3-Clause"
] | 1 | 2018-06-16T23:19:26.000Z | 2018-06-17T10:48:38.000Z | README.md | sshaman1101/what-about-blank | 66df54fcc3d715aafb50ed9be347698b7a4b14d3 | [
"BSD-3-Clause"
] | null | null | null | What about blank?
=================
This weekend project aims to create an extension for Google Chrome browser, which
replaces blank page which you see when opening a new tab.
The default blank page is quite boring and useless and I wanna to make it a bit useful for me (and maybe for my colleagues and friends).
Things I want to place on a brand new blank page:
- Github's PRs that needs my attention.
- JIRA tasks assigned to me.
- Weather in three cities that I visit periodically.
- Personal tasks from Wunderlist app (unsorted TODOs and shopping list).
- Local time, sunrise and sunset time.
This project contains two parts: a backend and data-collectors written in Python 3.6 (using aiohttp features),
a frontend part is written with Angular (by @instingt, because I can only make weird, spaghetti-driven jQuery code!).
| 46.111111 | 136 | 0.763855 | eng_Latn | 0.999502 |
ffa55849c626c52c5b9e48de4575d47da451996f | 5,287 | md | Markdown | README.md | 4-alok/flutter-pdf-text | 1d2be2f9aadf939eebfdbd70b0fc9deca8542b20 | [
"MIT"
] | null | null | null | README.md | 4-alok/flutter-pdf-text | 1d2be2f9aadf939eebfdbd70b0fc9deca8542b20 | [
"MIT"
] | null | null | null | README.md | 4-alok/flutter-pdf-text | 1d2be2f9aadf939eebfdbd70b0fc9deca8542b20 | [
"MIT"
] | null | null | null | # PDF Text Plugin
[](https://pub.dev/packages/pdf_text)
[](https://github.com/AlessioLuciani/flutter-pdf-text/network)
[](https://github.com/AlessioLuciani/flutter-pdf-text/stargazers)
[](https://github.com/AlessioLuciani/flutter-pdf-text/blob/master/LICENSE)
This plugin for [Flutter](https://flutter.dev) allows you to read the text content of PDF documents and convert it into strings. It works on iOS and Android. On iOS it uses Apple's [PDFKit](https://developer.apple.com/documentation/pdfkit). On Android it uses Apache's [PdfBox](https://github.com/TomRoush/PdfBox-Android) Android porting.
<p align="center">
<img src="https://raw.githubusercontent.com/AlessioLuciani/flutter-pdf-text/master/example/flutter-pdf-text.gif" alt="Demo Example App" style="margin:auto" width="250" height="550">
</p>
## Getting Started
Add this to your package's `pubspec.yaml` file:
```yaml
dependencies:
pdf_text: ^0.4.0
```
## Usage
Import the package with:
```dart
import 'package:pdf_text/pdf_text.dart';
```
**Create a PDF document instance using a File object:**
```dart
PDFDoc doc = await PDFDoc.fromFile(file);
```
or using a path string:
```dart
PDFDoc doc = await PDFDoc.fromPath(path);
```
or using a URL string:
```dart
PDFDoc doc = await PDFDoc.fromURL(url);
```
Pass a password for encrypted PDF documents:
```dart
PDFDoc doc = await PDFDoc.fromFile(file, password: password);
```
**Read the text of the entire document:**
```dart
String docText = await doc.text;
```
Retrieve the number of pages of the document:
```dart
int numPages = doc.length;
```
**Access a page of the document:**
```dart
PDFPage page = doc.pageAt(pageNumber);
```
**Read the text of a page of the document:**
```dart
String pageText = await page.text;
```
**Read the information of the document:**
```dart
PDFDocInfo info = doc.info;
```
Optionally, you can delete the file of a document when you no longer need it.
This can be useful when you import a PDF document from outside the local
file system (e.g using a URL), since it is automatically stored in the temporary
directory of the app.
Delete the file of a single document:
```dart
doc.deleteFile();
```
or delete all the files of all the documents imported from outside the local
file system:
```dart
PDFDoc.deleteAllExternalFiles();
```
## Functioning
This plugin applies lazy loading for the text contents of the pages. The text is cached page per page. When you request the text of a page for the first time, it is parsed and stored in memory, so that the second access will be faster. Anyway, the text of pages that are not requested is not loaded. This mechanism
allows you not to waste time loading text that you will probably not use. When you request the text content of the entire document, only the pages that have not been loaded yet are then loaded.
## Public Methods
### PDFDoc
| Return | Description |
|---|---|
| PDFPage | **pageAt(int pageNumber)** <br> Gets the page of the document at the given page number. |
| static Future\<PDFDoc> | **fromFile(File file, {String password = ""})** <br> Creates a PDFDoc object with a File instance. Optionally, takes a password for encrypted PDF documents.|
| static Future\<PDFDoc> | **fromPath(String path, {String password = ""})** <br> Creates a PDFDoc object with a file path. Optionally, takes a password for encrypted PDF documents.|
| static Future\<PDFDoc> | **fromURL(String url, {String password = ""})** <br> Creates a PDFDoc object with a url. Optionally, takes a password for encrypted PDF documents.|
| void | **deleteFile()** <br> Deletes the file related to this PDFDoc.<br>Throws an exception if the FileSystemEntity cannot be deleted. |
| static Future | **deleteAllExternalFiles()** <br> Deletes all the files of the documents that have been imported from outside the local file system (e.g. using fromURL). |
## Objects
```dart
class PDFDoc {
int length; // Number of pages of the document
List<PDFPage> pages; // Pages of the document
Future<String> text; // Text of the document
}
class PDFPage {
int number; // Number of the page in the document
Future<String> text; // Text of the page
}
class PDFDocInfo {
String author; // Author string of the document
List<String> authors; // Authors of the document
DateTime creationDate; // Creation date of the document
DateTime modificationDate; // Modification date of the document
String creator; // Creator of the document
String producer; // Producer of the document
List<String> keywords; // Keywords of the document
String title; // Title of the document
String subject; // Subject of the document
}
```
## Contribute
If you have any suggestions, improvements or issues, feel free to contribute to this project.
You can either submit a new issue or propose a pull request. Direct your pull requests into the *dev* branch.
| 34.555556 | 338 | 0.736334 | eng_Latn | 0.407406 |
ffa564af7a741f0df915f773d7bb1f552256b4aa | 1,878 | md | Markdown | _posts/algorithm/2020-05-09-algorithm-Baekjoon-3052.md | HyunjungLee-dev/HyunjungLee-dev.github.io | ac73ceba0c1de1907bdd53bed896a84d81c534ba | [
"MIT"
] | 1 | 2020-01-04T07:06:12.000Z | 2020-01-04T07:06:12.000Z | _posts/algorithm/2020-05-09-algorithm-Baekjoon-3052.md | HyunjungLee-dev/HyunjungLee-dev.github.io | ac73ceba0c1de1907bdd53bed896a84d81c534ba | [
"MIT"
] | null | null | null | _posts/algorithm/2020-05-09-algorithm-Baekjoon-3052.md | HyunjungLee-dev/HyunjungLee-dev.github.io | ac73ceba0c1de1907bdd53bed896a84d81c534ba | [
"MIT"
] | null | null | null | ---
title: "[algorithm]BAEKJOON 백준 3052번 나머지"
comments: true
toc : true
toc_sticky : true
categories:
- algorithm
tags:
- Baekjoon
- C++
- algorithm
---
# Baekjoon Online Judge No.3052
<https://www.acmicpc.net/problem/3052>
## 문제
두 자연수 A와 B가 있을 때, A%B는 A를 B로 나눈 나머지 이다. 예를 들어, 7, 14, 27, 38을 3으로 나눈 나머지는 1, 2, 0, 2이다.
수 10개를 입력받은 뒤, 이를 42로 나눈 나머지를 구한다. 그 다음 서로 다른 값이 몇 개 있는지 출력하는 프로그램을 작성하시오.
## 입력
첫째 줄부터 열번째 줄 까지 숫자가 한 줄에 하나씩 주어진다. 이 숫자는 1,000보다 작거나 같고, 음이 아닌 정수이다.
## 출력
첫째 줄에, 42로 나누었을 때, 서로 다른 나머지가 몇 개 있는지 출력한다.
## 예제 입력 1
```
39
40
41
42
43
44
82
83
84
85
```
## 예제 출력 1
```
6
```
## 힌트
39, 40, 41, 42, 43, 44, 82, 83, 84, 85를 42로 나눈 나머지는 39, 40, 41, 0, 1, 2, 40, 41, 0, 1이다. 서로 다른 값은 모두 6개가 있다.
## 코드
### C++
처음 이 문제를 해결하기 위해서 생각했던 방법은 입력받는 숫자가 10개이니 `arr[10]`에 for 문을 통해 입력받은 후 `%= 42`를 해서 값을 입력받은 해당 인덱스에 나머지 값을 바로 넣어준 후 중복된 수를 제외하는 방식으로 count를 하면 될 것이라는 생각으로 코드를 작성했고 그 결과 예제와는 같은 값이 나왔지만 예외가 발생하고 채점 결과 또한 틀렸습니다가 나왔다.
2577과 비슷한 유형이라고 하기에 그와 같이 접근해보기로 하였다 42의 나머지 값은 0~41까지 나오게 되므로 사이즈 42의 배열을 0으로 초기화하여 선언한다. 나머지의 값을 인덱스로 하여 해당 배열 인덱스에 1을 넣어주고 그 값들을 더 하면 될 것이라는 생각을 하였고 밑의 코드와 같은 방식으로 문제 해결이 가능했다.
```c++
#include <iostream>
using namespace std;
int main()
{
int arr[42] = { 0 };
int num, count = 0;
for (int i = 0; i < 10; i++)
{
cin >> num;
arr[num % 42] = 1;
}
for (int i = 0; i < 42; i++)
{
count += arr[i];
}
cout << count << '\n';
return 0;
}
```
다른 방법이 없을까 알아보던 중 for문을 한번 사용하여 문제를 해결한 밑의 코드를 찾게 되었다.
```c++
#include <iostream>
using namespace std;
int main()
{
int num, arr[42] = { 0 };
int count = 0;
for (int i = 0; i < 10; i++)
{
cin >> num;
if (!arr[num % 42]++)
count++;
}
cout << count << '\n';
return 0;
}
```
> 참조 : https://aorica.tistory.com/41
배열에 논리 연산자를 사용해본 적이 없기 때문에 생각해보지 못한 코드였고 for 문을 한 번만 사용하여 코드의 길이도 줄일 수 있었다. 사용하는 메모리에는 차이가 없기 때문에 상황에 따라 선택해서 사용할 수 있을 것 같다.
| 15.781513 | 212 | 0.595847 | kor_Hang | 1.00001 |
ffa59ef6f2670dd0c1263cd0127c02bdebc8a248 | 1,745 | md | Markdown | docs/visual-basic/misc/bc31196.md | acidburn0zzz/docs.fr-fr | 5fdf04b7027f8b7d749c2180da4b99068e1f44ee | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-04-11T17:00:02.000Z | 2019-04-11T17:00:02.000Z | docs/visual-basic/misc/bc31196.md | Acidburn0zzz/docs.fr-fr | 5fdf04b7027f8b7d749c2180da4b99068e1f44ee | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/visual-basic/misc/bc31196.md | Acidburn0zzz/docs.fr-fr | 5fdf04b7027f8b7d749c2180da4b99068e1f44ee | [
"CC-BY-4.0",
"MIT"
] | 1 | 2022-02-23T14:59:20.000Z | 2022-02-23T14:59:20.000Z | ---
title: Les littéraux XML et les propriétés d’axe XML ne sont pas disponibles pendant cette session de débogage car ils ne sont pas utilisés dans cet assembly
ms.date: 07/20/2015
f1_keywords:
- vbc31196
- bc31196
helpviewer_keywords:
- BC31196
ms.assetid: 36be5c92-dd6b-41d4-894a-2bd71d772092
ms.openlocfilehash: c009509c7e961f19ad01a75be2a90375cf9c25b9
ms.sourcegitcommit: 5c1abeec15fbddcc7dbaa729fabc1f1f29f12045
ms.translationtype: MT
ms.contentlocale: fr-FR
ms.lasthandoff: 03/15/2019
ms.locfileid: "58047868"
---
# <a name="xml-literals-and-xml-axis-properties-are-not-available-during-this-debugging-session-because-they-are-not-used-in-this-assembly"></a>Les littéraux XML et les propriétés d’axe XML ne sont pas disponibles pendant cette session de débogage car ils ne sont pas utilisés dans cet assembly
Un littéral XML ou une propriété d’axe XML a été référencée dans le **espion** ou **immédiat** fenêtre pendant une session de débogage dans laquelle le langage XML en Visual Basic les fonctionnalités ne sont pas disponibles. C’est le cas pour un assembly qui n’utilise pas le code XML dans les fonctionnalités de Visual Basic ou est une version Release.
**ID d’erreur :** BC31196
## <a name="to-correct-this-error"></a>Pour corriger cette erreur
- Démarrez une nouvelle session de débogage à l’aide de la version Debug de l’assembly.
## <a name="see-also"></a>Voir aussi
- [Débogage de votre Application Visual Basic](../../visual-basic/developing-apps/debugging.md)
- [Littéraux XML](../../visual-basic/language-reference/xml-literals/index.md)
- [Propriétés d’axe XML](../../visual-basic/language-reference/xml-axis/index.md)
- [XML](../../visual-basic/programming-guide/language-features/xml/index.md)
| 54.53125 | 355 | 0.77192 | fra_Latn | 0.814145 |
ffa5e9dc974ca78b8a8a56ce4c0bb68a6382953e | 9,102 | md | Markdown | reference/6/Microsoft.PowerShell.Management/Remove-ItemProperty.md | guyisit/PowerShell-Docs | 2b0d31305a2343ead5cce1c0ecb3adddac29e343 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | reference/6/Microsoft.PowerShell.Management/Remove-ItemProperty.md | guyisit/PowerShell-Docs | 2b0d31305a2343ead5cce1c0ecb3adddac29e343 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | reference/6/Microsoft.PowerShell.Management/Remove-ItemProperty.md | guyisit/PowerShell-Docs | 2b0d31305a2343ead5cce1c0ecb3adddac29e343 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
ms.date: 5/14/2019
schema: 2.0.0
locale: en-us
keywords: powershell,cmdlet
online version: http://go.microsoft.com/fwlink/?LinkId=821617
external help file: Microsoft.PowerShell.Commands.Management.dll-Help.xml
title: Remove-ItemProperty
---
# Remove-ItemProperty
## SYNOPSIS
Deletes the property and its value from an item.
## SYNTAX
### Path (Default)
```
Remove-ItemProperty [-Path] <String[]> [-Name] <String[]> [-Force] [-Filter <String>] [-Include <String[]>]
[-Exclude <String[]>] [-Credential <PSCredential>] [-InformationAction <ActionPreference>]
[-InformationVariable <String>] [-WhatIf] [-Confirm] [<CommonParameters>]
```
### LiteralPath
```
Remove-ItemProperty -LiteralPath <String[]> [-Name] <String[]> [-Force] [-Filter <String>]
[-Include <String[]>] [-Exclude <String[]>] [-Credential <PSCredential>]
[-WhatIf] [-Confirm] [<CommonParameters>]
```
## DESCRIPTION
The `Remove-ItemProperty` cmdlet deletes a property and its value from an item.
You can use it to delete registry values and the data that they store.
## EXAMPLES
### Example 1: Delete a registry value
This command deletes the "SmpProperty" registry value, and its data, from the "SmpApplication"
subkey of the `HKEY_LOCAL_MACHINE\Software` registry key.
```powershell
Remove-ItemProperty -Path "HKLM:\Software\SmpApplication" -Name "SmpProperty"
```
Because the command is issued from a file system drive (`PS C:\>`), it includes the fully qualified
path of the "SmpApplication" subkey, including the drive, `HKLM:`, and the "Software" key.
### Example 2: Delete a registry value from the HKCU location
These commands delete the "Options" registry value, and its data, from the "MyApp" subkey of
"HKEY_CURRENT_USER\Software\MyCompany".
```
PS C:\> Set-Location HKCU:\Software\MyCompany\MyApp
PS HKCU:\Software\MyCompany\MyApp> Remove-ItemProperty -Path . -Name "Options" -Confirm
```
The first command uses the `Set-Location` cmdlet to change the current location to the
**HKEY_CURRENT_USER** drive (`HKCU:`) and the `Software\MyCompany\MyApp` subkey.
The second command uses `Remove-ItemProperty` to remove the "Options" registry value, and its data,
from the "MyApp" subkey. Because **Path** is required, the command uses a dot (`.`) to indicate the
current location. The **Confirm** parameter requests a user prompt before deleting the value.
### Example 3: Remove a registry value by using the pipeline
This command deletes the "NoOfEmployees" registry value, and its data, from the
`HKLM\Software\MyCompany` registry key.
```powershell
Get-Item -Path HKLM:\Software\MyCompany | Remove-ItemProperty -Name NoOfEmployees
```
The command uses the `Get-Item` cmdlet to get an item that represents the registry key.
It uses a pipeline operator (`|`) to send the object to `Remove-ItemProperty`.
Then, it uses the **Name** parameter of `Remove-ItemProperty` to specify the name of the registry
value.
## PARAMETERS
### -Credential
> [!NOTE]
> This parameter is not supported by any providers installed with PowerShell.
> To impersonate another user, or elevate your credentials when running this cmdlet,
> use [Invoke-Command](../Microsoft.PowerShell.Core/Invoke-Command.md).
```yaml
Type: PSCredential
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: Current user
Accept pipeline input: True (ByPropertyName)
Accept wildcard characters: False
```
### -Exclude
Specifies, as a string array, an item or items that this cmdlet excludes in the operation. The value
of this parameter qualifies the **Path** parameter. Enter a path element or pattern, such as
`*.txt`. Wildcard characters are permitted. The **Exclude** parameter is effective only when the
command includes the contents of an item, such as `C:\Windows\*`, where the wildcard character
specifies the contents of the `C:\Windows` directory.
```yaml
Type: String[]
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: True
```
### -Filter
Specifies a filter to qualify the **Path** parameter. The [FileSystem](../Microsoft.PowerShell.Core/About/about_FileSystem_Provider.md)
provider is the only installed PowerShell provider that supports the use of filters. You can find
the syntax for the **FileSystem** filter language in [about_Wildcards](../Microsoft.PowerShell.Core/About/about_Wildcards.md).
Filters are more efficient than other parameters, because the provider applies them when the cmdlet
gets the objects rather than having PowerShell filter the objects after they are retrieved.
```yaml
Type: String
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: True
```
### -Force
Forces the cmdlet to remove a property of an object that cannot otherwise be accessed by the user.
Implementation varies from provider to provider.
For more information, see [about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md).
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: False
Accept pipeline input: False
Accept wildcard characters: False
```
### -Include
Specifies, as a string array, an item or items that this cmdlet includes in the operation. The value
of this parameter qualifies the **Path** parameter. Enter a path element or pattern, such as
`"*.txt"`. Wildcard characters are permitted. The **Include** parameter is effective only when the
command includes the contents of an item, such as `C:\Windows\*`, where the wildcard character
specifies the contents of the `C:\Windows` directory.
```yaml
Type: String[]
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: True
```
### -LiteralPath
Specifies a path to one or more locations. The value of **LiteralPath** is used exactly as it is
typed. No characters are interpreted as wildcards. If the path includes escape characters, enclose
it in single quotation marks. Single quotation marks tell PowerShell not to interpret any characters
as escape sequences.
For more information, see [about_Quoting_Rules](../Microsoft.Powershell.Core/About/about_Quoting_Rules.md).
```yaml
Type: String[]
Parameter Sets: LiteralPath
Aliases: PSPath
Required: True
Position: Named
Default value: None
Accept pipeline input: True (ByPropertyName)
Accept wildcard characters: False
```
### -Name
Specifies the names of the properties to remove.
Wildcard characters are permitted.
```yaml
Type: String[]
Parameter Sets: (All)
Aliases: PSProperty
Required: True
Position: 1
Default value: None
Accept pipeline input: True (ByPropertyName)
Accept wildcard characters: True
```
### -Path
Specifies the path of the item whose properties are being removed.
Wildcard characters are permitted.
```yaml
Type: String[]
Parameter Sets: Path
Aliases:
Required: True
Position: 0
Default value: None
Accept pipeline input: True (ByPropertyName, ByValue)
Accept wildcard characters: True
```
### -Confirm
Prompts you for confirmation before running the cmdlet.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
Required: False
Position: Named
Default value: False
Accept pipeline input: False
Accept wildcard characters: False
```
### -WhatIf
Shows what would happen if the cmdlet runs.
The cmdlet is not run.
```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
Required: False
Position: Named
Default value: False
Accept pipeline input: False
Accept wildcard characters: False
```
### CommonParameters
This cmdlet supports the common parameters: `-Debug`, `-ErrorAction`, `-ErrorVariable`,
`-InformationAction`, `-InformationVariable`, `-OutVariable`, `-OutBuffer`, `-PipelineVariable`,
`-Verbose`, `-WarningAction`, and `-WarningVariable`. For more information, see
[about_CommonParameters](../Microsoft.PowerShell.Core/About/about_CommonParameters.md).
## INPUTS
### System.String
You can pipe a string that contains a path, but not a literal path, to this cmdlet.
## OUTPUTS
### None
This cmdlet does not return any output.
## NOTES
- In the PowerShell Registry provider, registry values are considered to be properties of a registry
key or subkey. You can use the **ItemProperty** cmdlets to manage these values.
- `Remove-ItemProperty` is designed to work with the data exposed by any provider. To list the
providers available in your session, type `Get-PSProvider`. For more information, see
[about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md).
## RELATED LINKS
[Get-Item](Get-Item.md)
[Clear-ItemProperty](Clear-ItemProperty.md)
[Copy-ItemProperty](Copy-ItemProperty.md)
[Get-ItemProperty](Get-ItemProperty.md)
[Move-ItemProperty](Move-ItemProperty.md)
[New-ItemProperty](New-ItemProperty.md)
[Remove-Item](Remove-Item.md)
[Rename-ItemProperty](Rename-ItemProperty.md)
[Set-ItemProperty](Set-ItemProperty.md)
[Set-Location](Set-Location.md)
[about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md)
| 28.35514 | 135 | 0.76214 | eng_Latn | 0.917424 |
ffa6e4cfa359d18f13eeefecfbbb18cdef7b0b30 | 3,692 | md | Markdown | _posts/2016-02-21-sublime-linter.md | kylebebak/kylebebak.github.io | 052cf14904d9991d5e035e6b8300c0231d839988 | [
"MIT"
] | 1 | 2017-11-26T21:56:11.000Z | 2017-11-26T21:56:11.000Z | _posts/2016-02-21-sublime-linter.md | kylebebak/kylebebak.github.io | 052cf14904d9991d5e035e6b8300c0231d839988 | [
"MIT"
] | null | null | null | _posts/2016-02-21-sublime-linter.md | kylebebak/kylebebak.github.io | 052cf14904d9991d5e035e6b8300c0231d839988 | [
"MIT"
] | 2 | 2016-07-11T16:05:40.000Z | 2020-04-16T01:51:44.000Z | ---
layout: post
comments: true
title: "SublimeLinter for Code Linting in Any Language"
categories: code sublime-text
tags: [sublime-text, sublime-linter, linting, software-design]
---
[SublimeLinter](https://github.com/SublimeLinter/SublimeLinter3) is a code linting framework for Sublime Text. Its design is straightforward and very effective, and I feel like writing about it.
>In [background mode](https://sublimelinter.readthedocs.org/en/latest/lint_modes.html#background), lint requests are generated for every modification of a view, as well as on file loading and saving... Remember that background lint requests only trigger a lint if the associated view has not been modified when the request is pulled off the queue...
On each modification of a view, a lint request is enqueued. After a delay, the request gets pulled off the queue. If no other requests were added to the queue during the delay, i.e. the current request is the only request on the queue when it gets pulled off, then it triggers a lint. This debounces linting requests, like in the [auto-save](https://github.com/jamesfzhang/auto-save) plugin I contribute to. The lint looks at the syntax of the file, and runs all of the SublimeLinter __linters__ assigned to the syntax of the view. Each __linter__, in turn, calls the command line executable it uses for linting (`eslint`, `javac -Xlint`, `pyflakes`, `ruby -wc`, ...), retrieves line-specific warnings and errors, and returns them to SublimeLinter. SublimeLinter finishes up by aggregating the errors and displaying them in the gutter. Here's a [detailed description](https://sublimelinter.readthedocs.org/en/latest/usage.html#usage-linting) from the excellent documentation.
The SublimeLinter __linters__ I mentioned above are separate packages that must be installed with Package Control. SublimeLinter manages delegation details, like displaying errors and managing the queue of lint requests, but does no linting on its own. If you were paying attention above, you noticed that __linters__ don't lint either; they delegate lint requests to their command line linter of choice.
This modular design makes SublimeLinter easy to extend. To add linting for a new syntax, e.g. [ES6 JS or JSX](./eslint), you don't even touch SublimeLinter. You create a package that calls a linting executable and passes the results to SublimeLinter, basing your code on the many existing linting packages.
SublimeLinter settings are specified in `User/SublimeLinter.sublime-settings` under your packages directory. Here you can change the "debounce" `delay`, the `lint_mode`, configure individual linters, and define a `syntax_map` to make sure your linters are called for files with specialized syntax.
~~~json
{
"user": {
...
"delay": 0.5,
...
"lint_mode": "background",
"linters": {
"eslint": {
"@disable": false,
"args": [],
"excludes": []
}
},
...
"syntax_map": {
"html (django)": "html",
"html (rails)": "html",
"html 5": "html",
"javascript (babel)": "javascript",
"php": "html",
"python django": "python"
},
...
}
}
~~~
I find IDEs clunky and bloated; they're designed for many things, but not for editing text. Text is the raw material of all programs, __which for me is enough to make IDEs an anti-pattern__. Code linting, however, has always been one of their strong points. SublimeLinter gives you industrial strength code linting in a lean, mean text editor, which, if this applies to you, is one more reason to drop your IDE.
| 73.84 | 975 | 0.721018 | eng_Latn | 0.989333 |
ffa72ec4fa9880bc65ec4f1471ba9be974ea6a70 | 1,472 | md | Markdown | tone-analyzer/README.md | saiprabha-sujith/watson-java-sdk | 78a2bf0b8d9d34a8b227ad0f1a54e7a4e7468cdf | [
"Apache-2.0"
] | null | null | null | tone-analyzer/README.md | saiprabha-sujith/watson-java-sdk | 78a2bf0b8d9d34a8b227ad0f1a54e7a4e7468cdf | [
"Apache-2.0"
] | null | null | null | tone-analyzer/README.md | saiprabha-sujith/watson-java-sdk | 78a2bf0b8d9d34a8b227ad0f1a54e7a4e7468cdf | [
"Apache-2.0"
] | null | null | null | # Tone Analyzer
## Installation
##### Maven
```xml
<dependency>
<groupId>com.ibm.watson.developer_cloud</groupId>
<artifactId>tone-analyzer</artifactId>
<version>5.4.0</version>
</dependency>
```
##### Gradle
```gradle
'com.ibm.watson.developer_cloud:tone-analyzer:5.4.0'
```
## Usage
Use the [Tone Analyzer][tone_analyzer] service to get the tone of your email.
```java
ToneAnalyzer service = new ToneAnalyzer("2017-09-21");
service.setUsernameAndPassword("<username>", "<password>");
String text =
"I know the times are difficult! Our sales have been "
+ "disappointing for the past three quarters for our data analytics "
+ "product suite. We have a competitive data analytics product "
+ "suite in the industry. But we need to do our job selling it! "
+ "We need to acknowledge and fix our sales challenges. "
+ "We can’t blame the economy for our lack of execution! "
+ "We are missing critical sales opportunities. "
+ "Our product is in no way inferior to the competitor products. "
+ "Our clients are hungry for analytical tools to improve their "
+ "business outcomes. Economy has nothing to do with it.";
// Call the service and get the tone
ToneOptions toneOptions = new ToneOptions.Builder()
.html(text)
.build();
ToneAnalysis tone = service.tone(toneOptions).execute();
System.out.println(tone);
```
[tone_analyzer]: https://console.bluemix.net/docs/services/tone-analyzer/index.html
| 30.666667 | 83 | 0.705163 | eng_Latn | 0.876359 |
ffa7cb40f89c239e79e41ffbfe3d5118a3c4613b | 3,189 | md | Markdown | docs/sharepoint/sharepoint-project-item-schema-reference.md | akiomik/visualstudio-docs.ja-jp | baf3fd9b8ec3adc813fb9ff2c07a1ec57ccea85b | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/sharepoint/sharepoint-project-item-schema-reference.md | akiomik/visualstudio-docs.ja-jp | baf3fd9b8ec3adc813fb9ff2c07a1ec57ccea85b | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/sharepoint/sharepoint-project-item-schema-reference.md | akiomik/visualstudio-docs.ja-jp | baf3fd9b8ec3adc813fb9ff2c07a1ec57ccea85b | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: SharePoint プロジェクト項目スキーマリファレンス |Microsoft Docs
description: Sharepointprojectitem.spdata ファイルの内容を検証するために使用される、SharePoint プロジェクト項目の XML スキーマ参照 (ProjectItemModelSchema) の概要について説明します。
ms.custom: SEO-VS-2020
ms.date: 02/02/2017
ms.topic: conceptual
dev_langs:
- VB
- CSharp
helpviewer_keywords:
- FeatureProperty element
- SafeControls element
- SafeControl element
- .spdata files
- ExtensionData element
- FeatureProperties element
- ProjectOutputFile element
- Files element
- ProjectItemFolder element
- ProjectItemFile element
- ExtensionDataItem element
- ProjectItem element
author: John-Hart
ms.author: johnhart
manager: jmartens
ms.workload:
- office
ms.openlocfilehash: 466bc68ca002914b64698d7cd87f98ff276bfc0e
ms.sourcegitcommit: ae6d47b09a439cd0e13180f5e89510e3e347fd47
ms.translationtype: MT
ms.contentlocale: ja-JP
ms.lasthandoff: 02/08/2021
ms.locfileid: "99892282"
---
# <a name="sharepoint-project-item-schema-reference"></a>SharePoint プロジェクト項目スキーマのリファレンス
Visual Studio では、SharePoint プロジェクト項目スキーマを使用して、 *sharepointprojectitem.spdata* ファイルの内容を検証します。 *Sharepointprojectitem.spdata* ファイルは、SharePoint プロジェクトアイテムの内容と動作を指定します。 SharePoint プロジェクト項目の内容の詳細については、「 [sharepoint プロジェクト項目の項目テンプレートとプロジェクトテンプレートを作成](../sharepoint/creating-item-templates-and-project-templates-for-sharepoint-project-items.md)する」を参照してください。
SharePoint プロジェクト項目スキーマは ProjectItemModelSchema という名前で、既定では% Program Files (x86)% \ Microsoft Visual Studio 11.0 \ xmlschema にインストールされます。
ルート要素は [ProjectItem](../sharepoint/projectitem-element.md) 要素です。 次の表では、スキーマで定義されているすべての要素について説明します。
|要素|説明|
|-------------|-----------------|
|[ExtensionData](../sharepoint/extensiondata-element.md)|SharePoint プロジェクトアイテムに関連付けられているカスタムデータアイテムのコレクションを表します。|
|[ExtensionDataItem](../sharepoint/extensiondataitem-element.md)|SharePoint プロジェクト項目に関連付けられているカスタムデータ項目を表します (キー/値の形式)。 キーと値は、どちらも文字列である必要があります。|
|[FeatureProperties](../sharepoint/featureproperties-element.md)|SharePoint に配置されるときにフィーチャーに含まれるプロパティ値のコレクションを表します。 フィーチャーが配置されると、コード内のプロパティ値にアクセスできるようになります。|
|[FeatureProperty](../sharepoint/featureproperty-element.md)|SharePoint に配置されるときにフィーチャーに含まれるカスタムプロパティを表します。 フィーチャーが配置された後、コード内のプロパティにアクセスできます。|
|[[ファイル]](../sharepoint/files-element.md)|フィーチャー要素ファイルやプロジェクトの出力など、SharePoint プロジェクトアイテムと共に配置するファイルを指定します。|
|[ProjectItem](../sharepoint/projectitem-element.md)|SharePoint プロジェクトアイテムを表します。|
|[ProjectItemFile](../sharepoint/projectitemfile-element.md)|SharePoint に配置されるときにプロジェクト項目に含める、フィーチャー要素ファイルなどの SharePoint ファイルを表します。|
|[ProjectItemFolder](../sharepoint/projectitemfolder-element.md)|マップされたフォルダーを表します。|
|[ProjectOutputFile](../sharepoint/projectoutputfile-element.md)|SharePoint に配置されるときにプロジェクト項目に含めるプロジェクトの出力を表します。|
|[SafeControl](../sharepoint/safecontrol-element.md)|SharePoint サイトの任意の ASPX ページで任意のユーザーがアクセスできるようにセキュリティで保護されていると指定された ASPX コントロールまたは Web パーツを表します。|
|[SafeControls](../sharepoint/safecontrols-element.md)|SharePoint サイトの任意の ASPX ページですべてのユーザーがアクセスできるようにセキュリティで保護されたものとして指定された ASPX コントロールおよび Web パーツのコレクションを表します。|
## <a name="see-also"></a>関連項目
- [SharePoint プロジェクト項目の項目テンプレートとプロジェクトテンプレートを作成する](../sharepoint/creating-item-templates-and-project-templates-for-sharepoint-project-items.md)
| 54.982759 | 352 | 0.830041 | yue_Hant | 0.576486 |
ffa8150062a198d806945566a6994825891745f8 | 3,755 | md | Markdown | WindowsServerDocs/administration/windows-commands/start.md | tabithahsia/windowsserverdocs | e2964a803cba1b8037e10d065a076819d61e8dbe | [
"CC-BY-4.0",
"MIT"
] | 1 | 2022-02-01T11:31:12.000Z | 2022-02-01T11:31:12.000Z | WindowsServerDocs/administration/windows-commands/start.md | tabithahsia/windowsserverdocs | e2964a803cba1b8037e10d065a076819d61e8dbe | [
"CC-BY-4.0",
"MIT"
] | null | null | null | WindowsServerDocs/administration/windows-commands/start.md | tabithahsia/windowsserverdocs | e2964a803cba1b8037e10d065a076819d61e8dbe | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-12-20T05:17:06.000Z | 2021-12-20T05:17:06.000Z | ---
title: start
description: "Windows Commands topic for **** - "
ms.custom: na
ms.prod: windows-server
ms.reviewer: na
ms.suite: na
ms.technology: manage-windows-commands
ms.tgt_pltfrm: na
ms.topic: article
ms.assetid: 0173f9b3-5cd7-4edb-b01e-d02193b4fadc
author: coreyp-at-msft
ms.author: coreyp
manager: dongill
ms.date: 10/16/2017
---
# start
Starts a separate Command Prompt window to run a specified program or command.
For examples of how to use this command, see [Examples](#BKMK_examples).
## Syntax
```
start ["<Title>"] [/d <Path>] [/i] [{/min | /max}] [{/separate | /shared}] [{/low | /normal | /high | /realtime | /abovenormal | belownormal}] [/affinity <HexAffinity>] [/wait] [/b {<Command> | <Program>} [<Parameters>]]
```
## Parameters
|Parameter|Description|
|---------|-----------|
|"\<Title>"|Specifies the title to display in the Command Prompt window title bar.|
|/d \<Path>|Specifies the startup directory.|
|/i|Passes the Cmd.exe startup environment to the new Command Prompt window. If **/i** is not specified, the current environment is used.|
|/min \| /max|Specifies to minimize (**/min**) or maximize (**/max**) the new Command Prompt window.|
|/separate \| /shared|Starts 16-bit programs in a separate memory space (**/separate**) or shared memory space (**/shared**). These options are not supported on 64-bit platforms.|
|/low \| /normal \| /high \| /realtime \| /abovenormal \| /belownormal|Starts an application in the specified priority class. Valid priority class values are **/low**, **/normal**, **/high**, **/realtime**, **/abovenormal**, and **/belownormal**.|
|/affinity \<HexAffinity>|Applies the specified processor affinity mask (expressed as a hexadecimal number) to the new application.|
|/wait|Starts an application and waits for it to end.|
|/b|Starts an application without opening a new Command Prompt window. CTRL+C handling is ignored unless the application enables CTRL+C processing. Use CTRL+BREAK to interrupt the application.|
|/b \<Command> \| \<Program>|Specifies the command or program to start.|
|\<Parameters>|Specifies parameters to pass to the command or program.|
|/?|Displays help at the command prompt.|
## Remarks
- You can run nonexecutable files through their file association by typing the name of the file as a command.
- When you run a command that contains the string "CMD" as the first token without an extension or path qualifier, "CMD" is replaced with the value of the COMSPEC variable. This prevents users from picking up **cmd** from the current directory.
- When you run a 32-bit graphical user interface (GUI) application, **cmd** does not wait for the application to quit before returning to the command prompt. This behavior does not occur if you run the application from a command script.
- When you run a command that uses a first token that does not contain an extension, Cmd.exe uses the value of the PATHEXT environment variable to determine which extensions to look for and in what order. The default value for the PATHEXT variable is:
```
.COM;.EXE;.BAT;.CMD
```
Note that the syntax is the same as the PATH variable, with semicolons separating each extension.
- When it searches for an executable file, if there is no match on any extension, **start** checks to see if the name matches a directory name. If it does, **start** opens Explorer.exe on that path.
## <a name="BKMK_examples"></a>Examples
To start the Myapp program at the command prompt and retain use of the current Command Prompt window, type:
```
start myapp
```
To view the **start** command-line help topic in a separate maximized Command Prompt window, type:
```
start /max start /?
```
#### Additional references
[Command-Line Syntax Key](command-line-syntax-key.md)
| 49.407895 | 253 | 0.728895 | eng_Latn | 0.993883 |
ffa8311063c62f15c5de21d0cb763d8e1c8d31b3 | 2,018 | md | Markdown | _texts/o-captain.md | gustinjabriel/gustinjabriel.github.io | 8965790c0ae13852c6fbebd65ca2015ca6227215 | [
"MIT"
] | 246 | 2017-11-19T12:09:42.000Z | 2022-03-25T02:11:16.000Z | _texts/o-captain.md | gustinjabriel/gustinjabriel.github.io | 8965790c0ae13852c6fbebd65ca2015ca6227215 | [
"MIT"
] | 26 | 2017-12-04T22:09:14.000Z | 2022-03-18T01:51:12.000Z | _drafts/o-captain.md | bryantan/bryanstan-site | b30ca7e7a1952e37a81b6d2d4bad3a00630d7856 | [
"MIT"
] | 259 | 2017-11-28T19:49:58.000Z | 2022-03-26T08:19:50.000Z | ---
layout: poem
title: "O Captain! My Captain!"
author: Walt Whitman
editor: Alex Gil
source: Poetry Foundation
---
- O Captain! my Captain! our fearful trip is done;[^fn1]
- The ship has weather’d every rack, the prize we sought is won,
- The port is near, the bells I hear, the people all exulting,
- While follow eyes the steady keel, the vessel grim and daring;
- {:.indent-3}But O heart! heart! heart!
- {:.indent-4}O the bleeding drops of red,
- {:.indent-5}Where on the deck my Captain lies,
- {:.indent-6}Fallen cold and dead.
- O Captain! my Captain! rise up and hear the bells;
- Rise up—for you the flag is flung—for you the bugle[^fn2] trills,
- For you bouquets and ribbon’d wreaths—for you the shores a-crowding,
- For you they call, the swaying mass, their eager faces turning;
- {:.indent-3}Here Captain! dear father!
- {:.indent-4}This arm beneath your head!
- {:.indent-5}It is some dream that on the deck,
- {:.indent-6}You’ve fallen cold and dead.
- My Captain does not answer, his lips are pale and still,[^fn3]
- My father does not feel my arm, he has no pulse nor will,
- The ship is anchor’d safe and sound, its voyage closed and done,
- From fearful trip the victor ship comes in with object won;
- {:.indent-3}Exult O shores, and ring O bells!
- {:.indent-4}But I with mournful tread,
- {:.indent-5}Walk the deck my Captain lies,
- {:.indent-6}Fallen cold and dead.
<br>
---
## Footnotes
[^fn1]:
The author had just landed in La Guardia Airport after the flight captain died. All the passengers stood up to applaud the co-pilot. We have it in good authority that the event in question led Yoko Ono to write her "Letter to John":
> - On a windy day let's go flying
> - There may be no trees to rest on
> - There may be no clouds to ride
> - But we'll have our wings and the wind will be with us
> - That's enough for me, that's enough for me.
{:.poetry}
[^fn2]: The bugle is a small trumpet implicated in the military industrial complex.
[^fn3]: Another footnote. Why not?
| 35.403509 | 233 | 0.710605 | eng_Latn | 0.99882 |
ffa869a5e2f03f65e33549ac4a726dff1cdb39b0 | 2,713 | md | Markdown | src/es/2022-01/05/07.md | Adventech/sabbath-school-lessons | baf65ac98fa7c7bce73e16c263eb0cc1bf0ba62a | [
"MIT"
] | 68 | 2016-10-30T23:17:56.000Z | 2022-03-27T11:58:16.000Z | src/es/2022-01/05/07.md | Adventech/sabbath-school-lessons | baf65ac98fa7c7bce73e16c263eb0cc1bf0ba62a | [
"MIT"
] | 367 | 2016-10-21T03:50:22.000Z | 2022-03-28T23:35:25.000Z | src/es/2022-01/05/07.md | Adventech/sabbath-school-lessons | baf65ac98fa7c7bce73e16c263eb0cc1bf0ba62a | [
"MIT"
] | 109 | 2016-08-02T14:32:13.000Z | 2022-03-31T10:18:41.000Z | ---
title: Para Estudiar y Meditar
date: 28/01/2022
---
Es muy revelador que Pablo, en Hebreos, usara el reposo sabático, y no el dominical, como símbolo de la salvación por la gracia que Dios nos ofrece. El uso del reposo sabático en este sentido implica que aquellos creyentes apreciaban y observaban el sábado. Sin embargo, desde el siglo II d.C. en adelante, encontramos evidencias de un cambio decisivo en la iglesia. La observancia del sábado dejó de ser considerada un símbolo de salvación y, en cambio, se consideraba un símbolo de lealtad al judaísmo y al Antiguo Pacto; algo para evitar. Guardar el sábado se convirtió en el equivalente de “judaizar”. Por ejemplo, Ignacio de Antioquía (alrededor del año 110 d.C.) comentó: “Aquellos que vivieron según el antiguo orden han encontrado la nueva esperanza. Ya no observan el sábado, sino el día del Señor, el día en que nuestra vida resucitó con Cristo y por su muerte” (J. B. Doukhan, Israel and the Church: Two Voices for the Same God [Israel y la iglesia: Dos voces para el mismo Dios], p. 42). Asimismo, Marción ordenó a sus seguidores que ayunaran en sábado como señal de rechazo a los judíos y a su Dios, y Victorino no quiso dar la impresión de que “observaba el sábado de los judíos” (ver Israel and the Church, pp. 41–45). Fue la falta de entendimiento de la observancia del sábado como símbolo de la salvación por gracia lo que llevó a su desaparición en la iglesia cristiana.
“Una vida en Cristo es una vida de reposo. Puede no haber éxtasis de sentimientos, pero habrá una confianza permanente y apacible. Tu esperanza no está en ti; está en Cristo. Tu debilidad está unida a su fortaleza; tu ignorancia, a su sabiduría; tu fragilidad, a su poder eterno. De modo que no debes mirarte a ti mismo, ni dejar que la mente se espacie en el yo, sino mirar a Cristo. Que tu mente se espacie en su amor, en la belleza y la perfección de su carácter. Cristo en su abnegación, Cristo en su humillación, Cristo en su pureza y santidad, Cristo en su incomparable amor; esto es lo que debe contemplar el ser humano. Es amándolo, imitándolo y dependiendo enteramente de él como serás transformado a su semejanza” (CC 60).
**Preguntas para dialogar**
`1. ¿Cuál es la relación entre la observancia del sábado y la justificación por la fe?`
`2. ¿Cuál es la diferencia entre la verdadera observancia del sábado y una observancia legalista del sábado? ¿Cómo podemos no solo conocer la diferencia, sino también experimentar esa diferencia en nuestra vida al guardar el sábado?`---
#### Comentarios Elena G.W
Mi vida hoy, 5 de noviembre, “El escudo de la fe”, p. 323;
Historia de los patriarcas y profetas, “El viaje alrededor de Edom”, p. 447. | 135.65 | 1,388 | 0.773314 | spa_Latn | 0.999151 |
ffa955f853c9e33c866c7a27c160102e7742e51d | 380 | md | Markdown | _posts/2009-06-29-another-site-i-found.md | opensourcecatholic/opensourcecatholic | ca3e095ba3ab8c629a14d2f577c023a437ddccdf | [
"MIT"
] | 36 | 2016-01-02T22:48:46.000Z | 2022-02-28T12:46:32.000Z | _posts/2009-06-29-another-site-i-found.md | opensourcecatholic/opensourcecatholic | ca3e095ba3ab8c629a14d2f577c023a437ddccdf | [
"MIT"
] | 34 | 2016-01-02T22:47:52.000Z | 2021-12-12T03:12:05.000Z | _posts/2009-06-29-another-site-i-found.md | opensourcecatholic/opensourcecatholic | ca3e095ba3ab8c629a14d2f577c023a437ddccdf | [
"MIT"
] | 8 | 2016-01-21T09:08:54.000Z | 2021-11-30T04:48:17.000Z | ---
layout: post
title: Another site I found...
author: catholicservant
nid: 22
comments: true
redirect_from: /forum/topics/22/
created: 1246303868
---
<p>I found this site the other day... <a href="http://geeksandgod.com/">geeksandgod.com/</a> </p>
<p>Some similarities with this site, but it's more Protestant leaning...though I'm sure they're open to some fisheaters.</p>
| 31.666667 | 124 | 0.728947 | eng_Latn | 0.966949 |
ffa9700f7a76a94d629d9bf2188d52d35b41d7fa | 91 | md | Markdown | day10-rust/README.md | jgosmann/aoc2021 | ea507a44d7caeff0f5341946834fb329c87f0536 | [
"Unlicense"
] | null | null | null | day10-rust/README.md | jgosmann/aoc2021 | ea507a44d7caeff0f5341946834fb329c87f0536 | [
"Unlicense"
] | null | null | null | day10-rust/README.md | jgosmann/aoc2021 | ea507a44d7caeff0f5341946834fb329c87f0536 | [
"Unlicense"
] | null | null | null | # Day 10
Pretty trivial with a push-down automaton (stack).
Once more implemented in Rust. | 22.75 | 50 | 0.769231 | eng_Latn | 0.948203 |
ffa9e86c1b523321fe255a1bed715e0c4fbc4c3c | 70 | md | Markdown | README.md | massiveco/tls_exporter | b2e633b48e29a416aa136714c09bd9559da99eea | [
"Apache-2.0"
] | 1 | 2018-07-04T03:50:24.000Z | 2018-07-04T03:50:24.000Z | README.md | massiveco/tls_exporter | b2e633b48e29a416aa136714c09bd9559da99eea | [
"Apache-2.0"
] | null | null | null | README.md | massiveco/tls_exporter | b2e633b48e29a416aa136714c09bd9559da99eea | [
"Apache-2.0"
] | null | null | null | # tls_exporter
Exports the number of days until a certificate expires
| 23.333333 | 54 | 0.828571 | eng_Latn | 0.9989 |
ffaa1f742413d285d5571284983cd43716a09827 | 1,823 | md | Markdown | docs/outlook/mapi/using-macros-for-error-handling.md | MicrosoftDocs/office-developer-client-docs.es-ES | d4568d789fd46de778fdecb250a28fb84b4bf02e | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-05-19T18:52:21.000Z | 2021-04-21T00:13:46.000Z | docs/outlook/mapi/using-macros-for-error-handling.md | MicrosoftDocs/office-developer-client-docs.es-ES | d4568d789fd46de778fdecb250a28fb84b4bf02e | [
"CC-BY-4.0",
"MIT"
] | 3 | 2021-12-08T02:36:34.000Z | 2021-12-08T03:08:40.000Z | docs/outlook/mapi/using-macros-for-error-handling.md | MicrosoftDocs/office-developer-client-docs.es-ES | d4568d789fd46de778fdecb250a28fb84b4bf02e | [
"CC-BY-4.0",
"MIT"
] | 2 | 2018-10-24T20:53:01.000Z | 2019-10-13T18:19:17.000Z | ---
title: Uso de macros para el control de errores
manager: soliver
ms.date: 03/09/2015
ms.audience: Developer
ms.localizationpriority: medium
api_type:
- COM
ms.assetid: 351405ca-b72b-4e9e-bc8e-947344588970
description: 'Última modificación: 09 de marzo de 2015'
ms.openlocfilehash: 0d3c10a167c961dd2dfe8e31313f6b0f5d827abe
ms.sourcegitcommit: a1d9041c20256616c9c183f7d1049142a7ac6991
ms.translationtype: MT
ms.contentlocale: es-ES
ms.lasthandoff: 09/24/2021
ms.locfileid: "59619501"
---
# <a name="using-macros-for-error-handling"></a>Uso de macros para el control de errores
**Se aplica a**: Outlook 2013 | Outlook 2016
Hay varias macros para facilitar el trabajo con valores HRESULT.
Hay dos conjuntos de macros que prueban el error o el éxito: HR_SUCCEEDED y HR_FAILED y SUCCEEDED y FAILED. SUCCEEDED es el mismo que HR_SUCCEEDED y FAILED es el mismo que HR_FAILED.
En este caso, use la macro **ResultFromScode** para establecer la variable HRESULT en el valor HRESULT correspondiente para S_OK.
Las macros usadas con frecuencia se describen brevemente en la tabla siguiente.
|**Macro**|**Descripción**|
|:-----|:-----|
|**MAKE_HRESULT** <br/> |Construye un HRESULT a partir de sus componentes. <br/> |
|**HR_SUCCEEDED** <br/> |Prueba un HRESULT para una condición correcta o de advertencia. <br/> |
|**HR_FAILED** <br/> |Comprueba un HRESULT para una condición de error. <br/> |
|**HRESULT_CODE** <br/> |Extrae la parte del código de error del HRESULT. <br/> |
|**HRESULT_FACILITY** <br/> |Extrae la instalación del HRESULT. <br/> |
|**HRESULT_SEVERITY** <br/> |Extrae el bit de gravedad de SEVERITY. <br/> |
|**SUCCEEDED** <br/> |Prueba un HRESULT para una condición correcta o de advertencia. <br/> |
|**ERROR** <br/> |Comprueba un HRESULT para una condición de error. <br/> |
| 41.431818 | 182 | 0.734504 | spa_Latn | 0.884666 |
ffaa3afc8d8beae690aa2fc51ef74ae29c2e75b8 | 2,308 | md | Markdown | README.md | linwe2012/media-shack | fbc64c40c3b5fafb0a63d352e9254cf55cff2492 | [
"MIT"
] | 3 | 2019-09-02T14:41:37.000Z | 2020-04-07T07:26:20.000Z | README.md | alexdevero/electron-react-typescript-webpack-boilerplate | 498bee7e63f8a3592caf9deebfb21ee65296977d | [
"MIT"
] | 4 | 2021-01-28T20:12:15.000Z | 2022-02-26T17:22:03.000Z | README.md | linwe2012/media-shack | fbc64c40c3b5fafb0a63d352e9254cf55cff2492 | [
"MIT"
] | 1 | 2019-12-10T14:47:59.000Z | 2019-12-10T14:47:59.000Z | <!-- <p align="center">
<img src="https://cdn.rawgit.com/alexdevero/electron-react-typescript-webpack-boilerplate/master/docs/images/electron-react-typescript-webpack-boilerplate.png" width="135" align="center">
<br>
<br>
</p> -->
<p align="center">
<a href="https://david-dm.org/alexdevero/electron-react-typescript-webpack-boilerplate"><img alt="Dependency Status" src="https://david-dm.org/alexdevero/electron-react-typescript-webpack-boilerplate.svg?style=flat"></a>
<a href="https://david-dm.org/alexdevero/electron-react-typescript-webpack-boilerplate?type=dev"><img alt="devDependency Status" src="https://david-dm.org/alexdevero/electron-react-typescript-webpack-boilerplate/dev-status.svg?style=flat"></a>
<a href="http://opensource.org/licenses/MIT"><img alt="MIT License" src="https://img.shields.io/npm/l/express.svg"></a>
</p>
<p align="center">
<a href="https://alexdevero.com"><img alt="Built by DEVERO" src="https://img.shields.io/badge/built%20by-DEVERO-brightgreen.svg?colorB=d30320"></a>
<a href="https://github.com/alexdevero/electron-react-typescript-webpack-boilerplate/releases"><img alt="Current release" src="https://img.shields.io/github/release/alexdevero/electron-react-typescript-webpack-boilerplate.svg"></a>
</p>
## Minimal Electron, React, TypeScript and Webpack boilerplate
Minimal Electron, React, TypeScript and Webpack boilerplate to help you get started with building your next awesome electron app.
### Table of contents
* [Install](#install)
* [Usage](#usage)
* [Code of Conduct](#code-of-conduct)
* [License](#license)
### Install
#### Clone this repo
```
git clone https://github.com/alexdevero/electron-react-typescript-webpack-boilerplate.git
```
#### Install dependencies
```
npm install
```
or
```
yarn
```
### Usage
#### Run the app
```
npm run start
```
or
```
yarn start
```
#### Build the app (automatic)
```
npm run package
```
or
```
yarn package
```
#### Build the app (manual)
```
npm run build
```
or
```
yarn build
```
#### Test the app (after `npm run build` || `yarn run build`)
```
npm run prod
```
```
yarn prod
```
### Code of Conduct
[Contributor Code of Conduct](code-of-conduct.md). By participating in this project you agree to abide by its terms.
### License
MIT © [Alex Devero](https://alexdevero.com).
| 24.553191 | 245 | 0.707539 | eng_Latn | 0.252119 |
ffaac0c38e6517854015e72b8dbb0643c7142293 | 2,348 | md | Markdown | readme.md | brunodsazevedo/ignite-challenges-2 | a5bc075a3d8cbb5da8a97560c09bfda29a0d5eb4 | [
"MIT"
] | null | null | null | readme.md | brunodsazevedo/ignite-challenges-2 | a5bc075a3d8cbb5da8a97560c09bfda29a0d5eb4 | [
"MIT"
] | null | null | null | readme.md | brunodsazevedo/ignite-challenges-2 | a5bc075a3d8cbb5da8a97560c09bfda29a0d5eb4 | [
"MIT"
] | null | null | null | # **Ignite Challenges - #2**
### Desafio do curso Ignite - Rocketseat
<br>
Este repositório foi um desafio realizado pela corporação Rocketseat com intuito de firmar conhecimentos e fundamentos de componentização utilizando ReactJS
A aplicação é um sistema de serviço de streaming de séries e filmes conforme imagem ilustrada abaixo:
## **Contexto do desafio**
Observando o código original, todo código HTML da aplicação estava sendo feita dentro do arquivo `App.tsx`. Por mais que no momento o código em questão esteja pequeno, é preciso avaliar a questão de novas features, ficará cada vez mais dificil dar manutenção ao código.
## **Objetivo**
O objetivo desse desafio é identificar o que pode ser componentizado no momento para deixar a aplicação com um código limpo e escalável.
Analisando o código e a aplicação, foi possível detectar os seguintes elementos a serem componentizados:
<ul>
<li><strong>Sidebar: </strong>conteúdo que lista os botões de gênero de filmes</li>
<li><strong>Content: </strong>conteúdo que lista os filmes de acordo com o gênero selecionado</li>
</ul>
Foi realizado então a componentização dos elementos, possibilitando assim mais escalabilidade na aplicação e um código limpo.
## **Instalação das dependencias**
Antes de rodar a aplicação deverá ter instalado e configurado previamente o <a href="https://nodejs.org/en/">NodeJS</a> e <a href="https://yarnpkg.com/">Yarn</a>.
Para instalar as dependências do projeto, digite a linha de comando abaixo:
`$ yarn`
## Executando a aplicação
A aplicação possui um Fake API utilizando MirageJS para listar os filmes e gêneros que serão exibidos em tela.
Execute o servidor fake para consumir a API Fake:
`$yarn server`
E logo em seguida, execute em outro terminal o comando para executar o frontent da aplicação:
`$ yarn dev`
No navegador, abra a rota http://localhost:8080 e será exibido a aplicação com a melhoria dos elementos componentizados.
https://user-images.githubusercontent.com/58368716/154701739-029843d4-1235-40fa-a4d2-fdc57aede14b.mp4
Desafio concluído com sucesso! :)
| 35.575758 | 269 | 0.778535 | por_Latn | 0.999512 |
ffaac768e458a7ba37f5037452d900fadb306290 | 5,228 | md | Markdown | pages/content/amp-dev/documentation/guides-and-tutorials/start/visual_story/create_cover_page@zh_CN.md | machal/docs | 6a63453ae3b296ad485870a3ab15a8bf07a7becd | [
"Apache-2.0"
] | 10 | 2018-07-27T12:13:59.000Z | 2019-02-09T16:54:01.000Z | pages/content/amp-dev/documentation/guides-and-tutorials/start/visual_story/create_cover_page@zh_CN.md | machal/docs | 6a63453ae3b296ad485870a3ab15a8bf07a7becd | [
"Apache-2.0"
] | 140 | 2018-07-25T17:20:43.000Z | 2019-03-06T17:33:00.000Z | pages/content/amp-dev/documentation/guides-and-tutorials/start/visual_story/create_cover_page@zh_CN.md | machal/docs | 6a63453ae3b296ad485870a3ab15a8bf07a7becd | [
"Apache-2.0"
] | 3 | 2018-07-25T13:52:29.000Z | 2019-07-05T09:21:22.000Z | ---
$title: 创建封面页
---
AMP 故事内的网页由 `<amp-story-page>` 组件表示。一个 [`amp-story`]({{g.doc('/content/amp-dev/documentation/components/reference/amp-story.md', locale=doc.locale).url.path}}) 中可包含一个或多个 `<amp-story-page>` 组件，以用于呈现故事的各个画面。您按文档顺序指定的第一页即是故事中显示的第一页。
若想创建故事网页，请将 `<amp-story-page>` 元素**添加**为 [`amp-story`]({{g.doc('/content/amp-dev/documentation/components/reference/amp-story.md', locale=doc.locale).url.path}}) 的子级。为该网页**分配**一个唯一 ID。对于我们的第一页（即封面页），我们不妨分配唯一 ID `cover`：
```html hl_lines="6 7"
<amp-story standalone
title="Joy of Pets"
publisher="AMP tutorials"
publisher-logo-src="assets/AMP-Brand-White-Icon.svg"
poster-portrait-src="assets/cover.jpg">
<amp-story-page id="cover">
</amp-story-page>
</amp-story>
```
现在，我们已为封面页搭建好了“外壳”，但我们的故事仍是无效的。在此网页内，我们需要指定至少 1 个**图层**。
{{ image('/static/img/docs/tutorials/amp_story/cover_layers.png', 416, 679, alt='此封面页有 2 个图层', align='right third' ) }}
## 网页中的图层
与图形中的图层一样，您可在 AMP 故事网页中使用图层来创建视觉效果。图层是相互堆叠的，因此，第一个图层是最底层，第二个图层在第一个图层之上，以此类推。
我们的封面页实际上是由 2 个图层组成：
* **第 1 个图层**：一张用作背景幕的图片
* **第 2 个图层**：故事的标题和署名行
### 创建第 1 个图层
让我们向封面页添加第 1 个图层。该图层包含一张会填满整个屏幕的图片。
将 `<amp-story-grid-layer>` 元素添加为 `<amp-story-page>` 的子级，即可创建该图层。由于我们想让该图片填满整个屏幕，因此需要为 `amp-story-grid-layer` 指定 `template="fill"` 属性。在该图层中，为 `cover.jpg` 文件添加 [`amp-img`]({{g.doc('/content/amp-dev/documentation/components/reference/amp-img.md', locale=doc.locale).url.path}}) 元素，并确保它是自适应元素（即 `layout="responsive"`）且图片尺寸为 720 x 1280 像素。我们的这个图层会如下所示：
```html hl_lines="2 3 4 5 6 7"
<amp-story-page id="cover">
<amp-story-grid-layer template="fill">
<amp-img src="assets/cover.jpg"
width="720" height="1280"
layout="responsive">
</amp-img>
</amp-story-grid-layer>
</amp-story-page>
```
我们来看看该网页的显示效果。在您的浏览器中打开该网页：<a href="http://localhost:8000/pets.html">http://localhost:8000/pets.html</a>。
它看起来应该会如下所示：
{{ image('/static/img/docs/tutorials/amp_story/pg0_layer1.jpg', 720, 1280, align='center third' ) }}
### 创建第 2 个图层
好了，我们已经有背景幕了，但现在需要创建第 2 个图层，该图层应位于背景幕之上且包含我们的标题和署名行。添加第 2 个图层时，我们要执行的操作与添加第 1 个图层时相同，但这次要改用 **`vertical`** 模板（而不使用 `fill` 模板）。不过，在进一步操作之前，让我们先来了解一下各种模板以及如何在 `<amp-story-grid-layer>` 中摆放 AMP 和 HTML 元素。
#### 使用模板摆放元素
`<amp-story-grid-layer>` 元素会将其子级元素摆放在网格（基于 [CSS 网格](https://www.w3.org/TR/css-grid-1/)）中。若想指明您希望如何摆放这些子级元素，您需要指定以下布局模板之一：
<table class="noborder">
<tr>
<td colspan="2"><h5 id="fill">模板：Fill</h5></td>
</tr>
<tr>
<td width="65%"><strong>fill</strong> 模板会使用该图层中的第一个子级元素填满屏幕。但该图层中的任何其他子级元素都不会显示。
<p>fill 模板非常适用于添加背景内容（包括图片和视频）。</p>
<code class="nopad"><pre><amp-story-grid-layer template="fill">
<amp-img src="dog.png"
width="720" height="1280"
layout="responsive">
</amp-img>
</amp-story-grid-layer></pre></code>
</td>
<td>
{{ image('/static/img/docs/tutorials/amp_story/layer-fill.png', 216, 341) }}
</td>
</tr>
<tr>
<td colspan="2"><h5 id="vertical">模板：Vertical</h5></td>
</tr>
<tr>
<td width="65%"><strong>vertical</strong> 模板会沿着 y 轴放置子级元素。这些元素会与屏幕顶部对齐，并会沿着 x 轴占据整个屏幕。
<p>当您想沿垂直方向一个紧挨着一个地堆叠元素时，vertical 模板堪称理想之选。</p>
<code class="nopad"><pre><amp-story-grid-layer template="vertical">
<p>element 1</p>
<p>element 2</p>
<p>element 3</p>
</amp-story-grid-layer></pre></code>
</td>
<td>{{ image('/static/img/docs/tutorials/amp_story/layer-vertical.png', 216, 341) }}
</td>
</tr>
<tr>
<td colspan="2"><h5 id="horizontal">模板：Horizontal</h5></td>
</tr>
<tr>
<td width="65%"><strong>horizontal</strong> 模板会沿着 x 轴放置子级元素。这些元素会与屏幕起始位置对齐，并会沿着 y 轴占据整个屏幕。
<p>当您想沿水平方向一个紧挨着一个地堆叠元素时，horizontal 模板无疑是不错的选择。</p>
<code class="nopad"><pre><amp-story-grid-layer template="horizontal">
<p>element 1</p>
<p>element 2</p>
<p>element 3</p>
</amp-story-grid-layer></pre></code>
</td>
<td>
{{ image('/static/img/docs/tutorials/amp_story/layer-horizontal.png', 216, 341) }}
</td>
</tr>
<tr>
<td colspan="2"><h5 id="thirds">模板：Thirds</h5></td>
</tr>
<tr>
<td width="65%">
<strong>thirds</strong> 模板会将屏幕均分为 3 行，以便您在各个区域中放置相应内容。
<p>您还可指定一个已命名的 <code>grid-area</code>，以指明您希望自己的内容位于 <code>upper-third</code>、<code>middle-third</code> 还是 <code>lower-third</code> 中。如果您想更改元素的默认显示区域，已命名的网格区域会很有用。例如，如果您的图层包含 2 个元素，则可指定让第一个元素在 <code>grid-area="upper-third"</code> 中显示，让第二个元素在 <code>grid-area="lower-third"</code> 中显示。</p>
<code class="nopad"><pre><amp-story-grid-layer template="thirds">
<h1 grid-area="upper-third">element 1</h1>
<p grid-area="lower-third">element 2</p>
</amp-story-grid-layer>
</pre></code>
</td>
<td>{{ image('/static/img/docs/tutorials/amp_story/layer-thirds.png', 216, 341) }}</td>
</tr>
</table>
### 完成封面页
现在，您已经了解了各种图层模板，下面我们就来完成封面页中的第 2 个图层吧。
对于第 2 个图层，我们想将标题和署名行放置在顶部，并希望元素相继堆叠，因此我们将指定 `vertical` 模板。我们的第二个 `amp-story-grid-layer` 会跟在第一个图层后面，如下所示：
```html hl_lines="4 5 6 7"
<amp-story-grid-layer>
<!--our first layer -->
</amp-story-grid-layer>
<amp-story-grid-layer template="vertical">
<h1>The Joy of Pets</h1>
<p>By AMP Tutorials</p>
</amp-story-grid-layer>
```
刷新浏览器即可查看您的工作成果。至此，我们的封面页就制作完毕了。
{{ image('/static/img/docs/tutorials/amp_story/pg0_cover.png', 720, 1280, align='center third', alt='完成后的封面页' ) }}
| 33.729032 | 347 | 0.682288 | yue_Hant | 0.377626 |
ffabce7d4f45c945038558b3141fb910760f31ec | 24 | md | Markdown | README.md | tarun7singh/Alexa-Coiner-Bot-Skill | b64907d125f97c05add5fe8d5a0107e2989cd93d | [
"MIT"
] | null | null | null | README.md | tarun7singh/Alexa-Coiner-Bot-Skill | b64907d125f97c05add5fe8d5a0107e2989cd93d | [
"MIT"
] | null | null | null | README.md | tarun7singh/Alexa-Coiner-Bot-Skill | b64907d125f97c05add5fe8d5a0107e2989cd93d | [
"MIT"
] | null | null | null | # Alexa-Coiner-Bot-Skill | 24 | 24 | 0.791667 | eng_Latn | 0.259631 |
ffabe82b8164c96a19e04139c07f66b241bfc6ae | 6,105 | md | Markdown | articles/machine-learning/algorithm-module-reference/multiclass-boosted-decision-tree.md | AClerbois/azure-docs.fr-fr | 6a7ba4fa8a31f7915c925fef2f809b03d9a2df4e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/machine-learning/algorithm-module-reference/multiclass-boosted-decision-tree.md | AClerbois/azure-docs.fr-fr | 6a7ba4fa8a31f7915c925fef2f809b03d9a2df4e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/machine-learning/algorithm-module-reference/multiclass-boosted-decision-tree.md | AClerbois/azure-docs.fr-fr | 6a7ba4fa8a31f7915c925fef2f809b03d9a2df4e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'Arbre de décision optimisé à plusieurs classes : Informations de référence sur les modules'
titleSuffix: Azure Machine Learning
description: Découvrez comment utiliser le module de l’arbre de décision optimisé multiclasse dans Azure Machine Learning pour créer un classifieur à l’aide de données étiquetées.
services: machine-learning
ms.service: machine-learning
ms.subservice: core
ms.topic: reference
author: likebupt
ms.author: keli19
ms.date: 02/19/2020
ms.openlocfilehash: 1a1cb7661ae01dd89d45afe004978813ac90eaff
ms.sourcegitcommit: 53acd9895a4a395efa6d7cd41d7f78e392b9cfbe
ms.translationtype: HT
ms.contentlocale: fr-FR
ms.lasthandoff: 09/22/2020
ms.locfileid: "90905299"
---
# <a name="multiclass-boosted-decision-tree"></a>Arbre de décision optimisé à plusieurs classes
Cet article décrit un module dans le concepteur Azure Machine Learning.
Ce module vous permet de créer un modèle Machine Learning reposant sur l’algorithme d’arbres de décision optimisés.
Un arbre de décision optimisé est une méthode d’apprentissage d’ensemble dans laquelle le second arbre corrige les erreurs du premier arbre, le troisième arbre corrige les erreurs du premier et du deuxième arbres, et ainsi de suite. Les prédictions sont basées sur l’ensemble des arborescences.
## <a name="how-to-configure"></a>Comment configurer
Ce module crée un modèle de classification non entraîné. Étant donné que la classification est une méthode d’apprentissage supervisée, vous avez besoin d’un *jeu de données étiqueté* incluant une colonne étiquette avec une valeur pour toutes les lignes.
Vous pouvez effectuer l’apprentissage de ce type de modèle à l’aide de l’article [Entraîner le modèle](././train-model.md).
1. Ajoutez le module **Arbre de décision optimisé multiclasse** à votre pipeline.
1. Spécifiez le mode d’apprentissage du modèle en définissant l’option **Créer un mode d’apprentissage**.
+ **Single Parameter** (Paramètre unique) : si vous savez comment vous voulez configurer le modèle, vous pouvez fournir un ensemble spécifique de valeurs comme arguments.
+ **Plage de paramètres** : Sélectionnez cette option si vous n’êtes pas sûr des paramètres à choisir et que vous souhaitez exécuter un balayage des paramètres. Sélectionnez la plage de valeurs sur laquelle vous souhaitez effectuer l'itération. Le module [Optimiser les hyperparamètres du modèle](tune-model-hyperparameters.md) effectue alors une itération sur toutes les combinaisons possibles des paramètres que vous avez fournis pour déterminer les hyperparamètres qui produisent les résultats optimaux.
1. **Maximum number of leaves per tree** (Nombre maximal de nœuds terminaux par arbre) limite le nombre maximal de nœuds terminaux qui peuvent être créés dans un arbre quelconque.
En augmentant cette valeur, vous augmentez potentiellement la taille de l’arbre et vous bénéficiez d’un surcroît de précision, au risque d’un surajustement et d’un temps d’apprentissage plus long.
1. **Minimum number of samples per leaf node** (Nombre minimal d’échantillons par nœud terminal), indique le nombre de cas requis pour la création d’un nœud terminal dans un arbre.
Plus cette valeur est grande, plus le seuil de création de règles augmente. Par exemple, la valeur par défaut de 1, un seul cas suffit à entraîner la création d’une règle. Si la valeur passe à 5, les données d’apprentissage doivent contenir au moins cinq cas remplissant les mêmes conditions.
1. **Learning rate** (taux d’apprentissage) définit la taille de l’étape pendant l’apprentissage. Entrez un nombre compris entre 0 et 1.
Le taux d’apprentissage détermine la vitesse à laquelle l’apprentissage converge vers une solution optimale. Si la taille de pas est trop élevée, vous risquez de passer à côté de la solution optimale. Si la taille de pas est trop faible, l’apprentissage nécessite plus de temps pour converger vers la meilleure solution.
1. **Number of trees constructed** (Nombre d’arbres construits) indique le nombre total d’arbres de décision à créer dans l’ensemble. En créant plusieurs arbres de décision, vous pouvez obtenir une meilleure couverture, mais cette opération augmente la durée d’apprentissage.
1. **Random number seed** (Valeur de départ aléatoire) définit un entier non négatif à utiliser comme valeur initiale aléatoire. La spécification d’une valeur de départ garantit la reproductibilité entre les exécutions qui présentent les mêmes données et paramètres.
La valeur de départ aléatoire est définie par défaut sur 42. Les exécutions successives utilisant des valeurs de départ aléatoires différentes peuvent avoir des résultats différents.
1. Effectuez l’apprentissage du modèle :
+ Si vous définissez **Create trainer mode** (Créer un mode d’apprentissage) sur **Single Parameter** (Paramètre unique), connectez un jeu de données balisé au module [Entraîner le modèle](train-model.md).
+ Si vous définissez **Créer un mode d’apprentissage** sur **Plage de paramètres**, connectez un jeu de données avec balises et effectuez l’apprentissage du modèle en utilisant [Optimiser les hyperparamètres du modèle](tune-model-hyperparameters.md).
> [!NOTE]
>
> Si vous transmettez une plage de paramètres au module [Entraîner le modèle](train-model.md), il utilise uniquement la valeur par défaut dans la liste des paramètres uniques.
>
> Si vous transmettez un ensemble unique de valeurs de paramètre au module [Optimiser les hyperparamètres du modèle](tune-model-hyperparameters.md), quand il attend une plage de paramètres pour chaque paramètre, il ignore les valeurs et utilise les valeurs par défaut pour l’apprenant.
>
> Si vous sélectionnez l’option **Plage de paramètres** et que vous entrez une valeur unique pour un paramètre, cette valeur unique que vous avez spécifiée est utilisée tout au long du balayage, même si d’autres paramètres changent dans une plage de valeurs.
## <a name="next-steps"></a>Étapes suivantes
Consultez [l’ensemble des modules disponibles](module-reference.md) pour Azure Machine Learning.
| 80.328947 | 512 | 0.789844 | fra_Latn | 0.987371 |
ffabef69479d66a8b6a54033e5ee601f9d28a62b | 989 | md | Markdown | api/PowerPoint.Application.ProductCode.md | RichardCory/VBA-Docs | 1240462311fb77ee051d4e8b7d7a434d7d020dd3 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-03-09T13:24:12.000Z | 2020-03-09T16:19:11.000Z | api/PowerPoint.Application.ProductCode.md | MarkFern/VBA-Docs | b84627cc8e24acfd336d1e9761a9ddd58f19d352 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | api/PowerPoint.Application.ProductCode.md | MarkFern/VBA-Docs | b84627cc8e24acfd336d1e9761a9ddd58f19d352 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Application.ProductCode property (PowerPoint)
keywords: vbapp10.chm502037
f1_keywords:
- vbapp10.chm502037
ms.prod: powerpoint
api_name:
- PowerPoint.Application.ProductCode
ms.assetid: 27376e9f-47c6-7373-af34-4ce71723e6a6
ms.date: 06/08/2017
localization_priority: Normal
---
# Application.ProductCode property (PowerPoint)
Returns the Microsoft PowerPoint globally unique identifier (GUID). Read-only.
## Syntax
_expression_. `ProductCode`
_expression_ A variable that represents a [Application](./PowerPoint.Application.md) object.
## Return value
String
## Remarks
You might use the GUID, for example, when making program calls to an Application Programming Interface (API).
## Example
This example returns the PowerPoint GUID to the variable `pptGUID`.
```vb
Dim pptGUID As String
pptGUID = Application.ProductCode
```
## See also
[Application Object](PowerPoint.Application.md)
[!include[Support and feedback](~/includes/feedback-boilerplate.md)] | 18.314815 | 110 | 0.776542 | eng_Latn | 0.506972 |
ffabfa2fe8bd4e7c77190cec82cae1b8b157faf4 | 13,611 | md | Markdown | articles/cognitive-services/Bing-News-Search/vs-bing-news-search-connected-service.md | salem84/azure-docs.it-it | 3ec6a13aebb82936591c7fc479f084be9bb8776d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/cognitive-services/Bing-News-Search/vs-bing-news-search-connected-service.md | salem84/azure-docs.it-it | 3ec6a13aebb82936591c7fc479f084be9bb8776d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/cognitive-services/Bing-News-Search/vs-bing-news-search-connected-service.md | salem84/azure-docs.it-it | 3ec6a13aebb82936591c7fc479f084be9bb8776d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Connettersi all'API Ricerca notizie Bing tramite Servizi connessi in Visual Studio e C#
titleSuffix: Azure Cognitive Services
description: Connettersi a Ricerca notizie Bing da un'applicazione Web ASP.NET Core.
services: cognitive-services
author: ghogen
manager: nitinme
ms.service: cognitive-services
ms.subservice: bing-news-search
ms.topic: tutorial
ms.date: 06/18/2019
ms.author: ghogen
ms.openlocfilehash: 85afae087b1b1e572759943142412743744ee806
ms.sourcegitcommit: b7a44709a0f82974578126f25abee27399f0887f
ms.translationtype: HT
ms.contentlocale: it-IT
ms.lasthandoff: 06/18/2019
ms.locfileid: "67203410"
---
# <a name="tutorial-connect-to-bing-news-search-api-with-connected-services-in-visual-studio-and-c"></a>Esercitazione: Connettersi all'API Ricerca notizie Bing tramite Servizi connessi in Visual Studio e C#
Usando la Ricerca notizie Bing, è possibile abilitare le app e i servizi per sfruttare la potenza di un motore di ricerca senza annunci con ambito Web. Ricerca notizie Bing è uno dei servizi di ricerca disponibili con Servizi cognitivi.
Questo articolo fornisce informazioni dettagliate per usare la funzionalità servizio connesso di Visual Studio per Ricerca notizie Bing. La funzionalità è disponibile in Visual Studio 2017 15.7 o versioni successive, con l'estensione Servizi cognitivi installata.
## <a name="prerequisites"></a>Prerequisiti
- Una sottoscrizione di Azure. Se non si ha una sottoscrizione, è possibile iscriversi per ottenere un [account gratuito](https://azure.microsoft.com/pricing/free-trial/).
- Visual Studio 2019 con il carico di lavoro Sviluppo Web installato. [Scaricarla qui](https://aka.ms/vsdownload?utm_source=mscom&utm_campaign=msdocs).
[!INCLUDE [vs-install-cognitive-services-vsix](../../../includes/vs-install-cognitive-services-vsix.md)]
## <a name="add-support-to-your-project-for-bing-news-search-api"></a>Aggiungere al progetto il supporto l'API Ricerca notizie Bing
1. Creare un nuovo progetto Web ASP.NET Core denominato MyWebApplication. Usare il modello di progetto **App Web (Model-View-Controller)** con tutte le impostazioni predefinite. È importante denominare il progetto MyWebApplication, in modo che quando si copia il codice nel progetto lo spazio dei nomi corrisponda.
1. In **Esplora soluzioni** scegliere **Aggiungi** > **Servizio connesso**.
Verrà visualizzata la pagina Servizio connesso con i servizi che è possibile aggiungere al progetto.
1. Nel menu dei servizi disponibili, scegliere **Bring Intelligent Search To Your Apps** (Aggiungi ricerca intelligente alle applicazioni).
Se è stato effettuato l'accesso a Visual Studio e al proprio account è associata una sottoscrizione di Azure, viene visualizzata una pagina contenente un elenco a discesa con le sottoscrizioni. Selezionare la sottoscrizione che si intende usare e quindi scegliere un nome per l'API Ricerca notizie Bing. È anche possibile scegliere **Modifica** per modificare il nome generato automaticamente.
1. Scegliere il gruppo di risorse e il piano tariffario.
Se si intende visualizzare ulteriori dettagli sui piani tariffari, selezionare **Review pricing** (Esamina prezzi).
1. Fare clic su **Aggiungi** per aggiungere supporto per il servizio connesso.
Visual Studio modifica il progetto per aggiungere i pacchetti NuGet, le voci del file di configurazione e altre modifiche per supportare una connessione all'API Ricerca notizie Bing. L'output mostra il log delle operazioni eseguite nel progetto. Verrà visualizzata una schermata simile alla seguente:
```output
[5/4/2018 12:41:21.084 PM] Adding Intelligent Search to the project.
[5/4/2018 12:41:21.271 PM] Creating new Intelligent Search...
[5/4/2018 12:41:24.128 PM] Installing NuGet package 'Microsoft.Azure.CognitiveServices.Search.ImageSearch' version 1.2.0...
[5/4/2018 12:41:24.135 PM] Installing NuGet package 'Microsoft.Azure.CognitiveServices.Search.NewsSearch' version 1.2.0...
[5/4/2018 12:41:24.154 PM] Installing NuGet package 'Microsoft.Azure.CognitiveServices.Search.WebSearch' version 1.2.0...
[5/4/2018 12:41:24.168 PM] Installing NuGet package 'Microsoft.Azure.CognitiveServices.Search.CustomSearch' version 1.2.0...
[5/4/2018 12:41:24.187 PM] Installing NuGet package 'Microsoft.Azure.CognitiveServices.Search.VideoSearch' version 1.2.0...
[5/4/2018 12:42:07.287 PM] Retrieving keys...
[5/4/2018 12:42:07.741 PM] Updating appsettings.json setting: 'ServiceKey' = 'c271412f3e4c4e1dacc7c4145fa0572a'
[5/4/2018 12:42:07.745 PM] Updating appsettings.json setting: 'ServiceEndPoint' = 'https://api.cognitive.microsoft.com/bing/v7.0'
[5/4/2018 12:42:07.749 PM] Updating appsettings.json setting: 'Name' = 'WebApplicationCore-Search_IntelligentSearch'
[5/4/2018 12:42:10.217 PM] Successfully added Intelligent Search to the project.
```
Il file appsettings.json contiene ora le nuove impostazioni seguenti:
```json
"CognitiveServices": {
"IntelligentSearch": {
"ServiceKey": "<your service key>",
"ServiceEndPoint": "https://api.cognitive.microsoft.com/bing/v7.0",
"Name": "WebApplicationCore-Search_IntelligentSearch"
}
}
```
## <a name="use-the-bing-news-search-api-to-add-search-functionality-to-a-web-page"></a>Usare l'API Ricerca notizie Bing per aggiungere una funzionalità di ricerca a una pagina Web
Ora che è stato aggiunto il supporto per l'API Ricerca notizie Bing al progetto, di seguito viene illustrato come usare l'API per aggiungere la funzionalità di ricerca intelligente a una pagina Web.
1. In *Startup.cs*, nel metodo `ConfigureServices` aggiungere una chiamata a `IServiceCollection.AddSingleton`. In questo modo l'oggetto di configurazione che contiene le impostazioni delle chiavi diventa disponibile per il codice nel progetto.
```csharp
public void ConfigureServices(IServiceCollection services)
{
services.AddMvc();
services.AddSingleton<IConfiguration>(Configuration);
}
```
1. Aggiungere un nuovo file di classe nella cartella **Modelli** denominato *BingNewsModel.cs*. Se il progetto ha un nome diverso, usare lo spazio dei nomi del progetto, anziché MyWebApplication. Sostituire il contenuto con il codice seguente:
```csharp
using Microsoft.Azure.CognitiveServices.Search.NewsSearch.Models;
using System;
using System.Collections.Generic;
using System.Linq;
using System.Threading.Tasks;
namespace MyWebApplication.Models
{
public class BingNewsModel
{
public News SearchResult { get; set; }
public string SearchText { get; set; }
}
}
```
Questo modello viene usato per archiviare i risultati di una chiamata al servizio Ricerca notizie Bing.
1. Nella cartella **Controller** aggiungere un nuovo file di classe denominato *IntelligentSearchController.cs*. Sostituire il contenuto con il codice seguente:
```csharp
using System.Net.Http;
using System.Threading.Tasks;
using MyWebApplication.Models;
using Microsoft.AspNetCore.Mvc;
using Microsoft.Azure.CognitiveServices.Search.NewsSearch;
using Microsoft.Extensions.Configuration;
namespace MyWebApplication.Controllers
{
// A controller to handle News Search requests
public class IntelligentSearchController : Controller
{
private IConfiguration configuration;
// Set up the configuration that contains the keys
// (from the appsettings.json file)
// that you will use to access the service
public IntelligentSearchController(IConfiguration configuration)
{
this.configuration = configuration;
}
// Call the Bing News Search API and put the result in the model object.
public async Task<IActionResult> BingSearchResult(BingNewsModel model)
{
if (!string.IsNullOrWhiteSpace(model.SearchText))
{
INewsSearchAPI client = this.GetNewsSearchClient(new MyHandler());
model.SearchResult = await client.News.SearchAsync(model.SearchText);
}
return View(model);
}
// Forward requests to the Search endpoint to the BingSearchResult method
[HttpPost("Search")]
public IActionResult Search(BingNewsModel model)
{
return RedirectToAction("BingSearchResult", model);
}
// Get the search client object
private INewsSearchAPI GetNewsSearchClient(DelegatingHandler handler)
{
string key =
configuration.GetSection("CognitiveServices")["IntelligentSearch:ServiceKey"];
INewsSearchAPI client = new NewsSearchAPI(
new ApiKeyServiceClientCredentials(key), handlers: handler);
return client;
}
}
}
```
In questo codice, il costruttore imposta l'oggetto di configurazione che contiene le chiavi. Il metodo per la route `Search` è semplicemente un reindirizzamento alla funzione `BingSearchResult`. Viene chiamato il metodo `GetNewsSearchClient` per ottenere l'oggetto client `NewsSearchAPI`. L'oggetto client `NewsSearchAPI` contiene il metodo `SearchAsync` che chiama il servizio e restituisce i risultati nel modello `SearchResult` appena creato.
1. Aggiungere una classe, `MyHandler`, a cui è stato fatto riferimento nel codice precedente. Questo delega la chiamata asincrona al servizio di ricerca alla classe di base, `DelegatingHandler`.
```csharp
using System.Net.Http;
using System.Threading.Tasks;
using System.Threading;
class MyHandler : DelegatingHandler
{
protected async override Task<HttpResponseMessage> SendAsync(
HttpRequestMessage request, CancellationToken cancellationToken)
{
// Call the inner handler.
var response = await base.SendAsync(request, cancellationToken);
return response;
}
}
```
1. Per aggiungere il supporto per l'invio di ricerche e la visualizzazione dei risultati, nella cartella **Visualizzazioni** creare una nuova cartella denominata **IntelligentSearch**. In questa nuova cartella, aggiungere una visualizzazione *BingSearchResult.cshtml*. Copiare il codice seguente:
```cshtml
@using System
@model MyWebApplication.Models.BingNewsModel
@{
ViewData["Title"] = "BingSearchResult";
}
<h2>Search News</h2>
<div class="row">
<section>
<form asp-controller="IntelligentSearch" asp-action="Search" method="POST"
class="form-horizontal" enctype="multipart/form-data">
<table width ="90%">
<tr>
<td>
<input type="text" name="SearchText" class="form-control" />
</td>
<td>
<button type="submit" class="btn btn-default">Search</button>
</td>
</tr>
</table>
</form>
</section>
</div>
<h2>Search Result</h2=
<table>
@if (!string.IsNullOrEmpty(Model.SearchText)) {
foreach (var item in Model.SearchResult.Value) {
<tr>
<td rowspan="2" width="90">
<img src=@item?.Image?.Thumbnail?.ContentUrl width="80" height="80" />
</td>
<td><a [email protected]>@item.Name</a></td>
</tr>
<tr>
<td>@item.Description</td>
</tr>
<tr height="10">
<td/><td/>
</tr>
} }
</table>
<div>
<hr />
<p>
<a asp-controller="Home" asp-action="Index">Return to Index</a>
</p>
</div>
```
1. Avviare l'applicazione Web in locale, immettere l'URL della pagina appena creata (/IntelligentSearch/BingSearchResult) e inviare una richiesta di ricerca con il pulsante di ricerca.
## <a name="clean-up-resources"></a>Pulire le risorse
Quando il gruppo di risorse non è più necessario, è possibile eliminarlo. In questo modo vengono eliminati il servizio cognitivo e le risorse correlate. Per eliminare il gruppo di risorse tramite il portale:
1. Immettere il nome del gruppo di risorse nella casella di ricerca nella parte superiore del portale. Scegliere il gruppo di risorse da eliminare.
2. Selezionare **Elimina gruppo di risorse**.
3. Nella casella **Digitare il nome del gruppo di risorse** immettere il nome del gruppo di risorse e selezionare **Elimina**.
## <a name="next-steps"></a>Passaggi successivi
Per altre informazioni sull'API ricerca notizie Bing, vedere le [informazioni relative a Ricerca notizie Bing](index.yml).
| 50.040441 | 450 | 0.701785 | ita_Latn | 0.956692 |
ffac66175a929c777a662746df512c574b3514f1 | 2,789 | md | Markdown | README.md | Kiera-Hegarty/IMS-Project | f2cb4d5291cf26e650bc730157b930233fcf8f50 | [
"MIT"
] | null | null | null | README.md | Kiera-Hegarty/IMS-Project | f2cb4d5291cf26e650bc730157b930233fcf8f50 | [
"MIT"
] | null | null | null | README.md | Kiera-Hegarty/IMS-Project | f2cb4d5291cf26e650bc730157b930233fcf8f50 | [
"MIT"
] | null | null | null | Jira board link - https://kiera-hegarty.atlassian.net/jira/software/projects/KH/boards/3
Coverage: 64.5%
**IMS Project**
The aim of this project is to create an inventory management system by using:
**Java
Maven
JUnit
Mockito
MySQL
Jira**
**Getting Started**
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
**Prerequisites**
Software Installations for this project:
MySQL: https://dev.mysql.com/downloads/windows/installer/8.0.html
Java: https://www.oracle.com/java/technologies/javase/jdk14-archive-downloads.html
Eclipse: https://www.eclipse.org/downloads/
Maven: https://maven.apache.org/download.cgi?Preferred=ftp://ftp.osuosl.org/pub/apache/
**Installing**
A step by step series of examples that tell you how to get a development env running;
First, install and set up all software.
Then open MySQL Workbench to create a database. Select the local database instance to enter credentials. In the query section make a database called ims; CREATE DATABASE ims.
To run the IMS system go to the directory where the pom.xml file is located; Run command: mvn clean package This will create a directory 'target' which will contain a jar file. Run the jar file by navigating to target file and running the following command: java -jar ims-jar-with-dependencies.jar
**Running the tests**
**Integration Tests**
JUnit
@Test
public void itemTestUpdate() {
final Item updated = new Item(1L,"Hunger Games", 35, 10);
assertEquals(updated, DAO.update(updated));
}
**Unit Tests**
Mockito
@Test
public void itemTestCreate() {
final String I_NAME = "The Giver";
final int STOCK = 25, PRICE = 10;
final Item created = new Item(I_NAME, STOCK, PRICE);
Mockito.when(utils.getString()).thenReturn(I_NAME);
Mockito.when(utils.getInt()).thenReturn(STOCK, PRICE);
Mockito.when(dao.create(created)).thenReturn(created);
assertEquals(created, controller.create());
Mockito.verify(utils, Mockito.times(1)).getString();
Mockito.verify(utils, Mockito.times(2)).getInt();
Mockito.verify(dao, Mockito.times(1)).create(created);
}
**Deployment**
CRUD functions work. However, cannot add individual items to to order (attempted code commented at bottom of OrderControllers class).
**Built With**
Maven - Dependency Management
Versioning
We use SemVer for versioning.
**Authors**
* **Chris Perrins** - *Initial work* - christophperrins
* **Kiera Hegarty** - *Continued to build on intital work* - Kiera-Hegarty
**License**
This project is licensed under the MIT license - see the LICENSE.md file for details
For help in Choosing a license
**Acknowledgments**
Chris Perrins who created the inital project
| 32.057471 | 297 | 0.756902 | eng_Latn | 0.882734 |
ffaca32e3d911b348e16a252f96c94d6c2cc2e91 | 2,665 | md | Markdown | data/issues/ZF-11636.md | zendframework/zf3-web | 5852ab5bfd47285e6b46f9e7b13250629b3e372e | [
"BSD-3-Clause"
] | 40 | 2016-06-23T17:52:49.000Z | 2021-03-27T20:02:40.000Z | data/issues/ZF-11636.md | zendframework/zf3-web | 5852ab5bfd47285e6b46f9e7b13250629b3e372e | [
"BSD-3-Clause"
] | 80 | 2016-06-24T13:39:11.000Z | 2019-08-08T06:37:19.000Z | data/issues/ZF-11636.md | zendframework/zf3-web | 5852ab5bfd47285e6b46f9e7b13250629b3e372e | [
"BSD-3-Clause"
] | 52 | 2016-06-24T22:21:49.000Z | 2022-02-24T18:14:03.000Z | ---
layout: issue
title: "Zend_Application_Resource_Multidb with CacheManager doesn't cache"
id: ZF-11636
---
ZF-11636: Zend\_Application\_Resource\_Multidb with CacheManager doesn't cache
------------------------------------------------------------------------------
Issue Type: Bug Created: 2011-08-02T15:02:54.000+0000 Last Updated: 2011-08-16T20:25:39.000+0000 Status: Closed Fix version(s):
Reporter: Eugene Istrati (eistrati) Assignee: Ramon Henrique Ornelas (ramon) Tags: - Zend\_Application\_Resource
- cache
- multidb
- zend
Related issues:
Attachments:
### Description
I have configured Multidb with CacheManager as per documentation (see below). No errors in logs, full access to filesystem, everything should work like charm, the only problem is that no cache is created...
1) CacheManager configuration: resources.cachemanager.database.frontend.name = Core resources.cachemanager.database.frontend.customFrontendNaming = false resources.cachemanager.database.frontend.options.lifetime = 7200 resources.cachemanager.database.frontend.options.automatic\_serialization = true resources.cachemanager.database.backend.name = File resources.cachemanager.database.backend.customBackendNaming = false resources.cachemanager.database.backend.options.cache\_dir = APPLICATION\_PATH "/../temp/cache" resources.cachemanager.database.frontendBackendAutoload = false
2) Multidb configuration: resources.multidb.defaultMetadataCache = "database"
resources.multidb.db1.adapter = "pdo\_mysql" resources.multidb.db1.host = "localhost" resources.multidb.db1.username = "webuser" resources.multidb.db1.password = "XXXX" resources.multidb.db1.dbname = "db1" resources.multidb.db1.default = true
resources.multidb.db2.adapter = "pdo\_pgsql" resources.multidb.db2.host = "example.com" resources.multidb.db2.username = "dba" resources.multidb.db2.password = "notthatpublic" resources.multidb.db2.dbname = "db2"
### Comments
Posted by Ramon Henrique Ornelas (ramon) on 2011-08-06T04:35:09.000+0000
Exists a problem before 1.11.1 but already was fixed. See here a reproduce <https://gist.github.com/1129015>.
Greetings Ramon
Posted by Ramon Henrique Ornelas (ramon) on 2011-08-13T09:10:07.000+0000
Feel free to reopen case are given more information. See [http://ralphschindler.com/2010/02/…](http://ralphschindler.com/2010/02/18/the-anatomy-of-a-bug-issue-reproduction-script)
Greetings Ramon
Posted by Eugene Istrati (eistrati) on 2011-08-16T20:25:39.000+0000
Why this issue was closed? It is not fixed at all... I am expecting caching files to be created in APPLICATION\_PATH "/../temp/cache", but instead it does nothing!
| 42.983871 | 579 | 0.760225 | eng_Latn | 0.455368 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.