hexsha
stringlengths 40
40
| size
int64 5
1.04M
| ext
stringclasses 6
values | lang
stringclasses 1
value | max_stars_repo_path
stringlengths 3
344
| max_stars_repo_name
stringlengths 5
125
| max_stars_repo_head_hexsha
stringlengths 40
78
| max_stars_repo_licenses
sequencelengths 1
11
| max_stars_count
int64 1
368k
⌀ | max_stars_repo_stars_event_min_datetime
stringlengths 24
24
⌀ | max_stars_repo_stars_event_max_datetime
stringlengths 24
24
⌀ | max_issues_repo_path
stringlengths 3
344
| max_issues_repo_name
stringlengths 5
125
| max_issues_repo_head_hexsha
stringlengths 40
78
| max_issues_repo_licenses
sequencelengths 1
11
| max_issues_count
int64 1
116k
⌀ | max_issues_repo_issues_event_min_datetime
stringlengths 24
24
⌀ | max_issues_repo_issues_event_max_datetime
stringlengths 24
24
⌀ | max_forks_repo_path
stringlengths 3
344
| max_forks_repo_name
stringlengths 5
125
| max_forks_repo_head_hexsha
stringlengths 40
78
| max_forks_repo_licenses
sequencelengths 1
11
| max_forks_count
int64 1
105k
⌀ | max_forks_repo_forks_event_min_datetime
stringlengths 24
24
⌀ | max_forks_repo_forks_event_max_datetime
stringlengths 24
24
⌀ | content
stringlengths 5
1.04M
| avg_line_length
float64 1.14
851k
| max_line_length
int64 1
1.03M
| alphanum_fraction
float64 0
1
| lid
stringclasses 191
values | lid_prob
float64 0.01
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
4db8cd1d6bdc3c1a3d44249e7db1dae8a17c53fe | 59 | md | Markdown | pages/_resume-new.md | connorjan/connorgoldberg.com | d73cc89f8c86a17017ddedf088591aaed19d4db5 | [
"MIT"
] | 4 | 2016-08-03T14:10:00.000Z | 2022-01-10T04:47:18.000Z | pages/_resume-new.md | connorjan/connorgoldberg.com | d73cc89f8c86a17017ddedf088591aaed19d4db5 | [
"MIT"
] | null | null | null | pages/_resume-new.md | connorjan/connorgoldberg.com | d73cc89f8c86a17017ddedf088591aaed19d4db5 | [
"MIT"
] | 2 | 2016-08-31T23:22:27.000Z | 2021-07-06T00:13:47.000Z | ---
layout: page
permalink: /resumenew/
title: Resume
---
| 8.428571 | 22 | 0.661017 | eng_Latn | 0.470139 |
4db920af06ff57c2340592e4b9d7e64706b043b3 | 44 | md | Markdown | README.md | hfu/q | f9fd1eee6d1b7f8a0847b089791974cb384b8cf5 | [
"Unlicense"
] | null | null | null | README.md | hfu/q | f9fd1eee6d1b7f8a0847b089791974cb384b8cf5 | [
"Unlicense"
] | null | null | null | README.md | hfu/q | f9fd1eee6d1b7f8a0847b089791974cb384b8cf5 | [
"Unlicense"
] | null | null | null | # q
Ruby implementation of quantity level q
| 14.666667 | 39 | 0.795455 | eng_Latn | 0.798093 |
4db9932bccfa9c296647323a9641f9b2195d703e | 1,802 | md | Markdown | bootstrap-htaccess-filter_module-error-on-godaddy/README.md | eladkarako/icompile | fdea5c6300696ae4b42ca83d53491764cd47d1c9 | [
"Unlicense"
] | 5 | 2020-02-29T08:33:39.000Z | 2021-12-20T12:24:42.000Z | bootstrap-htaccess-filter_module-error-on-godaddy/README.md | eladkarako/icompile | fdea5c6300696ae4b42ca83d53491764cd47d1c9 | [
"Unlicense"
] | 1 | 2019-10-10T19:14:28.000Z | 2019-10-10T19:14:29.000Z | bootstrap-htaccess-filter_module-error-on-godaddy/README.md | eladkarako/icompile | fdea5c6300696ae4b42ca83d53491764cd47d1c9 | [
"Unlicense"
] | 4 | 2019-06-15T12:28:35.000Z | 2021-12-20T12:24:37.000Z | The following part from <a title="https://github.com/billpatrianakos/matvre/blob/master/bootstrap.htaccess" href="https://github.com/billpatrianakos/matvre/blob/master/bootstrap.htaccess" target="_blank">https://github.com/billpatrianakos/matvre/blob/master/bootstrap.htaccess</a> does not seems to be working with GoDaddy's servers so remove it... unless you like the "Server Error 500" thing...
<pre># HTML, TXT, CSS, JavaScript, JSON, XML, HTC:
FilterDeclare COMPRESS
FilterProvider COMPRESS DEFLATE resp=Content-Type $text/html
FilterProvider COMPRESS DEFLATE resp=Content-Type $text/css
FilterProvider COMPRESS DEFLATE resp=Content-Type $text/plain
FilterProvider COMPRESS DEFLATE resp=Content-Type $text/xml
FilterProvider COMPRESS DEFLATE resp=Content-Type $text/x-component
FilterProvider COMPRESS DEFLATE resp=Content-Type $application/javascript
FilterProvider COMPRESS DEFLATE resp=Content-Type $application/json
FilterProvider COMPRESS DEFLATE resp=Content-Type $application/xml
FilterProvider COMPRESS DEFLATE resp=Content-Type $application/xhtml+xml
FilterProvider COMPRESS DEFLATE resp=Content-Type $application/rss+xml
FilterProvider COMPRESS DEFLATE resp=Content-Type $application/atom+xml
FilterProvider COMPRESS DEFLATE resp=Content-Type $application/vnd.ms-fontobject
FilterProvider COMPRESS DEFLATE resp=Content-Type $image/svg+xml
FilterProvider COMPRESS DEFLATE resp=Content-Type $application/x-font-ttf
FilterProvider COMPRESS DEFLATE resp=Content-Type $font/opentype
FilterChain COMPRESS
FilterProtocol COMPRESS DEFLATE change=yes;byteranges=no
</pre>
also this..
<pre>
# Rename session cookie to something else, than PHPSESSID
php_value session.name coolcookiename
</pre> | 62.137931 | 397 | 0.784684 | yue_Hant | 0.567324 |
4dba3a4492bbc56e4a9013ac3502831a74420c05 | 18,827 | md | Markdown | articles/active-directory-domain-services/scoped-synchronization.md | ialeksander1/azure-docs.pt-br | d5a7a2c2d4a31282f49bd1e35036cb1939911974 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory-domain-services/scoped-synchronization.md | ialeksander1/azure-docs.pt-br | d5a7a2c2d4a31282f49bd1e35036cb1939911974 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory-domain-services/scoped-synchronization.md | ialeksander1/azure-docs.pt-br | d5a7a2c2d4a31282f49bd1e35036cb1939911974 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Sincronização escopo para serviços de domínio Azure AD | Microsoft Docs
description: Saiba como configurar a sincronização escopo do Azure AD para um domínio gerenciado do Azure Active Directory Domain Services
services: active-directory-ds
author: iainfoulds
manager: daveba
ms.assetid: 9389cf0f-0036-4b17-95da-80838edd2225
ms.service: active-directory
ms.subservice: domain-services
ms.workload: identity
ms.topic: how-to
ms.date: 03/31/2020
ms.author: iainfou
ms.openlocfilehash: 9ef7e14cc2a290cc5583e3e599e278f98882152c
ms.sourcegitcommit: 62c5557ff3b2247dafc8bb482256fef58ab41c17
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 04/03/2020
ms.locfileid: "80654734"
---
# <a name="configure-scoped-synchronization-from-azure-ad-to-azure-active-directory-domain-services"></a>Configure a sincronização escopo do Azure AD para o Azure Active Directory Domain Services
Para fornecer serviços de autenticação, o Azure Active Directory Domain Services (Azure AD DS) sincroniza usuários e grupos do Azure AD. Em um ambiente híbrido, usuários e grupos de um ambiente AD DS (Active Directory Domain Services, serviços de domínio de diretório ativo) no local podem ser sincronizados primeiro com o Azure AD Connect e, em seguida, sincronizados com o Azure AD DS.
Por padrão, todos os usuários e grupos de um diretório Azure AD estão sincronizados com um domínio Gerenciado pelo Azure AD DS. Se você tiver necessidades específicas, você pode optar por sincronizar apenas um conjunto definido de usuários.
Este artigo mostra como criar um domínio gerenciado pelo Azure AD DS que usa sincronização escopo e, em seguida, alterar ou desativar o conjunto de usuários com escopo.
## <a name="scoped-synchronization-overview"></a>Visão geral da sincronização escopo
Por padrão, todos os usuários e grupos de um diretório Azure AD estão sincronizados com um domínio Gerenciado pelo Azure AD DS. Se apenas alguns usuários precisarem acessar o domínio gerenciado, você poderá sincronizar apenas essas contas de usuário. Esta sincronização escopo é baseada em grupo. Quando você configura a sincronização escopo baseada em grupo, apenas as contas de usuário que pertencem aos grupos especificados são sincronizadas ao domínio gerenciado pelo Azure AD DS.
A tabela a seguir descreve como usar a sincronização escopo:
| Estado atual | Estado desejado | Configuração necessária |
| --- | --- | --- |
| Um domínio gerenciado existente é configurado para sincronizar todas as contas e grupos de usuários. | Você deseja sincronizar apenas contas de usuário que pertencem a grupos específicos. | Você não pode mudar de sincronizar todos os usuários para usar sincronização com escopo. [Exclua o domínio gerenciado existente](delete-aadds.md)e siga as etapas deste artigo para recriar um domínio gerenciado pelo Azure AD DS com sincronização escopo configurada. |
| Nenhum domínio gerenciado existente. | Você deseja criar um novo domínio gerenciado e sincronizar apenas as contas de usuário que pertencem a grupos específicos. | Siga as etapas deste artigo para criar um domínio gerenciado pelo Azure AD DS com sincronização escopo configurada. |
| Um domínio gerenciado existente é configurado para sincronizar apenas contas que pertencem a grupos específicos. | Você deseja modificar a lista de grupos cujos usuários devem ser sincronizados com o domínio gerenciado pelo Azure AD DS. | Siga as etapas deste artigo para modificar a sincronização escopo. |
Você usa o portal Azure ou powerShell para configurar as configurações de sincronização com escopo:
| Ação | | |
|--|--|--|
| Crie um domínio gerenciado pelo Azure AD DS e configure a sincronização com escopo | [Azure portal](#enable-scoped-synchronization-using-the-azure-portal) | [PowerShell](#enable-scoped-synchronization-using-powershell) |
| Modificar sincronização escopo | [Azure portal](#modify-scoped-synchronization-using-the-azure-portal) | [PowerShell](#modify-scoped-synchronization-using-powershell) |
| Desativar a sincronização com escopo | [Azure portal](#disable-scoped-synchronization-using-the-azure-portal) | [PowerShell](#disable-scoped-synchronization-using-powershell) |
> [!WARNING]
> Alterar o escopo da sincronização faz com que o domínio Gerenciado pelo Azure AD DS ressincronizar todos os dados. As seguintes considerações se aplicam:
>
> * Quando você altera o escopo de sincronização de um domínio gerenciado pelo Azure AD DS, ocorre uma ressincronização completa.
> * Os objetos que não são mais necessários no domínio gerenciado pelo Azure AD DS são excluídos. Novos objetos são criados no domínio gerenciado.
> * A ressincronização pode levar muito tempo para ser concluída. O tempo de sincronização depende do número de objetos, como usuários, grupos e membros de grupos no domínio gerenciado do Azure AD DS e no diretório Azure AD. Para diretórios grandes com várias centenas de milhares de objetos, a ressincronização pode levar alguns dias.
## <a name="enable-scoped-synchronization-using-the-azure-portal"></a>Habilite a sincronização escopo usando o portal Azure
Para habilitar a sincronização escopo no portal Azure, complete as seguintes etapas:
1. Siga o [tutorial para criar e configurar uma instância Azure AD DS](tutorial-create-instance-advanced.md). Complete todos os pré-requisitos e etapas de implantação que não sejam para o escopo de sincronização.
1. Escolha **Escopo** na etapa de sincronização e selecione os grupos Azure AD para sincronizar a instância Azure AD DS.
O domínio gerenciado pelo Azure AD DS pode levar até uma hora para concluir a implantação. No portal Azure, a página **Visão geral** do domínio gerenciado pelo Azure AD DS mostra o status atual durante esta fase de implantação.
Quando o portal Azure mostra que o domínio gerenciado pelo Azure AD DS terminou o provisionamento, as seguintes tarefas precisam ser concluídas:
* Atualize as configurações de DNS da rede virtual, de modo que as máquinas virtuais possam encontrar o domínio gerenciado para ingresso no domínio ou autenticação.
* Para configurar o DNS, selecione o domínio gerenciado pelo Azure AD DS no portal. Na **janela Visão geral,** você é solicitado a configurar automaticamente essas configurações de DNS.
* [Habilite a sincronização de senha satisco no Azure AD Domain Services para](tutorial-create-instance-advanced.md#enable-user-accounts-for-azure-ad-ds) que os usuários finais possam entrar no domínio gerenciado usando suas credenciais corporativas.
## <a name="modify-scoped-synchronization-using-the-azure-portal"></a>Modificar sincronização escopo usando o portal Azure
Para modificar a lista de grupos cujos usuários devem ser sincronizados com o domínio gerenciado pelo Azure AD DS, complete as seguintes etapas:
1. No portal Azure, procure e selecione **Azure AD Domain Services**. Escolha sua instância, como *aaddscontoso.com*.
1. Selecione **Sincronização** no menu do lado esquerdo.
1. Para adicionar um grupo, escolha **+ Selecione grupos** na parte superior e escolha os grupos a serem adicionados.
1. Para remover um grupo do escopo de sincronização, selecione-o na lista de grupos sincronizados atualmente e escolha **Remover grupos**.
1. Quando todas as alterações forem feitas, selecione **Salvar o escopo de sincronização**.
Alterar o escopo da sincronização faz com que o domínio Gerenciado pelo Azure AD DS ressincronizar todos os dados. Os objetos que não são mais necessários no domínio gerenciado pelo Azure AD DS são excluídos e a ressincronização pode levar muito tempo para ser concluída.
## <a name="disable-scoped-synchronization-using-the-azure-portal"></a>Desativar a sincronização com escopo usando o portal Azure
Para desativar a sincronização com escopo baseada em grupo para um domínio gerenciado pelo Azure AD DS, complete as seguintes etapas:
1. No portal Azure, procure e selecione **Azure AD Domain Services**. Escolha sua instância, como *aaddscontoso.com*.
1. Selecione **Sincronização** no menu do lado esquerdo.
1. Defina o escopo de sincronização de **Escopo** para **Todos**e selecione **Salvar o escopo de sincronização**.
Alterar o escopo da sincronização faz com que o domínio Gerenciado pelo Azure AD DS ressincronizar todos os dados. Os objetos que não são mais necessários no domínio gerenciado pelo Azure AD DS são excluídos e a ressincronização pode levar muito tempo para ser concluída.
## <a name="powershell-script-for-scoped-synchronization"></a>Script PowerShell para sincronização escopo
Para configurar a sincronização escopo usando o PowerShell, primeiro `Select-GroupsToSync.ps1`salve o script a seguir em um arquivo chamado . Este script configura o Azure AD DS para sincronizar grupos selecionados do Azure AD. Todas as contas de usuário que fazem parte dos grupos especificados estão sincronizadas com o domínio gerenciado pelo Azure AD DS.
Este script é usado nas etapas adicionais deste artigo.
```powershell
param (
[Parameter(Position = 0)]
[String[]]$groupsToAdd
)
Connect-AzureAD
$sp = Get-AzureADServicePrincipal -Filter "AppId eq '2565bd9d-da50-47d4-8b85-4c97f669dc36'"
$role = $sp.AppRoles | where-object -FilterScript {$_.DisplayName -eq "User"}
Write-Output "`n****************************************************************************"
Write-Output "Total group-assignments need to be added: $($groupsToAdd.Count)"
$newGroupIds = New-Object 'System.Collections.Generic.HashSet[string]'
foreach ($groupName in $groupsToAdd)
{
try
{
$group = Get-AzureADGroup -Filter "DisplayName eq '$groupName'"
$newGroupIds.Add($group.ObjectId)
Write-Output "Group-Name: $groupName, Id: $($group.ObjectId)"
}
catch
{
Write-Error "Failed to find group: $groupName. Exception: $($_.Exception)."
}
}
Write-Output "****************************************************************************`n"
Write-Output "`n****************************************************************************"
$currentAssignments = Get-AzureADServiceAppRoleAssignment -ObjectId $sp.ObjectId
Write-Output "Total current group-assignments: $($currentAssignments.Count), SP-ObjectId: $($sp.ObjectId)"
$currAssignedObjectIds = New-Object 'System.Collections.Generic.HashSet[string]'
foreach ($assignment in $currentAssignments)
{
Write-Output "Assignment-ObjectId: $($assignment.PrincipalId)"
if ($newGroupIds.Contains($assignment.PrincipalId) -eq $false)
{
Write-Output "This assignment is not needed anymore. Removing it! Assignment-ObjectId: $($assignment.PrincipalId)"
Remove-AzureADServiceAppRoleAssignment -ObjectId $sp.ObjectId -AppRoleAssignmentId $assignment.ObjectId
}
else
{
$currAssignedObjectIds.Add($assignment.PrincipalId)
}
}
Write-Output "****************************************************************************`n"
Write-Output "`n****************************************************************************"
foreach ($id in $newGroupIds)
{
try
{
if ($currAssignedObjectIds.Contains($id) -eq $false)
{
Write-Output "Adding new group-assignment. Role-Id: $($role.Id), Group-Object-Id: $id, ResourceId: $($sp.ObjectId)"
New-AzureADGroupAppRoleAssignment -Id $role.Id -ObjectId $id -PrincipalId $id -ResourceId $sp.ObjectId
}
else
{
Write-Output "Group-ObjectId: $id is already assigned."
}
}
catch
{
Write-Error "Exception occurred assigning Object-ID: $id. Exception: $($_.Exception)."
}
}
Write-Output "****************************************************************************`n"
```
## <a name="enable-scoped-synchronization-using-powershell"></a>Habilite a sincronização escopo usando o PowerShell
Use o PowerShell para concluir o seguinte conjunto de etapas. Confira as instruções para [Habilitar o Azure Active Directory Domain Services usando o PowerShell](powershell-create-instance.md). Algumas das etapas neste artigo foram ligeiramente modificadas para configurar a sincronização no escopo.
1. Complete as seguintes tarefas do artigo para habilitar o Azure AD DS usando o PowerShell. Pare na etapa para realmente criar o domínio gerenciado. Você configura a sincronização escopo que você cria o domínio gerenciado pelo Azure AD DS.
* [Instale os módulos PowerShell necessários](powershell-create-instance.md#prerequisites).
* [Crie o principal de serviço necessário e o grupo Azure AD para acesso administrativo](powershell-create-instance.md#create-required-azure-ad-resources).
* [Crie recursos de suporte do Azure como uma rede virtual e sub-redes](powershell-create-instance.md#create-supporting-azure-resources).
1. Determine os grupos e usuários que eles contêm que você deseja sincronizar a partir do Azure AD. Faça uma lista dos nomes de exibição dos grupos para sincronizar com o Azure AD DS.
1. Execute o [script da seção anterior](#powershell-script-for-scoped-synchronization) e use o parâmetro *-groupsToAdd* para passar a lista de grupos para sincronizar.
> [!WARNING]
> Você deve incluir o grupo *Administradores AAD DC* na lista de grupos para sincronização escopo. Se você não incluir esse grupo, o domínio gerenciado pelo Azure AD DS será inutilizável.
```powershell
.\Select-GroupsToSync.ps1 -groupsToAdd @("AAD DC Administrators", "GroupName1", "GroupName2")
```
1. Agora crie o domínio gerenciado do Azure AD DS e habilite a sincronização escopo baseada em grupo. Inclua *"filteredSync" = "Ativado"* no parâmetro *-Propriedades.*
Defina seu ID de assinatura do Azure e, em seguida, forneça um nome para o domínio gerenciado, como *aaddscontoso.com*. Você pode obter seu ID de assinatura usando o [cmdlet Get-AzSubscription.][Get-AzSubscription] Defina o nome do grupo de recursos, o nome da rede virtual e a região para os valores usados nas etapas anteriores para criar os recursos do Azure de suporte:
```powershell
$AzureSubscriptionId = "YOUR_AZURE_SUBSCRIPTION_ID"
$ManagedDomainName = "aaddscontoso.com"
$ResourceGroupName = "myResourceGroup"
$VnetName = "myVnet"
$AzureLocation = "westus"
# Enable Azure AD Domain Services for the directory.
New-AzResource -ResourceId "/subscriptions/$AzureSubscriptionId/resourceGroups/$ResourceGroupName/providers/Microsoft.AAD/DomainServices/$ManagedDomainName" `
-Location $AzureLocation `
-Properties @{"DomainName"=$ManagedDomainName; "filteredSync" = "Enabled"; `
"SubnetId"="/subscriptions/$AzureSubscriptionId/resourceGroups/$ResourceGroupName/providers/Microsoft.Network/virtualNetworks/$VnetName/subnets/DomainServices"} `
-Force -Verbose
```
Leva alguns minutos para criar o recurso e retornar o controle ao prompt powershell. O domínio gerenciado pelo Azure AD DS continua a ser provisionado em segundo plano e pode levar até uma hora para concluir a implantação. No portal Azure, a página **Visão geral** do domínio gerenciado pelo Azure AD DS mostra o status atual durante esta fase de implantação.
Quando o portal Azure mostra que o domínio gerenciado pelo Azure AD DS terminou o provisionamento, as seguintes tarefas precisam ser concluídas:
* Atualize as configurações de DNS da rede virtual, de modo que as máquinas virtuais possam encontrar o domínio gerenciado para ingresso no domínio ou autenticação.
* Para configurar o DNS, selecione o domínio gerenciado pelo Azure AD DS no portal. Na **janela Visão geral,** você é solicitado a configurar automaticamente essas configurações de DNS.
* Se você criou um domínio gerenciado pelo Azure AD DS em uma região que suporta Zonas de disponibilidade, crie um grupo de segurança de rede para restringir o tráfego na rede virtual para o domínio gerenciado pelo Azure AD DS. Um balanceador de carga padrão do Azure é criado que exige que essas regras sejam colocadas. Esse grupo de segurança de rede protege o Azure AD DS e é necessário para que o domínio gerenciado funcione corretamente.
* Para criar o grupo de segurança da rede e as regras necessárias, selecione o domínio gerenciado pelo Azure AD DS no portal. Na janela **Visão geral,** você é solicitado a criar e configurar automaticamente o grupo de segurança da rede.
* [Habilite a sincronização de senha satisco no Azure AD Domain Services para](tutorial-create-instance-advanced.md#enable-user-accounts-for-azure-ad-ds) que os usuários finais possam entrar no domínio gerenciado usando suas credenciais corporativas.
## <a name="modify-scoped-synchronization-using-powershell"></a>Modificar sincronização escopo usando powershell
Para modificar a lista de grupos cujos usuários devem ser sincronizados com o domínio gerenciado pelo Azure AD DS, execute novamente o [script PowerShell](#powershell-script-for-scoped-synchronization) e especifique a nova lista de grupos. No exemplo a seguir, os grupos para sincronizar não incluem mais *GroupName2*e agora incluem *GroupName3*.
> [!WARNING]
> Você deve incluir o grupo *Administradores AAD DC* na lista de grupos para sincronização escopo. Se você não incluir esse grupo, o domínio gerenciado pelo Azure AD DS será inutilizável.
```powershell
.\Select-GroupsToSync.ps1 -groupsToAdd @("AAD DC Administrators", "GroupName1", "GroupName3")
```
Alterar o escopo da sincronização faz com que o domínio Gerenciado pelo Azure AD DS ressincronizar todos os dados. Os objetos que não são mais necessários no domínio gerenciado pelo Azure AD DS são excluídos e a ressincronização pode levar muito tempo para ser concluída.
## <a name="disable-scoped-synchronization-using-powershell"></a>Desativar a sincronização com escopo usando o PowerShell
Para desativar a sincronização escopo baseada em grupo para um domínio gerenciado pelo Azure AD DS, defina *"filteredSync" = "Disabled"* no recurso Azure AD DS e atualize o domínio gerenciado. Quando concluído, todos os usuários e grupos são definidos para sincronizar a partir do Azure AD.
```powershell
// Retrieve the Azure AD DS resource.
$DomainServicesResource = Get-AzResource -ResourceType "Microsoft.AAD/DomainServices"
// Disable group-based scoped synchronization.
$disableScopedSync = @{"filteredSync" = "Disabled"}
// Update the Azure AD DS resource
Set-AzResource -Id $DomainServicesResource.ResourceId -Properties $disableScopedSync
```
Alterar o escopo da sincronização faz com que o domínio Gerenciado pelo Azure AD DS ressincronizar todos os dados. Os objetos que não são mais necessários no domínio gerenciado pelo Azure AD DS são excluídos e a ressincronização pode levar muito tempo para ser concluída.
## <a name="next-steps"></a>Próximas etapas
Para saber mais sobre o processo de sincronização, consulte [Entender a sincronização no Azure AD Domain Services](synchronization.md).
<!-- EXTERNAL LINKS -->
[Get-AzSubscription]: /powershell/module/Az.Accounts/Get-AzSubscription
| 71.858779 | 484 | 0.765071 | por_Latn | 0.99792 |
4dba6cdf8f48f93769dcf3376da1e52cdabf2b8f | 4,304 | md | Markdown | notes/v1.0.0-M9.md | fooblahblah/bloop | 34110ad72fc0eb988b3f16bafcdfe7e289dbfcf3 | [
"Apache-2.0"
] | 845 | 2017-11-30T19:30:12.000Z | 2022-03-31T06:24:06.000Z | notes/v1.0.0-M9.md | fooblahblah/bloop | 34110ad72fc0eb988b3f16bafcdfe7e289dbfcf3 | [
"Apache-2.0"
] | 1,113 | 2017-11-30T19:09:11.000Z | 2022-03-31T11:39:22.000Z | notes/v1.0.0-M9.md | fooblahblah/bloop | 34110ad72fc0eb988b3f16bafcdfe7e289dbfcf3 | [
"Apache-2.0"
] | 192 | 2017-11-30T20:16:53.000Z | 2022-03-15T22:43:08.000Z | # Bloop v1.0.0-M9
Bloop is getting closer and closer to 1.0.0! :walking_man:
**This milestone of Bloop includes changes to the configuration files; you'll need to re-generate
your configuration files if you used a previous version of Bloop. See the [installation
instructions][installation instructions].**
## Install the latest release :candy:
If you're on Mac OS X, upgrade to the latest version with:
```sh
$ brew install scalacenter/bloop/bloop
```
Otherwise, run:
```
$ curl -L https://github.com/scalacenter/bloop/releases/download/v1.0.0-M9/install.py | python
```
Read the complete instructions in our [Installation page][installation instructions].
## Highlights
#### [Change configuration file to JSON][#415] :memo:
**Requires a complete regeneration of configuration files**
The configuration file didn't have a well-specified format that could be reused
by external tools, was difficult to read and write and didn't allow the
representation of nested data structures. Java properties were flexible, but
didn't quite cut them as a good configuration file.
This release replaces the Java properties file with JSON configuration files,
accompanied of a JSON schema, accessible in [The Configuration
Format][configuration] docs. The docs display with `docson` the json schema.
Bloop v1.0.0-M9 also includes the `bloop-config` Scala artifact so that
external tools can read and write Bloop configuration files.
We hope that this format makes it easier to integrate with bloop.
#### [Support for test options][#415] :person_fencing:
**Requires a complete regeneration of configuration files**
Bloop now supports options for the test frameworks, and they can be specified
in the configuration file.
These options are framework specific. They specify `excludes` and the test
arguments passed in to the test server initialization.
This new feature allows to fix a bug in JUnit test execution. The JUnit test
framework required the `-z` defaults to show the test logs, and those defaults
are now visible in the configuration files and interpreted by bloop test
runner. [#329][] is now fixed.
#### [Remove stale configuration files in sbt][#104] :hammer:
Stale configuration files are configuration files for projects that have been
removed from the stock build tool after doing `bloopInstall`. These
configuration files stay in the configuration directory if they are not removed
manually by the user. Their presence causes bloop to load them up and try to
compile projects that don't exist anymore. As a result, bloop now removes these
files if it detects that a project has been removed.
#### [The configuration directory has been migrated to `.bloop`][#411] :rocket:
**Requires a complete regeneration of configuration files**
The previous default configuration directory was `.bloop-config`, which was
a misnomer given that bloop also stores the analysis files and the classes
directory within `.bloop-config`.
This release makes `.bloop` the new default one. Make sure you add it to your
`.gitignore` file to avoid pushing the configuration files to your repository.
#### [Use user nailgun environment to run and test projects][#413] :wrench:
Bloop didn't expose the environment variables from the use site to the test or
main runners.
With this change, any environment variable that you update at the CLI use site
will be visible to Bloop, and therefore accessible in your test suites and main
classes.
#### [Detect `compile->test` and `test->compile` dependencies][#409] :male_detective:
Generating configuration files for `compile->test` and `test->compile`
configurations is common when you want the tests of a project to depend only on
the compile of a downstream project.
This release makes sbt-bloop recognize these dependencies and output the correct
dependencies.
[#104]: https://github.com/scalacenter/bloop/issues/104
[#411]: https://github.com/scalacenter/bloop/pull/411
[#409]: https://github.com/scalacenter/bloop/pull/409
[#413]: https://github.com/scalacenter/bloop/pull/413
[#415]: https://github.com/scalacenter/bloop/pull/415
[#329]: https://github.com/scalacenter/bloop/issues/329
[installation instructions]: https://scalacenter.github.io/bloop/docs/installation
[configuration]: https://scalacenter.github.io/bloop/docs/configuration-format/
| 40.603774 | 97 | 0.781366 | eng_Latn | 0.994814 |
4dbadde55f86b6f5e8102d5b2c7c68db5ed9770e | 8,219 | md | Markdown | README.md | xsharkx/CAP | 450c01dbc355040140b0ac313ae3137fbc02a29f | [
"MIT"
] | 3 | 2021-04-08T16:44:01.000Z | 2021-04-12T20:23:00.000Z | README.md | CoolMoonGG/CAP | 273e7bf4a8fc41537857aeba1fe4dabbd260d1cf | [
"MIT"
] | null | null | null | README.md | CoolMoonGG/CAP | 273e7bf4a8fc41537857aeba1fe4dabbd260d1cf | [
"MIT"
] | 1 | 2021-03-25T01:51:04.000Z | 2021-03-25T01:51:04.000Z | # CAP [中文](https://github.com/dotnetcore/CAP/blob/develop/README.zh-cn.md)
[](https://travis-ci.org/dotnetcore/CAP)
[](https://ci.appveyor.com/project/yuleyule66/cap)
[](https://www.nuget.org/packages/DotNetCore.CAP/)
[](https://www.nuget.org/packages/DotNetCore.CAP/)
[](https://github.com/dotnetcore)
[](https://raw.githubusercontent.com/dotnetcore/CAP/master/LICENSE.txt)
CAP is a library based on .Net standard, which is a solution to deal with distributed transactions, also has the function of EventBus, it is lightweight, easy to use, and efficiently.
## OverView
In the process of building an SOA or MicroService system, we usually need to use the event to integrate each services. In the process, the simple use of message queue does not guarantee the reliability. CAP is adopted the local message table program integrated with the current database to solve the exception may occur in the process of the distributed system calling each other. It can ensure that the event messages are not lost in any case.
You can also use the CAP as an EventBus. The CAP provides a simpler way to implement event publishing and subscriptions. You do not need to inherit or implement any interface during the process of subscription and sending.
This is a diagram of the CAP working in the ASP.NET Core MicroService architecture:
> The solid line in the figure represents the user code, and the dotted line represents the internal implementation of the CAP.
## Getting Started
### NuGet
You can run the following command to install the CAP in your project.
```
PM> Install-Package DotNetCore.CAP
```
If you want use Kafka to send integrating event, installing by:
```
PM> Install-Package DotNetCore.CAP.Kafka
```
If you want use RabbitMQ to send integrating event, installing by:
```
PM> Install-Package DotNetCore.CAP.RabbitMQ
```
CAP supports SqlServer, MySql, PostgreSql as event log storage.
```
// select a database provider you are using, event log table will integrate into.
PM> Install-Package DotNetCore.CAP.SqlServer
PM> Install-Package DotNetCore.CAP.MySql
PM> Install-Package DotNetCore.CAP.PostgreSql
```
### Configuration
First,You need to config CAP in your Startup.cs：
```cs
public void ConfigureServices(IServiceCollection services)
{
//......
services.AddDbContext<AppDbContext>();
services.AddCap(x =>
{
// If you are using EF, you need to add the following configuration：
// Notice: You don't need to config x.UseSqlServer(""") again! CAP can autodiscovery.
x.UseEntityFramework<AppDbContext>();
// If you are using ado.net,you need to add the configuration：
x.UseSqlServer("Your ConnectionStrings");
x.UseMySql("Your ConnectionStrings");
x.UsePostgreSql("Your ConnectionStrings");
// If you are using RabbitMQ, you need to add the configuration：
x.UseRabbitMQ("localhost");
// If you are using Kafka, you need to add the configuration：
x.UseKafka("localhost");
});
}
public void Configure(IApplicationBuilder app)
{
//.....
app.UseCap();
}
```
### Publish
Inject `ICapPublisher` in your Controller, then use the `ICapPublisher` to send message
```c#
public class PublishController : Controller
{
[Route("~/publishWithTransactionUsingEF")]
public async Task<IActionResult> PublishMessageWithTransactionUsingEF([FromServices]AppDbContext dbContext, [FromServices]ICapPublisher publisher)
{
using (var trans = dbContext.Database.BeginTransaction())
{
// your business code
//If you are using EF, CAP will automatic discovery current environment transaction, so you do not need to explicit pass parameters.
//Achieving atomicity between original database operation and the publish event log thanks to a local transaction.
await publisher.PublishAsync("xxx.services.account.check", new Person { Name = "Foo", Age = 11 });
trans.Commit();
}
return Ok();
}
[Route("~/publishWithTransactionUsingAdonet")]
public async Task<IActionResult> PublishMessageWithTransactionUsingAdonet([FromServices]ICapPublisher publisher)
{
var connectionString = "";
using (var sqlConnection = new SqlConnection(connectionString))
{
sqlConnection.Open();
using (var sqlTransaction = sqlConnection.BeginTransaction())
{
// your business code
publisher.Publish("xxx.services.account.check", new Person { Name = "Foo", Age = 11 }, sqlTransaction);
sqlTransaction.Commit();
}
}
return Ok();
}
}
```
### Subscribe
**Action Method**
Add the Attribute `[CapSubscribe()]` on Action to subscribe message:
```c#
public class PublishController : Controller
{
[CapSubscribe("xxx.services.account.check")]
public async Task CheckReceivedMessage(Person person)
{
Console.WriteLine(person.Name);
Console.WriteLine(person.Age);
return Task.CompletedTask;
}
}
```
**Service Method**
If your subscribe method is not in the Controller,then your subscribe class need to Inheritance `ICapSubscribe`:
```c#
namespace xxx.Service
{
public interface ISubscriberService
{
public void CheckReceivedMessage(Person person);
}
public class SubscriberService: ISubscriberService, ICapSubscribe
{
[CapSubscribe("xxx.services.account.check")]
public void CheckReceivedMessage(Person person)
{
}
}
}
```
Then inject your `ISubscriberService` class in Startup.cs
```c#
public void ConfigureServices(IServiceCollection services)
{
//Note: The injection of services needs before of `services.AddCap()`
services.AddTransient<ISubscriberService,SubscriberService>();
services.AddCap(x=>{});
}
```
### Dashboard
CAP 2.1 and above provides the dashboard pages, you can easily view the sent and received messages. In addition, you can also view the message status in real time on the dashboard.
In the distributed environment, the dashboard built-in integrated [Consul](http://consul.io) as a node discovery, while the realization of the gateway agent function, you can also easily view the node or other node data, It's like you are visiting local resources.
```c#
services.AddCap(x =>
{
//...
// Register Dashboard
x.UseDashboard();
// Register to Consul
x.UseDiscovery(d =>
{
d.DiscoveryServerHostName = "localhost";
d.DiscoveryServerPort = 8500;
d.CurrentNodeHostName = "localhost";
d.CurrentNodePort = 5800;
d.NodeId = 1;
d.NodeName = "CAP No.1 Node";
});
});
```
The default dashboard address is :[http://localhost:xxx/cap](http://localhost:xxx/cap) , you can also change the `cap` suffix to others with `d.MatchPath` configuration options.
## Contribute
One of the easiest ways to contribute is to participate in discussions and discuss issues. You can also contribute by submitting pull requests with code changes.
### License
[MIT](https://github.com/dotnetcore/CAP/blob/master/LICENSE.txt)
| 33.96281 | 444 | 0.711765 | eng_Latn | 0.765586 |
4dbb03025e52a42d0155406d93be6bd2169d50c2 | 3,713 | md | Markdown | deployments/docker/README.md | swipswaps/signalfx-agent | 4d3a5a7f6ed898e676b2aa75608eff15c5bb9fd7 | [
"Apache-2.0"
] | 1 | 2020-04-14T08:31:12.000Z | 2020-04-14T08:31:12.000Z | deployments/docker/README.md | swipswaps/signalfx-agent | 4d3a5a7f6ed898e676b2aa75608eff15c5bb9fd7 | [
"Apache-2.0"
] | 55 | 2022-01-24T11:40:41.000Z | 2022-03-31T11:31:33.000Z | deployments/docker/README.md | swipswaps/signalfx-agent | 4d3a5a7f6ed898e676b2aa75608eff15c5bb9fd7 | [
"Apache-2.0"
] | null | null | null | # SignalFx Agent Docker Image
We provide a Docker image at
[quay.io/signalfx/signalfx-agent](https://quay.io/signalfx/signalfx-agent). The
image is tagged using the same agent version scheme.
If you are using Docker outside of Kubernetes, you can run the agent in a
Docker container and still gather metrics on the underlying host by running it
with the following flags:
```sh
$ docker run \
--name signalfx-agent \
--pid host \
--net host \
-v /:/hostfs:ro \
-v /var/run/docker.sock:/var/run/docker.sock:ro \
-v /etc/signalfx/:/etc/signalfx/:ro \
-v /etc/passwd:/etc/passwd:ro \
quay.io/signalfx/signalfx-agent:<version>
```
This assumes you have the agent config in the conventional directory
(`/etc/signalfx`) on the root mount namespace. If you want to use a default,
built-in configuration, omit the volume bind mount for the `/etc/signalfx`
directory and see [Configuration](#configuration).
If you have the Docker API available through the conventional UNIX domain
socket, you should mount that in to be able to use the
[docker-container-stats](../../docs/monitors/docker-container-stats.md) monitor.
It is necessary to mount in the host root filesystem at `/hostfs` in order to
get disk usage metrics for the host filesystems using the [filesystems
monitor](../../docs/monitors/filesystems.md). You will need to set the
`hostFSPath: /hostfs` config option on that monitor to make it use this
non-default path.
The other special config you will need is the `etcPath: /hostfs/etc` option
under the [host-metadata](../../docs/monitors/host-metadata.md) monitor config.
This tells it where to find certain files like `/etc/os-release` that are used
to generate host metadata such as the Linux distro and version.
By using the `--pid host` flag, the `/proc` filesystem in the container will
match the host's, so that no special configuration of the `/proc` path is
required.
You may also want to use the [Docker observer](../../docs/observers/docker.md) to
automatically discover other containers running in the same Docker engine.
## Configuration
For any non-trivial use-cases you will need to provide a custom configuration
file, but for simple setups or demo purposes, you can use [the supplied agent
configuration file](./agent.yaml) in the image by omitting the `-v
/etc/signalfx:/etc/signalfx/:ro` flag in the run command above. Then you can
set the following environment variables on the agent container:
| Environment Variable | Required | Description |
| --------- | -------- | ----------- |
| `SFX_ACCESS_TOKEN` | **yes** | The SignalFx API access token. |
| `SFX_INGEST_URL` | no | Often used in conjunction with the [SignalFx Gateway](https://github.com/signalfx/gateway) to specify a different target URL for datapoints and events. If not specified, this defaults to the global SignalFx ingest server. |
| `SFX_API_URL` | no | If you are operating in a different SignalFx realm, this value will need to be set to the SignalFx API server URL in your realm. |
The supplied configuration will also load any additional yaml files found in `/etc/signalfx/monitors/` as
part of the `monitors` list in the agent config like so:
```yaml
monitors:
- {"#from": "/etc/signalfx/monitors/*.yaml", flatten: true, optional: true}
- type: cpu
...
```
For example, you can add an ElasticSearch monitor to a configuration by
providing a Docker volume mount to `/etc/signalfx/monitors/` with a file that
follows the [monitor config schema](../../docs/monitor-config.md):
```yaml
- elasticsearch
host: localhost
port: 9200
```
Other options could be specified according to the [ElasticSearch Monitor
configuration](../../docs/monitors/elasticsearch.md)
| 43.174419 | 249 | 0.741988 | eng_Latn | 0.991363 |
4dbb2b2dc5011c15e7e14b476307f72f65f231a3 | 749 | md | Markdown | README.md | christinelfrank16/cupcake-shop | afeec01ae8cc6ca09a9757003a64c97d63f5d011 | [
"MIT"
] | null | null | null | README.md | christinelfrank16/cupcake-shop | afeec01ae8cc6ca09a9757003a64c97d63f5d011 | [
"MIT"
] | null | null | null | README.md | christinelfrank16/cupcake-shop | afeec01ae8cc6ca09a9757003a64c97d63f5d011 | [
"MIT"
] | null | null | null | # Cupcake Shop
#### A webpage dedicated to displaying the items sold by a cupcake shop, 9-Aug-2019
#### By Christine Frank & Anita Kemp
## Description
The purpose of this webpage is to display the cupcakes sold by the cupcake shop.
## Setup Steps
#### View a local version of this site
* Clone this repository
* At the local repository, copy the full path of the index.html file
* Open a new web browser
* Paste the copied path into the browser
## Known Bugs
* None Known
## Contact Details
Email: [email protected]
LinkedIn: https://www.linkedin.com/in/christine-frank-b482005a
## Technologies Used
* HTML
* CSS
* Bootstrap
### License
Copyright (c) 2019 **Christine Frank**
This software is licensed under the MIT license.
| 23.40625 | 83 | 0.738318 | eng_Latn | 0.938776 |
4dbb3099af6586fcb9c34eb969187be9602f62ac | 4,538 | md | Markdown | documentation/scenarios/using-system-drawing-common.md | ScriptBox99/dotnet-docker | 2a2faa7339d2cd04b53c5cf1fca84aed42f41cc8 | [
"MIT"
] | 3,485 | 2015-11-18T16:13:49.000Z | 2022-03-30T11:21:43.000Z | documentation/scenarios/using-system-drawing-common.md | ScriptBox99/dotnet-docker | 2a2faa7339d2cd04b53c5cf1fca84aed42f41cc8 | [
"MIT"
] | 2,058 | 2015-11-18T16:30:58.000Z | 2022-03-31T13:03:38.000Z | documentation/scenarios/using-system-drawing-common.md | ScriptBox99/dotnet-docker | 2a2faa7339d2cd04b53c5cf1fca84aed42f41cc8 | [
"MIT"
] | 1,890 | 2015-11-19T03:59:53.000Z | 2022-03-31T16:18:10.000Z | # Using the System.Drawing.Common Package in a Docker Container
If your application makes use of the System.Drawing.Common NuGet package, you'll need to ensure some additional dependencies are installed in your Docker container for both Linux and Windows. See #618 (Linux) and #1098 (Windows) for more info on this issue.
## Linux
For Linux, it's just a matter of installing a few extra packages in your Dockerfile:
Debian/Ubuntu:
```Dockerfile
# install System.Drawing native dependencies
RUN apt-get update \
&& apt-get install -y --allow-unauthenticated \
libc6-dev \
libgdiplus \
libx11-dev \
&& rm -rf /var/lib/apt/lists/*
```
Alpine:
```Dockerfile
# install System.Drawing native dependencies
RUN apk add \
--no-cache \
--repository http://dl-3.alpinelinux.org/alpine/edge/testing/ \
libgdiplus
```
## Windows
For Windows, it's going to be more work because the required dependencies are not available in Windows Nano Server, the OS type which the official .NET images for Windows are based on. With .NET 5.0 and higher, official images for Windows Server Core are available so it's recommended to use those images if you can. Otherwise, you'll need to use the [Windows Server Core](https://hub.docker.com/_/microsoft-windows-servercore) or [Windows](https://hub.docker.com/_/microsoft-windows) images that are installed with the necessary dependencies. Note that the [Server Core](https://hub.docker.com/_/microsoft-windows-servercore) and [Windows](https://hub.docker.com/_/microsoft-windows) images are substantially larger than [Nano Server](https://hub.docker.com/_/microsoft-windows-nanoserver) images.
You have two deployment options available: you can choose to use a [framework-dependent](https://docs.microsoft.com/dotnet/core/deploying/#framework-dependent-deployments-fdd) or [self-contained](https://docs.microsoft.com/dotnet/core/deploying/#self-contained-deployments-scd) deployment. A framework-dependent deployment requires that the .NET runtime be installed on the base image whereas with a self-contained deployment, the app and all of its dependencies (including .NET) are deployed together.
### Self-contained deployment
A self-contained deployment is particularly handy in this scenario where there's a dependency on the System.Drawing.Common package. This is because there's no need to use a base image that has .NET installed. By deploying your app and all of its .NET dependencies, you can select the particular Windows base image that meets your need. In this example, since Windows Server Core has the required files and Nano Server does not, you can simply select a Windows Server Core image to use as your base image.
```Dockerfile
FROM mcr.microsoft.com/dotnet/sdk:3.1-nanoserver-ltsc2022 AS build
WORKDIR /app
# copy csproj and restore as distinct layers
COPY *.csproj .
RUN dotnet restore
# copy and publish app and libraries
COPY . .
RUN dotnet publish -c Release -o out -r win-x64 --self-contained true
# reference the Server Core image from the windows repo
FROM mcr.microsoft.com/windows/servercore:ltsc2022 AS runtime
WORKDIR /app
COPY --from=build /app/out ./
ENTRYPOINT ["dotnetapp"]
```
### Framework-dependent deployment
For a framework-dependent deployment, you're relying on .NET being installed in the base image you'll be referencing. Because there are no official .NET Core 3.1 images based on [Windows Server Core](https://hub.docker.com/_/microsoft-windows-servercore) or [Windows](https://hub.docker.com/_/microsoft-windows), you'll need to author a Dockerfile that installs .NET Core yourself.
Follow the instructions for [Installing .NET in a Dockerfile](installing-dotnet.md) in order to create a custom image based on [Windows Server Core](https://hub.docker.com/_/microsoft-windows-servercore) or [Windows](https://hub.docker.com/_/microsoft-windows) that has .NET Core installed. For this example, let's say that you've tagged your image as `servercore/runtime:3.1`. You can then construct your application's Dockerfile to reference that tag as the base image:
```Dockerfile
FROM mcr.microsoft.com/dotnet/sdk:3.1-nanoserver-ltsc2022 AS build
WORKDIR /app
# copy csproj and restore as distinct layers
COPY *.csproj .
RUN dotnet restore
# copy and publish app and libraries
COPY . .
RUN dotnet publish -c Release -o out
# reference custom Server Core runtime image tag
FROM servercore/runtime:3.1 AS runtime
WORKDIR /app
COPY --from=build /app/out ./
ENTRYPOINT ["dotnet", "dotnetapp.dll"]
```
| 50.988764 | 798 | 0.7684 | eng_Latn | 0.967124 |
4dbd7d69d16e1603c83fef541b73c8b3ac238e8c | 1,363 | md | Markdown | CONTRIBUTING.md | holodata/ancient-one-dark | f30f29a6f81834c1158d49dd33d7bb4e12f8b579 | [
"MIT"
] | 5 | 2021-11-03T08:21:47.000Z | 2022-03-11T10:17:33.000Z | CONTRIBUTING.md | holodata/ancient-one-dark | f30f29a6f81834c1158d49dd33d7bb4e12f8b579 | [
"MIT"
] | null | null | null | CONTRIBUTING.md | holodata/ancient-one-dark | f30f29a6f81834c1158d49dd33d7bb4e12f8b579 | [
"MIT"
] | null | null | null | # Dev
## What's in the folder
- This folder contains all of the files necessary for your color theme extension.
- `package.json` - this is the manifest file that defines the location of the theme file and specifies the base theme of the theme.
- `themes/*-color-theme.json` - the color theme definition file.
## Get up and running straight away
- Press `F5` to open a new window with your extension loaded.
- Open `File > Preferences > Color Themes` and pick your color theme.
- Open a file that has a language associated. The languages' configured grammar will tokenize the text and assign 'scopes' to the tokens. To examine these scopes, invoke the `Developer: Inspect Editor Tokens and Scopes` command from the Command Palette (`Ctrl+Shift+P` or `Cmd+Shift+P` on Mac) .
## Make changes
- Changes to the theme file are automatically applied to the Extension Development Host window.
## Install your extension
- To start using your extension with Visual Studio Code copy it into the `<user home>/.vscode/extensions` folder and restart Code.
- To share your extension with the world, read on https://code.visualstudio.com/docs about publishing an extension.
## Publish
```bash
vsce publish <major|minor|patch>
```
## References
- [Extension Manifest | Visual Studio Code Extension API](https://code.visualstudio.com/api/references/extension-manifest)
| 41.30303 | 295 | 0.760822 | eng_Latn | 0.986975 |
4dbda856b092323f08a0a97085545a3c7e1f0018 | 1,237 | md | Markdown | docs/relational-databases/system-functions/system-trace-functions.md | serverclient/sql-docs.zh-tw | bd5bf3d5c1d97e133627f930d18a07cfc6f657ce | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/relational-databases/system-functions/system-trace-functions.md | serverclient/sql-docs.zh-tw | bd5bf3d5c1d97e133627f930d18a07cfc6f657ce | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/relational-databases/system-functions/system-trace-functions.md | serverclient/sql-docs.zh-tw | bd5bf3d5c1d97e133627f930d18a07cfc6f657ce | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
description: 系統追蹤函數
title: 系統追蹤函數 |Microsoft Docs
ms.custom: ''
ms.date: 03/14/2017
ms.prod: sql
ms.prod_service: database-engine
ms.reviewer: ''
ms.technology: system-objects
ms.topic: language-reference
dev_langs:
- TSQL
ms.assetid: 166426e1-555d-4ce4-bae3-248dcac56883
author: WilliamDAssafMSFT
ms.author: wiassaf
ms.openlocfilehash: 546b524bced8719422ec94825094f268fcfa1d36
ms.sourcegitcommit: a9e982e30e458866fcd64374e3458516182d604c
ms.translationtype: MT
ms.contentlocale: zh-TW
ms.lasthandoff: 01/11/2021
ms.locfileid: "98092758"
---
# <a name="system-trace-functions"></a>系統追蹤函數
[!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] 提供下列系統追蹤函數。
## <a name="in-this-section"></a>本節內容
[fn_trace_geteventinfo](../../relational-databases/system-functions/sys-fn-trace-geteventinfo-transact-sql.md)
[fn_trace_getfilterinfo](../../relational-databases/system-functions/sys-fn-trace-getfilterinfo-transact-sql.md)
[fn_trace_getinfo](../../relational-databases/system-functions/sys-fn-trace-getinfo-transact-sql.md)
[fn_trace_gettable](../../relational-databases/system-functions/sys-fn-trace-gettable-transact-sql.md)
| 32.552632 | 115 | 0.763137 | yue_Hant | 0.278372 |
4dbdf5de877e6c04ab529f7629f9f9061a3c6eff | 2,231 | md | Markdown | Skype/SfbServer/deploy/deploy-enterprise-voice/view-sip-info.md | afilosa/OfficeDocs-SkypeForBusiness | 80ece4f981bf33252ab8010785c25d5177aa2847 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | Skype/SfbServer/deploy/deploy-enterprise-voice/view-sip-info.md | afilosa/OfficeDocs-SkypeForBusiness | 80ece4f981bf33252ab8010785c25d5177aa2847 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | Skype/SfbServer/deploy/deploy-enterprise-voice/view-sip-info.md | afilosa/OfficeDocs-SkypeForBusiness | 80ece4f981bf33252ab8010785c25d5177aa2847 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "View information about individual SIP trunks in Skype for Business Server"
ms.reviewer:
ms.author: v-cichur
author: cichur
manager: serdars
audience: ITPro
ms.topic: quickstart
ms.prod: skype-for-business-itpro
f1.keywords:
- NOCSH
localization_priority: Normal
ms.collection:
- IT_Skype16
- Strat_SB_Admin
ms.custom:
ms.assetid: adfacb74-7ea5-4c53-934e-ba7ec59879eb
description: "Summary: Learn how to view information about SIP trunks in Skype for Business Server."
---
# View information about individual SIP trunks in Skype for Business Server
**Summary:** Learn how to view information about SIP trunks in Skype for Business Server.
SIP trunks are used to connect Skype for Business Server Voice over IP phone network with the Public Switched Telephone Network (PSTN). In previous version of the product, trunks were used to route outbound calls from a Mediation Server to a PSTN gateway and each gateway was limited to a single trunk. As a result, a PSTN gateway and a SIP trunk were essentially identical. For administrators, that meant they could view information about an individual SIP trunk simply by viewing information about the associated PSTN gateway.
In Skype for Business Server, however, multiple trunks can now be assigned to a single PSTN gateway; this means that gateways and trunks are no longer one and the same. In turn, that means that administrators must use the new [Get-CsTrunk](/powershell/module/skype/get-cstrunk?view=skype-ps) cmdlet in order to view information about an individual SIP trunk.
### To view information for all your SIP trunks
- The following command returns information about all the SIP trunks in use in your organization:
```powershell
Get-CsTrunk
```
### To view information for a specific SIP trunk
- This command returns information only for the SIP trunk with the Identity PstnGateway:192.168.0.240:
```powershell
Get-CsTrunk -Identity "PstnGateway:192.168.0.240"
```
### View information for all the SIP trunks assigned to a pool
- In this example, information is returned for all the SIP trunks assigned to the pool atl-cs-001.litwareinc.com:
```powershell
Get-CsTrunk -PoolFqdn "atl-cs-001.litwareinc.com"
``` | 43.745098 | 528 | 0.775437 | eng_Latn | 0.966414 |
d56eacece02ba826637425c0785e09667dea3472 | 7,196 | md | Markdown | articles/dns/dns-domain-delegation.md | alzhr/azure-docs.fr-fr | 9173b798c3e6f668810b3a9dfebd0bd95f897e6d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/dns/dns-domain-delegation.md | alzhr/azure-docs.fr-fr | 9173b798c3e6f668810b3a9dfebd0bd95f897e6d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/dns/dns-domain-delegation.md | alzhr/azure-docs.fr-fr | 9173b798c3e6f668810b3a9dfebd0bd95f897e6d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Présentation de la délégation DNS Azure
description: Découvrez comment modifier la délégation de domaine et les serveurs de noms Azure DNS pour fournir l’hébergement d’un domaine.
services: dns
author: asudbring
ms.service: dns
ms.date: 2/19/2019
ms.author: allensu
ms.topic: conceptual
ms.openlocfilehash: 3d8a87e199736bf51fcdc051c17c2fded3402b79
ms.sourcegitcommit: d6b68b907e5158b451239e4c09bb55eccb5fef89
ms.translationtype: HT
ms.contentlocale: fr-FR
ms.lasthandoff: 11/20/2019
ms.locfileid: "74212102"
---
# <a name="delegation-of-dns-zones-with-azure-dns"></a>Délégation de zones DNS dans Azure DNS
Azure DNS vous permet d’héberger une zone DNS et de gérer les enregistrements DNS pour un domaine dans Azure. Pour que les requêtes DNS d’un domaine atteignent Azure DNS, le domaine doit être délégué à Azure DNS à partir du domaine parent. GardeN’oubliez pas qu’Azure DNS n’est pas le bureau d’enregistrement de domaines. Cet article explique le fonctionnement de la délégation de domaine et indique comment déléguer des domaines à Azure DNS.
## <a name="how-dns-delegation-works"></a>Fonctionnement de la délégation DNS
### <a name="domains-and-zones"></a>Zones et domaines
DNS est une hiérarchie de domaines. Celle-ci démarre à partir du domaine « racine », dont le nom est simplement « **.** ». Puis viennent les domaines de niveau supérieur, tels que « com », « net », « org », « uk » ou « jp ». Vous trouvez ensuite les domaines de second niveau, comme « org.uk » ou « co.jp ». Et ainsi de suite. Les domaines de la hiérarchie DNS sont hébergés à l’aide de zones DNS distinctes. Ces zones sont globalement distribuées, et hébergées par des serveurs DNS dans le monde entier.
Une **zone DNS** est un nom unique dans le système DNS, par exemple, « contoso.com ». Une zone DNS permet d’héberger les enregistrements DNS d’un domaine particulier. Par exemple, le domaine « contoso.com » peut contenir plusieurs enregistrements DNS, tels que « mail.contoso.com » (pour un serveur de messagerie) et « www.contoso.com » (pour un site web).
Un **bureau d’enregistrement de domaines** est une société qui fournit des noms de domaine Internet. Il vérifie si le domaine Internet que vous souhaitez utiliser est disponible. Vous pouvez ensuite l’acheter. Une fois inscrit, le nom de domaine est votre propriété légale. Si vous disposez déjà d’un domaine Internet, vous allez utiliser le bureau d’enregistrement de domaines actuel pour la délégation à Azure DNS.
Pour plus d’informations sur les bureaux d’enregistrement de domaines agréés, consultez la page [ICANN-Accredited Registrars](https://www.icann.org/registrar-reports/accredited-list.html) (Bureaux d’enregistrement agréés par l’ICANN).
### <a name="resolution-and-delegation"></a>Résolution et délégation
Deux types de serveur DNS sont disponibles :
* Un serveur DNS *faisant autorité* héberge les zones DNS. Il répond aux requêtes DNS pour les enregistrements de ces zones uniquement.
* Un serveur DNS *récursif* n’héberge pas de zones DNS. Il répond à toutes les requêtes DNS, en appelant des serveurs DNS faisant autorité pour rassembler les données dont il a besoin.
Azure DNS fournit un service DNS faisant autorité. Il ne fournit pas un service DNS récursif. Les services cloud et machines virtuelles contenus dans Azure sont automatiquement configurés pour utiliser un service DNS récursif, fourni séparément, dans le cadre de l’infrastructure Azure. Pour savoir comment modifier ces paramètres DNS, voir [Résolution de noms dans Azure](../virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances.md#name-resolution-that-uses-your-own-dns-server).
Les clients DNS des PC ou appareils mobiles appellent généralement un serveur DNS récursif pour effectuer les requêtes DNS dont les applications clientes ont besoin.
Lorsqu’un serveur DNS récursif reçoit une requête pour un enregistrement DNS tel que « www.contoso.com », il doit d’abord rechercher le serveur de noms qui héberge la zone pour le domaine « contoso.com ». Pour ce faire, il commence par les serveurs de noms racines, puis il recherche les serveurs de noms hébergeant la zone « com ». Il interroge ensuite les serveurs de noms « com » pour trouver les serveurs de noms hébergeant la zone « contoso.com ». Enfin, il est en mesure de rechercher « www.contoso.com » parmi ces serveurs de noms.
On parle dans ce cas de résolution de noms DNS. À strictement parler, la résolution DNS inclut toutefois des étapes supplémentaires, telles que le suivi des enregistrements CNAME, mais ce n’est pas important pour comprendre le fonctionnement de la délégation DNS.
Comment une zone parente « pointe-t-elle » vers les serveurs de noms d’une zone enfant ? Elle utilise pour cela un type spécial d’enregistrement DNS appelé enregistrement NS (pour « serveur de noms »). Par exemple, la zone racine contient les enregistrements NS pour « com » et affiche les serveurs de noms pour la zone « com ». La zone « com », quant à elle, contient les enregistrements NS pour « contoso.com » et affiche les serveurs de noms pour la zone « contoso.com ». La configuration d’enregistrements NS pour une zone enfant dans une zone parente est appelée « délégation de domaine ».
L’image suivante montre un exemple de requête DNS. contoso.net et partners.contoso.net sont des zones Azure DNS.
1. Le client demande `www.partners.contoso.net` à partir du serveur DNS local.
2. Le serveur DNS local ne dispose pas de l’enregistrement. Aussi, il effectue une demande auprès du serveur de noms racine.
3. Le serveur de noms racine ne dispose pas de l’enregistrement, mais il connaît l’adresse du serveur de noms `.net` et la fournit au serveur DNS.
4. Le serveur DNS local envoie la demande au serveur de noms `.net`.
5. Le serveur de noms `.net` n’a pas l’enregistrement, mais il connaît l’adresse du serveur de noms `contoso.net`. Dans ce cas, il répond avec l’adresse du serveur de noms pour la zone DNS hébergée dans Azure DNS.
6. Le serveur DNS local envoie la demande au serveur de noms pour la zone `contoso.net` hébergée dans Azure DNS.
7. La zone `contoso.net` n’a pas l’enregistrement, mais elle connaît le serveur de noms `partners.contoso.net` et envoie l’adresse comme réponse. Dans ce cas, il s’agit d’une zone DNS hébergée dans Azure DNS.
8. Le serveur DNS local envoie la demande au serveur de noms pour la zone `partners.contoso.net`.
9. La zone `partners.contoso.net` a l’enregistrement A et envoie l’adresse IP comme réponse.
10. Le serveur DNS local fournit l’adresse IP au client.
11. Le client se connecte au site web `www.partners.contoso.net`.
Chaque délégation a en fait deux copies des enregistrements NS : une dans la zone parent qui pointe vers la zone enfant et l’autre dans la zone enfant elle-même. La zone « contoso.net » contient les enregistrements NS pour « contoso.net » (en plus des enregistrements NS dans « net »). Il s’agit d’enregistrements NS faisant autorité ; ils se trouvent au sommet de la zone enfant.
## <a name="next-steps"></a>Étapes suivantes
Découvrez comment [déléguer votre domaine à Azure DNS](dns-delegate-domain-azure-dns.md).
| 99.944444 | 594 | 0.780295 | fra_Latn | 0.98212 |
d56f5b9b68df6a7d27312804917d82104429b248 | 267 | md | Markdown | README.md | noeldelgado/neo-widget | 282fdcf5c6cb970dd6e88bb513c70758936c739c | [
"MIT"
] | null | null | null | README.md | noeldelgado/neo-widget | 282fdcf5c6cb970dd6e88bb513c70758936c739c | [
"MIT"
] | null | null | null | README.md | noeldelgado/neo-widget | 282fdcf5c6cb970dd6e88bb513c70758936c739c | [
"MIT"
] | null | null | null | # neo-widget
[](https://www.npmjs.com/package/neo-widget)
#### WIP
| 33.375 | 101 | 0.719101 | yue_Hant | 0.096122 |
d56f67cb27d88642a95090195f264bcfe29f2ac3 | 6,793 | md | Markdown | attic/2019/contributions-2019/open/jespel-btel/README.md | Agriad/devops-course | 380aa43fa69efd71992933f013fb11a96ce16a74 | [
"MIT"
] | null | null | null | attic/2019/contributions-2019/open/jespel-btel/README.md | Agriad/devops-course | 380aa43fa69efd71992933f013fb11a96ce16a74 | [
"MIT"
] | 51 | 2021-04-08T11:39:59.000Z | 2021-05-07T12:01:27.000Z | attic/2019/contributions-2019/open/jespel-btel/README.md | Agriad/devops-course | 380aa43fa69efd71992933f013fb11a96ce16a74 | [
"MIT"
] | null | null | null | # Flaky Test
An animation that symbolises flaky tests.
## The main idea
We would like to create an art project representing flaky tests as our open project.
Our idea is to create an animation of an ECG that works most of the time, but sometimes for no reason weirds out (like flatlines for a short while or take a double beat) before it returns to normal.
Our idea is to create a small webpage to hold this animation.
We created the image above as small exploatory project to understand the techniques to create the ECG effect.
## Side goals
Developing this website we would like to practice some of the DevOps techniques that are taught in the course. We beleive that especially CI and CD would fit the project.
Further we got a crazy idea that it might be cool to be able to visualize the progress of project, i.e. being able to see every commit of the project.
# Result
## Main project
[https://flaky.jesperlarsson.me](https://flaky.jesperlarsson.me) holds the final animation.
## Artistic meaning
The final product contains two different animations:
1. normal heartbeats, and
2. flatline.
We did not animate arrythmia manifesting as a double heartbeat since we deemed that it was not neccessary to deliver our artistic vision.
Our vision was to create an animation that could convey the feeling of flaky tests. The normal heartbeats represents that tests passing as they should, and the site is dominated by a calming green to ensure the viewer that everything is fine. But then, suddenly, it all changes to an alarming red with a constant monotonic noise when the ECG flatlines and turns red. This represents the heartstopping fear one might feel when their normally green chekckmark suddenly turns into a red cross due to a flaky test. But just as suddenly as it flatlined, it goes back to the calming green, and momentarily calms you, but you feel that your trust has slightly diminished.
## Implementation
The frontend was implemented as static site, with plain HTML, CSS and JS. The following sections will describe how we generated datapoints for the heartbeat and displayed them.
### The heartbeat function
The heartbeat was implemented from scratch by using some simple built
in mathematical functions. The function attempts to describe the
different interval, segments and waves of a high detailed ECG. First
is the P-wave, which is described by a simple sine function. After
this comes the very characteristic spike of an ECG, known as the QRS
segment. The function describes this by gluing together 4 different
linear functions with different derivatives, to give the
characteristicly sharp look that drops before and after the
highpoint. The QRS segment is followed by the T-wave, also described
by a simple sine function. After this is the seldom seen U-wave, a
wave with very small magnitude compared to the other parts of the ECG,
and this is often missed if the ECG has a low resolution. The U-wave
is also described by a sine function.
The heartbeat function returns an object with information that the
display uses. The attributes are height (`y`), colour and sound, which
tells the display to send sound or not.
### The display
To display all this, a html canvas was used to continously draw the
points provided by the hearbeat function, and a nice thematic
background was added using a colour gradient effect.
To display this, points were fetched from the heartbeat function by
supplying it with a parameter t, which determined how far into the
heartbeat the display is.
A tone was also played depending on the return value of the hearbeat
function, much like a normal ECG (with a continous sound being played
during a flatline).
One can also click on the animation to switch between art and monitor mode.
### The backend
The backend was written in Python using the Flask framework to create
an API to control the front-end. A few different routes were used to
controle the mode of the front end (is it an art-work or build health
monitor?), change the build status and provide the current build
status.
* `/status` displays the current status of the build
* `/mode` the current mode of the canvas
* `/flip-mode` switch the current mode of the canvas
* `/hook` endpoint to communicate with gitlab about the build status
## Repo structure
Other than the main frontend-only animation that was the focus of the project we created a small backend that the frontend may communicate with. The purpose of the backend is to listen for webhooks signaling the status of a repo. (The backend only support GitLab for the moment, but is designed so that it is easy to add support for other platforms.) The frontend may also function just as an artpiece without a backend if desired.
### Flaky
The frontend is contained within the repository Flaky. It is simply a static webapp and could be deployed as such to any webserver. We hosted ours on a server that ran the docker manager dokku. For a custom deployment where one would like to integrate it with our developed backend, one would have to update the url to that backend though. This can easily be done on [line 318](https://gitlab.com/flaky_kth_devops/flaky/blob/master/public_html/index.js#L318) of index.js. (It might have been more friendly to extract that value to a constant at the top of the file though.)
### flaky_back_end
We choose to seperate the backend to its own repository (flaky_backend) so that the frontend would deploy as a simple static website. The backend listens to status webhooks from GitLab and stores it. The frontend may then query that status through the route `/status`. The backend may only monitor one repo at a time, so one backend need to be deployed per repo to monitor. The backend is otherwise a flask application and may be deployed as such. Before deploying, one need to configure CORS to allow the frontend to talk to the backend. This can easily be done on [line 8](https://gitlab.com/flaky_kth_devops/flaky_back_end/blob/master/controller.py#L8) in controller.py. We also hosted this using dokku.
### flaky_test
The repo flaky_test was used as a dummy repo that our backend could monitor. We purposefully made it pass or fail tests to ensure that our backend integrated with GitLab as desired.
## Side goal
We were happy with our devops practices. Our project focused very much on the visual and artistic side of the product resulting in us forgoing unit tests, but we are proud over our automatic deployment. Our repos can be found at [https://gitlab.com/flaky_kth_devops](https://gitlab.com/flaky_kth_devops).
Unfortunately we did not have time to implement our crazy idea. However, we did implement an alternative mode where the animation will continously flatline if some CI fails in a specified repo.
| 63.485981 | 706 | 0.793317 | eng_Latn | 0.999841 |
d57003a1a8f0b7b18f784a89797fb1308931472a | 1,753 | md | Markdown | README.md | korolr/go-sh | 68a4101a66f730ad5a3636514f999941c2048e1c | [
"MIT"
] | null | null | null | README.md | korolr/go-sh | 68a4101a66f730ad5a3636514f999941c2048e1c | [
"MIT"
] | null | null | null | README.md | korolr/go-sh | 68a4101a66f730ad5a3636514f999941c2048e1c | [
"MIT"
] | null | null | null | ## Stacks
- Go
- GraphQL : [graphql-go](https://github.com/graph-gophers/graphql-go)
- ORM : [gorm](https://github.com/jinzhu/gorm)
## Features
- User Sign Up & Sign In
- Change a Password, Profile
## How to Run
### Initialize DB
1. Create a database
```shell
postgres=# CREATE DATABASE go;
```
2. Create a user as owner of database
```shell
postgres=# CREATE USER go WITH ENCRYPTED PASSWORD 'go';
postgres=# ALTER DATABASE go OWNER TO go;
```
3. Grant all privileges to user for the database
```shell
postgres=# GRANT ALL PRIVILEGES ON DATABASE go TO go;
```
4. Configure the db in `db.go`
```go
// ConnectDB : connecting DB
func ConnectDB() (*DB, error) {
db, err := gorm.Open("postgres", "host=localhost port=5432 user=go dbname=go password=go sslmode=disable")
if err != nil {
panic(err)
}
return &DB{db}, nil
}
```
or with Docker
> host address should be edited to `host.docker.internal` to connect a host interface.
```go
// ConnectDB : connecting DB
func ConnectDB() (*DB, error) {
db, err := gorm.Open("postgres", "host=host.docker.internal port=5432 user=go dbname=go password=go sslmode=disable")
if err != nil {
panic(err)
}
return &DB{db}, nil
}
```
### Initial Migration
```shell
$ go run ./migrations/init.go
```
or with Docker
```
$ docker build -t go-graphql-api .
$ docker run --rm go-graphql-api migrate
```
This will generate the `users` table in the database as per the User Model declared in `./model/user.go`
### Run the server
```shell
$ go run server.go
```
or with Docker
```
$ docker run --rm -d -p 8080:8080 go-graphql-api
```
### GraphQL Playground
Connect to http://localhost:8080
### Authentication : JWT
You need to set the Http request headers `Authorization`: `{JWT_token}`
| 17.186275 | 118 | 0.677695 | eng_Latn | 0.451152 |
d570477145b85566e999a49542f2b1d0b51a315a | 112 | md | Markdown | README.md | Lynneice/Predicting-customer-churn- | 6024137de69371e569f8a47c5888bf3b66c1f8a0 | [
"MIT"
] | null | null | null | README.md | Lynneice/Predicting-customer-churn- | 6024137de69371e569f8a47c5888bf3b66c1f8a0 | [
"MIT"
] | null | null | null | README.md | Lynneice/Predicting-customer-churn- | 6024137de69371e569f8a47c5888bf3b66c1f8a0 | [
"MIT"
] | null | null | null | # Predicting-customer-churn-
Predicting customer churn using Kaggle telecom data. PAC and Logistic Regression.
| 37.333333 | 82 | 0.821429 | eng_Latn | 0.929757 |
d5707770a94fcab09670d3e5328ee0771e7f4ee6 | 29 | md | Markdown | README.md | fengzhiwei-yu/yuyao | 66446d049d92da15c66dd964f90a0adbfa7113d7 | [
"MIT"
] | null | null | null | README.md | fengzhiwei-yu/yuyao | 66446d049d92da15c66dd964f90a0adbfa7113d7 | [
"MIT"
] | null | null | null | README.md | fengzhiwei-yu/yuyao | 66446d049d92da15c66dd964f90a0adbfa7113d7 | [
"MIT"
] | null | null | null | # yuyao
Unforgettable person
| 9.666667 | 20 | 0.827586 | ast_Latn | 0.47544 |
d5708f17deaefa07b44772b9b58053c926119e07 | 5,650 | md | Markdown | README.md | johndpope/swift-1 | 52c5e830999694ce7d58d4d2472ae0d66ae60cce | [
"CC-BY-4.0"
] | null | null | null | README.md | johndpope/swift-1 | 52c5e830999694ce7d58d4d2472ae0d66ae60cce | [
"CC-BY-4.0"
] | null | null | null | README.md | johndpope/swift-1 | 52c5e830999694ce7d58d4d2472ae0d66ae60cce | [
"CC-BY-4.0"
] | null | null | null | <p align="center">
<img src="images/logo.png">
</p>
# Swift for TensorFlow
Welcome to the Swift for TensorFlow development community! For discussions, join the [[email protected] mailing list](https://groups.google.com/a/tensorflow.org/d/forum/swift).
Swift for TensorFlow is a new way to develop machine learning models. It
gives you the power of
[TensorFlow](https://www.tensorflow.org) directly integrated into the
[Swift programming language](https://swift.org/about).
With Swift, you can write the following imperative code, and Swift
automatically turns it into **a single TensorFlow Graph** and runs it
with the full performance of TensorFlow Sessions on CPU, GPU and
[TPU](https://cloud.google.com/tpu).
```swift
import TensorFlow
var x = Tensor<Float>([[1, 2], [3, 4]])
for i in 1...5 {
x += x • x
}
print(x)
```
Swift combines the flexibility of
[Eager Execution](https://www.tensorflow.org/programmers_guide/eager) with the
high performance of [Graphs and Sessions](https://www.tensorflow.org/programmers_guide/graphs).
Behind the scenes, Swift analyzes your Tensor code and automatically builds
graphs for you. Swift also catches type errors and shape mismatches before running
your code, has the ability to import any Python library, and has
[Automatic Differentiation](https://en.wikipedia.org/wiki/Automatic_differentiation)
built right in. We believe that machine learning tools are so important that they
deserve **a first-class language and a compiler**.
**Note:** Swift for TensorFlow is an early stage project. It has been released
to enable open source development and is not yet ready for general use
by machine learning developers.
## Installation and Usage
You can [download a pre-built package](Installation.md) for Swift for TensorFlow.
After installation, you can follow these [instructions](Usage.md) to try it out.
For instructions on building from source, visit
[apple/swift](https://github.com/apple/swift/tree/tensorflow).
## Documentation
Below are some documents explaining the Swift for TensorFlow project.
### Conceptual overview
- [Swift for TensorFlow Design Overview](docs/DesignOverview.md)
- [Why *Swift* for TensorFlow?](docs/WhySwiftForTensorFlow.md)
- [Frequently Asked Questions](FAQ.md)
### Technology deep dive
- [Graph Program Extraction](docs/GraphProgramExtraction.md)
- [Automatic Differentiation](docs/AutomaticDifferentiation.md)
- [Python Interoperability](docs/PythonInteroperability.md)
### Swift API reference
- [TensorFlow](https://www.tensorflow.org/api_docs/swift/Structs/Tensor)
### Design proposals
- [One Graph Function per Host Function](https://github.com/tensorflow/swift/blob/master/proposals/OneGraphFunctionPerHostFunction.md)
- [Parameter Update Design](https://github.com/tensorflow/swift/blob/master/proposals/ParameterUpdate.md)
## Source code
The active development of Swift for TensorFlow will happen under the
"tensorflow" branch of
[apple/swift](https://github.com/apple/swift/tree/tensorflow).
These projects include:
- The compiler and standard libraries: [apple/swift](http://github.com/apple/swift/tree/tensorflow)
- Debugger and REPL support: [apple/swift-lldb](http://github.com/apple/swift-lldb/tree/tensorflow)
Swift for TensorFlow is **not** intended to remain a long-term fork of the official
Swift language. New language features will eventually go through the Swift evolution process
as part of being considered for being pulled into master.
## Models
You can find example machine learning models at
[tensorflow/swift-models](https://github.com/tensorflow/swift-models).
## Related Projects
### Jupyter Notebook support
[Jupyter Notebook](http://jupyter.org/) support for Swift for TensorFlow is under development at
[google/swift-jupyter](https://github.com/google/swift-jupyter).
## Community
Discussion about Swift for TensorFlow happens on the
[[email protected] mailing list](https://groups.google.com/a/tensorflow.org/d/forum/swift).
## Bugs Reports and Feature Requests
Before reporting an issue, please check the [Frequently Asked Questions](FAQ.md) to see if your question has already been addressed.
For questions about general use or feature requests, please report them in this repository or send an email to the [mailing list](mailto:[email protected]).
For Swift compiler bugs introduced by Swift for TensorFlow, please file them to [bugs.swift.org](https://bugs.swift.org) within the “Swift for TensorFlow” component.
For bugs in the example models, please report them to [tensorflow/swift-models](https://github.com/tensorflow/swift-models/issues).
## Contributing
We welcome source code contributions: please read
[Contributing Code](https://swift.org/contributing/#contributing-code).
It is always a good idea to discuss your plans on the mailing list
before making any major submissions.
The compiler and the standard library have the most [open issues](https://github.com/google/swift/issues).
To get started, you can try to tackle issues labeled "good first issue".
## Code of Conduct
In the interest of fostering an open and welcoming environment, we as
contributors and maintainers pledge to making participation in our project and
our community a harassment-free experience for everyone, regardless of age, body
size, disability, ethnicity, gender identity and expression, level of
experience, education, socio-economic status, nationality, personal appearance,
race, religion, or sexual identity and orientation.
The Swift for TensorFlow community is guided by our [Code of
Conduct](CODE_OF_CONDUCT.md), which we encourage everybody to read before
participating.
| 39.788732 | 179 | 0.783894 | eng_Latn | 0.968076 |
d570fd6f2d0727440959eab02454ef533d61f6ee | 750 | md | Markdown | lightsail/README.md | doitintl/compute_options | 3e9268eb111154b7533dd2062e25b6c020ff2ec9 | [
"MIT"
] | 3 | 2021-01-18T10:00:05.000Z | 2021-02-06T12:29:46.000Z | lightsail/README.md | doitintl/compute_options | 3e9268eb111154b7533dd2062e25b6c020ff2ec9 | [
"MIT"
] | null | null | null | lightsail/README.md | doitintl/compute_options | 3e9268eb111154b7533dd2062e25b6c020ff2ec9 | [
"MIT"
] | 1 | 2021-07-17T04:13:21.000Z | 2021-07-17T04:13:21.000Z | # AWS Lightsail
Prerequisites: Docker; the AWS CLI with credentials configured to an AWS account; the [Lightsail plugin for the AWS CLI.]( https://lightsail.aws.amazon.com/ls/docs/en_us/articles/amazon-lightsail-install-software)
This `deploy.sh` script pushes a container to Lightsail, but Lightsail allows you to skip that step if you deploy services from pre-defined containers.
The script is not rerunnable: It will fail on the second run if you do not clean up resources.
A [Getting Started article](https://aws.amazon.com/blogs/aws/lightsail-containers-an-easy-way-to-run-your-containers-in-the-cloud/) for Lightsail with containers is available. The article shows how to to it with the help of the console, but also entirely on the CLI.
| 68.181818 | 266 | 0.789333 | eng_Latn | 0.995567 |
d5711aee501046ffacbc776d86b74e30e19720de | 439 | md | Markdown | _components/fajita-seasoning.md | PhilipNelson5/Chowdown | b293aa6001277c37c95a5a61043f2a89a3d8c5a7 | [
"Unlicense"
] | 2 | 2020-02-06T11:22:50.000Z | 2022-01-26T03:23:10.000Z | _components/fajita-seasoning.md | PhilipNelson5/Chowdown | b293aa6001277c37c95a5a61043f2a89a3d8c5a7 | [
"Unlicense"
] | 1 | 2022-02-26T06:51:27.000Z | 2022-02-26T06:51:27.000Z | _components/fajita-seasoning.md | PhilipNelson5/Chowdown | b293aa6001277c37c95a5a61043f2a89a3d8c5a7 | [
"Unlicense"
] | 3 | 2019-12-12T16:13:31.000Z | 2021-01-18T23:13:53.000Z | ---
layout: recipe
title: "Fajita Seasoning"
image: fajita-seasoning.jpg
imagecredit: https://www.jocooks.com/recipes/fajita-seasoning/
ingredients:
- 1 tbsp chili powder
- 1 tsp cumin ground
- 1 tsp paprika (I used smoked)
- 1/4 tsp cayenne pepper
- 1 tsp salt
- 1 tsp ground black pepper
directions:
- Mix all the ingredients together in a bowl. Recipe will yield about 2 1/2 tbsp. Store in a spice jar in your spice cabinet.
---
| 19.954545 | 125 | 0.735763 | eng_Latn | 0.524341 |
d5717a02c65a6513cb47c54d2ea01aa0ea1bc5b5 | 1,256 | md | Markdown | components/input-number/index.en-US.md | gotjoshua/ant-design | 2cc232aa155de0ecbbae468b45b2a636a5b5c244 | [
"MIT"
] | 9 | 2019-06-16T15:33:24.000Z | 2019-11-26T13:05:40.000Z | components/input-number/index.en-US.md | gotjoshua/ant-design | 2cc232aa155de0ecbbae468b45b2a636a5b5c244 | [
"MIT"
] | 64 | 2020-01-23T19:00:38.000Z | 2021-10-01T12:41:37.000Z | components/input-number/index.en-US.md | gotjoshua/ant-design | 2cc232aa155de0ecbbae468b45b2a636a5b5c244 | [
"MIT"
] | 1 | 2019-06-21T05:06:12.000Z | 2019-06-21T05:06:12.000Z | ---
category: Components
type: Data Entry
title: InputNumber
---
Enter a number within certain range with the mouse or keyboard.
## When To Use
When a numeric value needs to be provided.
## API
| Property | Description | Type | Default |
| --- | --- | --- | --- |
| autoFocus | get focus when component mounted | boolean | false |
| defaultValue | initial value | number | |
| disabled | disable the input | boolean | false |
| formatter | Specifies the format of the value presented | function(value: number \| string): string | - |
| max | max value | number | Infinity |
| min | min value | number | -Infinity |
| parser | Specifies the value extracted from formatter | function( string): number | - |
| precision | precision of input value | number | - |
| decimalSeparator | decimal separator | string | - |
| size | height of input box | string | - |
| step | The number to which the current value is increased or decreased. It can be an integer or decimal. | number\|string | 1 |
| value | current value | number | |
| onChange | The callback triggered when the value is changed. | function(value: number \| string) | |
## Methods
| Name | Description |
| ------- | ------------ |
| blur() | remove focus |
| focus() | get focus |
| 33.945946 | 129 | 0.655255 | eng_Latn | 0.994873 |
d5719b4b55f6a79f5607f4af02f3fcea49721a7e | 3,670 | md | Markdown | docs/documentation/quartz-1.x/tutorial/jobs-and-triggers.md | ahmad-moussawi/quartznet | a22915a9abac1568accb93eb24b4cce5331c8249 | [
"Apache-2.0"
] | 4,575 | 2015-01-04T05:10:01.000Z | 2022-03-31T19:11:25.000Z | docs/documentation/quartz-1.x/tutorial/jobs-and-triggers.md | aubryll/quartznet | 6be2fe214562ef0429a7eabb8f6bbd0147380915 | [
"Apache-2.0"
] | 929 | 2015-01-02T04:53:14.000Z | 2022-03-29T16:51:39.000Z | docs/documentation/quartz-1.x/tutorial/jobs-and-triggers.md | aubryll/quartznet | 6be2fe214562ef0429a7eabb8f6bbd0147380915 | [
"Apache-2.0"
] | 1,626 | 2015-01-10T15:15:27.000Z | 2022-03-25T11:48:01.000Z | ---
title: 'Lesson 2: Jobs And Triggers'
---
As mentioned previously, you can make .NET component executable by the scheduler simply by making it
implement the IJob interface. Here is the interface:
__IJob Interface__
```csharp
namespace Quartz
{
public interface IJob
{
void Execute(JobExecutionContext context);
}
}
```
In case you couldn't guess, when the job's trigger fires (more on that in a moment), the Execute(..) method
is invoked by the scheduler. The JobExecutionContext object that is passed to this method provides
the job instance with information about its "run-time" environment - a handle to the IScheduler that executed it,
a handle to the Trigger that triggered the execution, the job's JobDetail object, and a few other items.
The JobDetail object is created by the Quartz.NET client (your program) at the time the Job is added
to the scheduler. It contains various property settings for the Job, as well as a JobDataMap, which can be used
to store state information for a given instance of your job class.
Trigger objects are used to trigger the execution (or 'firing') of jobs. When you wish to schedule a job,
you instantiate a trigger and 'tune' its properties to provide the scheduling you wish to have.
Triggers may also have a JobDataMap associated with them - this is useful to passing parameters to a Job
that are specific to the firings of the trigger. Quartz.NET ships with a handful of different trigger types,
but the most commonly used types are SimpleTrigger and CronTrigger.
SimpleTrigger is handy if you need 'one-shot' execution (just single execution of a job at a given moment in time),
or if you need to fire a job at a given time, and have it repeat N times, with a delay of T between executions.
CronTrigger is useful if you wish to have triggering based on calendar-like schedules - such as "every Friday,
at noon" or "at 10:15 on the 10th day of every month."
## Why Jobs AND Triggers?
Many job schedulers do not have separate notions of jobs and triggers. Some define a 'job' as simply an
execution time (or schedule) along with some small job identifier. Others are much like the union
of Quartz.NET's job and trigger objects. While developing Quartz for Java, Quartz team decided that it made sense to create
a separation between the schedule and the work to be performed on that schedule. This has (in our opinion)
many benefits.
For example, jobs can be created and stored in the job scheduler independent of a trigger, and many triggers
can be associated with the same job. Another benefit of this loose-coupling is the ability to configure jobs
that remain in the scheduler after their associated triggers have expired, so that that it can be rescheduled
later, without having to re-define it. It also allows you to modify or replace a trigger without having to
re-define its associated job.
## Identifiers
Jobs and Triggers are given identifying names as they are registered with the Quartz.NET scheduler.
Jobs and triggers can also be placed into 'groups' which can be useful for organizing your jobs and triggers
into categories for later maintenance. The name of a job or trigger must be unique within its group - or in other
words, the true identifier of a job or trigger is its name + group. If you leave the group of the
Job or Trigger 'null', it is equivalent to having specified SchedulerConstants.DefaultGroup.
You now have a general idea about what Jobs and Triggers are, you can learn more about them in
[Lesson 3: More About Jobs & JobDetails](more-about-jobs.md) and [Lesson 4: More About Triggers](more-about-triggers.md)
| 57.34375 | 124 | 0.773025 | eng_Latn | 0.999885 |
d571bcee6692d09b1a9f4a204724d06e61429ef3 | 244 | md | Markdown | can_become_palidrone/README.md | nunezpaul/practice_problems | 22449c014046b702a4284bb66548f3a70c265622 | [
"MIT"
] | null | null | null | can_become_palidrone/README.md | nunezpaul/practice_problems | 22449c014046b702a4284bb66548f3a70c265622 | [
"MIT"
] | null | null | null | can_become_palidrone/README.md | nunezpaul/practice_problems | 22449c014046b702a4284bb66548f3a70c265622 | [
"MIT"
] | null | null | null | Verify if a word is a palindrome or can become a palindrome by removing a letter.
Example:
aabbaa -> True
aabbbaa -> True
ababbaa -> True
bbabbaa -> False
abcdefg -> False | 27.111111 | 83 | 0.52459 | eng_Latn | 0.766299 |
d571cea33428b115736fa26ec1fd0a9717c348fa | 6,517 | md | Markdown | CHANGELOG.md | pavellzubkov/ncfork | 681598906c8053a5b1c3e9fcf6429b498989eab6 | [
"MIT"
] | null | null | null | CHANGELOG.md | pavellzubkov/ncfork | 681598906c8053a5b1c3e9fcf6429b498989eab6 | [
"MIT"
] | null | null | null | CHANGELOG.md | pavellzubkov/ncfork | 681598906c8053a5b1c3e9fcf6429b498989eab6 | [
"MIT"
] | null | null | null | <a name="1.1.1"></a>
## [1.1.1](https://github.com/ncform/ncform/compare/v1.1.0...v1.1.1) (2019-03-30)
### Bug Fixes
* **ncform-theme-elementui:** fixed error when not provide otherParams ([66d1713](https://github.com/ncform/ncform/commit/66d1713))
* **ncform-theme-elementui:** fixed select widget bugs ([ea05422](https://github.com/ncform/ncform/commit/ea05422))
<a name="1.1.0"></a>
## [1.1.0](https://github.com/ncform/ncform/compare/v1.0.0...v1.1.0) (2019-03-30)
### Code Refactoring
* rename $t to $nclang, in order to avoid conflicts with vue-i18n method ([6df509e](https://github.com/ncform/ncform/commit/6df509e)), closes [#51](https://github.com/ncform/ncform/issues/51)
<a name="1.0.0"></a>
## [1.0.0](https://github.com/ncform/ncform/compare/v0.1.28...v1.0.0) (2019-03-19)
### Bug Fixes
* Fixed object layout cann't show label when setting v layout ([ff65ac1](https://github.com/ncform/ncform/commit/ff65ac1))
* **ncform:** fixed image width or height not adaptive when preview ([61bea74](https://github.com/ncform/ncform/commit/61bea74))
* **ncform:** fixed the bug that the valueTemplate initialization value is overwritten by the dynamically calculated value ([7a8ca09](https://github.com/ncform/ncform/commit/7a8ca09))
### Features
* All stardard widgets's widgetConfig support dx expression ([ae829e0](https://github.com/ncform/ncform/commit/ae829e0))
* ui.legend support dx expression ([45af266](https://github.com/ncform/ncform/commit/45af266))
* ui.label support dx expression ([cc0f585](https://github.com/ncform/ncform/commit/cc0f585))
* Fully tested
### BREAKING CHANGES
* All custom widgets's widgetConfig configuration properties automatically support dx expressions
* Widget's mergeConfig is readonly now. don't use it as data for assignment.
<a name="0.1.28"></a>
## [0.1.28](https://github.com/ncform/ncform/compare/v0.1.27...v0.1.28) (2019-03-04)
### Bug Fixes
Fixed init lang parameter default value bugs && array-table required flag display bugs([cc38c47](https://github.com/ncform/ncform/commit/cc38c47))
<a name="0.1.27"></a>
## [0.1.27](https://github.com/ncform/ncform/compare/v0.1.26...v0.1.27) (2019-03-03)
### Bug Fixes
* Add lang option when init ncform && remove `$ncformSetLang` api ([25d4684](https://github.com/ncform/ncform/commit/25d4684))
<a name="0.1.26"></a>
## [0.1.26](https://github.com/ncform/ncform/compare/v0.1.25...v0.1.26) (2019-03-03)
### Features
* Add `$ncformAddWidget` and `$ncformAddRule` apis ([3aba786](https://github.com/ncform/ncform/commit/3aba786))
* Add `$ncformSetLang` api && all standard components support en && zh-cn ([3ba93ff](https://github.com/ncform/ncform/commit/3ba93ff))
<a name="0.1.25"></a>
## [0.1.25](https://github.com/ncform/ncform/compare/v0.1.24...v0.1.25) (2019-02-26)
### Bug Fixes
* Fixed the display bug of the object type control in the h layout ([88aa77b](https://github.com/ncform/ncform/commit/88aa77b))
* Remove garbled chars ([db4e9ca](https://github.com/ncform/ncform/commit/db4e9ca))
### Features
* Add HTML && COMP types to support static content show. ([e4a9bc7](https://github.com/ncform/ncform/commit/e4a9bc7))
* Add array item collapse feature ([7ac74ad](https://github.com/ncform/ncform/commit/7ac74ad))
<a name="0.1.17"></a>
## [0.1.17](https://github.com/ncform/ncform/compare/v0.1.16...v0.1.17) (2018-10-29)
### Features
* **ncform:** add isDirty prop ([82a468b](https://github.com/ncform/ncform/commit/82a468b)), closes [#32](https://github.com/ncform/ncform/issues/32)
<a name="0.1.16"></a>
## [0.1.16](https://github.com/ncform/ncform/compare/v0.1.15...v0.1.16) (2018-10-27)
### Bug Fixes
* **ncform-theme-elementui:** fixed upload control fields assignment error ([23a4acf](https://github.com/ncform/ncform/commit/23a4acf)), closes [#23](https://github.com/ncform/ncform/issues/23)
* **ncform-theme-elementui:** fixed select control when multiple is set to true, then the otherParams changed cause error ([1485660](https://github.com/ncform/ncform/commit/1485660)), closes [#24](https://github.com/ncform/ncform/issues/24)
### Features
* **ncform:** add new rule - ajax ([961f1eb](https://github.com/ncform/ncform/commit/961f1eb)), closes [#29](https://github.com/ncform/ncform/issues/29)
* **ncform:** add reset method - $ncformReset(formName) ([a192afc](https://github.com/ncform/ncform/commit/a192afc)), closes [#25](https://github.com/ncform/ncform/issues/25)
* **ncform:** description support dx expression && html content ([7fc4532](https://github.com/ncform/ncform/commit/7fc4532)), closes [#27](https://github.com/ncform/ncform/issues/27)
<a name="0.1.15"></a>
## [0.1.15](https://github.com/ncform/ncform/compare/v0.1.14...v) (2018-10-11)
### Bug Fixes
* **ncform-theme-elementui:** fixed input control $emit input event when init with compound.prependSelect config ([941a88f](https://github.com/ncform/ncform/commit/941a88f)), closes [#19](https://github.com/ncform/ncform/issues/19)
### Features
* **ncform:** add valueTemplate config, now you can easily control one field's value depend on another ([8ac95eb](https://github.com/ncform/ncform/commit/8ac95eb))
<a name="0.1.13"></a>
## [0.1.13](https://github.com/ncform/ncform/compare/v0.1.12...v0.1.13) (2018-09-10)
### Bug Fixes
* **ncform:** fixed non-required fields still verify rules with empty value ([fe9901c](https://github.com/ncform/ncform/commit/fe9901c)), issue [#16](https://github.com/ncform/ncform/issues/16)
### Features
* **ncform:** add globalConfig.ignoreRulesWhenHidden configure ([4d0b6d0](https://github.com/ncform/ncform/commit/4d0b6d0)), issue [#17](https://github.com/ncform/ncform/issues/17)
* **ncform:** pattern rule value support string type ([cd22f48](https://github.com/ncform/ncform/commit/cd22f48)), issue [#15](https://github.com/ncform/ncform/issues/15)
<a name="0.1.12"></a>
## [0.1.12](https://github.com/ncform/ncform/compare/v0.1.10...v) (2018-08-24)
### Features
* **ncform:** default value support dx expression ([bee57fc](https://github.com/ncform/ncform/commit/bee57fc))
<a name="0.1.10"></a>
## [0.1.10](https://github.com/ncform/ncform/compare/v0.1.8...v0.1.10) (2018-08-07)
### Features
* Build `template compiled` lib to suppoort runtime-only version vue； ([98f46f5](https://github.com/ncform/ncform/commit/98f46f5))
* Upgrade webpack version to 4；([98f46f5](https://github.com/ncform/ncform/commit/98f46f5))
* **ncform-theme-element:** input control add trim configure; ([98f46f5](https://github.com/ncform/ncform/commit/98f46f5))
| 45.573427 | 240 | 0.712137 | eng_Latn | 0.218204 |
d57206d45dd23b392e5c995ccca159381248c3f1 | 186 | md | Markdown | content/textes/charte/titre1/chap4/art23.md | beckojr/kibaro | a783645f91c64a0353bd2bdb5e772407dd2243e1 | [
"MIT"
] | null | null | null | content/textes/charte/titre1/chap4/art23.md | beckojr/kibaro | a783645f91c64a0353bd2bdb5e772407dd2243e1 | [
"MIT"
] | null | null | null | content/textes/charte/titre1/chap4/art23.md | beckojr/kibaro | a783645f91c64a0353bd2bdb5e772407dd2243e1 | [
"MIT"
] | null | null | null | ---
title: "Article 23"
type: "article"
---
Les libertés d'opinion, d'expression, de conscience et de culte sont garanties. Les conditions de lent exercice sont définies par la loi.
| 18.6 | 137 | 0.731183 | fra_Latn | 0.912595 |
d57210d76058e49372807f3063ccc00b1fd0edd8 | 517 | md | Markdown | Oniguruma/README.md | WaterByWind/Solaris-IPS-Packaging | 280d8f2366b13505383793d775cb4877ae7d6ca3 | [
"MIT"
] | null | null | null | Oniguruma/README.md | WaterByWind/Solaris-IPS-Packaging | 280d8f2366b13505383793d775cb4877ae7d6ca3 | [
"MIT"
] | null | null | null | Oniguruma/README.md | WaterByWind/Solaris-IPS-Packaging | 280d8f2366b13505383793d775cb4877ae7d6ca3 | [
"MIT"
] | null | null | null | ## Oniguruma
Oniguruma is a regular expressions library. The characteristics of this library is that different character encoding for every regular expression object can be specified.
### Packaging
See [BUILDNOTES.md](Build/BUILDNOTES.md) for details regarding compiling Oniguruma and building an IPS package.
### References
- Primary location: https://github.com/kkos/oniguruma
- Downloads: https://github.com/kkos/oniguruma/releases
- Development repository mirror (GitHub): https://github.com/kkos/oniguruma
| 43.083333 | 170 | 0.794971 | eng_Latn | 0.818093 |
d572de5d9c3e91864ad750df2135421c2cba283e | 26,242 | md | Markdown | CHANGELOG.md | MathisFederico/client | 43b942e12303100d38f1719550e351d994700e41 | [
"Apache-2.0"
] | null | null | null | CHANGELOG.md | MathisFederico/client | 43b942e12303100d38f1719550e351d994700e41 | [
"Apache-2.0"
] | null | null | null | CHANGELOG.md | MathisFederico/client | 43b942e12303100d38f1719550e351d994700e41 | [
"Apache-2.0"
] | null | null | null | ## 0.8.36 (May 11, 2020)
#### :bug: Bug Fix
- Catch all exceptions when saving Jupyter sessions
- validation_data automatically set in TF >= 2.2
- _implements_\* hooks now implemented in keras callback for TF >= 2.2
#### :nail_care: Enhancement
- Raw source code saving now disabled by default
- We now support global settings on boot to enable code saving on the server
- New `code_save=True` argument to wandb.init to enable code saving manually
## 0.8.35 (May 1, 2020)
#### :bug: Bug Fix
- Ensure cells don't hang on completion
- Fixed jupyter integration in PyCharm shells
- Made session history saving handle None metadata in outputs
## 0.8.34 (Apr 28, 2020)
#### :nail_care: Enhancement
- Save session history in jupyter notebooks
- Kaggle internet enable notification
- Extend wandb.plots.feature_importances to work with more model types, thanks @neomatrix369!
#### :bug: Bug Fix
- Code saving for jupyter notebooks restored
- Fixed thread errors in jupyter
- Ensure final history rows aren't dropped in jupyter
## 0.8.33 (Apr 24, 2020)
#### :nail_care: Enhancement
- Add default class labels for semantic segmentation
- Enhance bounding box API to be similar to semantic segmentation API
#### :bug: Bug Fix
- Increase media table rows to improve ROC/PR curve logging
- Fix issue where pre binned histograms were not being handled properly
- Handle nan values in pytorch histograms
- Fix handling of binary image masks
## 0.8.32 (Apr 14, 2020)
#### :nail_care: Enhancement
- Improve semantic segmentation image mask logging
## 0.8.31 (Mar 19, 2020)
#### :nail_care: Enhancement
- Close all open files to avoice ResourceWarnings, thanks @CrafterKolyan!
#### :bug: Bug Fix
- Parse "tensor" protobufs, fixing issues with tensorboard syncing in 2.1
## 0.8.30 (Mar 19, 2020)
#### :nail_care: Enhancement
- Add ROC, precision_recall, HeatMap, explainText, POS, and NER to wandb.plots
- Add wandb.Molecule() logging
- Capture kaggle runs for metrics
- Add ability to watch from run object
#### :bug: Bug Fix
- Avoid accidently picking up global debugging logs
## 0.8.29 (Mar 5, 2020)
#### :nail_care: Enhancement
- Improve bounding box annotations
- Log active GPU system metrics
- Only writing wandb/settings file if wandb init is called
- Improvements to wandb local command
#### :bug: Bug Fix
- Fix GPU logging on some devices without power metrics
- Fix sweep config command handling
- Fix tensorflow string logging
## 0.8.28 (Feb 21, 2020)
#### :nail_care: Enhancement
- Added code saving of main python module
- Added ability to specify metadata for bounding boxes and segmentation masks
#### :bug: Bug Fix
- Fix situations where uncommited data from wandb.log() is not persisted
## 0.8.27 (Feb 11, 2020)
#### :bug: Bug Fix
- Fix dependency conflict with new versions of six package
## 0.8.26 (Feb 10, 2020)
#### :nail_care: Enhancement
- Add best metric and epoch to run summary with Keras callback
- Added wandb.run.config_static for environments required pickled config
#### :bug: Bug Fix
- Fixed regression causing failures with wandb.watch() and DataParallel
- Improved compatibility with python 3.8
- Fix model logging under windows
## 0.8.25 (Feb 4, 2020)
#### :bug: Bug Fix
- Fix exception when using wandb.watch() in a notebook
- Improve support for sparse tensor gradient logging on GPUs
## 0.8.24 (Feb 3, 2020)
#### :bug: Bug Fix
- Relax version dependancy for PyYAML for users with old environments
## 0.8.23 (Feb 3, 2020)
#### :nail_care: Enhancement
- Added scikit-learn support
- Added ability to specify/exclude specific keys when building wandb.config
#### :bug: Bug Fix
- Fix wandb.watch() on sparse tensors
- Fix incompatibilty with ray 0.8.1
- Fix missing pyyaml requirement
- Fix "W&B process failed to launch" problems
- Improved ability to log large model graphs and plots
## 0.8.22 (Jan 24, 2020)
#### :nail_care: Enhancement
- Added ability to configure agent commandline from sweep config
#### :bug: Bug Fix
- Fix fast.ai prediction logging
- Fix logging of eager tensorflow tensors
- Fix jupyter issues with logging notebook name and wandb.watch()
## 0.8.21 (Jan 15, 2020)
#### :nail_care: Enhancement
- Ignore wandb.init() specified project and entity when running a sweep
#### :bug: Bug Fix
- Fix agent "flapping" detection
- Fix local controller not starting when sweep is pending
## 0.8.20 (Jan 10, 2020)
#### :nail_care: Enhancement
- Added support for LightGBM
- Added local board support (Experimental)
- Added ability to modify sweep configuration
- Added GPU power logging to system metrics
#### :bug: Bug Fix
- Prevent sweep agent from failing continously when misconfigured
## 0.8.19 (Dec 18, 2019)
#### :nail_care: Enhancement
- Added beta support for ray/tune hyperopt search strategy
- Added ability to specify max runs per agent
- Improve experience starting a sweep without a project already created
#### :bug: Bug Fix
- Fix repeated wandb.Api().Run(id).scan_history() calls get updated data
- Fix early_terminate/hyperband in notebook/python environments
## 0.8.18 (Dec 4, 2019)
#### :nail_care: Enhancement
- Added min_step and max_step to run.scan_history for grabbing sub-sections of metrics
- wandb.init(reinit=True) now automatically calls wandb.join() to better support multiple runs per process
#### :bug: Bug Fix
- wandb.init(sync_tensorboard=True) works again for TensorFlow 2.0
## 0.8.17 (Dec 2, 2019)
#### :nail_care: Enhancement
- Handle tags being passed in as a string
#### :bug: Bug Fix
- Pin graphql-core < 3.0.0 to fix install errors
- TQDM progress bars update logs properly
- Oversized summary or history logs are now dropped which prevents retry hanging
## 0.8.16 (Nov 21, 2019)
#### :bug: Bug Fix
- Fix regression syncing some versions of Tensorboard since 0.8.13
- Fix network error in Jupyter
## 0.8.15 (Nov 5, 2019)
#### :bug: Bug Fix
- Fix calling wandb.init with sync_tensorboard multiple times in Jupyter
- Fix RuntimeError race when using threads and calling wandb.log
- Don't initialize Sentry when error reporting is disabled
#### :nail_care: Enhancement
- Added best_run() to wandb.sweep() public Api objects
- Remove internal tracking keys from wandb.config objects in the public Api
## 0.8.14 (Nov 1, 2019)
#### :bug: Bug Fix
- Improve large object warning when values reach maximum size
- Warn when wandb.save isn't passed a string
- Run stopping from the UI works since regressing in 0.8.12
- Restoring a file that already exists locally works
- Fixed TensorBoard incorrectly placing some keys in the wrong step since 0.8.10
- wandb.Video only accepts uint8 instead of incorrectly converting to floats
- SageMaker environment detection is now more robust
- Resuming correctly populates config
- wandb.restore respects root when run.dir is set #658
- Calling wandb.watch multiple times properly namespaces histograms and graphs
#### :nail_care: Enhancement
- Sweeps now work in Windows!
- Added sweep attribute to Run in the public api
- Added sweep link to Jupyter and terminal output
- TensorBoard logging now stores proper timestamps when importing historic results
- TensorBoard logging now supports configuring rate_limits and filtering event types
- Use simple output mirroring stdout doesn't have a file descriptor
- Write wandb meta files to the system temp directory if the local directory isn't writable
- Added beta api.reports to the public API
- Added wandb.unwatch to remove hooks from pytorch models
- Store the framework used in config.\_wandb
## 0.8.13 (Oct 15, 2019)
#### :bug: Bug Fix
- Create nested directory when videos are logged from tensorboard namespaces
- Fix race when using wandb.log `async=True`
- run.summary acts like a proper dictionary
- run.summary sub dictionaries properly render
- handle None when passing class_colors for segmentation masks
- handle tensorflow2 not having a SessionHook
- properly escape args in windows
- fix hanging login when in anonymode
- tf2 keras patch now handles missing callbacks args
#### :nail_care: Enhancement
- Updates documentation autogenerated from docstrings in /docs
- wandb.init(config=config_dict) does not update sweep specified parameters
- wandb.config object now has a setdefaults method enabling improved sweep support
- Improved terminal and jupyter message incorporating :rocket: emojii!
- Allow wandb.watch to be called multiple times on different models
- Improved support for watching multple tfevent files
- Windows no longer requires `wandb run` simply run `python script_name.py`
- `wandb agent` now works on windows.
- Nice error message when wandb.log is called without a dict
- Keras callback has a new `log_batch_frequency` for logging metrics every N batches
## 0.8.12 (Sep 20, 2019)
#### :bug: Bug Fix
- Fix compatibility issue with python 2.7 and old pip dependencies
#### :nail_care: Enhancement
- Improved onboarding flow when creating new accounts and entering api_key
## 0.8.11 (Sep 19, 2019)
#### :bug: Bug Fix
- Fix public api returning incorrect data when config value is 0 or False
- Resumed runs no longer overwrite run names with run id
#### :nail_care: Enhancement
- Added recording of spell.run id in config
## 0.8.10 (Sep 13, 2019)
#### :bug: Bug Fix
- wandb magic handles the case of tf.keras and keras being loaded
- tensorboard logging won't drop steps if multiple loggers have different global_steps
- keras gradient logging works in the latest tf.keras
- keras validation_data is properly set in tensorflow 2
- wandb pull command creates directories if they don't exist, thanks @chmod644
- file upload batching now asserts a minimum size
- sweeps works in python2 again
- scan_history now iterates the full set of points
- jupyter will run local mode if credentials can't be obtained
#### :nail_care: Enhancement
- Sweeps can now be run from within jupyter / directly from python! https://docs.wandb.com/sweeps/python
- New openai gym integration will automatically log videos, enabled with the monitor_gym keyword argument to wandb.init
- Ray Tune logging callback in wandb.ray.WandbLogger
- New global config file in ~/.config/wandb for global settings
- Added tests for fastai, thanks @borisdayma
- Public api performance enhancements
- Deprecated username in favor of enitity in the public api for consistency
- Anonymous login support enabled by default
- New wandb.login method to be used in jupyter enabling anonymous logins
- Better dependency error messages for data frames
- Initial integration with spell.run
- All images are now rendered as PNG to avoid JPEG artifacts
- Public api now has a projects field
## 0.8.9 (Aug 19, 2019)
#### :bug: Bug Fix
- run.summary updates work in jupyter before log is called
- don't require numpy to be installed
- Setting nested keys in summary works
- notebooks in nested directories are properly saved
- Don't retry 404's / better error messaging from the server
- Strip leading slashes when loading paths in the public api
#### :nail_care: Enhancement
- Small files are batch uploaded as gzipped tarballs
- TensorBoardX gifs are logged to wandb
## 0.8.8 (Aug 13, 2019)
#### :bug: Bug Fix
- wandb.init properly handles network failures on startup
- Keras callback only logs examples if data_type or input_type is set
- Fix edge case PyTorch model logging bug
- Handle patching tensorboard multiple times in jupyter
- Sweep picks up config.yaml from the run directory
- Dataframes handle integer labels
- Handle invalid JSON when querying jupyter servers
#### :nail_care: Enhancement
- fastai uses a fixed seed for example logging
- increased the max number of images for fastai callback
- new wandb.Video tag for logging video
- sync=False argument to wandb.log moves logging to a thread
- New local sweep controller for custom search logic
- Anonymous login support for easier onboarding
- Calling wandb.init multiple times in jupyter doesn't error out
## 0.8.7 (Aug 7, 2019)
#### :bug: Bug Fix
- keras callback no longer guesses input_type for 2D data
- wandb.Image handles images with 1px height
#### :nail_care: Enhancement
- wandb Public API now has `run.scan_history` to return all history rows
- wandb.config prints helpful errors if used before calling init
- wandb.summary prints helpful errors if used before calling init
- filestream api points to new url on the backend
## 0.8.6 (July 31, 2019)
#### :bug: Bug Fix
- fastai callback uses the default monitor instead of assuming val_loss
- notebook introspections handles error cases and doesn't print stacktrace on failure
- Don't print description warning when setting name
- Fixed dataframe logging error with the keras callback
- Fixed line offsets in logs when resuming runs
- wandb.config casts non-builtins before writing to yaml
- vendored backports.tempfile to address missing package on install
#### :nail_care: Enhancement
- Added `api.sweep` to the python export api for querying sweeps
- Added `WANDB_NOTEBOOK_NAME` for specifying the notebook name in cases we can't infer it
- Added `WANDB_HOST` to override hostnames
- Store if a run was run within jupyter
- Client now supports stopping runs from the web ui
- Handle floats passed as step to `wandb.log`
- wandb.config has full unicode support
- sync the main file to wandb if code saving is enabled and it's untracked by git
- XGBoost callback: wandb.xgboost.wandb_callback()
## 0.8.5 (July 12, 2019)
#### :bug: Bug Fix
- Fixed plotly charts with large numpy arrays not rendering
- `wandb docker` works when nvidia is present
- Better error when non string keys are sent to log
- Relaxed pyyaml dependency to fix AMI installs
- Magic works in jupyter notebooks.
#### :nail_care: Enhancement
- New preview release of auto-dataframes for Keras
- Added input_type and output_type to the Keras callback for simpler config
- public api supports retrieving specific keys and custom xaxis
## 0.8.4 (July 8, 2019)
#### :bug: Bug Fix
- WANDB_IGNORE_GLOBS is respected on the final scan of files
- Unified run.id, run.name, and run.notes across all apis
- Handle funky terminal sizes when setting up our psuedo tty
- Fixed Jupyter notebook introspection logic
- run.summary.update() persists changes to the server
- tensorboard syncing is robust to invalid histograms and truncated files
#### :nail_care: Enhancement
- preview release of magic, calling wandb.init(magic=True) should automatically track config and metrics when possible
- cli now supports local installs of the backend
- fastai callback supports logging example images
## 0.8.3 (June 26, 2019)
#### :bug: Bug Fix
- image logging works in Windows
- wandb sync handles tfevents with a single timestep
- fix incorrect command in overview page for running runs
- handle histograms with > 512 bins when streaming tensorboard
- better error message when calling wandb sync on a file instead of a directory
#### :nail_care: Enhancement
- new helper function for handling hyperparameters in sweeps `wandb.config.user_items()`
- better mocking for improved testing
## 0.8.2 (June 20, 2019)
#### :bug: Bug Fix
- entity is persisted on wandb.run when queried from the server
- tmp files always use the temporary directory to avoid syncing
- raise error if file shrinks while uploading
- images log properly in windows
- upgraded pyyaml requirement to address CVE
- no longer store a history of rows to prevent memory leak
#### :nail_care: Enhancement
- summary now supports new dataframe format
- WANDB_SILENT environment variable writes all wandb messages to debug.log
- Improved error messages for windows and tensorboard logging
- output.log is uploaded at the end of each run
- metadata, requirements, and patches are uploaded at the beginning of a run
- when not running from a git repository, store the main python file
- added WANDB_DISABLE_CODE to prevent diffing and code saving
- when running in jupyter store the name of the notebook
- auto-login support for colab
- store url to colab notebook
- store the version of this library in config
- store sys.executable in metadata
- fastai callback no longer requires path
- wandb.init now accepts a notes argument
- The cli replaced the message argument with notes and name
## 0.8.1 (May 23, 2019)
#### :bug: Bug Fix
- wandb sync handles tensorboard embeddings
- wandb sync correctly handles images in tensorboard
- tf.keras correctly handles single input functional models
- wandb.Api().runs returns an iterator that's reusable
- WANDB_DIR within a hidden directory doesn't prevent syncing
- run.files() iterates over all files
- pytorch recurssion too deep error
#### :nail_care: Enhancement
- wandb sync accepts an --ignore argument with globs to skip files
- run.summary now has an items() method for iterating over all keys
## 0.8.0 (May 17, 2019)
#### :bug: Bug Fix
- Better error messages on access denied
- Better error messages when optional packages aren't installed
- Urls printed to the termial are url-escaped
- Namespaced tensorboard events work with histograms
- Public API now retries on failures and re-uses connection pool
- Catch git errors when remotes aren't pushed to origin
- Moved keras graph collection to on_train_begin to handle unbuilt models
- Handle more cases of not being able to save weights
- Updates to summary after resuming are persisted
- PyTorch histc logging fixed in 0.4.1
- Fixed `wandb sync` tensorboard import
#### :nail_care: Enhancement
- wandb.init(tensorboard=True) works with Tensorflow 2 and Eager Execution
- wandb.init(tensorboard=True) now works with tb-nightly and PyTorch
- Automatically log examples with tf.keras by adding missing validation_data
- Socket only binds to localhost for improved security and prevents firewall warnings in OSX
- Added user object to public api for getting the source user
- Added run.display_name to the public api
- Show display name in console output
- Added --tags, --job_group, and --job_type to `wandb run`
- Added environment variable for minimum time to run before considering crashed
- Added flake8 tests to CI, thanks @cclauss!
## 0.7.3 (April 15, 2019)
#### :bug: Bug Fix
- wandb-docker-run accepts image digests
- keras callback works in tensorflow2-alpha0
- keras model graph now puts input layer first
#### :nail_care: Enhancement
- PyTorch log frequency added for gradients and weights
- PyTorch logging performance enhancements
- wandb.init now accepts a name parameter for naming runs
- wandb.run.name reflects custom display names
- Improvements to nested summary values
- Deprecated wandb.Table.add_row in favor of wandb.Table.add_data
- Initial support for a fast.ai callback thanks to @borisdayma!
## 0.7.2 (March 19, 2019)
#### :bug: Bug Fix
- run.get_url resolves the default entity if one wasn't specified
- wandb restore accepts run paths with only slashes
- Fixed PyYaml deprecation warnings
- Added entrypoint shell script to manifest
- Strip newlines from cuda version
## 0.7.1 (March 14, 2019)
#### :bug: Bug Fix
- handle case insensitive docker credentials
- fix app_url for private cloud login flow
- don't retry 404's when starting sweep agents
## 0.7.0 (February 28, 2019)
#### :bug: Bug Fix
- ensure DNS lookup failures can't prevent startup
- centralized debug logging
- wandb agent waits longer to send a SIGKILL after sending SIGINT
#### :nail_care: Enhancement
- support for logging docker images with the WANDB_DOCKER env var
- WANDB_DOCKER automatically set when run in kubernetes
- new wandb-docker-run command to automatically set env vars and mount code
- wandb.restore supports launching docker for runs that ran with it
- python packages are now recorded and saved in a requirements.txt file
- cpu_count, gpu_count, gpu, os, and python version stored in wandb-metadata.json
- the export api now supports docker-like paths, i.e. username/project:run_id
- better first time user messages and login info
## 0.6.35 (January 29, 2019)
#### :bug: Bug Fix
- Improve error reporting for sweeps
## 0.6.34 (January 23, 2019)
#### :bug: Bug Fix
- fixed Jupyter logging, don't change logger level
- fixed resuming in Jupyter
#### :nail_care: Enhancement
- wandb.init now degrades gracefully if a user hasn't logged in to wandb
- added a **force** flag to wandb.init to require a machine to be logged in
- Tensorboard and TensorboardX logging is now automatically instrumented when enabled
- added a **tensorboard** to wandb.init which patches tensorboard for logging
- wandb.save handles now accepts a base path to files in sub directories
- wandb.tensorflow and wandb.tensorboard can now be accessed without directly importing
- `wandb sync` will now traverse a wandb run directory and sync all runs
## 0.6.33 (January 22, 2019)
#### :bug: Bug Fix
- Fixed race where wandb process could hang at the end of a run
## 0.6.32 (December 22, 2018)
#### :bug: Bug Fix
- Fix resuming in Jupyter on kernel restart
- wandb.save ensures files are pushed regardless of growth
#### :nail_care: Enhancement
- Added replace=True keyword to init for auto-resuming
- New run.resumed property that can be used to detect if we're resuming
- New run.step property to use for setting an initial epoch on resuming
- Made Keras callback save the best model as it improves
## 0.6.31 (December 20, 2018)
#### :bug: Bug Fix
- Really don't require numpy
- Better error message if wandb.log is called before wandb.init
- Prevent calling wandb.watch multiple times
- Handle datetime attributes in logs / plotly
#### :nail_care: Enhancement
- Add environment to sweeps
- Enable tagging in the public API and in wandb.init
- New media type wandb.Html for logging arbitrary html
- Add Public api.create_run method for custom integrations
- Added glob support to wandb.save, files save as they're written to
- Added wandb.restore for pulling files on resume
## 0.6.30 (December 6, 2018)
#### :bug: Bug Fix
- Added a timeout for generating diffs on large repos
- Fixed edge case where file syncing could hang
- Ensure all file changes are captured before exit
- Handle cases of sys.exit where code isn't passed
- Don't require numpy
#### :nail_care: Enhancement
- New `wandb sync` command that pushes a local directory to the cloud
- Support for syncing tfevents file during training
- Detect when running as TFJob and auto group
- New Kubeflow module with initial helpers for pipelines
## 0.6.29 (November 26, 2018)
#### :bug: Bug Fix
- Fixed history / summary bug
## 0.6.28 (November 24, 2018)
#### :nail_care: Enhancement
- Initial support for AWS SageMaker
- `hook_torch` renamed to `watch` with a deprecation warning
- Projects are automatically created if they don't exist
- Additional GPU memory_allocated metric added
- Keras Graph stores edges
#### :bug: Bug Fix
- PyTorch graph parsing is more robust
- Fixed PyTorch 0.3 support
- File download API supports WANDB_API_KEY authentication
## 0.6.27 (November 13, 2018)
#### :nail_care: Enhancement
- Sweeps work with new backend (early release).
- Summary tracks all history metrics unless they're overridden by directly writing
to summary.
- Files support in data API.
#### :bug: Bug Fix
- Show ongoing media file uploads in final upload progress.
## 0.6.26 (November 9, 2018)
#### :nail_care: Enhancement
- wandb.Audio supports duration
#### :bug: Bug Fix
- Pass username header in filestream API
## 0.6.25 (November 8, 2018)
#### :nail_care: Enhancement
- New wandb.Audio data type.
- New step keyword argument when logging metrics
- Ability to specify run group and job type when calling wandb.init() or via
environment variables. This enables automatic grouping of distributed training runs
in the UI
- Ability to override username when using a service account API key
#### :bug: Bug Fix
- Handle non-tty environments in Python2
- Handle non-existing git binary
- Fix issue where sometimes the same image was logged twice during a Keras step
## 0.6.23 (October 19, 2018)
#### :nail_care: Enhancement
- PyTorch
- Added a new `wandb.hook_torch` method which records the graph and logs gradients & parameters of pytorch models
- `wandb.Image` detects pytorch tensors and uses **torchvision.utils.make_grid** to render the image.
#### :bug: Bug Fix
- `wandb restore` handles the case of not being run from within a git repo.
## 0.6.22 (October 18, 2018)
#### :bug: Bug Fix
- We now open stdout and stderr in raw mode in Python 2 ensuring tools like bpdb work.
## 0.6.21 (October 12, 2018)
#### :nail_care: Enhancement
- Catastrophic errors are now reported to Sentry unless WANDB_ERROR_REPORTING is set to false
- Improved error handling and messaging on startup
## 0.6.20 (October 5, 2018)
#### :bug: Bug Fix
- The first image when calling wandb.log was not being written, now it is
- `wandb.log` and `run.summary` now remove whitespace from keys
## 0.6.19 (October 5, 2018)
#### :bug: Bug Fix
- Vendored prompt_toolkit < 1.0.15 because the latest ipython is pinned > 2.0
- Lazy load wandb.h5 only if `summary` is accessed to improve Data API performance
#### :nail_care: Enhancement
- Jupyter
- Deprecated `wandb.monitor` in favor of automatically starting system metrics after the first wandb.log call
- Added new **%%wandb** jupyter magic method to display live results
- Removed jupyter description iframe
- The Data API now supports `per_page` and `order` options to the `api.runs` method
- Initial support for wandb.Table logging
- Initial support for matplotlib logging
| 33.092055 | 121 | 0.736301 | eng_Latn | 0.983645 |
d5734338664d14e657b973200df2822304d77e88 | 25 | md | Markdown | README.md | troyashields/troyashields.github.io | e764c5abb4004346cc956dbb7a4ac8ac22c1f774 | [
"CC-BY-3.0"
] | null | null | null | README.md | troyashields/troyashields.github.io | e764c5abb4004346cc956dbb7a4ac8ac22c1f774 | [
"CC-BY-3.0"
] | null | null | null | README.md | troyashields/troyashields.github.io | e764c5abb4004346cc956dbb7a4ac8ac22c1f774 | [
"CC-BY-3.0"
] | null | null | null | # troyashields.github.io
| 12.5 | 24 | 0.8 | nld_Latn | 0.214738 |
d57387b4966427897d0d7317091946f5fe95d268 | 1,571 | md | Markdown | partiExp/Contributing.md | JovanWang/AdaptiveStreamSpTTMFramework | 3ba43efe0d78a3f93c14c03cb959db0b00927ab4 | [
"BSD-3-Clause"
] | 21 | 2018-01-01T15:08:14.000Z | 2022-02-06T03:49:03.000Z | partiExp/Contributing.md | JovanWang/AdaptiveStreamSpTTMFramework | 3ba43efe0d78a3f93c14c03cb959db0b00927ab4 | [
"BSD-3-Clause"
] | 2 | 2021-12-21T10:27:07.000Z | 2022-01-04T20:13:46.000Z | partiExp/Contributing.md | JovanWang/AdaptiveStreamSpTTMFramework | 3ba43efe0d78a3f93c14c03cb959db0b00927ab4 | [
"BSD-3-Clause"
] | 13 | 2017-05-07T03:51:45.000Z | 2022-03-24T06:36:47.000Z | Contributing to ParTI!
======================
This is the guide aboue contributing to ParTI!.
Language standard
-----------------
ParTI! mainly follows C99 standard, and must be compatible with GCC 4.9 through 6.2.
CUDA code follows C++03 standard, which is the default of NVCC compiler.
Indentation and format
----------------------
Feel free to use any indent style, but please respect the original style of an existing file.
Naming convention
-----------------
C does not have namespace, thus it is important to keep names from conflicting. All ParTI! functions have names starting with `spt`. Private funcions start with `spt_`.
Names of functions and types follow `PascalCase`. Constants and enumerations follow `UPPER_CASE`. While variables are not restricted to a naming convention.
Error checking
--------------
`spt_CheckError`, `spt_CheckOSError`, `spt_CheckCudaError` are used to check for invalid input or environmental exceptions.
Use `assert` to check for some conditions that should never happen on a production system, such as wrong data produced by other parts of ParTI!. I/O error or invalid data from the outside should not go into this category.
Using `const`
-------------
`const` provides immutability check, optimizes code, and improves documentation clarity. Correct usage of `const` against pointers and arrays are required.
Licensing and copyright
-----------------------
Contribution to ParTI! must license the code under LGPL version 3. Put a copyright notice alongside with your name at the top of each file you modify.
| 33.425532 | 221 | 0.725652 | eng_Latn | 0.998385 |
d57390ea7a276b4d836ad764bedb4afa705c2212 | 19,450 | md | Markdown | articles/azure-functions/functions-bindings-timer.md | beatrizmayumi/azure-docs.pt-br | ca6432fe5d3f7ccbbeae22b4ea05e1850c6c7814 | [
"CC-BY-4.0",
"MIT"
] | 39 | 2017-08-28T07:46:06.000Z | 2022-01-26T12:48:02.000Z | articles/azure-functions/functions-bindings-timer.md | beatrizmayumi/azure-docs.pt-br | ca6432fe5d3f7ccbbeae22b4ea05e1850c6c7814 | [
"CC-BY-4.0",
"MIT"
] | 562 | 2017-06-27T13:50:17.000Z | 2021-05-17T23:42:07.000Z | articles/azure-functions/functions-bindings-timer.md | beatrizmayumi/azure-docs.pt-br | ca6432fe5d3f7ccbbeae22b4ea05e1850c6c7814 | [
"CC-BY-4.0",
"MIT"
] | 113 | 2017-07-11T19:54:32.000Z | 2022-01-26T21:20:25.000Z | ---
title: Gatilho de temporizador para o Azure Functions
description: Entenda como usar gatilhos de temporizador no Azure Functions.
author: craigshoemaker
ms.assetid: d2f013d1-f458-42ae-baf8-1810138118ac
ms.topic: reference
ms.date: 11/18/2020
ms.author: cshoe
ms.custom: devx-track-csharp, devx-track-python
ms.openlocfilehash: f99f9d240a0a9220d3b7f57cddd0a4f8ba6b6101
ms.sourcegitcommit: 772eb9c6684dd4864e0ba507945a83e48b8c16f0
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 03/19/2021
ms.locfileid: "104595968"
---
# <a name="timer-trigger-for-azure-functions"></a>Gatilho de temporizador para o Azure Functions
Este artigo explica como trabalhar com gatilhos de temporizador no Azure Functions. Um gatilho de temporizador permite executar uma função em uma agenda.
[!INCLUDE [intro](../../includes/functions-bindings-intro.md)]
Para obter informações sobre como executar manualmente uma função disparada por temporizador, consulte [executar manualmente uma função não disparada por http](./functions-manually-run-non-http.md).
## <a name="packages---functions-2x-and-higher"></a>Pacotes-funções 2. x e superior
O gatilho de timer é fornecido no [Microsoft.Azure.WebJobs.Extensions](https://www.nuget.org/packages/Microsoft.Azure.WebJobs.Extensions) pacote NuGet, versão 2. x. O código-fonte do pacote está no repositório GitHub [azure-webjobs-sdk-extensions](https://github.com/Azure/azure-webjobs-sdk-extensions/blob/master/src/WebJobs.Extensions/Extensions/Timers/).
[!INCLUDE [functions-package-auto](../../includes/functions-package-auto.md)]
## <a name="packages---functions-1x"></a>Pacotes - Functions 1. x
O gatilho de timer é fornecido no [Microsoft.Azure.WebJobs.Extensions](https://www.nuget.org/packages/Microsoft.Azure.WebJobs.Extensions) pacote NuGet, versão 2. x. O código-fonte do pacote está no repositório GitHub [azure-webjobs-sdk-extensions](https://github.com/Azure/azure-webjobs-sdk-extensions/blob/v2.x/src/WebJobs.Extensions/Extensions/Timers/).
[!INCLUDE [functions-package-auto](../../includes/functions-package-auto.md)]
## <a name="example"></a>Exemplo
# <a name="c"></a>[C#](#tab/csharp)
O exemplo a seguir mostra uma [função C#](functions-dotnet-class-library.md) que é executada cada vez que os minutos têm um valor divisível por cinco (por exemplo, se a função começar em 18:57:00, o próximo desempenho será em 19:00:00). O [`TimerInfo`](https://github.com/Azure/azure-webjobs-sdk-extensions/blob/master/src/WebJobs.Extensions/Extensions/Timers/TimerInfo.cs) objeto é passado para a função.
```cs
[FunctionName("TimerTriggerCSharp")]
public static void Run([TimerTrigger("0 */5 * * * *")]TimerInfo myTimer, ILogger log)
{
if (myTimer.IsPastDue)
{
log.LogInformation("Timer is running late!");
}
log.LogInformation($"C# Timer trigger function executed at: {DateTime.Now}");
}
```
# <a name="c-script"></a>[Script do C#](#tab/csharp-script)
O exemplo a seguir mostra uma associação de gatilho de temporizador em um arquivo *function.json* e uma [função C# script](functions-reference-csharp.md) que usa a associação. A função grava um log que indica se esta chamada de função deve-se a uma ocorrência de agendamento ausente. O [`TimerInfo`](https://github.com/Azure/azure-webjobs-sdk-extensions/blob/master/src/WebJobs.Extensions/Extensions/Timers/TimerInfo.cs) objeto é passado para a função.
Aqui estão os dados de associação no arquivo *function.json*:
```json
{
"schedule": "0 */5 * * * *",
"name": "myTimer",
"type": "timerTrigger",
"direction": "in"
}
```
Aqui está o código de script do C#:
```csharp
public static void Run(TimerInfo myTimer, ILogger log)
{
if (myTimer.IsPastDue)
{
log.LogInformation("Timer is running late!");
}
log.LogInformation($"C# Timer trigger function executed at: {DateTime.Now}" );
}
```
# <a name="java"></a>[Java](#tab/java)
A função de exemplo a seguir é disparada e executada a cada cinco minutos. A anotação `@TimerTrigger` na função define o agendamento usando o mesmo formato de cadeia de caracteres que as [expressões CRON](https://en.wikipedia.org/wiki/Cron#CRON_expression).
```java
@FunctionName("keepAlive")
public void keepAlive(
@TimerTrigger(name = "keepAliveTrigger", schedule = "0 */5 * * * *") String timerInfo,
ExecutionContext context
) {
// timeInfo is a JSON string, you can deserialize it to an object using your favorite JSON library
context.getLogger().info("Timer is triggered: " + timerInfo);
}
```
# <a name="javascript"></a>[JavaScript](#tab/javascript)
O exemplo a seguir mostra uma associação de gatilho de temporizador em um arquivo *function.json* e uma [função JavaScript](functions-reference-node.md) que usa a associação. A função grava um log que indica se esta chamada de função deve-se a uma ocorrência de agendamento ausente. Um [objeto de timer](#usage) é passado para a função.
Aqui estão os dados de associação no arquivo *function.json*:
```json
{
"schedule": "0 */5 * * * *",
"name": "myTimer",
"type": "timerTrigger",
"direction": "in"
}
```
Aqui está o código JavaScript:
```JavaScript
module.exports = function (context, myTimer) {
var timeStamp = new Date().toISOString();
if (myTimer.IsPastDue)
{
context.log('Node is running late!');
}
context.log('Node timer trigger function ran!', timeStamp);
context.done();
};
```
# <a name="powershell"></a>[PowerShell](#tab/powershell)
O exemplo a seguir demonstra como configurar o *function.jsem* e *run.ps1* arquivo para um gatilho de temporizador no [PowerShell](./functions-reference-powershell.md).
```json
{
"bindings": [
{
"name": "Timer",
"type": "timerTrigger",
"direction": "in",
"schedule": "0 */5 * * * *"
}
]
}
```
```powershell
# Input bindings are passed in via param block.
param($Timer)
# Get the current universal time in the default string format.
$currentUTCtime = (Get-Date).ToUniversalTime()
# The 'IsPastDue' property is 'true' when the current function invocation is later than scheduled.
if ($Timer.IsPastDue) {
Write-Host "PowerShell timer is running late!"
}
# Write an information log with the current time.
Write-Host "PowerShell timer trigger function ran! TIME: $currentUTCtime"
```
Uma instância do [objeto de timer](#usage) é passada como o primeiro argumento para a função.
# <a name="python"></a>[Python](#tab/python)
O exemplo a seguir usa uma associação de gatilho de temporizador cuja configuração é descrita na *function.jsno* arquivo. A [função Python](functions-reference-python.md) real que usa a associação é descrita no arquivo *__init__. py* . O objeto passado para a função é do tipo [objeto Azure. Functions. TimerRequest](/python/api/azure-functions/azure.functions.timerrequest). A lógica de função grava nos logs indicando se a invocação atual é devido a uma ocorrência de agendamento ausente.
Aqui estão os dados de associação no arquivo *function.json*:
```json
{
"name": "mytimer",
"type": "timerTrigger",
"direction": "in",
"schedule": "0 */5 * * * *"
}
```
Aqui está o código Python:
```python
import datetime
import logging
import azure.functions as func
def main(mytimer: func.TimerRequest) -> None:
utc_timestamp = datetime.datetime.utcnow().replace(
tzinfo=datetime.timezone.utc).isoformat()
if mytimer.past_due:
logging.info('The timer is past due!')
logging.info('Python timer trigger function ran at %s', utc_timestamp)
```
---
## <a name="attributes-and-annotations"></a>Atributos e anotações
# <a name="c"></a>[C#](#tab/csharp)
Em [bibliotecas de classes do C#](functions-dotnet-class-library.md), utilize o atributo [TimerTriggerAttribute](https://github.com/Azure/azure-webjobs-sdk-extensions/blob/master/src/WebJobs.Extensions/Extensions/Timers/TimerTriggerAttribute.cs).
O construtor do atributo usa a expressão CRON ou um `TimeSpan`. Você só poderá usar `TimeSpan` se o aplicativo de funções estiver em execução em um plano do serviço de aplicativo. `TimeSpan` Não tem suporte para funções Premium de consumo ou elástico.
O exemplo a seguir mostra uma expressão CRON:
```csharp
[FunctionName("TimerTriggerCSharp")]
public static void Run([TimerTrigger("0 */5 * * * *")]TimerInfo myTimer, ILogger log)
{
if (myTimer.IsPastDue)
{
log.LogInformation("Timer is running late!");
}
log.LogInformation($"C# Timer trigger function executed at: {DateTime.Now}");
}
```
# <a name="c-script"></a>[Script do C#](#tab/csharp-script)
O script C# não dá suporte a atributos.
# <a name="java"></a>[Java](#tab/java)
A anotação `@TimerTrigger` na função define o agendamento usando o mesmo formato de cadeia de caracteres que as [expressões CRON](https://en.wikipedia.org/wiki/Cron#CRON_expression).
```java
@FunctionName("keepAlive")
public void keepAlive(
@TimerTrigger(name = "keepAliveTrigger", schedule = "0 */5 * * * *") String timerInfo,
ExecutionContext context
) {
// timeInfo is a JSON string, you can deserialize it to an object using your favorite JSON library
context.getLogger().info("Timer is triggered: " + timerInfo);
}
```
# <a name="javascript"></a>[JavaScript](#tab/javascript)
O JavaScript não dá suporte a atributos.
# <a name="powershell"></a>[PowerShell](#tab/powershell)
Não há suporte para atributos pelo PowerShell.
# <a name="python"></a>[Python](#tab/python)
O Python não dá suporte a atributos.
---
## <a name="configuration"></a>Configuração
A tabela a seguir explica as propriedades de configuração de associação que você define no arquivo *function.json* e no atributo `TimerTrigger`.
|Propriedade function.json | Propriedade de atributo |Descrição|
|---------|---------|----------------------|
|**tipo** | n/d | Deve ser definido como "timerTrigger". Essa propriedade é definida automaticamente quando você cria o gatilho no portal do Azure.|
|**direction** | n/d | Deve ser definido como "in". Essa propriedade é definida automaticamente quando você cria o gatilho no portal do Azure. |
|**name** | n/d | O nome da variável que representa o objeto de temporizador no código de função. |
|**agendamento**|**ScheduleExpression**|Um [expressão CRON](#ncrontab-expressions) ou um valor [TimeSpan](#timespan). É possível usar um `TimeSpan` somente para um aplicativo de função executado em um Plano do Serviço de Aplicativo. Você pode colocar a expressão de agendamento em uma configuração de aplicativo e definir essa propriedade como o nome da configuração do aplicativo encapsulado em **%** sinais, como neste exemplo: "% ScheduleAppSetting%". |
|**runOnStartup**|**RunOnStartup**|Se `true`, a função será invocada quando o runtime for iniciado. Por exemplo, o runtime inicia quando o aplicativo de função desperta depois de ficar ocioso devido à inatividade. Quando o aplicativo de funções é reiniciado devido a alterações de função e quando o aplicativo de funções é dimensionado horizontalmente. Portanto, **runOnStartup** deve ser raramente, se já estiver definido como `true` , especialmente em produção. |
|**useMonitor**|**UseMonitor**|Definido como `true` ou `false` para indicar se o agendamento deve ser monitorado. Agendar o monitoramento persiste as ocorrências de agendamento para ajudar a garantir que o agendamento seja mantido corretamente mesmo quando instâncias do aplicativo de função forem reiniciadas. Se não for definido explicitamente, o padrão será `true` para agendas que têm um intervalo de recorrência maior ou igual a 1 minuto. Para agendamentos que disparam mais de uma vez por minuto, o padrão é `false`.
[!INCLUDE [app settings to local.settings.json](../../includes/functions-app-settings-local.md)]
> [!CAUTION]
> Recomendamos a configuração **runOnStartup** para `true` em produção. Usar essa configuração faz com que código seja executado em momentos altamente imprevisíveis. Em determinadas configurações de produção, essas execuções extras podem resultar em custos significativamente mais altos para aplicativos hospedados em planos de consumo. Por exemplo, com **runOnStartup** habilitado, o gatilho é invocado sempre que seu aplicativo de funções é dimensionado. Verifique se você compreender totalmente o comportamento de produção de suas funções antes de habilitar **runOnStartup** em produção.
## <a name="usage"></a>Uso
Quando uma função de gatilho de temporizador é invocada, um objeto de temporizador é passado para a função. O JSON a seguir é uma representação de exemplo do objeto timer.
```json
{
"schedule":{
},
"scheduleStatus": {
"last":"2016-10-04T10:15:00+00:00",
"lastUpdated":"2016-10-04T10:16:00+00:00",
"next":"2016-10-04T10:20:00+00:00"
},
"isPastDue":false
}
```
A propriedade `isPastDue` é `true` quando a invocação da função atual é posterior ao agendado. Por exemplo, uma reinicialização do aplicativo de função pode causar a perda de uma invocação.
## <a name="ncrontab-expressions"></a>Expressões NCRONTAB
Azure Functions usa a biblioteca [NCronTab](https://github.com/atifaziz/NCrontab) para interpretar as expressões NCronTab. Uma expressão NCRONTAB é semelhante a uma expressão CRON, exceto que ela inclui um sexto campo adicional no início a ser usado para a precisão de tempo em segundos:
`{second} {minute} {hour} {day} {month} {day-of-week}`
Cada campo pode ter um dos seguintes tipos de valores:
|Type |Exemplo |Quando disparado |
|---------|---------|---------|
|Um valor específico |<nobr>`0 5 * * * *`</nobr>| Uma vez a cada hora do dia, no minuto 5 de cada hora |
|Todos os valores (`*`)|<nobr>`0 * 5 * * *`</nobr>| A cada minuto na hora, começando na hora 5 |
|Um intervalo (`-` operador)|<nobr>`5-7 * * * * *`</nobr>| Três vezes por minuto em segundos de 5 a 7 durante cada minuto de cada hora de cada dia |
|Um conjunto de valores (`,` operador)|<nobr>`5,8,10 * * * * *`</nobr>| Três vezes por minuto em segundos 5, 8 e 10 durante cada minuto de cada hora de cada dia |
|Um valor de intervalo (`/` operador)|<nobr>`0 */5 * * * *`</nobr>| 12 vezes por hora – em segundo 0 de cada quinto minuto de cada hora de cada dia |
[!INCLUDE [functions-cron-expressions-months-days](../../includes/functions-cron-expressions-months-days.md)]
### <a name="ncrontab-examples"></a>Exemplos de NCRONTAB
Aqui estão alguns exemplos de expressões NCRONTAB que você pode usar para o gatilho de temporizador no Azure Functions.
| Exemplo | Quando disparado |
|--------------------|------------------------------------|
| `0 */5 * * * *` | uma vez a cada cinco minutos |
| `0 0 * * * *` | uma vez a cada hora |
| `0 0 */2 * * *` | uma vez a cada duas horas |
| `0 0 9-17 * * *` | uma vez a cada hora entre 9h e 17h |
| `0 30 9 * * *` | às 9h30 todos os dias |
| `0 30 9 * * 1-5` | às 9h30 todo dia útil |
| `0 30 9 * Jan Mon` | em 9H30 toda segunda-feira em janeiro |
> [!NOTE]
> A expressão NCRONTAB requer um formato de **seis campos** . A posição sexto campo é um valor para segundos que é colocado no início da expressão. Não há suporte para expressões cron de cinco campos no Azure.
### <a name="ncrontab-time-zones"></a>NCRONTAB fuso horário
Os números em uma expressão CRON se referem a uma hora e uma data, não a um período de tempo. Por exemplo, um 5 no campo `hour` se refere a 5h, não cada cinco horas.
[!INCLUDE [functions-timezone](../../includes/functions-timezone.md)]
## <a name="timespan"></a>TimeSpan
É possível usar um `TimeSpan` somente para um aplicativo de função executado em um Plano do Serviço de Aplicativo.
Ao contrário de uma expressão CRON, um valor `TimeSpan` especifica o intervalo de tempo entre cada invocação de função. Quando uma função é concluída após a execução por mais tempo do que o intervalo especificado, o temporizador imediatamente chama a função novamente.
Expresso como uma cadeia de caracteres, o formato `TimeSpan` é `hh:mm:ss` quando `hh` é menor que 24. Quando os dois primeiros dígitos são 24 ou superior, o formato é `dd:hh:mm`. Estes são alguns exemplos:
| Exemplo | Quando disparado |
|--------------|----------------|
| "01:00:00" | a cada hora |
| "00:01:00" | a cada minuto |
| "25:00:00" | a cada 25 dias |
| "1,00:00:00" | Todos os dias |
## <a name="scale-out"></a>Escalabilidade horizontal
Se um aplicativo de funções se expandir para várias instâncias, apenas uma única instância de uma função disparada por temporizador será executada em todas as instâncias. Ele não será disparado novamente se houver uma invocação pendente ainda em execução.
## <a name="function-apps-sharing-storage"></a>Armazenamento de compartilhamento de aplicativos de função
Se você estiver compartilhando contas de armazenamento entre aplicativos de funções que não são implantados no serviço de aplicativo, talvez seja necessário atribuir explicitamente a ID do host a cada aplicativo.
| Versão do Functions | Configuração |
| ----------------- | ---------------------------------------------------- |
| 2. x (e superior) | A variável de ambiente `AzureFunctionsWebHost__hostid` |
| 1.x | `id` em *host.jsem* |
Você pode omitir o valor de identificação ou definir manualmente cada aplicativo de função que identifica a configuração para um valor diferente.
O gatilho de temporizador usa um bloqueio de armazenamento para garantir que haja apenas uma instância de temporizador quando um aplicativo de funções é dimensionado para várias instâncias. Se dois aplicativos de funções compartilharem a mesma configuração de identificação e cada um usar um gatilho de temporizador, apenas um temporizador será executado.
## <a name="retry-behavior"></a>Tentar comportamento novamente
Ao contrário do gatilho de fila, o gatilho de temporizador não tenta novamente após a falha de uma função. Quando uma função falha, ele não é chamado novamente até a próxima vez na agenda.
## <a name="manually-invoke-a-timer-trigger"></a>Invocar manualmente um gatilho de temporizador
O gatilho de temporizador para Azure Functions fornece um webhook HTTP que pode ser invocado para disparar a função manualmente. Isso pode ser extremamente útil nos cenários a seguir.
* Teste de integração
* Trocas de slot como parte de uma atividade de smoke test ou aquecimento
* Implantação inicial de uma função para popular imediatamente um cache ou uma tabela de pesquisa em um banco de dados
Veja [executar manualmente uma função não disparada por http](./functions-manually-run-non-http.md) para obter detalhes sobre como invocar manualmente uma função disparada por temporizador.
## <a name="troubleshooting"></a>Solução de problemas
Para obter informações sobre o que fazer quando o gatilho de timer não funcionar conforme o esperado, confira [Investigar e relatar problemas com funções disparadas de timer não acionadas](https://github.com/Azure/azure-functions-host/wiki/Investigating-and-reporting-issues-with-timer-triggered-functions-not-firing).
## <a name="next-steps"></a>Próximas etapas
> [!div class="nextstepaction"]
> [Vá para um guia de início rápido que use um gatilho de temporizador](functions-create-scheduled-function.md)
> [!div class="nextstepaction"]
> [Aprenda mais sobre gatilhos e de associações do Azure Functions](functions-triggers-bindings.md)
| 49.871795 | 590 | 0.722674 | por_Latn | 0.997203 |
d573a19e8320a4bc76bb06dfd5040e261d7c05c9 | 255 | md | Markdown | _members/jackson_morgan.md | jpmorgan98/CEMeNT-PSAAP.github.io | ac09f177ce55de21c75efcd5ede903f34d3c0b39 | [
"BSD-3-Clause"
] | null | null | null | _members/jackson_morgan.md | jpmorgan98/CEMeNT-PSAAP.github.io | ac09f177ce55de21c75efcd5ede903f34d3c0b39 | [
"BSD-3-Clause"
] | null | null | null | _members/jackson_morgan.md | jpmorgan98/CEMeNT-PSAAP.github.io | ac09f177ce55de21c75efcd5ede903f34d3c0b39 | [
"BSD-3-Clause"
] | null | null | null | ---
title: "Jackson Morgan"
excerpt: "Graduate Student, Oregon State Univerity"
classes: wide
header:
teaser: assets/bio/jackson_morgan.jpg
author: Jackson Morgan
---
## Education
* BS, Mechanical Engineering, Oregon Institute of Technology, 2020
| 17 | 66 | 0.74902 | eng_Latn | 0.576343 |
d573a2ebd94fe40f5303fad3879926fee7c13a60 | 1,831 | md | Markdown | user/pages/02.basics/01.requirements/docs.md | shanegring/r00t | 1dee7683bc56eec7ea14d5af910a864eda249b8d | [
"MIT"
] | null | null | null | user/pages/02.basics/01.requirements/docs.md | shanegring/r00t | 1dee7683bc56eec7ea14d5af910a864eda249b8d | [
"MIT"
] | null | null | null | user/pages/02.basics/01.requirements/docs.md | shanegring/r00t | 1dee7683bc56eec7ea14d5af910a864eda249b8d | [
"MIT"
] | null | null | null | ---
title: Grid
taxonomy:
category:
- docs
visible: true
---
Lorem markdownum pius. Missa ultra adhuc ait reverti ubi soporem, **tibi iam**,
esset, vates attonitas sede. Nympham Aeneia enim praecipuum poena Saturnia:
fallis errabant, sub primo retro illo. Caesariem tincta natam contineat demens.
*Si sed* ardescunt Delphice quasque alteraque servant.
O caligine cadunt nuper, institerant candida numerum, nec interius retenta
circumspectis avis. Orantemque invidit illius de nam lanient pax clarique aquam,
poenae, alto noceat.
## Percussae oculos
Defendentia **flammas mundi salutem** fraudate, non munus revirescere tamen,
imago? Ad sit festumque [super](http://hipstermerkel.tumblr.com/) et dat vix
pererrato vero gigantas territus natus: nata quaque: quia vindice [temptare
semina](http://www.lipsum.com/)! Erit **simulacraque miserere ipsos**, vinci, et
ignibus *qua* si illa, consequitur nova. Constitit habet coniugis; coegit nostri
in fuissem!
Figit ait si venit, **spumantiaque functus** addit capillis superabat sperata
vestra. In nymphas cervus eram feret lingua, hunc, nulla quae. Gens *artisque*
ad peregit nitido cursu pondere. Petitur ex virtus, terrae infesto Circen: voce
roganti latet. Exit hydrae, expellitur onerosa gratissima iniustum Clytii
crimen.
## Pactique in quibus pariterque praebebat mare dapes
Sonat timeam furori non Sigei furiali os ut, orbe! Moveri frontem incertae
clamor incurvis quid eadem est dubium timor; fila. Suos *trepidaeque* cornua
sparsus.
Mihi [aut palustribus](http://www.billmays.net/), natus semilacerque audito
Enaesimus, fuerat refert. Aevi et evadere potentior Pergama sis.
Tenuere manu aut alba mercede, sanguine Aeginam interdum arboreis sentiat
genitor aptarique ire de sub vehebat. Aspera sedesque, et tempus deseruere
contenta, rex interea nisi arma.
| 40.688889 | 80 | 0.790279 | cat_Latn | 0.210042 |
d573c1cb1d0ea74b426f872e69a04ccfd14457d8 | 25 | md | Markdown | README.md | kumarkarthi/Order-management-system | a6e1b1471affa04b20e81cbc91cd74904c4f2e15 | [
"MIT"
] | null | null | null | README.md | kumarkarthi/Order-management-system | a6e1b1471affa04b20e81cbc91cd74904c4f2e15 | [
"MIT"
] | null | null | null | README.md | kumarkarthi/Order-management-system | a6e1b1471affa04b20e81cbc91cd74904c4f2e15 | [
"MIT"
] | null | null | null | # Order-management-system | 25 | 25 | 0.84 | pol_Latn | 0.424665 |
d573dbe23fa4704b69e2a281545113904e1193c2 | 202 | md | Markdown | _posts/2019-05-28-post-the-key-to-learning-fast-is-looking-dumb.md | nature-ghost/minimal-mistakes | 1f3f641ca26bbc5c9085b13abb9957ccd089ac6c | [
"MIT"
] | null | null | null | _posts/2019-05-28-post-the-key-to-learning-fast-is-looking-dumb.md | nature-ghost/minimal-mistakes | 1f3f641ca26bbc5c9085b13abb9957ccd089ac6c | [
"MIT"
] | null | null | null | _posts/2019-05-28-post-the-key-to-learning-fast-is-looking-dumb.md | nature-ghost/minimal-mistakes | 1f3f641ca26bbc5c9085b13abb9957ccd089ac6c | [
"MIT"
] | null | null | null | ---
title: "Post: The key to learning fast is looking dumb"
date: 2019-05-28T05:00:00:00+09:00
categories:
- Study
tags:
- Javascript
- async
- await
link: https://link.medium.com/AdIz8CQe2W
--- | 18.363636 | 55 | 0.683168 | eng_Latn | 0.323604 |
d573ea5af2765023ef4655b64db890038274bafa | 543 | md | Markdown | _games/runjumpers.md | walsh9/walsh9.net | 5981b06227e222544b0757dc707cf4a174d0f1db | [
"MIT"
] | null | null | null | _games/runjumpers.md | walsh9/walsh9.net | 5981b06227e222544b0757dc707cf4a174d0f1db | [
"MIT"
] | null | null | null | _games/runjumpers.md | walsh9/walsh9.net | 5981b06227e222544b0757dc707cf4a174d0f1db | [
"MIT"
] | null | null | null | ---
title: "Runjumpers"
font: "Bangers"
image: "runjumpers04.gif"
home: https://walsh9.github.io/runjumpers/
sortorder: 1
links:
- title: "itch.io Jam Submission Page"
url: https://itch.io/jam/gbjam-5/rate/90391
- title: Post-mortem
url: http://walsh9.online/games/runjumpers-post-mortem
actions:
- title: "View Source"
url: https://github.com/walsh9/runjumpers
- title: "Play Online"
url: https://walsh9.github.io/runjumpers/
---
A game about running and jumping.
Made for the [GBJAM 5](https://itch.io/jam/gbjam-5).
| 25.857143 | 58 | 0.696133 | kor_Hang | 0.161884 |
d574012da6164b3829acd07b1c973d0b86a2d469 | 3,780 | md | Markdown | docs/components/BottomSheetBehavior.md | AttwellBrian/material-components-android | b082edabdc9ce35d3cf76e08c83ba191386f8db3 | [
"Apache-2.0"
] | null | null | null | docs/components/BottomSheetBehavior.md | AttwellBrian/material-components-android | b082edabdc9ce35d3cf76e08c83ba191386f8db3 | [
"Apache-2.0"
] | null | null | null | docs/components/BottomSheetBehavior.md | AttwellBrian/material-components-android | b082edabdc9ce35d3cf76e08c83ba191386f8db3 | [
"Apache-2.0"
] | null | null | null | <!--docs:
title: "Bottom Sheets"
layout: detail
section: components
excerpt: "Bottom sheets slide up from the bottom of the screen to reveal more content."
iconId: bottom_sheet
path: /catalog/bottom-sheet-behavior/
-->
# Bottom Sheets
<!--{: .article__asset.article__asset--screenshot }-->
`BottomSheetBehavior` is applied to a child of
[CoordinatorLayout](CoordinatorLayout.md)
to make that child a **persistent bottom sheet**.
Persistent bottom sheets are views that come up from the bottom of the
screen, elevated over the main content. They can be dragged vertically to
expose more or less of their content.
Note: If you want to use Bottom Sheets that are modal (dialogs), use
[BottomSheetDialogFragment](BottomSheetDialogFragment.md).
## Design & API Documentation
- [Material Design guidelines: Bottom
Sheets](https://material.io/guidelines/components/bottom-sheets.html#bottom-sheets-persistent-bottom-sheets)
<!--{: .icon-list-item.icon-list-item--spec }-->
- [Class
definition](https://github.com/material-components/material-components-android/tree/master/lib/java/android/support/design/widget/BottomSheetBehavior.java)
<!--{: .icon-list-item.icon-list-item--link }-->
- [Class
overview](https://developer.android.com/reference/android/support/design/widget/BottomSheetBehavior.html)
<!--{: .icon-list-item.icon-list-item--link }--> <!--{: .icon-list }-->
## Usage
`BottomSheetBehavior` works in tandem with CoordinatorLayout to let you display
content on a Bottom sheet (a layer on top of the main content), perform
enter/exit animations, respond to dragging/swiping gestures, etc.
Bottom sheets have 5 states:
- `STATE_COLLAPSED`: The bottom sheet is visible but only showing its peek
height. This state is usually the 'resting position' of a Bottom Sheet. The
peek height is chosen by the developer and should be enough to indicate
there is extra content, allow the user to trigger an action or expand the
bottom sheet.
- `STATE_EXPANDED`: The bottom sheet is visible and its maximum height and it
is neither dragging or settling (see below).
- `STATE_DRAGGING`: The user is actively dragging the bottom sheet up or down.
- `STATE_SETTLING`: The bottom sheet is settling to specific height after a
drag/swipe gesture. This will be the peek height, expanded height, or
0, in case the user action caused the bottom sheet to hide.
- `STATE_HIDDEN`: The bottom sheet is no longer visible.
If you're already using CoordinatorLayout for your activity, adding a bottom
sheet is trivial:
1. Add any View as a direct child of CoordinatorLayout.
2. Apply the behavior by adding the following xml attribute
`app:layout_behavior="android.support.design.widget.BottomSheetBehavior"`
3. Set the desired behavior flags
- `app:behavior_hideable` whether this bottom sheet can be hidden by
dragging it down.
- `app:behavior_peekHeight` the peek height for the collapsed state.
- `app:behavior_skipCollapsed` if the bottom sheet is hideable, and this
is set to true, it does not have a collapsed state.
To programatically control the bottom sheet you can call the `setState` method
on the `BottomSheetBehavior`. A common pattern is setting a peek height and
setting the state to collapsed to make it visible to the user:
```java
bottomSheetBehavior.setPeekHeight(300);
bottomSheetBehavior.setState(BottomSheetBehavior.STATE_COLLAPSED);
```
## Related Concepts
Using [BottomSheetDialogFragment](BottomSheetDialogFragment.md) provides a
similar UI and interactions as `BottomSheetBehavior`, however
BottomSheetDialogFragment does not require CoordinatorLayout and creates a modal
bottom sheet (essentially a dialog).
| 43.448276 | 159 | 0.763492 | eng_Latn | 0.967387 |
d5746780901d18f94f1575265adf50a519d4cdf7 | 327 | md | Markdown | README.md | keygenqt/MyLibrary-webapp | 7b156976af16a5dfbeba31b0063056d3aea0e4af | [
"Apache-2.0"
] | 1 | 2021-01-18T08:47:48.000Z | 2021-01-18T08:47:48.000Z | README.md | keygenqt/MyLibrary-webapp | 7b156976af16a5dfbeba31b0063056d3aea0e4af | [
"Apache-2.0"
] | null | null | null | README.md | keygenqt/MyLibrary-webapp | 7b156976af16a5dfbeba31b0063056d3aea0e4af | [
"Apache-2.0"
] | 1 | 2021-01-18T07:26:10.000Z | 2021-01-18T07:26:10.000Z | MyLibrary
===================
MyLibrary is an application for cataloging your books library.
The application is designed to help unite lovers of literature.
Find a rare book among users MyLibrary.
**It's desktop part - [Electron](https://www.electronjs.org/) + [React](https://reactjs.org/)**
| 29.727273 | 95 | 0.712538 | eng_Latn | 0.7047 |
d575013187d399316be9960817fdca07a471d0b1 | 674 | md | Markdown | README.md | kulikov/go-sbus | b24eca9dd232cde804383fe7695310832c53ab4a | [
"BSD-3-Clause"
] | 1 | 2017-01-30T20:09:10.000Z | 2017-01-30T20:09:10.000Z | README.md | kulikov/go-sbus | b24eca9dd232cde804383fe7695310832c53ab4a | [
"BSD-3-Clause"
] | 1 | 2018-07-11T17:20:27.000Z | 2018-07-11T17:20:27.000Z | README.md | kulikov/go-sbus | b24eca9dd232cde804383fe7695310832c53ab4a | [
"BSD-3-Clause"
] | null | null | null | # go-sbus
### Pub/Sub
```golang
import "github.com/kulikov/go-sbus"
sbus.Sub("my-command-subject", func(msg sbus.Message, log *logrus.Entry) error {
log.Infof("Receive: %v", msg)
return nil
})
sbus.Pub("my-command-subject", map[string]string{"do": "any"})
```
### Request/Reply
```golang
import "github.com/kulikov/go-sbus"
sbus.Sub("get-user", func(msg sbus.Message, log *logrus.Entry) error {
sbus.Reply(map[string]string{"name": "dima", "userId": msg.Data["userId"]})
return nil
})
sbus.Request("get-user", map[string]string{"userId":"12345"}, func(msg sbus.Message, log *logrus.Entry) error {
log.Infof("Result: %v", msg)
return nil
})
```
| 23.241379 | 111 | 0.655786 | yue_Hant | 0.18882 |
d575556808c3c99b85ace6379ce49868eae53480 | 527 | md | Markdown | ML based Multi-label Text Classification/Readme.md | Ivanka07/Blog_References | 0a4a8f0eb7b94ac90137001a84b28ea84b4622d2 | [
"MIT"
] | 6 | 2021-05-28T11:32:31.000Z | 2022-03-24T20:15:48.000Z | ML based Multi-label Text Classification/Readme.md | Ivanka07/Blog_References | 0a4a8f0eb7b94ac90137001a84b28ea84b4622d2 | [
"MIT"
] | 1 | 2020-10-11T15:48:12.000Z | 2020-10-14T09:16:07.000Z | ML based Multi-label Text Classification/Readme.md | Ivanka07/Blog_References | 0a4a8f0eb7b94ac90137001a84b28ea84b4622d2 | [
"MIT"
] | 8 | 2021-08-25T00:21:55.000Z | 2022-03-20T00:19:13.000Z | Machine Learning Based Models for Multi-Label Text Classification [Reuters Dataset] (https://www.kaggle.com/nltkdata/reuters) <br />
Takeaways: <br />
1. Introduction to Text-processing
2. Feature Extraction
3. Visualizing Text Data
4. Models for Multi-Label Classification
5. OneVsRest Classifier
6. Model Evaluation with Micro and Macro Averaging<br />
TO Do: <br />
* [x] Use T-SNE for Visualizing tf-idf vectors
* [x] Compare Machine learning models.
* [x] Compare OneVsRest and LabelPowerSet.
* [ ] Use Word Embeddings
| 31 | 132 | 0.759013 | kor_Hang | 0.552321 |
d5755bea0f087e692c8cd15137fcc20e9ec0edcc | 189 | md | Markdown | _posts/2022-2-3-foo.md | visionairs/web | ab81bb3892aecb6272c785ea0dd9f926f106dfaf | [
"CC-BY-3.0"
] | null | null | null | _posts/2022-2-3-foo.md | visionairs/web | ab81bb3892aecb6272c785ea0dd9f926f106dfaf | [
"CC-BY-3.0"
] | null | null | null | _posts/2022-2-3-foo.md | visionairs/web | ab81bb3892aecb6272c785ea0dd9f926f106dfaf | [
"CC-BY-3.0"
] | 1 | 2022-01-27T18:28:06.000Z | 2022-01-27T18:28:06.000Z | ---
layout: post
title: Tensorflow with Intel Realsense
---
<ul class="actions">
<li><a href="/Notebooks/TensorFlow-HUB/IntelRealseDetection.html" class="button">Check now</a></li>
</ul>
| 21 | 100 | 0.708995 | kor_Hang | 0.301551 |
d57606d0378e2b3e00202dcf305a5403e31910e0 | 1,112 | md | Markdown | docs/code-quality/c6296.md | 1DanielaBlanco/visualstudio-docs.es-es | 9e934cd5752dc7df6f5e93744805e3c600c87ff0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/code-quality/c6296.md | 1DanielaBlanco/visualstudio-docs.es-es | 9e934cd5752dc7df6f5e93744805e3c600c87ff0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/code-quality/c6296.md | 1DanielaBlanco/visualstudio-docs.es-es | 9e934cd5752dc7df6f5e93744805e3c600c87ff0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: C6296
ms.date: 11/04/2016
ms.topic: reference
f1_keywords:
- C6296
helpviewer_keywords:
- C6296
ms.assetid: 226573e0-db18-4c44-8fc6-0bc09d1028bc
author: mikeblome
ms.author: mblome
manager: wpickett
ms.workload:
- multiple
ms.openlocfilehash: b036cfda3a951654f9f92918d2a86ea5c1d0b8a0
ms.sourcegitcommit: 21d667104199c2493accec20c2388cf674b195c3
ms.translationtype: MT
ms.contentlocale: es-ES
ms.lasthandoff: 02/08/2019
ms.locfileid: "55914586"
---
# <a name="c6296"></a>C6296
Advertencia C6296: Bucle for definido incorrecto: El cuerpo del bucle se ejecuta solo una vez
Esta advertencia indica que un bucle for podría no funcionar según lo previsto. Cuando el índice es sin signo y un bucle cuenta hacia atrás desde cero, el cuerpo se ejecuta solo una vez.
## <a name="example"></a>Ejemplo
El código siguiente genera esta advertencia:
```
void f( )
{
unsigned int i;
for (i = 0; i < 100; i--)
{
// code ...
}
}
```
Para corregir esta advertencia, utilice el código siguiente:
```
void f( )
{
unsigned int i;
for (i = 0; i < 100; i++)
{
// code ...
}
}
``` | 20.592593 | 187 | 0.709532 | spa_Latn | 0.775232 |
d57661baf4e1657d62841dac7b14a4c04c770b0c | 1,848 | md | Markdown | AlchemyInsights/micro-delays-or-throttling-in-exchange-online-powershell.md | isabella232/OfficeDocs-AlchemyInsights-pr.ru-RU | d76cee281de068f382e8f53f2917f5d7e1dd9bfa | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-05-19T19:07:42.000Z | 2020-05-19T19:07:42.000Z | AlchemyInsights/micro-delays-or-throttling-in-exchange-online-powershell.md | MicrosoftDocs/OfficeDocs-AlchemyInsights-pr.ru-RU | b43e825f8df7ec85c583a3e3790e29ca77ef25c0 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2022-02-09T06:59:01.000Z | 2022-02-09T06:59:14.000Z | AlchemyInsights/micro-delays-or-throttling-in-exchange-online-powershell.md | isabella232/OfficeDocs-AlchemyInsights-pr.ru-RU | d76cee281de068f382e8f53f2917f5d7e1dd9bfa | [
"CC-BY-4.0",
"MIT"
] | 2 | 2019-10-09T20:25:46.000Z | 2021-10-09T11:33:34.000Z | ---
title: Микрозадержки или регулирование скорости в Exchange Online PowerShell
ms.author: pebaum
author: pebaum
manager: scotv
ms.audience: Admin
ms.topic: article
ms.service: o365-administration
ROBOTS: NOINDEX, NOFOLLOW
localization_priority: Priority
ms.collection: Adm_O365
ms.custom:
- "3500011"
- "5106"
ms.openlocfilehash: 2fab21f76f455815979ae162c1ce8246ad5c297e
ms.sourcegitcommit: ab75f66355116e995b3cb5505465b31989339e28
ms.translationtype: HT
ms.contentlocale: ru-RU
ms.lasthandoff: 08/13/2021
ms.locfileid: "58314713"
---
# <a name="micro-delays-or-throttling-in-exchange-online-powershell"></a>Микрозадержки или регулирование скорости в Exchange Online PowerShell
При запуске сценариев и командлетов в Exchange Online могут отображаться предупреждения "Применена микрозадержка" или возникать задержки. Вот несколько советов по решению этой проблемы.
- Запустите наше средство диагностики, чтобы сделать политику регулирования PowerShell на вашем клиенте менее жесткой. Это решает проблему в большинстве случаев.
- Если проблема не исчезнет, попробуйте использовать [модуль PowerShell Exchange Online v2](https://docs.microsoft.com/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2?view=exchange-ps&preserve-view=true): он включает командлеты на основе API REST, их производительность значительно выше. Это решение может быть оптимальным для множества часто используемых командлетов Get.
- Если нужно использовать командлеты, не входящие в состав модуля v2, см статью [Запуск командлетов PowerShell для большого количества пользователей в Office 365](https://techcommunity.microsoft.com/t5/exchange-team-blog/updated-running-powershell-cmdlets-for-large-numbers-of-users-in/ba-p/1000628#). В ней описываются обходные решения для ограничений регулирования PowerShell в Exchange Online.
| 63.724138 | 420 | 0.832792 | rus_Cyrl | 0.691306 |
d5770a074e8fd0a67fcd68e73cb5a3cb76aa9e79 | 151 | md | Markdown | src/etc/complete/README.md | Xvezda/dotfile | 27fb48521690a8894631d288047330736f918d53 | [
"MIT"
] | 11 | 2019-06-12T18:46:30.000Z | 2020-10-11T15:14:33.000Z | src/etc/complete/README.md | Xvezda/dotfile | 27fb48521690a8894631d288047330736f918d53 | [
"MIT"
] | 28 | 2018-09-19T20:06:42.000Z | 2021-04-06T11:50:47.000Z | src/etc/complete/README.md | Xvezda/dotfile | 27fb48521690a8894631d288047330736f918d53 | [
"MIT"
] | 3 | 2020-03-05T03:56:19.000Z | 2021-02-21T17:39:22.000Z | VIM Template script
===================
[DEPRECATED]
------------
This script is now replaced with [Ultisnips](https://github.com/SirVer/ultisnips).
| 18.875 | 82 | 0.609272 | yue_Hant | 0.59575 |
d5785d2d4ad15bf436abea929647337f6698b85c | 1,191 | md | Markdown | README.md | scholarsportal/sp_ask_transcript_review | 0b03eccbc9667d271cd1dd1935c1e9a600207a7d | [
"MIT"
] | 1 | 2022-01-23T22:39:31.000Z | 2022-01-23T22:39:31.000Z | README.md | scholarsportal/sp_ask_transcript_review | 0b03eccbc9667d271cd1dd1935c1e9a600207a7d | [
"MIT"
] | null | null | null | README.md | scholarsportal/sp_ask_transcript_review | 0b03eccbc9667d271cd1dd1935c1e9a600207a7d | [
"MIT"
] | null | null | null | Sp Ask Transcript Downloader
======================================================
- Download Transcript from LibraryH3lp
- Removing Operator and School name from the Metadata.
## Screenshots
<p float="left">
<img src="screenshots/example.png" width="100%"/>
</p>
<h3>Features</h3>
<ul>
<li>- removing operator username from Scholars portal' Ask Transcript and replacing it by **operator**</li>
<li>- 12:41PM **operator**@ca.libraryh3lp.com/yuxzl4a9vd69fj still looking</li>
<li>- removing school name from Scholars portal' Ask Transcript and replacing it by **system**</li>
<li>- 12:56PM **system**@chat.ca.libraryh3lp.com System message: guest navigated away from chat</li>
<li>Creating files containing 60 chats each</li>
</ul>
<h3>Operating System</h3>
OS X
Unix based distro
<h3>Isntallation</h3>
pip install -r requirements.txt
<h3>Usage</h3>
from review import generate_html_template_from_transcript, write_html_to_template
output = generate_html_template_from_transcript([list, of , chat_id])
filePath = "./templates/ask.html"
write_html_to_template(output, filePath)
<h3>Testing</h3>
python -m unittest tests.py
| 28.357143 | 111 | 0.688497 | eng_Latn | 0.527997 |
d57870b62da82af3c0712bfdc7d41a2a79d29229 | 1,510 | md | Markdown | docs/content/docs/integrations/swarm.md | jqueguiner/cds | b629b7e18108142440dcc06fafca420001384511 | [
"BSD-3-Clause"
] | 4,040 | 2016-10-11T08:46:07.000Z | 2022-03-31T10:59:41.000Z | docs/content/docs/integrations/swarm.md | jqueguiner/cds | b629b7e18108142440dcc06fafca420001384511 | [
"BSD-3-Clause"
] | 2,582 | 2016-10-12T12:14:21.000Z | 2022-03-31T16:46:07.000Z | docs/content/docs/integrations/swarm.md | jqueguiner/cds | b629b7e18108142440dcc06fafca420001384511 | [
"BSD-3-Clause"
] | 436 | 2016-10-11T08:46:16.000Z | 2022-03-21T09:08:44.000Z | ---
title: Docker Swarm
main_menu: true
card:
name: compute
---
The Docker Swarm integration have to be configured by CDS administrator.
This integration allows you to run the Swarm [Hatchery]({{<relref "/docs/components/hatchery/_index.md">}}) to start CDS Workers.
As an end-users, this integration allows:
- to use [Worker Models]({{<relref "/docs/concepts/worker-model/_index.md">}}) of type "Docker"
- to use Service Prerequisite on your [CDS Jobs]({{<relref "/docs/concepts/job.md">}}).
## Start Swarm hatchery
Generate a token:
```bash
$ cdsctl consumer new me \
--scopes=Hatchery,RunExecution,Service,WorkerModel \
--name="hatchery.swarm" \
--description="Consumer token for swarm hatchery" \
--groups="" \
--no-interactive
Builtin consumer successfully created, use the following token to sign in:
xxxxxxxx.xxxxxxx.4Bd9XJMIWrfe8Lwb-Au68TKUqflPorY2Fmcuw5vIoUs5gQyCLuxxxxxxxxxxxxxx
```
Edit the section `hatchery.swarm` in the [CDS Configuration]({{< relref "/hosting/configuration.md">}}) file.
The token have to be set on the key `hatchery.swarm.commonConfiguration.api.http.token`.
This hatchery use the standard Docker environment variables to connect to a Docker host.
Then start hatchery:
```bash
export DOCKER_HOST=tcp://xx.xx.xx.xx:2375
engine start hatchery:swarm --config config.toml
```
This hatchery will now start worker of model 'docker' on you Docker installation.
## Setup a worker model
See [Tutorial]({{< relref "/docs/tutorials/worker_model-docker/_index.md" >}})
| 30.2 | 129 | 0.750993 | eng_Latn | 0.791159 |
d578bb4b234966e4e7713fcd840210bc193790d6 | 37,258 | md | Markdown | UPGRADE.md | michaelonye/bootique | c736ab01e20c8ce29c50069f80007c659fccabf5 | [
"Apache-2.0"
] | null | null | null | UPGRADE.md | michaelonye/bootique | c736ab01e20c8ce29c50069f80007c659fccabf5 | [
"Apache-2.0"
] | null | null | null | UPGRADE.md | michaelonye/bootique | c736ab01e20c8ce29c50069f80007c659fccabf5 | [
"Apache-2.0"
] | null | null | null | <!--
Licensed to ObjectStyle LLC under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ObjectStyle LLC licenses
this file to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
# UPGRADE INSTRUCTIONS
## 2.0.B1
* [bootique #300](https://github.com/bootique/bootique/issues/300): The new API allows to register configuration-loading
extensions like this:
```java
BQCoreModule.extend(b).addConfigLoader(MyLoader.class);
```
This obsoletes a couple of existing mechanisms. If you relied on `ConfigurationSource` object or on
`BQCoreModule.extend(b).addPostConfig("..")` (introduced in 2.0.M1), they will no longer be available and should be
replaced with custom `JsonConfigurationLoader`.
* [bootique-metrics #41](https://github.com/bootique/bootique-metrics/issues/41): A few configuration keys were changed
for `heartbeat`. Rename the following config keys in YAML or properties:
* `heartbeat.initialDelayMs` to `heartbeat.initialDelay`
* `heartbeat.fixedDelayMs` to `heartbeat.fixedDelay`
* `heartbeat.healthCheckTimeoutMs` to `heartbeat.healthCheckTimeout`
While you are at it, you can change the values to human-readable "durations":
```yaml
# was:
# heartbeat:
# healthCheckTimeoutMs: 20000
# became:
heartbeat:
healthCheckTimeout: 20sec
```
* [bootique-jdbc #106](https://github.com/bootique/bootique-jdbc/issues/106): Delete with condition API got improved.
If you are using delete with condition anywhere in tests (`table.delete().and(..)` or `table.delete().or(..)`), you
will get a compilation error. Change those calls to `table.delete().where(..)` to fix it.
* [bootique-jdbc #107](https://github.com/bootique/bootique-jdbc/issues/107): Table API related to SELECT queries
got reworked. If you receive compilation errors in tests either because `Table.selectColumns` signature is different,
or `Table.get*` or `Table.select*` methods are missing, consider replacing your code with either the new select API
(`Table.selectColumns(..)`) or a matcher (`Table.get*` are an indicator that you likely need a matcher to compare
values in DB instead of selecting them in Java).
## 2.0.M1
* [bootique #269](https://github.com/bootique/bootique/issues/269) Upgrade from Guice DI to "bootique-di". That's the BIG one!
The core of Bootique - its dependency injection engine - was switched over from Google Guice to a faster, lighter
["bootique-di"](https://github.com/bootique/bootique-di). The two DI implementations are conceptiually rather close, so
there is a straightforward migration path. More details are provided in the
[DI Migration Guide](https://bootique.io/docs/latest/migrate-from-guice/).
* [bootique #271](https://github.com/bootique/bootique/issues/271): Bootique is now integrated with JUnit 5. A few notes:
* Use `@RegisterExtension` to annotate `BQTestFactory`. For class-scoped test factory use the new `BQTestClassFactory`,
also annotated with `@RegisterExtension`.
* JUnit 4 compatibility. You still have the option to use JUnit 4, and can take your time to
[migrate to 5](https://junit.org/junit5/docs/current/user-guide/#migrating-from-junit4). Note that JUnit 4 support
is now done via JUnit 5 "Vintage" engine and JUnit itself is a _compile_ dependency of "bootique-test" (it used to be
"_provided_"). So if you import "bootique-test", you can remove an explicit JUnit dependency, and can mix and match
4 and 5 style tests in your code.
* `BQDaemonTestFactory` is not available under 5, as it is fairly useless and doesn't bring any advantages over
`BQTestFactory`.
* [bootique #288](https://github.com/bootique/bootique/issues/288): `Bootique.module(BQModuleProvider)` and
`BQTestRuntimeBuilder.module(BQModuleProvider)` were renamed to `moduleProvider` to avoid arguments ambiguity. If you
get compilation errors for these methods, replace them with `moduleProvider(BQModuleProvider)`.
* [bootique-cayenne #68](https://github.com/bootique/bootique-cayenne/issues/68): `maps` configuration option is changed
from **list** to **map**. You need to upgrade your yml configs accordingly.
* [bootique-jersey #47](https://github.com/bootique/bootique-jersey/issues/47): An internal injection point
(a `Set<Package>` listing Java packages that contain Jersey components) is now using an extra annotation to avoid
polluting common DI namespace. In an unlikely event that your code explicitly injects a `Set<Package>` to get custom
Jersey components, you will need to annotate the injection point with `@JerseyResource`.
* [bootique-agrest #42](https://github.com/bootique/bootique-agrest/issues/42): Previously deprecated `bootique-linkrest`
integration with the legacy LinkRest framework is removed. If you are still using it, you should be able to switch to
the new well-supported incarnation of this framework called Agrest. On Bootique side, simply replace the import
of `bootique-linkrest` with `bootique-agrest`, and on LinkRest side follow the
[upgrade instructions](https://github.com/agrestio/agrest/blob/master/UPGRADE-NOTES.md#upgrading-to-30) back from
Agrest version 3.0.
* [bootique-job #82](https://github.com/bootique/bootique-job/issues/82): Previously deprecated trigger
millisecond-based configs properties got removed. Please check your configurations and replace them with duration-based
analogs (durations are string that contain units, e.g. "5ms", "6sec", etc.) :
* `scheduler.triggers.fixedRateMs` should become `scheduler.triggers.fixedRate`
* `scheduler.triggers.fixedDelayMs` should become `scheduler.triggers.fixedDelay`
* `scheduler.triggers.initialDelayMs` should become `scheduler.triggers.initialDelay`
To update your config, change it from something like:
```yaml
scheduler:
triggers:
- job: j1
trigger: t1
initialDelayMs: 10
fixedDelayMs: 10000
```
to something like this:
```yaml
scheduler:
triggers:
- job: j1
trigger: t1
initialDelay: 10ms
fixedDelay: 10sec
```
* [bootique-kafka #28](https://github.com/bootique/bootique-kafka/issues/28): Support for the legacy Kafka client v 0.8
is removed. A newer client should be used. See [https://github.com/bootique/bootique-kafka] for details.
* [bootique-jetty #95](https://github.com/bootique/bootique-jetty/issues/95): Default value for `maxThreads` property was
lowered from 1024 to 200. If you relied on this default value you should now set it explicitly in the app config.
* [bootique-jersey #48](https://github.com/bootique/bootique-jersey/issues/48): `bootique-jersey-client` is no longer
a "top-level" project and was merged to `bootique-jersey`. There's no code changes, but the module coordinates have changed.
Instead of `io.bootique.jersey.client:bootique-jersey-client` you will need to import `io.bootique.jersey:bootique-jersey-client`.
* [bootique-rabbitmq #1](https://github.com/bootique/bootique-rabbitmq/issues/1): `bootique-rabitmq-client` artifact
"group" changed from `io.bootique.rabbitmq.client` to `io.bootique.rabbitmq`. Adjust your build scripts accordingly.
* [bootique-rabbitmq #2](https://github.com/bootique/bootique-rabbitmq/issues/2): There was a deep configuration system
refactoring:
* `ChannelFactory` was moved to `io.bootique.rabbitmq.client` package. Adjust your imports accordingly.
* `ConnectionFactory` was renamed to `ChannelManager` and is no longer injectable. You will rarely need to access it
directly, but if you do, you can retrieve it from `ChannelFactory`
* `ChannelFactory` methods no longer require a `Connection` parameter. Pass the connection *name* instead. The old
methods are still around, but are deprecated.
* [bootique-swagger #18](https://github.com/bootique/bootique-swagger/issues/18): The default URL of the Swagger UI
has changed from "/swagger" to "/swagger-ui". You'll need to either start using the new URL, or change it via configuration
property `swaggerui.<label>.uiPath`.
* [bootique-swagger #21](https://github.com/bootique/bootique-swagger/issues/21): To support the same Swagger UI servlet
serving multiple models in one app ("multitenancy"), "swaggerui" configuration is now nested, consisting of zero or
more named configurations. To update your config, change it from something like:
```yaml
swaggerui:
specUrl: "https://example.org/spec1.yml"
```
to something like this:
```yaml
swaggerui:
default: # "default" is an arbitrary name. You can use your own
specUrl: "https://example.org/spec1.yml"
```
* [bootique-swagger #24](https://github.com/bootique/bootique-swagger/issues/24): `bootique-swagger` (Swagger backend)
was upgraded to support OpenAPI spec 3.0 (instead of the legacy Swagger 2.0). If you were using Swagger annotations,
you will need to migrate from "io.swagger:swagger-annotations" to "io.swagger.core.v3:swagger-annotations".
* [bootique-curator #17](https://github.com/bootique/bootique-curator/issues/17): With Curator dependency upgrade,
`bootique-curator` now supports Zookeeper 3.5 or newer.
## 1.1
* [bootique #266](https://github.com/bootique/bootique/issues/266): To improve Java 11 compatibility, Bootique core
was upgraded to the latest Guice v 4.2.2. This is more of an FYI. No action is needed from the users, unless you
are manually managing Guice versions in your app.
* [bootique-agrest #37](https://github.com/bootique/bootique-agrest/issues/37): While `bootique-agrest` didn't change,
the underlying Agrest framework introduced a few breaking changes between 3.1 and 3.2, that hopefully affect only a small subset of users:
* Response with overlapping relationship / attribute "includes" is `include` order dependent [#406](https://github.com/agrestio/agrest/issues/406)
* @QueryParameter types changed to Strings and Integers [#408](https://github.com/agrestio/agrest/issues/408) If you are not directly injecting `Include`, `Exclude` and friends (injecting `UriInfo` instead), are you are not affected.
See [Agrest upgrade instructions](https://github.com/agrestio/agrest/blob/master/UPGRADE-NOTES.md#upgrading-to-32) for more details.
* [bootique-linkmove #37](https://github.com/bootique/bootique-linkmove/issues/37): LinkMove library was upgraded to
v 2.7. While `bootique-linkmove` didn't change, the underlying LinkMove framework introduced a few breaking changes
between 2.6 and 2.7. Namely switching of internal ETL data representation to DFLib DataFrame. If your get any
compilation errors as a result, see [LinkMove upgrade instructions](https://github.com/nhl/link-move/blob/master/UPGRADE-NOTES.md)
for details of the 2.7 changes.
## 1.0
Fully compatible with 1.0.RC1
## 1.0.RC1
* [bootique-agrest #35](https://github.com/bootique/bootique-agrest/issues/35): Group of `bootique-linkrest` artifact
changed from `io.bootique.linkrest` to `io.bootique.agrest`.
* [bootique #252](https://github.com/bootique/bootique/issues/252): Method `defaultValue()` in OptionMetadata builder
changed to `valueOptionalWithDefault()`
* [bootique #251](https://github.com/bootique/bootique/issues/251): Method `addConfigOnOption(String optionName, String configResourceId)`
in `BQCoreModuleExtender` renamed to `mapConfigResource`
* [bootique #249](https://github.com/bootique/bootique/issues/249): Confusing methods
`addOption(String configPath, String defaultValue, String name)` and `addOption(String configPath, String name)`
in `BQCoreModuleExtender` are replaced with new one `mapConfigPath(String optionName, String configPath)`
that has much clearer signature. **Note** that option that will be mapped to config path should be added separately.
* [bootique #188](https://github.com/bootique/bootique/issues/188): Guice was upgraded from 4.0 to
4.2.0 for better support of the latest versions of Java. This changes the version of Guava lib to
`23.6-android` and that Guava brings with it a whole set of other libraries (see the screenshot
[here](https://groups.google.com/forum/#!topic/bootique-user/elLjQXaK-40). If your code depends
on Guava elsewhere, be aware of this change. Also (and this is very unfortunate) this upgrade
increased the dependency footprint by ~500K.
* [bootique #214](https://github.com/bootique/bootique/issues/214): All APIs previously deprecated are
removed from Bootique core. Please recompile your code and fix any failures (refer to 0.25 JavaDocs for
suggested API replacements).
The most notable change though, that you will not notice just by recompiling, is that Bootique now
completely ignores `BQ_` environment variables that used to set config properties. Please inspect
your app launch environment (be it IDE or server/Docker/cloud) to see if you still rely on such variables.
Switch to explicitly declared variables instead:
```java
// FWIW, you can use your old BQ_ var name here if you feel like it.
// Just need to bind it explicitly.
BQCoreModule.extend(bidner).declareVar("a.b.c", "MY_VAR");
```
* [bootique-jetty #75](https://github.com/bootique/bootique-jetty/issues/75): As a part of deprecated
API removal `bootique-jetty-test` module was removed. It is enough to use
`bootique-test` as described in the [0.25 blog](https://blog.bootique.io/the-state-of-bootique-early-2018-part-1-ed6806d9c99a)
("Test API Improvements" section).
* [bootique-undertow #13](https://github.com/bootique/bootique-undertow/issues/13): As a part of deprecated
API removal `bootique-undertow-test` module was removed. It is enough to use
`bootique-test` as described in the [0.25 blog](https://blog.bootique.io/the-state-of-bootique-early-2018-part-1-ed6806d9c99a)
("Test API Improvements" section).
* [bootique-jetty #77](https://github.com/bootique/bootique-jetty/issues/77): Jetty health checked thresholds structure has
changed as shown in the following diff:
```yaml
jetty:
health:
- queuedRequestsThreshold: "2 3"
- poolUtilizationThreshold: "0.6 0.9"
+ queuedRequestsThresholds:
+ warning: 2
+ critical: 3
+ poolUtilizationThresholds:
+ warning: 60%
+ critical: 90%
```
* [bootique-jdbc #81](https://github.com/bootique/bootique-jdbc/issues/81): Hikari health check threashold structure has changed
as shown in the following diff. Now you can specify warning and critical ranges and use human-readable durations:
```yaml
jdbc:
mydb:
health:
- connectivityCheckTimeout: 250
- expected99thPercentile: 10
+ connectivity:
+ critical: 250ms
+ connection99Percent:
+ warning: 10ms
+ critical: 500ms
```
* [bootique-jdbc #82](https://github.com/bootique/bootique-jdbc/issues/82): `bootique-jdbc-instrumented` module was removed.
There are healthchecks specific to Tomcat and Hikari pools, so there's no need to have a generic set of healthchecks that interferes
with them. You will need to remove references to `bootique-jdbc-instrumented` from your build scripts and replace them with `bootique-jdbc-tomcat-instrumented` (that actually contains healtchecks ported from the removed module) or `bootique-jdbc-hikaricp-instrumented` (that has its own set of health checks).
* [bootique-job #64](https://github.com/bootique/bootique-job/pull/64): If you used Zookeeper for job locking, configuration is done differently
now. You will need to remove `scheduler.clusteredLocks: true` from YAML, and instead add a dependency on `io.bootique.job:bootique-job-zookeeper`
(or the new `io.bootique.job:bootique-job-consul`). Either will enable lock clustering, but with its own mechanism.
* [bootique-job #66](https://github.com/bootique/bootique-job/pull/66): Trigger configurations switched from numeric milliseconds to
"durations". While the configuration is backwards-compatible, we'd encourage you to review it and replace config keys "fixedDelayMs",
"fixedRateMs", "initialDelayMs" with "fixedDelay", "fixedRate", "initialDelay" respectively. While you are at it, you may switch to
more user-friendly forms, such as "3s" or "5min".
* [bootique-kafka #19](https://github.com/bootique/bootique-kafka/issues/19): `bootique-kafka-client` repository was renamed to `bootique-kafka`.
If you are using `bootique-kafka-client`, you will need change the Maven "groupId" to `io.bootique.kafka` from `io.bootique.kafka.client`.
* [bootique-kafka #21](https://github.com/bootique/bootique-kafka/issues/21): "kafkaclient.producer.lingerMs" property got renamed to
"kafkaclient.producer.linger" and was changed to a Duration type. Please change all references to `kafkaclient.producer.lingerMs`
in your config to be `kafkaclient.producer.linger`. Note that once you do it, you can use any supported duration format e.g. "1s".
Also note that the default value for this property was changed from 1 to 0 to match the Kafka default.
* [bootique-kafka #23](https://github.com/bootique/bootique-kafka/issues/23): Per this task, a new user-friendly Consumer API was
created. Breaking changes:
* Consumers can no longer be obtained via `KafkaClientFactory`. Instead inject `KafkaConsumerFactory` and use its Consumer builder methods.
* Producers can no longer be obtained via `KafkaClientFactory`. Instead inject `KafkaproducerFactory` and use its Producer builder methods.
* `kafkaclient.consumer.autoCommitIntervalMs` config is renamed to
`kafkaclient.consumer.autoCommitInterval` and is now a duration (so you can use readable values like "1ms"). Same goes
for `kafkaclient.consumer.sessionTimeoutMs` that got renamed to `kafkaclient.consumer.sessionTimeout`.
* [bootique-metrics #30](https://github.com/bootique/bootique-metrics/issues/30): There was a massive renaming of module metrics to
follow a single naming convention. Follow the link to [bootique-metrics #30](https://github.com/bootique/bootique-metrics/issues/30)
to see the old vs new names across all affected modules.
* [bootique-metrics #31](https://github.com/bootique/bootique-metrics/issues/31): Similarly to metrics, health checks got similarly renamed to
follow the same naming convention. Follow the link to [bootique-metrics #31](https://github.com/bootique/bootique-metrics/issues/31)
to see the old vs new names across all affected modules.
* [bootique-agrest #34](https://github.com/bootique/bootique-agrest/issues/34) : LinkRest was changed to Agrest
and bootique-agrest. Bootique-linkrest now deprecated. Please use bootique-agrest dependency.
## 0.25
* [bootique-jdbc #48](https://github.com/bootique/bootique-jdbc/issues/48): This affects all users of `bootique-jdbc`,
including indirect users, such as those relying on `bootique-cayenne`, `bootique-linkrest`, `bootique-linkmove`,
`bootique-jooq`, `bootique-liquibase`, etc. Due to `bootique-jdbc` module becoming "abstract", if you have a JDBC app, on startup you will
see an error like this:
```
No concrete 'bootique-jdbc' implementations found. You will need to add one
(such as 'bootique-jdbc-tomcat', etc.) as an application dependency.
```
To fix the problem, you will need to do exactly as suggested, i.e. add the following dependency to your `pom.xml`:
```xml
<dependency>
<groupId>io.bootique.jdbc</groupId>
<artifactId>bootique-jdbc-tomcat</artifactId>
<scope>compile</scope>
</dependency>
```
The original `bootique-jdbc` is now a transitive dependency of the new `bootique-jdbc-tomcat`, so you may remove
explicit `bootique-jdbc` import (or leave it, as no harm is being done by keeping it around). If you are using
`bootique-jdbc-instrumented` (i.e. JDBC with metrics), import a different dependency:
```xml
<dependency>
<groupId>io.bootique.jdbc</groupId>
<artifactId>bootique-jdbc-tomcat-instrumented</artifactId>
<scope>compile</scope>
</dependency>
```
* [bootique-jdbc #66](https://github.com/bootique/bootique-jdbc/issues/66): DataSource connection health checks were
renamed to uniquely identify their origin and purpose. E.g. a health check that may have previously been called
`mydb` after the DataSource name, will now be called `bq.jdbc.mydb.canConnect`. If any of your code or the monitoring
system depended on the certain name format, you will need to update it accordingly.
* [bootique-metrics #20](https://github.com/bootique/bootique-metrics/issues/20): Health check module was separated
from the metric module. If you used healthcheck API in your code and are getting compilation errors now, you will need
to add an extra dependency:
```xml
<dependency>
<groupId>io.bootique.metrics</groupId>
<artifactId>bootique-metrics-healthchecks</artifactId>
<scope>compile</scope>
</dependency>
```
Additionally if you called `MetricsModule.extend(binder)`, replace it with `HealthCheckModule.extend(binder)`.
* [bootique-jetty #69](https://github.com/bootique/bootique-jetty/issues/69): There was a slight change in health check
servlet output format. In case of errors the format now includes specific status (CRITICAL, WARNING, UNKNOWN). E.g.:
```yaml
// old format
! h3: ERROR - I am not healthy
// new format
! h3: WARNING - I am not healthy
! h3: CRITICAL - I am not healthy
```
* [bootique-jetty #70](https://github.com/bootique/bootique-jetty/issues/70): With introduction of explicit per-connector
`acceptorThreads` and `connectorThreads` configuration properties, the defaults used by the server for acceptors and
selectors have changed from 0.5 acceptor and 1 selector thread(s) per CPU core to 0.125 acceptor and 0.5 selector
thread(s) per CPU core. In the unlikely event that you need the old values back, you can configure them using the
new properties. E.g.:
```yaml
jetty:
connectors:
- acceptorThreads: 4
selectorThreads: 8
```
* [bootique-jetty #71](https://github.com/bootique/bootique-jetty/issues/71): We decided to clarify the meaning of the
Jetty thread pool metrics. The old "utilization" metric was not very useful as it compared used threads against the
current thread pool size. But since the pool can grow/shrink at any moment, it didn't tell anything about the state of the
app. So its meaning is now replaced to be the same as the old "utilization-max" (i.e. a ratio of used threads to the
max possible threads in the pool). "utilization-max" was deprecated.
If you used "utilization" metric for anything in your monitoring system, etc., make sure to adjust for the new
meaning.
* [bootique-jersey-client #29](https://github.com/bootique/bootique-jersey-client/issues/29): `followRedirects` default value
has changed from "false" to "true". If you implicitly relied on `jerseyclient.followRedirects` default to be "false", you will need to reconfigure your app to set it to false explicitly:
```yaml
jerseyclient:
followRedirects: false
```
## 0.24
* [bootique #180](https://github.com/bootique/bootique/issues/180): The ability to explicitly declare a BQ_* var was removed.
In other words this API is not longer available:
```java
// this used to declare a variable BQ_PROP_XYZ
BQCoreModule.extend(binder).declareVar("prop.xyz")
```
You have two choices for upgrading your code: either (1) simply remove this line of code (`BQ_PROP_XYZ` will keep working,
just won't show in help), or (2 - better) assign this variable an app-specific name. E.g.
`BQCoreModule.extend(binder).declareVar("prop.xyz", "MY_VAR")`.
* [bootique-jdbc #39](https://github.com/bootique/bootique-jdbc/issues/39): If you had unit tests that are using `Table.insertFromCsv(..)` and the `.csv` files contain timestamps, replace the space between date and time portions with "T" symbol. The new format is proper ISO-8601.
## 0.23
* [bootique #141](https://github.com/bootique/bootique/issues/141): If you've ever implemented your own "main" method
instead of relying on the one from `io.bootique.Bootique`, you may want to replace the call to the deprecated `Bootique.run()`
with `Bootique.exec().exit()`. Notice how the new API allows to insert custom code after Bootique finish, but before the
app exit.
* [bootique #142](https://github.com/bootique/bootique/issues/142): This issue introduces API-breaking changes to the
integration testing API. Instead of `BQTestRuntime` and `BQDaemonTestRuntime`, test factories now produce simply
`BQRuntime`, that helps to focus on the object being tested instead of test wrappers. Upgrade instructions:
1. `BQTestRuntime` and `BQDaemonTestRuntime` are gone, so replace references to them with just `BQRuntime`.
2. A common call to `testRuntime.getRuntime().getInstance(..)` should now be shortened to `testRuntime.getInstance(..)`.
3. If you need to get an outcome of a background task execution, instead of `daemonTestRuntime.getOutcome()` you need
to call `daemonTestFactory.getOutcome(runtime)` ("daemonTestFactory" is a `BQDaemonTestFactory` or subclasses like
`JettyTestFactory`, that are the `@Rule`'s in your test).
4. Use factory API (the same approach as in the previous point) if you need to manually start/stop the daemon runtime:
`daemonTestFactory.start(runtime)`, `daemonTestFactory.stop(runtime)`.
5. If you need to capture STDOUT or STDERR of a specific BQRuntime run, use the new `TestIO` class that can capture
this data. It additionally allows to suppress trace logging, making your test console much less verbose than before.
E.g.:
```java
TestIO io = TestIO.noTrace();
testFactory.app("-x")
.bootLogger(io.getBootLogger())
.createRuntime()
.run();
assertEquals("--out--", io.getStdout());
assertEquals("--err--", io.getStderr());
```
Other modules that have been affected by this change are
[bootique-jetty-test](https://github.com/bootique/bootique-jetty/issues/59),
[bootique-undertow-test](https://github.com/bootique/bootique-undertow/issues/3),
[bootique-jdbc-test](https://github.com/bootique/bootique-jdbc/issues/32),
[bootique-cayenne-test](https://github.com/bootique/bootique-cayenne/issues/39).
* [bootique-liquibase #16](https://github.com/bootique/bootique-liquibase/issues/16): Names of Liquibase module
commands have been changed by adding prefix "lb" to distinguish them from commands of others modules.
Old options:
--changelog-sync
Mark all changes as executed in the database.
--changelog-sync-sql
Writes SQL to mark all changes as executed in the database to STDOUT.
--clear-check-sums
Clears all checksums in the current changelog, so they will be
recalculated next update.
-u, --update
Updates DB with available migrations
-v, --validate
Checks the changelog for errors.
New options:
--lb-changelog-sync
Mark all changes as executed in the database.
--lb-changelog-sync-sql
Writes SQL to mark all changes as executed in the database to STDOUT.
--lb-clear-check-sums
Clears all checksums in the current changelog, so they will be
recalculated next update.
-u, --lb-update
Updates DB with available migrations
-v, --lb-validate
Checks the changelog for errors.
Short names has been preserved for partial backwards compatibility.
## 0.22
* [bootique-cayenne #36](https://github.com/bootique/bootique-cayenne/issues/36): If you used `bootique-cayenne-jcache`,
note that a big chunk of its functionality is now handled by Cayenne itself. From the upgrade perspective only one thing is affected:
if you ever used custom `InvalidationHandler`, you will need to switch that to `org.apache.cayenne.lifecycle.cache.InvalidationHandler`
that has a slightly different method signature (due to the need to keep Java 7 compatibility in Cayenne 4.0).
## 0.21
* [bootique #105](https://github.com/bootique/bootique/issues/105): The new default style for multi-word command classes
that are spelled in camel-case will result in the name parts separated with dash, while previously
we'd use no separators. E.g. `MySpecialCommand.java` will result in command name being "--myspecial" in 0.20,
and "--my-special" in 0.21. This affects you if you've written custom command classes with multi-word names.
You can manually override public command names in metadata to return to the old style (see
[CommandWithMetadata](https://github.com/bootique/bootique/blob/master/bootique/src/main/java/io/bootique/command/CommandWithMetadata.java)) or embrace the new naming scheme.
* [bootique #112](https://github.com/bootique/bootique/issues/112): The implementation of this feature has a few
(intentional) side-effects: (1) joptsimple library was upgraded to 5.0.6, (2) CLI option abbreviations are no longer
supported. You may have not known this, but before 0.21, you could use partial option names (e.g. "--he" for help). Not
anymore. Now either a short option or a long option with full name must be used (i.e. "-h" or "--help" in case of the
help command).
* [bootique #113](https://github.com/bootique/bootique/issues/113): Classes in ```io.bootique.application``` package
were moved under ```io.bootique.meta.application``` in an effort to centralize Bootique metadata facilities. If you
referenced them in your code, you will need to fix the imports and recompile. This will primarily affect custom Commands.
* [bootique-jdbc #6](https://github.com/bootique/bootique-jdbc/issues/6): bootique-jdbc uses Tomcat DataSource that has
a few dozens of config properties. As we migrated JDBC configuration from a map to a
[specific class](https://github.com/bootique/bootique-jdbc/blob/master/bootique-jdbc/src/main/java/io/bootique/jdbc/TomcatDataSourceFactory.java),
we dropped support for certain noop properties there were supported but ignored in the previous configuration. If you
get configuration errors, review your configs and remove those properties. Additionally the following properties
are treated differently than before:
- ```connectionProperties``` property is not supported (as it is unclear why it may be useful)
- ```jmxEnabled``` default is changed from true to false.
- ```object_name``` is renamed to ```jmxObjectName```.
* [bootique-liquibase #4](https://github.com/bootique/bootique-liquibase/issues/4): 'liquibase.changeLog' YAML config
property is deprecated, but still supported. The new alternative is 'changeLogs' collection. When migrating to
'changeLogs', ensure that you rewrite the paths in Bootique YAML files as well as in Liquibase XML/YAML change logs to
follow Bootique ResourceFactory approach. Specifically, if the resource is expected to be on classpath, it requires
"classpath:" prefix. Otherwise it will be treated as a file path.
* [bootique-logback #26](https://github.com/bootique/bootique-logback/issues/26): 'log.level' and
'log.loggers.<xyz>.level' must be specified in lowercase. I.e. ```level: debug``` instead of ```level: DEBUG```.
Uppercase values will now cause an exception.
* [bootique-job #15](https://github.com/bootique/bootique-job/issues/15): 'scheduler.jobPropertiesPrefix' property is no longer supported in configuration and needs to be removed from the config files, etc. Parameters for individual jobs should now be specified under 'params' key (previously they were specified under the job's name).
```yaml
# prior to 0.21
jobs:
myjob:
param1: value1
# starting with 0.21
jobs:
myjob:
params:
param1: value1
```
## 0.20
* [bootique #92](https://github.com/bootique/bootique/issues/92): We created a new application metadata package
at ```io.bootique.application```. The existing metadata objects where moved to this package from different places.
Specifically ```io.bootique.command.CommandMetadata``` was moved and ```io.bootique.cli.CliOption``` was moved and
renamed to ```OptionMetadata```. **This is a breaking change.** You will need to use module versions aligned with
0.20 Bootique BOM and fix any imports in your own code (especially in custom Commands).
* [bootique #97](https://github.com/bootique/bootique/issues/97): We simplifed integration test API. It now looks pretty much the same as a regular ```main(String[])``` method. There's no longer a need to use "configurator" lambda to configure test runtime. Instead you'd call Bootique-like methods on the test factory. When upgrading your tests you will need to change calls on ```BQTestFactory``` and ```BQDaemonTestFactory``` from ```newRuntime()``` to ```app(args)```. Terminating builder methods no longer take args (it is passed in the "app" method at the start of the chain). Pay attention to deprecating warnings and use your IDE for available APIs of the test factories.
* [bootique-jetty #52](https://github.com/bootique/bootique-jetty/issues/52): ```JettyTestFactory``` received the same API upgrades as ```BQTestFactory``` and ```BQDaemonTestFactory``` as described above. The upgrade instructions are similar.
## 0.19
The biggest change in 0.19 is combining modules under ```com.nhl.bootique``` and ```io.bootique``` into a single
namespace - ```io.bootique```. To upgrade, you will need to change module group names in your POM, Java package
names in imports, and the name of service provider files in your modules. Details are provided below:
* If you used Bootique-provided parent pom, in your ```pom.xml``` change the parent declaration:
```xml
<parent>
<groupId>io.bootique.parent</groupId>
<artifactId>bootique-parent</artifactId>
<version>0.12</version>
</parent>
```
* Change all group names of Maven artifacts in your ```pom.xml``` from ```com.nhl.bootique.*``` to ```io.bootique.*```.
Module names are preserved.
* Use ```io.bootique``` BOM, remove ```com.nhl.bootique``` BOM:
```xml
<dependency>
<groupId>io.bootique.bom</groupId>
<artifactId>bootique-bom</artifactId>
<version>0.19</version>
<type>pom</type>
<scope>import</scope>
</dependency>
```
Note that there was a brief period of time (0.18) when required both BOMs to be imported. Not anymore. ```io.bootique```
one is sufficient now.
* Look for Java compilation errors in your IDE, and change ```com.nhl.bootique.*``` import statements to ```io.bootique.*```.
* If you've written any auto-loadable modules, you will have ```META-INF/services/com.nhl.bootique.BQModuleProvider```
files sitting somewhere in your source.Rename these files to ```META-INF/services/io.bootique.BQModuleProvider```.
* Similarly if you've written any polymorphic config extensions, your sources will have ```META-INF/services/com.nhl.bootique.config.PolymorphicConfiguration```
files somewhere. Rename these files to ```META-INF/services/io.bootique.config.PolymorphicConfiguration```.
## 0.18
* [bootique-cayenne #12](https://github.com/nhl/bootique-cayenne/issues/12) : ```CayenneModule.builder()``` is removed.
Instead of using the builder, use YAML (or another form of) configuration. If you need a project-less Cayenne stack,
simply do not reference any Cayenne projects (and make sure "cayenne-project.xml" is not on classpath).
* [bootique-curator #4](https://github.com/nhl/bootique-curator/issues/4) : ```bootique-zookeeper``` was renamed to
```bootique-curator```, so the dependency import and Java package names need to be changed accordingly.
## 0.17
* [bootique #62](https://github.com/nhl/bootique/issues/62) : To fully take advantage of the default main class, make
sure you upgrade ```com.nhl.bootique.parent:bootique-parent``` to version 0.11.
## 0.12.2
* [bootique-cayenne #9](https://github.com/nhl/bootique-cayenne/issues/9) : CayenneModule ```noConfig``` and
```configName``` methods are moved into a builder, and constructor is made private. Now to set cayenne-...xml via
API use something like this:
```java
CayenneModule.builder()./* configure module */.build();
```
* [bootique-jdbc #4](https://github.com/nhl/bootique-jdbc/issues/4) : Instrumentation is removed from
```bootique-jdbc``` and into a separate ```bootique-jdbc-instrumented``` module.If you relied on the
DataSource metrics, change your import to the new Module.
## 0.12:
* Command API has been redone. If you have modules or apps that implement Commands,
you will need to update those. Sample commands can be found in our modules, e.g.
[bootique-jobs](https://github.com/nhl/bootique-job/tree/master/src/main/java/com/nhl/bootique/job/command).
* @Args annotation was moved to "com.nhl.bootique.annotation" package from "com.nhl.bootique.jopt".
Update your imports.
* Now only one command can match command line options. THis was true before, but wasn't enforced.
So you may see certain command line configs failing with errors, where they appeared to work before
by pure chance.
* BQBinder is deprecated. From within your Module use static methods on BQCoreModule to contribute
Module-specific commands, properties, CLI options.
| 55.775449 | 679 | 0.755516 | eng_Latn | 0.964333 |
d5795fba2d7e9fd2e61cd06dd019b1e0c0f37aa2 | 86 | md | Markdown | cards/readme.md | moshix/Art1 | f7c7248bb250784d0f503862466899809ab241e7 | [
"MIT"
] | 19 | 2021-01-24T20:11:50.000Z | 2022-01-25T22:04:45.000Z | cards/readme.md | moshix/Art1 | f7c7248bb250784d0f503862466899809ab241e7 | [
"MIT"
] | 2 | 2021-02-10T13:57:25.000Z | 2022-01-21T18:49:51.000Z | cards/readme.md | moshix/Art1 | f7c7248bb250784d0f503862466899809ab241e7 | [
"MIT"
] | 2 | 2021-04-07T21:19:30.000Z | 2021-07-05T08:14:56.000Z | A few Art1 programs. The test program referred to in Williams' notes is ``howto.25``.
| 43 | 85 | 0.744186 | eng_Latn | 0.998995 |
d5798c297308b79483a0deb49b24bcc91d3ae7c1 | 77 | md | Markdown | rgb2bwr/README.md | Denaun/inspiro-frame | f61b3d4900fe7e24f3d65f1182af78e4aaaacadf | [
"MIT"
] | 1 | 2021-03-08T09:03:10.000Z | 2021-03-08T09:03:10.000Z | rgb2bwr/README.md | Denaun/inspiro-frame | f61b3d4900fe7e24f3d65f1182af78e4aaaacadf | [
"MIT"
] | null | null | null | rgb2bwr/README.md | Denaun/inspiro-frame | f61b3d4900fe7e24f3d65f1182af78e4aaaacadf | [
"MIT"
] | null | null | null | # RGB2BWR
## A library to convert from RGB to 3-color (Black, White, Red). | 25.666667 | 64 | 0.675325 | eng_Latn | 0.669361 |
d579f26e9567671bd420974057c96b6cf3268646 | 910 | md | Markdown | _posts/2021-05-07-fast-to-reopen.md | Snoqualmie-Valley-Citizens-for-Schools/svcs.github.io | e357658196ed4921332f8e311d4f53255124badb | [
"CC0-1.0"
] | null | null | null | _posts/2021-05-07-fast-to-reopen.md | Snoqualmie-Valley-Citizens-for-Schools/svcs.github.io | e357658196ed4921332f8e311d4f53255124badb | [
"CC0-1.0"
] | null | null | null | _posts/2021-05-07-fast-to-reopen.md | Snoqualmie-Valley-Citizens-for-Schools/svcs.github.io | e357658196ed4921332f8e311d4f53255124badb | [
"CC0-1.0"
] | null | null | null | ---
layout: post
title: SVSD one of fastest King County districts to reopen
date: 2021-05-07
image: /assets/reopen-2021-05-07.jpg
tags:
- covid-19
author: Chris Alef
---
Snoqualmie Valley School District (SVSD) remains one of the fastest school districts to return to in-person attendance amongst the 18 King County school districts.
Thank you to everybody at the SVSD for working hard and quickly to ensure a safe reopening, while continuing to provide options for students that choose not to attend in person.
For all of the reopening data, visit the [Washington Office of Superintendent of Public Instruction (OSPI) website](https://www.k12.wa.us/about-ospi/press-releases/novel-coronavirus-covid-19-guidance-resources/school-reopening-data).
| 47.894737 | 233 | 0.79011 | eng_Latn | 0.988173 |
d579f93b5dc3062d38d6303b8f58534dd76b419d | 312 | md | Markdown | docs/tutorials.md | obniz/pxt-obniz | 6fcded6e3fc1dbccd52c7da3f5dead5afa33b96a | [
"MIT"
] | null | null | null | docs/tutorials.md | obniz/pxt-obniz | 6fcded6e3fc1dbccd52c7da3f5dead5afa33b96a | [
"MIT"
] | null | null | null | docs/tutorials.md | obniz/pxt-obniz | 6fcded6e3fc1dbccd52c7da3f5dead5afa33b96a | [
"MIT"
] | null | null | null | # Examples
Here are some fun programs for your @boardname@!
## Fun stuff
```codecard
[{
"name": "Square",
"description": "Move in a square",
"url":"/examples/square",
"cardType": "example"
}, {
"name": "Square 2",
"description": "TBDd",
"url": "/examples/square2",
"cardType": "example"
}]
``` | 16.421053 | 48 | 0.599359 | eng_Latn | 0.837634 |
d57a059460e4cbb74b0565f6d5d6b13436403829 | 3,758 | md | Markdown | ce/field-service/field-service-integration-overview.md | MicrosoftDocs/dynamics-365-customer-engagement | 7bae2e96942e0e1e79c8ecbef7d0bd8c14c833d9 | [
"CC-BY-4.0",
"MIT"
] | 194 | 2018-04-02T15:18:06.000Z | 2022-03-24T19:55:48.000Z | ce/field-service/field-service-integration-overview.md | WilliamH0010009/dynamics-365-customer-engagement | a741b73bce79a60aa367f80b666670b2d9e63013 | [
"CC-BY-4.0",
"MIT"
] | 2,219 | 2018-04-12T06:42:32.000Z | 2022-03-31T21:52:26.000Z | ce/field-service/field-service-integration-overview.md | WilliamH0010009/dynamics-365-customer-engagement | a741b73bce79a60aa367f80b666670b2d9e63013 | [
"CC-BY-4.0",
"MIT"
] | 406 | 2018-03-30T19:22:39.000Z | 2022-03-28T19:14:42.000Z | ---
title: "Overview of Dynamics 365 Field Service integrations | MicrosoftDocs"
description: Learn about the various ways to integrate Dynamics 365 Field Service with other business apps.
ms.date: 10/04/2021
ms.reviewer: krbjoran
ms.service: dynamics-365-field-service
ms.custom: intro-internal
ms.topic: article
applies_to:
- "Dynamics 365 (online)"
- "Dynamics 365 Version 9.x"
author: FieldServiceDave
ms.author: daclar
manager: shellyha
search.app:
- D365CE
- D365FS
---
# Overview of Field Service integrations
Microsoft Dynamics 365 Field Service integrates with various business apps to streamline your field service data and operations.
## Integrate with Dynamics 365 Supply Chain Management
While Dynamics 365 Field Service includes basic inventory capabilities for managing frontline worker truck stock, tracking asset service history, requesting purchase orders, and documenting returns; many field service organizations still integrate Field Service with their enterprise resource planning (ERP) systems. Organizations using the Microsoft Dynamics 365 stack will find it easy to integrate Dynamics 365 Field Service and Dynamics 365 Supply Chain Management systems. By leveraging Microsoft Dataverse (formerly Common Data Service), you can set up a synchronous two-way integration. For more information, see the article: [Integrate Dynamics 365 Field Service and Supply Chain Management](supply-chain-field-service-integration.md).
## Integrate with Dynamics 365 Remote Assist
If your organization is using Dynamics 365 Remote Assist, frontline workers can trigger a mixed reality video call from the Field Service mobile app or their HoloLens. This connects the frontline worker with a remote collaborator who can share their expertise and ultimately increase the chances of fixing the issue on the first trip. For more information, see the article: [collaborate in mixed reality with Field Service, Dynamics 365 Remote Assist](remote-assist-hololens.md).
## Integrate with Dynamics 365 Guides
Integration with Dynamics 365 Guides lets Field Service customers attach mixed reality guides to Field Service tasks, allowing frontline workers to launch the Dynamics 365 Guides HoloLens app to view the assigned guide and get their work done. For more information, see the article: [Integrate Field Service with Dynamics 365 Guides](mixed-reality-guides-integration.md).
## Integrate with Microsoft Teams
Integrate with Microsoft Teams to chat with team members in the context of work orders. Teams integration makes it easy to find answers and fix issues the first time. It also makes it easy to understand which team members may have previously worked on a work order.
After enabling the integration (currently in public preview), open a Teams panel from the work order form in Dynamics 365 and initiate chats with other team members. For more information, see the articles: [Collaborate on work orders with Microsoft Teams](field-service-teams-collaboration.md) and [Microsoft Teams integration with customer engagement apps in Dynamics 365](/dynamics365/teams-integration/teams-integration).
## Integrate with SAP
Integrate Dynamics 365 Field Service with SAP C-4Hana and SAP S-4Hana to connect your work order scheduling system to your enterprise resource planning (ERP) system. Microsoft offers guidance for integrating Field Service with the SAP Planned Maintenance and SAP Industry-Specific Utility (IS-U) modules. Integration is done by connecting SAP to the Dataverse (formerly Common Data Service), which Field Service is built on, along with other Dynamics 365 modules. For more information, see the article: [Integrate Dynamics 365 Field Service and Supply Chain Management](field-service-sap-integration.md).
| 65.929825 | 743 | 0.813731 | eng_Latn | 0.986583 |
d57a67f55db391264717b1ec4b13b358529fd00e | 1,738 | md | Markdown | Language/Concepts/Getting-Started/working-across-applications.md | italicize/VBA-Docs | 8d12d72a1e3e9e32f31b87be3a3f9e18e411c1b0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | Language/Concepts/Getting-Started/working-across-applications.md | italicize/VBA-Docs | 8d12d72a1e3e9e32f31b87be3a3f9e18e411c1b0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | Language/Concepts/Getting-Started/working-across-applications.md | italicize/VBA-Docs | 8d12d72a1e3e9e32f31b87be3a3f9e18e411c1b0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Working Across Applications
keywords: vbcn6.chm1012581
f1_keywords:
- vbcn6.chm1012581
ms.prod: office
ms.assetid: 46d31003-fdfb-04d3-6143-e286d91a46a8
ms.date: 06/08/2017
---
# Working Across Applications
Visual Basic can create new [objects](../../Glossary/vbe-glossary.md#object) and retrieve existing objects from many Microsoft applications. Other applications may also provide objects that you can create using Visual Basic. See the application's documentation for more information.
To create an new object or get an existing object from another application, use the **CreateObject** function or **GetObject** function:
```vb
' Start Microsoft Excel and create a new Worksheet object.
Set ExcelWorksheet = CreateObject("Excel.Sheet")
' Start Microsoft Excel and open an existing Worksheet object.
Set ExcelWorksheet = GetObject("SHEET1.XLS")
' Start Microsoft Word.
Set WordBasic = CreateObject("Word.Basic")
```
Most applications provide an **Exit** or **Quit** method that closes the application whether or not it is visible. For more information on the objects, methods, and properties an application provides, see the application's documentation.
Some applications allow you to use the **New**[keyword](../../Glossary/vbe-glossary.md#keyword) to create an object of any class that exists in its[type library](../../Glossary/vbe-glossary.md#type-library). For example:
```vb
Dim X As New Field
```
In this case, is an example of a [class](../../Glossary/vbe-glossary.md#class) in the data access type library. A new instance of a **Field** object is created using this syntax. Refer to the application's documentation for information about which object classes can be created in this way.
| 39.5 | 290 | 0.764097 | eng_Latn | 0.97167 |
d57abda3f906a330c1ecf59311d83ac838586d8c | 168 | md | Markdown | README.md | jufemaiz/whenever-elasticbeanstalk-test | 867dbf45ed5300f41bc95f61903a6d068ea2d03e | [
"MIT"
] | null | null | null | README.md | jufemaiz/whenever-elasticbeanstalk-test | 867dbf45ed5300f41bc95f61903a6d068ea2d03e | [
"MIT"
] | 8 | 2019-11-07T14:37:32.000Z | 2022-03-30T22:11:01.000Z | README.md | jufemaiz/whenever-elasticbeanstalk-test | 867dbf45ed5300f41bc95f61903a6d068ea2d03e | [
"MIT"
] | 1 | 2019-05-20T16:31:32.000Z | 2019-05-20T16:31:32.000Z | # whenever-elasticbeanstalk-test
Test Rails application for Whenever::Elasticbeanstalk
## Getting Started
```
bundle install
```
```
eb init
```
```
eb deploy
```
| 9.333333 | 53 | 0.690476 | eng_Latn | 0.85707 |
d57c46d90ed079bed2809a3f648b27da72cc4b13 | 1,128 | md | Markdown | content/Post/participatie-en-bestuurlijke-kwaliteit-van-start_06-10-2019.md | VughtParticipeert/Test | 2bf0fef71fe37a33eb0bcb3c2669626c41ccf8b4 | [
"MIT"
] | null | null | null | content/Post/participatie-en-bestuurlijke-kwaliteit-van-start_06-10-2019.md | VughtParticipeert/Test | 2bf0fef71fe37a33eb0bcb3c2669626c41ccf8b4 | [
"MIT"
] | 7 | 2021-02-05T15:41:53.000Z | 2022-02-26T17:52:05.000Z | content/Post/participatie-en-bestuurlijke-kwaliteit-van-start_06-10-2019.md | VughtParticipeert/Test | 2bf0fef71fe37a33eb0bcb3c2669626c41ccf8b4 | [
"MIT"
] | null | null | null | ---
title: Bewonerparticipatie en versterking bestuurlijke kwaliteit
date: 2019-09-24T17:14:49.721Z
theme: Bewonerparticipatie en versterking bestuurlijke kwaliteit
typePost: Publicatie
group: none
status: 1
answered: false
content: >-
Hebt u het ook wel eens meegemaakt dat u als bewoner wordt geconfronteerd met
een nieuw gebouw, verandering in parkeergelegenheid of afgegeven vergunning,
terwijl u daar niet mee eens was en u niet geïnformeerd noch betrokken was?
De gemeente Vught is een relatief kleine gemeente, toch moet zij alle diensten
van een gemeente aanbieden. Dat is makkelijker voor een grote gemeente, dus
zal de gemeente Vught ook andere wegen moeten bewandelen.
Door gebruik te maken van de kennis, ervaring en energie die er bij de eigen
inwoners beschikbaar zijn, kan de gemeente Vught haar capaciteit vergroten.
Het betrekken van inwoners levert mogelijk ook betere oplossingen en
vermindert eventueel verzet tegen beslissingen van de gemeente.
Hierdoor ontstaat een win-win-situatie: een sterkere betrokkenheid van de
inwoners en kwalitatief betere en gedragen plannen.
---
| 37.6 | 80 | 0.801418 | nld_Latn | 0.999992 |
d57cb0196b248c411fc3ea77f2fd4de260443e54 | 6,234 | md | Markdown | docs/core/1.0/transaction_family_specifications/xo_transaction_family.md | hyperledger/sawtooth-website | 22755c7cd0d77049710a90cf8d1ce8a6ea76ad87 | [
"CC-BY-4.0",
"MIT"
] | 3 | 2018-08-22T17:45:53.000Z | 2018-11-25T07:08:16.000Z | docs/core/1.0/transaction_family_specifications/xo_transaction_family.md | hyperledger/sawtooth-website | 22755c7cd0d77049710a90cf8d1ce8a6ea76ad87 | [
"CC-BY-4.0",
"MIT"
] | 19 | 2018-08-22T19:08:05.000Z | 2020-09-22T15:38:34.000Z | docs/core/1.0/transaction_family_specifications/xo_transaction_family.md | hyperledger/sawtooth-website | 22755c7cd0d77049710a90cf8d1ce8a6ea76ad87 | [
"CC-BY-4.0",
"MIT"
] | 30 | 2018-03-16T23:16:35.000Z | 2020-10-03T23:14:01.000Z | # XO Transaction Family
# Overview
<!--
Licensed under Creative Commons Attribution 4.0 International License
https://creativecommons.org/licenses/by/4.0/
-->
The XO transaction family allows users to play a simple board game known
variously as *tic-tac-toe*, *noughts and crosses*, and *XO*.
# State
An XO state entry consists of the UTF-8 encoding of a string with
exactly four commas formatted as follows:
`<name>,<board>,<game-state>,<player-key-1>,<player-key-2>`
where
- \<name> is a nonempty string not containing [\|]{.title-ref},
- \<board> is a string of length 9 containing only [O]{.title-ref},
[X]{.title-ref}, or [-]{.title-ref},
- \<game-state> is one of the following: [P1-NEXT]{.title-ref},
[P2-NEXT]{.title-ref}, [P1-WIN]{.title-ref}, [P2-WIN]{.title-ref},
or [TIE]{.title-ref}, and
- \<player-key-1> and \<player-key-2> are the (possibly empty) public
keys associated with the game\'s players.
In the event of a hash collision (i.e. two or more state entries sharing
the same address), the colliding state entries will stored as the UTF-8
encoding of the string `<a-entry>|<b-entry>|...`, where \<a-entry>,
\<b-entry>,\... are sorted alphabetically.
## Addressing
XO data is stored in state using addresses generated from the XO family
name and the name of the game being stored. In particular, an XO address
consists of the first 6 characters of the SHA-512 hash of the UTF-8
encoding of the string \"xo\" (which is \"5b7349\") plus the first 64
characters of the SHA-512 hash of the UTF-8 encoding of the game name.
For example, the XO address for a game called \"mygame\" could be
generated as follows:
``` pycon
>>> hashlib.sha512('xo'.encode('utf-8')).hexdigest()[:6] + hashlib.sha512('mygame'.encode('utf-8')).hexdigest()[:64]
'5b7349700e158b598043efd6d7610345a75a00b22ac14c9278db53f586179a92b72fbd'
```
# Transaction Payload
An XO transaction request payload consists of the UTF-8 encoding of a
string with exactly two commas formatted as follows:
`<name>,<action>,<space>`
where
- \<name> is a nonempty string not containing [\|]{.title-ref},
- \<action> is either [take]{.title-ref} or [create]{.title-ref}, and
- \<space> is an integer strictly between 0 and 10 if \<action> is
[take]{.title-ref}.
# Transaction Header
## Inputs and Outputs
The inputs and outputs for an XO transaction are just the state address
generated from the transaction game name.
## Dependencies
XO transactions have no explicit dependencies.
## Family
- family_name: \"xo\"
- family_version: \"1.0\"
## Encoding
- payload_encoding: \"csv-utf8\"
# Execution
The XO transaction processor receives a transaction request and a state
dictionary. If it is valid, the transaction request payload will have a
game name, an action, and, if the action is [take]{.title-ref}, a space.
1. If the action is [create]{.title-ref}, then the transaction is
invalid if the game name is already in state dictionary. Otherwise,
the TP will store a new state entry with board
[\-\-\-\-\-\-\-\--]{.title-ref} (i.e. a blank board), game state
[P1-NEXT]{.title-ref}, and empty strings for both player keys.
2. If the action is [take]{.title-ref}, then the transaction is invalid
if the game name is not in the state dictionary. Otherwise, there is
a state entry under the game name with a board, game state, player-1
key, and player-2 key. The transaction is invalid if:
- the game state is [P1-WIN]{.title-ref}, [P2-WIN]{.title-ref}, or
[TIE]{.title-ref}, or
- the game state is [P1-NEXT]{.title-ref} and the player-1 key is
not null and different from the transaction signing key, or
- the game state is [P2-NEXT]{.title-ref} and the player-2 key is
nonnull and different from the transaction signing key, or
- the space-th character in the board-string is not
[-]{.title-ref}.
Otherwise, the transaction processor will update the state entry
according to the following rules:
a. Player keys - If the player-1 key is null (the empty string), it
will be updated to key with which the transaction was signed. If
the player-1 key is nonnull and the player-2 key is null, the
player-2 will be updated to the signing key. Otherwise, the
player keys will not be changed.
b. Board - If the game state is [P1-NEXT]{.title-ref}, the updated
board will be the same as the initial board except with the
space-th character replaced by the character [X]{.title-ref},
and the same for the state [P2-NEXT]{.title-ref} and the
character [O]{.title-ref}.
c. Game state - Call the first three characters of the board string
its first row, the next three characters its second row, and the
last three characters its third row.If any of the rows consist
of the same character, say that character has a *win* on the
board. If all the rows have the same first character or the same
second character or the same third character (the board\'s
columns), that character has a win on the board. If the first
character of the first row and the second character of the
second row and the third character of the third row are the
same, or if the third character of the first row and the second
character of the second row and the first character of the third
row are the same, that character has a win on the board.
- If [X]{.title-ref} has a win on the board and
[O]{.title-ref} doesn\'t, the updated state will be
[P1-WINS]{.title-ref}.
- If [O]{.title-ref} has a win on the board and
[X]{.title-ref} doesn\'t, the updated state will be
[P2-WINS]{.title-ref}.
- Otherwise, if the updated board doesn\'t contain
[-]{.title-ref} (if the board has no empty spaces), the
updated state will be [TIE]{.title-ref}.
- Otherwise, the updated state will be [P2-NEXT]{.title-ref}
if the initial state is [P1-NEXT]{.title-ref} and
[P1-NEXT]{.title-ref} and if the initial state is
[P2-NEXT]{.title-ref}.
| 41.56 | 116 | 0.679339 | eng_Latn | 0.999597 |
d57cb73d9fceeac853d1958e2a17e1fe43150fed | 1,540 | md | Markdown | README.md | osism/ansible-prometheus | d2ae4507c415f6c4eb23596f82c3585509aa7cf4 | [
"Apache-2.0"
] | null | null | null | README.md | osism/ansible-prometheus | d2ae4507c415f6c4eb23596f82c3585509aa7cf4 | [
"Apache-2.0"
] | 10 | 2017-11-02T20:33:14.000Z | 2019-02-27T17:39:35.000Z | README.md | osism/ansible-prometheus | d2ae4507c415f6c4eb23596f82c3585509aa7cf4 | [
"Apache-2.0"
] | 2 | 2019-01-08T14:06:00.000Z | 2019-02-27T13:44:12.000Z | **This project is no longer maintained.**
There is now a Prometheus integration in kolla-ansible. Therefore this role
is no longer needed within OSISM and is no longer maintained.
# Ansible osism.prometheus
[](https://travis-ci.org/osism/ansible-prometheus)
[](https://galaxy.ansible.com/osism/prometheus/)
License
-------
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0.
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Author information
------------------
This role was created by [Betacloud Solutions GmbH](https://betacloud-solutions.de).
| 46.666667 | 138 | 0.762338 | eng_Latn | 0.812073 |
d57cfff36265b5fca17eab654e59dafb83bfb0ec | 13,173 | md | Markdown | README.md | EggPool/NyzoCli | 33103fba7386e26e296fd25d9a0e940695331c62 | [
"MIT"
] | 9 | 2019-01-26T19:45:55.000Z | 2021-03-29T04:13:26.000Z | README.md | EggPool/NyzoCli | 33103fba7386e26e296fd25d9a0e940695331c62 | [
"MIT"
] | 1 | 2020-12-20T07:49:26.000Z | 2021-01-11T16:47:52.000Z | README.md | EggPool/NyzoCli | 33103fba7386e26e296fd25d9a0e940695331c62 | [
"MIT"
] | 6 | 2019-02-09T02:04:32.000Z | 2021-03-20T02:21:15.000Z | # Nyzocli
A simple but efficient Nyzo client for command line and automation usage, in Python.
Uses the pynyzo client package https://github.com/EggPool/pynyzo
## Prerequisites
Python3.6+, pip
On default Ubuntu you can install pip by `apt install python3-pip`
## Installation
`pip3 install -r requirements.txt`
If you have errors when installing the requirements, you may need other libs that can be missing on your setup.
You can try to
`sudo apt install python3-setuptools`
`sudo apt install build-essential`
and redo the requirements install.
Nyzocli needs a `private_seed` file in the user private directory.
Just copy/rename the seed file you want to use.
Run with `-v` flag to check the location
If no file is found, it will create a new one.
## Help
`./Nyzocli.py --help`
(under windows, use `python3 Nyzocli.py [...]` invocation)
To get detailed help for a specific command, use --help with the command, for instance:
`./Nyzocli status --help`
## Example commands
### Get client info:
(does not connect anywhere)
`./Nyzocli.py info`
```
Your private dir is /home/my_redacted_username/nyzo-private
Your public address is abd7fede-35a84b10-8a36e6dc-361d9b32-ca84d149-f6eb85b4-a4e63015-278d4c9f
Default host is 127.0.0.1 on port 9444
```
### Get your balance (from verifier):
Get balance from the given verifier (defaults to localhost)
`./Nyzocli.py vbalance`
`./Nyzocli.py vbalance address`
`./Nyzocli.py -i ip.of.verifier.toask vbalance address `
```
At block: 1696064
Your Balance is: 219.449753
Blocks until fee: 157
```
or as json:
`./Nyzocli.py --json vbalance`
```
{
"block": 1696070,
"balance": 219449753,
"blocks_until_fee": 151,
"address": "abd7fede35a84b108a36e6dc361d9b32ca84d149f6eb85b4a4e63015278d4c9f"
}
```
You can query a specific verifier (default is 127.0.0.1) - use yours only or you'll likely be blacklisted.
`./Nyzocli.py -i verifier0.nyzo.co vbalance abd7fede35a84b10-8a36e6dc361d9b32-ca84d149f6eb85b4-a4e63015278d4c9f `
### Get your balance (from client):
Get balance from a nyzo client (defaults to client.nyzo.co)
`./Nyzocli.py balance`
`./Nyzocli.py balance address`
```
At block: 1696064
Your Balance is: 219.449753
```
or as json:
`./Nyzocli.py --json balance`
```
{
"block": 1696070,
"balance": 219449753,
"address": "abd7fede35a84b108a36e6dc361d9b32ca84d149f6eb85b4a4e63015278d4c9f",
"id_address": "id__8aMo_KWTH4JgzAsDV3puDRbayd59.LL5KajDc1kEAkQw84KHcKwc"
}
```
You can query a specific client (default is client.nyzo.co)
`./Nyzocli.py -c client.nyzo.co balance abd7fede35a84b10-8a36e6dc361d9b32-ca84d149f6eb85b4-a4e63015278d4c9f `
### Get a node status
`./Nyzocli.py status`
`./Nyzocli.py -i verifier0.nyzo.co status`
```
{
"message_type": "StatusResponse18",
"value": [
"nickname: Nyzo 0",
"version: 487",
"ID: b5fd...173b",
"mesh: 1398 total, 527 in cycle",
"cycle length: 530",
"transactions: 0",
"retention edge: 1694074",
"trailing edge: 1694098",
"frozen edge: 1696216 (Grimnoshtadrano)",
"open edge: 1696217",
"blocks transmitted/created: 206/104847",
"votes requested: 458237",
"- h: +1, n: 2, v: 79(79)",
"requester identifier: abd7...4c9f"
]
}
```
### Get a specific block info
> Block has to be recent enough, checking status before hand could help.
`./Nyzocli.py -i verifier0.nyzo.co block 1696093`
```
{
"message_type": "BlockResponse12",
"value": {
"balance": false,
"blocks": [
{"message_type": "Block",
"value": {
"height": 1696093,
"previous_block_hash": "148c51632c67dbc141a70ffef4ae136b1fb3436742efbafdeba14fa6def8a18e",
"start_timestamp": 1548669451000,
"verification_timestamp": 1548669460552,
"transactions": [
{"message_type": "Transaction",
"value": {
"type": 1, "timestamp": 1548669452000,
"amount": 562278171,
"receiver_identifier": "12d454a69523f739eb5eb71c7deb87011804df336ae0e2c19e0b24a636683e31",
"previous_hash_height": 0,
"previous_block_hash": "",
"sender_identifier": "12d454a69523f739eb5eb71c7deb87011804df336ae0e2c19e0b24a636683e31",
"sender_data": "",
"signature": "32914e455244234cbe0bbd4c5fa711dbdf8e25d540d8d73c577b55b3afe0e7ebde9f7848e4656444f8ec2d7f8373cd5c175a5050ed3d83b300ad5062d9e23006"
}}],
"balance_list_hash": "ad6aa5df2d9b40fa1d67400ed4598e9057666453ee70822245df2ac57d91b091",
"verifier_identifier": "3b558f9de4b66a7d91aece0780f2858b32e6e333e4c977d481ed54806f1ba4fc",
"verifier_signature": "9d692637da21310bd27d86de0ba01b4532f64a65bc25310c41bd23fb847c54e4b2fc8ddd7dfc139ca2f04a36acfd5849a897f89c06b6db5441e72db20ad34406"
}}],
"initial_balance_list": null
}
}
```
### Vote for a cycle tx:
Vote for the given cycle tx sig with the optionally provided key_... nyzostring.
If no seed is given, use the wallet one.
`./Nyzocli.py vote sig_gc6VHCY_yfjRc_DyosRLdi084AbY5wP9yVdTTRhajp4JUk7nbRw9c-aufwEwGY~.x0m55u.v.tGzjnA7VYP4V0m-eXyG`
`./Nyzocli.py vote sig_gc6VHCY_yfjRc_DyosRLdi084AbY5wP9yVdTTRhajp4JUk7nbRw9c-aufwEwGY~.x0m55u.v.tGzjnA7VYP4V0m-eXyG 1`
`./Nyzocli.py vote sig_gc6VHCY_yfjRc_DyosRLdi084AbY5wP9yVdTTRhajp4JUk7nbRw9c-aufwEwGY~.x0m55u.v.tGzjnA7VYP4V0m-eXyG 0 key_... `
Sample answer:
```
[
{'block height': '7572863',
'sender ID (raw)': 'f7e40b5eeb7471d2-2b50d63e945e8e05-9658c62f5e2ada2f-82da1b6267330a34',
'sender ID (Nyzo string)': 'id__8fwB2TZIu77iaT3nfGhvAxnnncpMozIrbWbr6U9EcNFSAvPFJ~pC',
'receiver ID (raw)': 'null',
'receiver ID (Nyzo string)': 'null',
'amount': '∩0.000000',
'previous verifier ID (raw)': '0b19818e841b764c-30a176a3e32b9a98-7f1cbf03204bb093-58c45147288ed7f9',
'previous verifier ID (Nyzo string)': 'id__80JqxpY46Vqcca5UF~cIDGy_7b-384LNBTA4kktFAKwXLEfqcvaR',
'expected verifier ID (raw)': '1c86e2b23e1b6e4e-ec70c48c53fc2ad9-6e366c82889d4f6d-3784e570d769874f',
'expected verifier ID (Nyzo string)': 'id__81Q6WI8~6UXeZ734A5f-aKCLdDQ2z9Tfsjv4Xo3orpufoNietWIg',
'next verifier ID (raw)': 'aed5ae8e69d5c823-ecf5474d60533a62-6079ac05667a1bdb-1c7bc88c4bb65fd9',
'next verifier ID (Nyzo string)': 'id__8aZmIFXGTtxAZfm7jn1jeD9xvrN5qEFsUPPZQ8PbKC_qzSwCQ0g5',
'forwarded': 'true'}
]
```
## Utils
see utils dir
### massvote.py
A Mass voter helper
Say you have several in-cycle verifiers, and wand to vote for several cycle tx.
You can vote from your sentinel but that would expose your verifiers (close timing, same order every time)
This script uses NyzoCli individual vote feature to vote with every verifier for every cycle tx once.
It's to be run on a local secure box.
- create a "keys.txt" text file with one key_ a line, from in-cycle verifiers
- create a "sigs.txt" text file with one sig_ vote a line
each line has a sig, one space, the vote (1 for yes or 0 for no)
if no vote is provided, default 1 is assumed.
For ncfp3, you can get and rename the ncfp3-sigs.txt from open nyzo github to vote yes for all.
- edit massvote.py settings if needed (min and max wait time)
- run massvote.py
- you'll get a "vote.sh" script you can then chmod +x and run. This will run the Nyzocli with all needed votes, randomized and with random wait in between.
(of course, you can check that vote.sh in a text editor and make sure it does what it claims)
**New:** Now does query nyzo.today API for existing votes.
Does not give any info about your verifiers, just asks the list of votes for a given sig_ and process locally.
That way, you can re-run the script after a first pass to check and re-submit missing votes.
You can deactivate that feature.
## New in 0.0.6:
### Send regular tx, with optional data and any key
Ex: Send a tip to Nyzocli dev, using local account:
`./Nyzocli.py send abd7fede35a84b10-8a36e6dc361d9b32-ca84d149f6eb85b4-a4e63015278d4c9f 10`
or with recipient id_ :
`./Nyzocli.py send id__8aMo_KWTH4JgzAsDV3puDRbayd59.LL5KajDc1kEAkQw84KHcKwc 10`
Send 10 NYZO **only** if the balance is > 200 NYZO:
`./Nyzocli.py send abd7fede35a84b10-8a36e6dc361d9b32-ca84d149f6eb85b4-a4e63015278d4c9f 10 200`
or with a specific key (sender):
`./Nyzocli.py send id__8aMo_KWTH4JgzAsDV3puDRbayd59.LL5KajDc1kEAkQw84KHcKwc 10 0 '' key_....`
Note: in that precise case you HAVE to specify the "above" condition as 0, data as empty '' then only the key_...
Full command `[]` denote an optional field, that has to be filled if there is another field following
`./Nyzocli.py send recipient amount [above_condition] [data] [key_...]`
So to use the "data" field you have to specify a "above" param (0 to send without condition)
## New since 0.0.7:
You can send the full balance by using "-1" as amount.
Ex: Send whole balance:
`./Nyzocli.py send -- abd7fede35a84b10-8a36e6dc361d9b32-ca84d149f6eb85b4-a4e63015278d4c9f -1`
**Note:** In order to differentiate options (like -v) from arguments (like -1 amount), you need to use `--` (two dashes) to consider all further elements as arguments and not options.
Any required option then goes *before* the `--`.
**Note:** This will empty the account and remove it from the nyzo balances list. The address will be unusable until it gets at leat a n10 deposit.
### Get current frozen edge from a client
(default is client.nyzo.co)
`./Nyzocli.py frozen`
```
height: 10228622
hash: 018f197a54452589fff7783e8a3f745272cb6716b7f01431a898061486a6d4d2
timestamp: 1608397162591
distance: 1
```
or as json:
`./Nyzocli.py --json frozen`
```
{"height": 10228594,
"hash": "513f156b8ba4cac0a5feb14715aa689571cc1eb9d16711cb2919800496343c5d",
"timestamp": 1608397162091,
"distance": "1"
}`
```
## New in 0.0.11, safe_send command
Same as send, with no "above" parameter.
Signs and sends a tx. Wait until the block is frozen.
If the transaction is not in that block, resend it until it passes (5 tries).
ex:
`./Nyzocli.py safe_send abd7fede35a84b10-8a36e6dc361d9b32-ca84d149f6eb85b4-a4e63015278d4c9f 10 key_...`
Can be used without "key_" to use the default wallet.
## New in 0.0.10, Nytro Tokens commands
### Token send
Example command: `./NyzoCli token send id_xxxx 10 TEST`
sends 10 "TEST" tokens to id_xxxx
### Token balance
Get balances - all tokens - for an address (raw or id__)
`./Nyzocli.py token balance a49138f27485cae4096c3eb72f9425943fe4b6f346d0fc76ef40084ec767365d`
or just get balance for a specific token
`./Nyzocli.py token balance a49138f27485cae4096c3eb72f9425943fe4b6f346d0fc76ef40084ec767365d TEST2`
### Token issue
Issue a token: token name, number of decimals, supply
`./Nyzocli.py --verbose token issue -- TEST3 3 -1`
If you use "-1" as supply (meaning mintable token) you need to use the `--` after the " token issue" command.
### Token mint
Only for mintable tokens, if you are the current owner.
Ex: mint 100 tokens "TEST3"
`./Nyzocli.py --verbose token mint TEST3 100`
### Token burn
Only for mintable tokens, up to the amount you have on your balance.
Ex: burn 3.123 tokens "TEST3"
`./Nyzocli.py --verbose token burn TEST3 3.123`
### Token ownership
Only for mintable tokens, if you are the current owner.
Ex: transfer the ownership of "TEST3" to the recipient:
`./Nyzocli.py --verbose token ownership TEST3 3f19e603b9577b6f91d4c84531e1e94e946aa172063ea3a88efb26e3fe75bb84`
## Tip Jar
Show your appreciation, send a few coffees or pizzas to the devs:
`abd7fede35a84b10-8a36e6dc361d9b32-ca84d149f6eb85b4-a4e63015278d4c9f`
or
`id__8aMo_KWTH4JgzAsDV3puDRbayd59.LL5KajDc1kEAkQw84KHcKwc`
## Known twerks
Still some debug or trace messages left over from the pynyzo package to be cleaned up later on.
## Short term roadmap
- (done) Move from using a verifier to using a nyzo client by default (balance)
- Fine tune commands and options
- Done (partially?) Generalize autodetection of address format between raw bytes and nyzostrings.
- Add conversion utils from/to Nyzo strings
- (Done) allow to send full balance (empty wallet)
## Mid term roadmap
- (Done) Add support for Nyzo tokens
- Easier installation, Windows pre-compiled releases
## Releases
* 0.0.12 - bug fix for some id_ string, upgrade pynyzo requirement.
* 0.0.11 - safe_send command (retries if necessary until the tx is frozen or fails)
* 0.0.10 - Tokens support
* 0.0.8 - Bugfix and proper doc for send full balance.
* 0.0.7 - Allow use of id__ or raw wallet id with auto detection.
Get balance from client(balance) or verifier (vbalance), Send whole balance.
*Note:* sending whole balance removes the address from the system, the address will then need 10n min to be used again.
* 0.0.6 - Get frozen edge, Send regular TX.
* 0.0.5 - Randomized Massvote and omitting of existing votes with help from nyzo.today API.
* 0.0.4 - Vote command, local signing, use of client API to forward
* 0.0.3 - Block and balance commands
* 0.0.2 - Status ok
* 0.0.1 - Initial crude version, nothing works yet
## About
Official Nyzo repo: https://github.com/n-y-z-o/nyzoVerifier
Pynyzo python package https://github.com/EggPool/pynyzo
| 32.286765 | 186 | 0.73476 | eng_Latn | 0.853824 |
d57f3096c331e6e774e7b60f1698a3ec2a045b0e | 2,141 | md | Markdown | README.md | alexsun/M3U8Pasersss | c572fd4b90ac7134bb60de2e551d56ea612d170d | [
"MIT"
] | 50 | 2016-08-09T05:15:29.000Z | 2022-02-07T13:38:25.000Z | README.md | alexsun/M3U8Pasersss | c572fd4b90ac7134bb60de2e551d56ea612d170d | [
"MIT"
] | 8 | 2017-04-04T15:58:20.000Z | 2019-10-23T03:05:44.000Z | README.md | alexsun/M3U8Pasersss | c572fd4b90ac7134bb60de2e551d56ea612d170d | [
"MIT"
] | 16 | 2016-10-28T00:10:48.000Z | 2021-12-31T09:33:04.000Z |
# M3U8Kit `We have moved this project to` [M3U8Kit](https://github.com/M3U8Kit/M3U8Parser).
[](https://travis-ci.org/alexsun/M3U8Paser)
[](https://img.shields.io/cocoapods/v/M3U8Kit.svg)
[](http://cocoadocs.org/docsets/M3U8Kit)
[](https://github.com/Carthage/Carthage)
<a id="installation"></a>
## Installation
### [Cocoapods](https://cocoapods.org/)
#### Podfile
To integrate M3U8Kit into your Xcode project using CocoaPods, specify it in your Podfile:
```ruby
source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '7.0'
target 'TargetName' do
pod 'M3U8Kit'
end
```
Then, run the following command:
```bash
$ pod install
```
### Carthage
[Carthage](https://github.com/Carthage/Carthage) is a decentralized dependency manager that builds your dependencies and provides you with binary frameworks.
To integrate MLSOAppDelegate into your Xcode project using Carthage, specify it in your `Carfile`:
```ogdl
github "alexsun/M3U8Paser" ~> 0.2.1
```
Run `carthage` to build the framework and drag the built `M3U8Kit.framework` into your Xcode project.
### Manually
If you prefer not to use either of the above mentioned dependency managers, you can integrate `M3U8Kit` into your project manually by adding the files contained in the [Source](https://github.com/alexsun/M3U8Paser/tree/master/Source) folder to your project.
## Usage
- Asynchronous
```objc
#import "NSURL+m3u8.h"
[<#URL#> loadM3U8AsynchronouslyCompletion:^(M3U8PlaylistModel *model, NSError *error) {
}];
```
- Synchronous
```objective-c
NSError *error = nil;
M3U8PlaylistModel *model = [[M3U8PlaylistModel alloc]
initWithURL:@"https://xxx.xxx.com/live.m3u8"
error:&error];
```
## License
M3U8Kit is available under the MIT license. See the LICENSE file for more info.
| 29.736111 | 257 | 0.723027 | eng_Latn | 0.52662 |
d57fe5a59494f7c66bf7e0acede083b5134b4127 | 2,061 | md | Markdown | Language/Reference/User-Interface-Help/list-property-microsoft-forms.md | skucab/VBA-Docs | 2912fe0343ddeef19007524ac662d3fcb8c0df09 | [
"CC-BY-4.0",
"MIT"
] | 4 | 2019-09-07T04:44:48.000Z | 2021-12-16T15:05:50.000Z | Language/Reference/User-Interface-Help/list-property-microsoft-forms.md | skucab/VBA-Docs | 2912fe0343ddeef19007524ac662d3fcb8c0df09 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-09-28T07:52:15.000Z | 2021-09-28T07:52:15.000Z | Language/Reference/User-Interface-Help/list-property-microsoft-forms.md | skucab/VBA-Docs | 2912fe0343ddeef19007524ac662d3fcb8c0df09 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-06-23T03:40:08.000Z | 2021-06-23T03:40:08.000Z | ---
title: List property (Microsoft Forms)
keywords: fm20.chm2001400
f1_keywords:
- fm20.chm2001400
ms.prod: office
ms.assetid: 15ea715a-a361-34f4-98af-520942a6664e
ms.date: 11/16/2018
localization_priority: Normal
---
# List property (Microsoft Forms)
Returns or sets the list entries of a **[ListBox](listbox-control.md)** or **[ComboBox](combobox-control.md)**.
## Syntax
_object_. **List(**_row, column_**)** [= _Variant_ ]
The **List** property syntax has these parts:
|Part|Description|
|:-----|:-----|
| _object_|Required. A valid object.|
| _row_|Required. An integer with a range from 0 to one less than the number of entries in the list.|
| _column_|Required. An integer with a range from 0 to one less than the number of columns.|
| _Variant_|Optional. The contents of the specified entry in the **ListBox** or **ComboBox**.|
## Settings
Row and column numbering begins with zero. That is, the row number of the first row in the list is zero; the column number of the first column is zero. The number of the second row or column is 1, and so on.
## Remarks
The **List** property works with the **[ListCount](listcount-property.md)** and **[ListIndex](listindex-property.md)** properties. Use **List** to access list items. A list is a variant [array](../../Glossary/vbe-glossary.md#array); each item in the list has a row number and a column number.
Initially, **ComboBox** and **ListBox** contain an empty list.
> [!NOTE]
> To specify items you want to display in a **ComboBox** or **ListBox**, use the **[AddItem](additem-method.md)** method. To remove items, use the **[RemoveItem](removeitem-method.md)** method.
Use **List** to copy an entire two-dimensional array of values to a control. Use **AddItem** to load a one-dimensional array or to load an individual element.
## See also
- [Microsoft Forms examples](examples-microsoft-forms.md)
- [Microsoft Forms reference](reference-microsoft-forms.md)
- [Microsoft Forms concepts](concepts-microsoft-forms.md)
[!include[Support and feedback](~/includes/feedback-boilerplate.md)] | 40.411765 | 292 | 0.729743 | eng_Latn | 0.976404 |
d580ab844cf92b418ca6a3b0ddcab43278c9fd1e | 19,656 | md | Markdown | docs/content/v1.1/architecture/concepts/docdb/persistence.md | eliahburns/yugabyte-db | 570d28dde28d6a0e6a689274b5e319de9a81b707 | [
"Apache-2.0",
"CC0-1.0"
] | null | null | null | docs/content/v1.1/architecture/concepts/docdb/persistence.md | eliahburns/yugabyte-db | 570d28dde28d6a0e6a689274b5e319de9a81b707 | [
"Apache-2.0",
"CC0-1.0"
] | null | null | null | docs/content/v1.1/architecture/concepts/docdb/persistence.md | eliahburns/yugabyte-db | 570d28dde28d6a0e6a689274b5e319de9a81b707 | [
"Apache-2.0",
"CC0-1.0"
] | null | null | null | ---
title: Persistence
linkTitle: Persistence
description: Persistence on top of RocksDB
menu:
v1.1:
identifier: docdb-persistence
parent: docdb
weight: 970
isTocNested: false
showAsideToc: true
---
Once data is replicated via Raft across a majority of the tablet-peers, it is applied to each tablet peer’s local DocDB document storage layer. This storage layer is essentially a persistent “**key to object/document**” store rather than just a “key to value” store.
* The **keys** in DocDB document model are compound keys consisting of:
* 1 or more **hash organized components**, followed by
* 0 or more **ordered (range) components**. These components are stored in their data type specific sort order; both
ascending and descending sort order is supported for each ordered component of the key.
* The **values** in DocDB document data model can be:
* **primitive types**: such as int32, int64, double, text, timestamp, etc.
* **non-primitive types (sorted maps)**: These objects map scalar keys to values, which could be either scalar or sorted maps as well.
This model allows multiple levels of nesting, and corresponds to a JSON-like format. Other data
structures like lists, sorted sets etc. are implemented using DocDB’s object type with special key
encodings. In DocDB, [hybrid timestamps](../../transactions/distributed-txns/) of each update are recorded carefully, so that it is possible to recover the state of any document at some point in the past. Overwritten or deleted versions of data are garbage-collected as soon as there are no transactions reading at a snapshot at which the old value would be visible.
## Enhancing RocksDB for Speed & Scale
DocDB uses a highly customized version of [RocksDB](http://rocksdb.org/), a log-structured merge tree (LSM) based key-value store.
The primary motivation behind the enhancements or customizations to RocksDB are described below:
* **Efficient implementation of a row/document model on top of a KV store**: To implement a flexible data
model---such as a row (comprising of columns), or collections types (such as list, map, set) with
arbitrary nesting---on top of a key-value store, but, more importantly, to implement efficient
operations on this data model such as:
* fine-grained updates to a part of the row or collection without incurring a read-modify-write
penalty of the entire row or collection
* deleting/overwriting a row or collection/object at an arbitrary nesting level without incurring a
read penalty to determine what specific set of KVs need to be deleted
* enforcing row/object level TTL based expiry:
a tighter coupling into the “read/compaction” layers of the underlying KV store (RocksDB) is needed.
We use RocksDB as an append-only store and operations such as row or collection delete are modeled
as an insert of a special “delete marker”. This allows deleting an entire subdocument efficiently
by just adding one key/value pair to RocksDB. Read hooks automatically recognize these markers and
suppress expired data. Expired values within the subdocument are cleaned up/garbage collected by our
customized compaction hooks.
* **Avoid penalty of two transaction/write-ahead (WAL) logs**: Yugabyte is a distributed database that
uses Raft for replication. Changes to the distributed system are already recorded/journalled as part
of Raft logs. When a change is accepted by a majority of peers, it is applied to each tablet peer’s
DocDB, but the additional WAL mechanism in RocksDB (under DocDB) is unnecessary and adds overhead.
For correctness, in addition to disabling the WAL mechanism in RocksDB, Yugabyte tracks the Raft
“sequence id” up to which data has been flushed from RocksDB’s memtables to SSTable files. This
ensures that we can correctly garbage collect the Raft WAL logs as well as replay the minimal number
of records from Raft WAL logs on a server crash or restart.
* **Multi-version concurrency control (MVCC) is done at a higher layer**: The mutations to records in the
system are versioned using hybrid-timestamps maintained at the YBase layer. As a result, the notion
of MVCC as implemented in a vanilla RocksDB (using sequence ids) is not necessary and only adds
overhead. Yugabyte does not use RocksDB’s sequence ids, and instead uses hybrid-timestamps that are
part of the encoded key to implement MVCC.
* **Backups/Snapshots**: These need to be higher level operations that take into consideration data in
DocDB as well as in the Raft logs to get a consistent cut of the state of the system
* **Read Optimizations**:
* **Data model aware bloom filters**: The keys stored by DocDB in RocksDB consist of a number of
components, where the first component is a "document key", followed by a few scalar components, and
finally followed by a timestamp (sorted in reverse order).
* The bloom filter needs to be aware of what components of the key need be added to the bloom so that only the relevant SSTable files in the LSM store are looked up during a read operation.
* In a traditional KV store, range scans do not make use of bloom filters because exact keys that fall in the range are unknown. However, we have implemented a data-model aware bloom filter, where range scans within keys that share the same hash component can also benefit from bloom filters. For
example, a scan to get all the columns within row or all the elements of a collection can also
benefit from bloom filters.
* **Data model aware range query optimization**: The ordered (or range) components of the compound-keys in DocDB frequently have a natural order. For example, it may be an int that represents a message id
(for a messaging like application) or a timestamp (for a IoT/Timeseries like use case). See example
below. By keeping hints with each SSTable file in the LSM store about the min/max values for these
components of the “key”, range queries can intelligently prune away the lookup of irrelevant SSTable
files during the read operation.
```sql
SELECT message_txt
FROM messages
WHERE user_id = 17
AND message_id > 50
AND message_id < 100;
```
Or, in the context of a time-series application:
```sql
SELECT metric_value
FROM metrics
WHERE metric_name = ’system.cpu’
AND metric_timestamp < ?
AND metric_timestamp > ?
```
* **Server-global block cache across multiple DocDB instances**: A shared block cache is used across the
DocDB/RocksDB instances of all the tablets hosted by a YB-TServer. This maximizes the use of memory
resources, and avoids creating silos of cache that each need to be sized accurately for different
user tables.
* **Server-global memstore limits across multiple DocDB instances**: While per-memstore flush sizes can be
configured, in practice, because the number of memstores may change over time as users create new
tables, or tablets of a table move between servers, we have enhanced the storage engine to enforce a
global memstore threshold. When such a threshold is reached, selection of which memstore to flush
takes into account what memstores carry the oldest records (determined using hybrid timestamps) and
therefore are holding up Raft logs and preventing them from being garbage collected.
* **Scan-resistant block cache**: We have enhanced RocksDB’s block cache to be scan resistant. The
motivation was to prevent operations such as long-running scans (e.g., due to an occasional large
query or background Spark jobs) from polluting the entire cache with poor quality data and wiping
out useful/hot data.
## Mapping DocDB documents to RocksDB
DocDB is the storage layer that acts as the common backbone of different APIs that are supported by
YugabyteDB (currently YCQL, YEDIS, and YSQL(beta)).
The documents are stored using a key-value store based on RocksDB, which is typeless. The documents
are converted to multiple key-value pairs along with timestamps. Because documents are spread across
many different key-values, it’s possible to partially modify them cheaply.
For example, consider the following document stored in DocDB:
```
DocumentKey1 = {
SubKey1 = {
SubKey2 = Value1
SubKey3 = Value2
},
SubKey4 = Value3
}
```
Keys we store in RocksDB consist of a number of components, where the first component is a "document
key", followed by a few scalar components, and finally followed by a MVCC timestamp (sorted in
reverse order). Each component in the DocumentKey, SubKey, and Value, are PrimitiveValues, which are
just (type, value) pairs, which can be encoded to and decoded from strings. When we encode primitive
values in keys, we use a binary-comparable encoding for the value, so that sort order of the
encoding is the same as the sort order of the value.
Assume that the example document above was written at time T10 entirely. Internally the above
example’s document is stored using 5 RocksDB key value pairs:
```
DocumentKey1, T10 -> {} // This is an init marker
DocumentKey1, SubKey1, T10 -> {}
DocumentKey1, SubKey1, SubKey2, T10 -> Value1
DocumentKey1, SubKey1, SubKey3, T10 -> Value2
DocumentKey1, SubKey4, T10 -> Value3
```
Deletions of Documents and SubDocuments are performed by writing a single Tombstone marker at the
corresponding value. During compaction, overwritten or deleted values are cleaned up to reclaim
space.
## Mapping of YCQL rows to DocDB
For CQL tables, every row is a document in DocDB. The Document key contains the full primary key -
the values of partition (hash) column(s) and clustering (range) column(s), in order. A 16-bit hash
of the hash portion is also prefixed in the DocKey. The subdocuments within the Document are the
rest of the columns, whose SubKey is the corresponding column ID. If a column is a non-primitive
type (such as a map or set), the corresponding subdocument is an Object.
There’s a unique byte for each data type we support in CQL. The values are prefixed with the
corresponding byte. The type prefix is also present in the primary key’s hash or range components.
We use a binary-comparable encoding to translate the value for each CQL type to strings that go to
the KV-Store.
In CQL there are two types of TTL, the table TTL and column level TTL. The column TTLs are stored
with the value using the same encoding as Redis. The Table TTL is not stored in DocDB (it is stored
in master’s syscatalog as part of the table’s schema). If no TTL is present at the column’s value,
the table TTL acts as the default value.
Furthermore, CQL has a distinction between rows created using Insert vs Update. We keep track of
this difference (and row level TTLs) using a "liveness column", a special system column invisible to
the user. It is added for inserts, but not updates: making sure the row is present even if all
non-primary key columns are deleted only in the case of inserts.
**CQL Example: Rows with primitive and collection types**
Consider the following CQL commands:
```sql
CREATE TABLE msgs (user_id text,
msg_id int,
msg text,
msg_props map<text, text>,
PRIMARY KEY ((user_id), msg_id));
T1: INSERT INTO msgs (user_id, msg_id, msg, msg_props)
VALUES ('user1', 10, 'msg1', {'from' : '[email protected]', 'subject' : 'hello'});
```
The entries in DocDB at this point will look like the following:
```
(hash1, 'user1', 10), liveness_column_id, T1 -> [NULL]
(hash1, 'user1', 10), msg_column_id, T1 -> 'msg1'
(hash1, 'user1', 10), msg_props_column_id, 'from', T1 -> '[email protected]'
(hash1, 'user1', 10), msg_props_column_id, 'subject', T1 -> 'hello'
```
```sql
T2: UPDATE msgs
SET msg_props = msg_props + {'read_status' : 'true'}
WHERE user_id = 'user1', msg_id = 10
```
The entries in DocDB at this point will look like the following:
<pre>
<code>(hash1, 'user1', 10), liveness_column_id, T1 -> [NULL]
(hash1, 'user1', 10), msg_column_id, T1 -> 'msg1'
(hash1, 'user1', 10), msg_props_column_id, 'from', T1 -> '[email protected]'
<b>(hash1, 'user1', 10), msg_props_column_id, 'read_status', T2 -> 'true'</b>
(hash1, 'user1', 10), msg_props_column_id, 'subject', T1 -> 'hello'
</code>
</pre>
```sql
T3: INSERT INTO msgs (user_id, msg_id, msg, msg_props)
VALUES (‘user1’, 20, 'msg2', {'from' : '[email protected]', 'subject' : 'bar'});
```
The entries in DocDB at this point will look like the following:
<pre>
<code>(hash1, 'user1', 10), liveness_column_id, T1 -> [NULL]
(hash1, 'user1', 10), msg_column_id, T1 -> 'msg1'
(hash1, 'user1', 10), msg_props_column_id, 'from', T1 -> '[email protected]'
(hash1, 'user1', 10), msg_props_column_id, 'read_status', T2 -> 'true'
(hash1, 'user1', 10), msg_props_column_id, 'subject', T1 -> 'hello'
<b>(hash1, 'user1', 20), liveness_column_id, T3 -> [NULL]
(hash1, 'user1', 20), msg_column_id, T3 -> 'msg2'
(hash1, 'user1', 20), msg_props_column_id, 'from', T3 -> '[email protected]'
(hash1, 'user1', 20), msg_props_column_id, 'subject', T3 -> 'bar'</b></code>
</pre>
Delete a single column from a row
```sql
T4: DELETE msg_props
FROM msgs
WHERE user_id = 'user1'
AND msg_id = 10;
```
Even though, in the example above, the column being deleted is a non-primitive column (a map), this
operation only involves adding a delete marker at the correct level, and does not incur any read
overhead. The logical layout in DocDB at this point is shown below.
<pre>
<code>(hash1, 'user1', 10), liveness_column_id, T1 -> [NULL]
(hash1, 'user1', 10), msg_column_id, T1 -> 'msg1'
<b>(hash1, 'user1', 10), msg_props_column_id, T4 -> [DELETE]</b>
<s>(hash1, 'user1', 10), msg_props_column_id, 'from', T1 -> '[email protected]'
(hash1, 'user1', 10), msg_props_column_id, 'read_status', T2 -> 'true'
(hash1, 'user1', 10), msg_props_column_id, 'subject', T1 -> 'hello'</s>
(hash1, 'user1', 20), liveness_column_id, T3 -> [NULL]
(hash1, 'user1', 20), msg_column_id, T3 -> 'msg2'
(hash1, 'user1', 20), msg_props_column_id, 'from', T3 -> '[email protected]'
(hash1, 'user1', 20), msg_props_column_id, 'subject', T3 -> 'bar'</code>
</pre>
*Note: The KVs that are displayed in “strike-through” font are logically deleted.*
Note: The above is not the physical layout per se, as the writes happen in a log-structured manner.
When compactions happen, the space for the KVs corresponding to the deleted columns is reclaimed, as
shown below.
<pre>
<code>(hash1, 'user1', 10), liveness_column_id, T1 -> [NULL]
(hash1, 'user1', 10), msg_column_id, T1 -> 'msg1'
(hash1, 'user1', 20), liveness_column_id, T3 -> [NULL]
(hash1, 'user1', 20), msg_column_id, T3 -> 'msg2'
(hash1, 'user1', 20), msg_props_column_id, 'from', T3 -> '[email protected]'
(hash1, 'user1', 20), msg_props_column_id, 'subject', T3 -> 'bar'
T5: DELETE FROM msgs // Delete entire row corresponding to msg_id 10
WHERE user_id = 'user1'
AND msg_id = 10;
<b>(hash1, 'user1', 10), T5 -> [DELETE]</b>
<s>(hash1, 'user1', 10), liveness_column_id, T1 -> [NULL]
(hash1, 'user1', 10), msg_column_id, T1 -> 'msg1'</s>
(hash1, 'user1', 20), liveness_column_id, T3 -> [NULL]
(hash1, 'user1', 20), msg_column_id, T3 -> 'msg2'
(hash1, 'user1', 20), msg_props_column_id, 'from', T3 -> '[email protected]'
(hash1, 'user1', 20), msg_props_column_id, 'subject', T3 -> 'bar'</code>
</pre>
**CQL Example #2: Time-To-Live (TTL) Handling**
CQL allows the TTL property to be specified at the level of each INSERT/UPDATE operation. In such
cases, the TTL is stored as part of the RocksDB value as shown below:
<pre>
<code>CREATE TABLE page_views (page_id text,
views int,
category text,
PRIMARY KEY ((page_id)));
T1: INSERT INTO page_views (page_id, views)
VALUES ('abc.com', 10)
USING TTL 86400
// The entries in DocDB will look like the following
(hash1, 'abc.com'), liveness_column_id, T1 -> (TTL = 86400) [NULL]
(hash1, 'abc.com'), views_column_id, T1 -> (TTL = 86400) 10
T2: UPDATE page_views
USING TTL 3600
SET category = 'news'
WHERE page_id = 'abc.com';
// The entries in DocDB will look like the following
(hash1, 'abc.com'), liveness_column_id, T1 -> (TTL = 86400) [NULL]
(hash1, 'abc.com'), views_column_id, T1 -> (TTL = 86400) 10
<b>(hash1, 'abc.com'), category_column_id, T2 -> (TTL = 3600) 'news'</b></code>
</pre>
**Table Level TTL**: CQL also allows the TTL property to be specified at the table level. In that case,
we do not store the TTL on a per KV basis in RocksDB; but the TTL is implicitly enforced on reads as
well as during compactions (to reclaim space).
## Mapping YEDIS keys to DocDB documents
Redis is a schemaless data store. There is only one primitive type (string) and some collection
types. In this case, the documents are pretty simple. For primitive values, the document consists of
only one value. The document key is just a string prefixed with a hash. Redis collections are single
level documents. Maps correspond to SubDocuments which are discussed above. Sets are stored as maps
with empty values, and Lists have indexes as keys. For non-primitive values (e.g., hash, set type),
we store the type in parent level initial value, which is sorted before the subkeys. Any redis value
can have a TTL, which is stored in the RocksDB-value.
**Redis Example**
| Timestamp | Command | New Key-Value pairs added in RocksDB |
|:---------:|:-----------------------------------------:|:---------------------------------------------------------------------------------------------------------------:|
|T1 |SET key1 value1 EX 15 |(h1, key1), T1 -> 15, value1 |
|T2 |HSET key2 subkey1 value1 |(h2, key2), T2 -> [Redis-Hash-Type]<br/>(h2, key2), subkey1, T2 -> value1 |
|T3 |HSET key2 subkey2 value2 |(h2, key2), subkey2, T3 -> value2 |
|T4 |DEL key2 |(h2, key2), T4 -> Tombstone |
|T5 |HMSET key2 subkey1 new_val1 subkey3 value3 |(h2, key2), T2 -> [Redis-Hash-Type]<br/>(h2, key2), subkey1, T5 -> new_val1<br/>(h2, key2), subkey3, T5 -> value3|
|T6 |SADD key3 value4 value5 |(h3, key3), T6 -> [Redis-Set-Type]<br/>(h3, key3), value4, T6 -> [NULL]<br/>(h3, key3), value5, T6 -> [NULL] |
|T7 |SADD key3 value6 |(h3, key3), value6, T7 -> [NULL] |
Although they are added out of order, we get a sorted view of the items in the key value store when
reading, as shown below:
```
(h1, key1), T1 -> 15, value1
(h2, key2), T5 -> [Redis-Hash-Type]
(h2, key2), T4 -> Tombstone
(h2, key2), T2 -> [Redis-Hash-Type]
(h2, key2), subkey1, T5 -> new_val1
(h2, key2), subkey1, T2 -> value1
(h2, key2), subkey2, T3 -> value2
(h2, key2), subkey3, T5 -> value3
(h3, key3), T6 -> [Redis-Set-Type]
(h3, key3), value6, T7 -> [NULL]
(h3, key3), value4, T6 -> [NULL]
(h3, key3), value5, T6 -> [NULL]
```
Using an iterator, it is easy to reconstruct the hash and set contents efficiently.
| 51.590551 | 366 | 0.694699 | eng_Latn | 0.993166 |
d580fc7abdac49e80eb5e27c6d56862e0e55d1d6 | 3,171 | md | Markdown | README.md | dilshan/ntp-clock | ed83aa0790b879627b408ac650a193176b18a5ea | [
"MIT"
] | 5 | 2021-04-27T21:04:02.000Z | 2022-03-27T22:29:21.000Z | README.md | dilshan/ntp-clock | ed83aa0790b879627b408ac650a193176b18a5ea | [
"MIT"
] | null | null | null | README.md | dilshan/ntp-clock | ed83aa0790b879627b408ac650a193176b18a5ea | [
"MIT"
] | null | null | null | # NTP based digital clock panel
This project introduces an open-source, *ATmega328* based, configurable [NTP](https://en.wikipedia.org/wiki/Network_Time_Protocol) clock with a 2.3-inch, 7-segment display driver. This clock automatically obtains time from the configured NTP server and updates the date and time of the built-in RTC (*real-time clock*). If the connection to the NTP server is lost, the clock continues to run using its built-in RTC.
All the parameters of this clock can configure using its USB base serial terminal. The firmware of this clock supports both *static* and *DHCP* addressing modes. Apart from that, parameters such as NTP server address, time-offset, and clock display formats can change through the menu-driven configuration terminal.
This clock is designed to drive large common-anode, 7-segment displays. The prototype version is assembled using four individual segments of 7.2V, 2.3-inch, red color displays (*FJS23101BH*). To archive, the necessary high output voltage and the current, the 7-segment display output stage of this clock is formed using *ULN2803* Darlington transistor array and *BC858* transistors.
The network component of this clock is built around the *ENC28J60* 10BASE-T stand-alone Ethernet controller.
Highly accurate *DS3231M* RTC is using in this clock for time-keeping operations. To backup the date and time, the *CR1220* type button cell is included in the PCB. The date and time are syncs with the NTP server during the system startup. Users can manually initiate synchronization by pressing the "*SYNC*" button in the system.
Depending on the NTP server, the user needs to specify the time offset to the system to get the correct local time. Time offset can configure using the system configuration menu, and it must be input in a standard format like *+5:30*.
Firmware of this clock is developed using the [Arduino framework](https://www.arduino.cc/en/software) and libraries.
[**PCBWay**](https://www.pcbway.com) provides sponsorship for this project. The [PCBWay online ordering service](https://www.pcbway.com/orderonline.aspx) provides excellent help to fabricate this PCB. We got finished PCBs within three days, and the quality of the service is at a superior level. PCB of this project can directly [order from PCBWay through this link](https://www.pcbway.com/project/shareproject/NTP_based_digital_clock_panel.html).
This project is a [certified](https://certification.oshwa.org/lk000009.html) open-source hardware project. All the content of this project are distributed under the terms of the following license:
- Hardware License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)
- Software and firmware License: [MIT](https://github.com/dilshan/ntp-clock/blob/main/LICENSE)
- [Documentation](https://github.com/dilshan/ntp-clock/wiki) License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)
[](https://certification.oshwa.org/lk000009.html)
| 113.25 | 447 | 0.791233 | eng_Latn | 0.984915 |
d5812596ffa4fef10c8abaf5ac3fc4a7563b8921 | 62 | md | Markdown | README.md | rudneymartins/CurdoEmVideoHTML5 | 56c4812d3abdb0a660552d16ca5527b258dc3e68 | [
"MIT"
] | null | null | null | README.md | rudneymartins/CurdoEmVideoHTML5 | 56c4812d3abdb0a660552d16ca5527b258dc3e68 | [
"MIT"
] | null | null | null | README.md | rudneymartins/CurdoEmVideoHTML5 | 56c4812d3abdb0a660552d16ca5527b258dc3e68 | [
"MIT"
] | null | null | null | # CurdoEmVideoHTML5
pagina feita no Curso em Video de HTML5.
| 20.666667 | 41 | 0.790323 | por_Latn | 0.988918 |
d58159c972c7d2c0f6d7245c67f743e11c7291f0 | 3,137 | md | Markdown | source/guides/dashboard/bitbucket-integration.md | mihaerzen/cypress-documentation | bb8d4ba745270317156d70230d6e482c67dc9209 | [
"MIT"
] | 1 | 2021-05-19T11:21:09.000Z | 2021-05-19T11:21:09.000Z | source/guides/dashboard/bitbucket-integration.md | pedrohyvo/cypress-documentation | 80d839b45d2a17a38cc1cc89439b3daa7ee3182a | [
"MIT"
] | 1 | 2018-10-03T19:15:40.000Z | 2018-10-03T19:15:40.000Z | source/guides/dashboard/bitbucket-integration.md | pedrohyvo/cypress-documentation | 80d839b45d2a17a38cc1cc89439b3daa7ee3182a | [
"MIT"
] | null | null | null | ---
title: Bitbucket Integration
---
{% note info %}
Bitbucket integration is currently in beta.
{% endnote %}
The {% url "Cypress Dashboard" https://on.cypress.io/dashboard %} can integrate your Cypress tests with your Bitbucket workflow via {% urlHash 'status checks' Status-checks %} and {% urlHash 'pull request comments' Pull-Request-comments %}. A project first needs to be {% url "setup to record" projects %} to the Cypress Dashboard to use Bitbucket integration.
{% note warning %}
Bitbucket Integration is dependent on your CI environment reliably providing commit SHA data (typically via an environment variable). This is not a problem for most users, but if you are facing Bitbucket integration issues with your CI setup, please make sure the git information is being sent properly by following {% url "these guidelines" continuous-integration-introduction#Git-information %}. If you are still facing issues after this, please [contact us](mailto:[email protected]).
{% endnote %}
## Installing the Bitbucket integration
{% note warning %}
Bitbucket OAuth2 applications will allow the Cypress Dashboard to authenticate as the user that registered the application. That means the Cypress will have visibility to every Bitbucket repo you can access. If you want tighter control on the repos that the Cypress will see, consider creating a service account with more limited access in Bitbucket.
{% endnote %}
1. Visit **Integrations** in the Cypress Dashboard.
1. Click **Install Bitbucket Integration**.
1. (For beta only) You need to enable Bitbucket's [development mode](https://support.atlassian.com/bitbucket-cloud/docs/enable-bitbucket-cloud-development-mode/) for your user account to continue.
1. Continue through the Bitbucket OAuth installation flow in the popup window.
1. Once installed, connect your projects to a Bitbucket repo.
1. (Optional) Configure the behavior for each project.
## Configuring the Bitbucket integration
### Status checks
By default, Cypress will post a **cypress/run** commit status containing the results of the Cypress run. This will prevent your team from merging any PRs with failing Cypress tests.
Additionally, Cypress can post a **cypress/flake** commit status indicating whether the Cypress run contained any flaky tests. This will prevent your team from merging any PRs with flaky tests.
You can manage this behavior in your project's **Project Settings** page.
### Pull Request comments
By default, Cypress will post a PR comment summarizing the run when the run completes. It will include test counts, run info, and a summary of tests that failed or were flaky.
You can manage this behavior in your project's **Project Settings** page.
## Uninstalling the Bitbucket integration
You can remove this integration by visiting the **Integrations → Bitbucket** page of your organization. This will stop all status checks and PR comments from Cypress.
## Feedback
Have ideas for how we can improve our Bitbucket Integration? [Let us know!](https://portal.productboard.com/cypress-io/1-cypress-dashboard/c/49-bitbucket-integration?utm_medium=social&utm_source=portal_share) | 62.74 | 486 | 0.784826 | eng_Latn | 0.992011 |
d5817a252cb1a4485d3ed0073924efb135e9beb0 | 2,157 | md | Markdown | vendor/clipboard-win/README.md | vcapra1/alacritty | 64026e22f889004c04297dfece71b2a65edb7f38 | [
"Apache-2.0"
] | null | null | null | vendor/clipboard-win/README.md | vcapra1/alacritty | 64026e22f889004c04297dfece71b2a65edb7f38 | [
"Apache-2.0"
] | null | null | null | vendor/clipboard-win/README.md | vcapra1/alacritty | 64026e22f889004c04297dfece71b2a65edb7f38 | [
"Apache-2.0"
] | null | null | null | clipboard-win
====================
[](https://crates.io/crates/clipboard-win)
[](https://docs.rs/clipboard-win/*/x86_64-pc-windows-msvc/clipboard_win/)
Provides simple way to interact with Windows clipboard.
# Clipboard
All read and write access to Windows clipboard requires user to open it.
For your convenience you can use [Clipboard](https://docs.rs/clipboard-win/*/x86_64-pc-windows-msvc/clipboard_win/struct.Clipboard.html) struct that opens it at creation
and closes on its drop.
Alternatively you can access all functionality directly through [raw module](https://docs.rs/clipboard-win/*/x86_64-pc-windows-msvc/clipboard_win/raw/index.html).
Below you can find examples of usage.
## Empty clipboard
```rust
use clipboard_win::Clipboard;
fn main() {
Clipboard::new().unwrap().empty();
}
```
## Set and get raw data
```rust
use clipboard_win::formats;
use clipboard_win::Clipboard;
use std::str;
fn main() {
let text = "For my waifu!\0"; //For text we need to pass C-like string
Clipboard::new().unwrap().set(formats::CF_TEXT, text.as_bytes());
let mut buffer = [0u8; 52];
let result = Clipboard::new().unwrap().get(formats::CF_TEXT, &mut buffer).unwrap();
assert_eq!(str::from_utf8(&buffer[..result]).unwrap(), text);
}
```
## Set and get String
```rust
use clipboard_win::Clipboard;
use std::str;
fn main() {
let text = "For my waifu!";
Clipboard::new().unwrap().set_string(text);
let mut result = String::new();
Clipboard::new().unwrap().get_string(&mut result).unwrap();
assert_eq!(text, result);
}
```
## Set and get String shortcuts
```rust
use clipboard_win::{set_clipboard_string, get_clipboard_string};
use std::str;
fn main() {
let text = "For my waifu!";
set_clipboard_string(text).expect("Success");
let result = get_clipboard_string().unwrap();
assert_eq!(text, result);
}
```
| 25.987952 | 170 | 0.668521 | eng_Latn | 0.392088 |
d5822dc16b98e9352080a9a70d3c3fd3909566a9 | 3,972 | md | Markdown | _posts/2021-07-25-implementing-lex-like-chatbot-using-kogpt2.md | haandol/haandol.github.com | 1128edc9810c69eaf1d27ab11c7f178d934fd921 | [
"MIT"
] | 3 | 2017-05-22T04:04:10.000Z | 2020-12-15T05:47:47.000Z | _posts/2021-07-25-implementing-lex-like-chatbot-using-kogpt2.md | haandol/haandol.github.com | 1128edc9810c69eaf1d27ab11c7f178d934fd921 | [
"MIT"
] | 3 | 2017-05-01T11:39:43.000Z | 2021-02-26T04:53:41.000Z | _posts/2021-07-25-implementing-lex-like-chatbot-using-kogpt2.md | haandol/haandol.github.com | 1128edc9810c69eaf1d27ab11c7f178d934fd921 | [
"MIT"
] | 1 | 2017-05-01T11:10:39.000Z | 2017-05-01T11:10:39.000Z | ---
layout: post
title: KoGPT2 로 Amazon Lex 같은 다이얼로그 기반의 챗봇 만들기
excerpt: Implement close-domain chatbot using KoGPT2
author: vincent
email: [email protected]
tags: kogpt2 transformers huggingface lex gpt chatbot
publish: true
---
## TL;DR
코드는 여기[^1]
## 시작하며
다이얼로그 기반의 한글 챗봇을 쓸 일이 생겼는데, Amazon Lex 는 한글지원이 안된다.
Rasa, Watson, Lex 같은 다이얼로그 기반의 챗봇 아키텍쳐들을 이것저것 뒤져봤는데, 머리가 나빠서 이해가 잘 안되었다..
그래서 NLP 공부하면서 Amazon Lex를 단순화 시킨 챗봇 프레임워크를 하나 만들어봤다.
(개인적으로는 프로덕션에서 쓴다면 구글의 다이얼로그플로우를 쓸 것 같다.)
## 아키텍쳐
일단 챗봇의 아키텍쳐는 대부분 아래와 같은 구조로 되어 있다.
<img src="https://miro.medium.com/max/3004/1*0JqMq7W9ndcOmL3UQ5lPhQ.png" />
1. 사용자가 입력한 문장을 `NLU(자연어처리유닛)` 가 받아서 적절한 처리를 한 뒤에
2. 적절한 `Intent(의도)`를 찾아낸다. 만약 의도를 찾을 수 없다면 `FallbackIntent` 로 처리된다.
3. 다이얼로그 매니저는 사용자의 의도를 처리하기 위해 필요한 정보들을 다시 사용자로부터 입력받는다. 이때 필요한 정보를 보통 `Slot` 이라고 부른다. (위 그림에서는 Entity)
4. 의도를 처리하기 위한 슬롯들이 다 채워졌다면(fulfilled)
5. 필요에 따라 사용자로부터 최종적으로 확인을 받거나, 그냥 의도를 종료처리한다.
그리고 Lex 는 다음과 같은 구조로 되어 있다.
<img src="https://media.amazonwebservices.com/blog/2016/lex_main_page_2.png"/>
- Intent
- Utterances
- Slots (and SlotTypes)
- Prompts
- Fulfillment
Lex 는 한글이 안되서 써본사람은 별로 없겠지만, 대략 위에서 설명한 챗봇 아키텍쳐랑 크게 다르지 않은 구조를 가진다.
## 구현설명
코드의 구조는 Lex 의 흐름을 그대로 가져다 만들려고 했기 때문에 코드 자체를 설명할 건 별로 없다.
그래서 본 글에서는 코드에 대한 모든 설명보다 주요 컴포넌트의 구현방향과 개선방향을 간단히 적어본다.
### nlu.py & dialog.py
NLU는 사용자의 입력테스트와 인텐트의 예제텍스트들간 유사도를 측정할 수 있도록 자연어를 피쳐로 변환해준다.
자연어처리는 다양한 방법으로 구현할 수 있지만, 프로토타이핑 정도로 만들거기 때문에 여기서는 정확도를 희생하고 가장 쉬워보이는 방법으로 구현했다.
현재 구현 형태는 아래와 같은데, huggingface 의 기학습된 kogpt2 언어모델을 그대로 사용했다.
intent 는 대략 이렇게 생겼다.
```yaml
intents:
- name: flower
utterances:
- 꽃을 사고 싶습니다
- 꽃을 사고 싶다
- 꽃 내놔
- 꽃이 필요해
- 플라워가 필요해
- 플라워를 사고 싶다
fulfill_prompt: '감사합니다. 주문이 완료되었습니다.'
reject_prompt: '아쉽군요. 꽃 주문을 취소하겠습니다.'
```
이 인텐트를 처리하기 위해 사용자의 입력문장을 매핑하는 과정은 다음과 같다.
0. Intent 에 미리 입력된 utternaces 을 언어모델에 넣고 다음 단어들을 예측해서 가지고 있는다.
1. 사용자 입력문장을 언어모델에 넣고 다음 단어들을 예측한다.
2. Intent 의 utternaces 로 예측된 단어들과 사용자 입력문장으로 예측된 단어들을 cosine_similarity 를 이용하여 유사도를 측정한다.
3. threshold 이상의 유사도를 보이면 입력문장을 해당 Intent 로 분류한다.
단순직관을 이용한 아이디어이기 때문에 정확도가 높지 않겠지만, 언어모델이 아니라 QA 모델을 쓰거나 언어모델에 도메인 데이터를 더 넣어주면 정확해질지도 모르겠다.
NSMC 처럼 인텐트 별로 파인튜닝된 모델을 사용하면 정확도가 훨씬 높아 질 것이다.(인텐트 분류기처럼 동작하도록) 하지만 Lex는 파인튜닝 과정이 없이 인텐트를 잘 잡아낸다.
임의의 인텐트를 쉽게 추가하려면 언어모델을 사용했으리라고 추측했고, 언어모델을 그대로 사용해보니 봐줄만하게 동작하는 것 같았다.
제대로 품을 들여서 만든다면 KoNLPy 등으로 핵심명사를 먼저 뽑아내고
(다이얼로그 특성상 처음 보는 단어는 없다고 가정할 수 있다. 정확히는 처리하지 않는다고 할 수 있지만..)
해당 명사와 동의어를 찾아내서 동의어들도 처리하게 해주는 것이 좋을 것이다.
이 부분도 역시 GPT2를 NER 로 파인튜닝해서 사용할 수 있다.
그리고 사용자의 동사가 트리거 동사들(꽃 구매의 경우 사다, 보다)일 경우에 해당 인텐트를 시작해주는 식으로 동사도 함께 볼 수 있다.(stemming 을 해줘야 할 것 같다.)
### slot.py & slot_type.py
인텐트를 처리하기 위해 필요한 정보를 정의하는 것이 슬롯(Slot)이고 이 슬롯의 값을 정의하는 것이 슬롯타입(SlotType)이다.
슬롯과 슬롯타입은 아래와 같이 생겼다.
```yaml
slots:
- intent_name: flower
values:
- name: kinds
type: flower_kinds
prompt: "무슨 종류의 꽃을 사고 싶으신가요?"
- name: pickup_date
type: date
prompt: "몇월 며칠에 {kinds} 을(를) 픽업하실 건가요?"
- name: pickup_time
type: time
prompt: "{pickup_date} 몇시 몇분에 {kinds} 을(를) 픽업하실 건가요?"
- name: confirm
type: confirm
prompt: "좋습니다. {pickup_date} {pickup_time}에 {kinds} 꽃을 준비해두면 될까요?"
----
slot_types:
- name: flower_kinds
values:
- 장미
- 백합
- 할미꽃
```
Lex 에서는 2종류의 슬롯타입을 지원한다.
1. 사용자가 값을 지정해두고 해당 값들에 매핑하는 커스텀 슬롯타입
2. `Amazon.DATES` 같은 형태로 빌트인 슬롯타입
위의 `flower_kinds` 는 커스텀 슬롯타입이고, `date`, `time` 은 빌트인 슬롯타입이라고 볼 수 있다.
커스텀 슬롯타입의 경우 대충 만들어서 현재는 완전 일치하지 않으면 해당 슬롯을 다시 채우게 시도하는데, Lex 의 경우처럼 대략 일치하면 채워지게끔 고쳐도 좋을 것 같다.
빌트인 슬롯타입도 대충 만들었는데, 제대로 만들면 훨씬 정교하고 예외에 강건하게 만들 수 있을 것이다.
## 람다에서 돌려보기
코드의 *README.md* 에 적어두었지만 람다에서 돌려볼 수 있다.
도커이미지는 대략 4G 정도 나오는데 GPT2 모델크기가 커서 그렇다.
(3GB 램 기준으로 첫 호출은 20초 후반에서 30초이상 걸릴때도 있다. 메모리를 크게 할당하든, 모델을 좀 작은걸 쓰든, 프로비전컨커런시를 걸어서 쓰든, 비동기로만 쓰든 해야할 것 같다..)
## 마치며
NLP 를 이번에 처음 공부한거라 NLP 모델을 쓰면서 익숙해질 겸 한번 챗봇을 만들어봤는데 만들다보니
NLP 모델보다 그냥 코딩이 많아졌다...
----
[^1]: [Tiny Lex](https://github.com/haandol/tiny-lex) | 25.792208 | 108 | 0.682528 | kor_Hang | 1.00001 |
d58300b2b42da4c7d8ec31958ef2d590b558f3bd | 4,263 | md | Markdown | README.md | noblesamurai/knex-log | 1979bd9e572e977a3e28f547e36bd0ef3d78b555 | [
"BSD-3-Clause"
] | null | null | null | README.md | noblesamurai/knex-log | 1979bd9e572e977a3e28f547e36bd0ef3d78b555 | [
"BSD-3-Clause"
] | null | null | null | README.md | noblesamurai/knex-log | 1979bd9e572e977a3e28f547e36bd0ef3d78b555 | [
"BSD-3-Clause"
] | 1 | 2018-01-20T11:45:19.000Z | 2018-01-20T11:45:19.000Z | # Knex-log [](http://travis-ci.org/noblesamurai/knex-log) [](http://badges.enytc.com/for/npm/knex-log)
> Implementation of a log using knex.
## Purpose
Implementation of [abstract-log](github.com/eugeneware/abstract-log) using [knex](knexjs.org).
## Usage
```js
const knex = {/* your knex instance */};
const knexLog = require('knex-log')(knex, { tableName: 'tableName' });
```
Now use it like [abstract-log](github.com/eugeneware/abstract-log).
## API
cf [abstract-log](github.com/eugeneware/abstract-log).
<a name="module_knex-log"></a>
## knex-log
- config.tableName - The table which logs are found in.
- config.columnName - The column which logs are found in.
| Param | Type | Description |
| --- | --- | --- |
| knex | <code>Knex</code> | knex instance to use, passed in... |
| config | <code>object</code> | |
* [knex-log](#module_knex-log)
* [~open()](#module_knex-log..open)
* [~close()](#module_knex-log..close)
* [~append(payload)](#module_knex-log..append)
* [~get(offset)](#module_knex-log..get) ⇒ <code>object</code>
* [~createWriteStream()](#module_knex-log..createWriteStream)
* [~createReadStream()](#module_knex-log..createReadStream)
<a name="module_knex-log..open"></a>
### knex-log~open()
**Kind**: inner method of [<code>knex-log</code>](#module_knex-log)
<a name="module_knex-log..close"></a>
### knex-log~close()
Call this when done.
**Kind**: inner method of [<code>knex-log</code>](#module_knex-log)
<a name="module_knex-log..append"></a>
### knex-log~append(payload)
**Kind**: inner method of [<code>knex-log</code>](#module_knex-log)
| Param | Type |
| --- | --- |
| payload | <code>object</code> |
<a name="module_knex-log..get"></a>
### knex-log~get(offset) ⇒ <code>object</code>
**Kind**: inner method of [<code>knex-log</code>](#module_knex-log)
**Returns**: <code>object</code> - value
| Param | Type |
| --- | --- |
| offset | <code>integer</code> |
<a name="module_knex-log..createWriteStream"></a>
### knex-log~createWriteStream()
Create a write stream that we can use to append to the log.
**Kind**: inner method of [<code>knex-log</code>](#module_knex-log)
<a name="module_knex-log..createReadStream"></a>
### knex-log~createReadStream()
- opts.offset.id - The id to read from
**Kind**: inner method of [<code>knex-log</code>](#module_knex-log)
**Params**: <code>object</code> opts
## Installation
This module is installed via npm:
``` bash
$ npm install knex-log
```
## Contributing
### Prerequisites
```
$ pip install pre-commit
```
### Installation
```
$ pre-commit install --install-hooks
```
## License
The BSD License
Copyright (c) 2017, Tim Allen
All rights reserved.
Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this
list of conditions and the following disclaimer in the documentation and/or
other materials provided with the distribution.
* Neither the name of the Tim Allen nor the names of its
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
| 30.45 | 254 | 0.712175 | kor_Hang | 0.360262 |
d583356bd354fd4803d7dcb7ca2419c767a55f41 | 4,444 | md | Markdown | DE-290.md | hagbeck/Abdeckung-mit-RVK-Notationen-via-CultureGraph | f314c16bdecc62412f89822a26dc53af3b4c7814 | [
"CC-BY-4.0"
] | null | null | null | DE-290.md | hagbeck/Abdeckung-mit-RVK-Notationen-via-CultureGraph | f314c16bdecc62412f89822a26dc53af3b4c7814 | [
"CC-BY-4.0"
] | null | null | null | DE-290.md | hagbeck/Abdeckung-mit-RVK-Notationen-via-CultureGraph | f314c16bdecc62412f89822a26dc53af3b4c7814 | [
"CC-BY-4.0"
] | null | null | null | ## Vorkommen der Bestandsdatensätze in CultureGraph
(CG-Bundles = Bündel von Datensätzen aus den Bibliotheksverbünden, die nach CultureGraph (CG) zusammengehören)
Manifestationen:
* 1.110.368 Manifestationen ohne Zeitschriften
* 880.301 Manifestationen ohne Zeitschriften in CG-Bundles
* 230.067 Manifestationen ohne Zeitschriften ohne CG-Bundle
Exemplare:
* 1.050.233 Exemplare
* 877.397 Exemplare in CG-Bundles
* 172.836 Exemplare ohne CG-Bundle
**Frage:** Wie kann es sein, dass die Exemplare weniger sind als die Manifestationen?
**Antwort:** Unter den Manifestationen gibt es auch E-Books, die keine Exemplardaten haben. Andererseits gibt es Manifestationen, die mehr als ein Exemplar haben. Daher ist ein direkter Vergleich der Zahlen nicht sinnvoll.
## Medientyp-Verteilung der Manifestationen mit Exemplaren
| **Medientyp** | **Titel** | **CG-Bündel** | **RVK** | **Anteil** |
| ------------------------------------------------------------ | ---------- | ---------- | ---------- | ----------- |
| **Monographie (Code m)** | 476.752 | 465.395 | 418.961 | **87,88 %** |
| **Teil einer Serie (Code s)** | 294.981 | 287.545 | 268.025 | **90,86 %** |
| **Teil einer mehrteiligen Monographie (Code B)** | 129.456 | 9 | 9 | **0,01 %** |
| **Mehrteilige Monographie - nicht Teil einer Reihe oder Teil einer gezählten Reihe (Code n)** | 598 | 0 | 0 | **0,00 %** |
| **Unselbständig erschienenes Werk (Code a)** | 124 | 39 | 17 | **13,71 %** |
| **Mehrteilige Monographie - Teil einer gezählten Reihe (Code t)** | 109 | 0 | 0 | **0,00 %** |
| **Integrierende Ressource (Code i)** | 1 | 0 | 0 | **0,00 %** |
| | **902.021** | **752.988** | **687.012** | **76,16 %** |
## Medientyp-Verteilung der Manifestationen ohne Exemplare
| **Medientyp** | **Titel** | **CG-Bündel** | **RVK** | **Anteil** |
| ------------------------------------------------------------ | ---------- | ---------- | ---------- | ----------- |
| **Monographie (Code m)** | 119.336 | 91.637 | 72.732 | **60,95 %** |
| **Teil einer Serie (Code s)** | 41.112 | 35.645 | 32.379 | **78,76 %** |
| **Mehrteilige Monographie - nicht Teil einer Reihe oder Teil einer gezählten Reihe (Code n)** | 39.773 | 20 | 13 | **0,03 %** |
| **Mehrteilige Monographie - Teil einer gezählten Reihe (Code t)** | 5.143 | 5 | 4 | **0,08 %** |
| **Teil einer mehrteiligen Monographie (Code B)** | 2.552 | 0 | 0 | **0,00 %** |
| **Integrierende Ressource (Code i)** | 347 | 0 | 0 | **0,00 %** |
| **Unselbständig erschienenes Werk (Code a)** | 84 | 6 | 2 | **2,38 %** |
| | **208.347** | **127.313** | **105.130** | **50,46 %** |
# RVK-Potential via CultureGraph
## ... über den Gesamtbestand
792.142 von 1.110.368 (71,34%) Manifestationen
## ... über die Standortverteilung
| **Standort** | **Manifestationen** | **mit RVK** | **Anteil** | **Anteil erste Erhebung** |
| --------------- | ------- | ------- | ------- | ------- |
| Zentralbibliothek (ZB, DE-290-0) | 673.181 | 513.843 | 76,33 % | 66,61 % |
| Bereichsbibliothek Raumplanung (BR, DE-290-9) | 38.168 | 27.179 | 71,21 % | 57,79 % |
| Bereichsbibliothek Bauwesen und Architektur (BAB, DE-290-10) | 24.371 | 18.023 | 73,95 % | 65,40 % |
| Emil-Figge-Bibliothek (EFB, DE-290-12) | 220.589 | 174.104 | 78,93 % | 80,32 % |
## ... über die Fachverteilung
* [Zentralbibliothek (ZB)](DE-290-0.md)
* [Bereichsbibliothek Raumplanung (BR)](DE-290-9.md)
* [Bereichsbibliothek Bauwesen und Architektur (BAB)](DE-290-10.md)
* [Emil-Figge-Bibliothek (EFB)](DE-290-12.md)
---
This work is licensed under a [Creative Commons Attribution 4.0 International License](https://creativecommons.org/licenses/by/4.0/).
| 61.722222 | 222 | 0.494824 | deu_Latn | 0.796966 |
d583549d8df1921fed42fe4353ff5424ecc86537 | 243 | md | Markdown | README.md | bv42/holiday_reminder | a417cffe086a73c9ae456a6134ef09b6e748a091 | [
"MIT"
] | 1 | 2020-11-18T05:58:10.000Z | 2020-11-18T05:58:10.000Z | README.md | bv42/holiday_reminder | a417cffe086a73c9ae456a6134ef09b6e748a091 | [
"MIT"
] | null | null | null | README.md | bv42/holiday_reminder | a417cffe086a73c9ae456a6134ef09b6e748a091 | [
"MIT"
] | null | null | null | # Holiday Reminder
Remind me about holidays around the word. Get a notification if there is a public holiday in some place in the world
you are interested in.
## Routes
```
/ hello world
/holidays display some data
``` | 22.090909 | 117 | 0.683128 | eng_Latn | 0.998653 |
d5839bf2bb1725ef374622b9a80f43b359278e24 | 65 | md | Markdown | README.md | spromtet/BeWaterAPI | bfef6981bba69b6da234697f72434dc7370211e7 | [
"MIT"
] | null | null | null | README.md | spromtet/BeWaterAPI | bfef6981bba69b6da234697f72434dc7370211e7 | [
"MIT"
] | null | null | null | README.md | spromtet/BeWaterAPI | bfef6981bba69b6da234697f72434dc7370211e7 | [
"MIT"
] | null | null | null | # BeWaterAPI
Instant CRUD API using Express & PostGres NOSQL
| 21.666667 | 51 | 0.8 | kor_Hang | 0.669537 |
d583cbedf87c244c5f3656e0d25da023c7353f66 | 127 | md | Markdown | README.md | dm-istomin/practice-apps | 266073beff5998b74400d97d9238cb57f4767bef | [
"MIT"
] | null | null | null | README.md | dm-istomin/practice-apps | 266073beff5998b74400d97d9238cb57f4767bef | [
"MIT"
] | null | null | null | README.md | dm-istomin/practice-apps | 266073beff5998b74400d97d9238cb57f4767bef | [
"MIT"
] | null | null | null | # Practice Apps
A collection of applications to play around with new tech. Will probably be Node and ES6-focused for a while.
| 31.75 | 109 | 0.787402 | eng_Latn | 0.999208 |
d584760925452c01e3926483b3b61e3627db6062 | 1,163 | md | Markdown | README.md | px-sama/Movie_Recommendation | 70de6cefc8e678193af0ed7c26ecbad379f869ed | [
"MIT"
] | null | null | null | README.md | px-sama/Movie_Recommendation | 70de6cefc8e678193af0ed7c26ecbad379f869ed | [
"MIT"
] | null | null | null | README.md | px-sama/Movie_Recommendation | 70de6cefc8e678193af0ed7c26ecbad379f869ed | [
"MIT"
] | null | null | null | # Movie Recommendation
## Project from Python for Data Science and Machine Learning Bootcamp
## Methods Used
Two most common types of recommender systems are **Content-Based** and **Collaborative Filtering (CF)**.
* Collaborative filtering produces recommendations based on the knowledge of users’ attitude to items, that is it uses the "wisdom of the crowd" to recommend items.
* Content-based recommender systems focus on the attributes of the items and give you recommendations based on the similarity between them.
## Collaborative Filtering
In general, Collaborative filtering (CF) is more commonly used than content-based systems because it usually gives better results and is relatively easy to understand (from an overall implementation perspective). The algorithm has the ability to do feature learning on its own, which means that it can start to learn for itself what features to use.
CF can be divided into **Memory-Based Collaborative Filtering** and **Model-Based Collaborative filtering**.
In this project, we will implement Model-Based CF by using singular value decomposition (SVD) and Memory-Based CF by computing cosine similarity.
| 64.611111 | 350 | 0.798796 | eng_Latn | 0.999319 |
d5854dafbdb240c1c8407eb39260c15b5ef4dae0 | 904 | md | Markdown | docs/csharp/misc/cs1633.md | mattia-lunardi/docs.it-it | b9909895e77ae22ac89a7cc8dc6ea289e49ce0b3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/csharp/misc/cs1633.md | mattia-lunardi/docs.it-it | b9909895e77ae22ac89a7cc8dc6ea289e49ce0b3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/csharp/misc/cs1633.md | mattia-lunardi/docs.it-it | b9909895e77ae22ac89a7cc8dc6ea289e49ce0b3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Avviso del compilatore (livello 1) CS1633
ms.date: 07/20/2015
f1_keywords:
- CS1633
helpviewer_keywords:
- CS1633
ms.assetid: f31db218-f880-4fc4-ab34-8bcdc49011da
ms.openlocfilehash: d2bd6f2f6ce749bf1bfa08bb858c4dcb79fd9a51
ms.sourcegitcommit: 3d5d33f384eeba41b2dff79d096f47ccc8d8f03d
ms.translationtype: HT
ms.contentlocale: it-IT
ms.lasthandoff: 05/04/2018
ms.locfileid: "33304830"
---
# <a name="compiler-warning-level-1-cs1633"></a>Avviso del compilatore (livello 1) CS1633
La direttiva #pragma non è stata riconosciuta
Il pragma usato non corrisponde a uno dei pragma noti supportati dal compilatore C#. Per risolvere questo errore, usare solo i pragma supportati.
L'esempio seguente genera l'errore CS1633:
```csharp
// CS1633.cs
// compile with: /W:1
#pragma unknown // CS1633
class C
{
public static void Main()
{
}
}
```
| 25.828571 | 148 | 0.728982 | ita_Latn | 0.750032 |
d58572eb30118d0e7dcf0e5fd805938e150521f7 | 4,341 | md | Markdown | docusaurus/website/i18n/fr/docusaurus-plugin-content-docs/current/questions/range.md | isle-project/isle-editor | 45a041571f723923fdab4eea2efe2df211323655 | [
"Apache-2.0"
] | 9 | 2019-08-30T20:50:27.000Z | 2021-12-09T19:53:16.000Z | docusaurus/website/i18n/fr/docusaurus-plugin-content-docs/current/questions/range.md | isle-project/isle-editor | 45a041571f723923fdab4eea2efe2df211323655 | [
"Apache-2.0"
] | 1,261 | 2019-02-09T07:43:45.000Z | 2022-03-31T15:46:44.000Z | docusaurus/website/i18n/fr/docusaurus-plugin-content-docs/current/questions/range.md | isle-project/isle-editor | 45a041571f723923fdab4eea2efe2df211323655 | [
"Apache-2.0"
] | 3 | 2019-10-04T19:22:02.000Z | 2022-01-31T06:12:56.000Z | ---
id: range-question
title: Range Question
sidebar_label: Range Question
---
Un élément de question de gamme qui demande aux élèves de fournir un point d'extrémité inférieur et supérieur.
## Options
* __question__ | `(string|node)`: question affichée. Default: `''`.
* __solution__ | `array<number>`: tableau à deux éléments contenant les points terminaux de la plage correcte. Default: `none`.
* __hintPlacement__ | `string`: l'emplacement des indices (soit `top`, `left`, `right` ou `bottom`). Default: `'top'`.
* __hints__ | `array<(string|node)>`: des conseils sur la façon de répondre à la question. Default: `[]`.
* __labels__ | `array`: un ensemble à deux éléments d'étiquettes personnalisées autres que `bottom` et "Haut de page. Default: `none`.
* __feedback__ | `boolean`: contrôle l'affichage des boutons de rétroaction. Default: `true`.
* __chat__ | `boolean`: contrôle si l'élément doit avoir un chat intégré. Default: `false`.
* __digits__ | `number`: nombre de chiffres qui doivent correspondre entre la solution et la réponse fournie par l'utilisateur. S'il n'est pas donné ou s'il est fixé à zéro, le composant vérifie la stricte égalité. S'il est défini à 0, il vérifie l'égalité des nombres entiers. Default: `3`.
* __max__ | `number`: valeur maximale d'entrée. Default: `null`.
* __min__ | `number`: valeur d'entrée minimale. Default: `null`.
* __provideFeedback__ | `boolean`: indique si un retour d'information comprenant la bonne réponse doit être affiché après que les apprenants aient soumis leurs réponses. Default: `true`.
* __allowMultipleAnswers__ | `boolean`: contrôle si l'on peut soumettre des réponses multiples. Default: `false`.
* __until__ | `Date`: le temps nécessaire pour permettre aux étudiants de soumettre des réponses. Default: `none`.
* __points__ | `number`: nombre maximum de points attribués dans le classement. Default: `10`.
* __style__ | `object`: Styles CSS en ligne. Default: `{}`.
* __onChangeLower__ | `function`: rappel déclenché après la modification de la limite inférieure par l'utilisateur. Default: `onChangeLower() {}`.
* __onChangeUpper__ | `function`: rappel déclenché après la modification de la limite supérieure par l'utilisateur. Default: `onChangeUpper() {}`.
* __onSubmit__ | `function`: rappel invoqué lors de la soumission de la réponse ; a comme premier paramètre un "booléen" indiquant si la réponse a été correctement donnée (le cas échéant, "nul" sinon) et la réponse fournie comme second paramètre. Default: `onSubmit() {}`.
## Exemples
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';
<Tabs
defaultValue="minimal"
values={[
{ label: 'Minimal', value: 'minimal' },
{ label: 'With Hints', value: 'withHints' },
{ label: 'With Style', value: 'withStyle' },
{ label: 'With Points and Feedback', value: 'withPoints' }
]}
lazy
>
<TabItem value="minimal">
```jsx live
<RangeQuestion
style={{ fontSize: 17, }}
question="What year did the Thirty Years War broke out and when did it?"
solution={[1618,1648]}
labels={['Start', 'End']}
min={1500}
max={2000}
/>
```
</TabItem>
<TabItem value="withHints">
```jsx live
<RangeQuestion
question="What year did the Thirty Years War broke out and when did it?"
solution={[1618,1648]}
labels={['Start', 'End']}
min={1500}
max={2000}
hints={['all this happened in the 17th century', 'it ended with the Peace of Westphalia in 1648']}
/>
```
</TabItem>
<TabItem value="withStyle">
```jsx live
<RangeQuestion
style={{ fontFamily: 'Georgia', boxShadow: '0 0 10px darkblue'}}
question="What year did the Thirty Years War broke out and when did it?"
solution={[1618,1648]}
labels={['Start', 'End']}
min={1500}
max={2000}
/>
```
</TabItem>
<TabItem value="withPoints">
```jsx live
<RangeQuestion
question="What year did the Thirty Years War broke out and when did it?"
solution={[1618,1648]}
labels={['Start', 'End']}
min={1500}
max={2000}
hints={['all this happened in the 17th century', 'it ended with the Peace of Westphalia in 1648']}
points={20}
onSubmit={(res) => {
if (res === true) {
alert('Great, you have received 20 points');
}
else alert('sorry, this answer was wrong');
}}
/>
```
</TabItem>
</Tabs>
| 37.422414 | 291 | 0.68763 | fra_Latn | 0.737606 |
d585d91726d028508f87623e28bc63fd83b289ef | 8,268 | md | Markdown | desktop-src/WinAuto/uiauto-usingiaccessibleex.md | citelao/win32 | bf61803ccb0071d99eee158c7416b9270a83b3e4 | [
"CC-BY-4.0",
"MIT"
] | 552 | 2019-08-20T00:08:40.000Z | 2022-03-30T18:25:35.000Z | desktop-src/WinAuto/uiauto-usingiaccessibleex.md | citelao/win32 | bf61803ccb0071d99eee158c7416b9270a83b3e4 | [
"CC-BY-4.0",
"MIT"
] | 1,143 | 2019-08-21T20:17:47.000Z | 2022-03-31T20:24:39.000Z | desktop-src/WinAuto/uiauto-usingiaccessibleex.md | citelao/win32 | bf61803ccb0071d99eee158c7416b9270a83b3e4 | [
"CC-BY-4.0",
"MIT"
] | 1,287 | 2019-08-20T05:37:48.000Z | 2022-03-31T20:22:06.000Z | ---
title: Adding UI Automation Functionality to Active Accessibility Servers
description: Controls that do not have a Microsoft UI Automation provider but that implement IAccessible can easily be upgraded to provide some UI Automation functionality, by implementing the IAccessibleEx interface.
ms.assetid: 7ceab704-3e02-4550-b236-748e4f0a092a
keywords:
- UI Automation,Active Accessibility servers
- UI Automation,Microsoft Active Accessibility servers
- UI Automation,IAccessible
- UI Automation,IAccessibleEx
- UI Automation,exposing IAccessibleEx
- UI Automation,implementing IAccessibleEx
- IAccessible
- IAccessibleEx
- Microsoft Active Accessibility
- Active Accessibility
- exposing IAccessibleEx
- implementing IAccessibleEx
ms.topic: article
ms.date: 05/31/2018
---
# Adding UI Automation Functionality to Active Accessibility Servers
Controls that do not have a Microsoft UI Automation provider but that implement [**IAccessible**](/windows/desktop/api/oleacc/nn-oleacc-iaccessible) can easily be upgraded to provide some UI Automation functionality, by implementing the [**IAccessibleEx**](/windows/desktop/api/UIAutomationCore/nn-uiautomationcore-iaccessibleex) interface. This interface enables the control to expose UI Automation properties and control patterns, without the need for a full implementation of UI Automation provider interfaces such as [**IRawElementProviderFragment**](/windows/desktop/api/UIAutomationCore/nn-uiautomationcore-irawelementproviderfragment). To implement **IAccessibleEx**, the baseline Microsoft Active Accessibility object hierarchy must contain no errors or inconsistencies (such as a child object whose parent object does not list it as a child), and must not conflict with UI Automation specifications. If the Microsoft Active Accessibility object hierarchy meets these requirements, it is a good candidate for adding functionality by using **IAccessibleEx**; otherwise, you must implement UI Automation alone or alongside the Microsoft Active Accessibility implementation.
Take the case of a custom control that has a range value. The Microsoft Active Accessibility server for the control defines its role, and is able to return its current value, but lacks the means to return the minimum and maximum values of the control, because these properties are not defined in Microsoft Active Accessibility. A UI Automation client is able to retrieve the control's role, current value, and other Microsoft Active Accessibility properties, because the UI Automation core can obtain these through [**IAccessible**](/windows/desktop/api/oleacc/nn-oleacc-iaccessible). However, without access to an [**IRangeValueProvider**](/windows/desktop/api/UIAutomationCore/nn-uiautomationcore-irangevalueprovider) interface on the object, UI Automation is also unable to retrieve the maximum and minimum values.
The control developer could supply a complete UI Automation provider for the control, but this would mean duplicating much of the existing functionality of the [**IAccessible**](/windows/desktop/api/oleacc/nn-oleacc-iaccessible) implementation: for example, navigation and common properties. Instead, the developer can continue to rely on **IAccessible** to supply this functionality, while adding support for control-specific properties through [**IRangeValueProvider**](/windows/desktop/api/UIAutomationCore/nn-uiautomationcore-irangevalueprovider).
Updating the custom control requires these main steps:
- Implement [IServiceProvider](/previous-versions/windows/internet-explorer/ie-developer/platform-apis/cc678965(v=vs.85)) on the accessible object so that the [**IAccessibleEx**](/windows/desktop/api/UIAutomationCore/nn-uiautomationcore-iaccessibleex) interface can be found on this or a separate object.
- Implement [**IAccessibleEx**](/windows/desktop/api/UIAutomationCore/nn-uiautomationcore-iaccessibleex) on the accessible object.
- Create distinct accessible objects for any Microsoft Active Accessibility child items, which in Microsoft Active Accessibility might have been represented by the [**IAccessible**](/windows/desktop/api/oleacc/nn-oleacc-iaccessible) interface on the parent object (for example, list items). Implement [**IAccessibleEx**](/windows/desktop/api/UIAutomationCore/nn-uiautomationcore-iaccessibleex) on these objects.
- Implement [**IRawElementProviderSimple**](/windows/desktop/api/UIAutomationCore/nn-uiautomationcore-irawelementprovidersimple) on all the accessible objects.
- Implement the appropriate control pattern interfaces on the accessible objects.
This topic contains the following sections.
- [Exposing IAccessibleEx](#exposing-iaccessibleex)
- [Implementing IAccessibleEx](#implementing-iaccessibleex)
- [Related topics](#related-topics)
## Exposing IAccessibleEx
Because the implementation of [**IAccessibleEx**](/windows/desktop/api/UIAutomationCore/nn-uiautomationcore-iaccessibleex) for a control may reside in a separate object, client applications cannot rely on [**QueryInterface**](/windows/desktop/api/unknwn/nf-unknwn-iunknown-queryinterface(q)) to obtain this interface. Instead, clients are expected to call [**IServiceProvider::QueryService**](/previous-versions/windows/internet-explorer/ie-developer/platform-apis/cc678966(v=vs.85)). In the following example implementation of this method, it is assumed that **IAccessibleEx** is not implemented on a separate object; therefore the method simply calls through to **QueryInterface**.
```C++
HRESULT CListboxAccessibleObject::QueryService(REFGUID guidService, REFIID riid, LPVOID *ppvObject)
{
if (!ppvObject)
{
return E_INVALIDARG;
}
*ppvObject = NULL;
if (guidService == __uuidof(IAccessibleEx))
{
return QueryInterface(riid, ppvObject);
}
else
{
return E_INVALIDARG;
}
};
```
## Implementing IAccessibleEx
The method of [**IAccessibleEx**](/windows/desktop/api/UIAutomationCore/nn-uiautomationcore-iaccessibleex) that is of most interest is [**GetObjectForChild**](/windows/desktop/api/UIAutomationCore/nf-uiautomationcore-iaccessibleex-getobjectforchild). This method gives the Microsoft Active Accessibility server an opportunity to create an accessible object (one that exposes, at a minimum, **IAccessibleEx**) for a child item. In Microsoft Active Accessibility, child items typically are not represented as accessible objects but as children of an accessible object. However, because UI Automation requires that each element be represented by a separate accessible object, **GetObjectForChild** must create a separate object for each child on demand.
The following example implementation returns an accessible object for an item in a custom list view.
```C++
HRESULT CListboxAccessibleObject::GetObjectForChild(long idChild, IAccessibleEx **pRetVal)
{
*pRetVal = NULL;
VARIANT vChild;
vChild.vt = VT_I4;
vChild.lVal = idChild;
// ValidateChildId is an application-defined function that checks whether
// the child ID is valid. This is similar to code that validates the varChild
// parameter in IAccessible methods.
//
// Additionally, if this idChild corresponds to a child that has its own
// IAccessible, we should also return E_INVALIDARG here. (The caller
// should instead be using the IAccessibleEx from that child's own
// IAccessible in that case.)
if (idChild == CHILDID_SELF || FAILED(ValidateChildId(vChild)))
{
return E_INVALIDARG;
}
// Return a suitable provider for this specific child.
// This implementation returns a new instance each time; an implementation
// can cache these if desired.
// _pListboxControl is a member variable pointer to the owning control.
IAccessibleEx* pAccEx = new CListItemAccessibleObject(idChild, _pListboxControl);
if (pAccEx == NULL)
{
return E_OUTOFMEMORY;
}
*pRetVal = pAccEx;
return S_OK;
}
```
For a complete sample implementation, see [Making Custom Controls Accessible, Part 5: Using IAccessibleEx to Add UI Automation Support to a Custom Control](/previous-versions/msdn10/cc307850(v=msdn.10)) on MSDN.
## Related topics
<dl> <dt>
[UI Automation Provider Programmer's Guide](uiauto-providerportal.md)
</dt> </dl>
| 65.619048 | 1,179 | 0.789066 | eng_Latn | 0.837553 |
d585e5f1362c08874bb72af0921285c45ec7d9c1 | 176 | md | Markdown | deployments/README.md | droxey/makefeedback | ca906d813ef775476d3e9841c6fa7a15f40e49f9 | [
"MIT"
] | 2 | 2019-01-22T21:38:29.000Z | 2019-04-15T09:34:15.000Z | deployments/README.md | droxey/makefeedback | ca906d813ef775476d3e9841c6fa7a15f40e49f9 | [
"MIT"
] | null | null | null | deployments/README.md | droxey/makefeedback | ca906d813ef775476d3e9841c6fa7a15f40e49f9 | [
"MIT"
] | null | null | null | # `/deployments`
IaaS, PaaS, system and container orchestration deployment configurations and templates (`docker-compose`, `kubernetes`/`helm`, `mesos`, `terraform`, `bosh`).
| 44 | 157 | 0.744318 | eng_Latn | 0.692562 |
d586460203c184aa67d8ede8e4681d3f22140190 | 4,207 | md | Markdown | _posts/2021-07-20-Docker - docker compose.md | wooody92/wooody92.github.io | 239d957bd4c024db2a5cd7d89d2bc9f6a5cfd385 | [
"MIT"
] | 1 | 2020-07-07T13:00:20.000Z | 2020-07-07T13:00:20.000Z | _posts/2021-07-20-Docker - docker compose.md | wooody92/wooody92.github.io | 239d957bd4c024db2a5cd7d89d2bc9f6a5cfd385 | [
"MIT"
] | null | null | null | _posts/2021-07-20-Docker - docker compose.md | wooody92/wooody92.github.io | 239d957bd4c024db2a5cd7d89d2bc9f6a5cfd385 | [
"MIT"
] | null | null | null | ---
title: "Docker - docker compose"
excerpt: "도커 컴포즈 docker-compose"
header:
categories:
- Docker
tags:
- Docker
- docekr compose
last_modified_at: 2021-07-20. 18:30:00
---
<br>
# Docker
## 도커 컴포즈 (docker compose)
> 도커 컴포즈의 기본 명령어와 문법을 이해한다.
### 개요
- 도커 컴포즈의 기본 명령어와 문법에 대해 이해한다.
### 도커 컴포즈 설치
```
docker-compose version
```
- Mac의 경우 Docker for Mac으로 설치 시 docker compose도 기본적으로 설치된다. (리눅스의 경우 별도로 설치가 필요)
### 실습 예제
```yaml
version: '2'
services:
db:
image: mysql:5.7
volumes:
- ./mysql:/var/lib/mysql
restart: always
environment:
MYSQL_ROOT_PASSWORD: wordpress
MYSQL_DATABASE: wordpress
MYSQL_USER: wordpress
MYSQL_PASSWORD: wordpress
wordpress:
image: wordpress:latest
volumes:
- ./wp:/var/www/html
ports:
- "8000:80"
restart: always
environment:
WORDPRESS_DB_HOST: db:3306
WORDPRESS_DB_PASSWORD: wordpress
```
- docker-compose.yml
- 도커 실행 명령어를 yml 파일로 스크립트 문서화 하여 관리한다.
- 도커 실행 명령어로 작성 시 발생하는 휴먼에러(띄어쓰기 등)를 줄이고 명확하게 파악 할 수 있다.
## docker-compose 기본 명령어
### 1.1 컨테이너 실행 : up
```
docker-compose up
docker-compose up -d
docker-compose up --force-recreate
docker-compose up --build
```
- 현재 디렉토리에 있는 docker-compose 파일을 실행하여, docker-compose 파일에 정의된 컨테이너를 실행한다.
- -d 옵션을 주면 daemon(백그라운드)으로 실행한다.
- --force-recreate 옵션으로 컨테이너를 새로 만들 수 있다.
- --build 옵션으로 도커 이미지를 다시 빌드한다. (build로 선언했을 때만)
### 2.1 컨테이너 종료 : down
```
docker-compose down
```
- docker-compose 파일에 정의된 컨테이너를 종료하고 삭제한다.
### 3.1 컨테이너 목록 : ps
```
docker-compose ps
```
- docker-compose로 실행중인 목록을 출력한다.
<img width="1244" alt="dc" src="https://user-images.githubusercontent.com/58318041/126296394-13e31979-25c6-4d06-9a2c-f6a6e1da48ea.png">
- docker 실행 명령어로 동작시킨 컨테이너는 docker-compose 명령어에 나타나지 않는다.
### 4.1 멈춘 컨테이너 시작 : start
```
docker-compose start
docker-compose start {service}
```
- stop으로 멈춘(PC 재부팅 등으로 멈춘) 컨테이너를 재개한다.
- 특정 서비스(예제에서는 wordpress)만 재개할 수 있다.
### 5.1 컨테이너 재시작 : restart
```
docker-compose restart
docker-compose restart {service}
```
- 컨테이너를 재시작한다.
### 6.1 컨테이너 정지 : stop
```
docker-compose stop
docker-compose stop {service}
```
- 실행중인 컨테이너를 정지한다.
### 7.1 컨테이너 로그 : logs
```
docker-compose logs
docker-compose logs -f
```
- 컨테이너의 로그를 확인하고, -f 옵션으로 로그를 follow 할 수 있다.
### 8.1 실행 중인 컨테이너에서 명령어 실행 : exec
```
docker-compose exec {service} {command}
docker-compose exec wordpress(컨테이너 이름) bash
```
- 실행 중인 컨테이너에 명령어를 실행 할 수 있다.
### 9.1 컨테이너 build 부분에 정의된 내용대로 빌드 : build
```
docker-compose build
docker-compose build {service}
```
- 컨테이너 build 부분에 정의된 내용대로 빌드한다.
## docker-compose 기본 문법
### version
```yaml
version: '3'
```
- docker-compose.yml 파일의 명세 버전이다.
- docker-compose.yml 버전에 따라 지원하는 도커 엔진 버전도 다르다.
### services
```yaml
services:
mysql:
...
django:
...
```
- 실행할 컨테이너의 이름 정의이다.
- 도커 실행 명령어의 docker run --name mysql과 같다고 생각 할 수 있다.
### image
```yaml
services:
mysql:
image: mysql:5.7
```
- 컨테이너에 사용할 이미지 이름과 태그를 정의한다.
- 태그를 생략하면 최신 버전(latest)을 가져오고, 로컬 환경에 이미지가 없으면 자동으로 pull 한다.
### ports
```yaml
services:
mysql:
...
ports:
- "3306:3306" ## "{host-port}:{container-port}"
```
- 호스트와 컨테이너의 포트 연결을 정의한다. port-fowarding
### environment
```yaml
services:
mysql:
...
environment:
- MYSQL_ROOT_PASSWORD: 1234
```
- 컨테이너에서 사용할 환경변수를 정의할 수 있다.
- {환경변수 이름} : {value}
### volumes
```yaml
services:
mysql:
...
volumes:
- ./mysql:/var/lib/mysql ## {host-directory}:{container-directory}
```
- 호스트 디렉토리와 컨테이너의 디렉토리를 마운트 할 수 있다.
- 예제에서는 현재 디렉토리 내 mysql 디렉토리로 마운트했다.
### restart
```yaml
services:
mysql:
restart: always ## "no", always, on-failure, unless-stopped
```
- 컨테이너 재시작 정책으로 "no", always, on-failure, unless-stopped 설정이 있다.
### build
```yaml
services:
mysql:
build:
context: .
dockerfile: ./compose/mysql/Dockerfile-dev
```
- 이미지를 자체 빌드 후 사용할 수 있다.
- image 속성 대신 사용하며, 여기에 사용할 별도의 도커 파일이 필요하다.
### Reference
- [subicura - 초보를 위한 도커 안내서](https://www.inflearn.com/course/%EB%8F%84%EC%BB%A4-%EC%9E%85%EB%AC%B8/dashboard)
- [https://github.com/wooody92/hello-docker/tree/main/docker](https://github.com/wooody92/hello-docker/tree/main/docker)
| 14.11745 | 135 | 0.643451 | kor_Hang | 0.999523 |
d586723d9595c179385a4e0c5203fefe97eb70c2 | 528 | md | Markdown | pages/common/nano.md | irfanirshad/tldr | ae1241967d9e66f292e669ae1f96c034da06d2f6 | [
"CC-BY-4.0"
] | 2 | 2021-07-01T08:05:51.000Z | 2021-07-02T06:45:41.000Z | pages/common/nano.md | irfanirshad/tldr | ae1241967d9e66f292e669ae1f96c034da06d2f6 | [
"CC-BY-4.0"
] | 1 | 2021-02-06T13:18:36.000Z | 2021-02-06T13:18:36.000Z | pages/common/nano.md | irfanirshad/tldr | ae1241967d9e66f292e669ae1f96c034da06d2f6 | [
"CC-BY-4.0"
] | null | null | null | # nano
> Simple, easy to use command-line text editor. An enhanced, free Pico clone.
> More information: <https://nano-editor.org>.
- Open a specific file:
`nano {{path/to/file}}`
- Open a file positioning the cursor at the specified line and column:
`nano +{{line}},{{column}} {{path/to/file}}`
- Enable smooth scrolling:
`nano -S {{filename}}`
- Indent new lines to the previous lines' indentation:
`nano -i {{filename}}`
- Before modification, backup separately as `{{current_file_name}}~`:
`nano -B {{filename}}`
| 21.12 | 77 | 0.6875 | eng_Latn | 0.782159 |
d58717490ce4dccedd5e09048162fc0abd7bc159 | 1,180 | md | Markdown | docs/Model/Creative.md | criteo/criteo-api-php-sdk | 261ea3502cce908e3787b3e1d2af84409f392d3b | [
"Unlicense"
] | null | null | null | docs/Model/Creative.md | criteo/criteo-api-php-sdk | 261ea3502cce908e3787b3e1d2af84409f392d3b | [
"Unlicense"
] | null | null | null | docs/Model/Creative.md | criteo/criteo-api-php-sdk | 261ea3502cce908e3787b3e1d2af84409f392d3b | [
"Unlicense"
] | null | null | null | # # Creative
## Properties
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**name** | **string** | The name of the creative | [optional]
**description** | **string** | The description of the creative | [optional]
**author** | **string** | The login of the person who created this creative ( | [optional]
**status** | **string** | The status of the creative | [optional]
**type** | **string** | The type of the creative | [optional]
**advertiser_id** | **string** | Advertiser linked to the Creative | [optional]
**partner_id** | **string** | Partner linked to the Creative | [optional]
**image_attributes** | [**\criteo\api\marketingsolutions\preview\Model\ImageAttributes**](ImageAttributes.md) | | [optional]
**third_party_html_attributes** | [**\criteo\api\marketingsolutions\preview\Model\ThirdPartyHtmlAttributes**](ThirdPartyHtmlAttributes.md) | | [optional]
**dynamic_attributes** | [**\criteo\api\marketingsolutions\preview\Model\DynamicAttributes**](DynamicAttributes.md) | | [optional]
[[Back to Model list]](../../README.md#models) [[Back to API list]](../../README.md#endpoints) [[Back to README]](../../README.md)
| 62.105263 | 154 | 0.659322 | eng_Latn | 0.366903 |
d5875ebc8547cd0a81f7cb1f022fd0b304439f6a | 548 | md | Markdown | src/smtrat-modules/ESModule/ESModule.md | ths-rwth/smtrat | efd83021d5b5fb0e2903b38cd3148a953a1972c0 | [
"MIT"
] | 2 | 2021-03-21T23:02:42.000Z | 2021-03-22T15:15:13.000Z | src/smtrat-modules/ESModule/ESModule.md | ths-rwth/smtrat | efd83021d5b5fb0e2903b38cd3148a953a1972c0 | [
"MIT"
] | 15 | 2021-03-16T11:00:37.000Z | 2022-02-22T14:51:57.000Z | src/smtrat-modules/ESModule/ESModule.md | ths-rwth/smtrat | efd83021d5b5fb0e2903b38cd3148a953a1972c0 | [
"MIT"
] | null | null | null | # ESModule {#ESModule}
Uses equations (or Boolean assertions) to eliminate variables from the remaining formula. Let the formula have the form \f$ e \land \varphi' \f$, then we use knowledge gained from \f$ e \f$ to simplify \f$ \varphi' \f$. If \f$ e \f$ is an arithmetic equation such that we can rewrite it to the form \f$ x = t \f$ (with \f$ x \f$ a variable) then we substitute \f$ t \f$ for \f$ x \f$ into \f$ \varphi' \f$. Otherwise we simply replace \f$ e \f$ with \f$ true \f$ in \f$ \varphi' \f$.
This is done recursively in the formula. | 137 | 483 | 0.678832 | eng_Latn | 0.99924 |
d58784c369771b2d4cea560301ba10188f62c601 | 4,829 | md | Markdown | packages/site/docs/api/Items/nodeMethods.en.md | SLin0218/G6 | 0a6f4770cb5ac6c2e830da1544327d9a8babd743 | [
"MIT"
] | 4,945 | 2017-02-26T14:14:57.000Z | 2019-11-28T03:10:32.000Z | packages/site/docs/api/Items/nodeMethods.en.md | SLin0218/G6 | 0a6f4770cb5ac6c2e830da1544327d9a8babd743 | [
"MIT"
] | 2,415 | 2019-11-28T04:46:50.000Z | 2022-03-31T08:23:02.000Z | packages/site/docs/api/Items/nodeMethods.en.md | SLin0218/G6 | 0a6f4770cb5ac6c2e830da1544327d9a8babd743 | [
"MIT"
] | 699 | 2019-11-28T05:10:46.000Z | 2022-03-27T08:36:02.000Z | ---
title: node.*
order: 1
---
Node inherits from item. The functions of Item are also available for Node. This document will only introduce the common functions for Node class. All the built-in nodes can be found in [Built-in Nodes Doc](/en/docs/manual/middle/elements/nodes/defaultNode) and [demo](/en/examples/item/defaultNodes), Custom Node can be found in [Custom Node Doc](/en/docs/manual/middle/elements/nodes/custom-node) and [demo](/en/examples/item/customNode).
### node.lock()
Lock the current node. The locked node will not response the drag event any more.
Tips: the locked node still can be moved while dragging and zooming the canvas. If you want to fix the node in these two situations, please refer to [Fix the Locked Node While Dragging](/en/docs/manual/middle/elements/methods/lock-node#fix-the-locked-node-while-dragging) and [Fix the Locked Node while Zooming](/en/docs/manual/middle/elements/methods/lock-node#fix-the-locked-node-while-zooming) to register a custom Behavior.
**Usage**
```javascript
const node = graph.findById('node');
node.lock();
```
### node.unlock()
Unlock the locked node.
**Usage**
```javascript
const node = graph.findById('node');
node.unlock();
```
### node.hasLocked()
Query the lock state of the node.
**Return**
- The type of return value: Boolean;
- The node is locked if it returns `true`, unlocked otherwise.
**Usage**
```javascript
const node = graph.findById('node');
const hasLocked = node.hasLocked();
```
### node.getNeighbors(type)
**Parameters**
| Name | Type | Required | Description |
| --- | --- | --- | --- |
| type | 'source' / 'target' / undefined | false | The type of the neighbors, 'source': only return the source nodes; 'target': only return the target nodes, undefined: return all of the neighbors |
**Return**
- Type of the return value: Array;
- Return a list of node items.
**Usage**
```javascript
const neighbors = node.getNeighbors('source');
```
### node.getEdges()
Get the related edges (the node is the source or the target of the edge) of the node.
**Return**
- The type of return value: Edge[];
- Returns the set of related edge items.
**Usage**
```javascript
// Get the related edges
const edges = node.getEdges();
```
### node.getInEdges()
Get the related in-edges, whose target is the node.
**Return**
- The type of return value: Edge[];
- Returns the set of related in-edges.
**Usage**
```javascript
// Get the related in-edges
const edges = node.getInEdges();
```
### node.getOutEdges()
Get the related out-edges, whose source is the node.
**Return**
- The type of return value: Edge[];
- Return the set of related out-edges.
**Usage**
```javascript
// Get the related out-edges
const edges = node.getOutEdges();
```
### node.getAnchorPoints()
Get all the anchor points of the node.
**Return**
- The type of return value: Array;
- The data structure of the return value:
```javascript
[
[100, 105],
[200, 105]
];
```
**Usage**
```javascript
// Get the anchor points of the node
const anchor = node.getAnchorPoints();
```
### node.getLinkPoint(point)
Get the nearest anchor point of the node to `point`.
**Parameters**
| Name | Type | Required | Description |
| ----- | ------ | -------- | ------------------------------------- |
| point | Object | true | A point with x and y ouside the node. |
**Return**
- The type of return value: Object；
- Returns (x, y) of the found anchor point. If there is no anchor point found, returns the center of the node.
**Usage**
```javascript
const point = {
x: 100,
y: 105,
};
// Get the anchor point which is nearest to the point
const linkPoint = node.getLinkPoint(point);
```
### node.getLinkPointByAnchor(index)
Get the (x, y) of the anchor point with the `index`.
**Parameters**
| Name | Type | Required | Description |
| ----- | ------ | -------- | ------------------------------ |
| index | Number | true | The index of the anchor point. |
**Return**
- The type of return value: Object;
- Returns the (x, y) of found anchor point.
**Usage**
```javascript
// Get the first anchor point of the node
const anchor = node.getLinkPointByAnchor(0);
```
### node.addEdge(edge)
Add the `edge` to the node.
**Parameters**
| Name | Type | Required | Description |
| ---- | ---- | -------- | --------------------- |
| edge | Edge | true | The item of the edge. |
**Usage**
```javascript
const edge = new Edge({
// TODO
});
node.addEdge(edge);
```
### node.removeEdge(edge)
Remove the `edge` from the node.
**Parameters**
| Name | Type | Required | Description |
| ---- | ---- | -------- | ----------------- |
| edge | Edge | true | The item of Edge. |
**Usage**
```javascript
const edge = graph.findById('edge1');
node.removeEdge(edge);
```
| 21.850679 | 440 | 0.643197 | eng_Latn | 0.909672 |
d58785888e98dfd6a7fba13ea4f4ea3125dea6aa | 67 | md | Markdown | _posts/2019-11-25-my-first-blog-post.md | mtanveersingh/github-pages-with-jekyll | 3e169f828e5959e0bb7e5dde7d25d13030c738ac | [
"MIT"
] | null | null | null | _posts/2019-11-25-my-first-blog-post.md | mtanveersingh/github-pages-with-jekyll | 3e169f828e5959e0bb7e5dde7d25d13030c738ac | [
"MIT"
] | 4 | 2019-11-25T19:38:18.000Z | 2019-11-25T19:58:50.000Z | _posts/2019-11-25-my-first-blog-post.md | mtanveersingh/github-pages-with-jekyll | 3e169f828e5959e0bb7e5dde7d25d13030c738ac | [
"MIT"
] | null | null | null | ---
title: "Trigo References"
date: 2019-11-25
---
# Trigonometry
| 9.571429 | 25 | 0.656716 | eng_Latn | 0.24322 |
d5883e06571b9926f097317be9feec5a5f0714ee | 19,063 | md | Markdown | articles/data-lake-analytics/data-lake-analytics-data-lake-tools-view-jobs.md | krimog/azure-docs.fr-fr | f9e0062239eb8e7107ea45ad1a8e07f6c905031e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/data-lake-analytics/data-lake-analytics-data-lake-tools-view-jobs.md | krimog/azure-docs.fr-fr | f9e0062239eb8e7107ea45ad1a8e07f6c905031e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/data-lake-analytics/data-lake-analytics-data-lake-tools-view-jobs.md | krimog/azure-docs.fr-fr | f9e0062239eb8e7107ea45ad1a8e07f6c905031e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Utiliser l’Explorateur de travaux et la Vue des travaux - Azure Data Lake Analytics
description: Cet article explique comment utiliser l’Explorateur de travaux et la Vue des travaux pour les travaux Azure Data Lake Analytics.
ms.service: data-lake-analytics
author: jasonwhowell
ms.author: jasonh
ms.assetid: bdf27b4d-6f58-4093-ab83-4fa3a99b5650
ms.topic: conceptual
ms.date: 08/02/2017
ms.openlocfilehash: 2d33a6ec5ff6b687913914e9433b85765aaa7aec
ms.sourcegitcommit: 0486aba120c284157dfebbdaf6e23e038c8a5a15
ms.translationtype: HT
ms.contentlocale: fr-FR
ms.lasthandoff: 09/26/2019
ms.locfileid: "71309948"
---
# <a name="use-job-browser-and-job-view-for-azure-data-lake-analytics"></a>Utiliser l’Explorateur de travaux et la Vue des travaux pour Azure Data Lake Analytics
Le service Azure Data Lake Analytics archive les travaux soumis dans un magasin de requêtes. Dans cet article, vous allez apprendre à utiliser l’Explorateur de travaux et la Vue des travaux dans Azure Data Lake Tools pour Visual Studio pour trouver les informations d’historique des travaux.
Par défaut, le service Data Lake Analytics archive les travaux des 30 derniers jours. La période d’expiration peut être configurée à partir du portail Azure en définissant la stratégie d’expiration personnalisée. Vous ne pourrez plus accéder aux informations des travaux après l’expiration.
## <a name="prerequisites"></a>Prérequis
Voir [Data Lake Tools for Visual Studio - Composants requis](data-lake-analytics-data-lake-tools-get-started.md#prerequisites).
## <a name="open-the-job-browser"></a>Ouverture de l’Explorateur de travaux
Accédez à l’Explorateur de travaux via **Explorateur de serveurs>Azure>Data Lake Analytics>Travaux** dans Visual Studio. L’explorateur de travaux vous permet d’accéder au magasin de requêtes d’un compte Data Lake Analytics. Il présente le magasin des requêtes sur la gauche, lequel indique des informations de base sur les travaux, et la vue du travail sur la droite, laquelle indique des informations détaillées sur les travaux.
## <a name="job-view"></a>Vue des travaux
La Vue des travaux affiche des informations détaillées sur un travail. Pour ouvrir un travail, vous pouvez double-cliquer sur un travail dans l’Explorateur de travaux ou l’ouvrir à partir du menu Data Lake en cliquant sur Vue des travaux. Une boîte de dialogue indiquant l’URL du travail devrait apparaître.
La Vue des travaux contient les éléments suivants :
* Résumé des tâches
Actualisez la Vue des travaux pour afficher les informations les plus récentes sur les travaux en cours d’exécution.
* Statut de tâche (graphique) :
Le statut de tâche indique les phases du travail :
* Préparation : Chargez votre script dans le cloud en le compilant et en l’optimisant à l’aide du service de compilation.
* Mise en file d'attente : Les travaux sont mis en file d’attente quand ils attendent des ressources suffisantes ou quand leur nombre dépasse la limite maximale de travaux simultanés par compte. Le paramètre de priorité détermine l’ordre des travaux mis en file d’attente : plus le numéro est faible, plus la priorité est élevée.
* Running : Le travail est en cours d’exécution dans votre compte Data Lake Analytics.
* Finalisation : Le travail se termine (par exemple, finalisation du fichier).
Le travail peut échouer à chaque phase. Par exemple, en cas d’erreurs de compilation dans la phase de préparation, d’erreurs d’expiration de délai lors de la phase de mise en file d’attente et d’erreurs d’exécution dans la phase d’exécution, etc.
* Informations de base
Les informations de base sur le travail apparaissent dans la partie inférieure du volet Résumé des tâches.
* Résultat du travail : A réussi ou a échoué. Le travail peut échouer à chaque phase.
* Durée totale : Temps écoulé (durée) entre l’heure de soumission et l’heure de fin.
* Durée totale de calcul : Somme des temps d’exécution de chaque vertex, que vous pouvez considérer comme le temps d’exécution du travail dans un seul vertex. Reportez-vous à la valeur Total des vertex pour plus d’informations sur les vertex.
* Heure de soumission/début/fin : Heure à laquelle le service Data Lake Analytics reçoit le travail soumis/commence à exécuter le travail/termine le travail avec succès ou non.
* Compilation/Mis en file d’attente/En cours d’exécution : Temps écoulé durant la phase de préparation/mise en file d’attente/en cours d’exécution.
* Compte : Compte Data Lake Analytics utilisé pour exécuter le travail.
* Auteur : Utilisateur qui a envoyé le travail. Il peut s’agit du compte d’une personne réelle ou d’un compte système.
* Priorité : Priorité du travail. Plus le numéro est faible, plus la priorité est élevée. Cette valeur affecte uniquement l’ordre des travaux dans la file d’attente. Définir une priorité plus élevée n’accélère pas les travaux en cours d’exécution.
* Parallélisme : Nombre maximal d’unités Azure Data Lake Analytics (ADLAU) simultanées demandées, également appelées vertex. Actuellement, un vertex est égal à une machine virtuelle avec deux cœurs virtuels et six Go de RAM, mais cette quantité peut être mise à niveau dans les prochaines mises à jour Data Lake Analytics.
* Octets restants : Octets qui restent à traiter jusqu'à ce que la tâche soit terminée.
* Octets lus/écrits : Octets qui ont été lus/écrits depuis le début de l’exécution du travail.
* Total des vertex : Le travail est divisé en plusieurs éléments, chaque élément étant appelé un vertex. Cette valeur indique le nombre d’éléments qui composent le travail. Vous pouvez considérer un vertex comme une unité de processus de base, également appelée Azure Data Lake Analytics Unit (ADLAU), et les vertex peuvent être exécutés dans un parallélisme.
* Terminé/En cours d’exécution/Échec : Nombre de vertex terminés/en cours d’exécution/ayant échoué. Les vertex peuvent échouer en raison d’erreurs au niveau du code utilisateur et du système, mais le système tente de relancer automatiquement plusieurs fois les vertex ayant échoué. Si le vertex échoue toujours après une nouvelle tentative, la totalité du travail échoue.
* Graphique du travail
Un script SQL-U représente la logique de la transformation des données d’entrée en données de sortie. Le script est compilé et optimisé pour un plan d’exécution physique lors la phase de préparation. Graphique du travail permet d’afficher le plan d’exécution physique. Le diagramme suivant illustre ce processus :
Un travail est divisé en plusieurs éléments. Chaque élément est appelé un vertex. Les vertex sont regroupés en Super Vertex (également appelé phase) et visualisés sous la forme d’un graphique de travail. Les panneaux verts dans le graphique du travail indiquant les différentes phases.
Chaque vertex d’une phase effectue le même type de travail en utilisant différentes parties des mêmes données. Par exemple, si vous disposez d’un fichier contenant un To de données et des centaines de vertex à lire, chaque vertex lit un bloc de données. Ces vertex sont regroupés dans la même phase et effectuent le même travail sur différentes parties du même fichier d’entrée.
* <a name="state-information"></a>Informations sur la phase
Au cours d’une phase spécifique, certains nombres apparaissent dans le panneau.
* SV1 Extract : Nom d’une phase, défini par un nombre et par la méthode d’opération.
* 84 vertex : Nombre total de vertex dans cette phase. Le chiffre indique le nombre d’éléments de travail qui composent cette phase.
* 12.90 s/vertex : Temps d’exécution moyen du vertex pour cette phase. Ce chiffre est calculé à l’aide de la fonction SUM (temps d’exécution de chaque vertex)/(nombre de vertex). Ce qui signifie que si vous avez pu attribuer tous les vertex exécutés dans le parallélisme, la totalité de la phase s’est terminée en 12,90 s. Cela signifie également que si tout le travail de cette phase a été effectué en série, le coût équivaudrait au nombre de vertex * temps moyen.
* 850 895 lignes écrites : Nombre total de lignes écrites au cours de cette phase.
* R/W : Quantité de données lues/écrites au cours de cette phase, en octets.
* Couleurs : Couleurs utilisées dans cette phase pour indiquer le statut des différents vertex.
* Vert indique que le vertex a réussi.
* Orange indique que le vertex a été relancé. Le vertex relancé a échoué mais il a été correctement automatiquement relancé par le système et la totalité de la phase s’est terminée avec succès. Si le vertex relancé échoue toujours, la couleur passe au rouge et la totalité du travail échoue.
* Rouge indique un échec, c’est-à-dire qu’un vertex a été relancé plusieurs fois par le système mais échoue toujours. Ce scénario provoque l’échec de la totalité du travail.
* Bleu signifie qu’un vertex est en cours d’exécution.
* Blanc indique que le vertex est en attente. Le vertex peut attendre d’être replanifié lorsqu’une unité ADLAU devient disponible, ou attendre d’autres informations si les données d’entrée ne sont pas prêtes.
Vous trouverez plus de détails sur la phase en plaçant le curseur de la souris sur un état :
* Vertex : Décrit les détails des vertex, par exemple le nombre total de vertex, le nombre de vertex terminés, ayant échoué, toujours en cours d’exécution, en attente, etc.
* Lecture des données dans un ou plusieurs pods : Les fichiers et les données sont stockés dans plusieurs pods dans un système de fichiers distribués. Cette valeur décrit la quantité de données lues dans le même pod ou dans plusieurs pods.
* Durée totale de calcul : Somme des temps d’exécution de chaque vertex au cours de la phase, que vous pouvez considérer comme le temps nécessaire si la totalité du travail de cette phase est exécutée dans un seul vertex.
* Données et lignes écrites/lues : Indique la quantité de données ou de lignes qui ont été lues/écrites ou qui doivent être lues.
* Échecs de lecture de vertex : Indique le nombre de vertex qui ont échoué lors de la lecture de données.
* Ignorer les vertex en double : Si un vertex s’exécute trop lentement, le système peut configurer plusieurs vertex afin qu’ils exécutent le même élément de travail. Les vertex redondants sont supprimés dès qu’un des vertex se termine avec succès. Cette option enregistre le nombre de vertex qui ont été ignorés car représentant des doublons dans la phase.
* Révocations de vertex : Le vertex a réussi, mais a été réexécuté ultérieurement pour certaines raisons. Par exemple, si un vertex en aval perd des données d’entrée intermédiaires, il demandera au vertex en amont de s’exécuter à nouveau.
* Exécutions de planifications de vertex : Durée totale de planification des vertex.
* Données minimales/moyennes/maximales lues : Valeur minimale/moyenne/maximale des données lues pour chaque vertex.
* Durée : Temps écoulé d’une phase. Vous devez charger le profil pour afficher cette valeur.
* Lecture de travail
Data Lake Analytics exécute les travaux et archive les informations sur l’exécution des vertex de ces travaux, par exemple l’heure à laquelle les vertex ont démarré, se sont arrêtés, ont échoué, comment ils ont été relancés, etc. Toutes les informations sont automatiquement consignées dans le magasin de requêtes puis stockées dans le profil de travail. Vous pouvez télécharger le profil de travail via l’option « Charger le profil » de la Vue des travaux, et vous pouvez afficher l’option Lecture de travail après avoir téléchargé le profil de travail.
Lecture de travail est une visualisation symbolique des opérations effectuées dans le cluster. Elle vous permet de surveiller la progression de l'exécution du travail et de détecter visuellement les anomalies de performance et les goulots d'étranglement très rapidement (moins de 30 s généralement).
* Affichage du tableau (Heat Map) du travail
Le tableau du travail peut être sélectionné dans la liste déroulante Affichage du menu Graphique du travail.
Cette option indique les valeurs d’E/S, de temps et de débit d’un travail, vous permettant d’identifier les zones où le travail passe le plus de temps, ou si votre travail est un travail avec des limites d’E/S et ainsi de suite.
* Progression : Progression de l’exécution du travail. Pour en savoir plus, consultez les informations de la phase.
* Données lues/écrites : Tableau des données totales lues/écrites à chaque phase.
* Temps de calcul : Tableau de la fonction SUM (temps d’exécution de chaque vertex), que vous pouvez considérer comme le temps nécessaire si la totalité du travail de cette phase est exécutée dans 1 seul vertex.
* Temps d’exécution moyen par nœud : Tableau de la fonction SUM (temps d’exécution de chaque vertex)/(nombre de vertex). Ce qui signifie que si vous avez pu attribuer tous les vertex exécutés dans le parallélisme, la totalité de la phase sera effectuée dans ce laps de temps.
* Débit d’entrée/sortie : Tableau du débit d’entrée/sortie de chaque phase, vous permettant de vérifier si votre travail comporte des limites d’E/S.
* Opérations sur les métadonnées
Vous pouvez effectuer certaines opérations sur les métadonnées dans votre script SQL-U, notamment créer une base de données, supprimer une table, etc. Ces opérations sont affichées dans Opération sur les métadonnées après compilation. Vous pouvez rechercher des assertions, créer des entités, ou déposer ici des entités.
* Historique de l'état
L’historique de l’état est également affiché dans le Résumé des tâches, mais vous pouvez obtenir plus de détails ici. Vous trouverez des informations détaillées telles l’heure à laquelle le travail a été préparé, mis en attente, démarré et terminé. Vous trouverez également le nombre de fois que le travail a été compilé (CcsAttempts : 1), quand le travail est réellement réparti sur le cluster (Détail : Répartition du travail sur le cluster), etc.
* Diagnostics
L’outil diagnostique automatiquement l’exécution du travail. Vous recevrez des alertes lorsqu'il y a des erreurs ou des problèmes de performances dans vos travaux. Veuillez noter que vous devez télécharger le profil pour obtenir ici des informations complètes.
* Avertissements : Une alerte apparaît ici avec un avertissement du compilateur. Vous pouvez cliquer sur « x problème(s) » pour obtenir plus de détails une fois l’alerte affichée.
* Exécution trop longue du vertex : Si un vertex expire (par exemple, après 5 heures), les problèmes sont décrits ici.
* Utilisation des ressources : Si vous avez alloué trop ou pas assez de parallélisme par rapport à ce qui est nécessaire, les problèmes sont décrits ici. Vous pouvez également cliquer sur Utilisation des ressources pour obtenir plus d’informations et analyser des scénarios afin de trouver une meilleure allocation des ressources (pour plus d’informations, consultez ce guide).
* Vérification de la mémoire : Si un vertex utilise plus de 5 Go de mémoire, les problèmes sont décrits ici. L’exécution du travail peut être annulée par le système s’il utilise davantage de mémoire que la limitation du système.
## <a name="job-detail"></a>Détail du travail
L’option Détail de la tâche affiche des informations détaillées sur le travail, y compris le script, les ressources et la vue d’exécution du vertex.
* Script
Le script SQL-U du travail est stocké dans le magasin de requêtes. Vous pouvez consulter le script U-SQL d’origine et le soumettre à nouveau si nécessaire.
* Ressources
Les sorties de compilation du travail sont stockés dans le magasin de requêtes via l’option Ressources. Par exemple, vous pouvez rechercher ici l’expression « algebra.xml », utilisée pour afficher le graphique du travail, les assemblys que vous avez enregistrés, etc.
* Vue d’exécution du vertex
Affiche des détails sur l’exécution des vertex. Le profil du travail archive chaque journal d’exécution du vertex, notamment le total des données lues/écrites, le temps d’exécution, l’état, etc. Dans cette vue, vous pouvez obtenir plus d’informations sur la façon dont un travail a été exécuté. Pour plus d’informations, consultez [Utilisation de la vue d’exécution du vertex dans Azure Data Lake Tools pour Visual Studio](data-lake-analytics-data-lake-tools-use-vertex-execution-view.md).
## <a name="next-steps"></a>Étapes suivantes
* Pour consigner les informations de diagnostic, consultez [Accès aux journaux de diagnostic d’Azure Data Lake Analytics](data-lake-analytics-diagnostic-logs.md)
* Pour voir une requête plus complexe, consultez [Analyse de journaux d’activité des sites web à l’aide d’Azure Data Lake Analytics](data-lake-analytics-analyze-weblogs.md).
* Pour utiliser la vue d’exécution du vertex, consultez [Utilisation de la vue d’exécution du vertex dans Data Lake Tools pour Visual Studio](data-lake-analytics-data-lake-tools-use-vertex-execution-view.md)
| 110.190751 | 560 | 0.778052 | fra_Latn | 0.99432 |
d5884b3d9b1b98096431ba815d1ab86481516641 | 84 | md | Markdown | README.md | sonal-raj/pysaaf | 23b8996c1ac79b2acef35d2afee8523353d7f06a | [
"MIT"
] | null | null | null | README.md | sonal-raj/pysaaf | 23b8996c1ac79b2acef35d2afee8523353d7f06a | [
"MIT"
] | null | null | null | README.md | sonal-raj/pysaaf | 23b8996c1ac79b2acef35d2afee8523353d7f06a | [
"MIT"
] | null | null | null | # pysaaf
Automatic Code Linting, Cleanup and formatting library for Python Projects
| 28 | 74 | 0.833333 | eng_Latn | 0.977812 |
d588da1ba64d06504e00a2cc84c2fcd9d5225e4d | 2,874 | md | Markdown | emerald-sdk/README.md | YazzyYaz/etcdev.gitbook | be56040a35ec506dd4e014b126b1dfa1b222750b | [
"Apache-2.0"
] | null | null | null | emerald-sdk/README.md | YazzyYaz/etcdev.gitbook | be56040a35ec506dd4e014b126b1dfa1b222750b | [
"Apache-2.0"
] | null | null | null | emerald-sdk/README.md | YazzyYaz/etcdev.gitbook | be56040a35ec506dd4e014b126b1dfa1b222750b | [
"Apache-2.0"
] | 1 | 2019-12-16T18:38:28.000Z | 2019-12-16T18:38:28.000Z | ---
description: >-
The Emerald SDK is a set of development tools that help developers create
decentralized applications (DApps) on Ethereum Classic.
---
# Emerald SDK
## The DApp Development Environment
In software development, an application is built in a testing environment before the production version is deployed. A testing environment allows developers to review the design, usability, and security of an application before deployment. This is true when building DApps and arguably more so due to the immutability of a decentralized public blockchain.
When a critical bug is discovered on a traditional application, it is possible for an admin \(or hacker\) to completely remove the application until further notice. However, on a decentralized public blockchain, mistakes cannot be _magically_ forgotten. This high-assurance is why DApp developers need their own testing environment with all the tools they’d expect on the main-net. So what tools does a DApp developer need for end-to-end development?
### Overview of a DApp Tool Set
1. **Interface**: The front-end a user interacts with the DApp.
2. **Test-net**: A personal Ethereum Classic test-net to develop against with the usual blockchain suspects; blocks, hashes, test-net accounts, etc…
3. **Wallet**: A wallet to create and sign transactions on the DApp.
4. **Block-explorer**: A personal block explorer to explore blocks on a test-net.
5. **Smart Contract Testing and Deployment**: Tool to compile, test, and deploy the DApp on a given network.
There are many tools available to developers such as ReMix to compile contracts, and MetaMask to interact with test contracts. However these tools do not work together, and do not provide a simple build chain to create a whole app. Presently everything is very piecemeal. The Emerald SDK encapsulate this workflow to make DApp development easier.
### Overview of Emerald SDK Tool Set
1. **Emerald-JS-UI** & **Emerald-JS**: Highly reusable and customizable React library that connects to the blockchain \(test-net or main-net\) through the Emerald-JS RPC API.
2. **Emerald TestRPC**: Light weight test-net \(based on SputnikVM-Dev\)supporting all the opcodes as the main-net. Generates blocks, test accounts, and the usual subjects you’d expect on the main-net to develop upon.
3. **Emerald Wallet**: An Ethereum Classic wallet that can toggle between network nodes \(test-net or main-net\) allowing developers to sign and send transaction for their DApps.
4. **Emerald Explorer**: A blockchain explorer that can toggle between networks. Developers can use the explorer to explore transaction
5. **Emerald-CLI**: _The Swiss Army Knife_ of the Emerald SDK, encapsulating the testRPC, wallet, explorer, and new project generation in one CLI with smart contract testing and deployment capabilities.
| 82.114286 | 450 | 0.783925 | eng_Latn | 0.995906 |
d588eb4f2347f84b43430cd6762cc65ff928fb63 | 397 | md | Markdown | README.md | henrino3/Jq-Todo | 5ef9c90028e6b76b9e8f11757c0ddd1f7d881aba | [
"MIT"
] | null | null | null | README.md | henrino3/Jq-Todo | 5ef9c90028e6b76b9e8f11757c0ddd1f7d881aba | [
"MIT"
] | null | null | null | README.md | henrino3/Jq-Todo | 5ef9c90028e6b76b9e8f11757c0ddd1f7d881aba | [
"MIT"
] | null | null | null | Problem Statement 1:
Create a simple To-Do application using HTML/CSS and jQuery.
Have three categories of tasks, Yet to Start, In - Progress and Completed.
An important argument is that no two tasks can end or start on the same date.
Please make sure you write cases for that.
Solution
UI
Create Layout
Create 2 Rows
Create 3 Columns
Create a Form Modal
Create a view for a column
Logic
| 17.26087 | 77 | 0.775819 | eng_Latn | 0.995418 |
d58a3aa5e631bfd8e5bd5a755c49a84a385404bb | 5,305 | md | Markdown | guides/i18n/use-locize.md | ronnyfv/next-right-now | e1af281634713c0f6f067e4e0bd7827cd63633b5 | [
"MIT"
] | null | null | null | guides/i18n/use-locize.md | ronnyfv/next-right-now | e1af281634713c0f6f067e4e0bd7827cd63633b5 | [
"MIT"
] | null | null | null | guides/i18n/use-locize.md | ronnyfv/next-right-now | e1af281634713c0f6f067e4e0bd7827cd63633b5 | [
"MIT"
] | null | null | null | ---
layout: default
title: How to use Locize
parent: I18n
grand_parent: Guides
nav_order: 20
---
# How to use Locize
{: .no_toc }
<div class="code-example" markdown="1">
The content displayed on NRN is translated using different ways, depending on where the translations are stored:
- Dynamic content - GraphCMS (fetched from the DB, through GraphCMS API). This content can be updated through GraphCMS backoffice.
- Static content - Locize (fetched from Locize API). This content can be updated through Locize backoffice, or when using in-context editor.
</div>
{% include page-toc.md %}
---
## Overview
## How to use Locize in-context editor?
You can enable **Locize in-context editor mode**, by appending `?locize=true` to the url, see [https://nrn-default.now.sh/?locize=true](https://nrn-default.now.sh/?locize=true)
Note that it's only enabled in development and staging stages, not in production.
## Fetching translations through Locize provider
> When the content we want to display doesn't come from GraphCMS API, then it's considered as a "static" content.
>
> This means that the content is managed by [Locize](https://locize.com?ref=unly-nrn) and must be updated manually there.
Check [this video](https://www.youtube.com/watch?v=9NOzJhgmyQE) to see Locize in action with react-i18next.
### Locize translation workflow in-depth
The Locize project contains two different **versions**:
- `latest`: This **Locize version** is used in **any non-production application stage** (development, staging). That's where translations get added/updated by translators.
- `production`: This **Locize version** is only used in the production application stages (`APP_STAGE=production`) _(all customers share the same `production` version in the current setup, for the sake of simplicity)_
> This separation between the two versions is important and very useful to avoid deploying unapproved changes to the production stage.
In order to update the `production` version, all changes must go through the `latest` version.
They can therefore be tested during the development phase, then during the staging phase.
Once you're ready to ship the content to production, the `production` version can be updated from the `latest` version, which will automatically update all customer production stages.
> **Tip**: New i18n keys are added automatically in the `development` stage, as they are being added to the source code, thanks to the `saveMissing` [option](src/utils/i18nextLocize.ts). _This can also be a bit boring with HMR, because useless keys may be created while programming._
#### Locize additional services
Locize provides a few [additional services](https://locize.com/services.html?ref=unly-nrn). Some are free, some are paid.
#### Other additional services
- One interesting thing is the ability to share part of the project to be translated by a third party using [`Crowdbased`](https://locize.com/services.html?ref=unly-nrn), without sharing the whole project.
- There are also several paid [Translation services](https://locize.com/services.html?ref=unly-nrn), where you can pay people to translate your content.
- It is also possible to enable [Audit](https://locize.com/services.html?ref=unly-nrn), which allows to audit every change to our translations, and keep changes up to 10 years. (_expensive_)
### Dependencies
We rely on those packages to manage the translations:
- [`i18next-locize-backend`](https://www.npmjs.com/package/i18next-locize-backend): This is an i18next backend to be used for locize service. It will load resources from locize server using xhr.
It will allow you to save missing keys containing both default value and context information
**This backend is used when using the browser.**
- [`i18next-node-locize-backend`](https://www.npmjs.com/package/i18next-node-locize-backend): This is a i18next backend to be used with node.js for the locize service. It's for the node.js server what the i18next-locize-backend is for the browser.
**This backend is used when using node (server).**
- [`locize-editor`](https://www.npmjs.com/package/locize-editor): The locize-editor enables you to directly connect content from your website / application with your content on your localization project on locize.
Enabling the editor by querystring ?locize=true you can click any text content on your website to open it on the right side editor window
**This plugin is used when using the browser.**
- [`locize-node-lastused`](https://www.npmjs.com/package/locize-node-lastused): This is an i18next plugin or standalone scriot to be used for locize service. It will update last used timestamps on reference keys from your locize project using xhr. It sets the last used date on your reference language's namespaces.
**This plugin is used when using node (server).**
It was quite complicated to configure Next with Locize, mostly because of the universal way Next works, while Locize has dedicated packages depending on the runtime engine.
> See `src/utils/i18nextLocize.ts` to see how it was all put together.
We were inspired by [this SO question](https://stackoverflow.com/questions/55994799/how-to-integrate-next-i18next-nextjs-locize/58782594).
https://locize.com/
https://docs.locize.com/
https://www.i18next.com/overview/for-enterprises#locize
| 60.977011 | 315 | 0.772479 | eng_Latn | 0.996532 |
d58a60ffcd4186ebe8180967b52cf01bae058621 | 25 | md | Markdown | README.md | edwindotcom/react-native-sample-app | 131be0532aa5aaafcac03463749ae7d31abe2478 | [
"MIT"
] | null | null | null | README.md | edwindotcom/react-native-sample-app | 131be0532aa5aaafcac03463749ae7d31abe2478 | [
"MIT"
] | 3 | 2020-09-06T22:06:56.000Z | 2021-05-10T08:12:39.000Z | README.md | edwindotcom/react-native-sample-app | 131be0532aa5aaafcac03463749ae7d31abe2478 | [
"MIT"
] | null | null | null | # react-native-sample-app | 25 | 25 | 0.8 | eng_Latn | 0.790951 |
d58aa16e9825f6393ab999f7b5a7a21a8576e820 | 524 | md | Markdown | packages/office-ui-fabric-react/src/components/Modal/docs/ModalOverview.md | nileshp87/fluentui | 345a76a39f36624ee5ea3d22f34da631a77c389f | [
"MIT"
] | 1 | 2020-05-27T14:07:51.000Z | 2020-05-27T14:07:51.000Z | packages/office-ui-fabric-react/src/components/Modal/docs/ModalOverview.md | nileshp87/fluentui | 345a76a39f36624ee5ea3d22f34da631a77c389f | [
"MIT"
] | 65 | 2019-09-25T06:45:12.000Z | 2021-07-27T23:42:53.000Z | packages/office-ui-fabric-react/src/components/Modal/docs/ModalOverview.md | nileshp87/fluentui | 345a76a39f36624ee5ea3d22f34da631a77c389f | [
"MIT"
] | 1 | 2020-05-26T13:04:35.000Z | 2020-05-26T13:04:35.000Z | Modals are temporary, modal UI overlay that generally provide contextual app information or require user confirmation/input, or can be used to advertise new app features. In some cases, Modals block interactions with the web page or application until being explicitly dismissed. They can be used for lightweight creation or edit tasks and simple management tasks, or for hosting heavier temporary content.
For usage requiring a quick choice from the user, [Dialog](#/controls/web/dialog) may be a more appropriate control.
| 131 | 405 | 0.816794 | eng_Latn | 0.999121 |
d58b218b0e4bea8516a3a17c28f4e50ecd226750 | 44 | md | Markdown | README.md | jimmylab/calendarjs | 8b19fc6841f708fd06cc87f3f86bc475e38f2f51 | [
"MIT"
] | null | null | null | README.md | jimmylab/calendarjs | 8b19fc6841f708fd06cc87f3f86bc475e38f2f51 | [
"MIT"
] | null | null | null | README.md | jimmylab/calendarjs | 8b19fc6841f708fd06cc87f3f86bc475e38f2f51 | [
"MIT"
] | null | null | null | # calendarjs
A web-based calendar brochure.
| 14.666667 | 30 | 0.795455 | eng_Latn | 0.863643 |
d58bb8f73951ceb1c72e652da897d316134f8b47 | 18 | md | Markdown | README.md | stacker-sh/api | bfade554cbe3c28e07ae3ce2ecaaefbefce0c120 | [
"MIT"
] | null | null | null | README.md | stacker-sh/api | bfade554cbe3c28e07ae3ce2ecaaefbefce0c120 | [
"MIT"
] | null | null | null | README.md | stacker-sh/api | bfade554cbe3c28e07ae3ce2ecaaefbefce0c120 | [
"MIT"
] | null | null | null | # api
Central API
| 6 | 11 | 0.722222 | kor_Hang | 0.446075 |
d58bd683c556e4d209926113207a8ad12d71eb34 | 169 | md | Markdown | src/__tests__/fixtures/unfoldingWord/en_tq/gen/46/34.md | unfoldingWord/content-checker | 7b4ca10b94b834d2795ec46c243318089cc9110e | [
"MIT"
] | null | null | null | src/__tests__/fixtures/unfoldingWord/en_tq/gen/46/34.md | unfoldingWord/content-checker | 7b4ca10b94b834d2795ec46c243318089cc9110e | [
"MIT"
] | 226 | 2020-09-09T21:56:14.000Z | 2022-03-26T18:09:53.000Z | src/__tests__/fixtures/unfoldingWord/en_tq/gen/46/34.md | unfoldingWord/content-checker | 7b4ca10b94b834d2795ec46c243318089cc9110e | [
"MIT"
] | 1 | 2022-01-10T21:47:07.000Z | 2022-01-10T21:47:07.000Z | # What did Joseph tell the brothers to say to Pharaoh concerning their occupation?
The brothers were to tell Pharaoh that they were keepers of cattle from their youth.
| 42.25 | 84 | 0.804734 | eng_Latn | 0.999982 |
d58bdadfbc3bdfc0ae7d462b799cb176ffe47bd3 | 2,065 | md | Markdown | README.md | qaxim/blog | d99f33cf39908b362059cf1fad15ecf6d5a777d7 | [
"MIT"
] | 4 | 2021-05-29T05:26:18.000Z | 2021-06-16T00:44:19.000Z | README.md | qaxim/blog | d99f33cf39908b362059cf1fad15ecf6d5a777d7 | [
"MIT"
] | null | null | null | README.md | qaxim/blog | d99f33cf39908b362059cf1fad15ecf6d5a777d7 | [
"MIT"
] | 3 | 2021-06-10T07:46:29.000Z | 2021-07-29T11:22:34.000Z | <p align="center"><a href="http://phpblogscript.com" target="_blank" rel="noopener noreferrer"><img width="200" src="http://phpblogscript.com/blog/uploads/global/logo.png" alt="php blogscript"></a></p>
<br>
Simplest PHP based blog fully optimized for search engines 100% opensource code and ready to extend the features. logically inspired by wordpress, medium, gitbook & ghost cms.
#### ❤️ Build with technologies : PHP MYSQL HTML CSS JS
#### 🔥 Features
- 🌐 100% opensource code
- 👑 Categories module
- 📄 Newsletter & subscribers
- ⏫ SEO optimized
- ⚡ Google AMP Optmized via url/amp
- 😎 Multi users accounts
- 📁 Built-it pages views analytics
- 💾 Post draft feature
- 💿 Base64 article optimized images
- 🔎 Auto Sitemap generation
- 📄 Beautify URLs
- 📱 Social links and shares
- ⚠️ Page hits views counter
#### Why PHP Blog Script
Starting your own niche based blog is very challenging specially when it comes to selecting any of your CMS or blog script. speed, performance, optimization, SEO and user-friendly are the options you need to be very handy. fancy cms and blog scripts are no more easy to handle configure or install on your shared or dedicated servers anymore. PHP Blog Script makes life much easier to just add your db credentials and install the entire platform within 2 minutes.
#### Google test pagespeed
<img align="center" width="100%" src="https://i.ibb.co/FXvwpT2/Page-Speed-Insights.png" alt="">
No plugins no libraries and fancy themes to customize and waste your time simple elegant and useful blog platform is ready for you to install for free and start blogging without wasting your time on search other blogging scripts.
#### Demo homepage
<img align="center" width="100%" src="https://i.ibb.co/yRV05RG/web.png" alt="">
#### Demo backend
<img align="center" width="100%" src="https://i.ibb.co/1b3t6Ng/Dashboard-1.png" alt="">
Main [Website](http://phpblogscript.com/)
Live [Demo](http://phpblogscript.com/blog)
## License
[MIT](https://opensource.org/licenses/MIT)
Copyright (c) 2021-present, Founder Qasim Hussain
| 45.888889 | 463 | 0.742857 | eng_Latn | 0.906322 |
d58e12ba2e5f8acc6167f7da333d2ef5a1ba2ea2 | 503 | md | Markdown | docs/error-messages/tool-errors/linker-tools-error-lnk1196.md | sunbohong/cpp-docs.zh-cn | 493f8d9a3d1ad73e056941fde491e76329f9c5ec | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/error-messages/tool-errors/linker-tools-error-lnk1196.md | sunbohong/cpp-docs.zh-cn | 493f8d9a3d1ad73e056941fde491e76329f9c5ec | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/error-messages/tool-errors/linker-tools-error-lnk1196.md | sunbohong/cpp-docs.zh-cn | 493f8d9a3d1ad73e056941fde491e76329f9c5ec | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
description: 了解详细信息：链接器工具错误 LNK1196
title: 链接器工具错误 LNK1196
ms.date: 11/04/2016
f1_keywords:
- LNK1196
helpviewer_keywords:
- LNK1196
ms.assetid: d0c6859b-85aa-45cc-9f5f-fc1f7070ab5a
ms.openlocfilehash: a66ad675eea642500a3aff1e6b54e9003950f22b
ms.sourcegitcommit: d6af41e42699628c3e2e6063ec7b03931a49a098
ms.translationtype: MT
ms.contentlocale: zh-CN
ms.lasthandoff: 12/11/2020
ms.locfileid: "97341654"
---
# <a name="linker-tools-error-lnk1196"></a>链接器工具错误 LNK1196
无效或损坏的导入对象：未知版本
导入库已损坏。 重新生成库。
| 22.863636 | 60 | 0.813121 | yue_Hant | 0.175573 |
d58e5166d68651f8bc699e245877d3e7d5cb1473 | 89,544 | md | Markdown | docs-en/api/api-SmartVision-Devices/ohos-uislider.md | PigSkin-Hup/hongmengdocs | 7958dbc646cedf526b7013728897ce32cc21c1d4 | [
"Apache-2.0"
] | null | null | null | docs-en/api/api-SmartVision-Devices/ohos-uislider.md | PigSkin-Hup/hongmengdocs | 7958dbc646cedf526b7013728897ce32cc21c1d4 | [
"Apache-2.0"
] | null | null | null | docs-en/api/api-SmartVision-Devices/ohos-uislider.md | PigSkin-Hup/hongmengdocs | 7958dbc646cedf526b7013728897ce32cc21c1d4 | [
"Apache-2.0"
] | null | null | null | # OHOS::UISlider<a name="EN-US_TOPIC_0000001054918181"></a>
- [Overview](#section1422396766165634)
- [Summary](#section229199819165634)
- [Data Structures](#nested-classes)
- [Public Member Functions](#pub-methods)
- [Additional Inherited Members](#inherited)
## **Overview**<a name="section1422396766165634"></a>
**Related Modules:**
[Graphic](graphic.md)
**Description:**
Represents a slider.
Users can drag or click the knob to adjust the progress of an event.
See also
: [UIBoxProgress](ohos-uiboxprogress.md)
**Since:**
1.0
**Version:**
1.0
## **Summary**<a name="section229199819165634"></a>
## Data Structures<a name="nested-classes"></a>
<a name="table948772166165634"></a>
<table><thead align="left"><tr id="row1091703481165634"><th class="cellrowborder" valign="top" width="50%" id="mcps1.1.3.1.1"><p id="p950535292165634"><a name="p950535292165634"></a><a name="p950535292165634"></a>Data Structure Name</p>
</th>
<th class="cellrowborder" valign="top" width="50%" id="mcps1.1.3.1.2"><p id="p1709966183165634"><a name="p1709966183165634"></a><a name="p1709966183165634"></a>Description</p>
</th>
</tr>
</thead>
<tbody><tr id="row2125654709165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p498846565165634"><a name="p498846565165634"></a><a name="p498846565165634"></a><a href="ohos-uislider-uislidereventlistener.md">UISliderEventListener</a></p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1015694718165634"><a name="p1015694718165634"></a><a name="p1015694718165634"></a>Represents the listener for a slider change. </p>
</td>
</tr>
</tbody>
</table>
## Public Member Functions<a name="pub-methods"></a>
<a name="table1871262863165634"></a>
<table><thead align="left"><tr id="row1355483873165634"><th class="cellrowborder" valign="top" width="50%" id="mcps1.1.3.1.1"><p id="p584323290165634"><a name="p584323290165634"></a><a name="p584323290165634"></a>Function</p>
</th>
<th class="cellrowborder" valign="top" width="50%" id="mcps1.1.3.1.2"><p id="p2001120734165634"><a name="p2001120734165634"></a><a name="p2001120734165634"></a>Description</p>
</th>
</tr>
</thead>
<tbody><tr id="row1498157348165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1610424983165634"><a name="p1610424983165634"></a><a name="p1610424983165634"></a><a href="graphic.md#ga67f8d874edcd65b1610117052ceed0a6">UISlider</a> ()</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p297232888165634"><a name="p297232888165634"></a><a name="p297232888165634"></a> </p>
<p id="p722898360165634"><a name="p722898360165634"></a><a name="p722898360165634"></a>A constructor used to create a <strong id="b1657572920165634"><a name="b1657572920165634"></a><a name="b1657572920165634"></a><a href="ohos-uislider.md">UISlider</a></strong> instance. </p>
</td>
</tr>
<tr id="row151746196165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p927486498165634"><a name="p927486498165634"></a><a name="p927486498165634"></a><a href="graphic.md#ga024c4f15347a0b70920ab745efe8d250">~UISlider</a> ()</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1754668273165634"><a name="p1754668273165634"></a><a name="p1754668273165634"></a>virtual </p>
<p id="p122715556165634"><a name="p122715556165634"></a><a name="p122715556165634"></a>A destructor used to delete the <strong id="b1060251295165634"><a name="b1060251295165634"></a><a name="b1060251295165634"></a><a href="ohos-uislider.md">UISlider</a></strong> instance. </p>
</td>
</tr>
<tr id="row1680870837165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p800231391165634"><a name="p800231391165634"></a><a name="p800231391165634"></a><a href="graphic.md#gac2070526833718284148689678c542a9">GetViewType</a> () const override</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p686116094165634"><a name="p686116094165634"></a><a name="p686116094165634"></a>UIViewType </p>
<p id="p1064918503165634"><a name="p1064918503165634"></a><a name="p1064918503165634"></a>Obtains the view type. </p>
</td>
</tr>
<tr id="row1014437338165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1816287669165634"><a name="p1816287669165634"></a><a name="p1816287669165634"></a><a href="graphic.md#gaf0de71e2d767ccfc3cb41679185a5529">SetKnobWidth</a> (int16_t width)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1758704345165634"><a name="p1758704345165634"></a><a name="p1758704345165634"></a>void </p>
<p id="p310294650165634"><a name="p310294650165634"></a><a name="p310294650165634"></a>Sets the width for this knob. </p>
</td>
</tr>
<tr id="row1762058459165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1065794077165634"><a name="p1065794077165634"></a><a name="p1065794077165634"></a><a href="graphic.md#ga9bac904abdf8b097778fea5febc1ec00">GetKnobWidth</a> ()</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p29301444165634"><a name="p29301444165634"></a><a name="p29301444165634"></a>int16_t </p>
<p id="p125296501165634"><a name="p125296501165634"></a><a name="p125296501165634"></a>Obtains the knob width. </p>
</td>
</tr>
<tr id="row1181702783165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1913382061165634"><a name="p1913382061165634"></a><a name="p1913382061165634"></a><a href="graphic.md#ga0685ff139a48f556a2323d06470ad301">SetImage</a> (const <a href="ohos-imageinfo.md">ImageInfo</a> *backgroundImage, const <a href="ohos-imageinfo.md">ImageInfo</a> *foregroundImage, const <a href="ohos-imageinfo.md">ImageInfo</a> *knobImage)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p148685646165634"><a name="p148685646165634"></a><a name="p148685646165634"></a>void </p>
<p id="p462577817165634"><a name="p462577817165634"></a><a name="p462577817165634"></a>Sets the images as pixel maps for this slider, including the background, foreground, and knob images. </p>
</td>
</tr>
<tr id="row387024090165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1136645305165634"><a name="p1136645305165634"></a><a name="p1136645305165634"></a><a href="graphic.md#gaea596b36fd10c26361666aeda1aca01e">SetImage</a> (const char *backgroundImage, const char *foregroundImage, const char *knobImage)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1708803454165634"><a name="p1708803454165634"></a><a name="p1708803454165634"></a>void </p>
<p id="p1890881462165634"><a name="p1890881462165634"></a><a name="p1890881462165634"></a>Sets the images for this slider, including the background, foreground, and knob images. </p>
</td>
</tr>
<tr id="row1568107203165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p58163703165634"><a name="p58163703165634"></a><a name="p58163703165634"></a><a href="graphic.md#ga8369feb4c08ec7a01e7200a881acb94b">SetSliderColor</a> (const <a href="ohos-color32.md">ColorType</a> backgroundColor, const <a href="ohos-color32.md">ColorType</a> foregroundColor, const <a href="ohos-color32.md">ColorType</a> knobColor)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1931155895165634"><a name="p1931155895165634"></a><a name="p1931155895165634"></a>void </p>
<p id="p2029380052165634"><a name="p2029380052165634"></a><a name="p2029380052165634"></a>Sets the colors for this slider, including the background, foreground, and knob colors. </p>
</td>
</tr>
<tr id="row1596530137165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p671374573165634"><a name="p671374573165634"></a><a name="p671374573165634"></a><a href="graphic.md#ga977ead9a79667465b107ca0776868712">SetSliderRadius</a> (int16_t backgroundRadius, int16_t foregroundRadius, int16_t knobRadius)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p246294829165634"><a name="p246294829165634"></a><a name="p246294829165634"></a>void </p>
<p id="p1441355183165634"><a name="p1441355183165634"></a><a name="p1441355183165634"></a>Sets the corner radiuses for this slider, including the background, foreground, and knob corner radiuses. </p>
</td>
</tr>
<tr id="row1991486930165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1704449494165634"><a name="p1704449494165634"></a><a name="p1704449494165634"></a><a href="graphic.md#gac78f9aa2fe12353627a74f87fe49ef4b">SetKnobStyle</a> (const <a href="ohos-style.md">Style</a> &style)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p2084759166165634"><a name="p2084759166165634"></a><a name="p2084759166165634"></a>void </p>
<p id="p409627752165634"><a name="p409627752165634"></a><a name="p409627752165634"></a>Sets the knob style. </p>
</td>
</tr>
<tr id="row636578369165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1703039427165634"><a name="p1703039427165634"></a><a name="p1703039427165634"></a><a href="graphic.md#ga80c30c69e9f565269b09fc9d7ded432e">SetKnobStyle</a> (uint8_t key, int64_t value)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p898540012165634"><a name="p898540012165634"></a><a name="p898540012165634"></a>void </p>
<p id="p649704438165634"><a name="p649704438165634"></a><a name="p649704438165634"></a>Sets a knob style. </p>
</td>
</tr>
<tr id="row708172536165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1921882192165634"><a name="p1921882192165634"></a><a name="p1921882192165634"></a><a href="graphic.md#gaecf92fe00a7565d034937e89fe2cf1e6">GetKnobStyle</a> () const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1525773214165634"><a name="p1525773214165634"></a><a name="p1525773214165634"></a>const <a href="ohos-style.md">Style</a> & </p>
<p id="p1622740090165634"><a name="p1622740090165634"></a><a name="p1622740090165634"></a>Obtains the knob style. </p>
</td>
</tr>
<tr id="row623712678165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1367309731165634"><a name="p1367309731165634"></a><a name="p1367309731165634"></a><a href="graphic.md#ga1fef57bd5d9a11a9c1946e8efec71b61">GetKnobStyle</a> (uint8_t key) const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1485354778165634"><a name="p1485354778165634"></a><a name="p1485354778165634"></a>int64_t </p>
<p id="p962546010165634"><a name="p962546010165634"></a><a name="p962546010165634"></a>Obtains the value of a knob style. </p>
</td>
</tr>
<tr id="row544598128165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1727879494165634"><a name="p1727879494165634"></a><a name="p1727879494165634"></a><a href="graphic.md#ga05029e55d4ccb50cd45f1cd2a53917e4">OnClickEvent</a> (const <a href="ohos-clickevent.md">ClickEvent</a> &event) override</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1901485280165634"><a name="p1901485280165634"></a><a name="p1901485280165634"></a>void </p>
<p id="p480381530165634"><a name="p480381530165634"></a><a name="p480381530165634"></a>Called when the view is clicked. </p>
</td>
</tr>
<tr id="row1537848855165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1704350793165634"><a name="p1704350793165634"></a><a name="p1704350793165634"></a><a href="graphic.md#ga4481d4453dbf06cc808e4848a814ed7e">OnDragEvent</a> (const <a href="ohos-dragevent.md">DragEvent</a> &event) override</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1546677570165634"><a name="p1546677570165634"></a><a name="p1546677570165634"></a>bool </p>
<p id="p882113830165634"><a name="p882113830165634"></a><a name="p882113830165634"></a>Called when the view is being dragged. </p>
</td>
</tr>
<tr id="row612373809165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p430523079165634"><a name="p430523079165634"></a><a name="p430523079165634"></a><a href="graphic.md#gae9136559779057065708312fb62304bb">OnDragEndEvent</a> (const <a href="ohos-dragevent.md">DragEvent</a> &event) override</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1454911881165634"><a name="p1454911881165634"></a><a name="p1454911881165634"></a>bool </p>
<p id="p1902051167165634"><a name="p1902051167165634"></a><a name="p1902051167165634"></a>Called when the view stops dragging. </p>
</td>
</tr>
<tr id="row1508677296165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1078332129165634"><a name="p1078332129165634"></a><a name="p1078332129165634"></a><a href="graphic.md#gaf0483e605613ee1789332e67f00f5e2d">OnPreDraw</a> (const <a href="ohos-rect.md">Rect</a> &invalidatedArea) override</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1824378243165634"><a name="p1824378243165634"></a><a name="p1824378243165634"></a>bool </p>
<p id="p341190379165634"><a name="p341190379165634"></a><a name="p341190379165634"></a>Called before a view is drawn. This function is used to check whether the parent view of this view needs to be redrawn so as to optimize the drawing process. </p>
</td>
</tr>
<tr id="row1260647109165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1046000551165634"><a name="p1046000551165634"></a><a name="p1046000551165634"></a><a href="graphic.md#gad6bd59e05d77868e595d087fd2de5d00">OnDraw</a> (const <a href="ohos-rect.md">Rect</a> &invalidatedArea) override</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p833636566165634"><a name="p833636566165634"></a><a name="p833636566165634"></a>void </p>
<p id="p1501906844165634"><a name="p1501906844165634"></a><a name="p1501906844165634"></a>Called when a view is drawn. </p>
</td>
</tr>
<tr id="row1638590945165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1421920505165634"><a name="p1421920505165634"></a><a name="p1421920505165634"></a><a href="graphic.md#ga1319a5ea74ad822cb12b0f48c19ccb5d">SetSliderEventListener</a> (<a href="ohos-uislider-uislidereventlistener.md">UISliderEventListener</a> *listener)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1015864286165634"><a name="p1015864286165634"></a><a name="p1015864286165634"></a>void </p>
<p id="p260124205165634"><a name="p260124205165634"></a><a name="p260124205165634"></a>Sets the listener for a slider change. </p>
</td>
</tr>
<tr id="row1528761590165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1565820367165634"><a name="p1565820367165634"></a><a name="p1565820367165634"></a><a href="graphic.md#ga315a532a3e0aa658a64d2f7739483f35">UIBoxProgress</a> ()</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p385507678165634"><a name="p385507678165634"></a><a name="p385507678165634"></a> </p>
<p id="p776726460165634"><a name="p776726460165634"></a><a name="p776726460165634"></a>A constructor used to create a <strong id="b706836409165634"><a name="b706836409165634"></a><a name="b706836409165634"></a><a href="ohos-uiboxprogress.md">UIBoxProgress</a></strong> instance. </p>
</td>
</tr>
<tr id="row319935866165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1507679904165634"><a name="p1507679904165634"></a><a name="p1507679904165634"></a><a href="graphic.md#ga7a5eefc7d4ad253a286444e76146af7f">~UIBoxProgress</a> ()</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1815933120165634"><a name="p1815933120165634"></a><a name="p1815933120165634"></a>virtual </p>
<p id="p842650711165634"><a name="p842650711165634"></a><a name="p842650711165634"></a>A destructor used to delete the <strong id="b222774227165634"><a name="b222774227165634"></a><a name="b222774227165634"></a><a href="ohos-uiboxprogress.md">UIBoxProgress</a></strong> instance. </p>
</td>
</tr>
<tr id="row1640696678165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p583673220165634"><a name="p583673220165634"></a><a name="p583673220165634"></a><a href="graphic.md#ga4b3eeb9de2443182480a71cadb23178c">SetWidth</a> (int16_t width) override</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1453280641165634"><a name="p1453280641165634"></a><a name="p1453280641165634"></a>void </p>
<p id="p1266977611165634"><a name="p1266977611165634"></a><a name="p1266977611165634"></a>Sets the width for the view holding this progress bar. </p>
</td>
</tr>
<tr id="row1286781301165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p58516601165634"><a name="p58516601165634"></a><a name="p58516601165634"></a><a href="graphic.md#ga54299cb7561cee9a03d0fc9d0ddda784">SetHeight</a> (int16_t height) override</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p501261553165634"><a name="p501261553165634"></a><a name="p501261553165634"></a>void </p>
<p id="p1885618989165634"><a name="p1885618989165634"></a><a name="p1885618989165634"></a>Sets the height for this view. </p>
</td>
</tr>
<tr id="row1213204667165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1909141262165634"><a name="p1909141262165634"></a><a name="p1909141262165634"></a><a href="graphic.md#ga3e2e7d0c37b4945a3f4f456c20cb0177">SetDirection</a> (const <a href="graphic.md#ga4a7a2c192206c8b18379f42a5fd176eb">Direction</a> &direction)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1057896755165634"><a name="p1057896755165634"></a><a name="p1057896755165634"></a>void </p>
<p id="p314445759165634"><a name="p314445759165634"></a><a name="p314445759165634"></a>Sets the direction for this progress bar. </p>
</td>
</tr>
<tr id="row1343705467165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p953792453165634"><a name="p953792453165634"></a><a name="p953792453165634"></a><a href="graphic.md#ga493699e8d0e934d7fb3d5502529a1c5e">GetDirection</a> () const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1308887397165634"><a name="p1308887397165634"></a><a name="p1308887397165634"></a><a href="graphic.md#ga4a7a2c192206c8b18379f42a5fd176eb">Direction</a> </p>
<p id="p11127999165634"><a name="p11127999165634"></a><a name="p11127999165634"></a>Obtains the direction of this progress bar. </p>
</td>
</tr>
<tr id="row288479635165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1961470630165634"><a name="p1961470630165634"></a><a name="p1961470630165634"></a><a href="graphic.md#gada3cf1819e826ee0aed4a40ef00b91a6">SetValidWidth</a> (int16_t width)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p371710456165634"><a name="p371710456165634"></a><a name="p371710456165634"></a>void </p>
<p id="p1922670202165634"><a name="p1922670202165634"></a><a name="p1922670202165634"></a>Sets the actual width for this progress bar. </p>
</td>
</tr>
<tr id="row1007194572165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1541742923165634"><a name="p1541742923165634"></a><a name="p1541742923165634"></a><a href="graphic.md#ga6577d38d85234e08f709dd0ae131b255">GetValidWidth</a> () const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p514720614165634"><a name="p514720614165634"></a><a name="p514720614165634"></a>int16_t </p>
<p id="p1715497666165634"><a name="p1715497666165634"></a><a name="p1715497666165634"></a>Obtains the actual width of this progress bar. </p>
</td>
</tr>
<tr id="row271482070165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1740471734165634"><a name="p1740471734165634"></a><a name="p1740471734165634"></a><a href="graphic.md#ga6958b8273ad7a5563dfa19267cc3a13c">SetValidHeight</a> (int16_t height)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p74893914165634"><a name="p74893914165634"></a><a name="p74893914165634"></a>void </p>
<p id="p1169935128165634"><a name="p1169935128165634"></a><a name="p1169935128165634"></a>Sets the actual height for this progress bar. </p>
</td>
</tr>
<tr id="row1243240287165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1703736964165634"><a name="p1703736964165634"></a><a name="p1703736964165634"></a><a href="graphic.md#ga1e6c92b20c4931a058c0b7775bf180c9">GetValidHeight</a> () const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p512202698165634"><a name="p512202698165634"></a><a name="p512202698165634"></a>int16_t </p>
<p id="p1168301486165634"><a name="p1168301486165634"></a><a name="p1168301486165634"></a>Obtains the actual height of this progress bar. </p>
</td>
</tr>
<tr id="row366396034165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1690068954165634"><a name="p1690068954165634"></a><a name="p1690068954165634"></a><a href="graphic.md#ga8f9bfb4f42ee0e094501ff776e3336da">UIAbstractProgress</a> ()</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1884224016165634"><a name="p1884224016165634"></a><a name="p1884224016165634"></a> </p>
<p id="p355371225165634"><a name="p355371225165634"></a><a name="p355371225165634"></a>A constructor used to create a <strong id="b802364370165634"><a name="b802364370165634"></a><a name="b802364370165634"></a><a href="ohos-uiabstractprogress.md">UIAbstractProgress</a></strong> instance. </p>
</td>
</tr>
<tr id="row29543974165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p688867913165634"><a name="p688867913165634"></a><a name="p688867913165634"></a><a href="graphic.md#ga5c1cf7239bf0c0f7d331e63df805b518">~UIAbstractProgress</a> ()</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p947276746165634"><a name="p947276746165634"></a><a name="p947276746165634"></a>virtual </p>
<p id="p1527873233165634"><a name="p1527873233165634"></a><a name="p1527873233165634"></a>A destructor used to delete the <strong id="b1272634091165634"><a name="b1272634091165634"></a><a name="b1272634091165634"></a><a href="ohos-uiabstractprogress.md">UIAbstractProgress</a></strong> instance. </p>
</td>
</tr>
<tr id="row1007135163165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1420201827165634"><a name="p1420201827165634"></a><a name="p1420201827165634"></a><a href="graphic.md#gacb680c1ddc9135371676df504dc6c8f2">EnableBackground</a> (bool enable)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p2133661237165634"><a name="p2133661237165634"></a><a name="p2133661237165634"></a>void </p>
<p id="p1250948351165634"><a name="p1250948351165634"></a><a name="p1250948351165634"></a>Sets whether the background of the progress bar is visible. </p>
</td>
</tr>
<tr id="row131805704165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p946685997165634"><a name="p946685997165634"></a><a name="p946685997165634"></a><a href="graphic.md#ga5f65014431a6489ffa1d4949f9c4449b">SetValue</a> (int16_t value)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1284761790165634"><a name="p1284761790165634"></a><a name="p1284761790165634"></a>void </p>
<p id="p1776391524165634"><a name="p1776391524165634"></a><a name="p1776391524165634"></a>Sets the current value for this progress bar. </p>
</td>
</tr>
<tr id="row738675252165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p625437575165634"><a name="p625437575165634"></a><a name="p625437575165634"></a><a href="graphic.md#ga6face76aa7972efeb6cbb8f525f23135">GetValue</a> () const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p625382544165634"><a name="p625382544165634"></a><a name="p625382544165634"></a>int16_t </p>
<p id="p1402123668165634"><a name="p1402123668165634"></a><a name="p1402123668165634"></a>Obtains the current value of this progress bar. </p>
</td>
</tr>
<tr id="row1948082477165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1302660589165634"><a name="p1302660589165634"></a><a name="p1302660589165634"></a><a href="graphic.md#ga089e3875453011499ad33ed89a44a699">SetRange</a> (int16_t rangeMax, int16_t rangeMin)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p216300233165634"><a name="p216300233165634"></a><a name="p216300233165634"></a>void </p>
<p id="p1395641725165634"><a name="p1395641725165634"></a><a name="p1395641725165634"></a>Sets the range for this progress bar. </p>
</td>
</tr>
<tr id="row917315521165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1512376810165634"><a name="p1512376810165634"></a><a name="p1512376810165634"></a><a href="graphic.md#ga68ab733afcf4224a799ccad2092d1d23">GetRangeMin</a> () const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1571507420165634"><a name="p1571507420165634"></a><a name="p1571507420165634"></a>int16_t </p>
<p id="p530395474165634"><a name="p530395474165634"></a><a name="p530395474165634"></a>Obtains the minimum value of this progress bar. </p>
</td>
</tr>
<tr id="row2067443986165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p964354040165634"><a name="p964354040165634"></a><a name="p964354040165634"></a><a href="graphic.md#ga1840199f22d5d3e4ef58e41ac8f4febc">GetRangeMax</a> () const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p705054458165634"><a name="p705054458165634"></a><a name="p705054458165634"></a>int16_t </p>
<p id="p2077502126165634"><a name="p2077502126165634"></a><a name="p2077502126165634"></a>Obtains the maximum value of this progress bar. </p>
</td>
</tr>
<tr id="row2133541815165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p299166605165634"><a name="p299166605165634"></a><a name="p299166605165634"></a><a href="graphic.md#ga5b3ec363e391f601e12bf937b9cf77db">SetImage</a> (const char *foregroundImage, const char *backgroundImage=nullptr)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p424982588165634"><a name="p424982588165634"></a><a name="p424982588165634"></a>void </p>
<p id="p101267524165634"><a name="p101267524165634"></a><a name="p101267524165634"></a>Sets the image for this progress bar. </p>
</td>
</tr>
<tr id="row23271973165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1412866928165634"><a name="p1412866928165634"></a><a name="p1412866928165634"></a><a href="graphic.md#ga10723293ab9e384907dd9dacbc9ad448">SetImage</a> (const <a href="ohos-imageinfo.md">ImageInfo</a> *foregroundImage, const <a href="ohos-imageinfo.md">ImageInfo</a> *backgroundImage=nullptr)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p317619944165634"><a name="p317619944165634"></a><a name="p317619944165634"></a>void </p>
<p id="p548586402165634"><a name="p548586402165634"></a><a name="p548586402165634"></a>Sets the image as a pixel map for this progress bar. </p>
</td>
</tr>
<tr id="row1772312169165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p927478133165634"><a name="p927478133165634"></a><a name="p927478133165634"></a><a href="graphic.md#ga747a29652b441a06d09a97a297aae9bb">SetStep</a> (uint16_t step)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p669196251165634"><a name="p669196251165634"></a><a name="p669196251165634"></a>void </p>
<p id="p880291016165634"><a name="p880291016165634"></a><a name="p880291016165634"></a>Sets the step for this progress bar. </p>
</td>
</tr>
<tr id="row1656742499165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1770020804165634"><a name="p1770020804165634"></a><a name="p1770020804165634"></a><a href="graphic.md#ga9c1678604605a54c2e338d283c46866d">GetStep</a> () const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p252406535165634"><a name="p252406535165634"></a><a name="p252406535165634"></a>uint16_t </p>
<p id="p80263159165634"><a name="p80263159165634"></a><a name="p80263159165634"></a>Obtains the current step of this progress bar. </p>
</td>
</tr>
<tr id="row1859975658165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p2111042957165634"><a name="p2111042957165634"></a><a name="p2111042957165634"></a><a href="graphic.md#ga6817b5178e93e5f16f2b420cf5a171c1">SetBackgroundStyle</a> (const <a href="ohos-style.md">Style</a> &style)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1413423135165634"><a name="p1413423135165634"></a><a name="p1413423135165634"></a>void </p>
<p id="p1044107025165634"><a name="p1044107025165634"></a><a name="p1044107025165634"></a>Sets the background style for this progress bar. </p>
</td>
</tr>
<tr id="row1213352915165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p235709430165634"><a name="p235709430165634"></a><a name="p235709430165634"></a><a href="graphic.md#ga23acea0a42587746e35ec5f3a74af59f">SetBackgroundStyle</a> (uint8_t key, int64_t value)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1876491480165634"><a name="p1876491480165634"></a><a name="p1876491480165634"></a>void </p>
<p id="p127460731165634"><a name="p127460731165634"></a><a name="p127460731165634"></a>Sets a background style for this progress bar. </p>
</td>
</tr>
<tr id="row589387002165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1722733660165634"><a name="p1722733660165634"></a><a name="p1722733660165634"></a><a href="graphic.md#gac2ca1212c23c11405b12ae0a46c7eff1">GetBackgroundStyle</a> () const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1870821460165634"><a name="p1870821460165634"></a><a name="p1870821460165634"></a>const <a href="ohos-style.md">Style</a> & </p>
<p id="p1379475966165634"><a name="p1379475966165634"></a><a name="p1379475966165634"></a>Obtains the background style of this progress bar. </p>
</td>
</tr>
<tr id="row746719038165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p68968429165634"><a name="p68968429165634"></a><a name="p68968429165634"></a><a href="graphic.md#ga946d3f2c39a79d45149118536b2557a9">GetBackgroundStyle</a> (uint8_t key) const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p686370237165634"><a name="p686370237165634"></a><a name="p686370237165634"></a>int64_t </p>
<p id="p1774945944165634"><a name="p1774945944165634"></a><a name="p1774945944165634"></a>Obtains the value of a background style of this progress bar. </p>
</td>
</tr>
<tr id="row1600366759165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1200189418165634"><a name="p1200189418165634"></a><a name="p1200189418165634"></a><a href="graphic.md#gaccebcfa35f98f9bc6be4bb8cc53eb11c">SetForegroundStyle</a> (const <a href="ohos-style.md">Style</a> &style)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p771252142165634"><a name="p771252142165634"></a><a name="p771252142165634"></a>void </p>
<p id="p769062285165634"><a name="p769062285165634"></a><a name="p769062285165634"></a>Sets the foreground style for this progress bar. </p>
</td>
</tr>
<tr id="row1065034701165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1204846828165634"><a name="p1204846828165634"></a><a name="p1204846828165634"></a><a href="graphic.md#gae6386ca25603e42f06087f6b2ef65bae">SetForegroundStyle</a> (uint8_t key, int64_t value)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1612365302165634"><a name="p1612365302165634"></a><a name="p1612365302165634"></a>void </p>
<p id="p1571156355165634"><a name="p1571156355165634"></a><a name="p1571156355165634"></a>Sets a foreground style for this progress bar. </p>
</td>
</tr>
<tr id="row1285965241165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1581699163165634"><a name="p1581699163165634"></a><a name="p1581699163165634"></a><a href="graphic.md#gac77f945f375f333f80bd70254b5c1f96">GetForegroundStyle</a> () const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p690069263165634"><a name="p690069263165634"></a><a name="p690069263165634"></a>const <a href="ohos-style.md">Style</a> & </p>
<p id="p813260701165634"><a name="p813260701165634"></a><a name="p813260701165634"></a>Obtains the foreground style of this progress bar. </p>
</td>
</tr>
<tr id="row1055359028165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1951418553165634"><a name="p1951418553165634"></a><a name="p1951418553165634"></a><a href="graphic.md#ga74cd121dd1794d7e8d905b233bd98217">GetForegroundStyle</a> (uint8_t key) const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1954714617165634"><a name="p1954714617165634"></a><a name="p1954714617165634"></a>int64_t </p>
<p id="p4075384165634"><a name="p4075384165634"></a><a name="p4075384165634"></a>Obtains the value of a foreground style of this progress bar. </p>
</td>
</tr>
<tr id="row286471056165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1136354619165634"><a name="p1136354619165634"></a><a name="p1136354619165634"></a><a href="graphic.md#gabdc0eb4d279212ea7c3ea7a1f9a85e13">SetCapType</a> (<a href="graphic.md#ga2db3928cdf793f4950245a6841dd43d6">CapType</a> cap)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1696745304165634"><a name="p1696745304165634"></a><a name="p1696745304165634"></a>void </p>
<p id="p1801401053165634"><a name="p1801401053165634"></a><a name="p1801401053165634"></a>Sets the type of caps on the background and foreground of the progress bar. </p>
</td>
</tr>
<tr id="row1987768101165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1707833345165634"><a name="p1707833345165634"></a><a name="p1707833345165634"></a><a href="graphic.md#ga7aad5b50d945efe5f9304bc978b2001c">UIView</a> ()</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p2034178567165634"><a name="p2034178567165634"></a><a name="p2034178567165634"></a> </p>
<p id="p1382303774165634"><a name="p1382303774165634"></a><a name="p1382303774165634"></a>A default constructor used to create an <strong id="b123515017165634"><a name="b123515017165634"></a><a name="b123515017165634"></a><a href="ohos-uiview.md">UIView</a></strong> instance. </p>
</td>
</tr>
<tr id="row216639869165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1476918358165634"><a name="p1476918358165634"></a><a name="p1476918358165634"></a><a href="graphic.md#ga57d429bb1cd71782f3b825f1bc6b9362">UIView</a> (const char *id)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1075649263165634"><a name="p1075649263165634"></a><a name="p1075649263165634"></a> </p>
<p id="p359465346165634"><a name="p359465346165634"></a><a name="p359465346165634"></a>A constructor used to create an <strong id="b1876949424165634"><a name="b1876949424165634"></a><a name="b1876949424165634"></a><a href="ohos-uiview.md">UIView</a></strong> instance. </p>
</td>
</tr>
<tr id="row1442173352165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1273401681165634"><a name="p1273401681165634"></a><a name="p1273401681165634"></a><a href="graphic.md#ga17f0ffc1090bdcce0f88288da5962012">~UIView</a> ()</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p954212481165634"><a name="p954212481165634"></a><a name="p954212481165634"></a>virtual </p>
<p id="p1703078330165634"><a name="p1703078330165634"></a><a name="p1703078330165634"></a>A destructor used to delete the <strong id="b1264324803165634"><a name="b1264324803165634"></a><a name="b1264324803165634"></a><a href="ohos-uiview.md">UIView</a></strong> instance. </p>
</td>
</tr>
<tr id="row1888821696165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1842656778165634"><a name="p1842656778165634"></a><a name="p1842656778165634"></a><a href="graphic.md#gab70473cd0d8fe7c9d4bb817caeee9153">OnPostDraw</a> (const <a href="ohos-rect.md">Rect</a> &invalidatedArea)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1101086663165634"><a name="p1101086663165634"></a><a name="p1101086663165634"></a>virtual void </p>
<p id="p804810092165634"><a name="p804810092165634"></a><a name="p804810092165634"></a>Called after a view is drawn. </p>
</td>
</tr>
<tr id="row32024812165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p240064214165634"><a name="p240064214165634"></a><a name="p240064214165634"></a><a href="graphic.md#ga81726238adeda1efa989be6ed4f4fe5b">ReMeasure</a> ()</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p651168844165634"><a name="p651168844165634"></a><a name="p651168844165634"></a>virtual void </p>
<p id="p1290278998165634"><a name="p1290278998165634"></a><a name="p1290278998165634"></a>Remeasures the view size. </p>
</td>
</tr>
<tr id="row1507374816165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1447339812165634"><a name="p1447339812165634"></a><a name="p1447339812165634"></a><a href="graphic.md#ga2a9a38b8450fbb196277238a51fbbf99">Invalidate</a> ()</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1337877669165634"><a name="p1337877669165634"></a><a name="p1337877669165634"></a>void </p>
<p id="p1758601604165634"><a name="p1758601604165634"></a><a name="p1758601604165634"></a>Refreshes the invalidated area of the view. </p>
</td>
</tr>
<tr id="row1419353821165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p643036450165634"><a name="p643036450165634"></a><a name="p643036450165634"></a><a href="graphic.md#gaf0e6b65ced8b931642f2a80c195962d2">InvalidateRect</a> (const <a href="ohos-rect.md">Rect</a> &invalidatedArea)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p94580761165634"><a name="p94580761165634"></a><a name="p94580761165634"></a>void </p>
<p id="p922774176165634"><a name="p922774176165634"></a><a name="p922774176165634"></a>Refreshes a view in a specified invalidated area. </p>
</td>
</tr>
<tr id="row1199015672165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1531974157165634"><a name="p1531974157165634"></a><a name="p1531974157165634"></a><a href="graphic.md#gac311aa47301d727c35fc31f8630d016e">OnLongPressEvent</a> (const <a href="ohos-longpressevent.md">LongPressEvent</a> &event)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p346165970165634"><a name="p346165970165634"></a><a name="p346165970165634"></a>virtual bool </p>
<p id="p346060419165634"><a name="p346060419165634"></a><a name="p346060419165634"></a>Called when the view is long pressed. </p>
</td>
</tr>
<tr id="row1509855479165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1404939488165634"><a name="p1404939488165634"></a><a name="p1404939488165634"></a><a href="graphic.md#gac0e10556ff99b8a92bfb11df6456d605">OnDragStartEvent</a> (const <a href="ohos-dragevent.md">DragEvent</a> &event)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p303423148165634"><a name="p303423148165634"></a><a name="p303423148165634"></a>virtual bool </p>
<p id="p742331502165634"><a name="p742331502165634"></a><a name="p742331502165634"></a>Called when the view starts to drag. </p>
</td>
</tr>
<tr id="row768376421165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1911541957165634"><a name="p1911541957165634"></a><a name="p1911541957165634"></a><a href="graphic.md#gafa544ff2d27785a9410a80689f1ad3b1">OnPressEvent</a> (const <a href="ohos-pressevent.md">PressEvent</a> &event)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1396882586165634"><a name="p1396882586165634"></a><a name="p1396882586165634"></a>virtual void </p>
<p id="p1255918822165634"><a name="p1255918822165634"></a><a name="p1255918822165634"></a>Called when the view is pressed. </p>
</td>
</tr>
<tr id="row1360215646165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p866560140165634"><a name="p866560140165634"></a><a name="p866560140165634"></a><a href="graphic.md#ga7bd1a74563b059b03fbf66f9add53ee3">OnReleaseEvent</a> (const <a href="ohos-releaseevent.md">ReleaseEvent</a> &event)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p733574036165634"><a name="p733574036165634"></a><a name="p733574036165634"></a>virtual void </p>
<p id="p1576197495165634"><a name="p1576197495165634"></a><a name="p1576197495165634"></a>Called when the view is released. </p>
</td>
</tr>
<tr id="row1419795531165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p2051334951165634"><a name="p2051334951165634"></a><a name="p2051334951165634"></a><a href="graphic.md#ga8f01ff25a33b20df0758f564148e579d">OnCancelEvent</a> (const <a href="ohos-cancelevent.md">CancelEvent</a> &event)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1366009165634"><a name="p1366009165634"></a><a name="p1366009165634"></a>virtual void </p>
<p id="p2022034993165634"><a name="p2022034993165634"></a><a name="p2022034993165634"></a>Called when a click event on the view is canceled. </p>
</td>
</tr>
<tr id="row1131559138165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1839192221165634"><a name="p1839192221165634"></a><a name="p1839192221165634"></a><a href="graphic.md#gad8e3cf5f0dd003a6aa932ef04e7b59f2">SetOnDragListener</a> (<a href="ohos-uiview-ondraglistener.md">OnDragListener</a> *onDragListener)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1534224289165634"><a name="p1534224289165634"></a><a name="p1534224289165634"></a>void </p>
<p id="p317867761165634"><a name="p317867761165634"></a><a name="p317867761165634"></a>Sets a drag event listener for the view. </p>
</td>
</tr>
<tr id="row116578017165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p2021238756165634"><a name="p2021238756165634"></a><a name="p2021238756165634"></a><a href="graphic.md#ga45a02cba4887c5c0b8e243941bcdc5cb">GetOnDragListener</a> ()</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p716799578165634"><a name="p716799578165634"></a><a name="p716799578165634"></a><a href="ohos-uiview-ondraglistener.md">OnDragListener</a> *& </p>
<p id="p1052966290165634"><a name="p1052966290165634"></a><a name="p1052966290165634"></a>Obtains the drag event listener for the view. </p>
</td>
</tr>
<tr id="row138899081165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1968719078165634"><a name="p1968719078165634"></a><a name="p1968719078165634"></a><a href="graphic.md#ga4564bf8d8c7184e9c02bf33c9e171fa3">SetOnClickListener</a> (<a href="ohos-uiview-onclicklistener.md">OnClickListener</a> *onClickListener)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p523876173165634"><a name="p523876173165634"></a><a name="p523876173165634"></a>void </p>
<p id="p223070113165634"><a name="p223070113165634"></a><a name="p223070113165634"></a>Sets a click event listener for the view. </p>
</td>
</tr>
<tr id="row2074297399165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p762734078165634"><a name="p762734078165634"></a><a name="p762734078165634"></a><a href="graphic.md#ga35e885cb380c37245fa4305bba10cd4a">GetOnClickListener</a> ()</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p315399750165634"><a name="p315399750165634"></a><a name="p315399750165634"></a><a href="ohos-uiview-onclicklistener.md">OnClickListener</a> *& </p>
<p id="p920390392165634"><a name="p920390392165634"></a><a name="p920390392165634"></a>Obtains the click event listener for the view. </p>
</td>
</tr>
<tr id="row82862699165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1285148246165634"><a name="p1285148246165634"></a><a name="p1285148246165634"></a><a href="graphic.md#gabcbe7a0adce600424f7f0d5a7396eb5b">SetOnLongPressListener</a> (<a href="ohos-uiview-onlongpresslistener.md">OnLongPressListener</a> *onLongPressListener)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1900037145165634"><a name="p1900037145165634"></a><a name="p1900037145165634"></a>void </p>
<p id="p655886561165634"><a name="p655886561165634"></a><a name="p655886561165634"></a>Sets a long-press event listener for the view. </p>
</td>
</tr>
<tr id="row1919356770165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p615665923165634"><a name="p615665923165634"></a><a name="p615665923165634"></a><a href="graphic.md#gaafd4d354f5f111e758d046109fd7f656">GetOnLongPressListener</a> ()</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p530759181165634"><a name="p530759181165634"></a><a name="p530759181165634"></a><a href="ohos-uiview-onlongpresslistener.md">OnLongPressListener</a> *& </p>
<p id="p387547160165634"><a name="p387547160165634"></a><a name="p387547160165634"></a>Obtains the long-press event listener for the view. </p>
</td>
</tr>
<tr id="row1508623428165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p652763732165634"><a name="p652763732165634"></a><a name="p652763732165634"></a><a href="graphic.md#gadd697fbf481f98d9d6ca8b67390071af">SetOnTouchListener</a> (<a href="ohos-uiview-ontouchlistener.md">OnTouchListener</a> *onTouchListener)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1637384550165634"><a name="p1637384550165634"></a><a name="p1637384550165634"></a>void </p>
<p id="p1649618151165634"><a name="p1649618151165634"></a><a name="p1649618151165634"></a>Sets a touch event listener for the view. </p>
</td>
</tr>
<tr id="row1135174290165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p793004815165634"><a name="p793004815165634"></a><a name="p793004815165634"></a><a href="graphic.md#gae7c65c68653103dae85acdcef78777a6">GetTouchListener</a> ()</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p273575597165634"><a name="p273575597165634"></a><a name="p273575597165634"></a><a href="ohos-uiview-ontouchlistener.md">OnTouchListener</a> *& </p>
<p id="p141741976165634"><a name="p141741976165634"></a><a name="p141741976165634"></a>Obtains the touch event listener for the view. </p>
</td>
</tr>
<tr id="row712640357165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1173589900165634"><a name="p1173589900165634"></a><a name="p1173589900165634"></a><a href="graphic.md#gaea9f334f2481e1c03a2cd8f3078d7c72">GetTargetView</a> (const <a href="ohos-point.md">Point</a> &point, <a href="ohos-uiview.md">UIView</a> **last)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1836748147165634"><a name="p1836748147165634"></a><a name="p1836748147165634"></a>virtual void </p>
<p id="p997029812165634"><a name="p997029812165634"></a><a name="p997029812165634"></a>Obtains the top-level view based on specified coordinates. </p>
</td>
</tr>
<tr id="row1803093085165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p291079456165634"><a name="p291079456165634"></a><a name="p291079456165634"></a><a href="graphic.md#gaeea67a3a84b4ffe9bfeda418b82184cc">SetParent</a> (<a href="ohos-uiview.md">UIView</a> *parent)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1827431276165634"><a name="p1827431276165634"></a><a name="p1827431276165634"></a>void </p>
<p id="p1132925156165634"><a name="p1132925156165634"></a><a name="p1132925156165634"></a>Sets the parent view for the view. </p>
</td>
</tr>
<tr id="row1027206418165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1012680718165634"><a name="p1012680718165634"></a><a name="p1012680718165634"></a><a href="graphic.md#ga706530e4a38108615d5e0c918685ec96">GetParent</a> () const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p575659283165634"><a name="p575659283165634"></a><a name="p575659283165634"></a><a href="ohos-uiview.md">UIView</a> * </p>
<p id="p773292375165634"><a name="p773292375165634"></a><a name="p773292375165634"></a>Obtains the parent view of the view. </p>
</td>
</tr>
<tr id="row910005267165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p891664798165634"><a name="p891664798165634"></a><a name="p891664798165634"></a><a href="graphic.md#ga02bec5de07d93cabc45affba79eba4ad">SetNextSibling</a> (<a href="ohos-uiview.md">UIView</a> *sibling)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1544201871165634"><a name="p1544201871165634"></a><a name="p1544201871165634"></a>void </p>
<p id="p1238876001165634"><a name="p1238876001165634"></a><a name="p1238876001165634"></a>Sets the next sibling view for the view. </p>
</td>
</tr>
<tr id="row330542268165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p375578365165634"><a name="p375578365165634"></a><a name="p375578365165634"></a><a href="graphic.md#gab0030977b30ddc9f2e15dbc2f58937e6">GetNextSibling</a> () const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p640359165165634"><a name="p640359165165634"></a><a name="p640359165165634"></a><a href="ohos-uiview.md">UIView</a> * </p>
<p id="p166738672165634"><a name="p166738672165634"></a><a name="p166738672165634"></a>Obtains the next sibling view of the view. </p>
</td>
</tr>
<tr id="row2109802205165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p329914348165634"><a name="p329914348165634"></a><a name="p329914348165634"></a><a href="graphic.md#ga07e7e1f268bd6ce975f4f0f8487af5d0">SetVisible</a> (bool visible)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p599255837165634"><a name="p599255837165634"></a><a name="p599255837165634"></a>virtual void </p>
<p id="p1942283280165634"><a name="p1942283280165634"></a><a name="p1942283280165634"></a>Sets whether the view is visible. </p>
</td>
</tr>
<tr id="row891365168165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1081474353165634"><a name="p1081474353165634"></a><a name="p1081474353165634"></a><a href="graphic.md#gaee178fc0a86ac03a6bdf2ade0c1914c8">IsVisible</a> () const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p757329650165634"><a name="p757329650165634"></a><a name="p757329650165634"></a>bool </p>
<p id="p865920905165634"><a name="p865920905165634"></a><a name="p865920905165634"></a>Checks whether the view is visible. </p>
</td>
</tr>
<tr id="row1222042274165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1046084360165634"><a name="p1046084360165634"></a><a name="p1046084360165634"></a><a href="graphic.md#gaf9fb55fd9aa397f7158f1515e90bce02">SetTouchable</a> (bool touch)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p2090570480165634"><a name="p2090570480165634"></a><a name="p2090570480165634"></a>void </p>
<p id="p1742796662165634"><a name="p1742796662165634"></a><a name="p1742796662165634"></a>Sets whether the view is touchable. </p>
</td>
</tr>
<tr id="row120230688165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1850331374165634"><a name="p1850331374165634"></a><a name="p1850331374165634"></a><a href="graphic.md#ga502a53fb77b260fa36b5b3adf82e2340">IsTouchable</a> () const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1199679011165634"><a name="p1199679011165634"></a><a name="p1199679011165634"></a>bool </p>
<p id="p1297967689165634"><a name="p1297967689165634"></a><a name="p1297967689165634"></a>Checks whether the view is touchable. </p>
</td>
</tr>
<tr id="row1565555763165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p577483483165634"><a name="p577483483165634"></a><a name="p577483483165634"></a><a href="graphic.md#gab06abe0fe824c048f3b72974f9a8f0d0">SetDraggable</a> (bool draggable)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p137243170165634"><a name="p137243170165634"></a><a name="p137243170165634"></a>void </p>
<p id="p1205183110165634"><a name="p1205183110165634"></a><a name="p1205183110165634"></a>Sets whether the view is draggable. </p>
</td>
</tr>
<tr id="row1639501380165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1848461662165634"><a name="p1848461662165634"></a><a name="p1848461662165634"></a><a href="graphic.md#ga25bb796ff400c767d622cbed280fc500">IsDraggable</a> () const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p2017660356165634"><a name="p2017660356165634"></a><a name="p2017660356165634"></a>bool </p>
<p id="p1749206738165634"><a name="p1749206738165634"></a><a name="p1749206738165634"></a>Checks whether the view is draggable. </p>
</td>
</tr>
<tr id="row553732786165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p481764073165634"><a name="p481764073165634"></a><a name="p481764073165634"></a><a href="graphic.md#ga6c08e49bf7a82a7ebaef0f251e7a6f85">SetDragParentInstead</a> (bool dragParentInstead)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1504182406165634"><a name="p1504182406165634"></a><a name="p1504182406165634"></a>void </p>
<p id="p1733542353165634"><a name="p1733542353165634"></a><a name="p1733542353165634"></a>Sets whether to transfer the drag event to the parent view for processing when the view is being dragged. </p>
</td>
</tr>
<tr id="row2129801186165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1973596956165634"><a name="p1973596956165634"></a><a name="p1973596956165634"></a><a href="graphic.md#gaf0c462bc31e779b1898ad4cdfdad6faf">IsDragParentInstead</a> () const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p608739943165634"><a name="p608739943165634"></a><a name="p608739943165634"></a>bool </p>
<p id="p1623420314165634"><a name="p1623420314165634"></a><a name="p1623420314165634"></a>Obtains whether the view transfers a drag event to the parent view for processing. </p>
</td>
</tr>
<tr id="row825521885165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p249869935165634"><a name="p249869935165634"></a><a name="p249869935165634"></a><a href="graphic.md#ga86cb8d364f18494d67636c55babced5c">GetRect</a> () const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p2051968054165634"><a name="p2051968054165634"></a><a name="p2051968054165634"></a><a href="ohos-rect.md">Rect</a> </p>
<p id="p822145322165634"><a name="p822145322165634"></a><a name="p822145322165634"></a>Obtains the absolute rectangle area of the view. When the view has deformation such as rotation, the rectangle area is the intersection set of the absolute rectangle area and deformation matrix. </p>
</td>
</tr>
<tr id="row1682545714165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1649014831165634"><a name="p1649014831165634"></a><a name="p1649014831165634"></a><a href="graphic.md#ga06e79704a19f2a238982076cac3d059b">GetVisibleRect</a> () const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p818719559165634"><a name="p818719559165634"></a><a name="p818719559165634"></a><a href="ohos-rect.md">Rect</a> </p>
<p id="p1905920319165634"><a name="p1905920319165634"></a><a name="p1905920319165634"></a>Obtains the visible absolute rectangle area of the view. </p>
</td>
</tr>
<tr id="row61961299165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1320540667165634"><a name="p1320540667165634"></a><a name="p1320540667165634"></a><a href="graphic.md#gab3f8993b3953f27bfc61d53429916cba">GetMaskedRect</a> () const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p2132850981165634"><a name="p2132850981165634"></a><a name="p2132850981165634"></a><a href="ohos-rect.md">Rect</a> </p>
<p id="p1056214162165634"><a name="p1056214162165634"></a><a name="p1056214162165634"></a>Obtains the valid absolute rectangle area of the view. The valid area refers to the area where the view can be displayed. Generally, the valid area is the same as the visible view area, but they may be different in the grid layout. </p>
</td>
</tr>
<tr id="row1121718711165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p590330944165634"><a name="p590330944165634"></a><a name="p590330944165634"></a><a href="graphic.md#ga64cf308a09999def1192f9c4e0f17f0a">GetOrigRect</a> () const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p671204506165634"><a name="p671204506165634"></a><a name="p671204506165634"></a><a href="ohos-rect.md">Rect</a> </p>
<p id="p315896213165634"><a name="p315896213165634"></a><a name="p315896213165634"></a>Obtains the absolute rectangle area of the view. </p>
</td>
</tr>
<tr id="row1498532651165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1725298213165634"><a name="p1725298213165634"></a><a name="p1725298213165634"></a><a href="graphic.md#ga9db88eae712676359d02a92be14fa316">GetContentRect</a> ()</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p236802941165634"><a name="p236802941165634"></a><a name="p236802941165634"></a>virtual <a href="ohos-rect.md">Rect</a> </p>
<p id="p814108172165634"><a name="p814108172165634"></a><a name="p814108172165634"></a>Obtains the content of the absolute rectangle area of the view. This area excludes padding. </p>
</td>
</tr>
<tr id="row649849379165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1689444094165634"><a name="p1689444094165634"></a><a name="p1689444094165634"></a><a href="graphic.md#gae9b96837fa1d45648a2a6fbbfcc5eb4a">GetRelativeRect</a> () const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p378485374165634"><a name="p378485374165634"></a><a name="p378485374165634"></a><a href="ohos-rect.md">Rect</a> </p>
<p id="p400917314165634"><a name="p400917314165634"></a><a name="p400917314165634"></a>Obtains the rectangular area of the view relative to the parent view, that is, the rectangular area relative to the coordinates of the parent view. </p>
</td>
</tr>
<tr id="row233505962165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p2120649316165634"><a name="p2120649316165634"></a><a name="p2120649316165634"></a><a href="graphic.md#gae6c5f3bcf99dc837bcecd60c38d3df5a">ResizeVisibleArea</a> (int16_t x, int16_t y, int16_t width, int16_t height)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1720891498165634"><a name="p1720891498165634"></a><a name="p1720891498165634"></a>void </p>
<p id="p895595222165634"><a name="p895595222165634"></a><a name="p895595222165634"></a>Adjusts the size of the visible area. This operation may affect the final display size. </p>
</td>
</tr>
<tr id="row1401336227165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1235398756165634"><a name="p1235398756165634"></a><a name="p1235398756165634"></a><a href="graphic.md#ga90cf8cffb98d71c30d6fc1d118442dbd">GetWidth</a> ()</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p462401490165634"><a name="p462401490165634"></a><a name="p462401490165634"></a>virtual int16_t </p>
<p id="p1356091375165634"><a name="p1356091375165634"></a><a name="p1356091375165634"></a>Obtains the width for the view. </p>
</td>
</tr>
<tr id="row880955777165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p845003724165634"><a name="p845003724165634"></a><a name="p845003724165634"></a><a href="graphic.md#ga9b35f4603a561c7a9a29b023a022ac97">GetHeight</a> ()</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1677504126165634"><a name="p1677504126165634"></a><a name="p1677504126165634"></a>virtual int16_t </p>
<p id="p1763269971165634"><a name="p1763269971165634"></a><a name="p1763269971165634"></a>Obtains the height for the view. </p>
</td>
</tr>
<tr id="row191615513165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1513749804165634"><a name="p1513749804165634"></a><a name="p1513749804165634"></a><a href="graphic.md#gae985b607d2f0701911778bf20d640ccd">Resize</a> (int16_t width, int16_t height)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1653944782165634"><a name="p1653944782165634"></a><a name="p1653944782165634"></a>virtual void </p>
<p id="p9719803165634"><a name="p9719803165634"></a><a name="p9719803165634"></a>Adjusts the size of the view. </p>
</td>
</tr>
<tr id="row1726145057165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1369613141165634"><a name="p1369613141165634"></a><a name="p1369613141165634"></a><a href="graphic.md#gaded403626558d28e62bf5632ccbb24b5">SetX</a> (int16_t x)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p413875377165634"><a name="p413875377165634"></a><a name="p413875377165634"></a>virtual void </p>
<p id="p1362563940165634"><a name="p1362563940165634"></a><a name="p1362563940165634"></a>Sets the x-coordinate for the view. </p>
</td>
</tr>
<tr id="row1892381406165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1037764722165634"><a name="p1037764722165634"></a><a name="p1037764722165634"></a><a href="graphic.md#ga89dc5f8fb1cb4b2259dc0439185359f1">GetX</a> () const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p55333942165634"><a name="p55333942165634"></a><a name="p55333942165634"></a>int16_t </p>
<p id="p1037230536165634"><a name="p1037230536165634"></a><a name="p1037230536165634"></a>Obtains the x-coordinate for the view. </p>
</td>
</tr>
<tr id="row927239799165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p540428690165634"><a name="p540428690165634"></a><a name="p540428690165634"></a><a href="graphic.md#gaaa8edc224cf1c7deb2724fb225960877">SetY</a> (int16_t y)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p918340870165634"><a name="p918340870165634"></a><a name="p918340870165634"></a>virtual void </p>
<p id="p197525903165634"><a name="p197525903165634"></a><a name="p197525903165634"></a>Sets the y-coordinate for the view. </p>
</td>
</tr>
<tr id="row206137398165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p797278554165634"><a name="p797278554165634"></a><a name="p797278554165634"></a><a href="graphic.md#ga193619d649204b0e9bb854d3b30275c3">GetY</a> () const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p2344758165634"><a name="p2344758165634"></a><a name="p2344758165634"></a>int16_t </p>
<p id="p933251066165634"><a name="p933251066165634"></a><a name="p933251066165634"></a>Obtains the y-coordinate for the view. </p>
</td>
</tr>
<tr id="row682883880165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1939939887165634"><a name="p1939939887165634"></a><a name="p1939939887165634"></a><a href="graphic.md#gab34233f6aeae330b025969137d03e67a">SetPosition</a> (int16_t x, int16_t y)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p420596475165634"><a name="p420596475165634"></a><a name="p420596475165634"></a>virtual void </p>
<p id="p65573075165634"><a name="p65573075165634"></a><a name="p65573075165634"></a>Sets the position for the view. </p>
</td>
</tr>
<tr id="row1221264720165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p20333696165634"><a name="p20333696165634"></a><a name="p20333696165634"></a><a href="graphic.md#gaf8ce4c009f23b7175b2b34bac4a74262">SetPosition</a> (int16_t x, int16_t y, int16_t width, int16_t height)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p75757359165634"><a name="p75757359165634"></a><a name="p75757359165634"></a>virtual void </p>
<p id="p452637453165634"><a name="p452637453165634"></a><a name="p452637453165634"></a>Adjusts the position and size of the view. </p>
</td>
</tr>
<tr id="row691794159165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1452100508165634"><a name="p1452100508165634"></a><a name="p1452100508165634"></a><a href="graphic.md#gab2ce8c11abbd55f40687f38a52511b11">IsViewGroup</a> () const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p794330395165634"><a name="p794330395165634"></a><a name="p794330395165634"></a>bool </p>
<p id="p482951361165634"><a name="p482951361165634"></a><a name="p482951361165634"></a>Checks whether the view is a container view. </p>
</td>
</tr>
<tr id="row2041293375165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1198718305165634"><a name="p1198718305165634"></a><a name="p1198718305165634"></a><a href="graphic.md#ga980fc6824c64cfae6af8657aee17af88">SetIntercept</a> (bool isIntercept)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1380427911165634"><a name="p1380427911165634"></a><a name="p1380427911165634"></a>void </p>
<p id="p659300551165634"><a name="p659300551165634"></a><a name="p659300551165634"></a>Sets whether to intercept the drag event. If intercepted, the view does not transfer the drag event to the parent view after local processing. </p>
</td>
</tr>
<tr id="row1257590643165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p876711978165634"><a name="p876711978165634"></a><a name="p876711978165634"></a><a href="graphic.md#ga8623abbbeff458c0cb2d7dc0d1f21e4a">SetTransformMap</a> (const <a href="ohos-transformmap.md">TransformMap</a> &transMap)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p453603322165634"><a name="p453603322165634"></a><a name="p453603322165634"></a>void </p>
<p id="p759849919165634"><a name="p759849919165634"></a><a name="p759849919165634"></a>Sets the affine transformation matrix. </p>
</td>
</tr>
<tr id="row581153157165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1664017417165634"><a name="p1664017417165634"></a><a name="p1664017417165634"></a><a href="graphic.md#gab8cee5a7052a88722768c8ed1324abc1">GetTransformMap</a> ()</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p973497337165634"><a name="p973497337165634"></a><a name="p973497337165634"></a><a href="ohos-transformmap.md">TransformMap</a> & </p>
<p id="p136307165634"><a name="p136307165634"></a><a name="p136307165634"></a>Obtains an affine transformation matrix. </p>
</td>
</tr>
<tr id="row214048456165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p4103241165634"><a name="p4103241165634"></a><a name="p4103241165634"></a><a href="graphic.md#ga0573aa25307c22319db4629781b5cad2">GetChildById</a> (const char *id) const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1482964355165634"><a name="p1482964355165634"></a><a name="p1482964355165634"></a>virtual <a href="ohos-uiview.md">UIView</a> * </p>
<p id="p1181176472165634"><a name="p1181176472165634"></a><a name="p1181176472165634"></a>Obtains the child view of a specified ID. </p>
</td>
</tr>
<tr id="row995467337165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1304991401165634"><a name="p1304991401165634"></a><a name="p1304991401165634"></a><a href="graphic.md#ga0caaa15c9b304673331e778a266be77f">SetViewId</a> (const char *id)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p626947783165634"><a name="p626947783165634"></a><a name="p626947783165634"></a>void </p>
<p id="p9361036165634"><a name="p9361036165634"></a><a name="p9361036165634"></a>Sets the view ID. </p>
</td>
</tr>
<tr id="row1205091183165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1025691155165634"><a name="p1025691155165634"></a><a name="p1025691155165634"></a><a href="graphic.md#gad6c7644bd2abfa3c92d80776b0bd1936">GetViewId</a> () const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1747738678165634"><a name="p1747738678165634"></a><a name="p1747738678165634"></a>const char * </p>
<p id="p1066777589165634"><a name="p1066777589165634"></a><a name="p1066777589165634"></a>Obtains the view ID. </p>
</td>
</tr>
<tr id="row1217075267165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1795245766165634"><a name="p1795245766165634"></a><a name="p1795245766165634"></a><a href="graphic.md#ga77a961aa53567c5214508b4569801c16">SetViewIndex</a> (int16_t <a href="utils.md#ga1d3748ca570dcb09a2fb28e8015107dd">index</a>)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p250165875165634"><a name="p250165875165634"></a><a name="p250165875165634"></a>void </p>
<p id="p83727846165634"><a name="p83727846165634"></a><a name="p83727846165634"></a>Sets the view index. </p>
</td>
</tr>
<tr id="row1504873662165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1459144916165634"><a name="p1459144916165634"></a><a name="p1459144916165634"></a><a href="graphic.md#ga62f51715b6d420a296ebe0296717b906">GetViewIndex</a> () const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p376939024165634"><a name="p376939024165634"></a><a name="p376939024165634"></a>int16_t </p>
<p id="p1139814011165634"><a name="p1139814011165634"></a><a name="p1139814011165634"></a>Obtains the view index. </p>
</td>
</tr>
<tr id="row393805443165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1395674636165634"><a name="p1395674636165634"></a><a name="p1395674636165634"></a><a href="graphic.md#gaca871fa2f8219e7ea9388e212d1f1e69">LayoutChildren</a> (bool neeInvalidate=false)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p2112743261165634"><a name="p2112743261165634"></a><a name="p2112743261165634"></a>virtual void </p>
<p id="p1107795944165634"><a name="p1107795944165634"></a><a name="p1107795944165634"></a>Lays out all child views according to the preset arrangement mode. </p>
</td>
</tr>
<tr id="row673104420165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p715705221165634"><a name="p715705221165634"></a><a name="p715705221165634"></a><a href="graphic.md#ga443b86ee9275b0421b37a47bad3264dc">LayoutCenterOfParent</a> (int16_t xOffSet=0, int16_t yOffset=0)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1429555673165634"><a name="p1429555673165634"></a><a name="p1429555673165634"></a>void </p>
<p id="p349258869165634"><a name="p349258869165634"></a><a name="p349258869165634"></a>Lays out the view in the center of the parent view. </p>
</td>
</tr>
<tr id="row1536536555165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p371918718165634"><a name="p371918718165634"></a><a name="p371918718165634"></a><a href="graphic.md#ga94999b271f27cd5d6bfaf303f7d5c708">LayoutLeftOfParent</a> (int16_t offset=0)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1644576334165634"><a name="p1644576334165634"></a><a name="p1644576334165634"></a>void </p>
<p id="p1439391126165634"><a name="p1439391126165634"></a><a name="p1439391126165634"></a>Lays out the view on the left of the parent view. </p>
</td>
</tr>
<tr id="row1278726334165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1249671838165634"><a name="p1249671838165634"></a><a name="p1249671838165634"></a><a href="graphic.md#ga479528ed259b5539e423955f2b60517d">LayoutRightOfParent</a> (int16_t offset=0)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1857316861165634"><a name="p1857316861165634"></a><a name="p1857316861165634"></a>void </p>
<p id="p1015041302165634"><a name="p1015041302165634"></a><a name="p1015041302165634"></a>Lays out the view on the right of the parent view. </p>
</td>
</tr>
<tr id="row1993003725165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p455546693165634"><a name="p455546693165634"></a><a name="p455546693165634"></a><a href="graphic.md#ga859288ea61ad23ba7e381bbc07769e83">LayoutTopOfParent</a> (int16_t offset=0)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1804805428165634"><a name="p1804805428165634"></a><a name="p1804805428165634"></a>void </p>
<p id="p611247256165634"><a name="p611247256165634"></a><a name="p611247256165634"></a>Lays out the view on the top of the parent view. </p>
</td>
</tr>
<tr id="row199285287165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p872157556165634"><a name="p872157556165634"></a><a name="p872157556165634"></a><a href="graphic.md#ga809aeee4792ae58218a0bcfcb94d5cdc">LayoutBottomOfParent</a> (int16_t offset=0)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1830522764165634"><a name="p1830522764165634"></a><a name="p1830522764165634"></a>void </p>
<p id="p656538706165634"><a name="p656538706165634"></a><a name="p656538706165634"></a>Lays out the view on the bottom of the parent view. </p>
</td>
</tr>
<tr id="row933876315165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1988911479165634"><a name="p1988911479165634"></a><a name="p1988911479165634"></a><a href="graphic.md#gac7f5f2584c716a56fee3783f8dea6246">AlignLeftToSibling</a> (const char *id, int16_t offset=0)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1234807200165634"><a name="p1234807200165634"></a><a name="p1234807200165634"></a>void </p>
<p id="p1959765545165634"><a name="p1959765545165634"></a><a name="p1959765545165634"></a>Aligns the view with the left of a sibling view. </p>
</td>
</tr>
<tr id="row1839878621165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1143204224165634"><a name="p1143204224165634"></a><a name="p1143204224165634"></a><a href="graphic.md#gabb1ac454cdf95593c1e387d5e272433c">AlignRightToSibling</a> (const char *id, int16_t offset=0)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p2037738160165634"><a name="p2037738160165634"></a><a name="p2037738160165634"></a>void </p>
<p id="p1576066348165634"><a name="p1576066348165634"></a><a name="p1576066348165634"></a>Aligns the view with the right of a sibling view. </p>
</td>
</tr>
<tr id="row1010076603165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1300768347165634"><a name="p1300768347165634"></a><a name="p1300768347165634"></a><a href="graphic.md#ga903d7cbc59bac06d728b7f6435c9a504">AlignTopToSibling</a> (const char *id, int16_t offset=0)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1310753642165634"><a name="p1310753642165634"></a><a name="p1310753642165634"></a>void </p>
<p id="p1253121741165634"><a name="p1253121741165634"></a><a name="p1253121741165634"></a>Aligns the view with the top of a sibling view. </p>
</td>
</tr>
<tr id="row571295625165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1655722234165634"><a name="p1655722234165634"></a><a name="p1655722234165634"></a><a href="graphic.md#ga7607c3f9661932c495d080e9d92fb1a3">AlignBottomToSibling</a> (const char *id, int16_t offset=0)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p612932816165634"><a name="p612932816165634"></a><a name="p612932816165634"></a>void </p>
<p id="p226887713165634"><a name="p226887713165634"></a><a name="p226887713165634"></a>Aligns the view with the bottom of a sibling view. </p>
</td>
</tr>
<tr id="row1880777468165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1223433432165634"><a name="p1223433432165634"></a><a name="p1223433432165634"></a><a href="graphic.md#gac23776dbc2fce7ff30d57438abfa5230">AlignHorCenterToSibling</a> (const char *id, int16_t offset=0)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p80777207165634"><a name="p80777207165634"></a><a name="p80777207165634"></a>void </p>
<p id="p1044435797165634"><a name="p1044435797165634"></a><a name="p1044435797165634"></a>Aligns the view with the center of a sibling view in the x-axis. </p>
</td>
</tr>
<tr id="row1498087881165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p99257734165634"><a name="p99257734165634"></a><a name="p99257734165634"></a><a href="graphic.md#gad3caa27aa0cb73ec4656e7d23aa222de">AlignVerCenterToSibling</a> (const char *id, int16_t offset=0)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p977590689165634"><a name="p977590689165634"></a><a name="p977590689165634"></a>void </p>
<p id="p655611615165634"><a name="p655611615165634"></a><a name="p655611615165634"></a>Aligns the view with the center of a sibling view in the y-axis. </p>
</td>
</tr>
<tr id="row30589375165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1790613168165634"><a name="p1790613168165634"></a><a name="p1790613168165634"></a><a href="graphic.md#ga58f1a34a943c4492970f901d63bbc3d8">LayoutLeftToSibling</a> (const char *id, int16_t offset=0)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p928693288165634"><a name="p928693288165634"></a><a name="p928693288165634"></a>void </p>
<p id="p838348631165634"><a name="p838348631165634"></a><a name="p838348631165634"></a>Lays out the view on the left of a sibling view. </p>
</td>
</tr>
<tr id="row96539422165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1223165672165634"><a name="p1223165672165634"></a><a name="p1223165672165634"></a><a href="graphic.md#gac4cd64de5291759add164825a323a0d6">LayoutRightToSibling</a> (const char *id, int16_t offset=0)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1261274786165634"><a name="p1261274786165634"></a><a name="p1261274786165634"></a>void </p>
<p id="p953292219165634"><a name="p953292219165634"></a><a name="p953292219165634"></a>Lays out the view on the right of a sibling view. </p>
</td>
</tr>
<tr id="row1000067027165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p707193719165634"><a name="p707193719165634"></a><a name="p707193719165634"></a><a href="graphic.md#gaaa8385807e3a9bea46f8dcc326252a70">LayoutTopToSibling</a> (const char *id, int16_t offset=0)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p136834705165634"><a name="p136834705165634"></a><a name="p136834705165634"></a>void </p>
<p id="p480654993165634"><a name="p480654993165634"></a><a name="p480654993165634"></a>Lays out the view on the above of a sibling view. </p>
</td>
</tr>
<tr id="row797730694165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1742069755165634"><a name="p1742069755165634"></a><a name="p1742069755165634"></a><a href="graphic.md#gaa23a68e8ef0fb13b362218e71cf67ace">LayoutBottomToSibling</a> (const char *id, int16_t offset=0)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p2095793220165634"><a name="p2095793220165634"></a><a name="p2095793220165634"></a>void </p>
<p id="p1509504858165634"><a name="p1509504858165634"></a><a name="p1509504858165634"></a>Lays out the view on the below of a sibling view. </p>
</td>
</tr>
<tr id="row2094763915165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1732206895165634"><a name="p1732206895165634"></a><a name="p1732206895165634"></a><a href="graphic.md#ga535942844ebee554d413e960634a2867">SetStyle</a> (<a href="ohos-style.md">Style</a> &style)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p954361669165634"><a name="p954361669165634"></a><a name="p954361669165634"></a>void </p>
<p id="p2079195532165634"><a name="p2079195532165634"></a><a name="p2079195532165634"></a>Sets the view style. </p>
</td>
</tr>
<tr id="row2068230040165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1079810414165634"><a name="p1079810414165634"></a><a name="p1079810414165634"></a><a href="graphic.md#ga0945c2f05815dc2e466ef9ceaca2f700">SetStyle</a> (uint8_t key, int64_t value)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p679554268165634"><a name="p679554268165634"></a><a name="p679554268165634"></a>virtual void </p>
<p id="p127835491165634"><a name="p127835491165634"></a><a name="p127835491165634"></a>Sets a style. </p>
</td>
</tr>
<tr id="row1118735306165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1301675355165634"><a name="p1301675355165634"></a><a name="p1301675355165634"></a><a href="graphic.md#ga4ea19bc9f4b487946c9e29e63b54a0e6">GetStyle</a> (uint8_t key) const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p88825172165634"><a name="p88825172165634"></a><a name="p88825172165634"></a>virtual int64_t </p>
<p id="p318233784165634"><a name="p318233784165634"></a><a name="p318233784165634"></a>Obtains the value of a style. </p>
</td>
</tr>
<tr id="row1236402218165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1976979944165634"><a name="p1976979944165634"></a><a name="p1976979944165634"></a><a href="graphic.md#ga1b28213d4c2cd0f8324bce3fe56eb7bb">GetStyleConst</a> () const</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1648295727165634"><a name="p1648295727165634"></a><a name="p1648295727165634"></a>const <a href="ohos-style.md">Style</a> & </p>
<p id="p491330711165634"><a name="p491330711165634"></a><a name="p491330711165634"></a>Obtains the view style. This function applies to scenarios where the style does not need to be modified, which saves memory. </p>
</td>
</tr>
<tr id="row336788099165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p2040882287165634"><a name="p2040882287165634"></a><a name="p2040882287165634"></a><a href="graphic.md#ga4854963aa969ee20a6cd174a70f5cd23">operator new</a> (size_t size)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p474896849165634"><a name="p474896849165634"></a><a name="p474896849165634"></a>void * </p>
<p id="p961701668165634"><a name="p961701668165634"></a><a name="p961701668165634"></a>Overrides the <strong id="b443247004165634"><a name="b443247004165634"></a><a name="b443247004165634"></a>new</strong> function. </p>
</td>
</tr>
<tr id="row410433549165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1305265354165634"><a name="p1305265354165634"></a><a name="p1305265354165634"></a><a href="graphic.md#gadf1997a0f56ac2b220e7f0f8e8e0a6ef">operator delete</a> (void *p)</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p787152992165634"><a name="p787152992165634"></a><a name="p787152992165634"></a>void </p>
<p id="p2078649185165634"><a name="p2078649185165634"></a><a name="p2078649185165634"></a>Overrides the <strong id="b99079335165634"><a name="b99079335165634"></a><a name="b99079335165634"></a>delete</strong> function. </p>
</td>
</tr>
</tbody>
</table>
## Additional Inherited Members<a name="inherited"></a>
<a name="table1100695776165634"></a>
<table><thead align="left"><tr id="row753845920165634"><th class="cellrowborder" valign="top" width="50%" id="mcps1.1.3.1.1"><p id="p1368517694165634"><a name="p1368517694165634"></a><a name="p1368517694165634"></a>Additional Inherited Member Name</p>
</th>
<th class="cellrowborder" valign="top" width="50%" id="mcps1.1.3.1.2"><p id="p1326578899165634"><a name="p1326578899165634"></a><a name="p1326578899165634"></a>Description</p>
</th>
</tr>
</thead>
<tbody><tr id="row1129320235165634"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.1 "><p id="p1794732552165634"><a name="p1794732552165634"></a><a name="p1794732552165634"></a><a href="graphic.md#ga4a7a2c192206c8b18379f42a5fd176eb">Direction</a> : uint8_t { <a href="graphic.md#gga4a7a2c192206c8b18379f42a5fd176eba43cb7d46f0e18f315d43b82024093b51">Direction::DIR_LEFT_TO_RIGHT</a>, <a href="graphic.md#gga4a7a2c192206c8b18379f42a5fd176eba49e31df5a7fc02ee8c2f85b5e15f0145">Direction::DIR_RIGHT_TO_LEFT</a>, <a href="graphic.md#gga4a7a2c192206c8b18379f42a5fd176eba68baeaa89ae4576fc3d9ac732f87a116">Direction::DIR_TOP_TO_BOTTOM</a>, <a href="graphic.md#gga4a7a2c192206c8b18379f42a5fd176eba78b28982b481790c740bc9b2c1292baa">Direction::DIR_BOTTOM_TO_TOP</a> }</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.1.3.1.2 "><p id="p1007821506165634"><a name="p1007821506165634"></a><a name="p1007821506165634"></a>Enumerates the directions of the progress bar. </p>
</td>
</tr>
</tbody>
</table>
| 104.12093 | 784 | 0.717513 | yue_Hant | 0.139071 |
d58e6df0b99a4eb9dd800e24795bbfe8e3ae455c | 4,203 | md | Markdown | powerapps-docs/developer/component-framework/reference/webapi/retrievemultiplerecords.md | jacobtonder/powerapps-docs | 09943e2350fe8d0919d4a867808cb6ae88b77adc | [
"CC-BY-4.0",
"MIT"
] | 273 | 2018-04-19T15:25:07.000Z | 2022-03-28T02:29:31.000Z | powerapps-docs/developer/component-framework/reference/webapi/retrievemultiplerecords.md | jacobtonder/powerapps-docs | 09943e2350fe8d0919d4a867808cb6ae88b77adc | [
"CC-BY-4.0",
"MIT"
] | 2,602 | 2018-03-07T20:40:08.000Z | 2022-03-31T21:56:14.000Z | powerapps-docs/developer/component-framework/reference/webapi/retrievemultiplerecords.md | jacobtonder/powerapps-docs | 09943e2350fe8d0919d4a867808cb6ae88b77adc | [
"CC-BY-4.0",
"MIT"
] | 558 | 2018-03-07T20:08:04.000Z | 2022-03-30T04:14:45.000Z | ---
title: retrieveMultipleRecords | Microsoft Docs
description: Retrieves a collection of table records.
keywords:
ms.author: nabuthuk
author: Nkrb
manager: kvivek
ms.date: 10/01/2019
ms.service: "powerapps"
ms.suite: ""
ms.tgt_pltfrm: ""
ms.topic: "article"
ms.assetid: 824a53f9-c743-435a-9de2-8128846f3191
---
# retrieveMultipleRecords
[!INCLUDE [retrievemultiplerecords-description](includes/retrievemultiplerecords-description.md)]
## Available for
Model-driven apps
## Syntax
`context.webAPI.retrieveMultipleRecords(entityLogicalName, options, maxPageSize).then(successCallback, errorCallback);`
## Parameters
<table style="width:100%">
<tr>
<th>Name</th>
<th>Type</th>
<th>Required</th>
<th>Description</th>
</tr>
<tr>
<td>entityLogicalName</td>
<td>String</td>
<td>Yes</td>
<td>The table logical name of the records you want to retrieve. For example: "account".</td>
</tr>
<tr>
<td>options</td>
<td>String</td>
<td>No</td>
<td><p>OData system query options or FetchXML query to retrieve your data. </p>
<ul>
<li>Following system query options are supported: <b>$select</b>, <b>$top</b>, <b>$filter</b>, <b>$expand</b>, and <b>$orderby</b>.</li>
<li>To specify a FetchXML query, use the <code>fetchXml</code> column to specify the query.</li>
</ul>
<p>NOTE: You must always use the <b>$select</b> system query option to limit the properties returned for a table record by including a comma-separated list of property names. This is an important performance best practice. If properties aren’t specified using <b>$select</b>, all properties will be returned.</li>
<p>You specify the query options starting with <code>?</code>. You can also specify multiple system query options by using <code>&</code> to separate the query options.
</td>
</tr>
<tr>
<td>maxPageSize</td>
<td>Number</td>
<td>No</td>
<td><p>Specify a positive number that indicates the number of table records to be returned per page. If you do not specify this parameter, the default value is passed as 5000.</p>
<p>If the number of records being retrieved is more than the specified <code>maxPageSize</code> value, <code>nextLink</code> column in the returned promise object will contain a link to retrieve the next set of tables. </td>
</tr>
<tr>
<td>successCallback</td>
<td>Function</td>
<td>No</td>
<td><p>A function to call when table records are retrieved. An object with the following columns is passed to the function:</p>
<ul>
<li><b>entities</b>: An array of JSON objects, where each object represents the retrieved table record containing columns and their values as <code>key: value</code> pairs. The Id of the table record is retrieved by default.</li>
<li><b>nextLink</b>: String. If the number of records being retrieved is more than the value specified in the <code>maxPageSize</code> parameter in the request, this column returns the URL to return next set of records.</li>
</ul>
</td>
</tr>
<tr>
<td>errorCallback</td>
<td>Function</td>
<td>No</td>
<td>A function to call when the operation fails.</td>
</tr>
</table>
## Return Value
Type: [Promise](https://developer.mozilla.org/docs/Web/JavaScript/reference/Global_Objects/Promise)<RetrieveMultipleResponse>
Description: The `RetrieveMultipleResponse` returns a promise that contains an array of JSON objects containing the retrieved table records and the **nextLink** parameter with the URL pointing to next set of records in case paging (`maxPageSize`) is specified in the request, and the record count returned exceeds the paging value. It has the following parameters:
|parameter|Return Value|Description|
|----|------|-------|
|entities|`Entity[]`|An array of JSON objects, where each object represents the retrieved table record containing columns and their values.|
|nextLink|`string`|If the number of records being retrieved is more than the value specified in the 'maxPageSize' parameter in the request, this parameter returns the URL to return next set of records.|
### Related topics
[Web API](../webapi.md)<br/>
[Power Apps component framework API reference](../../reference/index.md)<br/>
[Power Apps component framework overview](../../overview.md)
[!INCLUDE[footer-include](../../../../includes/footer-banner.md)] | 42.03 | 364 | 0.744706 | eng_Latn | 0.920385 |
d58edb2affbc5c467312ab59c712f1cd211d925d | 11 | md | Markdown | README.md | stewil/jaxandjett | 579e3507b8f0e3bd89523b9ba163175f4c8767c2 | [
"Apache-2.0"
] | null | null | null | README.md | stewil/jaxandjett | 579e3507b8f0e3bd89523b9ba163175f4c8767c2 | [
"Apache-2.0"
] | null | null | null | README.md | stewil/jaxandjett | 579e3507b8f0e3bd89523b9ba163175f4c8767c2 | [
"Apache-2.0"
] | null | null | null | #Jax & Jett | 11 | 11 | 0.636364 | vie_Latn | 0.450789 |
d58fc329e19a8f5a9ab1bc0608729fbabc1bcca1 | 2,986 | md | Markdown | mrsgit09Docset0516221715/SQL Server Protocols/MS-SSAS/468209a3-c3db-4e7b-985b-e4396eeb40d3.md | mrsgit09/mrsgit09Repo0516221715 | 4dee21c7aff766e4380cb99bb4172b56f713098e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | mrsgit09Docset0516221715/SQL Server Protocols/MS-SSAS/468209a3-c3db-4e7b-985b-e4396eeb40d3.md | mrsgit09/mrsgit09Repo0516221715 | 4dee21c7aff766e4380cb99bb4172b56f713098e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | mrsgit09Docset0516221715/SQL Server Protocols/MS-SSAS/468209a3-c3db-4e7b-985b-e4396eeb40d3.md | mrsgit09/mrsgit09Repo0516221715 | 4dee21c7aff766e4380cb99bb4172b56f713098e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | <html dir="LTR" xmlns:mshelp="http://msdn.microsoft.com/mshelp" xmlns:ddue="http://ddue.schemas.microsoft.com/authoring/2003/5" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:tool="http://www.microsoft.com/tooltip">
<head>
<meta http-equiv="Content-Type" content="text/html; CHARSET=utf-8"></meta>
<meta name="save" content="history"></meta>
<title>2.2.4.2.2 Complex Type Definitions for Server Object Hierarchy</title>
<xml>
<mshelp:toctitle title="2.2.4.2.2 Complex Type Definitions for Server Object Hierarchy"></mshelp:toctitle>
<mshelp:rltitle title="[MS-SSAS]: Complex Type Definitions for Server Object Hierarchy"></mshelp:rltitle>
<mshelp:keyword index="A" term="468209a3-c3db-4e7b-985b-e4396eeb40d3"></mshelp:keyword>
<mshelp:attr name="DCSext.ContentType" value="open specification"></mshelp:attr>
<mshelp:attr name="AssetID" value="468209a3-c3db-4e7b-985b-e4396eeb40d3"></mshelp:attr>
<mshelp:attr name="TopicType" value="kbRef"></mshelp:attr>
<mshelp:attr name="DCSext.Title" value="[MS-SSAS]: Complex Type Definitions for Server Object Hierarchy" />
</xml>
</head>
<body>
<div id="header">
<h1 class="heading">2.2.4.2.2 Complex Type Definitions for Server Object Hierarchy</h1>
</div>
<div id="mainSection">
<div id="mainBody">
<div id="allHistory" class="saveHistory"></div>
<div id="sectionSection0" class="section" name="collapseableSection">
<p>Each type described in this section has an XSD fragment that
describes the required XML syntax for the type and a table of additional
information about the elements that comprise the type. In addition to a brief
description of each element of each type, the table has columns for
"Read-Only" and "Default." </p>
<p>If a property is marked "Read-Only", the property
is returned by the server in DISCOVER_XML_METADATA. However, a value for the
property cannot be set by the contents of a <a href="81281208-2e24-4208-82a6-f43f99879626.md">Create</a> or <a href="374a42e4-3a0c-4eb0-ae9f-6650e23704f3.md">Alter</a> command executed on
the server. </p>
<p>The Default column indicates what value the server
instantiates for the object if a <b>Create</b> or <b>Alter</b> command omits
that particular element from the definition that is being sent to the server.
If the value in the Default column is "Required", there is no default
value, and the command that is sent to the server MUST set a value for that
property. If the command does not contain a value for the property, the command
results in an error.</p>
<p>Unless noted otherwise, all types that are described in this
section are in the http://schemas.microsoft.com/analysisservices/2003/engine
namespace.</p>
</div>
</div>
</div>
</body>
</html> | 55.296296 | 217 | 0.687877 | eng_Latn | 0.907454 |
d58ffcaa91c20097c7b7617ec9c183f58f9a5ae4 | 852 | md | Markdown | README.md | xChivalrouSx/agile-estimate-planning-poker | 2083672fe2ea5d1e2e283add4927ded26806b4c4 | [
"MIT"
] | null | null | null | README.md | xChivalrouSx/agile-estimate-planning-poker | 2083672fe2ea5d1e2e283add4927ded26806b4c4 | [
"MIT"
] | null | null | null | README.md | xChivalrouSx/agile-estimate-planning-poker | 2083672fe2ea5d1e2e283add4927ded26806b4c4 | [
"MIT"
] | null | null | null | # agile-estimate-planning-poker
Planning poker for estimate issues
---
## Server
#### `npm start`
Runs the app in the development mode.\
Backend code will run on http://localhost:3001. You should connect this from client app.
---
## Client
#### `npm start`
Runs the app in the development mode.\
Open [http://localhost:3000](http://localhost:3000) to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
---
### Images
<p float="left">
<img src="./app-images/planning-poker-00.png" alt="Image - 1" width="300"/>
<img src="./app-images/planning-poker-01.png" alt="Image - 2" width="300"/>
</p>
<p float="left">
<img src="./app-images/planning-poker-02.png" alt="Image - 3" width="600"/>
<img src="./app-images/planning-poker-03.png" alt="Image - 4" width="600"/>
</p>
| 22.421053 | 88 | 0.669014 | eng_Latn | 0.718418 |
d59035ecec85cfcf505850d9998aa40caaf89641 | 1,253 | md | Markdown | README.md | yungsnowx/MacOS-Setup-Script | faac1730b265e0f3c53bf6bd0a7a3a72c4926474 | [
"MIT"
] | null | null | null | README.md | yungsnowx/MacOS-Setup-Script | faac1730b265e0f3c53bf6bd0a7a3a72c4926474 | [
"MIT"
] | null | null | null | README.md | yungsnowx/MacOS-Setup-Script | faac1730b265e0f3c53bf6bd0a7a3a72c4926474 | [
"MIT"
] | null | null | null | # MacOS Setup Script
## Spoofing MAC-Adress
Spoof the MAC-Adress every boot and disable Wi-Fi interface at logout ([Source](https://sunknudsen.com/privacy-guides/how-to-spoof-mac-address-and-hostname-automatically-at-boot-on-macos))
## Install Apps
### Console
| App | Description |
| -------- | ------------------------ |
| brew | package manager |
| neofetch | yeah... u know. |
| htop | task manager |
| figlet | ascii art |
| pandoc | markup format conversion |
### Graphical
| App | Description |
| ------------------ | -------------------------------- |
| Firefox | webbrowser i use |
| Tor-Browser | secure webbrowser |
| iTerm2 | better terminal |
| Rectangle | window snapping |
| TextMate | text editor |
| Alfred | spotlight replacement |
| Spotify | music |
| Visual Studio Code | for development |
| ExifCleaner | cleans the exif data from a file |
| MacTeX (no-gui) | tex live distribution |
| 44.75 | 188 | 0.458101 | eng_Latn | 0.605157 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.