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 listlengths 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 listlengths 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 listlengths 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
fdc52e28e9cddf7ef7d3a7a27775b3aaa26f5965 | 2,840 | md | Markdown | lab1/README.md | Come1LLF00/device-drivers-development | c194bafa3eafb3d2e08501dff6aa5e5c89f6137a | [
"MIT"
] | 1 | 2022-02-12T15:32:44.000Z | 2022-02-12T15:32:44.000Z | lab1/README.md | Come1LLF00/device-drivers-development | c194bafa3eafb3d2e08501dff6aa5e5c89f6137a | [
"MIT"
] | null | null | null | lab1/README.md | Come1LLF00/device-drivers-development | c194bafa3eafb3d2e08501dff6aa5e5c89f6137a | [
"MIT"
] | 1 | 2022-03-16T12:43:24.000Z | 2022-03-16T12:43:24.000Z | # Лабораторная работа 1
**Название:** "Разработка драйверов символьных устройств"
**Цель работы:** разработать драйвер символьного устройства
## Описание функциональности драйвера
В файловой системе создаются два файла:
* `/dev/var2`
* `/proc/var2`
Первый имеет функциональность, что при чтении из него выдаются в кольцевой буфер ядра ( `sudo dmesg` ) последовательно `5` последних решений. А при записе в него простых выражений вида `argoparg`, где `arg` -- это целые числа, а `op` -- это символ операции, которую нужно сотворить с этими аргументами, он заполняет этот буфер. Второй имеет право только на чтение, при попытке записи вернется ошибка.
Список поддерживаемых операций:
* `+` -- сложение
* `-` -- вычитание
* `*` -- умножение
* `/` -- деление
## Инструкция по сборке
```
make # собрать исходники
sudo make load # загрузить модуль
sudo make mkdev # создать узел устройства
# далее свободно взаимодействуем с файлами, согласно интерфейсу определенному вариантом
```
### Дополнительно
```
sudo make unload # выгрузить загруженный модуль
sudo make rmdev # удалить созданный узел устройства
```
## Инструкция пользователя
1. Собрать модуль
2. Загрузить модуль
3. Создать узел для устройства
4. Писать в узел простые выражения ( без пробелов и прочих разделителей, все слитно -- операнд операция операнд ).
5. Читать из узла для получение ранее вычисленных выражений, на одно чтение по кругу выводятся последовательно пять последних результатов
6. При чтении из файла `/proc/var2` проверять лог для того, чтобы увидеть результат чтения
7. По завершению работы выгрузить модуль и удалить созданный узел с помощью соответствующих целей в `Makefile`
## Примеры использования
### Пример работы с `/dev/var2`
```
echo "-3+8" > /dev/var2
cat /dev/var2
sudo dmesg
-------------
[ 2675.645038] chr_comp: file /dev/var2 opened
[ 2675.645067] chr_comp: dev_var2_write: count = 3, a = -3, b = 8, c = +, length = 5
[ 2675.645075] chr_comp: file /dev/var2 closed
[ 2680.093943] chr_comp: file /dev/var2 opened
[ 2680.093963] chr_comp: dev_var2_read: 5
[ 2680.126896] chr_comp: file /dev/var2 closed
```
```
echo "1/0" > /dev/var2
cat /dev/var2
sudo dmesg
-------------
[ 2531.322739] chr_comp: file /dev/var2 opened
[ 2531.322768] chr_comp: dev_var2_write: count = 3, a = 1, b = 0, c = /, length = 4
[ 2531.332597] chr_comp: file /dev/var2 closed
[ 2638.040875] chr_comp: file /dev/var2 opened
[ 2638.040887] chr_comp: dev_var2_read: 0
[ 2638.089075] chr_comp: file /dev/var2 closed
```
### Пример работы с `/proc/var2`
```
cat /proc/var2
sudo dmesg -c
----------
[ 590.119804] chr_comp: file /proc/var2 opened
[ 590.119817] chr_comp: proc_var2_read: 5
[ 590.181147] chr_comp: file /proc/var2 closed
```
## Дополнительное задание
Через параметр задавать число создаваемых устройств.
История вычислений, /proc/var2 и dmesg общий.
| 33.023256 | 400 | 0.732394 | rus_Cyrl | 0.854221 |
fdc6633a88cc9b5991e9372c5a06ba045c4b8417 | 34 | md | Markdown | eventssubscription/Readme.md | ciromacedo/nwdaf | 5bba0bbed2d80b315301336302ef9b19644781fc | [
"Apache-2.0"
] | null | null | null | eventssubscription/Readme.md | ciromacedo/nwdaf | 5bba0bbed2d80b315301336302ef9b19644781fc | [
"Apache-2.0"
] | null | null | null | eventssubscription/Readme.md | ciromacedo/nwdaf | 5bba0bbed2d80b315301336302ef9b19644781fc | [
"Apache-2.0"
] | null | null | null | # Service specific package
To Do! | 11.333333 | 26 | 0.764706 | eng_Latn | 0.973081 |
fdc7433dd337122689d7c799f7e55001951d620a | 3,082 | md | Markdown | articles/media-services/media-services-dotnet-encoding-units.md | OpenLocalizationTestOrg/azure-docs-pr15_da-DK | d54890118a6e972d17db61fb83d96d3e56ca9f44 | [
"CC-BY-3.0",
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/media-services/media-services-dotnet-encoding-units.md | OpenLocalizationTestOrg/azure-docs-pr15_da-DK | d54890118a6e972d17db61fb83d96d3e56ca9f44 | [
"CC-BY-3.0",
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/media-services/media-services-dotnet-encoding-units.md | OpenLocalizationTestOrg/azure-docs-pr15_da-DK | d54890118a6e972d17db61fb83d96d3e56ca9f44 | [
"CC-BY-3.0",
"CC-BY-4.0",
"MIT"
] | null | null | null | <properties
pageTitle="Sådan føjer du kodning enheder"
description="Lær, hvordan du hvordan du tilføjer kodning enheder med .NET"
services="media-services"
documentationCenter=""
authors="juliako"
manager="erikre"
editor=""/>
<tags
ms.service="media-services"
ms.workload="media"
ms.tgt_pltfrm="na"
ms.devlang="na"
ms.topic="article"
ms.date="09/01/2016"
ms.author="juliako;milangada;gtrifonov"/>
#<a name="how-to-scale-encoding-with-net-sdk"></a>Sådan skalere kodning med .NET SDK
> [AZURE.SELECTOR]
- [Portal](media-services-portal-scale-media-processing.md )
- [.NET](media-services-dotnet-encoding-units.md)
- [RESTEN](https://msdn.microsoft.com/library/azure/dn859236.aspx)
- [Java](https://github.com/southworkscom/azure-sdk-for-media-services-java-samples)
- [PHP](https://github.com/Azure/azure-sdk-for-php/tree/master/examples/MediaServices)
##<a name="overview"></a>Oversigt
>[AZURE.IMPORTANT] Sørg for at gennemse emnet [Oversigt](media-services-scale-media-processing-overview.md) for at få flere oplysninger om skalering medier behandling emne.
For at ændre en reserveret enhedstype og antallet af kodning reserveret enheder ved hjælp af .NET SDK, skal du gøre følgende:
IEncodingReservedUnit encodingS1ReservedUnit = _context.EncodingReservedUnits.FirstOrDefault();
encodingS1ReservedUnit.ReservedUnitType = ReservedUnitType.Basic; // Corresponds to S1
encodingS1ReservedUnit.Update();
Console.WriteLine("Reserved Unit Type: {0}", encodingS1ReservedUnit.ReservedUnitType);
encodingS1ReservedUnit.CurrentReservedUnits = 2;
encodingS1ReservedUnit.Update();
Console.WriteLine("Number of reserved units: {0}", encodingS1ReservedUnit.CurrentReservedUnits);
##<a name="opening-a-support-ticket"></a>Åbne en Supportbilletter
Hver Media Services-konto kan som standard skaleres til op til 25 kodning og 5 efter behov Streaming reserveret enheder. Du kan anmode om en højere grænse ved at åbne en supportbilletter.
###<a name="open-a-support-ticket"></a>Åbne en supportbilletter
Brugertilladelse Benyt følgende fremgangsmåde for at åbne en support:
1. Klik på [få Support](https://manage.windowsazure.com/?getsupport=true). Hvis du ikke er logget, bliver du bedt om at angive dine legitimationsoplysninger.
1. Vælg dit abonnement.
1. Vælg "Tekniske" under type af support.
1. Klik på "Oprette brugertilladelse".
1. Vælg "Azure Media Services" på produktlisten præsenteres på den næste side.
1. Vælg en "problemtype", der er relevante for dit problem.
1. Klik på Fortsæt.
1. Følg instruktionerne på næste side og derefter angive oplysninger om dit problem.
1. Klik på Send for at åbne brugertilladelse.
##<a name="media-services-learning-paths"></a>Media Services læringsstier
[AZURE.INCLUDE [media-services-learning-paths-include](../../includes/media-services-learning-paths-include.md)]
##<a name="provide-feedback"></a>Give feedback
[AZURE.INCLUDE [media-services-user-voice-include](../../includes/media-services-user-voice-include.md)]
| 38.525 | 187 | 0.753082 | dan_Latn | 0.921842 |
fdca41afd082a4624711d240b8491d09141ca747 | 31 | md | Markdown | Lesson01/master/content/_index.md | TrainingByPackt/Introduction-to-DevOps-with-Kubernetes | cfdc9e93c918bf7bc89415237d8cc066ead16509 | [
"MIT"
] | 4 | 2021-06-21T11:52:10.000Z | 2022-03-15T08:14:49.000Z | Lesson01/master/content/_index.md | TrainingByPackt/Introduction-to-DevOps-with-Kubernetes | cfdc9e93c918bf7bc89415237d8cc066ead16509 | [
"MIT"
] | null | null | null | Lesson01/master/content/_index.md | TrainingByPackt/Introduction-to-DevOps-with-Kubernetes | cfdc9e93c918bf7bc89415237d8cc066ead16509 | [
"MIT"
] | 20 | 2019-05-15T11:52:19.000Z | 2022-03-28T08:00:39.000Z | ### Start DevOps journey now!
| 10.333333 | 29 | 0.677419 | eng_Latn | 0.656967 |
fdcad720a3391595d22ad6872ddf52d110d4d97a | 7,033 | md | Markdown | docs/outlook/mapi/supporting-event-notification.md | ManuSquall/office-developer-client-docs.fr-FR | 5c3e7961c204833485b8fe857dc7744c12658ec5 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-08-15T11:25:43.000Z | 2021-08-15T11:25:43.000Z | docs/outlook/mapi/supporting-event-notification.md | ManuSquall/office-developer-client-docs.fr-FR | 5c3e7961c204833485b8fe857dc7744c12658ec5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/outlook/mapi/supporting-event-notification.md | ManuSquall/office-developer-client-docs.fr-FR | 5c3e7961c204833485b8fe857dc7744c12658ec5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Prise en charge des notifications d’événement
manager: soliver
ms.date: 11/16/2014
ms.audience: Developer
localization_priority: Normal
api_type:
- COM
ms.assetid: a1e3e49c-8d1d-4f7e-ba5a-be441f0f10ae
description: 'Derniére modification : samedi 23 juillet 2011'
ms.openlocfilehash: 83c102c25b17b6769c0c676bbadd874224f75cf6
ms.sourcegitcommit: 8fe462c32b91c87911942c188f3445e85a54137c
ms.translationtype: MT
ms.contentlocale: fr-FR
ms.lasthandoff: 04/23/2019
ms.locfileid: "32327425"
---
# <a name="supporting-event-notification"></a>Prise en charge des notifications d’événement
**S’applique à** : Outlook 2013 | Outlook 2016
Étant donné que la prise en charge de la notification d’événement peut être compliquée, MAPI fournit trois méthodes d’objet de prise en charge qui implémentent les parties les plus difficiles du processus. Ces méthodes fonctionnent en tant qu’unité et un fournisseur doit utiliser les trois méthodes ou aucune d’entre elles.
Les méthodes de prise en charge MAPI utilisent des clés de notification pour gérer les connexions entre les réceptions de notification et les objets qui génèrent les notifications. Une clé de notification est une structure [NOTIFKEY](notifkey.md) qui contient des données binaires qui identifient un objet parmi les processus. Une clé de notification est généralement copiée à partir de l’identificateur d’entrée à long terme de l’objet source de notification. Si le client a fourni un identificateur d’entrée dans l’appel au service **Conseil,** vous pouvez l’utiliser pour la clé de notification. Si le _paramètre lpEntryID_ à **Advise** est NULL, utilisez l’identificateur d’entrée de l’objet conteneur le plus à l’extérieur possible, tel que la magasin de messages.
Pour utiliser les méthodes de support, appelez [IMAPISupport::Subscribe](imapisupport-subscribe.md) chaque fois qu’un client appelle votre méthode **Advise** pour s’inscrire à une notification. Allouez une structure [NOTIFKEY](notifkey.md) et créez une clé de notification unique pour votre objet source de conseil. Par exemple, un fournisseur de magasins de messages qui est invité à avertir un client lorsqu’un message est reçu dans un dossier particulier crée une clé de notification pour ce dossier. Passez un pointeur vers la structure **NOTIFKEY** dans l’appel à **s’abonner,** ainsi qu’un pointeur vers le sink de conseil du client. **Subscribe** calls the advise sink’s [IUnknown::AddRef](https://msdn.microsoft.com/library/b4316efd-73d4-4995-b898-8025a316ba63%28Office.15%29.aspx) method to increment its reference count and MAPI retains the pointer until the registration is canceled.
Vous pouvez transmettre l’indicateur NOTIFY_SYNC s’abonner pour demander que **Notify** se comporte de manière synchrone et ne retourne pas tant qu’il n’a pas effectué tous les appels aux méthodes [IMAPIAdviseSink::OnNotify](imapiadvisesink-onnotify.md) des sinks de notification inscrits. Définissez cet indicateur uniquement pour votre propre utilisation interne. Ne la définissez pas lorsque vous répondez à un **appel** de conseil client. La notification d’événement entre les clients et les fournisseurs est toujours asynchrone. Autrement dit, MAPI garantit que l’appel au cours duquel un événement se produit sera de retour au client avant que les appels **OnNotify** ne soient effectués.
Si vous définissez l’indicateur NOTIFY_SYNC, n’abonnez aucune modification à l’un des objets de sink de conseil et ne passez pas un wrapper advise sink créé par [HrThisThreadAdviseSink](hrthisthreadadvisesink.md) pour s’abonner. **HrThisThreadAdviseSink** crée une version thread-safe d’un réception de conseil à utiliser uniquement avec une notification asynchrone.
Si un réception de notification inscrit pour une notification synchrone renvoie à partir de **OnNotify** avec l’indicateur CALLBACK_DISCONTINUE définie, [IMAPISupport::Notify](imapisupport-notify.md) définit l’indicateur NOTIFY_CANCELED et renvoie sans effectuer d’appels à **OnNotify**.
Une **fois l’abonnement** renvoyé, vous n’aurez plus besoin de conserver votre copie du reçu de conseil du client. Appelez sa [méthode IUnknown::Release](https://msdn.microsoft.com/library/4b494c6f-f0ee-4c35-ae45-ed956f40dc7a%28Office.15%29.aspx) pour la libérer. **L’abonnement** renvoie un numéro de connexion autre que zéro que vous devez renvoyer au client. Le numéro de connexion représente le lien entre la source de conseil et le sink de conseil. Il reste valide jusqu’à ce que le client effectue un appel réussi à **Unadvise**.
Lorsque le client est prêt à annuler une inscription, il appelle votre **méthode Unadvise.** Passez le numéro de connexion de **l’appel Unadvise** à [IMAPISupport::Unsubscribe](imapisupport-unsubscribe.md). **Unsubscribe** calls the advise sink’s **IUnknown::Release** method. Comme avec **Advise** et **Unadvise,** les appels à **Subscribe** et **Unsubscribe** doivent être associés. Vous devez effectuer un appel à **Unsubscribe** pour chaque appel effectué pour **s’abonner.** Toutefois, vous n’avez pas besoin d’appeler **Subscribe** chaque fois que votre **méthode Advise** est appelée. À l’inverse, vous pouvez l’appeler pour la configuration des notifications internes.
Lorsqu’un événement se produit, allouez une ou plusieurs structures [de NOTIFICATION](notification.md) du type approprié pour l’événement et appelez [IMAPISupport::Notify](imapisupport-notify.md). **Notify** génère une notification pour chaque réception de notification inscrit. Vous devez définir tous les membres inutilisés de la structure [NOTIFICATION](notification.md) sur zéro. Cette technique d’initialisation de la structure **NOTIFICATION** peut aider les clients à créer des implémentations **OnNotify** plus petites, plus rapides et moins sujettes aux erreurs.
Notez qu’une structure **de NOTIFICATION** distincte est nécessaire pour chaque événement, même pour plusieurs événements du même type. Par exemple, si trois clients sont inscrits pour la notification de table sur une table particulière et que cinq lignes sont ajoutées à la table, vous devez créer cinq structures **OBJECT_NOTIFICATION** pour votre appel **Notify.** Une notification par lot comme celle-ci se traduit par de meilleures performances que l’appel **de Notification** cinq fois. Pour chaque **appel Notify,** MAPI appelle la méthode [IMAPIAdviseSink::OnNotify](imapiadvisesink-onnotify.md) de chaque reçu de notification inscrit. S’il n’existe aucun reçu de conseil inscrit, MAPI ignore l’appel.
Les fournisseurs de services qui envoient des notifications par lots doivent les commander afin qu’ils soient interprétés de la première notification à la dernière. Ce traitement est particulièrement nécessaire lorsqu’un lot de notifications contient une série d’événements, tels que TABLE_ROW_ADDED avec un événement qui fait référence à une ligne précédente ajoutée dans un autre événement du même lot.
## <a name="see-also"></a>Voir aussi
[Fournisseurs de services MAPI](mapi-service-providers.md)
| 135.25 | 895 | 0.799374 | fra_Latn | 0.986124 |
fdcb966ec89129e08c9d81ab6bf11d721f56c789 | 6,542 | md | Markdown | doc/API_REVIEW_rhs16_gkw.md | teddyf/voogasalad_TODOTeamName | 63ea02d227de1ffdf21c9d527ef48d522586d8df | [
"MIT"
] | null | null | null | doc/API_REVIEW_rhs16_gkw.md | teddyf/voogasalad_TODOTeamName | 63ea02d227de1ffdf21c9d527ef48d522586d8df | [
"MIT"
] | null | null | null | doc/API_REVIEW_rhs16_gkw.md | teddyf/voogasalad_TODOTeamName | 63ea02d227de1ffdf21c9d527ef48d522586d8df | [
"MIT"
] | null | null | null | API Review
Robert Steilberg | rhs16
Grayson Wise | gkw
#Part 1
1. I intend for the game controller.engine and the game controller.editor to be specifically flexible. The game controller.engine in particular should be flexible since it must be able to open a gamefile of any kind and then subsequently run it. As long as the gamefile corresponds to a format accepted by the controller.engine (i.e. a gamefile created with the controller.editor), the gamefile should be accepted. The controller.editor is also intended to be flexible because it will allow for the creation of multiple kinds of RPG games. For example, it will be possible to create games based off of Pokemon, Evoland, Dragon Warrior, et cetera with the single game controller.engine. The GameSaver and GameOpener classes will also be flexible since they should be able to save and open a game of any time, either for editing or playing.
2. Our API design encapsulates much of the basic gameplay that defines how each game functions. For example, NPC settings, model.interactions, battles, and winning conditions are all encapsulated. GameSaver and GameOpener are each encapsulating the design details associated with XML serialization; they will be used throughout game building and playing to open or save gamefiles. The Grid class will encapsulate most of the functionality associated with building RPG stages, since all of our RPG games will be model.grid-based. Thus, we can encapsulate functionality like adding or removing ui.scenes.controller.editor.objects to or from the overworld within this class.
3. My role is generally front end, and links to the back end when the created game is saved or opened. For example, after a overworld is created, it will be serialized and saved so that the back end can then interpret and run it. Additionally, gameplay model.interactions (i.e. battles, NPC settings, et cetera) will be handled through the back end, which is where my role ties into the back end. I must ensure that gameplay settings and serialization are each implemented in a way that allows the back end to tie into this functionality. The game controller.engine will be especially challenging since the back end will need to run the project, yet changes must be pushed to the front end so that the user can perceive and react to them.
4. There are lots of error cases that must be handled in the front end that are associated with building games. For example, if the user attempts to place blocks on the model.grid that conflict with other blocks, the front end must recognize this, reject the changes, and then prompt the user as to why overlaid blocks are not allowed. Furthermore, there are more sophisticated error cases associated with detecting gameplay. For example, if a user creates a game without a winning case, it may be a good idea to recognize this and then prompt the user to add a winning case so that the game is playable. Another error case that will need to be handled is if the user tries to play a gamefile that is not a valid gamefile type or that is corrupted. More sophisticated error detection may need to be handled by the back end but the front end game controller.engine file opener may be able to handle some initial trivial cases.
5. I believe our API is well designed in terms of how we separate the controller.editor and controller.engine. We intend for the controller.editor and controller.engine to be completely separate. For example, the controller.editor should be able to create games and open them for further editing at will, and the controller.engine need only be able to open any valid gamefile and run it. However, it may be useful to allow an instance of the controller.engine to run within the controller.editor for testing, which will not be difficult to implement since the controller.engine is completely separate from the controller.editor. Furthermore, I think that encapsulating gamefile saving and opening is "good" design in the sense that it is encapsulated and separate. Lastly, I think that encapsulating the functionality associated with the gameplay components (i.e. defining battles, defining NPCs, defining model.interactions) is good design because it will be easy to add more functionality implementations since each implementation is encapsulated. These examples are all "good" design in the sense that they are separate and easily extensible
#Part 2
1. I am most excited to work on the controller.editor component of our game authoring controller.engine because I want to craft a design that is intuitive and easy to follow. My goal is to build an controller.editor that is simple and easy to use for any user, yet allows the user to build powerful games.
2. I am most worried about working on the controller.engine component of our game authoring controller.engine. I am worried that it will be difficult to build an controller.engine that can read and execute any gamefile created with the controller.editor, and I am also still unsure about how the controller.engine will tie into the front end. Specifically, I don't yet understand how the back end will read in serialized XML files and then somehow convert those files into something that the front end can interpret and run as a fully functional game. I am also significantly worried about serializing the model.interactions that the user defines in the controller.editor.
3. I have just finished implementing the main menu; this weekend, I hope to implement the functionality for the game controller.editor. Ideally, by the end of the weekend, our VOOGA will have a completely functional game controller.editor that can successfully save games that the user creates.
4. I think our use cases are appropriate for what our game controller.editor and controller.engine need to do. There is a significant number of editing details that our controller.editor will have to account for, and I feel that we have described a wide spread of these potential functional components through our use cases. The majority of our use cases (> 30 of them) are related to the controller.editor. We may need more use cases specifically related to catching errors or the game controller.engine.
5. We have use cases that cover functionality during which errors may be thrown, but we need more use cases that specifically deal with cases in which an error will always be thrown. For example, some good additional use cases would be handiling opening a corrupted gamefile, opening a non-gamefile file, creating a game without a winnable state, et cetera. | 233.642857 | 1,144 | 0.808774 | eng_Latn | 0.999895 |
fdcc458c480dbcc3b55671ae10d31960cac979de | 134 | md | Markdown | docs/release.md | xiashuqin89/bk-chatbot | d3f95363032f699cbc7e6617060642e0763443a6 | [
"MIT"
] | null | null | null | docs/release.md | xiashuqin89/bk-chatbot | d3f95363032f699cbc7e6617060642e0763443a6 | [
"MIT"
] | null | null | null | docs/release.md | xiashuqin89/bk-chatbot | d3f95363032f699cbc7e6617060642e0763443a6 | [
"MIT"
] | null | null | null | # 版本日志
## 1.2.0
- 新功能
- 对接ITSM提单功能
- 支持企业微信JOB平台执行方案拉取、选择执行
- 支持企业微信标准运维模版拉取、选择执行
- 支持企业微信蓝盾流水线拉取、选择执行
- 支持新办企业微信卡片消息
| 10.307692 | 26 | 0.656716 | yue_Hant | 0.934858 |
fdcc9f227b769d090410a14fcb18d5649a3d1657 | 7,503 | md | Markdown | docs/vs-2015/debugger/debug-interface-access/idiapropertystorage.md | tommorris/visualstudio-docs.cs-cz | 92c436dbc75020bc5121cc2c9e4976f62c9b13ca | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vs-2015/debugger/debug-interface-access/idiapropertystorage.md | tommorris/visualstudio-docs.cs-cz | 92c436dbc75020bc5121cc2c9e4976f62c9b13ca | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vs-2015/debugger/debug-interface-access/idiapropertystorage.md | tommorris/visualstudio-docs.cs-cz | 92c436dbc75020bc5121cc2c9e4976f62c9b13ca | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Idiapropertystorage – | Dokumentace Microsoftu
ms.custom: ''
ms.date: 2018-06-30
ms.prod: visual-studio-dev14
ms.reviewer: ''
ms.suite: ''
ms.technology:
- vs-ide-debug
ms.tgt_pltfrm: ''
ms.topic: article
dev_langs:
- C++
helpviewer_keywords:
- IDiaPropertyStorage interface
ms.assetid: d3197a38-5973-4e56-873e-4f1b84c3f674
caps.latest.revision: 13
author: mikejo5000
ms.author: mikejo
manager: ghogen
ms.openlocfilehash: 009e90e5496031e4810e318e1ceecf506dd5c7c2
ms.sourcegitcommit: 55f7ce2d5d2e458e35c45787f1935b237ee5c9f8
ms.translationtype: MT
ms.contentlocale: cs-CZ
ms.lasthandoff: 08/22/2018
ms.locfileid: "42670630"
---
# <a name="idiapropertystorage"></a>IDiaPropertyStorage
[!INCLUDE[vs2017banner](../../includes/vs2017banner.md)]
Nejnovější verzi tohoto tématu můžete najít v [idiapropertystorage –](https://docs.microsoft.com/visualstudio/debugger/debug-interface-access/idiapropertystorage).
Umožňuje číst trvalou vlastnosti sady DIA vlastností.
## <a name="syntax"></a>Syntaxe
```
IDiaPropertyStorage : IUnknown
```
## <a name="methods-in-vtable-order"></a>Metody v tabulce Vtable pořadí
V následující tabulce jsou uvedeny metody objektu `IDiaPropertyStorage`.
|Metoda|Popis|
|------------|-----------------|
|[IDiaPropertyStorage::Enum](../../debugger/debug-interface-access/idiapropertystorage-enum.md)|Získá ukazatel na enumerátor pro vlastnosti v rámci této sady.|
|[IDiaPropertyStorage::ReadBOOL](../../debugger/debug-interface-access/idiapropertystorage-readbool.md)|Přečte `BOOL` hodnoty v sadu vlastností.|
|[IDiaPropertyStorage::ReadBSTR](../../debugger/debug-interface-access/idiapropertystorage-readbstr.md)|Přečte `BSTR` hodnoty v sadu vlastností.|
|[IDiaPropertyStorage::ReadDWORD](../../debugger/debug-interface-access/idiapropertystorage-readdword.md)|Přečte `DWORD` hodnoty v sadu vlastností.|
|[IDiaPropertyStorage::ReadLONG](../../debugger/debug-interface-access/idiapropertystorage-readlong.md)|Přečte `LONG` hodnoty v sadu vlastností.|
|[IDiaPropertyStorage::ReadMultiple](../../debugger/debug-interface-access/idiapropertystorage-readmultiple.md)|Načte hodnoty vlastností v sadu vlastností.|
|[IDiaPropertyStorage::ReadPropertyNames](../../debugger/debug-interface-access/idiapropertystorage-readpropertynames.md)|Získá odpovídající názvů řetězce pro daný vlastnost identifikátory.|
|[IDiaPropertyStorage::ReadULONGLONG](../../debugger/debug-interface-access/idiapropertystorage-readulonglong.md)|Přečte `ULONGLONG` hodnoty v sadu vlastností.|
## <a name="remarks"></a>Poznámky
Každou vlastnost v rámci sady vlastností je identifikován identifikátor vlastnosti (ID), čtyř bajtů `ULONG` hodnoty, které jsou jedinečné pro tuto sadu. Vlastnosti zveřejněné přes `IDiaPropertyStorage` rozhraní odpovídají dostupné vlastnosti v nadřazené rozhraní. Například vlastnosti [idiasymbol –](../../debugger/debug-interface-access/idiasymbol.md) rozhraní je přístupný podle názvu prostřednictvím `IDiaPropertyStorage` rozhraní (Upozorňujeme, že i v případě, že vlastnost může být přístupné, neznamená to je platný pro vlastnost konkrétní `IDiaSymbol` objekt).
## <a name="notes-for-callers"></a>Poznámky pro volající
Získat voláním toto rozhraní `QueryInterface` metodu na jiné rozhraní. Následující rozhraní může být dotázán na `IDiaPropertyStorage` rozhraní:
- [IDiaSectionContrib](../../debugger/debug-interface-access/idiasectioncontrib.md)
- [IDiaSegment](../../debugger/debug-interface-access/idiasegment.md)
- [IDiaInjectedSource](../../debugger/debug-interface-access/idiainjectedsource.md)
- [IDiaFrameData](../../debugger/debug-interface-access/idiaframedata.md)
- [IDiaSymbol](../../debugger/debug-interface-access/idiasymbol.md)
- [IDiaSourceFile](../../debugger/debug-interface-access/idiasourcefile.md)
- [IDiaLineNumber](../../debugger/debug-interface-access/idialinenumber.md)
## <a name="example"></a>Příklad
Tento příklad ukazuje funkci, která se zobrazí všechny vlastnosti, které jsou vystavené `IDiaPropertyStorage` objektu. Zobrazit [idiaenuminjectedsources –](../../debugger/debug-interface-access/idiaenuminjectedsources.md) rozhraní pro příklad, jak `IDiaPropertyStorage` rozhraní se získávají z [idiainjectedsource –](../../debugger/debug-interface-access/idiainjectedsource.md) rozhraní.
```cpp#
void PrintPropertyStorage(IDiaPropertyStorage* pPropertyStorage)
{
IEnumSTATPROPSTG* pEnumProps;
STATPROPSTG prop;
DWORD celt = 1;
if (pPropertyStorage->Enum(&pEnumProps) == S_OK)
{
while (pEnumProps->Next(celt, &prop, &celt) == S_OK)
{
PROPSPEC pspec = { PRSPEC_PROPID, prop.propid };
PROPVARIANT vt = { VT_EMPTY };
if (pPropertyStorage->ReadMultiple( 1, &pspec, &vt) == S_OK)
{
switch( vt.vt ){
case VT_BOOL:
wprintf( L"%32s:\t %s\n", prop.lpwstrName, vt.bVal ? L"true" : L"false" );
break;
case VT_I2:
wprintf( L"%32s:\t %d\n", prop.lpwstrName, vt.iVal );
break;
case VT_UI2:
wprintf( L"%32s:\t %d\n", prop.lpwstrName, vt.uiVal );
break;
case VT_I4:
wprintf( L"%32s:\t %d\n", prop.lpwstrName, vt.intVal );
break;
case VT_UI4:
wprintf( L"%32s:\t 0x%0x\n", prop.lpwstrName, vt.uintVal );
break;
case VT_UI8:
wprintf( L"%32s:\t 0x%x\n", prop.lpwstrName, vt.uhVal.QuadPart );
break;
case VT_BSTR:
wprintf( L"%32s:\t %s\n", prop.lpwstrName, vt.bstrVal );
break;
case VT_UNKNOWN:
wprintf( L"%32s:\t %p\n", prop.lpwstrName, vt.punkVal );
break;
case VT_SAFEARRAY:
break;
default:
break;
}
VariantClear((VARIANTARG*) &vt);
}
}
pEnumProps->Release();
}
}
```
## <a name="requirements"></a>Požadavky
Záhlaví: Dia2.h
Knihovna: diaguids.lib
Knihovny DLL: msdia80.dll
## <a name="see-also"></a>Viz také
[Rozhraní (Debug Interface Access SDK)](../../debugger/debug-interface-access/interfaces-debug-interface-access-sdk.md)
[Idiasession::getenumtables –](../../debugger/debug-interface-access/idiasession-getenumtables.md)
[Idiasectioncontrib –](../../debugger/debug-interface-access/idiasectioncontrib.md)
[Idiasegment –](../../debugger/debug-interface-access/idiasegment.md)
[Idiainjectedsource –](../../debugger/debug-interface-access/idiainjectedsource.md)
[Idiaframedata –](../../debugger/debug-interface-access/idiaframedata.md)
[Idiasymbol –](../../debugger/debug-interface-access/idiasymbol.md)
[Idiasourcefile –](../../debugger/debug-interface-access/idiasourcefile.md)
[Idialinenumber –](../../debugger/debug-interface-access/idialinenumber.md)
[IDiaEnumInjectedSources](../../debugger/debug-interface-access/idiaenuminjectedsources.md)
| 49.039216 | 569 | 0.654538 | ces_Latn | 0.668195 |
fdccb86e5ebd402cbc499f3cbeed652131a0269d | 1,383 | md | Markdown | README.md | joon0615/docs | 2d4bdd5fbd6f581e512ec8bb14746566bbef2ea5 | [
"CC-BY-4.0"
] | null | null | null | README.md | joon0615/docs | 2d4bdd5fbd6f581e512ec8bb14746566bbef2ea5 | [
"CC-BY-4.0"
] | null | null | null | README.md | joon0615/docs | 2d4bdd5fbd6f581e512ec8bb14746566bbef2ea5 | [
"CC-BY-4.0"
] | null | null | null | # SpaceONE Document
## How to use this repository
### Prerequisities
You need following installed locally
- npm
- Go
- Hugo(Extended version)
- Docker & Docker Compose
Before we start, install the dependencies, Clone the repository and navigate to the directory.
```bash
git clone --recurse-submodules --depth 1 https://github.com/spaceone-dev/docs
cd docs
```
SpaceONE blog uses Docsy Hugo theme. So, we strongly recommend pulling in the submodule and other developmment dependencies by running the following.
```bash
# pull in the Docsy submodule
git submodule update --init --recursive --depth 1
```
### Install PostCSS
To build SpaceONE blog, you also need `PostCSS` to create the final asset. If you need install it, you must have recent version of NodeJS installed on your machine so you can use npm.
```bash
npm install --no-optional -D --save
```
## Running Blog locally
Once you've made your own working copy of this repo, from the root folder, run:
```bash
hugo server -D
```
## Running Docker container locally
You can run SpaceONE blog by inside a Docker container.
```bash
docker-compose up --build
```
Open you web browser type `http://localhost:1313` in your navigation bar.
To stop Docker Compose, on your terminal window, press Ctrl + C.
To remove the produced images run:
```bash
docker-compose rm
```
| 16.270588 | 185 | 0.720174 | eng_Latn | 0.986117 |
fdcd2f25f37c7b4c27b5534b4becdad4423bbe52 | 406 | md | Markdown | objectives/control.md | jimhester/tidynomicon | ae87696c486ea811a2ab746dab92b7386df01497 | [
"CC-BY-4.0"
] | null | null | null | objectives/control.md | jimhester/tidynomicon | ae87696c486ea811a2ab746dab92b7386df01497 | [
"CC-BY-4.0"
] | null | null | null | objectives/control.md | jimhester/tidynomicon | ae87696c486ea811a2ab746dab92b7386df01497 | [
"CC-BY-4.0"
] | null | null | null | - Create `for` loops and `if`/`else` statements in R.
- Explain why vectors cannot be used directly in conditional expressions and correctly use `all` and `any` to combine their values.
- Define functions taking a fixed number of named arguments and/or a variable number of arguments.
- Explain what vectorization is and create vectorized equivalents of unnested loops containing simple conditional tests.
| 81.2 | 131 | 0.79803 | eng_Latn | 0.999499 |
fdce331ac25f678fad54784a3aaf55a50df9fb02 | 6,325 | md | Markdown | _posts/2019-12-07-android-library-github-package.md | fahimfarhan/blog | 5e9ea14bd5b73220693409ee352c83485c7d15ea | [
"MIT"
] | null | null | null | _posts/2019-12-07-android-library-github-package.md | fahimfarhan/blog | 5e9ea14bd5b73220693409ee352c83485c7d15ea | [
"MIT"
] | 1 | 2021-03-30T00:39:39.000Z | 2021-03-30T00:39:39.000Z | _posts/2019-12-07-android-library-github-package.md | fahimfarhan/blog | 5e9ea14bd5b73220693409ee352c83485c7d15ea | [
"MIT"
] | null | null | null | ---
layout: post
title: "Android Library Github Package"
description: How to Publish an Android Library as a Github Package
date: 2019-12-07 21:03:36 +0600
categories:
---
Hello there! In this post, we'll see how to publish an android library using github package.
## Create a Library
To begin with, first we need a demo project, let's call it MyAwesomeLibrary . For demonstration purposes, I am going to add a sample dependency named [alphamu/PinEntryEditText](https://github.com/alphamu/PinEntryEditText) to my library. Just add this line in the build.gradle file:
```
dependencies {
implementation ('com.alimuzaffar.lib:pinentryedittext:2.0.6')
// ... ... your other dependencies
}
```
Basically dependency is a beautiful looking pin edit text. You may try creating a sample xml file in the main activity or any other convenient place.
Next, open the `build.gradle` file. The first line is apply plugin: 'com.android.application', change it into apply plugin: 'com.android.library'.
## Generate Token
After that, go to your github account and navigate to Settings -> Developer Settings -> Personal Access Tokens -> Generate new token.
In the checklist, select write:packages, read:packages and Generate a token. You will see a token. This is the only time github will show you, so copy it and save it on a file on your computer for now. If you don't do it / lose it, basically it's gone for ever and so the only option is to regenerate/create a new token.
Once you have your token, go to your library project, create a new file named github.properties (or any other name that is meaningdul to you) and add your github username (because the token was generated from it) and the token, so the file now looks something like this:
```
gpr.usr=YOUR_USER_NAME
gpr.key=YOUR_TOKEN
```
We don't want our credentials to be compromised. So open the .gitignore file, and add github.properties in it. Then create a github repository and upload the library codes in it.
## Edit build.gradle file
Now open the build.gradle file again, and add the following code in it:
```
apply plugin: 'maven-publish'. // Apply this plugin at the top of your library build.gradle
def githubProperties = new Properties()
githubProperties.load(new FileInputStream(rootProject.file("github.properties"))) //Set env variable GPR_USER & GPR_API_KEY if not adding a properties file
def getVersionName = { ->
return "1.0.0" // Replace with version number
}
def getArtificatId = { ->
return "MyAwesomwLibrary" // your library name
}
publishing {
publications {
bar(MavenPublication) {
groupId 'com.yourcompany.anystring' // Replace with group ID/any meaningful string
artifactId getArtificatId()
version getVersionName()
artifact("$buildDir/outputs/aar/${getArtificatId()}-release.aar")
}
}
repositories {
maven {
name = "GitHubPackages"
/** Configure path of your package repository on Github
** Replace GITHUB_USERID with your/organisation Github userID
** and REPOSITORY with the repository name on GitHub
*/
url = uri("https://maven.pkg.github.com/GITHUB_USERID/REPOSITORY")
credentials {
/** Create github.properties in root project folder file with
** gpr.usr=GITHUB_USER_ID & gpr.key=PERSONAL_ACCESS_TOKEN
** Set env variable GPR_USER & GPR_API_KEY if not adding a properties file**/
username = githubProperties['gpr.usr'] ?: System.getenv("GPR_USER")
password = githubProperties['gpr.key'] ?: System.getenv("GPR_API_KEY")
}
}
}
}
```
## Publish Library
Finally, fire up your terminal and run the following commands:
```
$ cd path/to/MyAwesomeLibrary
$ gradle build # this line generates the library as .aar file
$ gradle publish # uploads the .aar file into github
```
## Use Your Library in other Project
Now that we have uploaded the library into github, we can use it.Let's create a new android project (say Prototype). Copy and paste the github.properties file that you created in the library into Prototype and add it into `.gitignore` file. After that, open the build.gradle file, and add edit it so that the file should look something like this:
```
apply plugin: 'com.android.application'
apply plugin: 'io.fabric'
/**Create github.properties in root project folder file with gpr.usr=GITHUB_USER_ID & gpr.key=PERSONAL_ACCESS_TOKEN**/
def githubPropertiesFile = rootProject.file("github.properties");
def githubProperties = new Properties()
githubProperties.load(new FileInputStream(githubPropertiesFile))
android {
// ...
}
dependencies {
// add myAwesomeLibrary
implementation 'com.yourcompany.anystring:MyAwesomeLibrary:1.0.0'
// implementation 'groupId:artifactId:versionNumber'
// Add MyAwesomeLibrary's dependencies
implementation ('com.alimuzaffar.lib:pinentryedittext:2.0.6')
// other dependencies
}
repositories {
maven {
name = "GitHubPackages"
/* Configure path to the library hosted on GitHub Packages Registry
* Replace UserID with package owner userID and REPOSITORY with the repository name
* e.g. "https://maven.pkg.github.com/enefce/AndroidLibraryForGitHubPackagesDemo"*/
url = uri("https://maven.pkg.github.com/UserID/REPOSITORY")
credentials {
/** Create github.properties in root project folder file with
** gpr.usr=GITHUB_USER_ID & gpr.key=PERSONAL_ACCESS_TOKEN
** Or set env variable GPR_USER & GPR_API_KEY if not adding a properties file**/
username = githubProperties['gpr.usr'] ?: System.getenv("GPR_USER")
password = githubProperties['gpr.key'] ?: System.getenv("GPR_API_KEY")
}
}
}
```
Remember, you need to add implementation 'groubId:ArtifactId:versionNumber' , so whatever you add in the library should be added in this format. Also, if your library has its own dependencies (such as alphamu/PinEntryEditText in this example as mentioned before), you must add them as well. Otherwise, your code won't run.
Finally, hit the hammer icon to build your project and then run it. Enjoy!
## References:
1. [proandroiddev.com](https://proandroiddev.com/publishing-android-libraries-to-the-github-package-registry-part-1-7997be54ea5a) | 48.653846 | 346 | 0.726324 | eng_Latn | 0.932907 |
fdce39b866e7b0be6bec75e510ce3022fafb37c8 | 3,402 | md | Markdown | README.md | wingedfox/cross-domain-local-storage | 68d4ad31ab5ca4ebf5c55bbf7ec572f740439d96 | [
"MIT"
] | null | null | null | README.md | wingedfox/cross-domain-local-storage | 68d4ad31ab5ca4ebf5c55bbf7ec572f740439d96 | [
"MIT"
] | null | null | null | README.md | wingedfox/cross-domain-local-storage | 68d4ad31ab5ca4ebf5c55bbf7ec572f740439d96 | [
"MIT"
] | null | null | null | Cross Domain Local Storage
==========================
1. [Problem](#problem)
2. [Solution](#solution)
3. [Why not use cookies?](#why-not-use-cookies)
4. [Installation](#installation)
5. [Usage](#usage)
6. [API](#api)
8. [Angular Support](#angular-support)
9. [Demo](#demo)
10. [Tests](#tests)
## Problem
As for now, standard HTML5 Web Storage (A.K.A Local Storage) doesn't now allow cross domain data sharing.
This may be a big problem in an organization which have a lot of sub domains and wants to share client data between them.
## Solution
xdLocalStorage is a lightweight js library which implements LocalStorage interface and support cross domain storage by using iframe post message communication.
## Why not use cookies?
Although cookies can be shared between sub domains, cookies have the overhead of being sent to the server on each request.
They're also have a size limit (4K for all cookies together)
## Installation
Download latest release from [here](https://github.com/ofirdagan/cross-domain-local-storage/releases) or use bower (recommended)
```sh
bower install xdLocalStorage --save
```
## Usage
- Create an empty html with the following content:
```html
<!DOCTYPE html>
<html>
<head>
<script src="xdLocalStoragePostMessageApi.min.js"></script>
</head>
<body>
This is the magical iframe
</body>
</html>
```
- On your client page (the page you will read/store your data from) add:
```html
<!-- if you use angular continue reading.. there's angular support -->
<script src="scripts/xdLocalStorage.min.js"></script>
```
- Init xdLocalStorage
```js
xdLocalStorage.init(
{
/* required */
iframeUrl:'path to your html from step 1',
//an option function to be called right after the iframe was loaded and ready for action
initCallback: function () {
console.log('Got iframe ready');
}
}
);
```
## API
```js
// Store
xdLocalStorage.setItem(key, value, function (data) {//callback});
// Retrieve
xdLocalStorage.getItem(key, function (data) {//callback });
// Remove
xdLocalStorage.removeItem(key, function (data) {//callback });
// Key Name
xdLocalStorage.key(index, function (data) {//callback });
// Clear All
xdLocalStorage.clear(function (data) {//callback });
```
## Angular Support
- import `ng-xdLocalStorage.min.js` instead of `xdLocalStorage.min.js`
- include xdLocalStorage module and config it.
```js
angular.module('yourModule', ['xdLocalStorage']).config(function (xdLocalStorageProvider) {
xdLocalStorageProvider.init(
{
/* required */
iframeUrl:'path to your html from step 1',
//an option function to be called right after the iframe was loaded and ready for action
initCallback: function () {
console.log('Got iframe ready');
}
});
});
```
- inject xdLocalStorage where ever you want and use the API
```js
angular.module('yourModule').run(function(xdLocalStorage) {
xdLocalStorage.setItem(key, value, function (data) {//callback});
});
```
## Demo
**Here's the <a href="https://rawgit.com/ofirdagan/cross-domain-local-storage/master/app/index.html" target="_blank">demo</a>**
## Tests
I covered the basic API with tests [here](https://github.com/ofirdagan/cross-domain-local-storage/blob/master/test/specs/xdLocalStorage.js) | 26.372093 | 159 | 0.677837 | eng_Latn | 0.845528 |
fdce4d7a84ee3479531f190da50c38271fc55ede | 2,496 | md | Markdown | README.md | React-Native-Daejeon/swiper-zoom-view | bd9b306fffe7ed6a63a460d90ae1ea504be33afe | [
"MIT"
] | 3 | 2020-08-03T19:15:56.000Z | 2021-06-07T03:07:04.000Z | README.md | React-Native-Daejeon/swiper-zoom-view | bd9b306fffe7ed6a63a460d90ae1ea504be33afe | [
"MIT"
] | 1 | 2020-12-26T06:59:31.000Z | 2020-12-26T06:59:31.000Z | README.md | React-Native-Daejeon/swiper-zoom-view | bd9b306fffe7ed6a63a460d90ae1ea504be33afe | [
"MIT"
] | null | null | null | <h1 align="center">
Swiper Zoom View
</h1>
<p align='center'>
<a href="https://badge.fury.io/js/swiper-zoom-view">
<img src="https://badge.fury.io/js/swiper-zoom-view.svg" alt="npm version">
</a>
<a href="[https://github.com/React-Native-Daejeon/swiper-zoom-view/blob/master/LICENSE](https://github.com/React-Native-Daejeon/swiper-zoom-view/blob/master/LICENSE)">
<img src="https://img.shields.io/badge/License-MIT-blue.svg" alt="Swiper Zoom View is released under the MIT license"/>
</a>
</p>
Swiper Zoom View는 간단한 이미지 갤러리 뷰를 보여주는 UI Component이며, iOS 및 Android 모두에서 사용이 가능합니다. Swiper Zoom View를 사용하면, 이미지들을 넘겨서 확인할 수 있으며 몇 가지 간단한 줌 액션을 사용할 수 있습니다.
Swiper Zoom View is a simple React Native UI Component that shows images gallery view for iOS and Android. You can use some zoom actions of image.
<br />
## 🙆♀ Installation
아래의 명령어를 통해 swiper-zoom-view를 설치할 수 있습니다.
Through the command to install swiper-zoom-view.
```bash
npm install --save swiper-zoom-view
```
<br />
## 📌 How to use
swiper-zoom-view를 import하고 render에서 아래와 같이 사용할 수 있습니다.
Import swiper-zoom-view and you can use it as below.
```js
import SwiperView from 'swiper-zoom-view';
...
return (
<SwiperView
initialData={[require("./image1.png"), require("./image2.png")]}
initialScrollIndex={0}
/>
);
```
<br />
## 📒 Props
아래의 모든 props를 사용하여 Swiper Zoom View를 적절하게 커스터마이징 하여 사용할 수 있습니다.
You can use all of the props below and customize Swiper Zoom View.
| props | required | type | description |
|-------|----------|--------|--------------------|
| initialData | O | image[ ] | List of images that is showed. Type of images is `string` or `object` that contains uri field|
| initialScrollIndex | X (default is `0`) | number | Index of image that is showed first .|
| width | X (default is `full width size` of window) | number | Width of swiper view component |
| height | X (default is `full height size` of window) | number | Height of swiper view component|
| backgroundColor | X (default is `black`) | string | Color of background |
| renderItem | X (default is `(info: ListRenderItemInfo) => React.Element`) | ListRenderItem | How to render the images |
| onRefresh | X | (prevData: images[], prevIndex: number) => PromiseLike<{newIndex: number, newData: image[]}> | How to refresh the view |
<br />
## 📱 Example (Demo)
<br />
## 📑 License
Swiper Zoom View is released under the [MIT license](https://github.com/React-Native-Daejeon/swiper-zoom-view/blob/master/LICENSE).
| 34.666667 | 168 | 0.691506 | kor_Hang | 0.764172 |
fdcf3f9fc9717aa9c4c72c0749e14f54051c30b1 | 560 | md | Markdown | includes/functions-durable-v1-tutorial-note.md | RobAaldijk/azure-docs.nl-nl | 519c7fc80075795af2670d665d1d93078faf7a87 | [
"CC-BY-4.0",
"MIT"
] | 16 | 2017-08-28T07:45:43.000Z | 2021-04-20T21:12:50.000Z | includes/functions-durable-v1-tutorial-note.md | RobAaldijk/azure-docs.nl-nl | 519c7fc80075795af2670d665d1d93078faf7a87 | [
"CC-BY-4.0",
"MIT"
] | 575 | 2017-08-30T07:14:53.000Z | 2022-03-04T05:36:23.000Z | includes/functions-durable-v1-tutorial-note.md | RobAaldijk/azure-docs.nl-nl | 519c7fc80075795af2670d665d1d93078faf7a87 | [
"CC-BY-4.0",
"MIT"
] | 58 | 2017-07-06T11:58:36.000Z | 2021-11-04T12:34:58.000Z | ---
author: anthonychu
ms.service: azure-functions
ms.topic: include
ms.date: 11/03/2019
ms.author: antchu
ms.openlocfilehash: a45e73721babcdbc10416b937c2c11e35df4ff69
ms.sourcegitcommit: 58faa9fcbd62f3ac37ff0a65ab9357a01051a64f
ms.translationtype: MT
ms.contentlocale: nl-NL
ms.lasthandoff: 04/29/2020
ms.locfileid: "73614577"
---
> [!NOTE]
> Dit is een zelf studie voor Durable Functions 1. x. Zie de documentatie voor [Durable functions versies](../articles/azure-functions/durable/durable-functions-versions.md) als u Durable functions 2. x wilt gebruiken. | 37.333333 | 218 | 0.805357 | nld_Latn | 0.30718 |
fdcf854f99a76c7812877406089667be7f550d98 | 348 | md | Markdown | mobile/README.md | CaioOliveira793/Next-Level-Week-1 | 3e078b30cd5f0afa9f434715df01ebadf5fac326 | [
"MIT"
] | null | null | null | mobile/README.md | CaioOliveira793/Next-Level-Week-1 | 3e078b30cd5f0afa9f434715df01ebadf5fac326 | [
"MIT"
] | 7 | 2021-05-11T16:37:37.000Z | 2022-02-27T06:05:23.000Z | mobile/README.md | CaioOliveira793/Next-Level-Week-1 | 3e078b30cd5f0afa9f434715df01ebadf5fac326 | [
"MIT"
] | null | null | null | # Mobile
## Como Executar
No diretorio do mobile, execute
```cmd
yarn install
yarn start
```
ou
```cmd
npm install
npm start
```
### Dispositivo Físico
Para utilizar seu dispositivo instale o app expo na sua loja de aplicativo e escaneie o QR code.
### Emulador
Caso preferir utilizar um emulador, o expo irá detectá e executar o projeto.
| 13.384615 | 96 | 0.732759 | por_Latn | 0.960985 |
fdd040fc2ce9a13068e0f7c98da40fc95e28f866 | 1,463 | md | Markdown | 2020/11/04/2020-11-04 16:35.md | zhzhzhy/WeiBoHot_history | 32ce4800e63f26384abb17d43e308452c537c902 | [
"MIT"
] | 3 | 2020-07-14T14:54:15.000Z | 2020-08-21T06:48:24.000Z | 2020/11/04/2020-11-04 16:35.md | zhzhzhy/WeiBoHot_history | 32ce4800e63f26384abb17d43e308452c537c902 | [
"MIT"
] | null | null | null | 2020/11/04/2020-11-04 16:35.md | zhzhzhy/WeiBoHot_history | 32ce4800e63f26384abb17d43e308452c537c902 | [
"MIT"
] | null | null | null | 2020年11月04日16时数据
Status: 200
1.沈梦辰向靳梦佳道歉
微博热度:3055791
2.多名孩子身上现针眼3涉案教师被批捕
微博热度:2673924
3.易烊千玺双11主题曲
微博热度:2669709
4.梁静茹方承认恋情
微博热度:2463164
5.张继科叫金晨我们晨晨
微博热度:2178930
6.美国内华达州发生枪击
微博热度:1441531
7.20多个孩子替去世同学孝敬父母
微博热度:1018485
8.iPhone或将重新使用Touch ID
微博热度:963440
9.美国正式退出巴黎协定
微博热度:956247
10.网购同一商品不同账号价格差25元
微博热度:954094
11.不清不楚的一律按照张大大处理
微博热度:938283
12.王牌对王牌
微博热度:927223
13.爸爸回应赤脚捞宝宝扔的玻璃渣
微博热度:912250
14.美国大选
微博热度:889783
15.蚂蚁集团致歉
微博热度:878124
16.2020的水逆都结束啦
微博热度:850224
17.胡歌探班唐嫣
微博热度:842455
18.男子10秒内2次躲过死神
微博热度:833205
19.郑州大学
微博热度:828723
20.隐秘的角落日本定档
微博热度:828698
21.小孩子的脚真的好灵活
微博热度:790868
22.新郎婚礼当日坠亡新娘继承183万
微博热度:671458
23.梁静茹林达光恋情
微博热度:613272
24.幼儿园男老师获最佳梳头奖
微博热度:595373
25.月牙泉景区来了一只小白狐
微博热度:593391
26.Yeri发悼念文配大笑照片
微博热度:593028
27.金钟大寸头
微博热度:560412
28.90后断臂女孩时装周走秀
微博热度:521769
29.边防战士涂防晒和唇膏的样子
微博热度:508304
30.被表白了也别开心太早
微博热度:499415
31.赵让
微博热度:496688
32.金莎盛况约会像偶像剧
微博热度:386419
33.女儿们的恋爱
微博热度:344723
34.飙车时速超250公里司机被处2个月拘役
微博热度:296790
35.日本街头仙人掌长到3层楼高
微博热度:295654
36.把节目制服穿成高定
微博热度:270669
37.喻言成立个人工作室
微博热度:261750
38.美国疫情
微博热度:244773
39.四六级成绩
微博热度:221282
40.白宫专家称美新冠疫情进入最致命阶段
微博热度:208456
41.瑞士日内瓦最低工资月薪近3万
微博热度:205679
42.外交部回应美同意向台湾出售无人机
微博热度:205357
43.2020KPL秋季赛
微博热度:205058
44.424的绝望
微博热度:204209
45.美术老师教学生用毛线编织美食
微博热度:203760
46.北京气温下半年来首次破零
微博热度:203228
47.马拉多纳脑部血肿将进行手术
微博热度:202717
48.腿麻能严重到什么程度
微博热度:202594
49.搭讪纸条原来可以这样写
微博热度:196285
50.上百头鲸鱼在斯里兰卡搁浅
微博热度:195333
| 7.171569 | 22 | 0.789474 | yue_Hant | 0.34418 |
fdd0e5f92350ef2e6c9a409dba74b8d84814b674 | 4,701 | markdown | Markdown | _posts/2019-06-11-erd-co-work.markdown | ubcare/ubcare.github.io | 1640f720e54800e1bc9b4616a260d1150fa8d51a | [
"MIT"
] | 1 | 2019-08-22T05:28:11.000Z | 2019-08-22T05:28:11.000Z | _posts/2019-06-11-erd-co-work.markdown | ubcare/ubcare.github.io | 1640f720e54800e1bc9b4616a260d1150fa8d51a | [
"MIT"
] | 1 | 2021-03-29T20:35:24.000Z | 2021-03-29T20:35:24.000Z | _posts/2019-06-11-erd-co-work.markdown | ubcare/ubcare.github.io | 1640f720e54800e1bc9b4616a260d1150fa8d51a | [
"MIT"
] | 1 | 2019-01-24T01:04:09.000Z | 2019-01-24T01:04:09.000Z | ---
layout: post
title: "ERD 협업! Aquerytool 소개"
date: 2019-06-07
author: 강성욱
categories: Post
//tag : database,query,erd
cover: "/assets/chipmunk.jpg"
---
# AQueryTool
Web 환경에서 간단하게 ERD를 그려볼 수 있는 Tool 이 있어 소개 해 보려고 합니다.
간단하게 ERD 를 그리고 관계를 설정하고, Query를 뽑아낼때 생산성 측면에서 활용이 가능할것으로 생각됩니다.
관련 소개와 도움말과 관련해서는 [해당 링크](https://aquerytool.com/help/index/){: target="blank"}를 참조하시면 더 자세하게 설명되어 있습니다.
<br>
<br>
## 1. 회원 가입 및 로그인
- AQuueryTool : [https://aquerytool.com](https://aquerytool.com/){: target="blank"} 에 접속
- 회원가입을 하지않아도 ERD 작성하고, 관련 SQL을 생성할 수 있지만, 작성한 ERD를 저장하거나 공유, 불러오기등을 위해서는 회원가입 및 로그인이 필요합니다.
<br><br>
## 2 테이블 추가 및 ERD 초기 정보 설정
- 로그인 하지 않고 사용할 수 있습니다. 저장하지 않은 ERD는 다시 불러올 수 없습니다. 이점을 주의하여 사용하여 주십시오. 간단하게 활용만 한다면, 회원가입 할 필요는 없습니다.
- 오른쪽 마우스 버튼을 누르면 다음과 같은 버튼이 나타나며, 테이블 추가가 가능합니다.
- 처음테이블을 추가 했을때는 ERD 에 대한 초기설정 팝업이 표시 됩니다.
- DataBase Type 과 (ORACLE , MySQL, MSSQL, MariaDB) , ERD Name 등을 지정하게 되고, 로그인 하지 않을 시에 저장되지 않는다는 경고문구가 출력됩니다.
- 데이터 베이스 타입을 지정하면, 해당 DBMS에 맞는, 생성 SQL Query를 뽑아 낼 수 있습니다. 그 밖에도, 자주 사용하는 쿼리등을 참조하면, 해당 테이블의 생성 , 삭제 , 연관테이블과의 조인 쿼리도 생성해주니 활용해보시면 좋을 것 같습니다.
<br><br>
## 3. 테이블 인터페이스 설명
테이블이 생성되면 다음과 같은 인터페이스를 가지게 되고 테이블 마다 메뉴를 통해 여러 작업을 수행할 수 있습니다.
<br><br>
### Table User Interface 간단 설명
<br><br>
### SQL / Model Menu
- 테이블 생성 SQL - 해당 테이블을 생성하는 SQL 을 작성해 줍니다.
- 즐겨 쓰는 SQL : 아래와 같은 기능들이 포함
- 테이블 복사 , 백업
- Select
- Paging Select
- Insert , Update, Delete
- 테스트 데이터 생성 : 해당 테이블의 테스트 데이터 생성
- Java 모델 생성 : Java 모델(Data Class) 자동 생성
- C# 모델 생성 : C# 모델(Data Class) 자동 생성
- Json 모델 생성 : Json 모델 자동 생성
<br><br>
## 4. 테이블 간의 관계 설정
- FK 컬럼을 마우스로 드래그 하여 참조할 테이블의 컬럼에 드랍 하면 관계가 설정 됩니다.
<br><br>
## 5. 인덱스 설정
- 테이블 하단의 인덱스 설정 메뉴를 클릭 합니다.
- 인덱스로 설정하고 싶은 컬럼 값을 마우스로 드래그 & 드랍 하여 인덱스 카트에 삽입 합니다.
- 최종적으로 인덱스 카트에 담긴 인덱스를 추가 합니다.
<br><br>
## 6. ERD Export - 모든 테이블 생성 SQL 파일 생성
- ERD에 그려져 있는 Table 들을 모두 생성하는 SQL 쿼리를 뽑아낼 수 있습니다.
- 그 밖에도, 이미지파일로 저장하거나 엑셀등의 포맷으로 저장할 수 있습니다.
<br><br>
## 7. ERD Share - Read Only URL 생성
- 서버에 저장된 ERD를 읽기전용으로 공유할 수 있는 방법입니다. 아쉽게도 저장되지 않거나 로그인하지 않고 공유하는 방법은 없는 것 같습니다.
- 이 방법으로 공유된 링크는 비회원도 비밀번호를 입력하여 ERD에 읽기 전용으로 접근할 수 있습니다.
- New Link 버튼을 누르면 다음과 같이 읽기권한이 부여된 접근 가능한 URL이 생성 됩니다.
- 비밀번호도 같이 부여되어, 공유 시 비밀번호도 같이 알려주어야 접근 가능 하니 주의하여 주시기 바랍니다.
<br><br>
## 8. ERD 공유 - 회원 간 공유 요청 및 허가
- 읽기전용 뿐만 아니라 같이 협업시 수정도 할 수 있게끔 회원간 ERD를 공유할 수 있습니다.
- ERD 공유 설정을 누르면, 해당 ERD를 공유할 수 있는 Code를 발급해주는 설정 창이 나옵니다 .
- 해당 코드를 클립보드에 복사하여, 공유를 원하고자 하는 사용자에게 알려주시면 상대방이 ERD 사용 권한을 ERD 작성자에게 요청할 수 있습니다.
- 접근 코드를 전달 받았다면, 다음 메뉴를 통해 공유 요청을 수행 할 수 있습니다.
- 다음과 같이 전달받은 코드를 입력하여 권한을 요청 합니다.
- ERD 의 최초 생성자는 권한 설정에서 권한 요청 목록을 확인하고, 권한을 부여해주면 됩니다. 쓰기 권한의 경우 실제 확인된 사용자만 부여하는것이 보안상 좋으니 주의 바랍니다.
- 권한이 잘 요청 되었다면, 다음과 같이 접근 권한 대기중 상태의 요청 건이 ERD 소유자 에게 보여지게되고, Edit , Read 권한을 부여한 후 저장 하여 주면 상대방이 ERD 불러오기를 통해 ERD 에 접근 할 수 있습니다.
- 권한 요청자는 권한이 부여된 후 ERD를 불러오기 메뉴를 통해 Load 할 수 있습니다.
끝. | 34.065217 | 142 | 0.71538 | kor_Hang | 0.999999 |
fdd23b042260628324c18a4f2d55325d969a91b2 | 3,884 | md | Markdown | docs/advanced-analytics/machine-learning-troubleshooting-faq.md | thiagoamc/sql-docs.pt-br | 32e5d2a16f76e552e93b54b343566cd3a326b929 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/advanced-analytics/machine-learning-troubleshooting-faq.md | thiagoamc/sql-docs.pt-br | 32e5d2a16f76e552e93b54b343566cd3a326b929 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/advanced-analytics/machine-learning-troubleshooting-faq.md | thiagoamc/sql-docs.pt-br | 32e5d2a16f76e552e93b54b343566cd3a326b929 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "Solução de problemas e perguntas Frequentes para o aprendizado de máquina no SQL Server | Microsoft Docs"
ms.custom:
ms.date: 03/16/2018
ms.prod: machine-learning-services
ms.prod_service: machine-learning-services
ms.service:
ms.component:
ms.reviewer:
ms.suite: sql
ms.technology:
ms.tgt_pltfrm:
ms.topic: article
author: HeidiSteen
ms.author: heidist
manager: cgronlun
ms.workload: Inactive
ms.openlocfilehash: 5b9a5c6497781ef67d9d2ef9b9032a4d9ee250e5
ms.sourcegitcommit: 8e897b44a98943dce0f7129b1c7c0e695949cc3b
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 03/21/2018
---
# <a name="troubleshoot-machine-learning"></a>Solucionar problemas de aprendizado de máquina
[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md-winonly](../includes/appliesto-ss-xxxx-xxxx-xxx-md-winonly.md)]
Este artigo fornece links para solução de problemas para guias de configuração, problemas conhecidos e notas de versão. Outros artigos vinculados a este artigo fornecerá subsídio sobre otimização de desempenho para soluções de aprendizado de máquina no SQL Server.
Use esta página como ponto de partida para localizar problemas conhecidos, perguntas comuns de instalação e procedimentos para solução de problemas.
**Aplica-se a:** R Services do SQL Server 2016, SQL Server 2017 Services (R e Python) de aprendizado de máquina
## <a name="known-issues"></a>Problemas conhecidos
Os artigos a seguir listam os problemas conhecidos com a versão atual ou descrevem problemas com versões anteriores:
+ [Problemas conhecidos do R Services](../advanced-analytics/known-issues-for-sql-server-machine-learning-services.md)
+ [Notas de versão do SQL Server 2016](../sql-server/sql-server-2016-release-notes.md)
+ [Notas de versão do SQL Server 2017](../sql-server/sql-server-2017-release-notes.md)
## <a name="troubleshooting-prerequisites"></a>Pré-requisitos de solução de problemas
Se você encontrou um erro ou precisa entender um problema em seu ambiente, é importante que você colete sistematicamente informações relacionadas. Essas informações incluem a versão, a edição, o contexto de segurança e o contexto de execução.
O artigo a seguir fornece uma lista de informações que facilita a solução de problemas de autoajuda, ou uma solicitação para obter suporte técnico.
+ [Coleta de dados para a solução de problemas de aprendizado de máquina](data-collection-ml-troubleshooting-process.md)
## <a name="setup-and-configuration-guides"></a>Guias de instalação e configuração
Comece aqui se você não configurou o aprendizado de máquina com o SQL Server, ou se você deseja adicionar o recurso:
+ [Instale os serviços de aprendizado de máquina do SQL Server de 2017 (no banco de dados)](install/sql-machine-learning-services-windows-install.md)
+ [Instalar o servidor do aprendizado de máquina 2017 SQL Server (autônomo)](install/sql-machine-learning-standalone-windows-install.md)
+ [Instalar o SQL Server 2016 R Services (no banco de dados)](install/sql-r-services-windows-install.md)
+ [Instalar o SQL Server 2016R Server (autônomo)](install/sql-r-standalone-windows-install.md)
+ [Instalação de prompt de comando](install/sql-ml-component-commandline-install.md)
+ [Instalação offline (sem internet)](install/sql-ml-component-install-without-internet-access.md)
### <a name="configuration"></a>Configuração
Os seguintes artigos contêm informações sobre os padrões e como personalizar a configuração em uma instância do aprendizado de máquina:
+ [Modificar o pool de conta de usuário do SQL Server R Services](r/modify-the-user-account-pool-for-sql-server-r-services.md)
+ [Configurar e gerenciar extensões de análise avançada](r/configure-and-manage-advanced-analytics-extensions.md)
+ [Como criar um pool de recursos](r/how-to-create-a-resource-pool-for-r.md)
+ [Otimização para cargas de trabalho de R](r/operationalizing-your-r-code.md)
| 57.117647 | 264 | 0.790165 | por_Latn | 0.98948 |
fdd2dde28c8cab192b59c87438090ea1d762bc09 | 552 | md | Markdown | dynamicsax2012-technet/unit-of-work.md | s0pach/DynamicsAX2012-technet | 8412306681e6b914ebcfad0a9ee05038474ef1e6 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-06-16T22:06:04.000Z | 2020-06-16T22:06:04.000Z | dynamicsax2012-technet/unit-of-work.md | s0pach/DynamicsAX2012-technet | 8412306681e6b914ebcfad0a9ee05038474ef1e6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | dynamicsax2012-technet/unit-of-work.md | s0pach/DynamicsAX2012-technet | 8412306681e6b914ebcfad0a9ee05038474ef1e6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: " unit of work"
TOCTitle: " unit of work"
ms:assetid: DynamicsAXGlossary.1510903
ms:mtpsurl: https://technet.microsoft.com/library/dynamicsaxglossary.1510903(v=AX.60)
ms:contentKeyID: 36057649
author: Khairunj
ms.date: 08/25/2014
mtps_version: v=AX.60
f1_keywords:
- Glossary.unit of work
---
# unit of work
An object that uses referential integrity constraints to sequence database reading and writing operations in one atomic work process.
## See also
[Microsoft Dynamics AX glossary](glossary/microsoft-dynamics-ax-glossary.md)
| 22.08 | 133 | 0.775362 | eng_Latn | 0.754821 |
fdd39f70ac7b6d568efe69b582064bbbb3e9571a | 816 | md | Markdown | README.md | elmahio/Elmah.Io.AspNetCore.Serilog | 86512268cc9aa4c1c799f087cf9151b133e9bc4b | [
"Apache-2.0"
] | 1 | 2021-08-29T02:13:52.000Z | 2021-08-29T02:13:52.000Z | README.md | elmahio/Elmah.Io.AspNetCore.Serilog | 86512268cc9aa4c1c799f087cf9151b133e9bc4b | [
"Apache-2.0"
] | null | null | null | README.md | elmahio/Elmah.Io.AspNetCore.Serilog | 86512268cc9aa4c1c799f087cf9151b133e9bc4b | [
"Apache-2.0"
] | 1 | 2021-08-29T02:13:54.000Z | 2021-08-29T02:13:54.000Z | # Elmah.Io.AspNetCore.Serilog
[](https://github.com/elmahio/Elmah.Io.AspNetCore.Serilog/actions/workflows/build.yml) [](https://www.nuget.org/packages/Elmah.Io.AspNetCore.Serilog/)
Middleware that uses Serilog's `LogContext` to decorate all log messages from ASP.NET Core with HTTP context information like URL and status code. The middleware is not specific to [elmah.io](https://elmah.io) but is typically used with the `Serilog.Sinks.ElmahIo` package and ASP.NET Core.
Documentation: [https://docs.elmah.io/logging-to-elmah-io-from-serilog/#aspnet-core](https://docs.elmah.io/logging-to-elmah-io-from-serilog/#aspnet-core) | 116.571429 | 338 | 0.784314 | yue_Hant | 0.445299 |
fdd4c0ea5c5fcd21386c25efe5ed3d1ef7655735 | 365 | md | Markdown | Project/README.md | Doc-Ix/MLCommunity_SageMaker_II | 7561c7772e62f318850be3455eb2ad7ca77682b0 | [
"MIT"
] | null | null | null | Project/README.md | Doc-Ix/MLCommunity_SageMaker_II | 7561c7772e62f318850be3455eb2ad7ca77682b0 | [
"MIT"
] | null | null | null | Project/README.md | Doc-Ix/MLCommunity_SageMaker_II | 7561c7772e62f318850be3455eb2ad7ca77682b0 | [
"MIT"
] | null | null | null | # SageMaker Deployment Project
The notebook and Python files provided here, once completed, result in a simple web app which interacts with a deployed recurrent neural network performing sentiment analysis on movie reviews. This project assumes some familiarity with SageMaker, the mini-project, Sentiment Analysis using XGBoost, should provide enough background.
| 91.25 | 332 | 0.835616 | eng_Latn | 0.995452 |
fdd4dffd4c0205ac68c41355d767992de7454532 | 2,794 | md | Markdown | CHANGELOG.md | ef4/cardstack | 80e3866b2551102d295ab4d66824d2a84d5cc704 | [
"MIT"
] | 344 | 2017-03-27T21:34:16.000Z | 2022-03-20T18:16:57.000Z | CHANGELOG.md | ef4/cardstack | 80e3866b2551102d295ab4d66824d2a84d5cc704 | [
"MIT"
] | 1,337 | 2017-04-04T00:51:27.000Z | 2022-03-31T19:59:44.000Z | CHANGELOG.md | ef4/cardstack | 80e3866b2551102d295ab4d66824d2a84d5cc704 | [
"MIT"
] | 56 | 2017-04-01T15:25:30.000Z | 2022-03-15T16:30:44.000Z | # Changelog
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
Since this is a pre-1.0 project,
it will track only significant breaking changes
and features, and is not intended to be an exhaustive list.
## [v0.19.0]
This version introduces a newer hub, where our cards are actually backed
by an javascript serialization stead of a JSON serialization and we have a
card compiler that can compile card hbs files into javascript. We are also
introducing a new web-client, and an SDK to use the card protocol for cardpay.
## [v0.18.0]
This version included the work for the "new Hub" aka "Hub v2,"
a card-centric rewrite of Cardstack internals, APIs, and mental models.
This is a significant breaking change.
See https://github.com/cardstack/cardstack/pull/1432 to view the change
in source code.
## [v0.17.0]
This release concludes a series of 409 conflict bugfixes
for the base card and seeded featured cards.
The bugfix work starteds in `v0.16.27`. See #1437
### Changed
- Breaking - Seeds no longer run for production deployments.
You must create seed data via the Card Builder UI
or in a data source directly. This fixes some 409 conflict issues
for featured cardsin deployed environments. See #1411
## [v0.16.22]
### Added
- core type `link` #1255
- core type `cta` #1255
## [v0.16.13]
### Added
- Feature: image core type
## [v0.14.22] - 2019-08-15
When upgrading, `@cardstack/eslint-config/browser` should become `@cardstack/eslint-config/ember-addon`
throughout a project. Then, `babel-eslint` should be added as a peer dependency in the top level
`package.json` with `yarn add -D -W babel-eslint`
### Added
- Commits for the WIP Cardstack CLI
### Changed
- Bugfix for tools package - enable string field editor #813
- error logging
- docs for git plugins
- more linting configuration to support using TypeScript
- Breaking - eslint plugin rules have changed filepaths for imports. See migration instructions above. #824
## [v0.14.21] - 2019-07-18
This is a summary of breaking changes and new features since `v0.13`.
To upgrade a project from `v0.13` to `v0.14`, follow
[these steps](https://github.com/cardstack/cardboard/issues/95)
Affected APIs include:
- `searchers.get()`
- `searchers.getFromControllingBranch()`
- `searchers.searchFromControllingBranch()`
- `searchers.search()`
- `indexers.beginUpdate()`,
- `controlling-branch` dependency injection
- `forBranch()`
- `forControllingBranch()`
- `writers.create()`
- `writers.update()`
- linting config
### Changed
- [FEATURE] Improved UX and designs for the Right Edge #752
### Removed
- [BREAKING] remove concept of `branches` #747
## Prior versions
See the [Releases](https://github.com/cardstack/cardstack/releases) and git commit
history for changes prior to `v0.14`.
| 29.104167 | 107 | 0.746242 | eng_Latn | 0.984479 |
fdd530124913fdf3f92bd88ad30b7cbab6662294 | 10,015 | md | Markdown | README.md | jucasoliveira/crypto-ratings | 32baabc13ea86bb3d70d4cf920b09d79b4ea2f0e | [
"Apache-2.0"
] | null | null | null | README.md | jucasoliveira/crypto-ratings | 32baabc13ea86bb3d70d4cf920b09d79b4ea2f0e | [
"Apache-2.0"
] | null | null | null | README.md | jucasoliveira/crypto-ratings | 32baabc13ea86bb3d70d4cf920b09d79b4ea2f0e | [
"Apache-2.0"
] | null | null | null | # Welcome to crypto-ratings
A rating / insurance platform of the crypto world
## Intention
The crypto market is a wild west. And this market was born with the intention of being decentralized and, being decentralized, it is practically impossible to be regulated by a centralized institution.
In recent centuries, we have experienced a cycle in markets where:
1. The market emerges without regulation, gains and losses happen.
2. Massive losses happen, people ask for regulation
3. A centralized institution comes with a "solution" and that market is regulated
Like it or not, every market ends up being regulated in one way or another. We can discuss whether regulations made by centralized institutions really have a positive effect or not, but these regulations exist anyway.
But the market for cryptocurrencies and financing/decentralized organizations is a little different for a few fundamental reasons:
1. It is fully combined on the Internet.
2. It is decentralized.
3. It is mostly encrypted.
These 3 reasons make any cryptocurrency, defi, dao virtually impossible to be regulated, because these assets/companies can be created anywhere in the world, far from the regulations of one country.
Although there is some kind of regulation that centralized institutions can do, these will be mainly focused on users of services provided with the crypto market, and they will only manage to force a lawsuit against decentralized institutions if some of these currencies, defi's and dao's meet within the reach of their jurisdiction. So its virtual impossible.
But regulating a decentralized market can be achieved naturally. When institutions go after more money to finance their operations, financial institutions will require the market to become more controlled... at least the main part of it, so how can we regulate it?
## Proposal
### Introducing Crypto Ratings
A Risk Evaluation in Decentralized Risk Management.
Throughout the years, financial institutions were looking at how they can trust borrow money from other institutions and understand the risks of not getting their money back. So some of them started to create rating grades, creating a risk assessment of those who seek investment, from companies to countries. Today, when a country want's to issue debt, investors look at S&P, Moody's, Fitch, DBRS risk ratings to understand how risky it is to borrow money from that country and get their money back ... with interests, and riskier the country, riskier is to get you money back.
And that's what I came to you to propose one of the solutions to regulate the crypto market: Educate on how risky it is to put your money on cryptos.
Today on decentralized market, we don't have those risk assessments yet, and you learn about scamming coins, defi's, and dao's only by experience and learning, but some people learn that too late when they already lost loads of money and put their life at risk. So I want to provide a platform where an Asset/Institution can be scanned, rated and this rate maintained by the community.
And for that, we have to understand how we can issue a risk assessment of a crypto asset/institution.
### Definitions
The terms below are defined for use in this paper standard of practice.
- **Whale**: A cryptocurrency wallet which hold's large amount of assets based on BTC comparison;
- **Wallet**: A crypto hash which holds assets such as crypto coins, NFT's , etc;
- **Economic Capital**: A set of factors which evaluates the capital of an DOrg and it's likelihood of survival or to meet
a business objective for a specified period of time and risk metric, given its risk profile.
- **Emerging Risk** : New or evolving risks that may be difficult to manage since their
likelihood, impact, timing or interdependency with other risks are highly uncertain.
- **Decentralized Risk Management** : The discipline by which an DOrg assesses, controls, exploits, finances and monitors risks from all sources for the purpose
of increasing the organization’s/cryptos short- and long-term value to its stakeholders.
- **Decentralized Risk Management Control Cycle** : The continuing process by which risks are
identified, risks are evaluated, risk appetites are chosen, risk limits are set, risks are
accepted or avoided, risk mitigation activities are performed, and actions are taken when
risk limits are breached.
- **DOrg** : The entity for which DRM is being performed. Examples include crypto assets, decentralized finance, and decentralized organizations.
- **Risk** : The potential of future losses or shortfalls from expectations due to deviation of
actual results from expected results.
- **Risk Appetite** : The level of aggregate risk that an DOrg chooses to take in pursuit
of its objectives.
- **Risk Evaluation System** : A combination of practices, tools, and methodologies within a
risk management system used to measure the potential impacts of risk events on the
performance metrics of an DOrg.
- **Risk Limit** : A threshold used to monitor the actual risk exposure of a specific unit or
units of the DOrg to ensure that the level of aggregate risk remains within the risk
tolerance.
- **Risk Management System** : A combination of practices, tools and methodologies that an
DOrg uses to identify, assess, measure, mitigate, and manage the risks it faces
during the course of conducting its business.
- **Risk Metric** : A measure of risk. Examples include value at risk, expected policyholders
deficit, and conditional tail expectation.
- **Risk Mitigation** : Action that reduces the frequency or severity of a risk.
- **Risk Profile** :The risks to which an DOrg is exposed over a specified period of
time.
- **Risk Tolerance** : The aggregate risk-taking capacity of an DOrg.
- **Scenario Test** : A process for assessing the impact of one possible event or several
simultaneously or sequentially occurring possible events on an DOrg financial
position.
- **Stress Test** : A process for measuring the impact of adverse changes in one or relatively
few factors affecting an DOrg financial position.
### Economic Capital
Economic capital is a set of evaluation of some DOrg specific factors, those are:
- **Liquidity risk**: Funding collateral given on liquidity pool and the spread of wallet holders of that pool, with Transactions and Volume indicators;
- **Interest Rate risk**: The interest rates of the pairs on the liquidity pools;
- **Market risk**: NVT Ratio;
- **Operational risk**: Combination of Realized P/L, Net Realized P/L , and Realized P/L ratio loss;
- **Business risk**: Volatility of the price of the asset;
### Risk Management system
A DOrg may or may not have any system to identify the risks of it's own institution, to understand if a DOrg have a RMS , we need to evaluate it's type.
#### CryptoCurrency
Evaluate a cryptocurrency might need to investigate it's source code, rather a participant node of the network or a smart contract, containing the rules of transaction and holdings of the asset.
The main factors to evaluate a RMS on a cryptocurrency are:
- **Anti-bot implementation**: A piece of code which provides safety measurements against trading bots;
- **Anti-liquidation implementation**: A piece of code which provides safety against instant liquidation of the asset;
- **Anti-laundry implementation**: A piece of code which provides traceability of the asset's traded;
#### DeFi
- **Liquidity collateral risk**: Safety measurements of the collateral fo the liquidity pool;
- **Liquidation safety**: A liquidation smart contract which insure network users safety returns in case of large liquidation;
#### DAO
### Risk Evaluation
How we going to evaluate a risk in many contexts, using various tools such as economic capital models and stress and scenario tests? In
performing services related to risk evaluation, we should consider, or may rely on others who have considered, the following:
Information about the financial strength, risk profile, and risk environment of the
organization that is appropriate to the assignment. Such information may include
the following:
#### For crypto coin
1. The number of whales wallet holding the asset;
2. The contract limits of transaction and or a risk management system, a.k.a anti bot;
3. the potential differences between the volatility of the coin price both in short term and long-term ;
4. the interests, including the risk/reward expectations, of relevant
stakeholders on liquidity pools. These stakeholders may include some or all of the following:
owners wallets, whales wallets and others potentially impacted by the
DOgs management of risk;
5. external ratings criteria for risk levels and the implications of
potential risk levels on the continuation of the coin exchange as reflected
in ratings or other external measures of security;
6. the degree to which the origins wallets interact withing other risk managed DOg's and whales;
7. the economic capital evaluation;
8. limitations to the coin's liquidation returns to stakeholders; and
9. the extent to which the DOg's exposure to risks may differ from
the exposures of its competitors.
#### For Defi:
#### For DAO:
### Risk Grading
Risk grading is the calculation of the Average Probability of DOg Default / price goes to 0:
- **AAA+**: 0.03%
- **AAA**: 0.05%
- **AA+**: 0.06%
- **AA**: 0.07%
- **A+**: 0.08%
- **A**: 0.09%
- **BBB+**: 0.10%
- **BBB**: 0.25%
- **BB+**: 0.50%
- **BB**: 1.00%
- **B+**: 2.50%
- **B**: 8.00%
- **CCC+**: 12.00%
- **CCC**: 22.00%
- **CC+**: 30.00%
- **CC**: 38.00%
- **C+**: 42.00%
- **C**: 50.00%
- **DDD+**: 58.00%
- **DDD**: 66.00%
- **DD+**: 74.00%
- **DD**: 82.00%
- **D+**: 90.00%
- **D**: 100%
### References
[Country list ratings](https://tradingeconomics.com/country-list/rating)
[Actuarial Standards Board](http://www.actuarialstandardsboard.org/wp-content/uploads/2013/12/asop046_165.pdf)
[Evaluation of Risk Management Plan](https://www.managementstudyguide.com/evaluation-of-risk-management-plan.htm)
| 49.825871 | 578 | 0.768447 | eng_Latn | 0.999008 |
fdd59de83f5f7825ea52f5565b5b9bc4a8654b18 | 267 | md | Markdown | README.md | thealgebraist/Calculator-github-actions | df0e9069f620d21280596acda571606b52213705 | [
"MIT"
] | null | null | null | README.md | thealgebraist/Calculator-github-actions | df0e9069f620d21280596acda571606b52213705 | [
"MIT"
] | null | null | null | README.md | thealgebraist/Calculator-github-actions | df0e9069f620d21280596acda571606b52213705 | [
"MIT"
] | null | null | null | # Calculator-github-actions
This repo is just the final version on how to test and deploy an iOS project using exclusively Github Actions.
Medium [story](https://medium.com/@tiagosanto/test-and-deploy-an-ios-app-using-github-actions-44de9a7dcef6) about this repo.
| 38.142857 | 124 | 0.794007 | eng_Latn | 0.909614 |
fdd5cdb685de63b7f162f2f4376af2f0b8803661 | 610 | md | Markdown | AlchemyInsights/staying-signed-in.md | isabella232/OfficeDocs-AlchemyInsights-pr.sv-SE | f65a29c0e7e545e9826e9af01b9a5d4fe8a977d6 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-05-19T19:08:09.000Z | 2021-04-21T00:13:49.000Z | AlchemyInsights/staying-signed-in.md | isabella232/OfficeDocs-AlchemyInsights-pr.sv-SE | f65a29c0e7e545e9826e9af01b9a5d4fe8a977d6 | [
"CC-BY-4.0",
"MIT"
] | 3 | 2020-06-02T23:25:58.000Z | 2022-02-09T06:54:54.000Z | AlchemyInsights/staying-signed-in.md | isabella232/OfficeDocs-AlchemyInsights-pr.sv-SE | f65a29c0e7e545e9826e9af01b9a5d4fe8a977d6 | [
"CC-BY-4.0",
"MIT"
] | 3 | 2019-10-09T20:31:36.000Z | 2021-10-09T10:38:14.000Z | ---
title: Vara inloggad
ms.author: pebaum
author: pebaum
manager: scotv
ms.date: 08/21/2020
ms.audience: Admin
ms.topic: article
ROBOTS: NOINDEX, NOFOLLOW
localization_priority: Priority
ms.collection: Adm_O365
ms.custom:
- "9003320"
- "6216"
ms.openlocfilehash: 3888ac22214a3120d37922d9a114c38ca2d1451e
ms.sourcegitcommit: 9818d3c8e6b10f23244e51286e2463caf48fffd5
ms.translationtype: MT
ms.contentlocale: sv-SE
ms.lasthandoff: 08/21/2020
ms.locfileid: "46872211"
---
# <a name="staying-signed-in"></a>Vara inloggad
Om du inte vill vara inloggad kan du välja **Visa inte detta igen** nästa gång du loggar in. | 25.416667 | 92 | 0.790164 | kor_Hang | 0.150264 |
fdd5fff7ee94a20270f8e7adc04d5d305261e010 | 226 | md | Markdown | README.md | fitronics/insight-surveys | eacd862e1c7f2bcea144434934a601c200bc9361 | [
"Apache-2.0"
] | 4 | 2019-06-04T12:50:00.000Z | 2019-06-05T07:44:12.000Z | README.md | mtrawin/insight-surveys | eacd862e1c7f2bcea144434934a601c200bc9361 | [
"Apache-2.0"
] | 1 | 2017-10-24T08:37:08.000Z | 2017-10-24T08:37:08.000Z | README.md | mtrawin/insight-surveys | eacd862e1c7f2bcea144434934a601c200bc9361 | [
"Apache-2.0"
] | 3 | 2017-10-23T09:21:15.000Z | 2017-11-06T11:18:59.000Z | # insight-surveys
Angular.js survey / form builder inspired by Google Forms
Fork of http://mwasiluk.github.io/angular-surveys
## Bower
You can install this package through `Bower` :
bower install insight-surveys --save
| 22.6 | 57 | 0.761062 | eng_Latn | 0.955057 |
fdd8db5f8fb0808141200c2b70ba495b3f750d1f | 2,434 | md | Markdown | usage/parameters/escaping-special-characters.md | jlamoree/commandbox-docs | 63196f674691f586867f1283fd8da57426ff39d0 | [
"Info-ZIP"
] | null | null | null | usage/parameters/escaping-special-characters.md | jlamoree/commandbox-docs | 63196f674691f586867f1283fd8da57426ff39d0 | [
"Info-ZIP"
] | null | null | null | usage/parameters/escaping-special-characters.md | jlamoree/commandbox-docs | 63196f674691f586867f1283fd8da57426ff39d0 | [
"Info-ZIP"
] | null | null | null | # Escaping Special Characters
If a value is a single word with no special characters, you don't need to escape anything. Certain characters are reserved as special characters though for parameters since they demarcate the beginning and end of the actual parameter and you'll need to escape them properly. These rules apply the same to named and positional parameters.
## Spaces
If a parameter has any white space in it, you'll need to wrap the value in single or double quotes. It doesn't matter which kind you use and it can vary from one parameter to another as long as they match properly.
```bash
echo 'Hello World'
echo "Good Morning Vietnam"
```
## Quotes
Quotes are actually allowed unescaped in a value like so:
```bash
echo O'reilly
```
However, if the parameter contains whitespace and is surrounded by quotes, you'll need to escape them with a backslash.
```bash
echo 'O\'reilly Auto Parts'
echo "Luis \"The Dev\" Majano"
```
> **Hint** Only like quotes need to be escaped. Single quotes can exist inside of double and vice versa without issue. These examples below are perfectly valid.
```bash
echo "O'reilly Auto Parts"
echo 'Luis "The Dev" Majano'
```
## Backticks
Backticks are used in parameter values to demarcate an expression to be parsed. Escape them with a backslash. All backticks need escaped regardless of whether they are encased on single or double quotes.
```bash
echo "Nothing to \`see\` here"
```
## Equals Signs
If you have an equals sign in your value, you'll need to escape it with a backslash unless you've quoted the entire string.
```bash
echo 2+2\=4
echo "2+2=4"
```
## Line Breaks
Line breaks can't be escaped directly as of Commandbox 4.0. Instead, most terminals let you enter a carriage return by pressing Ctrl-V and pressing enter. To enter a line feed, press Ctrl-V followed by Ctrl-J.
On ConEMU, which performs a paste operation with Ctrl-V, use Ctrl-Shift-V instead.
## Tabs
A tab character can't be escaped directly as of CommandBox 4.0. Instead, most terminals let you enter a tab char by pressing Ctrl-V followed by tab. In ConEMU which allows pasting via Ctrl-V, you can use Ctrl-Shift-V and then press tab.
## Backslash
Since the backslash is used as our escape character you'll need to escape any legitimate backslash that happens to precede a single quote, double quote, equals sign, or letter n.
```bash
echo foo\\\=bar
```
This will print `foo\=bar`
| 33.342466 | 337 | 0.754725 | eng_Latn | 0.998667 |
fdd9865991841418a35bd5c9b384c298bfc355f1 | 2,472 | md | Markdown | ru/data-transfer/operations/db-actions.md | ivanfomkin/docs | 20e9e18d7cae5ee608f59f90c4aa0e4192073ad9 | [
"CC-BY-4.0"
] | null | null | null | ru/data-transfer/operations/db-actions.md | ivanfomkin/docs | 20e9e18d7cae5ee608f59f90c4aa0e4192073ad9 | [
"CC-BY-4.0"
] | null | null | null | ru/data-transfer/operations/db-actions.md | ivanfomkin/docs | 20e9e18d7cae5ee608f59f90c4aa0e4192073ad9 | [
"CC-BY-4.0"
] | null | null | null | ---
__system: {"dislikeVariants":["Нет ответа на мой вопрос","Рекомендации не помогли","Содержание не соответствует заголовку","Другое"]}
---
# Работа с базами данных во время трансфера
В процессе работы трансфера [с репликацией данных](../concepts/index.md#transfer-type) (типы трансфера «{{ dt-repl }}» и «{{ dt-copy-repl }}») согласованность данных не гарантируется. Это означает, что данные на источнике и на приемнике могут различаться, пока работает трансфер. [После деактивации трансфера](transfer.md#deactivate-transfer) данные на приемнике будут находиться в согласованном состоянии (так называемая отложенная согласованность, eventual consistency). Учитывайте это, если ваши приложения читают из базы на приемнике во время трансфера.
## MySQL {#mysql}
Если трансфер находится в [статусе](../concepts/transfer-lifecycle.md) **Копирование**, любые изменения схемы данных (`ALTER`) на источнике или приемнике прервут трансфер.
В остальных случаях при трансфере можно изменять схему данных на источнике. Все операции `ALTER`, попавшие в бинарный лог (binlog) на источнике, автоматически применяется на приемнике. Изменения схемы данных в базе источника могут замедлить трансфер из-за того, что они могут долго применяться в базе приемника.
## PostgreSQL {#postgresql}
1. Для трансферов типа «{{ dt-copy }}» и «{{ dt-copy-repl }}» запрещено изменять базы данных, если трансфер находится в статусе **Копирование**.
1. Для трансферов типа «{{ dt-copy }}» и «{{ dt-copy-repl }}» в статусе **Репликация** не рекомендуется изменять схему данных на источнике. Если сделать это, то трансфер не сможет выполнить вставку данных на приемнике из-за особенностей реализации протокола репликации для {{ PG }}. В этом случае необходимо вручную выполнить аналогичный запрос на изменение схемы данных для приемника.
Например, пусть в таблицу `test_table` источника добавили новый столбец:
```sql
ALTER TABLE test_table ADD COLUMN val2 TEXT;
```
Если запись в эту таблицу продолжается, трансфер не сможет выполнить вставку данных на приемнике. Чтобы репликация продолжилась, выполните аналогичный запрос на изменение схемы данных на приемнике:
```sql
ALTER TABLE test_table ADD COLUMN val2 TEXT;
```
После этого трансфер сможет продолжить работу.
{% note tip %}
Избегайте изменения схемы данных в базах источника и приемника во время трансфера. Если избежать этого невозможно, проведите явные проверки на приемнике.
{% endnote %}
| 61.8 | 557 | 0.770631 | rus_Cyrl | 0.969583 |
fddbc29c25bdb3dddf0d949ad5a7d9b2893a9f75 | 1,062 | md | Markdown | planutils/packages/README.md | jdekarske/planutils | cbe16f4105a03fbd750045a7ad14b586281bc6bf | [
"MIT"
] | 35 | 2020-04-28T17:34:13.000Z | 2022-03-18T15:24:33.000Z | planutils/packages/README.md | jdekarske/planutils | cbe16f4105a03fbd750045a7ad14b586281bc6bf | [
"MIT"
] | 47 | 2020-04-28T18:35:29.000Z | 2021-12-20T18:21:23.000Z | planutils/packages/README.md | jdekarske/planutils | cbe16f4105a03fbd750045a7ad14b586281bc6bf | [
"MIT"
] | 13 | 2020-04-30T13:38:12.000Z | 2022-03-12T10:23:56.000Z | # planutils packages
Each package must contain the files `manifest.json`, `install`, and `uninstall`. Optionally, `run` can be included if the package installs a command-line executable (e.g., planners). An example of all four files can be found in the `TEMPLATE` directory, and a description of each follows. The directory name will correspond to how the package is run from the command line.
## manifest.json
Details on the package. Must include:
1. **name**: Long-form name of the package.
2. **description**: General description of the package.
3. **install-size**: Size of the package (estimated by `planutils` after you install it)
4. **dependencies**: List of shortnames for other `planutils` packages that are required.
## install
Script to install the package along with any dependencies not part of `planutils`.
## uninstall
Cleanup script to remove the package installation.
## run
(optional) Script to run the installed package. `shortname` specified in the `manifest.json` file will be used for the command-line invocation of this script.
| 42.48 | 372 | 0.76177 | eng_Latn | 0.999 |
fddc5d604386d074391a41ba3f6a8c7e6ccab0ee | 65 | md | Markdown | README.md | Klead3r/musicStream | c1255b96d2448de98c167310fb69a1d09bc7350b | [
"MIT"
] | null | null | null | README.md | Klead3r/musicStream | c1255b96d2448de98c167310fb69a1d09bc7350b | [
"MIT"
] | 1 | 2021-05-10T17:23:21.000Z | 2021-05-10T17:23:21.000Z | README.md | Klead3r/musicStream | c1255b96d2448de98c167310fb69a1d09bc7350b | [
"MIT"
] | null | null | null | # musicStream
Download from youtube and stream music with node.
| 16.25 | 49 | 0.8 | eng_Latn | 0.998921 |
fddd7270e628f4ded591059f79391352f8bd0fe1 | 3,920 | md | Markdown | material/icon/apple-finder.md | liuwave/icon-helper | 6339786f595d6f12a432db71e7aaccb693b9fe59 | [
"MIT"
] | 2 | 2020-10-26T16:32:26.000Z | 2021-01-13T09:28:45.000Z | material/icon/apple-finder.md | liuwave/icon-helper | 6339786f595d6f12a432db71e7aaccb693b9fe59 | [
"MIT"
] | 48 | 2020-04-04T12:39:59.000Z | 2022-02-27T01:30:09.000Z | material/icon/apple-finder.md | liuwave/icon-helper | 6339786f595d6f12a432db71e7aaccb693b9fe59 | [
"MIT"
] | null | null | null | ---
title: apple finder(苹果取景器) ICON转svg、png下载
name: apple-finder
zhTips: 苹果取景器
tags: ["brand-logo"]
search:
image: https://iconhelper.cn/svg/material/apple-finder.svg
---
# apple finder <small style="font-size: 60%;font-weight: 100">苹果取景器</small>
<div class="detail-page">
<p>
<span><span class="badge-success badge">免费图标</span> </span>
<br/>
<span>
ICON库：
<span class="badge-secondary badge">Material Design Icons</span>
</span>
<br/>
<span>
CSS名称：
<span class="badge-secondary badge">mdi-apple-finder</span>
</span>
<br/>
<span>
unicode：
<span class="badge-secondary badge">F0036</span>
<copy-btn content='F0036' btn-title=""></copy-btn>
<copy-btn :content='String.fromCodePoint(parseInt("F0036", 16))' btn-title="复制U"></copy-btn>
</span>
<br/>
<span>
版本：
<span class="badge-secondary badge">1.5.54</span>
</span><br/><span>标签：<span class="badge-light badge"><router-link to="/tags/brand-logo.html">商标、logo</router-link></span></span>
<br/>
<span>图标来源/作者：<span class="badge-light badge">Contributors</span></span>
<br/>
<span class="zh-detail">中文描述：<span class="badge-primary badge">苹果取景器</span><span class="help-link"><span>帮助改进</span>(<a href="https://gitee.com/liuwave/icon-helper/edit/master/json/material/apple-finder.json" target="_blank" rel="noopener noreferrer">gitee</a><a href="https://github.com/liuwave/icon-helper/edit/master/json/material/apple-finder.json" target="_blank" rel="noopener noreferrer">github</a></span>)</span><br/>
</p>
</div>
<div class="alert alert-dark">
<i class="mdi mdi-apple-finder mdi-48px"></i>
<i class="mdi mdi-apple-finder mdi-36px"></i>
<i class="mdi mdi-apple-finder mdi-24px"></i>
<i class="mdi mdi-apple-finder mdi-18px"></i>
</div>
<div>
<p>引入css文件后，可以用<code><span></code>包裹，放在页面中。具体如下所示：
</p>
<div class="alert alert-primary" style="font-size: 14px">
<span class="mdi mdi-apple-finder" aria-hidden="true"></span>
<copy-btn content='<span class="mdi mdi-apple-finder" aria-hidden="true"></span>'></copy-btn>
</div>
<div class="alert alert-secondary">
<i class="mdi mdi-apple-finder"
style="font-size: 24px"
aria-hidden="true"></i> mdi-apple-finder
<copy-btn content="mdi-apple-finder" btn-title="复制图标名称"></copy-btn>
</div>
</div>
<div id="svg" class="svg-wrap">
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M8 11C7.45 11 7 10.55 7 10V8C7 7.45 7.45 7 8 7C8.55 7 9 7.45 9 8V10C9 10.55 8.55 11 8 11M17 10V8C17 7.45 16.55 7 16 7C15.45 7 15 7.45 15 8V10C15 10.55 15.45 11 16 11C16.55 11 17 10.55 17 10M22 5V20C22 21.1 21.1 22 20 22H4C2.9 22 2 21.1 2 20V5C2 3.9 2.9 3 4 3H20C21.1 3 22 3.9 22 5M4 20L13.06 20C12.96 19.35 12.89 18.64 12.83 17.94C12.56 17.96 12.3 18 12 18C8.24 18 6.31 15.73 6.23 15.63C5.88 15.21 5.94 14.58 6.36 14.22C6.78 13.87 7.41 13.93 7.77 14.35C7.83 14.43 9.23 16 12 16C12.27 16 12.5 15.97 12.74 15.95C12.71 14.75 12.73 13.74 12.74 13.26H10.93C10.28 13.26 9.75 12.7 9.75 12C9.77 11.75 10.07 7.82 11 5H4L4 20M20 20L20 5H12.6C11.74 7.19 11.37 10.73 11.27 11.76H13.08C13.72 11.76 14.25 12.32 14.25 13C14.25 13.04 14.21 14.15 14.24 15.6C15.54 15.11 16.22 14.35 16.23 14.34C16.58 13.92 17.21 13.85 17.63 14.2C18.06 14.55 18.12 15.18 17.77 15.61C17.71 15.68 16.55 17.05 14.32 17.68C14.38 18.5 14.46 19.29 14.58 20H20Z" /></svg>
</div>
<detail full-name='mdi-apple-finder'></detail>
<div class="icon-detail__container">
<p>关于“<b>apple finder</b>”的评论:</p>
</div>
<Vssue title="关于“apple finder”的评论" />
<div><p>图标apple finder来源于Material Design Icons，可免费使用，更多关于 Material Design Icons的信息，参见：<a target="_blank" href="https://iconhelper.cn/material.html"> Material Design Icons</a>
</p></div>
<div style="padding:2rem 0 " class="page-nav"><p class="inner"><span class="prev">←<router-link to="/icon/apple-airplay.html">apple-airplay</router-link></span> <span class="next"><router-link to="/icon/apple-icloud.html">apple-icloud</router-link>→</span></p></div>
| 49.620253 | 998 | 0.68699 | yue_Hant | 0.282389 |
fdde19de925eead35bcef8011d5fc15113087b44 | 7,078 | md | Markdown | Documents/ImageDisplay.md | mwestphal/vtk-dicom | 9078df24cfeceead466a785d675b7a4afa034bba | [
"BSD-3-Clause"
] | 171 | 2015-03-15T11:16:10.000Z | 2022-03-30T01:57:09.000Z | Documents/ImageDisplay.md | mwestphal/vtk-dicom | 9078df24cfeceead466a785d675b7a4afa034bba | [
"BSD-3-Clause"
] | 181 | 2015-01-03T04:15:20.000Z | 2022-02-23T14:03:59.000Z | Documents/ImageDisplay.md | mwestphal/vtk-dicom | 9078df24cfeceead466a785d675b7a4afa034bba | [
"BSD-3-Clause"
] | 85 | 2015-01-23T17:34:21.000Z | 2022-03-30T01:57:34.000Z | ## Image Display {#imageDisplay}
@brief Correct display of pixel values.
## Overview
In general, the pixel values that are stored in a DICOM file cannot be
directly displayed to the screen. Instead, the pixel values go through
a *display pipeline* that changes the values to something suitable for
viewing. Unless the pixels are stored in the file as RGB or as 8-bit
grayscale, the display pipeline will generally do one of two things:
it will map the values through a palette to generate RGB pixels, or it
will rescale the values (sometimes in multiple steps) for monochrome display.
The vtkDICOMReader will, by default, produce the *Modality Values* of
the pixels, which are the values associated with the modality that
produced the images (e.g. Hounsfield values for CT). If desired, the
AutoRescaleOff() method can be called on the reader to force it to
produce *Stored Values* instead, which are the pixel values stored
in the file. Note that *Modality Values* are equal to *Stored Values*
for many modalities, including MRI and Ultrasound.
## Photometric Interpretation
The
[Image Pixel Module](http://dicom.nema.org/medical/dicom/current/output/chtml/part03/sect_C.7.6.3.html)
of the DICOM standard defines the Photometric Interpretation attribute
as a hint for how the stored pixel values should be interpreted by a
DICOM image display pipeline. Typical values are:
* MONOCHROME1 - negative image, where higher values are darker (e.g. radiographic film )
* MONOCHROME2 - positive image, where higher values are brighter (e.g. CT, MR)
* PALETTE COLOR - indexed color with palette
* RGB - full-color image with separate RGB components
In addition to the above, the YBR family of photometric interpretations
indicate that the image was stored with one luma channel and two color
channels, which is commonly done when a color image is compressed.
The vtkDICOMReader automatically converts YBR images to RGB, so display
pipelines should interpret YBR the same as RGB.
* YBR_FULL - used by ultrasound, usually with RLE compression
* YBR_FULL_422 - used by JPEG lossy compressed images
* YBR_PARTIAL_420 - used by MPEG lossy compressed video
* YBR_ICT - used by JPEG2000 lossy compressed images
* YBR_RCT - used by JPEG2000 lossless compressed images
Here is a short example of how to interpret the output of
vtkDICOMReader for display:
~~~~~~~~{.cpp}
reader->Update();
vtkDICOMMetaData *meta = reader->GetMetaData();
vtkDICOMValue photometric = meta->Get(DC::PhotometricInterpretation)
if (photometric.Matches("MONOCHROME1"))
{
// display with a lookup table that goes from white to black
}
else if (photometric.Matches("MONOCHROME2"))
{
// display with a lookup table that goes from black to white,
// or display with a suitable pseudocolor lookup table
}
else if (photometric.Matches("PALETTE*"))
{
// display with palette lookup table (see vtkDICOMLookupTable),
// or convert to RGB with vtkDICOMApplyPalette
}
else if (photometric.Matches("RGB*") || photometric.Matches("YBR*"))
{
// display RGB data directly
}
~~~~~~~~
## Grayscale image display
DICOM defines a grayscale display pipeline that converts the
*Stored Values* in the file to *Presentation Values* that are
suitable for display. The details of how this is done are described
in the
[Lookup Tables and Presentation
States](http://dicom.nema.org/medical/dicom/current/output/chtml/part03/sect_C.11.html)
chapter of the DICOM standard. A brief summary of the steps in the
grayscale display pipeline is as follows:
1. *Stored Values* are rescaled to generate *Modality Values*
2. *Modality Values* are windowed to generate *Windowed Values* (or *Values of Interest*)
3. *Windowed Values* are mapped to *Presentation Values*
The *Modality Values* are real values in units that are appropriate to
the modality, for example, Hounsfield units for CT or counts for PET.
The **RescaleIntercept** and **RescaleSlope** define a linear mapping
from *Stored Values* to *Modality Values*:
ModalityValue = RescaleSlope * StoredValue + RescaleIntercept
For modalities such as ultrasound and MRI that do not have any units,
the RescaleSlope and RescaleIntercept are absent and the *Modality Values*
are equal to the *Stored Values*.
The *Windowed Values* (or more generically, *Values of Interest* or
*VOIs*) represent the range of values to be displayed. Decreasing the
**WindowWidth** increases the perceived contrast of the image, and
decreasing the **WindowCenter** increases the perceived brightness of
the image. Note that, as shown in the pseudocode below, the DICOM
standard uses a definition of "window" and "level" that might be
different from that to which you are accustomed. The DICOM WindowWidth
must be greater than or equal to 1.
n = number of output gray levels (usually 256 or 1024)
w = WindowWidth - 1.0
c = WindowCenter - 0.5
if (ModalityValue <= c - 0.5*w), then WindowedValue = 0
else if (ModalityValue > c + 0.5*w), then WindowedValue = n - 1
else WindowedValue = ((ModalityValue - c)/w + 0.5) * (n - 1)
For ultrasound (and for 8-bit images in general) the WindowWidth and
WindowCenter may be absent from the file. If absent, they can be
assumed to be 256 and 128 respectively, which provides an 8-bit identity
mapping. More information can be found in the
[VOI LUT Module](http://dicom.nema.org/medical/dicom/current/output/chtml/part03/sect_C.11.2.html)
of the DICOM standard. Note that a DICOM display application should
allow the user to adjust the window according to his or her needs.
The *Presentation Values* are the values that are ultimately displayed
to the user. If the PhotometricInterpretation is MONOCHROME2, then the
*Windowed Values* should be displayed directly. If the
the PhotometricInterpetation is MONOCHROME1, then the grayscale
lookup table should be inverted such that a value of 0 is displayed as
white and the maximum value is displayed as black.
## Color image display
There are several categories of color display for DICOM, the most important
of which are:
* RGB (or YBR) values stored directly in the file
* PALETTE COLOR where a palette LUT is applied to the stored values
* A supplemental palette LUT applied to some or all stored values
* A pseudo-color palette LUT applied to the windowed values
For convenience, the vtkDICOMApplyPalette filter can convert a PALETTE
COLOR image to RGB, or can convert an image with a supplemental palette
to RGB, but will pass through all other images. For more information
about supplemental palettes, see the
[Supplemental Palette Lookup Table Module](http://dicom.nema.org/medical/dicom/current/output/chtml/part03/sect_C.7.6.19.html).
As an alternative to vtkDICOMApplyPalette, the palette lookup table can
be retrieved from a DICOM data set with the vtkDICOMLookupTable class.
The final category of color display, pseudo-color, is displayed as per
the grayscale pipeline described above, except that a pseudocolor LUT
is used in place of the black-to-white (MONOCHROME2) or
white-to-black (MONOCHROME1) LUT.
| 46.874172 | 127 | 0.773947 | eng_Latn | 0.987861 |
fdde1cd3ef0e73057171c5b0c82d8b0577dc38f6 | 4,728 | md | Markdown | docs/data/oledb/ole-db-object-model.md | sgrepos/cpp-docs | 8c2de32e96c84d0147af3cce1e89e4f28707ff12 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/data/oledb/ole-db-object-model.md | sgrepos/cpp-docs | 8c2de32e96c84d0147af3cce1e89e4f28707ff12 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/data/oledb/ole-db-object-model.md | sgrepos/cpp-docs | 8c2de32e96c84d0147af3cce1e89e4f28707ff12 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "OLE DB Object Model | Microsoft Docs"
ms.custom: ""
ms.date: "10/22/2018"
ms.technology: ["cpp-data"]
ms.topic: "reference"
dev_langs: ["C++"]
helpviewer_keywords: ["rowsets, OLE DB object model", "OLE DB, object model"]
ms.assetid: 1a274a25-c310-4430-a1ec-bd2bd8120eff
author: "mikeblome"
ms.author: "mblome"
ms.workload: ["cplusplus", "data-storage"]
---
# OLE DB Object Model
The OLE DB object model is made of the following objects or components. The first four objects or components listed (data sources, sessions, commands, and rowsets) allow you to connect to a data source and view it. The rest, starting with accessors, relate to working with the data when it's displayed.
## Data Sources
Data source objects allow you to connect to a data source such as a file or DBMS. A data source object creates and manages the connection and contains permissions and authentications information (such as login name and password). A data source object can create one or more sessions.
## Sessions
A session manages a particular interaction with the data source to query and retrieve data. Each session is a single transaction. A transaction is an indivisible work unit defined by the ACID test. For a definition of ACID, see [Transactions](#vcconoledbcomponents_transactions).
Sessions do important tasks such as opening rowsets and returning the data source object that created it. Sessions can also return metadata, or information about the data source itself (such as table information).
A session can create one or more commands.
## Commands
Commands execute a text command such as a SQL statement. If the text command specifies a rowset, such as a SQL **SELECT** statement, the command creates the rowset.
A command is simply a container for a text command, which is a string (such as a SQL statement) passed from a consumer to a data source object for execution by the provider's underlying data store. Typically, the text command is a SQL **SELECT** statement (in which case, because SQL **SELECT** specifies a rowset, the command automatically creates a rowset).
## Rowsets
Rowsets show data in tabular format. An index is a special case of a rowset. You can create rowsets from the session or the command.
### Schema Rowsets
Schemas have metadata (structural information) about a database. Schema rowsets are rowsets that have schema information. Some OLE DB providers for DBMS support schema rowset objects. For more information about schema rowsets, see [Obtaining Metadata with Schema Rowsets](../../data/oledb/obtaining-metadata-with-schema-rowsets.md) and [Schema Rowset Classes and Typedef Classes](../../data/oledb/schema-rowset-classes-and-typedef-classes.md).
### View Objects
A view object defines a subset of the rows and columns from a rowset. It has no data of its own. View objects can't combine data from multiple rowsets.
## Accessors
Only OLE DB uses the concept of accessors. An accessor describes how data is stored in a consumer. It has a set of bindings (called a column map) between rowset fields (columns) and data members that you declare in the consumer.
## <a name="vcconoledbcomponents_transactions"></a> Transactions
Transaction objects are used when committing or aborting nested transactions at other than the lowest level. A transaction is an indivisible work unit defined by the ACID test. ACID stands for:
- Atomicity, can't be divided into smaller work units
- Concurrency, more than one transaction can occur at a time
- Isolation, one transaction has limited knowledge about changes made by another
- Durability, the transaction makes persistent changes
## Enumerators
Enumerators search for available data sources and other enumerators. Consumers that aren't customized for a particular data source use enumerators to search for a data source to use.
A root enumerator, shipped in the Microsoft Data Access SDK, traverses the registry looking for data sources and other enumerators. Other enumerators traverse the registry or search in a provider-specific manner.
## Errors
Any interface on any OLE DB object can generate errors. Errors have additional information about an error, including an optional custom error object. This information is stored in an HRESULT.
## Notifications
Notifications are used by groups of cooperating consumers sharing a rowset (where sharing means that the consumers are assumed to be working within the same transaction). Notifications enable cooperating consumers sharing a rowset to be informed about actions on the rowset performed by their peers.
## See Also
[OLE DB Programming](../../data/oledb/ole-db-programming.md)<br/>
[OLE DB Programming Overview](../../data/oledb/ole-db-programming-overview.md) | 58.37037 | 443 | 0.786591 | eng_Latn | 0.996445 |
fdde432920fda9410a55394c3103f3c408f58c2c | 16,358 | md | Markdown | articles/active-directory/active-directory-saas-8x8virtualoffice-tutorial.md | OpenLocalizationTestOrg/azure-docs-pr15_fr-BE | 753623e5195c97bb016b3a1f579431af9672c200 | [
"CC-BY-3.0",
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/active-directory-saas-8x8virtualoffice-tutorial.md | OpenLocalizationTestOrg/azure-docs-pr15_fr-BE | 753623e5195c97bb016b3a1f579431af9672c200 | [
"CC-BY-3.0",
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/active-directory-saas-8x8virtualoffice-tutorial.md | OpenLocalizationTestOrg/azure-docs-pr15_fr-BE | 753623e5195c97bb016b3a1f579431af9672c200 | [
"CC-BY-3.0",
"CC-BY-4.0",
"MIT"
] | null | null | null | <properties
pageTitle="Didacticiel : Intégration d’Azure Active Directory 8 x 8 virtuel Office | Microsoft Azure"
description="Découvrez comment configurer l’authentification unique entre Azure Active Directory et 8 x 8 bureau virtuel."
services="active-directory"
documentationCenter=""
authors="jeevansd"
manager="femila"
editor=""/>
<tags
ms.service="active-directory"
ms.workload="identity"
ms.tgt_pltfrm="na"
ms.devlang="na"
ms.topic="article"
ms.date="10/10/2016"
ms.author="jeedes"/>
# <a name="tutorial-azure-active-directory-integration-with-8x8-virtual-office"></a>Didacticiel : Intégration d’Azure Active Directory avec Office virtuelle de 8 x 8
L’objectif de ce didacticiel est de vous montrer comment intégrer le bureau virtuel de 8 x 8 avec Azure Active Directory (AD Azure).
Intégration de 8 x 8 bureau virtuel avec AD Azure vous offre les avantages suivants :
- Vous pouvez contrôler dans Azure AD qui a accès au bureau virtuel de 8 x 8
- Vous pouvez autoriser les utilisateurs à automatiquement obtenir signé sur 8 x 8 Virtual Office (Single Sign-On) avec leur compte Azure AD
- Vous pouvez gérer vos comptes dans un emplacement central : le portail classique Azure
Si vous souhaitez connaître plus de détails sur l’intégration de l’application SaaS avec AD Azure, consultez [accès aux applications et single sign-on avec Azure Active Directory](active-directory-appssoaccess-whatis.md).
## <a name="prerequisites"></a>Conditions préalables
Pour configurer l’intégration de publicités Azure avec 8 x 8 Virtual Office, vous devez les éléments suivants :
- Un abonnement Azure AD
- Une 8 x 8 Virtual Office connexion unique abonnement activé
> [AZURE.NOTE] Pour tester les étapes de ce didacticiel, nous ne recommandons pas l’utilisation d’un environnement de production.
Pour tester les étapes de ce didacticiel, vous devez suivre ces recommandations :
- Vous ne devez pas utiliser votre environnement de production, sauf si cela est nécessaire.
- Si vous n’avez pas un environnement d’essai Azure AD, vous pouvez obtenir un mois d’évaluation [ici](https://azure.microsoft.com/pricing/free-trial/).
## <a name="scenario-description"></a>Description du scénario
L’objectif de ce didacticiel est pour vous permettre de tester Microsoft Azure AD Single Sign-On dans un environnement de test.
Le scénario décrit dans ce didacticiel se compose de deux blocs de construction principaux :
1. Ajout de 8 x 8 Virtual Office à partir de la galerie
2. Configuration et test de Microsoft Azure AD Single Sign-On
## <a name="adding-8x8-virtual-office-from-the-gallery"></a>Ajout de 8 x 8 Virtual Office à partir de la galerie
Pour configurer l’intégration de 8 x 8 Virtual Office dans AD Azure, vous devez ajouter 8 x 8 Virtual Office à partir de la bibliothèque à la liste des applications gérées de SaaS.
**Pour ajouter des 8 x 8 Virtual Office à partir de la galerie, procédez comme suit :**
1. Dans **Azure Portal classique**, dans le volet de navigation de gauche, cliquez sur **Active Directory**.
![Active Directory][1]
2. Dans la liste **répertoire** , sélectionnez le répertoire pour lequel vous souhaitez activer l’intégration d’annuaire.
3. Pour ouvrir la vue des applications, dans la vue du répertoire, cliquez sur **Applications** dans le menu supérieur.
![Applications][2]
4. Cliquez sur **Ajouter** au bas de la page.
![Applications][3]
5. Dans la boîte de dialogue **que voulez-vous faire** , cliquez sur **Ajouter une application à partir de la galerie**.
![Applications][4]
6. Dans la zone Rechercher, tapez **8 x 8 Virtual Office**.
7. Dans le volet de résultats, sélectionnez le **bureau virtuel de 8 x 8**et puis cliquez sur **Terminer** pour ajouter l’application.
## <a name="configuring-and-testing-microsoft-azure-ad-single-sign-on"></a>Configuration et test de Microsoft Azure AD Single Sign-On
L’objectif de cette section est de vous montrer comment configurer et tester Microsoft Azure AD Single Sign-On avec 8 x 8 Qu'office virtuel basé sur un utilisateur de test appelé « Britta Simon ».
Pour de l’authentification unique fonctionner, AD Azure doit savoir ce que l’utilisateur équivalent virtuel Office à un utilisateur dans AD Azure est de 8 x 8. En d’autres termes, une relation de liaison entre un utilisateur AD Azure et l’utilisateur connexe dans 8 x 8 bureau virtuel doit être établi.
Ce lien est établi en affectant la valeur du **nom d’utilisateur** dans AD Azure comme valeur du **nom d’utilisateur** dans un bureau virtuel de 8 x 8.
Pour configurer et tester Microsoft Azure AD Single Sign-On avec 8 x 8 Virtual Office, vous devez effectuer les blocs de construction suivantes :
1. **[Configuration Microsoft Azure AD Single Sign-On](#configuring-azure-ad-single-single-sign-on)** - pour autoriser les utilisateurs à utiliser cette fonctionnalité.
2. **[Création d’une annonce Azure tester l’utilisateur](#creating-an-azure-ad-test-user)** - pour tester Microsoft Azure AD Single Sign-On avec Britta Simon.
3. **[Création d’un utilisateur de test de bureau virtuel 8 x 8](#creating-a-8x8-virtual-office-test-user)** - avoir un équivalent de Britta Simon bureau virtuel 8 x 8 qui est lié à la représentation sous forme de publicité Azure de sa.
4. **[Tester l’utilisateur affectant la publicité Azure](#assigning-the-azure-ad-test-user)** - pour activer Britta Simon à utiliser Microsoft Azure AD Single Sign-On.
5. **[Test de l’authentification unique](#testing-single-sign-on)** - pour vérifier si la configuration fonctionne.
### <a name="configuring-microsoft-azure-ad-single-sign-on"></a>Configuration Microsoft Azure AD unique Single Sign-On
Dans cette section, vous activez Microsoft Azure AD Single Sign-On dans le portail classique et configurez l’authentification unique dans votre application de bureau virtuel 8 x 8.
**Pour configurer Microsoft Azure AD Single Sign-On avec 8 x 8 Virtual Office, effectuez les opérations suivantes :**
1. Dans le portail classique, sur la page intégration d’application **Office du virtuel 8 x 8** , cliquez **sur Configurer l’authentification unique** pour ouvrir la boîte de dialogue **Configuration de l’authentification unique** .
![Configurer l’authentification unique][6]
2. Dans la page **Comment voulez-vous aux utilisateurs de se connecter à un bureau virtuel de 8 x 8** , sélectionnez **Microsoft Azure AD Single Sign-On**, puis cliquez sur **suivant**.
3. Sur la page de la boîte de dialogue **Configurer les paramètres d’application** , effectuez les opérations suivantes, puis cliquez sur **suivant**:
une barre d’outils. Dans la zone de texte **URL de réponse** , tapez :`https://sso.8x8.com/saml2`
b. Cliquez sur **suivant**
4. Dans la page **configurer l’authentification unique au bureau virtuel de 8 x 8** , effectuez les opérations suivantes, puis cliquez sur **suivant**:
une barre d’outils. Cliquez sur **Télécharger le certificat**et puis enregistrez le fichier sur votre ordinateur.
b. Cliquez sur **suivant**.
5. Ouverture de session sur vos clients de bureau virtuel 8 x 8 en tant qu’administrateur.
6. Sélectionnez **Gestionnaire de compte de bureau virtuel** sur le panneau de l’Application.
7. Sélectionnez compte **d’entreprise** à gérer et cliquez sur le bouton de **Connexion** .
8. Cliquez sur onglet **comptes** de la liste du menu.
9. Cliquez sur **Single Sign On** dans la liste des comptes.
10. Sélectionnez **Session monocristallines** sous méthode d’authentification et cliquez sur **SAML**.
11. Copiez **SAML SSO URL**, **unique à l’aide des URL de Service** et **émetteur** de publicité Azure à **signer dans l’URL**, **Déconnectez-vous d’URL** et **les URL de l’émetteur** dans le bureau virtuel de 8 x 8.
12. Cliquez sur le bouton **navigateur** pour télécharger le certificat que vous avez téléchargé à partir d’AD Azure.
13. Cliquez sur le bouton **Enregistrer** .
14. Dans le portail classique, sélectionnez la confirmation de la configuration d’ouverture de session unique, puis cliquez sur **suivant**.
![Azure AD unique Single Sign-On][10]
15. Sur la page de **confirmation d’ouverture de session unique** , cliquez sur **Terminer**.
![Azure AD unique Single Sign-On][11]
### <a name="creating-an-azure-ad-test-user"></a>Création d’un utilisateur de test AD Azure
L’objectif de cette section est de créer un utilisateur test dans le portail classique appelé Britta Simon.
![Créer utilisateur d’AD Azure][20]
**Pour créer un utilisateur test dans Azure AD, effectuez les opérations suivantes :**
1. Dans **Azure Portal classique**, dans le volet de navigation de gauche, cliquez sur **Active Directory**.
2. Dans la liste **répertoire** , sélectionnez le répertoire pour lequel vous souhaitez activer l’intégration d’annuaire.
3. Pour afficher la liste des utilisateurs, dans le menu de la partie supérieure, cliquez sur **utilisateurs**.
4. Pour ouvrir la boîte de dialogue **Ajouter un utilisateur** , dans la barre d’outils dans la partie inférieure, cliquez sur **Ajouter un utilisateur**.
5. Sur la page de dialogue **nous dire sur cet utilisateur** , effectuez les opérations suivantes :
une barre d’outils. En tant que Type d’utilisateur, sélectionnez nouvel utilisateur de votre organisation.
b. Dans la **zone de texte**nom d’utilisateur, tapez **BrittaSimon**.
c. Cliquez sur **suivant**.
6. Sur la page de la boîte de dialogue **Profil d’utilisateur** , effectuez les opérations suivantes :
une barre d’outils. Dans la zone de texte **nom** , tapez **Brian**.
b. Dans la zone de texte **Nom** , type, **Simon**.
c. Dans la zone de texte **Nom complet** , tapez **Brian Simon**.
d. Dans la liste **rôle** , sélectionnez **utilisateur**.
e. Cliquez sur **suivant**.
7. Sur la page de boîte de dialogue **obtenir le mot de passe temporaire** , cliquez sur **créer**.
8. Sur la page de boîte de dialogue **obtenir le mot de passe temporaire** , effectuez les opérations suivantes :
une barre d’outils. Notez que la valeur de **Nouveau mot de passe**.
b. Cliquez sur **terminé**.
### <a name="creating-a-8x8-virtual-office-test-user"></a>Création d’un utilisateur de test de bureau virtuel 8 x 8
L’objectif de cette section est de créer un utilisateur appelé Britta Simon bureau virtuel de 8 x 8. 8 x 8 virtuel Office prend en charge le provisionnement juste-à-temps, qui est par défaut activée.
Il n’y a aucun élément d’action pour vous dans cette section. Un nouvel utilisateur est créé lors d’une tentative d’accéder à 8 x 8 Virtual Office s’il n’existe pas encore.
> [AZURE.NOTE] Si vous avez besoin créer un utilisateur manuellement, vous devez contacter l’équipe de prise en charge du bureau virtuel 8 x 8.
### <a name="assigning-the-azure-ad-test-user"></a>Affectation de l’utilisateur de test AD Azure
L’objectif de cette section est l’activation Britta Simon à utiliser Azure SSO en accordant l’accès au bureau virtuel de 8 x 8.
![Affecter des utilisateurs][200]
**Pour affecter des Britta Simon à 8 x 8 Virtual Office, effectuez les opérations suivantes :**
1. Sur le portail classique, pour ouvrir la vue des applications, dans la vue du répertoire, cliquez sur **Applications** dans le menu supérieur.
![Affecter des utilisateurs][201]
2. Dans la liste des applications, sélectionnez **bureau virtuel de 8 x 8**.
3. Dans le menu du haut, cliquez sur **utilisateurs**.
![Affecter des utilisateurs][203]
4. Dans la liste utilisateurs, sélectionnez **Brian Simon**.
5. Dans la barre d’outils dans la partie inférieure, cliquez sur **attribuer**.
![Affecter des utilisateurs][205]
### <a name="testing-single-sign-on"></a>Test de l’authentification unique
L’objectif de cette section est pour tester votre configuration de l’ouverture de session unique Microsoft Azure AD à l’aide du panneau d’accès.
Lorsque vous cliquez sur la mosaïque du bureau virtuel de 8 x 8 dans le panneau d’accès, vous devez obtenir automatiquement signé-sur à votre application de bureau virtuel 8 x 8.
## <a name="additional-resources"></a>Ressources supplémentaires
* [Liste des didacticiels sur la façon d’intégrer les applications SaaS avec Azure Active Directory](active-directory-saas-tutorial-list.md)
* [Quel est l’accès de l’application et de l’authentification unique avec Azure Active Directory ?](active-directory-appssoaccess-whatis.md)
<!--Image references-->
[1]: ./media/active-directory-saas-8x8virtualoffice-tutorial/tutorial_general_01.png
[2]: ./media/active-directory-saas-8x8virtualoffice-tutorial/tutorial_general_02.png
[3]: ./media/active-directory-saas-8x8virtualoffice-tutorial/tutorial_general_03.png
[4]: ./media/active-directory-saas-8x8virtualoffice-tutorial/tutorial_general_04.png
[6]: ./media/active-directory-saas-8x8virtualoffice-tutorial/tutorial_general_05.png
[10]: ./media/active-directory-saas-8x8virtualoffice-tutorial/tutorial_general_06.png
[11]: ./media/active-directory-saas-8x8virtualoffice-tutorial/tutorial_general_07.png
[20]: ./media/active-directory-saas-8x8virtualoffice-tutorial/tutorial_general_100.png
[200]: ./media/active-directory-saas-8x8virtualoffice-tutorial/tutorial_general_200.png
[201]: ./media/active-directory-saas-8x8virtualoffice-tutorial/tutorial_general_201.png
[203]: ./media/active-directory-saas-8x8virtualoffice-tutorial/tutorial_general_203.png
[204]: ./media/active-directory-saas-8x8virtualoffice-tutorial/tutorial_general_204.png
[205]: ./media/active-directory-saas-8x8virtualoffice-tutorial/tutorial_general_205.png
| 54.165563 | 302 | 0.765558 | fra_Latn | 0.942452 |
fdde625cd64aecf29312519eb88e849280d1a0af | 9,967 | md | Markdown | mdop/appv-v5/migrating-from-a-previous-version-app-v-50.md | MicrosoftDocs/mdop-docs-pr.de-de | 2c2dc8dbac77a389cbaa09dc05c11d2f24ecd31c | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-04-20T21:13:51.000Z | 2021-04-20T21:13:51.000Z | mdop/appv-v5/migrating-from-a-previous-version-app-v-50.md | MicrosoftDocs/mdop-docs-pr.de-de | 2c2dc8dbac77a389cbaa09dc05c11d2f24ecd31c | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-07-08T05:12:12.000Z | 2020-07-08T15:38:40.000Z | mdop/appv-v5/migrating-from-a-previous-version-app-v-50.md | MicrosoftDocs/mdop-docs-pr.de-de | 2c2dc8dbac77a389cbaa09dc05c11d2f24ecd31c | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-11-04T12:31:43.000Z | 2021-11-04T12:31:43.000Z | ---
title: Migrieren von einer früheren Version
description: Migrieren von einer früheren Version
author: dansimp
ms.assetid: a13cd353-b22a-48f7-af1e-5d54ede2a7e5
ms.reviewer: ''
manager: dansimp
ms.author: dansimp
ms.pagetype: mdop, appcompat, virtualization
ms.mktglfcycl: deploy
ms.sitesec: library
ms.prod: w10
ms.date: 08/30/2016
ms.openlocfilehash: a05bbd498cdb77a1ddf694b1aab6aeb42124775b
ms.sourcegitcommit: 354664bc527d93f80687cd2eba70d1eea024c7c3
ms.translationtype: MT
ms.contentlocale: de-DE
ms.lasthandoff: 06/26/2020
ms.locfileid: "10805066"
---
# Migrieren von einer früheren Version
Mit App-v 5,0 können Sie Ihre vorhandene App-v 4,6-Infrastruktur auf die flexiblere, integrierte und einfacher zu verwaltende App-v 5,0-Infrastruktur migrieren.
Wenn Sie Ihre Migrationsstrategie planen, sollten Sie die folgenden Abschnitte in Frage stellen:
**Hinweis** Weitere Informationen zu den Unterschieden zwischen App-v 4,6 und App-v 5,0 finden Sie unter **Unterschiede zwischen App-v 4,6 und App-v 5,0 im Abschnitt** [über APP-v 5,0](about-app-v-50.md).
## Konvertieren von Paketen, die mit einer früheren Version von App-V erstellt wurden
Verwenden Sie das Paket Konverter-Dienstprogramm, um virtuelle Anwendungspakete zu aktualisieren, die mit früheren Versionen von App-V erstellt wurden. Der Paket Konverter verwendet PowerShell zum Konvertieren von Paketen und kann die Automatisierung des Prozesses unterstützen, wenn viele Pakete vorhanden sind, für die eine Konvertierung erforderlich ist.
**Wichtig** Nachdem Sie ein vorhandenes Paket konvertiert haben, sollten Sie das Paket vor der Bereitstellung des Pakets testen, um sicherzustellen, dass der Konvertierungsvorgang erfolgreich war.
**Was Sie wissen müssen, bevor Sie vorhandene Pakete konvertieren**
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Problem</th>
<th align="left">Problemumgehung</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Paket Skripts werden nicht konvertiert.</p></td>
<td align="left"><p>Testen Sie das konvertierte Paket. Falls erforderlich, konvertieren Sie das Skript.</p></td>
</tr>
<tr class="even">
<td align="left"><p>Überschreibungen für die Paket Registrierungseinstellung werden nicht konvertiert.</p></td>
<td align="left"><p>Testen Sie das konvertierte Paket. Fügen Sie bei Bedarf Registrierungs Überschreibungen erneut hinzu.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Virtuelle Pakete, die DSC verwenden, werden nach der Konvertierung nicht verknüpft.</p></td>
<td align="left"><p>Verknüpfen Sie die Pakete mithilfe von Verbindungsgruppen. Siehe <a href="managing-connection-groups.md" data-raw-source="[Managing Connection Groups](managing-connection-groups.md)"> Verwalten von Verbindungsgruppen </a> .</p></td>
</tr>
<tr class="even">
<td align="left"><p>Während der Konvertierung werden Umgebungsvariablen Konflikte erkannt.</p></td>
<td align="left"><p>Beheben Sie alle Konflikte in der zugehörigen <strong> OSD- </strong> Datei.</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Während der Konvertierung werden hart codierte Pfade erkannt.</p></td>
<td align="left"><p>Hart codierte Pfade sind schwierig, richtig zu konvertieren. Der Paket Konverter erkennt Pakete mit Dateien, die hart codierte Pfade enthalten, und gibt diese zurück. Zeigen Sie die Datei mit dem hartcodierten Pfad an, und ermitteln Sie, ob das Paket die Datei erfordert. Wenn dies der Fall ist, empfiehlt es sich, das Paket neu zu sequenzieren.</p></td>
</tr>
</tbody>
</table>
Beim Konvertieren einer Paketprüfung auf fehlerhafte Dateien oder Verknüpfungen. Suchen Sie das Element in App-V 4,6-Paket. Möglicherweise ist es ein hartcodierter Pfad. Konvertieren Sie den Pfad.
**Hinweis** Es wird empfohlen, den App-V 5,0-Sequenzer zum Konvertieren kritischer Anwendungen oder Anwendungen zu verwenden, die Features nutzen müssen. Lesen Sie, [wie Sie eine neue Anwendung mit App-V 5,0 Sequenzieren](how-to-sequence-a-new-application-with-app-v-50-beta-gb18030.md).
Wenn ein konvertiertes Paket nicht geöffnet wird, nachdem Sie es konvertiert haben, empfiehlt es sich auch, die Anwendung mithilfe des App-V 5,0-Sequencers neu zu sequenzieren.
[So konvertieren Sie ein Paket, das in einer früheren Version von App-V erstellt wurde](how-to-convert-a-package-created-in-a-previous-version-of-app-v.md)
## Migrieren von Clients
In der folgenden Tabelle wird die empfohlene Methode zum Aktualisieren von Clients angezeigt.
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Aufgabe</th>
<th align="left">Weitere Informationen</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Aktualisieren Ihrer Umgebung auf App-v 4.6 SP2</p></td>
<td align="left"><p><a href="../appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy.md" data-raw-source="[Application Virtualization Deployment and Upgrade Considerations](../appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy.md)">Überlegungen zur Implementierung und zum Upgrade von Application Virtualization </a></p></td>
</tr>
<tr class="even">
<td align="left"><p>Installieren Sie den App-V 5,0-Client mit aktivierter Koexistenz.</p></td>
<td align="left"><p><a href="how-to-deploy-the-app-v-46-and-the-app-v--50-client-on-the-same-computer.md" data-raw-source="[How to Deploy the App-V 4.6 and the App-V 5.0 Client on the Same Computer](how-to-deploy-the-app-v-46-and-the-app-v--50-client-on-the-same-computer.md)">Bereitstellen der APP-v 4,6 und des App-v 5,0-Clients auf </a> demselben Computer</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Sequenzieren und Rollout von App-V 5,0-Paketen. Bei Bedarf können Sie die Veröffentlichung von App-V 4,6-Paketen aufheben.</p></td>
<td align="left"><p><a href="how-to-sequence-a-new-application-with-app-v-50-beta-gb18030.md" data-raw-source="[How to Sequence a New Application with App-V 5.0](how-to-sequence-a-new-application-with-app-v-50-beta-gb18030.md)">So wird es gemacht: Sequenzierung einer neuen Anwendung mit APP- </a> V 5,0</p></td>
</tr>
</tbody>
</table>
**Wichtig** Sie müssen App-v 4.6 SP3 ausführen, um den Koexistenzmodus verwenden zu können. Wenn Sie ein Paket sequenzieren, müssen Sie außerdem die Einstellung für die Verwaltungsautorität konfigurieren, die sich in der **Benutzerkonfiguration** befindet, die sich im Abschnitt **Benutzerkonfiguration** befindet.
## Migrieren der vollständigen Infrastruktur des App-V 5,0-Servers
Es gibt keine direkte Methode zum Upgrade auf eine vollständige App-V 5,0-Infrastruktur. Verwenden Sie die Informationen im folgenden Abschnitt, um Informationen zum Upgrade des App-V-Servers zu erhalten.
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Aufgabe</th>
<th align="left">Weitere Informationen</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Aktualisieren Sie Ihre Umgebung auf App-v 4.6 SP3.</p></td>
<td align="left"><p><a href="../appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy.md" data-raw-source="[Application Virtualization Deployment and Upgrade Considerations](../appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy.md)">Überlegungen zur Implementierung und zum Upgrade von Application Virtualization </a></p></td>
</tr>
<tr class="even">
<td align="left"><p>Bereitstellen der App-V 5,0-Version des Clients</p></td>
<td align="left"><p><a href="how-to-deploy-the-app-v-client-gb18030.md" data-raw-source="[How to Deploy the App-V Client](how-to-deploy-the-app-v-client-gb18030.md)">Bereitstellen des App-V </a> -Clients</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Installieren Sie den App-V 5,0-Server.</p></td>
<td align="left"><p><a href="how-to-deploy-the-app-v-50-server-50sp3.md" data-raw-source="[How to Deploy the App-V 5.0 Server](how-to-deploy-the-app-v-50-server-50sp3.md)">Bereitstellen des App-V 5,0 </a> -Servers</p></td>
</tr>
<tr class="even">
<td align="left"><p>Migrieren vorhandener Pakete</p></td>
<td align="left"><p>Weitere Informationen finden Sie unter <strong> Konvertieren von Paketen, die mit einer früheren Version von App-V </strong> in diesem Artikel erstellt wurden.</p></td>
</tr>
</tbody>
</table>
## Zusätzliche Migrationsaufgaben
Sie können auch zusätzliche Migrationsaufgaben wie die Neukonfiguration von Endpunkten und das Öffnen eines Pakets ausführen, das mit einer früheren Version auf einem Computer mit dem App-V 5,0-Client erstellt wurde. Die folgenden Links enthalten weitere Informationen zum Ausführen dieser Aufgaben.
[So migrieren Sie Erweiterungspunkte von einem App-V 4.6-Paket zu einem konvertierten App-V 5.0-Paket für alle Benutzer eines bestimmten Computers](how-to-migrate-extension-points-from-an-app-v-46-package-to-a-converted-app-v-50-package-for-all-users-on-a-specific-computer.md)
[So migrieren Sie Erweiterungspunkte von einem App-V 4.6-Paket zu App-V 5.0 für einen bestimmten Benutzer](how-to-migrate-extension-points-from-an-app-v-46-package-to-app-v-50-for-a-specific-user.md)
[So setzen Sie Erweiterungspunkte von einem App-V 5.0-Paket auf ein App-V 4.6-Paket für alle Benutzer eines bestimmten Computers zurück](how-to-revert-extension-points-from-an-app-v-50-package-to-an-app-v-46-package-for-all-users-on-a-specific-computer.md)
[So setzen Sie Erweiterungspunkte von einem App-V 5.0-Paket auf ein App-V 4.6-Paket für einen bestimmten Benutzer zurück](how-to-revert-extension-points-from-an-app-v-50-package-to-an-app-v-46-package-for-a-specific-user.md)
## Weitere Ressourcen für die Ausführung von App-V-Migrationsaufgaben
[Vorgänge für App-V 5.0](operations-for-app-v-50.md)
[Ein vereinfachtes Upgrade-Verfahren für Microsoft App-V 5,1-Verwaltungs Server](https://go.microsoft.com/fwlink/p/?LinkId=786330)
| 49.835 | 377 | 0.761212 | deu_Latn | 0.959504 |
fdde7149dccc739d792d8a8f628308ab248d1a52 | 2,055 | md | Markdown | doc/REFACTORING_DISCUSSION__cl349_dvt5_mmb70_mg367_asq3_pkp9.md | DuyTrieu1999/VoogaSalad_TinyPicnicFrogs | ff5aec61f5305c871bdf06eea73bd3d6e1f15f73 | [
"MIT"
] | null | null | null | doc/REFACTORING_DISCUSSION__cl349_dvt5_mmb70_mg367_asq3_pkp9.md | DuyTrieu1999/VoogaSalad_TinyPicnicFrogs | ff5aec61f5305c871bdf06eea73bd3d6e1f15f73 | [
"MIT"
] | null | null | null | doc/REFACTORING_DISCUSSION__cl349_dvt5_mmb70_mg367_asq3_pkp9.md | DuyTrieu1999/VoogaSalad_TinyPicnicFrogs | ff5aec61f5305c871bdf06eea73bd3d6e1f15f73 | [
"MIT"
] | null | null | null | Refactoring Discussion
===
## Authors
Allen Qiu (asq3)
Max Bartlett (mmb70)
Michael Glushakov (mg367)
## Refactoring Decisions
### TopMenu.java
- Paddings and insets were converted to well-named constants to avoid magic numbers
- We moved the file menu subitems closer to the place where they are actually used
- Removed useless/wildcard imports
### MessageForm.java
- Window sizes were converted to well-named constants to avoid magic numbers
- Removed useless imports
- Made public classes that didn't need to be public either package-private or private
### Grid.java
- Magic numbers for window sizes were converted to well-named constants
- Removed useless imports
- Returned List objects instead of ArrayList since we didn't require specific ArrayList implementations
### ActorManager.java
- Combined two catch statements into one
- Set pane widths and heights to well-named constants to avoid magic numbers
- Removed useless imports
- Returned List objects instead of ArrayList since we didn't require specific ArrayList implementations
### AuthoringView.java
- Commented out empty methods that have not been implemented yet
- Replaced magic numbers with well-named constants for grid size defaults
- Removed useless imports
### MapMenu.java
- Replaced paddings and other magic numbers with well-named constants
- Removed unused variables
- Made public classes that didn't need to be public either package-private or private
### PopupFactory.java
- Made constants final variables
- Made public classes that didn't need to be public either package-private or private
- Changed public variables to private if needed
### PrototypeForm.java
- Made constants final variables
- Made public classes that didn't need to be public either package-private or private
- Changed public variables to private if needed
### Actor.java
- Fixed code smell relating to reusing variables
### SceneManager.java
- Fixed e.printStacktrace() by using cusom exceptions
- Launch an alert with exception message
### SaveForm.java
- Made constants private and final | 34.25 | 103 | 0.794161 | eng_Latn | 0.995149 |
fdde8a7c733a2a12d1e3dec724becb7da1a4cb9d | 2,384 | md | Markdown | handbook/communication/team_chat.md | saylynt/about | c0e9ef74502ec4ce969b0f25007218661c2121f6 | [
"MIT"
] | 1 | 2019-12-20T05:56:14.000Z | 2019-12-20T05:56:14.000Z | handbook/communication/team_chat.md | saylynt/about | c0e9ef74502ec4ce969b0f25007218661c2121f6 | [
"MIT"
] | null | null | null | handbook/communication/team_chat.md | saylynt/about | c0e9ef74502ec4ce969b0f25007218661c2121f6 | [
"MIT"
] | null | null | null | # Team chat
We use [Slack for team chat](index.md#slack). We have many Slack channels. You don't have to join them all, but here is a good breakdown of the most active ones by category.
If you are a new member of the engineering team, you'll most likely want to join all of the channels in the engineering section below.
## General
- #general - Anything about Sourcegraph in general (that doesn't fit a more specific channel below).
- #random - Cool things you're doing in life, cat photos, jokes, vacation photos, etc.
- #progress - Share cool/interesting progress with the team
- #thanks - Appreciate someone's work? You can thank them here! :) {#thanks}
- #handbook - Updates to and discussion of [this handbook](../index.md)
## Product
- #design - How Sourcegraph looks visually
- #feedback - Feedback directly from our users & customers
- #product - Product questions, ideas and thoughts
- #metrics - User metrics, analytics, etc.
## Business
- #marketing - [Marketing](../marketing/index.md)
- #sales - [Sales](../sales/index.md)
- #marketintel - Market and industry intelligence - products, funding, competition
- #payments - Customer payment notifications
- #hiring-active - Candidate hiring
- #customer-updates - Updates on the status of customers
- #dev-rel - Developer relations, events, blog posts, tweets, etc.
## Engineering
### Engineering teams
- #a8n - All things automation.
- #code-intel - All things code intelligence.
- #core-services - Repository management, authentication, stability -- you name it.
- #distribution - Everything from how Sourcegraph is packaged and delivered to customers, to ensuring it works well for them).
- #web - The webapp and browser extension, search UI/UX.
### Engineering general
All engineers should join the following channels (feel free to adjust your notification preferences for each as you see fit, though):
- #dev-announce - Things that affect a majority of the dev team in some way (e.g. site or buildkite is down, we will have expected downtime, etc.). *You should read every message in here, and messages you post to it should have a high signal-noise ratio.*
- #dev-chat - anything related to Sourcegraph development :)
- #dev-ops - discussing incidents and any other ops-related work
- #buildkite - see notifications about Buildkite / CI failures.
- #opsgenie - where pager notifications get sent to Slack
| 46.745098 | 255 | 0.748322 | eng_Latn | 0.994595 |
fdde91fb58cc644bfc864f025ef6a4cab73a345c | 506 | md | Markdown | Readme.md | sharo-jef/fencejumper | bf2a7b01e28d16f82e4a5ed9e5c3804e1f310574 | [
"MIT"
] | null | null | null | Readme.md | sharo-jef/fencejumper | bf2a7b01e28d16f82e4a5ed9e5c3804e1f310574 | [
"MIT"
] | null | null | null | Readme.md | sharo-jef/fencejumper | bf2a7b01e28d16f82e4a5ed9e5c3804e1f310574 | [
"MIT"
] | null | null | null | # Fence Jumper
This is the **unofficial** version for MCJE 1.16.4.
## Overview
A simple utility mod that allows jumping over fences and walls without the need for pesky carpet, trap doors, or jump boost.
This only applies to players, your farms are safe!
Permissions: You are allowed to use this on servers/in mod packs, no permissions necessary.
## Details
- Minecraft 1.16.4
- Forge 1.16.4-35.1.7
## Usage
1. Install Minecraft Forge for 1.16.4.
2. Drop `fencejumper-x.x.jar` into `mods` folder.
| 23 | 124 | 0.735178 | eng_Latn | 0.990074 |
fdde964d42452ed9721853129a7824fd2db45a32 | 1,584 | md | Markdown | README.md | yy-ininin/ininin-validator | 755d2397e0eba73a85a53823d01cb9f52216708a | [
"MIT"
] | null | null | null | README.md | yy-ininin/ininin-validator | 755d2397e0eba73a85a53823d01cb9f52216708a | [
"MIT"
] | null | null | null | README.md | yy-ininin/ininin-validator | 755d2397e0eba73a85a53823d01cb9f52216708a | [
"MIT"
] | null | null | null | # ininin-validator
表单验证工具类，包含整数验证、小数验证、电话号码验证
# install
npm i ininin-validator
# github
https://github.com/yy-ininin/ininin-validator
# usage
```javascript
import validator from "ininin-validator";
/**
* 验证整数
* @param {Object} opts 参数
* @param {Number|String} opts.value 字段值
* @param {Number|String} opts.minimum 最小值，默认-999999999
* @param {Number|String} opts.maximum 最大值，默认999999999
* @param {String} [opts.field] 字段名
* @param {Boolean} [opts.required] 是否必填，默认false
* @param {Boolean} [opts.thanEqual] 是否为开区间（大于等于/小于等于），默认true
* @returns {String} 验证信息
*/
const validMsg = validator.validInteger({
value: 0,
field: "年龄",
minimum: 1
});
console.log(validMsg);
// 年龄必须大于等于 1
/**
* 验证小数
* @param {Object} opts 参数
* @param {Number|String} opts.value 字段值
* @param {Number|String} opts.minimum 最小值，默认-999999999
* @param {Number|String} opts.maximum 最大值，默认999999999
* @param {String} [opts.field] 字段名
* @param {Number} [opts.decimals] 小数位，默认2
* @param {Boolean} [opts.required] 是否必填，默认false
* @param {Boolean} [opts.thanEqual] 是否为开区间（大于等于/小于等于），默认true
* @returns {String} 验证信息
*/
const validMsg = validator.validDecimal({ value: 0.455, field: "金额" });
console.log(validMsg);
// 金额仅支持两位小数
/**
* 验证电话号码
* @param {Object} opts 参数
* @param {Number|String} opts.value 字段值
* @param {String} [opts.field] 字段名
* @param {Number} [opts.mode] 模式，默认0，0：手机和座机，1：手机，2：座机
* @param {Boolean} [opts.required] 是否必填，默认false
* @returns {String} 验证信息
*/
const validMsg = validator.validPhone({ value: "1281234567", field: "手机号" });
console.log(validMsg);
// 手机号格式有误
| 24 | 77 | 0.691288 | yue_Hant | 0.087726 |
fddf3e988fc2d4dd6c6ac514f201cc04b6a804ea | 158 | md | Markdown | CHANGELOG.md | wz1000/unboxed | e4c6ca80fb8946b1abfe595ba1c36587a33931db | [
"BSD-2-Clause"
] | 24 | 2021-02-19T11:05:32.000Z | 2021-02-24T23:27:27.000Z | CHANGELOG.md | wz1000/unboxed | e4c6ca80fb8946b1abfe595ba1c36587a33931db | [
"BSD-2-Clause"
] | 2 | 2021-04-25T15:39:49.000Z | 2021-04-26T12:06:08.000Z | CHANGELOG.md | wz1000/unboxed | e4c6ca80fb8946b1abfe595ba1c36587a33931db | [
"BSD-2-Clause"
] | 3 | 2021-04-08T17:49:41.000Z | 2021-05-18T10:07:29.000Z | 0.2 [yyyy.mm.dd] unreleased
-----------------
* Edward Kmett replaced it with a completely different library.
0.1
---
* Carter Schonwald released a library.
| 19.75 | 63 | 0.664557 | eng_Latn | 0.989106 |
fddf77b1bd424269b1c93c66bde49b04e4a394c6 | 446 | md | Markdown | english/strange-room/room.md | bllarkin/create-your-own-adventure | 6fc97fa00c3c9d4a1f5f8b4533146cf13e01acc9 | [
"CC-BY-3.0"
] | 652 | 2015-01-02T02:12:21.000Z | 2022-03-29T18:40:26.000Z | english/strange-room/room.md | bllarkin/create-your-own-adventure | 6fc97fa00c3c9d4a1f5f8b4533146cf13e01acc9 | [
"CC-BY-3.0"
] | 6,903 | 2015-01-01T00:09:52.000Z | 2022-01-11T05:36:44.000Z | english/strange-room/room.md | bllarkin/create-your-own-adventure | 6fc97fa00c3c9d4a1f5f8b4533146cf13e01acc9 | [
"CC-BY-3.0"
] | 15,776 | 2015-01-01T02:59:42.000Z | 2022-03-27T21:26:09.000Z | Upon entering, you see a sparsely furnished room with just a table, with a lit candle, and two chairs.
It's obvious someone has been here recently but who?
You don't feel scared in the room for now, so you decide to look around for a
few minutes. You look under the table, and find a card with a random phone
number written on it.
Do you:
[Call the random number?](../call-a-random-number/answer.md)
[Leave the room?](../find-exit/leave.md)
| 31.857143 | 102 | 0.744395 | eng_Latn | 0.999842 |
fddf9f24b34104a7ca403e5345157a8c47f5167c | 163 | md | Markdown | CHANGELOG.md | L3K0V/parse-server-firebase | e59c95de09952b4c396df646d3106cf638371d3f | [
"MIT"
] | 5 | 2020-11-14T09:11:04.000Z | 2022-03-23T16:39:23.000Z | CHANGELOG.md | nopol10/parse-server-firebase | 319a6136566dff065d596776efab9911c62b6c89 | [
"MIT"
] | null | null | null | CHANGELOG.md | nopol10/parse-server-firebase | 319a6136566dff065d596776efab9911c62b6c89 | [
"MIT"
] | 1 | 2020-12-08T08:39:53.000Z | 2020-12-08T08:39:53.000Z | ## 1.1.0 - 2020-04-14
### Added
- Support for generation of image thumbnails
## 1.0.0 - 2020-04-12
### Added
- `FirebaseAuthAdapter`
- `FirebaseStorageAdapter`
| 14.818182 | 44 | 0.674847 | eng_Latn | 0.390358 |
fde08a195d809d59ccae1f0486e880c9eeff799d | 6,990 | md | Markdown | CHANGELOG.md | acoburn/solid-client-js | ccab172fb687fbe411d8154ad7810c4b255a1cdb | [
"MIT"
] | null | null | null | CHANGELOG.md | acoburn/solid-client-js | ccab172fb687fbe411d8154ad7810c4b255a1cdb | [
"MIT"
] | null | null | null | CHANGELOG.md | acoburn/solid-client-js | ccab172fb687fbe411d8154ad7810c4b255a1cdb | [
"MIT"
] | null | null | null | # Changelog
This project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
The following changes have been implemented but not released yet:
## [Unreleased]
The following sections document changes that have been released already:
## [1.0.0] - 2020-11-04
The big v1! There are no major changes in this release, but from now on, when we intend to change
our publicly-documented non-experimental API's, we will bump up the major version to help you plan
the impact of the upgrade.
### Deprecations
- solid-client will no longer attempt to automatically load solid-auth-client, because it comes with
security risks. It is recommended to use
[solid-client-authn-browser](https://www.npmjs.com/package/@inrupt/solid-client-authn-browser)
instead. It will remain possible to pass a `fetch` function generated by solid-auth-client to the
data fetching functions in solid-client.
## [0.6.4] - 2020-11-03
### Bugs fixed
- The compiled code of solid-client was not sent to the correct location, causing imports to fail.
This bug was introduced in version 0.6.2.
## [0.6.3] - 2020-11-03
This release contains no public changes.
## [0.6.2] - 2020-10-30
### Bugs fixed
- When writing non-RDF data, the request headers were incorrectly set.
## [0.6.1] - 2020-10-15
### Bugs fixed
- All `get*WithAcl()` functions would always fetch _both_ the Resource's own ACL and its fallback
ACL, causing issues when the Resource is the Pod's root, but not at the root of the domain,
resulting in an attempt to find a fallback ACL for a Resource outside of the Pod. These functions
will now only attempt to fetch the Fallback ACL if the Resource's own ACL is not available. Hence,
only at most one of the two will be available at any time.
## [0.6.0] - 2020-10-14
### New features
- `deleteSolidDataset` and `deleteContainer`: two functions that allow you to delete a SolidDataset
and a Container from the user's Pod, respectively.
- `hasServerResourceInfo`: a function that determines whether server-provided information about the
Resource is present, such as which server-managed Resources are linked to it.
- `getPodOwner` and `isPodOwner` allow you to check who owns the Pod that contains a given Resource,
if supported by the Pod server and exposed to the current user.
## [0.5.1] - 2020-10-13
### Bugs fixed
- The type definition of `asUrl` caused the compiler to complain when passing it a Thing of which
the final URL was either known or not known yet, when using TypeScript.
## [0.5.0] - 2020-09-24
### Breaking changes
- All previously deprecated functions have been removed (their replacements are still available).
- Previously, if no data with the given URL could be found, `getThing` would return a new, empty
Thing. From now on, it will return `null` in those situations.
### Bugs fixed
- `createAclFromFallbackAcl` did not correctly initialise the new ACL: rules that applied to the
applicable Resource's children _before_ the new ACL was created (i.e. defined in the fallback ACL)
no longer applied after saving the new one. This is now fixed.
## [0.4.0] - 2020-09-15
### Deprecations
- The experimental function `fetchResourceInfoWithAcl` has been deprecated. It is replaced by the
otherwise identical (but still experimental) `getResourceInfoWithAcl`.
### New features
- `getResourceInfo`: Function fetching metadata for a resource, without fetching the resource itself. This enables
having lightwheight interaction with a Pod before fetching a large file.
- When fetching data from or storing data to a Pod results in an error, those error messages now
contain more information about what data was being sent, and where it was sent to.
### Bugs fixed
- When creating a new Container on Node Solid Server using `createContainerAt`, no error would be
thrown when the Container already exists. Now, as with other Solid servers, an error will be
thrown if the Container you are trying to create already exists.
- The second, optional parameter to functions like `getSolidDataset`, which allows you to pass e.g.
your own `fetch` function, was not included in our type definitions. This prevented editors from
autocompleting them, and could cause compilation errors for developers using TypeScript.
## [0.3.0] - 2020-09-03
### New features
- `thingAsMarkdown()`, `solidDatasetAsMarkdown()` and `changeLogAsMarkdown`: functions that take a
Thing and SolidDataset (with local changes), respectively, and returns a string representation of
it that can assist in debugging issues.
## [0.2.0] - 2020-08-27
### New features
- `hasResourceInfo`: a function that can verify whether its parameter (e.g. a file or a
SolidDataset) was fetched from somewhere, or was initialised in-memory.
- `createContainerAt` and `createContainerInContainer`: two functions that can help you create an
empty Container at a given location or in another Container on the Pod, respectively.
- `isThing`: a function that can verify whether its parameter is a Thing.
- `mockSolidDatasetFrom`, `mockContainerFrom`, `mockFileFrom`, `mockThingFrom`,
`addMockResourceAclTo` and `addMockFallbackAclTo`: functions that allow you to mock the
solid-client data structures in your unit tests.
- `getFileWithAcl`: like `getSolidDatasetWithAcl`, this function lets you fetch a file along with
its ACLs, if available.
- The legacy predicate `acl:defaultForNew` is now supported by our library. If you interact with a
server where it is used to stipulate default access, `@inrupt/solid-client` will behave as expected.
### Bugs fixed
- `getSourceUrl` used to throw an error when called on a Resource that was not fetched from
somewhere (and hence had no source URL). It now returns `null` in that case.
- Giving more rights to an Agent or Group could lead to privilege escalation for an app identified
by an `acl:origin` predicate in the ACL.
- While we allow reading data of different types, they are stored as plain strings. While multiple
serialisations of data are often possible, we only supported one per data type. What this means
is that, whereas we would correctly return `true` for a boolean stored as `"1"`, we would not do
so for `"true"`, even though both are valid serialisations of the value `true` according to the
XML Schema Datatypes specification: https://www.w3.org/TR/xmlschema-2. solid-client now recognises
all valid serialisations of all supported data types as defined by that specification.
## [0.1.0] - 2020-08-06
### New features
First release! What's possible with this first release:
- Fetch data from Solid Pods or other public sources that publish Turtle data.
- Store data back to Solid Pods.
- Read data from datasets.
- Manipulate data in datasets.
- Inspect a user's, group's and public permissions w.r.t. a given Resource or child Resources of a
Container. (Experimental.)
- Retrieve, delete and/or write any file (including non-RDF) from/to a Pod. (Experimental.)
| 44.240506 | 114 | 0.7598 | eng_Latn | 0.998711 |
fde0d75a540d86acbe7c20792f03c697eef9ce91 | 632 | md | Markdown | docs/v1/DashboardTemplateVariables.md | ConnectionMaster/datadog-api-client-ruby | dd9451bb7508c1c1211556c995a04215322ffada | [
"Apache-2.0"
] | null | null | null | docs/v1/DashboardTemplateVariables.md | ConnectionMaster/datadog-api-client-ruby | dd9451bb7508c1c1211556c995a04215322ffada | [
"Apache-2.0"
] | 1 | 2021-01-27T05:06:34.000Z | 2021-01-27T05:12:09.000Z | docs/v1/DashboardTemplateVariables.md | ConnectionMaster/datadog-api-client-ruby | dd9451bb7508c1c1211556c995a04215322ffada | [
"Apache-2.0"
] | null | null | null | # DatadogAPIClient::V1::DashboardTemplateVariables
## Properties
| Name | Type | Description | Notes |
| ---- | ---- | ----------- | ----- |
| **default** | **String** | The default value for the template variable on dashboard load. | [optional] |
| **name** | **String** | The name of the variable. | |
| **prefix** | **String** | The tag prefix associated with the variable. Only tags with this prefix appear in the variable drop-down. | [optional] |
## Example
```ruby
require 'datadog_api_client/v1'
instance = DatadogAPIClient::V1::DashboardTemplateVariables.new(
default: my-host,
name: host1,
prefix: host
)
```
| 27.478261 | 148 | 0.651899 | eng_Latn | 0.694772 |
fde1cb5a1a27fc24c69c14968a6d71bf0379b53c | 4,692 | md | Markdown | _posts/2020-10-23-javascript-se-consolida-como-a-linguagem-de-programacao-mais-popular.md | terminalnet/terminalnet.github.io | a2687d41b8ab9eaa4e5d74b6a35882f64dadc9c2 | [
"MIT"
] | null | null | null | _posts/2020-10-23-javascript-se-consolida-como-a-linguagem-de-programacao-mais-popular.md | terminalnet/terminalnet.github.io | a2687d41b8ab9eaa4e5d74b6a35882f64dadc9c2 | [
"MIT"
] | 3 | 2020-08-08T18:18:58.000Z | 2021-12-04T16:08:01.000Z | _posts/2020-10-23-javascript-se-consolida-como-a-linguagem-de-programacao-mais-popular.md | terminalnet/terminalnet.github.io | a2687d41b8ab9eaa4e5d74b6a35882f64dadc9c2 | [
"MIT"
] | null | null | null | ---
layout: post
title: "JavaScript se consolida como a linguagem de programação mais popular"
categories: [ News ]
image: 'assets/img/js-prog.jpg'
---
> Segundo pesquisa da SlashData Python está em segundo lugar, seguido de perto por Java na terceira posição
Segundo uma pesquisa da empresa de análise de mercado SlashData, a linguagem de programação mais popular na atualidade é JavaScript, que incluindo variantes como CoffeeScript e TypeScript é usada por 12,4 milhões de desenvolvedores em todo o mundo.
<!-- QUADRADO -->
<script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>
<ins class="adsbygoogle"
style="display:inline-block;width:336px;height:280px"
data-ad-client="ca-pub-2838251107855362"
data-ad-slot="5351066970"></ins>
<script>
(adsbygoogle = window.adsbygoogle || []).push({});
</script>
A afirmação é baseada na 19ª edição da pesquisa ["State of the Developer Nation"](https://www.slashdata.co/free-resources/developer-economics-state-of-the-developer-nation-19th-edition), referente ao terceiro trimestre de 2020. Ela inclui respostas de mais de 17 mil desenvolvedores em 159 países, e além da popularidade de linguagens de programação também mede a atitude de desenvolvedores em relação a software Open Source, adoção de práticas de DevOps e uso de tecnologias como contêineres e Kubernetes.
<!-- MINI ANÚNCIO -->
<script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>
<!-- Games Root -->
<ins class="adsbygoogle"
style="display:inline-block;width:730px;height:95px"
data-ad-client="ca-pub-2838251107855362"
data-ad-slot="5351066970"></ins>
<script>
(adsbygoogle = window.adsbygoogle || []).push({});
</script>
De acordo com o estudo, mais de cinco milhões de desenvolvedores se juntaram à comunidade JavaScript desde 2017. "Mesmo em setores onde JavaScript é menos popular, como em ciência de dados e realidade aumentada e virtual, mais de um quinto dos desenvolvedores a usa em seus projetos", diz a SlashData.
<!-- RETANGULO LARGO 2 -->
<script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>
<ins class="adsbygoogle"
style="display:block; text-align:center;"
data-ad-layout="in-article"
data-ad-format="fluid"
data-ad-client="ca-pub-2838251107855362"
data-ad-slot="8549252987"></ins>
<script>
(adsbygoogle = window.adsbygoogle || []).push({});
</script>
A segunda linguagem mais popular no ranking é Python, cujo número de usuários é estimado em 9 milhões, e que neste ano ultrapassou Java, que agora esta na terceira posição com 8,2 milhões de usuários.
Outras linguagens como C, C++, PHP e C# são usadas por entre 6 e 6,3 milhões de desenvolvedores. Atrás delas vem Kotlin, do Google, e Swift, da Apple, tem entre 2,3 e 2,8 milhões de usuários. Go, Ruby, Objective C, Rust e Lua tem entre 800 mil e 1,5 milhão de usuários.
<!-- RETANGULO LARGO -->
<script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>
<!-- Informat -->
<ins class="adsbygoogle"
style="display:block"
data-ad-client="ca-pub-2838251107855362"
data-ad-slot="2327980059"
data-ad-format="auto"
data-full-width-responsive="true"></ins>
<script>
(adsbygoogle = window.adsbygoogle || []).push({});
</script>
# Números relativos
Vale lembrar que estes números não são uma verdade absoluta, e a popularidade de uma linguagem varia de acordo com a metodologia da pesquisa, número de desenvolvedores entrevistados, sua área de atuação, etc.
Por exemplo, em junho deste ano o ranking da Redmonk mostrava que Python era mais popular que Java, enquanto em outubro a Tiobe mostrava Java à frente, porém em tendência de queda, com Python quase "encostado" e apresentando uma tendência de crescimento.
Ainda assim, para quem pretende seguir uma carreira como desenvolvedor de software, tanto JavaScript quanto Python parecem ser uma aposta "segura" com um amplo mercado de trabalho. A Microsoft tem em seu canal no YouTube cursos de Python e JavaScript, que visam auxiliar quem já tem algum conhecimento em programaçao a dar seus primeiros passos nestas linguagens.
<!-- QUADRADO -->
<script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>
<ins class="adsbygoogle"
style="display:inline-block;width:336px;height:280px"
data-ad-client="ca-pub-2838251107855362"
data-ad-slot="5351066970"></ins>
<script>
(adsbygoogle = window.adsbygoogle || []).push({});
</script>
Via: [ZDNet](https://www.zdnet.com/google-amp/article/microsoft-vs-code-update-gets-new-features-with-programming-language-typescript-4-0/) por [Olhar Digital](https://olhardigital.com.br/noticia/javascript-se-consolida-como-a-linguagem-de-programacao-mais-popular/109142)
| 55.2 | 506 | 0.769821 | por_Latn | 0.992776 |
fde32e8a4324c0ba25d8a1de172d73190466868f | 593 | md | Markdown | scripts/README.md | nhsuk/frontend-library | 20558ce53d218910fae1abf81d46c11f018a008b | [
"MIT"
] | 9 | 2017-08-05T17:55:25.000Z | 2019-01-23T10:02:06.000Z | scripts/README.md | nhsuk/frontend-library | 20558ce53d218910fae1abf81d46c11f018a008b | [
"MIT"
] | 24 | 2017-06-21T14:24:37.000Z | 2019-06-14T13:30:08.000Z | scripts/README.md | nhsuk/frontend-library | 20558ce53d218910fae1abf81d46c11f018a008b | [
"MIT"
] | 8 | 2017-07-01T15:38:31.000Z | 2021-04-11T07:38:16.000Z | # Scripts
See [https://github.com/github/scripts-to-rule-them-all](https://github.com/github/scripts-to-rule-them-all)
for additional background on these scripts.
Below is a list of the scripts available, along with a short description of
the script does. If interested in the details of the script, they are
able to be read.
[`pre-bootstrap`](pre-bootstrap)
Links to a repo containing the base development machine setup.
[`bootstrap`](bootstrap)
Installs the project's direct dependencies e.g. npm packages.
[`start`](start)
Starts the application on port [3333](http://localhost:3333).
| 32.944444 | 108 | 0.768971 | eng_Latn | 0.957755 |
fde48041c29d36ccf33f30f4d9a9feebf63f5b23 | 236 | md | Markdown | _cop/dep/nsubjpass.md | mjabrams/docs | eef96df1ce8f6752e9f80660c8255482b2a07c45 | [
"Apache-2.0"
] | null | null | null | _cop/dep/nsubjpass.md | mjabrams/docs | eef96df1ce8f6752e9f80660c8255482b2a07c45 | [
"Apache-2.0"
] | null | null | null | _cop/dep/nsubjpass.md | mjabrams/docs | eef96df1ce8f6752e9f80660c8255482b2a07c45 | [
"Apache-2.0"
] | null | null | null | ---
layout: relation
title: 'nsubjpass'
shortdef: 'passive nominal subject'
udver: '2'
---
The relation `nsubjpass` is not used in Coptic. For both transitive stative subjects and third person plural pseudo-passivization, use `nsubj`.
| 26.222222 | 143 | 0.758475 | eng_Latn | 0.991981 |
fde6e2b2a2d1dc2308d7a53c8dff1366024d7c29 | 118 | md | Markdown | README.md | surfaceowl/colab_pytorch_tensorboard | eb4fadae9ab9b8cae00178f67ee77e77943de169 | [
"MIT"
] | null | null | null | README.md | surfaceowl/colab_pytorch_tensorboard | eb4fadae9ab9b8cae00178f67ee77e77943de169 | [
"MIT"
] | null | null | null | README.md | surfaceowl/colab_pytorch_tensorboard | eb4fadae9ab9b8cae00178f67ee77e77943de169 | [
"MIT"
] | null | null | null | # colab_pytorch_tensorboard
quick repo to demonstrate use of tensorboard with pytorch, using Google Colab environment
| 39.333333 | 89 | 0.855932 | eng_Latn | 0.958562 |
fde768c5de2b142c7f1b612e667dd9c2a6aa6506 | 49 | md | Markdown | README.md | YanisCharkiolakis/nvd3-charts | 4a25ad033476af492a95a4ca9a28fbfac209d364 | [
"Apache-2.0"
] | null | null | null | README.md | YanisCharkiolakis/nvd3-charts | 4a25ad033476af492a95a4ca9a28fbfac209d364 | [
"Apache-2.0"
] | null | null | null | README.md | YanisCharkiolakis/nvd3-charts | 4a25ad033476af492a95a4ca9a28fbfac209d364 | [
"Apache-2.0"
] | null | null | null | # nvd3-charts
Vaadin wrapper for nvd3.js library
| 16.333333 | 34 | 0.795918 | eng_Latn | 0.653184 |
fde7fd678d624acc3ca091c36ffdfffe8e99c44c | 3,838 | md | Markdown | _utilities/clearfix.md | huyenltnguyen/uswds-site | c0f7418324c85e49413e7ddd071336f44a00b583 | [
"CC0-1.0"
] | 102 | 2018-01-28T04:59:38.000Z | 2022-03-13T18:18:37.000Z | _utilities/clearfix.md | huyenltnguyen/uswds-site | c0f7418324c85e49413e7ddd071336f44a00b583 | [
"CC0-1.0"
] | 553 | 2018-01-23T18:05:13.000Z | 2022-03-30T19:59:24.000Z | _utilities/clearfix.md | huyenltnguyen/uswds-site | c0f7418324c85e49413e7ddd071336f44a00b583 | [
"CC0-1.0"
] | 92 | 2018-01-24T13:24:05.000Z | 2022-03-23T15:27:56.000Z | ---
permalink: /utilities/clearfix/
layout: styleguide
type: utility
title: Clearfix
category: Utilities
lead: Clear any floated elements
subnav:
- text: Utility mixins
href: '#utility-mixins'
- text: Advanced settings
href: '#advanced-settings'
utilities:
- base: clearfix
var: clearfix
output: true
responsive: false
active: false
focus: false
hover: false
visited: false
---
<section class="utilities-section">
{% include utilities/utilities-section-title-bar.html %}
<section class="utility" id="utility-clearfix">
{% include utilities/utility-title-bar.html
title="Clearfix"
property=false
%}
<section class="utility-examples">
<div class="clearfix border-1px">
<span class="float-left bg-secondary-light padding-2">.float-left</span>
<span class="float-right bg-secondary-light padding-2">.float-right</span>
</div>
<div class="usa-accordion usa-accordion--bordered site-accordion-code margin-top-4">
<button class="usa-accordion__button" aria-controls="code-clearfix" aria-expanded="true">Code</button>
<div id="code-clearfix" class="usa-accordion__content margin-bottom-1">
<div markdown="1">
{% highlight html linenos %}
<div class="clearfix">
<span class="float-left">.float-left</span>
<span class="float-right">.float-right</span>
</div>
{% endhighlight %}
</div>
</div>
</div>
</section><!-- .utility-examples -->
</section><!-- .utility#clearfix -->
</section><!-- .utilities -->
<section class="utilities-section margin-top-6">
<h2 class="utilities-section-title">Default output</h2>
<table class="usa-table--borderless site-table-responsive site-table-simple">
<thead>
<tr>
<th scope="col" class="tablet:maxw-card-lg display-inline-flex">Utility</th>
<th scope="col" class="display-inline-flex">Output</th>
</tr>
</thead>
<tbody class="font-mono-2xs">
<tr>
<th scope="row" data-title="Utility" class="tablet:text-no-wrap tablet:maxw-card-lg display-inline-flex">
<span class="text-normal">
.clearfix
</span>
</th>
<td data-title="Output">
<span>
::after { clear: both; content: ""; display: block; }
</span>
</td>
</tr>
</tbody>
</table>
</section>
<section id="utility-mixins" class="padding-top-4">
<h2 class="site-h2 margin-y-0">Utility mixins</h2>
{% include utilities/utility-mixin-intro.html %}
<table class="usa-table--borderless site-table-responsive site-table-simple">
<thead>
<tr>
<th scope="col" class="tablet:maxw-card-lg display-inline-flex">Utility</th>
<th scope="col" class="display-inline-flex">Mixin</th>
<th scope="col" class="display-inline-flex">Example</th>
</tr>
</thead>
<tbody class="font-mono-2xs">
<tr>
<th scope="row" data-title="Utility" class="tablet:text-no-wrap tablet:maxw-card-lg display-inline-flex">
<span class="text-normal">
.cleafix
</span>
</th>
<td data-title="Mixin" class="display-inline-flex">
<span>
clearfix
</span>
</td>
<td data-title="Example" class="display-inline-flex">
<span>
@include clearfix
</span>
</td>
</tr>
</tbody>
</table>
{% include utilities/utility-mixin-using.html %}
</section>
<section id="advanced-settings" class="padding-top-4">
<h2 class="site-h2 margin-y-0">Advanced settings</h2>
{% include utilities/responsive-variants.html %}
{% include utilities/state-variants.html %}
{% include utilities/output-control.html %}
{% include utilities/values-no-custom-values.html %}
</section>
| 29.984375 | 113 | 0.615425 | eng_Latn | 0.477184 |
fde862e05df2d598722d9489b8928fa36040ff47 | 20 | md | Markdown | README.md | jb38/boost-data-logger | c9132b0878129e4635df2afe42f4df44570492b1 | [
"MIT"
] | null | null | null | README.md | jb38/boost-data-logger | c9132b0878129e4635df2afe42f4df44570492b1 | [
"MIT"
] | null | null | null | README.md | jb38/boost-data-logger | c9132b0878129e4635df2afe42f4df44570492b1 | [
"MIT"
] | null | null | null | # boost-data-logger
| 10 | 19 | 0.75 | swe_Latn | 0.341732 |
fde957b226ceb717c67687995deb644f4ebb945f | 295 | md | Markdown | _posts/1939-12-16-carnegie-institute's-marine-biological-laboratory.md | MiamiMaritime/miamimaritime.github.io | d087ae8c104ca00d78813b5a974c154dfd9f3630 | [
"MIT"
] | null | null | null | _posts/1939-12-16-carnegie-institute's-marine-biological-laboratory.md | MiamiMaritime/miamimaritime.github.io | d087ae8c104ca00d78813b5a974c154dfd9f3630 | [
"MIT"
] | null | null | null | _posts/1939-12-16-carnegie-institute's-marine-biological-laboratory.md | MiamiMaritime/miamimaritime.github.io | d087ae8c104ca00d78813b5a974c154dfd9f3630 | [
"MIT"
] | null | null | null | ---
title: Carnegie Institute's Marine Biological Laboratory
tags:
- Dec 1939
---
Carnegie Institute's Marine Biological Laboratory at Dry Tortugas will close after 30 years of service.
Newspapers: **Miami Morning News or The Miami Herald**
Page: **2**, Section: **A**
| 24.583333 | 105 | 0.684746 | eng_Latn | 0.631815 |
fde95d9800d16caf9330b61a76d540bc97a191d0 | 2,938 | md | Markdown | formal-verification-classification/SMT/SMT.md | golovach-ivan/Correct-by-Construction | cb1b5329248036bcf30a0f0b1b59b72c96ce59be | [
"Apache-2.0"
] | null | null | null | formal-verification-classification/SMT/SMT.md | golovach-ivan/Correct-by-Construction | cb1b5329248036bcf30a0f0b1b59b72c96ce59be | [
"Apache-2.0"
] | null | null | null | formal-verification-classification/SMT/SMT.md | golovach-ivan/Correct-by-Construction | cb1b5329248036bcf30a0f0b1b59b72c96ce59be | [
"Apache-2.0"
] | null | null | null | ## Satisfiability Modulo Theories (SMT)
> Satisfiability Modulo Theories (SMT) is an area of automated deduction that studies methods for checking the satisfiability of first-order formulas with respect to some logical theory T of interest [BSST09]. What distinguishes SMT from general automated deduction is that the background theory T need not be finitely or even first-order axiomatizable, and that specialized inference methods are used for each theory. By being theory-specific and restricting their language to certain classes of formulas (such as, typically but not exclusively, quantifier-free formulas), these specialized methods can be implemented in solvers that are more efficient in practice than general-purpose theorem provers.
> While SMT techniques have been traditionally used to support deductive software verification, they have found applications in other areas of computer science such as, for instance, planning, model checking and automated test generation. Typical theories of interest in these applications include **formalizations of various forms of arithmetic, arrays, finite sets, bit vectors, algebraic datatypes, strings, floating point numbers, equality with uninterpreted functions, and various combinations of these**.
> The defining problem of Satisfiability Modulo Theories is checking whether a given (closed) logical formula ϕ is satisfiable, not in general but in the context of some background theory T which constrains the interpretation of the symbols used in ϕ. Technically, the SMT problem for ϕ and T is the question of whether there is a model of T that makes ϕ true.
### SMT solvers
> SMT solver is any software system that implements a procedure for satisfiability modulo some given theory. In general, one can distinguish among a solver’s
> 1. **underlying logic**, e.g., first-order, modal, temporal, second-order, and so on,
> 2. **background theory**, the theory against which satisfiability is checked,
> 3. **input formulas**, the class of formulas the solver accepts as input, and
> 4. **interface**, the set of functionalities provided by the solver.
> For instance, in a solver for linear arithmetic the underlying logic is first-order logic with equality, the background theory is the theory of real numbers, and the input language may be limited to conjunctions of inequations between linear polynomials. The interface may be as simple as accepting a system of inequations and returning a binary response indicating whether the system is satisfiable or not. More sophisticated interfaces include the ability to return concrete solutions for satisfiable inputs, return proofs for unsatisfiable ones, allow incremental and backtrackable input, and so on.
#### SMT solver competition (SMT-COMP)
### Links
- Barrett, Sebastiani, Seshia, Tinelli, 2009, "Satisfiability Modulo Theories"
- Barrett, de Moura, Stump, 2005, "SMT-COMP: Satisfiability Modulo Theories Competition"
| 127.73913 | 703 | 0.804969 | eng_Latn | 0.99861 |
fdea6ed7aeeb6ee72f2158ed2f4840849d0ddd0f | 4,270 | md | Markdown | publications.md | desGeorgesLab/desGeorgesLab.github.io | 52d0ac249453799c24e11ad99cb9821283de5784 | [
"MIT"
] | 1 | 2019-12-31T19:50:49.000Z | 2019-12-31T19:50:49.000Z | publications.md | desGeorgesLab/desGeorgesLab.github.io | 52d0ac249453799c24e11ad99cb9821283de5784 | [
"MIT"
] | null | null | null | publications.md | desGeorgesLab/desGeorgesLab.github.io | 52d0ac249453799c24e11ad99cb9821283de5784 | [
"MIT"
] | 1 | 2018-05-12T01:41:09.000Z | 2018-05-12T01:41:09.000Z | ---
layout: page
title: Publications
---
<div class="row">
<div class="col-md-5" markdown="1">
<br>
</div>
<div class="col-md-7" markdown="1">
A. Dashti, D.B. Hail, G. Mashayekhi, P. Schwander, A. des Georges, J. Frank, A. Ourmazd (co-corresponding author) (2018) Functional Pathways of Biomolecules Retrieved from Single-particle Snapshots. bioRxiv: 291922 (pre-print)
</div>
</div>
<div class="row">
<div class="col-md-5" markdown="1">
<br>
</div>
<div class="col-md-7" markdown="1">
Montemiglio, L. C., Testi, C., Ceci, P., Falvo, E., Pitea, M., Savino, C., Arcovito, A., Peruzzi, G., Baiocco, P., Mancia, F., Boffi, A., des Georges, A., … Vallone, B. (2019). Cryo-EM structure of the human ferritin-transferrin receptor 1 complex. Nature communications, 10(1), 1121. doi:10.1038/s41467-019-09098-w
</div>
</div>
<div class="row">
<div class="col-md-5" markdown="1">
<br>
</div>
<div class="col-md-7" markdown="1">
Chase, J., Catalano, A., Noble, A. J., Eng, E. T., Olinares, P. D., Molloy, K., Pakotiprapha, D., Samuels, M., Chait, B., des Georges, A., … Jeruzalmi, D. (2018). Mechanisms of opening and closing of the bacterial replicative helicase. eLife, 7, e41140. doi:10.7554/eLife.41140
</div>
</div>
<div class="row">
<div class="col-md-5" markdown="1">
<br>
</div>
<div class="col-md-7" markdown="1">
Iketani, S., Shean, R. C., Ferren, M., Makhsous, N., Aquino, D. B., des Georges, A., Rima, B., Mathieu, C., Porotto, M., Moscona, A., … Greninger, A. L. (2018). Viral Entry Properties Required for Fitness in Humans Are Lost through Rapid Genomic Change during Viral Isolation. mBio, 9(4), e00898-18. doi:10.1128/mBio.00898-18
</div>
</div>
<div class="row">
<div class="col-md-5" markdown="1">
<br>
</div>
<div class="col-md-7" markdown="1">
Noble, A. J., Dandey, V. P., Wei, H., Brasch, J., Chase, J., Acharya, P., Tan, Y. Z., Zhang, Z., Kim, L. Y., Scapin, G., Rapp, M., Eng, E. T., Rice, W. J., Cheng, A., Negro, C. J., Shapiro, L., Kwong, P. D., Jeruzalmi, D., des Georges, A., Potter, C. S., … Carragher, B. (2018). Routine single particle CryoEM sample and grid characterization by tomography. eLife, 7, e34257. doi:10.7554/eLife.34257
</div>
</div>
<div class="row">
<div class="col-md-5" markdown="1">
<br>
</div>
<div class="col-md-7" markdown="1">
Calisti, L., Trabuco, M. C., Boffi, A., Testi, C., Montemiglio, L. C., des Georges, A., Benni, I., Ilari, A., Taciak, B., Białasek, M., Rygiel, T., Król, M., Baiocco, P., … Bonamore, A. (2018). Engineered ferritin for lanthanide binding. PloS one, 13(8), e0201859. doi:10.1371/journal.pone.0201859
</div>
</div>
<div class="row">
<div class="col-md-5" markdown="1">
<br>
</div>
<div class="col-md-7" markdown="1">
Santulli, G., Lewis, D., des Georges, A., Marks, A. R., & Frank, J. (2018). Ryanodine Receptor Structure and Function in Health and Disease. Sub-cellular biochemistry, 87, 329-352
</div>
</div>
<div class="row">
<div class="col-md-5" markdown="1">
<br>
</div>
<div class="col-md-7" markdown="1">
des Georges, A., Clarke, O. B., Zalk, R., Yuan, Q., Condon, K. J., Grassucci, R. A., Hendrickson, W. A., Marks, A. R., … Frank, J. (2016). Structural Basis for Gating and Activation of RyR1. Cell, 167(1), 145-157.e17
</div>
</div>
<div class="row">
<div class="col-md-5" markdown="1">
<br>
</div>
<div class="col-md-7" markdown="1">
des Georges, A., Dhote, V., Kuhn, L., Hellen, C. U., Pestova, T. V., Frank, J., & Hashem, Y. (2015). Structure of mammalian eIF3 in the context of the 43S preinitiation complex. Nature, 525(7570), 491-5
</div>
</div>
<div class="row">
<div class="col-md-5" markdown="1">
<br>
</div>
<div class="col-md-7" markdown="1">
Zalk, R., Clarke, O. B., des Georges, A., Grassucci, R. A., Reiken, S., Mancia, F., Hendrickson, W. A., Frank, J., … Marks, A. R. (2014). Structure of a mammalian ryanodine receptor. Nature, 517(7532), 44-9
</div>
</div>
| 44.479167 | 403 | 0.627166 | eng_Latn | 0.112739 |
fdeb2c639f496331410ad5c19dac882ea3ac74d4 | 14,533 | md | Markdown | en/application-dev/reference/apis/js-apis-particleAbility.md | acidburn0zzz/openharmony | f19488de6f7635f3171b1ad19a25e4844c0a24df | [
"CC-BY-4.0"
] | null | null | null | en/application-dev/reference/apis/js-apis-particleAbility.md | acidburn0zzz/openharmony | f19488de6f7635f3171b1ad19a25e4844c0a24df | [
"CC-BY-4.0"
] | null | null | null | en/application-dev/reference/apis/js-apis-particleAbility.md | acidburn0zzz/openharmony | f19488de6f7635f3171b1ad19a25e4844c0a24df | [
"CC-BY-4.0"
] | null | null | null | # ParticleAbility Module
## Constraints
The ParticleAbility module is used to perform operations on abilities of the Data and Service types.
## Modules to Import
```js
import particleAbility from '@ohos.ability.particleAbility'
```
## particleAbility.startAbility
startAbility(parameter: StartAbilityParameter, callback: AsyncCallback\<void>: void
Starts a Service ability. This method uses a callback to return the result.
**Parameters**
| Name| Type| Mandatory| Description|
| --------- | ----------------------------------------------- | ---- | ----------------- |
| parameter | [StartAbilityParameter](#startabilityparameter) | Yes| Ability to start.|
| callback | AsyncCallback\<void> | Yes| Callback used to return the result.|
**Example**
```js
import particleAbility from '@ohos.ability.particleAbility'
particleAbility.startAbility(
{
want:
{
action: "action.system.home",
entities: ["entity.system.home"],
type: "MIMETYPE",
flags: FLAG_AUTH_READ_URI_PERMISSION;
deviceId: "",
bundleName: "com.example.Data",
abilityName: "com.example.Data.MainAbility",
uri:""
},
},
(error, result) => {
console.log('particleAbility startAbility errCode:' + error + 'result:' + result)
},
)
```
## particleAbility.startAbility
startAbility(parameter: StartAbilityParameter): Promise\<number>
Starts a Service ability. This method uses a promise to return the result.
**Parameters**
| Name| Type| Mandatory| Description|
| --------- | ----------------------------------------------- | ---- | ----------------- |
| parameter | [StartAbilityParameter](#startabilityparameter) | Yes| Ability to start.|
**Return value**
| Type| Description|
| -------------- | ------------------------- |
| Promise\<void> | Promise used to return the result.|
**Example**
```js
import particleAbility from '@ohos.ability.particleAbility'
particleAbility.startAbility(
{
want:
{
action: "action.system.home",
entities: ["entity.system.home"],
type: "MIMETYPE",
flags: FLAG_AUTH_READ_URI_PERMISSION;
deviceId: "",
bundleName: "com.example.Data",
abilityName: "com.example.Data.MainAbility",
uri:""
},
},
).then((void) => {
console.info("particleAbility startAbility");
});
```
## particleAbility.terminateSelf
terminateSelf(callback: AsyncCallback\<void>): void
Terminates this Service ability. This method uses a callback to return the result.
**Parameters**
| Name| Type| Mandatory| Description|
| -------- | -------------------- | ---- | -------------------- |
| callback | AsyncCallback\<void> | Yes| Callback used to return the result.|
**Example**
```js
import particleAbility from '@ohos.ability.particleAbility'
particleAbility.terminateSelf(
(error, result) => {
console.log('particleAbility terminateSelf errCode:' + error + 'result:' + result)
}
)
```
## particleAbility.terminateSelf
terminateSelf(): Promise\<void>
Terminates this Service ability. This method uses a promise to return the result.
**Return value**
| Type| Description|
| -------------- | ------------------------- |
| Promise\<void> | Promise used to return the result.|
**Example**
```js
import particleAbility from '@ohos.ability.particleAbility'
particleAbility.terminateSelf().then((void) => {
console.info("particleAbility terminateSelf");
});
```
## particleAbility.acquireDataAbilityHelper
acquireDataAbilityHelper(uri: string): DataAbilityHelper
Obtains a **dataAbilityHelper** object.
**Parameters**
| Name| Type| Mandatory| Description|
| :--- | ------ | ---- | ------------------------ |
| uri | string | Yes| URI of the file to open.|
**Return value**
| Type| Description|
| ----------------- | -------------------------------------------- |
| DataAbilityHelper | A utility class used to help other abilities access a Data ability.|
**Example**
```js
import particleAbility from '@ohos.ability.particleAbility'
var uri = "";
particleAbility.acquireDataAbilityHelper(uri)
```
## particleAbility.connectAbility
connectAbility(request: Want, options:ConnectOptions): number
Connects this ability to a specific Service ability. This method uses a callback to return the result.
**Parameters**
| Name| Type| Mandatory| Description|
| ------- | -------------- | ---- | -------------------------- |
| request | [Want](#want) | Yes| Service ability to connect.|
| options | ConnectOptions | Yes| Callback used to return the result.|
ConnectOptions
| Name| Readable/Writable| Type| Mandatory| Description|
| ------------ | -------- | -------- | ---- | ---------------------------------- |
| onConnect | Read-only| function | Yes| Callback invoked when the connection is set up.|
| onDisconnect | Read-only| function | Yes| Callback invoked when the connection is interrupted.|
| onFailed | Read-only| function | Yes| Callback invoked when the connection fails.|
**Return value**
| Type| Description|
| ------ | -------------------------- |
| number | Unique identifier of the connection between the client and the service side.|
**Example**
```javascript
import particleAbility from '@ohos.ability.particleAbility'
function onConnectCallback(element, remote){
console.log('ConnectAbility onConnect remote is proxy:' + (remote instanceof rpc.RemoteProxy));
}
function onDisconnectCallback(element){
console.log('ConnectAbility onDisconnect element.deviceId : ' + element.deviceId)
}
function onFailedCallback(code){
console.log('particleAbilityTest ConnectAbility onFailed errCode : ' + code)
}
var connId = particleAbility.connectAbility(
{
bundleName: "com.ix.ServiceAbility",
abilityName: "com.ix.ServiceAbility.ServiceAbilityA",
},
{
onConnect: onConnectCallback,
onDisconnect: onDisconnectCallback,
onFailed: onFailedCallback,
},
);
```
## particleAbility.disconnectAbility
disconnectAbility(connection: number, callback:AsyncCallback\<void>): void
Disconnects this ability from a specific Service ability. This method uses a callback to return the result.
**Parameters**
| Name| Type| Mandatory| Description|
| ---------- | ------------- | ---- | ------------------------------ |
| connection | number | Yes| ID of the Service ability to disconnect.|
| callback | AsyncCallback\<void> | Yes| Callback used to return the result.|
**Example**
```javascript
import particleAbility from '@ohos.ability.particleAbility'
function onConnectCallback(element, remote){
console.log('ConnectAbility onConnect remote is proxy:' + (remote instanceof rpc.RemoteProxy));
}
function onDisconnectCallback(element){
console.log('ConnectAbility onDisconnect element.deviceId : ' + element.deviceId)
}
function onFailedCallback(code){
console.log('particleAbilityTest ConnectAbility onFailed errCode : ' + code)
}
var connId = particleAbility.connectAbility(
{
bundleName: "com.ix.ServiceAbility",
abilityName: "com.ix.ServiceAbility.ServiceAbilityA",
},
{
onConnect: onConnectCallback,
onDisconnect: onDisconnectCallback,
onFailed: onFailedCallback,
},
);
var result = particleAbility.disconnectAbility(connId,
(error,data) => {
console.log('particleAbilityTest DisConnectAbility result errCode : ' + error.code + " data: " + data)
},
);
```
## particleAbility.disconnectAbility
disconnectAbility(connection: number): Promise\<void>
Disconnects this ability from a specific Service ability. This method uses a promise to return the result.
**Parameters**
| Name| Type| Mandatory| Description|
| ---------- | ------ | ---- | ------------------------------ |
| connection | number | Yes| ID of the Service ability to disconnect.|
**Return value**
| Type| Description|
| -------------- | ------------------------- |
| Promise\<void> | Promise used to return the result.|
**Example**
```javascript
import particleAbility from '@ohos.ability.particleAbility'
function onConnectCallback(element, remote){
console.log('ConnectAbility onConnect remote is proxy:' + (remote instanceof rpc.RemoteProxy));
}
function onDisconnectCallback(element){
console.log('ConnectAbility onDisconnect element.deviceId : ' + element.deviceId)
}
function onFailedCallback(code){
console.log('particleAbilityTest ConnectAbility onFailed errCode : ' + code)
}
var connId = particleAbility.connectAbility(
{
bundleName: "com.ix.ServiceAbility",
abilityName: "com.ix.ServiceAbility.ServiceAbilityA",
},
{
onConnect: onConnectCallback,
onDisconnect: onDisconnectCallback,
onFailed: onFailedCallback,
},
);
var result = particleAbility.disconnectAbility(connId).then((void) => {
console.info("particleAbilityTest disconnectAbility");
});
```
## StartAbilityParameter
| Name| Readable/Writable| Type| Mandatory| Description|
| ------------------- | -------- | --------------------- | ---- | ------------------------------------------------------------ |
| want | Read-only| [Want](#want) | Yes| Information about the ability to start.|
| abilityStartSetting | Read-only| {[key: string]: any} | No| Special attribute of the ability to start. This attribute can be passed in the method call.|
## Want
| Name| Readable/Writable| Type| Mandatory| Description|
| ----------- | -------- | -------------------- | ---- | ------------------------------------------------------------ |
| deviceId | Read-only| string | No| ID of the device running the ability to start.|
| bundleName | Read-only| string | No| Bundle name of the ability to start. If both **bundleName** and **abilityName** are specified in a **Want** object, the **Want** object can directly match the specified ability.|
| abilityName | Read-only| string | No| Name of the ability to start. If both **bundleName** and **abilityName** are specified in a **Want** object, the **Want** object can directly match the specified ability.|
| uri | Read-only| string | No| URI information to match. If **uri** is specified in a **Want** object, the **Want** object will match the specified URI information, including **scheme**, **schemeSpecificPart**, **authority**, and **path**.|
| type | Read-only| string | No| MIME type, for example, **text/plain** or **image/***.|
| flags | Read-only| number | No| How the **Want** object will be handled. By default, numbers are passed in. For details, see [flags](#flags).|
| action | Read-only| string | No| Action option.|
| parameters | Read-only| {[key: string]: any} | No| List of parameters in the **Want** object.|
| entities | Read-only| Array\<string> | No| List of entities.|
## flags
| Name| Value| Description|
| ------------------------------------ | ---------- | ------------------------------------------------------------ |
| FLAG_AUTH_READ_URI_PERMISSION | 0x00000001 | Indicates the permission to read the URI.|
| FLAG_AUTH_WRITE_URI_PERMISSION | 0x00000002 | Indicates the permission to write the URI.|
| FLAG_ABILITY_FORWARD_RESULT | 0x00000004 | Returns the result to the ability.|
| FLAG_ABILITY_CONTINUATION | 0x00000008 | Indicates whether the ability on the local device can be migrated to a remote device.|
| FLAG_NOT_OHOS_COMPONENT | 0x00000010 | Indicates that a component does not belong to OHOS.|
| FLAG_ABILITY_FORM_ENABLED | 0x00000020 | Indicates whether to enable an ability.|
| FLAG_AUTH_PERSISTABLE_URI_PERMISSION | 0x00000040 | Indicates the permission to make the URI persistent.|
| FLAG_AUTH_PREFIX_URI_PERMISSION | 0x00000080 | Indicates the permission to verify URIs by prefix matching.|
| FLAG_ABILITYSLICE_MULTI_DEVICE | 0x00000100 | Supports cross-device startup in a distributed scheduler.|
| FLAG_START_FOREGROUND_ABILITY | 0x00000200 | Indicates that the Service ability is started regardless of whether the host application has been started.|
| FLAG_ABILITY_CONTINUATION_REVERSIBLE | 0x00000400 | Indicates that the migration is reversible.|
| FLAG_INSTALL_ON_DEMAND | 0x00000800 | Indicates that the specific ability will be installed if it has not been installed.|
| FLAG_INSTALL_WITH_BACKGROUND_MODE | 0x80000000 | Indicates that the specific ability will be installed in the background if it has not been installed.|
| FLAG_ABILITY_CLEAR_MISSION | 0x00008000 | Clears other operation missions. This flag can be set for the **Want** object passed to **ohos.app.Context#startAbility** and must be used together with **flag_ABILITY_NEW_MISSION**.|
| FLAG_ABILITY_NEW_MISSION | 0x10000000 | Creates a mission on the historical mission stack.|
| FLAG_ABILITY_MISSION_TOP | 0x20000000 | Starts the mission on the top of the existing mission stack; creates an ability instance if no mission exists.|
## AbilityStartSetting
The **AbilityStartSetting** attribute is an object defined as [key: string]: any. The key is a type of **AbilityStartSetting**, and the value is a type of **AbilityWindowConfiguration**.
Defines special attributes of an ability, for example, **featureAbility.AbilityStartSetting.BOUNDS_KEY**.
| Name| Value| Description|
| --------------- | --------------- | -------------------------- |
| BOUNDS_KEY | "abilityBounds" | Ability window size.|
| WINDOW_MODE_KEY | "windowMode" | Ability window display mode.|
| DISPLAY_ID_KEY | "displayId" | Display device ID.|
## AbilityWindowConfiguration
Defines the window display modes of a Page ability, for example, **featureAbility.AbilityWindowConfiguration.WINDOW_MODE_UNDEFINED**.
| Name| Value| Description|
| --------------------------- | ---- | ---------- |
| WINDOW_MODE_UNDEFINED | 0 | The Page ability is in an undefined window display mode.|
| WINDOW_MODE_FULLSCREEN | 1 | The Page ability is in full screen mode.|
| WINDOW_MODE_SPLIT_PRIMARY | 100 | The Page ability is displayed in the primary window when it is in split-screen mode.|
| WINDOW_MODE_SPLIT_SECONDARY | 101 | The Page ability is displayed in the secondary window when it is in split-screen mode.|
| WINDOW_MODE_FLOATING | 102 | The Page ability is displayed in floating window mode.|
| 38.858289 | 263 | 0.648662 | eng_Latn | 0.770202 |
fdec33f7327d07d69d140bff8e71a6fff9ebb720 | 498 | md | Markdown | _posts/2015-09-01-backport-activerelationor-to-rails-423.md | bf4/bf4.github.com | b4282ec8bfe64519035193a01ac16a9226313e9e | [
"MIT"
] | 1 | 2018-12-31T02:38:43.000Z | 2018-12-31T02:38:43.000Z | _posts/2015-09-01-backport-activerelationor-to-rails-423.md | bf4/bf4.github.com | b4282ec8bfe64519035193a01ac16a9226313e9e | [
"MIT"
] | 6 | 2015-08-04T15:17:57.000Z | 2018-04-19T15:34:25.000Z | _posts/2015-09-01-backport-activerelationor-to-rails-423.md | bf4/bf4.github.com | b4282ec8bfe64519035193a01ac16a9226313e9e | [
"MIT"
] | 1 | 2015-06-28T20:42:31.000Z | 2015-06-28T20:42:31.000Z | ---
layout: post
title: "Backport ActiveRecord::Relation#or to Rails 4.2.3"
description: "Backport ActiveRecord::Relation#or to Rails 4.2.3"
permalink: "backport-activerelation-or"
categories: [ 'rails', 'top' ]
tags: [ 'rails' ]
published: true
---
{% include JB/setup %}
I've backported `ActiveRecord::Relation#or` from Rails master for use in our Rails 4.2.3 app.
It was non-trivial, so I thought I'd share. Enjoy!
<script src="https://gist.github.com/bf4/84cff9cc6ac8489d769e.js"></script>
| 29.294118 | 93 | 0.722892 | eng_Latn | 0.722042 |
fded8acf39b0c9723a4c4b9ac8090d9b01df88f7 | 4,673 | md | Markdown | packages/core/CHANGELOG.md | mallikarjun1234/nucleus | 3e65b7b3c4a71ebf0ce2fd09e2d0a79a75597ecf | [
"MIT"
] | null | null | null | packages/core/CHANGELOG.md | mallikarjun1234/nucleus | 3e65b7b3c4a71ebf0ce2fd09e2d0a79a75597ecf | [
"MIT"
] | null | null | null | packages/core/CHANGELOG.md | mallikarjun1234/nucleus | 3e65b7b3c4a71ebf0ce2fd09e2d0a79a75597ecf | [
"MIT"
] | null | null | null | # Change Log
All notable changes to this project will be documented in this file.
See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
# [0.3.0](https://github.com/freshdesk/nucleus/compare/@freshworks/core@0.2.1...@freshworks/core@0.3.0) (2020-05-06)
### Features
* **Datepicker:** Implementation ([#179](https://github.com/freshdesk/nucleus/issues/179)) ([aa20813](https://github.com/freshdesk/nucleus/commit/aa208132c6d603ff044a2337af82022d0e7bc281))
## [0.2.1](https://github.com/freshdesk/nucleus/compare/@freshworks/core@0.2.0...@freshworks/core@0.2.1) (2020-04-13)
**Note:** Version bump only for package @freshworks/core
# [0.2.0](https://github.com/freshdesk/nucleus/compare/@freshworks/core@0.1.17...@freshworks/core@0.2.0) (2020-03-30)
### Features
* **toggle:** Implementation ([#141](https://github.com/freshdesk/nucleus/issues/141)) ([d2ff164](https://github.com/freshdesk/nucleus/commit/d2ff164a65ebe5dc14a233748c45120c07a389be))
## 0.1.17 (2020-03-30)
### Bug Fixes
* Changed Responsive design ([#98](https://github.com/freshdesk/nucleus/issues/98)) ([2623f7a](https://github.com/freshdesk/nucleus/commit/2623f7a385d0d9f06c12f2366835e342a3937baf))
* **modal:** Fixes bugs for focus-trap and autofocus ([#148](https://github.com/freshdesk/nucleus/issues/148)) ([198ec6f](https://github.com/freshdesk/nucleus/commit/198ec6f25ddec0bcff6f5e97a38c507b2b181a0d))
* **packages:** refactored dependencies ([#83](https://github.com/freshdesk/nucleus/issues/83)) ([cb1dc9f](https://github.com/freshdesk/nucleus/commit/cb1dc9f0e9c3f53cfdd78a072e92cc454be17c60))
* **toast-message:** Design review updates ([#155](https://github.com/freshdesk/nucleus/issues/155)) ([30742b5](https://github.com/freshdesk/nucleus/commit/30742b595d932ff6c33524f89990a8bedc1a91a5))
## [0.1.16](https://github.com/freshdesk/nucleus/compare/@freshworks/core@0.1.14...@freshworks/core@0.1.16) (2020-03-20)
### Bug Fixes
* **toast-message:** Design review updates ([#155](https://github.com/freshdesk/nucleus/issues/155)) ([30742b5](https://github.com/freshdesk/nucleus/commit/30742b595d932ff6c33524f89990a8bedc1a91a5))
## [0.1.15](https://github.com/freshdesk/nucleus/compare/@freshworks/core@0.1.14...@freshworks/core@0.1.15) (2020-03-20)
### Bug Fixes
* **toast-message:** Design review updates ([#155](https://github.com/freshdesk/nucleus/issues/155)) ([30742b5](https://github.com/freshdesk/nucleus/commit/30742b595d932ff6c33524f89990a8bedc1a91a5))
## [0.1.14](https://github.com/freshdesk/nucleus/compare/@freshworks/core@0.1.13...@freshworks/core@0.1.14) (2020-03-12)
### Bug Fixes
* **modal:** Fixes bugs for focus-trap and autofocus ([#148](https://github.com/freshdesk/nucleus/issues/148)) ([198ec6f](https://github.com/freshdesk/nucleus/commit/198ec6f25ddec0bcff6f5e97a38c507b2b181a0d))
## 0.1.13 (2020-03-09)
**Note:** Version bump only for package @freshworks/core
## 0.1.12 (2020-02-25)
**Note:** Version bump only for package @freshworks/core
## 0.1.11 (2020-02-25)
**Note:** Version bump only for package @freshworks/core
## 0.1.10 (2020-02-19)
**Note:** Version bump only for package @freshworks/core
## 0.1.9 (2020-02-18)
### Bug Fixes
* **packages:** refactored dependencies ([#83](https://github.com/freshdesk/nucleus/issues/83)) ([cb1dc9f](https://github.com/freshdesk/nucleus/commit/cb1dc9f0e9c3f53cfdd78a072e92cc454be17c60))
* Changed Responsive design ([#98](https://github.com/freshdesk/nucleus/issues/98)) ([2623f7a](https://github.com/freshdesk/nucleus/commit/2623f7a385d0d9f06c12f2366835e342a3937baf))
## [0.1.8](https://github.com/freshdesk/nucleus/compare/@freshworks/core@0.1.7...@freshworks/core@0.1.8) (2020-02-07)
**Note:** Version bump only for package @freshworks/core
## [0.1.5](https://github.com/freshdesk/nucleus/compare/@freshworks/core@0.1.4...@freshworks/core@0.1.5) (2019-12-19)
### Bug Fixes
* **packages:** refactored dependencies ([#83](https://github.com/freshdesk/nucleus/issues/83)) ([cb1dc9f](https://github.com/freshdesk/nucleus/commit/cb1dc9f0e9c3f53cfdd78a072e92cc454be17c60))
## [0.1.4](https://github.com/freshdesk/nucleus/compare/@freshworks/core@0.1.3...@freshworks/core@0.1.4) (2019-12-16)
**Note:** Version bump only for package @freshworks/core
## [0.1.3](https://github.com/freshdesk/nucleus/compare/@freshworks/core@0.1.2...@freshworks/core@0.1.3) (2019-12-12)
**Note:** Version bump only for package @freshworks/core
## 0.1.2 (2019-11-26)
**Note:** Version bump only for package @freshworks/core
## 0.1.1 (2019-11-19)
**Note:** Version bump only for package @freshworks/core
| 27.011561 | 208 | 0.72523 | yue_Hant | 0.33482 |
fdedd24c97bbfd9a09f8c19519e4db7ad21e0d5d | 7,905 | md | Markdown | CircuitBreaker/src/AspDotNetCore/FortuneTeller/Fortune-Teller-Service/README.md | miclip/Samples | 949b3af6b40fd7b46b62672e2eaa055e3f695462 | [
"Apache-2.0"
] | 3 | 2021-04-30T00:43:02.000Z | 2021-04-30T01:27:00.000Z | CircuitBreaker/src/AspDotNetCore/FortuneTeller/Fortune-Teller-Service/README.md | corn-pivotal/steeltoe-demo-net46 | 8fe436ade2a006010a610fbdbf750082f4d6da54 | [
"Apache-2.0"
] | null | null | null | CircuitBreaker/src/AspDotNetCore/FortuneTeller/Fortune-Teller-Service/README.md | corn-pivotal/steeltoe-demo-net46 | 8fe436ade2a006010a610fbdbf750082f4d6da54 | [
"Apache-2.0"
] | 6 | 2017-11-13T21:50:18.000Z | 2019-09-11T01:17:44.000Z | # Fortune-Teller-Service - ASP.NET Core Microservice
ASP.NET Core sample app illustrating how to use [Spring Cloud Eureka Server](http://projects.spring.io/spring-cloud) for registering micro services and [Spring Cloud Hystrix](http://cloud.spring.io/spring-cloud) for building resilient micro services applications. The Fortune-Teller-Service registers the fortuneService with the Eureka server upon startup and the Fortune-Teller-UI uses a Hystrix command with fallback ability when communicating with the Fortune service.
This sample also illustrates how to use the [Hystrix Dashboard](http://cloud.spring.io/spring-cloud) to gather status and metrics of the Hystrix command used in communications.
Note: You can run this either locally or on CloudFoundry.
# Pre-requisites - Running Local
This sample assumes that there is a running Spring Cloud Eureka Server and a Hystrix dashboard on your machine. To make this happen:
1. Install Java 8 JDK.
2. Install Maven 3.x.
3. Clone the Spring Cloud Samples Eureka repository. (https://github.com/spring-cloud-samples/eureka.git)
4. Go to the eureka server directory (`eureka`) and fire it up with `mvn spring-boot:run`
5. When running locally, this sample will default to looking for its eurka server on http://localhost:8761/eureka, so it should all connect.
6. Clone the Spring Cloud Samples Hystrix dashboard. (https://github.com/spring-cloud-samples/hystrix-dashboard.git)
7. Go to the hystrix dashboard directory (`hystix-dashboard`) and fire it up with `mvn spring-boot:run`
8. Install .NET Core SDK
# Building & Running - Local
1. Clone this repo. (i.e. git clone https://github.com/SteeltoeOSS/Samples)
2. cd samples/CircuitBreaker/src/AspDotNetCore/Fortune-Teller/Fortune-Teller-Service
3. dotnet restore --configfile nuget.config
4. dotnet run -f netcoreapp2.0 --server.urls http://*:5000
# What to expect - Local
After building and running the app, you should see something like the following:
```
$ cd samples/CircuitBreaker/src/AspDotNetCore/Fortune-Teller/Fortune-Teller-Service
$ dotnet run -f netcoreapp2.0 --server.urls http://*:5000
info: Microsoft.Data.Entity.Storage.Internal.InMemoryStore[1]
Saved 50 entities to in-memory store.
Hosting environment: Production
Now listening on: http://*:5000
Application started. Press Ctrl+C to shut down.
```
At this point the Fortune Teller Service is up and running and ready for the Fortune Teller UI to ask for fortunes.
# Pre-requisites - CloudFoundry
1. Installed Pivotal CloudFoundry
2. Installed Spring Cloud Services
3. Install .NET Core SDK
# Setup Service Registry on CloudFoundry
You must first create an instance of the Service Registry service in a org/space.
1. cf target -o myorg -s development
2. cf create-service p-service-registry standard myDiscoveryService
3. Wait for the service to become ready! (i.e. cf services)
# Publish App & Push to CloudFoundry
1. cf target -o myorg -s development
2. cd samples/CircuitBreaker/src/AspDotNetCore/Fortune-Teller/Fortune-Teller-Service
3. dotnet restore --configfile nuget.config
4. Publish app to a directory selecting the framework and runtime you want to run on.
(e.g. `dotnet publish -f netcoreapp2.0 -r ubuntu.14.04-x64`)
5. Push the app using the appropriate manifest.
(e.g. `cf push -f manifest.yml -p bin/Debug/netcoreapp2.0/ubuntu.14.04-x64/publish` or `cf push -f manifest-windows.yml -p bin/Debug/netcoreapp2.0/win10-x64/publish`)
Note: If you are using self-signed certificates it is possible that you might run into SSL certificate validation issues when pushing this app. The simplest way to fix this:
1. Disable certificate validation for the Spring Cloud Discovery Client. You can do this by editing `appsettings.json` and add `eureka:client:validate_certificates=false`.
# What to expect - CloudFoundry
After building and running the app, you should see something like the following in the logs.
To see the logs as you startup and use the app: `cf logs fortuneservice`
On a Windows cell, you should see something like this during startup:
```
2016-05-14T06:22:39.54-0600 [APP/0] OUT dbug: Steeltoe.Discovery.Eureka.Transport.EurekaHttpClient[0]
2016-05-14T06:22:39.54-0600 [APP/0] OUT GetRequestContent generated JSON: ......
2016-05-14T06:22:39.57-0600 [APP/0] OUT dbug: Steeltoe.Discovery.Eureka.Transport.EurekaHttpClient[0]
2016-05-14T06:22:39.58-0600 [APP/0] OUT RegisterAsync .....
2016-05-14T06:22:39.58-0600 [APP/0] OUT dbug: Steeltoe.Discovery.Eureka.DiscoveryClient[0]
2016-05-14T06:22:39.58-0600 [APP/0] OUT Register FORTUNESERVICE/fortuneService.apps.testcloud.com:2f7a9e48-bb3e-402a-6b44-68e9386b3b15 returned: NoContent
2016-05-14T06:22:41.07-0600 [APP/0] OUT info: Microsoft.Data.Entity.Storage.Internal.InMemoryStore[1]
2016-05-14T06:22:41.07-0600 [APP/0] OUT Saved 50 entities to in-memory store.
2016-05-14T06:22:41.17-0600 [APP/0] OUT Hosting starting
2016-05-14T06:22:41.17-0600 [APP/0] OUT verb: Microsoft.AspNet.Hosting.Internal.HostingEngine[4]
2016-05-14T06:22:41.19-0600 [APP/0] OUT Start
2016-05-14T06:22:41.19-0600 [APP/0] OUT info: Microsoft.Net.Http.Server.WebListener[0]
2016-05-14T06:22:41.23-0600 [APP/0] OUT Listening on prefix: http://*:57991/
2016-05-14T06:22:41.23-0600 [APP/0] OUT info: Microsoft.Net.Http.Server.WebListener[0]
2016-05-14T06:22:41.31-0600 [APP/0] OUT verb: Microsoft.AspNet.Hosting.Internal.HostingEngine[5]
2016-05-14T06:22:41.31-0600 [APP/0] OUT Hosting started
2016-05-14T06:22:41.31-0600 [APP/0] OUT Hosting environment: development
2016-05-14T06:22:41.32-0600 [APP/0] OUT Now listening on: http://*:57991
2016-05-14T06:22:41.32-0600 [APP/0] OUT Application started. Press Ctrl+C to shut down.
2016-05-14T06:23:09.76-0600 [APP/0] OUT dbug: Steeltoe.Discovery.Eureka.Transport.EurekaHttpClient[0]
2016-05-14T06:23:09.76-0600 [APP/0] OUT SendHeartbeatAsync ......., status: OK, instanceInfo: null
2016-05-14T06:23:09.76-0600 [APP/0] OUT dbug: Steeltoe.Discovery.Eureka.DiscoveryClient[0]
2016-05-14T06:23:09.76-0600 [APP/0] OUT Renew FORTUNESERVICE/fortuneService.apps.testcloud.com:2f7a9e48-bb3e-402a-6b44-68e9386b3b15 returned: OK
```
At this point the Fortune Teller Service is up and running and ready for the Fortune Teller UI to ask for fortunes.
# Using Container-to-Container on Cloud Foundry
If you wish to use Container-to-Container (C2C) communications between the UI and the Fortune Service, look at the comments in the files listed below. You will need to make modifications to those files. Also, you are encouraged to read the Cloud Foundry [C2C documentation](https://docs.pivotal.io/pivotalcf/1-10/devguide/deploy-apps/cf-networking.html) FIRST, before trying to use it with the Fortune Teller app.
1. `appsettings.json` - Eureka registration option settings
# Enabling SSL usage on Cloud Foundry
If you wish to use SSL communications between the Fortune Teller UI and the Fortune Teller Service, have a look at the comments in the files listed below. You will need to make modifications to one or more of those files. Also, you are encouraged to read the [Cloud Foundry documentation](https://docs.pivotal.io/pivotalcf/1-10/adminguide/securing-traffic.html) on how SSL is configured, used and implemented before trying to use it with the Fortune Teller app.
1. `appsettings.json` - Eureka registration option settings
2. `Program.cs` - Changes needed to enable SSL usage with Kestrel (Note: These changes are only required if using Containter-to-Container (C2C) networking, together with SSL, between the UI and the fortune service).
3. `manifest.yml` - Startup command line change (Note: This change is only required if using Containter-to-Container (C2C) networking, together with SSL, between the UI and the fortune service). | 69.342105 | 471 | 0.762555 | eng_Latn | 0.81124 |
fdede3cb0e7b9c215ced3340451e1d6c296b1299 | 2,315 | md | Markdown | docs/framework/unmanaged-api/metadata/imetadataimport-getrva-method.md | CarlosLanderas/docs.es-es | d3a206ffbac27e45072d0875ca9e4d2c158493e7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/unmanaged-api/metadata/imetadataimport-getrva-method.md | CarlosLanderas/docs.es-es | d3a206ffbac27e45072d0875ca9e4d2c158493e7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/unmanaged-api/metadata/imetadataimport-getrva-method.md | CarlosLanderas/docs.es-es | d3a206ffbac27e45072d0875ca9e4d2c158493e7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: IMetaDataImport::GetRVA (Método)
ms.date: 03/30/2017
api_name:
- IMetaDataImport.GetRVA
api_location:
- mscoree.dll
api_type:
- COM
f1_keywords:
- IMetaDataImport::GetRVA
helpviewer_keywords:
- GetRVA method [.NET Framework metadata]
- IMetaDataImport::GetRVA method [.NET Framework metadata]
ms.assetid: ea422217-988b-4acd-b2db-c55357938275
topic_type:
- apiref
ms.openlocfilehash: a3a5cadc1b5a9df7967aae271ff10296843121dd
ms.sourcegitcommit: 9a39f2a06f110c9c7ca54ba216900d038aa14ef3
ms.translationtype: MT
ms.contentlocale: es-ES
ms.lasthandoff: 11/23/2019
ms.locfileid: "74436957"
---
# <a name="imetadataimportgetrva-method"></a>IMetaDataImport::GetRVA (Método)
Obtiene la dirección virtual relativa (RVA) y las marcas de implementación del método o campo representado por el token especificado.
## <a name="syntax"></a>Sintaxis
```cpp
HRESULT GetRVA (
[in] mdToken tk,
[out] ULONG *pulCodeRVA,
[out] DWORD *pdwImplFlags
);
```
## <a name="parameters"></a>Parámetros
`tk`
de Símbolo (token) de metadatos de MethodDef o FieldDef que representa el objeto de código para el que se va a devolver la RVA. Si el token es FieldDef, el campo debe ser una variable global.
`pulCodeRVA`
enuncia Un puntero a la dirección virtual relativa del objeto de código representado por el token.
`pdwImplFlags`
enuncia Puntero a las marcas de implementación para el método. Este valor es una máscara de máscara de la enumeración [CorMethodImpl (](../../../../docs/framework/unmanaged-api/metadata/cormethodimpl-enumeration.md) . El valor de `pdwImplFlags` solo es válido si `tk` es un token de MethodDef.
## <a name="requirements"></a>Requisitos
**Plataformas:** Vea [Requisitos de sistema](../../../../docs/framework/get-started/system-requirements.md).
**Encabezado:** Cor. h
**Biblioteca:** Se incluye como recurso en MsCorEE. dll
**Versiones de .NET Framework:** [!INCLUDE[net_current_v10plus](../../../../includes/net-current-v10plus-md.md)]
## <a name="see-also"></a>Vea también
- [IMetaDataImport (interfaz)](../../../../docs/framework/unmanaged-api/metadata/imetadataimport-interface.md)
- [IMetaDataImport2 (interfaz)](../../../../docs/framework/unmanaged-api/metadata/imetadataimport2-interface.md)
| 37.95082 | 296 | 0.72527 | spa_Latn | 0.512593 |
fdee2743566b16339b03fddb476f9b1be7112138 | 153 | md | Markdown | docs/ru/docs/dev/reference/connection-type/alcatel/7450/cfm.md | prorevizor/noc | 37e44b8afc64318b10699c06a1138eee9e7d6a4e | [
"BSD-3-Clause"
] | 84 | 2017-10-22T11:01:39.000Z | 2022-02-27T03:43:48.000Z | docs/ru/docs/dev/reference/connection-type/alcatel/7450/cfm.md | prorevizor/noc | 37e44b8afc64318b10699c06a1138eee9e7d6a4e | [
"BSD-3-Clause"
] | 22 | 2017-12-11T07:21:56.000Z | 2021-09-23T02:53:50.000Z | docs/ru/docs/dev/reference/connection-type/alcatel/7450/cfm.md | prorevizor/noc | 37e44b8afc64318b10699c06a1138eee9e7d6a4e | [
"BSD-3-Clause"
] | 23 | 2017-12-06T06:59:52.000Z | 2022-02-24T00:02:25.000Z | ---
uuid: 4e5ff78d-252f-4758-aa38-e52d1cab1f74
---
# Alcatel | 7450 | CFM Connection Type
Alcatel 7450 CFM Slot
Genders
: `mf` - male and female types
| 15.3 | 42 | 0.712418 | eng_Latn | 0.438287 |
fdee30f0e919cd9958726f5c2775c47abdf7c4d3 | 2,956 | md | Markdown | docs/includes/ctp-support-exclusion.md | bingenortuzar/sql-docs.es-es | 9e13730ffa0f3ce461cce71bebf1a3ce188c80ad | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-04-26T21:26:08.000Z | 2021-04-26T21:26:08.000Z | docs/includes/ctp-support-exclusion.md | jlporatti/sql-docs.es-es | 9b35d3acbb48253e1f299815df975f9ddaa5e9c7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/includes/ctp-support-exclusion.md | jlporatti/sql-docs.es-es | 9b35d3acbb48253e1f299815df975f9ddaa5e9c7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
ms.openlocfilehash: ccc96ecf7dccede236616e4680243116b8492d6b
ms.sourcegitcommit: 0c6c1555543daff23da9c395865dafd5bb996948
ms.translationtype: HT
ms.contentlocale: es-ES
ms.lasthandoff: 09/04/2019
ms.locfileid: "70309935"
---
## <a name="enabled-deployment-scenarios"></a>Escenarios de implementación habilitados
La versión candidata para lanzamiento (RC) de SQL Server 2019 permite los escenarios siguientes:
- Instalación simultánea. Instale instancias de SQL Server 2019 RC con instancias de SQL Server 2012 a SQL Server 2017 u otras instancias de SQL Server 2019 CTP 3.0 o superior.
>[!NOTE]
>Aunque la instalación simultánea no se bloquea con SQL Server 2008 y 2008 R2, no hay versiones del sistema operativo Windows que se admitan habitualmente entre ellas y SQL Server 2019.
- Actualización local. Actualice a SQL Server 2019 RC desde instancias de SQL Server 2012 a SQL Server 2017 y SQL Server CTP 3.0. No se admite la actualización desde una instancia de SQL Server 2019 CTP inferior a la versión 3.0; se debe realizar una instalación nueva.
>[!NOTE]
>Aunque la instalación local desde SQL Server 2008 y 2008 R2 no se bloquea, no hay versiones del sistema operativo Windows que se admitan habitualmente entre ellas y SQL Server 2019.
## <a name="support"></a>Soporte técnico
SQL Server 2019 RC es software en versión preliminar. No se admite públicamente para las operaciones. Los clientes que participen en el [programa de adopción temprana de SQL](http://aka.ms/sqleap) pueden tener soporte técnico para ejecutar SQL Server 2019 RC por un contrato especial, en colaboración con Microsoft.
En una de las ubicaciones siguientes se puede encontrar soporte técnico limitado para los clientes que no participen en el programa de adopción temprana:
- Foros
- [Introducción a SQL Server](https://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?forum=sqlgetstarted)
- [Transact-SQL](https://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?forum=transactsql)
- [Documentación de SQL Server](https://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?forum=sqldocumentation)
- También puede enviar un tuit a [@SQLServer](https://twitter.com/SQLServer) con [#sqlhelp](https://twitter.com/search?q=%23sqlhelp)
**Pruebe [!INCLUDE[sql-server-2019](../includes/sssqlv15-md.md)]**
- [](https://go.microsoft.com/fwlink/?LinkID=862101) [Descargue [!INCLUDE[sql-server-2019](../includes/sssqlv15-md.md)] para instalarlo en Windows](https://go.microsoft.com/fwlink/?LinkID=862101).
- Instalar en Linux para [Red Hat Enterprise Server](../linux/quickstart-install-connect-red-hat.md), [SUSE Linux Enterprise Server](../linux/quickstart-install-connect-suse.md) y [Ubuntu](../linux/quickstart-install-connect-ubuntu.md)
- [Ejecutar [!INCLUDE[sql-server-2019](../includes/sssqlv15-md.md)] en Docker](../linux/quickstart-install-connect-docker.md).
| 77.789474 | 315 | 0.7818 | spa_Latn | 0.87369 |
fdee39672f2db80285932588388e1b0370671b64 | 731 | md | Markdown | README.md | gsc229/vanity-numbers | fc25f2c4b4d538bd3625070c815e89f640036c6f | [
"MIT"
] | null | null | null | README.md | gsc229/vanity-numbers | fc25f2c4b4d538bd3625070c815e89f640036c6f | [
"MIT"
] | null | null | null | README.md | gsc229/vanity-numbers | fc25f2c4b4d538bd3625070c815e89f640036c6f | [
"MIT"
] | 1 | 2021-12-02T00:05:13.000Z | 2021-12-02T00:05:13.000Z | # VoiceFoundry Code Challenge Submission
## Contents:
- [Overview](#overview)
- [Running the Python Application Locally](RUNPYTHONAPP.md)
- [CloudFormation Instructions](CLOUDFORMATION.md)
- [Contact Flow Instructions](CONTACTFLOW.md)
- [Managing The Project (Trello Board)](https://trello.com/b/MtaGkEdG/voicefoundry-code-challenge)
- [Blockers (Trello Board)](https://trello.com/b/MtaGkEdG/voicefoundry-code-challenge)
## Overview:
### Try it out:
Call: +1-800-52MOTTO | 1 (800) 526 - 6886
#### Tech Stack
- AWS Lambda
- AWS DynamoDB
- AWS Connect
- Python (for the lambda function)
#### Cloud Architecture
#### Contact Flow
| 25.206897 | 98 | 0.742818 | yue_Hant | 0.344683 |
fdf096d3090252bac6bb5359347a25111b7049f1 | 949 | md | Markdown | _bookmarks/2016/2016-02-26-7e8cb82ce37078e406dfd99a4a2ce7ac.md | tut-tuuut/boris.schapira.dev | e8fe080a5b4fe4438d456fc28881b5f25dfb306d | [
"MIT"
] | null | null | null | _bookmarks/2016/2016-02-26-7e8cb82ce37078e406dfd99a4a2ce7ac.md | tut-tuuut/boris.schapira.dev | e8fe080a5b4fe4438d456fc28881b5f25dfb306d | [
"MIT"
] | null | null | null | _bookmarks/2016/2016-02-26-7e8cb82ce37078e406dfd99a4a2ce7ac.md | tut-tuuut/boris.schapira.dev | e8fe080a5b4fe4438d456fc28881b5f25dfb306d | [
"MIT"
] | null | null | null | ---
_id: 'https://my.framasoft.org/u/borisschapira/?PSLCIg'
title: >-
"Content Performance Policy : une étape supplémentaire pour un web plus
rapide ?", Damien Jubeau
link: >-
http://blog.dareboost.com/fr/2016/02/content-performance-policy-pour-un-web-plus-rapide/
date: '2016-02-26'
tags:
- name: boostmarks
slug: boostmarks
- name: CPP
slug: cpp
- name: sharemarks
slug: sharemarks
---
<div class="markdown"><p>"Tim Kaldec et Yoav Weiss se sont donc inspirés de ce mécanisme [Content Security Policy], pour le transposer au sujet de la performance web, en proposant un nouvel en-tête HTTP (Content Performance Policy) permettant de déclarer précisément le degré de compatibilité d’une page avec certaines bonnes pratiques de performance web. À la charge ensuite du navigateur web, de forcer l’application des bonnes pratiques annoncées qui ne seraient pas respectées par l’éditeur."
</p></div>
| 47.45 | 506 | 0.737619 | fra_Latn | 0.918131 |
fdf121a2a2f06726a244d8fc6d6a4edc1697a351 | 24,900 | md | Markdown | docs/framework/install/guide-for-developers.md | cihanyakar/docs.tr-tr | 03b6c8998a997585f61b8be289df105261125239 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/install/guide-for-developers.md | cihanyakar/docs.tr-tr | 03b6c8998a997585f61b8be289df105261125239 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/install/guide-for-developers.md | cihanyakar/docs.tr-tr | 03b6c8998a997585f61b8be289df105261125239 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: .NET Framework Geliştirici paketi yükleyin veya yeniden dağıtılabilir
ms.custom: updateeachrelease
ms.date: 04/10/2018
helpviewer_keywords:
- .NET Framework redistributable package, downloading
- .NET Framework, installing
- installing .NET Framework
- installation [.NET Framework]
ms.assetid: daf9d9d5-84ac-4bd9-a864-27665ffd0f5c
author: rpetrusha
ms.author: ronpet
ms.openlocfilehash: 8d78549d2822ad6c660fae39d458a98f23eca390
ms.sourcegitcommit: ccd8c36b0d74d99291d41aceb14cf98d74dc9d2b
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 12/10/2018
ms.locfileid: "53146745"
---
# <a name="install-the-net-framework-for-developers"></a>Geliştiriciler için .NET Framework'ü yükleme
.NET, Windows üzerinde çalışan çok sayıda uygulamaların önemli bir parçasıdır ve bu uygulamaları çalıştırmak için ortak işlevselliği sağlar. Geliştiriciler için uygulamaları oluşturma için tutarlı bir programlama modeli sahip kullanıcı deneyimleri ve sorunsuz ve güvenli iletişimi görsel olarak etkileyici ve kapsamlı bir .NET Framework sağlar.
> [!NOTE]
> Bu konuda yöneliktir **geliştiriciler** ya da isteyen kendi sisteminde veya kendi uygulamaları ile kurmak isteyen .NET Framework'ü yüklemek. İçin **kullanıcılar** .NET Framework'ü yükleme ilgileniyor .NET Framework gibi belirli işletim sistemlerine yükleme tartışmak bireysel konulara bakın [Windows 10 ve Windows üzerinde .NET Framework yükleme Server 2016](on-windows-10.md).
Bu makalede .NET Framework'ün tüm sürümler için .NET Framework 4.5 yükleme için bağlantılar sağlar. [!INCLUDE[net_current](../../../includes/net-current-version.md)] bilgisayarınızda. Bir geliştiriciyseniz, bu bağlantıları karşıdan yüklemek ve .NET Framework ile uygulamalarınızı yeniden dağıtmak için kullanabilirsiniz. Uygulamanızı .NET Framework sürümünü dağıtma hakkında daha fazla bilgi için bkz. [geliştiriciler için .NET Framework Dağıtım Kılavuzu](../deployment/deployment-guide-for-developers.md).
[!INCLUDE[net-framework-4-versions](../../../includes/net-framework-4x-versions.md)]
Sürümleri .NET Framework ve bir bilgisayarda hangi sürümlerinin yüklü olduğunu belirleme hakkında daha fazla bilgi için bkz. [sürümler ve bağımlılıklar](~/docs/framework/migration-guide/versions-and-dependencies.md) ve [nasıl yapılır: Hangi .NET Framework sürümlerinin yüklü olduğunu belirleme](../../../docs/framework/migration-guide/how-to-determine-which-versions-are-installed.md).
> [!NOTE]
> .NET Framework 3.5 hakkında daha fazla bilgi için bkz: [Windows 10, Windows 8.1 ve Windows 8 üzerinde .NET Framework 3.5 yükleme](~/docs/framework/install/dotnet-35-windows-10.md).
Hızlı bağlantılar veya ayrıntılar için okumaya devam için aşağıdaki tabloyu kullanın. .NET Framework'ü yüklemeden önce sistem gereksinimlerini görmek için bkz: [sistem gereksinimleri](~/docs/framework/get-started/system-requirements.md). Sorun giderme ile ilgili daha fazla yardım için bkz: [sorun giderme](~/docs/framework/install/troubleshoot-blocked-installations-and-uninstallations.md).
|.NET Framework sürümü|Geliştirici yükleme|Yeniden dağıtılabilir yükleme|Platform desteği|
|----------------------------|----------------------------|----------------------------------|----------------------|
|**4.7.2**|[.NET framework 4.7.2 Geliştirici paketi](https://go.microsoft.com/fwlink/?LinkId=874338)|[İndirme Merkezi 4.7.2 web yükleyicisi](https://go.microsoft.com/fwlink/?LinkId=863262)<br/><br/>[İndirme Merkezi 4.7.2 çevrimdışı yükleyici](https://go.microsoft.com/fwlink/?LinkId=863265)|Dahil: <br/>Windows 10 Ekim 2018 güncelleştirmesi<br/>Windows 10 Nisan 2018 güncelleştirmesi<br /><br /> Üzerinde yükleyebilirsiniz:<br/> <br/>Windows 10 Fall Creators Update<br/>Windows 10 Creators Update <br /> Windows 10 Yıldönümü Güncelleştirmesi<br /> Windows 8.1 ve önceki sürümleri<br /> Windows Server sürüm 1709 ve öncesi<br /> (tam listesi için bkz: [sistem gereksinimleri](~/docs/framework/get-started/system-requirements.md))||
|**4.7.1**|[NET Framework 4.7.1 Geliştirici paketi](https://go.microsoft.com/fwlink/?LinkId=852105)|[4.7.1 için indirme sayfası web yükleyicisi](https://go.microsoft.com/fwlink/?LinkId=852095)<br /><br /> [4.7.1 için indirme sayfası çevrimdışı yükleyici](https://go.microsoft.com/fwlink/?LinkId=852107)|Dahil: <br/>Windows 10 Fall Creators Update<br/>Windows Server 1709 sürümü<br /><br /> Üzerinde yükleyebilirsiniz:<br/> Windows 10 Creators Update <br /> Windows 10 Yıldönümü Güncelleştirmesi<br /> Windows 8.1 ve önceki sürümleri<br /> Windows Server 2016 ve önceki sürümleri<br /> (tam listesi için bkz: [sistem gereksinimleri](~/docs/framework/get-started/system-requirements.md))||
|**4.7**|[NET Framework 4.7 Geliştirici paketi](https://go.microsoft.com/fwlink/?LinkId=825319)|[4.7 web Yükleyicisi için indirme sayfası](https://go.microsoft.com/fwlink/?LinkId=825299)<br /><br /> [4.7 çevrimdışı Yükleyicisi için indirme sayfası](https://go.microsoft.com/fwlink/?LinkId=825303)|Dahil: <br/>Windows 10 Creators Update<br /><br /> Üzerinde yükleyebilirsiniz:<br /> Windows 10 Yıldönümü Güncelleştirmesi<br /> Windows 8.1 ve önceki sürümleri<br /> Windows Server 2016 ve önceki sürümleri<br /> (tam listesi için bkz: [sistem gereksinimleri](~/docs/framework/get-started/system-requirements.md))||
|**4.6.2**|[.NET Framework 4.6.2 Geliştirici paketi](https://go.microsoft.com/fwlink/?LinkId=780617)|[4.6.2 için indirme sayfası web yükleyicisi](https://go.microsoft.com/fwlink/?LinkId=780597)<br /><br /> [4.6.2 için indirme sayfası çevrimdışı yükleyici](https://go.microsoft.com/fwlink/?LinkId=780601)|Dahil: <br /> Windows 10 Yıldönümü Güncelleştirmesi<br /><br /> Üzerinde yükleyebilirsiniz:<br /> Windows 10 Kasım güncelleştirmesi <br/> Windows 10 <br /> Windows 8.1 ve önceki sürümleri<br /> Windows Server 2012 R2 ve önceki sürümleri<br /> (tam listesi için bkz: [sistem gereksinimleri](~/docs/framework/get-started/system-requirements.md))|
|**4.6.1**|[NET Framework 4.6.1 Geliştirici paketi](https://go.microsoft.com/fwlink/?LinkId=690706)|[4.6.1 için indirme sayfası web yükleyicisi](https://go.microsoft.com/fwlink/?LinkId=671729)<br /><br /> [4.6.1 için indirme sayfası çevrimdışı yükleyici](https://go.microsoft.com/fwlink/?LinkId=671744)|Üzerinde yükleyebilirsiniz:<br /> Windows 10 <br /> Windows 8.1 ve önceki sürümleri<br /> Windows Server 2012 R2 ve önceki sürümleri<br /> (tam listesi için bkz: [sistem gereksinimleri](~/docs/framework/get-started/system-requirements.md))|
|**4.6**|Visual Studio 2015'te dahil.<br /><br /> [Microsoft .NET Framework 4.6 targeting pack](https://go.microsoft.com/fwlink/?LinkId=528261)|[4.6 web Yükleyicisi için indirme sayfası](https://go.microsoft.com/fwlink/?LinkId=528259)<br /><br /> [4.6 çevrimdışı Yükleyicisi için indirme sayfası](https://go.microsoft.com/fwlink/?LinkId=528233)|Dahil: <br /> Windows 10 <br />[Visual Studio 2015](https://my.visualstudio.com/Downloads?q=visual%20studio%202015)<br /><br /> Üzerinde yükleyebilirsiniz:<br /> Windows 8.1 ve önceki sürümleri<br /> Windows Server 2012 R2 ve önceki sürümleri<br /> (tam listesi için bkz: [sistem gereksinimleri](~/docs/framework/get-started/system-requirements.md))|
|**4.5.2**|[Microsoft .NET Framework 4.5.2 Geliştirici paketi](https://go.microsoft.com/fwlink/?LinkId=397702)<br /><br /> Visual Studio 2013, Visual Studio 2012 veya diğer Ide'leri ile kullanmak için|[4.5.2 için indirme sayfası web yükleyicisi](https://go.microsoft.com/fwlink/p/?LinkId=397703)<br /><br /> [4.5.2 için indirme sayfası çevrimdışı yükleyici](https://go.microsoft.com/fwlink/p/?LinkId=397706)|Üzerinde yükleyebilirsiniz:<br /> Windows 8.1 ve önceki sürümleri<br /> Windows Server 2012 R2 ve önceki sürümleri<br /> (tam listesi için bkz: [sistem gereksinimleri](~/docs/framework/get-started/system-requirements.md))|
|**4.5.1**|[Microsoft .NET Framework 4.5.1 Geliştirici paketi](https://go.microsoft.com/fwlink/?LinkId=324213)<br /><br /> Visual Studio 2013, Visual Studio 2012 veya diğer Ide'leri ile kullanmak için|[4.5.1 için sayfayı karşıdan yükleme web yükleyicisi](https://go.microsoft.com/fwlink/p/?LinkId=310158)<br /><br /> [4.5.1 için sayfayı karşıdan yükleme çevrimdışı yükleyici](https://go.microsoft.com/fwlink/p/?LinkId=310159)|Dahil:<br /> [!INCLUDE[win81](../../../includes/win81-md.md)]<br /> Windows Server 2012 R2<br /> [Visual Studio 2013](https://my.visualstudio.com/Downloads?q=visual%20studio%202013)<br /><br /> Üzerinde yükleyebilirsiniz:<br /> [!INCLUDE[win8](../../../includes/win8-md.md)] ve önceki sürümleri<br /> [!INCLUDE[winserver8](../../../includes/winserver8-md.md)] ve önceki sürümleri<br />(tam listesi için bkz: [sistem gereksinimleri](~/docs/framework/get-started/system-requirements.md))|
|**4.5**|Visual Studio 2012'de dahil<br /><br /> Olarak da kullanılabilir parçası [Windows 8 SDK'sı](https://msdn.microsoft.com/windows/hardware/hh852363)|[4.5 web Yükleyicisi için indirme sayfası](https://go.microsoft.com/fwlink/p/?LinkId=245484)|Dahil: <br /> [!INCLUDE[win8](../../../includes/win8-md.md)]<br /> [!INCLUDE[winserver8](../../../includes/winserver8-md.md)]<br /> [Visual Studio 2012](https://my.visualstudio.com/Downloads?q=visual%20studio%202012)<br /><br /> Üzerinde yükleyebilirsiniz:<br /> Windows 7 ve öncesi<br /> Windows Server 2008 SP2 ve önceki sürümleri<br />(tam listesi için bkz: [sistem gereksinimleri](~/docs/framework/get-started/system-requirements.md))|
Yükleyebileceğiniz **Geliştirici paketi** tüm desteklenen platformlarda kullanılabilir ise .NET Framework, belirli bir sürümü için.
Yükleyebileceğiniz **Web veya çevrimdışı yükleyiciyi** üzerinde:
- Windows 8.1 ve önceki sürümleri
- Windows Server 2012 R2 ve önceki sürümleri
Tam bir listesi için bkz [sistem gereksinimleri](~/docs/framework/get-started/system-requirements.md).
Kullanıcılara ve geliştiricilere yönelik .NET Framework'e Genel bir giriş için bkz: [Başlarken](../get-started/index.md). Uygulamanızı .NET Framework'ü dağıtma hakkında daha fazla bilgi için bkz: [Dağıtım Kılavuzu](~/docs/framework/deployment/deployment-guide-for-developers.md). Mimarisi ve .NET Framework'ün temel özellikleri hakkında bilgi için bkz [genel bakış](~/docs/framework/get-started/overview.md).
## <a name="installation-choices"></a>Yükleme Seçenekleri
Visual Studio veya başka bir geliştirme ortamında .NET Framework'ün en son sürüme karşı geliştirmek için paketi bir geliştirici yükleyebilir veya uygulamanın veya denetimin ile dağıtım için yeniden dağıtılabilir .NET Framework indirin.
### <a name="to-install-the-net-framework-developer-pack-or-targeting-pack"></a>.NET Framework Geliştirici paketi veya Targeting Pack yüklemek için
A *targeting pack* uygulamanızı Visual Studio hem de diğer geliştirme ortamlarında geliştirirken .NET Framework'ün belirli bir sürümü hedeflemesini sağlar. A *Geliştirici paketi* .NET Framework ve eşlik eden SDK'si, karşılık gelen hedefleme paketiyle birlikte, belirli bir sürümünü içerir.
.NET Framework 4.5.2 ya da 4.5.1 Geliştirici paketi, .NET Framework 4.6 targeting pack ve .NET Framework 4.6.1, 4.6.2, 4.7, 4.7.1 veya 4.7.2 Geliştirici paketi bir belirli .NET Framework'ün sürümü başvuru derlemelerini sağlar, dil paketlerini ve IntelliSense dosyaları için Visual Studio gibi bir tümleşik geliştirme ortamında kullanın. Ayrıca Visual Studio Geliştirici paketi kullanarak veya targeting pack, yeni bir proje oluşturduğunuzda, .NET Framework'ün yüklü sürümü hedef seçenekleri ekler. Aşağıdakilerden birini seçin:
- [Microsoft .NET Framework 4.7.2 Geliştirici paketi](https://go.microsoft.com/fwlink/?LinkId=874338)
- [Microsoft .NET Framework 4.7.1 Geliştirici paketi](https://go.microsoft.com/fwlink/?LinkId=852105)
- [Microsoft .NET Framework 4.7 Geliştirici paketi](https://go.microsoft.com/fwlink/?LinkId=825319)
- [Microsoft .NET Framework 4.6.2 Geliştirici paketi](https://go.microsoft.com/fwlink/?LinkId=780617)
- [Microsoft .NET Framework 4.6.1 Geliştirici paketi](https://go.microsoft.com/fwlink/?LinkId=690706)
- [Microsoft .NET Framework 4.6 Targeting Pack](https://go.microsoft.com/fwlink/?LinkId=528261)
- [.NET framework 4.5.2 Geliştirici paketi](https://go.microsoft.com/fwlink/?LinkId=397702) sürüm 4.5.2 Windows 8.1 veya önceki sürümleri, Visual Studio 2013, Visual Studio 2012 veya diğer Ide'leri yüklemek için.
- [.NET framework 4.5.1 Geliştirici paketi](https://go.microsoft.com/fwlink/?LinkId=324213) sürüm 4.5.1, Visual Studio 2012 veya diğer Ide'leri yüklemek için.
Geliştirici paketi indirme sayfasından, **indirme**. Sonraki seçin **çalıştırma** veya **Kaydet**, istendiğinde yönergeleri izleyin. Geliştirici paketi veya isteğe bağlı bileşenler'den seçerek targeting pack .NET Framework'ün belirli bir sürümü için de yükleyebilirsiniz **.NET Masaüstü geliştirmesinden** Visual Studio yükleyicisi, iş yükü olarak Aşağıdaki şekilde gösterir.
.NET Framework'ün belirli bir sürümünü hedeflediğinizde, bu sürümün Geliştirici paketi ile birlikte başvuru bütünleştirilmiş kodları kullanarak uygulamanızı oluşturdunuz. Çalışma zamanında, derlemeleri genel bütünleştirilmiş kod önbelleğinden çözümlenir ve başvuru derlemelerini kullanılmaz.
MSBuild, Visual Studio veya MSBuild'ı komut satırından kullanarak uygulama oluşturma, hata MSB3644, "Çerçevesi için başvuru bütünleştirilmiş" görüntüleyebilir*framework sürümü*"bulunamadı." Hatayı gidermek için geliştirici paketi veya .NET Framework sürümü hedefleme paketini indirin.
### <a name="to-install-or-download-the-net-framework-redistributable"></a>Yüklemek veya .NET Framework yeniden dağıtılabilir'i indirmek için
Yükleyiciler, bir uygulama ya da .NET Framework'ün bu sürümlerini hedefleyen bir denetim için .NET Framework bileşenlerini karşıdan yükleyin. Bu bileşenler uygulamanın veya denetimin çalıştığı her bilgisayara yüklenmelidir. Bu yükleyiciler yeniden dağıtılabilir, olduğundan bunları uygulamanız için Kurulum programına ekleyebilirsiniz.
Yükleme sayfası çeşitli dillerde sağlanmaktadır, ancak karşıdan çoğu yalnızca İngilizce dilinde sağlanır. Ek dil desteği için bir dil paketini sizin yüklemeniz gerekir.
Yeniden dağıtılabilir yükleyici iki türü kullanılabilir:
- **Web yükleyicisi** (web önyükleyicisi), gerekli bileşenleri ve Web'den yükleme bilgisayarının işletim sistemiyle eşleşen dil paketini yükler. Bu paket çevrimdışı Yükleyiciden daha küçüktür, ancak tutarlı bir Internet bağlantısı gerektirir. İndirebileceğiniz [tek başına dil paketlerini](#to-install-language-packs) ek dil desteği yüklemek için.
- **Çevrimdışı yükleyici** (tek başına yeniden dağıtılabilir) .NET Framework yükleme için gerekli tüm bileşenleri içerir, ancak dil paketlerini içermez. Bu indirme web yükleyicisinden daha büyüktür. Çevrimdışı yükleyici Internet bağlantısı gerektirmez. Çevrimdışı yükleyiciyi çalıştırdıktan sonra indirebileceğiniz [tek başına dil paketlerini](#to-install-language-packs) dil desteğini yüklemek için. Tutarlı bir Internet bağlantısı olması güvenemezsiniz çevrimdışı yükleyiciyi kullanın.
Hem web hem de çevrimdışı yükleyiciler x86 ve x64 tabanlı bilgisayarlar için tasarlanmıştır (bkz [sistem gereksinimleri](~/docs/framework/get-started/system-requirements.md)), ancak İtanyum tabanlı bilgisayarları desteklemez.
1. Yüklemek istediğiniz .NET Framework sürümü için indirme sayfayı açın:
- .NET framework 4.7.2 ([web yükleyicisi](https://go.microsoft.com/fwlink/?LinkId=863262) veya [çevrimdışı yükleyici](https://go.microsoft.com/fwlink/p/?LinkId=863265))
- .NET framework 4.7.1 ([web yükleyicisi](https://go.microsoft.com/fwlink/?LinkId=852095) veya [çevrimdışı yükleyici](https://go.microsoft.com/fwlink/p/?LinkId=852107))
- .NET framework 4.7 ([web yükleyicisi](https://go.microsoft.com/fwlink/?LinkId=825299) veya [çevrimdışı yükleyici](https://go.microsoft.com/fwlink/p/?LinkId=825303))
- .NET framework 4.6.2 ([web yükleyicisi](https://go.microsoft.com/fwlink/?LinkId=780597) veya [çevrimdışı yükleyici](https://go.microsoft.com/fwlink/p/?LinkId=780601))
- .NET framework 4.6.1 ([web yükleyicisi](https://go.microsoft.com/fwlink/?LinkId=671729) veya [çevrimdışı yükleyici](https://go.microsoft.com/fwlink/p/?LinkId=671744))
- .NET framework 4.6 ([web yükleyicisi](https://go.microsoft.com/fwlink/?LinkId=528259) veya [çevrimdışı yükleyici](https://go.microsoft.com/fwlink/p/?LinkId=528233))
- .NET framework 4.5.2 ([web yükleyicisi](https://go.microsoft.com/fwlink/p/?LinkId=397703) veya [çevrimdışı yükleyici](https://go.microsoft.com/fwlink/p/?LinkId=397706))
- .NET framework 4.5.1 ([web yükleyicisi](https://go.microsoft.com/fwlink/p/?LinkId=310158) veya [çevrimdışı yükleyici](https://go.microsoft.com/fwlink/p/?LinkId=310159))
- [.NET Framework 4.5](https://go.microsoft.com/fwlink/p/?LinkId=245484)
1. İndirme sayfası dilini seçin. Bu seçenek, .NET Framework'ün yerelleştirilmiş kaynaklarını karşıdan yüklemez; yalnızca karşıdan yükleme sayfasında görüntülenen metni etkiler.
1. Seçin **indirme**.
1. İstenirse, sistem mimarinizle eşleşen indirmeyi seçin ve ardından **sonraki**.
1. Karşıdan yükleme istemi göründüğünde yapın **bir** biri:
- Bilgisayarınızda .NET Framework'ü yüklemek isterseniz, seçin **çalıştırma**ve ardından ekrandaki yönergeleri izleyin.
- .NET Framework yeniden dağıtım için yüklemek istediğiniz kaldığınızda **Kaydet**ve ardından ekrandaki yönergeleri izleyin.
1. Ek diller için kaynak indirmek isterseniz, bir veya daha fazla dil paketlerini yüklemek için sonraki bölümünde yer alan yönergeleri izleyin.
> [!NOTE]
> Yükleme sırasında herhangi bir sorunla karşılaşırsanız, bkz [sorun giderme](~/docs/framework/install/troubleshoot-blocked-installations-and-uninstallations.md).
**Yükleme notları:**
- [!INCLUDE[net_v451](../../../includes/net-v451-md.md)] Ve 4.5.2, hem de [!INCLUDE[net_v46](../../../includes/net-v46-md.md)], 4.6.1, 4.6.2, 4.7, 4.7.1 ve 4.7.2 yerinde güncelleştirmeleri olan [!INCLUDE[net_v45](../../../includes/net-v45-md.md)].
- [!INCLUDE[net_v45](../../../includes/net-v45-md.md)], Kendi noktası sürümler [!INCLUDE[net_v46](../../../includes/net-v46-md.md)] ve sürümler ve .NET Framework 4.7 ve onun nokta sürümleri Değiştir noktasını [!INCLUDE[net_v40_long](../../../includes/net-v40-long-md.md)]. Bulunan bir sistemde bu sürümleri yüklediğinizde [!INCLUDE[net_v40_short](../../../includes/net-v40-short-md.md)] yüklediğinizde derlemeler değiştirilir.
- Kaldırma [!INCLUDE[net_v45](../../../includes/net-v45-md.md)], kendi noktası sürümler [!INCLUDE[net_v46](../../../includes/net-v46-md.md)] ve onun nokta sürümleri, veya .NET Framework 4.7 ve onun nokta sürümleri de önceden var olan kaldırır [!INCLUDE[net_v40_short](../../../includes/net-v40-short-md.md)] dosyaları. Geri dönmek istiyorsanız [!INCLUDE[net_v40_short](../../../includes/net-v40-short-md.md)], onu ve tüm güncellemelerini yeniden yüklemeniz gerekir. (Bkz [.NET Framework 4'ü yükleme](https://go.microsoft.com/fwlink/p/?LinkId=230665).)
- Yüklemek için yönetici kimlik bilgileriniz olmalıdır [!INCLUDE[net_v45](../../../includes/net-v45-md.md)], sürümler, .NET Framework 4.6 ve onun nokta sürümleri ve .NET Framework 4.7 ve onun nokta yayın gelin.
- .NET Framework 4.5 yeniden dağıtılabilir 2012'de 9 Ekim, dijital imzanın süresinin zamanından önce dolmasına Microsoft tarafından imzalanmış ve üretilen dosyaları neden bir dijital sertifika üzerinde hatalı zaman damgasıyla ilgili sorunu gidermek için güncelleştirildi. Daha önce yeniden dağıtılabilir paket 16 Ağustos 2012 tarihli .NET Framework 4.5 yüklü değilse kopyanızı ile en son yeniden dağıtılabilir Paketle güncelleştirmenizi öneririz [Microsoft Download Center](https://go.microsoft.com/fwlink/p/?LinkId=245484). Bu sorun hakkında daha fazla bilgi için bkz. [Microsoft Security Advisory 2749655](https://docs.microsoft.com/security-updates/SecurityAdvisories/2012/2749655) ve [Knowledge Base makalesi 2770445](https://support.microsoft.com/kb/2770445).
## <a name="to-install-language-packs"></a>Dil paketlerini yüklemek için
Dil paketleri, desteklenen diller için yerelleştirilmiş kaynaklar (örneğin, çevrilmiş hata iletileri ve UI metni) içeren çalıştırılabilir dosyalardır. Bir dil paketi yüklemezseniz, .NET Framework hata iletileri ve diğer metinler İngilizce görüntülenir. Web yükleyicisi, işletim sisteminize eşleşen dil paketini otomatik olarak yüklenir, ancak bilgisayarınıza ek dil paketlerini indirebilirsiniz unutmayın. Çevrimdışı yükleyiciler dil paketlerini içermez.
> [!IMPORTANT]
> Dil paketlerini, dil paketi yüklemeden önce web veya çevrimdışı yükleyiciyi çalıştırmanız gerekir böylece bir uygulamayı çalıştırmak için gerekli olan .NET Framework bileşenlerini içermezler. Bir dil paketi yüklediyseniz, bunu kaldırın, .NET Framework'ü yüklemek ve dil paketini yeniden yükleyin.
1. Yüklediğiniz .NET Framework sürümü için dil paketi indirme sayfasını açın:
- [.NET framework 4.7.2 dil paketleri](https://go.microsoft.com/fwlink/?LinkID=863258)
- [.NET framework 4.7.1 dil paketleri](https://go.microsoft.com/fwlink/?LinkID=852090)
- [.NET framework 4.7 Dil paketleri](https://go.microsoft.com/fwlink/?LinkID=825306)
- [.NET framework 4.6.2 dil paketleri](https://go.microsoft.com/fwlink/?LinkID=780604)
- [.NET framework 4.6.1 dil paketi](https://go.microsoft.com/fwlink/?LinkID=671747)
- [.NET framework 4.6 dil paketi](https://go.microsoft.com/fwlink/?LinkID=528314)
- [.NET framework 4.5.2 dil paketleri](https://go.microsoft.com/fwlink/?LinkId=397701)
- [.NET framework 4.5.1 dil paketleri](https://go.microsoft.com/fwlink/?LinkId=322101)
- [.NET framework 4.5 dil paketleri](https://go.microsoft.com/fwlink/p/?LinkId=245451)
2. Dil listesinde, indirmek istediğiniz dili seçin ve sayfanın bu dilde yeniden yüklenmesi için birkaç saniye bekleyin.
3. Seçin **indirme**.
Aşağıdaki tabloda desteklenen diller listelenmiştir.
| Dil | Kültür |
| --------------------- | :-----: |
| Arapça | ar |
| Çekçe | cs |
| Danca | da |
| Felemenkçe | nl |
| Fince | Fi |
| İngilizce (ABD) | en-US |
| Fransızca | FR |
| Almanca | de |
| Yunanca | el |
| İbranice | He |
| Macarca | hu |
| İtalyanca | Bunu |
| Japonca | ja |
| Korece | Ko |
| Norveççe | Yok |
| Lehçe | PL |
| Portekizce (Brezilya) | pt-BR |
| Portekizce (Portekiz) | pt-PT |
| Rusça | RU |
| Basitleştirilmiş Çince | zh-CHS |
| İspanyolca | ES |
| İsveççe | sv |
| Geleneksel Çince | zh-CHT |
| Türkçe | tr |
## <a name="next-steps"></a>Sonraki adımlar
- .NET Framework konusunda yeniyseniz, bkz. [genel bakış](~/docs/framework/get-started/overview.md) anahtar kavramlar ve bileşenlere giriş için.
- Yeni özellikler ve geliştirmeler .NET Framework 4.5 ve sonraki tüm sürümler için bkz. [yenilikler](../../../docs/framework/whats-new/index.md).
- Uygulamanızı .NET Framework'ü dağıtma hakkında ayrıntılı bilgi için bkz: [geliştiriciler için Dağıtım Kılavuzu](~/docs/framework/deployment/deployment-guide-for-developers.md).
- Uygulamanızla birlikte .NET Framework dağıtımını etkileyen değişiklikler için bkz: [azaltma sistemi yeniden sırasında .NET Framework 4.5 yüklemeleri](~/docs/framework/deployment/reducing-system-restarts.md).
- Uygulamanızı .NET Framework 4'e geçiş hakkında bilgi için [!INCLUDE[net_v45](../../../includes/net-v45-md.md)] veya onun nokta sürümleri birine bakın [Geçiş Kılavuzu](~/docs/framework/migration-guide/index.md).
- Bkz: [.NET Framework başvuru kaynağı](https://referencesource.microsoft.com/) .NET Framework kaynak kodu çevrimiçi gidin. Başvuru kaynağı de kullanılabilir [GitHub](https://github.com/Microsoft/referencesource). Yapabilecekleriniz [başvuru kaynağı indir](https://referencesource.microsoft.com/download.html) çevrimdışı izleme ve hata ayıklama sırasında (düzeltme eklerini ve güncelleştirmeleri gibi) kaynakları adımlayın. Daha fazla bilgi için blog girişine bakın [.NET başvuru kaynağı için yeni bir görünüm](https://blogs.msdn.com/b/dotnet/archive/2014/02/24/a-new-look-for-net-reference-source.aspx).
## <a name="see-also"></a>Ayrıca bkz.
- [Geliştiriciler için Dağıtım Kılavuzu](~/docs/framework/deployment/deployment-guide-for-developers.md)
- [Yöneticiler için Dağıtım Kılavuzu](~/docs/framework/deployment/guide-for-administrators.md)
- [Windows 10, Windows 8.1 ve Windows 8’de .NET Framework 3.5 Yükleme](~/docs/framework/install/dotnet-35-windows-10.md)
- [Engellenen .NET Framework yükleme ve kaldırma sorunlarını giderme](~/docs/framework/install/troubleshoot-blocked-installations-and-uninstallations.md)
| 104.1841 | 912 | 0.75739 | tur_Latn | 0.9981 |
fdf1cc1d0f16179adca7a76f8514b6cf959bd14d | 1,433 | md | Markdown | 2.MVC-and-frontend-development/Pre-read Materials/README.md | BalticMicrosoftDevelopersCommunity/letsbuild-2021 | 49c2234addab803d0a305ce812697d0009bc8c10 | [
"MIT"
] | 2 | 2021-04-15T15:22:07.000Z | 2021-11-23T10:47:05.000Z | 2.MVC-and-frontend-development/Pre-read Materials/README.md | SlippingAway/letsbuild-2021 | 73e01a29336d06fd443bc1030fe276b8ea47ff3b | [
"MIT"
] | null | null | null | 2.MVC-and-frontend-development/Pre-read Materials/README.md | SlippingAway/letsbuild-2021 | 73e01a29336d06fd443bc1030fe276b8ea47ff3b | [
"MIT"
] | 5 | 2021-04-14T13:11:34.000Z | 2021-04-15T16:01:44.000Z | # Pre-read materials recommendations
This session is dedicated to ASP.NET MVC and frontend development.
We recommend to familiarize yourself with the following topics, which will give you better understanding of presented materials:
[Overview of ASP.NET Core MVC](https://docs.microsoft.com/en-us/aspnet/core/mvc/overview?view=aspnetcore-5.0)
[Get started with ASP.NET Core MVC](https://docs.microsoft.com/en-us/aspnet/core/tutorials/first-mvc-app/start-mvc?view=aspnetcore-5.0&tabs=visual-studio)
[Layout in ASP.NET Core](https://docs.microsoft.com/en-us/aspnet/core/mvc/views/layout?view=aspnetcore-5.0)
[Razor syntax reference for ASP.NET Core](https://docs.microsoft.com/en-us/aspnet/core/mvc/views/razor?view=aspnetcore-5.0)
[Partial views in ASP.NET Core](https://docs.microsoft.com/en-us/aspnet/core/mvc/views/partial?view=aspnetcore-5.0)
[Model validation in ASP.NET Core MVC and Razor Pages](https://docs.microsoft.com/en-us/aspnet/core/mvc/models/validation?view=aspnetcore-5.0)
[Introduction to ASP.NET Core Blazor](https://docs.microsoft.com/en-us/aspnet/core/blazor/?view=aspnetcore-5.0)
[ASP.NET Core Blazor data binding](https://docs.microsoft.com/en-us/aspnet/core/blazor/components/data-binding?view=aspnetcore-5.0)
[Bootstrap](https://getbootstrap.com/)
[Bootswatch](https://bootswatch.com/)
[Bootswatch Superhero Theme](https://bootswatch.com/superhero/)
[Git documentation](https://git-scm.com/doc) | 49.413793 | 154 | 0.780181 | yue_Hant | 0.543417 |
fdf1f54b0146bbc3c21a14ebfef81a7e5528bb24 | 55 | md | Markdown | README.md | YouBM/prod2csv | fe02b1b1e3c14bb79b216b721b07f44c78841d56 | [
"MIT"
] | null | null | null | README.md | YouBM/prod2csv | fe02b1b1e3c14bb79b216b721b07f44c78841d56 | [
"MIT"
] | null | null | null | README.md | YouBM/prod2csv | fe02b1b1e3c14bb79b216b721b07f44c78841d56 | [
"MIT"
] | null | null | null | # prod2csv
extract json of view products to a CSV file
| 18.333333 | 43 | 0.781818 | eng_Latn | 0.754402 |
fdf23fc97f53f3eb55319873287bb294ef7a76cd | 1,839 | md | Markdown | content/xwlb/xwlb20200922.md | leeleilei/52etf.net | 934d558bd4181a1e0b39a7a10e0d7076c53995fb | [
"CC-BY-4.0"
] | 10 | 2020-06-01T16:08:00.000Z | 2021-10-31T15:17:26.000Z | content/xwlb/xwlb20200922.md | leeleilei/52etf.net | 934d558bd4181a1e0b39a7a10e0d7076c53995fb | [
"CC-BY-4.0"
] | null | null | null | content/xwlb/xwlb20200922.md | leeleilei/52etf.net | 934d558bd4181a1e0b39a7a10e0d7076c53995fb | [
"CC-BY-4.0"
] | null | null | null | ---
title: CCTV新闻联播摘要20200922
date: 2020-09-22T22:23:46.921084+08:00
tags: [新闻联播, 文化,新冠,服务,疫情,消费]
draft: false
---
中共中央总书记、国家主席、中央军委主席习近平9月22日下午在京主持召开教育<span class="keywords_content">文化</span>卫生体育领域专家代表座谈会并发表重要讲话，就“十四五”时期经济社会发展听取意见和建议。
国际移民组织总干事安东尼奥·维托里诺表示，习近平主席重申中国支持多边主义，这是对联合国的坚定支持，中国在加强多边主义以及为应对<span class="keywords_content">新冠</span>肺炎<span class="keywords_content">疫情</span>和之后的紧迫问题寻找全球共同解决方案方面发挥着重要作用。
他强调，党和国家高度重视教育、<span class="keywords_content">文化</span>、卫生、体育事业发展，党的十八大以来党中央就此作出一系列战略部署，各级党委和政府要抓好落实工作，努力培养担当民族复兴大任的时代新人，扎实推进社会主义<span class="keywords_content">文化</span>建设，大力发展卫生健康事业，加快体育强国建设，推动各项社会事业增添新动力、开创新局面，不断增强人民群众获得感、幸福感、安全感。
座谈会上，北京师范大学党委书记程建平，北京大学校长郝平，天津大学冯骥才文学艺术研究院院长冯骥才，中国社会科学院考古研究所所长陈星灿，中国文联副主席、中国戏剧家协会副主席、天津青年京剧团艺委会主任孟广禄，中国文联副主席、上海话剧艺术中心一级演员奚美娟，中国美术家协会主席、中央美术学院院长范迪安，中国疾控中心党委书记卢江，北京大学医学部常务副主任、北京大学第三医院院长乔杰，北京体育大学中国体育政策研究院执行院长鲍明晓等10位教育、<span class="keywords_content">文化</span>、卫生、体育领域专家和代表先后发言，就教育改革和发展、<span class="keywords_content">文化</span>传承和创新、卫生人才队伍建设、全面建设体育强国等提出意见和建议。
要聚焦影响人民健康的重大疾病和主要问题，加快实施健康中国行动，深入开展爱国卫生运动，完善国民健康促进政策，创新社会动员机制，健全健康教育制度，从源头上预防和控制重大疾病，实现从以治病为中心转向以健康为中心。
国新办发布会介绍体教融合有关政策情况国新办今天（9月22日）上午举行新闻发布会，国家体育总局和教育部相关负责人就中央全面深化改革委员会审议通过的《关于深化体教融合 促进青少年健康发展的意见》介绍了相关的政策情况。
《意见》指出，要以习近平新时代中国特色社会主义思想为指导，坚定实施扩大内需战略，以新业态新模式为引领，加快推动新型<span class="keywords_fund">消费</span>扩容提质，努力实现新型<span class="keywords_fund">消费</span>加快发展。
《意见》提出，经过3—5年努力，促进新型<span class="keywords_fund">消费</span>发展的体制机制和政策体系更加完善，到2025年，培育形成一批新型<span class="keywords_fund">消费</span>示范城市和领先企业，实物商品网上零售额占社会<span class="keywords_fund">消费</span>品零售总额比重显著提高，“互联网+<span class="keywords_fund">服务</span>”等<span class="keywords_fund">消费</span>新业态新模式得到普及并趋于成熟。
2014年，习近平总书记在第二次中央新疆工作座谈会上指出，要坚定不移推动新疆更好更快发展，同时，发展要落实到改善民生上、落实到惠及当地上、落实到增进团结上，让各族群众切身感受到党的关怀和祖国大家庭的温暖。
国家卫生健康委今天（9月22日）通报，9月21日0—24时，31个省（自治区、直辖市）和新疆生产建设兵团报告新增确诊病例6例，均为境外输入病例。
| 68.111111 | 354 | 0.844481 | yue_Hant | 0.824875 |
fdf257f7a95113b42f100d0bef4d171808b0a451 | 67 | md | Markdown | README.md | digigrade/OttoProgWin | d1eabad342a7d8e42244df7124e84e1eff6b03ab | [
"MIT"
] | null | null | null | README.md | digigrade/OttoProgWin | d1eabad342a7d8e42244df7124e84e1eff6b03ab | [
"MIT"
] | null | null | null | README.md | digigrade/OttoProgWin | d1eabad342a7d8e42244df7124e84e1eff6b03ab | [
"MIT"
] | null | null | null | # OttoProgWin
Windows OS Otto Programmer libraries and application
| 22.333333 | 52 | 0.850746 | eng_Latn | 0.665169 |
fdf30dd0aa72dbb4147a386af68598280ee17658 | 3,301 | md | Markdown | README.md | jakubpycha/express-conditional-request | ec1c28c5d3952af551062772641cc004aa03cc3c | [
"MIT"
] | 6 | 2017-07-17T12:42:19.000Z | 2021-06-20T09:24:28.000Z | README.md | jakubpycha/express-conditional-request | ec1c28c5d3952af551062772641cc004aa03cc3c | [
"MIT"
] | 3 | 2016-11-25T07:54:32.000Z | 2018-08-03T00:26:06.000Z | README.md | jakubpycha/express-conditional-request | ec1c28c5d3952af551062772641cc004aa03cc3c | [
"MIT"
] | 5 | 2017-07-05T10:31:06.000Z | 2021-07-16T08:27:47.000Z | # Conditional Requests
[](https://travis-ci.org/richardschneider/express-conditional-request)
[](https://coveralls.io/github/richardschneider/express-conditional-request?branch=master)
[](https://badge.fury.io/js/express-preconditions)
Middleware for HTTP Conditional Requests ([RFC 7232](https://tools.ietf.org/html/rfc7232)).
It conditionally processes a HTTP request based on a precondition (such as an etag or modification date).
A precondition is specified using the `If-Match`, `If-None-Match`, `If-Modified-Since` or `If-Unmodified-Since` HTTP header.
The [change log](https://github.com/richardschneider/express-conditional-request/releases) is automatically produced with
the help of [semantic-release](https://github.com/semantic-release/semantic-release).
## Getting started
Install with [npm](http://blog.npmjs.org/post/85484771375/how-to-install-npm)
> npm install express-preconditions --save
## Usage
Include the following in your server startup
````javascript
const preconditions = require('express-preconditions')
app.use(preconditions())
````
or
````javascript
const preconditions = require('express-preconditions')
const options = { ... }
app.use(preconditions(options))
````
See our [test server](https://github.com/richardschneider/express-conditional-request/blob/master/test/server.js) for more details.
## Options
Name | Description
:---- | :-----------
error | A function that takes (`status code, message, req, res`) and sends an error response.
requiredWith | An array of HTTP methods that must include one of the precondition headers. This prevents the [lost update issue](https://en.wikipedia.org/wiki/Concurrency_control). Defaults to `['PUT', 'PATCH', 'DELETE']`.
stateAsync | A function that takes `(req)` and returns a `Promise` to the get the assoiciated resource state.
### Resource state
The resource state contains the `etag` and `lastModified` properties, which conform to the respective HTTP headers
and can be `undefined`.
The default `stateAsync()` obtains the resource state by sending a `HEAD` request to the server.
## Status codes
The following HTTP status codes can be returned by the middleware
Code | Reason
:---- | :------
[304 (Not Modified)](https://tools.ietf.org/html/rfc7232#section-4.1) | The resource has not been modified since the version specified by the precondition(s).
[412 (Precondition Failed)](https://tools.ietf.org/html/rfc7232#section-4.2) | A precondition failed.
[428 (Precondition Required)](https://tools.ietf.org/html/rfc6585#section-3) | A precondition header is required to avoid the [lost update issue](https://en.wikipedia.org/wiki/Concurrency_control).
[501 (Not implemented)](https://tools.ietf.org/html/rfc7231#section-6.6.2s) | A precondition is not yet implemented.
# TODO
* The `If-Range` header is not currently supported.
# License
The [MIT license](LICENSE).
Copyright © 2016 Richard Schneider [(makaretu@gmail.com)](mailto:makaretu@gmail.com?subject=express-conditional-request)
| 46.492958 | 224 | 0.75674 | eng_Latn | 0.822514 |
fdf332ead0fb0a0857d3c10ab384bd59cfb4e081 | 4,048 | md | Markdown | docs/framework/unmanaged-api/profiling/icorprofilercallback-jitcompilationstarted-method.md | CharleyGui/docs.fr-fr | 2563c94abf0d041d775f700b552d1dbe199f03d5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/unmanaged-api/profiling/icorprofilercallback-jitcompilationstarted-method.md | CharleyGui/docs.fr-fr | 2563c94abf0d041d775f700b552d1dbe199f03d5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/unmanaged-api/profiling/icorprofilercallback-jitcompilationstarted-method.md | CharleyGui/docs.fr-fr | 2563c94abf0d041d775f700b552d1dbe199f03d5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: ICorProfilerCallback::JITCompilationStarted, méthode
ms.date: 03/30/2017
api_name:
- ICorProfilerCallback.JITCompilationStarted
api_location:
- mscorwks.dll
api_type:
- COM
f1_keywords:
- ICorProfilerCallback::JITCompilationStarted
helpviewer_keywords:
- JITCompilationStarted method [.NET Framework profiling]
- ICorProfilerCallback::JITCompilationStarted method [.NET Framework profiling]
ms.assetid: 31782b36-d311-4518-8f45-25f65385af5b
topic_type:
- apiref
ms.openlocfilehash: 7ce100a68a3e2b8963ed14bbf044fa9ba11d629f
ms.sourcegitcommit: d8020797a6657d0fbbdff362b80300815f682f94
ms.translationtype: MT
ms.contentlocale: fr-FR
ms.lasthandoff: 11/24/2020
ms.locfileid: "95725514"
---
# <a name="icorprofilercallbackjitcompilationstarted-method"></a>ICorProfilerCallback::JITCompilationStarted, méthode
Notifie le profileur que le compilateur juste-à-temps (JIT) a commencé à compiler une fonction.
## <a name="syntax"></a>Syntaxe
```cpp
HRESULT JITCompilationStarted(
[in] FunctionID functionId,
[in] BOOL fIsSafeToBlock);
```
## <a name="parameters"></a>Paramètres
`functionId`
dans ID de la fonction pour laquelle la compilation démarre.
`fIsSafeToBlock`
dans Valeur indiquant au profileur si le blocage affecte le fonctionnement du Runtime. La valeur est `true` si le blocage peut amener le runtime à attendre que le thread appelant retourne à partir de ce rappel ; sinon, `false` .
Bien qu’une valeur de n' `true` endommage pas le runtime, elle peut incliner les résultats de profilage.
## <a name="remarks"></a>Remarques
Il est possible de recevoir plusieurs `JITCompilationStarted` appels de et [ICorProfilerCallback :: JITCompilationFinished](icorprofilercallback-jitcompilationfinished-method.md) pour chaque fonction, en raison de la façon dont le Runtime gère les constructeurs de classe. Par exemple, le runtime commence à effectuer une compilation JIT de la méthode A, mais le constructeur de classe de la classe B doit être exécuté. Par conséquent, le runtime JIT compile le constructeur pour la classe B et l’exécute. Pendant que le constructeur est en cours d’exécution, il effectue un appel à la méthode A, ce qui entraîne une nouvelle compilation juste-à-temps de la méthode A. Dans ce scénario, la première compilation JIT de la méthode A est arrêtée. Toutefois, les deux tentatives de compilation JIT de la méthode A sont signalées par des événements de compilation JIT. Si le profileur va remplacer le code MSIL (Microsoft Intermediate Language) pour la méthode A en appelant la méthode [ICorProfilerInfo :: SetILFunctionBody](icorprofilerinfo-setilfunctionbody-method.md) , il doit le faire pour les deux `JITCompilationStarted` événements, mais il peut utiliser le même bloc MSIL pour les deux.
Les profileurs doivent prendre en charge la séquence de rappels JIT dans les cas où deux threads effectuent simultanément des rappels. Par exemple, le thread A appelle `JITCompilationStarted` . Toutefois, avant que le thread A appelle `JITCompilationFinished` , le thread B appelle [ICorProfilerCallback :: ExceptionSearchFunctionEnter,](icorprofilercallback-exceptionsearchfunctionenter-method.md) avec l’ID de fonction du rappel du thread A `JITCompilationStarted` . Il peut sembler que l’ID de fonction ne soit pas encore valide, car un appel à `JITCompilationFinished` n’a pas encore été reçu par le profileur. Toutefois, dans un cas comme celui-ci, l’ID de fonction est valide.
## <a name="requirements"></a>Configuration requise
**Plateformes :** Consultez [Configuration requise](../../get-started/system-requirements.md).
**En-tête :** CorProf.idl, CorProf.h
**Bibliothèque :** CorGuids.lib
**Versions de .NET Framework :**[!INCLUDE[net_current_v20plus](../../../../includes/net-current-v20plus-md.md)]
## <a name="see-also"></a>Voir aussi
- [ICorProfilerCallback, interface](icorprofilercallback-interface.md)
- [JITCompilationFinished, méthode](icorprofilercallback-jitcompilationfinished-method.md)
| 60.41791 | 1,193 | 0.782115 | fra_Latn | 0.829424 |
fdf415bd75896fbcce7f085c9ee3a9095f16ff13 | 691 | md | Markdown | weibotop_content/2021/2021-07/2021-07-29/17:51.md | handn-work/spider | 8130508da1ba31df2d1430c0077ad08602417fd3 | [
"MIT"
] | null | null | null | weibotop_content/2021/2021-07/2021-07-29/17:51.md | handn-work/spider | 8130508da1ba31df2d1430c0077ad08602417fd3 | [
"MIT"
] | null | null | null | weibotop_content/2021/2021-07/2021-07-29/17:51.md | handn-work/spider | 8130508da1ba31df2d1430c0077ad08602417fd3 | [
"MIT"
] | 1 | 2022-01-24T09:20:56.000Z | 2022-01-24T09:20:56.000Z | 最高法发布司法解释保护人脸安全
马龙VS奥恰洛夫
国乒锁定男女单打金银牌
中国女排VS俄罗斯女排
全新YSL小黑条
王梦洁救球
提前包揽金银牌的中国队yyds
樊振东晋级乒乓男单决赛
成都确诊一家三口并未观看魅力湘西演出
用最奶的脸打最凶的球
李盈莹yyds
陈意涵怀二胎
马龙被罚分
国外举重选手感谢中国网友
刘国梁站起来为樊振东欢呼
今年奥运会最忙的人还有撒贝宁
朱婷的手腕
马龙4比3击败奥恰洛夫
田志希整容前后对比
郑州暴雨涨价到2888酒店已摘牌停业
陈赫说女单太绝了
专家建议别买二手儿童安全座椅
鸿星尔克系统崩溃恳请退款
马龙樊振东会师男单决赛
伊藤美诚哭了
刘耀文跟着张国伟学废了
黄雅琼说金牌属于中国
孙颖莎的脸国乒知名景点
宋茜是不是在修车店兼职过
河南强降雨已致99人遇难
樊振东以暴制暴
万茜想捏孙颖莎的脸
中国队女子4×200米自由泳接力夺金
许魏洲连发200多个哈
国人为何不再唯金牌论了
六公主在放催眠大师
距离张雨霏上一次夺金已经过去了80分钟
最让人放心的夺金赛
中国女排进入决胜局
石智勇说钓鱼比举重有趣
张家界确诊1例本土病例
张哲瀚直播
湖北扫黄打非办加入校外培训监管整治
奥运直播
孙颖莎战胜伊藤美诚
张常宁好稳
东京都新增确诊3865例
女排音乐
贵人鸟
张雨绮夸张雨霏漂亮又有实力
贾乃亮说孙颖莎好样的
自带鬼畜的乒乓球队队歌
| 13.037736 | 21 | 0.772793 | yue_Hant | 0.499226 |
fdf4abb86feaf5ccfbd8b275856694a707b259a5 | 2,775 | md | Markdown | tests/README.md | Drakorgaur/hipanel-core | 9851814b6c7ddc91c2d4ad3758e75d586d5b4c0c | [
"BSD-3-Clause"
] | 38 | 2016-01-27T09:46:59.000Z | 2022-01-24T10:11:32.000Z | tests/README.md | Drakorgaur/hipanel-core | 9851814b6c7ddc91c2d4ad3758e75d586d5b4c0c | [
"BSD-3-Clause"
] | 15 | 2017-05-17T17:02:28.000Z | 2021-11-20T16:54:57.000Z | tests/README.md | Drakorgaur/hipanel-core | 9851814b6c7ddc91c2d4ad3758e75d586d5b4c0c | [
"BSD-3-Clause"
] | 21 | 2016-04-24T20:28:05.000Z | 2022-01-26T08:08:01.000Z | # Additional Classes for testing HiPanel with Codecept
All additional classes are divided by directories where dir-name is short name of class functionality. All methods aggregating in one file _\_support/\_generated/AcceptanceTesterActoions.php_
## \_support/Helper
- [CredentialsProvider] helps to authorize different roles.
- [PnotifyHelper] helps to close the modal window after the event.
- [PressButtonHelper] helps to press the buttons by the value of the text in the button.
- [WaitHelper] helps to check if the Ajax requests have ended.
[CredentialsProvider]: _support/Helper/CredentialsProvider.php
[PnotifyHelper]: _support/Helper/PnotifyHelper.php
[PressButtonHelper]: _support/Helper/PressButtonHelper.php
[WaitHelper]: _support/Helper/WaitHelper.php
## \_support/Page
- [Authenticated] helps to log in and go to the tested page.
- [IndexPage] helps to check the presence of all blocks (legend, filters, columns) on the index page of the module, check the operation of filters or sort, select a row of a table by ID or number, check the drop-down row-menu in the table.
- [SidebarMenu] helps to check the presence of menu items in the sidebar.
- [Login] helps to log in.
[Authenticated]: _support/Page/Authenticated.php
[IndexPage]: _support/Page/IndexPage.php
[SidebarMenu]: _support/Page/SidebarMenu.php
[Login]: _support/Page/Login.php
## \_support/Page/Widget/Input
- [TestableInput] is basic class for input element. The elements can be created in three different ways: free input element, as Advanced search element, as Table filter element of index page.
- [Dropdown] helps to check visible dropdown, set value, etc.
- [Input] helps to search or filter by selector and set value in input.
- [Select2] helps to test dropdown select with query, search or filter by selector, set value in select, etc.
- [Textarea] search or filter by selector and set value in textarea.
[TestableInput]: _support/Page/Widget/Input/TestableInput.php
[Dropdown]: _support/Page/Widget/Input/Dropdown.php
[Input]: _support/Page/Widget/Input/Input.php
[Select2]: _support/Page/Widget/Input/Select2.php
[Textarea]: _support/Page/Widget/Input/Textarea.php
## \_support
- [AcceptanceTester] helps to login and init credentials.
[AcceptanceTester]: _support/AcceptanceTester.php
## \_support/Step/Acceptance
- [Client] helps to login Client Role and init creditials.
- [Admin] helps to login Admin Role and init credentials.
- [Manager] helps to login Manager Role and init credentials.
- [Seller] helps to login Seller Role and init credentials.
[Client]: _support/Step/Acceptance/Client.php
[Admin]: _support/Step/Acceptance/Admin.php
[Manager]: _support/Step/Acceptance/Manager.php
[Seller]: _support/Step/Acceptance/Seller.php
| 46.25 | 243 | 0.775495 | eng_Latn | 0.922673 |
fdf579f4f83fb5232cc334fc71e9b26c98509f90 | 705 | md | Markdown | 2012/CVE-2012-1500.md | sei-vsarvepalli/cve | fbd9def72dd8f1b479c71594bfd55ddb1c3be051 | [
"MIT"
] | 4 | 2022-03-01T12:31:42.000Z | 2022-03-29T02:35:57.000Z | 2012/CVE-2012-1500.md | sei-vsarvepalli/cve | fbd9def72dd8f1b479c71594bfd55ddb1c3be051 | [
"MIT"
] | null | null | null | 2012/CVE-2012-1500.md | sei-vsarvepalli/cve | fbd9def72dd8f1b479c71594bfd55ddb1c3be051 | [
"MIT"
] | 1 | 2022-03-29T02:35:58.000Z | 2022-03-29T02:35:58.000Z | ### [CVE-2012-1500](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-1500)
### Description
Stored XSS vulnerability in UpdateFieldJson.jspa in JIRA 4.4.3 and GreenHopper before 5.9.8 allows an attacker to inject arbitrary script code.
### POC
#### Reference
- https://web.archive.org/web/20121014055829/http://www.cloudscan.me/2012/09/cve-2012-1500-ghs-5375-ghs-5642.html
- https://www.exploit-db.com/exploits/21052
#### Github
No GitHub POC found.
| 37.105263 | 143 | 0.744681 | yue_Hant | 0.301367 |
fdf60eece2d3de482b509ec788ed6faca2d52572 | 978 | md | Markdown | content/post/staking/zi-yuan/index.md | EthereumCN/-ecn_gatsby_eth2 | d70cf4c0eff0929fa91895b64570aaf091b20151 | [
"MIT"
] | null | null | null | content/post/staking/zi-yuan/index.md | EthereumCN/-ecn_gatsby_eth2 | d70cf4c0eff0929fa91895b64570aaf091b20151 | [
"MIT"
] | null | null | null | content/post/staking/zi-yuan/index.md | EthereumCN/-ecn_gatsby_eth2 | d70cf4c0eff0929fa91895b64570aaf091b20151 | [
"MIT"
] | null | null | null | ---
path: zi-yuan
id: 24
title: 相关资源
description: 相关资源
date: 2020-06-25T02:15:01.762Z
author: ECN
---
<br/>
### Eth2 验证者启动器
[Eth2 Launchpad](https://launchpad.ethereum.org/)
### 收益计算
[beaconcha.in 质押计算器](https://beaconcha.in/calculator)
[beaconscan 计算器](https://beaconscan.com/staking-calculator)
### 社区
EthStaker : [Reddi](https://www.reddit.com/r/ethstaker/)、[Discord](https://discord.com/invite/6fJw9qG)
### 浏览器
[beaconcha.in 以太坊 2.0 信标链浏览器](https://beaconcha.in/)
[Etherscan Eth2 信标链存款](https://cn.etherscan.com/txsBeaconDeposit)
[Beaconscan](https://beaconscan.com/)
### 质押服务
beaconcha.in [质押服务汇总列表](https://beaconcha.in/stakingServices)
### 学习资源
EthFans : [以太坊 2.0 知识库 ](https://ethfans.org/wikis/Home#%E4%BB%A5%E5%A4%AA%E5%9D%8A-2-0)
beacon.in：[以太坊 2.0 知识库](https://kb.beaconcha.in/)
Attestant : [Staking 相关文章](https://www.attestant.io/posts/)
Ethhub : [以太坊 2.0 知识库](https://docs.ethhub.io/ethereum-roadmap/ethereum-2.0/eth-2.0-phases/)
###
| 16.862069 | 102 | 0.691207 | yue_Hant | 0.550368 |
fdf6728cb805d940ca04d2576b0e1b8fdb46ae83 | 1,947 | md | Markdown | content/blog/old-posts/85.md | hemisu/hemisu.github.io | 60f3610ad7ecf33117590f6c5c9aca8802480896 | [
"0BSD"
] | null | null | null | content/blog/old-posts/85.md | hemisu/hemisu.github.io | 60f3610ad7ecf33117590f6c5c9aca8802480896 | [
"0BSD"
] | 1 | 2020-06-14T15:49:22.000Z | 2020-06-14T15:49:22.000Z | content/blog/old-posts/85.md | hemisu/hemisu.github.io | 60f3610ad7ecf33117590f6c5c9aca8802480896 | [
"0BSD"
] | 5 | 2015-07-17T03:02:47.000Z | 2015-08-21T15:08:33.000Z | ---
title: PAT A1058
date: 2017-02-04 21:47:55
updated: 2017-02-04 22:11:10
categories: algorithm - PAT
tags:
keywords:
description:
typecho_id: 85
---
If you are a fan of Harry Potter, you would know the world of magic has its own currency system -- as Hagrid explained it to Harry, "Seventeen silver Sickles to a Galleon and twenty-nine Knuts to a Sickle, it's easy enough." Your job is to write a program to compute A+B where A and B are given in the standard form of "Galleon.Sickle.Knut" (Galleon is an integer in [0, 107], Sickle is an integer in [0, 17), and Knut is an integer in [0, 29)).
Input Specification:
Each input file contains one test case which occupies a line with A and B in the standard form, separated by one space.
Output Specification:
For each test case you should output the sum of A and B in one line, with the same format as the input.
Sample Input:
3.2.1 10.16.27
Sample Output:
14.1.28
#include "stdio.h"
const int Galleon = 17 * 29;
const int Sickle = 29;
int main(){
int a1, a2, a3;
int b1, b2, b3;
scanf("%d.%d.%d %d.%d.%d", &a1, &a2, &a3, &b1, &b2, &b3);
long long a, b, c;
a = a1 * Galleon + a2 * Sickle + a3;
b = b1 * Galleon + b2 * Sickle + b3;
c = a + b;
printf("%lld.%lld.%lld", c / Galleon, c % Galleon / Sickle, c % Sickle);
return 0;
}
此题与PAT B1037有些类似，但是按照那个写法无法通过（18/20）
看了算法笔记的代码，再百度了一下，还是贴一个我觉得简单的AC吧
#include "stdio.h"
const int Galleon = 17;
const int Sickle = 29;
int main(){
int a1, a2, a3;
int b1, b2, b3;
scanf("%d.%d.%d %d.%d.%d", &a1, &a2, &a3, &b1, &b2, &b3);
//处理Knuts进位
a3 += b3;
a2 += a3 / Sickle;
a3 %= Sickle;
//处理Sickle进位
a2 += b2;
a1 += a2 / Galleon;
a2 %= Galleon;
//处理Galleon
a1 += b1;
printf("%d.%d.%d", a1, a2, a3);
return 0;
}
| 29.059701 | 445 | 0.587057 | eng_Latn | 0.952533 |
fdf6b8dc513b7320984168e8c23a666839749dd6 | 843 | md | Markdown | user/pages/18.remmina-plugin-webkit/01.index/item.it.md | muflone/grav-muflone | 7417022e2f83ef1e890e0c7e1b614d5b54c3d4d1 | [
"MIT"
] | null | null | null | user/pages/18.remmina-plugin-webkit/01.index/item.it.md | muflone/grav-muflone | 7417022e2f83ef1e890e0c7e1b614d5b54c3d4d1 | [
"MIT"
] | null | null | null | user/pages/18.remmina-plugin-webkit/01.index/item.it.md | muflone/grav-muflone | 7417022e2f83ef1e890e0c7e1b614d5b54c3d4d1 | [
"MIT"
] | null | null | null | ---
title: Introduzione
product: remmina-plugin-webkit
depth: 1
---
# Descrizione
**Remmina Plugin WebKit** è un plugin di protocollo libero per aprire una pagina web utilizzando un browser integrato basato su GTK+ WebKit. Diventa utile quando è necessario accedere alle risorse dalla finestra di Remmina, come avere accesso alle pagine web di amministrazione di router, stampanti e altre risorse in rete.
[muflone-install type="index" package="remmina-plugin-webkit" name="Remmina Plugin WebKit"][/muflone-install]
# Impostazioni
Le impostazioni del plugin Remmina Plugin WebKit sono documentate nella [pagina Impostazioni](../settings).
[muflone-license type="index" package="remmina-plugin-webkit" name="Remmina Plugin WebKit"][/muflone-license]
| 44.368421 | 323 | 0.792408 | ita_Latn | 0.976776 |
fdf7f7d931370779b2a5053a37efeec9b66b3888 | 304 | md | Markdown | Documentation/release/dev/remove-vtkExtractHistogram.md | tornado12345/ParaView | 4148d68eb7edf4ba2ab0a8ace33534bd616aea69 | [
"Apache-2.0",
"BSD-3-Clause"
] | null | null | null | Documentation/release/dev/remove-vtkExtractHistogram.md | tornado12345/ParaView | 4148d68eb7edf4ba2ab0a8ace33534bd616aea69 | [
"Apache-2.0",
"BSD-3-Clause"
] | null | null | null | Documentation/release/dev/remove-vtkExtractHistogram.md | tornado12345/ParaView | 4148d68eb7edf4ba2ab0a8ace33534bd616aea69 | [
"Apache-2.0",
"BSD-3-Clause"
] | null | null | null | # Remove vtkExtractHistogram from paraview project
'vtkExtractHistogram' has been moved upstream into the VTK project. Hence it
has been removed from the paraview project. The 'vtkPExtractHistogram' subclass
has been modified to reflect the normalize/accumulate features added to
'vtkExtractHistogram'.
| 43.428571 | 79 | 0.835526 | eng_Latn | 0.996598 |
fdf89613de96f14ba3cae79b18b7618af45684a8 | 1,308 | md | Markdown | README.md | leminhquang11/Ruby | 153f7d79dd67da98e2cc3d9a975de2cb2d9e04c6 | [
"Beerware"
] | null | null | null | README.md | leminhquang11/Ruby | 153f7d79dd67da98e2cc3d9a975de2cb2d9e04c6 | [
"Beerware"
] | 38 | 2019-12-22T06:12:58.000Z | 2022-03-31T00:23:30.000Z | README.md | leminhquang11/Ruby | 153f7d79dd67da98e2cc3d9a975de2cb2d9e04c6 | [
"Beerware"
] | null | null | null | Le Minh Quang - 20163293 - HEDSPI - HUST
Ruby on Rails Tutorial sample application
All source code in the Ruby on Rails Tutorial is available jointly under the MIT License and the Beerware License. See LICENSE.md for details.
Getting started
ruby 2.5.5
Rails 5.2.4
To get started with the app, clone the repo and then install the needed gems:
$ bundle install --without production
Next, migrate the database:
$ rails db:migrate
Finally, run the test suite to verify that everything is working correctly:
$ rails test
If the test suite passes, you'll be ready to run the app in a local server:
$ rails server
For more information, see the Ruby on Rails Tutorial book.
# Weekly exercise description on commit
* Week 1: complete fizz-buzz, prime number, quadratic equation exercise
* Week 2: complete chapter 1
*simple_app:
* Week 3: complete chapter 2, show microposts in user's page, add select box
* Week 4: complete chapter 3, 4, 5, add static pages, layout
* Week 5: complete chapter 6, 7, 8, add signin, signup, facebook's login
* Week 6: complete chapter 9, add remember me
* Week 7: complete chapter 10, authorization
* Week 8: complete chapter 11, send mail
* Week 9: complete chapter 12, send reset password
* Week 10: complete chapter 13, 14, add microposts, following users
| 29.066667 | 142 | 0.754587 | eng_Latn | 0.981162 |
fdf89997d6c774fc6f83bb655aa786d3d4105507 | 3,856 | md | Markdown | kubernetes/README.md | meijies/ballista | 8954c29ee3edc8d71e77c850c91fc6f677ef9c08 | [
"Apache-2.0"
] | null | null | null | kubernetes/README.md | meijies/ballista | 8954c29ee3edc8d71e77c850c91fc6f677ef9c08 | [
"Apache-2.0"
] | null | null | null | kubernetes/README.md | meijies/ballista | 8954c29ee3edc8d71e77c850c91fc6f677ef9c08 | [
"Apache-2.0"
] | null | null | null | # Deploying Ballista to Kubernetes
This document explains how to create a Ballista cluster in Kubernetes.
## Generic kubernetes
This guide assumes that we have a kubernetes cluster and our role has permissions to:
* list and create pods
* list and create secrets
* list and create persistent volumes and claims
* create ClusterRole and ClusterRoleBinding
on the namespace `default`.
### Deploy volumes and write data to it
For this guide, we will create a persistent volume and claim and write data to it, which we can then query through Ballista.
To do so, run
```bash
kubectl apply -f kubernetes/pv.yaml
```
and check that its status and the claim status is "Bound":
```
kubectl get pv
kubectl get pvc
```
Next, we will spawn a pod to download data from s3 and write to the persistent volume:
```bash
kubectl apply -f kubernetes/populate-data.yaml
```
This operation takes some time as we have some data to download. This is done when the pod `populate-data` on `kubectl get pods`
shows status `Completed`. We can't deploy the cluster before this step is completed, as the volume can only be claimed by
a single pod at the time. Feel free to change [populate-data.yaml](./populate-data.yaml) do dump a smaller CSV.
### Setup credentials for pulling images
We offer docker images on github that we can use to run the cluster.
They require authentication to be pulled. For this, we will create a secret in k8s:
```bash
kubectl create secret docker-registry github \
--docker-server=docker.pkg.github.com \
--docker-username=$GITHUB_USERNAME \
--docker-password=$GITHUB_TOKEN \
--docker-email=jorgecarleitao@gmail.com
```
where `$GITHUB_TOKEN` is an [OAuth token](https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token) for your `$USERNAME`.
### Give the cluster permissions to list pods
```bash
kubectl apply -f kubernetes/rbac.yaml
```
This gives all pods running on namespace `default` permissions to list pods from the cluster's API
and is necessary for scheduling.
### Deploy Ballista
Once `populate-data` completes, we can bring the cluster up. For this, run
```bash
kubectl apply -f kubernetes/ballista-cluster.yaml
```
We can check the status with `kubectl get pods` and `kubectl logs ballista-0`.
This deploys two replicas and a service on port `50051`.
At this point, we can connect remotely with this port to run queries against the cluster.
A simple method to connect to it is to port-forward to our local machine:
```bash
kubectl port-forward service/ballista 50051:50051
```
and connect to this port to run queries against the cluster. In particular,
we can use [this example](../rust/examples/distributed-query) to query the cluster.
### Customization
The procedure above is a minimal setup to deploy ballista on kubernetes. From here, we can just change any configuration above
to our needs. In particular, we can use the image name from `ballistacompute/ballista-rust` to `ballistacompute/ballista-jvm` or `ballistacompute/ballista-spark` to use a different executor.
## Deploy on minikube
For local development, we can also use minikube. We can set it up exactly the same way, but since
minikube runs locally, we can simplify the deployment a bit:
First, we can use docker images from our own docker deamon,
```bash
eval $(minikube -p minikube docker-env)
minikube start --driver=docker
```
which does not require setting up a github access token.
Secondly, we can use a local mounted volume before creating a persistent volume:
```bash
minikube mount /mnt/:/mnt/
```
This way, we can download the data to our computer and place it in the mounted volume.
## Teardown
To revert all the steps above, we run `kubectl delete -f` on each of the files above. To delete the secret used
to download images, run
```bash
kubectl delete secret github
```
| 31.606557 | 190 | 0.761929 | eng_Latn | 0.993843 |
fdf8dfc2946285459c17eb8db8b83344a6b65ff4 | 863 | md | Markdown | ce/developer/clientapi/reference/events/form-onload.md | astockli/dynamics-365-customer-engagement | 6928051e68cd1a98a52678263b712dcd2d4bc40a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ce/developer/clientapi/reference/events/form-onload.md | astockli/dynamics-365-customer-engagement | 6928051e68cd1a98a52678263b712dcd2d4bc40a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ce/developer/clientapi/reference/events/form-onload.md | astockli/dynamics-365-customer-engagement | 6928051e68cd1a98a52678263b712dcd2d4bc40a | [
"CC-BY-4.0",
"MIT"
] | 4 | 2022-02-10T04:56:47.000Z | 2022-02-10T07:32:49.000Z | ---
title: "Form OnLoad Event (Client API reference) in Dynamics 365 Customer Engagement| MicrosoftDocs"
ms.date: 10/31/2017
ms.service: "crm-online"
ms.topic: "reference"
applies_to: "Dynamics 365 (online)"
ms.assetid: 89123cde-7c66-4c7d-94e4-e287285019f8
author: "KumarVivek"
ms.author: "kvivek"
manager: "amyla"
search.audienceType:
- developer
search.app:
- D365CE
---
# Form OnLoad Event (Client API reference)
[!INCLUDE[](../../../../includes/cc_applies_to_update_9_0_0.md)]
The form `OnLoad` event occurs after the form has loaded. It cannot prevent the window from loading. Use the `OnLoad` event to apply logic about how the form should be displayed, to set properties on fields, and interact with other page elements.
When the Microsoft Dynamics 365 for tablets client is disconnected, the `OnLoad` event is the only event that will occur.
| 33.192308 | 246 | 0.755504 | eng_Latn | 0.951114 |
fdfa43ea676052e7b90c984c8f62eda15bf659a5 | 4,118 | md | Markdown | ru/iam/best-practices/using-iam-securely.md | anton-bryukhov/docs | 8fb69a121137c195745c17cc1e7f0cc68169edec | [
"CC-BY-4.0"
] | null | null | null | ru/iam/best-practices/using-iam-securely.md | anton-bryukhov/docs | 8fb69a121137c195745c17cc1e7f0cc68169edec | [
"CC-BY-4.0"
] | null | null | null | ru/iam/best-practices/using-iam-securely.md | anton-bryukhov/docs | 8fb69a121137c195745c17cc1e7f0cc68169edec | [
"CC-BY-4.0"
] | null | null | null | # Безопасное использование Яндекс.Облака
В разделе представлены рекомендации по использованию возможностей сервиса {{ iam-short-name }} для обеспечения безопасной работы с сервисами Яндекс.Облака.
## Не давайте лишних прав доступа {#restrict-access}
Для критически важных ресурсов:
* Назначайте минимально необходимые для работы [роли](../concepts/access-control/roles.md). Например, чтобы в {{ compute-name }} разрешить использовать образы для создания виртуальных машин, [назначьте роль](../operations/roles/grant.md) `compute.images.user`, а не `editor` или выше.
* Старайтесь назначать сервисные роли вместо примитивных (`viewer`, `editor`, `admin`). Примитивные роли действуют для ресурсов любого из сервисов Яндекс.Облака.
Используйте примитивные роли, если нет подходящей сервисной роли или вы хотите дать пользователю широкие полномочия.
* Назначайте только роли, которые необходимы сейчас. Не назначайте роли, которые могут потребоваться только в будущем.
* Помните, что когда вы назначаете роль на каталог или облако, разрешения этой роли [унаследуют все вложенные ресурсы](../concepts/access-control/index.md#inheritance).
* Назначайте роли [администратора](../concepts/access-control/roles.md#admin) и [владельца облака](../concepts/access-control/roles.md#owner) только тем, кто должен управлять доступом к ресурсам в вашем проекте.
Администратор может лишить прав доступа другого администратора, а владелец — отозвать у другого владельца его роль. Еще эти роли включают все разрешения роли `editor` — они позволяют создавать, изменять и удалять ресурсы.
## Защитите свой аккаунт на Яндексе {#protect-account}
* {% include [yandex-account-2fa-warning.md](../../_includes/iam/yandex-account-2fa-warning.md) %}
* Держите в секрете ваш [OAuth-токен](../concepts/authorization/oauth-token.md), с его помощью можно получить [IAM-токен](../concepts/authorization/iam-token.md) и выполнять любые операции в облаке от вашего имени.
Если кто-то мог узнать ваш OAuth-токен, [отзовите его](https://yandex.ru/dev/oauth/doc/dg/reference/token-invalidate-docpage/) и выпустите новый.
* Старайтесь не использовать OAuth-токен для аутентификации, если можно использовать IAM-токен. OAuth-токен действует 1 год, а IAM-токен — {{ iam-token-lifetime }}. Если ваш токен будет скомпрометирован, у злоумышленника будет ограниченное время, чтобы воспользоваться им.
## Используйте сервисные аккаунты {#use-sa}
Используйте [сервисные аккаунты](../concepts/users/service-accounts.md) для автоматизации работы с Яндекс.Облаком и следуйте этим рекомендациям:
* Контролируйте доступ к вашим сервисным аккаунтам. Роль `editor` на сервисный аккаунт позволит пользователю выполнять операции, разрешенные этому сервисному аккаунту. Если сервисный аккаунт — администратор в облаке, то пользователь сможет сделать себя администратором с его помощью.
* Создавайте отдельные сервисные аккаунты для выполнения разных задач. Так вы сможете назначить им только те роли, которые необходимы. В любой момент вы сможете отозвать роли у сервисного аккаунта или удалить его, не затронув другие аккаунты.
* Давайте сервисным аккаунтам имена, которые позволят понять, для чего аккаунт используется и какие разрешения он должен иметь.
* Держите в секрете [ключи сервисного аккаунта](../concepts/users/service-accounts#sa-key) — с их помощью можно выполнять операции от имени сервисного аккаунта. Не храните ключи сервисного аккаунта в исходном коде.
Периодически отзывайте старые ключи и выпускайте новые. Особенно если кто-то мог узнать ваш секретный ключ.
* Не используйте ключи для аутентификации, если можно использовать [IAM-токен](../concepts/authorization/iam-token.md). Срок жизни ключей неограничен, а IAM-токен действует {{ iam-token-lifetime }}.
* Если вы выполняете операции изнутри виртуальной машины, [привяжите к ней сервисный аккаунт](../../compute/operations/vm-connect/auth-inside-vm.md). Тогда для аутентификации не нужно хранить ключи сервисного аккаунта на виртуальной машине — IAM-токен будет доступен [по ссылке на сервис метаданных](../../compute/operations/vm-connect/auth-inside-vm#auth-inside-vm). | 108.368421 | 367 | 0.797232 | rus_Cyrl | 0.973543 |
fdfa853b31029fab21a92fff45548bd57d1c85ff | 2,064 | md | Markdown | C15-Dynamic-Programming/15.1.md | rasoolianbehnam/CLRS | db68425d4f6abaac19cdc352fa3f2f1baf205fdc | [
"MIT"
] | 9,395 | 2015-05-24T02:23:43.000Z | 2022-03-31T18:47:19.000Z | C15-Dynamic-Programming/15.1.md | WoodyLinwc/CLRS | b7d3df5ba834b2a15007d0f0fc320f1dfc9f4041 | [
"MIT"
] | 198 | 2015-07-16T00:03:43.000Z | 2022-03-30T12:58:21.000Z | C15-Dynamic-Programming/15.1.md | WoodyLinwc/CLRS | b7d3df5ba834b2a15007d0f0fc320f1dfc9f4041 | [
"MIT"
] | 3,340 | 2015-05-25T04:10:33.000Z | 2022-03-31T00:23:19.000Z | ### Exercises 15.1-1
***
Show how to modify the PRINT-STATIONS procedure to print out the stations in increasing order of station number. (Hint: Use recursion.)
### `Answer`
It's very easy. See my [implementation](./Assembly-line-sche.c)
### Exercises 15.1-2
***
Use equations (15.8) and (15.9) and the substitution method to show that ri(j), the number of references made to fi[j] in a recursive algorithm, equals 2^(n - j).
### `Answer`
1. j = n时,r(i,j) = 1 = 2^(n-n) 成立
2. 假设当j = k时, r(i,k) = 2^(n-k) <br \>
当j = k -1时, r(i,k-1) = r(1,k)+r(2,k) = 2^(n-k) + 2^(n-k) = 2^(n-(k-1))
3. 综上所述, 等式成立
### Exercises 15.1-3
***
Using the result of Exercise 15.1-2, show that the total number of references to all fi[j] values, or 
)
, is exactly 2^(n+1) - 2.
### `Answer`
%0d%0a=%202\(\\sum_{j=1}^{n}2^{n-j}\)%20=%202\(2^n-1\)%20=%202^{n+1}-1)
### Exercises 15.1-4
***
Together, the tables containing fi[j] and li[j] values contain a total of 4n - 2 entries. Show how to reduce the space requirements to a total of 2n + 2 entries, while still computing f* and still being able to print all the stations on a fastest way through the factory.
### `Answer`
It's simple. When we calculate f(n),we just need f(n-1).so we just alloc f1[2] and f2[2].
### Exercises 15.1-5
***
Professor Canty conjectures that there might exist some ei, ai,j, and ti,j values for which FASTEST-WAY produces li[j] values such that l1[j] = 2 and l2[j] = 1 for some station number j. Assuming that all transfer costs ti,j are nonnegative, show that the professor is wrong.
### `Answer`
if l1[j] = 2,then f1[j-1]>f2[j-1]+t(2,j-1) ------ @1
if l2[j] = 1,then f2[j-1]>f1[j-1]+t(1,j-1) ------ @2
we add @1 and @2,find that t(1,j-1)+t(2,j-1) < 0 wrong !!!!!!
***
Follow [@louis1992](https://github.com/gzc) on github to help finish this task.
| 36.210526 | 276 | 0.618217 | eng_Latn | 0.96048 |
fdfbb3282cfff320eb7966ef47016e2beffaa8f8 | 2,141 | md | Markdown | README.md | Mitulsharma123/CKAD-exercises | 0c317764e89aeff6b6e539253e8dbbdd96ec087f | [
"MIT"
] | null | null | null | README.md | Mitulsharma123/CKAD-exercises | 0c317764e89aeff6b6e539253e8dbbdd96ec087f | [
"MIT"
] | null | null | null | README.md | Mitulsharma123/CKAD-exercises | 0c317764e89aeff6b6e539253e8dbbdd96ec087f | [
"MIT"
] | null | null | null | [](LICENSE)
[](http://makeapullrequest.com)
[](https://github.com/dgkanatsios/gaforgithub)
# CKAD Exercises
A set of exercises that helped me prepare for the [Certified Kubernetes Application Developer](https://www.cncf.io/certification/ckad/) exam, offered by the Cloud Native Computing Foundation, organized by curriculum domain. They may as well serve as learning and practicing with Kubernetes.
During the exam, you are allowed to keep only one other browser tab open to refer to official documentation. Make a mental note of the breadcrumb at the start of the excercise section, to quickly locate the relevant document in kubernetes.io. It is recommended that you read the official documents before attempting exercises below it.
## Contents
- [Core Concepts - 13%](a.core_concepts.md)
- [Multi-container pods - 10%](b.multi_container_pods.md)
- [Pod design - 20%](c.pod_design.md)
- [Configuration - 18%](d.configuration.md)
- [Observability - 18%](e.observability.md)
- [Services and networking - 13%](f.services.md)
- [State persistence - 8%](g.state.md)
- [helm](h.helm.md)
- [Custom Resource Definitions](i.crd.md)
> If your work is related to multiplayer game servers, checkout out [thundernetes, a brand new project to host game servers on Kubernetes](https://github.com/PlayFab/thundernetes)!
### Can I PR? There is an error/an alternative way/an extra question/solution I can offer
Absolutely! Feel free to PR and edit/add questions and solutions, but please stick to the existing format.
If this repo has helped you in any way, feel free to post on [discussions](https://github.com/dgkanatsios/CKAD-exercises/discussions) or buy me a coffee!
<a href="https://www.buymeacoffee.com/dgkanatsios" target="_blank"><img src="https://cdn.buymeacoffee.com/buttons/default-orange.png" alt="Buy Me A Coffee" height="41" width="174"></a>
| 66.90625 | 335 | 0.7688 | eng_Latn | 0.910746 |
fdfca36330a737c3423924125736d038cc9da144 | 22,904 | md | Markdown | articles/active-directory/managed-identities-azure-resources/services-support-managed-identities.md | IrisClasson/azure-docs.sv-se | a6a2b03ee9a98c9e3708bf0df9f77628db79f1f6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/managed-identities-azure-resources/services-support-managed-identities.md | IrisClasson/azure-docs.sv-se | a6a2b03ee9a98c9e3708bf0df9f77628db79f1f6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/managed-identities-azure-resources/services-support-managed-identities.md | IrisClasson/azure-docs.sv-se | a6a2b03ee9a98c9e3708bf0df9f77628db79f1f6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Azure-tjänster som har stöd för hanterade identiteter – Azure AD
description: Lista över tjänster som stöder hanterade identiteter för Azure-resurser och Azure AD-autentisering
services: active-directory
author: MarkusVi
ms.author: markvi
ms.date: 07/09/2020
ms.topic: conceptual
ms.service: active-directory
ms.subservice: msi
manager: markvi
ms.collection: M365-identity-device-management
ms.custom: references_regions
ms.openlocfilehash: 13521017076c609c2fadb4362d5cccdf12d94098
ms.sourcegitcommit: dea88d5e28bd4bbd55f5303d7d58785fad5a341d
ms.translationtype: MT
ms.contentlocale: sv-SE
ms.lasthandoff: 08/06/2020
ms.locfileid: "87873593"
---
# <a name="services-that-support-managed-identities-for-azure-resources"></a>Tjänster som stöder hanterade identiteter för Azure-resurser
Hanterade identiteter för Azure-resurser ger Azure-tjänster en automatiskt hanterad identitet i Azure Active Directory. Med hjälp av en hanterad identitet kan du autentisera till en tjänst som stöder Azure AD-autentisering utan att ha autentiseringsuppgifter i din kod. Vi håller på att integrera hanterade identiteter för Azure-resurser och Azure AD-autentisering i Azure. Kom tillbaka ofta för uppdateringar.
> [!NOTE]
> Hanterade identiteter för Azure-resurser är det nya namnet på tjänsten som tidigare hade namnet Hanterad tjänstidentitet (MSI).
## <a name="azure-services-that-support-managed-identities-for-azure-resources"></a>Azure-tjänster som stöder hanterade identiteter för Azure-resurser
Följande Azure-tjänster har stöd för hanterade identiteter för Azure-resurser:
### <a name="azure-api-management"></a>Azure API Management
Hanterad identitets typ | Alla allmänt tillgängliga<br>Globala Azure-regioner | Azure Government | Azure Tyskland | Azure Kina 21Vianet |
| --- | :-: | :-: | :-: | :-: |
| Systemtilldelad | ![Tillgänglig][check] | ![Tillgänglig][check] | Inte tillgängligt | ![Tillgänglig][check] |
| Användartilldelad | Förhandsgranskning | Förhandsgranskning | Inte tillgängligt | Förhandsgranskning |
I följande lista kan du konfigurera hanterad identitet för Azure API Management (i regioner där det är tillgängligt):
- [Azure Resource Manager mall](/azure/api-management/api-management-howto-use-managed-service-identity)
### <a name="azure-app-service"></a>Azure App Service
| Hanterad identitets typ | Alla allmänt tillgängliga<br>Globala Azure-regioner | Azure Government | Azure Tyskland | Azure Kina 21Vianet |
| --- | :-: | :-: | :-: | :-: |
| Systemtilldelad | ![Tillgänglig][check] | ![Tillgänglig][check] | ![Tillgänglig][check] | ![Tillgänglig][check] |
| Användartilldelad | ![Tillgänglig][check] | ![Tillgänglig][check] | ![Tillgänglig][check] | ![Tillgänglig][check] |
I följande lista kan du konfigurera hanterad identitet för Azure App Service (i regioner där det finns tillgängligt):
- [Azure-portalen](/azure/app-service/overview-managed-identity#using-the-azure-portal)
- [Azure CLI](/azure/app-service/overview-managed-identity#using-the-azure-cli)
- [Azure PowerShell](/azure/app-service/overview-managed-identity#using-azure-powershell)
- [Azure Resource Manager mall](/azure/app-service/overview-managed-identity#using-an-azure-resource-manager-template)
### <a name="azure-arc-enabled-kubernetes"></a>Azure Arc-aktiverade Kubernetes
| Hanterad identitets typ | Alla allmänt tillgängliga<br>Globala Azure-regioner | Azure Government | Azure Tyskland | Azure Kina 21Vianet |
| --- | :-: | :-: | :-: | :-: |
| Systemtilldelad | Förhandsgranskning | Inte tillgänglig | Inte tillgänglig | Inte tillgänglig |
| Användartilldelad | Inte tillgänglig | Inte tillgänglig | Inte tillgänglig | Inte tillgänglig |
Azure Arc-aktiverade Kubernetes [stöder för närvarande systemtilldelad identitet](https://docs.microsoft.com/azure/azure-arc/kubernetes/connect-cluster#azure-arc-agents-for-kubernetes). Det hanterade tjänst identitets certifikatet används av alla Azure Arc-aktiverade Kubernetes-agenter för kommunikation med Azure.
### <a name="azure-blueprints"></a>Azure Blueprint
|Hanterad identitets typ | Alla allmänt tillgängliga<br>Globala Azure-regioner | Azure Government | Azure Tyskland | Azure Kina 21Vianet |
| --- | :-: | :-: | :-: | :-: |
| Systemtilldelad | ![Tillgänglig][check] | ![Tillgänglig][check] | Inte tillgänglig | Inte tillgänglig |
| Användartilldelad | ![Tillgänglig][check] | ![Tillgänglig][check] | Inte tillgänglig | Inte tillgänglig |
Se följande lista för att använda en hanterad identitet med [Azure-skisser](../../governance/blueprints/overview.md):
- [Azure Portal skiss tilldelning](../../governance/blueprints/create-blueprint-portal.md#assign-a-blueprint)
- [REST API skiss tilldelning](../../governance/blueprints/create-blueprint-rest-api.md#assign-a-blueprint)
### <a name="azure-cognitive-search"></a>Azure Cognitive Search
Hanterad identitets typ | Alla allmänt tillgängliga<br>Globala Azure-regioner | Azure Government | Azure Tyskland | Azure Kina 21Vianet |
| --- | :-: | :-: | :-: | :-: |
| Systemtilldelad | ![Tillgänglig][check] | ![Tillgänglig][check] | Inte tillgängligt | ![Tillgänglig][check] |
| Användartilldelad | Inte tillgänglig | Inte tillgänglig | Inte tillgänglig | Inte tillgänglig |
### <a name="azure-cognitive-services"></a>Azure Cognitive Services
Hanterad identitets typ | Alla allmänt tillgängliga<br>Globala Azure-regioner | Azure Government | Azure Tyskland | Azure Kina 21Vianet |
| --- | :-: | :-: | :-: | :-: |
| Systemtilldelad | ![Tillgänglig][check] | ![Tillgänglig][check] | Inte tillgängligt | ![Tillgänglig][check] |
| Användartilldelad | Inte tillgänglig | Inte tillgänglig | Inte tillgänglig | Inte tillgänglig |
### <a name="azure-container-instances"></a>Azure Container Instances
Hanterad identitets typ | Alla allmänt tillgängliga<br>Globala Azure-regioner | Azure Government | Azure Tyskland | Azure Kina 21Vianet |
| --- | :-: | :-: | :-: | :-: |
| Systemtilldelad | Linux: för hands version<br>Windows: inte tillgängligt | Inte tillgänglig | Inte tillgänglig | Inte tillgänglig |
| Användartilldelad | Linux: för hands version<br>Windows: inte tillgängligt | Inte tillgänglig | Inte tillgänglig | Inte tillgänglig |
I följande lista kan du konfigurera hanterad identitet för Azure Container Instances (i regioner där det finns tillgängligt):
- [Azure CLI](~/articles/container-instances/container-instances-managed-identity.md)
- [Azure Resource Manager mall](~/articles/container-instances/container-instances-managed-identity.md#enable-managed-identity-using-resource-manager-template)
- [YAML](~/articles/container-instances/container-instances-managed-identity.md#enable-managed-identity-using-yaml-file)
### <a name="azure-container-registry-tasks"></a>Azure Container Registry Tasks
Hanterad identitets typ | Alla allmänt tillgängliga<br>Globala Azure-regioner | Azure Government | Azure Tyskland | Azure Kina 21Vianet |
| --- | :-: | :-: | :-: | :-: |
| Systemtilldelad | ![Tillgänglig][check] | Inte tillgänglig | Inte tillgänglig | Inte tillgänglig |
| Användartilldelad | Förhandsgranskning | Inte tillgänglig | Inte tillgänglig | Inte tillgänglig |
I följande lista kan du konfigurera hanterad identitet för Azure Container Registry uppgifter (i regioner där det är tillgängligt):
- [Azure CLI](~/articles/container-registry/container-registry-tasks-authentication-managed-identity.md)
### <a name="azure-data-explorer"></a>Azure-datautforskaren
Hanterad identitets typ | Alla allmänt tillgängliga<br>Globala Azure-regioner | Azure Government | Azure Tyskland | Azure Kina 21Vianet |
| --- | :-: | :-: | :-: | :-: |
| Systemtilldelad | ![Tillgänglig][check] | ![Tillgänglig][check] | Inte tillgängligt | ![Tillgänglig][check] |
| Användartilldelad | Inte tillgänglig | Inte tillgänglig | Inte tillgänglig | Inte tillgänglig |
### <a name="azure-data-factory-v2"></a>Azure Data Factory V2
Hanterad identitets typ | Alla allmänt tillgängliga<br>Globala Azure-regioner | Azure Government | Azure Tyskland | Azure Kina 21Vianet |
| --- | :-: | :-: | :-: | :-: |
| Systemtilldelad | ![Tillgänglig][check] | ![Tillgänglig][check] | Inte tillgängligt | ![Tillgänglig][check] |
| Användartilldelad | Inte tillgänglig | Inte tillgänglig | Inte tillgänglig | Inte tillgänglig |
I följande lista kan du konfigurera hanterad identitet för Azure Data Factory v2 (i regioner där det finns):
- [Azure-portalen](~/articles/data-factory/data-factory-service-identity.md#generate-managed-identity)
- [PowerShell](~/articles/data-factory/data-factory-service-identity.md#generate-managed-identity-using-powershell)
- [REST](~/articles/data-factory/data-factory-service-identity.md#generate-managed-identity-using-rest-api)
- [SDK](~/articles/data-factory/data-factory-service-identity.md#generate-managed-identity-using-sdk)
### <a name="azure-event-grid"></a>Azure Event Grid
Hanterad identitets typ |Alla allmänt tillgängliga<br>Globala Azure-regioner | Azure Government | Azure Tyskland | Azure Kina 21Vianet |
| --- | :-: | :-: | :-: | :-: |
| Systemtilldelad | Förhandsgranskning | Förhandsgranskning | Inte tillgängligt | Förhandsgranskning |
| Användartilldelad | Inte tillgänglig | Inte tillgänglig | Inte tillgänglig | Inte tillgänglig |
### <a name="azure-functions"></a>Azure Functions
Hanterad identitets typ |Alla allmänt tillgängliga<br>Globala Azure-regioner | Azure Government | Azure Tyskland | Azure Kina 21Vianet |
| --- | :-: | :-: | :-: | :-: |
| Systemtilldelad | ![Tillgänglig][check] | ![Tillgänglig][check] | ![Tillgänglig][check] | ![Tillgänglig][check] |
| Användartilldelad | ![Tillgänglig][check] | ![Tillgänglig][check] | ![Tillgänglig][check] | ![Tillgänglig][check] |
I följande lista kan du konfigurera hanterad identitet för Azure Functions (i regioner där det finns tillgängligt):
- [Azure-portalen](/azure/app-service/overview-managed-identity#using-the-azure-portal)
- [Azure CLI](/azure/app-service/overview-managed-identity#using-the-azure-cli)
- [Azure PowerShell](/azure/app-service/overview-managed-identity#using-azure-powershell)
- [Azure Resource Manager mall](/azure/app-service/overview-managed-identity#using-an-azure-resource-manager-template)
### <a name="azure-iot-hub"></a>Azure IoT Hub
Hanterad identitets typ | Alla allmänt tillgängliga<br>Globala Azure-regioner | Azure Government | Azure Tyskland | Azure Kina 21Vianet |
| --- | :-: | :-: | :-: | :-: |
| Systemtilldelad | ![Tillgänglig][check] | ![Tillgänglig][check] | Inte tillgängligt | ![Tillgänglig][check] |
| Användartilldelad | Inte tillgänglig | Inte tillgänglig | Inte tillgänglig | Inte tillgänglig |
I följande lista kan du konfigurera hanterad identitet för Azure Data Factory v2 (i regioner där det finns):
- [Azure-portalen](../../iot-hub/virtual-network-support.md#turn-on-managed-identity-for-iot-hub)
### <a name="azure-importexport"></a>Azure Import/Export
Hanterad identitets typ | Alla allmänt tillgängliga<br>Globala Azure-regioner | Azure Government | Azure Tyskland | Azure Kina 21Vianet |
| --- | --- | --- | --- | --- |
| Systemtilldelad | Tillgängligt i regionen där Azure import export-tjänsten är tillgänglig | Förhandsgranskning | Tillgänglig | Tillgänglig |
| Användartilldelad | Inte tillgänglig | Inte tillgänglig | Inte tillgänglig | Inte tillgänglig |
### <a name="azure-kubernetes-service-aks"></a>Azure Kubernetes Service (AKS)
| Hanterad identitets typ | Alla allmänt tillgängliga<br>Globala Azure-regioner | Azure Government | Azure Tyskland | Azure Kina 21Vianet |
| --- | :-: | :-: | :-: | :-: |
| Systemtilldelad | ![Tillgänglig][check] | ![Tillgänglig][check] | Inte tillgängligt | ![Tillgänglig][check] |
| Användartilldelad | ![Tillgänglig][check] | ![Tillgänglig][check] | Inte tillgängligt | ![Tillgänglig][check] |
Mer information finns i [använda hanterade identiteter i Azure Kubernetes-tjänsten](https://docs.microsoft.com/azure/aks/use-managed-identity).
### <a name="azure-logic-apps"></a>Azure Logic Apps
Hanterad identitets typ | Alla allmänt tillgängliga<br>Globala Azure-regioner | Azure Government | Azure Tyskland | Azure Kina 21Vianet |
| --- | :-: | :-: | :-: | :-: |
| Systemtilldelad | ![Tillgänglig][check] | ![Tillgänglig][check] | Inte tillgängligt | ![Tillgänglig][check] |
| Användartilldelad | ![Tillgänglig][check] | ![Tillgänglig][check] | Inte tillgängligt | ![Tillgänglig][check] |
I följande lista kan du konfigurera hanterad identitet för Azure Logic Apps (i regioner där det finns tillgängligt):
- [Azure-portalen](/azure/logic-apps/create-managed-service-identity#enable-system-assigned-identity-in-azure-portal)
- [Azure Resource Manager mall](https://docs.microsoft.com/azure/logic-apps/logic-apps-azure-resource-manager-templates-overview)
### <a name="azure-policy"></a>Azure Policy
|Hanterad identitets typ | Alla allmänt tillgängliga<br>Globala Azure-regioner | Azure Government | Azure Tyskland | Azure Kina 21Vianet |
| --- | :-: | :-: | :-: | :-: |
| Systemtilldelad | ![Tillgänglig][check] | ![Tillgänglig][check] | ![Tillgänglig][check] | ![Tillgänglig][check] |
| Användartilldelad | Inte tillgänglig | Inte tillgänglig | Inte tillgänglig | Inte tillgänglig |
I följande lista kan du konfigurera hanterad identitet för Azure Policy (i regioner där det finns tillgängligt):
- [Azure-portalen](../../governance/policy/tutorials/create-and-manage.md#assign-a-policy)
- [PowerShell](../../governance/policy/how-to/remediate-resources.md#create-managed-identity-with-powershell)
- [Azure CLI](https://docs.microsoft.com/cli/azure/policy/assignment?view=azure-cli-latest#az-policy-assignment-create)
- [Azure Resource Manager-mallar](https://docs.microsoft.com/azure/templates/microsoft.authorization/policyassignments)
- [REST](https://docs.microsoft.com/rest/api/resources/policyassignments/create)
### <a name="azure-service-fabric"></a>Azure Service Fabric
[Hanterad identitet för Service Fabric program](https://docs.microsoft.com/azure/service-fabric/concepts-managed-identity) är tillgänglig i alla regioner.
Hanterad identitets typ | Alla allmänt tillgängliga<br>Globala Azure-regioner | Azure Government | Azure Tyskland | Azure Kina 21Vianet |
| --- | :-: | :-: | :-: | :-: |
| Systemtilldelad | ![Tillgänglig][check] | Inte tillgängligt | Inte tillgängligt | inte tillgängligt |
| Användartilldelad | ![Tillgänglig][check] | Inte tillgängligt | Inte tillgängligt |Inte tillgängligt |
Se följande lista för att konfigurera hanterad identitet för Azure Service Fabric-program i alla regioner:
- [Azure Resource Manager mall](https://github.com/Azure-Samples/service-fabric-managed-identity/tree/anmenard-docs)
### <a name="azure-spring-cloud"></a>Azure Spring Cloud
| Hanterad identitets typ | Alla allmänt tillgängliga<br>Globala Azure-regioner | Azure Government | Azure Tyskland | Azure Kina 21Vianet |
| --- | :-: | :-: | :-: | :-: |
| Systemtilldelad | ![Tillgänglig][check] | Inte tillgängligt | Inte tillgängligt | Inte tillgängligt |
| Användartilldelad | Inte tillgängligt | Inte tillgängligt | Inte tillgängligt | Inte tillgängligt |
Mer information finns i [så här aktiverar du systemtilldelad hanterad identitet för Azure våren Cloud Application](~/articles/spring-cloud/spring-cloud-howto-enable-system-assigned-managed-identity.md).
### <a name="azure-virtual-machine-scale-sets"></a>Azure Virtual Machine Scale Sets
|Hanterad identitets typ | Alla allmänt tillgängliga<br>Globala Azure-regioner | Azure Government | Azure Tyskland | Azure Kina 21Vianet |
| --- | :-: | :-: | :-: | :-: |
| Systemtilldelad | ![Tillgänglig][check] | Förhandsgranskning | Förhandsgranskning | Förhandsgranskning |
| Användartilldelad | ![Tillgänglig][check] | Förhandsgranskning | Förhandsgranskning | Förhandsgranskning |
I följande lista kan du konfigurera hanterad identitet för Azure Virtual Machine Scale Sets (i regioner där det är tillgängligt):
- [Azure-portalen](qs-configure-portal-windows-vm.md)
- [PowerShell](qs-configure-powershell-windows-vm.md)
- [Azure CLI](qs-configure-cli-windows-vm.md)
- [Azure Resource Manager-mallar](qs-configure-template-windows-vm.md)
- [REST](qs-configure-rest-vm.md)
### <a name="azure-virtual-machines"></a>Azure Virtual Machines
| Hanterad identitets typ | Alla allmänt tillgängliga<br>Globala Azure-regioner | Azure Government | Azure Tyskland | Azure Kina 21Vianet |
| --- | :-: | :-: | :-: | :-: |
| Systemtilldelad | ![Tillgänglig][check] | ![Tillgänglig][check] | Förhandsgranskning | Förhandsgranskning |
| Användartilldelad | ![Tillgänglig][check] | ![Tillgänglig][check] | Förhandsgranskning | Förhandsgranskning |
I följande lista kan du konfigurera hanterad identitet för Azure Virtual Machines (i regioner där det är tillgängligt):
- [Azure-portalen](qs-configure-portal-windows-vm.md)
- [PowerShell](qs-configure-powershell-windows-vm.md)
- [Azure CLI](qs-configure-cli-windows-vm.md)
- [Azure Resource Manager-mallar](qs-configure-template-windows-vm.md)
- [REST](qs-configure-rest-vm.md)
### <a name="azure-vm-image-builder"></a>Image Builder för Azure VM
| Hanterad identitets typ | Alla allmänt tillgängliga<br>Globala Azure-regioner | Azure Government | Azure Tyskland | Azure Kina 21Vianet |
| --- | :-: | :-: | :-: | :-: |
| Systemtilldelad | Inte tillgängligt | Inte tillgängligt | Inte tillgängligt | Inte tillgängligt |
| Användartilldelad | [Tillgängligt i regioner som stöds](https://docs.microsoft.com/azure/virtual-machines/windows/image-builder-overview#regions) | Inte tillgängligt | Inte tillgängligt | Inte tillgängligt |
Information om hur du konfigurerar hanterad identitet för Azure VM Image Builder (i regioner där tillgänglig) finns i [Översikt över Image Builder](https://docs.microsoft.com/azure/virtual-machines/windows/image-builder-overview#permissions).
### <a name="azure-signalr-service"></a>Azure SignalR Service
Hanterad identitets typ | Alla allmänt tillgängliga<br>Globala Azure-regioner | Azure Government | Azure Tyskland | Azure Kina 21Vianet |
| --- | :-: | :-: | :-: | :-: |
| Systemtilldelad | Förhandsgranskning | Förhandsgranskning | Inte tillgängligt | Förhandsgranskning |
| Användartilldelad | Förhandsgranskning | Förhandsgranskning | Inte tillgängligt | Förhandsgranskning |
I följande lista kan du konfigurera hanterad identitet för Azure SignalR service (i regioner där det finns):
- [Azure Resource Manager mall](../../azure-signalr/howto-use-managed-identity.md)
## <a name="azure-services-that-support-azure-ad-authentication"></a>Azure-tjänster som stöder Azure AD-autentisering
Följande tjänster stöder Azure AD-autentisering och har testats med klient tjänster som använder hanterade identiteter för Azure-resurser.
### <a name="azure-resource-manager"></a>Azure Resource Manager
Se följande lista för att konfigurera åtkomst till Azure Resource Manager:
- [Tilldela åtkomst via Azure Portal](howto-assign-access-portal.md)
- [Tilldela åtkomst via PowerShell](howto-assign-access-powershell.md)
- [Tilldela åtkomst via Azure CLI](howto-assign-access-CLI.md)
- [Tilldela åtkomst via Azure Resource Manager mall](../../role-based-access-control/role-assignments-template.md)
| Molnet | Resurs-ID | Status |
|--------|------------|:-:|
| Azure Global | `https://management.azure.com/`| ![Tillgänglig][check] |
| Azure Government | `https://management.usgovcloudapi.net/` | ![Tillgänglig][check] |
| Azure Tyskland | `https://management.microsoftazure.de/` | ![Tillgänglig][check] |
| Azure Kina 21Vianet | `https://management.chinacloudapi.cn` | ![Tillgänglig][check] |
### <a name="azure-key-vault"></a>Azure Key Vault
| Molnet | Resurs-ID | Status |
|--------|------------|:-:|
| Azure Global | `https://vault.azure.net`| ![Tillgänglig][check] |
| Azure Government | `https://vault.usgovcloudapi.net` | ![Tillgänglig][check] |
| Azure Tyskland | `https://vault.microsoftazure.de` | ![Tillgänglig][check] |
| Azure Kina 21Vianet | `https://vault.azure.cn` | ![Tillgänglig][check] |
### <a name="azure-data-lake"></a>Azure Data Lake
| Molnet | Resurs-ID | Status |
|--------|------------|:-:|
| Azure Global | `https://datalake.azure.net/` | ![Tillgänglig][check] |
| Azure Government | | Inte tillgängligt |
| Azure Tyskland | | Inte tillgängligt |
| Azure Kina 21Vianet | | Inte tillgängligt |
### <a name="azure-sql"></a>Azure SQL
| Molnet | Resurs-ID | Status |
|--------|------------|:-:|
| Azure Global | `https://database.windows.net/` | ![Tillgänglig][check] |
| Azure Government | `https://database.usgovcloudapi.net/` | ![Tillgänglig][check] |
| Azure Tyskland | `https://database.cloudapi.de/` | ![Tillgänglig][check] |
| Azure Kina 21Vianet | `https://database.chinacloudapi.cn/` | ![Tillgänglig][check] |
### <a name="azure-event-hubs"></a>Azure Event Hubs
| Molnet | Resurs-ID | Status |
|--------|------------|:-:|
| Azure Global | `https://eventhubs.azure.net` | ![Tillgänglig][check] |
| Azure Government | | Inte tillgängligt |
| Azure Tyskland | | Inte tillgängligt |
| Azure Kina 21Vianet | | Inte tillgängligt |
### <a name="azure-service-bus"></a>Azure Service Bus
| Molnet | Resurs-ID | Status |
|--------|------------|:-:|
| Azure Global | `https://servicebus.azure.net` | ![Tillgänglig][check] |
| Azure Government | | ![Tillgänglig][check] |
| Azure Tyskland | | Inte tillgängligt |
| Azure Kina 21Vianet | | Inte tillgängligt |
### <a name="azure-storage-blobs-and-queues"></a>Azure Storage blobbar och köer
| Molnet | Resurs-ID | Status |
|--------|------------|:-:|
| Azure Global | `https://storage.azure.com/` <br /><br />`https://<account>.blob.core.windows.net` <br /><br />`https://<account>.queue.core.windows.net` | ![Tillgänglig][check] |
| Azure Government | `https://storage.azure.com/`<br /><br />`https://<account>.blob.core.usgovcloudapi.net` <br /><br />`https://<account>.queue.core.usgovcloudapi.net` | ![Tillgänglig][check] |
| Azure Tyskland | `https://storage.azure.com/`<br /><br />`https://<account>.blob.core.cloudapi.de` <br /><br />`https://<account>.queue.core.cloudapi.de` | ![Tillgänglig][check] |
| Azure Kina 21Vianet | `https://storage.azure.com/`<br /><br />`https://<account>.blob.core.chinacloudapi.cn` <br /><br />`https://<account>.queue.core.chinacloudapi.cn` | ![Tillgänglig][check] |
### <a name="azure-analysis-services"></a>Azure Analysis Services
| Molnet | Resurs-ID | Status |
|--------|------------|:-:|
| Azure Global | `https://*.asazure.windows.net` | ![Tillgänglig][check] |
| Azure Government | `https://*.asazure.usgovcloudapi.net` | ![Tillgänglig][check] |
| Azure Tyskland | `https://*.asazure.cloudapi.de` | ![Tillgänglig][check] |
| Azure Kina 21Vianet | `https://*.asazure.chinacloudapi.cn` | ![Tillgänglig][check] |
> [!Note]
> Microsoft Power BI [stöder också hanterade identiteter](https://docs.microsoft.com/azure/stream-analytics/powerbi-output-managed-identity).
[check]: media/services-support-managed-identities/check.png "Få"
| 56.693069 | 410 | 0.730702 | swe_Latn | 0.853929 |
fdfda4ac02c2424013a8cd29abbefd1f56f70216 | 35,030 | md | Markdown | README.md | Teichlab/celltypist | b00bf029e86bd429f783bbfe38bfab5c80d5a039 | [
"MIT"
] | 37 | 2021-05-20T16:15:02.000Z | 2022-03-07T08:45:22.000Z | README.md | Teichlab/celltypist | b00bf029e86bd429f783bbfe38bfab5c80d5a039 | [
"MIT"
] | 12 | 2021-07-22T14:05:02.000Z | 2022-03-25T11:10:22.000Z | README.md | Teichlab/celltypist | b00bf029e86bd429f783bbfe38bfab5c80d5a039 | [
"MIT"
] | 4 | 2022-01-08T16:08:58.000Z | 2022-02-07T10:54:21.000Z | <p align="left"><img src="https://github.com/Teichlab/celltypist/blob/main/docs/source/_static/img/logo_celltypist.png" width="250" height="85"></p>
[](https://pypi.org/project/celltypist) [](https://celltypist.readthedocs.io/en/latest/?badge=latest)
CellTypist is an automated cell type annotation tool for scRNA-seq datasets on the basis of logistic regression classifiers optimised by the stochastic gradient descent algorithm. CellTypist allows for cell prediction using either built-in (with a current focus on immune sub-populations) or custom models, in order to assist in the accurate classification of different cell types and subtypes.
# CellTypist website
Information of CellTypist can be also found in our CellTypist portal. [](https://www.celltypist.org/)
# Interactive tutorials
[Using CellTypist for cell type classification ](https://colab.research.google.com/github/Teichlab/celltypist/blob/main/docs/notebook/celltypist_tutorial.ipynb)
[Using CellTypist for multi-label classification ](https://colab.research.google.com/github/Teichlab/celltypist/blob/main/docs/notebook/celltypist_tutorial_ml.ipynb)
[Best practice in large-scale cross-dataset label transfer using CellTypist ](https://colab.research.google.com/github/Teichlab/celltypist/blob/main/docs/notebook/celltypist_tutorial_cv.ipynb)
# Install CellTypist
### Using pip [](https://pypi.org/project/celltypist)
```console
pip install celltypist
```
### Using conda [](https://anaconda.org/bioconda/celltypist)
```console
conda install -c bioconda -c conda-forge celltypist
```
# Usage
<details>
<summary><strong>1. Use in the Python environment</strong></summary>
+ <details>
<summary><strong>1.1. Import the module</strong></summary>
```python
import celltypist
from celltypist import models
```
</details>
+ <details>
<summary><strong>1.2. Download available models</strong></summary>
The models serve as the basis for cell type predictions. Information of available models can be also found [here](https://www.celltypist.org/models).
```python
#Show all available models that can be downloaded and used.
models.models_description()
#Download a specific model, for example, `Immune_All_Low.pkl`.
models.download_models(model = 'Immune_All_Low.pkl')
#Download a list of models, for example, `Immune_All_Low.pkl` and `Immune_All_High.pkl`.
models.download_models(model = ['Immune_All_Low.pkl', 'Immune_All_High.pkl'])
#Update the models by re-downloading the latest versions if you think they may be outdated.
models.download_models(model = ['Immune_All_Low.pkl', 'Immune_All_High.pkl'], force_update = True)
#Show the local directory storing these models.
models.models_path
```
A simple way is to download all available models. Since each model is on average 1 megabyte (MB), we encourage the users to download all of them.
```python
#Download all the available models.
models.download_models()
#Update all models by re-downloading the latest versions if you think they may be outdated.
models.download_models(force_update = True)
```
</details>
+ <details>
<summary><strong>1.3. Overview of the models</strong></summary>
All models are serialised in a binary format by [pickle](https://docs.python.org/3/library/pickle.html).
```python
#Get an overview of the models that are downloaded in `1.2.`.
#By default (`on_the_fly = False`), all possible models (even those that are not downloaded) are shown.
models.models_description(on_the_fly = True)
```
</details>
+ <details>
<summary><strong>1.4. Inspect the model of interest</strong></summary>
To take a look at a given model, load the model as an instance of the `Model` class as defined in CellTypist.
```python
#Select the model from the above list. If the `model` argument is not provided, will default to `Immune_All_Low.pkl`.
model = models.Model.load(model = 'Immune_All_Low.pkl')
#Examine cell types contained in the model.
model.cell_types
#Examine genes/features contained in the model.
model.features
#The stochastic gradient descent logistic regression classifier within the model.
model.classifier
#The standard scaler within the model (used to scale the input query data).
model.scaler
#The model information.
model.description
```
</details>
+ <details>
<summary><strong>1.5. Celltyping based on the input of count table</strong></summary>
CellTypist accepts the input data as a count table (cell-by-gene or gene-by-cell) in the format of `.txt`, `.csv`, `.tsv`, `.tab`, `.mtx` or `.mtx.gz`. A raw count matrix (reads or UMIs) is required. Non-expressed genes (if you are sure of their expression absence in your data) are suggested to be included in the input table as well, as they point to the negative transcriptomic signatures when compared with the model used.
```python
#Get a demo test data. This is a UMI count csv file with cells as rows and gene symbols as columns.
input_file = celltypist.samples.get_sample_csv()
```
Assign the cell type labels from the model to the input test cells using the `annotate` function.
```python
#Predict the identity of each input cell.
predictions = celltypist.annotate(input_file, model = 'Immune_All_Low.pkl')
#Alternatively, the model argument can be a previously loaded `Model` as in 1.4.
predictions = celltypist.annotate(input_file, model = model)
```
If your input file is in a gene-by-cell format (genes as rows and cells as columns), pass in the `transpose_input = True` argument. In addition, if the input is provided in the `.mtx` format, you will also need to specify the `gene_file` and `cell_file` arguments as the files containing names of genes and cells, respectively.
```python
#In case your input file is a gene-by-cell table.
predictions = celltypist.annotate(input_file, model = 'Immune_All_Low.pkl', transpose_input = True)
#In case your input file is a gene-by-cell mtx file.
predictions = celltypist.annotate(input_file, model = 'Immune_All_Low.pkl', transpose_input = True, gene_file = '/path/to/gene/file.txt', cell_file = '/path/to/cell/file.txt')
```
Again, if the `model` argument is not specified, CellTypist will by default use the `Immune_All_Low.pkl` model.
The `annotate` function will return an instance of the `AnnotationResult` class as defined in CellTypist.
```python
#Summary information for the prediction result.
str(predictions)
#Examine the predicted cell type labels.
predictions.predicted_labels
#Examine the matrix representing the decision score of each cell belonging to a given cell type.
predictions.decision_matrix
#Examine the matrix representing the probability each cell belongs to a given cell type (transformed from decision matrix by the sigmoid function).
predictions.probability_matrix
```
By default, with the `annotate` function, each query cell is predicted into the cell type with the largest score/probability among all possible cell types (`mode = 'best match'`). This mode is straightforward and can be used to differentiate between highly homogeneous cell types.
However, in some scenarios where a query cell cannot be assigned to any cell type in the reference model (i.e., a novel cell type) or can be assigned to multiple cell types (i.e., multi-label classification), a mode of probability match can be turned on (`mode = 'prob match'`) with a probability cutoff (default to 0.5, `p_thres = 0.5`) to decide the cell types (none, 1, or multiple) assigned for a given cell.
```python
#Query cell will get the label of 'Unassigned' if it fails to pass the probability cutoff in each cell type.
#Query cell will get multiple label outputs (concatenated by '|') if more than one cell type passes the probability cutoff.
predictions = celltypist.annotate(input_file, model = 'Immune_All_Low.pkl', mode = 'prob match', p_thres = 0.5)
```
The three tables in the `AnnotationResult` (`.predicted_labels`, `.decision_matrix` and `.probability_matrix`) can be written out to local files (tables) by the function `to_table`, specifying the target `folder` for storage and the `prefix` common to each table.
```python
#Export the three results to csv tables.
predictions.to_table(folder = '/path/to/a/folder', prefix = '')
#Alternatively, export the three results to a single Excel table (.xlsx).
predictions.to_table(folder = '/path/to/a/folder', prefix = '', xlsx = True)
```
The resulting `AnnotationResult` can be also transformed to an [AnnData](https://anndata.readthedocs.io/en/latest/) which stores the expression matrix in the log1p normalised format (to 10,000 counts per cell) by the function `to_adata`. The predicted cell type labels can be inserted to this `AnnData` as well by specifying `insert_labels = True` (which is the default behavior of `to_adata`).
Confidence scores of query cells can be inserted by specifying `insert_conf = True` (which is also the default behavior of `to_adata`). The scores correspond to the probabilities of cell predictions based on either `predictions.predicted_labels.predicted_labels` or `predictions.predicted_labels.majority_voting` (see `1.7.`), which can be specified by `insert_conf_by` (default to the former, `predicted_labels`).
```python
#Get an `AnnData` with predicted labels and confidence scores embedded into the observation metadata columns.
adata = predictions.to_adata(insert_labels = True, insert_conf = True)
#Inspect these columns (`predicted_labels` and `conf_score`).
adata.obs
```
In addition, you can insert the decision matrix into the `AnnData` by passing in `insert_decision = True`, which represents the decision scores of each cell type distributed across the input cells. Alternatively, setting `insert_prob = True` will insert the probability matrix into the `AnnData`. The latter is the recommended way as probabilities are more interpretable (though sometimes not all query datasets converge to a meaningful range of probability values).
After the insertion, multiple columns will show up in the cell metadata of `AnnData`, with each column's name as a cell type name. Of note, all these columns (including the `predicted_labels` and `conf_score`) can be prefixed with a specific string by setting `prefix` in `to_adata`.
```python
#Get an `AnnData` with predicted labels, confidence scores, and decision matrix.
adata = predictions.to_adata(insert_labels = True, insert_conf = True, insert_decision = True)
#Get an `AnnData` with predicted labels, confidence scores, and probability matrix (recommended).
adata = predictions.to_adata(insert_labels = True, insert_conf = True, insert_prob = True)
```
You can now manipulate this object with any functions or modules applicable to `AnnData`. Actually, CellTypist provides a quick function `to_plots` to visualise your `AnnotationResult` and store the figures without the need of explicitly transforming it into an `AnnData`.
```python
#Visualise the predicted cell types overlaid onto the UMAP.
predictions.to_plots(folder = '/path/to/a/folder', prefix = '')
```
A different prefix for the output figures can be specified with the `prefix` tag, and UMAP coordinates will be generated for the input dataset using a canonical [Scanpy](https://scanpy.readthedocs.io/en/stable/) pipeline. The labels in the figure may be crowded if too many cell types are predicted (can be alleviated by a majority voting process, see `1.7.`).
If you also would like to inspect the decision score and probability distributions for each cell type involved in the model, pass in the `plot_probability = True` argument. This may take a bit longer time as one figure will be generated for each of the cell types from the model.
```python
#Visualise the decision scores and probabilities of each cell type overlaid onto the UMAP as well.
predictions.to_plots(folder = '/path/to/a/folder', prefix = '', plot_probability = True)
```
Multiple figures will be generated, including the predicted cell type labels overlaid onto the UMAP space, plus the decision score and probability distributions of each cell type on the UMAP.
</details>
+ <details>
<summary><strong>1.6. Celltyping based on AnnData</strong></summary>
CellTypist also accepts the input data as an [AnnData](https://anndata.readthedocs.io/en/latest/) generated from for example [Scanpy](https://scanpy.readthedocs.io/en/stable/).
Since the expression of each gene will be centred and scaled by matching with the mean and standard deviation of that gene in the provided model, CellTypist requires a logarithmised and normalised expression matrix stored in the `AnnData` (log1p normalised expression to 10,000 counts per cell). CellTypist will try the `.X` attribute first, and if it does not suffice, try the `.raw.X` attribute. If none of them fit into the desired data type or the expression matrix is not properly normalised, an error will be raised.
```python
#Provide the input as an `AnnData`.
predictions = celltypist.annotate('/path/to/input.h5ad', model = 'Immune_All_Low.pkl')
#Alternatively, the input can be specified as an `AnnData` already loaded in memory.
predictions = celltypist.annotate(a_loaded_adata, model = 'Immune_All_Low.pkl')
```
All the parameters and downstream operations are the same as in `1.5.`, except that 1) the transformed `AnnData` from `to_adata` stores all the expression matrix and other information as is in the original object. 2) when generating the visualisation figures, existing UMAP coordinates will be used. If no UMAP coordinates are found, CellTypist will fall back on the neighborhood graph to yield new 2D UMAP projections. If none is available, a canonical Scanpy pipeline will be performed to generate the UMAP coordinates as in `1.5.`.
Of note, when the input is an `AnnData`, compared to the visualisations in `1.5.`, a more useful way for visualising the prediction result is to use the function `celltypist.dotplot`, which quantitatively compares the CellTypist prediction result with the cell types (or clusters) pre-defined and stashed in the `AnnData` by the user. Specifically, a dot plot will be generated, demonstrating the match between CellTypist predictions and manual annotations (or clusters). For each cell type or cluster (each column within the dot plot), this plot shows how it can be 'decomposed' into different cell types predicted by CellTypist.
```python
#Examine the correspondence between CellTypist predictions (`use_as_prediction`) and manual annotations (`use_as_reference`).
#Here, `predicted_labels` from `predictions.predicted_labels` is used as the prediction result from CellTypist.
#`use_as_prediction` can be also set as `majority_voting` (see `1.7.`).
celltypist.dotplot(predictions, use_as_reference = 'column_key_of_manual_annotation', use_as_prediction = 'predicted_labels')
```
</details>
+ <details>
<summary><strong>1.7. Use a majority voting classifier combined with celltyping</strong></summary>
By default, CellTypist will only do the prediction jobs to infer the identities of input cells, which renders the prediction of each cell independent. To combine the cell type predictions with the cell-cell transcriptomic relationships, CellTypist offers a majority voting approach based on the idea that similar cell subtypes are more likely to form a (sub)cluster regardless of their individual prediction outcomes.
To turn on the majority voting classifier in addition to the CellTypist predictions, pass in `majority_voting = True` to the `annotate` function.
```python
#Turn on the majority voting classifier as well.
predictions = celltypist.annotate(input_file, model = 'Immune_All_Low.pkl', majority_voting = True)
```
During the majority voting, to define cell-cell relations, CellTypist will use a heuristic over-clustering approach according to the size of the input data with the aid of a Leiden clustering pipeline. Users can also provide their own over-clustering result to the `over_clustering` argument. This argument can be specified in several ways:
1) an input plain file with the over-clustering result of one cell per line.
2) a string key specifying an existing cell metadata column in the `AnnData` (pre-created by the user).
3) a list-like object (such as a numpy 1D array) indicating the over-clustering result of all cells.
4) if none of the above is provided, will use a heuristic over-clustering approach, noted above.
```python
#Add your own over-clustering result.
predictions = celltypist.annotate(input_file, model = 'Immune_All_Low.pkl', majority_voting = True, over_clustering = '/path/to/over_clustering/file')
```
There is also a `min_prop` parameter (defaults to 0) which controls the minimum proportion of cells from the dominant cell type required to name a given subcluster by this cell type. Subcluster that fails to pass this proportion threshold will be assigned `Heterogeneous`.
Similarly, an instance of the `AnnotationResult` class will be returned.
```python
#Examine the predicted cell type labels.
predictions.predicted_labels
#Examine specifically the majority-voting results.
predictions.predicted_labels.majority_voting
#Examine the matrix representing the decision score of each cell belonging to a given cell type.
predictions.decision_matrix
#Examine the matrix representing the probability each cell belongs to a given cell type (transformed from decision matrix by the sigmoid function).
predictions.probability_matrix
```
Compared to the results without majority-voting functionality as in `1.5.` and `1.6.`, the `.predicted_labels` attribute now has two extra columns (`over_clustering` and `majority_voting`) in addition to the column `predicted_labels`.
Other parameters and downstream operations are the same as in `1.5.` and `1.6.`. Note that due to the majority-voting results added, the exported tables (by `to_table`), the transformed `AnnData` (by `to_adata`), and the visualisation figures (by `to_plots`) will all have additional outputs or information indicating the majority-voting outcomes. For example, when using the function `celltypist.dotplot`, you can set `use_as_prediction = 'majority_voting'` to visualise the match between majority-voting results with manual annotations. The other example is that when using `to_adata`, you can specify `insert_conf_by = 'majority_voting'` to have the confidence scores corresponding to the majority-voting result instead of raw predictions (`insert_conf_by = 'predicted_labels'` which is the default).
```python
#Examine the correspondence between CellTypist predictions (`use_as_prediction`) and manual annotations (`use_as_reference`).
celltypist.dotplot(predictions, use_as_reference = 'column_key_of_manual_annotation', use_as_prediction = 'majority_voting')
```
</details>
</details>
<details>
<summary><strong>2. Use as the command line</strong></summary>
+ <details>
<summary><strong>2.1. Check the command line options</strong></summary>
```bash
celltypist --help
```
</details>
+ <details>
<summary><strong>2.2. Download all available models</strong></summary>
```bash
celltypist --update-models
```
This will download the latest models from the remote server.
</details>
+ <details>
<summary><strong>2.3. Overview of the models</strong></summary>
```bash
celltypist --show-models
```
</details>
+ <details>
<summary><strong>2.4. Celltyping based on the input of count table</strong></summary>
See `1.5.` for the format of the desired count matrix.
```bash
celltypist --indata /path/to/input/file --model Immune_All_Low.pkl --outdir /path/to/outdir
```
You can add a different model to be used in the `--model` option. If the `--model` is not provided, CellTypist will by default use the `Immune_All_Low.pkl` model. The output directory will be set to the current working directory if `--outdir` is not specified.
If your input file is in a gene-by-cell format (genes as rows and cells as columns), add the `--transpose-input` option.
```bash
celltypist --indata /path/to/input/file --model Immune_All_Low.pkl --outdir /path/to/outdir --transpose-input
```
If the input is provided in the `.mtx` format, you will also need to specify the `--gene-file` and `--cell-file` options as the files containing names of genes and cells, respectively.
The default mode (`--mode best_match`) for prediction is to choose the cell type with the largest score/probability as the final prediction; setting `--mode prob_match` combined with a probability threshold (default to 0.5, `--p-thres 0.5`) will enable a multi-label classification, which assigns 0 (i.e., unassigned), 1, or >=2 cell type labels to each query cell.
Other options that control the output files of CellTypist include `--prefix` which adds a custom prefix and `--xlsx` which merges the output files into one xlsx table. Check `celltypist --help` for more details.
</details>
+ <details>
<summary><strong>2.5. Celltyping based on AnnData</strong></summary>
See `1.6.` for the requirement of the expression matrix in the AnnData object (`.h5ad`).
```bash
celltypist --indata /path/to/input/adata --model Immune_All_Low.pkl --outdir /path/to/outdir
```
Other command line options are the same as in `2.4.`.
</details>
+ <details>
<summary><strong>2.6. Use a majority voting classifier combined with celltyping</strong></summary>
See `1.7.` for how the majority voting classifier works.
```bash
celltypist --indata /path/to/input/file --model Immune_All_Low.pkl --outdir /path/to/outdir --majority-voting
```
During the majority voting, to define cell-cell relations, CellTypist will use a heuristic over-clustering approach according to the size of the input data with the aid of a Leiden clustering pipeline. Users can also provide their own over-clustering result to the `--over-clustering` option. This option can be specified in several ways:
1) an input plain file with the over-clustering result of one cell per line.
2) a string key specifying an existing cell metadata column in the `AnnData` (pre-created by the user).
3) if none of the above is provided, will use a heuristic over-clustering approach, noted above.
```bash
celltypist --indata /path/to/input/file --model Immune_All_Low.pkl --outdir /path/to/outdir --majority-voting --over-clustering /path/to/over_clustering/file
```
There is also a `--min-prop` option (defaults to 0) which controls the minimum proportion of cells from the dominant cell type required to name a given subcluster by this cell type. Subcluster that fails to pass this proportion threshold will be assigned `Heterogeneous`.
Other command line options are the same as in `2.4.`.
</details>
+ <details>
<summary><strong>2.7. Generate visualisation figures for the results</strong></summary>
In addition to the tables output by CellTypist, you have the option to generate multiple figures to get an overview of your prediction results. See `1.5.`, `1.6.` and `1.7.` for what these figures represent.
```bash
#Plot the results after the celltyping process.
celltypist --indata /path/to/input/file --model Immune_All_Low.pkl --outdir /path/to/outdir --plot-results
#Plot the results after the celltyping and majority-voting processes.
celltypist --indata /path/to/input/file --model Immune_All_Low.pkl --outdir /path/to/outdir --majority-voting --plot-results
```
</details>
</details>
<details>
<summary><strong>3. Use in the R environment</strong></summary>
Currently, there is no plan for R compatibility. Try to convert R objects into AnnData for use in CellTypist.
</details>
<details>
<summary><strong>Supplemental guidance: generate a custom model</strong></summary>
## Supplemental guidance: generate a custom model
As well as the models provided by CellTypist (see `1.2.`), you can generate your own model from which the cell type labels can be transferred to another scRNA-seq dataset. This will be most useful when a large and comprehensive reference atlas is trained for future use, or when the similarity between two scRNA-seq datasets is under examination.
### Inputs for data training
The inputs for CellTypist training comprise the gene expression data, the cell annotation details (i.e., cell type labels), and in some scenarios the genes used. To facilitate the training process, the `train` function (see below) has been designed to accommodate different kinds of input formats:
1) The gene expression data can be provided as a path to the expression table (such as `.csv` and `.mtx`), or a path to the `AnnData` (`.h5ad`), with the former containing raw counts (in order to reduce the file size) while the latter containing log1p normalised expression (to 10,000 counts per cell) stored in `.X` or `.raw.X`. In addition to specifying the paths, you can provide any array-like objects (e.g., `csr_matrix`) or `AnnData` which are already loaded in memory (both should be in the log1p format). A cell-by-gene format (cells as rows and genes as columns) is required.
2) The cell type labels can be supplied as a path to the file containing cell type label per line corresponding to the cells in gene expression data. Any list-like objects (such as a `tuple` or `series`) are also acceptable. If the gene expression data is input as an `AnnData`, you can also provide a column name from its cell metadata (`.obs`) which represents information of cell type labels.
3) The genes will be automatically extracted if the gene expression data is provided as a table file, an `AnnData` or a `DataFrame`. Otherwise, you need to specify a path to the file containing one gene per line corresponding to the genes in the gene expression data. Any list-like objects (such as a `tuple` or `series`) are also acceptable.
### One-pass data training
Derive a new model by training the data using the `celltypist.train` function:
```python
#Training a CellTypist model.
new_model = celltypist.train(expression_input, labels = label_input, genes = gene_input)
```
If the input is a table file, an `AnnData` or a `DataFrame`, genes will be automatically extracted and the `genes` tag can thus be omitted from the above code. If your input is in a gene-by-cell format (genes as rows and cells as columns), remember to pass in the `transpose_input = True` argument.
Before the training is conducted, the gene expression format will be checked to make sure the input data is supplied as required. For example, the expression matrix should be in log1p normalised expression (to 10,000 counts per cell) if the input is an `AnnData`. This means when you subset the input with given genes (e.g., by highly variable genes), an error may be raised as CellTypist cannot judge the input as properly normalised with only a subset of genes. In such a case, pass in `check_expression = False` to skip the expression format check.
```python
#Training a CellTypist model with only subset of genes (e.g., highly variable genes).
#Restricting the input to a subset of genes can accelerate the training process.
#Use `AnnData` here as an example.
new_model = celltypist.train(some_adata[:, some_adata.var.highly_variable], labels = label_input, check_expression = False)
```
By default, data is trained using a traditional logistic regression classifier. This classifier is well suited to datasets of small or intermediate sizes (as an empirical estimate, <= 100k cells), and usually leads to an unbiased probability range with less parameter tuning. Among the training parameters, three important ones are `solver` which (if not specified by the user) is selected based on the size of the input data by CellTypist, `C` which sets the inverse of L2 regularisation strength, and `max_iter` which controls the maximum number of iterations before reaching the minimum of the cost function. Other (hyper)parameters from [LogisticRegression](https://scikit-learn.org/stable/modules/generated/sklearn.linear_model.LogisticRegression.html) are also applicable in the `train` function.
When the dimensions of the input data are large, training may take longer time even with CPU parallelisation (achieved by the `n_jobs` argument). To reduce the training time as well as to add some randomness to the classifier's solution, a stochastic gradient descent (SGD) logistic regression classifier can be enabled by `use_SGD = True`.
```python
#Training a CellTypist model with SGD learning.
new_model = celltypist.train(expression_input, labels = label_input, genes = gene_input, use_SGD = True)
```
A logistic regression classifier with SGD learning reduces the training burden dramatically and has a comparable performance versus a traditional logistic regression classifier. A minor caveat is that more careful model parameter tuning may be needed if you want to utilise the probability values from the model for scoring cell types in the prediction step (the selection of the most likely cell type for each query cell is not influenced however). Among the training parameters, two important ones are `alpha` which sets the L2 regularisation strength and `max_iter` which controls the maximum number of iterations. Other (hyper)parameters from [SGDClassifier](https://scikit-learn.org/stable/modules/generated/sklearn.linear_model.SGDClassifier.html) are also applicable in the `train` function.
When the training data contains a huge number of cells (for example >500k cells) or more randomness in selecting cells for training is needed, you may consider using the mini-batch version of the SGD logistic regression classifier by specifying `use_SGD = True` and `mini_batch = True`. As a result, in each epoch (default to 10 epochs, `epochs = 10`), cells are binned into equal-sized (the size is default to 1000, `batch_size = 1000`) random batches, and are trained in a batch-by-batch manner (default to 100 batches, `batch_number = 100`).
```python
#Get a CellTypist model with SGD mini-batch training.
new_model = celltypist.train(expression_input, labels = label_input, genes = gene_input, use_SGD = True, mini_batch = True)
```
By selecting part of cells for training (default to 1,000,000 cells with possible duplications, `epochs` x `batch_size` x `batch_number`), training time can be again reduced and the performance of the derived model is shown to persist as compared to the above two methods. Since some rare cell types may be undersampled during this procedure, you can pass in the `balance_cell_type = True` argument to sample rare cell types with a higher probability, ensuring close-to-even cell type distributions in mini-batches (subject to the maximum number of cells that can be provided by a given cell type).
There are also some free texts that can be inserted (e.g., `date`) to describe the model. Check out the `celltypist.train` for more information.
The resulting model is an instance of the `Model` class as in `1.4.`, and can be manipulated as with other CellTypist models.
Save this model locally:
```python
#Write out the model.
new_model.write('/path/to/local/folder/some_model_name.pkl')
```
A suggested location for stashing the model is the `models.models_path` (see `1.2.`). Through this, all models (including the models provided by CellTypist) will be in the same folder, and can be accessed in the same manner as in `1.4.`.
```python
#Write out the model in the `models.models_path` folder.
new_model.write(f'{models.models_path}/some_model_name.pkl')
```
To leverage this model, first load it by `models.Model.load`.
```python
new_model = models.Model.load('/path/to/local/folder/some_model_name.pkl')
```
This model can be used as with the built-in CellTypist models, for example, it can be specified as the `model` argument in `annotate`.
```python
#Predict the identity of each input cell with the new model.
predictions = celltypist.annotate(input_file, model = new_model)
#Alternatively, just specify the model path (recommended as this ensures the model is intact every time it is loaded).
predictions = celltypist.annotate(input_file, model = '/path/to/local/folder/some_model_name.pkl')
#If the model is stored in `models.models_path`, only the model name is needed.
predictions = celltypist.annotate(input_file, model = 'some_model_name.pkl')
```
Downstream operations are the same as in `1.4.`, `1.5.`, `1.6.`, and `1.7.`.
### Two-pass data training incorporating feature selection
Some scRNA-seq datasets may involve the noise mostly from genes not helpful or even detrimental to the characterisation of cell types. To mitigate this, `celltypist.train` has the option (`feature_selection = True`) to do a fast feature selection based on the feature importance (here, the absolute regression coefficients) using SGD learning. In short, top important genes (default: `top_genes = 300`) are selected from each cell type, and are further combined across cell types as the final feature set. The classifier is then re-run using the corresponding subset of the input data.
```python
#Two-pass data training with traditional logistic regression after SGD-based feature selection.
new_model = celltypist.train(expression_input, labels = label_input, genes = gene_input, feature_selection = True)
#Two-pass data training with SGD learning after feature selection.
new_model = celltypist.train(expression_input, labels = label_input, genes = gene_input, use_SGD = True, feature_selection = True)
#Two-pass data training with SGD mini-batch training after feature selection.
new_model = celltypist.train(expression_input, labels = label_input, genes = gene_input, use_SGD = True, mini_batch = True, feature_selection = True)
```
If you prefer other feature selection approaches and obtain a set of genes which are designated as important features, you can subset your input data and train the CellTypist model accordingly. As noted in the previous section, remember to pass in the `check_expression = False` argument.
```python
new_model = celltypist.train(expression_input_subset, labels = label_input, genes = gene_input, check_expression = False)
```
The downstream workflow is the same as that from one-pass data training.
</details>
| 81.845794 | 805 | 0.767228 | eng_Latn | 0.991947 |
fdfdb8c630d4ce1e8f455d7ac1a9b92c27633f25 | 922 | md | Markdown | README.md | andrew749/FlickrWallpaper | 324eba0fa1a4b2efeac29b792a805075f6f88a11 | [
"Apache-2.0"
] | null | null | null | README.md | andrew749/FlickrWallpaper | 324eba0fa1a4b2efeac29b792a805075f6f88a11 | [
"Apache-2.0"
] | null | null | null | README.md | andrew749/FlickrWallpaper | 324eba0fa1a4b2efeac29b792a805075f6f88a11 | [
"Apache-2.0"
] | null | null | null | # Drizio
##A Live Wallpaper for Android which displays flickr photos.
Drizio is a simple live wallpaper. The app allows you to specify
a certain number of cached images, as well as the refresh period for the
wallpaper. These properties in turn are read by the underlying service running in the background.It is this service which displays a slideshow of images.
##Screenshots
| 65.857143 | 153 | 0.796095 | eng_Latn | 0.780807 |
fdfdcd80c444256636a9bddca672a32c0386759b | 5,641 | md | Markdown | treebanks/yo_ytb/yo_ytb-feat-Person.md | vistamou/docs | 116b9c29e4218be06bf33b158284b9c952646989 | [
"Apache-2.0"
] | 204 | 2015-01-20T16:36:39.000Z | 2022-03-28T00:49:51.000Z | treebanks/yo_ytb/yo_ytb-feat-Person.md | vistamou/docs | 116b9c29e4218be06bf33b158284b9c952646989 | [
"Apache-2.0"
] | 654 | 2015-01-02T17:06:29.000Z | 2022-03-31T18:23:34.000Z | treebanks/yo_ytb/yo_ytb-feat-Person.md | vistamou/docs | 116b9c29e4218be06bf33b158284b9c952646989 | [
"Apache-2.0"
] | 200 | 2015-01-16T22:07:02.000Z | 2022-03-25T11:35:28.000Z | ---
layout: base
title: 'Statistics of Person in UD_Yoruba-YTB'
udver: '2'
---
## Treebank Statistics: UD_Yoruba-YTB: Features: `Person`
This feature is universal.
It occurs with 3 different values: `1`, `2`, `3`.
1008 tokens (12%) have a non-empty value of `Person`.
87 types (6%) occur at least once with a non-empty value of `Person`.
84 lemmas (6%) occur at least once with a non-empty value of `Person`.
The feature is used with 9 part-of-speech tags: <tt><a href="yo_ytb-pos-PRON.html">PRON</a></tt> (990; 12% instances), <tt><a href="yo_ytb-pos-ADJ.html">ADJ</a></tt> (5; 0% instances), <tt><a href="yo_ytb-pos-AUX.html">AUX</a></tt> (4; 0% instances), <tt><a href="yo_ytb-pos-ADP.html">ADP</a></tt> (2; 0% instances), <tt><a href="yo_ytb-pos-NOUN.html">NOUN</a></tt> (2; 0% instances), <tt><a href="yo_ytb-pos-PROPN.html">PROPN</a></tt> (2; 0% instances), <tt><a href="yo_ytb-pos-CCONJ.html">CCONJ</a></tt> (1; 0% instances), <tt><a href="yo_ytb-pos-NUM.html">NUM</a></tt> (1; 0% instances), <tt><a href="yo_ytb-pos-SCONJ.html">SCONJ</a></tt> (1; 0% instances).
### `PRON`
990 <tt><a href="yo_ytb-pos-PRON.html">PRON</a></tt> tokens (73% of all `PRON` tokens) have a non-empty value of `Person`.
The most frequent other feature values with which `PRON` and `Person` co-occurred: <tt><a href="yo_ytb-feat-PronType.html">PronType</a></tt><tt>=Prs</tt> (990; 100%), <tt><a href="yo_ytb-feat-Number.html">Number</a></tt><tt>=Sing</tt> (659; 67%), <tt><a href="yo_ytb-feat-Case.html">Case</a></tt><tt>=Nom</tt> (549; 55%).
`PRON` tokens may have the following values of `Person`:
* `1` (177; 18% of non-empty `Person`): <em>a, mi, èmi, mo, mí, wa, bíi, àwa, Nnaji, à</em>
* `2` (213; 22% of non-empty `Person`): <em>ẹ, yín, ìwọ, rẹ, ẹ̀yin, ọ, ọ́, alàtúnkọ, jọ, mọ</em>
* `3` (600; 61% of non-empty `Person`): <em>ó, rẹ̀, wọn, wọ́n, un, i, òun, a, tirẹ̀, á</em>
* `EMPTY` (367): <em>tí, ẹni, ara, èyí, náà, ẹnikẹ́ni, wọ́n, àwọn, ti, ẹ</em>
<table>
<tr><th>Paradigm <i>ó</i></th><th><tt>1</tt></th><th><tt>2</tt></th><th><tt>3</tt></th></tr>
<tr><td><tt><tt><a href="yo_ytb-feat-Case.html">Case</a></tt><tt>=Gen</tt>|<tt><a href="yo_ytb-feat-Typo.html">Typo</a></tt><tt>=Yes</tt></tt></td><td></td><td></td><td><em>o</em></td></tr>
<tr><td><tt><tt><a href="yo_ytb-feat-Case.html">Case</a></tt><tt>=Nom</tt></tt></td><td><em>ó</em></td><td><em>ó</em></td><td><em>ó</em></td></tr>
</table>
`Person` seems to be **lexical feature** of `PRON`. 93% lemmas (70) occur only with one value of `Person`.
### `ADJ`
5 <tt><a href="yo_ytb-pos-ADJ.html">ADJ</a></tt> tokens (3% of all `ADJ` tokens) have a non-empty value of `Person`.
`ADJ` tokens may have the following values of `Person`:
* `1` (4; 80% of non-empty `Person`): <em>gidi, tíkòsi´</em>
* `3` (1; 20% of non-empty `Person`): <em>Bìrìtìkó</em>
* `EMPTY` (191): <em>ọ̀pọ̀, ńlá, Alábùkún, dára, irú, àìmọ́, rere, mìíràn, tósòro, náà</em>
### `AUX`
4 <tt><a href="yo_ytb-pos-AUX.html">AUX</a></tt> tokens (1% of all `AUX` tokens) have a non-empty value of `Person`.
`AUX` tokens may have the following values of `Person`:
* `1` (2; 50% of non-empty `Person`): <em>maa, ti</em>
* `3` (2; 50% of non-empty `Person`): <em>ó</em>
* `EMPTY` (397): <em>ń, ti, jẹ́, kí, yóò, lè, máa, má, le, ó</em>
### `ADP`
2 <tt><a href="yo_ytb-pos-ADP.html">ADP</a></tt> tokens (0% of all `ADP` tokens) have a non-empty value of `Person`.
`ADP` tokens may have the following values of `Person`:
* `1` (2; 100% of non-empty `Person`): <em>Ni, bíi</em>
* `EMPTY` (691): <em>ní, fún, sí, láti, nínú, ti, inú, kúrò, lẹ́yìn, nípa</em>
### `NOUN`
2 <tt><a href="yo_ytb-pos-NOUN.html">NOUN</a></tt> tokens (0% of all `NOUN` tokens) have a non-empty value of `Person`.
`NOUN` tokens may have the following values of `Person`:
* `1` (2; 100% of non-empty `Person`): <em>Nnaji, Omi</em>
* `EMPTY` (1514): <em>Ọlọ́run, ènìyàn, ohun, ọmọ, ilẹ̀, ilé, ọ̀run, ojú, ojúewé, àgùntàn</em>
### `PROPN`
2 <tt><a href="yo_ytb-pos-PROPN.html">PROPN</a></tt> tokens (1% of all `PROPN` tokens) have a non-empty value of `Person`.
`PROPN` tokens may have the following values of `Person`:
* `1` (2; 100% of non-empty `Person`): <em>Alhaji, Naijiria</em>
* `EMPTY` (163): <em>Jésù, olúwa, Júù, Màríà, Wikipédíà, Mátà, Lásárù, Jáírù, Yorùbá, Jòhánù</em>
### `CCONJ`
1 <tt><a href="yo_ytb-pos-CCONJ.html">CCONJ</a></tt> tokens (0% of all `CCONJ` tokens) have a non-empty value of `Person`.
`CCONJ` tokens may have the following values of `Person`:
* `1` (1; 100% of non-empty `Person`): <em>tàbi</em>
* `EMPTY` (347): <em>sì, àti, ṣùgbọ́n, tàbí, Olorì, ati, si, sí, sùgbọ́n, òun</em>
### `NUM`
1 <tt><a href="yo_ytb-pos-NUM.html">NUM</a></tt> tokens (1% of all `NUM` tokens) have a non-empty value of `Person`.
The most frequent other feature values with which `NUM` and `Person` co-occurred: <tt><a href="yo_ytb-feat-NumType.html">NumType</a></tt><tt>=EMPTY</tt> (1; 100%).
`NUM` tokens may have the following values of `Person`:
* `1` (1; 100% of non-empty `Person`): <em>2i</em>
* `EMPTY` (74): <em>kan, méjì, 3, 000, 2004, 2005, mẹ́rin, Ọ̀kan, 10, 1520</em>
### `SCONJ`
1 <tt><a href="yo_ytb-pos-SCONJ.html">SCONJ</a></tt> tokens (0% of all `SCONJ` tokens) have a non-empty value of `Person`.
`SCONJ` tokens may have the following values of `Person`:
* `1` (1; 100% of non-empty `Person`): <em>bíi</em>
* `EMPTY` (347): <em>pé, bí, nítorí, bá, kí, tilẹ̀, tó, Tí, baà, ìbáṣe</em>
## Relations with Agreement in `Person`
The 10 most frequent relations where parent and child node agree in `Person`:
<tt>PRON --[<tt><a href="yo_ytb-dep-expl.html">expl</a></tt>]--> PRON</tt> (1; 100%).
| 47.403361 | 660 | 0.623294 | yue_Hant | 0.372758 |
fdffc50008d734c57a867f2e1e497a838e589ff9 | 651 | md | Markdown | weibotop_content/2021/2021-08/2021-08-06/21:33.md | handn-work/spider | 8130508da1ba31df2d1430c0077ad08602417fd3 | [
"MIT"
] | null | null | null | weibotop_content/2021/2021-08/2021-08-06/21:33.md | handn-work/spider | 8130508da1ba31df2d1430c0077ad08602417fd3 | [
"MIT"
] | null | null | null | weibotop_content/2021/2021-08/2021-08-06/21:33.md | handn-work/spider | 8130508da1ba31df2d1430c0077ad08602417fd3 | [
"MIT"
] | 1 | 2022-01-24T09:20:56.000Z | 2022-01-24T09:20:56.000Z | 确保重要民生商品保供稳价
中国队获乒乓球男团金牌
刘诗颖获女子标枪金牌
许昕球打到马龙背上
新液体卫生巾限时包邮试
第一次见这么拿冠军的
奥恰洛夫 吹球
全红婵家门口堆满辣条
奥恰洛夫好强
尹笑言空手道夺银
国乒男团VS德国男团
庞倩玉自由式摔跤夺银
罪犯在监狱不听话怎么办
马龙熟悉的躲避姿势
樊振东表现
马龙许昕10年后仍是中国第一男双
许昕说再打几年不是大问题
谢楠点评吴京许昕表情包
王思聪花100万组装电脑
刘国梁赛前指导如何击败伊藤美诚
张继科躲球姿势
樊振东暴力美学
被偷柴犬找到时已成待售狗肉
樊振东神仙球
披荆斩棘的哥哥官宣
全红婵馋哭外国教练
杨紫再扮欢乐颂邱莹莹
泰国男星Toytoy杀死女友
男子举报别人吸毒反被抓
杨洋高情商解说东京奥运
和马说将回哈佛上学
被踹门查补课老师称不敢开门
马龙少女式跺脚
美国金牌
国乒男团举起国旗
中国队第36金
中国好声音
马龙奥运5金历史第一人
高菡的解说
国乒男团阶梯式握拳
龙蟒胖的时代
央视批疫情防控粗暴执法实属不该
3只野生大熊猫出门相亲被拍到
INTO1百日宴下班花絮
王曼昱把花拿反了
奖牌榜
警方通报撞死路人跑车司机被刑拘
玉楼春
女子4×100米接力决赛
樊振东喊起来了
黄磊一家报警
被福原爱纪录片里的小男生撩到
| 12.283019 | 18 | 0.757296 | yue_Hant | 0.804927 |
fdfffd4a37ed2dce017abf1a47f1616427ae4ded | 69 | md | Markdown | source/npcs.md | delaford/docs | f6c656a4d6de27bd8477815f0cbcbfd115a11c66 | [
"MIT"
] | 1 | 2022-02-03T08:53:27.000Z | 2022-02-03T08:53:27.000Z | source/npcs.md | delaford/docs | f6c656a4d6de27bd8477815f0cbcbfd115a11c66 | [
"MIT"
] | null | null | null | source/npcs.md | delaford/docs | f6c656a4d6de27bd8477815f0cbcbfd115a11c66 | [
"MIT"
] | 1 | 2022-02-03T08:53:27.000Z | 2022-02-03T08:53:27.000Z | ---
title: NPCs
description: null
extends: _layouts.documentation
--- | 13.8 | 31 | 0.753623 | eng_Latn | 0.887995 |
a900f8e99066bd0225a55fea0a38abe00525485c | 6,545 | md | Markdown | includes/azure-virtual-network-limits.md | decarli/azure-docs.pt-br | 20bc383d005c11e7b7dc7b7b0777fc0de1262ffc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | includes/azure-virtual-network-limits.md | decarli/azure-docs.pt-br | 20bc383d005c11e7b7dc7b7b0777fc0de1262ffc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | includes/azure-virtual-network-limits.md | decarli/azure-docs.pt-br | 20bc383d005c11e7b7dc7b7b0777fc0de1262ffc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: incluir arquivo
description: incluir arquivo
services: networking
author: anavinahar
ms.service: networking
ms.topic: include
ms.date: 01/14/2020
ms.author: anavin
ms.custom: include file
ms.openlocfilehash: 17558b44c91425ce1a06625f8fd5c1806a762ba2
ms.sourcegitcommit: 3dc1a23a7570552f0d1cc2ffdfb915ea871e257c
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 01/15/2020
ms.locfileid: "76021221"
---
<a name="azure-resource-manager-virtual-networking-limits"></a>Limites de rede-Azure Resource Manager os seguintes limites se aplicam somente a recursos de rede gerenciados por meio de **Azure Resource Manager** por região por assinatura. Saiba como [exibir seu uso de recursos atual em relação a seus limites de assinatura](../articles/networking/check-usage-against-limits.md).
> [!NOTE]
> Recentemente, aumentamos todos os limites padrão para seus limites máximos. Se não houver uma coluna de limite máximo, o recurso não terá limites ajustáveis. Se você tivesse esses limites aumentados pelo suporte no passado e não vir os limites atualizados nas tabelas a seguir, [abra uma solicitação de atendimento ao cliente online sem encargos](../articles/azure-resource-manager/templates/error-resource-quota.md)
| Grupos | Limite máximo/padrão |
| --- | --- |
| Redes virtuais |1,000 |
| Sub-redes por rede virtual |3\.000 |
| Emparelhamentos de rede virtual por rede virtual |500 |
| [Gateways de rede virtual (gateways de VPN) por rede virtual](../articles/vpn-gateway/vpn-gateway-about-vpngateways.md#gwsku) |1 |
| [Gateways de rede virtual (gateways de ExpressRoute) por rede virtual](../articles/expressroute/expressroute-about-virtual-network-gateways.md#gwsku) |1 |
| Servidores DNS por rede virtual |20 |
| Endereços IP privados por rede virtual |65.536 |
| Endereços IP privados por interface de rede |256 |
| Endereços IP privados por máquina virtual |256 |
| Endereços IP públicos por interface de rede |256 |
| Endereços IP públicos por máquina virtual |256 |
| [Fluxos TCP ou UDP simultâneos por NIC de uma máquina virtual ou instância de função](../articles/virtual-network/virtual-machine-network-throughput.md#flow-limits-and-recommendations) |500.000 |
| Placas de interface de rede |65.536 |
| Grupos de Segurança de Rede |5\.000 |
| Regras de NSG por NSG |1,000 |
| Endereços e intervalos IP especificados para a origem ou o destino em um grupo de segurança |4\.000 |
| Grupos de segurança do aplicativo |3\.000 |
| Grupos de segurança do aplicativo por configuração de IP, por NIC |20 |
| Configurações de IP por grupo de segurança do aplicativo |4\.000 |
| Os grupos de segurança do aplicativo que podem ser especificados em todas as regras de segurança de um grupo de segurança de rede |100 |
| Tabelas de rotas definidas pelo usuário |200 |
| Rotas definidas pelo usuário por tabela de rotas |400 |
| Certificados raiz ponto a site por gateway de VPN do Azure |20 |
| TAPs de rede virtual |100 |
| Configurações de TAP do adaptador de rede por TAP de rede virtual |100 |
#### <a name="publicip-address"></a>Limites do endereço IP público
| Grupos | Limite padrão | Limite máximo |
| --- | --- | --- |
| Endereços IP públicos - dinâmicos | 1\.000 para Basic. |Entre em contato com o suporte. |
| Endereços IP públicos - estáticos | 1\.000 para Basic. |Entre em contato com o suporte. |
| Endereços IP públicos - estáticos | 1\.000 para Standard.|Entre em contato com o suporte. |
| Comprimento do prefixo IP público | / 28 | Entre em contato com o suporte. |
#### <a name="load-balancer"></a>Limites de balanceador de carga
Os limites a seguir aplicam-se apenas a recursos de rede gerenciados pelo Azure Resource Manager por região e assinatura. Saiba como [exibir seu uso de recursos atual em relação a seus limites de assinatura](../articles/networking/check-usage-against-limits.md).
**Standard Load Balancer**
| Grupos | Limite máximo/padrão |
|-----------------------------------------|-------------------------------|
| Balanceadores de carga | 1,000 |
| Regras por recurso | 1\.500 |
| Regras por NIC (em todos os IPs em uma NIC) | 300 |
| Configurações de IP de front-end | 600 |
| Tamanho do pool de back-end | 1\.000 configurações de IP, rede virtual única |
| Portas de alta disponibilidade | 1 por front-end interno |
| Regras de saída por Load Balancer | 20 |
**Load Balancer básica**
| Grupos | Limite máximo/padrão |
|-----------------------------------------|------------------------------|
| Balanceadores de carga | 1,000 |
| Regras por recurso | 250 |
| Regras por NIC (em todos os IPs em uma NIC) | 300 |
| Configurações de IP de front-end | 200 |
| Tamanho do pool de back-end | 300 configurações de IP, conjunto de disponibilidade único |
| Conjuntos de disponibilidade por Load Balancer | 150 |
#### <a name="virtual-networking-limits-classic"></a>Os limites a seguir se aplicam somente a recursos de rede gerenciados por meio do modelo de implantação **clássico** por assinatura. Saiba como [exibir seu uso de recursos atual em relação a seus limites de assinatura](../articles/networking/check-usage-against-limits.md).
| Grupos | Limite padrão | Limite máximo |
| --- | --- | --- |
| Redes virtuais |100 |100 |
| Sites de redes locais |20 |50 |
| Servidores DNS por rede virtual |20 |20 |
| Endereços IP privados por rede virtual |4\.096 |4\.096 |
| Fluxos TCP ou UDP simultâneos por NIC de uma máquina virtual ou instância de função |500.000, até 1 milhão para duas ou mais NICs. |500.000, até 1 milhão para duas ou mais NICs. |
| Grupos de segurança de rede (NSG) |200 |200 |
| Regras de NSG por NSG |1,000 |1,000 |
| Tabelas de rotas definidas pelo usuário |200 |200 |
| Rotas definidas pelo usuário por tabela de rotas |400 |400 |
| Endereços IP públicos (dinâmicos) |500 |500 |
| Endereços IP públicos reservados |500 |500 |
| VIP público por implantação |5 |Entrar em contato com o suporte |
| VIP privado (balanceamento de carga interno) por implantação |1 |1 |
| Listas de controle de acesso de ponto de extremidade (ACLs) |50 |50 |
| 62.932692 | 418 | 0.67013 | por_Latn | 0.996177 |
a9012fbf3fe7d0ccdb8c5b66d178bd153a27581e | 786 | md | Markdown | chapter-13/pearls-nwjs/README.md | zaherg/cross-platform-desktop-applications | a39bc8707fa722a1377ef917d5ce5ddd2b0ab155 | [
"MIT"
] | 147 | 2016-07-10T23:06:34.000Z | 2022-03-12T19:54:01.000Z | chapter-13/pearls-nwjs/README.md | zaherg/cross-platform-desktop-applications | a39bc8707fa722a1377ef917d5ce5ddd2b0ab155 | [
"MIT"
] | 6 | 2017-06-04T09:38:12.000Z | 2021-04-27T13:14:55.000Z | chapter-13/pearls-nwjs/README.md | zaherg/cross-platform-desktop-applications | a39bc8707fa722a1377ef917d5ce5ddd2b0ab155 | [
"MIT"
] | 116 | 2016-08-15T21:12:21.000Z | 2022-03-07T23:25:53.000Z | # Pearls (NW.js)
A quotes app, built with NW.js for [Cross Platform Desktop Applications](https://manning.com/books/cross-platform-desktop-applications).
### Dependencies
- Node.js (4.x and above)
- NW.js (0.15.x and above)
### Installation
```
cd PATH_TO_THIS_APP
npm install
```
### Starting the app
```
cd PATH_TO_THIS_APP
npm start
```
### About this application
This application was created for [Cross Platform Desktop Applications](https://manning.com/books/cross-platform-desktop-applications).
### Licence and Credits
© 2016 Paul Jensen. The app source code is licensed under the MIT License.
| 23.818182 | 167 | 0.755725 | eng_Latn | 0.596704 |
a901307aedec9c8e3e148f8ca4339263cbc93ec8 | 8,879 | md | Markdown | articles/iot-hub/iot-hub-live-data-visualization-in-power-bi.md | marcduiker/azure-docs.nl-nl | 747ce1fb22d13d1e7c351e367c87810dd9eafa08 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/iot-hub/iot-hub-live-data-visualization-in-power-bi.md | marcduiker/azure-docs.nl-nl | 747ce1fb22d13d1e7c351e367c87810dd9eafa08 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/iot-hub/iot-hub-live-data-visualization-in-power-bi.md | marcduiker/azure-docs.nl-nl | 747ce1fb22d13d1e7c351e367c87810dd9eafa08 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "Realtime gegevensvisualisatie van sensorgegevens uit Azure IoT Hub – Power BI | Microsoft Docs"
description: Gebruik Power BI om temperatuur en vochtigheid gegevens die worden verzameld van de sensor en verzonden naar uw Azure-IoT-hub te visualiseren.
services: iot-hub
documentationcenter:
author: shizn
manager: timlt
tags:
keywords: realtime gegevensvisualisatie, live gegevensvisualisatie, sensor gegevensvisualisatie
ms.assetid: e67c9c09-6219-4f0f-ad42-58edaaa74f61
ms.service: iot-hub
ms.devlang: arduino
ms.topic: article
ms.tgt_pltfrm: na
ms.workload: na
ms.date: 08/24/2017
ms.author: xshi
ms.openlocfilehash: b190fea06ffc2406d781c7edad091f097cca9c2d
ms.sourcegitcommit: 6699c77dcbd5f8a1a2f21fba3d0a0005ac9ed6b7
ms.translationtype: MT
ms.contentlocale: nl-NL
ms.lasthandoff: 10/11/2017
---
# <a name="visualize-real-time-sensor-data-from-azure-iot-hub-using-power-bi"></a>Realtime-sensorgegevens uit Azure IoT Hub met Power BI visualiseren
[!INCLUDE [iot-hub-get-started-note](../../includes/iot-hub-get-started-note.md)]
## <a name="what-you-learn"></a>Wat u leert
U leert hoe voor het visualiseren van realtime-sensorgegevens die uw Azure-IoT-hub ontvangt door Power BI. Als u proberen de gegevens in uw IoT-hub met Web-Apps wilt, raadpleegt u [gebruik Azure Web Apps voor het visualiseren van realtime-sensorgegevens uit Azure IoT Hub](iot-hub-live-data-visualization-in-web-apps.md).
## <a name="what-you-do"></a>Wat u doet
- Bereid uw IoT-hub voor toegang tot gegevens door een consumergroep toe te voegen.
- Maken, configureren en uitvoeren van een Stream Analytics-taak voor overdracht van gegevens uit uw IoT-hub aan uw Power BI-account.
- Maken en publiceren van een Power BI-rapport om de gegevens te visualiseren.
## <a name="what-you-need"></a>Wat u nodig hebt
- Zelfstudie [instellen van uw apparaat](iot-hub-raspberry-pi-kit-node-get-started.md) voltooid die wordt ingegaan op de volgende vereisten:
- Een actief Azure-abonnement.
- Een Azure-IoT-hub in uw abonnement.
- Een clienttoepassing dat berichten naar uw Azure-IoT-hub verzendt.
- Een Power BI-account. ([Probeer Power BI gratis](https://powerbi.microsoft.com/))
[!INCLUDE [iot-hub-get-started-create-consumer-group](../../includes/iot-hub-get-started-create-consumer-group.md)]
## <a name="create-configure-and-run-a-stream-analytics-job"></a>Maken, configureren en uitvoeren van een Stream Analytics-taak
### <a name="create-a-stream-analytics-job"></a>Een Stream Analytics-taak maken
1. Klik in de Azure-portal op Nieuw > Internet der dingen > Stream Analytics-taak.
1. Voer de volgende informatie voor de taak.
**Taaknaam**: de naam van de taak. De naam moet wereldwijd uniek zijn.
**Resourcegroep**: gebruik dezelfde resourcegroep die gebruikmaakt van uw IoT-hub.
**Locatie**: gebruik dezelfde locatie als uw resourcegroep.
**Vastmaken aan dashboard**: Schakel deze optie voor eenvoudige toegang naar uw IoT-hub vanuit het dashboard.
1. Klik op **Create**.
### <a name="add-an-input-to-the-stream-analytics-job"></a>Invoer voor de Stream Analytics-taak toevoegen
1. Open de Stream Analytics-taak.
1. Onder **taak topologie**, klikt u op **invoer**.
1. In de **invoer** deelvenster, klikt u op **toevoegen**, en voer de volgende informatie:
**Invoeralias**: de alias die uniek zijn voor de invoer.
**Bron**: Selecteer **IoT-hub**.
**Consumergroep**: Selecteer de consumergroep die u zojuist hebt gemaakt.
1. Klik op **Create**.
### <a name="add-an-output-to-the-stream-analytics-job"></a>Uitvoer toevoegen aan Stream Analytics-taak
1. Onder **taak topologie**, klikt u op **uitvoer**.
1. In de **uitvoer** deelvenster, klikt u op **toevoegen**, en voer de volgende informatie:
**Uitvoeraliassen**: de alias die uniek zijn voor de uitvoer.
**Sink**: Selecteer **Power BI**.
1. Klik op **autoriseren**, en vervolgens meldt u zich bij uw Power BI-account.
1. Na autorisatie, voer de volgende informatie:
**Werkruimte groep**: Selecteer de groep doelwerkruimte.
**Naam van DataSet**: Voer een gegevenssetnaam.
**Tabelnaam**: Voer een tabelnaam.
1. Klik op **Create**.
### <a name="configure-the-query-of-the-stream-analytics-job"></a>De query van de Stream Analytics-taak configureren
1. Onder **taak topologie**, klikt u op **Query**.
1. Vervang `[YourInputAlias]` met de ingevoerde alias van de taak.
1. Vervang `[YourOutputAlias]` met de uitvoeralias van de taak.
1. Klik op **Opslaan**.
### <a name="run-the-stream-analytics-job"></a>De Stream Analytics-taak uitvoeren
Klik in de Stream Analytics-taak op **Start** > **nu** > **Start**. Zodra de taak kan worden gestart, wordt de taakstatus verandert van **gestopt** naar **met**.
## <a name="create-and-publish-a-power-bi-report-to-visualize-the-data"></a>Maken en publiceren van een Power BI-rapport om de gegevens te visualiseren
1. Controleer dat de voorbeeldtoepassing op uw apparaat wordt uitgevoerd. Als u niet het geval is, raadpleegt u de zelfstudies onder [instellen van uw apparaat](https://docs.microsoft.com/azure/iot-hub/iot-hub-raspberry-pi-kit-node-get-started).
1. Aanmelden bij uw [Power BI](https://powerbi.microsoft.com/en-us/) account.
1. Ga naar de werkruimte voor groep die u hebt ingesteld toen u de uitvoer voor de Stream Analytics-taak gemaakt.
1. Klik op **Streaming gegevenssets**.
U ziet de vermelde gegevensset die u hebt opgegeven toen u de uitvoer voor de Stream Analytics-taak gemaakt.
1. Onder **acties**, klikt u op het eerste pictogram om een rapport te maken.
1. Maak een lijndiagram om weer te geven van realtime temperatuur gedurende een bepaalde periode.
1. Voeg een lijndiagram op de pagina rapport maken.
1. Op de **velden** deelvenster, vouw de tabel die u hebt opgegeven toen u de uitvoer voor de Stream Analytics-taak gemaakt.
1. Sleep **EventEnqueuedUtcTime** naar **as** op de **visualisaties** deelvenster.
1. Sleep **temperatuur** naar **waarden**.
Nu wordt een lijndiagram gemaakt. De x-as geeft de datum en tijd in UTC-tijdzone. De y-as worden temperatuur van de sensor weergegeven.
1. Maak een andere lijndiagram om weer te geven van realtime vochtigheid gedurende een bepaalde periode. U doet dit door dezelfde stappen hierboven en plaats **EventEnqueuedUtcTime** op de x-as en **vochtigheid** op de y-as.
1. Klik op **opslaan** het rapport wilt opslaan.
1. Klik op **bestand** > **publiceren op web**.
1. Klik op **invoegcode maken**, en klik vervolgens op **publiceren**.
U hebt de rapportkoppeling hebt opgegeven dat u met iedereen voor toegang tot rapporten en een codefragment delen kunt aan het rapport integreren in uw blog of website.
Microsoft biedt ook de [mobiele apps van Power BI](https://powerbi.microsoft.com/en-us/documentation/powerbi-power-bi-apps-for-mobile-devices/) voor het weergeven en interactie met uw Power BI-dashboards en rapporten op je mobiele apparaat.
## <a name="next-steps"></a>Volgende stappen
U hebt Power BI is gebruikt voor het visualiseren van realtime-sensorgegevens uit uw Azure-IoT-hub.
Er is een andere manier om gegevens uit Azure IoT Hub te visualiseren. Zie [gebruik Azure Web Apps voor het visualiseren van realtime-sensorgegevens uit Azure IoT Hub](iot-hub-live-data-visualization-in-web-apps.md).
[!INCLUDE [iot-hub-get-started-next-steps](../../includes/iot-hub-get-started-next-steps.md)]
| 54.808642 | 321 | 0.75932 | nld_Latn | 0.992315 |
a901af6a97d2272118a8379692ccce19d6349ad2 | 1,992 | md | Markdown | src/uk/2019-04/04/07.md | kalong2008/sabbath-school-lessons | 0f012fee82d9ce678a0668927ba7dd53760ee1da | [
"MIT"
] | null | null | null | src/uk/2019-04/04/07.md | kalong2008/sabbath-school-lessons | 0f012fee82d9ce678a0668927ba7dd53760ee1da | [
"MIT"
] | null | null | null | src/uk/2019-04/04/07.md | kalong2008/sabbath-school-lessons | 0f012fee82d9ce678a0668927ba7dd53760ee1da | [
"MIT"
] | null | null | null | ---
title: Для подальшого дослідження
date: 25/10/2019
---
Прочитайте з книги Е. Уайт «Пророки і царі» розділи «Будівничі стін Єрусалима», «Засудження здирства» і «Змова язичників» (С. 635-660).
«Опозиція відкритих ворогів та розчарування від уявних друзів – усе, із чим зустрічалися будівничі за днів Неемії, - характерне явище сьогодення, з яким стикаються всі Божі працівники. Християни зазнають випробувань не тільки через гнів, презирство та жорстокість ворогів, а й через лінощі, непослідовність, інертність й віроломство друзів і помічників» (Е. Уайт. Пророки і царі. С. 644).
«Ворогам не вдалося подолати Неемію, і це завдяки його непохитній відданості Божій справі та цілковитій довірі до Бога. Бездіяльна людина стає легкою здобиччю спокуси; але хто поставив перед собою благородну мету, що поглинає увесь його час і всі сили, той практично неприступний для зла. Якщо християнин постійно зростає у вірі, він не ослабне, бо в усьому вбачатиме руку Безмежної Любові, Котра робить усе для здійснення Своїх добрих намірів. Справжні Божі слуги трудяться з неослабною рішучістю, тому що престол благодаті – їхня вічна опора» (там само. С. 660).
**Питання для обговорення**
`Поставте себе на місце Зоровавеля, Ісуса та інших керівників, коли вороги прийшли до них із пропозицією допомоги. Озираючись назад, ми можемо бачити, що євреї вчинили правильно, не погоджуючись на таку пропозицію. Як ми, адвентисти, можемо знати, коли повинні, а коли не повинні співпрацювати з іншими? Яких критеріїв ми повинні дотримуватися?`
`Вивчаючи біблійну історію, ми бачимо небезпеку компромісу зі світом. Справді, уся історія стародавнього Ізраїлю аж до вавилонського полону була яскравим прикладом такого компромісу. Водночас, що відбувається, коли люди, намагаючись уникнути цієї небезпеки, впадають в іншу крайність? Самого Ісуса звинуватили в порушенні суботи (див. Івана 9:14-16) ‒ хіба це не приклад того, що Його обвинувачі впали в іншу крайність? Як нам дотримуватися золотої середини?`
| 117.176471 | 564 | 0.800703 | ukr_Cyrl | 1.000005 |
a9022cfed134258ecb3434be3eff1b1fab3cbc26 | 3,053 | md | Markdown | docs/odbc/microsoft/sqlsetstmtoption-visual-foxpro-odbc-driver.md | polocco/sql-docs.it-it | 054013d9cd6f2c81f53fc91a7eafc8043f12c380 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/odbc/microsoft/sqlsetstmtoption-visual-foxpro-odbc-driver.md | polocco/sql-docs.it-it | 054013d9cd6f2c81f53fc91a7eafc8043f12c380 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/odbc/microsoft/sqlsetstmtoption-visual-foxpro-odbc-driver.md | polocco/sql-docs.it-it | 054013d9cd6f2c81f53fc91a7eafc8043f12c380 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
description: SQLSetStmtOption (driver ODBC Visual FoxPro)
title: SQLSetStmtOption (driver ODBC Visual FoxPro) | Microsoft Docs
ms.custom: ''
ms.date: 01/19/2017
ms.prod: sql
ms.prod_service: connectivity
ms.reviewer: ''
ms.technology: connectivity
ms.topic: conceptual
helpviewer_keywords:
- SQLSetStmtOption function [ODBC], Visual FoxPro ODBC Driver
ms.assetid: 76b813e3-c7dc-4bb2-a710-d2aa9dcfdc36
author: David-Engel
ms.author: v-daenge
ms.openlocfilehash: c2688a41b660fd12314186fbc270cdc49f16bbe6
ms.sourcegitcommit: e700497f962e4c2274df16d9e651059b42ff1a10
ms.translationtype: MT
ms.contentlocale: it-IT
ms.lasthandoff: 08/17/2020
ms.locfileid: "88421625"
---
# <a name="sqlsetstmtoption-visual-foxpro-odbc-driver"></a>SQLSetStmtOption (driver ODBC Visual FoxPro)
> [!NOTE]
> Questo argomento contiene informazioni specifiche del driver ODBC Visual FoxPro. Per informazioni generali su questa funzione, vedere l'argomento appropriato in informazioni di [riferimento sulle API ODBC](../../odbc/reference/syntax/odbc-api-reference.md).
Supporto: completo
Conformità API ODBC: livello 1
Imposta le opzioni correlate a un handle di istruzione, *HSTMT*.
|*fOption*|Valori consentiti|Commenti|
|---------------|--------------------|--------------|
|SQL_ASYNC_ENABLE|SQL_ASYNC_ENABLE_OFF|Se si tenta di impostare questo *fOption*, il driver restituirà l'errore: "driver non in grado". Visual FoxPro non supporta l'esecuzione asincrona.|
|SQL_BIND_TYPE|SQL_BIND_BY_COLUMN o un valore a 32 bit che indica la lunghezza della struttura o un'istanza di un buffer in cui verranno vincolate le colonne di risultati.||
|SQL_CONCURRENCY|SQL_CONCUR_READ_ONLY<br /><br /> SQL_CONCUR_LOCK<br /><br /> SQL_CONCUR_VALUES|Il driver non consente SQL_CONCUR_ROWVER, perché Visual FoxPro non dispone del controllo delle versioni delle righe basato su timestamp.|
|SQL_CURSOR_TYPE|SQL_CURSOR_FORWARD_ONLY<br /><br /> SQL_CURSOR_STATIC|Il driver non consente SQL_CURSOR_KEYSET_DRIVEN o SQL_CURSOR_DYNAMIC; Per ulteriori informazioni, vedere [SQLSetScrollOptions](../../odbc/microsoft/sqlsetscrolloptions-visual-foxpro-odbc-driver.md) .|
|SQL_KEYSET_SIZE|Errore: "driver non in grado di supportare"|Visual FoxPro non supporta il modello di cursore keyset.|
|SQL_MAX_LENGTH|0|Se si tenta di impostare questo valore *fOption* , il driver restituisce l'errore "driver non in grado".|
|SQL_MAX_ROWS|0|Se si tenta di impostare questo valore *fOption* , il driver restituisce l'errore "driver non in grado".|
|SQL_NOSCAN|SQL_NOSCAN_OFF||
|SQL_QUERY_TIMEOUT|0|Se si tenta di impostare questo valore *fOption* , il driver restituisce l'errore "driver non in grado".|
|SQL_RETRIEVE_DATA|SQL_RD_ON, SQL_RD_OFF||
|SQL_ROWSET_SIZE|da 1 a 4.294.967.296||
|SQL_SIMULATE_CURSOR|Errore: "driver non in grado di supportare"||
|SQL_USE_BOOKMARKS|SQL_UB_OFF<br /><br /> SQL_UB_ON||
Per ulteriori informazioni, vedere [SQLSetStmtOption](../../odbc/reference/syntax/sqlsetstmtoption-function.md) in *ODBC Programmer ' s Reference*.
| 61.06 | 273 | 0.773993 | ita_Latn | 0.668933 |
a9031f3c5ce54b79a8dcd45969d254c9928c5af3 | 60 | md | Markdown | README.md | egribelsky/blazor-sample | 9d318756a1b73cc4ee5199f6742684cc67070c64 | [
"MIT"
] | null | null | null | README.md | egribelsky/blazor-sample | 9d318756a1b73cc4ee5199f6742684cc67070c64 | [
"MIT"
] | null | null | null | README.md | egribelsky/blazor-sample | 9d318756a1b73cc4ee5199f6742684cc67070c64 | [
"MIT"
] | null | null | null | # blazor-sample
Dipping toes into the cool waters of Blazor
| 20 | 43 | 0.8 | eng_Latn | 0.997844 |
a903b08582a49125c21efda01c72f50f11cfb6a2 | 343 | md | Markdown | README.md | matiasbavera/reduce-image-size-and-place-logo | e55d532e9b54d67041dbcad2ba419dc6e5a9eb03 | [
"Apache-2.0"
] | null | null | null | README.md | matiasbavera/reduce-image-size-and-place-logo | e55d532e9b54d67041dbcad2ba419dc6e5a9eb03 | [
"Apache-2.0"
] | null | null | null | README.md | matiasbavera/reduce-image-size-and-place-logo | e55d532e9b54d67041dbcad2ba419dc6e5a9eb03 | [
"Apache-2.0"
] | 1 | 2021-02-17T18:55:42.000Z | 2021-02-17T18:55:42.000Z | # reduce-image-size-and-place-logo
### How to install
`pip install -r requirements`
### How to run
Rename your profile picture, to `background.(png|jpeg)` (As a suggestion, you can place the logo image and the background image on the root folder) and run:
`python super_impose.py`
This will generate a new png file with the impose image. | 26.384615 | 156 | 0.746356 | eng_Latn | 0.99248 |
a9044c3113abf4b69c9688a731e6d702159b05dd | 2,125 | md | Markdown | WindowsServerDocs/remote/multipoint-services/Install-MultiPoint-services.md | SeekZ85/windowsserverdocs.fr-fr | 5bf1419505b71bb5f82621880aa069a0e5c88e45 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | WindowsServerDocs/remote/multipoint-services/Install-MultiPoint-services.md | SeekZ85/windowsserverdocs.fr-fr | 5bf1419505b71bb5f82621880aa069a0e5c88e45 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | WindowsServerDocs/remote/multipoint-services/Install-MultiPoint-services.md | SeekZ85/windowsserverdocs.fr-fr | 5bf1419505b71bb5f82621880aa069a0e5c88e45 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Installer MultiPoint Services
description: Découvrez comment installer et configurer MultiPoint services dans Windows Server 2016
ms.custom: na
ms.date: 07/22/2016
ms.prod: windows-server
ms.technology: multipoint-services
ms.reviewer: na
ms.suite: na
ms.tgt_pltfrm: na
ms.topic: article
ms.assetid: f6f8970b-de3f-4255-b2a1-5472a16ed02f
author: evaseydl
manager: scottman
ms.author: evas
ms.openlocfilehash: 442699afe40ee67e4cd4f13572d1a482f675b84a
ms.sourcegitcommit: 6aff3d88ff22ea141a6ea6572a5ad8dd6321f199
ms.translationtype: MT
ms.contentlocale: fr-FR
ms.lasthandoff: 09/27/2019
ms.locfileid: "71395381"
---
# <a name="install-multipoint-services"></a>Installer MultiPoint Services
Si vous installez un serveur à partir de zéro, suivez ces instructions pour installer MultiPoint services.
Une fois que vous avez installé Windows Server 2016, connectez-vous en tant qu’administrateur. Utilisez le Gestionnaire de serveur où vous pouvez activer MultiPoint services. Le Gestionnaire de serveur s’ouvre automatiquement au démarrage. Dans le tableau de bord, sélectionnez **Ajouter des rôles et des fonctionnalités** pour activer multipoint services et suivez les instructions de l’Assistant.
Dans la section pour le type d’installation, vous pouvez utiliser le
- Installation basée sur un rôle ou une fonctionnalité
- Installation de Services Bureau à distance
Pour les déploiements standard de MultiPoint services, nous vous recommandons de sélectionner l’installation Services Bureau à distance qui vous permet de sélectionner facilement le rôle MultiPoint services sous type de déploiement. Pour l’installation basée sur les rôles, vous devez sélectionner **multipoint services** dans la liste des rôles. Le serveur redémarrera après une installation réussie.
## <a name="configure-your-primary-station"></a>Configurer votre station principale
1. Sur la page **créer une station multipoint Server** , tapez la lettre spécifiée à partir du clavier pour cette analyse. L’entrée de clé appropriée associe le clavier et la souris de cette station.
2. Connectez-vous en tant qu’administrateur. | 57.432432 | 403 | 0.812235 | fra_Latn | 0.961104 |
a9045a62b53c8b442695750415b6b0cf58c7ca48 | 3,448 | md | Markdown | server-2013/lync-server-2013-lync-windows-store-app-requirements.md | v-vijanu/OfficeDocs-SkypeforBusiness-Test-pr.es-es | b8058e4767e19709e1df553cb66a7e6df429cf5e | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-05-19T19:28:10.000Z | 2020-05-19T19:28:10.000Z | server-2013/lync-server-2013-lync-windows-store-app-requirements.md | v-vijanu/OfficeDocs-SkypeforBusiness-Test-pr.es-es | b8058e4767e19709e1df553cb66a7e6df429cf5e | [
"CC-BY-4.0",
"MIT"
] | 21 | 2018-04-26T18:42:59.000Z | 2018-08-23T23:00:11.000Z | server-2013/lync-server-2013-lync-windows-store-app-requirements.md | v-vijanu/OfficeDocs-SkypeforBusiness-Test-pr.es-es | b8058e4767e19709e1df553cb66a7e6df429cf5e | [
"CC-BY-4.0",
"MIT"
] | 11 | 2018-06-19T11:13:26.000Z | 2021-11-15T11:25:02.000Z | ---
title: Requisitos de la aplicación de la Tienda Windows de Lync
TOCTitle: Requisitos de la aplicación de la Tienda Windows de Lync
ms:assetid: 5f2e0a40-8450-4f61-b6f6-913fc1906020
ms:mtpsurl: https://technet.microsoft.com/es-es/library/JJ823129(v=OCS.15)
ms:contentKeyID: 52061647
ms.date: 01/07/2017
mtps_version: v=OCS.15
ms.translationtype: HT
---
# Requisitos de la aplicación de la Tienda Windows de Lync
_**Última modificación del tema:** 2016-12-08_
Las organizaciones con una implementación local de Lync Server deben cumplir los siguientes requisitos para admitir Aplicación de la Tienda Windows de Lync.
> [!NOTE]
> Para Lync Server 2010, ejecute la actualización acumulativa para Lync Server 2010 de febrero de 2012 (disponible en <A class=uri href="http://go.microsoft.com/fwlink/?linkid=3052%26kbid=2670352">http://go.microsoft.com/fwlink/?linkid=3052&kbid=2670352</A>) o posterior en todos los servidores. Para permitir que los usuarios participen en reuniones, ejecute la actualización acumulativa para Lync Server 2010 de octubre de 2012 (disponible en <A class=uri href="http://go.microsoft.com/fwlink/?linkid=3052%26kbid=2737915">http://go.microsoft.com/fwlink/?linkid=3052&kbid=2737915</A>) en todos los servidores.
- Habilite los servicios de detección automática, Lync Web App y vales web en el servidor.
- Habilite la autenticación de certificados en Servidor front-end o Grupo de servidores front-end. (El proceso de registro del usuario en Servidor front-end o Grupo de servidores front-end suele denominarse registrador). Para obtener información detallada, consulte [Creación de opciones de configuración de un registrador](lync-server-2013-create-registrar-configuration-settings.md).
- Publique los registros de recurso de alias DNS (CNAME) para el servicio de detección automática.
- Ya no hace falta asegurarse de que el punto de distribución de la lista de revocación de certificados (CRL) correspondiente a los certificados emitidos a Lync Server apunte a un recurso HTTP en vez de a un recurso LDAP, pero sí hay que asegurarse de que los equipos cliente tengan instaladas las últimas actualizaciones de Windows.
- Configure proxies HTTP en la empresa para permitir tráfico HTTP relacionado con Lync Server. Agregue excepciones para los servicios de detección automática, Lync Web App y vales web, si es necesario.
- En Clientes, instale Windows 8.1 y la versión más reciente de Aplicación de la Tienda Windows de Lync para solucionar un problema con el inicio de sesión que, en general, ocurre cuando se utilizan varios dominios (por ejemplo, si el URI de SIP es **userA@domainZ.com** pero el servidor perimetral es **sip.domainX.com**).
Si la organización está suscrita a Lync Online u Office 365 y va a usar su propio nombre de dominio, debe llevar a cabo algunos pasos adicionales para configurar la red para la detección automática de los servidores de Lync. Los requisitos de la configuración de red son los mismos para Aplicación de la Tienda Windows de Lync y Lync en dispositivos móviles. Siga las instrucciones “Configurar la red” en el artículo Wiki de Office 365: “Configurar dispositivos móviles de Lync,” disponible en [http://go.microsoft.com/fwlink/?LinkId=271822](http://go.microsoft.com/fwlink/?linkid=271822).
## Vea también
#### Conceptos
[Implementar la aplicación de la Tienda Windows de Lync](lync-server-2013-deploying-lync-windows-store-app.md)
| 74.956522 | 618 | 0.791473 | spa_Latn | 0.969813 |
a9047070b37d6c155c447b44023746e9f0f649c9 | 598 | md | Markdown | 2018/Marco/06.md | crisgon/dailylog | 3b81eb6fb4a38755168e2814efa51cdcd9c86d09 | [
"MIT"
] | 8 | 2018-02-02T18:21:19.000Z | 2021-01-05T09:59:23.000Z | 2018/Marco/06.md | crisgon/dailylog | 3b81eb6fb4a38755168e2814efa51cdcd9c86d09 | [
"MIT"
] | null | null | null | 2018/Marco/06.md | crisgon/dailylog | 3b81eb6fb4a38755168e2814efa51cdcd9c86d09 | [
"MIT"
] | 8 | 2018-01-30T04:45:16.000Z | 2020-02-09T19:05:13.000Z | ## 06 de março :pushpin:
Hoje foi um dia complicado, tive poucos resultados, pois fiquei travado no exercicio 23 do js-ninja, criar uma calculadora... Só conseguir fazer a captura básica dos botões e estou tendo problema com a validação das operações.
### Artigos que Li :newspaper:
Não fiz nenhuma leitura hoje =/
### Códigos que escrevi :computer:
[Repositório dos exercícios do js-ninja](https://github.com/crisgon/curso-javascript-ninja)
### Materias que utilizei para estudo :scroll:
Minha fonte de estudos foi o [Developer Mozilla](https://developer.mozilla.org/pt-BR/docs)
| 22.148148 | 226 | 0.750836 | por_Latn | 0.999283 |
a904dc850ecd4711d9affbd1848e0a9ff9df0c3d | 80 | md | Markdown | README.md | rodrigoamurrio/practicas-java | 4cf974d865b4f185800f6ca6221e32c0e10adafd | [
"Apache-2.0"
] | null | null | null | README.md | rodrigoamurrio/practicas-java | 4cf974d865b4f185800f6ca6221e32c0e10adafd | [
"Apache-2.0"
] | null | null | null | README.md | rodrigoamurrio/practicas-java | 4cf974d865b4f185800f6ca6221e32c0e10adafd | [
"Apache-2.0"
] | null | null | null | # practicas-java
En este repositorio se subira mis practicas en lenguaje java.
| 20 | 61 | 0.8 | spa_Latn | 0.944091 |