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
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
c9150d2f239893000d44a3d4eda810eea7c304d8 | 5,303 | md | Markdown | Exchange-Server-2013/configure-protected-voice-mail-from-authenticated-callers-exchange-2013-help.md | v-kents/OfficeDocs-Exchange-Test-pr.fr-fr | ef5f903ed67ab02903b8d8097438da160dfa8672 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | Exchange-Server-2013/configure-protected-voice-mail-from-authenticated-callers-exchange-2013-help.md | v-kents/OfficeDocs-Exchange-Test-pr.fr-fr | ef5f903ed67ab02903b8d8097438da160dfa8672 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | Exchange-Server-2013/configure-protected-voice-mail-from-authenticated-callers-exchange-2013-help.md | v-kents/OfficeDocs-Exchange-Test-pr.fr-fr | ef5f903ed67ab02903b8d8097438da160dfa8672 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'Configurer la messagerie vocale protégée des appelants authentifiés: Exchange 2013 Help'
TOCTitle: Configurer la messagerie vocale protégée des appelants authentifiés
ms:assetid: f69e94a7-9768-4445-9ded-e78d732bd623
ms:mtpsurl: https://technet.microsoft.com/fr-fr/library/Ee423560(v=EXCHG.150)
ms:contentKeyID: 52057193
ms.date: 05/23/2018
mtps_version: v=EXCHG.150
ms.translationtype: MT
---
# Configurer la messagerie vocale protégée des appelants authentifiés
_**Sapplique à :** Exchange Online, Exchange Server 2013, Exchange Server 2016_
_**Dernière rubrique modifiée :** 2013-02-22_
Vous pouvez configurer la messagerie unifiée pour répondre à un appel entrant, puis déterminez si elle s'applique protection messages vocaux en utilisant un chiffrement. Lorsqu'un message vocal est protégé :
- Le message est marqué comme Privé dans Microsoft Outlook et Outlook Web App.
- Le message vocal peut être ouvert uniquement par le destinataire prévu.
- Le destinataire peut répondre au message vocal, mais il ne peut pas le transférer à une personne ne figurant pas sur le message vocal d'origine.
Ce paramètre s'applique aux messages vocaux envoyés aux utilisateurs à extension messagerie unifiée lorsqu'ils ne répondent pas leur téléphone. Ce paramètre s'applique également lorsque les appelants se connecter à leur boîte aux lettres à l'aide de Outlook Voice Access, puis créer et envoyer un message vocal.
Pour les autres tâches de gestion relatives aux procédures de la messagerie vocale protégée, consultez la rubrique [Procédures de la messagerie vocale protégées](protected-voice-mail-procedures-exchange-2013-help.md).
## Ce qu'il faut savoir avant de commencer
- Durée d'exécution estimée : moins d'une minute.
- Des autorisations doivent vous être attribuées avant de pouvoir exécuter cette procédure. Pour voir les autorisations qui vous sont nécessaires, consultez Entrée « Stratégies de boîte aux lettres de messagerie unifiée » dans la rubrique [Autorisations de messagerie unifiée](unified-messaging-permissions-exchange-2013-help.md).
- Avant d'exécuter ces procédures, vérifiez qu'un plan de numérotation de messagerie unifiée a été créé. Pour obtenir la procédure détaillée, consultez la rubrique [Créer un plan de numérotation de messagerie unifiée](create-a-um-dial-plan-exchange-2013-help.md).
- Avant d'effectuer ces procédures, vérifiez qu'une stratégie de boîte aux lettres de messagerie unifiée a été créée. Pour obtenir la procédure détaillée, consultez la rubrique [Créer une stratégie de boîte aux lettres de messagerie unifiée](create-a-um-mailbox-policy-exchange-2013-help.md).
- Pour des informations sur les raccourcis clavier applicables aux procédures de cette rubrique, voir Raccourcis clavier dans Exchange 2013[Raccourcis clavier dans le Centre d’administration Exchange](keyboard-shortcuts-in-the-exchange-admin-center-exchange-online-protection-help.md).
> [!TIP]
> Vous rencontrez des difficultés ? Demandez de l’aide en participant aux forums Exchange. Visitez les forums sur les pages <a href="https://go.microsoft.com/fwlink/p/?linkid=60612">Exchange Server</a>, <a href="https://go.microsoft.com/fwlink/p/?linkid=267542">Exchange Online</a>, et <a href="https://go.microsoft.com/fwlink/p/?linkid=285351">Exchange Online Protection</a>..
## Que souhaitez-vous faire ?
## Utiliser le CAE pour configurer la messagerie vocale protégée d'appelants authentifiés
1. Dans le CAE, accédez à **Messagerie unifiée** \> **Plans de numérotation de messagerie unifiée**. Dans l'affichage Liste, sélectionnez le plan de numérotation de messagerie unifiée à modifier, puis cliquez sur **Modifier**.gif "Icône Modifier").
2. Dans la page **Plan de numérotation de messagerie unifiée**, sous **Stratégies de boîte aux lettres de messagerie unifiée**, sélectionnez la stratégie de boîte aux lettres de messagerie unifiée à gérer, puis cliquez sur **Modifier**.gif "Icône Modifier").
3. Dans la page **Stratégie de boîte aux lettres de messagerie unifiée** \> **Messagerie vocale protégée**, sous **Protéger les messages vocaux provenant d'appelants authentifiés**, activez l'une des options suivantes :
- **Aucun** Quand vous définissez ce paramètre, aucune protection n'est appliquée aux messages vocaux envoyés aux utilisateurs à extension messagerie unifiée.
- **Privé** Quand ce paramètre est défini, la messagerie unifiée applique une protection uniquement aux messages vocaux qui ont été marqués comme Privé par l'appelant.
- **Tous** Quand ce paramètre est défini, la messagerie unifiée applique une protection à tous les messages vocaux, y compris à ceux qui ne sont pas marqués comme privés.
4. Cliquez sur **Enregistrer**.
## Utiliser l'environnement de ligne de commande pour configurer la messagerie vocale protégée d'appelants authentifiés
Cet exemple montre comment protéger les messages vocaux de tous les appelants authentifiés dans la stratégie de boîte aux lettres de messagerie unifiée `MyUMMailboxPolicy`.
Set-UMMailboxPolicy -identity MyUMMailboxPolicy ProtectAuthenticatedVoiceMail -All
| 73.652778 | 377 | 0.791062 | fra_Latn | 0.986527 |
c916c929c8d3772e6502ec6a8bfc38c9427ac830 | 6,796 | md | Markdown | Basic/Lab 4 API Consumption - Developers and Apps/README.md | rmistry75/virtual-apijam | 5004fe2181b081860a2589bbaecfd8c809594b0f | [
"Apache-2.0"
] | 5 | 2020-01-22T17:35:12.000Z | 2020-05-13T09:52:45.000Z | Basic/Lab 4 API Consumption - Developers and Apps/README.md | rmistry75/virtual-apijam | 5004fe2181b081860a2589bbaecfd8c809594b0f | [
"Apache-2.0"
] | null | null | null | Basic/Lab 4 API Consumption - Developers and Apps/README.md | rmistry75/virtual-apijam | 5004fe2181b081860a2589bbaecfd8c809594b0f | [
"Apache-2.0"
] | 2 | 2020-01-22T17:29:13.000Z | 2020-10-08T17:36:42.000Z | # API Consumption : Developers and Apps
*Duration : 15 mins*
*Persona : Developer*
# Use case
As an app developer you would like to learn about APIs exposed by the API Team using API Documentation. Register using the Developer Portal to get access to the APIs exposed by the API Team.
# How can Apigee Edge help?
Apigee Edge has an out-of-the-box lightweight Developer Portal which allows the API Team to publish API Documentation. As an app developer you can self register with API Platform. Once logged in, you can create apps to get API keys. API keys can be used to access protected APIs.
In this lab, we will see how to register as an app developer, create an app in the Developer Portal to access API keys, and test the APIs using the keys we got from the Developer Portal.
# Pre-requisites
*API Security* and *API Publishing* lab exercises.
# Instructions
* Go to [https://login.apigee.com/](https://login.apigee.com/) and log in.
* Select **Publish → Portals** in the side navigation menu. Select the developer portal that you created in earlier lab exercise.
* Click on the **Live Portal** link to access the Developer Portal to start interacting as a developer.
* In this lab, we will play the role of an app developer who would like to access the APIs and API Documentation.
* Let’s register as an app developer by clicking on the **Sign In** link on the home page.
* In the **Sign In** page, click on **Create account**
* Fill in the details and then click on **Create Account**
* As the message indicates, check your inbox to view the confirmation email.
* Click on the verification link in your confirmation email to verify your account. You will be redirected back to the developer portal.
* Once again, click on the **Sign In** button, then fill in your Developer Portal credentials to log into the portal.
* Note that the **Sign In** button has been replaced with your email, indicating a successful login.
* Click on the **APIs** link in the top menu to view the list of API products associated to this portal.
* Click on the employee product to view the API Product documentation.
* Go through API Documentation to view the list of APIs and visualize the API Request and Response.
* Let’s **create** a developer app.
Typically, developers who want to consume APIs go to the developer portal and register to use them. When registering, the developer gets to select which of the API products he or she wishes to use. For example, some products may be offered for free, while others require payment depending on a service plan. Upon completion, this registration step produces an Edge entity called a **developer app**. A developer app includes the products the developer selected and a set of API keys that the developer will be required to use to access the APIs that are associated with those products.
* To Create an app, Click on your **Email Address** & then **My Apps** in the top menu bar.
* Click on **+ New App** to create an app.
* Fill in the app's name, description, and click on the toggle to enable access to the Employee product. Click on the **Create** button to create a new developer app.
* After the app has been created, the app page will now have a new section containing the API key. Copy the key, which can be used to make secured API calls.
* From the main Apigee UI (not the Developer Portal), go back to the Employee API you've already created and click the **Trace** tab in the upper right.
* Click **Start Trace Session** to begin a trace session.
* Click **Send** to send a request. (Do not add the API key to the query string yet). You should see a 401 (Unauthorized) response for your API call because the API proxy was expecting an API key as a query parameter. See the trace session below.
* Now add the query parameter ```?apikey={your_api_key}``` to the URL in the trace tool and try again. (Replace ```{your_api_key}``` with the API key you just copied in this lab and resend the request. You should see a 2xx response code and the Trace for that request should show that the Verify API Key policy is now passing.
# Test in the developer portal
* Return to the developer portal and navigate to APIs > Employee Product
* Click Authorize and select the app you registered previously (my-employee-app)
* Click Authorize
* Click OK
* In the left frame, click the /employees GET endpoint. In the right frame, click Execute. You should see a 2xx response code and a list of employees. As an app developer, you can use the portal to test the API paths and see real response data. From here, a developer could start coding an app that will consume the proxies included in the API products they registered.
# Lab Video
If you like to learn by watching, here is a short video on consuming APIs using Apigee Developer Portal [https://youtu.be/nCJwlVF6waw](https://youtu.be/nCJwlVF6waw)
# Earn Extra-points
* Now that you have registered in your developer portal and created an app, read the API documentation, and explore more by making more API calls using keys generated above.
* Explore the Edge UI (not the developer portal) and find and examine the developer and developer app you created using the developer portal.
# Quiz
1. When you create an app, what are the different keys associated with it?
2. Is it possible to create different apps with same app name?
3. Is it possible to associate multiple API products with same app?
# Summary
That completes this hands-on lesson. In this simple lab you learned how to self register as an app developer to access APIs, create apps, access API keys, and navigate through API documentation.
# References
* Useful Apigee documentation link on lightweight Apigee developer portal:
* Apigee Developer Portal: [https://docs-new.apigee.com/portal](https://docs-new.apigee.com/portal)
# Rate this lab
How did you like this lab? Rate [here](https://goo.gl/forms/H4qE5nLy36yWjj642).
Now to go [Lab-5](../Lab%205%20Traffic%20Management%20-%20Rate%20Limit%20APIs/README.md)
| 43.564103 | 586 | 0.75309 | eng_Latn | 0.993517 |
c9172c38109f3da12b1eb668eb75995b0d3a1246 | 127,015 | md | Markdown | LICENSE-3RD-PARTY.md | haberdashPI/empriser | 50811764fb7d707c33a8d1f5f868812dd3ae4849 | [
"MIT-0",
"Apache-2.0",
"CC0-1.0",
"MIT"
] | 2 | 2019-02-18T12:30:56.000Z | 2021-07-29T03:07:21.000Z | LICENSE-3RD-PARTY.md | haberdashPI/empriser | 50811764fb7d707c33a8d1f5f868812dd3ae4849 | [
"MIT-0",
"Apache-2.0",
"CC0-1.0",
"MIT"
] | null | null | null | LICENSE-3RD-PARTY.md | haberdashPI/empriser | 50811764fb7d707c33a8d1f5f868812dd3ae4849 | [
"MIT-0",
"Apache-2.0",
"CC0-1.0",
"MIT"
] | 1 | 2019-02-18T12:31:59.000Z | 2019-02-18T12:31:59.000Z | This software relies on the following, unmodified 3rd party libraries:
Library: [email protected]
> The MIT License (MIT)
>
> Copyright (c) 2014 Tim Oxley
>
> 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.
Library: [email protected]
> Copyright (c) 2011 Alexander Shtuchkin
>
> 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.
>
Library: [email protected]
> Copyright JS Foundation and other contributors, https://js.foundation/
>
> Redistribution and use in source and binary forms, with or without
> modification, are permitted provided that the following conditions are met:
>
> * Redistributions of source code must retain the above copyright
> notice, this list of conditions and the following disclaimer.
> * Redistributions in binary form must reproduce the above copyright
> notice, this list of conditions and the following disclaimer in the
> documentation and/or other materials provided with the distribution.
>
> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
> AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
> IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
> ARE DISCLAIMED. IN NO EVENT SHALL <COPYRIGHT HOLDER> BE LIABLE FOR ANY
> DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
> (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
> LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
> ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
> (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
> THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Library: [email protected]
> Copyright (c) 2014-2016 Denis Pushkarev
>
> 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.
Library: [email protected]
> The MIT License (MIT)
>
> Copyright (c) 2015 Zhiye Li
>
> 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.
>
Library: [email protected]
> Copyright (c) 2013 Ben Newman <[email protected]>
>
> 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.
Library: [email protected]
> The MIT License (MIT)
>
> Copyright (c) Sindre Sorhus <[email protected]> (sindresorhus.com)
>
> 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.
Library: [email protected]
> Apache License, Version 2.0
>
> Copyright (c) 2011 Dominic Tarr
>
> Licensed under the Apache License, Version 2.0 (the "License");
> you may not use this file except in compliance with the License.
> You may obtain a copy of the License at
>
> http://www.apache.org/licenses/LICENSE-2.0
>
> Unless required by applicable law or agreed to in writing, software
> distributed under the License is distributed on an "AS IS" BASIS,
> WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> See the License for the specific language governing permissions and
> limitations under the License.
Library: [email protected]
> This software is released under the MIT license:
>
> 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.
Library: [email protected]
> The MIT License (MIT)
> Copyright (c) 2015 Dmitry Ivanov
>
> 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.
Library: [email protected]
> Copyright (c) 2014 Jonas Wagner
>
> 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.
Library: [email protected]
> Copyright 2010 James Halliday ([email protected])
>
> This project is free software released under the MIT/X11 license:
>
> 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.
Library: [email protected]
> BSD License
>
> For fbjs software
>
> Copyright (c) 2013-present, Facebook, Inc.
> All rights reserved.
>
> Redistribution and use in source and binary forms, with or without modification,
> are permitted provided that the following conditions are met:
>
> * Redistributions of source code must retain the above copyright notice, this
> list of conditions and the following disclaimer.
>
> * Redistributions in binary form must reproduce the above copyright notice,
> this list of conditions and the following disclaimer in the documentation
> and/or other materials provided with the distribution.
>
> * Neither the name Facebook nor the names of its contributors may be used to
> endorse or promote products derived from this software without specific
> prior written permission.
>
> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
> ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
> WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
> DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
> ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
> (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
> LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
> ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
> (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
> SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Library: [email protected]
> The MIT License (MIT)
>
> Copyright (c) 2015-present Dan Abramov
>
> 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.
Library: [email protected]
> The MIT License (MIT)
>
> Copyright (c) 2014-present Stephen J. Collings, Matthew Honnibal, Pieter Vanderwerff
>
> 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.
Library: [email protected]
> Copyright (c) 2013 Ben Newman <[email protected]>
>
> 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.
Library: [email protected]
> BSD License
>
> For jstransform software
>
> Copyright (c) 2013-present, Facebook, Inc.
> All rights reserved.
>
> Redistribution and use in source and binary forms, with or without modification,
> are permitted provided that the following conditions are met:
>
> * Redistributions of source code must retain the above copyright notice, this
> list of conditions and the following disclaimer.
>
> * Redistributions in binary form must reproduce the above copyright notice,
> this list of conditions and the following disclaimer in the documentation
> and/or other materials provided with the distribution.
>
> * Neither the name Facebook nor the names of its contributors may be used to
> endorse or promote products derived from this software without specific
> prior written permission.
>
> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
> ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
> WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
> DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
> ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
> (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
> LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
> ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
> (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
> SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Library: [email protected]
> BSD License
>
> For Immutable JS software
>
> Copyright (c) 2014-2015, Facebook, Inc. All rights reserved.
>
> Redistribution and use in source and binary forms, with or without modification,
> are permitted provided that the following conditions are met:
>
> * Redistributions of source code must retain the above copyright notice, this
> list of conditions and the following disclaimer.
>
> * Redistributions in binary form must reproduce the above copyright notice,
> this list of conditions and the following disclaimer in the documentation
> and/or other materials provided with the distribution.
>
> * Neither the name Facebook nor the names of its contributors may be used to
> endorse or promote products derived from this software without specific
> prior written permission.
>
> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
> ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
> WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
> DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
> ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
> (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
> LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
> ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
> (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
> SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Library: [email protected]
> The MIT License (MIT)
>
> Copyright (c) 2015 Jayson Harshbarger
>
> 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.
>
Library: [email protected]
>
> Copyright (c) 2009-2011, Mozilla Foundation and contributors
> All rights reserved.
>
> Redistribution and use in source and binary forms, with or without
> modification, are permitted provided that the following conditions are met:
>
> * Redistributions of source code must retain the above copyright notice, this
> list of conditions and the following disclaimer.
>
> * Redistributions in binary form must reproduce the above copyright notice,
> this list of conditions and the following disclaimer in the documentation
> and/or other materials provided with the distribution.
>
> * Neither the names of the Mozilla Foundation nor the names of project
> contributors may be used to endorse or promote products derived from this
> software without specific prior written permission.
>
> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
> ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
> WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
> DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
> FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
> DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
> SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
> CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
> OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
> OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Library: [email protected]
> The MIT License (MIT)
>
> Copyright (c) Sindre Sorhus <[email protected]> (sindresorhus.com)
>
> 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.
Library: [email protected]
> MIT License
>
> Copyright (c) 2017 Robin Frischmann
>
> 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.
Library: [email protected]
> This software is released under the MIT license:
>
> 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.
Library: [email protected]
> The MIT License (MIT)
>
> Copyright (c) 2015 Matt Andrews
>
> 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.
Library: [email protected]
> This software is released under the MIT license:
>
> 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.
Library: [email protected]
> The ISC License
>
> Copyright (c) Isaac Z. Schlueter and Contributors
>
> Permission to use, copy, modify, and/or distribute this software for any
> purpose with or without fee is hereby granted, provided that the above
> copyright notice and this permission notice appear in all copies.
>
> THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
> WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
> MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
> ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
> WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
> ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR
> IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Library: [email protected]
> BSD License
>
> For React software
>
> Copyright (c) 2013-2015, Facebook, Inc.
> All rights reserved.
>
> Redistribution and use in source and binary forms, with or without modification,
> are permitted provided that the following conditions are met:
>
> * Redistributions of source code must retain the above copyright notice, this
> list of conditions and the following disclaimer.
>
> * Redistributions in binary form must reproduce the above copyright notice,
> this list of conditions and the following disclaimer in the documentation
> and/or other materials provided with the distribution.
>
> * Neither the name Facebook nor the names of its contributors may be used to
> endorse or promote products derived from this software without specific
> prior written permission.
>
> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
> ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
> WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
> DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
> ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
> (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
> LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
> ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
> (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
> SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Library: [email protected]
> (The MIT License)
>
> Copyright (c) 2011 TJ Holowaychuk <[email protected]>
>
> 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.
Library: [email protected]
> The MIT License
>
> Copyright (c) 2013-2016 Mathew Groves, Chad Engler
>
> 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.
Library: [email protected]
> The MIT License (MIT)
>
> Copyright (c) 2014 Call-Em-All
>
> 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.
Library: [email protected]
> Copyright jQuery Foundation and other contributors <https://jquery.org/>
>
> Based on Underscore.js, copyright Jeremy Ashkenas,
> DocumentCloud and Investigative Reporters & Editors <http://underscorejs.org/>
>
> This software consists of voluntary contributions made by many
> individuals. For exact contribution history, see the revision history
> available at https://github.com/lodash/lodash
>
> The following license applies to all parts of this software except as
> documented below:
>
> ====
>
> 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.
>
> ====
>
> Copyright and related rights for sample code are waived via CC0. Sample
> code is defined as all source code displayed within the prose of the
> documentation.
>
> CC0: http://creativecommons.org/publicdomain/zero/1.0/
>
> ====
>
> Files located in the node_modules and vendor directories are externally
> maintained libraries used by this software which have their own
> licenses; we recommend you read them, as their terms may differ from the
> terms above.
Library: [email protected]
> Copyright (c) 2014 Ben Newman <[email protected]>
>
> 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.
Library: [email protected]
> Copyright 2009–2017 Kristopher Michael Kowal. All rights reserved.
> 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.
Library: [email protected]
> The ISC License
>
> Copyright (c) Isaac Z. Schlueter and Contributors
>
> Permission to use, copy, modify, and/or distribute this software for any
> purpose with or without fee is hereby granted, provided that the above
> copyright notice and this permission notice appear in all copies.
>
> THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
> WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
> MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
> ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
> WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
> ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR
> IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Library: [email protected]
> BSD License
>
> For React software
>
> Copyright (c) 2013-present, Facebook, Inc.
> All rights reserved.
>
> Redistribution and use in source and binary forms, with or without modification,
> are permitted provided that the following conditions are met:
>
> * Redistributions of source code must retain the above copyright notice, this
> list of conditions and the following disclaimer.
>
> * Redistributions in binary form must reproduce the above copyright notice,
> this list of conditions and the following disclaimer in the documentation
> and/or other materials provided with the distribution.
>
> * Neither the name Facebook nor the names of its contributors may be used to
> endorse or promote products derived from this software without specific
> prior written permission.
>
> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
> ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
> WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
> DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
> ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
> (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
> LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
> ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
> (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
> SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Library: [email protected]
> The MIT License (MIT)
>
> Copyright (c) 2014 Arnout Kazemier
>
> 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.
Library: [email protected]
> The MIT License (MIT)
>
> Copyright (c) 2015-present Dan Abramov
>
> 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.
Library: [email protected]
> BSD License
>
> For fbjs software
>
> Copyright (c) 2013-2015, Facebook, Inc.
> All rights reserved.
>
> Redistribution and use in source and binary forms, with or without modification,
> are permitted provided that the following conditions are met:
>
> * Redistributions of source code must retain the above copyright notice, this
> list of conditions and the following disclaimer.
>
> * Redistributions in binary form must reproduce the above copyright notice,
> this list of conditions and the following disclaimer in the documentation
> and/or other materials provided with the distribution.
>
> * Neither the name Facebook nor the names of its contributors may be used to
> endorse or promote products derived from this software without specific
> prior written permission.
>
> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
> ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
> WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
> DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
> ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
> (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
> LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
> ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
> (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
> SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Library: [email protected]
> Copyright (c) 2015, Espen Hovlandsdal
> All rights reserved.
>
> Redistribution and use in source and binary forms, with or without
> modification, are permitted provided that the following conditions are met:
>
> * Redistributions of source code must retain the above copyright notice, this
> list of conditions and the following disclaimer.
>
> * Redistributions in binary form must reproduce the above copyright notice,
> this list of conditions and the following disclaimer in the documentation
> and/or other materials provided with the distribution.
>
> * Neither the name of hyphenate-style-name nor the names of its
> contributors may be used to endorse or promote products derived from
> this software without specific prior written permission.
>
> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
> AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
> IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
> DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
> FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
> DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
> SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
> CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
> OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
> OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
>
Library: [email protected]
> The MIT License (MIT)
>
> Copyright (c) Sindre Sorhus <[email protected]> (sindresorhus.com)
>
> 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.
Library: [email protected]
> The MIT License (MIT)
>
> Copyright (c) 2014-2015 Zilverline B.V.
>
> 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.
Library: [email protected]
> Copyright (c) 2016, Andres Suarez
> All rights reserved.
>
> Redistribution and use in source and binary forms, with or without
> modification, are permitted provided that the following conditions are met:
>
> * Redistributions of source code must retain the above copyright notice, this
> list of conditions and the following disclaimer.
>
> * Redistributions in binary form must reproduce the above copyright notice,
> this list of conditions and the following disclaimer in the documentation
> and/or other materials provided with the distribution.
>
> * Neither the name of invariant nor the names of its
> contributors may be used to endorse or promote products derived from
> this software without specific prior written permission.
>
> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
> AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
> IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
> DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
> FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
> DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
> SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
> CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
> OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
> OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Library: [email protected]
> # react-download
> File download component for React
Library: [email protected]
> Copyright jQuery Foundation and other contributors <https://jquery.org/>
>
> Based on Underscore.js, copyright Jeremy Ashkenas,
> DocumentCloud and Investigative Reporters & Editors <http://underscorejs.org/>
>
> This software consists of voluntary contributions made by many
> individuals. For exact contribution history, see the revision history
> available at https://github.com/lodash/lodash
>
> The following license applies to all parts of this software except as
> documented below:
>
> ====
>
> 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.
>
> ====
>
> Copyright and related rights for sample code are waived via CC0. Sample
> code is defined as all source code displayed within the prose of the
> documentation.
>
> CC0: http://creativecommons.org/publicdomain/zero/1.0/
>
> ====
>
> Files located in the node_modules and vendor directories are externally
> maintained libraries used by this software which have their own
> licenses; we recommend you read them, as their terms may differ from the
> terms above.
Library: [email protected]
> Copyright (c) 2009-2015 Jeremy Ashkenas, DocumentCloud and Investigative
> Reporters & Editors
>
> 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.
Library: [email protected]
> BSD License
>
> For React software
>
> Copyright (c) 2013-present, Facebook, Inc.
> All rights reserved.
>
> Redistribution and use in source and binary forms, with or without modification,
> are permitted provided that the following conditions are met:
>
> * Redistributions of source code must retain the above copyright notice, this
> list of conditions and the following disclaimer.
>
> * Redistributions in binary form must reproduce the above copyright notice,
> this list of conditions and the following disclaimer in the documentation
> and/or other materials provided with the distribution.
>
> * Neither the name Facebook nor the names of its contributors may be used to
> endorse or promote products derived from this software without specific
> prior written permission.
>
> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
> ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
> WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
> DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
> ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
> (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
> LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
> ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
> (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
> SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Library: [email protected]
> The MIT License (MIT)
>
> Copyright (c) 2014 captivationsoftware
>
> 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.
Library: [email protected]
> The MIT License (MIT)
>
> Copyright (c) 2013 linkgod
>
> 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.
Library: [email protected]
> This software is released under the MIT license:
>
> 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.
Library: [email protected]
>
> The MIT License (MIT)
>
> Copyright (c) 2013 Mikola Lysenko
>
> 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.
Library: [email protected]
> Copyright JS Foundation and other contributors, https://js.foundation/
>
> Redistribution and use in source and binary forms, with or without
> modification, are permitted provided that the following conditions are met:
>
> * Redistributions of source code must retain the above copyright
> notice, this list of conditions and the following disclaimer.
> * Redistributions in binary form must reproduce the above copyright
> notice, this list of conditions and the following disclaimer in the
> documentation and/or other materials provided with the distribution.
>
> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
> AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
> IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
> ARE DISCLAIMED. IN NO EVENT SHALL <COPYRIGHT HOLDER> BE LIABLE FOR ANY
> DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
> (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
> LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
> ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
> (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
> THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Library: [email protected]
> The MIT License (MIT)
>
> Copyright (c) 2016 David Frank
>
> 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.
>
Library: [email protected]
> The MIT License (MIT)
>
> Copyright (c) 2015 Jason Quense
>
> 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.
Library: [email protected]
>
> Copyright 2009–2014 Contributors. All rights reserved.
>
> 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.
>
Library: [email protected]
> The MIT License (MIT)
>
> Copyright (c) Sindre Sorhus <[email protected]> (sindresorhus.com)
>
> 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.
Library: [email protected]
> Copyright (c) 2012-2014 Andris Reinman
>
> 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 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.
Library: [email protected]
> ## License
>
> (MIT)
>
> Copyright (c) 2013 Julian Gruber <[email protected]>
>
> 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.
Library: [email protected]
> The ISC License
>
> Copyright (c) Isaac Z. Schlueter
>
> Permission to use, copy, modify, and/or distribute this software for any
> purpose with or without fee is hereby granted, provided that the above
> copyright notice and this permission notice appear in all copies.
>
> THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH
> REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
> FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,
> INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
> LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR
> OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
> PERFORMANCE OF THIS SOFTWARE.
>
Library: [email protected]
> Copyright JS Foundation and other contributors, https://js.foundation/
>
> This software consists of voluntary contributions made by many
> individuals. For exact contribution history, see the revision history
> available at https://github.com/jquery/jquery
>
> The following license applies to all parts of this software except as
> documented below:
>
> ====
>
> 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.
>
> ====
>
> All files located in the node_modules and external directories are
> externally maintained libraries used by this software which have their
> own licenses; we recommend you read them, as their terms may differ from
> the terms above.
Library: [email protected]
> The ISC License
>
> Copyright (c) Isaac Z. Schlueter and Contributors
>
> Permission to use, copy, modify, and/or distribute this software for any
> purpose with or without fee is hereby granted, provided that the above
> copyright notice and this permission notice appear in all copies.
>
> THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
> WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
> MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
> ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
> WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
> ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR
> IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Library: [email protected]
> Copyright (C) 2012-2016 by various contributors (see AUTHORS)
>
> 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.
Library: [email protected]
> The MIT License (MIT)
>
> Copyright (c) 2015-present React-Bootstrap
>
> 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.
>
Library: [email protected]
> (MIT)
>
> Copyright (c) 2013 Julian Gruber <[email protected]>
>
> 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.
Library: [email protected]
> The MIT License
>
> Copyright (c) 2015-2017 Chad Engler
>
> 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.
Library: [email protected]
> amdefine is released under two licenses: new BSD, and MIT. You may pick the
> license that best suits your development needs. The text of both licenses are
> provided below.
>
>
> The "New" BSD License:
> ----------------------
>
> Copyright (c) 2011-2016, The Dojo Foundation
> All rights reserved.
>
> Redistribution and use in source and binary forms, with or without
> modification, are permitted provided that the following conditions are met:
>
> * Redistributions of source code must retain the above copyright notice, this
> list of conditions and the following disclaimer.
> * Redistributions in binary form must reproduce the above copyright notice,
> this list of conditions and the following disclaimer in the documentation
> and/or other materials provided with the distribution.
> * Neither the name of the Dojo Foundation nor the names of its contributors
> may be used to endorse or promote products derived from this software
> without specific prior written permission.
>
> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
> ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
> WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
> DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE
> FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
> DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
> SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
> CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
> OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
> OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
>
>
>
> MIT License
> -----------
>
> Copyright (c) 2011-2016, The Dojo Foundation
>
> 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.
Library: [email protected]
> The MIT License (MIT)
>
> Copyright (c) 2016 Jed Watson
>
> 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.
Library: [email protected]
> The MIT License (MIT)
>
> Copyright (c) 2015 Andres Suarez <[email protected]>
>
> 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.
Library: [email protected]
> Copyright (c) 2016 Andrew Nesbitt
>
> 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.
Library: [email protected]
> Copyright (c) 2014 Forbes Lindesay
>
> 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.
Library: [email protected]
> Copyright (c) 2012 Barnesandnoble.com, llc, Donavon West, and Domenic Denicola
>
> 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.
Library: [email protected]
> Copyright (c) 2016, Mapbox
>
> Permission to use, copy, modify, and/or distribute this software for any purpose
> with or without fee is hereby granted, provided that the above copyright notice
> and this permission notice appear in all copies.
>
> THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH
> REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
> FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,
> INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS
> OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
> TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF
> THIS SOFTWARE.
Library: [email protected]
> The ISC License
>
> Copyright (c) Isaac Z. Schlueter and Contributors
>
> Permission to use, copy, modify, and/or distribute this software for any
> purpose with or without fee is hereby granted, provided that the above
> copyright notice and this permission notice appear in all copies.
>
> THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
> WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
> MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
> ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
> WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
> ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR
> IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Library: [email protected]
> Dual licensed under GPLv2 & MIT
>
> Copyright © 2012-2016 Faisal Salman <<[email protected]>>
>
> 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.
Library: [email protected]
> Copyright (c) 2015 Denis Pushkarev
>
> 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.
Library: [email protected]
> The MIT License (MIT)
>
> Copyright (c) 2014, 2015, 2016, 2017 Simon Lydell
>
> 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.
Library: [email protected]
> The MIT License (MIT)
>
> Copyright (c) Sindre Sorhus <[email protected]> (sindresorhus.com)
> Copyright (c) Ben Lesh <[email protected]>
>
> 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.
Library: [email protected]
> BSD License
>
> For React software
>
> Copyright (c) 2013-present, Facebook, Inc.
> All rights reserved.
>
> Redistribution and use in source and binary forms, with or without modification,
> are permitted provided that the following conditions are met:
>
> * Redistributions of source code must retain the above copyright notice, this
> list of conditions and the following disclaimer.
>
> * Redistributions in binary form must reproduce the above copyright notice,
> this list of conditions and the following disclaimer in the documentation
> and/or other materials provided with the distribution.
>
> * Neither the name Facebook nor the names of its contributors may be used to
> endorse or promote products derived from this software without specific
> prior written permission.
>
> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
> ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
> WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
> DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
> ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
> (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
> LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
> ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
> (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
> SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Library: [email protected]
> Copyright (c) 2012 Ben Newman <[email protected]>
>
> 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.
Library: [email protected]
> Copyright (c) 2014-2015 GitHub, Inc.
>
> 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.
Library: [email protected]
> The ISC License
>
> Copyright (c) Isaac Z. Schlueter
>
> Permission to use, copy, modify, and/or distribute this software for any
> purpose with or without fee is hereby granted, provided that the above
> copyright notice and this permission notice appear in all copies.
>
> THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
> WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
> MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
> ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
> WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
> ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR
> IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Library: [email protected]
> The MIT License (MIT)
>
> Copyright (c) 2015 Robin Frischmann
>
> 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.
>
Library: [email protected]
> BSD License
>
> For React software
>
> Copyright (c) 2013-present, Facebook, Inc.
> All rights reserved.
>
> Redistribution and use in source and binary forms, with or without modification,
> are permitted provided that the following conditions are met:
>
> * Redistributions of source code must retain the above copyright notice, this
> list of conditions and the following disclaimer.
>
> * Redistributions in binary form must reproduce the above copyright notice,
> this list of conditions and the following disclaimer in the documentation
> and/or other materials provided with the distribution.
>
> * Neither the name Facebook nor the names of its contributors may be used to
> endorse or promote products derived from this software without specific
> prior written permission.
>
> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
> ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
> WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
> DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
> ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
> (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
> LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
> ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
> (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
> SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Library: [email protected]
> BSD License
>
> For React software
>
> Copyright (c) 2013-present, Facebook, Inc.
> All rights reserved.
>
> Redistribution and use in source and binary forms, with or without modification,
> are permitted provided that the following conditions are met:
>
> * Redistributions of source code must retain the above copyright notice, this
> list of conditions and the following disclaimer.
>
> * Redistributions in binary form must reproduce the above copyright notice,
> this list of conditions and the following disclaimer in the documentation
> and/or other materials provided with the distribution.
>
> * Neither the name Facebook nor the names of its contributors may be used to
> endorse or promote products derived from this software without specific
> prior written permission.
>
> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
> ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
> WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
> DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
> ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
> (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
> LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
> ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
> (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
> SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Library: [email protected]
> Copyright (c) 2014-2016 GitHub, Inc.
>
> 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.
Library: [email protected]
> Copyright 2015, Dustin Diaz (the "Original Author")
> All rights reserved.
>
> MIT License
>
> 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.
>
> Distributions of all or part of the Software intended to be used
> by the recipients as they would use the unmodified Software,
> containing modifications that substantially alter, remove, or
> disable functionality of the Software, outside of the documented
> configuration mechanisms provided by the Software, shall be
> modified such that the Original Author's bug reporting email
> addresses and urls are either replaced with the contact information
> of the parties responsible for the changes, or removed entirely.
>
> 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.
>
>
> Except where noted, this license applies to any and all software
> programs and associated documentation files created by the
> Original Author, when distributed with the Software.
Library: [email protected]
> The ISC License
>
> Copyright (c) Isaac Z. Schlueter, Ben Noordhuis, and Contributors
>
> Permission to use, copy, modify, and/or distribute this software for any
> purpose with or without fee is hereby granted, provided that the above
> copyright notice and this permission notice appear in all copies.
>
> THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
> WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
> MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
> ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
> WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
> ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR
> IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Library: [email protected]
> Copyright (c) 2009-2011, Mozilla Foundation and contributors
> All rights reserved.
>
> Redistribution and use in source and binary forms, with or without
> modification, are permitted provided that the following conditions are met:
>
> * Redistributions of source code must retain the above copyright notice, this
> list of conditions and the following disclaimer.
>
> * Redistributions in binary form must reproduce the above copyright notice,
> this list of conditions and the following disclaimer in the documentation
> and/or other materials provided with the distribution.
>
> * Neither the names of the Mozilla Foundation nor the names of project
> contributors may be used to endorse or promote products derived from this
> software without specific prior written permission.
>
> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
> ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
> WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
> DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
> FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
> DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
> SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
> CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
> OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.>
Library: [email protected]
> The MIT License (MIT)
>
> Copyright © 2016 Kiko Beats
>
> 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.
Library: [email protected]
> Software License Agreement (BSD License)
> ========================================
>
> Copyright (c) 2015, Yahoo! Inc. All rights reserved.
> ----------------------------------------------------
>
> Redistribution and use of this software in source and binary forms, with or
> without modification, are permitted provided that the following conditions are
> met:
>
> * Redistributions of source code must retain the above copyright notice, this
> list of conditions and the following disclaimer.
> * Redistributions in binary form must reproduce the above copyright notice,
> this list of conditions and the following disclaimer in the documentation
> and/or other materials provided with the distribution.
> * Neither the name of Yahoo! Inc. nor the names of YUI's contributors may be
> used to endorse or promote products derived from this software without
> specific prior written permission of Yahoo! Inc.
>
> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
> ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
> WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
> DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
> ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
> (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
> LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
> ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
> (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
> SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Library: [email protected]
> The MIT License (MIT)
>
> 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.
Library: [email protected]
> ## License
>
> This content is released under the [MIT License](http://opensource.org/licenses/MIT).
Library: [email protected]
> Copyright (C) 1997 - 2002, Makoto Matsumoto and Takuji Nishimura,
> All rights reserved.
> Redistribution and use in source and binary forms, with or without
> modification, are permitted provided that the following conditions
> are met:
> 1. Redistributions of source code must retain the above copyright
> notice, this list of conditions and the following disclaimer.
> 2. Redistributions in binary form must reproduce the above copyright
> notice, this list of conditions and the following disclaimer in the
> documentation and/or other materials provided with the distribution.
> 3. The names of its contributors may not be used to endorse or promote
> products derived from this software without specific prior written
> permission.
> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
> "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
> LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
> A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
> CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
> EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
> PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
> PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
> LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
> NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
> SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Library: [email protected]
> Copyright JS Foundation and other contributors <https://js.foundation/>
>
> Based on Underscore.js, copyright Jeremy Ashkenas,
> DocumentCloud and Investigative Reporters & Editors <http://underscorejs.org/>
>
> This software consists of voluntary contributions made by many
> individuals. For exact contribution history, see the revision history
> available at https://github.com/lodash/lodash
>
> The following license applies to all parts of this software except as
> documented below:
>
> ====
>
> 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.
>
> ====
>
> Copyright and related rights for sample code are waived via CC0. Sample
> code is defined as all source code displayed within the prose of the
> documentation.
>
> CC0: http://creativecommons.org/publicdomain/zero/1.0/
>
> ====
>
> Files located in the node_modules and vendor directories are externally
> maintained libraries used by this software which have their own
> licenses; we recommend you read them, as their terms may differ from the
> terms above.
Library: [email protected]
> The MIT License (MIT)
>
> Copyright (c) 2015 react-bootstrap
>
> 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.
>
Library: [email protected]
> The MIT License (MIT)
>
> Copyright (c) 2015-2016 Andrew Clark
>
> 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.
Library: [email protected]
> MIT License
>
> Copyright (c) 2017 Mike Reinstein
>
> 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.
Library: [email protected]
> Copyright (c) 2011-2016 Heather Arthur <[email protected]>
>
> 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.
>
Library: [email protected]
> Copyright JS Foundation and other contributors <https://js.foundation/>
>
> Based on Underscore.js, copyright Jeremy Ashkenas,
> DocumentCloud and Investigative Reporters & Editors <http://underscorejs.org/>
>
> This software consists of voluntary contributions made by many
> individuals. For exact contribution history, see the revision history
> available at https://github.com/lodash/lodash
>
> The following license applies to all parts of this software except as
> documented below:
>
> ====
>
> 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.
>
> ====
>
> Copyright and related rights for sample code are waived via CC0. Sample
> code is defined as all source code displayed within the prose of the
> documentation.
>
> CC0: http://creativecommons.org/publicdomain/zero/1.0/
>
> ====
>
> Files located in the node_modules and vendor directories are externally
> maintained libraries used by this software which have their own
> licenses; we recommend you read them, as their terms may differ from the
> terms above.
Library: [email protected]
> BSD License
>
> For React software
>
> Copyright (c) 2013-2015, Facebook, Inc.
> All rights reserved.
>
> Redistribution and use in source and binary forms, with or without modification,
> are permitted provided that the following conditions are met:
>
> * Redistributions of source code must retain the above copyright notice, this
> list of conditions and the following disclaimer.
>
> * Redistributions in binary form must reproduce the above copyright notice,
> this list of conditions and the following disclaimer in the documentation
> and/or other materials provided with the distribution.
>
> * Neither the name Facebook nor the names of its contributors may be used to
> endorse or promote products derived from this software without specific
> prior written permission.
>
> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
> ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
> WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
> DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
> ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
> (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
> LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
> ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
> (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
> SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Library: @axetroy/[email protected]
> The MIT License (MIT)
>
> Copyright (c) 2017 axetroy
>
> 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
> [email protected]
>
> MIT License
>
> Copyright (c) 2014-2017 Sebastian McKenzie <[email protected]>
>
> 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.
>
[email protected]
>
> The MIT License (MIT)
>
> Copyright (c) 2015 Jason Quense
>
> 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.
>
| 50.66414 | 462 | 0.772594 | yue_Hant | 0.653972 |
c917dd679706bd1455d75719327161d0b2b0b2d1 | 802 | md | Markdown | README.md | Riflio/JSDistanceTrasform | 4dfc6fb07410d177b98627b4e331a048724b6db4 | [
"MIT"
] | 2 | 2019-06-19T02:25:07.000Z | 2019-07-17T16:40:45.000Z | README.md | Riflio/JSDistanceTrasform | 4dfc6fb07410d177b98627b4e331a048724b6db4 | [
"MIT"
] | 1 | 2020-03-24T00:46:09.000Z | 2020-03-24T00:46:09.000Z | README.md | Riflio/JSDistanceTrasform | 4dfc6fb07410d177b98627b4e331a048724b6db4 | [
"MIT"
] | null | null | null | # Distance transform algorithm experiments
## index1_distanceTrasformFast
## index2_distanceTrasform
## index3_distanceTrasformToHeightMap
## index4_distanceTrasformToHeightMapAndLighter
## index5_distanceTrasformAndLighter2
| 66.833333 | 126 | 0.861596 | yue_Hant | 0.211776 |
c9180f0e85400518a3c70b445202f861bb030afd | 4,929 | md | Markdown | docs/architecture/microservices/implement-resilient-applications/handle-partial-failure.md | MoisesMlg/docs.es-es | 4e8c9f518ab606048dd16b6c6a43a4fa7de4bcf5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/architecture/microservices/implement-resilient-applications/handle-partial-failure.md | MoisesMlg/docs.es-es | 4e8c9f518ab606048dd16b6c6a43a4fa7de4bcf5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/architecture/microservices/implement-resilient-applications/handle-partial-failure.md | MoisesMlg/docs.es-es | 4e8c9f518ab606048dd16b6c6a43a4fa7de4bcf5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Controlar errores parciales
description: Obtenga información sobre cómo controlar errores parciales con elegancia. Un microservicio podría no ser totalmente funcional y aun así realizar trabajo útil.
ms.date: 10/16/2018
ms.openlocfilehash: 3345fffe3a38b8336d71ebb9c88e76d3315fd2e2
ms.sourcegitcommit: a8730298170b8d96b4272e0c3dfc9819c606947b
ms.translationtype: HT
ms.contentlocale: es-ES
ms.lasthandoff: 09/17/2020
ms.locfileid: "90738767"
---
# <a name="handle-partial-failure"></a>Controlar errores parciales
En sistemas distribuidos como las aplicaciones basadas en microservicios, hay un riesgo siempre presente de error parcial. Por ejemplo, se puede producir un error en un único contenedor o microservicio o este podría no estar disponible para responder durante un breve período, o se podría bloquear una única máquina virtual o un servidor. Puesto que los clientes y los servicios son procesos independientes, es posible que un servicio no pueda responder de forma oportuna a una solicitud del cliente. Es posible que el servicio esté sobrecargado y responda muy lentamente a las solicitudes, o bien que simplemente no sea accesible durante un breve período debido a problemas de red.
Por ejemplo, considere la página de detalles Order de la aplicación de ejemplo eShopOnContainers. Si el microservicio Ordering no responde cuando el usuario intenta enviar un pedido, una implementación incorrecta del proceso del cliente (la aplicación web MVC), por ejemplo, si el código de cliente usara RPC sincrónicas sin tiempo de espera, bloquearía los subprocesos indefinidamente en espera de una respuesta. Además de la mala experiencia del usuario, cada espera sin respuesta usa o bloquea un subproceso, y los subprocesos son muy valiosos en aplicaciones altamente escalables. Si hay muchos subprocesos bloqueados, al final el tiempo de ejecución de la aplicación puede quedarse sin subprocesos. En ese caso, la aplicación puede no responder globalmente en lugar de solo parcialmente, como se muestra en la figura 8-1.
**Figura 8-1**. Errores parciales debido a dependencias que afectan a la disponibilidad del subproceso de servicio
En una aplicación basada en microservicios de gran tamaño, cualquier error parcial se puede amplificar, especialmente si la mayor parte de la interacción de los microservicios internos se basa en llamadas HTTP sincrónicas (lo que se considera un anti-patrón). Piense en un sistema que recibe millones de llamadas entrantes al día. Si el sistema tiene un diseño incorrecto basado en cadenas largas de llamadas HTTP sincrónicas, estas llamadas entrantes podrían dar lugar a muchos más millones de llamadas salientes (supongamos una proporción 1:4) a decenas de microservicios internos como dependencias sincrónicas. Esta situación se muestra en la figura 8-2, especialmente la dependencia 3, que inicia una cadena, llama a la dependencia 4, que a su vez llama a la dependencia 5.
**Figura 8-2**. Impacto de tener un diseño incorrecto que incluye cadenas largas de solicitudes HTTP
Los errores intermitentes están garantizados en un sistema distribuido basado en la nube, aunque cada dependencia tenga una disponibilidad excelente. Es un hecho que se debe tener en cuenta.
Si no diseña ni implementa técnicas para asegurar la tolerancia a errores, incluso se pueden magnificar los pequeños tiempos de inactividad. Por ejemplo, 50 dependencias con un 99,99 % de disponibilidad cada una darían lugar a varias horas de tiempo de inactividad al mes debido a este efecto dominó. Cuando se produce un error en una dependencia de un microservicio al controlar un gran volumen de solicitudes, ese error puede saturar rápidamente todos los subprocesos de solicitudes disponibles en cada servicio y bloquear toda la aplicación.
**Figura 8-3**. Error parcial amplificado por los microservicios con cadenas largas de llamadas HTTP sincrónicas
Para minimizar este problema, en la sección [La integración asincrónica del microservicio obliga a su autonomía](../architect-microservice-container-applications/communication-in-microservice-architecture.md#asynchronous-microservice-integration-enforces-microservices-autonomy), esta guía recomienda usar la comunicación asincrónica entre los microservicios internos.
Además, es fundamental que diseñe las aplicaciones cliente y los microservicios para controlar los errores parciales, es decir, que compile microservicios y aplicaciones cliente resistentes.
>[!div class="step-by-step"]
>[Anterior](index.md)
>[Siguiente](partial-failure-strategies.md)
| 114.627907 | 826 | 0.823696 | spa_Latn | 0.992658 |
c9187c0acf9ae8d05ad109c222b0ba99e544e23e | 331 | md | Markdown | src/regions/ca/info/faq/47_financial-help.fr.md | MQL-Medops/covid-19 | d64658f6b706925c6846f1ddba2da3150e412dd2 | [
"MIT"
] | 47 | 2020-03-10T12:28:16.000Z | 2022-03-26T21:47:29.000Z | src/regions/ca/info/faq/47_financial-help.fr.md | MQL-Medops/covid-19 | d64658f6b706925c6846f1ddba2da3150e412dd2 | [
"MIT"
] | 79 | 2020-03-08T00:51:06.000Z | 2021-06-17T14:47:19.000Z | src/regions/ca/info/faq/47_financial-help.fr.md | MQL-Medops/covid-19 | d64658f6b706925c6846f1ddba2da3150e412dd2 | [
"MIT"
] | 14 | 2020-03-06T23:11:43.000Z | 2020-11-09T13:40:47.000Z | ## Est ce qu’il existe des aides financières pour les Canadiens et les entreprises?
Oui, voici l’information du [Gouvernement du Canada](https://www.canada.ca/fr/ministere-finances/nouvelles/2020/03/plan-dintervention-economique-du-canada-pour-repondre-a-la-covid-19.html) sur le sujet.
_Dernière mise à jour le 13 octobre 2020_
| 55.166667 | 202 | 0.794562 | fra_Latn | 0.910654 |
c91907aa3d3c2d61cfe90bec41bfac964713e229 | 403 | md | Markdown | README.md | leobalter/npm-ipu | 482765eb87c45326543fc3ee613f149c5d8782ed | [
"MIT"
] | null | null | null | README.md | leobalter/npm-ipu | 482765eb87c45326543fc3ee613f149c5d8782ed | [
"MIT"
] | null | null | null | README.md | leobalter/npm-ipu | 482765eb87c45326543fc3ee613f149c5d8782ed | [
"MIT"
] | null | null | null | # npm-ipu
Safe npm updates. It literally just runs `npm install`, `npm prune`, and `npm update`.
An alias solves that as well.
This module will be discontinued as soon as I can have an npm alias configuration or run these commands at once.
## Install
You need npm to be installed and running in your path.
```shell
npm install -g npm-ipu
```
## Running
From your repo's folder:
```
npm-ipu
```
| 16.791667 | 112 | 0.712159 | eng_Latn | 0.99877 |
c91924264545741d34f7ef8deceab932898f3c4f | 2,126 | md | Markdown | content/references/rippled-api/api-conventions/base58-encodings.md | fossabot/xrpl-dev-portal | c189df941fd6808c0ba8af9a28cdab418ff213a0 | [
"Apache-2.0"
] | 3 | 2021-03-03T00:18:47.000Z | 2021-03-09T10:53:00.000Z | content/references/rippled-api/api-conventions/base58-encodings.md | fossabot/xrpl-dev-portal | c189df941fd6808c0ba8af9a28cdab418ff213a0 | [
"Apache-2.0"
] | 1 | 2021-01-03T14:09:05.000Z | 2021-01-03T14:09:05.000Z | content/references/rippled-api/api-conventions/base58-encodings.md | fossabot/xrpl-dev-portal | c189df941fd6808c0ba8af9a28cdab418ff213a0 | [
"Apache-2.0"
] | 1 | 2021-01-03T14:02:06.000Z | 2021-01-03T14:02:06.000Z | # base58 Encodings
The `rippled` APIs often use a "base58" encoding with a checksum (sometimes called "Base58Check") to represent [account addresses](accounts.html#addresses) and other types of values related to cryptographic keys. This encoding is the same as [the one used for Bitcoin addresses](https://en.bitcoin.it/wiki/Base58Check_encoding), except that the XRP Ledger uses the following dictionary: `rpshnaf39wBUDNEGHJKLM4PQRST7VWXYZ2bcdeCg65jkm8oFqi1tuvAxyz`.
The XRP Ledger prefixes different types of values with a specific 8-bit number before encoding them to distinguish between different data types. With the arrangement of characters in the XRP Ledger's base58 dictionary, the result is that the base58 representations for different types of encoded values start with specific letters by type.
The following table lists all the encodings the XRP Ledger uses:
| Data Type | Starts With | Type Prefix | Content size¹ | Maximum characters |
|:-----------------------------------------|:------------|:------------|:--------------|:--|
| [Account][] address | r | `0x00` | 20 bytes | 35 |
| Account public key | a | `0x23` | 33 bytes | 53 |
| Seed value (for secret keys) | s | `0x21` | 16 bytes | 29 |
| Validation public key or node public key | n | `0x1C` | 33 bytes | 53 |
¹ Content size excludes the 1-byte type prefix.
[Account]: accounts.html
## See Also
- [Address Encoding](accounts.html#address-encoding) - detailed information on address encoding
- [Cryptographic Keys](cryptographic-keys.html) - types of cryptographic keys in the XRP Ledger and how they're used
- [wallet_propose Reference][wallet_propose method] - API method for generating account keys
- [validation_create Reference][validation_create method] - API method for generating validator keys
<!--{# common link defs #}-->
{% include '_snippets/rippled-api-links.md' %}
{% include '_snippets/tx-type-links.md' %}
{% include '_snippets/rippled_versions.md' %}
| 66.4375 | 448 | 0.669332 | eng_Latn | 0.976185 |
c919cc48969cff067bb9934247ac49206c6bc797 | 427 | md | Markdown | CHANGELOG.md | arktos65/tgw_wordpress | 7d3cfdde37950da005582496897b57fd0cfcd3fb | [
"Apache-2.0"
] | null | null | null | CHANGELOG.md | arktos65/tgw_wordpress | 7d3cfdde37950da005582496897b57fd0cfcd3fb | [
"Apache-2.0"
] | null | null | null | CHANGELOG.md | arktos65/tgw_wordpress | 7d3cfdde37950da005582496897b57fd0cfcd3fb | [
"Apache-2.0"
] | null | null | null | # TGW_WORDPRESS CHANGELOG
This file is used to list changes made in each version of the tgw_wordpress cookbook.
# 0.2.0 (12-Dec-2020)
- Configure Nginx to host Wordpress site.
- Fixed bugs in nginx recipe.
# 0.1.0 (10-Dec-2020)
- Installs base server configuration.
- Installs and configures MySQL Community Edition v5.7
- Installs and configures Nginx web server.
- Loads Wordpress software into designated user account.
| 26.6875 | 85 | 0.770492 | eng_Latn | 0.916617 |
c91b9c48f4d3cb0607f2b44fe830f0513e1ab269 | 2,659 | md | Markdown | docs/relational-databases/sqlxml-annotated-xsd-schemas-using/specifying-the-sql-inverse-attribute-on-sql-relationship-sqlxml-4-0.md | KochertNinja/sql-docs | 04c031f7411aa33e2174be11dfced7feca8fbcda | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-04-10T15:18:59.000Z | 2019-04-10T15:18:59.000Z | docs/relational-databases/sqlxml-annotated-xsd-schemas-using/specifying-the-sql-inverse-attribute-on-sql-relationship-sqlxml-4-0.md | KochertNinja/sql-docs | 04c031f7411aa33e2174be11dfced7feca8fbcda | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/relational-databases/sqlxml-annotated-xsd-schemas-using/specifying-the-sql-inverse-attribute-on-sql-relationship-sqlxml-4-0.md | KochertNinja/sql-docs | 04c031f7411aa33e2174be11dfced7feca8fbcda | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-04-02T15:42:37.000Z | 2019-04-02T15:42:37.000Z | ---
title: "Specifying the sql:inverse Attribute on sql:relationship (SQLXML 4.0) | Microsoft Docs"
ms.custom: ""
ms.date: "03/17/2017"
ms.prod: sql
ms.prod_service: "database-engine, sql-database"
ms.reviewer: ""
ms.technology: xml
ms.topic: "reference"
helpviewer_keywords:
- "sql:relationship"
- "bulk load [SQLXML]"
- "inverse attribute"
- "relationships [SQLXML], inverse orders"
- "relationship annotation"
- "XSD schemas [SQLXML], relationships"
- "annotated XSD schemas, relationships"
- "updategrams [SQLXML], relationships"
- "sql:inverse"
ms.assetid: 08904cbd-9c86-493d-90c3-f5e1d13ce59d
author: MightyPen
ms.author: douglasl
manager: craigg
monikerRange: "=azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current"
---
# Specifying the sql:inverse Attribute on sql:relationship (SQLXML 4.0)
[!INCLUDE[appliesto-ss-asdb-xxxx-xxx-md](../../includes/appliesto-ss-asdb-xxxx-xxx-md.md)]
The **sql:inverse** attribute is useful only when the XSD schema is used for either bulk load or by an updategram. The **sql:inverse** attribute can be specified on the **\<sql:relationship>** element. In updategrams, the updategram logic interprets the schema in determining the tables and columns that are updated by the updategram operation. The parent-child relationships that are specified in the schema determine the order in which the records are modified (inserted or deleted).
If you have an XSD schema in which the parent-child relationship is specified in the inverse order of the primary-key/foreign-key relationship between the corresponding database columns, the insert or delete updategram operation will fail because of the primary-key/foreign-key violation. In such cases, the **sql:inverse** attribute is specified (**sql:inverse="true"**) in the **\<sql:relationship>** element, and the updategram logic inverses its interpretation of the parent-child relationship specified in the schema.
The **sql:inverse** attribute takes a Boolean value (0=false, 1=true). The acceptable values are 0, 1, true, and false.
For a working sample using the **sql:inverse** annotation, see [Specifying an Annotated Mapping Schema in an Updategram](../../relational-databases/sqlxml-annotated-xsd-schemas-xpath-queries/updategrams/specifying-an-annotated-mapping-schema-in-an-updategram-sqlxml-4-0.md).
## See Also
[Specifying Relationships Using sql:relationship (SQLXML 4.0)](../../relational-databases/sqlxml-annotated-xsd-schemas-using/specifying-relationships-using-sql-relationship-sqlxml-4-0.md)
| 66.475 | 526 | 0.750658 | eng_Latn | 0.898028 |
c91ba2985755b1a806a23d4e73f4b2d95acf63eb | 1,952 | md | Markdown | docs/2014/sql-server/install/repair-powerpivot-for-sharepoint.md | adiazcan/sql-docs.es-es | 7221c45ca1a7fd1fc7aeeefe8d0b023bb0b711b1 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/2014/sql-server/install/repair-powerpivot-for-sharepoint.md | adiazcan/sql-docs.es-es | 7221c45ca1a7fd1fc7aeeefe8d0b023bb0b711b1 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/2014/sql-server/install/repair-powerpivot-for-sharepoint.md | adiazcan/sql-docs.es-es | 7221c45ca1a7fd1fc7aeeefe8d0b023bb0b711b1 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Reparar PowerPivot para SharePoint | Microsoft Docs
ms.custom: ''
ms.date: 06/13/2017
ms.prod: sql-server-2014
ms.reviewer: ''
ms.technology:
- database-engine
ms.topic: conceptual
ms.assetid: 9c346ae8-87fa-44e5-b88a-47e804fedf20
author: markingmyname
ms.author: maghan
manager: craigg
ms.openlocfilehash: 408d6a3bfdd2618931ceefa5d6d82ad6ab581485
ms.sourcegitcommit: 3da2edf82763852cff6772a1a282ace3034b4936
ms.translationtype: MT
ms.contentlocale: es-ES
ms.lasthandoff: 10/02/2018
ms.locfileid: "48065235"
---
# <a name="repair-powerpivot-for-sharepoint"></a>Reparar PowerPivot para SharePoint
Puede utilizar la Herramienta de configuración de PowerPivot para reparar una instalación existente de PowerPivot para SharePoint. La herramienta lee la configuración para una instancia local de PowerPivot para SharePoint y proporciona acciones para reconfigurar un valor que es incoherente con una instalación de PowerPivot para SharePoint. Por ejemplo, si detiene un servicio o retira una solución, la herramienta proporcionará las acciones para iniciar el servicio e implementar la solución.
Para obtener más información, consulte [configurar o reparar PowerPivot para SharePoint 2010 (herramienta de configuración de PowerPivot)](../../../2014/analysis-services/configure-repair-powerpivot-sharepoint-2010.md).
## <a name="see-also"></a>Vea también
[Quitar una instalación de SQL Server 2014](../../database-engine/install-windows/repair-a-failed-sql-server-installation.md)
[Instalar PowerPivot para SharePoint 2010](../../../2014/sql-server/install/install-powerpivot-for-sharepoint-2010.md)
[Desinstalar una instancia existente de SQL Server (programa de instalación)](../../../2014/sql-server/install/uninstall-an-existing-instance-of-sql-server-setup.md)
[Instalación de PowerPivot para SharePoint 2010](../../../2014/sql-server/install/powerpivot-for-sharepoint-2010-installation.md)
| 59.151515 | 498 | 0.788422 | spa_Latn | 0.716908 |
c91be9ccc8762a5d3fc142622b22d76b31b614c9 | 1,025 | md | Markdown | README.md | erichilarysmithsr/GECentricity | f00a4902ab732eb46cdce8941d7d1f27f7faed02 | [
"MS-PL"
] | null | null | null | README.md | erichilarysmithsr/GECentricity | f00a4902ab732eb46cdce8941d7d1f27f7faed02 | [
"MS-PL"
] | null | null | null | README.md | erichilarysmithsr/GECentricity | f00a4902ab732eb46cdce8941d7d1f27f7faed02 | [
"MS-PL"
] | null | null | null | GECentricity
============
Centricity is a brand of healthcare IT software solutions from GE Healthcare, a division of General Electric.
The GECentricity is subproject of mdObject initiative to simplify patient medical record exchange.
The $mdObject is simple JSON stricture that is easy to implement and to use.
The mdObject is stand for [M]edical [D]ata Object.
For users of GE Centricity EMR9.8 Evaluation version, execute the following line to enable ActiveX component:
Regsvr32 "C:\Program Files (x86)\Centricity EMR 9.8 Evaluation\GE.EMR.Msg.IF.dll"
Use IE9+ for demo.
To create new observation (jQuery is used bellow to pull the height value from HTML control) :
var currentDate = new Date();
var obsDate = (currentDate.getMonth() + 1) + '/' + currentDate.getDate() + '/' + currentDate.getFullYear();
var height = $("#Height").val();
var heightObs = new $mdObject.Observation();
heightObs.name = "HEIGHT";
heightObs.value = height;
heightObs.date = obsDate;
heightObs.save();
| 39.423077 | 111 | 0.724878 | eng_Latn | 0.933535 |
c91c10a726d2c012d2d0c5b1ed00c0272fb0a8c9 | 1,900 | md | Markdown | AlchemyInsights/suggestions-for-solving-unlicensed-product-errors.md | AdrianaMedia/OfficeDocs-AlchemyInsights-pr.cs-CZ | 1eeb3a75180d9d8bf791c4554db66c7bebd4f0b6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | AlchemyInsights/suggestions-for-solving-unlicensed-product-errors.md | AdrianaMedia/OfficeDocs-AlchemyInsights-pr.cs-CZ | 1eeb3a75180d9d8bf791c4554db66c7bebd4f0b6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | AlchemyInsights/suggestions-for-solving-unlicensed-product-errors.md | AdrianaMedia/OfficeDocs-AlchemyInsights-pr.cs-CZ | 1eeb3a75180d9d8bf791c4554db66c7bebd4f0b6 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-06-10T18:26:09.000Z | 2021-06-10T18:26:09.000Z | ---
title: Návrhy na řešení chyb typu nelicencovaný produkt
ms.author: pebaum
author: pebaum
manager: mnirkhe
ms.date: 04/21/2020
ms.audience: ITPro
ms.topic: article
ms.service: o365-administration
ROBOTS: NOINDEX, NOFOLLOW
localization_priority: Normal
ms.custom:
- "849"
- "2000021"
ms.assetid: 6422774e-c7a5-4894-a60f-cdef5ca60afe
ms.openlocfilehash: b1a1ebe313cc90d49633522546b7757fc2d93543
ms.sourcegitcommit: c6692ce0fa1358ec3529e59ca0ecdfdea4cdc759
ms.translationtype: MT
ms.contentlocale: cs-CZ
ms.lasthandoff: 09/15/2020
ms.locfileid: "47808412"
---
# <a name="suggestions-for-solving-unlicensed-product-errors"></a>Návrhy na řešení potíží s chybami "nelicencovaný produkt"
Zkontrolujte, jestli máte předplatné, které umožňuje klientské licence, jako jsou aplikace Microsoft 365 pro firmy nebo Microsoft 365 Business Premium, a [Zkontrolujte, jestli má uživatel přiřazenou licenci](https://docs.microsoft.com/microsoft-365/admin/add-users/add-users). [Deaktivujte instalaci](https://docs.microsoft.com/microsoft-365/admin/add-users/delete-a-user) a zkontrolujte, jestli jste překročili počet instalací podporovaných vaším předplatným.
Ujistěte se, že se uživatel přihlašuje pomocí stejného účtu, který má přiřazenou licenci.
Spusťte [Poradce při potížích s aktivací](https://aka.ms/SARA-OfficeActivation-Alchemy).
Kontrola, jestli platnost vašeho předplatného vypršela
Podívejte se na [stránku stavu služeb](https://docs.microsoft.com/office365/enterprise/view-service-health) a zjistěte, jestli se vyskytly nějaké problémy.
[Provedení online opravy Office](https://support.office.com/Article/7821d4b6-7c1d-4205-aa0e-a6b40c5bb88b?wt.mc_id=Alchemy_ClientDIA)
Další řešení pro řešení potíží najdete v tématu: [chyby typu nelicencovaný produkt a chyby aktivace v Office](https://support.office.com/Article/0d23d3c0-c19c-4b2f-9845-5344fedc4380?wt.mc_id=Alchemy_ClientDIA).
| 50 | 460 | 0.810526 | ces_Latn | 0.983712 |
c91c2eed146b2695eb39f7d9ab9bbaa8172adbf2 | 3,956 | md | Markdown | wdk-ddi-src/content/wdm/ns-wdm-_dma_adapter.md | henke37/windows-driver-docs-ddi | 787885908a0474b7e2c3d2f8a47355dee62c7aec | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-08-16T13:05:36.000Z | 2021-08-16T13:05:36.000Z | wdk-ddi-src/content/wdm/ns-wdm-_dma_adapter.md | henke37/windows-driver-docs-ddi | 787885908a0474b7e2c3d2f8a47355dee62c7aec | [
"CC-BY-4.0",
"MIT"
] | null | null | null | wdk-ddi-src/content/wdm/ns-wdm-_dma_adapter.md | henke37/windows-driver-docs-ddi | 787885908a0474b7e2c3d2f8a47355dee62c7aec | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
UID: NS:wdm._DMA_ADAPTER
title: _DMA_ADAPTER (wdm.h)
description: The DMA_ADAPTER structure describes a system-defined interface to a DMA controller for a given device. A driver calls IoGetDmaAdapter to obtain this structure.
old-location: kernel\dma_adapter.htm
tech.root: kernel
ms.date: 04/30/2018
keywords: ["DMA_ADAPTER structure"]
ms.keywords: "*PADAPTER_OBJECT, *PDMA_ADAPTER, DMA_ADAPTER, DMA_ADAPTER structure [Kernel-Mode Driver Architecture], PDMA_ADAPTER, PDMA_ADAPTER structure pointer [Kernel-Mode Driver Architecture], _DMA_ADAPTER, kernel.dma_adapter, kstruct_a_030ef4da-75e2-4427-baf6-cb9a5eb194cf.xml, wdm/DMA_ADAPTER, wdm/PDMA_ADAPTER"
req.header: wdm.h
req.include-header: Wdm.h, Ntddk.h, Ntifs.h
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: "*PADAPTER_OBJECT, DMA_ADAPTER, *PDMA_ADAPTER"
f1_keywords:
- _DMA_ADAPTER
- wdm/_DMA_ADAPTER
- PADAPTER_OBJECT
- wdm/PADAPTER_OBJECT
- DMA_ADAPTER
- wdm/DMA_ADAPTER
topic_type:
- APIRef
- kbSyntax
api_type:
- HeaderDef
api_location:
- Wdm.h
api_name:
- DMA_ADAPTER
---
# _DMA_ADAPTER structure
## -description
The <b>DMA_ADAPTER</b> structure describes a system-defined interface to a DMA controller for a given device. A driver calls <a href="/windows-hardware/drivers/ddi/wdm/nf-wdm-iogetdmaadapter">IoGetDmaAdapter</a> to obtain this structure.
## -struct-fields
### -field Version
Specifies the version of this structure. Version 3 of the <b>DMA_ADAPTER</b> structure is available starting with Windows 8. For versions 1 and 2 of this structure, this member is set to the value 1. For more information, see the following Remarks section.
### -field Size
Specifies the size, in bytes, of this structure.
### -field DmaOperations
Pointer to a <a href="/windows-hardware/drivers/ddi/wdm/ns-wdm-_dma_operations">DMA_OPERATIONS</a> structure that contains pointers to DMA adapter functions. The version of the <b>DMA_OPERATIONS</b> structure that this member points to is determined by the version of the <b>DMA_ADAPTER</b> structure. Thus, for version 1 of the <b>DMA_ADAPTER</b> structure, <i>DmaOperations</i> points to version 1 of the <b>DMA_OPERATIONS</b> structure, and so on. For more information about structure versions, see the following Remarks section.
## -remarks
Drivers for devices that use DMA to transfer data use this structure to obtain the addresses of functions that enable use of a DMA controller. Usually, drivers obtain this structure by calling the <a href="/windows-hardware/drivers/ddi/wdm/nf-wdm-iogetdmaadapter">IoGetDmaAdapter</a> routine. Drivers can also obtain this structure by querying for the <a href="/windows-hardware/drivers/ddi/wdm/ns-wdm-_bus_interface_standard">BUS_INTERFACE_STANDARD</a> interface.
<div class="alert"><b>Note</b> When the <b>IoGetDmaAdapter</b> routine returns a pointer to version 1 or version 2 of the <b>DMA_ADAPTER</b> structure, this routine always sets the <b>Version</b> member of this structure to 1. Thus, the caller cannot use the <b>Version</b> member to distinguish between versions 1 and 2 of the <b>DMA_ADAPTER</b> structure. For more information about how to determine the version of a <b>DMA_ADAPTER</b> structure that is returned by this routine, see <a href="/windows-hardware/drivers/ddi/wdm/nf-wdm-iogetdmaadapter">IoGetDmaAdapter</a>.</div>
<div> </div>
## -see-also
<a href="/windows-hardware/drivers/ddi/wdm/ns-wdm-_bus_interface_standard">BUS_INTERFACE_STANDARD</a>
<a href="/windows-hardware/drivers/ddi/wdm/ns-wdm-_dma_operations">DMA_OPERATIONS</a>
<a href="/windows-hardware/drivers/ddi/wdm/nf-wdm-iogetdmaadapter">IoGetDmaAdapter</a>
| 46 | 581 | 0.760617 | eng_Latn | 0.581636 |
c91c9a181bffe844fd8153dbd31529ac904394ca | 3,159 | md | Markdown | _posts/openstack/2015-03-22-elk.md | zjxylc/zjxylc.github.io | 46a5656874f4fdeef8b92904568c6cd49575c18d | [
"MIT"
] | 3 | 2015-06-06T14:53:47.000Z | 2017-09-24T14:40:31.000Z | _posts/openstack/2015-03-22-elk.md | zjxylc/zjxylc.github.io | 46a5656874f4fdeef8b92904568c6cd49575c18d | [
"MIT"
] | null | null | null | _posts/openstack/2015-03-22-elk.md | zjxylc/zjxylc.github.io | 46a5656874f4fdeef8b92904568c6cd49575c18d | [
"MIT"
] | 5 | 2015-03-27T04:46:30.000Z | 2018-11-19T16:01:55.000Z | ---
layout: post
title: ELK日志分析
category: OpenStack
tags: ELK
keywords: ELK 日志分析 ElasticSearch LogStash Kibana Redis OpenStack
description:
---
## 平台结构
Shipper(LogStash) *n --------> Broker(Redis) -----> Indexer(LogStash) ------> Search&Store(ElasticSearch) -----> WebInterface(Kibana)
示例环境
- 中心： 192.168.1.100 redis,agent(LogStash),ElasticSearch,Kibana
- 远程： 192.168.1.101 agent(LogStash)
- 系统： 不做要求，测试环境Ubuntu Server 14.04.2 LTS 64-bit
- JRE： openjdk-7-jre 7u75
- Redis： 2.8.4
- LogStash： 1.4.2
- ElasticSearch： 1.4.4
- Kibana： 4.0.1
## 部署
### 1. 部署ElasticSearch
```
wget https://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-1.4.4.tar.gz
tar zxvf elasticsearch-1.4.4.tar.gz -C /usr/local
cd /usr/local
ln -s elasticsearch-1.4.4 elasticsearch
cd elasticsearch
```
根据需要修改配置文件，默认cluster name为：elasticsearch
启动：
`bin/elasticsearch -d`
### 2. 中心安装redis
```
apt-get install redis-server
```
修改/etc/redis/redis.conf
```
daemonize yes
port 6379
bind 192.168.1.100
logfile /var/log/redis/redis-server.log
appendonly yes
```
重启redis-server
```
service redis-server restart
```
### 3. 部署中心LogStash
```
wget https://download.elasticsearch.org/logstash/logstash/logstash-1.4.2.tar.gz
tar zxvf logstash-1.4.2.tar.gz -C /usr/local/
cd /usr/local
ln -s logstash-1.4.2 logstash
cd logstash
mkdir conf logs
```
配置文件conf/central.conf
```
input {
redis {
host => "192.168.1.100"
port => 6379
type => "redis-input"
data_type => "list"
key => "key_count"
}
}
output {
stdout {}
elasticsearch {
cluster => "elasticsearch"
codec => "json"
protocol => "http"
}
}
```
> 需要启动ElasticSearch后才能启动LogStash，因为上面配置文件的output指向的是ElasticSearch
启动：
`bin/logstash agent --verbose --config conf/central.conf --log logs/stdout.log`
配置文件表示输入来自于redis，使用redis的list类型存储数据，key为"key_count"；输出到elasticsearch，cluster的名称为"elasticsearch";
> 根据自身需要设置运行方式
### 4. 部署Kibana
```
wget https://download.elasticsearch.org/kibana/kibana/kibana-4.0.1-linux-x64.tar.gz
tar zxvf kibana-4.0.1-linux-x64 -C /usr/local
cd /usr/local
ln -s kibana-4.0.1-linux-x64 kibana
cd kibana
```
修改配置文件config/kibana.yml
```
port: 5601
host: "192.168.1.100"
elasticsearch_url: "http://192.168.1.100:9200"
```
启动：
`bin/kibana`
访问地址：
`http://192.168.1.100/5601`
### 5. 部署远程LogStash
与部署中心相似，配置文件不一样
1. 安装java运行环境
2. 安装LogStash
配置文件conf/shipper.conf
```
input {
file {
type => "type_count"
path => ["/data/logs/count/stdout.log", "/data/logs/count/stderr.log"]
exclude => ["*.gz", "access.log"]
}
}
output {
stdout {}
redis {
host => "192.168.1.100"
port => 6379
data_type => "list"
key => "key_count"
}
}
```
配置文件表示输入来自于目录`/data/logs/count/`下的`stdout.log`和`stderr.log`两个文件，且排除该目录下所有`.gz`文件和`access.log`；(这里因为path没有使用通配符，所以exclude是没有效果的)；输出表示将监听到的event发送到redis服务器，使用redis的list保存，key为”key_count”，这里的`data_type`属性和`key`属性应该与中心agent的配置一致
> 这里测试的时候需要确保这个目录和文件存在。根据自身需要配置所要收集的日志文件。
## 后续计划
将ELK这一套环境用来监控OpenStack环境。
## 参考文档
1. [http://nkcoder.github.io/blog/20141031/elkr-log-platform-deploy/](http://nkcoder.github.io/blog/20141031/elkr-log-platform-deploy/)
2. [http://www.elastic.co/guide/](http://www.elastic.co/guide/)
> 感谢原作者
| 17.648045 | 224 | 0.707819 | yue_Hant | 0.337259 |
c91d4396f23c0f3bc5af72bda793a879e49a62ce | 1,951 | md | Markdown | src/pydoc/pymakegridpoint.md | mjc87/SHTOOLS | 8d83c42d1313d5624c4db8c2e57300c5d819834e | [
"BSD-3-Clause"
] | 251 | 2015-01-27T12:58:28.000Z | 2022-03-29T17:19:36.000Z | src/pydoc/pymakegridpoint.md | mjc87/SHTOOLS | 8d83c42d1313d5624c4db8c2e57300c5d819834e | [
"BSD-3-Clause"
] | 193 | 2015-03-11T06:21:08.000Z | 2022-03-31T14:05:45.000Z | src/pydoc/pymakegridpoint.md | mjc87/SHTOOLS | 8d83c42d1313d5624c4db8c2e57300c5d819834e | [
"BSD-3-Clause"
] | 100 | 2015-04-03T07:11:05.000Z | 2022-03-23T23:46:33.000Z | # MakeGridPoint()
Evaluate a real function expressed in real spherical harmonics at a set of points.
# Usage
value = MakeGridPoint (cilm, lat, lon, [lmax, norm, csphase, dealloc])
# Returns
value : float, ndarray
: Value of the function at (lat, lon).
# Parameters
cilm : float, dimension (2, lmaxin+1, lmaxin+1)
: The real spherical harmonic coefficients of the function. The coefficients C0lm and C1lm refer to the cosine (Clm) and sine (Slm) coefficients, respectively, with Clm=cilm[0,1,m] and Slm=cilm[1,l,m].
lat : float, array_like
: The geocentric latitude of the point in degrees.
lon : float, array_like
: The longitude of the point in degrees.
lmax : integer, array_like, optional, default = lmaxin
: The maximum spherical harmonic degree used in evaluating the function.
norm : integer, array_like, optional, default = 1
: 1 (default) = Geodesy 4-pi normalized harmonics; 2 = Schmidt semi-normalized harmonics; 3 = unnormalized harmonics; 4 = orthonormal harmonics.
csphase : integer, array_like, optional, default = 1
: 1 (default) = do not apply the Condon-Shortley phase factor to the associated Legendre functions; -1 = append the Condon-Shortley phase factor of (-1)^m to the associated Legendre functions.
dealloc : integer, array_like, optional, default = 0
: 0 (default) = Save variables used in the external Legendre function calls. (1) Deallocate this memory at the end of the funcion call.
# Description
MakeGridPoint will expand a function expressed in spherical harmonics at a given set of points. The input latitudes and longitudes are in degrees, and the maximum degree used in evaluating the function is the smaller of lmaxin and lmax. The employed spherical harmonic normalization and Condon-Shortley phase convention can be set by the optional arguments norm and csphase; if not set, the default is to use geodesy 4-pi normalized harmonics that exclude the Condon-Shortley phase of (-1)^m.
| 48.775 | 492 | 0.762686 | eng_Latn | 0.990822 |
c91d4f4c35ca0ba41c56b651c1e08325998994a0 | 5,660 | md | Markdown | docs/illustrator/illustrator-basic.md | Benbinbin/blog-design | 6117816de4f2f03dc2176ce443e8ed82dc81f2a2 | [
"MIT"
] | null | null | null | docs/illustrator/illustrator-basic.md | Benbinbin/blog-design | 6117816de4f2f03dc2176ce443e8ed82dc81f2a2 | [
"MIT"
] | null | null | null | docs/illustrator/illustrator-basic.md | Benbinbin/blog-design | 6117816de4f2f03dc2176ce443e8ed82dc81f2a2 | [
"MIT"
] | null | null | null | # 基础操作
常用工具的基本使用方法。
## 快捷键
:point_right: 更多快捷键参考 Adobe 提供的[速查表](https://helpx.adobe.com/cn/illustrator/using/default-keyboard-shortcuts.html)。
## 新建文档
可以根据所需创建特定画板大小的文件，也可以选择常见的预设空文档或模板。
:bulb: 新建文档快捷键：`Ctrl + N`
## 移动
:bulb: 移动工具快捷键：`V`
### 智能参考线
对象在移动时会出现 **<span style="color:purple">紫色</span>** 的线，称为是智能参考线，用以辅助对齐定位。
* 开启/关闭智能参考线： （菜单栏）`视图` -> `智能参考线`
:bulb: 开启/关闭智能参考线快捷键：`Ctrl + U`
### 移动复制
通过复制一个副本的形式进行对象移动。
:bulb: 移动复制：移动对象时按住 `Alt` 键
## 画板
画板相当于一个专门的页面，可单独保存或导出这个画板上的文件。在一个文档中可以使用 `画板工具` 创建多个画板，以便在同一个文档中存储项目相关的所有设计，如 Logo、Banner、leaflet、business card 等。
:bulb: 画板工具快捷键：`Shift + O`
<iframe style="width: 100%;aspect-ratio: 16/9;" src="//player.bilibili.com/player.html?aid=92256512&page=11&high_quality=1&danmaku=0" allowfullscreen="true" loading="lazy"></iframe>
* 调整画板大小：
:key: 方法一：使用`画板工具`调整画板四周的锚点
:key: 方法二：在（选项栏）输入宽高 `w` 和 `H` 数值
:key: 方法三：使用（选项栏）预设画板
<iframe style="width: 100%;aspect-ratio: 16/9;" src="//player.bilibili.com/player.html?aid=92256512&cid=157515112&page=10&high_quality=1&danmaku=0" allowfullscreen="true" loading="lazy"></iframe>
* 修改画板名称：
:key: 方法一：在选项栏修改画板名称
:key: 方法二：在（属性面板）`画板` 双击画板名称进行修改
* 调整画板顺序：在（属性面板）`画板` 中拖拽以更改画板的顺序（导出时可能需要使用该序号）
### 复制画板
<iframe style="width: 100%;aspect-ratio: 16/9;" src="//player.bilibili.com/player.html?aid=92256512&cid=157514923&page=1&high_quality=1&danmaku=0" allowfullscreen="true" loading="lazy"></iframe>
* 以复制副本的方式移动画板：移动画板时按住 `Alt` 键
:warning: 如果希望同时拷贝画板上的图稿，需要激活（选项栏）`移动/复制带画板的图稿`
### 导出画板
可以选择性保存或导出单个/多个画板。
<iframe style="width: 100%;aspect-ratio: 16/9;" src="//player.bilibili.com/player.html?aid=92256512&cid=157515044&page=5&high_quality=1&danmaku=0" allowfullscreen="true" loading="lazy"></iframe>
### 删除画板
<iframe style="width: 100%;aspect-ratio: 16/9;" src="//player.bilibili.com/player.html?aid=92256512&cid=157515032&page=4&high_quality=1&danmaku=0" allowfullscreen="true" loading="lazy"></iframe>
:bulb: 删除画板快捷键：（选择相应的画板）`Delete` 键，
:warning: 删除画板时，不会删除画板上的图稿
## 导航
对画板进行缩放和移动的操作。
### 缩放
:bulb: 缩放工具快捷键：`Z`
#### 任意缩放
<iframe style="width: 100%;aspect-ratio: 16/9;" src="//player.bilibili.com/player.html?aid=92256512&cid=157515252&page=19&high_quality=1&danmaku=0" allowfullscreen="true" loading="lazy"></iframe>
:key: 方法一 ：使用 `缩放工具` 通过点击画板进行任意梯度的缩放（默认是放大，按住 `Alt` 键再点击则为缩小）
:key: 方法二：按住 `Alt` 键，滚动 🖱️ 鼠标滑轮进行任意梯度的缩放
:key: 方法三：使用 `缩放工具` 时按住 🖱️ 鼠标向右拖动放大，向左拖动缩小（无级缩放）
:warning: 要实现无级缩放需要开启`动画缩放`（否则只能进行框选放大，或按住 `Alt` 键框选缩小），开启步骤：（菜单栏）`编辑` -> `首选项` -> `性能` 。
:bulb: （基于画板中央）缩放快捷键：`Ctrl` + `+` 放大，`Ctrl` + `-` 缩小
#### 特定缩放
<iframe style="width: 100%;aspect-ratio: 16/9;" src="//player.bilibili.com/player.html?aid=92256512&cid=157515269&page=20&high_quality=1&danmaku=0" allowfullscreen="true" loading="lazy"></iframe>
<iframe style="width: 100%;aspect-ratio: 16/9;" src="//player.bilibili.com/player.html?aid=92256512&cid=157515269&page=20&high_quality=1&danmaku=0" allowfullscreen="true" loading="lazy"></iframe>
将当前画板缩放至适应窗口：单击（属性面板）`画板` 中特定的画板名称
:bulb: 将当前画板缩放至适应窗口快捷键：`Ctrl + 0`
:bulb: 将所有画板缩放至适应窗口快捷键：`Ctrl + Alt + 0`
### 移动
使用 `抓手工具` 可以左右拖动视图
:bulb: 抓手工具快捷键：按住 `Space`
## 选择
常用的两种选择工具
* `选择工具` 用于选择形状整体，选中的形状其边框会突出显示。用以调整尺寸、旋转形状等。
* `直接选择工具` 用于选择形状的具体锚点，重新调整形状结构。
:bulb: 选择工具的快捷键：`v`
:bulb: 直接选择工具的快捷键：`A`
:bulb: 取消所有选择的快捷键：`Ctrl + Shift + A`
<iframe style="width: 100%;aspect-ratio: 16/9;" src="//player.bilibili.com/player.html?aid=92256512&cid=157515152&page=13&high_quality=1&danmaku=0" allowfullscreen="true" loading="lazy"></iframe>
:warning: 为了可以使用 `选择工具` 对形状进行调整，需要打开定界框，以显式对象四周的锚点
:key:（菜单栏）`视图` -> `显示定界框`
### 选择多个元素
:key: 方法一：使用 `选择工具` 或 `直接选择工具` 框选多个形状或锚点
:key: 方法二：使用 `选择工具` 或 `直接选择工具` 同时按住 `Shift` 键点选多个形状或锚点
:key: 方法三：使用 `套索工具` 圈选多个形状或锚点（当框选形状的部分，然后使用 `直接选择工具` 移动进行操作）
:bulb: 若需要取消其中的一些已选择元素，可以按住 `Shift` 键后点选形状或锚点取消选中
:bulb: 取消所有选择的快捷键：`Ctrl + Shift + A`
* 通过反向选择当前选中元素余下的元素（整个文件内，包括其他画布的元素）：（菜单栏）`选择` -> `反向`
### 锁定元素
通过锁定元素，如背景，避免操作过程中被误选中。
:key: 方法一：（菜单栏）`对象` -> `锁定` -> `所选对象`
:key: 方法二：（属性面板）`图层` 点击元素所在图层单击眼睛图标后方进行锁定
:bell: 若图层过多，可在选定元素后，点击（属性面板）`图层` 下方的搜索按钮 :mag_right: 快速定位
<iframe style="width: 100%;aspect-ratio: 16/9;" src="//player.bilibili.com/player.html?aid=92256512&cid=157515088&page=8&high_quality=1&danmaku=0" allowfullscreen="true" loading="lazy"></iframe>
:bulb: 锁定选中元素的快捷键：`Ctrl + 2`
:bulb: 全部解锁的快捷键：`Alt + Ctrl + 2`
## 对齐与分布
选择（多个）对象后，选项栏会出现对齐（和分布模式）的可视化按钮。
* 对齐模式依次为：水平左对齐、水平居中对齐、水平右对齐、垂直顶对齐、垂直居中对齐、垂直底对齐
* 分布模式依次为：垂直顶分布、垂直居中分布、垂直底分布、水平左分布、水平居中分布、水平右分布
在（属性面板）`对齐` 中进行更详细的对齐与分布设置，如设置对齐的参考系：
* 对齐所选对象
* 对齐关键对象（可以设置间距），如果选择了对齐关键对象后，关键对象会显示为深蓝色，如果需要更改参考对象，此时可以点击画布中任一选中的对象将其作为关键对象。
* 对齐画板
<iframe style="width: 100%;aspect-ratio: 16/9;" src="//player.bilibili.com/player.html?aid=92256512&cid=157515293&page=21&high_quality=1&danmaku=0" allowfullscreen="true" loading="lazy"></iframe>
## 元素排列
元素的排列是指其**在其图层中**叠放的先后次序
:key: 方法一：选中元素后点击鼠标右键 -> `排列` 选择需要调整的排列方式
:bulb: 置于顶层的快捷键 `Shift + Ctrl + ]`
:bulb: 前移一层的快捷键 `Ctrl + ]`
:bulb: 后移一层的快捷键 `Ctrl + [`
:bulb: 置于底层的快捷键 `Shift + Ctrl + [`
:key: 方法二：在（属性面板）手动拖拽元素（分组）调整它在图层中的相对顺序
<iframe style="width: 100%;aspect-ratio: 16/9;" src="//player.bilibili.com/player.html?aid=92256512&bvid=BV1S7411N7WV&cid=220777547&page=23&high_quality=1&danmaku=0" allowfullscreen="true" loading="lazy"></iframe>
| 23.292181 | 213 | 0.710601 | yue_Hant | 0.49033 |
c91ea337037ad7368cd251de1f63c7c34764f90a | 70 | md | Markdown | README.md | hunyadi-dev/librdkafka_demo | ea465405f570b0ec7965dfeb83aa5e228348fbf3 | [
"Apache-2.0"
] | null | null | null | README.md | hunyadi-dev/librdkafka_demo | ea465405f570b0ec7965dfeb83aa5e228348fbf3 | [
"Apache-2.0"
] | null | null | null | README.md | hunyadi-dev/librdkafka_demo | ea465405f570b0ec7965dfeb83aa5e228348fbf3 | [
"Apache-2.0"
] | null | null | null | # librdkafka_demo
Demo repository for librdkafka related tests (C++).
| 23.333333 | 51 | 0.785714 | eng_Latn | 0.477605 |
c91ef4b18b5319e7b6f144e83ef9ae987a439cad | 8,669 | md | Markdown | docs/Grove-XBee_Carrier.md | speedbug78/wiki_english | 9581b9ee9668634eeb16e26158fb5e7115caf229 | [
"MIT"
] | 1 | 2020-08-11T02:42:40.000Z | 2020-08-11T02:42:40.000Z | docs/Grove-XBee_Carrier.md | speedbug78/wiki_english | 9581b9ee9668634eeb16e26158fb5e7115caf229 | [
"MIT"
] | null | null | null | docs/Grove-XBee_Carrier.md | speedbug78/wiki_english | 9581b9ee9668634eeb16e26158fb5e7115caf229 | [
"MIT"
] | null | null | null | ---
name: Grove - XBee Carrier
category: Sensor
bzurl: https://www.seeedstudio.com/grove-xbee-carrier-p-905.html?cPath=132_134
oldwikiname: Grove - XBee Carrier
prodimagename: Bee_Stem.jpg
surveyurl: https://www.research.net/r/Grove-XBee_Carrier
sku: 113020004
---
The Grove - XBee Carrier is a Wireless Sensor Network (WSN) base board designed for Bee series and Grove units. It is primarily suitable for standalone Bee Nodes like RFBee, Wifi Bee which have ATMega328 onboard and XBee (Zigbee) modules. It is compatible with [RFBee](/RFbee_V1.1-Wireless_Arduino_compatible_node "RFbee V1.1 - Wireless Arduino compatible node"), [Wifi Bee](/Wifi_Bee "Wifi Bee"), [XBee](http://garden.seeedstudio.com/index.php?title=Bee_series#ZigBee "Bee_series#ZigBee") and [Bluetooth Bee](/Bluetooth_Bee "Bluetooth Bee"). Besides a Bee receptacle, there are also two Grove connectors. The board can be powered by a lithium battery or through USB cable. You can use a Wireless charger, Solar Panel or the USB cable to charge the battery. The FT232RL chip onboard helps in downloading the program to Bee Module directly.
Bees which do not have ATMega328 like Bluetooth Bee can only be configured by using on-board FT232RL (USB to UART). Theses Bees are not suitable for standalone applications.
The on-board FT232RL can be used like any other 3.3V USB to UART interface when not connected to any Bee Modules. This is useful for programming a 3.3V MCU through Serial Port.
[](https://www.seeedstudio.com/grove-xbee-carrier-p-905.html?cPath=132_134)
## Features
---
* Bees Compatible Receptacle
* Two Grove Connectors
* Two Grove Place Holders
* LEDs for PWR, Charge Indication and UART transmission.
* Power Switch
* Reset Button
## Application Ideas
---
* Wireless Sensor Network with Standalone Bee Node like [Wifi Bee](/Wifi_Bee "Wifi Bee").
* As a configuration aid for Bees using FT232RL.
* Charger for Lithium Ion Cells using on-board charge controller.
* As a FT232RL based 3.3v USB-UART.
## Cautions
---
<font color="red">
</font>
* Insert the Bees in the proper direction. Use the Bee outline on the silk-screen.
## Specification
---
<table cellspacing="0" width="80%">
<tr>
<th scope="col"> Item
</th>
<th scope="col"> Min
</th>
<th scope="col"> Typical
</th>
<th scope="col"> Max
</th>
<th scope="col"> Unit
</th></tr>
<tr>
<th scope="row"> Voltage
</th>
<td> 3.0
</td>
<td> 3.3
</td>
<td> 3.6
</td>
<td> VDC
</td></tr>
<tr>
<th scope="row"> Charge Controller
</th>
<td colspan="4"> CN3063
</td></tr>
<tr>
<th scope="row"> CHARGER (Charging Voltage for LiPo Battery)
</th>
<td colspan="4"> 4.4V to 6V (as per CN3063 Spec)
</td></tr>
<tr>
<th scope="row"> Charging Current
</th>
<td colspan="4"> Max 500mA
</td></tr>
<tr>
<th scope="row"> 3.3V LDO
</th>
<td colspan="4"> Low Noise and Micropower type. Suitable for Battery Application.
</td></tr>
<tr>
<th scope="row"> I/O Logic
</th>
<td colspan="4"> 3.3V Logic
</td></tr></table>
## Interface Function
---
**U2:** RT9167A_33PB IC, 3.3V LDO Lownoise Micropower Regulator
**U3:** CN3083 IC, Charger controller for Lithium batteries (charging using solar panel)
**U4:** FT232RL IC, USB to serial UART interface
## Usage
---
When using an RFBee, the following pinouts of ATmage168 on RFBee apply for using the Arduino IDE
Pin 5 is the Grove connector for I/O - Yellow wire
Pin 6 is the Grove connector for I/O - White wire
Pin 16 may need to be driven low to provide enough power to the I/O Grove [via mosfet]
Pin 17 may need to be driven low to provide enough power to the I2C Grove [via mosfet]
**Note:** you can use the x2 Grove cable with the white and yellow wires swapped on one to access both I/O.
### Hardware Installation
#### Charging
Now you can choose a suitable battery for your application from **SeeedStudio** [Batteries and Chargers](/Solar_Charger_Shield_V2.2 "Solar_Charger_Shield_V2.2")
* Connect a 3.7v LiPo battery to **BAT** JST-socket.
* Connect a power source like Solar Panel to **CHARGER** JST-Socket.
* The Battery will be continuous charged. The end of charging would be indicated by LED marked 'OK'.
#### Working with Standalone Bee Nodes
Bee Nodes are standalone Arduino Compatible Wireless Nodes. **SeeedStudio** has two such Nodes - [Wifi Bee](/Wifi_Bee "Wifi Bee") and [RFBee](/RFbee_V1.1-Wireless_Arduino_compatible_node "RFbee V1.1 - Wireless Arduino compatible node").
* The following image illustrated the connection of [WiFi Bee](/Wifi_Bee "Wifi Bee") to **Grove - XBee Carrier**.
* Any Groves can be connected to the Grove sockets provided.
* The programming of WiFi Bee's onboard **AtMega328P** is carried by connecting to PC through USB port. (FT232RL is used)
Bee Stem Connected to Wifi BEE and A Twig.jpg
* Refer [Wifi Bee usage documentation for programming examples](http://garden.seeedstudio.com/index.php?title=Wifi_Bee#Usage "Wifi_Bee#Usage")
Bee Stem Connected To RFBee And TwoTwigs.jpg
#### Working with Bee Modules
This section is about those Bee modules which do not have a MCU pre-programmed with Arduino bootloader. They mostly act just like a wireless trans-receiver. These **Bee Modules** like Bluetooth Bee, etc.. can communicated with PC as well. In this case, **Grove - XBee Carrier** acts as a carrier for these Bees providing necessary power, communication interface with PC through FT232RL USB to UART.
* In the below example [Bluetooth Bee](/Bluetooth_Bee "Bluetooth Bee") is connected to **Grove - XBee Carrier** and configured using USB-UART
* The communication of Bluetooth Bee and PC is captured with a serial port terminal application.
* You can see the commands and their reply in the screenshot below.
* The Bluetooth Bee was put into INQ mode and it even has detected a Bluetooth device in the vicinity.
* For more information on using [Bluetooth Bee](/Bluetooth_Bee "Bluetooth Bee"), consult the [Bluetooth Bee Commands documentation](/Bluetooth_Bee#Commands_to_change_default_configuration "Bluetooth Bee").
### Programming
```
/*
Test code for use with an XBee Carrier & an RF Bee
Turns on PD5 (eg: grove relay) on for one second, then off for one second, repeatedly.
*/
void setup()
{
// initialize the digital pin as an output [Pin 5 is the Grove connector for I/O
pinMode(5, OUTPUT);
// These lines are needed to ensure that the relay will pull in [provides power to the Grove]
pinMode(16, OUTPUT);
digitalWrite(16, LOW);
}
void loop() {
digitalWrite(5, HIGH); // set the LED on
delay(1000); // wait for a second
digitalWrite(5, LOW); // set the LED off
delay(1000); // wait for a second
}
```
## Version Tracker
---
<table>
<tr>
<th> Revision
</th>
<th> Descriptions
</th>
<th> Release
</th></tr>
<tr>
<td width="300px"> v0.9b
</td>
<td width="500px"> Initial public release
</td>
<td width="200px"> 13th July 2011
</td></tr></table>
## Resources
---
* [Grove - XBee Carrier Eagle Files](https://github.com/SeeedDocument/Grove-XBee_Carrier/raw/master/res/PCBA-Grove%20XBee%20Carrier_Eagle.rar)
* [Grove - XBee Carrier PDF schematics file](https://github.com/SeeedDocument/Grove-XBee_Carrier/raw/master/res/Bee_Stem_v0.9b.pdf)
* [CN3063](http://www.consonance-elec.com/pdf/%E6%8A%80%E6%9C%AF%E8%AF%B4%E6%98%8E%E4%B9%A6/DSC-CN3063.pdf)
* [RT9167A_33PB](http://www.richtek.com/download_ds.jsp?s=238)
## Tech Support
Please submit any technical issue into our [forum](http://forum.seeedstudio.com/). <br /><p style="text-align:center"><a href="https://www.seeedstudio.com/act-4.html?utm_source=wiki&utm_medium=wikibanner&utm_campaign=newproducts" target="_blank"><img src="https://github.com/SeeedDocument/Wiki_Banner/raw/master/new_product.jpg" /></a></p> | 37.855895 | 839 | 0.73584 | eng_Latn | 0.774062 |
c91f31cb52c47d6f63020d6e74041ca4fe74f0a4 | 6,767 | md | Markdown | README.md | Kometia-Themes/Cycle | 188d8506575a3fa65a252a8a83a03d4aca2eefe5 | [
"MIT"
] | 1 | 2018-05-04T16:38:25.000Z | 2018-05-04T16:38:25.000Z | src/README.md | Shoperti-Themes/Cycle | 188d8506575a3fa65a252a8a83a03d4aca2eefe5 | [
"MIT"
] | 6 | 2021-05-08T23:39:54.000Z | 2022-02-26T11:12:59.000Z | src/README.md | Shoperti-Themes/Cycle | 188d8506575a3fa65a252a8a83a03d4aca2eefe5 | [
"MIT"
] | null | null | null | # Shoperti Cycle Theme 1.0
> Este es el tema instalado en [Cycle] (https://cycle-theme.shoperti.com/) y puede servirte de inspiración. Úsalo como base para crear uno nuevo, realizar ajustes pequeños o modificaciones. Sin duda, puede ser el punto de partida para aprender a construir tus propios temas desde cero.
>
> **Para más detalles sobre el desarrollo del tema, lee nuestra [Documentación del tema] (https://github.com/Shoperti-Themes/Cycle)**.
## Obteniendo este tema
1. [Descargar] (https://github.com/Shoperti-Themes/Cycle/archive/master.zip) la última versión de la rama master.
2. También puedes clonar el repositorio con git: <code>git clone [email protected]:Shoperti-Themes/Cycle.git</code>
## Implementación manual
La opción más sencilla, si no deseas realizar cambios en el tema, es cargar el archivo [theme.zip] (dist/theme.zip) encontrado dentro de la carpeta 'dist' del archivo theme.zip descargado.
**Puedes realizar cualquier cambio directamente descomprimiendo el archivo zip, sin embargo, no es recomendable porque se puede dañar alguna parte del código.**
## Personalizando el tema
Para facilitar aún más el desarrollo y la implementación del tema, utiliza las herramientas para construcción con Webpack incluídas.
Estas tareas toman el código fuente del 'src' (source), lo procesa y empaqueta en un zip para ser instalado.
### Instalando Node
Para compilar el tema debes tener Node. Para saber si cuentas con él, ve a tu terminal y escribe `node -v` y podrás ver algo así `v6.9.1` si ya lo tienes instalado. En caso contrario, ve al sitio de [Node] (https://nodejs.org/download/) y sigue las intrucciones.
1. Navega hasta la raíz de este proyecto descargado.
2. Ejecuta `npm install` para NPM o `yarn install` si usas Yarn.
Npm/Yarn examinará [package.json] (package.json) e instalará automáticamente las dependencias locales necesarias.
** ¿Qué es `npm` y `yarn`? Ambos son gestores de paquetes [npm] (http://npmjs.org/) / [yarn] (https://yarnpkg.com) y es una forma de administrar dependencias de desarrollo a través de Node.
## Comandos y funcionalidades
Existen 2 comandos, uno para desarrollo y otro para producción:
```
$ npm dev
$ npm build
```
```npm dev``` sirve para publicar tus archivos html, estilos y scripts en la carpeta **public** y así construir tu sitio sin funcionalidades de Twig. Incluye un servidor http para ver el sitio usando la ruta http://localhost:9000
```npm build``` genera una carpeta 'theme' dentro de 'dist' que te servirá para probar tu plantilla en ambiente local. Algunos archivos ahora tendrán la extensión ```.twig```.
Estas tareas toman el código fuente del tema y lo empaquetan en un zip para ser instalado.
### Implementación del tema
Instala un tema básico, puede ser Simplex, por ejemplo, y copia el contenido de cada archivo que hay al descomprimir el archivo theme.zip que está dentro de 'dist'.
Crea los 'partials' que no existan y que necesites, al igual en las páginas nuevas, layouts, estilos y scripts.
### Tareas de Webpack
Cada vez que corras alguno de los comandos desde tu terminal, Webpack realizará varias acciones, cómo compilar tus estilos CSS, SASS, LESS, Javascript o empaquetar los archivos.
Si quiere saber más sobre ve [Webpack 2](https://webpack.js.org/).
Para crear las páginas, estilos y scripts sin empaquetarse ejecuta: `npm dev` o `yarn dev` y Webpack estará en estado 'watch' esperando cambios para compilar y actualizar las vistas, scripts o estilos.
Para crear un empaquetado final para distribuir ejecuta: `npm build` o `yarn build `
Todo el contenido de la carpeta 'dist' se eliminará para colocar los nuevos archivos.
#### Estructura de los estilos
Es posible agregar cualquier tipo de hoja de estilo o preprocesador (less o sass).
Si deseas agregar una hoja CSS, sólo debe agregarla a la carpeta ```src/assets/``` con el nombre que gustes.
Ejemplo: miestilo.css
Para poder usar dicha hoja en el template, deberás agregarla al archivo ```src/app.js``` con esto sabrá Webpack lo que debe hacer.
Ejemplo:
```var css = require('./assets/miestilo.css');```
Puedes agregar cualquier archivo siguiendo el orden deseado de importación.
Ejemplo:
```
// Default Stylesheet
var sassfile = require('./assets/styles.scss');
var lessfile = require('./assets/lessfile.less');
var cssfile = require('./assets/miestilo.css');
```
Puedes importar archivos dentro de less o sass usando la tradicional nomenclatura.
Ejemplo:
```
// Less miarchivo.less
@import "miarchivo";
// Sass _miarchivo.scss
@import "miarchivo";
```
Variables:
Recuerda declarar las variables, ya sea en less o scss, con ```$``` o ```@```, según corresponda al tipo de archivo.
## Estructura final
```
theme
├── 1.0.0
| ├── assets
│ │ ├── app.js.twig
│ │ ├── apple-touch-icon-114.png
│ │ ├── apple-touch-icon-144.png
│ │ ├── blur-password.jpg
│ │ ├── favicon.ico
│ │ └── styles.css.twig
│ │
│ ├── config
│ │ ├── data.json
│ │ └── schema.json
│ │
│ ├── layouts
│ │ └── layout.twig
│ │
│ ├── pages
│ │ └── customers
│ │ │ ├── account.twig
│ │ │ ├── activate.twig
│ │ │ ├── login.twig
│ │ │ ├── order.twig
│ │ │ ├── recover.twig
│ │ │ ├── register.twig
│ │ │ └── reset.twig
│ │ │
│ │ ├── blog.twig
│ │ ├── cart.twig
│ │ ├── category.twig
│ │ ├── collection.twig
│ │ ├── collections.twig
│ │ ├── error404.twig
│ │ ├── home.twig
│ │ ├── maintenance.twig
│ │ ├── page.contact.twig
│ │ ├── page.twig
│ │ ├── password.twig
│ │ ├── post.twig
│ │ ├── product.twig
│ │ ├── products.twig
│ │ └── search.twig
│ │
│ ├── partials
│ │ └── ...
│ │
│ ├── screeshots
│ │
│ ├── .editorconfig
│ ├── .gitignore
│ ├── findreplace.js
│ ├── LICENSE
│ ├── README.md
│ ├── removefiles.js
│ ├── screenshot.png
│ ├── webpack.config.js
│ └── webpack.production.config.js
```
## Versionado
Para mayor transparencia y comprensión de nuestro ciclo de lanzamiento, y para tratar de mantener la compatibilidad con versiones anteriores, este proyecto se mantendrá en la medida de lo posible bajo las directrices de Versión Semántica.
`<Major>. <Minor>. <Patch>`
* `MAJOR` versión al realizar cambios incompatibles,
* `MINOR` cuando se agregue una funcionalidad de una manera que siga siendo compatible con versiones anteriores.
* `PATCH` cuando se corrijan errores compatibles con versiones anteriores.
Para obtener más información sobre [SemVer] (http://semver.org/lang/es/).
## Copyright
© Copyright Shoperti 2018 - Ver [TÉRMINOS Y CONDICIONES](https://www.shoperti.com/terminos-y-condiciones) para más detalles.
| 38.016854 | 285 | 0.703414 | spa_Latn | 0.97954 |
c91f6031544d47ede1904ecd620dd3e45b8e3268 | 6,262 | md | Markdown | client/docs/design/menu.md | thegrumpys/pcyl-web | a2e003c5cf2fc975d61729f1665e194bdf41fed3 | [
"MIT"
] | null | null | null | client/docs/design/menu.md | thegrumpys/pcyl-web | a2e003c5cf2fc975d61729f1665e194bdf41fed3 | [
"MIT"
] | 130 | 2018-07-03T06:42:31.000Z | 2018-08-17T19:09:55.000Z | client/docs/design/menu.md | thegrumpys/pcyl-web | a2e003c5cf2fc975d61729f1665e194bdf41fed3 | [
"MIT"
] | null | null | null | # Ideas for a web page menu structure
# July 13, 2018 - Updated July 23, 2018
# Menu Bar:
Current thinking has a conventional horizontal menu bar located at the top of the
page. Five main menu items should look like:
Sys-Name | File | Action | View | Help |
--- | --- | --- | --- | ---
---
# Menu Items:
* Sys-Name
* Link to web site
* File
* Open
* Save
* Save As
# ------------------
* Recent Designs
# ------------------
* System Preferences
# ------------------
* Action
* Search
* Seek
* Trade
# ----------------
* Select Size
* Select Catalog
# ----------------
* Execute
# ----------------
* View
* Define Sub-Problems
* Display Sub-Problems
#### ----------------
* Report
#### ----------------
* Calculation Inputs
* Violations
* Help
* Context Help F1
* Help Index
* Demo
* Tutorial
* About
---
# Menu Item Descriptions:
# Sys-Name : Web site
This menu item is a link to the public-facing web site. The linked page will open in a new
browser tab.
# File : Open
This menu item is similar to the PCyl-CLI START command. See issue #23 for additional detail on system (main web page) initialization.
# File : Save
This menu item is similar to the PCyl-CLI Save command. It over-writes the most
recently opened design file (.DSN) or database entry.
# File : Save As
This menu item is similar to the PCyl-CLI Save command. It creates a new design file
(.DSN) or database entry.
# -------------------------------------
# File : Recent designs
These menu entries are provided for user convenience in selecting recent designs for review or additional work.
# -------------------------------------
# File : System Preferences
This item provides a user interface to set system-specific values, including much of what is done by the PCyl-CLI SET command.
For example, system internal variables such as IOOPT, OBJMIN, FIX_WT, etc.
Other web-specific items, for example, auto re-calc and auto-search preferences, may be included.
Web page layout control should be handled in the View menu.
# -------------------------------------
# Action : Search
This menu item invokes the Search - directly equivalent to the PCyl-CLI Search
command. There may also be a search button on the main page. This menu item is
provided primarily to maintain consistency.
# Action : Seek
This menu item invokes Seek - directly equivalent to the PCyl-CLI Seek command.
There may also be Seek button(s) on the main page. This menu item is provided
primarily to maintain consistency.
# Action : Trade
This menu item provides a similar feature to the PCyl-CLI Trade command. One
possible implementation is to pop up a form where the user can specify a strategy
(radio buttons similar to the current 0 - 3), over-ride step size and decide to keep the
result or not.
# -------------------------------------
# Action : Select Size
This menu item allows a table look-up for a standard size of a specific Independent
Variable. It is similar to the PCyl-CLI SELECT command.
# Action : Select Catalog
This menu item allows the selection of the "nearest" design from a catalog of
standard designs. It is similar to the PCyl-CLI SELECT CATALOG command.
# -------------------------------------
# Action : Execute
This menu item will trigger the play-back of a previously recorded sequence. A popup
(?) can provide the user an opportunity to supply a (file?) name to specify the
sequence. Some mechanism, for example, user supplied pauses will likely be
necessary to allow the user to control the pace so as to observe what is happening.
Annotations / comments are probably necessary.
The process of creating play-back sequences (files?) is not required to be user
accessible.
If necessary, generic third party tools can be used to create and annotate play-back
recordings.
# -------------------------------------
# View : Define Sub-Problems
This menu item provides a user interface to control "IOCLASS" for independent and
dependent variables plus "static quantities".
# View : Display Sub-Problems
This menu item allows the user to specify a group of IOCLASSes be displayed. This
frequently requested feature can allow complex design problems to be "partitioned"
into sub-problems that map to sub-systems of the real world. Notably, selecting
(check in checkbox?) classes 2, 4 & 6 would display those variables / quantities
and suppress the display of all others.
# -------------------------------------
# View : Report
This menu item creates a .PDF file and invokes the system .PDF utility to display it.
Both generic (Independent & Dependent variables, constraint levels & violations, etc.)
as well as problem-specific data in problem-specific formats can be included in the
report. The user can use the features of the system .PDF utility in order to save the
file into the browser's local file system.
# -------------------------------------
# View : Calculation Inputs
A check in the checkbox will cause "calculation inputs" (previously known as
"constants") to be displayed.
# View : Violations
A check in the checkbox will cause both constraint violations and the value of the
objective function to be displayed.
# Help : Context Help F1
This menu item opens a new browser tab containing a context-specific web page
describing the current task (for example, the Trade pop-up form). Hitting the F1 key
produces the same result.
# Help : Help Index
This menu item opens a new browser tab containing the index page for the Help subsystem.
All Help topics should be reachable through links on the index page.
# Help : Demo
This menu item provides the ability to select from a list of demo sessions which play
back similarly to the Action : Execute menu item.
The demo sessions may include solutions to textbook problems in order to illustrate that the
program closely matches published results.
# Help : Tutorial
This menu item provides the ability to select from a list of tutorial sessions which play
back similarly to the Action : Execute menu item.
# Help : About
This menu item provides software release and design model version information. It
also includes a link to the home page of publicly-facing web site (a repeat of the sys-name link).
The linked page will open in a new browser tab.
| 36.406977 | 136 | 0.703449 | eng_Latn | 0.995612 |
c9207e710ab8380144a8967163fc2426704eaf73 | 484 | md | Markdown | README.md | TunedMystic/markette | 160408918be78efecd2ef4368fb506fbec7e9e02 | [
"MIT"
] | 1 | 2020-06-26T11:52:29.000Z | 2020-06-26T11:52:29.000Z | README.md | TunedMystic/markette | 160408918be78efecd2ef4368fb506fbec7e9e02 | [
"MIT"
] | 5 | 2020-03-15T18:27:48.000Z | 2020-04-05T23:45:34.000Z | README.md | TunedMystic/markette | 160408918be78efecd2ef4368fb506fbec7e9e02 | [
"MIT"
] | 1 | 2020-06-26T16:14:11.000Z | 2020-06-26T16:14:11.000Z | skol
---
[](https://travis-ci.com/TunedMystic/skol)
[](https://codecov.io/gh/TunedMystic/skol)
Skol is a simple Python project skeleton, built with starlette and asyncpg.
### Quickstart
Build the app containers with `make build`
Start the app with `make start`
Run tests with `make test`
Remove containers with `make remove`
| 28.470588 | 122 | 0.756198 | eng_Latn | 0.626189 |
c92108ca3b222471cc58c7ad1d70c03cb309b549 | 1,858 | md | Markdown | _posts/PS/2021-10-15-post.md | chajuhui123/chajuhui123.github.io | 4eafaeeb160bfef37ba0a15b34f23c322af73bc4 | [
"MIT"
] | null | null | null | _posts/PS/2021-10-15-post.md | chajuhui123/chajuhui123.github.io | 4eafaeeb160bfef37ba0a15b34f23c322af73bc4 | [
"MIT"
] | null | null | null | _posts/PS/2021-10-15-post.md | chajuhui123/chajuhui123.github.io | 4eafaeeb160bfef37ba0a15b34f23c322af73bc4 | [
"MIT"
] | 1 | 2021-08-30T06:49:46.000Z | 2021-08-30T06:49:46.000Z | ---
layout: post
title: "[PS/JavaScript] 문자열 내 마음대로 정렬하기
(연습문제) - 프로그래머스"
description: ""
date: 2021-10-15 11:30
tags: [PS, 프로그래머스, JavaScript]
comments: false
share: false
---
> [문제출처 : 문자열 내 마음대로 정렬하기 (연습문제) - 프로그래머스](https://programmers.co.kr/learn/courses/30/lessons/12915)
---
# 문제 설명 📝
문자열로 구성된 리스트 strings와, 정수 n이 주어졌을 때, 각 문자열의 인덱스 n번째 글자를 기준으로 오름차순 정렬하려 합니다. 예를 들어 strings가 ["sun", "bed", "car"]이고 n이 1이면 각 단어의 인덱스 1의 문자 "u", "e", "a"로 strings를 정렬합니다.
<br/>
### 제한사항
- strings는 길이 1 이상, 50이하인 배열입니다.
- strings의 원소는 소문자 알파벳으로 이루어져 - 있습니다.
- strings의 원소는 길이 1 이상, 100이하인 문자열입니다.
- 모든 strings의 원소의 길이는 n보다 큽니다.
- 인덱스 1의 문자가 같은 문자열이 여럿 일 경우, 사전순으로 앞선 문자열이 앞쪽에 위치합니다.
<br/>
### 입출력 예
|strings|n|return|
|---|---|---|
|["sun", "bed", "car"]|1|["car", "bed", "sun"]|
|["abce", "abcd", "cdx"]|2|["abcd", "abce", "cdx"]|
<br/>
# 풀이과정 💡
### 1️⃣ 문제이해
정렬을 잘 다룰 수 있는가를 파악하기 위한 문제입니다.
sort문을 활용하는 것을 떠올렸습니다.
<br/>
### 2️⃣ 수도코드
1. 배열 아이템의 n번째 인덱스의 요소들을 비교
2. 더 큰 문자를 앞에 정렬, 작은 문자는 뒤에 정렬
3. 크기가 같다면 strings 사전에서 먼저 오는 요소를 앞에 정렬
<br/>
### 3️⃣ 코드
```javascript
function solution(strings, n) {
strings.sort((a, b)=>{
if (a[n] > b[n]) return 1; // 앞에 있는 문자열이 우선순위 높은 경우
else if (a[n] < b[n]) return -1; // 뒤에 있는 문자열이 우선순위 높은 경우
else { // 두 문자열의 우선순위 같은 경우
if(a>b) return 1; // strings 사전순으로 먼저 있는 것이 먼저 옴
if(a<b) return -1;
}
});
return strings;
}
```
<br/>
### 4️⃣ 정리
### `localCompare()`
기준 문자열과 비교했을 때 비교 대상 문자열이 정렬상 전에 오는지, 후에 오는지 혹은 같은 순서에 배치되는지를 알려주는 숫자를 리턴
```javascript
// "a"는 "c"의 앞에 오기 때문에 음수 값을 리턴
'a'.localeCompare('c'); // -2 or -1 (or some other negative value)
//알파벳 순으로 "check"는 "against"의 뒤에 오기 때문에 양수 값을 리턴
'check'.localeCompare('against'); // 2 or 1 (or some other positive value)
// "a"는 "a"와 같기 때문에 0
'a'.localeCompare('a'); // 0
``` | 17.364486 | 168 | 0.581808 | kor_Hang | 1.00001 |
c921dd2af97e9471c2ed5959122c9f8861441b94 | 4,725 | md | Markdown | _posts/2010/2010-10-11-find-the-smallest-prime-greater-than-an-input-number.md | manbat/vsoch.github.io | b5ea22652bcb44977c5905cfd6671b28643c0ebe | [
"BSD-3-Clause"
] | 10 | 2016-01-30T00:42:42.000Z | 2021-07-05T21:56:10.000Z | _posts/2010/2010-10-11-find-the-smallest-prime-greater-than-an-input-number.md | manbat/vsoch.github.io | b5ea22652bcb44977c5905cfd6671b28643c0ebe | [
"BSD-3-Clause"
] | 20 | 2015-09-06T23:52:08.000Z | 2021-06-25T17:32:33.000Z | _posts/2010/2010-10-11-find-the-smallest-prime-greater-than-an-input-number.md | manbat/vsoch.github.io | b5ea22652bcb44977c5905cfd6671b28643c0ebe | [
"BSD-3-Clause"
] | 9 | 2015-09-08T23:57:03.000Z | 2022-02-21T07:43:07.000Z | ---
title: "Find the smallest prime greater than an input number"
date: 2010-10-11 20:01:25
tags:
code
grelin
matlab
puzzle
---
that is also in the Fibonacci Sequence!
For this one I left in all my print lines that were used for debugging / testing purposes. This script takes in a number, and finds the smallest prime that is greater than that number that is also part of the [Fibonacci Sequence](http://en.wikipedia.org/wiki/Fibonacci_sequence). It starts with the numbers 1 and 1, of course (the first two in the Fibonacci Sequence) and moves upward in the sequence until it hits a member of the sequence that is above the input number. It stops at the two members of the sequence before this number, and then adds these two numbers, tests if the outcome is prime, and if so, returns the value as an answer. If not, it calculates the next number in the sequence, and continues testing.
- The main function is called prime_fibonacci() with the number going in as input. There are two subfunctions one_up, which moves us up one order in the sequence to the next two numbers (so from 1, 1 to 1 2, for example) and
- is_prime: which does exactly what you would think – it first tests if the number is divisible by two, and if so, returns false (0). If not, it takes in an input number and tests for primeness by dividing by all possible factors – 1 through the (number + 1) /2. The modulus function is used for this test. In the case that there is no remainder, this means that the number is not prime, and we return false. In the case that there is always a remainder, then hooray! The number is prime, and we return it as the answer.
<pre>
<code>
function prime_fibonacci(number)
% Find 2 fibonacci numbers below the number given by the user. Start with
% n_one as 1, and n_two as 1, and slowly work upwards until we are just
% below the user specified number.
n_one = 1;
n_two = 1;
% n_one is always larger, we check it first. At the end of this loop we
% have the two numbers in the Fibonacci sequence directly before our input
% number
fprintf('%s%d%s%d\n','Number one is ',n_one,' and Number two is ',n_two);
while n_one < number && n_two < number
if n_one + n_two <= number
[n_one,n_two] = up_one(n_one,n_two);
fprintf('%s\n','The summed numbers are still less than the input number, getting next set.');
fprintf('%s%d%s%d\n','Number one is now ',n_one,' and Number two is ',n_two);
else
fprintf('%s\n','The summed numbers would be equal or greater than the input number, stopping');
break;
end
end
% We add the two numbers to get the next number in the Fibonacci sequence,
% which we know is larger than our number after the tests above. We now
% need to check if this number is a prime. If yes, then we've found our
% answer. If not, then we need to look at the next number.
decision = 0;
while decision == 0;
decision = isprime(n_one + n_two);
if decision == 0
fprintf('Creating a new set of numbers...')
fprintf('%s%d%s%d\n','New Numbers: Number one (',n_one, ') and Number two: (',n_two, ')');
[n_one,n_two] = up_one(n_one,n_two);
else
answer = n_two + n_one;
fprintf('%s%d%s%d%s%d\n','The sum of Number one (',n_one, ') and Number two (',n_two, ') is a prime number! ',answer);
fprintf('%s%d\n','The answer is ',answer);
end
end
%--------------------------------------------------------------------------
% Function isprime
%
% This function checks if an input number is prime by dividing by all
% possible factors through the input number / 2. In the case that there
% is always a remainder for all these divisions, we know that the number
% has to be prime, meaning that it is only divisible by 1 and itself.
%--------------------------------------------------------------------------
function f = isprime(number_two)
% if our number is even, we don't continue
if mod(number_two,2)==0
fprintf('%s%d%s%d\n','The number ',number_two,' is even so it cannot be prime');
f = 0;
return;
else
fprintf('%s%d%s\n','The number ',number_two,' is not even, checking divisibility')
for i = 3:(number_two/2)
fprintf('%s%d\n','Checking divisibility for ',i)
if mod(number_two,i) == 0
fprintf('%d%s\n',number_two,' is divisible by ',i, ' and therefore cannot be prime!');
f = 0;
return;
end
end
f = 1;
fprintf('%d%s\n',number_two,' is not divisible by anything and is therefore prime!');
return
end
end
%--------------------------------------------------------------------------
% Function upone
%
% This function creates the next two fibonacci numbers. n_one is always
% treated as the larger of the two.
%--------------------------------------------------------------------------
function [numone,numtwo] = up_one(one, two)
numone = one + two;
numtwo = one;
return
end
end
</code>
</pre>
| 40.042373 | 720 | 0.68 | eng_Latn | 0.999217 |
c921e19df9c58b9a61c7315515abc5d98e6afac2 | 6,560 | md | Markdown | MPSSC/README.md | ishspsy/project | 704804ccba0f65ea07735676f2d61a54b09e138c | [
"MIT"
] | 18 | 2017-07-25T18:04:11.000Z | 2021-08-24T02:27:16.000Z | README.md | zhengzhongpku/project | 704804ccba0f65ea07735676f2d61a54b09e138c | [
"MIT"
] | 3 | 2018-03-15T06:59:27.000Z | 2021-04-02T07:01:30.000Z | README.md | zhengzhongpku/project | 704804ccba0f65ea07735676f2d61a54b09e138c | [
"MIT"
] | 11 | 2018-02-13T06:25:24.000Z | 2021-03-13T14:00:16.000Z | # MPSSC: Spectral clustering based on learning similarity matrix
## Overview
*MPSSC* is a novel spectral clustering framework that imposes sparse structures on a target matrix. Specifically, it utilizes multiple doubly stochastic affinity matrices to construct a normalized graph Laplacian (Step 1). Then, it imposes a sparse structure on the target matrix (Step 2) followed by shrinking pairwise differences of the rows in the target matrix (Step 3). This spectral clustering method uses multiple similarity matrices via non-convex optimization framework. *MPSSC* solves the proposed non-convex problem iteratively with the embedded ADMM algorithm.
### Main functions
[clus_fin_update.m](https://github.com/ishspsy/project/blob/master/MPSSC/Code/clus_fin_update.m)
: Main *MPSSC* algorithm (with similarity learning) consisting of the three steps.
[clus_fin_update_no_learning.m](https://github.com/ishspsy/project/blob/master/MPSSC/Code/clus_fin_update_no_learning.m)
: Main *PSSC* algorithm (without similarity learning).
[func_doubly.m](https://github.com/ishspsy/project/blob/master/MPSSC/Code/func_doubly.m)
: Contruct multiple doubly stochastic similarity matrices using Gaussian kernels (Step 1).
[clus_sim_update2_2.m](https://github.com/ishspsy/project/blob/master/MPSSC/Code/clus_sim_update2_2.m)
: Obtain the intermediate target matrix involving ADMM step (Step 2).
[clus_sim_update0_3.m](https://github.com/ishspsy/project/blob/master/MPSSC/Code/clus_sim_update0_3.m)
: Obtain the final target matrix involving ADMM step (Step 3).
### Example files
Please follow the links to reproduce the clustering results of real scRNA-seq data sets
- [small-scale scRNA-seq data sets](https://github.com/ishspsy/project/blob/master/MPSSC/Working_m_files/running_small_scRNA%20(Fig4%2C6).m)
: Generate all the results related to the six small-scale scRNA-seq data sets.
- [large-scale scRNA-seq data sets](https://github.com/ishspsy/project/blob/master/MPSSC/Working_m_files/running_large_scRNA%20(Fig5).m)
: Generate all the results related to the three large-scale scRNA-seq data sets. These were run on the computing cluster (6 CPUs, 800 GB of memory).
- [generating all figures](https://github.com/ishspsy/project/tree/master/MPSSC/Working_m_files/Figure_generate)
: Generate all figures presented in the manuscript.
**Note** Most of the simulations and scRNA-seq applications were implemented on an Apple MacBook Pro (2.7 GHz, 8 GB of memory) using the MATLAB 2016b. However, certain computational or memory-intensive steps (e.g. larger-scale data sets) were run on the computing cluster (6 CPUs, 800 GB of memory).
```
%Example using Deng data set:
clear all
addpath(genpath(pwd))
%% load data sets ('in_X' and 'true_labs')
load('Data_Deng.mat')
% Note: one can use any data set that consists of in_X and true_labs, where in_X is an n by p gene
%expression matrix and true_labs is the ground truth labels. Here n and p are number of cells and
%genes, respectively.
%% Penalty parameters. We use the following specification:
rho=0.2; lam=0.0001; lam2=lam; eta=1; c=0.1;
%% Run MPSSC and obtain the target matrix P
[P] = clus_fin_update(rho, lam, lam2, eta, c, in_X, true_labs);
%% Obtain clustering labels "clus_labs" and compute NMI measure:
[NMI, ~,clus_labs,~]=calc2_nmis(max(true_labs), double(P),true_labs);
%% Compute performance measures
% Compute Purity
Purity=purity(max(true_labs), clus_labs, true_labs)
% Compute ARI
ARI=RandIndex(clus_labs,true_labs)
%%% Final output: Performances (three measures) of MPSSC
[NMI, Purity, ARI]
```
### Directory
All the functions used in the proposed algorithm are located in the directory ["**Code**"](https://github.com/ishspsy/project/tree/master/MPSSC/Code).
All the matlab functions generating results in the manuscript are located in the directory ["**Working_m_files**"](https://github.com/ishspsy/project/tree/master/MPSSC/Working_m_files).
**All the codes generating figures shown in the manuscript are located in the directory ["**Working_m_files/Figure_generate**"](https://github.com/ishspsy/project/tree/master/MPSSC/Working_m_files/Figure_generate).
All the resulting files (e.g. .MAT and .eps) are located in the directory ["**Results_files**"](https://github.com/ishspsy/project/tree/master/MPSSC/Results_files).
The nine scRNA-seq data sets used in the manuscript are located in the directory ["**Data**"](https://github.com/ishspsy/project/tree/master/MPSSC/Data).
The other directories:
["SIMLR"](https://github.com/ishspsy/project/tree/master/MPSSC/SIMLR) includes all the files related to *SIMLR*.
["SparseSC"](https://github.com/ishspsy/project/tree/master/MPSSC/SparseSC) includes all the files related to Sparse spectral clustering (*SSC*).
["tSNE"](https://github.com/ishspsy/project/tree/master/MPSSC/tSNE) includes all the files related to *t-SNE*.
["KPCA.1"](https://github.com/ishspsy/project/tree/master/MPSSC/KPCA.1) includes the files related to kernel construction.
Specifically, the codes of *SIMLR* refers to https://github.com/BatzoglouLabSU/SIMLR, *SparseSC* refers to https://github.com/canyilu/LibADMM, *tSNE* refers to https://lvdmaaten.github.io/tsne/, and *KPCA.1* refers to
https://arxiv.org/abs/1207.3538.
## Example data sets
The 9 data sets are provided in the directory [*Data*](https://github.com/ishspsy/project/tree/master/MPSSC/Data).
Specifically, the dataset of Data_Deng.mat refers to http://science.sciencemag.org/content/343/6167/193.
Data_Ting.mat refers to https://www.ncbi.nlm.nih.gov/pubmed/25242334.
Data_Treutlin.mat refers to https://www.ncbi.nlm.nih.gov/pubmed/24739965.
Data_Ginhoux.mat refers to https://www.ncbi.nlm.nih.gov/pubmed/26054720.
Data_Buettner.mat refers to https://www.ncbi.nlm.nih.gov/pubmed/25599176.
Data_Pollen.mat refers to https://www.nature.com/articles/nbt.2967.
For the large scale data, Data_Zeisel.mat refers to https://www.ncbi.nlm.nih.gov/pubmed/25700174.
Data_Tasic.mat refers to https://www.ncbi.nlm.nih.gov/pubmed/26727548.
Data_Macosko.mat refers to https://www.ncbi.nlm.nih.gov/pubmed/26000488.
## DOWNLOAD
We provide MATLAB implementations of *MPSSC* in the MPSSC branch.
## Authors
* [**Seyoung Park**](http://people.yale.edu/search/seyoung_park.profile) and [**Hongyu Zhao**](https://publichealth.yale.edu/biostat/people/hongyu_zhao.profile)
Department of Biostatistics, School of Public Health, Yale University
## Contact
* [email protected]
## License
This project is licensed under the MIT License.
| 40.493827 | 572 | 0.771037 | eng_Latn | 0.735733 |
c9220deef9814f539ced714a655102f7310ac895 | 1,244 | md | Markdown | api/Excel.Slicer.Cut.md | skucab/VBA-Docs | 2912fe0343ddeef19007524ac662d3fcb8c0df09 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-04-08T20:10:22.000Z | 2021-04-08T20:10:22.000Z | api/Excel.Slicer.Cut.md | skucab/VBA-Docs | 2912fe0343ddeef19007524ac662d3fcb8c0df09 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-09-28T07:52:15.000Z | 2021-09-28T07:52:15.000Z | api/Excel.Slicer.Cut.md | skucab/VBA-Docs | 2912fe0343ddeef19007524ac662d3fcb8c0df09 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-09-28T07:45:29.000Z | 2021-09-28T07:45:29.000Z | ---
title: Slicer.Cut method (Excel)
keywords: vbaxl10.chm905090
f1_keywords:
- vbaxl10.chm905090
ms.prod: excel
api_name:
- Excel.Slicer.Cut
ms.assetid: a8778661-612f-0031-78b0-d59bb87fdf62
ms.date: 06/08/2017
localization_priority: Normal
---
# Slicer.Cut method (Excel)
Cuts the specified slicer and copies it to the clipboard.
## Syntax
_expression_. `Cut`
_expression_ A variable that represents a '[Slicer](Excel.Slicer.md)' object.
## Example
The following code example accesses the Customer slicer by using the **[Range](Excel.Shapes.Range.md)** property of the **[Shapes](Excel.Shapes.md)** collection, and then cuts and pastes it into the active worksheet.
```vb
ActiveSheet.Shapes.Range(Array("Customer")).Select
Selection.Cut
ActiveSheet.Paste
```
Alternatively, you can perform the same operation by using the **[Slicers](Excel.SlicerCache.Slicers.md)** property of the **[SlicerCaches](Excel.SlicerCaches.md)** collection to access the slicer, as shown in the following code example.
```vb
ActiveWorkbook.SlicerCaches("Slicer_Customer") _
.Slicers("Customer").Cut
ActiveSheet.Paste
```
## See also
[Slicer Object](Excel.Slicer.md)
[!include[Support and feedback](~/includes/feedback-boilerplate.md)] | 22.214286 | 238 | 0.752412 | eng_Latn | 0.871731 |
c9226fce59ed689dd6158f84098c6a4b7760472b | 22,337 | md | Markdown | readme.md | x2c3z4/slack-bot | 53d0cbca8bbe5c7f56d3ae4cfea5294c9efe6d0c | [
"MIT"
] | null | null | null | readme.md | x2c3z4/slack-bot | 53d0cbca8bbe5c7f56d3ae4cfea5294c9efe6d0c | [
"MIT"
] | null | null | null | readme.md | x2c3z4/slack-bot | 53d0cbca8bbe5c7f56d3ae4cfea5294c9efe6d0c | [
"MIT"
] | null | null | null | # Slack Bot
This Slack bot improves the workflow of development teams. Especially with focus on Jenkins, Github, Gitlab and Jira, as the integration is working out of the box.
But also custom commands, macros, crons and other project specific commands can be implemented in a simple and flexible way.
[](https://github.com/innogames/slack-bot/actions)
[](https://pkg.go.dev/github.com/innogames/slack-bot/v2/)
[](https://goreportcard.com/report/github.com/innogames/slack-bot)
[](https://github.com/innogames/slack-bot/releases)
[](https://codecov.io/gh/innogames/slack-bot)
[](https://opensource.org/licenses/MIT)
[](https://hub.docker.com/r/brainexe/slack-bot)
[](https://github.com/avelino/awesome-go)
# Installation
## 1st) Create+prepare the Slack App:
### Recommended way: Use Manifest file as App template
1. Create a [Slack App](https://api.slack.com/apps?new_app=1)
2. Select "From an app manifest"
3. Select your Workspace
4. Paste this Yaml code:
<details>
<summary>Click to expand!</summary>
```yaml
_metadata:
major_version: 1
minor_version: 1
display_information:
name: slack_bot
features:
app_home:
messages_tab_enabled: true
messages_tab_read_only_enabled: false
bot_user:
display_name: bot
always_online: true
oauth_config:
scopes:
bot:
- app_mentions:read
- channels:read
- chat:write
- im:history
- im:write
- mpim:history
- reactions:read
- reactions:write
- users:read
- files:write
settings:
event_subscriptions:
bot_events:
- app_mention
- message.im
interactivity:
is_enabled: true
org_deploy_enabled: false
socket_mode_enabled: true
```
</details>
5. Create the App!
6. Go to "Basic Information"
7. -> in "App-Level Tokens", "Generate a Token" with the scope "connections:write"
8. You will see a App-Level Token (beginning with xapp-). Set it in the config.yaml as slack.socket_token.
9. Go to "OAuth & Permissions":
10. -> "Install to Workspace"
11. -> you should see a "Bot User OAuth Access Token" (beginning with "xoxb-"). Use it as slack.token in the config.yaml
12. start the bot!
### Alternative: Manual steps when **not** using the App Manifest
<details>
<summary>Expand steps!</summary>
- Create a [Slack App](https://api.slack.com/apps?new_app=1)
- Select from scratch and choose a name and workspace.
- Go to "Socket Mode" menu and activate it.
- - use any token name, like "Slack-Bot Socket Mode token"
- - You will see a App-Level Token (beginning with xapp-). Sse it in the config.yaml as slack.socket_token.
- Enable "Interactivity & Shortcuts"
- Enable "Event Subscriptions":
- - if you see a "Send events to my app using the new format" checkbox, check it (only for old migrated apps)
- - in "Subscribe to bot events", add "app_mention" and "message.im" events
- Go to "OAuth & Permissions":
- - use the "Bot User OAuth Access Token" (beginning with "xoxb-") as slack.token in the config.yaml
- - in "Scopes" we need this permissions: "app_mentions:read", "channels:read", "chat:write", "im:history", "im:write", "users:read", "reactions:read", "reactions:write"
- Go to "Install your App" and "Install your app to your workspace"
- Back to "Install app" tab, the "Bot User OAuth Access Token" is visible (starts with "xoxb-"). You need this one in the config.yaml in slack->token.
</details>
## 2nd) Run the bot
### Option 1: run via go
1. install go
2. create a config.yaml (at least a slack token is required) or take a look in config-example.yaml
3. `go run github.com/innogames/slack-bot/v2/cmd/bot`
### Option 2: via Docker
1. [install Docker incl. docker-compose](https://docs.docker.com/get-docker/)
2. clone this repo or at least fetch the docker-compose.yaml
3. create a config.yaml (at least a slack token is required) or take a look in config-example.yaml
4. add your Slack user id or user name in the "allowed_users:" section of the config.yaml
5. `docker-compose up`
### Option 3: Advanced:when planning working on the bot core
1. install go (at least 1.16)
2. clone/fork this repo
3. create a config.yaml (at least a slack token is required) or take a look in config-example.yaml
4. run `go run cmd/bot/main.go` or `make run` to run the go application
# Usage
As slack user, you just have to send a private message to the bot user/app containing the command to execute.
Additionally you can execute bot commands in channels by prefix your command with @bot_name, e.g. `@slack-bot start job DailyDeployment`
**Note:** You have to invite the bot into the channel to be able to handle commands.
# Bot Commands
## Help
The `help` command just prints a list of all available commands of this bot.
With `help *command*` you'll get a short description and some examples for a single command.
## Jenkins (optional)
The bot is able to start and monitor jenkins job on a simple but powerful way.
By default the commands are not available and not visible in the "help", till the "jenkins.host" is defined in the config file.
### Start Jenkins jobs
The `start job` command starts a Jenkins job and shows the current progress. **Attention:** only whitelisted jobs in the config are startable!
In additions each job can have a configurable `trigger` which make it possible to create custom commands to start jobs. (it's a regexp which takes parameter names into account).
E.g. "start daily deployment" could be the trigger for one jenkins job. Sending this text to the bot would start he job.
After starting a job the bot will show the estimated build time and some action buttons. There you can open the logs or abort the build directly.
The bot is also able to parse parameters and lookup branch names using a fuzzy branch search.
**Examples:**
- `trigger job DeployBeta`
- `start job BackendTests TEST-123` (search for a full branch name, containing TEST-123. e.g. feature/TEST-123-added-feature-456)
### Jenkins build notifications
The bot has also the possibility to create one time notifications for jenkins builds. This might be useful for long running jobs where the devs is waiting for the result.
**Example:**
- `inform me about build NightlyTests` (watches the most recent running build)
- `inform me about build MyJobName #423` (specify a build number)
- `inform job MyJobName` (alternative syntax)
### Jenkins job notifications
Receive slack messages for all process builds for the given job:
**Example:**
- `watch JenkinsSelfCheck` notifies about any build of Job `JenkinsSelfCheck`
- `unwatch JenkinsSelfCheck`
### Jenkins status
Small command to disable/enable job execution on Jenkins side.
**Example:**
- `disable job NightlyTests` (disable job on jenkins)
- `enable job NightlyTests`
### Jenkins retry
When a build failed you are able to retry any build by:
**Example:**
- `retry build NightlyTests` (retries the last build of a job)
- `retry build NightlyTests #100` (retries given build)
### Nodes
`jenkins nodes` lists all available Jenkins nodes. The online/offline status and number of executors are visible.
## Pull Requests
If you just paste a link to a Github/Gitlab/Bitbucket/Stash Pull request, the bot will track the state of the ticket!
- When a developer was added as reviewer, it will add a "eyes" reaction to show other devs that someone is already taking a look
- When the reviewer approved the ticket, a checkmark is added
- After merging the pull request, it will add a "merge" reaction
You're also able to set custom "approved" reactions. E.g to see directly who or which component/department approved a pull request you can use the name of the reaction or the Unicode character directory
<details>
<summary>Expand example!</summary>
```yaml
pullrequest:
reactions:
merged: custom_merge_arrow
review: 👀
custom_approve_reaction:
nerdydev: "approved_backend"
iamamobiledev: "approved_mobile"
iamamobiledev2: "approved_mobile"
```
</details>
**Extra Features:**
For Bitbucket the bot is able to extract the current build status (e.g. from Jenkins/Bamboo etc) and show failed and running builds (fire reaction) as a reaction (circle arrow reaction). When the build is stable, the build reactions disappear.
## Command Queue
The `queue` command (with the alias `then`) is able to queue the given command, until the currently running command finished.
Example following scenario: you have a build job (which might take some minutes) and a deploy job which relies of the build artifacts. Now you can do:
- `trigger job Build feature1234` to start the Build job with given branch
- `queue trigger job DeployBranch feature1234`
- `queue reply Deployment is done!`
**Other example:**
- `delay 1h`
- `then send message #backend coffee time?`
To see all running background commands (like Jenkins jobs or PR watcher) use this command:
- `list queue`
## Jira (optional)
The bot is able to query information from Jira, either from a single ticket, or a whole list of tickets.
By default the commands are not available and not visible in the "help", till the "jira.host" is defined in the config file.
**Examples**
- `jira TEST-1234`
- `jira 1242` (opens the ticket, using the configured default jira project)
- `jql type=bug and status=open` (use default project by default)
- `jira "Second city"` (text search of tickets in default project)
It's also possible to get a notification when there is a state change in a certain Jira ticket.
**Example**
- `watch ticket PROJ-12234`
## Interactions
It's possible to create buttons which are performing any bot action when pressing the button.
[Slack interactions](https://api.slack.com/interactivity/actions)
**Examples:**
- `add button "Start Deployment" "trigger job LiveDeployment"`
**Note**
- only whitelisted users can click the button
- each button is only active once
## Custom variables
Configure user specific variables to customize bot behaviour. E.g. each developer has his own server environment.
**Example:** Having this global config:
```yaml
commands:
- name: Deploy
trigger: "deploy (?P<branch>.*)"
commands:
- deploy {{.branch}} to {{ customVariable "defaultServer" }}
```
Each developer can now call ONCE this commands like: `set variable defaultSerer foobarX.local` to register the custom "defaultServer".
When now calling `deploy mater`, it will deploy the `master` branch to `foobarX.local` server.
**Another example**
Here an advanced version which uses [Go templates](https://golang.org/pkg/text/template/).
In the end the command will generate one subcommand, like:
`reply <!here> demo for <https://jira.example.com/TEST-1234|TEST-1234: Example-Ticket>` which will post the link to the Slack channel.
```yaml
- name: demo
trigger: "demo (?P<ticketId>\\w+-\\d+)"
commands:
- |
{{ $ticket := jiraTicket .ticketId }}
{{ if $ticket }}
reply <!here> demo for <{{ jiraTicketUrl $ticket.Key }}|{{ $ticket.Key }}: {{ $ticket.Fields.Summary }}>
{{ else }}
reply Ticket {{ .ticketId }} not found :white_frowning_face:
{{ end }}
description: Informs the current channel about a demo of a Jira ticket. It directly posts a link to the ticket
examples:
- demo XYZ-1232
```
User can define his default environment once by using `set variable serverEnvironment aws-02`.
Then the `deploy feature-123` will deploy the branch to the defined `aws-02` environment.
Each user can define his own variables.
## Quiz command
If you need a small break and want to play a little quiz game you can do so by calling this command.
No more than 50 questions are allowed.
The questions are from different categories and difficult levels and are either multiple choice or true/false questions.
**Commands**
- `quiz 10` to start a quiz with 10 questions
- `answer 1` to answer a question with the first answer
## Weather command (optional)
It's possible to setup [OpenWeatherMap](https://openweathermap.org/) to get information about the current weather at your location.
**Example config:**
```yaml
open_weather:
apikey: "612325WD623562376678"
location: "Hamburg, DE"
units: "metric"
```
## Custom command
Every user is able to define own command aliases.
This is a handy feature to avoid typing the same command every day.
**Example usage**
- `list commands` to just list the defined commands for the current user
- `add command 'myCommand' 'trigger job RestoreWorld 7` -> then just call `myCommand` later
- `add command 'build master' 'trigger job Deploy master ; then trigger job DeployClient master'`
- `delete command 'build master'`
- -> then you can execute `myCommand` to trigger this jenkins job
## Commands
Defined "Commands" (former called "Macros") are very magical and can be defined in the yaml configuration files.
They have a trigger (a regular expression) and have a list of sub commands which will be executed.
They take parameter groups from regexp into account - so they can be very flexible!
One simple example to start two Jenkins jobs with a given branch name at the same time:
```yaml
commands:
- name: build clients
trigger: "build clients (?P<branch>.*)"
commands:
- "reply I'll build {{ .branch }} for you"
- "trigger job BuildFrontendClient {{ .branch }}"
- "trigger job BuildMobileClient {{ .branch }}"
- "then reply done! :checkmark:"
```
**Note**: In the commands you can use the full set of [template features of go](https://golang.org/pkg/text/template/) -> loops/conditions are possible!
### Template functions
Beside the usual [template features of go](https://golang.org/pkg/text/template/) a bunch of bot specific commands are available in the template scope.
A list of all available functions (with arguments and return types) can be generated by using the `list template functions` command.
**Note:** This template functions can be used in different commands/features:
- [Crons](#cron)
- [Defined commands](#commands) (via .yaml)
- [Custom commands](#custom-command) (defined per user)
- [Jenkins hooks](#jenkins) (lik send custom message when a Job fails)
## Retry
With `retry` or `repeat` your last executed command will be re-executed. -> Useful when a failed Jenkins job got fixed.
## Delay
A small command which might be useful in combination with `command` command or as hook for jenkins jobs.
Example command: `delay 10m trigger job DeployWorldwide`
As reply you'll get a command to stop the queued job (like `stop timer 123456`). As everyone can send the command, the command can be used to announce a deployment and in doubt, the execution can still be stopped by everyone.
## Reply / send message
`reply` and `send message` are also small commands which are useful in combination with `command` or jenkins hooks.
**Examples:**
- `send message to #backend The job failed :panic:`
- `delay 10m send message to @peter_pan I should notify you to...`
## Random
Simple command if you are not able to decide between different options
**Examples**
- `random Pizza Pasta` -> produce either "Pizza" or "Pasta"
- `random Peter Paul Tom Jan` -> who has to take about organizing food today?
# Installation
1. Make sure Go version 1.12+ is installed
2. clone the project
3. create config file called `config.yaml` (you can take a look at `config.example.yaml`)
## Run without docker
This command will start the bot, using the `config.yaml` file by default. Use the `-config` argument to use the config file(s) from another location.
```
go run cmd/bot/main.go
```
## Run via docker-compose
**Attention**: Create a config.yaml file first
```
docker-compose up
```
# Configuration
The configuration is managed via simple .yaml files which are storing the credentials for the external services and the custom commands etc.
The easiest way is to just have one `config.yaml` file with all needed options included the `config.yaml` is loaded by default. It's also possible to split up the configuration into multiple files.
**Example structure with mutiple config files:**
- `secret.yaml` containing the credentials for the external services (slack, jenkins) - can be managed by puppet/ansible etc.
- `jenkins.yaml` configuration of jenkins job and their parameters etc
- `project-X.yaml` custom commands for a specific team
- `project-Y.yaml`
To load the multiple config files, use `go run cmd/bot/main.go -config /path/to/config/*.yaml` which merged all configs together.
## Slack
To run this bot, you need a "bot token" for your slack application. See the [installation](#installation) section how to create a proper app with the needed tokens.
## Jenkins config
To be able to start or monitor jenkins jobs, you have to setup the host and the credentials first. The user needs read access to the jobs and the right to trigger jobs for your whitelisted jobs.
```
jenkins:
host: https://jenkins.example.de
username: jenkinsuser
password: secret
```
### Jenkins jobs
To be able to start a job, the job and it's parameters have to be defined in the config.
A job without any parameter looks very simple:
```yaml
jenkins:
jobs:
CleanupJob:
```
Then you can use `trigger job CleanupJob` or `start job CleanupJob` to start the job. It will also notify you when the job succeeded or failed (incl. error log).
Next a job with two parameters:
```yaml
jenkins:
jobs:
RunTests:
parameters:
- name: BRANCH
default: master
type: branch
- name: GROUP
default: all
```
This job can handle two parameters:
- BRANCH: VCS branch name, "master" as default
- GROUP: optional parameter, using "all" as default
If you setup the VSC in the config, you don't have to pass the full branch name but can use the fuzzy search.
**Example:**
- `start job RunTests` would start "all" groups on master branch
- `start job JIRA-1224 unit` would try to find a matching branch for the ticket number. (Error message if there is no unique search result!)
Now a more complex example with more magic:
```yaml
jenkins:
jobs:
DeployBranch:
trigger: "deploy (?P<BRANCH>[\\w\\-_\\.\\/]*) to (?P<ENVIRONMENT>prod|test|dev)"
parameters:
- name: BRANCH
default: master
type: branch
- name: ENVIRONMENT
onsuccess:
- reply Tadaa: Take a look on http://{{ .ENVIRONMENT }}.example.com
```
**Step by step:**
The `trigger` is a regular expression to start the job which may contain named groups. The regexp groups will be matched to the job parameters automatically.
Then you can use `deploy bugfix-1234 to test` to start the jenkins job.
**Note:** You can always start this job also via `start job DeployBranch master`. The `trigger` is just an alternative.
The `onsuccess` is a hook which will be executed when a job ist started via this bot.
In addition `onsuccess` and `onerror` is also available...e.g. to send custom error messages.
### Cron
It's possible to define periodical commands via crons, using the [robfig/cron library](github.com/robfig/cron).
**Example config**
```yaml
crons:
- schedule: "0 8 * * *"
commands:
- trigger job BuildClients
- then deploy master to staging
channel: "#backend"
```
## VCS / Stash / Bitbucket
To be able to resolve branch names in jenkins trigger, a VCS system can be configured (at the moment it's just Stash/Bitbucket).
```yaml
vcs:
type: bitbucket
host: https://bitbucket.example.com
username: readonlyuser
password: secret
project: MyProjectKey
repository: repo_name
```
If no config is provided, there is no automated branch lookup and the "branch" parameters are passed 1:1 to the jenkins job.
# Development
## File structure
- `bot/` contains the code classes of the bot: connection to slack, user management, command matching...
- `cmd/bot/` entry points aka main.go for the bot and the CLI test tool
- `command/` real command implementing the bot.Command interface
- `client/` communication interfaces for Slack, Jenkins, Jira etc...
## Create a new (native) command
If you need a new command, which is not implementable with a "command" command, you have to write to write go code.
- create a new file within the "commands/" directory or one submodule of it
- create a new struct which fulfills the bot.Command interface. The service.SlackClient might be needed as dependency
- GetMatcher() needs to provide the information which command text is matching our command
- register the command in command/commands.go
- restart the bot application
- it's recommended to fulfill the bot.HelpProvider (your command will show up in `help)
- it's also recommended to create a integration test for your command
## CLI tool
There is a handy CLI application which emulates the Slack application...just chat with your local console without any Slack connection!
```
make run-cli
```
## Auto live reload
`make air` to use the ["air auto reload tool"](https://github.com/cosmtrek/air).
## Testing
There are a bunch of tests which can be executed via:
```
make test
```
Test coverage is generated to build/coverage.html
```
make test-coverage
```
| 40.030466 | 245 | 0.73179 | eng_Latn | 0.990951 |
c9228621f182e740781e9add7f389aa5d7cc344e | 6,937 | md | Markdown | articles/sql-database/sql-database-elastic-jobs-service-installation.md | OpenLocalizationOrg/azuretest1_zh-CN | 358681cf517ea1d0b86fff60a5f45d3c4762670d | [
"CC-BY-3.0"
] | null | null | null | articles/sql-database/sql-database-elastic-jobs-service-installation.md | OpenLocalizationOrg/azuretest1_zh-CN | 358681cf517ea1d0b86fff60a5f45d3c4762670d | [
"CC-BY-3.0"
] | null | null | null | articles/sql-database/sql-database-elastic-jobs-service-installation.md | OpenLocalizationOrg/azuretest1_zh-CN | 358681cf517ea1d0b86fff60a5f45d3c4762670d | [
"CC-BY-3.0"
] | null | null | null | ---
ms.openlocfilehash: a809d4d86304cb54dd9e44db5bce754b05375464
ms.sourcegitcommit: bab1265d669c3e6871daa7cb8a5640a47104947a
translationtype: MT
---
<properties
pageTitle="安装弹性数据库作业"
description="逐步安装弹性作业功能。"
services="sql-database"
documentationCenter=""
manager="jhubbard"
authors="sidneyh"
editor=""/>
<tags
ms.service="sql-database"
ms.workload="sql-database"
ms.tgt_pltfrm="na"
ms.devlang="na"
ms.topic="article"
ms.date="08/03/2015"
ms.author="ddove; sidneyh"/>
# 安装弹性数据库作业概述
**弹性数据库作业**可以安装通过 PowerShell 或 Azure 的入口，虽然您才可以访问用于创建和管理作业使用 PowerShell API，只有在安装 PowerShell 包。 此外，PowerShell Api 提供多得多的功能比门户在此时间点。 关于**弹性数据库作业**的详细信息，请参阅[弹性数据库作业概述](sql-database-elastic-jobs-overview.md)。
如果您已经从现有**弹性数据库池**安装**弹性数据库作业**通过门户网站，最新的 Powershell 预览包括用于将现有安装升级脚本。 强烈建议要充分利用新功能，通过 PowerShell Api 公开将安装升级到最新的**弹性数据库作业**组件。
## 先决条件
* Azure 的订阅。 免费试用版，请参阅[免费试用版](http://azure.microsoft.com/pricing/free-trial/)。
* Azure PowerShell 版本 > = 0.8.16。 安装最新版本 (0.9.5) 通过[Web 平台安装程序](http://go.microsoft.com/fwlink/p/?linkid=320376)。 有关详细信息，请参阅[如何安装和配置 Azure PowerShell](powershell-install-configure.md)。
* [NuGet 命令行实用程序](https://nuget.org/nuget.exe)用于安装弹性数据库作业包。 有关详细信息，请参阅 http://docs.nuget.org/docs/start-here/installing-nuget。
## 下载并导入弹性数据库作业 PowerShell 包
1. 启动 Microsoft Azure PowerShell 命令窗口并定位到您下载 NuGet 命令行实用工具 (nuget.exe) 的目录。
2. 下载并将**弹性数据库作业**包导入到当前目录中使用下面的命令︰
PS C:\>.\nuget install Microsoft.Azure.SqlDatabase.Jobs -prerelease
**弹性数据库作业**文件放在一个名为**Microsoft.Azure.SqlDatabase.Jobs.x.x.xxxx.x** *x.x.xxxx.x*在其中反映的版本编号文件夹中的本地目录。 （包括所需的客户端的.dll） 的 PowerShell cmdlet 都位于**tools\ElasticDatabaseJobs**子目录，PowerShell 脚本来安装、 升级和卸载也驻留在**工具**的子目录中。
3. 导航到工具 Microsoft.Azure.SqlDatabase.Jobs.x.x.xxx.x 文件夹下的子目录下，键入 cd 工具，例如︰
PS C:\*Microsoft.Azure.SqlDatabase.Jobs.x.x.xxxx.x*>cd tools
4. 执行.\InstallElasticDatabaseJobsCmdlets.ps1 脚本将 ElasticDatabaseJobs 目录复制到 $home\Documents\WindowsPowerShell\Modules。 这将自动导入模块供使用，例如︰
PS C:\*Microsoft.Azure.SqlDatabase.Jobs.x.x.xxxx.x*\tools>Unblock-File .\InstallElasticDatabaseJobsCmdlets.ps1
PS C:\*Microsoft.Azure.SqlDatabase.Jobs.x.x.xxxx.x*\tools>.\InstallElasticDatabaseJobsCmdlets.ps1
## 安装使用 PowerShell 的弹性数据库作业组件
1. 启动 Microsoft Azure PowerShell 命令窗口，然后定位到 \tools 的 Microsoft.Azure.SqlDatabase.Jobs.x.x.xxx.x 文件夹下的子目录︰ 键入 cd \tools
PS C:\*Microsoft.Azure.SqlDatabase.Jobs.x.x.xxxx.x*>cd tools
2. 执行.\InstallElasticDatabaseJobs.ps1 PowerShell 脚本，并提供为其请求变量的值。 此脚本将创建所述[弹性数据库作业组件和定价](sql-database-elastic-jobs-overview/#components-and-pricing)及适当地使用从属组件将 Azure 云服务配置的组件。
PS C:\*Microsoft.Azure.SqlDatabase.Jobs.x.x.xxxx.x*\tools>Unblock-File .\InstallElasticDatabaseJobs.ps1
PS C:\*Microsoft.Azure.SqlDatabase.Jobs.x.x.xxxx.x*\tools>.\InstallElasticDatabaseJobs.ps1
当您运行此命令时打开一个窗口，要求输入**用户名**和**密码**。 这不是 Azure 凭据、 输入的用户名称和要创建的新服务器的管理员凭据的密码。
在此示例调用提供的参数可以修改为您所需的设置。 下面提供了每个参数的行为的详细信息︰
<table style="width:100%">
<tr>
<th>参数</th>
<th>说明</th>
</tr>
<tr>
<td>ResourceGroupName</td>
<td>提供创建包含新创建的 Azure 组件的 Azure 的资源组名称。 此参数默认为"__ElasticDatabaseJob"。 建议不要更改此值。</td>
</tr>
</tr>
<tr>
<td>ResourceGroupLocation</td>
<td>提供要用于新创建的 Azure 元件的 Azure 位置。 到美国中部的位置，此参数默认值。</td>
</tr>
<tr>
<td>ServiceWorkerCount</td>
<td>提供安装服务工作人员的数目。 此参数默认为 1。 扩展服务，以提供高可用性，可以使用更多的工作人员。 建议用于需要高可用性服务的部署，"2"。</td>
</tr>
</tr>
<tr>
<td>ServiceVmSize</td>
<td>提供云服务中使用虚拟机大小。 此参数默认为 A0。 参数值的 A0/A1/A2/A3 接受这导致辅助角色，使用 ExtraSmall/小型/中型/大型的大小，分别。 Fo 辅助角色大小，详细信息请参阅[弹性数据库作业组件和定价](sql-database-elastic-jobs-overview/#components-and-pricing)。</td>
</tr>
</tr>
<tr>
<td>SqlServerDatabaseSlo</td>
<td>标准版提供的服务等级目标。 此参数默认为 S0。 接受这导致 SQL Azure 数据库使用各自的 SLO S0/S1/S2/S3 的参数值。 SQL 数据库 Slo 的详细信息，请参阅[弹性数据库作业组件和定价](sql-database-elastic-jobs-overview/#components-and-pricing)。</td>
</tr>
</tr>
<tr>
<td>SqlServerAdministratorUserName</td>
<td>提供新创建的 SQL Azure 数据库服务器的管理员用户名。 如果未指定，PowerShell 凭据将打开一个窗口来提示输入凭据。</td>
</tr>
</tr>
<tr>
<td>SqlServerAdministratorPassword</td>
<td>新创建的 SQL Azure 数据库服务器提供管理员密码。 如果不提供，PowerShell 凭据将打开一个窗口来提示输入凭据。</td>
</tr>
</table>
对于目标有大量针对大量数据库的并行运行的作业的系统，建议指定参数如︰-ServiceWorkerCount 2-ServiceVmSize A2-SqlServerDatabaseSlo S2。
PS C:\*Microsoft.Azure.SqlDatabase.Jobs.dll.x.x.xxx.x*\tools>Unblock-File .\InstallElasticDatabaseJobs.ps1
PS C:\*Microsoft.Azure.SqlDatabase.Jobs.dll.x.x.xxx.x*\tools>.\InstallElasticDatabaseJobs.ps1 -ServiceWorkerCount 2 -ServiceVmSize A2 -SqlServerDatabaseSlo S2
## 更新现有的弹性数据库作业组件安装使用 PowerShell
可以扩展和高可用性的现有安装中更新**弹性数据库作业**。 此过程允许将来升级服务代码而无需除去并重新创建管理数据库。 此过程还可相同的版本中修改服务 VM 大小或服务器辅助计数。
要更新的安装虚拟机大小，请使用更新为您选择的值的参数运行以下脚本。
PS C:\*Microsoft.Azure.SqlDatabase.Jobs.dll.x.x.xxx.x*\tools>Unblock-File .\UpdateElasticDatabaseJobs.ps1
PS C:\*Microsoft.Azure.SqlDatabase.Jobs.dll.x.x.xxx.x*\tools>.\UpdateElasticDatabaseJobs.ps1 -ServiceVmSize A1 -ServiceWorkerCount 2
<table style="width:100%">
<tr>
<th>参数</th>
<th>说明</th>
</tr>
<tr>
<td>ResourceGroupName</td>
<td>标识的弹性数据库作业组件开始安装时使用的 Azure 的资源组名称。 此参数默认为"__ElasticDatabaseJob"。 建议不要更改此值，因为您不必指定该参数。</td>
</tr>
</tr>
</tr>
<tr>
<td>ServiceWorkerCount</td>
<td>提供安装服务工作人员的数目。 此参数默认为 1。 扩展服务，以提供高可用性，可以使用更多的工作人员。 建议用于需要高可用性服务的部署，"2"。</td>
</tr>
</tr>
<tr>
<td>ServiceVmSize</td>
<td>提供云服务中使用虚拟机大小。 此参数默认为 A0。 参数值的 A0/A1/A2/A3 接受这导致辅助角色，使用 ExtraSmall/小型/中型/大型的大小，分别。 Fo 辅助角色大小，详细信息请参阅[弹性数据库作业组件和定价](sql-database-elastic-jobs-overview/#components-and-pricing)。</td>
</tr>
</table>
## 使用门户弹性数据库作业组件安装
一旦[创建弹性数据库池](sql-database-elastic-pool-portal.md)，您可以安装**弹性数据库作业**组件能够弹性数据库池中的每个数据库管理任务的执行。 与使用**弹性数据库作业**PowerShell Api 时门户界面是当前限制为仅执行对现有池。
**估计完成时间︰** 10 分钟。
1. 从弹性数据库池通过[Azure 预览门户](https://ms.portal.azure.com/#)的仪表板视图，请单击**创建作业**。
2. 如果您第一次创建一个作业，则必须通过单击**预览条款**安装**弹性数据库作业**。
3. 单击复选框来接受的条款。
4. 在"安装服务"视图中，单击**作业凭据**。
![安装服务][1]
5. 键入用户名和密码的数据库管理员。 作为安装的一部分，创建新的 SQL Azure 数据库服务器。 在此新服务器中，一个新的数据库，称为管理数据库中，创建和使用包含弹性数据库作业的元数据。 用户名称和密码在此处创建用于登录到管理数据库。 一个单独的凭据用于对池内数据库的脚本执行。
![创建用户名和密码][2]
6. 单击确定按钮。 组件会为您创建新的[资源组](../resource-group-portal.md)中的几分钟时间。 新的资源组被固定到开始板，如下所示。 一旦所有创建的组中创建、 弹性数据库作业 （云服务、 SQL 数据库、 服务总线和存储）。
![在开始板中的资源组][3]
7. 如果您尝试创建或管理作业时弹性数据库作业安装提供**凭据**时，您将看到下面的消息。
![仍在进行的部署][4]
如果必须卸载，则删除该资源组。 了解[如何卸载弹性数据库作业组件](sql-database-elastic-jobs-uninstall.md)。
## 下一步行动
确保具有适当权限的脚本执行凭据创建的组中，每个数据库的详细信息，请参阅[如何将用户添加到所有数据库中我的数据库的用户组](sql-database-elastic-jobs-add-logins-to-dbs.md)。 请参阅[创建和管理弹性数据库作业](sql-database-elastic-jobs-create-and-manage.md)开始。
<!--Image references-->
[1]: ./media/sql-database-elastic-jobs-service-installation/screen-1.png
[2]: ./media/sql-database-elastic-jobs-service-installation/credentials.png
[3]: ./media/sql-database-elastic-jobs-service-installation/start-board.png
[4]: ./media/sql-database-elastic-jobs-service-installation/incomplete.png
| 35.943005 | 215 | 0.739513 | yue_Hant | 0.716856 |
c922d8e7029d2fe316a8f570b97786be267855b7 | 320 | md | Markdown | wiki/translations/es/Category_Template_Navigation.md | arslogavitabrevis/FreeCAD-documentation | 8166ce0fd906f0e15672cd1d52b3eb6cf9e17830 | [
"CC0-1.0"
] | null | null | null | wiki/translations/es/Category_Template_Navigation.md | arslogavitabrevis/FreeCAD-documentation | 8166ce0fd906f0e15672cd1d52b3eb6cf9e17830 | [
"CC0-1.0"
] | null | null | null | wiki/translations/es/Category_Template_Navigation.md | arslogavitabrevis/FreeCAD-documentation | 8166ce0fd906f0e15672cd1d52b3eb6cf9e17830 | [
"CC0-1.0"
] | null | null | null | # Category:Template:Navigation/es
This category lists templates that create navigation elements.
### Contents:
[<img src="images/Property.png" style="width:16px"> Template/es](<img src="images/Property.png" style="width:16px"> Template/es.md)
---
[documentation index](../README.md) > Category:Template:Navigation/es
| 32 | 131 | 0.75 | yue_Hant | 0.83204 |
c9233102fbd3157fd8b688ce58aa37efca1cfa09 | 719 | md | Markdown | README.md | yuokada/gohcs | 52f7044dca5308bef29689cfc7a5ad560c5cda80 | [
"MIT"
] | null | null | null | README.md | yuokada/gohcs | 52f7044dca5308bef29689cfc7a5ad560c5cda80 | [
"MIT"
] | 13 | 2017-01-15T04:11:48.000Z | 2019-04-23T00:03:05.000Z | README.md | yuokada/gohcs | 52f7044dca5308bef29689cfc7a5ad560c5cda80 | [
"MIT"
] | null | null | null | # gohcs
## Overview
This server returns 200 OK when "/status.html" is in the document root and they are listened a particular port on tcp/udp.
## How to use
### run server
```
$ ./gohcs -checklist /path/to/checklist.json
```
## configfile
server checklist
```
# checklist.json
[
# [<network>, <address> ]
["tcp", "localhost:8081"],
["tcp", "127.0.0.1:8083"],
["tcp", "127.0.0.1:8000"]
]
```
## dependencies
- [pkg/errors: Simple error handling primitives](https://github.com/pkg/errors)
- [sirupsen/logrus: Structured, pluggable logging for Go.](https://github.com/sirupsen/logrus "sirupsen/logrus: Structured, pluggable logging for Go.")
## LICENSE
MIT licensed. See the LICENSE file for details.
| 19.432432 | 151 | 0.680111 | eng_Latn | 0.546249 |
c9237429cf0970ed8c299cc6ea577982511722db | 1,600 | md | Markdown | README-zh.md | lcsan/webmagic-my | c271356c451139c484f8907d362daa2053259299 | [
"Apache-2.0"
] | null | null | null | README-zh.md | lcsan/webmagic-my | c271356c451139c484f8907d362daa2053259299 | [
"Apache-2.0"
] | null | null | null | README-zh.md | lcsan/webmagic-my | c271356c451139c484f8907d362daa2053259299 | [
"Apache-2.0"
] | 1 | 2019-08-24T10:31:17.000Z | 2019-08-24T10:31:17.000Z | 
[](https://travis-ci.org/code4craft/webmagic)
官方网站[http://webmagic.io/](http://webmagic.io/)
>基于webmagic 0.7.3，增强选择器，支持选择器链式执行：
<br/> 混合选择器 MixeSelector，就是一个表达式执行器，支持xpath|css|json|regex|replace|filter|split各种选择器表达式化。
```java
// MixeSelector为默认选择器
@ExtractBy("xpath('//a/text()').filter('\\S+').replace('^[\\s\\d、]+(.*?)[\\sABCD]+$','$1')")
private String title;
@ExtractBy("xpath('//div/text()').split('\\s+')")
private List<String> answer;
```
或者
```java
new MixeSelector("xpath('//a/text()').filter('\\S+').replace('^[\\s\\d、]+(.*?)[\\sABCD]+$','$1')").select(dom);
new MixeSelector("xpath('//a/text()').filter('\\S+').replace('^[\\s\\d、]+(.*?)[\\sABCD]+$','$1')").selectList(dom);
```
拆分选择器 SplitSelector，将字符串拆成数组。
```java
@ExtractBy(value="\\s+",type=Type.split)
private List<String> answer;
```
或者
```java
new SplitSelector("\\s+").select(dom);
new SplitSelector("\\s+").selectList(dom);
```
过滤选择器 FilterSelector，value为正则表达式，前后自动补齐^和$，支持正向和反向过滤。
···java
@ExtractBy(value="\\S+",type=Type.filter)
private String answer;
···
或者
```java
new FilterSelector("\\S+").select(dom);
```
替换选择器 ReplaceSelector，支持替换和提取。提取和RegexSelector效果差不多
```java
@ExtractBy(value="'^[\\s\\d、]+(.*?)[\\sABCD]+$','$1'",type=Type.replace)
private String title;
```
或者
```java
new ReplaceSelector("^[\\s\\d、]+(.*?)[\\sABCD]+$", "$1").select(dom);
new ReplaceSelector("'^[\\s\\d、]+(.*?)[\\sABCD]+$','$1'").select(dom);
```
| 29.090909 | 121 | 0.60625 | yue_Hant | 0.83249 |
c9239008ba7e389db6af4f8cd133757f90232543 | 414 | md | Markdown | README.md | ashleyadrias/lending-club-interest-rate-predictor-dash-app | 2c7f0856d473028f61e19d52d4484bdf96c81a3f | [
"MIT"
] | null | null | null | README.md | ashleyadrias/lending-club-interest-rate-predictor-dash-app | 2c7f0856d473028f61e19d52d4484bdf96c81a3f | [
"MIT"
] | null | null | null | README.md | ashleyadrias/lending-club-interest-rate-predictor-dash-app | 2c7f0856d473028f61e19d52d4484bdf96c81a3f | [
"MIT"
] | 1 | 2022-02-07T07:16:22.000Z | 2022-02-07T07:16:22.000Z | ## PREDICT INTEREST RATE USING LENDING CLUB LOAN DATA
Interested in knowing the interest rate on your loan type without running a credit check?
Look no further!
Use this interest rate predictor app to see how much your interest rate will be based on your annual income, credit score, loan amount, loan purpose, Debt Utilization %, and Debt-to-Income %.
Visit app here: https://int-rate-predictor.herokuapp.com/ | 46 | 191 | 0.785024 | eng_Latn | 0.977342 |
c923b8212410e1b4d1a0c9f9c71847c969288aad | 3,874 | md | Markdown | src/posts/front-end-dev/sass-color-variable-pop-quiz.md | dandenney/dandenney.com-11ty | 6d2bc1bcc9664e1d3cdf03aef52920ac185035c2 | [
"MIT"
] | 1 | 2021-12-23T02:06:55.000Z | 2021-12-23T02:06:55.000Z | src/posts/front-end-dev/sass-color-variable-pop-quiz.md | dandenney/dandenney.com-11ty | 6d2bc1bcc9664e1d3cdf03aef52920ac185035c2 | [
"MIT"
] | 4 | 2020-02-26T17:54:04.000Z | 2022-02-14T08:10:52.000Z | src/posts/front-end-dev/sass-color-variable-pop-quiz.md | dandenney/dandenney.com-eleventy | 0aeecd902e5eb41f704f0daf8e9f6eacbf85f4dd | [
"MIT"
] | null | null | null | ---
path: "/posts/front-end-dev/sass-color-variable-pop-quiz"
title: Sass Color Variable Pop Quiz
summary: Sharing results from asking when people set variables
date: "2013-01-21"
codeHighlighting: true
tags:
- front-end-dev
layout: layouts/post.njk
---
## I had a question about color variables
Each project has some really easy to define colors that can get you started. Base font color, a highlight color, link color, etc. Once you're a few hundred lines in though, you start coming across more colors that are used for shading, borders, highlights, etc.
I knew [Nick](http://twitter.com/nickawalsh) and [Drew](http://twitter.com/drewbarontini) would have answers, so I popped some questions into the Envy Design Campfire.
### How many times do you have to use a color before it should be a variable and how do you conjure up names beyond the first 6 or 7?
Nick chimed in with "if I use it more than three-ish times, it's usually time to variableize it or if it's a completely different color that doesn't fall into a sass-adjustment case (e.g blue theme, random green button appears)". Drew followed up with a gist of examples that was something like this:
```
Variables
Brand Colors
$color-brand-a: #606E67
$color-brand-b: #C98344
Base Colors
$color-base: #636365
$color-body: #EFEDDF
$color-border: #A9A9A9
$color-header: #3F4944
$color-input: #DCD7CE
Button Colors
$color-btn-a: #228B9B
$color-btn-b: #783737
$color-btn-c: #BFBEB2
Utility Colors
$color-error: $color-btn-b
$color-success: $color-header
Container Colors
$color-block-a: $color-header
$color-block-b: desaturate(darken($color-body, 4%), 11%)
$color-block-c: #D4D5C2
$color-card-a: lighten($color-body, 4%)
$color-card-b: $color-block-b
```
### To the Twitters!
I thought that this might be something cool that other people would have an opinion on. So I tweeted the questions and I'm sharing the answers below. Please chime in if you have a method. I love learning how other people approach these types of things.
Daniel Peplow aka [@danielpeplow](http://twitter.com/danielpeplow)
How many times before variableizing? **1**
Naming approach? **red1, red2, darkred1, darkred2, primarybrand, secondarybrand depending on what is required**
Chris Brauckmuller aka [@cbrauckmuller](http://twitter.com/cbrauckmuller)
How many times before variableizing? **1**
Naming approach? **It depends. For neutrals I usually have $gray, $gray-light and $gray-dark. For the main brand colors, I would name the original color something like $brand-green. Then if I needed variants of that, I might do \$brand-green-lighterX, where X just represents how many percent lighter it is versus the original.**
Sample? [https://github.com/cbrauckmuller/helium/blob/master/scss/config.scss](https://github.com/cbrauckmuller/helium/blob/master/scss/config.scss)
Elyse Holladay aka [@elyseholladay](http://twitter.com/elyseholladay)
How many times before variableizing? **3**
Naming approach? **In a small/personal project, sometimes I'll just say 'blue' 'darkblue', etc. In the large apps I work on, especially ones that require theming, I try to cut down on # of available colors by using darken/lighten in SASS rather than 2 different shades of blue. I name "global" colors like black/white by their names. For themable colors, I go primary/secondary/tertiary/highlight/error/success, and so on.**
Sample? [https://gist.github.com/4550373](https://gist.github.com/4550373)
Chase Woodford aka [@chase1263070](http://twitter.com/chase1263070)
How many times before variableizing? **2**
Naming approach? **I try to stick to a `groupName-differentiator` naming convention.**
Sample? [https://github.com/chasewoodford/chasewoodford.com/blob/master/css/sass/\_variables.scss](https://github.com/chasewoodford/chasewoodford.com/blob/master/css/sass/_variables.scss)
| 47.82716 | 424 | 0.756066 | eng_Latn | 0.967047 |
c925361cfc667401c995645c67c610f8c9b03371 | 5,704 | md | Markdown | source/_posts/pregnant_ashley_tisdale_covers_up_her_baby_bump_in_white_overalls_as_she_goes_for_a_stroll_in_la.md | soumyadipdas37/finescoop.github.io | 0346d6175a2c36d4054083c144b7f8364db73f2f | [
"MIT"
] | null | null | null | source/_posts/pregnant_ashley_tisdale_covers_up_her_baby_bump_in_white_overalls_as_she_goes_for_a_stroll_in_la.md | soumyadipdas37/finescoop.github.io | 0346d6175a2c36d4054083c144b7f8364db73f2f | [
"MIT"
] | null | null | null | source/_posts/pregnant_ashley_tisdale_covers_up_her_baby_bump_in_white_overalls_as_she_goes_for_a_stroll_in_la.md | soumyadipdas37/finescoop.github.io | 0346d6175a2c36d4054083c144b7f8364db73f2f | [
"MIT"
] | 2 | 2021-09-18T12:06:26.000Z | 2021-11-14T15:17:34.000Z | ---
extends: _layouts.post
section: content
image: https://i.dailymail.co.uk/1s/2020/09/28/23/33738938-0-image-a-143_1601332580677.jpg
title: Pregnant Ashley Tisdale covers up her baby bump in white overalls as she goes for a stroll in LA
description: Pregnant Ashley Tisdale, 35, stepped out with her husband Chris French, 38, and their adorable dogs. She hid her growing baby bump under a pair of white overalls, as she grabbed an iced beverage in LA
date: 2020-09-29-01-16-57
categories: [latest, tv]
featured: true
---
Pregnant Ashley Tisdale stepped out on Sunday with her husband of six years, musician Chris French, for a caffeine fix and a light stroll.
The High School Musical star, 35, who just announced her pregnancy about a week ago, seemed to be savoring her weekend as she and Chris, 38, enjoyed a family outing.
Concealing her baby bump in a pair of white overalls, the actress put on a stylish display for their lowkey day.
Mom-to-be: Pregnant Ashley Tisdale, 35, stepped out with her husband Chris French, 38, and their adorable dogs Sushi and Ziggy. The expecting mom hid her growing baby bump under a pair of oversized white overalls as she grabbed an iced beverage in LA
The mom-to-be had her two dogs, Sushi and Ziggy, in tow as she walked out with an iced beverage from the Coffee Bean.
The blonde rocked a pair of black Chanel dad sandals, that coordinated with her black t-shirt under the overalls.
She hid her short blonde locks under a grey beanie, accessorizing her look with round sunglasses and a green bandana tied around her neck.
Taking her grey face mask off to take a sip of her beverage, the actress made sure nobody was around as she guided her two small pups.
Rockstar couple: Ashley and Chris put on an edgy display for their Sunday outing as they took their pooches out for a walk
Chris played up the edge with his look, wearing a ripped black t-shirt and a pair of black sweat shorts that were embroidered with a skull and crossbones.
He kept his dark locks gelled and rocked a pair of rayban sunglasses, as he stepped out with white sneakers and a face mask on their neighborhood stroll.
The pair traded off taking ownership over their pooches, as they chatted and relished in each other's company.
Later in the day Ashley posted a photo of herself from bed as she said it was 'time to relax.'
Dog parents: The pair traded off taking ownership over their pooches as they chatted and relished in each other's company while strolling in LA
She swapped her overalls for a pair of tie-dye sweatpants and hotel slippers, as she lounged with her dog Ziggy under the covers.
The Frenshe founder recently took to her wellness blog to discuss her first trimester of pregnancy, after announcing her baby news in a post titled 'Surprise, I’m Pregnant!'
'It hasn’t been an easy first trimester, but everyone is different and I know there are people who’ve had it way worse' she said.
'I definitely fall somewhere in the middle where I didn’t just have nausea, but threw up a couple of times and felt like I’ve had stomach flu for three months' she continued.
Baby bliss: Ashley took to her blog Frenshe - a play on her husband's last name - to share the news that she and her husband of six years were expecting
The Suite Life actress also shared that she felt pressure after getting married to have children, adding that she was not in the right headspace at the time.
'To be honest, it just felt invasive' she shared. 'I wasn’t ready for that step yet and I wanted to be selfish and have Chris all to myself for a while.'
Last week, Ashley continued to get candid about her life on her blog as she talked about having her breast implants removed.
The actress wrote that she had been suffering some health problems and decided to get an explant surgery after reading about it online.
Explant: The High School Musical actress got candid on her blog, Frenshe, sharing that after suffering some health problems she decided to get her implants removed
'I just knew that taking them out was already going to relieve some of the symptoms I was struggling with' she shared.
Discussing her journey of living with her body after surgery, Ashley revealed a level of self-love she had not previously had.
'Seeing my body in a way I hadn’t seen it in a while and fully loving the way I looked is a feeling I’ll never forget' she wrote.
She also credits her husband Chris with helping to make her feel beautiful in her own skin.
Love overall: Ashley and Chris have been married for six years after being introduced by mutual friends in 2012; pictured in September 2019
'My husband always helps me look at the positive and says that those scars represent my journey and what got me to where I am right now...I embrace those imperfections, and I embrace that I’m not perfect and that I’m beautiful just as I am' she wrote.
The couple first met in 2012 through mutual friends after it was revealed that Ashley, who also sings, had a thing for 'rocker types'. Talking to On Air With Ryan Seacrest in 2013, she revealed it was love at first sight.
'I was like, OK, this is the guy, and he knew the same thing. It doesn't get any better. I just can't explain it,' she gushed.
Ashley's most recent film Phineas and Ferb The Movie is currently streaming on Disney+. The actress reprised her role as Candace in the animated film version of the television show, for the first time in five years.
Love at first sight: In a 2013 On Air interview, Ashley revealed that it was love at first sight for she and her husband. 'I was like, OK, this is the guy' she gushed ;pictured at the Golden Globes after party, January 2019
| 72.202532 | 252 | 0.779102 | eng_Latn | 0.999933 |
c9254d6c78cc5334c055d853c5610445cc3a363b | 80,555 | md | Markdown | WSL/release-notes.md | zawataki/WSL.ja-JP | 3a64ac0bcc180264f73ccfc2aac861f684b17f8a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | WSL/release-notes.md | zawataki/WSL.ja-JP | 3a64ac0bcc180264f73ccfc2aac861f684b17f8a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | WSL/release-notes.md | zawataki/WSL.ja-JP | 3a64ac0bcc180264f73ccfc2aac861f684b17f8a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Windows Subsystem for Linux のリリースノート
description: Windows Subsystem for Linux のリリースノートです。 毎週更新されました。
keywords: BashOnWindows、bash、wsl、windows、windows subsystem for linux、windowssubsystem、ubuntu
author: benhillis
ms.date: 07/31/2017
ms.topic: article
ms.assetid: 36ea641e-4d49-4881-84eb-a9ca85b1cdf4
ms.custom: seodec18
ms.openlocfilehash: b03d837e0ab3a371fd676e37b5c65a173824f84c
ms.sourcegitcommit: 9175a28f04573f25338358faf61d73b1a5d1ade6
ms.translationtype: MT
ms.contentlocale: ja-JP
ms.lasthandoff: 08/06/2019
ms.locfileid: "68832116"
---
# <a name="release-notes-for-windows-subsystem-for-linux"></a>Windows Subsystem for Linux のリリースノート
## <a name="build-18945"></a>ビルド18945
ビルド18945の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2019/07/26/announcing-windows-10-insider-preview-build-18945/)を参照してください。
### <a name="wsl"></a>WSL
* [WSL2]Localhost: port を使用して、WSL2 のリスニング tcp ソケットにホストからアクセスできるようにします
* [WSL2]インストール/変換エラーの修正と今後の問題を追跡するための追加の診断 [GH 4105]
* [WSL2]Diagnosability WSL2 のネットワークの問題を改善する
* [WSL2]カーネルバージョンを4.19.55 に更新する
* [WSL2]Docker に必要な構成オプションを使用してカーネルを更新する [GH 4165]
* [WSL2]ライトウェイトユーティリティ VM に割り当てられた Cpu の数を、ホストと同じになるように増やします (以前はカーネル構成の CONFIG_NR_CPUS によって8個に制限されていました) [GH 4137]
* [WSL2]WSL2 ライトウェイト VM 用のスワップファイルを作成する
* [WSL2]Wsl $ \\ \\ディストリビューションを使用してユーザーのマウントを表示できるようにします (例 sshfs) [GH 4172]\\
* [WSL2]9p ファイルシステムのパフォーマンスの向上
* [WSL2]Vhd ACL が無制限に拡張されないようにする [GH 4126]
* [WSL2]Squashfs と xt_conntrack をサポートするようにカーネル構成を更新する [GH 4107, 4123]
* [WSL2]Interop の修正。 enabled/etc/wsl.conf オプション [GH 4140]
* [WSL2]ファイルシステムで EAs がサポートされていない場合は、ENOTSUP を返します。
* [WSL2]Wsl $ で\\CopyFile hang を\\修正します
* 既定の umask を0022に切り替え、/etc/wsl.conf にファイルシステムの umask 設定を追加します。
* シンボリックリンクを適切に解決するために wslpath を修正しました。これは19h1 で低下したました [GH 4078]
* WSL2 設定を調整\\するための% UserProfile%. wslconfig ファイルの導入
```
[wsl2]
kernel=<path> # An absolute Windows path to a custom Linux kernel.
memory=<size> # How much memory to assign to the WSL2 VM.
processors=<number> # How many processors to assign to the WSL2 VM.
swap=<size> # How much swap space to add to the WSL2 VM. 0 for no swap file.
swapFile=<path> # An absolute Windows path to the swap vhd.
localhostForwarding=<bool> # Boolean specifying if ports bound to wildcard or localhost in the WSL2 VM should be connectable from the host via localhost:port (default true).
# <path> entries must be absolute Windows paths with escaped backslashes, for example C:\\Users\\Ben\\kernel
# <size> entries must be size followed by unit, for example 8GB or 512MB
```
## <a name="build-18917"></a>ビルド18917
ビルド18917の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2019/06/12/announcing-windows-10-insider-preview-build-18917/)を参照してください。
### <a name="wsl"></a>WSL
* WSL 2 が利用可能になりました。 詳細については、[ブログ](https://devblogs.microsoft.com/commandline/wsl-2-is-now-available-in-windows-insiders/)を参照してください。
* シンボリックリンクを使用した Windows プロセスの起動が正常に機能しない回帰を修正する [GH 3999]
* Wsl--list--verbose, wsl--list--quiet, および wsl .exe--import--version オプションを wsl に追加します。
* Wsl--shutdown オプションを追加します。
* プラン 9:書き込み用のディレクトリを開くことを成功させる
## <a name="build-18890"></a>ビルド18890
ビルド18890の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2019/05/01/announcing-windows-10-insider-preview-build-18890/)を参照してください。
### <a name="wsl"></a>WSL
* 非ブロッキングソケットリーク [GH 2913]
* ターミナルへの EOF 入力が後続の読み取りをブロックする可能性がある [GH 3421]
* Resolv.conf を参照するようにを更新する (GH 3928 で説明)
* Epoll delete コードでのデッドロック [GH 3922]
* --Import および– export の引数内のスペースを処理する [GH 3932]
* Mmap ファイルの拡張が正しく機能しない [GH 3939]
* ARM64 \\wsl $ アクセスが正常に動作しない問題を修正します
* Wsl のより適切な既定のアイコンを追加する
## <a name="build-18342"></a>ビルド18342
ビルド18342の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2019/02/20/announcing-windows-10-insider-preview-build-18342/)を参照してください。
### <a name="wsl"></a>WSL
* Windows から WSL ディストリビューションの Linux ファイルにユーザーがアクセスできる機能が追加されました。 これらのファイルには、コマンドラインを使用してアクセスできます。また、ファイルエクスプローラーや VSCode などの Windows アプリもこれらのファイルと対話できます。 \\Wsl $ \\ \\ \\< distro_name > に移動してファイルにアクセスするか、wsl $ に移動して実行中のディストリビューションの一覧を表示します。\\
* CPU 情報タグを追加し、Cpus_allowed [リスト] の値を修正する [GH 2234]
* リーダー以外のスレッドからの exec のサポート [GH 3800]
* 構成の更新エラーを致命的でないものとして扱う [GH 3785]
* オフセットを正しく処理するように binfmt を更新する [GH 3768]
* プラン9のネットワークドライブのマッピングを有効にする [GH 3854]
* Windows > Linux および Linux をサポートする-bind マウント用の Windows パス変換 >
* 読み取り専用で開かれたファイルのマッピングの読み取り専用セクションを作成する
## <a name="build-18334"></a>ビルド18334
ビルド18334の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2019/02/08/announcing-windows-10-insider-preview-build-18334/)を参照してください。
### <a name="wsl"></a>WSL
* Windows タイムゾーンを Linux タイムゾーンにマップする方法の設計 [GH 3747]
* メモリリークを修正し、新しい文字列変換関数を追加する [GH 3746]
* スレッドのない threadgroup の SIGCONT は、no op [GH 3741]
* /Proc/self/fd にソケットと epoll ファイル記述子を正しく表示する
## <a name="build-18305"></a>ビルド18305
ビルド18305の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/12/19/announcing-windows-10-insider-preview-build-18305/)を参照してください。
### <a name="wsl"></a>WSL
* pthreads プライマリスレッドが終了したときにファイルへのアクセスが失われる [GH 3589]
* TIOCSCTTY は、必要な場合を除き、"force" パラメーターを無視する必要があります [GH 3652]
* wsl コマンドラインの機能強化とインポート/エクスポート機能の追加。
```
Usage: wsl.exe [Argument] [Options...] [CommandLine]
Arguments to run Linux binaries:
If no command line is provided, wsl.exe launches the default shell.
--exec, -e <CommandLine>
Execute the specified command without using the default Linux shell.
--
Pass the remaining command line as is.
Options:
--distribution, -d <DistributionName>
Run the specified distribution.
--user, -u <UserName>
Run as the specified user.
Arguments to manage Windows Subsystem for Linux:
--export <DistributionName> <FileName>
Exports the distribution to a tar file.
The filename can be - for standard output.
--import <DistributionName> <InstallLocation> <FileName>
Imports the specified tar file as a new distribution.
The filename can be - for standard input.
--list, -l [Options]
Lists distributions.
Options:
--all
List all distributions, including distributions that are currently
being installed or uninstalled.
--running
List only distributions that are currently running.
-setdefault, -s <DistributionName>
Sets the distribution as the default.
--terminate, -t <DistributionName>
Terminates the distribution.
--unregister <DistributionName>
Unregisters the distribution.
--upgrade <DistributionName>
Upgrades the distribution to the WslFs file system format.
--help
Display usage information.
```
## <a name="build-18277"></a>ビルド18277
ビルド18277の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/11/07/announcing-windows-10-insider-preview-build-18277/)を参照してください。
### <a name="wsl"></a>WSL
* ビルド18272で導入された "そのようなインターフェイスがサポートされていません" というエラーを修正する [GH 3645]
* Umount syscall の MNT_FORCE フラグを無視する [GH 3605]
* WSL 相互運用機能を切り替えて、正式な Create擬似コンソール API を使用する
* FUTEX_WAIT の再起動時にタイムアウト値を保持しない
## <a name="build-18272"></a>ビルド18272
ビルド18272の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/10/31/announcing-windows-10-insider-preview-build-18272/)を参照してください。
### <a name="wsl"></a>WSL
* **要する**このビルドには、WSL が動作しなくなる問題があります。 ディストリビューションを起動しようとすると、"そのようなインターフェイスはサポートされていません" というエラーが表示されます。 この問題は修正され、来週の Insider Fast ビルドに含まれるようになりました。 このビルドがインストールされている場合は、「設定-> Update & Security-> Recovery」の「以前のバージョンの Windows 10 に戻る」を使用して、以前の Windows ビルドにロールバックできます。
## <a name="build-18267"></a>ビルド18267
ビルド18267の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/10/24/announcing-windows-10-insider-preview-build-18267/)を参照してください。
### <a name="wsl"></a>WSL
* ゾンビプロセスが reaped されず、無期限に保持される問題を修正します。
* エラーメッセージが最大長を超えた場合、WslRegisterDistribution がハングする [GH 3592]
* DrvFs で読み取り専用ファイルの fsync を正常に実行できるようにする [GH 3556]
* [GH 3584] 内にシンボリックリンクを作成する前に、/bin と/sbin ディレクトリが存在することを確認します。
* WSL インスタンスのインスタンス終了タイムアウトメカニズムが追加されました。 タイムアウトは現在15秒に設定されています。つまり、最後の WSL プロセスが終了してから15秒後にインスタンスが終了します。 ディストリビューションをすぐに終了するには、次のように使用します。
```
wslconfig.exe /terminate <DistributionName>
```
## <a name="build-17763-1809"></a>ビルド 17763 (1809)
ビルド17763の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/10/02/how-to-get-the-windows-10-october-2018-update/)を参照してください。
### <a name="wsl"></a>WSL
* 同じスレッド優先順位を変更するための setpriority syscall アクセス許可チェックが strict すぎます [GH 1838]
* Clock_gettime (CLOCK_BOOTTIME) の負の値が返されないように、起動時間にバイアスをかけない割り込み時間を使用することを確認してください () [GH 3434]
* WSL binfmt インタープリターでのシンボリックリンクの処理 [GH 3424]
* Threadgroup リーダーファイル記述子のクリーンアップをより適切に処理します。
* KeQueryPerformanceCounter ではなく KeQueryInterruptTimePrecise を使用してオーバーフローを回避するように WSL を切り替える [GH 3252]
* Ptrace をアタッチすると、システムコールから無効な戻り値が返される [GH 1731]
* AF_UNIX 関連のいくつかの問題を修正する [GH 3371]
* 現在の作業ディレクトリの長さが5文字未満の場合に WSL 相互運用機能が失敗する原因となる問題を修正しました [GH 3379]
* 存在しないポートへのループバック接続で1秒間の遅延が発生しないようにする [GH 3286]
* /Proc/sys/fs/file-max スタブファイルの追加 [GH 2893]
* より正確な IPV6 スコープ情報。
* PR_SET_PTRACER のサポート [GH 3053]
* パイプファイルシステムがエッジトリガーの epoll イベントを誤って消去しています [GH 3276]
* NTFS シンボリックリンクによって起動された Win32 実行可能ファイルがシンボリックリンク名を尊重しない [GH 2909]
* 強化されたゾンビサポート [GH 1353]
* Windows 相互運用機能の動作を制御するための wsl のエントリを追加する [GH 1493]
```
[interop]
enabled=false # enable launch of Windows binaries; default is true
appendWindowsPath=false # append Windows path to $PATH variable; default is true
```
* 常に UNIX ソケットファミリの種類を返す getsockname でないことを修正する [GH 1774]
* TIOCSTI のサポートを追加する [GH 1863]
* 接続処理中の非ブロッキングソケットは、書き込み試行に EAGAIN を返します [GH 2846]
* マウントされた Vhd での相互運用のサポート [GH 3246, 3291]
* ルートフォルダーでのアクセス許可チェックの問題の修正 [GH 3304]
* TTY キーボード ioctl KDGKBTYPE、KDGKBMODE、および KDSKBMODE のサポートが制限されています。
* Windows UI アプリは、バックグラウンドで起動した場合でも実行する必要があります。
* Wsl-u または--user オプションを追加する [GH 1203]
* 高速スタートアップが有効になっているときの WSL 起動の問題を修正する [GH 2576]
* Unix ソケットが切断されたピア資格情報を保持する必要がある [GH 3183]
* EAGAIN で無制限の非ブロッキング Unix ソケットが失敗する [GH 3191]
* case = off は新しい既定の drvfs マウントの種類 [GH 2937, 3212, 3328]
* 詳細については、[ブログ](https://blogs.msdn.microsoft.com/commandline/2018/06/14/improved-per-directory-case-sensitivity-support-in-wsl/)を参照してください。
* Wslconfig/terminate を追加して、実行中のディストリビューションを停止します。
* スペースを含むパスを正しく処理しない WSL シェルコンテキストメニューエントリの問題を修正します。
* ディレクトリごとの大文字と小文字の区別を拡張属性として公開する
* ARM64: キャッシュメンテナンス操作をエミュレートします。 [Dotnet の問題](https://github.com/dotnet/core/issues/1561)を解決します。
* DrvFs: エスケープされた文字に対応するプライベート範囲内の文字のみを unescape します。
* ELF パーサーインタープリターの長さの検証での1つずつのエラーの修正 [GH 3154]
* 過去の時間を持つ WSL 絶対タイマーが起動しない [GH 3091]
* 新しく作成された再解析ポイントが親ディレクトリに表示されていることを確認します。
* DrvFs に大文字と小文字を区別するディレクトリをアトミックに作成します。
* ファイルが存在する場合でも、マルチスレッド操作が ENOENT を返す可能性のある追加の問題を修正しました。 [GH 2712]
* UMCI が有効になっているときの WSL 起動エラーを修正しました。 [GH 3020]
* WSL [GH 437, 603, 1836] を起動するには、エクスプローラーのコンテキストメニューを追加します。 を使用するには、エクスプローラーウィンドウで、shift キーを押しながら右クリックします。
* Unix ソケットの非ブロッキング動作の修正 [GH 2822、3100]
* GH 2026 で報告されているように、ハングしている NETLINK コマンドを修正しました。
* マウント伝達フラグ [GH 2911] のサポートを追加します。
* Truncate で inotify イベントが発生しない問題を修正する [GH 2978]。
* シェルを使用せずに1つのバイナリを呼び出すには、wsl の--exec オプションを追加します。
* 特定のディストリビューションを選択するには、wsl のディストリビューションオプションを追加します。
* Dmesg のサポートが制限されています。 アプリケーションは、dmesg にログを記録できるようになりました。 WSL ドライバーは、制限された情報を dmesg に記録します。 将来は、この機能を拡張して、ドライバーから他の情報や診断情報を伝達することができます。
* 注: 現在、 `/dev/kmsg` dmesg はデバイスインターフェイスでサポートされています。 `syslog`syscall インターフェイスはまだサポートされていません。 そのため、などの一部の`dmesg`コマンドラインオプション`-S` `-C`は機能しません。
* ネイティブと一致するように既定の gid とシリアルデバイスのモードを変更する [GH 3042]
* DrvFs は拡張属性をサポートするようになりました。
* 注:DrvFs では、拡張属性の名前にいくつかの制限があります。 一部の文字 ('/'、': '、'\*' など) は使用できません。また、拡張属性名は、drvfs では大文字と小文字が区別されません。
## <a name="build-18252-skip-ahead"></a>ビルド 18252 (前へスキップ)
ビルド18252の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/10/03/announcing-windows-10-insider-preview-build-18252/)を参照してください。
### <a name="wsl"></a>WSL
* Init と bsdtar のバイナリを lxssmanager dll から別のツールフォルダーに移動する
* CLONE_FILES を使用するときのファイル記述子の終了に関する競合を修正します。
* DrvFs パスを変換するときに/proc/pid/mountinfo の省略可能なフィールドを処理する
* S_IFREG のメタデータをサポートせずに DrvFs mknod を正常に実行できるようにする
* DrvFs で作成される readonly ファイルは、readonly 属性セットを持つ必要があります [GH 3411]
* DrvFs のマウントを処理する/sbin/mount.drvfs helper を追加する
* DrvFs で POSIX 名の変更を使用します。
* ボリューム GUID がないボリュームでパスの変換を許可します。
## <a name="build-17738-fast"></a>ビルド 17738 (高速)
ビルド17738の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/08/14/announcing-windows-10-insider-preview-build-17738/)を参照してください。
### <a name="wsl"></a>WSL
* 同じスレッド優先順位を変更するための setpriority syscall アクセス許可チェックが strict すぎます [GH 1838]
* Clock_gettime (CLOCK_BOOTTIME) の負の値が返されないように、起動時間にバイアスをかけない割り込み時間を使用することを確認してください () [GH 3434]
* WSL binfmt インタープリターでのシンボリックリンクの処理 [GH 3424]
* Threadgroup リーダーファイル記述子のクリーンアップをより適切に処理します。
## <a name="build-17728-fast"></a>ビルド 17728 (高速)
ビルド17728の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/07/31/announcing-windows-10-insider-preview-build-17728/)を参照してください。
### <a name="wsl"></a>WSL
* KeQueryPerformanceCounter ではなく KeQueryInterruptTimePrecise を使用してオーバーフローを回避するように WSL を切り替える [GH 3252]
* Ptrace をアタッチすると、システムコールから無効な戻り値が返される [GH 1731]
* AF_UNIX 関連のさまざまな問題を修正する [GH 3371]
* 現在の作業ディレクトリの長さが5文字未満の場合に WSL 相互運用機能が失敗する原因となる問題を修正しました [GH 3379]
## <a name="build-18204-skip-ahead"></a>ビルド 18204 (前へスキップ)
ビルド18204の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/07/25/announcing-windows-10-insider-preview-build-17723-and-build-18204/)を参照してください。
### <a name="wsl"></a>WSL
* パイプファイルシステム inadvertenly によるエッジトリガー epoll イベントの消去 [GH 3276]
* NTFS シンボリックリンクによって起動された Win32 実行可能ファイルがシンボリックリンク名を尊重しない [GH 2909]
## <a name="build-17723-fast"></a>ビルド 17723 (高速)
ビルド17723の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/07/25/announcing-windows-10-insider-preview-build-17723-and-build-18204/)を参照してください。
### <a name="wsl"></a>WSL
* 存在しないポートへのループバック接続で1秒間の遅延が発生しないようにする [GH 3286]
* /Proc/sys/fs/file-max スタブファイルの追加 [GH 2893]
* より正確な IPV6 スコープ情報。
* PR_SET_PTRACER のサポート [GH 3053]
* パイプファイルシステム inadvertenly によるエッジトリガー epoll イベントの消去 [GH 3276]
* NTFS シンボリックリンクによって起動された Win32 実行可能ファイルがシンボリックリンク名を尊重しない [GH 2909]
## <a name="build-17713"></a>ビルド17713
ビルド17713の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/07/11/announcing-windows-10-insider-preview-build-17713/)を参照してください。
### <a name="wsl"></a>WSL
* 強化されたゾンビサポート [GH 1353]
* Windows 相互運用機能の動作を制御するための wsl のエントリを追加する [GH 1493]
```
[interop]
enabled=false # enable launch of Windows binaries; default is true
appendWindowsPath=false # append Windows path to $PATH variable; default is true
```
* 常に UNIX ソケットファミリの種類を返す getsockname でないことを修正する [GH 1774]
* TIOCSTI のサポートを追加する [GH 1863]
* 接続処理中の非ブロッキングソケットは、書き込み試行に EAGAIN を返します [GH 2846]
* マウントされた Vhd での相互運用のサポート [GH 3246, 3291]
* ルートフォルダーでのアクセス許可チェックの問題の修正 [GH 3304]
* TTY キーボード ioctl KDGKBTYPE、KDGKBMODE、および KDSKBMODE のサポートが制限されています。
* Windows UI アプリは、バックグラウンドで起動した場合でも実行する必要があります。
## <a name="build-17704"></a>ビルド17704
ビルド17704の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/06/27/announcing-windows-10-insider-preview-build-17704/)を参照してください。
### <a name="wsl"></a>WSL
* Wsl-u または--user オプションを追加する [GH 1203]
* 高速スタートアップが有効になっているときの WSL 起動の問題を修正する [GH 2576]
* Unix ソケットが切断されたピア資格情報を保持する必要がある [GH 3183]
* EAGAIN で無制限の非ブロッキング Unix ソケットが失敗する [GH 3191]
* case = off は新しい既定の drvfs マウントの種類 [GH 2937, 3212, 3328]
* 詳細については、[ブログ](https://blogs.msdn.microsoft.com/commandline/2018/06/14/improved-per-directory-case-sensitivity-support-in-wsl/)を参照してください。
* Wslconfig/terminate を追加して、実行中のディストリビューションを停止します。
## <a name="build-17692"></a>ビルド 17692
ビルド17692の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/06/14/announcing-windows-10-insider-preview-build-17692)を参照してください。
### <a name="wsl"></a>WSL
* スペースを含むパスを正しく処理しない WSL シェルコンテキストメニューエントリの問題を修正します。
* ディレクトリごとの大文字と小文字の区別を拡張属性として公開する
* ARM64: キャッシュメンテナンス操作をエミュレートします。 [Dotnet の問題](https://github.com/dotnet/core/issues/1561)を解決します。
* DrvFs: エスケープされた文字に対応するプライベート範囲内の文字のみを unescape します。
## <a name="build-17686"></a>ビルド 17686
ビルド17686の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/06/06/announcing-windows-10-insider-preview-build-17686)を参照してください。
### <a name="wsl"></a>WSL
* ELF パーサーインタープリターの長さの検証での1つずつのエラーの修正 [GH 3154]
* 過去の時間を持つ WSL 絶対タイマーが起動しない [GH 3091]
* 新しく作成された再解析ポイントが親ディレクトリに表示されていることを確認します。
* DrvFs に大文字と小文字を区別するディレクトリをアトミックに作成します。
## <a name="build-17677"></a>ビルド17677
ビルド17677の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/05/24/announcing-windows-10-insider-preview-build-17677/)を参照してください。
### <a name="wsl"></a>WSL
* ファイルが存在する場合でも、マルチスレッド操作が ENOENT を返す可能性のある追加の問題を修正しました。 [GH 2712]
* UMCI が有効になっているときの WSL 起動エラーを修正しました。 [GH 3020]
## <a name="build-17666"></a>ビルド17666
ビルド17666の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/05/09/announcing-windows-10-insider-preview-build-17666/)を参照してください。
### <a name="wsl"></a>WSL
#### <a name="warning-there-is-an-issue-preventing-wsl-from-running-on-some-amd-chipsets-gh-3134-a-fix-is-ready-and-making-its-way-to-the-insider-build-branch"></a>警告:一部の AMD チップセットで WSL の実行を妨げる問題があります [GH 3134]。 修正の準備ができました。 Insider Build 分岐に変更することができます。
* WSL [GH 437, 603, 1836] を起動するには、エクスプローラーのコンテキストメニューを追加します。 [エクスプローラー] ウィンドウで [保留] をクリックして右クリックします。
* Unix ソケットの非ブロッキング動作の修正 [GH 2822、3100]
* GH 2026 で報告されているように、ハングしている NETLINK コマンドを修正しました。
* マウント伝達フラグ [GH 2911] のサポートを追加します。
* Truncate で inotify イベントが発生しない問題を修正する [GH 2978]。
* シェルを使用せずに1つのバイナリを呼び出すには、wsl の--exec オプションを追加します。
* 特定のディストリビューションを選択するには、wsl のディストリビューションオプションを追加します。
## <a name="build-17655-skip-ahead"></a>ビルド 17655 (前へスキップ)
ビルド17655の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/04/25/announcing-windows-10-insider-preview-build-17655-for-skip-ahead/)を参照してください。
### <a name="wsl"></a>WSL
* Dmesg のサポートが制限されています。 アプリケーションは、dmesg にログを記録できるようになりました。 WSL ドライバーは、制限された情報を dmesg に記録します。 将来は、この機能を拡張して、ドライバーから他の情報や診断情報を伝達することができます。
* 注: 現在、 `/dev/kmsg` dmesg はデバイスインターフェイスでサポートされています。 `syslog`sycall インターフェイスは、まだサポートされていません。 そのため、などの一部の`dmesg`コマンドラインオプション`-S` `-C`は機能しません。
* ファイルが存在する場合でも、マルチスレッド操作で ENOENT が返される問題を修正しました。 [GH 2712]
## <a name="build-17639-skip-ahead"></a>ビルド 17639 (前へスキップ)
ビルド17639の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/04/04/announcing-windows-10-insider-preview-build-17639-for-skip-ahead/)を参照してください。
### <a name="wsl"></a>WSL
* ネイティブと一致するように既定の gid とシリアルデバイスのモードを変更する [GH 3042]
* DrvFs は拡張属性をサポートするようになりました。
* 注:DrvFs では、拡張属性の名前にいくつかの制限があります。 特に、一部の文字 ('/'、': '、'\*' など) は使用できません。また、拡張属性名は、drvfs では大文字と小文字が区別されません。
## <a name="build-17133-fast"></a>ビルド 17133 (高速)
ビルド17133の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/03/27/announcing-windows-10-insider-preview-build-17133-for-fast/)を参照してください。
### <a name="wsl"></a>WSL
* WSL のハングを修正します。 [GH 3039、3034]
## <a name="build-17128-fast"></a>ビルド 17128 (高速)
ビルド17128の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/03/23/announcing-windows-10-insider-preview-build-17128-for-fast/)を参照してください。
### <a name="wsl"></a>WSL
* なし
## <a name="build-17627-skip-ahead"></a>ビルド 17627 (前へスキップ)
ビルド17627の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/03/21/announcing-windows-10-insider-preview-build-17627-for-skip-ahead/)を参照してください。
### <a name="wsl"></a>WSL
* Futex pi 対応の操作のサポートを追加します。 [GH 1006]
* 優先順位は現在サポートされている WSL 機能ではないため、制限がありますが、標準の使用をブロック解除する必要があります。
* WSL プロセス用の Windows ファイアウォールのサポート。 [GH 1852]
* たとえば、WSL python プロセスが任意のポートでリッスンできるようにするには、管理者特権の Windows cmd を使用します。```netsh.exe advfirewall firewall add rule name=wsl_python dir=in action=allow program="C:\users\<username>\appdata\local\packages\canonicalgrouplimited.ubuntuonwindows_79rhkp1fndgsc\localstate\rootfs\usr\bin\python2.7" enable=yes```
* ファイアウォール規則を追加する方法の詳細については、「[リンク](https://support.microsoft.com/en-us/help/947709/how-to-use-the-netsh-advfirewall-firewall-context-instead-of-the-netsh)」を参照してください。
* Wsl を使用するときのユーザーの既定のシェルを尊重します。 [GH 2372]
* すべてのネットワークインターフェイスをイーサネットとして報告します。 [GH 2996]
* 破損した/etc/passwd ファイルの処理が改善されます。 [GH 3001]
### <a name="console"></a>Console
* 修正はありません。
### <a name="ltp-results"></a>LTP の結果:
テストを実行中です。
## <a name="build-17618-skip-ahead"></a>ビルド 17618 (前へスキップ)
ビルド17618の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/03/07/announcing-windows-10-insider-preview-build-17618-skip-ahead/)を参照してください。
### <a name="wsl"></a>WSL
* NT interop の擬似コンソール機能の導入 [GH 988、1366、1433、1542、2370、2406]。
* レガシインストールメカニズム (lxrun) は非推奨となりました。 ディストリビューションのインストールに関してサポートされているメカニズムは、Microsoft Store を使用することです。
### <a name="console"></a>Console
* 修正はありません。
### <a name="ltp-results"></a>LTP の結果:
テストを実行中です。
## <a name="build-17110"></a>ビルド 17110
ビルド17110の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/02/27/announcing-windows-10-insider-preview-build-17110-fast/)を参照してください。
### <a name="wsl"></a>WSL
* /Init を Windows から終了することを許可します [GH 2928]。
* DrvFs では、既定でディレクトリごとの大文字小文字の区別が使用されるようになりました ("case = dir" マウントオプションと同等)。
* "Case = force" (以前の動作) を使用するには、レジストリキーを設定する必要があります。 次のコマンドを実行して、使用する必要がある場合は "case = force" を有効にします。 reg add HKLM\SYSTEM\CurrentControlSet\Services\lxss/v DrvFsAllowForceCaseSensitivity/t REG_DWORD/d 1
* 以前のバージョンの Windows で wsl で作成された既存のディレクトリがあり、大文字と小文字を区別する必要がある場合は、fsutil を使用し<path>て大文字と小文字を区別するように指定します。 fsutil .exe ファイル setcasesensitiveinfo enable
* Uname syscall から返された NULL の終了文字列。
### <a name="console"></a>Console
* 修正はありません。
### <a name="ltp-results"></a>LTP の結果:
テストを実行中です。
## <a name="build-17107"></a>ビルド17107
ビルド17107の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/02/23/announcing-windows-10-insider-preview-build-17107-fast-ring/)を参照してください。
### <a name="wsl"></a>WSL
* マスター pty エンドポイントで TCSETSF と TCSETSF をサポートする [GH 2552]。
* 相互運用プロセスを同時に開始すると、EINVAL [GH 2813] になります。
* /Proc/pid/status. に適切なトレースの状態を表示するように PTRACE_ATTACH を修正します。
* CLEARTID フラグと SETTID フラグの両方で複製された短い有効期間のプロセスが、TID アドレスをクリアせずに終了する可能性がある競合を修正しました。
* 17093より前のビルドから移動するときに、Linux ファイルシステムディレクトリをアップグレードするときにメッセージを表示します。 17093ファイルシステムの変更の詳細については、 [17093](https://github.com/MicrosoftDocs/WSL/blob/live/WSL/release-notes.md#build-17093)のリリースノートを参照してください。
### <a name="console"></a>Console
* 修正はありません。
### <a name="ltp-results"></a>LTP の結果:
テストを実行中です。
## <a name="build-17101"></a>ビルド17101
ビルド17101の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/02/14/announcing-windows-10-insider-preview-build-17101-fast-build-17604-skip-ahead/)を参照してください。
### <a name="wsl"></a>WSL
* Signalfd のサポート。 [GH 129]
* ファイル名に無効な NTFS 文字を含むファイル名は、プライベート Unicode 文字としてエンコードすることによってサポートされます。 [GH 1514]
* 書き込みがサポートされていない場合、自動マウントは読み取り専用にフォールバックします。 [GH 2603]
* Unicode サロゲートペア (絵文字文字など) の貼り付けを許可します。 [GH 2765]
* /Proc および/sys の疑似ファイルは、select、poll、epoll、et al から読み取りおよび書き込み準備を返す必要があります。 [GH 2838]
* レジストリが改ざんされているか、または破損している場合に、サービスが無限ループに入る可能性のある問題を修正しました。
* Iproute2 の新しい (アップストリーム 4.14) バージョンで動作するように netlink メッセージを修正します。
### <a name="console"></a>Console
* 修正はありません。
### <a name="ltp-results"></a>LTP の結果:
テストを実行中です。
## <a name="build-17093"></a>ビルド17093
ビルド17093の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/02/07/announcing-windows-10-insider-preview-build-17093-pc/)を参照してください。
#### <a name="important"></a>重要:
このビルドにアップグレードした後に初めて WSL を開始するときは、Linux ファイルシステムディレクトリをアップグレードする作業を実行する必要があります。 この処理には数分かかる場合があるため、WSL の開始に時間がかかることがあります。 これは、ストアからインストールされた各ディストリビューションにつき1回のみ発生します。
* DrvFs での大文字と小文字の区別のサポートが向上しました。
* DrvFs では、ディレクトリごとの大文字小文字の区別がサポートされるようになりました。 これは、ディレクトリに設定できる新しいフラグで、これらのディレクトリ内のすべての操作を大文字と小文字を区別して扱う必要があることを示します。これにより、Windows アプリケーションでも大文字と小文字のみが異なるファイルを正しく開くことができます。
* DrvFs には、ディレクトリごとに大文字と小文字の区別を制御する新しいマウントオプションがあります。
* case = force: すべてのディレクトリは大文字と小文字を区別して処理されます (ドライブのルートを除く)。 WSL で作成された新しいディレクトリは、大文字と小文字が区別されます。 これは、新しいディレクトリの大文字小文字の区別をマークする場合を除き、従来の動作です。
* case = dir: ディレクトリごとの大文字小文字の区別フラグを持つディレクトリのみが、大文字と小文字を区別して扱われます。他のディレクトリでは大文字と小文字が区別されます。 WSL で作成された新しいディレクトリは、大文字と小文字が区別されます。
* case = off: ディレクトリごとの大文字小文字の区別フラグを持つディレクトリのみが、大文字と小文字を区別して扱われます。他のディレクトリでは大文字と小文字が区別されます。 WSL で作成された新しいディレクトリは、大文字と小文字が区別されません。
* 注: 以前のリリースで WSL によって作成されたディレクトリには、このフラグが設定されていないため、"case = dir" オプションを使用した場合、は大文字と小文字が区別されません。 既存のディレクトリにこのフラグを設定する方法は近日中に予定されています。
* これらのオプションを使用してマウントする例 (既存のドライブの場合は、別のオプションでマウントする前にマウントを解除する必要があります): sudo mount-t drvfs C:/mnt/c case = dir
* ここでは、case = force は引き続き既定のオプションです。 これは、将来、case = dir に変更されます。
* DrvFs をマウントするときに Windows パスでスラッシュを使用できるようになりました。例: sudo mount-t drvfs/server/mnt/share
* WSL は、インスタンスの開始時に/etc/fstab ファイルを処理するようになりました [GH 2636]。
* これは、DrvFs ドライブを自動的にマウントする前に行われます。fstab によって既にマウントされているドライブは自動的には再マウントされないため、特定のドライブのマウントポイントを変更することができます。
* この動作は、wsl を使用して無効にすることができます。
* Mount、mountinfo、および mountstats の各ファイルは、円記号やスペースなどの特殊文字を正しくエスケープします [GH 2799]
* WSL シンボリックリンクなどの DrvFs を使用して作成された特殊なファイル、またはメタデータが有効になっている場合は、fifo とソケットを使用して、Windows からコピーおよび移動できるようになりました。
#### <a name="wsl-is-more-configurable-with-wslconf"></a>WSL は wsl. conf で構成可能
WSL で特定の機能を自動的に構成するためのメソッドを追加しました。これは、サブシステムを起動するたびに適用されます。 これには、自動マウントオプションとネットワーク構成が含まれます。 詳細については、次のブログ投稿を参照してください。 https://aka.ms/wslconf
#### <a name="af_unix-allows-socket-connections-between-linux-processes-on-wsl-and-windows-native-processes"></a>AF_UNIX は、WSL および Windows ネイティブプロセスでの Linux プロセス間のソケット接続を許可します。
WSL と Windows アプリケーションは、Unix ソケット経由で相互に通信できるようになりました。 Windows でサービスを実行し、Windows と WSL アプリの両方で使用できるようにする場合を考えてみましょう。 これは、Unix ソケットで可能です。 詳細については、ブログの投稿の「」を参照してください。 https://aka.ms/afunixinterop
### <a name="wsl"></a>WSL
* MAP_NORESERVE を使用した mmap () のサポート [GH 121、2784]
* Support CLONE_PTRACE and CLONE_UNTRACED [GH 121, 2781]
* 複製で SIGCHLD 以外の終了シグナルを処理する [GH 121, 2781]
* スタブ/proc/sys/fs/inotify/max_user_instances と/proc/sys/fs/inotify/max_user_watches [GH 1705]
* 0以外のオフセットで読み込みヘッダーを含む ELF バイナリの読み込み中にエラーが発生した [GH 1884]
* イメージの読み込み時に、ページの末尾のバイトをゼロアウトします。
* Execve がサイレントモードでプロセスを終了するケースを減らす
### <a name="console"></a>Console
* 修正はありません。
### <a name="ltp-results"></a>LTP の結果:
テストを実行中です。
## <a name="build-17083"></a>ビルド 17083
ビルド17083の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/01/24/announcing-windows-10-insider-preview-build-17083-for-pc/)を参照してください。
### <a name="wsl"></a>WSL
* Epoll に関連するバグチェック (GH 2798、2801、2857) を修正します。
* ASLR をオフにするとハングを修正する [GH 1185, 2870]
* Mmap 操作がアトミックとして表示されることを確認する [GH 2732]
### <a name="console"></a>Console
* 修正はありません。
### <a name="ltp-results"></a>LTP の結果:
テストを実行中です。
## <a name="build-17074"></a>ビルド17074
ビルド17074の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2018/01/11/announcing-windows-10-insider-preview-build-17074-pc/)を参照してください。
### <a name="wsl"></a>WSL
* DrvFs メタデータの固定ストレージ形式 [GH 2777] </br>
**重要:** このビルドの前に作成された DrvFs メタデータは、正しく表示されないか、まったく表示されません。 影響を受けるファイルを修正するには、chmod と chown を使用してメタデータを再適用します。
* 複数のシグナルと再開可能な syscall の問題を修正した。
### <a name="console"></a>Console
* 修正はありません。
### <a name="ltp-results"></a>LTP の結果:
テストを実行中です。
## <a name="build-17063"></a>ビルド17063
ビルド17063の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/12/19/announcing-windows-10-insider-preview-build-17063-pc/)を参照してください。
### <a name="wsl"></a>WSL
* DrvFs は、追加の Linux メタデータをサポートします。 これにより、chmod/chown を使用してファイルの所有者とモードを設定できるほか、fifo、unix ソケット、デバイスファイルなどの特殊なファイルを作成することもできます。 現時点では、これはまだ試験段階であるため、既定では無効になっています。
**注:** DrvFs で使用されるメタデータ形式のバグを修正しています。 メタデータは実験のためにこのビルドで機能しますが、今後のビルドでは、このビルドによって作成されたメタデータを正しく読み取ることができません。 変更したファイルの所有者を手動で更新しなければならない場合があります。カスタムデバイス ID を持つデバイスを再作成する必要があります。
有効にするには、メタデータオプションを使用して DrvFs をマウントします (既存のマウントで有効にするには、最初にマウントを解除する必要があります)。
```bash
mount -t drvfs C: /mnt/c -o metadata
```
Linux のアクセス許可は、ファイルに追加のメタデータとして追加されます。Windows のアクセス許可には影響しません。 Windows エディターを使用してファイルを編集すると、メタデータが削除される場合があることに注意してください。 この場合、ファイルは既定のアクセス許可に戻ります。
* メタデータなしでファイルを制御するための、DrvFs にマウントオプションを追加しました。
* uid: すべてのファイルの所有者に使用されるユーザー ID。
* gid: すべてのファイルの所有者に使用されるグループ ID。
* umask: すべてのファイルとディレクトリに対して除外するアクセス許可の8進数のマスク。
* fmask: すべての標準ファイルに対して除外するアクセス許可の8進数のマスク。
* dmask: すべてのディレクトリに対して除外するアクセス許可の8進数のマスク。
例:
```
mount -t drvfs C: /mnt/c -o uid=1000,gid=1000,umask=22,fmask=111
```
メタデータオプションと組み合わせて、メタデータのないファイルに対する既定のアクセス許可を指定します。
* では、wsl と`WSLENV`Win32 の間で環境変数がどのように流れるかを構成するために、新しい環境変数が導入されました。
以下に例を示します。
``` bash
WSLENV=GOPATH/l:USERPROFILE/pu:DISPLAY
```
`WSLENV`は、wsl から Win32 または Win32 プロセスから WSL プロセスを起動するときに含めることができる環境変数のコロン区切りの一覧です。 各変数には、スラッシュとその後に続くフラグを付けて、変換方法を指定できます。
* irtran-p値は、WSL パスと Win32 パスの間で変換されるパスです。
* 左右値はパスの一覧です。 WSL では、コロンで区切られたリストです。 Win32 では、セミコロンで区切られたリストです。
* u値は、Win32 から WSL を呼び出すときにのみ含める必要があります
* リダイレクト値は、WSL から Win32 を呼び出すときにのみ含める必要があります
ユーザーのカスタム`WSLENV` Windows 環境では、.bashrc またはを設定できます。
* drvfs マウントによって tar、cp-p からのタイムスタンプが正しく保持される (GH 1939)
* drvfs symlink は正しいサイズを報告します (GH 2641)
* I/O サイズが非常に大きい場合の読み取り/書き込みの機能 (GH 2653)
* waitpid はプロセスグループ Id と連動します (GH 2534)
* 大きな予約領域での mmap パフォーマンスが大幅に向上しました。ghc のパフォーマンスを向上させます (GH 1671)
* READ_IMPLIES_EXEC でのパーソナリティのサポート最大化 a と clisp (GH 1185) を修正します。
* mprotect は PROT_GROWSDOWN をサポートしています。clisp (GH 1128) を修正します。
* 過剰コミットモードでのページフォールトの修正sbcl (GH 1128) を修正します。
* 複製では、より多くのフラグの組み合わせがサポートされます
* Epoll ファイルの select/epoll (以前は no op) をサポートします。
* 未実装の syscall の ptrace を通知します。
* Resolv.conf を生成するときにアップしていないインターフェイスを無視する [GH 2694]
* 物理アドレスのないネットワークインターフェイスを列挙します。 [GH 2685]
* 追加のバグの修正と改善。
### <a name="linux-tools-available-to-developers-on-windows"></a>Windows の開発者が使用できる Linux ツール
* Windows コマンドラインツールチェーンには、bsdtar (tar) と curl が含まれています。
この2つの新しいツールの追加の詳細と、Windows での開発者エクスペリエンスの整形方法を確認するには、[このブログ](https://aka.ms/tarcurlwindows)を参照してください。
* `AF_UNIX`は、Windows Insider SDK (17061 +) で利用できます。
の詳細と、Windows 上の`AF_UNIX`開発者が使用する方法については、[このブログ](https://blogs.msdn.microsoft.com/commandline/2017/12/19/af_unix-comes-to-windows/)を参照してください。
### <a name="console"></a>Console
* 修正はありません。
### <a name="ltp-results"></a>LTP の結果:
テストを実行中です。
## <a name="build-17046"></a>ビルド17046
ビルド17046の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/11/22/announcing-windows-10-insider-preview-build-17046-pc)を参照してください。
### <a name="fixed"></a>固定
#### <a name="wsl"></a>WSL
- アクティブなターミナルを使用せずにプロセスを実行できるようにします。 [GH 709、1007、1511、2252、2391、et al.]
- CLONE_VFORK と CLONE_VM のサポートの強化。 [GH 1878、2615]
- WSL ネットワーク操作の TDI フィルタードライバーをスキップします。 [GH 1554]
- DrvFs は、特定の条件が満たされたときに NT シンボリックリンクを作成します。 [GH 353、1475、2602]
- リンク先は相対パスである必要があり、マウントポイントやシンボリックリンクを越えることはできず、存在する必要があります。
- 開発者モードが有効になっていない場合は、ユーザーは SE_CREATE_SYMBOLIC_LINK_PRIVILEGE を持っている必要があります (通常は、管理者特権で起動する必要があります)。
- それ以外の状況でも、DrvFs は WSL シンボリックリンクを作成します。
- 昇格および昇格されていない WSL インスタンスの同時実行を許可します。
- /Proc/sys/kernel/yama/ptrace_scope のサポート
- Wslpath を追加して、WSL <-> Windows パス変換を実行します。 [GH 522、1243、1834、2327、et al]
```
wslpath usage:
-a force result to absolute path format
-u translate from a Windows path to a WSL path (default)
-w translate from a WSL path to a Windows path
-m translate from a WSL path to a Windows path, with ‘/’ instead of ‘\\’
EX: wslpath ‘c:\users’
```
#### <a name="console"></a>Console
- 修正はありません。
### <a name="ltp-results"></a>LTP の結果:
テストを実行中です。
## <a name="build-17040"></a>ビルド17040
ビルド17040の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/11/16/announcing-windows-10-insider-preview-build-17040-pc)を参照してください。<br/>
### <a name="fixed"></a>固定
#### <a name="wsl"></a>WSL
- 17035以降の修正プログラムはありません。
#### <a name="console"></a>Console
- 17035以降の修正プログラムはありません。
### <a name="ltp-results"></a>LTP の結果:
テストを実行中です。
## <a name="build-17035"></a>ビルド17035
ビルド17035の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/11/08/announcing-windows-10-insider-preview-build-17035-pc)を参照してください。<br/>
### <a name="fixed"></a>固定
#### <a name="wsl"></a>WSL
- DrvFs 上のファイルへのアクセスは、場合によっては、EINVAL で失敗することがあります。 [GH 2448]
#### <a name="console"></a>Console
- VT モードで行を挿入または削除するときに色が失われることがあります。
### <a name="ltp-results"></a>LTP の結果:
テストを実行中です。
## <a name="build-17025"></a>ビルド17025
ビルド17025の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/10/25/announcing-windows-10-insider-preview-build-17025-pc)を参照してください。<br/>
### <a name="fixed"></a>固定
#### <a name="wsl"></a>WSL
- 新しいフォアグラウンドプロセスグループで初期プロセスを開始します [GH 1653, 2510]。
- SIGHUP 配信の修正プログラム [GH 2496]。
- [GH 2497] が指定されていない場合は、既定の仮想ブリッジ名を生成します。
- /Proc/sys/kernel/random/boot_id [GH 2518] を実装します。
- 相互運用機能の stdout/stderr パイプの修正。
- Syncfs システム呼び出しをスタブします。
#### <a name="console"></a>Console
- サードパーティコンソールの入力 VT translation の修正 [GH 111]
### <a name="ltp-results"></a>LTP の結果:
テストを実行中です。
## <a name="build-17017"></a>ビルド17017
ビルド17017の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/10/13/announcing-windows-10-insider-preview-build-17017-pc)を参照してください。<br/>
### <a name="fixed"></a>固定
#### <a name="wsl"></a>WSL
- 空の ELF プログラムヘッダー [GH 330] を無視します。
- LxssManager が非対話型ユーザーの WSL インスタンスを作成できるようにします (ssh およびスケジュールされたタスクのサポート) [GH 777, 1602]。
- WSL-> Win32 > WSL ("設立") シナリオのサポート [GH 1228]。
- 相互運用機能によって起動されるコンソールアプリの終了の制限付きサポート [GH 1614]。
- Devpts のマウントオプション [GH 1948] をサポートします。
- Ptrace が子スタートアップをブロックしています [GH 2333]。
- EPOLLET には、一部のイベント [GH 2462] がありません。
- PTRACE_GETSIGINFO の他のデータを返します。
- Getdents と lseek では、正しくない結果が得られます。
- いくつかの Win32 相互運用アプリのハングを修正しました。これ以上データのないパイプで入力を待機しています。
- O_ASYNC は、tty/pty ファイルをサポートしています。
- 追加の機能強化とバグ修正
#### <a name="console"></a>Console
- このリリースでは、コンソールに関連する変更はありません。
### <a name="ltp-results"></a>LTP の結果:
テストを実行中です。
## <a name="fall-creators-update"></a>Fall Creators Update
## <a name="build-16288"></a>ビルド16288
ビルド16288の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/09/12/announcing-windows-10-insider-preview-build-16288-pc-build-15250-mobile/#7pLWQbj23JisfzV5.97/)を参照してください。<br/>
### <a name="fixed"></a>固定
#### <a name="wsl"></a>WSL
- ソケットファイル記述子の uid、gid、およびモードを正しく初期化して報告する [GH 2490]
- 追加の機能強化とバグ修正
#### <a name="console"></a>Console
- このリリースでは、コンソールに関連する変更はありません。
### <a name="ltp-results"></a>LTP の結果:
16273以降の変更はありません
## <a name="build-16278"></a>ビルド16278
ビルド162738の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/08/29/announcing-windows-10-insider-preview-build-16278-pc/#HMz6Xq7Su68WKi0t.97/)を参照してください。<br/>
### <a name="fixed"></a>固定
#### <a name="wsl"></a>WSL
- LX MM 状態を解除するときに、ファイルによってサポートされるセクションのマップされたビューを明示的にマップ解除する [GH 2415]
- 追加の機能強化とバグ修正
#### <a name="console"></a>Console
- このリリースでは、コンソールに関連する変更はありません。
### <a name="ltp-results"></a>LTP の結果:
16273以降の変更はありません
## <a name="build-16275"></a>ビルド16275
ビルド162735の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/08/25/announcing-windows-10-insider-preview-build-16275-pc-build-15245-mobile/#8QkxWqQbY37yZslV.97/)を参照してください。<br/>
### <a name="fixed"></a>固定
#### <a name="wsl"></a>WSL
- このリリースでは、WSL 関連の変更はありません。
#### <a name="console"></a>Console
- このリリースでは、コンソールに関連する変更はありません。
### <a name="ltp-results"></a>LTP の結果:
16273以降の変更はありません
## <a name="build-16273"></a>ビルド16273
ビルド16273の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/08/23/announcing-windows-10-insider-preview-build-16273-pc/)を参照してください。<br/>
### <a name="fixed"></a>固定
#### <a name="wsl"></a>WSL
- DrvFs がディレクトリに対して正しくないファイルの種類を報告する場合があるという問題を修正しました [GH 2392]
- Uevent [GH 1121、2293、2242、2295、2235、648、637] を使用するプログラムのブロックを解除するための NETLINK_KOBJECT_UEVENT sockets の作成を許可します
- 非ブロッキング接続のサポートを追加する [GH 903、1391、1584、1585、1829、2290、2314]
- CLONE_FS CLONE システム呼び出しフラグを実装する [GH 2242]
- NT interop でタブまたは引用符を正しく処理しない問題を修正する [GH 1625, 2164]
- WSL インスタンスを再起動しようとしたときにアクセス拒否エラーを解決する [GH 651、2095]
- Futex FUTEX_REQUEUE と FUTEX_CMP_REQUEUE 操作の実装 [GH 2242]
- さまざまな SysFs ファイルのアクセス許可を修正する [GH 2214]
- セットアップ中に Haskell stack のハングを修正する [GH 2290]
- Binfmt_misc ' C ' ' O ' および ' P ' フラグを実装する [GH 2103]
- /Proc/sys/kernel/shmmax/shmmni & 追加する [GH 1753]
- Ioprio_set システム呼び出しの部分的なサポートを追加する [GH 498]
- スタブ SO_REUSEPORT & SO_PASSCRED for netlink sockets のサポートの追加 [GH 69]
- ディストリビューションが現在インストールまたはアンインストールされている場合は、RegisterDistribuiton から別のエラーコードを返します。
- Wslconfig .exe 経由で部分的にインストールされた WSL ディストリビューションの登録解除を許可する
- Udp:: msg_peek から python ソケットテストハングを修正します。
- 追加の機能強化とバグ修正
#### <a name="console"></a>Console
- このリリースでは、コンソールに関連する変更はありません。
### <a name="ltp-results"></a>LTP の結果:
テストの合計:1904<br/>
スキップされたテストの合計数:209<br/>
合計エラー数:229<br/>
[LTP テストの実行ログ](https://github.com/Microsoft/CommandLine-Documentation/tree/live/LTP_Results/16273)<br/>
## <a name="build-16257"></a>ビルド 16257
ビルド16257の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/08/02/announcing-windows-10-insider-preview-build-16257-pc-build-15237-mobile/)を参照してください。<br/>
### <a name="fixed"></a>固定
#### <a name="wsl"></a>WSL
- Prlimit64 システム呼び出しを実装する
- Ulimit-n (setrlimit RLIMIT_NOFILE) のサポートを追加する [GH 1688]
- TCP ソケットのスタブ MSG_MORE [GH 2351]
- 無効な AT_EXECFN 補助ベクター動作の修正 [GH 2133]
- コンソール/tty のコピー/貼り付け動作を修正し、完全なバッファー処理をさらに追加する [GH 2204, 2131]
- AT_SECURE プログラムと set-group-ID プログラムの補助ベクターでの設定 [GH 2031]
- Psuedo-ターミナルマスターエンドポイントが TIOCPGRP を処理しない [GH 1063]
- Lseek が LxFs のディレクトリを巻き戻していることを修正する [GH 2310]
- 大きな使用率が高くなった後の GH のロック [1882]
- 追加の機能強化とバグ修正
#### <a name="console"></a>Console
- すべての場所で水平線/アンダースコアを修正する [GH 2168]
- プロセスの順序が変更されたことを修正し、NPM を閉じることが困難になる [GH 2170]
- 新しい配色を追加しました。 https://blogs.msdn.microsoft.com/commandline/2017/08/02/updating-the-windows-console-colors/
### <a name="ltp-results"></a>LTP の結果:
16251以降の変更はありません
### <a name="syscall-support"></a>Syscall のサポート
次に示すのは、WSL でいくつかの実装を持つ新しいまたは強化された syscall の一覧です。 この一覧の syscall は、少なくとも1つのシナリオでサポートされていますが、現時点では一部のパラメーターがサポートされていない可能性があります。
`prlimit64`<br/>
### <a name="known-issues"></a>既知の問題
#### <a name="github-issue-2392-windows-folders-not-recognized-by-wsl-httpsgithubcommicrosoftbashonwindowsissues2392"></a>[GitHub の問題 2392:Windows フォルダーは WSL によって認識されません...](https://github.com/Microsoft/BashOnWindows/issues/2392)
ビルド16257では、を介し`/mnt/c/...`て Windows ファイル/フォルダーを列挙するときに、wsl に問題があります。
この問題は修正されており、8/14/2017 の実行時に、Insider ビルドでリリースされる必要があります。
<br/>
## <a name="build-16251"></a>ビルド16251
ビルド16251の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/07/26/announcing-windows-10-insider-preview-build-16251-pc-build-15235-mobile/)を参照してください。<br/>
### <a name="fixed"></a>固定
#### <a name="wsl"></a>WSL
- WSL オプションコンポーネントからベータタグを削除します。詳細については、[ブログの投稿](https://blogs.msdn.microsoft.com/commandline/2017/07/28/windows-subsystem-for-linux-out-of-beta/)を参照してください。
- Set-ユーザー ID および set-ID バイナリが exec で正しく初期化されました。 exec [GH 962, 1415, 2072]
- Ptrace PTRACE_O_TRACEEXIT のサポートを追加しました [GH 555]
- NT_FPREGSET を使用した ptrace PTRACE_GETFPREGS と PTRACE_GETREGSET のサポートを追加しました [GH 555]
- 無視されたシグナルで停止する ptrace を修正しました
- 追加の機能強化とバグ修正
#### <a name="console"></a>Console
- このリリースでは、コンソールに関連する変更はありません。
### <a name="ltp-results"></a>LTP の結果:
成功したテストの数:768</br>
失敗したテストの数:244</br>
スキップされたテストの数:96</br>
[LTP テストの実行ログ](https://github.com/Microsoft/CommandLine-Documentation/tree/live/LTP_Results/16251)<br/>
</br>
## <a name="build-16241"></a>ビルド16241
ビルド16241の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/07/13/announcing-windows-10-insider-preview-build-16241-pc-build-15230-mobile/)を参照してください。<br/>
### <a name="fixed"></a>固定
#### <a name="wsl"></a>WSL
- このリリースでは、WSL 関連の変更はありません。
#### <a name="console"></a>Console
- [ここで](https://www.reddit.com/r/Windows10/comments/6in82t/i_believe_ive_found_the_most_obscure_bug_ever/)最初に報告された、10進線に誤った文字を出力するように修正しました。
- コードページ 65001 (utf8) に出力テキストが表示されないように修正します。
- ある色の RGB 値に対して行われた変更を、選択の変更時にパレットの他の部分に転送しないでください。 これにより、コンソールプロパティシートが非常に使いやすいようになります。
- Ctrl + S が正しく動作していません
- ANSI エスケープコードに完全に存在しない太字/-Dim [GH 2174]
- コンソールが Vim 色のテーマを正しくサポートしていない [GH 1706]
- 特定の文字を貼り付けることはできません [GH 2149]
- 編集/コマンドライン上にあるときに bash ウィンドウのサイズを変更すると、リフローサイズの変更がおかしくなる [GH ConEmu 1123]
- Ctrl + L を押したまま画面をダーティにする [GH 1978]
- HDPI で VT を表示するときのコンソールレンダリングのバグ [GH 1907]
- Unicode 文字 U + 30FB で Japansese 文字が奇妙に見える [GH 2146]
- 追加の機能強化とバグ修正
</br>
## <a name="build-16237"></a>ビルド 16237
ビルド16237の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/07/07/announcing-windows-10-insider-preview-build-16237-pc/)を参照してください。<br/>
### <a name="fixed"></a>固定
- Lxfs に EAs がないファイルの既定の属性を使用する (ルート、ルート、0000)
- 拡張属性を使用するディストリビューションのサポートを追加しました
- Getdents と getdents64 によって返されるエントリの埋め込みを修正する
- Shmctl SHM_STAT システム呼び出しのアクセス許可チェックを修正する [GH 2068]
- Tty の初期 epoll 状態が正しくないことを修正した [GH 2231]
- すべてのエントリを返さないように DrvFs readdir を修正する [GH 2077]
- ファイルのリンクが解除されたときに LxFs readdir を修正する [GH 2077]
- Procfs を使用して、リンクされていない drvfs ファイルを再び開くことを許可する
- WSL 機能を無効にするためのグローバルレジストリキーの上書き (相互運用/ドライブのマウント) を追加しました
- DrvFs (および LxFs) の "stat" で間違ったブロックカウントを修正する [GH 1894]
- 追加の機能強化とバグ修正
</br>
## <a name="build-16232"></a>ビルド16232
ビルド16232の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/06/28/announcing-windows-10-insider-preview-build-16232-pc-build-15228-mobile/)を参照してください。<br/>
### <a name="fixed"></a>固定
- このリリースでは、WSL 関連の変更はありません。
</br>
## <a name="build-16226"></a>ビルド16226
ビルド16226の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/06/21/announcing-windows-10-insider-preview-build-16226-pc/)を参照してください。<br/>
### <a name="fixed"></a>固定
- xattr 関連の syscall サポート (getxattr、setxattr、listxattr、removexattr)。
- capablity xattr のサポート。
- 特定のファイルシステムとフィルター (MS 以外の SMB サーバーを含む) との互換性が向上しました。 [GH #1952]
- OneDrive プレースホルダー、GVFS プレースホルダー、および圧縮された OS 圧縮ファイルのサポートが強化されました。
- 追加の機能強化とバグ修正
</br>
## <a name="build-16215"></a>ビルド16215
ビルド16215の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/06/08/announcing-windows-10-insider-preview-build-16215-pc-build-15222-mobile/)を参照してください。<br/>
### <a name="fixed"></a>固定
- WSL には開発者モードが不要になりました。
- Drvfs のディレクトリの接合をサポートします。
- WSL distribution appx パッケージのアンインストールを処理します。
- Procfs を更新して、プライベートと共有のマッピングを表示します。
- Wslconfig .exe を追加して、部分的にインストールまたはアンインストールされたディストリビューションをクリーンアップします。
- TCP ソケット用の IP_MTU_DISCOVER のサポートを追加しました。 [GH 1639、2115、2205]
- AF_INADDR へのルートのプロトコルファミリを推定します。
- シリアルデバイスの機能強化 [GH 1929]。
</br>
## <a name="build-16199"></a>ビルド16199
ビルド16199の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/05/17/announcing-windows-10-insider-preview-build-16199-pc-build-15215-mobile/)を参照してください。<br/>
### <a name="fixed"></a>固定
- これらのリリースでは、WSL 関連の変更はありません。
</br>
## <a name="build-16193"></a>ビルド16193
ビルド16193の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/05/11/announcing-windows-10-insider-preview-build-16193-pc-build-15213-mobile/)を参照してください。<br/>
### <a name="fixed"></a>固定
- 送信 SIGCONT と threadgroup 終了の間の競合状態 [GH 1973]
- tty および pty デバイスを FILE_DEVICE_CONSOLE ではなくレポート FILE_DEVICE_NAMED_PIPE に変更する [GH 1840]
- IP_OPTIONS の SSH 修正
- DrvFs を init デーモンにマウントしました [GH 1862、1968、1767、1933]
- 次の NT シンボリックリンクに対する DrvFs のサポートが追加されました。
</br>
## <a name="build-16184"></a>ビルド16184
ビルド16184の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/04/28/announcing-windows-10-insider-preview-build-16184-pc-build-15208-mobile/)を参照してください。<br/>
### <a name="fixed"></a>固定
- Apt パッケージのメンテナンスタスク (lxrun/update) を削除しました
- Node.js の Windows プロセスからに表示されない修正済みの出力 [GH 1840]
- Lxcore での調整要件の緩和 [GH 1794]
- システム呼び出しの数値における AT_EMPTY_PATH フラグの処理を修正した。
- 開いているハンドルを持つ DrvFs ファイルを削除すると、ファイルに未定義の動作が発生する問題を修正した (GH 544、966、1357、1535、1615)
- /etc/hosts は Windows hosts ファイル (%windir%\system32\drivers\etc\hosts) からエントリを継承するようになりました [GH 1495]
</br>
## <a name="build-16179"></a>ビルド16179
ビルド16179の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/04/19/announcing-windows-10-insider-preview-build-16179-pc-build-15205-mobile/)を参照してください。<br/>
### <a name="fixed"></a>固定
- 今週、WSL の変更はありません。
</br>
## <a name="build-16176"></a>ビルド16176
ビルド16176の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/04/14/announcing-windows-10-insider-preview-build-16176-pc-build-15204-mobile/)を参照してください。<br/>
### <a name="fixed"></a>固定
- [有効なシリアルサポート](https://blogs.msdn.microsoft.com/wsl/2017/04/14/serial-support-on-the-windows-subsystem-for-linux/)
- 追加された IP ソケットオプション IP_OPTIONS [GH 1116]
- Pwritev 関数の実装 (nginx/PHP-FPM へのファイルのアップロード) [GH 1506]
- 追加された IP ソケットオプション IP_MULTICAST_IF & IPV6_MULTICAST_IF [GH 990]
- ソケットオプション IP_MULTICAST_LOOP & IPV6_MULTICAST_LOOP のサポート [GH 1678]
- Apps ノード、traceroute、掘り下げ、nslookup、host の IP (V6) MTU socket オプションを追加しました
- 追加された IP ソケットオプション IPV6_UNICAST_HOPS
- [ファイルシステムの機能強化](https://blogs.msdn.microsoft.com/wsl/2017/04/18/file-system-improvements-to-the-windows-subsystem-for-linux/)
* UNC パスのマウントを許可する
* Drvfs で CDF サポートを有効にする
* Drvfs でネットワークファイルシステムのアクセス許可を正しく処理する
* Drvfs にリモートドライブのサポートを追加する
* Drvfs での FAT サポートを有効にする
- その他の修正プログラムと機能強化
### <a name="ltp-results"></a>LTP の結果
15042以降の変更はありません
</br>
## <a name="build-16170"></a>ビルド16170
ビルド16170の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/04/07/announcing-windows-10-insider-preview-build-16170-pc/)を参照してください。<br/>
WSL のテストの取り組みについて説明する新しい[ブログ投稿](https://blogs.msdn.microsoft.com/wsl/2017/04/11/testing-the-windows-subsystem-for-linux/)をリリースしました。
### <a name="fixed"></a>固定
- サポートソケットオプション IP_ADD_MEMBERSHIP & IPV6_ADD_MEMBERSHIP [GH 1678]
- PTRACE_OLDSETOPTIONS のサポートを追加します。 [GH 1692]
- その他の修正プログラムと機能強化
### <a name="ltp-results"></a>LTP の結果
15042以降の変更はありません
</br>
## <a name="build-15046-to-windows-10-creators-update"></a>ビルド15046から Windows 10 の作成者への更新
Windows 10 の作成者の更新プログラムに含まれるように計画されている WSL 修正プログラムや機能はこれ以上ありません。 WSL のリリースノートは、次の主要な Windows Update を対象とした追加のために、今後数週間にわたって再開されます。 ビルド15046および今後の Insider リリースに関する一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/02/28/announcing-windows-10-insider-preview-build-15046-pc/)を参照してください。 <br/><br/>
<br/>
## <a name="build-15042"></a>ビルド15042
ビルド15042の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/02/24/announcing-windows-10-insider-preview-build-15042-pc-build-15043-mobile/)を参照してください。<br/>
### <a name="fixed"></a>固定
- "." で終わるパスの削除時にデッドロックが発生する問題を修正します。
- FIONBIO が成功時に0を返さないという問題を修正した [GH 1683]
- Inet データグラムソケットの長さゼロの読み取りに関する問題を修正した
- Drvfs inode 参照で競合状態が発生したことが原因でデッドロックが発生する可能性を修正する [GH 1675]
- Unix ソケットの補助データの拡張サポートSCM_CREDENTIALS および SCM_RIGHTS [GH 514, 613, 1326]
- その他の修正プログラムと機能強化
### <a name="ltp-results"></a>LTP の結果:
成功したテストの数:737</br>
非パッシング (失敗、スキップされたなど) の数:255
</br>
## <a name="build-15031"></a>ビルド15031
ビルド15031の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/02/08/announcing-windows-10-insider-preview-build-15031-pc/)を参照してください。<br/>
### <a name="fixed"></a>固定
- Time (2) が散発的に不適切な動作するバグを修正しています。
- \* SIGSYSCALL MASK がシグナルマスクを破壊する可能性がある問題を修正しました。
- WSL プロセス作成通知でコマンドラインの完全な長さを返すようになりました。 [GH 1632]
- WSL は、GDB がハングした場合に ptrace を介してスレッドの終了を報告するようになりました。 [GH 1196]
- Tmux IO が大量に発生した後に ptys がハングするバグを修正します。 [GH 1358]
- 多くのシステムコールでタイムアウトの検証を修正 (futex、semtimedop、ppoll、sigtimedwait、itimer、timer_create)
- 追加された eventfd EFD_SEMAPHORE サポート [GH 452]
- その他の修正プログラムと機能強化
### <a name="ltp-results"></a>LTP の結果:
成功したテストの数:737</br>
非パッシング (失敗、スキップされたなど) の数:255 </br>
[LTP テストの実行ログ](https://github.com/Microsoft/CommandLine-Documentation/tree/live/LTP_Results/15031)<br/>
<br/>
## <a name="build-15025"></a>ビルド15025
ビルド15025の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/02/01/announcing-windows-10-insider-preview-build-15025-pc/)を参照してください。<br/>
### <a name="fixed"></a>固定
- Grep 2.27 を破損したバグの修正 [GH 1578]
- Eventfd2 syscall の EFD_SEMAPHORE フラグの実装 [GH 452]
- 実装された/proc/[pid]/net/ipv6_route [GH 1608]
- Unix ストリームソケットに対するシグナル駆動型 IO のサポート [GH 393, 68]
- F_GETPIPE_SZ と F_SETPIPE_SZ のサポート [GH 1012]
- Recvmmsg () syscall の実装 [GH 1531]
- Epoll_wait () が待機していないバグを修正 [GH 1609]
- /Proc/version_signature を実装する
- T syscall は、両方のファイル記述子が同じパイプを参照している場合にエラーを返すようになりました
- Unix ソケット用の SO_PEERCRED の正しい動作を実装しています
- Tkill syscall の無効なパラメーター処理を修正した
- Drvfs の preformace を増やすための変更
- Ruby IO ブロックの軽微な修正
- Inet sockets の MSG_DONTWAIT フラグの EINVAL を返す recvmsg () を修正した [GH 1296]
- その他の修正プログラムと機能強化
### <a name="ltp-results"></a>LTP の結果:
成功したテストの数:732</br>
非パッシング (失敗、スキップされたなど) の数:255 </br>
[LTP テストの実行ログ](https://github.com/Microsoft/CommandLine-Documentation/tree/live/LTP_Results/15025)<br/>
<br/>
## <a name="build-15019"></a>ビルド15019
ビルド15019の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/01/27/announcing-windows-10-insider-preview-build-15019-pc/)を参照してください。<br/>
### <a name="fixed"></a>固定
- Htop (GH 823、945、971) などのツールに対して procfs の CPU 使用率が誤って報告されたバグを修正しました
- 既存のファイルに対して O_TRUNC を使用して open () を呼び出すと、IN_OPEN の前に IN_MODIFY が生成されるようになりました。
- Unix socket getsockopt SO_ERROR で postgress [GH 61, 1354] を有効にするための修正
- /Proc/sys/net/core/somaxconn を実装する
- Apt-パッケージ更新のバックグラウンドタスクをビューから非表示にするようになりました
- Ipv6 localhost のスコープをクリアします (Spring Framework (Java) エラー)。
- その他の修正プログラムと機能強化
### <a name="ltp-results"></a>LTP の結果:
成功したテストの数:714 </br>
非パッシング (失敗、スキップされたなど) の数:249 </br>
[LTP テストの実行ログ](https://github.com/Microsoft/CommandLine-Documentation/tree/live/LTP_Results/15019)<br/>
<br/>
## <a name="build-15014"></a>ビルド15014
ビルド15014の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/01/19/announcing-windows-10-insider-preview-build-15014-for-pc-and-mobile-hello-windows-insiders-today-we-are-excited-to-be-releasing-windows-10-insider-preview-build-15014-for-pc-and-mobile)を参照してください。<br/>
### <a name="fixed"></a>固定
- Ctrl + C は意図したとおりに動作するようになりました
- htop と ps auxw で、正しいリソース使用率 (GH #516) が表示されるようになりました
- NT 例外からシグナルへの基本的な変換です。 (GH #513)
- fallocate は、EINVAL (GH #1571) ではなく領域が不足しているときに、ENOSPC で失敗するようになりました。
- 追加された/proc/sys/kernel/sem.
- Semop および semtimedop システム呼び出しを実装します。
- IP_RECVTOS & IPV6_RECVTCLASS socket オプションで nslookup エラーを修正した (GH 69)
- ソケットオプションの IP_RECVTTL と IPV6_RECVHOPLIMIT のサポート
- その他の修正プログラムと機能強化
### <a name="ltp-results"></a>LTP の結果:
成功したテストの数:709 </br>
非パッシング (失敗、スキップされたなど) の数:255 </br>
[LTP テストの実行ログ](https://github.com/Microsoft/CommandLine-Documentation/tree/live/LTP_Results/15014)<br/>
### <a name="syscall-summary"></a>Syscall の概要
合計 Syscall:384 </br>
実装された合計:235 </br>
スタブの合計数:22 </br>
未実装の合計数:127 </br>
[詳細な内訳](https://github.com/Microsoft/CommandLine-Documentation/tree/live/LTP_Results/15014/Syscalls.txt)<br/>
<br/>
## <a name="build-15007"></a>ビルド15007
ビルド15007の一般的な Windows 情報については、 [windows のブログ]( https://blogs.windows.com/windowsexperience/2017/01/12/announcing-windows-10-insider-preview-build-15007-pc-mobile)を参照してください。<br/>
### <a name="known-issue"></a>既知の問題
- コンソールが一部の Ctrl + <key>入力を認識しないという既知のバグがあります。 これには、通常の "c" キーの押下として機能する ctrl + c コマンドが含まれます。
- 回避策:代替キーを Ctrl + C にマップします。 たとえば、ctrl + K を Ctrl + C キーにマップするに`stty intr \^k`は、次のようにします。 このマッピングはターミナル単位で行われ、bash が起動されるたびに実行される必要があります。 ユーザーは、オプションを調べて、`.bashrc`
### <a name="fixed"></a>固定
- WSL を実行すると CPU コアの 100% が消費される問題を修正しました
- ソケットオプション IP_PKTINFO、IPV6_RECVPKTINFO がサポートされるようになりました。 (GH #851、987)
- Lxcore でネットワークインターフェイスの物理アドレスを16バイトに切り捨てる (GH #1452、1414、1343、468、308)
- その他の修正プログラムと機能強化
### <a name="ltp-results"></a>LTP の結果:
成功したテストの数:709 </br>
非パッシング (失敗、スキップされたなど) の数:255 </br>
[LTP テストの実行ログ](https://github.com/Microsoft/CommandLine-Documentation/tree/live/LTP_Results/15007)<br/>
<br/>
## <a name="build-15002"></a>ビルド15002
ビルド15002の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2017/01/09/announcing-windows-10-insider-preview-build-15002-pc/)を参照してください。<br/>
### <a name="known-issue"></a>既知の問題
2つの既知の問題:
- コンソールが一部の Ctrl + <key>入力を認識しないという既知のバグがあります。 これには、通常の "c" キーの押下として機能する ctrl + c コマンドが含まれます。
- 回避策:代替キーを Ctrl + C にマップします。 たとえば、ctrl + K を Ctrl + C キーにマップするに`stty intr \^k`は、次のようにします。 このマッピングはターミナル単位で行われ、bash が起動されるたびに実行される必要があります。 ユーザーは、オプションを調べて、`.bashrc`
- WSL が実行されている間、システムスレッドは CPU コアの 100% を消費します。 根本原因は、内部的に解決されています。
### <a name="fixed"></a>固定
- すべての bash セッションは、同じアクセス許可レベルで作成する必要があります。 別のレベルでセッションを開始しようとすると、ブロックされます。 つまり、管理者コンソールと管理者以外のコンソールを同時に実行することはできません。 (GH #626)
<br/>
- 次の NETLINK_ROUTE メッセージを実装した (Windows 管理者が必要)
- RTM_NEWADDR (サポート`ip addr add`)
- RTM_NEWROUTE (サポート`ip route add`)
- RTM_DELADDR (サポート`ip addr del`)
- RTM_DELROUTE (サポート`ip route del`)
- 更新するパッケージのスケジュールされたタスクは、従量制課金接続では実行されなくなります (GH #1371)
- パイプがスタックした場合のエラーを修正します。 bash-c "ls-alR/" |bash-c "cat" (GH #1214)
- 実装された TCP_KEEPCNT socket オプション (GH #843)
- IP_MTU_DISCOVER INET socket オプション (GH #720、717、170、69) を実装しています
- Nt パス参照を使用して init から NT バイナリを実行する従来の機能を削除しました。 (GH #1325)
- グループまたはその他の読み取りアクセスを許可するように更新モードを修正する (0644) (GH #1321)
- 実装された/proc/sys/kernel/random/uuid (GH #1092)
- プロセスの開始時刻が2432年 (GH #974) と表示されたエラーを修正しました
- 既定の用語環境変数を xterm-256 色に切り替えました (GH #1446)
- プロセスフォーク中にコミットが計算される方法を変更しました。 (GH #1286)
- /Proc/sys/vm/overcommit_memory. の実装 (GH #1286)
- 実装された/proc/net/route ファイル (GH #69)
- ショートカット名が正しくローカライズされていないエラーを修正しました (GH #696)
- プログラムヘッダーの検証に誤りのある elf 解析ロジックを修正した場合は、PATH_MAX 未満である必要があります。 (GH #1048)
- Procfs、sysfs、cgroupfs、および binfmtfs (GH #1378) の statfs コールバックを実装します。
- 閉じることのできない AptPackageIndexUpdate ウィンドウを修正しました (GH #1184、GH #1193 で説明)
- ASLR パーソナリティ ADDR_NO_RANDOMIZE のサポートを追加しました。 (GH #1148、1128)
- AV 中に適切な gdb スタックトレースを実現するための PTRACE_GETSIGINFO、SIGSEGV が改善されました (GH #875)
- Elf の解析は、パッチ elf バイナリでは失敗します。 (GH #471)
- /Etc/resolv.conf に反映された VPN DNS (GH #416、1350)
- より信頼性の高いデータ転送のための TCP close の機能強化。 (GH #610、616、1025、1335)
- 開いているファイルが多すぎる場合 (EMFILE)、適切なエラーコードを返すようになりました。 (GH #1126、2090)
- Windows 監査ログで、プロセス作成の監査でイメージ名が報告されるようになりました。
- Bash ウィンドウ内から bash を起動すると、正常に失敗する
- 相互運用機能が LxFs で作業ディレクトリにアクセスできないときにエラーメッセージが追加されました (例: .bashrc)
- WSL で Windows パスが切り捨てられた問題を修正しました
- その他の修正プログラムと機能強化
### <a name="ltp-results"></a>LTP の結果:
成功したテストの数:690 </br>
非パッシング (失敗、スキップされたなど) の数:274 </br>
[LTP テストの実行ログ](https://github.com/Microsoft/CommandLine-Documentation/tree/live/LTP_Results/15002)<br/>
<br/>
### <a name="syscall-support"></a>Syscall のサポート
次に示すのは、WSL でいくつかの実装を持つ新しいまたは強化された syscall の一覧です。 この一覧の syscall は、少なくとも1つのシナリオでサポートされていますが、現時点では一部のパラメーターがサポートされていない可能性があります。
`shmctl`<br/>
`shmget`<br/>
`shmdt`<br/>
`shmat`<br/>
<br/>
## <a name="build-14986"></a>ビルド14986
ビルド14986の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2016/12/07/announcing-windows-10-insider-preview-build-14986-pc/)を参照してください。<br/>
### <a name="fixed"></a>固定
- Netlink および Pty Ioctl を使用したバグチェックの修正
- カーネルのバージョンが Xenial との一貫性のために 4.4.0-43 を報告するようになりました
- "Nul:" にリダイレクトされたときに Bash が起動するようになりました (GH #1259)
- Procfs (GH #967) でスレッド Id が正しくレポートされるようになりました
- IN_UNMOUNT |IN_Q_OVERFLOW |IN_IGNORED |IN_ISDIR フラグが inotify_add_watch () でサポートされるようになりました (GH #1280)
- Timer_create と関連するシステムコールを実装します。 これにより、GHC サポート (GH #307) が可能になります。
- Ping によって 0.000 m の時間 (GH #1296) が返された問題を修正しました。
- 開いているファイルが多すぎる場合は、正しいエラーコードを返します。
- WSL の Netlink 要求が、インターフェイスのハードウェアアドレスが32バイト (Teredo インターフェイスなど) の場合は EINVAL で失敗する問題を修正した。
- Linux の "ip" ユーティリティには、WSL が32バイトのハードウェアアドレスを報告した場合にクラッシュするバグが含まれていることに注意してください。 これは、WSL ではなく、"ip" のバグです。 "Ip" ユーティリティは、ハードウェアアドレスの印刷に使用される文字列バッファーの長さをハードコーディングします。また、32バイトのハードウェアアドレスを出力するには、バッファーが小さすぎます。
- その他の修正プログラムと機能強化
### <a name="ltp-results"></a>LTP の結果:
成功したテストの数:669 </br>
非パッシング (失敗、スキップされたなど) の数:258 </br>
[LTP テストの実行ログ](https://github.com/Microsoft/CommandLine-Documentation/tree/live/LTP_Results/14986)<br/>
<br/>
### <a name="syscall-support"></a>Syscall のサポート
次に示すのは、WSL でいくつかの実装を持つ新しいまたは強化された syscall の一覧です。 この一覧の syscall は、少なくとも1つのシナリオでサポートされていますが、現時点では一部のパラメーターがサポートされていない可能性があります。
`timer_create`<br/>
`timer_delete`<br/>
`timer_gettime`<br/>
`timer_settime`<br/>
<br/>
## <a name="build-14971"></a>ビルド14971
ビルド14971の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2016/11/17/announcing-windows-10-insider-preview-build-14971-for-pc/)を参照してください。<br/>
### <a name="fixed"></a>固定
- Windows Subsystem for Linux では、コントロールを超える状況により、このビルドには更新プログラムがありません。 定期的にスケジュールされた更新は、次回のリリースで再開されます。
### <a name="ltp-results"></a>LTP の結果:
14965から変更されていません </br>
成功したテストの数:664 </br>
非パッシング (失敗、スキップされたなど) の数:263 </br>
[LTP テストの実行ログ](https://github.com/Microsoft/CommandLine-Documentation/tree/live/LTP_Results/14965)<br/>
<br/>
## <a name="build-14965"></a>ビルド14965
ビルド14965の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2016/11/09/announcing-windows-10-insider-preview-build-14965-for-mobile-and-pc/)を参照してください。<br/>
### <a name="fixed"></a>固定
- Netlink sockets NETLINK_ROUTE protocol の RTM_GETLINK および RTM_GETADDR (GH #468) のサポート
- ネットワーク列挙に対する ifconfig および ip コマンドを有効にします
- 詳細については、 [Wsl ネットワークに関するブログ記事](https://blogs.msdn.microsoft.com/wsl/2016/11/08/225/)を参照してください。
- /sbin がユーザーのパスに既定で含まれるようになりました。
- NT ユーザーパスが既定で WSL パスに追加されました (つまり、Linux パスに System32 を追加せずに notepad.exe を入力できるようになりました)
- /Proc/sys/kernel/cap_last_cap のサポートを追加しました
- 現在の作業ディレクトリに ansi 以外の文字が含まれている場合、WSL から NT バイナリを起動できるようになりました (GH #1254)
- 切断された unix ストリームソケットでのシャットダウンを許可します。
- PR_GET_PDEATHSIG のサポートを追加しました。
- CLONE_PARENT のサポートを追加しました
- パイプがスタックした場合のエラーを修正します。 bash-c "ls-alR/" |bash-c "cat" (GH #1214)
- 現在のターミナルに接続するための要求を処理します。
- /Proc/<pid>/oom_score_adj を書き込み可能としてマークします。
- /Fs フォルダーを追加します。
- sched_setaffinity は、関係ビットマスクの数を返す必要があります
- インタープリターパスの長さが64文字未満であることを誤って想定している ELF 検証ロジックを修正します。 (GH #743)
- 開いているファイル記述子は、コンソールウィンドウを開いたままにすることができます (GH #1187)
- 名前の変更 () がターゲット名の末尾のスラッシュで失敗した Fixeed エラー (GH #1008)
- /Proc/net/dev ファイルを実装する
- タイマー精度による 0.000 ms ping を修正します。
- 実装された/proc/self/environ (GH #730)
- その他のバグ修正と機能強化
### <a name="ltp-results"></a>LTP の結果:
成功したテストの数:664 </br>
非パッシング (失敗、スキップされたなど) の数:263 </br>
[LTP テストの実行ログ](https://github.com/Microsoft/CommandLine-Documentation/tree/live/LTP_Results/14965)<br/>
<br/>
## <a name="build-14959"></a>ビルド14959
ビルド14959の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2016/11/03/announcing-windows-10-insider-preview-build-14959-for-mobile-and-pc/#iI82GufJxMF3POU1.97)を参照してください。<br/>
### <a name="fixed"></a>固定
- Windows の Pico Process 通知が改善されました。 [Wsl ブログ](https://blogs.msdn.microsoft.com/wsl/2016/11/01/wsl-antivirus-and-firewall-compatibility/)に記載されている追加情報。
- Windows の相互運用性による安定性の向上
- エンタープライズデータ保護 (EDP) が有効になっている場合に bash を起動したときのエラー0x80070057 を修正しました
- その他のバグ修正と機能強化
### <a name="ltp-results"></a>LTP の結果:
成功したテストの数:665 </br>
非パッシング (失敗、スキップされたなど) の数:263 </br>
[LTP テストの実行ログ](https://github.com/Microsoft/CommandLine-Documentation/tree/live/LTP_Results/14959)<br/>
<br/>
## <a name="build-14955"></a>ビルド14955
ビルド14955の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2016/10/25/announcing-windows-10-insider-preview-build-14955-for-mobile-and-pc/#guGXQzKVFrZIDUYR.97)を参照してください。<br/>
### <a name="fixed"></a>固定
- Windows Subsystem for Linux では、コントロールを超える状況により、このビルドには更新プログラムがありません。 定期的にスケジュールされた更新は、次回のリリースで再開されます。
### <a name="ltp-results"></a>LTP の結果:
成功したテストの数:665 </br>
非パッシング (失敗、スキップされたなど) の数:263 </br>
[LTP テストの実行ログ](https://github.com/Microsoft/CommandLine-Documentation/tree/live/LTP_Results/14955)<br/>
<br/>
## <a name="build-14951"></a>ビルド14951
ビルド14951の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2016/10/19/announcing-windows-10-insider-preview-build-14951-for-mobile-and-pc/)を参照してください。<br/>
### <a name="new-feature-windows--ubuntu-interoperability"></a>新機能:Windows/Ubuntu の相互運用性
Windows バイナリを WSL コマンドラインから直接呼び出すことができるようになりました。 これにより、ユーザーは Windows 環境とシステムを、不可能な方法で操作できるようになります。 簡単な例として、ユーザーが次のコマンドを実行できるようになりました。
```
$ export PATH=$PATH:/mnt/c/Windows/System32
$ notepad.exe
$ ipconfig.exe | grep IPv4 | cut -d: -f2
$ ls -la | findstr.exe foo.txt
$ cmd.exe /c dir
```
詳細については、以下を参照してください。
- [相互運用のための WSL チームブログ](https://blogs.msdn.microsoft.com/wsl/2016/10/19/windows-and-ubuntu-interoperability/)<br/>
- [MSDN Interop のドキュメント](https://msdn.microsoft.com/en-us/commandline/wsl/interop)<br/>
### <a name="fixed"></a>固定
- Ubuntu 16.04 (Xenial) が、すべての新しい WSL インスタンスにインストールされるようになりました。 既存の 14.04 (Trusty) インスタンスを持つユーザーは自動的にアップグレードされません。
- インストール中に設定されたロケールが表示されるようになりました
- WSL プロセスをファイルにリダイレクトする場合のバグを含むターミナルの機能強化
- コンソールの有効期間は、bash の有効期間に関連付けられている必要があります
- コンソールウィンドウのサイズは、バッファーサイズではなく表示サイズを使用する必要があります
- その他のバグ修正と機能強化
### <a name="ltp-results"></a>LTP の結果:
成功したテストの数:665 </br>
非パッシング (失敗、スキップされたなど) の数:263 </br>
[LTP テストの実行ログ](https://github.com/Microsoft/CommandLine-Documentation/tree/live/LTP_Results/14951)<br/>
<br/>
## <a name="build-14946"></a>ビルド14946
ビルド14946の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2016/10/13/announcing-windows-10-insider-preview-build-14946-for-pc-and-mobile/#xj8GdVooEqo4H7H7.97)を参照してください。<br/>
### <a name="fixed"></a>固定
- スペースまたは引用符を含む NT ユーザー名を持つユーザーの WSL ユーザーアカウントを作成できない問題を修正しています。
- ディレクトリのリンク数が stat で0を返すように、VolFs と DrvFs を変更します。
- IPV6_MULTICAST_HOPS socket オプションをサポートします。
- Tty ごとに1つのコンソール i/o ループに制限します。 例: 次のコマンドを実行できます。
- bash-c "echo data" |bash-c "ssh [email protected] " cat > foo .txt ""
- /proc/cpuinfo のタブでスペースを置換する (GH #1115)
- Mountinfo に DrvFs が、マウントされた Windows ボリュームと一致する名前で表示されるようになりました。
- /home と/root が mountinfo に正しい名前で表示されるようになりました
- その他のバグ修正と機能強化
### <a name="ltp-results"></a>LTP の結果:
成功したテストの数:665 </br>
非パッシング (失敗、スキップされたなど) の数:263 </br>
[LTP テストの実行ログ](https://github.com/Microsoft/CommandLine-Documentation/tree/live/LTP_Results/14946)<br/>
<br/>
## <a name="build-14942"></a>ビルド14942
ビルド14942の一般的な Windows 情報については、 [windows のブログ](https://aka.ms/onefourninefourtwoooooo)を参照してください。<br/>
### <a name="fixed"></a>固定
- SSH をブロックしていた "NOEXECUTE MEMORY の実行を試行しました" というネットワーククラッシュを含む、いくつかのバグを解決しました。
- DrvFs の Windows アプリケーションから生成された通知の inotifiy サポートがになりました。
- TCP_KEEPIDLE と TCP_KEEPINTVL を mongod 用に実装します。 (GH #695)
- Pivot_root システムコールを実装する
- SO_DONTROUTE のソケットの実装オプション
- その他のバグ修正と機能強化
### <a name="ltp-results"></a>LTP の結果:
成功したテストの数:665 </br>
非パッシング (失敗、スキップされたなど) の数:263 </br>
[LTP テストの実行ログ](https://github.com/Microsoft/CommandLine-Documentation/tree/live/LTP_Results/14942)<br/>
### <a name="syscall-support"></a>Syscall のサポート
次に示すのは、WSL でいくつかの実装を持つ新しいまたは強化された syscall の一覧です。 この一覧の syscall は、少なくとも1つのシナリオでサポートされていますが、現時点では一部のパラメーターがサポートされていない可能性があります。
`pivot_root`<br/>
<br/>
## <a name="build-14936"></a>ビルド14936
ビルド14936の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2016/09/28/announcing-windows-10-insider-preview-build-14936-for-pc/)を参照してください。<br/>
注:WSL は、今後のリリースで Ubuntu 14.04 (Trusty) ではなく、Ubuntu バージョン 16.04 (Xenial) をインストールします。 この変更は、新しいインスタンスをインストールする場合に適用されます (lxrun/install または bash の最初の実行)。 Trusty を使用した既存のインスタンスは自動的にはアップグレードされません。 ユーザーは、Trusty コマンドを使用して、自分のイメージを Xenial にアップグレードできます。
### <a name="known-issue"></a>既知の問題
WSL でいくつかのソケット実装に問題が発生しています。 "NOEXECUTE MEMORY の実行を試行しました" というエラーが発生すると、バグチェックはクラッシュします。 この問題の最も一般的な取り組みは、ssh を使用する場合のクラッシュです。 根本原因は内部ビルドで固定されており、最も早い機会に Insider にプッシュされます。
### <a name="fixed"></a>固定
- Chroot システム呼び出しを実装します。
- ~~DrvFs の Windows アプリケーションから生成された通知のサポートを含む~~inotify の機能強化
- 量現時点では利用できない Windows アプリケーションからの変更については、Inotify のサポートが提供されています。
- IPV6 へのソケットバインド:<port n> : で IPV6_V6ONLY (GH #68、#157、#393、#460、#674、#740、#982、#996) がサポートされるようになりました。
- Waitid systemcall が実装された WNOWAIT 動作 (GH #638)
- IP ソケットオプション IP_HDRINCL と IP_TTL のサポート
- 長さ0の読み取り () はすぐに返される必要があります (GH #975)
- Tar ファイルに NULL 終端文字を含まないファイル名とファイル名プレフィックスを正しく処理します。
- /dev/null の epoll サポート
- 更新プログラムのタイムソースを修正する
- Bash-c がファイルにリダイレクトできるようになりました
- その他のバグ修正と機能強化
### <a name="ltp-results"></a>LTP の結果:
成功したテストの数:664 </br>
非パッシング (失敗、スキップされたなど) の数:264 </br>
[LTP テストの実行ログ](https://github.com/Microsoft/CommandLine-Documentation/tree/live/LTP_Results/14936)<br/>
### <a name="syscall-support"></a>Syscall のサポート
次に示すのは、WSL でいくつかの実装を持つ新しいまたは強化された syscall の一覧です。 この一覧の syscall は、少なくとも1つのシナリオでサポートされていますが、現時点では一部のパラメーターがサポートされていない可能性があります。
`chroot`<br/>
<br/>
## <a name="build-14931"></a>ビルド14931
ビルド14931の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2016/09/21/announcing-windows-10-insider-preview-build-14931-for-pc/)を参照してください。<br/>
### <a name="fixed"></a>固定
- Windows Subsystem for Linux では、コントロールを超える状況により、このビルドには更新プログラムがありません。 定期的にスケジュールされた更新は、次のリリースで再開されます。
<br/>
## <a name="build-14926"></a>ビルド14926
ビルド14926の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2016/09/14/announcing-windows-10-insider-preview-build-14926-for-pc-and-mobile/)を参照してください。<br/>
### <a name="fixed"></a>固定
- 管理者特権を持たないコンソールで Ping が機能するようになりました。
- Ping6 がサポートされるようになりました。管理者特権も必要ありません
- WSL によって変更されたファイルの Inotify サポート。 (GH #216)
- サポートされているフラグ:
- inotify_init1:LX_O_CLOEXEC, LX_O_NONBLOCK
- inotify_add_watch イベント:LX_IN_ACCESS, LX_IN_MODIFY, LX_IN_ATTRIB, LX_IN_CLOSE_WRITE, LX_IN_CLOSE_NOWRITE, LX_IN_OPEN, LX_IN_MOVED_FROM, LX_IN_MOVED_TO, LX_IN_CREATE, LX_IN_DELETE, LX_IN_DELETE_SELF, LX_IN_MOVE_SELF
- inotify_add_watch 属性 (i):LX_IN_DONT_FOLLOW, LX_IN_EXCL_UNLINK, LX_IN_MASK_ADD, LX_IN_ONESHOT, LX_IN_ONLYDIR
- 出力の読み取り:LX_IN_ISDIR, LX_IN_IGNORED
- 既知の問題:Windows アプリケーションからファイルを変更してもイベントが生成されない
- Unix ソケットで SCM_CREDENTIALS がサポートされるようになりました。
### <a name="ltp-results"></a>LTP の結果:
成功したテストの数:651 </br>
非パッシング (失敗、スキップされたなど) の数:258 </br>
[LTP テストの実行ログ](https://github.com/Microsoft/CommandLine-Documentation/tree/live/LTP_Results/14926)<br/>
<br/>
## <a name="build-14915"></a>ビルド14915
ビルド14915の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2016/08/31/announcing-windows-10-insider-preview-build-14915-for-pc-and-mobile)を参照してください。<br/>
### <a name="fixed"></a>固定
- Unix データグラムソケットの socketpair (GH #262)
- SO_REUSEADDR の Unix ソケットサポート
- SO_BROADCAST の UNIX ソケットサポート (GH #568)
- SOCK_SEQPACKET の Unix ソケットサポート (GH #758、#546)
- Unix データグラムソケットの送信、受信、およびシャットダウンのサポートの追加
- 非固定アドレスに対する mmap パラメーターの検証が無効なため、バグチェックを修正します。 (GH #847)
- ターミナル状態の中断/再開のサポート
- 画面ユーティリティのブロックを解除する TIOCPKT ioctl のサポート (GH #774)
- 既知の問題:関数キーが動作していません
- TimerFd の競合を修正しました。これにより、解放されたメンバー ' ReaderReady ' が Lxp Timerfdworkspace Erroutine (GH #814) によってアクセスされる可能性があります
- Futex、投票、clock_nanosleep の再起動可能なシステムコールのサポートを有効にする
- バインドマウントサポートを追加しました
- マウントの名前空間のサポートの共有を解除する
- 既知の問題:現在の作業ディレクトリを使用し`unshare(CLONE_NEWNS)`て新しいマウント名前空間を作成すると、引き続き古い名前空間が参照されます。
- 追加の機能強化とバグ修正
<br/>
## <a name="build-14905"></a>ビルド14905
ビルド14905の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2016/08/17/announcing-windows-10-insider-preview-build-14905-for-pc-mobile/)を参照してください。<br/>
### <a name="fixed"></a>固定
- 再開可能なシステムコールがサポートされるようになりました (GH #349、GH #520)
- 現在操作中のディレクトリへのシンボリックリンク (GH #650)
- /Dev/random の RNDGETENTCNT ioctl を実装します。
- /Proc/[pid]/マウント,/proc/[pid]/mountinfo および/proc/[pid]/mountstats ファイルを実装します。
- その他のバグ修正と機能強化
</br>
## <a name="build-14901"></a>ビルド14901
Windows 10 記念日更新リリースの最初の Insider ビルド。
ビルド14901の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2016/08/11/announcing-windows-10-insider-preview-build-14901-for-pc/)を参照してください。<br/>
### <a name="fixed"></a>固定
- 末尾のスラッシュの問題を修正した
- などのコマンドが動作するようになりました`$ mv a/c/ a/b/`
- Ubuntu ロケールを Windows ロケールに設定するかどうかを確認するメッセージが表示されるようになりました
- Ns フォルダーの Procfs サポート
- Tmpfs、procfs、および sysfs ファイルシステムのマウントとマウント解除を追加しました
- Mknod [at] 32 ビット ABI 署名の修正
- Unix ソケットをディスパッチモデルに移行
- Setsockopt を使用して、INET ソケットの recv バッファーサイズを設定する必要があります
- MSG_CMSG_CLOEXEC unix socket receive message フラグを実装する
- Linux プロセス stdin/stdout パイプのリダイレクト (GH #2)
- CMD で bash-c コマンドのパイプを使用できるようにします。 例: > dir |bash-c "grep foo"
- Bash を複数のシステムにインストールできるようになりました (GH #538、#358)
- 既定の INET ソケットバッファーサイズは、既定の Ubuntu セットアップのものと一致している必要があります。
- Xattr syscall を listxattr に揃える
- SIOCGIFCONF から有効な IPv4 アドレスを持つインターフェイスのみを返す
- Ptrace によって挿入されるときのシグナルの既定の動作を修正する
- /proc/sys/vm/min_free_kbytes を実装する
- Sigreturn でコンテキストを復元するときにマシンコンテキストレジスタの値を使用する
- これにより、一部のユーザーに対して java と javac がハングした問題が解決されます。
- /Proc/sys/kernel/hostname を実装する
### <a name="syscall-support"></a>Syscall のサポート
次に示すのは、WSL でいくつかの実装を持つ新しいまたは強化された syscall の一覧です。 この一覧の syscall は、少なくとも1つのシナリオでサポートされていますが、現時点では一部のパラメーターがサポートされていない可能性があります。
`waitid`<br/>
`epoll_pwait`<br/>
<br/>
## <a name="build-14388-to-windows-10-anniversary-update"></a>14388を Windows 10 記念日更新プログラムにビルドする
ビルド14388の一般的な Windows 情報については、 [windows のブログ](https://aka.ms/14388wip)を参照してください。 <br/>
### <a name="fixed"></a>固定
- 8/2 で Windows 10 記念日更新プログラムを準備するための修正プログラム
- 記念日の更新に関する詳細については、こちらの[ブログ](https://blogs.msdn.microsoft.com/wsl/)を参照してください。
<br/>
## <a name="build-14376"></a>ビルド14376
ビルド14376の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2016/06/28/announcing-windows-10-insider-preview-build-14376-for-pc-and-mobile/)を参照してください。 <br/>
### <a name="fixed"></a>固定
- Apt-get がハングするインスタンスをいくつか削除しました (GH #493)
- 空のマウントが正しく処理されない問題を修正しました
- Ramdisks が正しくマウントされていない問題を修正しました
- Unix ソケットの受け入れをサポートフラグに変更する (partial GH #451)
- 一般的なネットワーク関連のブルースクリーンを修正した
- /Proc/[pid]/task (GH #523) にアクセスするときにブルースクリーンを修正
- 一部の pty シナリオ (GH #488、#504) の高 CPU 使用率を修正した
- その他のバグ修正と機能強化
<br/>
## <a name="build-14371"></a>ビルド14371
ビルド14371の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2016/06/22/announcing-windows-10-insider-preview-build-14371-for-pc/)を参照してください。 <br/>
### <a name="fixed"></a>固定
- Ptrace を使用するときに SIGCHLD と wait () を使用してタイミングレースを修正しました
- パスの末尾に/(GH #432) がある場合の動作を修正しました
- 子へのハンドルが開いているため、名前の変更とリンク解除に失敗する問題を修正した
- その他のバグ修正と機能強化
<br/>
## <a name="build-14366"></a>ビルド14366
ビルド14366の一般的な Windows 情報については、 [windows のブログ](https://blogs.windows.com/windowsexperience/2016/06/14/announcing-windows-10-insider-preview-build-14366-mobile-build-14364/)を参照してください。 <br/>
### <a name="fixed"></a>固定
- シンボリックリンクを使用したファイル作成時の修正
- Python 用 listxattr (GH 385) が追加されました
- その他のバグ修正と機能強化
### <a name="syscall-support"></a>Syscall のサポート
- 次に示すのは、WSL でいくつかの実装を持つ新しいまたは強化された syscall の一覧です。 この一覧の syscall は、少なくとも1つのシナリオでサポートされていますが、現時点では一部のパラメーターがサポートされていない可能性があります。
`listxattr`<br/>
<br/>
## <a name="build-14361"></a>ビルド14361
ビルド14361の一般的な Windows 情報については、 [windows のブログ](https://aka.ms/wip14361)を参照してください。 <br/>
### <a name="fixed"></a>固定
- Windows 上で Bash on Ubuntu を実行すると、DrvFs の大文字と小文字が区別されるようになりました。
- ユーザーは .txt と大文字小文字を区別することができます。/Mnt/c ドライブ上の TXT
- 大文字小文字の区別は、Bash on Ubuntu on Windows でのみサポートされています。 Bash の外部では、ファイルが正しく報告されますが、予期しない動作が Windows からのファイルの操作で発生する場合があります。
- 各ボリュームのルート (つまり/mnt/c) は大文字と小文字が区別されません。
- これらのファイルを Windows で処理する方法の詳細については、[こちら](https://support.microsoft.com/en-us/kb/100625)を参照してください。
- Pty/tty のサポートが大幅に強化されました。 TMUX のようなアプリケーションがサポートされるようになりました (GH #40)
- ユーザーアカウントが常に作成されていないインストールの問題を修正しました
- 非常に長い引数リストを許可する最適化されたコマンドライン arg 構造体。 (GH #153)
- DrvFs からファイルを削除することができるようになりました。
- 切断時にターミナルがハングする一部のインスタンスを修正した (GH #43)
- chmod と chown が tty デバイスで動作するようになりました
- 0\.0.0.0 および:: as localhost (GH #388) への接続を許可します
- Sendmsg/recvmsg が > 1 (partial GH #376) の IO ベクターの長さを処理するようになりました
- ユーザーは、自動生成された hosts ファイル (GH #398) をオプトアウトできるようになりました。
- インストール中に Linux ロケールを NT ロケールに自動的に一致させる (GH #11)
- /Proc/sys/vm/swappiness ファイル (GH #306) が追加されました。
- strace が正常に終了するようになりました
- /Proc/self/fd を使用してパイプを再度開くことを許可する (GH #222)
- DrvFs から%LOCALAPPDATA%\lxss の下にあるディレクトリを非表示にする (GH #270)
- Bash の処理の強化 ~. などのコマンド"bash ~-c %.ls"(GH #467) をサポートするようになりました
- ソケットはシャットダウン中に使用可能な epoll read を通知するようになりました (GH #271)
- lxrun/uninstall では、ファイルとフォルダーを削除する機能が改善されています。
- 修正された ps-f (GH #246)
- XEmacs (GH #481) などの x11 アプリのサポートの強化
- 既定の Ubuntu 設定に一致するように初期スレッドスタックサイズを更新し、get_rlimit syscall (GH #172、#258) にサイズを正しく報告しました
- Pico プロセスのイメージ名 (監査のためなど) のレポートが改善されました。
- Df コマンドの/proc/mountinfo を実装します。
- 子名のシンボリックリンクエラーコードを修正した。 そして。
- 追加の改善バグ修正と改善
### <a name="syscall-support"></a>Syscall のサポート
次に示すのは、WSL でいくつかの実装を持つ新しいまたは強化された syscall の一覧です。 この一覧の syscall は、少なくとも1つのシナリオでサポートされていますが、現時点では一部のパラメーターがサポートされていない可能性があります。
`GETTIMER`<br/>
`MKNODAT`<br/>
`RENAMEAT`<br/>
`SENDFILE`<br/>
`SENDFILE64`<br/>
`SYNC_FILE_RANGE`<br/>
<br/>
## <a name="build-14352"></a>ビルド14352
ビルド14352の一般的な Windows 情報については、 [windows のブログ](https://aka.ms/wip14352)を参照してください。<br/>
### <a name="fixed"></a>固定
- 大きなファイルが正しくダウンロードまたは作成されなかった問題を修正しました。 これにより、npm とその他のシナリオ (GH #3、GH #313) のブロックが解除されます。
- ソケットがハングする一部のインスタンスを削除しました
- いくつかの ptrace エラーを修正しました
- 255文字を超えるファイル名を許可する WSL の問題を修正しました
- 英語以外の文字のサポートの強化
- 現在の Windows タイムゾーンデータを追加し、既定として設定する
- 各マウントポイントの一意のデバイス id (jre fix – GH #49)
- "." を含むパスの問題を修正してください。 および "."
- 追加された Fifo サポート (GH #71)
- ネイティブ Ubuntu 形式に一致するように resolv.conf の形式を更新しました
- 一部の procfs クリーンアップ
- 管理者コンソールの ping を有効にする (GH #18)
### <a name="syscall-support"></a>Syscall のサポート
次に示すのは、WSL でいくつかの実装を持つ新しいまたは強化された syscall の一覧です。 この一覧の syscall は、少なくとも1つのシナリオでサポートされていますが、現時点では一部のパラメーターがサポートされていない可能性があります。
`FALLOCATE`<br/>
`EXECVE`<br/>
`LGETXATTR`<br/>
`FGETXATTR`<br/>
<br/>
## <a name="build-14342"></a>ビルド14342
ビルド14342の一般的な Windows 情報については、 [Windows ブログ](https://aka.ms/wip14342)を参照してください。 <br/>
VolFs とドライブ Fs に関する情報は、 [Wsl ブログ](https://blogs.msdn.microsoft.com/wsl)を参照してください。 <br/>
### <a name="fixed"></a>固定
- Windows ユーザーのユーザー名に Unicode 文字が含まれている場合のインストールの問題を修正しました
- FAQ の apt get 更新 udev の回避策は、最初の実行時に既定で提供されるようになりました。
- ドライブ fs (/mnt/<drive>) ディレクトリでのシンボリックリンクの有効化
- シンボリックリンクがドライブ Fs と VolFs 間で機能するようになりました
- 解析の問題、アドレス指定された最上位レベル パス: %.ls/期待どおりに、正しく動作/。
- npm がドライブ Fs にインストールされ、-g オプションが機能するようになりました。
- PHP サーバーの起動を妨げている問題を修正した
- ネイティブ Ubuntu に近い $PATH など、既定の環境値が更新されました
- Apt パッケージキャッシュを更新するための週単位のメンテナンスタスクが Windows に追加されました
- ELF ヘッダーの検証に関する問題を修正しました。 WSL ですべての Melkor オプションがサポートされるようになりました
- Zsh シェルが機能しています
- プリコンパイル済みのジャンプバイナリがサポートされるようになりました
- Bash の初回実行時のプロンプトが正しくローカライズされるようになりました
- /proc/meminfo が正しい情報を返すようになりました
- VFS でソケットがサポートされるようになりました
- /dev が tempfs としてマウントされるようになりました
- Fifo がサポートされるようになりました
- /Proc/cpuinfo で、マルチコアシステムが正しく表示されるようになりました。
- 初回実行時の追加の改善とエラーメッセージのダウンロード
- Syscall の機能強化とバグ修正。 以下のサポートされている syscall 一覧。
- その他のバグ修正と機能強化
### <a name="known-issues"></a>既知の問題
- '. ' を解決できません 場合によっては、ドライブ Fs で正しく動作します。
### <a name="syscall-support"></a>Syscall のサポート
次に示すのは、WSL でいくつかの実装を持つ新しいまたは強化された syscall の一覧です。 この一覧の syscall は、少なくとも1つのシナリオでサポートされていますが、現時点では一部のパラメーターがサポートされていない可能性があります。
`FCHOWNAT`<br/>
`GETEUID`<br/>
`GETGID`<br/>
`GETRESUID`<br/>
`GETXATTR`<br/>
`PTRACE`<br/>
`SETGID`<br/>
`SETGROUPS`<br/>
`SETHOSTNAME`<br/>
`SETXATTR`<br/>
<br/>
## <a name="build-14332"></a>ビルド14332
ビルド14332の一般的な Windows 情報については、 [windows のブログ](https://aka.ms/wip14332)を参照してください。 <br/>
### <a name="fixed"></a>固定
- DNS エントリの優先順位を含む resolv.conf の生成の向上
- /Mnt ドライブと/mnt 以外のドライブの間でファイルとディレクトリを移動する場合の問題
- シンボリックリンクを使用して Tar ファイルを作成できるようになりました。
- インスタンスの作成時に既定の/run/lock ディレクトリが追加されました
- /Dev/null を更新して適切な stat 情報を返す
- 初回実行時のダウンロード時の追加エラー
- Syscall の機能強化とバグ修正。 以下のサポートされている syscall 一覧。
- 追加の改善バグ修正と改善
### <a name="syscall-support"></a>Syscall のサポート
以下は、WSL で実装がいくつかある新しい syscall です。 この一覧の syscall は、少なくとも1つのシナリオでサポートされていますが、現時点では一部のパラメーターがサポートされていない可能性があります。
`READLINKAT`<br/>
<br/>
## <a name="build-14328"></a>ビルド14328
ビルド14332の一般的な Windows 情報については、 [windows のブログ](https://aka.ms/wip14328)を参照してください。 <br/>
### <a name="new-features"></a>新機能
* Linux ユーザーがサポートされるようになりました。 Bash on Ubuntu on Windows をインストールすると、Linux ユーザーの作成を求めるメッセージが表示されます。 詳細については、「」を参照してください。 https://aka.ms/wslusers
* ホスト名が Windows コンピューター名に設定されました@localhost
* ビルド14328の詳細については、次を参照してください。 https://aka.ms/wip14328
### <a name="fixed"></a>固定
* 非/mnt/<drive>ファイルのシンボリックリンクの機能強化
* npm のインストールが機能するようになりました
* jdk/jre[はここ](https://xubuntugeek.blogspot.com/2012/09/how-to-install-oracle-jdk-7-manually-in.html)に記載されている手順に従ってインストールできるようになりました。
* 既知の問題: symlink は Windows マウントでは機能しません。 機能は、後のビルドで使用できるようになります
* 上部と htop が表示されるようになりました
* 一部のインストールエラーに関する追加のエラーメッセージ
* Syscall の機能強化とバグ修正。 以下のサポートされている syscall 一覧。
* 追加の改善バグ修正と改善
### <a name="syscall-support"></a>Syscall のサポート
WSL で実装がいくつかある syscall の一覧を次に示します。 この一覧の syscall は、少なくとも1つのシナリオでサポートされていますが、現時点では一部のパラメーターがサポートされていない可能性があります。
`ACCEPT`<br/>
`ACCEPT4`<br/>
`ACCESS`<br/>
`ALARM`<br/>
`ARCH_PRCTL`<br/>
`BIND`<br/>
`BRK`<br/>
`CAPGET`<br/>
`CAPSET`<br/>
`CHDIR`<br/>
`CHMOD`<br/>
`CHOWN`<br/>
`CLOCK_GETRES`<br/>
`CLOCK_GETTIME`<br/>
`CLOCK_NANOSLEEP`<br/>
`CLONE`<br/>
`CLOSE`<br/>
`CONNECT`<br/>
`CREAT`<br/>
`DUP`<br/>
`DUP2`<br/>
`DUP3`<br/>
`EPOLL_CREATE`<br/>
`EPOLL_CREATE1`<br/>
`EPOLL_CTL`<br/>
`EPOLL_WAIT`<br/>
`EVENTFD`<br/>
`EVENTFD2`<br/>
`EXECVE`<br/>
`EXIT`<br/>
`EXIT_GROUP`<br/>
`FACCESSAT`<br/>
`FADVISE64`<br/>
`FCHDIR`<br/>
`FCHMOD`<br/>
`FCHMODAT`<br/>
`FCHOWN`<br/>
`FCHOWNAT`<br/>
`FCNTL64`<br/>
`FDATASYNC`<br/>
`FLOCK`<br/>
`FORK`<br/>
`FSETXATTR`<br/>
`FSTAT64`<br/>
`FSTATAT64`<br/>
`FSTATFS64`<br/>
`FSYNC`<br/>
`FTRUNCATE`<br/>
`FTRUNCATE64`<br/>
`FUTEX`<br/>
`GETCPU`<br/>
`GETCWD`<br/>
`GETDENTS`<br/>
`GETDENTS64`<br/>
`GETEGID`<br/>
`GETEGID16`<br/>
`GETEUID`<br/>
`GETEUID16`<br/>
`GETGID`<br/>
`GETGID16`<br/>
`GETGROUPS`<br/>
`GETPEERNAME`<br/>
`GETPGID`<br/>
`GETPGRP`<br/>
`GETPID`<br/>
`GETPPID`<br/>
`GETPRIORITY`<br/>
`GETRESGID`<br/>
`GETRESGID16`<br/>
`GETRESUID`<br/>
`GETRESUID16`<br/>
`GETRLIMIT`<br/>
`GETRUSAGE`<br/>
`GETSID`<br/>
`GETSOCKNAME`<br/>
`GETSOCKOPT`<br/>
`GETTID`<br/>
`GETTIMEOFDAY`<br/>
`GETUID`<br/>
`GETUID16`<br/>
`GETXATTR`<br/>
`GET_ROBUST_LIST`<br/>
`GET_THREAD_AREA`<br/>
`INOTIFY_ADD_WATCH`<br/>
`INOTIFY_INIT`<br/>
`INOTIFY_RM_WATCH`<br/>
`IOCTL`<br/>
`IOPRIO_GET`<br/>
`IOPRIO_SET`<br/>
`KEYCTL`<br/>
`KILL`<br/>
`LCHOWN`<br/>
`LINK`<br/>
`LINKAT`<br/>
`LISTEN`<br/>
`LLSEEK`<br/>
`LSEEK`<br/>
`LSTAT64`<br/>
`MADVISE`<br/>
`MKDIR`<br/>
`MKDIRAT`<br/>
`MKNOD`<br/>
`MLOCK`<br/>
`MMAP`<br/>
`MMAP2`<br/>
`MOUNT`<br/>
`MPROTECT`<br/>
`MREMAP`<br/>
`MSYNC`<br/>
`MUNLOCK`<br/>
`MUNMAP`<br/>
`NANOSLEEP`<br/>
`NEWUNAME`<br/>
`OPEN`<br/>
`OPENAT`<br/>
`PAUSE`<br/>
`PERF_EVENT_OPEN`<br/>
`PERSONALITY`<br/>
`PIPE`<br/>
`PIPE2`<br/>
`POLL`<br/>
`PPOLL`<br/>
`PRCTL`<br/>
`PREAD64`<br/>
`PROCESS_VM_READV`<br/>
`PROCESS_VM_WRITEV`<br/>
`PSELECT6`<br/>
`PTRACE`<br/>
`PWRITE64`<br/>
`READ`<br/>
`READLINK`<br/>
`READV`<br/>
`REBOOT`<br/>
`RECV`<br/>
`RECVFROM`<br/>
`RECVMSG`<br/>
`RENAME`<br/>
`RMDIR`<br/>
`RT_SIGACTION`<br/>
`RT_SIGPENDING`<br/>
`RT_SIGPROCMASK`<br/>
`RT_SIGRETURN`<br/>
`RT_SIGSUSPEND`<br/>
`RT_SIGTIMEDWAIT`<br/>
`SCHED_GETAFFINITY`<br/>
`SCHED_GETPARAM`<br/>
`SCHED_GETSCHEDULER`<br/>
`SCHED_GET_PRIORITY_MAX`<br/>
`SCHED_GET_PRIORITY_MIN`<br/>
`SCHED_SETAFFINITY`<br/>
`SCHED_SETPARAM`<br/>
`SCHED_SETSCHEDULER`<br/>
`SCHED_YIELD`<br/>
`SELECT`<br/>
`SEND`<br/>
`SENDMMSG`<br/>
`SENDMSG`<br/>
`SENDTO`<br/>
`SETDOMAINNAME`<br/>
`SETGID`<br/>
`SETGROUPS`<br/>
`SETHOSTNAME`<br/>
`SETITIMER`<br/>
`SETPGID`<br/>
`SETPRIORITY`<br/>
`SETREGID`<br/>
`SETRESGID`<br/>
`SETRESUID`<br/>
`SETREUID`<br/>
`SETRLIMIT`<br/>
`SETSID`<br/>
`SETSOCKOPT`<br/>
`SETTIMEOFDAY`<br/>
`SETUID`<br/>
`SETXATTR`<br/>
`SET_ROBUST_LIST`<br/>
`SET_THREAD_AREA`<br/>
`SET_TID_ADDRESS`<br/>
`SHUTDOWN`<br/>
`SIGACTION`<br/>
`SIGALTSTACK`<br/>
`SIGPENDING`<br/>
`SIGPROCMASK`<br/>
`SIGRETURN`<br/>
`SIGSUSPEND`<br/>
`SOCKET`<br/>
`SOCKETCALL`<br/>
`SOCKETPAIR`<br/>
`SPLICE`<br/>
`STAT64`<br/>
`STATFS64`<br/>
`SYMLINK`<br/>
`SYMLINKAT`<br/>
`SYNC`<br/>
`SYSINFO`<br/>
`TEE`<br/>
`TGKILL`<br/>
`TIME`<br/>
`TIMERFD_CREATE`<br/>
`TIMERFD_GETTIME`<br/>
`TIMERFD_SETTIME`<br/>
`TIMES`<br/>
`TKILL`<br/>
`TRUNCATE`<br/>
`TRUNCATE64`<br/>
`UMASK`<br/>
`UMOUNT`<br/>
`UMOUNT2`<br/>
`UNLINK`<br/>
`UNLINKAT`<br/>
`UNSHARE`<br/>
`UTIME`<br/>
`UTIMENSAT`<br/>
`UTIMES`<br/>
`VFORK`<br/>
`WAIT4`<br/>
`WAITPID`<br/>
`WRITE`<br/>
`WRITEV`<br/>
| 38.840405 | 329 | 0.760052 | yue_Hant | 0.713774 |
c925975783b7b3d742c1d2d8cc52afdd5f4a80d1 | 40,034 | md | Markdown | README.md | NXPmicro/mcu-boot-utility | 7a3dae30006157ad0e6acc247b5d7668f789a171 | [
"Apache-2.0"
] | 2 | 2021-10-08T08:06:49.000Z | 2021-12-15T09:59:11.000Z | README.md | NXPmicro/mcu-boot-utility | 7a3dae30006157ad0e6acc247b5d7668f789a171 | [
"Apache-2.0"
] | null | null | null | README.md | NXPmicro/mcu-boot-utility | 7a3dae30006157ad0e6acc247b5d7668f789a171 | [
"Apache-2.0"
] | 1 | 2021-12-23T08:35:05.000Z | 2021-12-23T08:35:05.000Z | # NXP MCU Boot Utility
### 1 Overview
#### 1.1 Introduction
NXP-MCUBootUtility is a GUI tool specially designed for NXP MCU secure boot. Its features correspond to the BootROM function in NXP MCU. Currently, it mainly supports i.MXRT, LPC, Kinetis series MCU chips, Compared to NXP official security enablement toolset (OpenSSL, CST, sdphost, blhost, elftosb, BD, MfgTool2), NXP-MCUBootUtility is a real one-stop tool, a tool that includes all the features of NXP's official security enablement toolset, and what's more, it supports full graphical user interface operation. With NXP-MCUBootUtility, you can easily get started with NXP MCU secure boot.
The main features of NXP-MCUBootUtility include：
-------------------------------------------------------
> * Support both UART and USB-HID serial downloader modes
> * Support various user application image file formats (elf/axf/srec/hex/bin)
> * Can validate the range and applicability of user application image
> * Support for converting bare image into bootable image
> * Support for loading bootable image into external boot devices
> * Support common boot device memory operation (Flash Programmer)
-------------------------------------------------------
> * Support i.MXRT1011, i.MXRT1015, i.MXRT1021, i.MXRT1024 SIP, i.MXRT105x, i.MXRT106x, i.MXRT1064 SIP, i.MXRT116x, i.MXRT117x
> * User image file can be either bare image file or bootable image file
> * Support for converting bare image into .sb file for MfgTool and RT-Flash
> * Support for loading bootable image into FlexSPI NOR boot device
> * Support for loading bootable image into FlexSPI NAND boot device
> * Support for loading bootable image into SEMC NAND boot device
> * Support for loading bootable image into SEMC NOR boot device
> * Support for loading bootable image into uSDHC SD/eMMC boot device
> * Support for loading bootable image into LPSPI NOR/EEPROM recovery boot device
> * Support DCD which can help load image to SDRAM
> * Support development boot case (Unsigned)
> * Support HAB encryption secure boot case (Signed only, Signed and Encrypted)
> * Can back up certificate with time stamp
> * Support BEE encryption secure boot case (SNVS Key, User Keys)
> * Support OTFAD encryption secure boot case (SNVS Key, User Keys)
> * Support common eFuse memory operation (eFuse Programmer)
> * Support common FlexRAM memory operation (ISP Boot)
> * Support for reading back and marking bootable image(NFCB/DBBT/FDCB/EKIB/EPRDB/IVT/Boot Data/DCD/Image/CSF/DEK KeyBlob) from boot device
-------------------------------------------------------
> * Support i.MXRT5xx, i.MXRT6xx
> * Support for loading bootable image into FlexSPI/QuadSPI NOR boot device
> * Support for loading bootable image into Flexcomm SPI NOR recovery boot device
> * Support development boot case (Unsigned, CRC)
> * Support common OTP memory operation (OTP Programmer)
> * Support common SRAM memory operation (ISP Boot)
> * Support for reading back and marking bootable image(OTFAD KeyBlob/FDCB/KeyStore/Image) from boot device
-------------------------------------------------------
> * Support LPC550x/S0x, LPC551x/S1x, LPC552x/S2x, LPC55S69
> * Support for loading bootable image into C040HD Flash
> * Support development boot case (Unsigned)
-------------------------------------------------------
> * Support 2nd gen Kinetis Series (With BootROM, eg: MKL03Z, MK8xF)
> * Support for loading bootable image into FTFx Flash
> * Support development boot case (Unsigned)
#### 1.2 Download
NXP-MCUBootUtility is developed in Python, and it is open source. The development environment is Python 2.7.15 (32bit), wxPython 4.0.3, pySerial 3.4, pywinusb 0.4.2, bincopy 15.0.0, PyAudio 0.2.11, PyInstaller 3.3.1 (or higher).
NXP-MCUBootUtility is packaged by PyInstaller, all Python dependencies have been packaged into an executable file (\NXP-MCUBootUtility\bin\NXP-MCUBootUtility.exe), so if you do not want to develop NXP-MCUBootUtility for new feature, there is no need to install any Python software or related libraries.
> Note1: For complete package with final .exe file, you need to download mcu-boot-utility-x.x.x-with-exe.zip from https://github.com/NXPmicro/mcu-boot-utility/releases
> Note2: Before using NXP-MCUBootUtility, you need to download [HAB Code Signing Tool](https://www.nxp.com/webapp/sps/download/license.jsp?colCode=IMX_CST_TOOL&appType=file2&location=null&DOWNLOAD_ID=null&lang_cd=en) from NXP website，upzip it and put it in the \NXP-MCUBootUtility\tools\cst\ directory, then modify the code to enable AES function and rebuild \NXP-MCUBootUtility\tools\cst\mingw32\bin\cst.exe, or HAB related encryption function can not be used properly。See more details in [《The step-by-step guide to rebuild cst.exe for HAB encryption》](https://www.cnblogs.com/henjay724/p/10189593.html)
> Note3: Before using NXP-MCUBootUtility, you need to rebuild the source in \NXP-MCUBootUtility\tools\image_enc\code directory to generate image_enc.exe and put it in \NXP-MCUBootUtility\tools\image_enc\win directory, or BEE/OTFAD related encryption function can not be used properly。See more details in [《The step-by-step guide to build image_enc.exe for BEE/OTFAD encryption》](https://www.cnblogs.com/henjay724/p/10189602.html)
> Note4: The NXP-MCUBootUtility.exe in the source code package is packaged in the Windows 10 x64 environment and has only been tested in this environment. If it cannot be used directly for system environment reasons, you need to install [Python2.7.15 x86 version ](https://www.python.org/ftp/python/2.7.15/python-2.7.15.msi)(Confirm that the directory "\Python27\" and "\Python27\Scripts\" are in the system environment variable path after the installation is completed), then click on "do_setup_by_pip.bat" in the "\NXP-MCUBootUtility\env\" directory to install the Python library on which NXP-MCUBootUtility depends. Finally, click "do_pack_by_pyinstaller.bat" to regenerate the NXP-MCUBootUtility.exe.
> Note5: You must use Python2 x86 version, because NXP-MCUBootUtility uses the pywinusb library, which cannot be packaged by PyInstaller in Python2 x64 version. The pywinusb author has no plan to fix the problem.
> Note6: You cannot make any frequency adjustments in the encrypted code area, if your code includes calling of BOARD_BootClockRUN or any other frequency adjustment function, you should allocate those functions and the function called inside into non encrypted code area.
#### 1.3 Installation
NXP-MCUBootUtility is a pure green free installation tool. After downloading the source code package, double-click "\NXP-MCUBootUtility\bin\NXP-MCUBootUtility.exe" to use it. No additional software is required.
Before the NXP-MCUBootUtility.exe graphical interface is displayed, a console window will pop up first. The console will work along with the NXP-MCUBootUtility.exe graphical interface. The console is mainly for the purpose of showing error information of NXP-MCUBootUtility.exe. At present, NXP-MCUBootUtility is still in development stage, and the console will be removed when the NXP-MCUBootUtility is fully validated.
#### 1.4 Contents
The NXP-MCUBootUtility software directory is organized as follows:
```text
\NXP-MCUBootUtility
\apps --Place example source image files
\bin --Place NXP-MCUBootUtility.exe and user configuration file
\doc --Place reference documents related to NXP MCU Boot
\env --Place scripts to install the NXP-MCUBootUtility development environment and to do package
\gen --Place temporary files generated during the use of NXP-MCUBootUtility
\bd_file -- Generated BD files based on configuration
\bee_crypto -- Generated BEE encryption related files
\bootable_image -- Generated bootable image file
\dcd_file -- Generated DCD data file
\fdcb_file -- Generated FDCB file based on configuration
\hab_cert -- Generated HAB signature related files
\hab_crypto -- Generated HAB encryption related files
\json_file -- Generated JSON files based on configuration
\log_file -- Saved software operation log
\otfad_crypto -- Generated OTFAD encryption related files
\sb_image -- Generated .sb file
\user_file -- Temporary files
\gui --Place NXP-MCUBootUtility development UI build project file
\img --Place the image to be loaded during the use of NXP-MCUBootUtility
\src --Place all Python source code files for developing NXP-MCUBootUtility
\tools --Place all external programs to be called during the use of NXP-MCUBootUtility
\blhost -- Host command line tool to communicate with Flashloader
\cst -- HAB encryption command line tool
\elftosb -- Command line tool to generate bootable image
\ide_utils -- Command line tool to convert image format
\image_enc -- BEE encryption command line tool
\imgutil -- Command line tool to generate DCD data
\openssl -- Standard tool to generate certificates and keys
\sdphost -- Host command line tool to communicate with ROM
```
#### 1.5 Interface
The following figure shows the main interface of the NXP-MCUBootUtility tool. The interface consists of six parts. The functions of each part are as follows:
> * [Menu Bar]: Functional menu bar, providing general software settings.
> * [Target Setup]: Target device setting bar, providing MCU Device and Boot Device configuration options.
> * [Port Setup]: In the serial interface setting field, select the interface for connecting to the MCU Device.
> * [Device Status]: The target device status information field is used to display the status of the target device after connecting to the target device.
> * [Secure Boot Action]: Secure boot main interface, providing all operations for encrypting the target device.
> * [Log Info]: Operation log bar, recording software operation log
### 2 Preparation
There are two main preparations before using the NXP-MCUBootUtility tool: 1. Prepare the i.MXRT hardware board and the serial download cable (USB/UART). 2. Prepare the source image file for downloading into Flash.
For serial download line connections, you need to check the System Boot chapter of the i.MXRT Reference Manual to ensure that the connected UART/USB pins are specified by the BootROM.
Regarding the source image file preparation, the NXP-MCUBootUtility tool can recognize the images of the five common formats (elf/axf/srec/hex/bin). Note that the source image can be either bare image or bootable image.
Take the NXP official SDK as an example to further explain the generation of the source image file, register and log in to the NXP official website, go to the [MCUXpresso SDK Builder](https://mcuxpresso.nxp.com/en/select) page, select the appropriate MCU chip and IDE (take RT1060 chip, IAR IDE as an example) and click Download SDK to get SDK_2.4.0_EVK-MIMXRT1060.zip.
Use IAR to open the \boards\evkmimxrt1060\demo_apps\led_blinky\iar\led_blinky.eww sample application in the SDK package:
The led_blinky application actually contains three projects (ram/flexspi_nor/sdram), which correspond to three different linker files (.icf). The image generated by the ram project is the so-called Non-XIP image, and the image generated by the flexspi_nor project is so-called XIP image.
By default, the image files generated by the ram project and the flexspi_nor project cannot be used directly by NXP-MCUBootUtility, and some minor changes are required.
You need to modify the linker file for the ram project as follows: (It is recommended to put the link interrupt vector table start from 0x3000, and reserve some memory space in front of the interrupt vector table for placing the file header required for i.MXRT boot).
```text
define symbol m_interrupts_start = 0x00003000; // 0x00000000
define symbol m_interrupts_end = 0x000033FF; // 0x000003FF
define symbol m_text_start = 0x00003400; // 0x00000400
define symbol m_text_end = 0x0001FFFF;
define symbol m_data_start = 0x20000000;
define symbol m_data_end = 0x2001FFFF;
define symbol m_data2_start = 0x20200000;
define symbol m_data2_end = 0x202BFFFF;
```
You need to modify the Defined symbols in the project configuration options for the flexspi_nor project as follows: (Set XIP_BOOT_HEADER_ENABLE to 0, It is no need to generate an image containing the i.MXRT boot headers; Keep XIP_BOOT_HEADER_ENABLE as 1, The generated image will contain i.MXRT boot headers).
If you just want to quickly verify the NXP-MCUBootUtility tool, all the led_blinky application image files of NXP's official i.MXRT evaluation boards are stored by default in the NXP-MCUBootUtility\apps folder.
### 3 Basic Usage
#### 3.1 Setting the target device
When using NXP-MCUBootUtility, you need to configure the target device. The target device includes MCU Device and Boot Device. Taking the NXP official development board EVK-MIMXRT1060 as an example, the main chip of the development board is i.MXRT1062DVL6A, so [MCU Device] should be set to i.MXRT106x. Taking the most commonly used FlexSPI NOR boot as an example, [Boot Device] is set to FLEXSPI NOR, and the corresponding external memory chip on the development board is IS25WP064AJBLE, which is a commonly used four-wire QSPI NOR Flash, which needs to be further configured. Click the [Boot Device Configuration] button to pop up the following new configuration page:
In the pop-up FlexSPI NOR Device Configuration page, you can see many options describing the Multi-IO SPI NOR Flash feature, such as Device Type, Query Pads, etc. These options need to be set correctly to aligned with the external Flash in the development board.
In addition, there is an option called [Use Typical Device Model] on the page. The NXP-MCUBootUtility pre-defines some commonly used Multi-IO SPI NOR Flash model models, if the external storage chip on the development board happens to be in pre-defined model list, you can select the corresponding model directly in the [Use Typical Device Model] without having to configure it one by one in the Nor Option.
The IS25WP064AJBLE chip on the EVK-MIMXRT1060 development board belongs to the ISSI-IS25LP064A category, so we only need to select ISSI - IS25LP064A in [Use Typical Device Model] and click [Ok] to complete the setting of the target device.
#### 3.2 Connecting target devices
After setting up the target device, the next step is to connect the target device. Taking the USB-HID interface as an example, supply power to the EVK-MIMXRT1060 board, and connect the PC to the J9 port with USB Cable. If everything is going well, you can find new HID device (vid=0x1fc9, pid=0x0135) named HID-compliant vendor-defined device is enumerated. If the HID device is not found, please check the board SW7 DIP switch to set Boot Mode to 2'b01(Serial Downloader mode).
After confirming the existence of the HID device, select USB-HID in [Port Setup], and then directly click the [Connect to ROM] button. The NXP-MCUBootUtility will automatically complete the whole process of connecting the target device (using sdphost to connect to the ROM to obtain some MCU internal register information. Using sdphost to load Flashloader and jump to it, using blhost to connect to Flashloader, get some eFuse information, use blhost to configure boot device and get boot device meomry information), this process takes about 5s, if the target device is connected properly, you can see the indicator LED turns blue, and the [Connect to ROM] button label changes to [Reset Device]. If the target device fails to connect, the indicator LED will turn red and the [Connect to ROM] button label will change to [Reconnect].
After the target device is successfully connected, you can see some useful device status information in the target device status information bar, such as the UUID value of the MCU chip, the HAB status, the important Fuse value related to boot, and the Page/Sector/Block size of the Boot Device.
#### 3.3 Secure Encryption Boot
At first, you should make sure Tools/Generate .sb file option in menu bar is set as "No", after the target device is successfully connected, the core secure boot operation can be started. Before the secure boot operation is started, Let's see the secure boot main interface:
> * [Image Generation Sequence]: The image generation window is used to encrypt the source image then generate a bootable image that can be placed in the Boot Device.
> * [Image Loading Sequence]: The image download window is used to download the generated bootable image into the Boot Device, and burn the corresponding Fuse value in the MCU (various Key, HAB settings, etc.)
> * [eFuse Operation Utility]: The eFuse readback and burning window allows the user to burn custom values into the Fuse Region.
> * [Boot Device Memory]: The image readback and annotation display window is used to read back the downloaded Bootable image data from the Boot Device and mark the data components.
> * [Secure Boot Type]: Select the secure boot mode, select the desired secure mode (do not enable security, HAB signature only, HAB signature & encryption, BEE encryption).
> * [All-In-One Action]: One-stop operation, Actions in the image generation window and the image loading window are automatically executed in sequence.
##### 3.3.1 Mode 1: No security measures are enabled
The first mode is the simplest mode, that is, no security measures are initiated, and it is generally used in the product development and debugging phase.
Select "DEV Unsigned Image Boot" in [Secure Boot Type], and then click the [Browse] button to select a raw image file (using the bare image file generated by the IDE, do not need to include any additional headers required for i.MXRT boot in image file**<u>) H</u>**ead), click the [All-In-One Action] button to complete the bootable image generation and download operations.
> Note: If 'Auto-detect image format' option is selected, the source file format is automatically recognized based on the file extension. However, for the axf file generated by MCUXpresso or GCC, it needs to be set to ".out(axf) from MCUXpresso/GCC ARM".
Step4 and Step5 in the above figure are not must-have operations. They are only used to confirm whether the [All-In-One Action] button operation is successful, especially the Step5 operation. You can check the Bootable image composition picture displayed in the image download window.
All operations are correct. Set the Boot Mode to 2'b10(Internal Boot mode) via SW7 DIP switch on the board. The rest remains all 0s. You can see that the unsigned image is executed normally after power-on.
##### 3.3.2 Mode 2: Enable HAB signature authentication
The second mode is the primary security mode, that is, only the image is signed and authenticated, and is generally used in applications where product security is high. The signature authentication is mainly to verify the validity of the image and detect whether the image is abnormally damaged or tampered. If the image is found to be illegal, the MCU will not start executing the image.
Select "HAB Signed Image Boot" in [Secure Boot Type], then enter serial (must be 8 digits) and key_pass (any length character) and click the [Advanced Cert Settings] button to configure all the signature authentication parameters (Refer to [NXP CST Tool](https://www.nxp.com/webapp/sps/download/license.jsp?colCode=IMX_CST_TOOL&appType=file2&location=null&DOWNLOAD_ID=null&lang_cd=en)). Then click the [Browse] button to select an original image file, and finally click the [All-In-One Action] button to complete all operations of bootable image generation and download.
Step5 in the above figure is mainly used to confirm two points: First, whether the HAB status is Closed (Fuse 0x460[31:0] bit1 is 1'b1); Second, whether SRKH is correctly programmed (Fuse 0x580 - 0x5f0, a total of 256bit, that is, the sha-256 algorithm), SRKH is the hash value of the Public RSA Key in the CSF data in the final bootable image, and is used to verify whether the Public RSA Key is legal.
All operations are correct. Set the Boot Mode to 2'b10(Internal Boot mode) via SW7 DIP switch on the board. The rest will remain all 0. When the power is turned back on, you can see that the HAB signed image is executed normally.
Because the HAB status of the MCU chip is already Closed and the SRKH has been burned and cannot be changed, the unauthenticated image cannot be run normally. In the software directory \NXP-MCUBootUtility\tools\cst\crts, the Private RSA Key file is stored in the folder. Please save it properly. If it is lost, the new image will not be properly signed and the HAB authentication will fail to be executed.
##### 3.3.3 Mode 3: Enable HAB signature authentication and HAB encryption
The third mode is the intermediate security mode, which is to sign and authenticate the image and HAB level encryption, which is generally used in applications where product security is very high. The signature authentication is mainly to verify the validity of the image, and the encryption can protect the image from being illegally stolen in the external Boot Device. Because the external cryptographic data is stored in the external Boot Device, even if it is illegally acquired, it cannot be easily Cracked, and the encryption is bound to the MCU chip, because the HAB encryption process uses the only Master Secret Key in the MCU's internal SNVS module.
Select "HAB Encrypted Image Boot" in [Secure Boot Type], and then configure all the parameters for signature authentication (if there is a certificate in the local, you can use it without configuration, the software will try to reuse), and then click the [Browse] button to select a raw image file. Finally, click the [All-In-One Action] button to complete all operations of bootable image generation and download.
After the Step6 operation in the above figure, you can see that the image downloaded into Boot Deivce is indeed cipher text. In fact, HAB encryption only supports encrypted image area, and other areas (such as FDCB, IVT, Boot Data, etc.) are not encrypted.
All operations are correct. Set the Boot Mode to 2'b10(Internal Boot mode) via SW7 DIP switch on the board. The rest will remain all 0s. After power-on, you can see that the HAB signed encrypted image is executed normally.
You may be curious, since the image is HAB encrypted, where is the password? How to set it up? In fact, the image encryption operation is completely encapsulated by the HAB encryption tool. The AES-128 algorithm is used by HAB encryption, the corresponding 128-bit AES-128 Key is not user-defined, but the HAB encryption tool automatically generates it randomly, and each AES-128 Key generated by every encryption operation is different, even if you have not replaced the original image. The AES-128 Key is saved in the \NXP-MCUBootUtility\gen\hab_crypto\hab_dek.bin file.
From the above diagram, the Bootable image shown in the image download window shows that compared to the HAB single-signature method, the final part of the Bootable image is a DEK KeyBlob component. This DEK KeyBlob is the key data in hab_dek.bin is dynamically encrypted by the Master Secret Key in the internal SNVS module of the MCU chip. Because the Master Secret Key is the unique in each chip, the DEK KeyBlob is also unique. This is key to protect the image from being illegally stolen.
Why does HAB encryption not support XIP Image? In fact, a simple analysis of the boot principle makes it clear that Image stores ciphertext in the Boot Device. This part of the ciphertext must be decrypted into plaintext by HAB before it can be executed by the CPU. Therefore, it must be specified different storage spaces to store the image plaintext, Non-XIP Image naturally specifies that the plaintext should be stored in the chip's internal SRAM or external SDRAM, and the XIP Image is directly executed in the Boot Device. The plaintext address and the ciphertext address are the same. Therefore, HAB encryption does not support XIP Image.
##### 3.3.4 Mode 4: Enable single-engine BEE encryption (unique SNVS Key)
The fourth mode is the advanced security mode, that is, single-engine BEE-level encryption of image with a unique SNVS Key, which is generally used in applications where product security is extremely high. The main difference between BEE encryption and HAB encryption is that the main body of the decryption operation is different. There are three main differences:
> * HAB encryption is performed by HAB in BootROM to decrypt all encrypted images into plaintext and then execute (static decryption). BEE encryption is performed by the BEE module inside the MCU chip to decrypt the encrypted image. (If it is XIP Image, then it belogns to Dynamic decryption; if it is Non-XIP image, then it is similar to HAB Encryption).
> * HAB encryption only supports Non-XIP Image (not limited to Boot Device), while BEE encryption only supports Image in FlexSPI NOR (Both XIP and Non-XIP image are supported).
> * The HAB encryption area cannot be specified (the default is all user image area), and the BEE encrypted area can be specified by the user.
Select "BEE Encrypted Image Boot" in [Secure Boot Type], and then configure all the parameters for signature authentication (if there is a certificate in the local, you can use it without configuration, the software will try to reuse), and then click the [Browse] button to select an original image file (must be XIP image in FlexSPI NOR), select "Fixed Otpmk(SNVS) Key" in [Key Storage Region], then click the [Advanced Key Settings] button to configure all BEE encryption parameters, and finally click the [All-In-One Action] button to complete the bootable image generation and download operations.
The Step6 operation in the above figure is mainly used to confirm one point: whether BEE_KEY0_SEL is set to From OTPMK[255:128] (bit 13 of Fuse 0x460[31:0], 12 is 2'b10). After Step6 operation, you can see that the Bootable image downloaded into Boot Deivce is all ciphertext from IVT. This example only enables one encryption area. Which areas are encrypted are specified in [Advanced Key Settings], and the maximum support is specified. 3 blocks of encryption.
It is necessary to introduce the following BEE parameter setting page using Fixed Otpmk (SNVS) Key encryption. Set the Region Count and specify the Region range, the default is 0 which means encrypted region is the entire image.
All operations are correct. Set Boot Mode to 2'b10(Internal Boot mode) via SW7 DIP switch on the board, and sets BT_CFG[1] to 1'b1 (Encrypted XIP is enabled). The rest remains all 0s. You can see that the BEE encrypted image is executed normally.
BEE encryption is more secure than HAB encryption, because HAB encryption can only be static decryption after all. When the HAB decryption is completed, all the image plaintext is stored in SRAM/SDRAM. If the hacker illegally accesses SRAM/SDRAM at this moment, it is possible to get all the plain text of the image(But don't worry, You can set JTAG access right for i.MXRT); and BEE encryption can be dynamic decryption, where the CPU will go to decrypt somewhere, there is no complete image plaintext at any time, the hacker can never get all the image plaintext.
##### 3.3.5 Mode 5: Enable dual-engine BEE encryption (user-defined Key)
The fifth mode is the top security mode, which uses a user-defined Key to perform dual-engine BEE-level encryption on the image. Similar to the fourth mode (single-engine) principle, it is generally used in applications where product security is extremely high. The specific differences between single-engine BEE encryption and dual-engine BEE encryption are as follows:
> * The only SNVS Key single-engine BEE encryption uses SNVS Key by default. The SNVS Key is pre-burned and cannot be changed. The user-defined Key dual-engine BEE encryption key is set by the user and needs to be manually burned in Fuse SW_GP2 and GP4 area.
> * Unique SNVS Key single-engine BEE encryption only enables BEE engine 0; user-defined Key dual-engine BEE encryption can enable both BEE engine 0 and engine 1. However, it should be noted that no matter how many BEE engines are enabled, the total number of encrypted areas is three.
> * The unique SNVS Key single-engine BEE encryption must be used with the HAB signature, because the SNVS Key can only be obtained in the state of HAB Closed; the user-defined Key dual-engine BEE encryption does not have to use the HAB signature.
Select "BEE Encrypted Image Boot" in [Secure Boot Type], click the [Browse] button to select an original image file (must be XIP image in FlexSPI NOR), select "Flexible User Keys" in [Key Storage Region], then click the [Advanced Key Settings] button to configure all BEE encryption parameters, and finally click the [All-In-One Action] button to complete the bootable image generation and download operations.
The Step6 operation in the above figure is mainly used to confirm two points: 1. Whether BEE_KEY0_SEL is set correctly (bits13, 12 of Fuse 0x460[31:0]) and whether BEE_KEY1_SEL is set correctly (bit 15 and 14 of Fuse 0x460[31:0]); Whether the user key is correctly programmed (SW_GP2: Fuse 0x690 - 0x6c0, GP4: Fuse 0x8c0 - 0x8f0).
It is necessary to introduce the BEE parameter setting page encrypted by Flexible User Keys as follows. Firstly, select the BEE engine to be activated. You can activate the BEE engine 0 separately, or activate the BEE engine 1 separately. Of course, you can activate the BEE engines(0/1) at the same time. This example activates both BEE engines 0 and 1. After the BEE engine is specified, the storage space of the Key used for encryption is further configured for the engine and the Key (128 bits) is required to manually input. Finally, you need to set the area for encryption protection. In this example, two areas are encrypted, which are 0x60001000 - 0x60001fff (protected by BEE engine 0) and 0x60003000 - 0x60003fff (protected by BEE engine 1).
To confirm that the image is encrypted by the specified area, you can open the unencrypted bootable image file under the \NXP-MCUBootUtility\gen\bootable_image\ folder and compare it with the contents of the image readback window.
All operations are correct. Set Boot Mode to 2'b10(Internal Boot mode) via SW7 DIP switch on the board, and sets BT_CFG[1] to 1'b1 (Encrypted XIP is enabled). The rest remains all 0s. You can see that the BEE encrypted image is executed normally.
NXP-MCUBootUtility burns the user-defined Key into the Fuse SW_GP2/GP4 area for the dual-engine BEE encryption, but the Fuse content of the area can be read back. If the hacker gets the Key, it is still possible to crack Image ciphertext in the external Boot Device. Is there a way to protect the Fuse SW_GP2/GP4 area? Of course, you can lock the specified Fuse area, you can set the Fuse area access rights (read protection, write protection, coverage protection), as detailed in a separate chapter. The NXP-MCUBootUtility tool directly locks the SW_GP2/GP4 area for security reasons.
Compared with single-engine BEE encryption, dual-engine BEE encryption doubles the difficulty from the perspective of cracking. After all, two different keys can be enabled to jointly protect the image from being illegally obtained.
##### 3.3.6 Mode 6: Enable single-level OTFAD encryption (unique SNVS Key)
The sixth mode is similar to the fourth mode, FlexSPI on-the-fly encryption module in early i.MXRT chip (eg i.MXRT105x) is BEE, it switches to OTFAD in subsequent i.MXRT chip (eg i.MXRT1011). OTFAD is enhanced than BEE.
##### 3.3.7 Mode 7: Enable dual-level OTFAD encryption (user-defined Key)
The seventh mode is the top security mode. The specific differences between dual-engine BEE encryption and dual-level OTFAD encryption are as follows:
> * BEE encryption can support 3 protection regions and 2 user keys; OTFAD can support 4 protection regions, each region can have its own user key, besidesm there is a global key used to protect user keys.
> * User keys used for BEE are stored in efuse directly; global key used for OTFAD can be protected by scramble algorithm.
Let's see the OTFAD flexible user key configuration:
kek is the global key, it is stored in eFuse. user keys are saved in OTFAD DEK KeyBlob, and KeyBlob is stored in NOR Flash, kek is used to protect KeyBlob.
#### 3.4 Generate .sb file
Set Tools/Generate .sb file option as "Yes" in menu bar, then click 【All-In-One Action】 button, A .sb file will be generated into \NXP-MCUBootUtility\gen\sb_image\ folder, this .sb file can be used for MfgTool or RT-Flash tool. Note that clicking 【All-In-One Action】 button will not really perform any boot command on MCU，it just record all boot commands in \NXP-MCUBootUtility\gen\bd_file\imx_application_sb_gen.bd file to generate final .sb file。
> Note1: There is one limitation in generating .sb file，you need to reconnect device every time you want ro generate new .sb file，click 【Reset device】 button to move back to initial state，then click 【Connect to ROM】 button.
> Note2: If there is necessary efuse operation in generated .sb file, tool will generate three .sb files in total. application_device.sb includes all operations(flash+efuse), application_device_flash.sb includes flash operations only, application_device_efuse.sb includes efuse operations only, it is flexible for production.
> Note3: For NOR Flash devices (FlexSPI NOR, LPSPI NOR), you can either connect or disconnect board to generate .sb file.
> Note4: [Scan], [Burn] buttons in eFuse Operation Utility window can also be used to generate .sb file which contains efuse operation only.
### 4 Advanced Usage
The NXP-MCUBootUtility is set to work in the Entry Mode by default. You can set it to Master Mode through the function menu bar Tools->Option. Some advanced functions are opened in the Master Mode, which is suitable for users who are very familiar with the NXP MCU chip and the Boot ROM.
#### 4.1 Step-by-step connection
In the Master Mode, you can uncheck the One Step option, so you can connect to the target device step by step. The main meaning of the single-step connection is that you can connect to the Flashloader to implement the eFuse operation without configuring the Boot Device.
#### 4.2 Dedicated eFuse Programmer
When NXP-MCUBootUtility is in Master Mode, you can see that all eFuse areas are open. You can burn the specified eFuse area at will. The eFuse operation is a bit-by-bit. It can only be written as 1 and when it has been burned to 1 and it cannot be changed. Therefore, the operation of eFuse requires special care.
In the previous chapter, the secure boot process, we will burn SRKH (0x580 - 0x5f0), SW_GP2 (0x690 - 0x6c0), GP4 (0x8c0 - 0x8f0), these areas can not be changed once burned, even we want these areas can't only be changed, it can not be read back.
From the above figure, eFuse 0x400 is the Locker of each Fuse function area. We can lock the SW_GP2, and GP4 areas by burning eFuse 0x400. So how do you burn it? In fact, it is very simple, fill in the value you want to burn directly in each eFuse box, click the [Burn] button.
For some mixed eFuse fields, you can also click the index button, then each efuse bits as below：
#### 4.3 Dedicated FlexRAM Programmer
In the Master Mode, you can click the [Read], [Write], [Execute] button to implement any read, write and execute operations of the FlexRAM, so that the NXP-MCUBootUtility tool can be used as a FlexRAM programmer.
#### 4.4 Universal Flash Programmer
In the Master Mode, you can click the [Read], [Erase], [Write] button to implement any read and write operations of the configured Flash, so that the NXP-MCUBootUtility tool can be used as a general-purpose Flash programmer.
#### 4.5 Update flashloader
NXP-MCUBootUtility mainly depends on i.MXRT ROM Flashloader and blhost, As Flashloader is often updated with SDK, so we may need to update flashloader for NXP-MCUBootUtility. it is easy to update flashloader, we need to build new flashloader from SDK (middleware/mcu-boot) and rename it to 'flashloader_user.srec' and then put it into /src/targets/MIMXRTxxxx/.
| 126.290221 | 838 | 0.763401 | eng_Latn | 0.993642 |
c9260d80fe076204607b909260ac776b1cb87b7a | 175 | md | Markdown | pages/etherCIS/troubleshooting.md | tony-shannon/test4Docs | ae687bd8cb3e0c291d73fa8366a9046267de47b1 | [
"MIT",
"BSD-3-Clause"
] | null | null | null | pages/etherCIS/troubleshooting.md | tony-shannon/test4Docs | ae687bd8cb3e0c291d73fa8366a9046267de47b1 | [
"MIT",
"BSD-3-Clause"
] | null | null | null | pages/etherCIS/troubleshooting.md | tony-shannon/test4Docs | ae687bd8cb3e0c291d73fa8366a9046267de47b1 | [
"MIT",
"BSD-3-Clause"
] | 1 | 2017-05-22T13:21:48.000Z | 2017-05-22T13:21:48.000Z | ---
title: Troubleshooting EtherCIS
keywords: EtherCIS
sidebar: EtherCIS_sidebar
permalink: troubleshooting.html
folder: etherCIS
---
## TroubleShooting EtherCIS
Try this;
| 13.461538 | 31 | 0.794286 | kor_Hang | 0.493577 |
c9267dba303643488e8fdeeec2541fc4892342c4 | 19,369 | md | Markdown | Assets/Plugins/backtrace-unity-2.0.5-alpha1/README.md | vlussenburg/RedRunner | 0ba4a4a2bb611897dc836d2468263fd790573d14 | [
"MIT"
] | null | null | null | Assets/Plugins/backtrace-unity-2.0.5-alpha1/README.md | vlussenburg/RedRunner | 0ba4a4a2bb611897dc836d2468263fd790573d14 | [
"MIT"
] | null | null | null | Assets/Plugins/backtrace-unity-2.0.5-alpha1/README.md | vlussenburg/RedRunner | 0ba4a4a2bb611897dc836d2468263fd790573d14 | [
"MIT"
] | 1 | 2020-05-07T10:02:35.000Z | 2020-05-07T10:02:35.000Z | # Backtrace Unity support
[Backtrace](http://backtrace.io/)'s integration with unity games allows customers to capture and report handled and unhandled Unity exceptions to their Backtrace instance, instantly offering the ability to prioritize and debug software errors.
[github release]: (https://github.com/backtrace-labs/backtrace-labs/)
## Usage
```csharp
//Read from manager BacktraceClient instance
var backtraceClient = GameObject.Find("_Manager").GetComponent<BacktraceClient>();
try{
//throw exception here
}
catch(Exception exception){
var report = new BacktraceReport(exception);
backtraceClient.Send(report);
}
```
# Features Summary <a name="features-summary"></a>
- Light-weight Unity client that quickly submits crashed generated in Unity environment to your Backtrace dashboard
- Can include callstack, system metadata, custom metadata, custom attributes and file attachments if needed
- Supports a wide range of unity version and environments
- Supports .NET 4.5 Backend, IL2CPP and Mono environments
- Supports offline database for error report storage and re-submission in case of network outage
- Fully customizable and extendable event handlers
- Custom IDE integrations
# Prerequisites
- Unity environment 2017.4.x
- .NET 4.5 scripting runtime version
- Mono or IL2CPP scripting backend
# Setup <a name="installation"></a>
List of steps necessary to setup full Backtrace Unity integration.
## Installation guide
- Download the backtrace-unity zip file. Unzip it and keep the folder in a known location. It can be downloaded from https://github.com/backtrace-labs/backtrace-unity/releases
- Open your Unity project and ensure it is configured to build with .NET 4.5+ runtime and a mono or il2cpp backend.
- Copy the unzipped folder to your project's asset folder in the Windows File Explorer. The Unity editor will refresh and the Backtrace Plugin should become available in the editor.
## Integrating into your project
- Under the Assets Menu, there is now a Backtrace -> Configuration option. Choose that option (or Right click on empty space and select from the menu box) to have a Backtrace Configuration is generated in the Assets folder. You can drag and drop generated asset file into Backtrace Client configuration window.
- Next, select an object from the Scene Hierarchy to associate the Backtrace reporting client to. In the example below, we use the Manager object., Using the Inspector panel, click the Add Component button and search for the Backtrace Client object.
- Within the Backtrace Client panel, there is a Backtrace Configuration field. Drag and drop the Backtrace Configuration from the Assets folder to that field. More fields will appear for you to fill in to configure the Backtrace Client and Offline Database options.
- Provide valid Backtrace client configuration and start using library!
Watch this 1 minute silent video to see the Integration and Configuration in action. The first 20 seconds of the video shows the above Integrating steps, and the second part shows details of the below Client and Database Settings - https://player.vimeo.com/video/300051476
## Backtrace Client and Offline Database Settings
The following is a reference guide to the Backtrace Client fields:
- Server Address: This field is required to submit exceptions from your Unity project to your Backtrace instance. More information about how to retrieve this value for your instance is our docs at What is a submission URL and What is a submission token? NOTE: the backtrace-unity plugin will expect full URL with token to your Backtrace instance,
- Reports per minute: Limits the number of reports the client will send per minutes. If set to 0, there is no limit. If set to a higher value and the value is reached, the client will not send any reports until the next minute. Further, the BacktraceClient.Send/BacktraceClient.SendAsync method will return false.
- Destroy client on new scene load - Backtrace-client by default will be available on each scene. Once you initialize Backtrace integration, you can fetch Backtrace game object from every scene. In case if you don't want to have Backtrace-unity integration available by default in each scene, please set this value to true.
- Handle unhandled exceptions: Toggle this on or off to set the library to handle unhandled exceptions that are not captured by try-catch blocks.
- Game Object Depth Limit: Allows developer to filter number of game object childrens in Backtrace report.
- Ignore SSL validation: Unity by default will validate ssl certificates. By using this option you can avoid ssl certificates validation. However, if you don't need to ignore ssl validation, please set this option to false.
- Deduplication rules: Backtrace-unity plugin allows you to combine the same reports. By using deduplication rules, you can tell backtrace-unity plugin how we should merge reports.
- Enable Database: When this setting is toggled, the backtrace-unity plugin will configure an offline database that will store reports if they can't be submitted do to being offline or not finding a network. When toggled on, there are a number of Database settings to configure.
- Backtrace Database path: This is the path to directory where the Backtrace database will store reports on your game. NOTE: Backtrace database will remove all existing files on database start
- Create database directory toggle: If toggled, the library will create the offline database directory if the provided path doesn't exists,
- Auto Send Mode: When toggled on, the database will send automatically reports to Backtrace server based on the Retry Settings below. When toggled off, the developer will need to use the Flush method to attempt to send and clear. Recommend that this is toggled on.
- Maximum number of records: This is one of two limits you can impose for controlling the growth of the offline store. This setting is the maximum number of stored reports in database. If value is equal to zero, then limit not exists, When the limit is reached, the database will remove the oldest entries.
- Maximum database size: This is the second limit you can impose for controlling the growth of the offline store. This setting is the maximum database size in MB. If value is equal to zero, then size is unlimited, When the limit is reached, the database will remove the oldest entries.
- Retry interval: If the database is unable to send its record, this setting specifies how many seconds the library should wait between retries.
- Maximum retries: If the database is unable to send its record, this setting specifies the maximum number of retries before the system gives up.
- Retry order: This specifies in which order records are sent to the Backtrace server.
# API Overview
You can further configure your game to submit crashes by making further changes in the C# code for your game.
## Basic configuration
If you setup `Backtrace client` and `Backtrace database` configuration you can retrieve database and client instances by using `GameObject`. When you retrieve client instance you can start sending reports from try/catch block in your game!
```csharp
//Read from manager BacktraceClient instance
var backtraceClient = GameObject.Find("manager name").GetComponent<BacktraceClient>();
//Read from manager BacktraceClient instance
var database = GameObject.Find("manager name").GetComponent<BacktraceDatabase>();
try{
//throw exception here
}
catch(Exception exception){
var report = new BacktraceReport(exception);
backtraceClient.Send(report);
}
```
If you would like to change Backtrace client/database options, we recommend to change these values on the Unity UI via Backtrace Configuration file. However, if you would like to change these values dynamically, please use method `Refresh` to apply new configuration changes.
For example:
```csharp
//Read from manager BacktraceClient instance
var backtraceClient = GameObject.Find("manager name").GetComponent<BacktraceClient>();
//Change configuration value
backtraceClient.Configuration.DeduplicationStrategy = deduplicationStrategy;
//Refresh configuraiton
backtraceClient.Refresh();
```
## Sending an error report <a name="documentation-sending-report"></a>
`BacktraceClient.Send` method will send an error report to the Backtrace endpoint specified. There `Send` method is overloaded, see examples below:
### Using BacktraceReport
The `BacktraceReport` class represents a single error report. (Optional) You can also submit custom attributes using the `attributes` parameter, or attach files by supplying an array of file paths in the `attachmentPaths` parameter.
```csharp
try
{
//throw exception here
}
catch (Exception exception)
{
var report = new BacktraceReport(
exception: exception,
attributes: new Dictionary<string, object>() { { "key", "value" } },
attachmentPaths: new List<string>() { @"file_path_1", @"file_path_2" }
);
backtraceClient.Send(report);
}
```
Notes:
- if you setup `BacktraceClient` with `BacktraceDatabase` and your application is offline or you pass invalid credentials to `Backtrace server`, reports will be stored in database directory path,
- `BacktraceReport` allows you to change default Fingerprint generation algorithm. You can use `Fingerprint` property if you want to change Fingerprint value. Keep in mind - Fingerprint should be valid sha256 string. By setting `Fingerprint` you are instructing the client reporting library to only write a single report for the exception as it is encountered, and maintain a counter for every additional time it is encountered, instead of creating a new report. This will allow better control over the volume of reports being generated and sent to Backtrace. The counter is reset when the offline database is cleared (usually when the reports are sent to the server). A new single report will be created the next time the error is encountered.
- `BacktraceReport` allows you to change grouping strategy in Backtrace server. If you want to change how algorithm group your reports in Backtrace server please override `Factor` property.
If you want to use `Fingerprint` and `Factor` property you have to override default property values. See example below to check how to use these properties:
```csharp
try
{
//throw exception here
}
catch (Exception exception)
{
var report = new BacktraceReport(...){
Fingerprint = "sha256 string",
Factor = exception.GetType().Name
};
....
}
```
## Attaching custom event handlers <a name="documentation-events"></a>
`BacktraceClient` allows you to attach your custom event handlers. For example, you can trigger actions before the `Send` method:
```csharp
//Add your own handler to client API
backtraceClient.BeforeSend =
(Model.BacktraceData model) =>
{
var data = model;
//do something with data for example:
data.Attributes.Add("eventAttribute", "EventAttributeValue");
if(data.Classifier == null || !data.Classifier.Any())
{
data.Attachments.Add("path to attachment");
}
return data;
};
```
`BacktraceClient` currently supports the following events:
- `BeforeSend`
- `OnClientReportLimitReached`
- `OnServerResponse`
- `OnServerError`
## Reporting unhandled application exceptions
`BacktraceClient` supports reporting of unhandled application exceptions not captured by your try-catch blocks. To enable reporting of unhandled exceptions even if you don't set this option in `Backtrace configuration window` please use code below:
```csharp
backtraceClient.HandleApplicationException();
```
## Flush database
When your application starts, database can send stored offline reports. If you want to do make it manually you can use `Flush` method that allows you to send report to server and then remove it from hard drive. If `Send` method fails, database will no longer store data.
```csharp
backtraceDatabase.Flush();
```
## Clearing database
You can clear all data from database without sending it to server by using `Clear` method. `BacktraceDatabase` will remove all files and won't send it to server.
```csharp
backtraceDatabase.Clear();
```
#### Deduplication
Backtrace unity integration allows you to aggregate the same reports and send only one message to Backtrace Api. As a developer you can choose deduplication options. Please use `DeduplicationStrategy` enum to setup possible deduplication rules in Unity UI:
Deduplication strategy types:
- Ignore - ignore deduplication strategy,
- Default - deduplication strategy will only use current strack trace to find duplicated reports,
- Classifier - deduplication strategy will use stack trace and exception type to find duplicated reports,
- Message - deduplication strategy will use stack trace and exception message to find duplicated reports,
Notes:
- When you aggregate reports via Backtrace C# library, `BacktraceDatabase` will increase number of reports in BacktraceDatabaseRecord counter property.
- Deduplication algorithm will include `BacktraceReport` `Fingerprint` and `Factor` properties. `Fingerprint` property will overwrite deduplication algorithm result. `Factor` property will change hash generated by deduplication algorithm.
- If Backtrace unity integration combine multiple reports and user will close a game before plugin will send data to Backtrace, you will lose coutner information.
- `BacktraceDatabase` methods allows you to use aggregated diagnostic data together. You can check `Hash` property of `BacktraceDatabaseRecord` to check generated hash for diagnostic data and `Counter` to check how much the same records we detect.
- `BacktraceDatabase` `Count` method will return number of all records stored in database (included deduplicated records),
- `BacktarceDatabase` `Delete` method will remove record (with multiple deduplicated records) at the same time.
# Architecture description
## BacktraceReport <a name="architecture-BacktraceReport"></a>
**`BacktraceReport`** is a class that describe a single error report.
## BacktraceClient <a name="architecture-BacktraceClient"></a>
**`BacktraceClient`** is a class that allows you to send `BacktraceReport` to `Backtrace` server by using `BacktraceApi`. This class sets up connection to the Backtrace endpoint and manages error reporting behavior (for example, saving minidump files on your local hard drive and limiting the number of error reports per minute). `BacktraceClient` inherits from `Mono behavior`.
`BacktraceClient` requires from a `Backtrace configuration window`
- `Sever URL` - URL to `Backtrace` server,
- `Token` - token to `Backtrace` project,
- `ReportPerMin` - A cap on the number of reports that can be sent per minute. If `ReportPerMin` is equal to zero then there is no cap.
- `HandleUnhandledExceptions` - flag that allows `BacktraceClient` handling unhandled exception by default.
## BacktraceData <a name="architecture-BacktraceData"></a>
**`BacktraceData`** is a serializable class that holds the data to create a diagnostic JSON to be sent to the Backtrace endpoint via `BacktraceApi`. You can add additional pre-processors for `BacktraceData` by attaching an event handler to the `BacktraceClient.BeforeSend` event. `BacktraceData` require `BacktraceReport` and `BacktraceClient` client attributes.
## BacktraceApi <a name="architecture-BacktraceApi"></a>
**`BacktraceApi`** is a class that sends diagnostic JSON to the Backtrace endpoint. `BacktraceApi` is instantiated when the `BacktraceClient` awake method is called. `BacktraceApi` can asynchronous reports to the Backtrace endpoint.
## BacktraceDatabase <a name="architecture-BacktraceDatabase"></a>
**`BacktraceDatabase`** is a class that stores error report data in your local hard drive. `BacktraceDatabase` stores error reports that were not sent successfully due to network outage or server unavailability. `BacktraceDatabase` periodically tries to resend reports
cached in the database. In `BacktraceDatabaseSettings` you can set the maximum number of entries (`Maximum retries`) to be stored in the database. The database will retry sending
stored reports every `Retry interval` seconds up to `Retry limit` times, both customizable in the `Backtrace database configuration`.
`Backtrace database` has the following properties:
- `Database path` - the local directory path where `BacktraceDatabase` stores error report data when reports fail to send,
- `MaxRecordCount` - Maximum number of stored reports in Database. If value is equal to `0`, then there is no limit.
- `MaxDatabaseSize` - Maximum database size in MB. If value is equal to `0`, there is no limit.
- `AutoSendMode` - if the value is `true`, `BacktraceDatabase` will automatically try to resend stored reports. Default is `false`.
- `RetryBehavior` - - `RetryBehavior.ByInterval` - Default. `BacktraceDatabase` will try to resend the reports every time interval specified by `RetryInterval`. - `RetryBehavior.NoRetry` - Will not attempt to resend reports
- `RetryInterval` - the time interval between retries, in seconds.
- `RetryLimit` - the maximum number of times `BacktraceDatabase` will attempt to resend error report before removing it from the database.
If you want to clear your database or remove all reports after send method you can use `Clear` and `Flush`.
## ReportWatcher <a name="architecture-ReportWatcher"></a>
**`ReportWatcher`** is a class that validate send requests to the Backtrace endpoint. If `reportPerMin` is set in the `BacktraceClient` constructor call, `ReportWatcher` will drop error reports that go over the limit. `BacktraceClient` check rate limit before `BacktraceApi` generate diagnostic json.
# Investigating an Error in Backtrace
Once errors are being reported to your Backtrace instance, you should see them in your Triage and Web Debugger view. See below for a screenshot of the Triage view with some Unity exceptions reported.
The developer who is debugging the error may find it useful to view more details of Exception. They choose the 'View Latest Trace' action to see more details in the Backtrace Web Debugger. Below we can see a list of all attributes submitted with a report. (Note the yield signs are just an indicator that this value is not indexed in Backtrace). We can also see the call stack and details of the selected frame.
Below we see more details above the Environment Variables from the Web Debugger to further assist with investigation.
# Nice to know
- Backtrace Unity integration use JSON.NET library to create diagnostic JSON. JSON.NET Source code is available in `src` directory. JSON.NET was modified for Backtrace-plugin purpose.
| 63.297386 | 744 | 0.785637 | eng_Latn | 0.979325 |
c926ac86790b58478baf2e0b940816d8e346a3dc | 4,683 | md | Markdown | _posts/2016-06-13-bitcoin-block.md | sherryhuynh/blog | 547808aa01fdca3e8fabd0297d3810533c471fcf | [
"MIT"
] | 5 | 2018-10-15T03:11:04.000Z | 2020-12-03T08:04:45.000Z | _posts/2016-06-13-bitcoin-block.md | sherryhuynh/blog | 547808aa01fdca3e8fabd0297d3810533c471fcf | [
"MIT"
] | 1 | 2017-08-09T09:12:51.000Z | 2017-08-09T09:12:51.000Z | _posts/2016-06-13-bitcoin-block.md | sherryhuynh/blog | 547808aa01fdca3e8fabd0297d3810533c471fcf | [
"MIT"
] | 5 | 2017-08-09T07:11:10.000Z | 2018-10-16T16:10:42.000Z | ---
layout: post
cover: 'assets/images/covers/cover2.jpg'
title: Bitcoin block
date: 2016-06-13
tags: [bitcoin, bài dịch, cryptocurrency, blockchain]
author: jaken
description: >
Dữ liệu giao dịch bitcoin được lưu trữ trên các tập tin gọi là block. Bạn có thể tưởng tượng mỗi block giống như là một trang trong cuốn sổ ghi nợ, với mỗi dòng ghi lại số lượng tiền một người đã mượn/ trả. Các block được sắp xếp thành một chuỗi theo thời gian ( block chain). Các giao dịch mới được các bitcoin miner sắp xếp vào các block mới, được đặt vào cuối chuỗi và không thể bị thay đổi hoặc xóa khi nó đã được mạng bitcoin thừa nhận (tuy nhiên một số phần mềm bỏ qua các block rác - block không có hiệu lực).
---
Dữ liệu giao dịch bitcoin được lưu trữ trên các tập tin gọi là block. Bạn có thể tưởng tượng mỗi block giống như là một trang trong cuốn sổ ghi nợ, với mỗi dòng ghi lại số lượng tiền một người đã mượn/ trả. Các block được sắp xếp thành một chuỗi theo thời gian ( block chain). Các giao dịch mới được các bitcoin miner sắp xếp vào các block mới, được đặt vào cuối chuỗi và không thể bị thay đổi hoặc xóa khi nó đã được mạng bitcoin thừa nhận (tuy nhiên một số phần mềm bỏ qua các block rác - block không có hiệu lực).
#### Cấu trúc một block
````
4 bytes đầu: magic number 0xD9B4BEF9
4 bytes kế: số byte trong block
80 bytes kế: Blockheader
1-9 bytes kế: transaction counter
Danh sách các transactions
```
#### Mô tả
Mỗi block là một bản ghi của một vài hoặc tất cả các giao dịch gần nhất, và một tham chiếu tới block trước nó. Nó cũng chứa một đáp án cho "bài toán đố khó giải", đáp án này khác nhau với mỗi block. Các block mới không thể được gửi tới mạng bitcoin mà không có đáp án này, quá trình "đào bitcoin" là cuộc thi giữa các thợ mỏ để "giải" block hiện tại, tìm ra câu trả lời sớm nhất. Bài toán trong mỗi block đặc biệt khó, nhưng khi một đáp án đúng được tìm thấy, việc kiểm tra tính đúng đắn của đáp án này lại rất dễ. Mỗi block có thể có vài đáp án đúng khác nhau, nhưng chỉ cần tìm được một đáp án để giải bài toán.
Vì có một phần thưởng: các bitcoin mới sẽ được phát hành như phần quà cho việc giải đố các block, mỗi block cũng chứa một record ghi địa chỉ bitcoin hoặc script nhận phần quà. Record này được gọi là generation transaction hoặc coinbase transaction, và luôn là giao dịch đầu của các block. Số bitcoin phát hành trong một block ban đầu là 50 và giảm còn một nữa mỗi 210000 block (khoảng bốn năm).
Các giao dịch bitcoin được người gửi công bố trên toàn hệ thống, và tất cả các máy đào trong mạng sẽ nhận, thêm nó vào block đang làm việc. Các thợ mỏ được khuyến khích thêm các transaction vào block bằng mức phí đính kèm giao dịch.
Độ khó của bài toán được thay đổi tự động bởi hệ thống bitcoin, ví dụ hệ thống đặt một mục tiêu là giải 6 block mỗi giờ, sau 2016 blocks (giải trong khoảng hai tuần), tất cả các máy bitcoin so sánh số block thực sự giải được với con số giả định ban đầu. Dựa vào đó, mạng bitcoin có thể đưa ra quyết định tăng hoặc giảm độ khó của các block sinh ra.
Vì mỗi block có chứa một tham chiếu tới block trước, tất cả các block kết nối với nhau thành một xâu chuỗi. Tuy nhiên, xâu chuỗi này không luôn thẳng mà đôi khi có những nhánh rẽ: ví dụ hai thợ mỏ cùng lúc giải được một block, độc lập với người kia. Mạng bitcoin được thiết kế để có thể xử lý những nhánh rẽ này, và chỉ có một trong hai nhánh sẽ là chuỗi chính được quyền sống sót.
Các client chọn nhánh "dài nhất" là nhánh hợp lệ. "Độ dài" của nhánh tính theo độ khó tổng của các blocks, chứ không phải số block. Điều ngày ngăn cản một kẻ tấn công tạo một số lượng lớn các block dễ và tạo nên một chuỗi "dài"
#### Các câu hỏi thường gặp về block
* [Hiện có bao nhiêu block](https://blockexplorer.com/api/status?q=getBlockCount)?
* Số lượng tối đa block là bao nhiêu?
Không có một số block tối đa, các block liên tục được add vào block chain mỗi 10 phút
* Ngay cả khi 21 triệu bitcoin được phát hành hết?
Đúng, các transaction sẽ còn được sinh ra chừng nào còn người sử dụng bitcoin
* Cần bao lâu để tạo ra một block bằng tay?
Không có một con số chính xác, bạn thử đoán xem.
* Nếu tôi giải 1% của block và...?
Không có khái niệm giải 1% của block. Bạn không có một "tiến độ giải block" dù đã giải bao lâu, sau 24 giờ làm việc, xác xuất bạn giải được bài toán vẫn bằng lúc bạn bắt đầu giải cách đây 24h. Giống như ảo tưởng của tay đánh bạc, giải bài toán tương tự như việc gieo xúc sắc, xác xuất bạn gieo được ba mặt sáu là như nhau bất chấp bạn đã gieo bao nhiêu lần.
Tôi muốn biết sâu hơn về phần kỹ thuật của block?
Vâng, có một bài chi tiết [ở đây](/2016/06/18/bitcoin-block-hashing-algorithm)
Dịch từ https://en.bitcoin.it/wiki/Block | 79.372881 | 613 | 0.748665 | vie_Latn | 1.00001 |
c9272c2f163ee2b01f42d01ddba6c72784c68884 | 16,267 | md | Markdown | articles/service-fabric/service-fabric-disaster-recovery.md | ymasaoka/azure-docs.ja-jp | b4e9552f935e0522fe5f13f54a098d7d80ba2a00 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-05-18T23:13:17.000Z | 2021-05-18T23:13:17.000Z | articles/service-fabric/service-fabric-disaster-recovery.md | ymasaoka/azure-docs.ja-jp | b4e9552f935e0522fe5f13f54a098d7d80ba2a00 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/service-fabric/service-fabric-disaster-recovery.md | ymasaoka/azure-docs.ja-jp | b4e9552f935e0522fe5f13f54a098d7d80ba2a00 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Azure Service Fabric でのディザスター リカバリー
description: Azure Service Fabric では、障害に対処するための機能が提供されています。 この記事では、発生する可能性がある災害の種類とそれらに対処する方法について説明します。
author: masnider
ms.topic: conceptual
ms.date: 08/18/2017
ms.author: masnider
ms.openlocfilehash: 9c258d8d0a7aa26c96ab4f64017770ebdd153e60
ms.sourcegitcommit: dabd9eb9925308d3c2404c3957e5c921408089da
ms.translationtype: HT
ms.contentlocale: ja-JP
ms.lasthandoff: 07/11/2020
ms.locfileid: "86257507"
---
# <a name="disaster-recovery-in-azure-service-fabric"></a>Azure Service Fabric でのディザスター リカバリー
高可用性を実現するうえで欠かせないのは、サービスがあらゆる種類の障害を切り抜けられるようにすることです。 これは、計画外の障害や、制御できない障害に関しては特に重要です。
この記事では、正しくモデル化および管理されていない場合に、災害につながる可能性がある一般的な障害モードをいくつか取り上げて説明します。 さらに、軽減策や災害発生時の対処方法についても解説します。 その目的は、計画的または計画外の障害時に、ダウンタイムやデータ損失のリスクを軽減または排除することです。
## <a name="avoiding-disaster"></a>災害の回避
Azure Service Fabric の主な目的は、一般的な障害が災害につながらないように、環境とサービスの両方をモデル化できるよう支援することです。
一般的に、災害/障害のシナリオには 2 つの種類があります。
- ハードウェアおよびソフトウェアのエラー
- 操作上のエラー
### <a name="hardware-and-software-faults"></a>ハードウェアおよびソフトウェアのエラー
ハードウェアとソフトウェアのエラーは予測できません。 障害を最も簡単に切り抜けるには、ハードウェアまたはソフトウェアのエラーの境界で、より多くのサービス コピーを実行します。
たとえば、サービスが 1 台のマシンでのみ実行されている場合、そのマシンで障害が発生するということは、サービスで災害が発生するということです。 この災害は、サービスを複数のマシンで実行することによって、簡単に回避できます。 1 台のマシンの障害によって実行中のサービスが中断しないように、テストを行う必要もあります。 容量計画によって置換インスタンスを他の場所に作成すれば、容量が減っても、残りのサービスが過負荷になりません。
このパターンは、回避しようとしている障害の種類にかかわらず有効です。 たとえば、SAN の障害が心配であれば、複数の SAN で実行します。 サーバー ラックの損失が心配であれば、複数のラックで実行します。 データセンターの損失が心配であれば、複数の Azure リージョン、複数の Azure Availability Zones、またはご自身のデータセンターでサービスを実行します。
サービスが複数の物理インスタンス (マシン、ラック、データセンター、リージョン) にまたがっていても、同時に発生する一部の障害の影響はまだ受けます。 ただし、1 つの障害と、種類によっては複数の障害 (1 つの仮想マシンまたはネットワーク リンクの障害など) については自動的に処理されるため、これはもはや "災害" ではありません。
Service Fabric には、クラスターを拡張するメカニズムが用意されており、障害が発生したノードとサービスを元に戻します。 また、計画外の障害が本当の意味での災害にならないように、Service Fabric では、サービスのインスタンスを多数実行できます。
障害に対応できる規模でのデプロイを実現できないのには理由があるのでしょう。 たとえば、ハードウェア リソースのコストが、障害が発生する可能性を考えたときに、惜しまずに支払える金額を超えているのかもしれません。 分散アプリケーションを扱う場合は、地理的に離れた場所における追加の通信ホップまたは状態レプリケーション コストにより、許容できない待機時間が発生することがあります。 この線引きはアプリケーションごとに異なります。
特にソフトウェア エラーについては、スケールしようとしているサービスでエラーが発生している可能性があります。 この場合、コピーを増やしても災害を防ぐことはできません。障害の状態が、すべてのインスタンス間で相互に関連付けられているためです。
### <a name="operational-faults"></a>操作上のエラー
サービスが世界規模で分散され、あらゆる冗長性が実現されていても、災害を引き起こすイベントは発生します。 たとえば、ユーザーは誤ってサービスの DNS 名を再構成したり、完全に削除したりすることがあります。
ステートフルな Service Fabric サービスがあり、誰かがそのサービスを誤って削除したとします。 軽減策がなければ、サービスとそのサービスの状態はすべて失われます。 こうした種類の操作上の災害 ("不測") には、通常の計画外の障害とは異なる復旧対策と手順が必要です。
このような操作上のエラーを回避する最善の方法を次に示します。
- 環境への作業のためのアクセスを制限する。
- 危険な操作を厳密に監査する。
- 自動化を実施し、手動または帯域外の変更を防止するほか、環境に対する特定の変更を適用前に検証する。
- 破壊的な操作が "ソフト" であることを確認する。 ソフト操作はすぐには有効になりません。一定の時間内であれば操作を元に戻すことができます。
Service Fabric には、クラスター操作に対する[ロールベース](service-fabric-cluster-security-roles.md)のアクセス制御など、操作上のエラーを回避するためのメカニズムが用意されています。 ただし、このような操作上のエラーのほとんどでは、組織的な取り組みと他のシステムが必要です。 Service Fabric には、操作上のエラーを切り抜けるためのメカニズムが用意されています。中でもよく知られているのは、[ステートフル サービスのバックアップと復元](service-fabric-backuprestoreservice-quickstart-azurecluster.md)です。
## <a name="managing-failures"></a>障害の管理
Service Fabric では、障害を自動管理することを目標としています。 ただし、障害の中には、処理するために、追加コードがサービスに必要な場合があります。 また、安全性とビジネス継続性の理由により、自動的に対処するべき "_ではない_" 種類の障害もあります。
### <a name="handling-single-failures"></a>1 つの障害への対処
1 台のマシンで障害が発生する理由はさまざまです。 たとえば、電源やネットワーク ハードウェアの障害など、ハードウェアが原因の場合があります。 また、ソフトウェアが原因であることもあります。 これにはオペレーティング システムとサービス自体の障害が含まれます。 Service Fabric では、ネットワークの問題によりマシンが他のマシンから切り離されている、といった状況を含め、このような障害が自動的に検出されます。
サービスの種類に関係なく、実行されているインスタンスが 1 つだと、そのコードの 1 つのコピーが何らかの理由で失敗した場合に、そのサービスでダウンタイムが発生します。
すべての障害に対して最も簡単に対応するには、ご自身のサービスを、既定で、複数のノードで実行するようにします。 ステートレス サービスの場合は、`InstanceCount` が 1 よりも大きな値であることを確認します。 ステートフル サービスの場合、推奨最小値は、`TargetReplicaSetSize` と `MinReplicaSetSize` 両方が 3 に設定されています。 サービス コードのコピーを複数実行すると、サービスによって、すべての障害が確実に自動処理されます。
### <a name="handling-coordinated-failures"></a>組織的障害への対処
クラスター内での組織的障害の原因は、計画的または計画外インフラストラクチャ障害と変更、または計画的ソフトウェア変更のいずれかです。 Service Fabric は、組織的障害が発生しているインフラストラクチャ ゾーンを、"*障害ドメイン*" としてモデル化します。 組織的ソフトウェア変更が発生する領域は、"*アップグレード ドメイン*" としてモデル化されます。 障害ドメイン、アップグレード ドメイン、およびクラスター トポロジの詳細については、「[クラスター リソース マネージャーを使用して Service Fabric クラスターを記述する](service-fabric-cluster-resource-manager-cluster-description.md)」を参照してください。
既定では、Service Fabric は、障害ドメインとアップグレード ドメインを考慮して、サービスを実行する場所を計画します。 また、Service Fabric では、既定で複数の障害ドメインとアップグレード ドメインにわたってサービスを実行しようとするため、計画的または計画外変更が発生しても、サービスは使用可能な状態のままです。
たとえば、電源の障害により、ラック上のすべてのマシンで同時に障害が発生したとします。 サービスの複数のコピーが実行されているため、障害ドメインでの多数のマシンの喪失は、サービスに対する単一障害の別の一例に過ぎません。 障害およびアップグレード ドメインの管理が、サービスの高可用性の確保に欠かせないのはこのためです。
Azure で Service Fabric を実行している場合、障害ドメインおよびアップグレード ドメインは自動的に管理されます。 他の環境では、そうではない可能性があります。 オンプレミスで独自のクラスターを作成する場合は、障害ドメインのレイアウトを必ず正しく計画し、マップしてください。
アップグレード ドメインは、ソフトウェア アップグレードを同時に実行する領域をモデル化するときに役に立ちます。 このため、アップグレード ドメインは、多くの場合、計画的アップグレード中にソフトウェアが停止される境界も定義します。 Service Fabric とサービスの両方のアップグレードが同じモデルに従います。 ローリング アップグレード、アップグレード ドメイン、および予期しない変更による影響をクラスターとサービスが受けないようにするうえで役立つ Service Fabric 正常性モデルの詳細については、以下を参照してください。
- [アプリケーションのアップグレード](service-fabric-application-upgrade.md)
- [アプリケーション アップグレードのチュートリアル](service-fabric-application-upgrade-tutorial.md)
- [Service Fabric 正常性モデル](service-fabric-health-introduction.md)
[Service Fabric Explorer](service-fabric-visualizing-your-cluster.md) で提供されるクラスター マップを使用して、クラスターのレイアウトを視覚化できます。
<center>
![Service Fabric Explorer での障害ドメインに分散されたノードの表示][sfx-cluster-map]
</center>
> [!NOTE]
> 障害領域のモデル化、ローリング アップグレード、サービス コードと状態の多くのインスタンスの実行、障害ドメインとアップグレード ドメインでサービスを確実に実行するための配置ルール、および組み込みの正常性の監視は、通常の操作上の問題や障害が災害につながるのを未然に防ぐために、Service Fabric に用意されている機能の "*一部*" にすぎません。
>
### <a name="handling-simultaneous-hardware-or-software-failures"></a>ハードウェアまたはソフトウェアの同時障害への対処
ここまでは 1 つの障害について説明しました。 おわかりのように、この障害は、障害ドメインとアップグレード ドメインで実行されているコード (および状態) のコピーを複数保持するだけで、ステートレス サービスとステートフル サービスの両方を簡単に処理できます。
複数の障害がランダムに同時発生することがあります。 こうした障害は、ダウンタイムまたは実際の災害につながる可能性が高くなります。
#### <a name="stateless-services"></a>ステートレス サービス
ステートレス サービスの インスタンス数は、実行されている必要のある望ましいインスタンス数を示します。 いずれか (またはすべて) のインスタンスに障害が発生すると、その対応として、Service Fabric は自動的に置換インスタンスを他のノード上に作成します。 Service Fabric は、サービスのインスタンス数が望ましい数に戻るまで、置換インスタンスを作成し続けます。
たとえば、ステートレス サービスの `InstanceCount` が -1 だとします。 この値は、クラスター内の各ノード上で 1 つのインスタンスが実行されている必要があることを意味します。 そのいずれかのインスタンスに障害が発生した場合、Service Fabric はサービスが望ましい状態になっていないことを検出し、インスタンスが不足しているノード上にインスタンスを作成しようと試みます。
#### <a name="stateful-services"></a>ステートフル サービス
ステートフル サービスには、次の 2 種類があります。
- 状態が永続化されるステートフル。
- 状態が永続化されないステートフル (状態はメモリに格納される)。
ステートフル サービスの障害復旧は、ステートフル サービスの種類、サービスに存在するレプリカの数、および障害の発生したレプリカの数によって異なります。
ステートフル サービスでは、レプリカ (プライマリと任意のアクティブ セカンダリ) 間で受信データがレプリケートされます。 レプリカの過半数がデータを受信した場合、データは "*クォーラム*" コミットされていると見なされます (5 つのレプリカなら 3 がクォーラム)。つまり、どの時点でも、少なくとも最新のデータを持つレプリカのクォーラムが存在することになります。 レプリカに障害が発生した場合は (たとえば 5 つのレプリカのうち 2 つに障害が発生した場合は)、クォーラム値を使用して、復旧できるかどうかを計算できます (5 つのレプリカのうち残り 3 つはまだ稼動状態であるため、少なくとも 1 つのレプリカに完全なデータが存在することが保証されます)。
レプリカのクォーラムで障害が発生すると、パーティションは、"*クォーラム損失*" 状態で宣言されます。 たとえば、パーティションに 5 つのレプリカがあるとします。つまり、少なくとも 3 つのレプリカに完全なデータがあることが保証されるということです。 レプリカのクォーラム (5 つのうち 3 つ) で障害が発生した場合、残りのレプリカ (5 つのうち 2 つ) にパーティションを復元できるだけのデータがあるかどうかは、Service Fabric には判断できません。 クォーラム損失を検出した Service Fabric は、既定では、パーティションへの追加の書き込みを防止し、クォーラム損失を宣言して、レプリカのクォーラムが復元されるのを待ちます。
ステートフル サービスについて災害が発生したかどうかを判断し、それを管理するプロセスは、3 つの段階に従って実行されます。
1. クォーラムの損失があるかどうかを確認する。
ステートフル サービスのレプリカの過半数が同時にダウンしているときは、クォーラム損失が宣言されます。
2. クォーラムの損失が永続的かどうかを確認する。
ほとんどの場合、障害は一時的なものです。 プロセス、ノード、仮想マシンが再起動され、ネットワーク パーティションは修復します。 ただし、障害が永続的である場合もあります。 障害が永続的かどうかは、ステートフル サービスによって、状態が維持されるかどうか、または状態がメモリ内にのみ保持されるかどうかによって異なります。
- 永続化状態でないサービスの場合、クォーラムまたはレプリカで障害が発生すると、"_直ちに_" 永続的なクォーラム損失が発生します。 Service Fabric は、非永続的なステートフル サービスでクォーラムの損失を検出すると、(潜在的な) データ損失を宣言することによって直ちに手順 3. に処理を進めます。 Service Fabric にとって、レプリカの復旧を待っても無駄であることは自明であるため、データ損失として処理を進めることは理にかなっています。 復旧されたとしても、非永続というサービスの性質上、データは失われます。
- 永続的なステートフル サービスの場合、クォーラム以上のレプリカで障害が発生すると、Service Fabric は、レプリカが復旧してクォーラムが復元するのを待ちます。 これにより、影響を受けるサービス パーティション ("レプリカ セット") に対するすべての "_書き込み_" でサービス停止が発生します。 ただし、一貫性の保証は少なくなりますが、読み取りはまだ可能です。 続行することは (潜在的な) データ損失イベントであり、他のリスクを伴うため、Service Fabric がクォーラムの復元を待つ既定の時間は "*無制限*" です。 つまり、管理者がデータ損失を宣言するアクションを実行しない限り、Service Fabric が次の手順に進むことはありません。
3. 実際にデータが損失したかどうかを確認し、バックアップから復元する。
クォーラム損失が (自動的に、または管理アクションによって) 宣言された場合、Service Fabric とサービスは、データが実際に損失したかどうかの確認に進みます。 この時点で、Service Fabric は、他のレプリカが戻らないこともわかっています。 これは、クォーラム損失が解決されるのを待つことをやめたとき行われた決定です。 サービスに対する最善なアクションは、通常、アクションを凍結し、特定の管理介入を待つことです。
Service Fabric が `OnDataLossAsync` メソッドを呼び出す場合、それは常に、データ損失の "_疑いがある_" ためです。 Service Fabric により、この呼び出しは確実に "_最適_" な残りのレプリカに配信されます。 これは、最も進捗しているレプリカです。
常に、データ損失の "_疑いがある_" のは、クォーラムが損失したときのプライマリの状態と、残りのレプリカがまったく同じ状態である可能性がある、ということが理由です。 しかし、比較対象となる状態がなければ、Service Fabric やオペレーターが適切な方法でそれを確信することはできません。
では、`OnDataLossAsync` メソッドの一般的な実装では何を行うのでしょう。
1. 実装は、`OnDataLossAsync` がトリガーされたことがログに記録し、必要な管理アラートを起動します。
1. 通常、実装は一時停止され、さらなる決定と、手動アクションが実行されるのを待ちます。 これは、バックアップを使用できる場合でも、準備が必要な可能性があるためです。
たとえば、2 つの異なるサービスで情報を調整する場合、復元後に、その 2 つのサービスに関連する情報の一貫性を確保するために、こうしたバックアップの変更が必要になることがあります。
1. 多くの場合、サービスの他のテレメトリや消費データが存在します。 このメタデータは、他のサービスまたはログに含まれている可能性があります。 この情報を必要に応じて使用し、バックアップに存在しない呼び出し、またはこの特定のレプリカにレプリケートされなかった呼び出しが、プライマリで受信および処理されたかどうかを判断します。 復元を実現するには、これらの呼び出しを再生するか、バックアップに追加しなければならないことがあります。
1. 実装は、残りのレプリカの状態と、使用できるバックアップに含まれるものを比較します。 Service Fabric の信頼できるコレクションを使用している場合、このための[ツールやプロセス](service-fabric-reliable-services-backup-restore.md)を入手できます。 その目的は、レプリカ内の状態が十分かどうか、およびバックアップで何が不足している可能性があるかを確認することです。
1. 比較の完了後、(必要に応じて) 復元が行われ、その後に状態が変更されると、サービス コードは **true** を返します。 レプリカが使用可能な最善の状態のコピーであると判断された場合、変更は行われず、コードは **false** を返します。
**true** の値は、"_他_" の残りのレプリカが、このレプリカと整合性がとれていない可能性があることを示します。 残りのレプリカは削除され、このレプリカから再作成されます。 **false** は、状態の変更は行われていないため、他のレプリカをそのまま保持できることを意味します。
サービスが運用環境にデプロイされる前に、サービス作成者が潜在的なデータ損失と障害のシナリオを実施することが非常に重要です。 データ損失の可能性から保護するには、すべてのステートフル サービスの geo 冗長ストアへの[状態のバックアップ](service-fabric-reliable-services-backup-restore.md)を定期的に行うことが重要です。
また、状態を復元する機能を確保する必要もあります。 さまざまなサービスのバックアップがそれぞれ異なるタイミングで行われるため、復元後、こうしたサービスのビューが相互に一貫性があることを確認する必要があります。
たとえば、あるサービスが数値を生成して格納し、その数値を他のサービスに送信したとします。送信先のサービスも、受け取った数値を格納します。 復元後、2 番目のサービスに数値があり、最初のサービスにはないことに気が付きました。これはバックアップに、この操作が含まれていなかったためです。
残りのレプリカがデータ損失のシナリオで続行するには不十分なことがわかり、サービスの状態をテレメトリまたは消費データから再構成できない場合は、バックアップの頻度によって、可能性のある最適な目標復旧時点 (RPO) が決定されます。 Service Fabric には、バックアップからの復元を必要とする永続的なクォーラムやデータ損失を含め、さまざまな障害のシナリオをテストするための多数のツールが用意されています。 こうしたシナリオは、Fault Analysis Service によって管理される、Service Fabric の Testability ツールに含まれています。 ツールとパターンの詳細については、「[Fault Analysis Service の概要](service-fabric-testability-overview.md)」を参照してください。
> [!NOTE]
> システム サービスでもクォーラム損失が発生する可能性があり、 その影響は問題のあるサービスに固有です。 たとえば、ネーム サービスでのクォーラム損失は名前解決に影響があり、Failover Manager サービスでクォーラム損失が発生すると、新しいサービスの作成とフェールオーバーがブロックされます。
>
> Service Fabric システム サービスは状態管理のためのサービスと同じパターンに従いますが、それらをクォーラム損失から潜在的なデータ損失に移動しようとすることはお勧めしません。 代わりに、[サポートを利用](service-fabric-support.md)して、個別の状況に合ったソリューションを見つけることをお勧めします。 通常は、ダウンしたレプリカが復旧するまで待つのがよいでしょう。
>
#### <a name="troubleshooting-quorum-loss"></a>クォーラム損失のトラブルシューティング
一時的な障害によってレプリカが断続的にダウンすることがあります。 このような場合は、Service Fabric が復旧を試みるので、しばらくお待ちください。 レプリカがダウンしたまま所定の時間が経過した場合は、次のトラブルシューティング手順に従います。
- レプリカがクラッシュしている可能性があります。 レプリカ レベルの正常性レポートおよびアプリケーション ログをチェックしてください。 クラッシュ ダンプを収集し、復元のために必要な措置を講じます。
- レプリカのプロセスが無応答状態になっている可能性があります。 アプリケーション ログを見てそれを確認してください。 プロセス ダンプを収集し、応答しないプロセスを停止します。 Service Fabric は、代替プロセスを作成してレプリカの復旧を試みます。
- レプリカをホストしているノードがダウンしている可能性があります。 基になる仮想マシンを再起動して、ノードを稼動状態にしてください。
レプリカを復旧できない可能性があることもあります。 ドライブが故障している、マシンが物理的に応答していない、といった場合などです。 そのような場合は、レプリカの復旧を待たないよう Service Fabric に指示する必要があります。
サービスをオンライン状態にするためのデータ損失を許容できない場合、これらの方法は "*使用しない*" でください。 この場合は、物理マシン復旧のために、できることをすべて行う必要があります。
次のアクションは、データ損失につながる可能性があります。 その点を理解したうえで実行してください。
> [!NOTE]
> 対象の方法以外で特定のパーティションに対してこれらの方法を使用するのは、"_決して_" 安全ではありません。
>
- `Repair-ServiceFabricPartition -PartitionId` または `System.Fabric.FabricClient.ClusterManagementClient.RecoverPartitionAsync(Guid partitionId)` API を使用します。 この API により、クォーラム損失から潜在的なデータ損失に移行するために、パーティションの ID を指定できます。
- クォーラム損失の状態をサービスに引き起こすような障害がクラスターで頻繁に発生する場合で、かつ潜在的な "_データ損失が許容できる_" 場合は、適切な [QuorumLossWaitDuration](/powershell/module/servicefabric/update-servicefabricservice?view=azureservicefabricps) 値を指定することが、サービスの自動復旧に役立つことがあります。 Service Fabric は、指定された `QuorumLossWaitDuration` 値 (既定では無期限) 待機した後、復旧を実行します。 この方法は予期しないデータ損失につながるおそれがあるため "*お勧めしません*"。
## <a name="availability-of-the-service-fabric-cluster"></a>Service Fabric クラスターの可用性
一般的に、Service Fabric クラスターは高度な分散環境で、単一障害点がありません。 どのノードで障害が発生しても、クラスターの可用性または信頼性で問題が発生することはありません。これは主に Service Fabric システム サービスが、前に説明したものと同じガイドラインに従っているためです。 つまり、既定で常に 3 つ以上のレプリカで実行され、ステートレスのシステム サービスはすべてのノードで実行されています。
基になる Service Fabric ネットワークとエラー検出レイヤーは完全に分散されています。 システム サービスは総じてメタデータから再構築できるか、他の場所から状態を再同期する方法を認識しています。 クラスターの可用性が低下する可能性があるのは、前述したようなクォーラム損失状態がシステム サービスで発生した場合です。 このような場合、アップグレードの開始、一部の操作 (新しいサービスのデプロイなど) をクラスターで実行できないことがありますが、クラスター自体はまだ起動しています。
実行中のクラスター上のサービスについては、システム サービスに書き込まなくても継続して動作できるのであれば、こうした状況でも引き続き実行されます。 たとえば、Failover Manager でクォーラム損失が発生しても、すべてのサービスが継続して実行されます。 ただし、障害が発生しているサービスについては、Failover Manager の関与が必要であるため、自動的に再起動することはできません。
### <a name="failures-of-a-datacenter-or-an-azure-region"></a>データセンターまたはAzure リージョンの障害
まれに、停電やネットワーク切断のために、物理的なデータセンターが一時的に使用できなくなることがあります。 このような場合、そのデータセンターまたは Azure リージョンの Service Fabric クラスターとサービスは使用できなくなります。 ただし、"_データは保存されます_"。
Azure で実行されているクラスターの場合、「[Azure の状態][azure-status-dashboard]」ページで停止に関する更新情報を確認できます。 極めてまれなことですが、データ センターが物理的に一部または全体が破壊された場合、そこでホストされている Service Fabric クラスター、またはその中のサービスが失われる可能性があります。 この損失には、そのデータセンターやリージョン外でバックアップされていない状態も含まれます。
1 つのデータセンターやリージョンにおける永続的または持続的な障害を切り抜けるための戦略は 2 つあります。
- このような複数のリージョンで Service Fabric クラスターをそれぞれ実行し、こうした環境間でのフェールオーバーとフェールバックのメカニズムをいくつか使用します。 このような複数クラスターのアクティブ/アクティブまたはアクティブ/パッシブ モデルには、追加の管理および操作コードが必要です。 また、このモデルには、あるデータセンターやリージョンで障害が発生したときに、その中のサービスを他のデータセンターやリージョンで使用できるように、サービスのバックアップの調整も必要です。
- 複数のデータセンターやリージョンにまたがる 1 つの Service Fabric クラスターを実行します。 この戦略がサポートされる最小構成は 3 つのデータ センターまたはリージョンです。 推奨されるリージョンまたはデータセンターの数は 5 つです。
このモデルには、さらに複雑なクラスター トポロジが必要になります。 ただし、利点は、1 つのデータセンターまたはリージョンの障害が、災害から通常の障害に変換される点です。 こうした障害は、1 つのリージョン内のクラスターに対して有効なメカニズムで処理できます。 障害ドメイン、アップグレード ドメイン、および Service Fabric の配置ルールにより、通常の障害が許容されるようにワークロードが分散されます。
この種類のクラスターにおけるサービス操作に役立つポリシーの詳細については、「[Service Fabric サービスの配置ポリシー](service-fabric-cluster-resource-manager-advanced-placement-rules-placement-policies.md)」を参照してください。
### <a name="random-failures-that-lead-to-cluster-failures"></a>クラスター障害につながるランダムに発生する障害
Service Fabric には "*シード ノード*" の概念があります。 これは基になるクラスターの可用性を維持するノードです。
特定の種類の障害が発生しているときに、他のノードとのリースを確立し、タイブレーカーとして機能することで、クラスターが確実に稼働し続けるうえで、シード ノードが役立ちます。 ランダムに発生する障害によりクラスターのシード ノードの大部分が削除され、すぐには元に戻らない場合、お使いのクラスターは自動的にシャット ダウンします。 その後、クラスターは失敗します。
Azure では、Service Fabric リソース プロバイダーによって、Service Fabric クラスターの構成が管理され、 既定では、"*プライマリ ノード タイプ*" のフォールト ドメインとアップグレード ドメインに、シード ノードが分散されます。 プライマリ ノード タイプが Silver または Gold の持続性とマークされている場合、(プライマリ ノード タイプをスケーリングするか、手動で) シード ノードを削除するときに、クラスターによって、プライマリ ノード タイプの空き領域から別の非シード ノードへの昇格が試みられます。 空き容量が、プライマリ ノード タイプに必要なクラスターの信頼性レベルよりも少ない場合、この試みは失敗します。
スタンドアロンの Service Fabric クラスターと Azure の両方について、シードを実行するのは "プライマリ ノード タイプ" です。 プライマリ ノード タイプを定義するとき、Service Fabric では、システム サービスごとに最大 9 個のシード ノードと 7 個のレプリカを作成することで、提供されるノード数が自動的に使用されます。 ランダムに発生する障害によって、こうしたレプリカの大部分が同時に削除されると、システム サービスはクォーラム損失に移行します。 シード ノードの大部分が失われた場合、クラスターは直ちにシャット ダウンします。
## <a name="next-steps"></a>次のステップ
- [Testability フレームワーク](service-fabric-testability-overview.md)を使用して、さまざまな障害をシミュレートする方法を確認します。
- ディザスター リカバリーと高可用性に関する他のリソースを読みます。 Microsoft は、これらのトピックに関して多数のガイダンスを公開しています。 これらのリソースの一部は他の製品で使用するための具体的な方法に関するものですが、Service Fabric に適用できる一般的なベスト プラクティスが多数含まれます。
- [可用性のチェックリスト](/azure/architecture/checklist/resiliency-per-service)
- [ディザスター リカバリー訓練の実行](../azure-sql/database/disaster-recovery-drills.md)
- [Azure アプリケーションのディザスター リカバリーと高可用性][dr-ha-guide]
- [Service Fabric のサポート オプション](service-fabric-support.md)について学びます。
<!-- External links -->
[repair-partition-ps]: /windows/win32/perfctrs/specifying-a-counter-path
[azure-status-dashboard]:https://azure.microsoft.com/status/
[azure-regions]: https://azure.microsoft.com/regions/
[dr-ha-guide]: /previous-versions/azure/dn251004(v=azure.100)
<!-- Images -->
[sfx-cluster-map]: ./media/service-fabric-disaster-recovery/sfx-clustermap.png
| 71.660793 | 390 | 0.853999 | jpn_Jpan | 0.897773 |
c927c97d01795cf24610e37ea073c72caa0f74f5 | 175 | md | Markdown | README.md | devrolet/contacts-app | d0cf5344ba000999bd061641b8cc5c4946c8700a | [
"MIT"
] | null | null | null | README.md | devrolet/contacts-app | d0cf5344ba000999bd061641b8cc5c4946c8700a | [
"MIT"
] | null | null | null | README.md | devrolet/contacts-app | d0cf5344ba000999bd061641b8cc5c4946c8700a | [
"MIT"
] | null | null | null | # contacts-app
AngularJS web app built using HTML5, JS, and CSS. Cloud storage using Firebase. This app uses the Foundation responsive framework and Angular Seed boilerplate. | 58.333333 | 159 | 0.811429 | eng_Latn | 0.98496 |
c928690fca3f956c682c1244c0535d98f87a61a1 | 464 | md | Markdown | src/pages/contract-private-functions/index.md | msinkec/scrypt-by-example.github.io | f7381b7c142e92878ece68b27ab5bb3843625977 | [
"MIT"
] | null | null | null | src/pages/contract-private-functions/index.md | msinkec/scrypt-by-example.github.io | f7381b7c142e92878ece68b27ab5bb3843625977 | [
"MIT"
] | 1 | 2022-01-05T19:57:09.000Z | 2022-01-05T19:57:09.000Z | src/pages/contract-private-functions/index.md | sCrypt-Inc/scrypt-by-example.github.io | a7ad9868f0613b89c17e5208c98b2c25fbbec859 | [
"MIT"
] | null | null | null | ---
title: Functions
version: 0.1.0
description: Functions in sCrypt
---
sCrypt enables developers to define their own functions as exemplified below:
```javascript
function sum(int a, int b): int {
return a + b;
}
```
They are only visible within the contract, similar to `private` functions in Solidity.
Every function must end with a `return` statement. Recursion is disallowed. A function cannot call itself in its body, either directly or indirectly.
| 25.777778 | 149 | 0.752155 | eng_Latn | 0.997714 |
c928a7c84f8c1c9af455e356399194d7a44fbd6f | 2,206 | md | Markdown | documentation/status-logging.md | Sharpie/trapperkeeper-metrics | e50e9f75c5f609bca5b40ca0e1a04659e915e2ef | [
"Apache-2.0"
] | 4 | 2015-04-25T14:46:11.000Z | 2016-12-11T22:30:23.000Z | documentation/status-logging.md | Sharpie/trapperkeeper-metrics | e50e9f75c5f609bca5b40ca0e1a04659e915e2ef | [
"Apache-2.0"
] | 71 | 2015-03-28T00:28:26.000Z | 2020-08-28T23:28:34.000Z | documentation/status-logging.md | Sharpie/trapperkeeper-metrics | e50e9f75c5f609bca5b40ca0e1a04659e915e2ef | [
"Apache-2.0"
] | 23 | 2015-03-27T19:34:53.000Z | 2020-08-28T21:51:21.000Z | # Status logging
TK-status can periodically log status data to a file in JSON format.
To take advantage of this you must do two things:
1. Enable logging through your TK app's configuration. For example, to log every 30 minutes, your configuration might look like this:
```
status: {
debug-logging: {
interval-minutes: 30,
}
}
```
2. Create a logback `logger` in your logback configuration for the `puppetlabs.trapperkeeper.services.status.status-logging` namespace.
For example, this `logger` and `appender` will send the status log messages to a file, manage rotating them, and keep them from taking up too much room
```
<appender name="STATUS" class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>/tmp/status.log</file>
<append>true</append>
<rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy">
<!-- rollover daily -->
<fileNamePattern>/status-%d{yyyy-MM-dd}.%i.log.zip</fileNamePattern>
<!-- each file should be at most 10MB, keep 90 days worth of history, but at most 1GB total-->
<maxFileSize>10MB</maxFileSize>
<maxHistory>90</maxHistory>
<totalSizeCap>1GB</totalSizeCap>
</rollingPolicy>
<encoder>
<!-- note that this will only log the JSON message (%m) and a newline (%n)-->
<pattern>%m%n</pattern>
</encoder>
</appender>
<!-- without additivity="false", the status log messages will be sent to every other appender as well-->
<logger name="puppetlabs.trapperkeeper.services.status.status-debug-logging" level="debug" additivity="false">
<appender-ref ref="STATUS"/>
</logger>
```
A simpler config with no rotation would look like this:
```
<appender name="STATUS" class="ch.qos.logback.core.FileAppender">
<file>/tmp/status.log</file>
<encoder>
<pattern>%m%n</pattern>
</encoder>
</appender>
<logger name="puppetlabs.trapperkeeper.services.status.status-debug-logging" level="debug" additivity="false">
<appender-ref ref="STATUS"/>
</logger>
```
| 39.392857 | 154 | 0.644606 | eng_Latn | 0.772637 |
c92a1c300775ea5e47e02de7f7311c1831118dcb | 1,663 | md | Markdown | api/qsharp/microsoft.quantum.canon.applyifonec.md | MicrosoftDocs/quantum-docs-pr.zh-CN | 1806cbf948b8a33a63155ed8e2735ef00972ecc4 | [
"CC-BY-4.0",
"MIT"
] | 4 | 2020-03-30T04:57:50.000Z | 2021-01-18T00:09:20.000Z | api/qsharp/microsoft.quantum.canon.applyifonec.md | MicrosoftDocs/quantum-docs-pr.zh-CN | 1806cbf948b8a33a63155ed8e2735ef00972ecc4 | [
"CC-BY-4.0",
"MIT"
] | 8 | 2020-03-12T23:57:52.000Z | 2021-01-17T23:51:11.000Z | api/qsharp/microsoft.quantum.canon.applyifonec.md | MicrosoftDocs/quantum-docs-pr.zh-CN | 1806cbf948b8a33a63155ed8e2735ef00972ecc4 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2021-01-17T23:24:50.000Z | 2021-11-15T09:23:22.000Z | ---
uid: Microsoft.Quantum.Canon.ApplyIfOneC
title: ApplyIfOneC 操作
ms.date: 1/23/2021 12:00:00 AM
ms.topic: article
qsharp.kind: operation
qsharp.namespace: Microsoft.Quantum.Canon
qsharp.name: ApplyIfOneC
qsharp.summary: Applies a controllable operation conditioned on a classical result value being one.
ms.openlocfilehash: ebeec5b46567892ad30f194ababb42876ba08bcb
ms.sourcegitcommit: 71605ea9cc630e84e7ef29027e1f0ea06299747e
ms.translationtype: MT
ms.contentlocale: zh-CN
ms.lasthandoff: 01/26/2021
ms.locfileid: "98841762"
---
# <a name="applyifonec-operation"></a>ApplyIfOneC 操作
命名空间： [Canon](xref:Microsoft.Quantum.Canon)
包： [Microsoft 量子. 标准版](https://nuget.org/packages/Microsoft.Quantum.Standard)
应用以传统结果值为一的可控操作。
```qsharp
operation ApplyIfOneC<'T> (result : Result, (op : ('T => Unit is Ctl), target : 'T)) : Unit is Ctl
```
## <a name="description"></a>说明
给定一个操作 `op` 和一个结果值时 `result` ， `op` `target` 如果为， `result` 则应用于 `One` 。 如果 `Zero` 为，则不会发生任何事情 `target` 。
后缀 `C` 指示要应用的操作可控制。
## <a name="input"></a>输入
### <a name="result--__invalidresult__"></a>结果：__无效 <Result>__
用于控制是否应用 op 的测量结果。
### <a name="op--t--unit--is-ctl"></a>op： t => [单位](xref:microsoft.quantum.lang-ref.unit) 为 Ctl
要有条件地应用的操作。
### <a name="target--t"></a>目标： t
将操作应用到的输入。
## <a name="output--unit"></a>输出： [单元](xref:microsoft.quantum.lang-ref.unit)
## <a name="type-parameters"></a>类型参数
### <a name="t"></a>找
要有条件地应用的操作的输入类型。
## <a name="see-also"></a>另请参阅
- [Canon. ApplyIfOneC](xref:Microsoft.Quantum.Canon.ApplyIfOneC)
- [Canon. ApplyIfOneA](xref:Microsoft.Quantum.Canon.ApplyIfOneA)
- [Canon. ApplyIfOneCA](xref:Microsoft.Quantum.Canon.ApplyIfOneCA) | 24.455882 | 104 | 0.716777 | yue_Hant | 0.681623 |
c92a4e8420e17237ecd331af5ddbe7ed78fd22c2 | 514 | md | Markdown | _pages/about.md | dshpark/dshpark.github.io | fb58d53442bc995841e1b36c744b613f4107db5f | [
"MIT"
] | null | null | null | _pages/about.md | dshpark/dshpark.github.io | fb58d53442bc995841e1b36c744b613f4107db5f | [
"MIT"
] | null | null | null | _pages/about.md | dshpark/dshpark.github.io | fb58d53442bc995841e1b36c744b613f4107db5f | [
"MIT"
] | null | null | null | ---
permalink: /
title: "About me"
excerpt: ""
author_profile: true
redirect_from:
- /about/
- /about.html
---
I am a Ph.D. Candidate at the Economics Department of University of California, Santa Cruz (UCSC), doing Development Economics with ongoing field projects in Liberia and Malawi.
[[Curriculum Vitae]](/files/CV_DavidSunghoPark.pdf)
Economics Department, University of California, Santa Cruz
1156 High Street, Santa Cruz, CA 95064
[davidspark [at] ucsc [dot] edu](mailto:[email protected])
| 25.7 | 179 | 0.745136 | eng_Latn | 0.617403 |
c92abc555367070ada0c4e4dc098499a58678c93 | 2,450 | md | Markdown | desktop-src/Msi/installed.md | citelao/win32 | bf61803ccb0071d99eee158c7416b9270a83b3e4 | [
"CC-BY-4.0",
"MIT"
] | 4 | 2021-07-26T16:18:49.000Z | 2022-02-19T02:00:21.000Z | desktop-src/Msi/installed.md | citelao/win32 | bf61803ccb0071d99eee158c7416b9270a83b3e4 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-04-09T17:00:51.000Z | 2020-04-09T18:30:01.000Z | desktop-src/Msi/installed.md | citelao/win32 | bf61803ccb0071d99eee158c7416b9270a83b3e4 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-07-19T02:58:48.000Z | 2021-03-06T21:09:47.000Z | ---
Description: The Installed property is set only if the product is installed per-machine or for the current user.
ms.assetid: 139a6324-58fb-485e-8b3e-c5cf2881d5d1
title: Installed property
ms.topic: reference
ms.date: 05/31/2018
---
# Installed property
The **Installed** property is set only if the product is installed per-machine or for the current user. This property is not set if the product is installed for a different user.
The **Installed** property can be used in conditional expressions to determine whether a product is installed per-computer or for the current user. For example, the property can be used in the conditional column of a sequence table or to differentiate between a first installation and a maintenance installation.
To determine whether the product is installed for a different user, check the [**ProductState**](productstate.md) property.
The value of the [**ProductVersion**](productversion.md) property is the version of the product in string format.
## Requirements
| | |
|--------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Version<br/> | Windows Installer 5.0 on Windows Server 2012, Windows 8, Windows Server 2008 R2 or Windows 7. Windows Installer 4.0 or Windows Installer 4.5 on Windows Server 2008 or Windows Vista. Windows Installer on Windows Server 2003 or Windows XP. See the [Windows Installer Run-Time Requirements](windows-installer-portal.md) for information about the minimum Windows service pack that is required by a Windows Installer version.<br/> |
## See also
<dl> <dt>
[Properties](properties.md)
</dt> </dl>
| 56.976744 | 457 | 0.485714 | eng_Latn | 0.977273 |
c92abda99eed57db489fc64d25283f01ab32c3b2 | 2,130 | md | Markdown | README.md | SagarGurnani/marketplaces-managedpath-php-demo | a93b6dca7057c39ee16568735438abda85b313f8 | [
"RSA-MD"
] | null | null | null | README.md | SagarGurnani/marketplaces-managedpath-php-demo | a93b6dca7057c39ee16568735438abda85b313f8 | [
"RSA-MD"
] | null | null | null | README.md | SagarGurnani/marketplaces-managedpath-php-demo | a93b6dca7057c39ee16568735438abda85b313f8 | [
"RSA-MD"
] | null | null | null | ## PayPal Commerce Platform Managed path
> **Important:** PayPal Commerce Platform for eCommerce Solution Providers and Marketplaces is a limited-release solution at this time. It is available to select partners for approved use cases. Two versions of the solution are available:
>
>New integrations: [version 2](https://developer.paypal.com/docs/partners/) (from February 2019)
>
>Existing integrations: [version 1](https://developer.paypal.com/docs/partners/v1/) (before February 2019)
>
>New customers should integrate version 2. For more information, reach out to your PayPal account manager.
>This code sample is not upgraded to use [version 2](https://developer.paypal.com/docs/partners/).
## Prerequisites
1. Update PayConfig.php with your "Partner credentials", "Seller emails" and "Seller Payer IDs". If you do not have the credentials, please reach out to your PayPal account manager.
2. Verify that all the files are in place by running and passing the Unit tests (process shown below).
wget https://phar.phpunit.de/phpunit-5.7.phar
(Download a version of PHPunit consisent with your php version)
mv phpunit-5.7.phar /usr/local/bin/phpunit
chmod a+x /usr/local/bin/phpunit
phpunit --version
phpunit Tests/unit_test.php
## Quick Start Demo Deployment Using XAMPP
1. Download PHP server.
Use a server such as XAMPP ([https://www.apachefriends.org/index.html]()) to be able to host the Demo code sample.
2. Browse to the ***htdocs*** directory of xampp. Unzip the downloaded demo code folder and place it in this ***htdocs*** directory.
3. Start the Apache server in XAMPP from the XAMPP control panel.
4. Open the website in the browser and access it as: [http://my_domain/php_code_folder_name/index.php]()
Here, ***my_domain*** will be localhost if hosting on your own machine.
The ***php_code_folder_name*** is the name of the folder under which the downloaded code resides.
5. Read further instructions when `index.php` in opened in a browser.
## How the code works
The starting point is `index.php`.
## License
Code released under [LICENSE](LICENSE.md)[]([]())
| 38.035714 | 238 | 0.749296 | eng_Latn | 0.976339 |
c92ac3ce65110473a0cb5c52d31cfefee6e684bb | 2,566 | md | Markdown | docs/framework/wpf/graphics-multimedia/how-to-animate-a-3-d-rotation-using-key-frames.md | BraisOliveira/docs.es-es | cc6cffb862a08615c53b07afbbdf52e2a5ee0990 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wpf/graphics-multimedia/how-to-animate-a-3-d-rotation-using-key-frames.md | BraisOliveira/docs.es-es | cc6cffb862a08615c53b07afbbdf52e2a5ee0990 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wpf/graphics-multimedia/how-to-animate-a-3-d-rotation-using-key-frames.md | BraisOliveira/docs.es-es | cc6cffb862a08615c53b07afbbdf52e2a5ee0990 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Procedimiento Animar un giro 3D mediante fotogramas clave
ms.date: 03/30/2017
helpviewer_keywords:
- animation [WPF], 3-D translations [WPF], with key frames (Rotation3DAnimation)
- key frames [WPF], Rotation3DAnimation
- 3-D translations [WPF], animating [WPF], with key frames (Rotation3DAnimation)
ms.assetid: 6f671b95-7f30-4836-9a4f-aeb7dc30121f
ms.openlocfilehash: e72ec94f830f0f5001a77e7492aa1326a47b309d
ms.sourcegitcommit: 9b552addadfb57fab0b9e7852ed4f1f1b8a42f8e
ms.translationtype: MT
ms.contentlocale: es-ES
ms.lasthandoff: 04/23/2019
ms.locfileid: "61762155"
---
# <a name="how-to-animate-a-3-d-rotation-using-key-frames"></a>Procedimiento Animar un giro 3D mediante fotogramas clave
En el ejemplo siguiente, <xref:System.Windows.Media.Animation.Rotation3DAnimationUsingKeyFrames> se usa para hacer girar mientras su eje de rotación resultante en un "oscilante" anima un objeto 3D. Esta animación usa los fotogramas clave siguientes:
1. <xref:System.Windows.Media.Animation.LinearRotation3DKeyFrame> se usa para crear una interpolación lineal suave entre valores.
2. <xref:System.Windows.Media.Animation.DiscreteRotation3DKeyFrame> se usa para crear "saltos" súbitos entre los valores (sin interpolación).
3. <xref:System.Windows.Media.Animation.SplineRotation3DKeyFrame> se utiliza para crear una transición variable entre los valores según el <xref:System.Windows.Media.Animation.SplineRotation3DKeyFrame.KeySpline%2A> propiedad. En el ejemplo siguiente, esta parte de la animación se inicia lentamente, pero hacia el final del segmento temporal, se acelera exponencialmente.
## <a name="example"></a>Ejemplo
[!code-xaml[Animation3DGallery_snip#Rotation3DAnimationUsingKeyFramesExampleWholePage](~/samples/snippets/csharp/VS_Snippets_Wpf/Animation3DGallery_snip/CS/Rotation3DAnimationUsingKeyFramesExample.xaml#rotation3danimationusingkeyframesexamplewholepage)]
## <a name="see-also"></a>Vea también
- [Información general sobre gráficos 3D](3-d-graphics-overview.md)
- [Información general sobre animaciones de fotogramas clave](key-frame-animations-overview.md)
- [Animar un giro 3D mediante Storyboards](how-to-animate-a-3-d-rotation-using-storyboards.md)
- [Animar un giro 3D mediante Rotation3DAnimation](how-to-animate-a-3-d-rotation-using-rotation3danimation.md)
- [Animar un giro 3D mediante cuaterniones](how-to-animate-a-3-d-rotation-using-quaternions.md)
- [Animar un giro 3D mediante fotogramas clave (QuaternionAnimationUsingKeyFrames)](animate-a-3-d-rotation-quaternionanimationusingkeyframes.md)
| 71.277778 | 373 | 0.811769 | spa_Latn | 0.520496 |
c92aca746adb2e83d31aa92cf2ec77507772040e | 6,475 | md | Markdown | onepage/validacao.md | cleydsonjr/integracao | a273729dde04b28c0ff71a7aa4667d1848c5ee28 | [
"Apache-2.0"
] | null | null | null | onepage/validacao.md | cleydsonjr/integracao | a273729dde04b28c0ff71a7aa4667d1848c5ee28 | [
"Apache-2.0"
] | null | null | null | onepage/validacao.md | cleydsonjr/integracao | a273729dde04b28c0ff71a7aa4667d1848c5ee28 | [
"Apache-2.0"
] | null | null | null | ## Validação
Segundo o MPS BR o propósito do processo de Validação é testificar que o produto ou seu componente atende aos requisitos determinados quando colocado no ambiente operacional, ou seja, confirma que esse cumpre suas especificações.
Esse processo certifica que o software corresponde às necessidades e expectativas do cliente, determinando dessa forma, o nível de qualidade do sistema/software desenvolvido. A pergunta a ser respondida aqui é " Fizemos o software correto ?". Nesse processo avaliamos se o que foi desenvolvido atende a regra de negócio do cliente e se ele literalmente está pagando por algo que supri suas necessidades, provavelmente definidas no levantamento de requisitos.
A norma pertinente a esse processo é a IEEE 1012, sendo utilizada para padronizar os processo que serão utilizados pela organização na Validação. Dentre seus processos estão a análise, revisão, inspeção, avaliação e teste de produto. A norma ajuda a definir tarefas, entradas, saídas esperadas em cada ciclo de vida e o Plano de verificação e validação, incluindo exemplos e formas que servem de diretivas.
Segundo Sommerville, existem muitos processos de software diferentes, mas todos devem incluir quatro atividades fundamentais para a engenharia de software. Entre essas 4 atividades está o processo de validação de software. Segundo o autor, o Teste de programa, em que o sistema é executado com dados de testes simulados, é a principal técnica de validação.
Para ele, esse processo é iterativo e se divide em 3, Teste de desenvolvimento, de sistema e de aceitação.
O Testes de desenvolvimento é onde os componentes do sistema são testados pelas pessoas que o desenvolveram. Ferramentas de automação de teste, como JUnit* (MASSOL e HUSTED, 2003), que podem reexecutar testes de componentes quando as novas versões dos componentes são criadas, são comumente usadas.
Já nos Testes de sistema, componentes do sistema são integrados para criar um sistema completo. Preocupando-se em encontrar os erros resultantes das interações inesperadas entre componentes e problemas de interface do componente. Também visa mostrar que o sistema satisfaz seus requisitos funcionais e não funcionais, bem como testar as propriedades emergentes do sistema.
Por último, estão os Testes de aceitação, onde o sistema é testado com dados fornecidos pelo cliente, e não com dados advindos de testes simulados.
O teste de aceitação pode revelar erros e omissões na definição dos requisitos do sistema, pois dados reais exercitam o sistema de formas diferentes dos dados de teste, revelando problemas de requisitos em que os recursos do sistema não atendam às necessidades do usuário ou o desempenho do sistema seja inaceitável.
Dessa forma, fica visível a grande importância desse processo quando se deseja produzir softwares de alta qualidade.
* JUnit - https://junit.org/junit5/
## Validação sob a ótica do SWEBOK V 3.0
Segundo o Swebok, a qualidade do software é definida como a capacidade do produto de software de satisfazer as necessidades implícitas sob condições especificadas, e como o grau em que esse produto de software atende aos requisitos estabelecidos, ressaltando assim, a importância da elaboração, manutenção e qualidade dos requisitos de software.
A qualidade de software, de acordo com o Swebok, está dividida em 4 tópicos, Fundamentos de qualidade de software, Processos de gerenciamento de qualidade de software, Considerações práticas e Ferramentas de qualidade de software.
O processo de Validação está incluso no tópico Processos de gerenciamento de qualidade de software, que define processos, proprietários de processos, requisitos para os processos, medições do processos e suas saídas e canais de feedback ao longo de todo o ciclo de vida do software.Dessa forma, o processo de Validação busca garantir que o produto cumpre com a finalidade pretendida e especificada, tendo como objetivo, juntamente com o processo de Verificação, ajudar o setor de desenvolvimento a construir o sistema com qualidade durante o ciclo de vida do software.
Sob essa perspectiva, a Validação inicia-se já no início do processo de desenvolvimento ou manutenção do software, fornecendo um exame das principais características do produto em relação às versões anteriores e às especificações a serem atendida. Esse exame, visa demonstrar se os requisitos são corretos, completos, precisos, consistentes e testáveis.
Como todo processo, a Validação também deve possuir planejamento, a fim de garantir que cada recurso, função e responsabilidade é claramente atribuído. Nessa fase serão gerados documentos, que devem descrever recursos, funções, atividades, técnicas e ferramentas a serem usadas no processo. Além disso, irá incluir fases de análise,revisão, inspeção, avaliação e teste de produtos,abrangendo em seu escopo sistemas, software e hardware.
Em todo o processo de V&V, serão abordados a gestão, comunicação, políticas e procedimentos das atividades de V&V e sua interação, bem como relatórios de defeitos e requisitos de documentação.
Assim sendo, observa-se que a Validação é um importante processo dentro de todo o ciclo de vida do software quando se pretende garantir sua qualidade e que suas saídas, quando aprovadas, servirão como entradas para o processo seguinte ou como evidências para a correção de algum ponto no software que esteja em desacordo com os requisitos estabelecidos.
## Referências
Sommerville, Ian Engenharia de Software / Ian Sommerville; tradução Ivan Bosnic e Kalinka G. de O. Gonçalves; revisão técnica Kechi Hirama. — 9. ed. — São Paulo: Pearson Prentice Hall, 2011.
PESSONI, Vinicius.Normas ISO / IEEE Importantes no Teste de Software.viniciuspessoni.com,2012.Disponível em: https://viniciuspessoni.com/2012/01/11/normas-iso-ieee-importantes-no-teste-de-software/#:~:text=O%20IEEE%20Std%201012%2D2004,os%20quais%20servem%20de%20diretivas. Acesso em: 16 de Setembro de 2020.
Verificação e validação.Wikipedia.org, 2018 . Disponível em: https://pt.wikipedia.org/wiki/Verifica%C3%A7%C3%A3o_e_valida%C3%A7%C3%A3o. Acesso em: 16 de Setembro de 2020.
IEEE Std. 1012. people.eecs.ku.edu, 2020. Disponível em: https://people.eecs.ku.edu/~hossein/Teaching/Stds/1012.pdf . Acesso em: 16 de Setembro de 2020.
SWEBOK. Guide to the Software Engineering Body of Knowledge. 2004 Version.project of the IEEE Computer Society Professional Practices Committee. Disponível em: <http://www.swebok.org/>. Acesso em: 30 de Setembro de 2020.
| 132.142857 | 568 | 0.812973 | por_Latn | 0.999884 |
c92aed6508b7c840c33320c1e8a23aad22df2bdb | 3,692 | md | Markdown | docs/relational-databases/sqlxml-annotated-xsd-schemas-xpath-queries/bulk-load-xml/annotation-interpretation-sqlxml-4-0.md | CeciAc/sql-docs.fr-fr | 0488ed00d9a3c5c0a3b1601a143c0a43692ca758 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/relational-databases/sqlxml-annotated-xsd-schemas-xpath-queries/bulk-load-xml/annotation-interpretation-sqlxml-4-0.md | CeciAc/sql-docs.fr-fr | 0488ed00d9a3c5c0a3b1601a143c0a43692ca758 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/relational-databases/sqlxml-annotated-xsd-schemas-xpath-queries/bulk-load-xml/annotation-interpretation-sqlxml-4-0.md | CeciAc/sql-docs.fr-fr | 0488ed00d9a3c5c0a3b1601a143c0a43692ca758 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-03-04T05:50:54.000Z | 2020-03-04T05:50:54.000Z | ---
title: Interprétation des annotations (SQLXML)
ms.date: 03/17/2017
ms.prod: sql
ms.prod_service: database-engine, sql-database
ms.reviewer: ''
ms.technology: xml
ms.topic: reference
helpviewer_keywords:
- annotated XSD schemas, XML Bulk Load
- XML Bulk Load [SQLXML], annotation intepretations
- annotations [SQLXML]
- bulk load [SQLXML], annotation interpretations
- annotated XDR schemas, XML Bulk Load
ms.assetid: 1c46bdb6-2812-4a13-b60b-7101c04b299f
author: MightyPen
ms.author: genemi
ms.custom: seo-lt-2019
monikerRange: =azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current
ms.openlocfilehash: 4dc5842487c0740386d97f3ec187dff144520a74
ms.sourcegitcommit: 792c7548e9a07b5cd166e0007d06f64241a161f8
ms.translationtype: MT
ms.contentlocale: fr-FR
ms.lasthandoff: 12/19/2019
ms.locfileid: "75246748"
---
# <a name="annotation-interpretation-sqlxml-40"></a>Interprétation d'annotation (SQLXML 4.0)
[!INCLUDE[appliesto-ss-asdb-xxxx-xxx-md](../../../includes/appliesto-ss-asdb-xxxx-xxx-md.md)]
Les rubriques de cette section décrivent comment le chargement en masse XML interprète les annotations dans le schéma XSD. Le comportement décrit ici s'applique également aux annotations dans le schéma XDR.
> [!NOTE]
> Les informations fournies dans ces rubriques décrivent uniquement les annotations utilisées par le chargement en masse XML lors de son traitement. Pour obtenir la liste complète des annotations pour le schéma XSD prises en charge par SQLXML 4,0, consultez [utilisation des annotations dans les schémas xsd (sqlxml 4,0)](../../../relational-databases/sqlxml-annotated-xsd-schemas-using/using-annotations-in-xsd-schemas-sqlxml-4-0.md). Pour obtenir la liste des annotations prises en charge pour les schémas XDR, consultez [schémas XDR Annotés (dépréciés dans SQLXML 4,0)](../../../relational-databases/sqlxml/annotated-xsd-schemas/annotated-xdr-schemas-deprecated-in-sqlxml-4-0.md).
## <a name="in-this-section"></a>Dans cette section
[SQL : Relationship et la règle de classement des clés (SQLXML 4,0)](../../../relational-databases/sqlxml-annotated-xsd-schemas-xpath-queries/bulk-load-xml/annotation-interpretation-sql-relationship-and-key-ordering-rule.md)
Décrit comment l’annotation **SQL : Relationship** est interprétée dans le chargement en masse XML.
[SQL : mappé (SQLXML 4,0)](../../../relational-databases/sqlxml-annotated-xsd-schemas-xpath-queries/bulk-load-xml/annotation-interpretation-sql-mapped.md)
Décrit comment l’annotation **SQL : mapped** est interprétée dans le chargement en masse XML.
[SQL : Limit-Field et SQL : limit-value (SQLXML 4,0)](../../../relational-databases/sqlxml-annotated-xsd-schemas-xpath-queries/bulk-load-xml/annotation-interpretation-sql-limit-field-and-sql-limit-value.md)
Décrit comment les annotations **SQL : Limit-Field** et **SQL : limit-value** sont interprétées dans le chargement en masse XML.
[SQL : overflow-field (SQLXML 4,0)](../../../relational-databases/sqlxml-annotated-xsd-schemas-xpath-queries/bulk-load-xml/annotation-interpretation-sql-overflow-field.md)
Décrit comment l’annotation **SQL : overflow** est interprétée dans le chargement en masse XML.
[Autres annotations (SQLXML 4,0)](../../../relational-databases/sqlxml-annotated-xsd-schemas-xpath-queries/bulk-load-xml/annotation-interpretation-other-annotations.md)
Décrit comment les annotations suivantes sont interprétées dans le chargement en masse XML : **SQL : id-prefix**, **SQL : use-cdata**, **SQL : URL-enencoder**, **SQL : is-mapping-schema**, **SQL : key-fields**.
| 72.392157 | 702 | 0.761647 | fra_Latn | 0.391634 |
c92b56b85a99a9b79e8ab01ad0aa7a7152dbf089 | 2,427 | md | Markdown | docs/examples/examples_md_nested_default/circular.md | u1735067/json-schema-for-humans | da5729d769652c9a37b05f650e7bfacb17143e00 | [
"Apache-2.0"
] | null | null | null | docs/examples/examples_md_nested_default/circular.md | u1735067/json-schema-for-humans | da5729d769652c9a37b05f650e7bfacb17143e00 | [
"Apache-2.0"
] | null | null | null | docs/examples/examples_md_nested_default/circular.md | u1735067/json-schema-for-humans | da5729d769652c9a37b05f650e7bfacb17143e00 | [
"Apache-2.0"
] | null | null | null | # Circular reference Schema
- [1. [Optional] Property Circular reference Schema > person](#person)
- [1.1. [Optional] Property Circular reference Schema > person > a1](#person_a1)
**Title:** Circular reference Schema
| Type | `object` |
| ------------------------- | ------------------------------------------------------------------------- |
| **Additional properties** | [[Any type: allowed]](# "Additional Properties of any type are allowed.") |
| | |
<details>
<summary><strong> <a name="person"></a>1. [Optional] Property Circular reference Schema > person</strong>
</summary>
<blockquote>
| Type | `object` |
| ------------------------- | ------------------------------------------------------------------------- |
| **Additional properties** | [[Any type: allowed]](# "Additional Properties of any type are allowed.") |
| **Defined in** | #/definitions/a |
| | |
<details>
<summary><strong> <a name="person_a1"></a>1.1. [Optional] Property Circular reference Schema > person > a1</strong>
</summary>
<blockquote>
| Type | `string` |
| ------------------------- | ------------------------------------------------------------------------- |
| **Additional properties** | [[Any type: allowed]](# "Additional Properties of any type are allowed.") |
| **Default** | `"Default from c"` |
| **Defined in** | #/definitions/b |
| | |
**Description:** Description from b
</blockquote>
</details>
</blockquote>
</details>
----------------------------------------------------------------------------------------------------------------------------
Generated using [json-schema-for-humans](https://github.com/coveooss/json-schema-for-humans) on date | 51.638298 | 124 | 0.337866 | eng_Latn | 0.567835 |
c92bedcfa153421a6d59ba2dc5aad7307d37d6a8 | 1,434 | md | Markdown | README.md | thesourcerer/clrmd | c81a592f3041a9ae86f4c09351d8183801e39eed | [
"MIT"
] | 355 | 2017-02-10T09:05:51.000Z | 2020-11-16T20:05:23.000Z | KeeTheft/ClrMD/README.md | gold1029/KeeThief | 53d4b81c8efe19bbf1163ed257a17bc7b09f6fe6 | [
"BSD-3-Clause"
] | 1 | 2018-05-06T16:47:22.000Z | 2018-05-06T16:47:22.000Z | KeeTheft/ClrMD/README.md | gold1029/KeeThief | 53d4b81c8efe19bbf1163ed257a17bc7b09f6fe6 | [
"BSD-3-Clause"
] | 65 | 2017-02-28T01:23:02.000Z | 2020-10-25T08:16:18.000Z | # Microsoft.Diagnostics.Runtime
`Microsoft.Diagnostics.Runtime.dll` (nicknamed "CLR MD") is a process and crash
dump introspection library. This allows you to write tools and debugger plugins
which can do thing similar to SOS and PSSCOR.
For more details, take a look at the [documentation] and [samples].
[documentation]: ./Documentation/ClrRuntime.md
[samples]: https://github.com/Microsoft/dotnetsamples/tree/master/Microsoft.Diagnostics.Runtime/CLRMD
## FAQ
Please see the [FAQ](./Documentation/FAQ.md) for more information.
## Tutorials
Here you will find a step by step walkthrough on how to use the CLR MD API.
These tutorials are meant to be read and worked through in linear order to teach
you the surface area of the API and what you can do with it.
1. [Getting Started](./Documentation/GettingStarted.md) - A brief introduction
to the API and how to create a CLRRuntime instance.
2. [The CLRRuntime Object](./Documentation/ClrRuntime.md) - Basic operations
like enumerating AppDomains, Threads, the Finalizer Queue, etc.
3. [Walking the Heap](./Documentation/WalkingTheHeap.md) - Walking objects on
the GC heap, working with types in CLR MD.
4. [Types and Fields in CLRMD](./Documentation/TypesAndFields.md) - More
information about dealing with types and fields in CLRMD.
5. [Machine Code in CLRMD](./Documentation/MachineCode.md) - Getting access to
the native code produced by the JIT or NGEN
| 39.833333 | 101 | 0.769874 | eng_Latn | 0.970368 |
c92bf46236676eb3ae1ba919d8c255387f3cffa9 | 6,122 | md | Markdown | infrastructure/lib/rest-api/README.md | m29827/Kai | b71ae8a12b3f1cb4d14cad98503ccc848e81a7cf | [
"Apache-2.0"
] | 3 | 2020-09-27T15:36:34.000Z | 2020-12-27T02:47:52.000Z | infrastructure/lib/rest-api/README.md | m29827/Kai | b71ae8a12b3f1cb4d14cad98503ccc848e81a7cf | [
"Apache-2.0"
] | 44 | 2019-10-28T09:51:56.000Z | 2021-08-12T20:50:58.000Z | infrastructure/lib/rest-api/README.md | m29827/Kai | b71ae8a12b3f1cb4d14cad98503ccc848e81a7cf | [
"Apache-2.0"
] | 6 | 2020-04-24T16:36:44.000Z | 2021-06-25T01:28:04.000Z | The Kai REST API
=========================
The Kai REST API exposes a number of endpoints whose access is restricted to members of the Kai User Pool.
Administration of graphs created via the REST API is by default restricted to the creating user, additional users can be specified when the graph is created.
The number of endpoints will grow over time and this document should be kept up-to-date with any changes. If you notice something incorrect or out of date in this document, let us know via a [Github issue](https://github.com/gchq/Kai/issues/new).
## Authorization
Access to the endpoints exposed by the Rest API is restricted to members of the Kai User Pool.
An Http request header containing a valid Cognito user identity token is required to invoke API endpoints via the execute-api. The mechanism for obtaining a token is dependent on the Cognito user pool configuration, the following example demonstrates how to create a user and obtain a token using the default Kai User Pool configuration.
```bash
#!/bin/bash
function userValueFor() {
local _PROMPT="${1}"
local _VALUE
read -p "${_PROMPT}" _VALUE
echo ${_VALUE}
}
while ([[ -z ${USER_POOL_ID} || -z ${APP_CLIENT_ID} || -z ${USERNAME} || -z ${PASSWORD} ]]) do
[[ -z ${USER_POOL_ID} ]] && USER_POOL_ID=$(userValueFor "User Pool Id: ")
[[ -z ${APP_CLIENT_ID} ]] && APP_CLIENT_ID=$(userValueFor "App Client Id: ")
[[ -z ${USERNAME} ]] && USERNAME=$(userValueFor "Username: ")
[[ -z ${PASSWORD} ]] && PASSWORD=$(userValueFor "Password: ")
done
# Create User
aws cognito-idp admin-create-user --user-pool-id ${USER_POOL_ID} --username ${USERNAME} || exit 1
# Set User Password
aws cognito-idp admin-set-user-password --user-pool-id ${USER_POOL_ID} --username ${USERNAME} --password ${PASSWORD} --permanent || exit 1
# Enable Admin User Password Authentication
aws cognito-idp update-user-pool-client --user-pool-id ${USER_POOL_ID} --client-id ${APP_CLIENT_ID} --explicit-auth-flows ALLOW_ADMIN_USER_PASSWORD_AUTH ALLOW_REFRESH_TOKEN_AUTH || exit 1
# Authenticate and obtain IdToken
aws cognito-idp admin-initiate-auth --user-pool-id ${USER_POOL_ID} --client-id ${APP_CLIENT_ID} --auth-flow ADMIN_USER_PASSWORD_AUTH --auth-parameters USERNAME=${USERNAME},PASSWORD=${PASSWORD} || exit 1
```
Once an IdToken has been obtained the Rest API endpoint can be called by passing the token in the "Authorization" header, for example using curl to retrieve all graphs:
```bash
curl -H "Authorization: <IdToken>" https://<restapi-id>.execute-api.<aws-region>.amazonaws.com/prod/graphs
```
## Endpoints
### The Graphs resource
The Graphs resource enables creation, deletion and retrieval of Graphs managed by Kai.
#### GET /graphs
Retrieves all graphs objects from the backend database. At present this only includes the graphName and its current state but this is likely to change as the project grows.
A graph can be in different states. At present these states can be:
* DEPLOYMENT_QUEUED
* DEPLOYMENT_IN_PROGRESS
* DEPLOYED
* DEPLOYMENT_FAILED
* DELETION_QUEUED
* DELETION_FAILED
* DELETION_IN_PROGRESS
Once a graph deployment is undeployed, it is removed from the backend database
Example response:
```json
[
{
"graphName": "roadTraffic",
"currentState": "DEPLOYED"
},
{
"graphName": "basicGraph",
"currentState": "DELETION_QUEUED"
}
]
```
#### GET /graphs/{graphName}
Retrieves a single graph from the backend database. If the Graph Id is not found, a 404 response is sent. If the requesting user is not a configured administrator of the graph a 403 response is returned.
Example response:
```json
{
"graphName": "roadTraffic",
"currentState": "DEPLOYED"
}
```
#### POST /graphs
Creates and deploys a new graph. This endpoint is asynchronous meaning it will return before deploying a graph which takes around 5 minutes. At present, you need to provide a Gaffer schema which is split into two parts: elements and types, as well as a graphName which must be unique. This endpoint will respond with a simple 201 return code. If the user requests a graph which is already created, A 400 response will be sent, along with an error message. There is a constraint in gaffer-docker that graph names have to be lowercase alphanumerics. We hope to address this in a bugfix to allow uppercase alphanumerics too. By default only the creating user has administration access to the graph through the REST API. If you wish to specify additional users with administration privileges they can be listed in an optional "administrators" property. If an attempt is made to configure users who are not members of the Cognito User Pool a 400 response will be returned.
Example request body:
```json
{
"graphName": "basic",
"administrators": [],
"schema": {
"elements": {
"edges": {
"BasicEdge": {
"source": "vertex",
"destination": "vertex",
"directed": "true",
"properties": {
"count": "count"
}
}
}
},
"types": {
"types": {
"vertex": {
"class": "java.lang.String"
},
"count": {
"class": "java.lang.Integer",
"aggregateFunction": {
"class": "uk.gov.gchq.koryphe.impl.binaryoperator.Sum"
}
},
"true": {
"description": "A simple boolean that must always be true.",
"class": "java.lang.Boolean",
"validateFunctions": [
{
"class": "uk.gov.gchq.koryphe.impl.predicate.IsTrue"
}
]
}
}
}
}
}
```
#### DELETE /graphs/{graphName}
Deletes a graph deployment from the platform. This endpoint is asynchronous meaning that it will respond before the graph deployment is removed. Once the graph deployment is removed, the graph will be removed from the backend database. If the requested graphName is not present or is not in the backend database at the start, a 400 error is returned. If the user is not an administrator a 403 response is returned. Otherwise a 202 status code is returned.
| 43.728571 | 967 | 0.700098 | eng_Latn | 0.963516 |
c92c60c9258a6f0985f58adf5d38177090c468d1 | 10,759 | md | Markdown | articles/service-bus-messaging/service-bus-messaging-sql-filter.md | sonquer/azure-docs.pl-pl | d8159cf8e870e807bd64e58188d281461b291ea8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/service-bus-messaging/service-bus-messaging-sql-filter.md | sonquer/azure-docs.pl-pl | d8159cf8e870e807bd64e58188d281461b291ea8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/service-bus-messaging/service-bus-messaging-sql-filter.md | sonquer/azure-docs.pl-pl | d8159cf8e870e807bd64e58188d281461b291ea8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Odwołanie do składni Azure Service Bus sqlfilter | Microsoft Docs
description: Ten artykuł zawiera szczegółowe informacje na temat gramatyki xmlfilter. Element sqlfilter obsługuje podzestaw standardu SQL-92.
services: service-bus-messaging
documentationcenter: na
author: spelluru
manager: timlt
editor: ''
ms.assetid: ''
ms.service: service-bus-messaging
ms.devlang: na
ms.topic: article
ms.tgt_pltfrm: na
ms.workload: na
ms.date: 09/05/2018
ms.author: spelluru
ms.openlocfilehash: d5a8e165fcee23c5feecd5935983dd77d3ec6c30
ms.sourcegitcommit: b5d646969d7b665539beb18ed0dc6df87b7ba83d
ms.translationtype: MT
ms.contentlocale: pl-PL
ms.lasthandoff: 01/26/2020
ms.locfileid: "76759667"
---
# <a name="sqlfilter-syntax"></a>Składnia elementu SQLFilter
Obiekt *sqlfilter* jest wystąpieniem [klasy sqlfilter](/dotnet/api/microsoft.servicebus.messaging.sqlfilter)i reprezentuje wyrażenie filtru oparte na języku SQL, które jest oceniane względem [BrokeredMessage](/dotnet/api/microsoft.servicebus.messaging.brokeredmessage). Element sqlfilter obsługuje podzestaw standardu SQL-92.
W tym temacie przedstawiono szczegółowe informacje na temat gramatyki xmlfilter.
```
<predicate ::=
{ NOT <predicate> }
| <predicate> AND <predicate>
| <predicate> OR <predicate>
| <expression> { = | <> | != | > | >= | < | <= } <expression>
| <property> IS [NOT] NULL
| <expression> [NOT] IN ( <expression> [, ...n] )
| <expression> [NOT] LIKE <pattern> [ESCAPE <escape_char>]
| EXISTS ( <property> )
| ( <predicate> )
```
```
<expression> ::=
<constant>
| <function>
| <property>
| <expression> { + | - | * | / | % } <expression>
| { + | - } <expression>
| ( <expression> )
```
```
<property> :=
[<scope> .] <property_name>
```
## <a name="arguments"></a>Argumenty
- `<scope>` jest opcjonalnym ciągiem wskazującym zakres `<property_name>`. Prawidłowe wartości to `sys` lub `user`. Wartość `sys` wskazuje zakres systemu, gdzie `<property_name>` jest publiczną nazwą właściwości [klasy BrokeredMessage](/dotnet/api/microsoft.servicebus.messaging.brokeredmessage). `user` wskazuje zakres użytkownika, gdzie `<property_name>` jest kluczem słownika [klasy BrokeredMessage](/dotnet/api/microsoft.servicebus.messaging.brokeredmessage) . zakres `user` jest domyślnym zakresem, jeśli nie określono `<scope>`.
## <a name="remarks"></a>Uwagi
Próba uzyskania dostępu do nieistniejącej właściwości systemu jest błędem, podczas gdy próba uzyskania dostępu do nieistniejącej właściwości użytkownika nie jest błędem. Zamiast tego nieistniejąca Właściwość użytkownika jest obliczana wewnętrznie jako nieznana wartość. Nieznana wartość jest traktowana specjalnie podczas obliczania operatora.
## <a name="property_name"></a>property_name
```
<property_name> ::=
<identifier>
| <delimited_identifier>
<identifier> ::=
<regular_identifier> | <quoted_identifier> | <delimited_identifier>
```
### <a name="arguments"></a>Argumenty
`<regular_identifier>` jest ciągiem przedstawionym przez następujące wyrażenie regularne:
```
[[:IsLetter:]][_[:IsLetter:][:IsDigit:]]*
```
Ta Gramatyka oznacza dowolny ciąg, który rozpoczyna się od litery, po której następuje jeden lub więcej podkreśleń/liter/cyfr.
`[:IsLetter:]` oznacza dowolny znak Unicode, który jest kategoryzowany jako litera Unicode. `System.Char.IsLetter(c)` zwraca `true`, jeśli `c` jest literą Unicode.
`[:IsDigit:]` oznacza dowolny znak Unicode, który jest kategoryzowany jako cyfra dziesiętna. `System.Char.IsDigit(c)` zwraca `true`, jeśli `c` jest cyfrą Unicode.
`<regular_identifier>` nie może być zastrzeżonym słowem kluczowym.
`<delimited_identifier>` to dowolny ciąg, który jest ujęty w nawiasy kwadratowe ([]). Prawy nawias kwadratowy jest reprezentowany jako dwa prawy nawias kwadratowy. Poniżej przedstawiono przykłady `<delimited_identifier>`:
```
[Property With Space]
[HR-EmployeeID]
```
`<quoted_identifier>` to dowolny ciąg, który jest ujęty w znaki podwójnego cudzysłowu. Podwójny cudzysłów w identyfikatorze jest reprezentowany jako dwa podwójne cudzysłowy. Nie zaleca się używania identyfikatorów w cudzysłowie, ponieważ można je łatwo pomylić z stałą typu String. Jeśli to możliwe, należy użyć oddzielonego identyfikatora. Poniżej przedstawiono przykład `<quoted_identifier>`:
```
"Contoso & Northwind"
```
## <a name="pattern"></a>znaczne
```
<pattern> ::=
<expression>
```
### <a name="remarks"></a>Uwagi
`<pattern>` musi być wyrażeniem, które jest oceniane jako ciąg. Jest używany jako wzorzec dla operatora LIKE. Może zawierać następujące symbole wieloznaczne:
- `%`: dowolny ciąg składający się z zero lub więcej znaków.
- `_`: dowolny pojedynczy znak.
## <a name="escape_char"></a>escape_char
```
<escape_char> ::=
<expression>
```
### <a name="remarks"></a>Uwagi
`<escape_char>` musi być wyrażeniem, które jest oceniane jako ciąg o długości 1. Jest używany jako znak ucieczki dla operatora LIKE.
Na przykład `property LIKE 'ABC\%' ESCAPE '\'` dopasowuje `ABC%` zamiast ciągu rozpoczynającego się od `ABC`.
## <a name="constant"></a>Stałe
```
<constant> ::=
<integer_constant> | <decimal_constant> | <approximate_number_constant> | <boolean_constant> | NULL
```
### <a name="arguments"></a>Argumenty
- `<integer_constant>` jest ciągiem liczb, które nie są ujęte w cudzysłów i nie zawierają punktów dziesiętnych. Wartości są przechowywane jako `System.Int64` wewnętrznie i zgodne z tym samym zakresem.
Są to przykłady długich stałych:
```
1894
2
```
- `<decimal_constant>` jest ciągiem liczb, które nie są ujęte w cudzysłów i zawierają separator dziesiętny. Wartości są przechowywane jako `System.Double` wewnętrznie i są zgodne z tym samym zakresem/dokładnością.
W przyszłej wersji ten numer może być przechowywany w innym typie danych w celu obsługi dokładnej semantyki liczb, dlatego nie należy polegać na tym, że podstawowy typ danych jest `System.Double` dla `<decimal_constant>`.
Poniżej przedstawiono przykłady stałych dziesiętnych:
```
1894.1204
2.0
```
- `<approximate_number_constant>` to liczba zapisywana w notacji wykładniczej. Wartości są przechowywane jako `System.Double` wewnętrznie i są zgodne z tym samym zakresem/dokładnością. Poniżej przedstawiono przykłady przybliżonych stałych liczbowych:
```
101.5E5
0.5E-2
```
## <a name="boolean_constant"></a>boolean_constant
```
<boolean_constant> :=
TRUE | FALSE
```
### <a name="remarks"></a>Uwagi
Stałe logiczne są reprezentowane przez słowa kluczowe **true** lub **false**. Wartości są przechowywane jako `System.Boolean`.
## <a name="string_constant"></a>string_constant
```
<string_constant>
```
### <a name="remarks"></a>Uwagi
Stałe ciągów są ujęte w znaki pojedynczego cudzysłowu i zawierają wszystkie prawidłowe znaki Unicode. Pojedynczy cudzysłów osadzony w stałej ciągu jest reprezentowany jako dwa znaki pojedynczego cudzysłowu.
## <a name="function"></a>funkcyjn
```
<function> :=
newid() |
property(name) | p(name)
```
### <a name="remarks"></a>Uwagi
Funkcja `newid()` zwraca element **System. GUID** wygenerowany przez metodę `System.Guid.NewGuid()`.
Funkcja `property(name)` zwraca wartość właściwości, do której odwołuje się `name`. Wartość `name` może być dowolnym prawidłowym wyrażeniem zwracającym wartość ciągu.
## <a name="considerations"></a>Zagadnienia do rozważenia
Rozważ użycie następujących semantyki [sqlfilter](/dotnet/api/microsoft.servicebus.messaging.sqlfilter) :
- Nazwy właściwości nie uwzględniają wielkości liter.
- Operatory stosują C# niejawną semantykę konwersji wszędzie tam, gdzie to możliwe.
- Właściwości systemu są właściwościami publicznymi ujawnianymi w wystąpieniach [BrokeredMessage](/dotnet/api/microsoft.servicebus.messaging.brokeredmessage) .
Rozważmy następujące `IS [NOT] NULL` semantyki:
- `property IS NULL` jest oceniane jako `true`, jeśli właściwość nie istnieje lub wartość właściwości jest `null`.
### <a name="property-evaluation-semantics"></a>Semantyka oceny właściwości
- Próba oszacowania nieistniejącej właściwości systemowej zgłasza wyjątek [filtruexception](/dotnet/api/microsoft.servicebus.messaging.filterexception) .
- Właściwość, która nie istnieje, jest obliczana wewnętrznie jako **nieznana**.
Nieznana Ocena w operatorach arytmetycznych:
- W przypadku operatorów binarnych, jeśli po lewej i/lub prawej stronie operandów jest oceniane jako **nieznany**, wynik jest **nieznany**.
- W przypadku operatorów jednoargumentowych, jeśli operand jest oceniany jako **nieznany**, wynik jest **nieznany**.
Nieznana Ocena w binarnych operatorach porównania:
- Jeśli po lewej i/lub prawej stronie operandów jest oceniane jako **nieznany**, wynik jest **nieznany**.
Nieznana Ocena w `[NOT] LIKE`:
- Jeśli którykolwiek operand jest oceniany jako **nieznany**, wynik jest **nieznany**.
Nieznana Ocena w `[NOT] IN`:
- Jeśli argument operacji po lewej stronie jest oceniany jako **nieznany**, wynik jest **nieznany**.
Nieznana Ocena w operatorze **i** :
```
+---+---+---+---+
|AND| T | F | U |
+---+---+---+---+
| T | T | F | U |
+---+---+---+---+
| F | F | F | F |
+---+---+---+---+
| U | U | F | U |
+---+---+---+---+
```
Nieznana Ocena w operatorze **lub** :
```
+---+---+---+---+
|OR | T | F | U |
+---+---+---+---+
| T | T | T | T |
+---+---+---+---+
| F | T | F | U |
+---+---+---+---+
| U | T | U | U |
+---+---+---+---+
```
### <a name="operator-binding-semantics"></a>Semantyka powiązania operatora
- Operatory porównania, takie jak `>`, `>=`, `<`, `<=`, `!=`i `=`, są zgodne z tą samą semantyką jak powiązanie C# operatora w promocjach typu danych i konwersje niejawne.
- Operatory arytmetyczne, takie jak `+`, `-`, `*`, `/`i `%`, są zgodne z tą samą C# semantyką jak powiązanie operatora w promocjach typu danych i konwersje niejawne.
## <a name="next-steps"></a>Następne kroki
- [Klasa sqlfilter (.NET Framework)](/dotnet/api/microsoft.servicebus.messaging.sqlfilter)
- [Klasa sqlfilter (.NET Standard)](/dotnet/api/microsoft.azure.servicebus.sqlfilter)
- [Klasa SQLRuleAction](/dotnet/api/microsoft.servicebus.messaging.sqlruleaction)
| 37.487805 | 538 | 0.681755 | pol_Latn | 0.999616 |
c92ce0333c816de723ff5e0afe4b43366f4e4bd4 | 39 | md | Markdown | _includes/03-links.md | arjseth/markdown-portfolio | 6ae59aa95a81145f978ab9cc18a4dfeba7c5eaed | [
"MIT"
] | null | null | null | _includes/03-links.md | arjseth/markdown-portfolio | 6ae59aa95a81145f978ab9cc18a4dfeba7c5eaed | [
"MIT"
] | 5 | 2021-05-03T14:50:09.000Z | 2021-05-04T01:38:53.000Z | _includes/03-links.md | arjseth/markdown-portfolio | 6ae59aa95a81145f978ab9cc18a4dfeba7c5eaed | [
"MIT"
] | null | null | null | [Wkipedia](https://www.wikipedia.org/)
| 19.5 | 38 | 0.717949 | zul_Latn | 0.158319 |
c92ce53f5f7263b024be7fa2162cf1f949afcb33 | 8,473 | md | Markdown | articles/talent/email-templates.md | MicrosoftDocs/Dynamics-365-Operations.sv-se | 90cb258993f991b2ce1b67078a6519e342608a4e | [
"CC-BY-4.0",
"MIT"
] | 3 | 2020-05-18T17:14:56.000Z | 2022-03-02T03:46:34.000Z | articles/talent/email-templates.md | MicrosoftDocs/Dynamics-365-Operations.sv-se | 90cb258993f991b2ce1b67078a6519e342608a4e | [
"CC-BY-4.0",
"MIT"
] | 7 | 2017-12-13T12:57:02.000Z | 2019-04-30T11:46:04.000Z | articles/talent/email-templates.md | MicrosoftDocs/Dynamics-365-Operations.sv-se | 90cb258993f991b2ce1b67078a6519e342608a4e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Skapa e-postmallar i Attract
description: Det här avsnittet ger information om e-postmallarna som du kan skapa och använda i Microsoft Dynamics 365 Talent - Attract.
author: andreabichsel
manager: AnnBe
ms.date: 10/19/2018
ms.topic: article
ms.prod: ''
ms.service: dynamics-365-talent
ms.technology: ''
ms.search.form: ''
audience: Application User
ms.reviewer: anbichse
ms.search.scope: Talent, Core
ms.custom: 7521
ms.assetid: 3b953d5f-6325-4c9e-8b9b-6ab0458a73f8
ms.search.region: Global
ms.author: anbichse
ms.search.validFrom: 2018-10-15
ms.dyn365.ops.version: Talent October 2018 update
ms.openlocfilehash: 55c12010cfd055ee6977f50e566b70f76a2e1682
ms.sourcegitcommit: 199848e78df5cb7c439b001bdbe1ece963593cdb
ms.translationtype: HT
ms.contentlocale: sv-SE
ms.lasthandoff: 10/13/2020
ms.locfileid: "4462550"
---
# <a name="create-email-templates-in-attract"></a>Skapa e-postmallar i Attract
[!include [banner](includes/banner.md)]
Genom att använda biblioteket för e-postmallar kan administratörer skapa ett enhetligt tema och profilering för alla e-postmeddelanden som skickas via Microsoft Dynamics 365 Talent: Attract eller erbjudande. Administratörer kan också anordna en samling innehåll för e-postmallar som andra användare kan använda. Anställningsteamet kan använda mallarna i arbetsflödet för att effektivare skicka e-post. Vissa e-postmeddelanden har konfigurerats att skickas automatiskt och administratören kan använda biblioteket för e-postmallar för att anpassa innehållet för dessa e-postmeddelanden.
> [!NOTE]
> Organisationen måste ha tillägget för omfattande anställning om du vill använda e-postmallar.
## <a name="global-template-configurations"></a>Konfiguration av global mall
För att skapa konsekvent profilering för alla e-postmeddelanden måste administratören först ställa in globalt sidhuvud och sidfot för alla e-postmallar. I Administrationscenter på fliken **Inställningar för e-postmall** i avsnittet **rubrik** kan administratör överföra en bild som ska användas som sidhuvud eller banderoll för alla e-postmeddelanden. Bilden kanske är företagets logotyp, ett brevhuvud eller någon annan representativ bild. Vi rekommenderar att bredden är mellan 25 och 800 pixlar och att höjden är mellan 25 och 150 pixlar, eftersom dessa mått är optimala för de flesta e-postklienter, till exempel Microsoft Outlook. Bilden måste vara en JPEG-, JPG-, PNG- eller SVG-fil och filen får inte vara mindre än 1 megabyte (MB). När en bild har överförts genereras och visas en förhandsgranskning av sidhuvudet. Om sidhuvudets bild måste tas bort eller ersättas, kan administratören använda alternativet **Ta bort** ovanför förhandsgranskningen.
I avsnittet **sidfot** kan administratören ge länkar till företagets sekretesspolicy för kommunikation och till de villkor som gäller. De här länkarna ingår i en sidfot som genereras automatiskt. Därefter visas en förhandsgranskning av den här sidfoten. Administratören kan också välja ett visst språk som e-postsidfötter ska skickas som en del av alla e-postmeddelanden. Samma språkkonfiguration kommer också att användas för att kombinera intervjuöversiktstabellen.
Kom ihåg att spara dina ändringar innan du stänger administratörscentret.
> [!NOTE]
> Sidhuvudet och sidfoten är globala inställningar för alla e-postmeddelanden. Därför visas de i e-postmeddelanden som skickas via Attract. Om inställningarna inte är konfigurerade lämnas sidhuvud- och sidfotstexten utanför alla e-postmeddelanden.
## <a name="email-template-library"></a>Bibliotek för e-postmallar
När den globala mallkonfigurationer är inställd kan administratör börja skapa och anordna mallar för e-postmeddelanden som skickas från Attract och erbjudande. Biblioteket för e-postmallar är endast tillgänglig för administratörer. För att öppna biblioteket på den huvudsakliga navigeringsmenyn, välj fliken **e-postmallar**. Biblioteket är kategoriserad efter olika aktiviteter i Attract e-post ska skickas för, t.ex tidsplanering, bedömning och skapa jobb och erbhjudanden. Administratören kan välja en kategori för att visa alla e-posttyper som är kopplade till aktiviteten. Markera exempelvis **tidsplanering** för att visa olika typer av e-post som skickas under planeringsprocessen och alla mallar som är tillgängliga för varje typ av e-post. Varje delavsnitt i en kategori representerar en typ av e-post.
Vissa typer av e-postmeddelandet kan ha fler än en mottagare. I till exempel kategorin **tidsplanering** skickas e-postmeddelanden när du behöver skicka sammanfattning av tidsplanen för intervjuer till både kandidater och intervjuare. Varje avsnitt har två huvudsakliga kolumner: **Malltitel** och **Mottagare**. Varje rad i avsnittet representerar en enda mall för en typ av e-post. En låssymbol visas först i raden för varje mall. Den här symbolen anger att mallen är en standardmall som ingår i Attract och att den inte kan tas bort. Administratören kan använda knappen med tre punkter för alla mallar (**...**) för att duplicera mallen, ange den som standardmall eller ta bort den. När en mall är en standardmall, kan ett av två problem uppstå. Beteendet framgår av brickan eller brickorna som visas på raden för mallen:
- **Standard** – Denna bricka anger att mallen är standardmallen för e-post som skickas och att informationen anges i den när en användare skickar e-post för den specifika typen.
- **Standard** + **Skickas automatiskt** – kombinationen av märken som indikerar att mallen är den aktiva mallen för systemgenererade e-postmeddelanden som skickas automatiskt.
Om du vill redigera en mall markerar du raden och gör ändringar i mallen.
> [!NOTE]
> Varje mottagare av en viss typ av e-postmeddelandet har en standardmall. Alla Attract-standardmallar ställs in som standardmallar tills administratören skapar en ny mall för en viss typ av e-post och anger den som standardmall.
## <a name="create-a-template"></a>Skapa en mall
Om du vill skapa en mall väljer du **+ Ny mall** i övre högra hörnet av biblioteket för e-postmallar. Om du vill välja vilken typ av e-postmeddelande som du skapar väljer du mallen för mottagaren, processen och evenemanget som e-postmeddelandet ska skickas för. Markera sedan **Skapa**.
Mallen öppnas i redigeringsvyn, och du kan ge mallen ett namn. Om mallen t.ex. är avsedd för kandidater från ett universitet i USA men har innehåll på franska kan du ange **Universitet\_USA\_Franska** som rubrik. Rubrik, ämne och brödtext för alla mallar kan stödja andra språk än engelska.
Fältet **Till** för en mall kan inte redigeras, eftersom du redan har markerat mottagaren när mallen skapades.
Kan du lägga till personer såsom **Rekryterare** eller **Anställande chef** till karbonkopiaraden (Cc). När e-postmeddelandet skickas ersätts automatiskt rollerna med lämpliga användare baserat på jobbets kontext.
Ämnesrad och brödtext stöder platshållare. Du kan infoga platshållare genom att skriva **\#** och sedan markera lämplig platshållaren i listrutan som slutförs automatiskt. Lista över tillgängliga platshållare visas till höger på sidan. När e-postmeddelandet skickas ersätts automatiskt platshållarna med lämpliga användare baserat på jobbets kontext och på mottagaren. Exempelvis innehåller en mall för ett e-postmeddelande som skickas till kandidater platshållaren \#{kandidat\_namn}. När e-postmeddelandet skickas till en annan kandidat som heter Cameron, ersätts platshållaren med Camerons namn.
Brödtextredigeraren är en textredigerare som låter dig utföra och formatera text. Du kan också infoga hyperlänkar och ankare.
När du har skapat en mall för en viss typ av e-post, välj knappen med tre punkter (**...**) på raden för mallen och ange den som standardmall.
## <a name="consume-templates"></a>Förbruka mallar
När anställningsteamet skickar ett e-postmeddelande, kan du använda mallar som skapas av administratören. Om flera mallar har skapats för den e-post som en användare skickar, visas en nedrullningsbar lista i arbetsflödet för e-postkomposition. Standardmallen anges automatiskt, men användaren kan välja en annan mall.
> [!NOTE]
> För e-postmeddelanden som skickas automatiskt, kan du skapa flera mallar. Men endast en mall kan anges som den aktiva mallen. Eftersom processen har utlösts av händelser, kan endast administratören avgöra vilken mall som ska användas baserat på kombinationen av brickorna **Standard** och **Skickas automatiskt** i biblioteket för mallar.
[!INCLUDE[footer-include](../includes/footer-banner.md)] | 98.523256 | 956 | 0.809395 | swe_Latn | 0.999941 |
c92da1531359a03c356ce8e7425627e5ec42b8f6 | 1,551 | md | Markdown | docs/content/functions/findRe.md | sidmusa/hugo | 58245a29dfe8eac504b640461ea4040e831c10e1 | [
"Apache-2.0"
] | 1 | 2019-03-25T02:28:43.000Z | 2019-03-25T02:28:43.000Z | docs/content/functions/findRe.md | sidmusa/hugo | 58245a29dfe8eac504b640461ea4040e831c10e1 | [
"Apache-2.0"
] | null | null | null | docs/content/functions/findRe.md | sidmusa/hugo | 58245a29dfe8eac504b640461ea4040e831c10e1 | [
"Apache-2.0"
] | 1 | 2020-02-07T03:07:41.000Z | 2020-02-07T03:07:41.000Z | ---
title: findRE
description: Returns a list of strings that match the regular expression.
godocref:
date: 2017-02-01
publishdate: 2017-02-01
lastmod: 2017-02-01
categories: [functions]
menu:
docs:
parent: "functions"
#tags: [regex]
signature: ["findRE PATTERN INPUT [LIMIT]"]
workson: []
hugoversion:
relatedfuncs: []
deprecated: false
aliases: []
---
By default all matches will be included. The number of matches can be limitted with an optional third parameter.
The example below returns a list of all second level headers (`<h2>`) in the content:
```
{{ findRE "<h2.*?>(.|\n)*?</h2>" .Content }}
```
You can limit the number of matches in the list with a third parameter. The following example shows how to limit the returned value to just one match (or none, if there are no matched substrings):
```
{{ findRE "<h2.*?>(.|\n)*?</h2>" .Content 1 }}
<!-- returns ["<h2 id="#foo">Foo</h2>"] -->
```
{{% note %}}
Hugo uses Golang's [Regular Expression package](https://golang.org/pkg/regexp/), which is the same general syntax used by Perl, Python, and other languages but with a few minor differences for those coming from a background in PCRE. For a full syntax listing, see the [GitHub wiki for re2](https://github.com/google/re2/wiki/Syntax).
If you are just learning RegEx, or at least Golang's flavor, you can practice pattern matching in the browser at <https://regex101.com/>.
{{% /note %}}
[partials]: /templates/partials/
[`plainify`]: /functions/plainify/
[toc]: /content-management/toc/
[`urlize`]: /functions/urlize
| 32.3125 | 333 | 0.707286 | eng_Latn | 0.982104 |
c92dd9925d693229ddad7e30ad610ad5aabb877f | 2,323 | md | Markdown | app/mortar/README.md | Matrix-K/Go-Template | 326ef76bd6d1911190d51e42e608c32d5dcc1a98 | [
"MIT"
] | 8 | 2021-03-14T04:10:55.000Z | 2022-03-21T12:15:22.000Z | app/mortar/README.md | Matrix-K/Go-Template | 326ef76bd6d1911190d51e42e608c32d5dcc1a98 | [
"MIT"
] | null | null | null | app/mortar/README.md | Matrix-K/Go-Template | 326ef76bd6d1911190d51e42e608c32d5dcc1a98 | [
"MIT"
] | 1 | 2021-08-01T00:04:26.000Z | 2021-08-01T00:04:26.000Z | # /app/mortar
Code in this directory is related to Mortar and uber-fx
- [Mortar Providers](https://github.com/go-masonry/mortar/tree/master/providers) invocations.
- Builders
- Your constructors wrapped as `fx.Option`
- Tracing/Monitoring/Logger implicit configurations
## HTTP
Constructors, options, interceptors and everything related to HTTP can be found in [http.go](http.go)
## Monitoring
This template is ready to work with a Prometheus service.
You need to configure it to expect a metric on this service default internal REST port.
```yml
mortar:
# Web server related configuration
server:
...
rest:
...
internal:
port: 5382
```
By default it's `:5382/metrics`
Constructors, options and everything else can be found in [metrics.go](metrics.go).
## Tracing
This template is assuming you will use Jaeger service.
In order for the bundled client to connect your Jaeger service you need to export some ENVIRONMENT variables.
```sh
export JAEGER_AGENT_HOST = localhost
export JAEGER_AGENT_PORT = 6831
export JAEGER_SAMPLER_TYPE = const
export JAEGER_SAMPLER_PARAM = 1
```
They are included in the [`makefile`](../../Makefile), when you execute `make run` they are exported.
Constructors, options and everything else can be found in [tracing.go](tracing.go).
## Logger
This template is using the [zerolog](https://github.com/rs/zerolog) library.
Zerolog can be configured to output in JSON format which is useful in production or the Console format which is useful for debug/local environments.
By default it is configured to use the Console format.
You can export `SERVER_LOGGER_CONSOLE=false` environment variable to disable this behavior in production or change the [`config.yml`](../../config/config.yml) file.
Constructors, options and everything else can be found in [logger.go](logger.go).
## Config
This template is using the [viper](https://github.com/spf13/viper) library.
Constructors, options and everything else can be found in [config.go](config.go).
## Authentication
This template doesn't enforce any Authentication. However there is a sample code showing how you can parse a JWT if found.
Default usage can be found in [`../validations/auth.go`](../validations/auth.go)
Constructors, options and everything else can be found in [auth.go](auth.go).
| 32.263889 | 164 | 0.758932 | eng_Latn | 0.982169 |
c92deb0e91dabfef16fdf5da1471fc1d8f93294a | 1,045 | md | Markdown | content/games/The_Wasted_Lands/index.zh-cn.md | itey/metabd | 263376ea70afea08cbc752c7117928826d2ec61a | [
"MIT"
] | null | null | null | content/games/The_Wasted_Lands/index.zh-cn.md | itey/metabd | 263376ea70afea08cbc752c7117928826d2ec61a | [
"MIT"
] | 6 | 2022-03-14T18:35:35.000Z | 2022-03-28T18:43:54.000Z | content/games/The_Wasted_Lands/index.zh-cn.md | itey/metabd | 263376ea70afea08cbc752c7117928826d2ec61a | [
"MIT"
] | null | null | null | ---
title: "The Wasted Lands"
description: "Puzzle RPG Strategy in a Post-Apocalypse Metaverse"
lead: "Puzzle RPG Strategy in a Post-Apocalypse Metaverse"
date: 2022-02-28T12:46:36.266+0800
lastmod: 2022-02-28T12:46:36.266+0800
draft: false
featuredImage: ["100_the-wasted-lands.jpg"]
score: "78"
status: "Live"
blockchain: ["Polygon"]
nft_support: "Yes"
free_to_play: "Yes"
play_to_earn: ["Crypto"]
website: "https://thewastedlands.io/?utm_source=PlayToEarn.net&utm_medium=organic&utm_campaign=gamepage"
twitter: "https://twitter.com/thewastedlands?s=20"
discord: "https://discord.com/invite/thewastedlands"
telegram: "https://t.me/TheWastedLands"
github:
youtube:
twitch:
facebook:
instagram:
reddit:
medium:
steam:
gitbook: "https://thewastedlands.io/white-paper"
googleplay:
appstore:
categories: ["games"]
games: ["PVP","Strategy","Turn-based"]
toc: false
pinned: false
weight:
---
The Wasted Lands is a NFT Game where you can Immerse yourself in a world of adventure across the post-apocolyptic world with our PVP mode! | 26.794872 | 138 | 0.751196 | eng_Latn | 0.351364 |
c92e13dc1371e4a641ac8acd9b0010d607aaed5c | 16,614 | markdown | Markdown | _posts/2019-10-06-wtr-primer.markdown | Markovictory/markovictory.github.io | 33a51b363d4ba7c28a313139e98971fac17a81ef | [
"MIT"
] | null | null | null | _posts/2019-10-06-wtr-primer.markdown | Markovictory/markovictory.github.io | 33a51b363d4ba7c28a313139e98971fac17a81ef | [
"MIT"
] | null | null | null | _posts/2019-10-06-wtr-primer.markdown | Markovictory/markovictory.github.io | 33a51b363d4ba7c28a313139e98971fac17a81ef | [
"MIT"
] | null | null | null | ---
layout: post
title: "Flesh and Blood Primer"
date: 2019-10-06 12:00:00 +0530
categories: flesh-and-blood welcome-to-rathe primer
---
This is only the beginning
---
New Zealand based game design, development, and publishing studio ‘Legend Story Studios’ is hot off the presses releasing their brand new trading card game ‘Flesh and Blood’ with its debut expansion ‘Welcome to Rathe’ in the coming days (October 11th) across the USA, Australia, and New Zealand.
The philosophy of the studio is strongly centered around community and bringing people together (in person) through the medium of games.
>“Every time people come together in the Flesh and Blood to play our game, we achieve our goal.” - [Source][about]
The game of ‘Flesh and Blood’ is drastically different from any other in my experience with playing card games. When I was given the opportunity to learn to play the game ahead of the World Premier event in late August this year I was initially taken aback.
The game pushed a lot of boundaries that I was concerned would make certain cards and strategies homogenous and eventually boring or repetitive. Each card in the game can serve many functions at any one time so any initial evaluation is vague. I thought that cards would be pigeon-holed into their most valuable function a majority of the time, and that cards which didn’t have a defined function weren’t good enough or interesting to play with, i.e. a card that is better at attacking than defending should mainly if not always be used for attacking.
Oh, how I was ***wrong***.
After a good many games (*you stop counting once you’re having too much fun*) I can confidently and safely say that my assumption is far from the truth, and that I am so glad about that fact. I would describe each game of ‘Flesh and Blood’ as a delicate and deadly dance with your opponent. Where every resource, decision, and piece of information that you can gather, make, or deduce is vital to the final outcome of who gets to be declared victorious.
**This is the type of game I’ve been searching for.**
A game where the player who gets to make the most out of what they have will be able to influence the result in their favour.
The main driving forces behind this type of gameplay is directly related by the design principles set out for ‘Flesh and Blood’:
- **Start Full** (Game begins fast and slows down, avoiding the need and risk of building incremental resources, e.g. hitting land drops and making plays on curve in Magic: the Gathering.)
- **Reduce Variance** (Eliminating scenarios where chance creates “non-games”, once again e.g. missing land drops or taking a multiple mulligans in Magic: the Gathering.)
- **Every Card Counts** (If a card is in your deck it better be useful when you draw it, and not a silver bullet to fetch up on demand. You will play games that exhaust every card in your deck.)
- **Reward Good Decisions, Not Good Luck** (Micro-gains will increase your odds of winning. There is no single card that will win the game on its own. Shivan Dragon doesn’t exist here.)
The specific execution of each of these principles combined is a whole other article in of itself and I will save going into that for another time. These principles are defined **[here][what-is-fab]**.
If you haven’t already and would like to learn how to play, you can watch this six minute video found **[here][learn]**. Also, if you would like to delve deeper there is also an advanced rulebook called the ‘Hero’s Handbook’ which you can find under the ‘Rules’ section **[here][rules]**.
Shuffling up
---
‘Legend Story Studios’ really have pulled out all the stops in their approach to organised play and support of the playerbase. ‘Flesh and Blood’ has been specifically designed to function in both constructed and limited (sealed and booster draft) formats, compared to most other games where one or the other is just tacked on (usually limited) out of convenience. Support has been shown with the announcement of events at both a frequent local level to large scale $10,000 competitive events. The avenues they’ve advertised to launch the game and inspire people to play and grow local communities is beyond ambitious and very exciting to witness!
A quick dive into each of these points;
- The game has been designed with both **Limited and Constructed** in mind. Paradigms have been set on how to differentiate gameplay between the two formats without any glaring exceptions or caveats. Case in point; **[young heroes][young]**.
- Frequent events at a local level (*Armory Events*) with promotional cards to score as well as a unique prize in the format of a stunning playmat that is distributed by the peers of your community. Really driving the mission of ‘Legend Story Studios’ forward and setting the motif of ‘Flesh and Blood’ to build support for local communities. Official details **[here][armory]**.
- And now for the pièce de résistance, ‘The Calling’ is a tournament series that offers up a staggering $10,000 of local currency as a cash prize pool. It seems that the frequency of these events is about once per month. This is such a tremendous way for ‘Legend Story Studios’ to show that they are truly serious in supporting the long term stability of the game and that of the players who are looking for a competitive outlet.
The first of this series is scheduled for the 27th of October in Auckland, New Zealand with a Sydney, Australia iteration on the 9th of November. Both events are sealed deck play with top 8 draft. More details on the official announcement **[here][calling]**.
Numerous articles have also been written on the official website about each format on offer, and can be found within the developer archive of articles **[here][developer]**. Notably these articles could shed light on both formats:
- [Start of Game Procedure][start-game]
- [Constructed][constructed]
- [Limited][limited]
I hope to find and hear about you playing and helping to build up your local community or having a crack at one of ‘The Calling’ events. You will be able to look up any stores that might be near you on the store locator list **[here][store-locator]**.
Flavour country
---
The game revolves around portraying yourself as one of many heroes of a subset of classes within the world of Rathe. The team at ‘Legend Story Studios’ have gone through an immense amount of effort to bring an entire universe to life through beautiful jaw-dropping artwork and storytelling full of lore around each of the heroes.
You can find out more about the world of Rathe and of each hero at these links:
- [World][world]
- [Story][story]
The heroes represented within the ‘Welcome to Rathe’ expansion and their classes are:
- **Bravo, Showstopper** the slow but powerful *Guardian*
- **Dorinthea Ironsong** the master of combat *Warrior*
- **Katsu, the Wandere**r the relentless attacking *Ninja*
- **Rhinar, Reckless Rampage** the heavy hitting *Brute*
An initial look and explanation for each of them has been well written and can be found **[here][heroes]**.
Products
---
With the release of ‘Welcome to Rathe’ there are two types of products on offer to start playing and grow your collection; **booster packs** and **‘Hero’ decks**.
The traditional booster pack product is something that we should all be so familiar with from other trading card games. Booster packs are distributed in boxes of twenty four (the perfect number for an eight player draft). The MSRP of a single booster pack is **$3.49 USD / $5.49 AUD / $5.99 NZD**. The prices of booster boxes vary from store to store, most have been throwing in a free ‘Hero Deck’ with every preorder of a full display of booster packs.
The breakdown of the contents of a booster pack is:
- 1 token
- 11 commons
- 1 rare
- 1 rare / super rare / majestic
- 1 equipment
- 1 premium foil
Based on the odds described **[here][collectability]** of opening a card based on its rarity (and the fact that you will only need three of any non-Legendary card), in order to acquire each card for your hero of choice you would need to open just about four booster boxes (*ninety six booster packs*) on average. This excludes the opportunity of trading any premium foils that you open, or that of other heroes, and of generic cards. Currently no secondary market exists (as the product hasn’t hit the shelves yet) so it’s unknown what the average price of a particular rarity is outside of its relation of frequency to other rarities.
Alternatively, there are four ‘Hero’ decks which are primarily exist for being able to jump right into the game with a low investment of time and money, securing the character that you’re interested in playing. They are described as ready-to-play 60 card constructed decks and have an MSRP of **$10.99 USD / $17.99 AUD / $19.99 NZD**.
The specific contents of each deck hasn’t yet been officially released, but it looks like each deck contains approximately thirteen rare cards based on what’s been shared around on social media. That amount of rares is similar to opening about seven booster packs (taking the exclusion of higher rarities into account). That’s a great outlook on dollar value to begin with, also, you aren’t guaranteed to be able to build a cohesive deck with the hero of your choice if you opt for the comparable price of four booster packs. These decks also serve as a starting template of how to play and build a deck around each hero. Personally, I’m excited to analyse each of them to understand how the developers intend each hero to be played to avoid any pitfalls when it comes to my own deck-building adventures.
You will be able to find more information on 'Welcome to Wrathe' products **[here][products]**.
The quickest way of finding a vendor to purchase ‘Welcome to Rathe’ and future ‘Flesh and Blood’ products would be to visit the store locator list on the official website **[here][store-locator]**.
If your local games store isn’t currently supplying ‘Flesh and Blood’ I encourage that you ask them to request access to the B2B portal **[here][b2b]**.
Hardware
---
A majority of cards from the ‘Welcome to Rathe’ expansion have been revealed to the public already through the official website, social channels, and allocated spoilers from members within the community (221/225 cards). The remaining four cards are of the highest rarity level (Legendary) with only one being officially revealed so far.
These ‘Legendary’ cards are of *immense* rarity, only appearing one in every ninety six booster packs! You do however only need to own one for your collection, as compared to other cards where a maximum of three is allowed for constructed play.
You will be able to view each officially spoiled card on the ‘Flesh and Blood’ website **[here][spoilers]**, as well as gain some more insight on the distribution of other rarities and cards within the expansion as well as the reprint policy for the game **[here][collectability]**.
Looking through the spoiler for the expansion you may notice cards that seem to be duplicates of each other.
This is no coincidence and is actually a bold choice by the developers to introduce a framework that acts as a benchmark for power level between cards and as a deck-building feature.
This pattern that will be rolled out to each qualifying card going forward with ‘Flesh and Blood’ was revealed to be named as “cycles” and was introduced with detail **[here][cycles]**.
In short; standalone cards of common and rare rarity can/will have three versions where the values are incrementally shifted between their pitch value and attack/defense (depending on the type of card). That being, the version of a card within its cycle with the lowest pitch value will be the highest impact of the three but the least flexible.
I believe that this approach to controlling design space and balance is especially exciting as it opens a lot more doors than described in the reference linked just prior. This is also an area where an in-depth look shall be saved for another time. For now though, my thoughts are aligned that each version of a cycle is feasible for play and that no version is “strictly better” than another.
If you would like a more technical look into each of the cards and their use please check out the ‘Release Notes’ section **[here][rules]**.
> *Psst! While looking through the release notes I noticed the description of a card that doesn’t exist within the preview section of the website. So, I can only assume that this is one of the remaining legendary equipment cards. Have a look!*
>
> **Fyendal’s Spring Tunic**
> *Generic Equipment - Chest*
>
> *At the start of your turn, if Fyendal’s Spring Tunic has less than 3 energy counters, you may put an energy counter on it.*
>
> *Instant - Remove 3 energy counters from Fyendal’s Spring Tunic: Gain {r}*
>
> *Blade Break (If your defend with Fyendal’s Spring Tunic, destroy it when the combat chain closes.)*
>
> *Defense: 1*
>
>
> **EDIT:** *This was just shared to the **[‘Flesh and Blood Fan Page’ Facebook group][facebook-group]**, what an exciting way to discover some of the most rare cards in the game to date!!!*
Moving on, it might be worth to note that ‘Flesh and Blood’ cards are of a similar enough size that they should fit all sleeves and accessories suited for ‘Magic: the Gathering’ cards and other *“standard”* size card games.
Wrapping up
---
If you’ve made it this far, thank you so much for your attention and I can only hope that I have been able to shed some light and spark some interest in ‘Flesh and Blood’. I truly feel like this game is doing something really special and would hate for anyone to miss out on its early days.
You should also check out one last link and register for a ‘Flesh and Blood’ account **[here][register]**. As far as I can hazard to guess, the purpose of this account will be to track your previous events as well as any other digital services that end up being provided.
Ultimately, I’m choosing to back this game because I am really impressed with the convergence of art, story, design, business model, and gameplay, as well as how ‘Legend Story Studios’ has shown their dedication and support for all types of players that hold up against their mission and principles. To me, it’s obvious that this game has plenty of years to come. I hope that we could all share some exciting moments on the journey and welcome the launch with open arms.
It would also be great to hear any stories that some of you might have from establishing or joining your local ‘Flesh and Blood’ community! Please feel free to reach out to me on any of my social channels if that happens to be the case and you’re willing to share :)
Thanks again,
Cheers!
**[@markovictory][twitter]**
[about]: https://legendstory.com/about
[what-is-fab]: https://fabtcg.com/what-is-fab/
[learn]: https://fabtcg.com/l2p/
[rules]: https://fabtcg.com/rules-and-policies/
[young]: https://fabtcg.com/articles/youth-and-learning/
[armory]: https://fabtcg.com/releases/armory-kit-season-1/
[calling]: https://fabtcg.com/articles/announcing-calling-tournament-series/
[developer]: https://fabtcg.com/articles/?type=Developer
[start-game]: https://fabtcg.com/articles/start-game-procedure/
[constructed]: https://fabtcg.com/articles/introduction-flesh-and-blood-constructed/
[limited]: https://fabtcg.com/articles/introducing-fab-limited-format/
[store-locator]: https://fabtcg.com/store-locator-list/
[world]: https://fabtcg.com/world/
[story]: https://fabtcg.com/articles/?type=Story
[heroes]: https://fabtcg.com/heroes/
[collectability]: https://fabtcg.com/articles/collectibility/
[products]: https://fabtcg.com/releases/welcome-rathe/
[b2b]: https://b2b.legendstory.com
[spoilers]: https://fabtcg.com/articles/wtr-card-previews/
[cycles]: https://fabtcg.com/articles/revealing-cycles/
[facebook-group]: https://www.facebook.com/groups/1982287188475057
[register]: https://fabtcg.com/accounts/register/
[twitter]: https://twitter.com/markovictory
| 78.739336 | 804 | 0.769712 | eng_Latn | 0.999442 |
c92e993ba97220ac31af9770a622c95adc1bd1e9 | 1,857 | md | Markdown | doc/cosign_public-key.md | Yongxuanzhang/cosign | f005e25466c3b6954546b718ce3a56d0efd6ec2b | [
"ECL-2.0",
"Apache-2.0"
] | null | null | null | doc/cosign_public-key.md | Yongxuanzhang/cosign | f005e25466c3b6954546b718ce3a56d0efd6ec2b | [
"ECL-2.0",
"Apache-2.0"
] | 70 | 2021-12-08T22:51:52.000Z | 2022-03-31T22:27:42.000Z | doc/cosign_public-key.md | Yongxuanzhang/cosign | f005e25466c3b6954546b718ce3a56d0efd6ec2b | [
"ECL-2.0",
"Apache-2.0"
] | null | null | null | ## cosign public-key
Gets a public key from the key-pair.
### Synopsis
Gets a public key from the key-pair and
writes to a specified file. By default, it will write to standard out.
```
cosign public-key [flags]
```
### Examples
```
# extract public key from private key to a specified out file.
cosign public-key --key <PRIVATE KEY FILE> --outfile <OUTPUT>
# extract public key from URL.
cosign public-key --key https://host.for/<FILE> --outfile <OUTPUT>
# extract public key from Azure Key Vault
cosign public-key --key azurekms://[VAULT_NAME][VAULT_URI]/[KEY]
# extract public key from AWS KMS
cosign public-key --key awskms://[ENDPOINT]/[ID/ALIAS/ARN]
# extract public key from Google Cloud KMS
cosign public-key --key gcpkms://projects/[PROJECT]/locations/global/keyRings/[KEYRING]/cryptoKeys/[KEY]
# extract public key from Hashicorp Vault KMS
cosign public-key --key hashivault://[KEY]
# extract public key from GitLab with project name
cosign verify --key gitlab://[OWNER]/[PROJECT_NAME] <IMAGE>
# extract public key from GitLab with project id
cosign verify --key gitlab://[PROJECT_ID] <IMAGE>
```
### Options
```
-h, --help help for public-key
--key string path to the private key file, KMS URI or Kubernetes Secret
--outfile string path to a payload file to use rather than generating one
--sk whether to use a hardware security key
--slot string security key slot to use for generated key (default: signature) (authentication|signature|card-authentication|key-management)
```
### Options inherited from parent commands
```
--output-file string log output to a file
-t, --timeout duration timeout for commands (default 3m0s)
-d, --verbose log debug output
```
### SEE ALSO
* [cosign](cosign.md) -
| 28.569231 | 150 | 0.682283 | eng_Latn | 0.88974 |
c92f0b13de0699b5b8518f7b8695850733fc2f22 | 1,037 | md | Markdown | meetings/2020-09-29/readme.md | dotnet-foundation/corporate-relations | fb31a5589ea2ddabd2d1291f9f25e62bd7e6f695 | [
"MIT"
] | 1 | 2021-06-07T07:04:51.000Z | 2021-06-07T07:04:51.000Z | meetings/2020-09-29/readme.md | dotnet-foundation/corporate-relations | fb31a5589ea2ddabd2d1291f9f25e62bd7e6f695 | [
"MIT"
] | 1 | 2021-06-07T07:06:26.000Z | 2021-06-08T00:41:44.000Z | meetings/2020-09-29/readme.md | dotnet-foundation/corporate-relations | fb31a5589ea2ddabd2d1291f9f25e62bd7e6f695 | [
"MIT"
] | 1 | 2020-03-26T19:06:26.000Z | 2020-03-26T19:06:26.000Z | # .NET Foundation Sponsorship Committee meeting September 29, 2020
- Attendees: Sponsorship Committee: Claire Novotny, Dee Dee Walsh, Rodney Littles II
- [Meeting minutes]()
## Notes
- The Committee will strive to provide value to the current Corporate Sponsors while developing strategies to recruit new sponsors.
- Discussed
- The Committee discussed creating a Corporate Membership and Sponsorship packages. Membership would be structured as Individual and Corporate Members.
- Corporate Sponsorship
- .NET Foundation Member logo to be displayed on their website
- Marketing opportunities to the. NET Foundation member base
- Their logo displayed on the .NET Foundation’s website
- Member access for up to five employees
- Quarterly opportunities to meet with a .NET Developer in the pre-build stage to provide insight into their upcoming product
- Committee discussed the importance of creating clear communication for Corporate Members and Sponsors, so they are immediately aware of their benefits as a member. | 69.133333 | 165 | 0.797493 | eng_Latn | 0.99652 |
c92f10cbbf2b60b471b3d7e285b77a668e4766ef | 5,629 | markdown | Markdown | _posts/2016-04-13-sniffer-gsm-using-c118.markdown | kaupelot/kaupelot.github.io | e8f93336362422c76731938d30789090fd987455 | [
"MIT"
] | null | null | null | _posts/2016-04-13-sniffer-gsm-using-c118.markdown | kaupelot/kaupelot.github.io | e8f93336362422c76731938d30789090fd987455 | [
"MIT"
] | null | null | null | _posts/2016-04-13-sniffer-gsm-using-c118.markdown | kaupelot/kaupelot.github.io | e8f93336362422c76731938d30789090fd987455 | [
"MIT"
] | 3 | 2016-10-18T21:32:37.000Z | 2020-10-29T06:39:44.000Z | ---
layout: post
title: "不到100块,就可以知道你家方圆50米收到了什么短信"
date: 2016-04-13 22:56:17
categories: iosre kaupelot
---
最近新闻比较多伪基站的案子,看到腾讯安全的一篇文章说是不到100块钱就可以弄一个伪基站,看完我很激动,开始在网上找短信嗅探和伪基站之类的东西.然后发现这些早在12年就被大神们玩剩下了.表示心有戚戚,看设备的时候发现使用到的摩托罗拉c118就是我人生的第一部手机.于是决定来一发.跑到闲鱼上面看到一部35块钱,入手了,再到淘宝买了c2102的接口和,c118的耳机线.然后给parallels上面的kali安装环境.终于在原料到齐全的第一天嗅探到了周边的短信,3个小时内收到了12条短信.没办法,我的移动号码,在这经常没有信号,所以gsm能够嗅探到时十分正常的了.不过是看不到收信人的信息的,发信人和短信内容清清楚楚.
下面是教程.
之前看到[那篇GSM_SMS嗅探文章](http://bbs.pediy.com/showthread.php?t=182574)后就开始试验了，但是按照文中的方法进行总是有错误，可能是我操作有问题吧。在这里，把路上总结的一些资料发出来，希望其他人别走弯路了。
网络上找得到的几处资料都或多或少存在一些错误或者没讲清楚的地方，可能原作者在修正错误后没有把过程写进去。无法找到某些资料原作者是谁了，只能在此表示感谢！
关于系统，虽然几个主流系统都可以，但是还是觉得Kali舒服，之前用别的系统出了好几个莫名其妙的错误。我这里用的是Win7_x64下VMware_10.0.0运行Kali_x64的VMware版镜像。
(一)环境配置
(1)添加源。vim看着就不舒服，用Leafpad直接开终端
代码:
leafpad /etc/apt/sources.list
把这三行复制到后面，保存。
代码:
deb http://mirrors.ustc.edu.cn/kali kali main non-free contrib
deb-src http://mirrors.ustc.edu.cn/kali kali main non-free contrib
deb http://mirrors.ustc.edu.cn/kali-security kali/updates main contrib non-free
(2)乱七八糟的都配置好。最好不要一次都复制进去执行，尤其是apt-get和wget可能会因为网络原因出错。
代码:
apt-get update
aptitude install libtool shtool autoconf git-core pkg-config make gcc
apt-get install build-essential libgmp3-dev libmpfr-dev libx11-6 libx11-dev texinfo flex bison libncurses5 \
libncurses5-dbg libncurses5-dev libncursesw5 libncursesw5-dbg libncursesw5-dev zlibc zlib1g-dev libmpfr4 libmpc-dev
wget -c http://bb.osmocom.org/trac/raw-attachment/wiki/GnuArmToolchain/gnu-arm-build.2.sh
chmod +x gnu-arm-build.2.sh
mkdir build install src
cd src/
(3)下载3个包。直接用迅雷下好拖进src文件夹也行。
代码:
wget http://www.gnuarm.com/bu-2.16.1_gcc-4.0.2-c-c++_nl-1.14.0_gi-6.4_x86-64.tar.bz2
wget http://ftp.gnu.org/gnu/binutils/binutils-2.21.1a.tar.bz2
wget ftp://sources.redhat.com/pub/newlib/newlib-1.19.0.tar.gz
(5)下面也是很多步骤都需要漫长的等待，不要着急，最好不要一次复制太多行进去
代码:
cd ..
./gnu-arm-build.2.sh
echo "export PATH=\$PATH:/root/install/bin">/root/.bashrc
source /root/.bashrc
cd ~
git clone git://git.osmocom.org/libosmocore.git
cd libosmocore/
autoreconf -i
./configure
make
make install
cd ..
.ldconfig
git clone git://git.osmocom.org/osmocom-bb.git
cd ~/osmocom-bb
git checkout --track origin/luca/gsmmap
cd src
git pull --rebase
准备好了，编译！
代码:
make
顺利的话环境配置到这里就结束了。
(6)出现错误？(我没遇到任何错误，下面收集两个来自网络的错误)
A错误:
代码:
/root/osmocom-bb/src/target/firmware/include/asm/swab.h: Assembler messages:
/root/osmocom-bb/src/target/firmware/include/asm/swab.h:32: Error: no such instruction: `eor %edx,%ecx,%ecx,ror’
make[4]: *** [gsmtap_util.lo] 错误 1
make[4]: Leaving directory `/root/osmocom-bb/src/shared/libosmocore/build-target/src’
make[3]: *** [all] 错误 2
make[3]: Leaving directory `/root/osmocom-bb/src/shared/libosmocore/build-target/src’
make[2]: *** [all-recursive] 错误 1
make[2]: Leaving directory `/root/osmocom-bb/src/shared/libosmocore/build-target’
make[1]: *** [all] 错误 2
make[1]: Leaving directory `/root/osmocom-bb/src/shared/libosmocore/build-target’
make: *** [shared/libosmocore/build-target/src/.libs/libosmocore.a] 错误 2
A解决：
代码:
tar xf bu-2.16.1_gcc-4.0.2-c-c++_nl-1.14.0_gi-6.4_x86-64.tar.bz2
mv gnuarm-* ~/gnuarm
export PATH=~/gnuarm/bin:$PATH
B错误:
代码:
make[1]: *** [board/compal_e88/hello_world.compalram.elf] 错误 1
make[1]: Leaving directory `/root/osmocom-bb/src/target/firmware’
make: *** [firmware] 错误 2
B解决:
代码:
git clean -dfx
make
(二)硬件配置
(1)准备需要的东西：
代码:
MOTOROLA_C118手机
CP201X(USB to TTL)
数据线(2.5mm耳机头转杜邦线)如果自制有的需要用刀把接头处切掉一圈才能完全插进去
(2)连线
模块上有3V3、TXD、RXD、GND、+5V，只用中间的三根
我这里是：红TXD白RXD黄GND，直接修了一张简图在图右侧标识出来。
(3)识别
手机不用插卡，不用开机。把USB插进去，在虚拟机->可移动设备下面会有
点连接(断开与 主机 的连接)
在Kali里面开个终端输入
代码:
lsmod | grep usb
(三)嗅探过程
(1)打开4个终端窗口ABCD
(2)在A中粘贴命令
代码:
cd ~/osmocom-bb/src/host/osmocon/
./osmocon -m c123xor -p /dev/ttyUSB0 ../../target/firmware/board/compal_e88/layer1.compalram.bin
然后按下手机红色开机键
有人说这是在刷固件，但事实上它只不过把这一段程序写到手机中运行而已，并未影响手机本身的固件。
(3)切换到B终端，粘贴命令
代码:
cd ~/osmocom-bb/src/host/layer23/src/misc/
./cell_log -O
漫长的等待之后会显示出扫描到的基站信息。
拿自己的手机测试，苹果手机可以直接*3001#12345#*然后拨出
在Field Test中点GSM Cell Environment，进入GSM Cell Info，再进入GSM Serving Cell，查看当前ARFCN的值
如果不用自己的手机测试，直接在扫描到的列表里随便选一个ARFCN好了。
(4)切换到C终端，粘贴命令
代码:
cd ~/osmocom-bb/src/host/layer23/src/misc/
./ccch_scan -i 127.0.0.1 -a 刚才的ARFCN
第二行命令后面-a后加一个空格，然后输入记录的ARFCN值
可以看到控制台疯狂刷屏
(5)切换到D终端，粘贴命令
代码:
wireshark -k -i lo -f 'port 4729'
在打开的Wireshark上修改成gsm_sms过滤，回车。
到这里就基本结束了，至于抓uplink，需要拆掉一个RX滤波器，手头没工具，以后再说吧。
关于脚本，@木桩 的原文写的已经相当详细了，没有必要重新发一遍。
原文链接：http://bbs.pediy.com/showthread.php?t=182574 | 24.158798 | 308 | 0.726772 | yue_Hant | 0.42114 |
c92f19498319e1a8895ae55bf67e108b96524d4b | 3,500 | md | Markdown | guides/02-guidelines/01-style/typography/index.md | IBM-Watson/design-guide | 9da98515076994898a55e837425a49524c53ed60 | [
"Apache-2.0",
"CC-BY-4.0"
] | 87 | 2015-07-09T22:54:37.000Z | 2022-02-20T22:06:42.000Z | guides/02-guidelines/01-style/typography/index.md | IBM-Watson/design-library | 9da98515076994898a55e837425a49524c53ed60 | [
"Apache-2.0",
"CC-BY-4.0"
] | 330 | 2015-03-11T23:02:32.000Z | 2015-06-24T21:14:40.000Z | guides/02-guidelines/01-style/typography/index.md | IBM-Watson/design-guide | 9da98515076994898a55e837425a49524c53ed60 | [
"Apache-2.0",
"CC-BY-4.0"
] | 39 | 2015-06-26T20:55:56.000Z | 2019-03-12T20:18:34.000Z | ---
type: guideline
title: Typography
variables:
aside:
usageRights:
description: "We are currently in the process of inquiring about full usage rights and licensing for Helvetica Neue for IBM. During this time, we're unable to provide downloadable font assets. Please defer to the Cross-Platform Fontstack Options below for comparable fontstacks."
example:
typefaceCombinations:
typefaceCombinationOne:
title: "Helvetica Neue Roman"
visualDisplay: /images/typography/typeface-roman.svg
typefaceCombinationTwo:
title: "Helvetica Neue Roman Italic"
visualDisplay: /images/typography/typeface-roman-italic.svg
typefaceCombinationThree:
title: "Helvetica Neue Bold"
visualDisplay: /images/typography/typeface-bold.svg
typefaceCombinationFour:
title: "Helvetica Neue Bold Italic"
visualDisplay: /images/typography/typeface-bold-italic.svg
responsiveTypography:
title: "Major Third with a breakpoint at 500px"
visualDisplay: /videos/typography/responsive-typography.webm
description: "When the browser gets wider than 500px, headings adopt the Golden Ratio type scale to increase legibility for the user at larger screen sizes."
---
Typography is the atomic element of good interface design. It colors the words in our language and shapes their meaning. It helps to set the visual tone for the entire IBM Watson experience. Text is largely differentiated by size and weight. Keep other properties the same or similar, differentiating only when necessary for the sake of clarity.
## Helvetica Neue for IBM
As a rule and wherever possible, use Helvetica Neue. It is the font of science and the information age, with a precision and objectivity that commands respect. We lean on Helvetica Neue to do the hard work of conveying information, specifications, and the basics. Its clean confidence makes it ideal for our product design.
{{ _aside.aside(aside.usageRights) }}
## Performance Considerations
When presenting large amounts of content, it is important to consider how multiple font downloads can affect the [browser’s performance](/guidelines/user-experience/performance/) for the user. To ensure optimized performance for all users, IBM Watson recommends choosing a combination of no more than four different weights and styles (light and light oblique being two different styles, for instance).
{{ _example.compare(example.typefaceCombinations) }}
## Typographic Scale
The IBM Design Language recommends using [modular type scales](http://www.ibm.com/design/language/framework/visual/typography.shtml) to create harmonious proportions and structure. Scale creates consistent sizing across elements. A visual type scale turns a typographic balancing act into a set ratio.
### Major Third Type Scale
IBM Watson recommends the Major Third ratio for screen sizes under 500px and the establishment of breakpoints for higher contrast on larger screens. This ratio is ideal for creating visual hierarchy on small screens without being too jarring.
{{ _example.large(example.responsiveTypography) }}
## Cross-Platform Fontstack Options
### Desktop or Browser
`font-family: 'Helvetica Neue for IBM', Helvetica, Arial, Roboto, sans-serif;`
######Monospace
`font-family: 'Source Code Pro', Lucida Console, Andale Mono, monospace;`
###Apple Watch
`font-family: 'San Francisco';`
###iOS
`font-family: 'Helvetica Neue';`
###Android
`font-family: 'Roboto';`
| 48.611111 | 403 | 0.770286 | eng_Latn | 0.974068 |
c92fc6a0a4d89b4293c449727071384f8fe5e1a8 | 245 | md | Markdown | README.md | vwnb/korttelicheck | 079789d4ed5ae2638557453daf5e055c90c48f6a | [
"MIT"
] | null | null | null | README.md | vwnb/korttelicheck | 079789d4ed5ae2638557453daf5e055c90c48f6a | [
"MIT"
] | null | null | null | README.md | vwnb/korttelicheck | 079789d4ed5ae2638557453daf5e055c90c48f6a | [
"MIT"
] | null | null | null | ### DISCLAIMER
_Broken, can be probably deployed with some small fixes. Most of the code works._
**_Keeping the repository up for some hints about using various Helsinki Open Data APIs 😊_**
To start:
```
npm install
npm start
```
MIT License
| 18.846154 | 92 | 0.746939 | eng_Latn | 0.975137 |
c92fe3b1a2565175a66605478eac76c71e4eb68f | 2,442 | md | Markdown | articles/avere-vfxt/avere-vfxt-demo-links.md | changeworld/azure-docs.it- | 34f70ff6964ec4f6f1a08527526e214fdefbe12a | [
"CC-BY-4.0",
"MIT"
] | 1 | 2017-06-06T22:50:05.000Z | 2017-06-06T22:50:05.000Z | articles/avere-vfxt/avere-vfxt-demo-links.md | changeworld/azure-docs.it- | 34f70ff6964ec4f6f1a08527526e214fdefbe12a | [
"CC-BY-4.0",
"MIT"
] | 41 | 2016-11-21T14:37:50.000Z | 2017-06-14T20:46:01.000Z | articles/avere-vfxt/avere-vfxt-demo-links.md | changeworld/azure-docs.it- | 34f70ff6964ec4f6f1a08527526e214fdefbe12a | [
"CC-BY-4.0",
"MIT"
] | 7 | 2016-11-16T18:13:16.000Z | 2017-06-26T10:37:55.000Z | ---
title: Progetti demo di Avere vFXT per Azure
description: "Questi esempi mostrano le funzionalità chiave e i casi d'uso per vFXT per Azure: rendering video, elaborazione ad alte prestazioni, prestazioni vFXT e configurazione client."
author: ekpgh
ms.service: avere-vfxt
ms.topic: conceptual
ms.date: 12/19/2019
ms.author: rohogue
ms.openlocfilehash: 43162c4c9812015952c749446d160ab1c0d84392
ms.sourcegitcommit: 32e0fedb80b5a5ed0d2336cea18c3ec3b5015ca1
ms.translationtype: MT
ms.contentlocale: it-IT
ms.lasthandoff: 03/30/2021
ms.locfileid: "105639412"
---
# <a name="avere-vfxt-demo-projects"></a>Progetti demo di Avere vFXT
In [GitHub](https://github.com/Azure/Avere) sono disponibili esercitazioni di esempio. Questi progetti di piccole dimensioni illustrano le funzionalità chiave e i casi d'uso per Avere vFXT per Azure.
## <a name="video-rendering"></a>Rendering video
* [Rendering con Azure batch e vFXT](https://github.com/Azure/Avere/blob/master/docs/maya_azure_batch_avere_vfxt_demo.md) -un progetto di 60 minuti che illustra come usare Autodesk Maya con Azure batch e un cluster vFXT per generare un film animato
* [Why use the Avere vFXT for rendering?](https://github.com/Azure/Avere/blob/master/docs/why_avere_for_rendering.md) (Perché usare Avere vFXT per il rendering?) -Dimostrazione che confronta i tempi di rendering dall'archiviazione collegata alla rete con e senza un cluster vFXT.
## <a name="high-performance-computing"></a>HPC (High Performance Computing)
* [Procedure consigliate per migliorare l'ora di avvio di una macchina virtuale (VM) di Azure](https://github.com/Azure/Avere/blob/master/docs/azure_vm_provision_best_practices.md) : un test riproducibile che usa VFXT per Azure per migliorare i tempi di avvio quando si avviano rapidamente migliaia di client di calcolo
## <a name="vfxt-performance"></a>Prestazioni di vFXT
* [Misurare le prestazioni di vFXT con vdbench](https://github.com/Azure/Avere/blob/master/docs/vdbench.md) : una configurazione di test di base per generare carichi di lavoro di piccole e medie dimensioni per testare i sottosistemi di memoria e disco vFXT
## <a name="client-setup"></a>Configurazione client
* [Windows 10 workstation for Avere vFXT](https://github.com/Azure/Avere/blob/master/docs/windows_10_avere_vfxt_mounted_workstation.md) (Workstation Windows 10 per Avere vFXT) - Illustra come configurare una workstation Windows e montarla in un cluster Avere vFXT
| 66 | 319 | 0.798116 | ita_Latn | 0.935604 |
c9309ecbfdc686131ad2dd70340ce43d57740fc1 | 638 | md | Markdown | add/metadata/System.Windows.Forms.VisualStyles/VisualStyleElement+StartPanel+MoreProgramsArrow.meta.md | MarktW86/dotnet.docs | 178451aeae4e2c324aadd427ed6bf6850e483900 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | add/metadata/System.Windows.Forms.VisualStyles/VisualStyleElement+StartPanel+MoreProgramsArrow.meta.md | MarktW86/dotnet.docs | 178451aeae4e2c324aadd427ed6bf6850e483900 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | add/metadata/System.Windows.Forms.VisualStyles/VisualStyleElement+StartPanel+MoreProgramsArrow.meta.md | MarktW86/dotnet.docs | 178451aeae4e2c324aadd427ed6bf6850e483900 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
uid: System.Windows.Forms.VisualStyles.VisualStyleElement.StartPanel.MoreProgramsArrow
author: "stevehoag"
ms.author: "shoag"
manager: "wpickett"
---
---
uid: System.Windows.Forms.VisualStyles.VisualStyleElement.StartPanel.MoreProgramsArrow.Normal
author: "stevehoag"
ms.author: "shoag"
manager: "wpickett"
---
---
uid: System.Windows.Forms.VisualStyles.VisualStyleElement.StartPanel.MoreProgramsArrow.Pressed
author: "stevehoag"
ms.author: "shoag"
manager: "wpickett"
---
---
uid: System.Windows.Forms.VisualStyles.VisualStyleElement.StartPanel.MoreProgramsArrow.Hot
author: "stevehoag"
ms.author: "shoag"
manager: "wpickett"
---
| 22.785714 | 94 | 0.783699 | yue_Hant | 0.592095 |
c9310033308735faa6bb4f4d7e2c5079f09edbda | 702 | md | Markdown | TimPengembang/Dokumentasi/Panduan/PanduanPemutakhiran/KondeKeLontara.md | ricocwp/wiki | e317307794cccf61709a0f02c8d952bf934f4ad4 | [
"MIT"
] | 16 | 2017-04-10T15:31:36.000Z | 2021-07-16T07:18:17.000Z | TimPengembang/Dokumentasi/Panduan/PanduanPemutakhiran/KondeKeLontara.md | ricocwp/wiki | e317307794cccf61709a0f02c8d952bf934f4ad4 | [
"MIT"
] | 54 | 2017-04-02T00:01:50.000Z | 2022-02-27T10:31:03.000Z | TimPengembang/Dokumentasi/Panduan/PanduanPemutakhiran/KondeKeLontara.md | ricocwp/wiki | e317307794cccf61709a0f02c8d952bf934f4ad4 | [
"MIT"
] | 38 | 2017-02-26T16:07:19.000Z | 2021-03-27T07:10:37.000Z | # Panduan Pindah Konde Ke Lontara
* Perbarui repositori BlankOn ke /etc/apt/sources.list. Ganti kata konde ke
lontara.
deb http://arsip.blankonlinux.or.id/blankon lontara main restricted
deb http://arsip.blankonlinux.or.id/blankon lontara-updates main
restricted
deb http://security.blankonlinux.or.id/blankon lontara-security main
restricted
* Perbarui basis data paket
sudo apt-get update
* Naikkan versi
sudo apt-get dist-upgrade
* Install blankon-desktop-minimalist untuk varian Minimalis dan jawab Ya
untuk semua pertanyaan.
sudo apt-get install blankon-desktop-minimalist
KategoriDok
Last modified on 06/17/2008 01:14:41 PM
| 31.909091 | 77 | 0.732194 | ind_Latn | 0.425756 |
c931732001598a6b95c7d4289530509625f7cda2 | 207 | md | Markdown | CHANGELOG.md | jokob-sk/mount-bookmark | d8d1a7a04bb2cf188eec9185075f88ff835f9d5e | [
"MIT"
] | 50 | 2021-05-22T18:36:34.000Z | 2022-01-12T19:51:55.000Z | CHANGELOG.md | jokob-sk/mount-bookmark | d8d1a7a04bb2cf188eec9185075f88ff835f9d5e | [
"MIT"
] | null | null | null | CHANGELOG.md | jokob-sk/mount-bookmark | d8d1a7a04bb2cf188eec9185075f88ff835f9d5e | [
"MIT"
] | 9 | 2021-05-26T01:18:40.000Z | 2021-09-21T07:50:24.000Z | # V1.0
**Name**: Inital Release\
**Release Date**: 22.05.2021\
**Features**:
- Youtube Video/Stream Background
- Custom Icons
- Custom Colorpalette
- Searchfield for any SearchEngine
- Bookmark Categories
| 17.25 | 34 | 0.729469 | kor_Hang | 0.436037 |
c931f2755e3690b5ab7c60245eddfd06a0a6ec05 | 21,558 | md | Markdown | powerbi-docs/create-reports/sample-datasets.md | Kaartick22/PowerBI | 24887643bd3e1b3749ce325dc0ae407432d7fee4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | powerbi-docs/create-reports/sample-datasets.md | Kaartick22/PowerBI | 24887643bd3e1b3749ce325dc0ae407432d7fee4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | powerbi-docs/create-reports/sample-datasets.md | Kaartick22/PowerBI | 24887643bd3e1b3749ce325dc0ae407432d7fee4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Get samples for Power BI
description: Sample content packs, apps, .pbix files, and Excel datasets for Power BI
author: maggiesMSFT
ms.author: maggies
ms.reviewer:
ms.custom:
ms.service: powerbi
ms.subservice: pbi-reports-dashboards
ms.topic: conceptual
ms.date: 03/27/2020
LocalizationGroup: Samples
---
# Get samples for Power BI
Say you're new to Power BI and want to try it out but don't have any data. Or maybe you'd like to see reports that illustrate some of the capabilities of Power BI. We've got you covered.
Power BI offers different kinds of samples, for different purposes:
- A **[Power BI report](#sales--returns-sample-pbix-file) (.pbix file)** that you can view in the Data Stories Gallery, open and explore in Power BI Desktop, or upload to the Power BI service.
- A **[sample app](#sample-app-from-appsource)** that you download from AppSource, also right in the Power BI service. Apps include dashboards, reports, and datasets. You can modify them, then distribute them to your colleagues.
- **[Eight original built-in samples](#eight-original-samples)** in the Power BI service as *content packs*, with dashboards, reports, and datasets. You install them right in the Power BI service. The built-in samples are also available as Power BI reports (.pbix) and Excel workbooks (.xlsx).
- **[Excel workbook](#download-sample-excel-files)** versions of the built-in samples, containing the data model and Power View sheets. You can explore or edit the data model in Excel, use the Excel workbook as a data source for a Power BI report. You can also upload the workbook as an Excel file and display the Excel visuals and PivotTables in Power BI reports.
- Also a **[Financial data sample workbook](sample-financial-download.md)**, a simple flat table in an Excel file available for download. It contains anonymized data with fictitious products, with sales divided by segments and countries/regions. It makes a useful basic data source for a Power BI report.
Our online documentation uses these same samples in tutorials and examples, so you can follow along.
## Sales & Returns sample .pbix file
:::image type="content" source="media/sample-datasets/sales-returns-sample-pbix.png" alt-text="Sales & Returns sample .pbix file":::
*The Sales & Returns sample report*
Power BI report designers Miguel Myers and Chris Hamill created the Sales & Returns .pbix file to demonstrate many new features in Power BI, including buttons, drill through, conditional formatting, what-if, and customized tooltips.
The scenario for this report is a company that sells Microsoft-themed skateboards. They want to see the state of their sales and returns, and analyze how they should modify their operations.
You can explore it these ways:
- View and interact with it in the Power BI Community [Data Stories Gallery](https://community.powerbi.com/t5/Data-Stories-Gallery/Sales-amp-Returns-Sample-Report/m-p/876607).
- Download the .pbix file and explore it in depth. Look "behind the curtain" to see how Miguel made it. Selecting this link downloads the file automatically: [Sales & Returns sample report](https://github.com/microsoft/powerbi-desktop-samples/blob/main/Sample%20Reports/Sales%20%26%20Returns%20Sample%20v201912.pbix).
- Read about the report in the Power BI blog post, [Take a tour of the new Sales & Returns sample report](https://powerbi.microsoft.com/blog/take_a_tour_of_the_new_sales_returns_sample_report/).
## Sample app from AppSource
The Marketing and Sales *app* is available from Microsoft AppSource. An app is a Power BI content type that combines related dashboards and reports. An app can have one or more dashboards and one or more reports, all bundled together. You can download the Marketing and Sales app from **Apps** in the Power BI service, or by going to AppSource in your browser.
- The article [Install and use apps](../consumer/end-user-app-view.md) explains how to download an app from within the Power BI service.
- This link takes you to the [Sales & Marketing app](https://appsource.microsoft.com/product/power-bi/microsoft-retail-analysis-sample.salesandmarketingsample?tab=Overview) in AppSource.
After you install it, you see it in your collection of apps.
:::image type="content" source="media/sample-datasets/power-bi-sales-marketing-app.png" alt-text="Sales & Marketing app tile":::
When you open it, select **Explore with sample data**.
:::image type="content" source="media/sample-datasets/power-bi-explore-app.png" alt-text="Explore the app":::
You see the app view, with the dashboard and individual report pages in the navigation pane.
:::image type="content" source="media/sample-datasets/power-bi-sales-marketing-app-navigation.png" alt-text="App navigation pane":::
Because you installed it, you can also open the *workspace* and edit the elements of the app. Select the **Edit** pencil icon to open the workspace.
:::image type="content" source="media/sample-datasets/power-bi-app-edit-pencil.png" alt-text="Edit the app":::
Now you see the dashboard, report, and dataset from the app in the list view of the workspace. Here in the workspace, you can edit each of them.
:::image type="content" source="media/sample-datasets/power-bi-sales-marketing-workspace.png" alt-text="Sales & Marketing workspace":::
If you want to, you can distribute this app to anyone in your organization. Select **Update app**.
:::image type="content" source="media/sample-datasets/power-bi-update-app.png" alt-text="Update app button":::
Complete the **Setup** tab, including choosing an **App theme color**.
:::image type="content" source="media/sample-datasets/power-bi-app-setup.png" alt-text="Select app setup":::
Complete the **Navigation** and **Permission** tabs, then select **Update app**.
:::image type="content" source="media/sample-datasets/power-bi-select-update-app.png" alt-text="Select Update app to publish it":::
Read more about [publishing apps in Power BI](../collaborate-share/service-create-distribute-apps.md).
## Eight original samples
Eight original samples are available for you to use. Each sample represents a different industry. You can engage with each in different formats:
- Install the [built-in content packs](#install-built-in-content-packs) in the Power BI service.
- Download the [Power BI report files](#download-original-sample-power-bi-files) (.pbix).
- Download the [Excel workbook files](#download-sample-excel-files) (.xlsx), then upload them to the Power BI service.
- Explore the [Excel files in Excel](#explore-excel-samples-inside-excel) itself.
The company obviEnce ([www.obvience.com](http://www.obvience.com/)) and Microsoft teamed up to create samples for you to use with Power BI. The data is anonymized and represents different industries: finance, HR, sales, and more.
Each of these samples is available in several formats: as a content pack, as an Excel workbook, and as a Power BI .pbix file. If you don't know what these things are, or how to get your hands on them -- don't worry. This article explains it all. For each of these samples, we've created a *tour*. Tours are articles that tell the story behind the sample and walk you through different scenarios. One scenario might be answering questions for your manager, another might be looking for competitive insights, or creating reports and dashboards to share, or explaining a business shift.
Before we get started, here are the legal guidelines for using these samples. After that, we introduce the samples and show how to use them.
### Usage guidelines for the sample Excel workbooks
©2015 Microsoft Corporation. All rights reserved. The documents and workbooks are provided "as-is." Information and views expressed in the workbooks, including URL and other Internet Web site references, may change without notice. You bear the risk of using it. Some examples are for illustration only and are fictitious. No real association is intended or inferred. Microsoft makes no warranties, express or implied, with respect to the information provided here.
The workbooks do not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this workbook for your internal, reference purposes.
The workbooks and related data are provided by obviEnce. [www.obvience.com](http://www.obvience.com)
ObviEnce is an ISV and an Intellectual Property (IP) Incubator focused on Microsoft Business Intelligence. ObviEnce works closely with Microsoft to develop best practices and thought leadership for jump-starting and deploying Microsoft Business Intelligence solutions.
The workbooks and data are property of obviEnce, LLC, and have been shared solely for the purpose of demonstrating Power BI functionality with industry sample data.
Any uses of the workbooks and/or data must include the above attribution (that is also on the Info worksheet included with each workbook). The workbook and any visualizations must be accompanied by the following copyright notice: obviEnce ©.
By clicking any of the following links to download the Excel workbook files or .pbix files, you are agreeing to the terms above.
### Customer Profitability sample 
[Take a tour of the Customer Profitability sample](sample-customer-profitability.md)
This industry sample analyzes a CFO's key metrics for the company's executives, products, and customers. You can investigate what factors impact the company's profitability.
### Human Resources sample 
[Take a tour of the HR sample](sample-human-resources.md)
This industry sample focuses on the hiring strategy for a company by analyzing new hires, active employees, and employees who have left. By exploring the data, you can find trends in voluntary separations and biases in the hiring strategy.
### IT Spend Analysis sample 
[Take a tour of the IT Spend Analysis sample](sample-it-spend.md)
In this industry sample, we analyze the planned vs. actual costs of the IT department of a company. This comparison helps us understand how well the company planned for the year and investigate areas with huge deviations from the plan. The company in this example goes through a yearly planning cycle, and then quarterly it produces a new Latest Estimate (LE) to help analyze changes in IT spend over the fiscal year.
### Opportunity Analysis sample 
[Take a tour of the Opportunity Analysis sample](sample-opportunity-analysis.md)
This industry sample explores a software company's sales channel. Sales managers monitor their direct and partner sales channels by tracking opportunities and revenue by region, deal size, and channel.
### Procurement Analysis sample 
[Take a tour of the Procurement Analysis sample](sample-procurement.md)
This industry sample analyzes a CFO's key metrics for the company's executives, products, and customers. You can investigate what factors impact the company's profitability.
### Retail Analysis sample 
[Take a tour of the Retail Analysis sample](sample-retail-analysis.md)
This industry sample analyzes retail sales data of items sold across multiple stores and districts. The metrics compare this year's performance to last year's in these areas: sales, units, gross margin, and variance, as well as new store analysis.
### Sales and Marketing sample 
[Take a tour of the Sales and Marketing sample](sample-sales-and-marketing.md)
This industry sample analyzes a manufacturing company, VanArsdel Ltd. It allows the Chief Marketing Officer to watch the industry and the market share for VanArsdel. By exploring the sample, you can find the company's market share, product volume, sales, and sentiment.
### Supplier Quality sample 
[Take a tour of the Supplier Quality sample](sample-supplier-quality.md)
This industry sample focuses on one of the typical supply chain challenges — supplier quality analysis. Two primary metrics are at play in this analysis: total number of defects and the total downtime that these defects caused. This sample has two main objectives: understand who the best and worst suppliers are, with respect to quality, and identify which plants do a better job finding and rejecting defects, to minimize downtime.
### Install built-in content packs
Let's start with the *content packs*. The built-in samples are available in the Power BI service; you don't have to leave Power BI to find them. A content pack is a bundle of one or more dashboards, datasets, and reports that someone creates and that can be used with the Power BI service. Each Power BI sample content pack contains a dataset, report, and dashboard. Content packs are still available, but are being deprecated. They aren't available for Power BI Desktop.
1. Open the Power BI service (app.powerbi.com) and sign in.
2. Navigate to your My Workspace, or another workspace where you want to install the sample.
2. In the bottom-left corner, select **Get data**.
3. On the Get Data page that appears, select **Samples**.
4. Select one of the samples to open a description of that sample, and choose **Connect**.
5. Power BI imports the content pack and adds a new dashboard, report, and dataset to your current workspace. Use the samples to take Power BI for a test run.
Now that you have data, you're on your way. Try out some of our tutorials using the sample content packs or just open the Power BI service and explore.
### Download original sample Power BI files
Each of the sample content packs is also available as Power BI .pbix file. The .pbix files are designed to be used with Power BI Desktop.
1. Download the files individually using the links below. Selecting these links saves the file automatically to your Downloads folder.
- [Customer Profitability Sample PBIX](https://download.microsoft.com/download/6/A/9/6A93FD6E-CBA5-40BD-B42E-4DCAE8CDD059/Customer%20Profitability%20Sample%20PBIX.pbix)
- [Human Resources Sample PBIX](https://download.microsoft.com/download/6/9/5/69503155-05A5-483E-829A-F7B5F3DD5D27/Human%20Resources%20Sample%20PBIX.pbix)
- [Procurement Analysis Sample PBIX](https://download.microsoft.com/download/D/5/3/D5390069-F723-413B-8D27-5888500516EB/Procurement%20Analysis%20Sample%20PBIX.pbix)
- [Retail Analysis Sample PBIX](https://download.microsoft.com/download/9/6/D/96DDC2FF-2568-491D-AAFA-AFDD6F763AE3/Retail%20Analysis%20Sample%20PBIX.pbix)
- [Sales and Marketing Sample PBIX](https://download.microsoft.com/download/9/7/6/9767913A-29DB-40CF-8944-9AC2BC940C53/Sales%20and%20Marketing%20Sample%20PBIX.pbix)
- [Supplier Quality Analysis Sample PBIX](https://download.microsoft.com/download/8/C/6/8C661638-C102-4C04-992E-9EA56A5D319B/Supplier-Quality-Analysis-Sample-PBIX.pbix)
1. In Power BI Desktop, select **File > Open** and navigate to the location where you saved the sample .pbix file.
4. Select the .pbix file to open it in Power BI Desktop.
### Download sample Excel files
Each of the sample content packs is also available as an Excel workbook. The Excel workbooks are designed to be used with the Power BI service.
1. Download the files individually using the links below, or [download a zip file of all the sample files](https://go.microsoft.com/fwlink/?LinkId=535020). If you're an advanced user, you might want to download the Excel workbooks to explore or edit the data models.
- [Customer Profitability Sample](https://go.microsoft.com/fwlink/?LinkId=529781)
- [Human Resources Sample](https://go.microsoft.com/fwlink/?LinkId=529780)
- [Opportunity Tracking Sample](https://go.microsoft.com/fwlink/?LinkId=529782)
- [Procurement Analysis Sample](https://go.microsoft.com/fwlink/?LinkId=529784)
- [Retail Analysis Sample](https://go.microsoft.com/fwlink/?LinkId=529778)
- [Sales and Marketing Sample](https://go.microsoft.com/fwlink/?LinkId=529785)
- [Supplier Quality Analysis Sample](https://go.microsoft.com/fwlink/?LinkId=529779)
2. Save the downloaded file. Where you save the file makes a difference.
 **Local** - If you save your file to a local drive on your computer or another location in your organization, from Power BI, you can import your file into Power BI. Your file remains on your local drive, so the whole file isn't imported into Power BI. What happens is a new dataset is created in your Power BI site and data, and in some cases the data model, are loaded into the dataset. If your file has any reports, those reports appear in your Power BI site under Reports.
 **OneDrive - Business** – If you have OneDrive for Business and you sign into it with the same account you sign into Power BI with, OneDrive for Business is by far the best place to keep your work in Excel, Power BI, or a .CSV file in-sync with your dataset, reports, and dashboards in Power BI. Because both Power BI and OneDrive are in the cloud, Power BI connects to your file on OneDrive about every hour. If any changes are found, your dataset, reports, and dashboards are automatically updated in Power BI.
 **SharePoint Team-Sites** Saving your Power BI files to SharePoint – Team Sites is much the same as saving to OneDrive for Business. The biggest difference is how you connect to the file from Power BI. You can specify a URL or connect to the root folder.
1. Open the Power BI service (app.powerbi.com) and sign in.
1. Navigate to your My Workspace or to another workspace, or create a workspace just for the sample.
4. In the bottom-left corner of the navigation pane, select **Get data**.
5. On the **Get Data** page that appears, select **Files > Get**.
6. Select the location where you downloaded and saved the sample.
7. Select the file. Depending on where you saved the file, select **Connect** or **Open**.
8. Choose whether to import the data or to bring the workbook into Power BI and see it exactly as it is in Excel online.
9. If you select **Import**, Power BI imports the sample workbook and adds it as a new dashboard, report, and dataset, in this case each named **Procurement Analysis Sample**.
- Because the workbook has Power View sheets, Power BI creates a report with a page for each Power BI sheet.
- Power BI creates a new dashboard with a new blank tile. Selecting that tile takes you to the report you just added.
10. Open the report. Select different elements of the report to explore their interactions.
### Explore Excel samples inside Excel
(Optional) Want to understand how the data in an Excel workbook gets converted to Power BI datasets and reports? Opening the Excel samples *in Excel* and exploring the worksheets provides some of the answers.
- When you first open a sample workbook in Excel, you may see two warnings. The first warning says the workbook is in Protected View. Select **Enable Editing**. The second warning may say that the workbook has external data connections. Select **Enable Content**.
- Each workbook contains several Power View sheets. If you want to see the Power View sheets in Excel, You need to [enable the Power View add-in](https://support.office.com/article/flash-silverlight-and-shockwave-controls-blocked-in-microsoft-office-55738f12-a01d-420e-a533-7cef1ff6aeb1) by downloading a package of registry keys.
- So where's the actual data? It's in the Power Pivot data model. You don't need the Power View sheets to see the data. On the **PowerPivot** tab, select **Manage**.
Don't see the **Power Pivot** tab? [Enable the Power Pivot add-in](https://support.office.com/article/Start-Power-Pivot-in-Microsoft-Excel-2013-add-in-A891A66D-36E3-43FC-81E8-FC4798F39EA8).
In Power Pivot, you can see the data in all the underlying tables, plus all the DAX formulas.
- The Info tab provides information about obviEnce, the company that created the sample.
## Next steps
[Basic concepts for designers in the Power BI service](../fundamentals/service-basic-concepts.md)
[Tutorial: Connect to the Power BI samples](sample-tutorial-connect-to-the-samples.md)
[Data sources for Power BI](../connect-data/service-get-data.md)
More questions? [Try the Power BI Community](https://community.powerbi.com/)
| 82.282443 | 587 | 0.77753 | eng_Latn | 0.990651 |
c933091eff8576506f2eaaf8b99d6593a29ec752 | 1,385 | md | Markdown | docs/zh-CN/readme.md | phiex/thinksns-plus | 39bfb67735b55869839b88b7f2346f04d0dfce5a | [
"Apache-2.0"
] | null | null | null | docs/zh-CN/readme.md | phiex/thinksns-plus | 39bfb67735b55869839b88b7f2346f04d0dfce5a | [
"Apache-2.0"
] | null | null | null | docs/zh-CN/readme.md | phiex/thinksns-plus | 39bfb67735b55869839b88b7f2346f04d0dfce5a | [
"Apache-2.0"
] | 1 | 2018-07-27T10:13:10.000Z | 2018-07-27T10:13:10.000Z | # ThinkSNS+ 中文文档
- [开始](get-started)
- [关于 ThinkSNS+](get-started)
- [安装](get-started/installed.md)
- [拓展包](package)
- [开发指南](package)
- [处理器 & 命令](package/console.md)
- [如果更好的开发一个拓展包](package/nice.md)
- [内置开发支持（模拟完整的线上打包，发布流程）](package/dev.md)
- [APIs]
- [概述](api-overview.md)
- Version 2 (REST ful)
- [启动信息](api2/bootstrappers.md)
- [验证码](api2/verification-code.md)
- [位置](api2/locations.md)
- [标签](api2/tags.md)
- [用户](api2/users)
- [授权](api2/users/authorization.md)
- [注册](api2/users/register.md)
- [用户收到的评论](api2/users/comments.md)
- [用户收到的喜欢](api2/users/likes.md)
- [关注](api2/users/followers.md)
- [标签](api2/users/tags.md)
- [身份认证](api2/users/certification.md)
- [找人](api2/find-users.md)
- [排行](api2/users/rank.md)
- [意见反馈](api2/users/feedback.md)
- [消息通知（系统消息）](api2/notifications.md)
- [钱包](api2/wallet)
- [概述](api2/wallet)
- [获取钱包信息](api2/wallet/show.md)
- [提现申请](api2/wallet/cashes.md)
- [余额充值](api2/wallet/recharge.md)
- [凭据](api2/wallet/charge.md)
- [文件](api2/files.md)
- [付费](api2/purchase.md)
- [广告位](api2/ad.md)
- [打赏](api2/reward.md)
- [关于我们](api2/aboutus.md)
| 33.780488 | 49 | 0.51769 | yue_Hant | 0.195168 |
c933e1710b094f52cb9699375096843f85a2c1ca | 16,332 | md | Markdown | wiki/translations/ro/Feature_editing.md | dwhr-pi/FreeCAD-documentation | 0c889672d80e7969dcabe83f5ddf503e72a4f5bb | [
"CC0-1.0"
] | null | null | null | wiki/translations/ro/Feature_editing.md | dwhr-pi/FreeCAD-documentation | 0c889672d80e7969dcabe83f5ddf503e72a4f5bb | [
"CC0-1.0"
] | null | null | null | wiki/translations/ro/Feature_editing.md | dwhr-pi/FreeCAD-documentation | 0c889672d80e7969dcabe83f5ddf503e72a4f5bb | [
"CC0-1.0"
] | null | null | null | # Feature editing/ro
{{TOCright}}
## Introducere
This page explains the way the <img alt="" src=images/Workbench_PartDesign.svg style="width:32px;"> [PartDesign Workbench](PartDesign_Workbench.md) is intended to be used starting with FreeCAD 0.17.
<div class="mw-translate-fuzzy">
În timp ce [Part Workbench](Part_Workbench/ro.md) și alte ateliere FreeCAD construiesc modele prin combinarea formelor împreună, atelierul PartDesign folosește **caracteristicile**. Funcția [1](https://en.wikipedia.org/wiki/Feature_recognition) este o operațiune care modifică forma unui model.
</div>
## Metodologia de editare a funcțiilor
Prima caracteristică este în mod obișnuit numită **caracteristică de bază**. La adăugarea mai multor caracteristici la model, fiecare caracteristică ia forma celei anterioare și adaugă sau înlătură materialul, creând dependențe liniare de la o caracteristică la alta. De fapt, această metodologie imită un proces de fabricație obișnuit: un bloc este tăiat pe o parte, apoi pe altă parte, se adaugă găuri, apoi arce de cerc etc.
Toate funcțiile sunt listate secvențial în arborele Model și pot fi editate în orice moment, ultima caracteristică din partea de jos reprezentând partea finală.
Caracteristicile pot fi sortate în diferite categorii:
- \'\'\' Bazat pe profil \'\'\': aceste caracteristici pornesc de la un profil pentru a defini forma materiei care urmează să fie adăugată sau eliminată. Profilul poate fi o schiță, o față plană pe geometria existentă (un profil va fi extras din marginile sale), un ShapeBinder sau un obiect Draft care a fost inclus în corpul activ.
- \'\'\'Additiv \'\': adaugă material modelului existent. Funcțiile adiționale prezintă iconițele galbene.
- \'\'\' Subtractive \'\'\': elimină materialul din modelul existent. Funcțiile subtitrate prezintă icoanițele roșii și albastre.
- \'\'\' Bazate pe Primitive \'\'\': bazate pe primitive geometrice (cub, cilindru, con, torus \...). Acestea pot fi aditive sau subtractive.
- **Caracteristicile transformării**: aplică o transformare la caracteristicile existente (simetrică, model liniar, model polar, multitransformare).
- *\' Dress-up*\': caracteristici care aplică un tratament pe margini sau fețe, cum ar fi teșire/ rotunjire, șanfren și trasare.
- **Procedural**: se poate spune despre caracteristici care nu se bazează pe schițe, cum ar fi trăsăturile de transformare și traiectoria adițională.
## Corp
<div class="mw-translate-fuzzy">
Lucrul în PartDesign necesită mai întâi crearea unui <img alt="" src=images/PartDesign_Body.png style="width:24px;"> **Corp**. Corpul este un container care grupează o secvență de caracteristici care formează un singur solid contiguu.
</div>
<div class="mw-translate-fuzzy">
Ce este un solid solid contiguu? Este un obiect ca o piesă turnată sau ceva prelucrat dintr-un singur bloc de metal. Dacă obiectul implică cuie, șuruburi, lipici sau sudură, acesta nu este un singur solid contiguu. Ca un exemplu practic, un scaun din lemn ar fi făcut din mai multe corpuri, câte unul pentru fiecare subcomponentă (picioare, șipci, fundul scaunului etc.).
</div>
Corpurile multiple pot fi create într-un document FreeCAD; ele pot fi, de asemenea, combinate pentru a forma un singur solid contiguu.
Only one body can be active in a document. The active body gets the new created features. A body can be activated or deactivated by double clicking on it. An activated body is highlighted in light blue. The highlighting color can be set in the preferences under Display/Colors/Active container since version 0.18.
<div class="mw-translate-fuzzy">
Atunci când un model necesită mai multe corpuri, cum ar fi exemplul precedent de scaun din lemn, scopul general [container part](Std_Part/ro.md) poate fi utilizat pentru a le grupa și a muta întregul ca unitate.
</div>
### Managementul Vizibilității Corpului
Un corp va prezenta implicit caracteristica cea mai recentă spre exterior. Această caracteristică este definită în mod prestabilit ca vârf. O bună analogie este expresia \"vârful aisbergului\": numai vârful este vizibil deasupra apei, cea mai mare parte a masei aisbergului (celelalte caracteristici) este ascunsă. Când o caracteristică nouă este adăugată corpului, vizibilitatea caracteristicii anterioare este dezactivată, iar noua caracteristică devine sfat.
<div class="mw-translate-fuzzy">
Nu poate exista decât o funcție vizibilă la un moment dat. Este posibil să comutați vizibilitatea oricărei caracteristici din corp, selectându-l în arborele Modelului și apăsând bara de spațiu, revenind în istoricul corpului.
</div>
### Originea corpului
Corpul are o origine care constă din planuri de referință (XY, XZ, YZ) și axe (X, Y, Z) care pot fi folosite de către schițe și caracteristici. Schițele pot fi atașate la planurile de origine și nu mai trebuie să fie cartografiate pe fețe plane pentru ca elementele bazate pe ele să fie adăugate sau scăzute din model.
### Mișcarea și Reorientarea Obiectelor
Este posibilă redefinirea temporară a vârfului la o caracteristică din mijlocul arborelui Corpului pentru a insera obiecte noi (caracteristici, schițe sau geometrie de origine). De asemenea, este posibilă reordonarea funcțiilor sub un Corp sau mutarea acestora într-un alt Corp. Selectați obiectul și faceți clic dreapta pentru a obține un meniu contextual care va oferi ambele opțiuni. Operația poate fi împiedicată dacă obiectul are dependențe în corpul sursă, cum ar fi atașarea la o față. Pentru a muta o schiță într-un alt corp, nu ar trebui să conțină legături către geometria exterioară.
### Difference with other CAD systems
A fundamental difference between FreeCAD and other programs, like Catia, is that FreeCAD doesn\'t allow you to have many disconnected solids in the same <img alt="" src=images/PartDesign_Body.svg style="width:24px;"> **[PartDesign Body](PartDesign_Body.md)**. That is, a new feature should always be built on top of the previous one. Or said in a different way, the newer feature should \"touch\" the previous feature, so that both features are fused together and become a single solid. You cannot have \"floating\" solids.
<img alt="" src=images/PartDesign_Body_non-contiguous.png style="width:550px;">
*Difference between Catia and FreeCAD. Left: Catia allows disconnected bodies from the previous features of the body. In FreeCAD this causes an error; Right: the newer feature should always contact or intersect the previous feature so that it is fused to it, and becomes a single contiguous solid.*
## Geometria de referință
<div class="mw-translate-fuzzy">
Geometria de referință constă din planuri personalizate, linii, puncte sau forme legate în exterior. Acestea pot fi create pentru a fi folosite ca referință prin schițe și caracteristici. Există o multitudine de posibilități de atașament pentru date.
</div>
In some CAD systems you can define a datum plane that is offset from the previous body and you can create a disconnected solid. So, placing a lot of datum planes, and building objects on them is okay and won\'t cause an error. Typically, you would eventually adjust the planes to their final positions, so that the individual objects are fused together.
In FreeCAD, as mentioned in the previous section, disconnected solids are **NOT** allowed, so a sketch on a datum plane that would create a non-contiguous solid will fail.
In FreeCAD, datum planes make sense if you are placing sketches (and padding, pocketing, etc.) in non-standard orientations, that is, in planes offset or rotated around the three main axes. Since sketches can also be placed in non-standard orientations in the same way as datum planes, often there is no need to use datum planes.
Datum planes also make sense if there will be more than one sketch in the same non-standard orientation. In this case a datum plane can be used and the orientation only needs to be adjusted for the datum plane to adjust all associated sketches and the features created from the sketches.
Both sketches and datum planes should be attached to base planes. Referencing generated geometry (geometry that is the result of a feature creating operation, for example a pad or pocket) should be avoided since faces and edges get renamed and renumbered and the references no longer refer to the same thing. This is called topological instability and is due the way FreeCAD uses some external geometric libraries. Hopefully this will be improved in the future. (See Advice for creating stable models below).
Even if not used for supporting sketches, datum objects are still helpful as visual indicators, to draw attention to important features or distances in the modelling process. (Though, simply adding geometry to a sketch also provides similar visual feedback.)
<img alt="" src=images/PartDesign_Body_non-contiguous_slanted.png style="width:550px;">
*Difference between Catia and FreeCAD. Left: Catia allows disconnected bodies from the previous features of the body. In FreeCAD this causes an error; Right: the newer feature should always contact or intersect the previous feature, so that it is fused to it, and becomes a single contiguous solid. In this example, the new solid is based on a datum plane that is rotated around the Y axis.*
## Referințe încrușișate
<div class="mw-translate-fuzzy">
Este posibilă trimiterea elementelor dintr-un corp în alt corp prin referințe. De exemplu, liantul de formă de origine permite copierea pe fețe dintr-un corp ca referință în altul. Acest lucru ar trebui să ușureze construirea unei cutii cu capac de montaj în două corpuri diferite. FreeCAD vă ajută să nu vă conectați în mod accidental la alte organisme și să vă întrebe care vă este intenția.
</div>
## Atașament
Obiectul atașat nu este un instrument specific PartDesign, ci mai degrabă un utilitar Partea introdus în v0.17 care poate fi găsit în meniul Part. Este foarte folosită în atelierul PartDesign pentru a atașa schițele și geometria de referință la planurile și axele standard ale Corpului. Sunt disponibile metode foarte extensive de a crea puncte de referință, linii și planuri. Parametrii offset de atașare opțional fac acest instrument foarte versatil.
<div class="mw-translate-fuzzy">
Informații suplimentare pot fi găsite la [Attachment](Part_EditAttachment/ro.md) page.
</div>
## Sfat pentru crearea de modele stabile
<div class="mw-translate-fuzzy">
Ideea de modelare parametrică implică faptul că puteți modifica valorile anumitor parametri, iar pașii ulteriori sunt modificați în funcție de noile valori. Cu toate acestea, atunci când se fac modificări ample, modelul se poate rupe. Comparativ cu versiunile anterioare ale FreeCAD, ruperea poate fi redusă la minimum atunci când respectați următoarele principii de proiectare:
</div>
<div class="mw-translate-fuzzy">
- Practic, trebuie să opriți cartografierea schițelor în fațete - în întregime! Plasați schițele pe planurile standard sau pe planurile de referință personalizate.
- Atunci când creați geometria de origine, nu o bazați pe topologia piesei, bazați-o pe planuri standard / axe și / sau schițe.
- Utilizați o \"schiță master\". Aceasta este o schiță de preferință nu prea complicată care conține elemente geometrice de bază ale modelului dvs. Aceste elemente pot fi menționate la modelarea caracteristicilor ulterioare. O astfel de schiță principală va fi de multe ori prima schiță din Corp, dar nu trebuie să fie; de fapt, nici măcar nu trebuie să-l folosiți deloc pentru altceva decât pentru a fi referit.
- Dacă trebuie să menționați în mod inevitabil o caracteristică intermediară, de ex. rezultatul unei operațiuni de grosime, utilizați prima referință posibilă în lista caracteristicilor ulterioare în care are loc elementul geometric referit. Din FreeCAD 0.17 nu trebuie să utilizați cea mai recentă caracteristică. Dacă luați o caracteristică timpurie ca referință, toate modificările aduse pașilor intermediari nu vă vor sparge modelul. Și din nou, este mai bine să faceți referire la o schiță decât la marginile și vârfurile unui solid.
</div>
## Body building workflow
There are several workflows that are possible with the [PartDesign Workbench](PartDesign_Workbench.md). What should always be noticed is that all the features created inside a [PartDesign Body](PartDesign_Body.md) will be fused together to obtain the final object.
### Different sketches
Sketches need to be supported by a plane. This plane can be one of the main planes (XY, XZ, or YZ) defined by the Origin of the Body. A sketch is either extruded into a positive solid (additive), with a tool like <img alt="" src=images/PartDesign_Pad.svg style="width:24px;"> [PartDesign Pad](PartDesign_Pad.md), or into a negative solid (subtractive), with a tool like <img alt="" src=images/PartDesign_Pocket.svg style="width:24px;"> [PartDesign Pocket](PartDesign_Pocket.md). The first adds volume to the final shape of the body, while the latter cuts volume from the final shape. Any number of sketches and partial solids can be created in this way; the final shape (tip) is the result of fusing these operations together. Naturally, the Body can\'t consist of only subtractive operations, as the final shape should be a solid with a positive, non-zero volume.
<img alt="" src=images/PartDesign_workflow_1.svg style="width:600px;">
### Sequential features
Sketches can be supported by the faces of previous solid operations. This may be necessary if you need to access a face that is only available after a certain feature has been created. However, this workflow isn\'t recommended since, if the original feature is modified, the following features in the sequence may break. This is the [topological naming problem](Topological_naming_problem.md).
<img alt="" src=images/PartDesign_workflow_2.svg style="width:600px;">
### Use of datum planes for support
Datum planes are useful to support the sketches. These auxiliary planes should be attached to the base planes of the body.
\'\'Note: In many cases, a sketch attached to a base plane with attachment offsets can accomplish the same function. Datums are particularly useful when multiple sketches or other constructs will use the datum. This means all changes to the datum will be apply to attached sketches, etc. Adding a single sketch to a datum, rather than using attachment offsets in the sketch properties, is an extra step and is essentially redundant. \'\'
As with sketches, it is possible to attach Datum planes to generated geometry (edges, faces of previously created solids), ***but this is not recommended*** since it can cause the topological naming problem.
In addition, a <img alt="" src=images/PartDesign_ShapeBinder.svg style="width:24px;"> [PartDesign ShapeBinder](PartDesign_ShapeBinder.md) can be used to import external geometry into the body to serve as reference; then sketches can be attached to this auxiliary body, either using datum planes or not.
*Again, the ShapeBinder should be based on Sketches from the previous body, not generated geometry.*
Using datum objects is often the best way to produce stable models, when used with base planes and attachment offsets, although it requires a bit more work from the user. For details about basic attachment see: [Basic Attachment Tutorial](Basic_Attachment_Tutorial.md) *Note: while this tutorial talks about sketches, datum attachment is done in similar fashion.*
## Tutorials
The [tutorials](Tutorials.md) page provides some examples of using the [feature editing](Feature_editing.md) method of the <img alt="" src=images/Workbench_PartDesign.svg style="width:24px;"> [PartDesign Workbench](PartDesign_Workbench.md).
- [Creating a simple part with PartDesign](Creating_a_simple_part_with_PartDesign.md)
- [Basic Part Design Tutorial](Basic_Part_Design_Tutorial.md)
- [Basic Attachment Tutorial](Basic_Attachment_Tutorial.md)
## Related
- [Constructive solid geometry](Constructive_solid_geometry.md)
<img alt="" src=images/PartDesign_workflow_3.svg style="width:600px;">
{{PartDesign Tools navi
}}
---
 [documentation index](../README.md) > [Common Questions](Category_Common Questions.md) > [PartDesign](Category_PartDesign.md) > Feature editing/ro
| 72.910714 | 866 | 0.790963 | ron_Latn | 0.980164 |
c9345e46316e1198260059dafa6417ae24651923 | 21 | md | Markdown | README.md | allen546/serverhttp | 1bc3ec8b1cc0c0f2072d52918ed04a98fe6fa897 | [
"Apache-2.0"
] | null | null | null | README.md | allen546/serverhttp | 1bc3ec8b1cc0c0f2072d52918ed04a98fe6fa897 | [
"Apache-2.0"
] | null | null | null | README.md | allen546/serverhttp | 1bc3ec8b1cc0c0f2072d52918ed04a98fe6fa897 | [
"Apache-2.0"
] | null | null | null | A Simple HTTP Server. | 21 | 21 | 0.809524 | kor_Hang | 0.524038 |
c934fdb10bff74cd9c6107cba9bf325c3edcdc7e | 420 | md | Markdown | CHANGELOG.md | AllenPan03/create-rnpx | 0addf438a5f1fb75280ee8de3d383b9d0b474700 | [
"MIT"
] | null | null | null | CHANGELOG.md | AllenPan03/create-rnpx | 0addf438a5f1fb75280ee8de3d383b9d0b474700 | [
"MIT"
] | null | null | null | CHANGELOG.md | AllenPan03/create-rnpx | 0addf438a5f1fb75280ee8de3d383b9d0b474700 | [
"MIT"
] | null | null | null |
## The new CHNAGELOG will be updated on the [Release page](https://github.com/create-rnpx/releases).
0.0.2 / 2020-06-08
==================
* refact: improve create-rnpx (#25)
* 重构一遍，结构清晰一些
* app 支持 TypeScript，Close #22, Close #17
* app 添加 ESLint 校验、treeShaking 配置
* 优化 ant-design-pro 仓库 clone 时间问题，Close #20
* 优化选择界面的提示文案，Close #24
0.0.1 / 2020-06-08
==================
* fix: update app-project
| 22.105263 | 100 | 0.611905 | yue_Hant | 0.454798 |
c935813c12f4482a678d23e78ae3571a3ad77796 | 29 | md | Markdown | README.md | anakrish/docs | 5445af051ddd940a3615dd8c10abaca30543bd04 | [
"MIT"
] | null | null | null | README.md | anakrish/docs | 5445af051ddd940a3615dd8c10abaca30543bd04 | [
"MIT"
] | null | null | null | README.md | anakrish/docs | 5445af051ddd940a3615dd8c10abaca30543bd04 | [
"MIT"
] | null | null | null | # docs
WIP docs and writeups
| 9.666667 | 21 | 0.758621 | eng_Latn | 0.996111 |
c935a4b9395d52a8c5a1d6ea05fb3683c7767465 | 4,475 | md | Markdown | docs/zh/config/README.md | axibase/vuepress | fd6390aac2f7b1bf67455bb4b21a50ae911d5f11 | [
"MIT"
] | null | null | null | docs/zh/config/README.md | axibase/vuepress | fd6390aac2f7b1bf67455bb4b21a50ae911d5f11 | [
"MIT"
] | null | null | null | docs/zh/config/README.md | axibase/vuepress | fd6390aac2f7b1bf67455bb4b21a50ae911d5f11 | [
"MIT"
] | null | null | null | ---
sidebar: auto
---
# 配置
## 基本配置
### base
- 类型: `string`
- 默认值: `/`
部署站点的基础路径，如果你想让你的网站部署到一个子路径下，你将需要设置它。如 Github pages，如果你想将你的网站部署到 `https://foo.github.io/bar/`，那么 `base` 应该被设置成 `"/bar/"`，它的值应当总是以斜杠开始，并以斜杠结束。
`base` 将会自动地作为前缀插入到所有以 `/` 开始的其他选项的链接中，所以你只需要指定一次。
**Also see:**
- [Base URL](../guide/assets.md#base-url)
- [部署指南 > Github Pages](../guide/deploy.md#github-pages)
### title
- 类型: `string`
- 默认值: `undefined`
网站的标题，它将会被用作所有页面标题的前缀，同时，默认主题下，它将显示在导航栏（navbar）上。
### description
- 类型: `string`
- 默认值: `undefined`
网站的描述，它将会以 `<meta>` 标签渲染到当前页面的 HTML 中。
### head
- 类型: `Array`
- 默认值: `[]`
额外的需要被注入到当前页面的 HTML `<head>` 中的标签，每个标签都可以以 `[tagName, { attrName: attrValue }, innerHTML?]` 的格式指定，举个例子，增加一个自定义的 favicon：
``` js
module.exports = {
head: [
['link', { rel: 'icon', href: '/logo.png' }]
]
}
```
### host
- Type: `string`
- Default: `'0.0.0.0'`
指定用于 dev server 的主机名。
### port
- 类型: `number`
- 默认值: `8080`
指定 dev server 的端口。
### dest
- 类型: `string`
- 默认值: `.vuepress/dist`
指定 `vuepress build` 的输出目录。
### ga
- 类型: `string`
- 默认值: `undefined`
提供一个 Google Analytics ID 来使 GA 生效。
### serviceWorker
- 类型: `boolean`
- 默认值: `false`
如果设置成 `true`，VuePress 将会自动生成并且注册一个 service worker，它缓存了那些已访问过的页面的内容，用于离线访问（仅在生产环境生效）。
如果你正在开发一个自定义主题，`Layout.vue` 组件将会自动触发下述的事件：
- `sw-ready`
- `sw-cached`
- `sw-updated`
- `sw-offline`
- `sw-error`
::: tip PWA NOTES
`serviceWorker` 选项仅仅用来控制 service worker，为了让你的网站完全地兼容 PWA，你需要在 `.vuepress/public` 提供 Manifest 和 icons，更多细节，请参见 [MDN docs about the Web App Manifest](https://developer.mozilla.org/en-US/docs/Web/Manifest).
此外，只有您能够使用 SSL 部署您的站点时才能启用此功能，因为 service worker 只能在 HTTPs 的 URL 下注册。
:::
### locales
- 类型: `{ [path: string]: Object }`
- 默认值: `undefined`
提供多语言支持的语言配置。具体细节请查看 [多语言支持](../guide/i18n.md)。
## 主题
### theme
- 类型: `string`
- 默认值: `undefined`
当你使用自定义主题的时候，需要指定它。当值为 `"foo"` 时，VuePress 将会尝试去加载位于 `node_modules/vuepress-theme-foo/Layout.vue` 的主题组件。
### themeConfig
- 类型: `Object`
- 默认值: `{}`
为当前的主题提供一些配置，这些选项依赖于你正在使用的主题。
**也可以参考:**
- [默认主题](../default-theme-config/)。
## Markdown
### markdown.lineNumbers
- 类型: `boolean`
- 默认值: `undefined`
是否在每个代码块的左侧显示行号。
### markdown.anchor
- 类型: `Object`
- 默认值: `{ permalink: true, permalinkBefore: true, permalinkSymbol: '#' }`
[markdown-it-anchor](https://github.com/valeriangalliat/markdown-it-anchor) 的选项。
### markdown.externalLinks
- Type: `Object`
- Default: `{ target: '_blank', rel: 'noopener noreferrer' }`
这个键值对将会作为特性被增加到是外部链接的 `<a>` 标签上，默认的选项将会在新窗口中打开一个该外部链接。
### markdown.toc
- 类型: `Object`
- 默认值: `{ includeLevel: [2, 3] }`
[markdown-it-table-of-contents](https://github.com/Oktavilla/markdown-it-table-of-contents) 的选项。
### markdown.config
- 类型: `Function`
- 默认值: `undefined`
一个用来对当前的 [markdown-it](https://github.com/markdown-it/markdown-it) 实例应用额外的插件的函数，举例如下：
``` js
module.exports = {
markdown: {
config: md => {
md.use(require('markdown-it-xxx'))
}
}
}
```
## 构建流程
### postcss
- 类型: `Object`
- 默认值: `{ plugins: [require('autoprefixer')] }`
[postcss-loader](https://github.com/postcss/postcss-loader) 的选项，请注意，指定这个值，将会覆盖内置的 autoprefixer，所以你需要自己将它加进去。
### stylus
- Type: `Object`
- Default: `{ preferPathResolver: 'webpack' }`
[stylus-loader](https://github.com/shama/stylus-loader) 的选项。
### scss
- Type: `Object`
- Default: `{}`
加载 `*.scss` 文件的 [sass-loader](https://github.com/postcss/postcss-loader) 的选项。
### sass
- Type: `Object`
- Default: `{ indentedSyntax: true }`
加载 `*.sass` 文件的 [sass-loader](https://github.com/postcss/postcss-loader) 的选项。
### less
- Type: `Object`
- Default: `{}`
[less-loader](https://github.com/webpack-contrib/less-loader) 的选项。
### configureWebpack
- 类型: `Object | Function`
- 默认值: `undefined`
用于修改内部的 Webpack 配置。如果给定一个对象，那么它将会被 [webpack-merge](https://github.com/survivejs/webpack-merge) 合并到最终的配置中，如果给定一个函数，它将会接受 `config` 作为第一个参数，以及 `isServer` 作为第二个参数，你可以直接更改 `config`，也可以返回一个待合并的对象。
``` js
module.exports = {
configureWebpack: (config, isServer) => {
if (!isServer) {
// 修改客户端的 webpack 配置
}
}
}
```
### chainWebpack
- 类型: `Function`
- 默认值: `undefined`
通过 [webpack-chain](https://github.com/mozilla-neutrino/webpack-chain) 来修改内部的 Webpack 配置。
``` js
module.exports = {
chainWebpack: (config, isServer) => {
// config 是 ChainableConfig 的一个实例
}
}
```
## 浏览器兼容性
### evergreen
- 类型: `boolean`
- 默认值: `false`
如果你的对象只有那些 “常青树” 浏览器，你可以将其设置成 `true`，这将会禁止 ESNext 到 ES5 的转译以及对 IE 的 polyfills，同时会带来更快的构建速度和更小的文件体积。
| 17.828685 | 203 | 0.665922 | yue_Hant | 0.61948 |
c9382831e5fc258a94fab1847c4d21fa6924866d | 4,185 | markdown | Markdown | README.markdown | jdsutherland/sideways.vim | 8aa2579a55c003df72c20796e7e70ca6c98196d0 | [
"MIT"
] | 2 | 2020-02-05T19:31:49.000Z | 2020-04-20T05:32:32.000Z | README.markdown | jdsutherland/sideways.vim | 8aa2579a55c003df72c20796e7e70ca6c98196d0 | [
"MIT"
] | 5 | 2020-10-15T07:07:18.000Z | 2021-04-27T13:14:38.000Z | README.markdown | jdsutherland/sideways.vim | 8aa2579a55c003df72c20796e7e70ca6c98196d0 | [
"MIT"
] | null | null | null | [](http://travis-ci.org/AndrewRadev/sideways.vim)
## Usage
The plugin defines two commands, `:SidewaysLeft` and `:SidewaysRight`, which
move the item under the cursor left or right, where an "item" is defined by a
delimiter. As an example:
``` python
def function(one, two, three):
pass
```
Placing the cursor on "two" and executing `:SidewaysLeft`, the "one" and "two"
arguments will switch their places, resulting in this:
``` python
def function(two, one, three):
pass
```
In this case, the delimiter is a comma. The plugin currently works with
various other cases and it's intended to make the process configurable. While
this particular example is in python, this should work for arguments in many
different languages that use round braces to denote function calls.
For ruby and eruby, it detects **method calls without braces** as well:
``` ruby
link_to user_registration_path, 'Something'
# changes to:
link_to 'Something', user_registration_path
```
Apart from functions, it works for **square-bracket lists** in dynamic languages:
``` python
list = [one, [two, four, five], three]
```
If you experiment with this example, you'll find that you can move the entire
second list around, as long as the cursor is on one of the inner brackets. The
plugin takes into consideration nested structures.
It also works for multiline lists. Try experimenting with this example:
``` html
<div class="example"
style="color: red;"
something="other">
Example
</div>
```
It's highly recommended to map the two main commands to convenient keys. For
example, mapping them to `<c-h>` and `<c-l>` would look like this:
``` vim
nnoremap <c-h> :SidewaysLeft<cr>
nnoremap <c-l> :SidewaysRight<cr>
```
The plugin also provides the commands `:SidewaysJumpLeft` and
`:SidewaysJumpRight`, which move the cursor left and right by items.
Other things that sideways works for:
**CSS declarations**:
``` css
a { color: #fff; background: blue; text-decoration: underline; }
```
**Lists within CSS declarations**:
``` css
border-radius: 20px 0 0 20px;
```
**HTML attributes**:
``` html
<input name="one" id="two" class="three" />
```
**Handlebars components**:
``` handlebars
{{parent/some-component one=two three="four" five=(action 'six')}}
```
**Cucumber tables**:
``` cucumber
Examples:
| input_1 | input_2 | button | output |
| 20 | 30 | add | 50 |
| 2 | 5 | add | 7 |
| 0 | 40 | add | 40 |
```
**Rust template arguments**:
``` rust
let dict = Hash<String, Vec<String>>::new();
```
**Rust return type** (a special case since there's always just one, useful as a text object):
``` rust
fn example() -> Result<String, String> {
```
**Go lists**:
``` go
[]string{"One", "Two", "Three"}
```
**C++ templates**:
``` cpp
/*
* Relies on "<" being surrounded by non-whitespace, or considers it a
* comparison. Parsing C++ is tricky.
*/
std::unordered_map<k, v>()
```
**Javascript-like objects**:
``` python
dict = {one: 1, two: 2, three: 3}
```
**OCaml lists**:
``` ocaml
let xs = [1;2;3]
```
The plugin is intended to be customizable, though at this point you'd need to
look at the source to do this.
## Bonus functionality
The plugin's machinery makes it easy to implement an "argument" text object.
There are two mappings provided:
<Plug>SidewaysArgumentTextobjA
<Plug>SidewaysArgumentTextobjI
These are the outer and inner text objects, respectively. To use them, you
need to create mappings in your configuration files. Something like this:
``` vim
omap aa <Plug>SidewaysArgumentTextobjA
xmap aa <Plug>SidewaysArgumentTextobjA
omap ia <Plug>SidewaysArgumentTextobjI
xmap ia <Plug>SidewaysArgumentTextobjI
```
This will map the "a" text object to operate on an "argument". So, you can
perform `daa` to delete an argument, `cia` to change an argument, and so on.
See `:help text-objects` for more information.
Also, a useful plugin to use alongside sideways is
[fieldtrip](https://github.com/tek/vim-fieldtrip). This defines a
[submode](https://github.com/kana/vim-submode) for sideways.vim.
| 25.993789 | 137 | 0.701314 | eng_Latn | 0.986389 |
c9391caa964698bf8e5b69090e069f62bc16e834 | 520 | md | Markdown | README.md | CJBright/BASH | 29881d30b211544f65d8423db27408391c28310f | [
"Linux-OpenIB"
] | null | null | null | README.md | CJBright/BASH | 29881d30b211544f65d8423db27408391c28310f | [
"Linux-OpenIB"
] | null | null | null | README.md | CJBright/BASH | 29881d30b211544f65d8423db27408391c28310f | [
"Linux-OpenIB"
] | null | null | null | <img src="Tux.png" align="right" width="177px" height="210px"/>
>Welcome to my BASH repo!
<ol>For notes on how to Linux and System Administration please refer to my <a href="https://github.com/CJBright/">website</a>.</ol>
<ol>The documents in this repo are simplistic functions for jobscript and application execution within a Linux system.</ol>
<ol>The work carries no license and may be adapted for use.
In these cases please note that absolute paths and file names should be adapted for use in your work. </ol>
</ol> | 65 | 131 | 0.753846 | eng_Latn | 0.989241 |
c9397af869b378eae546834226c94afe776266e3 | 2,319 | md | Markdown | cadence/migrations.md | rjshrjndrn/banzai-charts | af76d29045dd5677eddacbba50d51367433f6d01 | [
"Apache-2.0"
] | 1 | 2020-02-17T03:08:34.000Z | 2020-02-17T03:08:34.000Z | cadence/migrations.md | rjshrjndrn/banzai-charts | af76d29045dd5677eddacbba50d51367433f6d01 | [
"Apache-2.0"
] | null | null | null | cadence/migrations.md | rjshrjndrn/banzai-charts | af76d29045dd5677eddacbba50d51367433f6d01 | [
"Apache-2.0"
] | null | null | null | # Running migrations for Cadence
As of version 0.7.1 the production Cadence image does not automatically run migrations.
While the helm chart provides a way to automatically run them,
it's recommended to run them manually before installing/upgrading Cadence.
This guide contains commands to run migrations on Cassandra or MySQL.
The first step is to start a new shell in a Cadence container:
```bash
export CADENCE_VERSION=0.7.1
docker run --rm -it ubercadence/server:${CADENCE_VERSION} bash
```
## Cassandra
Set up environment variables:
```bash
export CASSANDRA_HOST=docker.for.mac.host.internal
export CASSANDRA_PORT=9042
# Optionally:
# export CASSANDRA_USER=
# export CASSANDRA_PASSWORD=
export CADENCE_KEYSPACE=cadence
export VISIBILITY_KEYSPACE=cadence_visibility
```
### Create keyspaces
```bash
cadence-cassandra-tool create -k ${CADENCE_KEYSPACE}
cadence-cassandra-tool create -k ${VISIBILITY_KEYSPACE}
```
### Set up schema for the first time
```bash
CASSANDRA_KEYSPACE=${CADENCE_KEYSPACE} cadence-cassandra-tool setup-schema -v 0.0
CASSANDRA_KEYSPACE=${VISIBILITY_KEYSPACE} cadence-cassandra-tool setup-schema -v 0.0
```
### Update schema
```bash
CASSANDRA_KEYSPACE=${CADENCE_KEYSPACE} cadence-cassandra-tool update-schema -d /etc/cadence/schema/cassandra/cadence/versioned
CASSANDRA_KEYSPACE=${VISIBILITY_KEYSPACE} cadence-cassandra-tool update-schema -d /etc/cadence/schema/cassandra/visibility/versioned
```
## MySQL
Set up environment variables:
```bash
export SQL_DRIVER=mysql
export SQL_HOST=docker.for.mac.host.internal
export SQL_PORT=3306
# Optionally:
# export SQL_USER=
# export SQL_PASSWORD=
export CADENCE_DATABASE=cadence
export VISIBILITY_DATABASE=cadence_visibility
```
### Create databases
```bash
cadence-sql-tool create --db ${CADENCE_DATABASE}
cadence-sql-tool create --db ${VISIBILITY_DATABASE}
```
### Set up schema for the first time
```bash
SQL_DATABASE=${CADENCE_DATABASE} cadence-sql-tool setup-schema -v 0.0
SQL_DATABASE=${VISIBILITY_DATABASE} cadence-sql-tool setup-schema -v 0.0
```
### Update schema
```bash
SQL_DATABASE=${CADENCE_DATABASE} cadence-sql-tool update-schema -d /etc/cadence/schema/mysql/v57/cadence/versioned
SQL_DATABASE=${VISIBILITY_DATABASE} cadence-sql-tool update-schema -d /etc/cadence/schema/mysql/v57/visibility/versioned
```
| 24.935484 | 132 | 0.786546 | yue_Hant | 0.375319 |
c939eeec465dddedbf7227f3e6f770bd85b03f33 | 602 | md | Markdown | pages.es/common/git-commit.md | irfanirshad/tldr | ae1241967d9e66f292e669ae1f96c034da06d2f6 | [
"CC-BY-4.0"
] | 3 | 2020-04-28T11:14:55.000Z | 2020-06-08T21:15:36.000Z | pages.es/common/git-commit.md | irfanirshad/tldr | ae1241967d9e66f292e669ae1f96c034da06d2f6 | [
"CC-BY-4.0"
] | 1 | 2021-02-06T13:18:36.000Z | 2021-02-06T13:18:36.000Z | pages.es/common/git-commit.md | irfanirshad/tldr | ae1241967d9e66f292e669ae1f96c034da06d2f6 | [
"CC-BY-4.0"
] | 3 | 2020-07-26T16:51:50.000Z | 2020-08-18T07:06:49.000Z | # git commit
> Realiza commits de los archivos al repositorio.
> Más información: <https://git-scm.com/docs/git-commit>.
- Raliza un commit de los archivos marcados al repositorio con un mensaje:
`git commit -m {{mensaje}`
- Marca automáticamente todos los archivos modificados y realiza un commit con un mensaje:
`git commit -a -m {{mensaje}}`
- Sustituye el último commit con los cambios marcados actualmente:
`git commit --amend`
- Realiza un commit para unos archivos específicos (que ya deben haber sido marcados previamente):
`git commit {{ruta/de/mi/archivo1}} {{ruta/de/mi/archivo2}}`
| 28.666667 | 98 | 0.747508 | spa_Latn | 0.988079 |
c93a353f609ac0f0be29198acb1c052be3fb2d39 | 492 | md | Markdown | content/project-activity/completed/hd-wallets.ru.md | btechn01/navcoin-org | 4d8d774910956573642cfbc15f6304170fad73e8 | [
"MIT"
] | null | null | null | content/project-activity/completed/hd-wallets.ru.md | btechn01/navcoin-org | 4d8d774910956573642cfbc15f6304170fad73e8 | [
"MIT"
] | null | null | null | content/project-activity/completed/hd-wallets.ru.md | btechn01/navcoin-org | 4d8d774910956573642cfbc15f6304170fad73e8 | [
"MIT"
] | null | null | null | ---
layout: roadmap
title: Иерархические детерминированные кошельки
author: Soopy452000
date: '2016-05-13'
feature_image: /images/uploads/navpi-patch.jpg
status: completed
externalUrl: https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki
---
После смены базы протокола Navcoin в 2016-ом году, в Navcoin Core был реализован BIP32. Теперь адреса генерируются детерминистически из главного закрытого ключа, что устраняет необходимость в частом резервном копировании вашего кошелька.
| 41 | 237 | 0.819106 | rus_Cyrl | 0.898805 |
c93ab6199ada4b04f408bdaa1c03bb1e37fb34cb | 2,730 | md | Markdown | content/publication/bail-exposure-2018/index.md | marcone84/academic-kickstart | b82b0587fa6263e5514af952d5469c69ca373d52 | [
"MIT"
] | null | null | null | content/publication/bail-exposure-2018/index.md | marcone84/academic-kickstart | b82b0587fa6263e5514af952d5469c69ca373d52 | [
"MIT"
] | null | null | null | content/publication/bail-exposure-2018/index.md | marcone84/academic-kickstart | b82b0587fa6263e5514af952d5469c69ca373d52 | [
"MIT"
] | null | null | null | ---
title: "Exposure to opposing views on social media can increase political polarization"
date: 2018-08-01
publishDate: 2020-02-03T21:37:00.903857Z
authors: ["Christopher A Bail", "Lisa P Argyle", "Taylor W Brown", "John P Bumpus", "Haohan Chen", "M B Fallin Hunzaker", "Jaemin Lee", "Marcus Mann", "Friedolin Merhout", "Alexander Volfovsky"]
publication_types: ["2"]
abstract: "Social media sites are often blamed for exacerbating political polarization by creating “echo chambers” that prevent people from being exposed to information that contradicts their preexisting beliefs. We conducted a field experiment that offered a large group of Democrats and Republicans financial compensation to follow bots that retweeted messages by elected officials and opinion leaders with opposing political views. Republican participants expressed substantially more conservative views after following a liberal Twitter bot, whereas Democrats' attitudes became slightly more liberal after following a conservative Twitter bot—although this effect was not statistically significant. Despite several limitations, this study has important implications for the emerging field of computational social science and ongoing efforts to reduce political polarization online.There is mounting concern that social media sites contribute to political polarization by creating “echo chambers” that insulate people from opposing views about current events. We surveyed a large sample of Democrats and Republicans who visit Twitter at least three times each week about a range of social policy issues. One week later, we randomly assigned respondents to a treatment condition in which they were offered financial incentives to follow a Twitter bot for 1 month that exposed them to messages from those with opposing political ideologies (e.g., elected officials, opinion leaders, media organizations, and nonprofit groups). Respondents were resurveyed at the end of the month to measure the effect of this treatment, and at regular intervals throughout the study period to monitor treatment compliance. We find that Republicans who followed a liberal Twitter bot became substantially more conservative posttreatment. Democrats exhibited slight increases in liberal attitudes after following a conservative Twitter bot, although these effects are not statistically significant. Notwithstanding important limitations of our study, these findings have significant implications for the interdisciplinary literature on political polarization and the emerging field of computational social science."
featured: false
publication: "*Proceedings of the National Academy of Sciences*"
url_pdf: "http://www.pnas.org/content/early/2018/08/27/1804840115.abstract"
---
| 210 | 2,197 | 0.827473 | eng_Latn | 0.999122 |
c93b5116bff475b564f5b3681d2befc5d496d3a2 | 314 | md | Markdown | examples/wasm-client/README.md | CptCrispyCrunchy/tonic-ws-transport | 17c7c1892bfede3b5aaf42cd61369c918cbee47f | [
"Apache-2.0",
"MIT"
] | 10 | 2020-11-20T08:30:06.000Z | 2021-12-18T22:33:18.000Z | examples/wasm-client/README.md | CptCrispyCrunchy/tonic-ws-transport | 17c7c1892bfede3b5aaf42cd61369c918cbee47f | [
"Apache-2.0",
"MIT"
] | 4 | 2021-07-13T10:48:15.000Z | 2022-02-01T09:35:03.000Z | examples/wasm-client/README.md | CptCrispyCrunchy/tonic-ws-transport | 17c7c1892bfede3b5aaf42cd61369c918cbee47f | [
"Apache-2.0",
"MIT"
] | 2 | 2021-08-16T05:47:37.000Z | 2021-12-21T08:24:44.000Z | # gRPC over WebSocket wasm example
You'll need [wasm-pack](https://github.com/rustwasm/wasm-pack) to build the wasm module from the
source code.
```
wasm-pack build --target web
```
Then start a local HTTP server in this directory, e.g.
```
python3 -m http.server
```
and navigate to its root in the browser.
| 18.470588 | 96 | 0.719745 | eng_Latn | 0.967281 |
c93b731728a80e95440f44762adb3dbe95ace95a | 41 | md | Markdown | README.md | sinnlosername/go-haste | d4b0170a60d38c0092879fe491501d1b49d47965 | [
"Apache-2.0"
] | null | null | null | README.md | sinnlosername/go-haste | d4b0170a60d38c0092879fe491501d1b49d47965 | [
"Apache-2.0"
] | null | null | null | README.md | sinnlosername/go-haste | d4b0170a60d38c0092879fe491501d1b49d47965 | [
"Apache-2.0"
] | null | null | null | # Go-Haste
A haste client written in go. | 13.666667 | 29 | 0.731707 | eng_Latn | 0.994867 |
c93b8a81139ae3744948b211d474c3f5019b5f33 | 1,557 | md | Markdown | AlchemyInsights/sign-out-of-outlook-on-the-web.md | isabella232/OfficeDocs-AlchemyInsights-pr.sk-SK | 8fd17c4b16a3370a34bbb761d4edc9f8dfb2784a | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-05-19T19:07:47.000Z | 2021-04-21T00:13:49.000Z | AlchemyInsights/sign-out-of-outlook-on-the-web.md | MicrosoftDocs/OfficeDocs-AlchemyInsights-pr.sk-SK | a4bdea6e681ab468fe3d8f0c6ea9c8f4f1c0af6f | [
"CC-BY-4.0",
"MIT"
] | 3 | 2020-06-02T23:29:32.000Z | 2022-02-09T06:59:11.000Z | AlchemyInsights/sign-out-of-outlook-on-the-web.md | isabella232/OfficeDocs-AlchemyInsights-pr.sk-SK | 8fd17c4b16a3370a34bbb761d4edc9f8dfb2784a | [
"CC-BY-4.0",
"MIT"
] | 3 | 2019-10-09T20:33:51.000Z | 2021-10-09T10:38:46.000Z | ---
title: Odhlásenie z Outlooku na webe
ms.author: pebaum
author: pebaum
manager: scotv
ms.audience: Admin
ms.topic: article
ms.service: o365-administration
ROBOTS: NOINDEX, NOFOLLOW
localization_priority: Priority
ms.collection: Adm_O365
ms.custom:
- "8000008"
- "1993"
ms.openlocfilehash: acac4252ce8a7d3b858355de5545080fe7299d0dce7e28db05436e2b06e8c3f6
ms.sourcegitcommit: b5f7da89a650d2915dc652449623c78be6247175
ms.translationtype: MT
ms.contentlocale: sk-SK
ms.lasthandoff: 08/05/2021
ms.locfileid: "54084802"
---
# <a name="sign-out-of-outlook-on-the-web"></a>Odhlásenie z Outlooku na webe
1. Kliknite na obrázok alebo iniciály konta v pravom hornom rohu obrazovky. Ak sa v hornej časti obrazovky nezobrazuje váš obrázok, skontrolujte, či nie je zapnutá funkcia blokovania reklamy. Táto funkcia niekedy zabraňuje zobrazeniu obrázka.
2. Kliknite na položku **Odhlásiť sa**. (Ak chcete Outlooku na webe zabrániť automatickému prihlasovaniu do pracovného alebo školského konta, pri ďalšom prihlásení zrušte začiarknutie políčka **Neodhlasovať ma**.)
3. Ak chýba možnosť odhlásenia, ide o známy problém a pracujeme na vydaní opravy v budúcom vydaní. Skúste vymazať vyrovnávaciu pamäť prehliadača a súbory cookie. Problém sa tak možno vyrieši. Ak sa nevyrieši, môžete [sa manuálne odhlásiť z konta](https://login.live.com/logout.srf) a zatvoriť všetky okná prehliadača.
Ďalšie informácie nájdete v téme [Prihlásenie do Outlooku na webe](https://support.office.com/article/how-to-sign-in-to-outlook-on-the-web-763fab4d-0138-4814-b450-37fc286bcb79).
| 50.225806 | 319 | 0.807964 | slk_Latn | 0.996035 |
c93c65bd33886949dddbd2d9629af33d12a7a04f | 2,981 | md | Markdown | book/src/using/builder_api.md | stevelr/rust-atelier | 131a9af7cae223497d35dadd79721092de25c0ec | [
"MIT"
] | 54 | 2020-07-02T19:00:32.000Z | 2022-03-31T17:01:31.000Z | book/src/using/builder_api.md | stevelr/rust-atelier | 131a9af7cae223497d35dadd79721092de25c0ec | [
"MIT"
] | 24 | 2020-07-28T14:50:52.000Z | 2022-02-25T22:06:42.000Z | book/src/using/builder_api.md | stevelr/rust-atelier | 131a9af7cae223497d35dadd79721092de25c0ec | [
"MIT"
] | 9 | 2020-09-23T19:27:35.000Z | 2022-03-31T03:37:15.000Z | # Using the Builder API
The following example demonstrates the builder interface to create the same service as the example
above. Hopefully this is more readable as it tends to be less repetative, uses `&str` for
identifiers, and includes helper functions for common traits for example. It provides this better
_construction experience_ (there are no read methods on builder objects) by compromising two aspects:
1. The API itself is very repetative; this means the same method may be on multiple objects, but
makes it easier to use. For example, you want to add the documentation trait to a shape, so you can:
1. construct a `Trait` entity using the core model and the `Builder::add_trait` method,
1. use the `TraitBuilder::documentation` method which also takes the string to use as the trait
value and returns a new `TraitBuilder`, or
1. use the `Builder::documentation` method that hides all the details of a trait and just takes
a string.
1. It hides a lot of the `Identifier` and `ShapeID` construction and so any of those calls to
`from_str` may fail when the code unwraps the result. This means the builder can panic in ways
the core model does not.
```rust
use atelier_core::builder::traits::ErrorSource;
use atelier_core::builder::values::{ArrayBuilder, ObjectBuilder};
use atelier_core::builder::{
traits, ListBuilder, MemberBuilder, ModelBuilder, OperationBuilder, ResourceBuilder,
ServiceBuilder, ShapeTraits, SimpleShapeBuilder, StructureBuilder, TraitBuilder,
};
use atelier_core::model::{Identifier, Model, ShapeID};
use atelier_core::Version;
use std::convert::TryInto;
let model: Model = ModelBuilder::new(Version::V10, "example.motd")
.service(
ServiceBuilder::new("MessageOfTheDay", "2020-06-21")
.documentation("Provides a Message of the day.")
.resource("Message")
.into(),
)
.resource(
ResourceBuilder::new("Message")
.identifier("date", "Date")
.read("GetMessage")
.into(),
)
.simple_shape(
SimpleShapeBuilder::string("Date")
.apply_trait(traits::pattern(r"^\d\d\d\d\-\d\d-\d\d$"))
.into(),
)
.operation(
OperationBuilder::new("GetMessage")
.readonly()
.input("GetMessageInput")
.output("GetMessageOutput")
.error("BadDateValue")
.into(),
)
.structure(
StructureBuilder::new("GetMessageInput")
.member("date", "Date")
.into(),
)
.structure(
StructureBuilder::new("GetMessageOutput")
.add_member(MemberBuilder::string("message").required().into())
.into(),
)
.structure(
StructureBuilder::new("BadDateValue")
.error_source(ErrorSource::Client)
.add_member(MemberBuilder::string("errorMessage").required().into())
.into(),
)
.try_into().unwrap();
```
| 39.746667 | 103 | 0.658839 | eng_Latn | 0.888839 |
c93c8409045997d5bd4f3d39d983eaf3ee5fb536 | 5,589 | md | Markdown | 07_sql/06_aggregations.md | TheBeege/jazzy_programming | 16f1690c2bf1c11c1cfbc576de9ebf9de5c6fde8 | [
"MIT"
] | null | null | null | 07_sql/06_aggregations.md | TheBeege/jazzy_programming | 16f1690c2bf1c11c1cfbc576de9ebf9de5c6fde8 | [
"MIT"
] | null | null | null | 07_sql/06_aggregations.md | TheBeege/jazzy_programming | 16f1690c2bf1c11c1cfbc576de9ebf9de5c6fde8 | [
"MIT"
] | null | null | null | # Aggregations
Next, we'll go over aggregations, which is the most likely type of query you'll be running for either data analysis or data science. Essentially, we'll be focusing on writing `SELECT` statements that aggregate and summarize data in a meaningful way to show to customers within your organization. Put on your smart-looking glasses, cuz we 'bout to do some SCIENCE! (But not data science, cuz I don't actually know how to do that shit.)
First, let's setup a new table that we might want to do analytics on:
```sql
create table call_log (
call_time timestamp not null default current_timestamp,
employee_id int not null,
origin_number varchar(13) not null,
duration_seconds int not null,
primary key (call_time, employee_id),
index call_log_reverse_index (employee_id, call_time),
index call_log_index_origin_number (origin_number)
);
```
Let's setup a new [DB-Fiddle](https://www.db-fiddle.com/f/asg5kM7LBkMJLKgvizTyyK/0) for you based on this.
Alright, so your boss wants to know which department gets the most phone calls. Let's write a query to find this out.
```sql
select
d.name,
count(1) as count_calls
from department d
join employee e
on e.department_id = d.id
join call_log l
on l.employee_id = e.id
group by d.name
```
There's no direct connection from department to call_log, so we have to go through employee. It doesn't matter if we start from department or from call_log. The database optimizer is smart enough under the hood to take care of efficiency of join order for you. You just need to make sure your logic is accurate. First, we grab all departments. Next, we connect those to the departments' employees. Lastly, we link those employees to the calls they've received. Once we've got the data connected, we can do our aggregation. It's sometimes helpful to verbalize what you want to help you get the right query. In this case, we want the "count of calls by department". We're doing the "<aggregate> of <measuring entity> by <grouping entity>". The <aggregate> is your aggregate function, in this case, `COUNT`. The <measuring entity> is the field you want to measure. Since we're counting, we just care about the number of records returned. The field doesn't matter. Lastly, we're grouping by the <grouping entity>, in this case, department. Since departments are unique by name, we can just group by their name. You need to also make sure you group by whatever you want to display, otherwise you'll get weird behavior.
Note also that we did `COUNT(1)`. This is shorthand. The `1` is actually the first field returned by the statement. Since we're counting records, it doesn't actually matter which field you specify. However, what if you wanted to count the number of distinct callers per department?
```sql
select
d.name,
count(distinct l.origin_number) as count_distinct_callers
from department d
join employee e
on e.department_id = d.id
join call_log l
on l.employee_id = e.id
group by d.name
```
This query will show the number of distinct callers per department. We're counting only `DISTINCT` instances of the origin number. This is especially useful, but I strongly recommend it only be done on indexed fields, similar to any `GROUP BY` phrases.
What if we wanted to see the total number of hours each employee has spent on the phone?
```sql
select
d.name as department,
e.name as employee,
round(sum(l.duration_seconds)/60) as total_call_duration_minutes
from department d
join employee e
on d.id = e.department_id
join call_log l
on e.id = l.employee_id
group by
d.name,
e.name
```
We have a few things going on here. We're using a new aggregate function, `SUM`. We're also using a number function `ROUND` to round the result of our division up to a whole number. Note that you should do your summation before your mathematical operations. If you have a lot of calls that are 89 seconds, for example, you could end up missing a large amount of time over a lot of records.
How about average number of calls per day of the week?
```sql
select
dayname(call_date),
avg(count_calls)
from (
select
date(call_time) as call_date,
count(1) as count_calls
from call_log
group by
date(call_time)
) as calls_per_day
group by
dayname(call_date)
```
This is new. We're doing a sub-select inside our `FROM` phrase. Let's look at the sub-select first:
```sql
select
date(call_time) as call_date,
count(1) as count_calls
from call_log
group by
date(call_time)
```
This gives us our total number of calls per date. Inside the larger query, we wrap this in parentheses and toss an `AS ...` at the end. This creates a "virtual table". The database creates a temporary table out of our select statement that it can use for further operations. It all happens in memory, so it's usually pretty fast, as long as the data isn't too large. It's a good idea to make sure that sub-selects are a limited set of data, like an aggregation. If your sub-select takes up too much memory, it will end up swapping to disk, bringing your query performance to a crawl. However, once we have our sub-select setup, we can treat it just like a table whose columns are the field aliases from the sub-select. From there, we just average the number of calls by the `DAYNAME()` of the call date. Fancy.
Again, sub-selects are virtual tables, so you can use them in `JOIN` phrases as well. This is helpful if you need to do joins of data or filtering based on aggregations.
See if you can come up with more interesting aggregations that you may want to report to a stakeholder or manager.
| 53.228571 | 1,213 | 0.765074 | eng_Latn | 0.999532 |
c93cdaa41777ded8d2fbfd931fd4dd3d7c8641d7 | 703 | md | Markdown | exampleSite/content/docs/archives/index.zh-cn.md | mluengas/hugo-theme-bootstrap | 070ff18fa3b232c99f2f9634275fb5cc303a7c98 | [
"MIT"
] | null | null | null | exampleSite/content/docs/archives/index.zh-cn.md | mluengas/hugo-theme-bootstrap | 070ff18fa3b232c99f2f9634275fb5cc303a7c98 | [
"MIT"
] | null | null | null | exampleSite/content/docs/archives/index.zh-cn.md | mluengas/hugo-theme-bootstrap | 070ff18fa3b232c99f2f9634275fb5cc303a7c98 | [
"MIT"
] | null | null | null | +++
title = "归档页面"
description = ""
date = 2021-12-03T11:16:51+08:00
featured = false
comment = true
toc = true
reward = true
categories = [
"归档"
]
tags = [
]
series = [
"文档"
]
images = []
aliases = [
"/zh-cn/posts/archives"
]
[menu.footer]
parent = "docs"
weight = 7
pre = '<i class="fas fa-fw fa-file-archive"></i>'
+++
归档页面按照年份对文章进行归档。
<!--more-->
## 前置条件
我們需要在 `content` 目錄下創建一個名為 `archives/_ index.md` 的檔案。
```toml
+++
title = "归档"
layout = "archive"
+++
```
## Site Parameters
| 名称 | 类型 | 默认值 | 描述
|---|:-:|:-:|---
| `archive` | Object | - | Archive.
| `archive.paginate` | Integer | `100` | Archive pagination.
| `archive.dateFormat` | Integer | `Jan 2` | Archive date format.
| 14.346939 | 65 | 0.58606 | yue_Hant | 0.477482 |
c93d0d0808e476a6f2138218242ab3be8a08d61a | 683 | md | Markdown | includes/azure-stack-edge-gateway-manage-personal-data.md | wastu01/azure-docs.zh-tw | 7ee2fba199b6243c617953684afa67b83b2acc82 | [
"CC-BY-4.0",
"MIT"
] | 66 | 2017-08-24T10:28:13.000Z | 2022-03-04T14:01:29.000Z | includes/azure-stack-edge-gateway-manage-personal-data.md | wastu01/azure-docs.zh-tw | 7ee2fba199b6243c617953684afa67b83b2acc82 | [
"CC-BY-4.0",
"MIT"
] | 534 | 2017-06-30T19:57:07.000Z | 2022-03-11T08:12:44.000Z | includes/azure-stack-edge-gateway-manage-personal-data.md | wastu01/azure-docs.zh-tw | 7ee2fba199b6243c617953684afa67b83b2acc82 | [
"CC-BY-4.0",
"MIT"
] | 105 | 2017-07-04T11:37:54.000Z | 2022-03-20T06:10:38.000Z | ---
author: alkohli
ms.service: databox
ms.topic: include
ms.date: 04/16/2019
ms.author: alkohli
ms.openlocfilehash: af4c3829c8b12bfcaae0602dde8f459de7e50f3a
ms.sourcegitcommit: 6a350f39e2f04500ecb7235f5d88682eb4910ae8
ms.translationtype: MT
ms.contentlocale: zh-TW
ms.lasthandoff: 12/01/2020
ms.locfileid: "96466374"
---
- **訂單詳細資料**。 建立訂單時，使用者的交貨位址、電子郵件地址及連絡人資訊都會儲存在 Azure 入口網站中。 儲存的資訊包括︰
- 連絡人姓名
- 電話號碼
- 電子郵件地址
- 街道地址
- City
- 郵遞區號
- 州
- 國家/地區/地區
- 運送追蹤號碼
訂單詳細資料會經過加密，並儲存在服務中。 服務會保留資訊，直到您明確刪除資源或訂單。 從裝置送出到 Microsoft 之前，會封鎖刪除資源和對應的順序。
- **送貨位址**。 訂購之後，資料箱服務會提供協力廠商貨運公司（例如 UPS）的送貨位址。
- **共用使用者**。 您裝置上的使用者也可以存取位於共用上的資料。 可以查看可以存取共用資料的使用者清單。 刪除共用時，也會一併刪除此清單。 | 23.551724 | 81 | 0.75549 | yue_Hant | 0.988133 |
c93df64b655456cedfdf5a0feba151b53121d595 | 5,230 | md | Markdown | _posts/2014-08-08-reflecting-and-blogging-about-the-complexity-of-fruit-salad-trees-tgif-39.md | co16353sidak/hood.ie | aa4f83451814221b0989132280eb0114ac427a70 | [
"Apache-2.0"
] | 68 | 2015-01-11T22:10:13.000Z | 2021-12-14T11:05:23.000Z | _posts/2014-08-08-reflecting-and-blogging-about-the-complexity-of-fruit-salad-trees-tgif-39.md | co16353sidak/hood.ie | aa4f83451814221b0989132280eb0114ac427a70 | [
"Apache-2.0"
] | 236 | 2015-01-08T04:30:47.000Z | 2019-10-19T16:56:38.000Z | _posts/2014-08-08-reflecting-and-blogging-about-the-complexity-of-fruit-salad-trees-tgif-39.md | co16353sidak/hood.ie | aa4f83451814221b0989132280eb0114ac427a70 | [
"Apache-2.0"
] | 76 | 2015-01-08T17:54:32.000Z | 2020-10-02T18:22:09.000Z | ---
title: 'Reflections on offline first and blogging about the complexity of fruit salad trees: TGIF! (39)'
author: Lena
layout: blog-post-tgif
---
Thank Grohl, Gauss, Glob, Galileo and Science it’s Friday! The week’s (almost) over, and these are our reading recommendations, curated for you by Julia and Lena, for your weekend or a lazy afternoon. Enjoy!
**Open Source**
<p>
The <a href="http://training.linuxfoundation.org/free-linux-training/linux-training-scholarship-program">Linux Training Scholarship Program</a> is accepting applications until the beginning of September.
</p>
<p>
Meet the Hoodies! In the next two months, we’ll be giving talks in Bonn, Edinburgh, Berlin, Istanbul (all details <a href="http://blog.hood.ie/2014/08/hoodietime-events-and-conferences-with-hoodies-in-august-and-september-2014/">here</a>). Looking forward to meeting you there!
</p>
<p>
The <a href="http://blog.couchdb.org/2014/08/07/couchdb-weekly-news-august-7-2014/">CouchDB Weekly News, August 7, 2014</a>.
</p>
**Design**
<p>
Investing some time <a href="http://www.webdesignerdepot.com/2014/08/why-your-brand-needs-a-style-guide-and-how-to-create-one/">in a style guide</a> can save you time, money, and even frustration.
</p>
<p>
On the search for inspiration, <a href="http://www.onextrapixel.com/2014/07/21/design-lessons-from-20-phenomenal-vintage-movie-posters/">vintage movie posters</a> can teach you a thing or two about design and composition.<!--more-->
</p>
<p>
Our great team member Ola Gasidlo on <a href="http://www.creativebloq.com/netmag/ola-gasidlo-benefits-offline-first-design-81412569">the benefits of Offline-First design</a>.
</p>
<p>
Breaking Development: <a href="http://www.lukew.com/ff/entry.asp?1902&utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+FunctioningForm+%28LukeW+Ideation+%2B+Design%29">Offline First is the new Mobile First </a>
</p>
<p>
Pro- and Beginner-Friendly CSSClasses: <a href="http://www.meetup.com/opentechschool-berlin/events/199567452/">next weekend in Berlin</a>!
</p>
**The Web and Development**
<p>
It’s the details that give your projects some personality. <a href="http://www.webdesignerdepot.com/2014/08/5-essential-elements-of-a-successful-404-error-page/">A successful 404 error page</a> might get your visitors talking.
</p>
<p>
<a href="http://www.smashingmagazine.com/2014/07/30/declarative-programming/">Declarative programming for web developers</a>
</p>
<p>
The secret to being a successful developer is <a href="http://csswizardry.com/2014/08/advice-to-budding-front-end-developers/">hard work</a> … as it is with most things.
</p>
<p>
Here is why <a href="http://chase-seibert.github.io/blog/2014/08/01/why-blogging.html">it might be a good idea to maintain a blog</a> as a software developer.
</p>
<p>
Why unpaid corporate hack days <a href="http://ntlk.net/2014/08/07/why-unpaid-corporate-hackdays-are-a-bad-idea/">are a bad idea</a>.
</p>
**The Tech World and Culture**
<p>
There’s a study that suggests that some women and minority leaders are being penalized for <a href="http://www.businessnewsdaily.com/6788-fostering-workplace-diversity.html?">fostering diversity.</a>
</p>
<p>
Why you should always invite <a href="http://geekfeminism.wikia.com/wiki/Tokenism">more then one woman to speak at your conference</a>.
</p>
<p>
35 practical <a href="http://www.xojane.com/issues/feminism-men-practical-steps">steps Men can take to support Feminism</a>.
</p>
**The Business**
<p>
Companies launch things all the time. Here are <a href="http://justcreative.com/2014/07/30/how-to-launch-anything-online/">a couple of things</a> that can help to make the process a success.
</p>
<p>
Some people argue that considering the human error in business just means that people get off the hook more easy. Developer Daniel Schauenberg <a href="http://www.unwiredcouch.com/2014/08/04/human-error-getting-off-the-hook.html">reflects on why reality is more complex than that.</a>
</p>
<p>
If you think about to start a funding campaign on kickstarter, there are <a href="http://littlemight.com/kickstarter-economics-101-the-true-costs-of-a-successful-project/">lots of things</a> to take into account while calculating the final costs of your project.
</p>
**We <3**
<p>
Some feelings can just be described in a <a href="http://visual.ly/11-untranslatable-words-other-cultures">foreign language</a>.
</p>
<p>
<a href="http://quotacle.com/watch.php?id=53d5dd0806">Next time you need to tell someone you’re their father</a>, Quotacle, though still in beta, can help you with an embedded video or gif of your favourite movie quote. You’re welcome.
</p>
<p>
The fruit salad tree – <a href="http://www.treeof40fruit.com/">it does exist!</a>
</p>
<p>
<a href="http://thebitchwhocodes.com/2014/08/05/should-i-reply-all-a-flowchart/">Should you hit “Reply all”?</a>
</p>
<p>
A <a href="https://medium.com/i-love-charts/a-map-of-the-introverts-heart-4db2d8c9cf48">map of the Introvert’s Heart</a>.
</p>
<p style="text-align: center;">
____________
</p>
<p style="text-align: center;">
<em>We wish you a great and sunny weekend!</em>
</p>
| 41.84 | 286 | 0.731358 | eng_Latn | 0.826139 |
c93e3566a3baa36d0f656a7f4ab6903c5057d544 | 208 | md | Markdown | README.md | rbcrwd/go-libarchive | 3fd1cffabca0501d0f0b6e22b3d79383ee9674d5 | [
"MIT"
] | 9 | 2015-09-25T17:52:55.000Z | 2020-12-12T15:24:23.000Z | README.md | rbcrwd/go-libarchive | 3fd1cffabca0501d0f0b6e22b3d79383ee9674d5 | [
"MIT"
] | 7 | 2015-10-22T22:15:32.000Z | 2018-10-08T14:57:56.000Z | README.md | rbcrwd/go-libarchive | 3fd1cffabca0501d0f0b6e22b3d79383ee9674d5 | [
"MIT"
] | 12 | 2015-05-06T09:41:47.000Z | 2022-02-10T09:58:45.000Z | go-libarchive
=============
Golang bindings for the [libarchive](http://libarchive.org) library.
Acknowledgments
===============
based on [robxu9's go-libarchive](https://github.com/robxu9/go-libarchive)
| 18.909091 | 74 | 0.668269 | oci_Latn | 0.264119 |
c93eeddcc30079a1bd62edb88f229ee951bb4271 | 3,502 | md | Markdown | libraries/common/Restler/versions/Restler-master/public/examples/_002_minimal/readme.md | lekster/md_new | 13abe6e5fb2a6129db50e1779653b4fe18100f4e | [
"MIT"
] | null | null | null | libraries/common/Restler/versions/Restler-master/public/examples/_002_minimal/readme.md | lekster/md_new | 13abe6e5fb2a6129db50e1779653b4fe18100f4e | [
"MIT"
] | null | null | null | libraries/common/Restler/versions/Restler-master/public/examples/_002_minimal/readme.md | lekster/md_new | 13abe6e5fb2a6129db50e1779653b4fe18100f4e | [
"MIT"
] | null | null | null | Minimal Example <requires>PHP >= 5.3</requires>
---------------
<tag>basic</tag> <tag>validation</tag> <tag>http status</tag>
Shows the bare minimum code needed to get your RESTful api server
up and running
> This API Server is made using the following php files/folders
>
> * index.php (gateway)
> * Math.php (api)
> * restler.php (framework)
> * JsonFormat.php (format)
This API Server exposes the following URIs
GET math/add ⇠ Math::add()
GET math/multiply/{n1}/{n2} ⇠ Math::multiply()
> **Note:-** Take note of the php doc comments, they make sure the
data is sent in the right type and validated automatically before calling
the api method.
Try the following links in your browser
GET [math/add](index.php/math/add)
:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
GET [math/add?n1=6&n2=4](index.php/math/add?n1=6&n2=4)
:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
10
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
GET [math/multiply/4/3](index.php/math/multiply/4/3)
:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
{"result":12}
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
GET [math/multiply/4/NaN](index.php/math/multiply/4/NaN)
:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
{
"error": {
"code": 400,
"message": "Bad Request: invalid value specified for n2"
}
}
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
We expect the following behaviour from this example.
```gherkin
@example2 @minimal
Feature: Testing Minimal Example
Scenario: Add using Default Values
When I request "/examples/_002_minimal/math/add"
Then the response status code should be 200
And the response is JSON
And the type is "int"
And the value equals 2
Scenario: Add 5 and 10
Given that "n1" is set to "5"
And "n2" is set to "10"
When I request "/examples/_002_minimal/math/add{?n1,n2}"
Then the response status code should be 200
And the response is JSON
And the type is "int"
And the value equals 15
Scenario: Verify Validation
Given that "n1" is set to "NaN"
When I request "/examples/_002_minimal/math/add{?n1,n2}"
Then the response status code should be 400
And the response is JSON
And the response has a "error" property
Scenario: Multiply
Given that "n1" is set to "10"
And "n2" is set to "5"
When I request "/examples/_002_minimal/math/multiply/{n1}/{n2}"
And the response is JSON
And the response has a "result" property
And the "result" property equals 50
Scenario: Multiply without value
When I request "/examples/_002_minimal/math/multiply"
Then the response status code should be 404
And the response is JSON
And the type is "array"
And the response has a "error" property
Scenario: Verify Validation for multiplication
Given that "n1" is set to "NaN"
And "n2" is set to "5"
When I request "/examples/_002_minimal/math/multiply/{n1}/{n2}"
Then the response status code should be 400
And the response is JSON
And the response has a "error" property
```
It can be tested by running the following command on terminal/command line
from the project root (where the vendor folder resides). Make sure `base_url`
in `behat.yml` is updated according to your web server.
```bash
bin/behat features/examples/_002_minimal.feature
```
*[index.php]: _002_minimal/index.php
*[Math.php]: _002_minimal/Math.php
*[restler.php]: ../../vendor/restler.php
*[JsonFormat.php]: ../../vendor/Luracast/Restler/Format/JsonFormat.php
| 26.732824 | 77 | 0.63478 | eng_Latn | 0.958079 |
c93ef195c781d19e60c13a20e097396c7cb7194b | 5,511 | md | Markdown | analise-urbana.md | p3palazzo/tau0006 | d16a39bb27edbc002bd05cbbe0a4743ef0a2f461 | [
"CC-BY-4.0"
] | null | null | null | analise-urbana.md | p3palazzo/tau0006 | d16a39bb27edbc002bd05cbbe0a4743ef0a2f461 | [
"CC-BY-4.0"
] | 24 | 2021-03-23T16:45:28.000Z | 2022-03-11T13:57:52.000Z | analise-urbana.md | p3palazzo/tau0006 | d16a39bb27edbc002bd05cbbe0a4743ef0a2f461 | [
"CC-BY-4.0"
] | 1 | 2022-03-09T01:30:17.000Z | 2022-03-09T01:30:17.000Z | ---
title: "Roteiro para análise urbana"
author: "Ricardo Trevisan (modificado por Pedro Paulo Palazzo)"
layout: page
---
Roteiro para análise urbana
===========================
> Objetivo:
> Criar um inventário por meio do reconhecimento e levantamento
> de dados e das condições existentes no sítio, de modo a ter
> um maior domínio da própria intervenção e de sua inserção
> no ambiente urbano existente.
Ambiente natural
----------------
### Condições de insolação
Orientação do norte magnético e verdadeiro e carta solar
para determinação de insolação nas fachadas;
intensidade e sazonalidade da radiação solar;
atentar para a presença de quebra-sóis, toldos, arcadas,
marquises e outras proteções nas fachadas dos edifícios
existentes.
### Condições atmosféricas
Verificação dos ventos dominantes por estação
(direção e velocidade), conforme cartas;
regime meteorológico (intensidade, sazonalidade) e
partículas atmosféricas;
conforto higrotérmico (diagrama de Givoni),
estratégias bioclimáticas adotadas no espaço público
e nas edificações existentes.
### Geologia
Condição do relevo da superfície de estudo;
aclives ou declives (verificar curvas de nível
presentes no mapa);
tipos de solos, condições de resistência;
barreiras e determinantes impostas pelo terreno.
### Hidrologia
Localização e determinação de cursos d'água, lagos,
represas, açudes, litoral marítimo, etc.,
constituição em barreiras ou recursos paisagísticos;
profundidade do lençol freático;
processos geológicos de erosão e outros.
### Vegetação
Verificar a existência de áreas verdes concentradas,
jardins, arborização junto ao arruamento, etc.;
anotar localização, tipo, porte (se possível, espécie);
acesso a madeira para construção civil.
Contexto histórico-cultural
---------------------------
### Modo de produção
Organização econômica da sociedade, razões para a escolha
do sítio;
condicionantes econômicos: acesso a recursos naturais
(água, terras cultiváveis, materiais de construção, etc.),
possibilidades produtivas;
recursos tecnológicos, inclusive de transporte de pessoas
e mercadorias.
### Organização política e cultural
Sistemas políticos sucessivos, religiões dominantes;
características culturais de privacidade, higiene,
estratificação social, gênero, segurança pública, etc.;
códigos, símbolos e arquétipos culturais;
costumes e tradições de apropriação do espaço.
### Eventos históricos
Revoluções, guerras, migrações, catástrofes naturais
e outros eventos que tenham impactado
a forma e o uso do sítio.
### Legislação
Normas vigentes em relação ao uso do solo e à construção
(código de obras, plano diretor, código de posturas, etc.);
regras atinentes ao convívio social, às expressões políticas,
à atividade econômica.
Traçado urbano
--------------
### Malha viária
Incorporar alterações não presentes em plantas ou mapas
(levantamento como construído);
estimar pendentes na área e no entorno;
determinar processo de formação do traçado urbano:
elementos geradores, intervenções e transformações.
Axialidade: integração e segregação dos eixos,
conectividade da malha.
### Percepção do espaço
Percursos, configurações visuais;
axialidade, conectividade e integração;
barreiras, distritos, caminhos, pontos focais
e marcos visuais;
espaço público, semi-público e privado.
### Arruamento
Geometria: dimensões e formas geométricas dos espaços convexos;
urbanidade e formalidade; perfis transversais dos espaços públicos.
Tipologia: praça, rua, avenida, beco ou travessa, ponte,
viaduto, túnel, passarela, galeria subterrânea, etc.;
estimar hierarquia de vias.
Função: circulação pública de veículos ou pedestres,
compartilhamento de espaços e faixas de tráfego, separação
por velocidades ou capacidade;
significado: praça, largo, esplanada, passeio, parque, jardim, etc.
### Pavimentação urbana
Pavimentadas (leito carroçável e espaços anexos) ou áreas não
pavimentadas (terra nua, anotar localização, estimar dimensões);
tipos de pavimentação, soluções de drenagem adotadas,
processo histórico.
### Mobiliário urbano
Bancos, abrigos, paradas de ônibus, caixas de correspondência,
cabines telefônicas, cabines de serviços, bancas de jornais,
carrinhos ou estandes de lanches, lixeiras, etc.;
zoneamento formal ou informal, características de perenidade.
### Iluminação pública e transmissão
Verificar sistemas (suporte e luminárias), transmissão de energia
e de comunicações (aérea ou subterrânea).
Parcelamento do solo
--------------------
### Macroparcelas (quarteirões)
Dimensões e formas predominantes e excepcionais;
pontos de acesso (constituições);
ocupação do interior das macroparcelas (Nolli);
linhas de coroamento, porosidade e rugosidade.
### Microparcelas (lotes)
Dimensões e formas predominantes e excepcionais;
processo histórico de parcelamento do solo;
ocupação das microparcelas.
### Funções e atividades
Identificação de atividades atuais e históricas;
funções utilitárias e simbólicas.
Edificações
-----------
### Morfologia
Tipos arquitetônicos e seu processo histórico;
arqueologia;
gabaritos, proporções das massas e alinhamentos;
construtividade: sistemas e materiais.
### Zoneamentos
Configuração dos espaços em relação a frente/fundos e
acima/abaixo;
atividades por setor.
### Composição de fachadas
Formas, planos, alinhamentos;
relação entre cheios e vazios (aberturas);
proporções dos elementos arquitetônicos;
ordens, galerias, arcadas, platibandas, beirais
e outros elementos;
linguagens arquitetônicas (estilos) e iconografia.
| 27.974619 | 67 | 0.788605 | por_Latn | 0.999878 |
c93f954f6ac92e37f0d0eefcc71ae32b894b1dfb | 424 | md | Markdown | _pages/News.md | mcib3d/imagej.github.io | 42950a9c4f07c0a0ba223596cefbde72fb22a88e | [
"CC-BY-3.0"
] | null | null | null | _pages/News.md | mcib3d/imagej.github.io | 42950a9c4f07c0a0ba223596cefbde72fb22a88e | [
"CC-BY-3.0"
] | null | null | null | _pages/News.md | mcib3d/imagej.github.io | 42950a9c4f07c0a0ba223596cefbde72fb22a88e | [
"CC-BY-3.0"
] | null | null | null | ---
autogenerated: true
title: News
layout: page
categories:
description: test description
---
This page shows the latest announcements and updates about ImageJ. You can also follow [\#imagej on Twitter](https://twitter.com/hashtag/imagej).
[ImageJ1](ImageJ1) release notes are listed on the [IJ1 news page](https://imagej.net/notes.html).
<listnews limit="20" />
You can also browse the [news archive](Category_News).
| 26.5 | 145 | 0.752358 | eng_Latn | 0.893889 |
c93fb28993bef015baa248595df2c7ebe5fde2d8 | 2,344 | md | Markdown | deployments/docker/sag-um-is-push/README.md | pbommali/templates | 6716864b9ffe17359e290ce2a5f752f89b617814 | [
"Apache-2.0"
] | 33 | 2017-12-01T15:31:18.000Z | 2022-01-12T14:19:39.000Z | deployments/docker/sag-um-is-push/README.md | pbommali/templates | 6716864b9ffe17359e290ce2a5f752f89b617814 | [
"Apache-2.0"
] | 35 | 2018-07-03T18:33:11.000Z | 2020-09-28T10:22:41.000Z | deployments/docker/sag-um-is-push/README.md | pbommali/templates | 6716864b9ffe17359e290ce2a5f752f89b617814 | [
"Apache-2.0"
] | 79 | 2017-10-09T21:31:51.000Z | 2022-03-18T11:09:24.000Z | <!-- Copyright 2013 - 2018 Software AG, Darmstadt, Germany and/or its licensors
SPDX-License-Identifier: Apache-2.0
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
# Small integration stack
Use this template to run containers and deploy configurations using Command Central templates for the following runtimes:
* [Universal Messaging Server](../../universal-messaging/Dockerfile)
* [Integration Server](../../containers/microservices-runtime/Dockerfile)
## Requirements
### Supported Software AG releases
* Universal Messaging 10.1 and higher
* Integration Server 10.3 and higher
* Command Central 10.3
### Supported platforms
* Docker 17.09+
### Supported use cases
* Running Universal Messaging and Integration Server containers
* Configuring the containers using the push deployment model from Command Central
## Launching integration stack using docker-compose
> IMPORTANT: if you run the stacks on a machine different from where you built container images, point to a remote Docker registry that contains the images
For example:
```bash
export REG=daerepository03.eur.ad.sag:4443/sagdevops
export CC_REG=daerepository03.eur.ad.sag:4443/ccdevops
```
### Launching containers with asset depoyment
Launch [Command Central Stack](../sag-cc/) first. It is required for configuration deployment.
Launch Universal Messaging and Integration Server containers and configure them using Command Central templates:
```bash
docker-compose run --rm init
```
Browse to [Command Central Web UI](https://localhost:8091/) and login (Administrator/manage)
Verify Universal Messaging and Integration Server containers are configured using these templates:
* [sag-um-config](../../../templates/sag-um-config/)
* [sag-is-config](../../../templates/sag-is-config/)
| 33.485714 | 155 | 0.74744 | eng_Latn | 0.967465 |
c9402a9159b581aa4aca7fe54ae64e7d8f802188 | 1,380 | md | Markdown | README.md | bootstrapstudio/lightbox-gallery-bootstrap-snippet | d68602d5617c01401f705d654dd891097c3f60be | [
"MIT"
] | 2 | 2020-07-08T08:53:09.000Z | 2021-04-01T23:31:56.000Z | README.md | bootstrapstudio/lightbox-gallery-bootstrap-snippet | d68602d5617c01401f705d654dd891097c3f60be | [
"MIT"
] | null | null | null | README.md | bootstrapstudio/lightbox-gallery-bootstrap-snippet | d68602d5617c01401f705d654dd891097c3f60be | [
"MIT"
] | 1 | 2020-11-14T08:11:33.000Z | 2020-11-14T08:11:33.000Z |
[](https://github.com/topics/bootstrap-freebies/)
**Lightbox gallery snippet** made with Bootstrap 4 and [lightbox.js](https://lokeshdhakar.com/projects/lightbox2/). It has a beautiful minimalistic design with image thumbnails in a grid. Thanks to the lightbox JavaScript plugin, users can click on images to zoom in and look through the photos in greater detail. [Get it in Bootstrap Studio »](https://bootstrapstudio.io)
[](https://bootstrapstudio.io)
## Features
* Beautiful & responsive design
* Perfect browser support
* Easy to customize
* 100% Free to use
<br>
## Use it in Bootstrap Studio
This snippet and many others are available in Bootstrap Studio, the powerful web development tool for building responsive websites. You can drag and drop beautiful components together and create great-looking websites in no time. [Get the app now and supercharge your designs!](https://bootstrapstudio.io)
[](https://bootstrapstudio.io/)
[Website](https://bootstrapstudio.io/) · [YouTube Tutorials](https://www.youtube.com/BootstrapStudioApp) · [GitHub](https://github.com/bootstrapstudio)
## License
This project is licensed under the [MIT license](LICENSE). | 49.285714 | 378 | 0.775362 | eng_Latn | 0.753698 |
c942239bcbf732a1499b2c439517cb4fa0bd6d89 | 899 | md | Markdown | api/Excel.GapDepth.md | ahkon/VBA-Docs | c047d7975de2b0949b496af150d279c505a8595b | [
"CC-BY-4.0",
"MIT"
] | 4 | 2019-09-07T04:44:48.000Z | 2021-12-16T15:05:50.000Z | api/Excel.GapDepth.md | ahkon/VBA-Docs | c047d7975de2b0949b496af150d279c505a8595b | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-06-13T09:32:15.000Z | 2021-06-13T09:32:15.000Z | api/Excel.GapDepth.md | ahkon/VBA-Docs | c047d7975de2b0949b496af150d279c505a8595b | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-11-28T06:51:45.000Z | 2019-11-28T06:51:45.000Z | ---
title: GapDepth property (Excel Graph)
keywords: vbagr10.chm5207398
f1_keywords:
- vbagr10.chm5207398
ms.prod: excel
api_name:
- Excel.GapDepth
ms.assetid: 0aa59fe6-29bf-c014-8c11-18481f9c5603
ms.date: 04/10/2019
localization_priority: Normal
---
# GapDepth property (Excel Graph)
Returns or sets the distance between the data series on a 3D chart, as a percentage of the marker width. The value of this property must be between 0 and 500. Read/write **Long**.
## Syntax
_expression_.**GapDepth**
_expression_ Required. An expression that returns one of the objects in the **Applies To** list.
## Example
This example sets the distance between the data series to 200 percent of the marker width. The example should be run on a 3D chart (the **GapDepth** property fails on 2D charts).
```vb
myChart.GapDepth = 200
```
[!include[Support and feedback](~/includes/feedback-boilerplate.md)] | 27.242424 | 179 | 0.760845 | eng_Latn | 0.971507 |
c9430f2c07a7eacdc380bf83fcf00f2df76f8bd3 | 722 | md | Markdown | 2018/CVE-2018-14695.md | justinforbes/cve | 375c65312f55c34fc1a4858381315fe9431b0f16 | [
"MIT"
] | 2,340 | 2022-02-10T21:04:40.000Z | 2022-03-31T14:42:58.000Z | 2018/CVE-2018-14695.md | justinforbes/cve | 375c65312f55c34fc1a4858381315fe9431b0f16 | [
"MIT"
] | 19 | 2022-02-11T16:06:53.000Z | 2022-03-11T10:44:27.000Z | 2018/CVE-2018-14695.md | justinforbes/cve | 375c65312f55c34fc1a4858381315fe9431b0f16 | [
"MIT"
] | 280 | 2022-02-10T19:58:58.000Z | 2022-03-26T11:13:05.000Z | ### [CVE-2018-14695](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14695)
### Description
Incorrect access control in the /mysql/api/diags.php endpoint in Drobo 5N2 NAS version 4.0.5-13.28.96115 allows unauthenticated attackers to retrieve diagnostic information via the "name" URL parameter.
### POC
#### Reference
- https://blog.securityevaluators.com/call-me-a-doctor-new-vulnerabilities-in-drobo5n2-4f1d885df7fc
#### Github
No PoCs found on GitHub currently.
| 40.111111 | 202 | 0.760388 | kor_Hang | 0.207787 |
c94373de06661c5c206ac51abffb6f08bc631a2d | 476 | md | Markdown | docs/SUPPORT.md | altay13/AirSim | a42fb69e6a692ec154f25abd80c0b49ef45caac4 | [
"MIT"
] | 6,115 | 2019-05-07T05:29:14.000Z | 2022-03-31T12:46:36.000Z | docs/SUPPORT.md | altay13/AirSim | a42fb69e6a692ec154f25abd80c0b49ef45caac4 | [
"MIT"
] | 2,306 | 2019-05-07T00:17:31.000Z | 2022-03-31T23:31:46.000Z | docs/SUPPORT.md | altay13/AirSim | a42fb69e6a692ec154f25abd80c0b49ef45caac4 | [
"MIT"
] | 2,059 | 2019-05-07T03:07:43.000Z | 2022-03-31T06:31:19.000Z | # Support
We highly recommend to take a look at source code and contribute to the project. Due to large number of incoming feature request we may not be able to get to your request in your desired timeframe. So please [contribute](CONTRIBUTING.md) :).
* [Ask in Discussions](https://github.com/microsoft/AirSim/discussions)
* [File GitHub Issue](https://github.com/Microsoft/AirSim/issues)
* [Join AirSim Facebook Group](https://www.facebook.com/groups/1225832467530667/)
| 59.5 | 241 | 0.773109 | eng_Latn | 0.789096 |
c943cb847da1052e2574f275727276747909e37d | 44 | md | Markdown | README.md | jaimerosales/aechacklmv | b58b91d4c34830cd0e99ca9c1d885652e35494e5 | [
"MIT"
] | null | null | null | README.md | jaimerosales/aechacklmv | b58b91d4c34830cd0e99ca9c1d885652e35494e5 | [
"MIT"
] | null | null | null | README.md | jaimerosales/aechacklmv | b58b91d4c34830cd0e99ca9c1d885652e35494e5 | [
"MIT"
] | null | null | null | # aechacklmv
Lmv Workshop for AEC Hackathon
| 14.666667 | 30 | 0.818182 | deu_Latn | 0.385372 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.