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
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
a6c2970e8eb1d91185cdd27f133c80030cbbdad8 | 13,886 | md | Markdown | docs/analysis-services/tabular-models/workspace-database-ssas-tabular.md | jaredmoo/sql-docs | fae18f2837c5135d3482a26f999173ecf4f9f58e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/analysis-services/tabular-models/workspace-database-ssas-tabular.md | jaredmoo/sql-docs | fae18f2837c5135d3482a26f999173ecf4f9f58e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/analysis-services/tabular-models/workspace-database-ssas-tabular.md | jaredmoo/sql-docs | fae18f2837c5135d3482a26f999173ecf4f9f58e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "Workspace database in SQL Server Data Tools| Microsoft Docs"
ms.custom: ""
ms.date: "03/30/2018"
ms.prod: analysis-services
ms.prod_service: "analysis-services, azure-analysis-services"
ms.service: ""
ms.component: ""
ms.reviewer: ""
ms.suite: "pro-bi"
ms.technology:
ms.component: multidimensional-tabular
ms.component: data-mining
ms.tgt_pltfrm: ""
ms.topic: conceptual
ms.assetid: 662daf08-a514-44a7-8675-44644aa454a2
caps.latest.revision: 24
author: "Minewiskan"
ms.author: "owend"
manager: "kfile"
---
# Workspace database
[!INCLUDE[ssas-appliesto-sqlas-aas](../../includes/ssas-appliesto-sqlas-aas.md)]
The tabular model workspace database, used during model authoring, is created when you create a new tabular model project in [!INCLUDE[ssBIDevStudioFull](../../includes/ssbidevstudiofull-md.md)].
## Specifying a workspace instance
When you create a new tabular model project in SSDT, you can specify an Analysis Services instance to use while authoring your project. Beginning with the September 2016 release (14.0.60918.0) of [!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)], introduces two modes for specifying a workspace instance when you create a new tabular model project.
**Integrated workspace** - Utilizes SSDT's own internal Analysis Services instance.
**Workspace server** - A workspace database is created on an explicit Analysis Services instance, often on the same computer as SSDT or another computer in the same network.
### Integrated workspace
With Integrated workspace, a working database is created in-memory using SSDTs own implicit Analysis Services instance. Integrated workspace mode significantly reduces the complexity of authoring tabular projects in SSDT because a separate explicit installation of SQL Server Analysis Services is not required.
By using Integrated workspace mode, SSDT Tabular dynamically starts its own internal SSAS instance in the background and loads the database. You can add and view tables, columns, and data in the model designer. If you add additional tables, columns, relationships, etc., you're modifying the workspace database. Integrated workspace mode does not change how SSDT Tabular works with a workspace server and database. What changes is where SSDT Tabular hosts the workspace database.
You can select Integrated workspace mode when creating a new tabular model project in SSDT.
By using the Workspace Database and Workspace Server properties for model.bim, you can discover the name of the temporary database and the TCP port of the internal SSAS instance where SSDT Tabular hosts the database. You can connect to the workspace database with SSMS as long as SSDT Tabular has the database loaded. The Workspace Retention setting specifies that SSDT Tabular keeps the workspace database on disk, but no longer in memory after a model project is closed. This ensures less memory is consumed than if the model was kept in memory at all times. If you want to control these settings, set the Integrated Workspace Mode property to False and then provide an explicit workspace server. An explicit workspace server also make sense if the data you are importing into a model exceeds the memory capacity of your SSDT workstation.
> [!NOTE]
> When using Integrated workspace mode, the local Analysis Services instance is 64-bit, while SSDT runs in the 32-bit environment of Visual Studio. If you're connecting to special data sources, make sure you install both the 32-bit and 64-bit versions of the corresponding data providers on your workstation. The 64-bit provider is required for the 64-bit Analysis Services instance and the 32-bit version is required for the Table Import Wizard in SSDT.
### <a name="bkmk_overview"></a> Workspace server
A workspace database is created on the [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)] instance, specified in the Workspace Server property, when you create a new Business Intelligence project by using one of the tabular model project templates in [!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)]. Each tabular model project will have its own workspace database. You can use [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] to view the workspace database on the [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)] server. The workspace database name includes the project name, followed by an underscore, followed by the username, followed by an underscore, followed by a GUID.
The workspace database resides in-memory while the tabular model project is open in [!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)]. When you close the project, the workspace database is either kept in-memory, stored to disk and removed from memory (default), or removed from memory and not stored on disk, as determined by the Workspace Retention property. For more information about the Workspace Retention property, see [Workspace Database Properties](#bkmk_ws_prop) later in this topic.
After you've added data to your model project by using the Table Import Wizard or by using copy/paste, when you view the tables, columns, and data in the model designer, you are viewing the workspace database. If you add additional tables, columns, relationships, etc. you are changing the workspace database.
When you deploy a tabular model project, the deployed model database, which is essentially a copy of the workspace database, is created on the Analysis Services server instance specified in the Deployment Server property. For more information about the Deployment Server property, see [Project properties](../../analysis-services/tabular-models/project-properties-ssas-tabular.md).
The model workspace database typically resides on localhost or a local named instance of an [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)] server. You can use a remote instance of [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)] to host the workspace database, however, this configuration is not recommended due to latency during data queries and other restrictions. Optimally, the instance of [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)] that will host the workspace databases is on the same computer as [!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)]. Authoring model projects on the same computer as the [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)] instance that hosts the workspace database can improve performance.
Remote workspace databases have the following restrictions:
- Potential latency during queries.
- The Data Backup property cannot be set to **Backup to disk**.
- You cannot import data from a [!INCLUDE[ssGemini](../../includes/ssgemini-md.md)] workbook when creating a new tabular model project by using the Import from [!INCLUDE[ssGemini](../../includes/ssgemini-md.md)] project template.
> [!IMPORTANT]
> The model's compatibility level and the Workspace Server must correspond.
> [!NOTE]
> If any of the tables in your model will contain a large number of rows, consider importing only a subset of the data during model authoring. By importing a subset of the data, you can reduce processing time and consumption of workspace database server resources.
> [!NOTE]
> The preview window in the Select Tables and Views page in the Table Import Wizard, Edit Table Properties dialog box, and Partition Manager dialog box show tables, columns, and rows at the data source, and may not show the same tables, columns, and rows as the workspace database.
## <a name="bkmk_ws_prop"></a> Workspace Database Properties
Workspace database properties are included in the model properties. To view model properties, in [!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)], in **Solution Explorer**, click the **Model.bim** file. Model properties can be configured using the **Properties** window. Workspace database specific properties include:
> [!NOTE]
> **Integrated Workspace Mode**, **Workspace Server**, **Workspace Retention**, and **Data Backup** properties have default settings applied when you create a new model project. You can change the default settings for new model projects on the **Data Modeling** page in **Analysis Server** settings in the Tools\Options dialog box. These properties, as well as others, can also be set for each model project in the **Properties** window. Changing default settings will not apply to model projects already created. For more information, see [Configure default data modeling and deployment properties](../../analysis-services/tabular-models/configure-default-data-modeling-and-deployment-properties-ssas-tabular.md).
|Property|Default Setting|Description|
|--------------|---------------------|-----------------|
|**Integrated Workspace Mode**|True, False|If Integrated workspace mode is selected for the workspace database when the project is created, this property will be True. If **Workspace server** mode is selected when the project is created, this property will be False. |
|**Workspace database**|Name|The name of the workspace database. This property cannot be edited when **Integrated Workspace Mode** is **True**.|
|**Workspace Retention**|Unload from memory|Specifies how a workspace database is retained after a model project is closed. A workspace database includes model metadata and imported data. In some cases, the workspace database can be very large and consume a large amount of memory. By default, when you close a model project in [!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)], the workspace database is unloaded from memory. When changing this setting it is important to consider your available memory resources as well as how often you plan to work on the model project. This property setting has the following options:<br /><br /> **Keep in memory** - Specifies to keep the workspace database in memory after a model project is closed. This option will consume more memory; however, when opening a model project in [!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)], fewer resources are consumed and the workspace database will load faster.<br /><br /> **Unload from memory** - Specifies to keep the workspace database on disk, but no longer in memory after a model project is closed. This option will consume less memory; however, when opening a model project in [!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)], the workspace database must be re-attached; additional resources are consumed and the model project will load more slowly than if the workspace database is kept in memory. Use this option when in-memory resources are limited or when working on a remote workspace database.<br /><br /> **Delete workspace** - Specifies to delete the workspace database from memory and not keep the workspace database on disk after the model project is closed. This option will consume less memory and storage space; however, when opening a model project in [!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)], additional resources are consumed and the model project will load more slowly than if the workspace database is kept in memory or on-disk. Use this option when only occasionally working on model projects.<br /><br /> The default setting for this property can be changed on the **Data Modeling** page in **Analysis Server** settings in the Tools\Options dialog box. This property cannot be edited when **Integrated Workspace Mode** is **True**.|
|**Workspace Server**|localhost|This property specifies the default server that will be used to host the workspace database while the model project is being authored in [!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)]. All available instances of [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)] running on the local computer are included in the listbox.<br /><br /> To specify a different [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)] server (running in Tabular mode), type the server name. The user logged on must be an Administrator on the [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)] server.<br /><br /> Note that It is recommended you specify a local [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)] server as the workspace server. For workspace databases on a remote server, importing from [!INCLUDE[ssGemini](../../includes/ssgemini-md.md)] is not supported, data cannot be backed up locally, and the user interface may experience latency during queries.<br /><br /> The default setting for this property can be changed on the Data Modeling page in [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)] settings in the Tools\Options dialog box. This property cannot be edited when **Integrated Workspace Mode** is **True**.|
## <a name="bkmk_use_ssms"></a> Using SSMS to Manage the Workspace Database
You can use SQL Server Management Studio (SSMS) to connect to a [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)] server that hosts a workspace database. Typically, there is no management of the workspace database necessary; the exception, is to detach or delete a workspace database, which must be done from [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)]. Do not use [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] to manage the workspace database while the project is open in the model designer. Doing so could lead to data loss.
## See also
[Model properties](../../analysis-services/tabular-models/model-properties-ssas-tabular.md)
| 143.154639 | 2,303 | 0.7702 | eng_Latn | 0.992914 |
a6c3a4fd19a1f11e6193cf312d5d41e7806ddc5b | 381 | md | Markdown | server/README.md | anderson-amorim/coinless | e90b34f84c5e836d52990dcd6ec4bd06caf356b2 | [
"MIT"
] | null | null | null | server/README.md | anderson-amorim/coinless | e90b34f84c5e836d52990dcd6ec4bd06caf356b2 | [
"MIT"
] | null | null | null | server/README.md | anderson-amorim/coinless | e90b34f84c5e836d52990dcd6ec4bd06caf356b2 | [
"MIT"
] | null | null | null | ## Coinless Server
Database configuration requires the following environment variables:
```sh
DB_USERNAME=postgres
DB_PASSWORD=password
DB_DATABASE=database_development
DB_HOST=localhost
DB_DIALECT=postgres
```
You can pass them as variables via cmd or put inside a `.env` file on the project's root
To start the server:
```sh
npm install
npm run start
or
yarn
yarn start
```
| 15.875 | 88 | 0.790026 | eng_Latn | 0.935934 |
a6c3b6c1245bd788cb5a8ea302ff9841404e04ce | 1,619 | md | Markdown | _posts/dev/publishing/2017-04-14-tilde-and-double-tilde-operator.md | arikim92/arikim92.github.io | 3b49c284c555660d81b6e0ead62d1f506b4f17df | [
"MIT"
] | 6 | 2019-11-29T01:26:03.000Z | 2021-09-09T11:38:49.000Z | _posts/dev/publishing/2017-04-14-tilde-and-double-tilde-operator.md | arikim92/arikim92.github.io | 3b49c284c555660d81b6e0ead62d1f506b4f17df | [
"MIT"
] | 4 | 2020-01-02T02:49:37.000Z | 2022-03-18T06:36:33.000Z | _posts/dev/publishing/2017-04-14-tilde-and-double-tilde-operator.md | arikim92/arikim92.github.io | 3b49c284c555660d81b6e0ead62d1f506b4f17df | [
"MIT"
] | 14 | 2017-04-17T10:19:34.000Z | 2022-03-15T02:46:29.000Z | ---
layout: post
comments: true
date: 2017-04-14 16:52:00
title: "제이쿼리 물결 연산자 ( tilde 연산자 )"
description: "물결 과 물결물결 연산자 사용법"
subject: dev
categories: [ publishing ]
sub: [ jQuery ]
tags: [ js, jQuery, indexof, floor ]
---
## 1. tilde( ~ ) 연산자<a id="1-tilde-연산자" href="#1-tilde-연산자" class="s-link" aria-hidden="true"></a>
-(n+1) 의 결과를 출력합니다.
```javascript
var val1 = 1234;
var val2 = -25;
console.log(~val1);
console.log(~val2);
> -1235
> 24
```
indexOf 로 응용할 수도 있습니다.
- 1 line : `하` 라는 글자가 str1 에 어느위치에 있는지 알려줍니다.
- 4 line : `오` 라는 글자는 str1 에 없기 때문에 0 을 출력합니다.
- 2, 5 line : ! 가 있기때문에 반대로 알려줍니다.
```javascript
var str1 = '안녕하세요.';
var str2 = '하';
var str3 = '오';
console.log(~str1.indexOf(str2));
console.log(!~str1.indexOf(str2));
console.log('---');
console.log(~str1.indexOf(str3));
console.log(!~str1.indexOf(str3));
> -3
> false
> ---
> 0
> true
```
## 2. double tilde( ~~ ) 연산자<a id="2-double-tilde-연산자" href="#2-double-tilde-연산자" class="s-link" aria-hidden="true"></a>
`Math.floor()` 과 비슷한 기능입니다.
양수에서는 결과가 같으나 음수에서 차이가 보입니다.
```javascript
var num1 = 1234.5678;
var num2 = -5.9;
console.log(Math.floor(num1));
console.log(~~num1);
console.log('---');
console.log(Math.floor(num2));
console.log(~~num2);
> 1234
> 1234
> ---
> -6
> -5
```
## 참고 블로그<a id="참고-블로그" href="#참고-블로그" class="s-link" aria-hidden="true"></a>
- [Web Club :: 틸트(~) 연산자와 물결물결(~~) 연산자](http://webclub.tistory.com/21){: target="_blank"}
- [Stack Overflow :: what-is-the-double-tilde-operator-in-javascript](http://stackoverflow.com/questions/5971645/what-is-the-double-tilde-operator-in-javascript/5971689){: target="_blank"}
| 20.75641 | 188 | 0.636813 | kor_Hang | 0.862477 |
a6c419c6aa980bb45b93008f32277437673ec8ee | 3,630 | md | Markdown | README.md | theliturgists/app | feff40204b70032152d02698e09a96819d94ce9a | [
"MIT"
] | 7 | 2017-12-14T01:16:34.000Z | 2020-06-20T05:00:51.000Z | README.md | theliturgists/app | feff40204b70032152d02698e09a96819d94ce9a | [
"MIT"
] | 189 | 2017-10-24T13:06:26.000Z | 2021-01-31T20:33:35.000Z | README.md | theliturgists/app | feff40204b70032152d02698e09a96819d94ce9a | [
"MIT"
] | null | null | null | # Media Catalog Mobile App
This is an app for making media available to supporters of an organization,
for both iOS and Android, built with React Native.
## Getting Started
### macOS
1. Set up for iOS builds:
1. Install [XCode](https://itunes.apple.com/us/app/xcode/id497799835) and [Android Studio & SDK](https://developer.android.com/studio)
1. Install [Cocoapods](https://cocoapods.org/)
1. Set up for Android builds:
1. Install the [Android NDK](https://developer.android.com/ndk/guides)
1. Open `android/local.properties` and add this line:
# Note: substitute the actual path to your sdk folder
ndk.dir=/path/to/android/sdk/ndk/<version>
1. Generate your Android `debug.keystore` for signing debug builds:
$ cd android
$ keytool \
-genkey -v -keystore debug.keystore \
-storepass android -alias androiddebugkey \
-keypass android -keyalg RSA -keysize 2048 -validity 10000
<answer questions however you like>
1. Install [Homebrew](https://brew.sh/)
1. `brew install node`
1. `brew install yarn`
1. `brew install watchman`
## Update dependencies
After first clone, and when new deps are added (i.e. if something breaks
because a package is missing):
```sh
$ yarn install (or just 'yarn')
```
This will also run `pod install` in the `ios` directory to ensure iOS native
libraries are up to date.
## Running Locally
### macOS
In one terminal:
```
$ yarn start
```
In another terminal:
```
# To open the iOS simulator and install + start the app:
$ yarn ios
# To open the Android emulator:
$ export ANDROID_HOME=/path/to/android/sdk
$ ./scripts/launch-android-emulator
# To build and install the app:
$ yarn android
```
## Debugging
### Method 1: Chrome / React Native Debugger
1. Install [React Native Debugger](https://github.com/jhen0409/react-native-debugger)
(optional, but recommended) and run `yarn` to set it up
1. [Open the debug menu](https://facebook.github.io/react-native/docs/debugging#accessing-the-in-app-developer-menu)
and select "Debug Remote JS".
### Method 2: Reactotron
This app is also hooked up to use [Reactotron] which allows you to see console
logs, Redux state and actions, and network activity all in one place. All you
need to do is follow their [installation instructions][Reactotron installation]
launch Reactotron, and reload the app.
[Reactotron]: https://github.com/infinitered/reactotron/blob/master/docs/installing.md
[Reactotron installation]: https://github.com/infinitered/reactotron/blob/master/docs/installing.md
## Storybook
**Warning: possibly out-of-date since ejecting from Expo**
Storybook allows us to create a showcase of the common compoments we create for this app.
They describe these "stories" as "visual test cases". It's a quick way to see how a component
looks and behaves, in its simplest form, detached from any other functionality in the app.
It also lets us quickly iterate on styling and tweaks and see the results immediately.
To start it up:
```sh
# in one terminal
$ yarn storybook
# in another terminal
$ open http://localhost:7007 # opens Storybook web UI
```
This runs both the Storybook server and the Expo packaging server, using
an `index.js` that registers the Storybook UI instead of the app as the root.
To switch back to running the app, Ctrl-C the `yarn storybook` command, run `yarn start`
again, and 'Reload JS' in the simulator. You may have to reload a few times, or
re-scan the QR code (on device), or re-initialize the simulator (using the Expo keyboard
shortcut; e.g. `i` for iOS, `a` for Android).
| 32.123894 | 137 | 0.727273 | eng_Latn | 0.960514 |
a6c4e109f40f9f4678226375ad893fbaaea6b5e5 | 1,804 | md | Markdown | README.md | GabrielGSD/planta-de-nivel-web | acfe4062bafcb3f156ce664b63782ea2703b2e76 | [
"Apache-2.0"
] | 1 | 2021-05-01T23:27:22.000Z | 2021-05-01T23:27:22.000Z | README.md | GabrielGSD/planta-de-nivel-web | acfe4062bafcb3f156ce664b63782ea2703b2e76 | [
"Apache-2.0"
] | null | null | null | README.md | GabrielGSD/planta-de-nivel-web | acfe4062bafcb3f156ce664b63782ea2703b2e76 | [
"Apache-2.0"
] | null | null | null | # WEB - Planta de nível
Projeto realizado na disciplina de C213 (Sistemas Embarcados) durante a graduação em Engenharia de Computação pelo [Inatel](https://inatel.br/home/). Ele permite que através do uso de uma API, desenvolvida em python, possamos ter uma visão melhor do comportamento das funções de transferência.
---
## Tecnologias utilizadas
- <img height="30" src="https://upload.wikimedia.org/wikipedia/commons/thumb/9/95/Vue.js_Logo_2.svg/1184px-Vue.js_Logo_2.svg.png"/> [Vue.js](https://vuejs.org/)
---
## Como utilizar?
Instale todos os requisitos do projeto::
```
npm install
```
Desde então, a demonstração pode ser iniciada em seu navegador:
```
npm run start
```
Execute a API do projeto, para isso acesse o link [aqui](https://github.com/MoisesSDelmoro/planta-de-nivel-api)
---
## Interface
<p>
<img height="250" src="https://user-images.githubusercontent.com/57488202/117463263-d826bc00-af25-11eb-946b-e812943c1ebd.png" />
<img height="250" src="https://user-images.githubusercontent.com/57488202/117463907-86cafc80-af26-11eb-80cd-0aa935019cf9.png" />
</p>
---
## Colaboradores
<table>
<tr>
<td align="center"><a href="https://github.com/GabrielGSD/"><img style="border-radius: 50%;" src="https://user-images.githubusercontent.com/57488202/117461169-a57bc400-af23-11eb-8e32-86dc54da88c2.png" width="100px;" alt=""/><br /><sub><b>Gabriel S. Daniel</b></sub></a></td>
<td align="center"><a href="https://github.com/MoisesSDelmoro"><img style="border-radius: 50%;" src="https://user-images.githubusercontent.com/57488202/117151468-7f251f80-ad8f-11eb-9e56-7a242b89ed72.png" width="100px;" alt=""/><br /><sub><b>Moises S. Delmoro</b></sub></a></td>
</tr>
</table>
---
## Licença
Este projeto está sob a licença [Apache License 2.0](./LICENSE).
| 40.088889 | 293 | 0.713415 | por_Latn | 0.81164 |
a6c5b2f363855b6efbd38e9acd5f6d888c9a8500 | 734 | md | Markdown | .github/PULL_REQUEST_TEMPLATE.md | WealthBar/peak-style | 8e430ada21f8d534111ae0b1323b7eb317c07bf7 | [
"MIT"
] | 1 | 2021-02-24T18:36:03.000Z | 2021-02-24T18:36:03.000Z | .github/PULL_REQUEST_TEMPLATE.md | WealthBar/peak-style | 8e430ada21f8d534111ae0b1323b7eb317c07bf7 | [
"MIT"
] | null | null | null | .github/PULL_REQUEST_TEMPLATE.md | WealthBar/peak-style | 8e430ada21f8d534111ae0b1323b7eb317c07bf7 | [
"MIT"
] | 1 | 2021-05-20T17:13:23.000Z | 2021-05-20T17:13:23.000Z | ### Summary
### Submitter Checklist:
<!-- Remove anything that is not relevant -->
- [ ] Demo new or changed functionality to stakeholders
- [ ] Perform self-review (see reviewer checklist)
- [ ] Annotate MR with comments for reviewer
- [ ] Document any new patterns or features on [peak-design-system](https://github.com/WealthBar/peak-design-system)
- [ ] Assign a team member who should specifically review this code
- [ ] Address reviewer feedback, if any, and assign back to reviewer
### Reviewer Checklist:
<!-- Remove anything that is not relevant -->
- [ ] Version bump in package.json
- [ ] Visually review significant UI changes
- [ ] Assign @pez-wb as reviewer if needed
- [ ] Assign back to submitter with feedback
| 31.913043 | 116 | 0.720708 | eng_Latn | 0.985703 |
a6c67528819300897377a35eaf96d66e25128ce6 | 4,389 | md | Markdown | articles/app-service/web-sites-traffic-manager-custom-domain-name.md | mikaelkrief/azure-docs.fr-fr | 4cdd4a1518555b738f72dd53ba366849013f258c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/app-service/web-sites-traffic-manager-custom-domain-name.md | mikaelkrief/azure-docs.fr-fr | 4cdd4a1518555b738f72dd53ba366849013f258c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/app-service/web-sites-traffic-manager-custom-domain-name.md | mikaelkrief/azure-docs.fr-fr | 4cdd4a1518555b738f72dd53ba366849013f258c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Configuration d’un nom de domaine personnalisé pour une application web dans Azure App Service utilisant Traffic Manager pour l’équilibrage de charge.
description: Utilisation d’un nom de domaine personnalisé pour une application web dans Azure App Service intégrant Traffic Manager pour équilibrer la charge.
services: app-service\web
documentationcenter: ''
author: cephalin
manager: cfowler
editor: ''
ms.assetid: 0f96c0e7-0901-489b-a95a-e3b66ca0a1c2
ms.service: app-service-web
ms.workload: web
ms.tgt_pltfrm: na
ms.devlang: na
ms.topic: article
ms.date: 08/17/2016
ms.author: cephalin
ms.openlocfilehash: c78fb7883559e46ebaa1d8dab59a15c55fb76fdf
ms.sourcegitcommit: 176c575aea7602682afd6214880aad0be6167c52
ms.translationtype: HT
ms.contentlocale: fr-FR
ms.lasthandoff: 01/09/2018
ms.locfileid: "27713849"
---
# <a name="configuring-a-custom-domain-name-for-a-web-app-in-azure-app-service-using-traffic-manager"></a>Configuration d’un nom de domaine personnalisé pour une application web dans Azure App Service utilisant Traffic Manager
[!INCLUDE [web-selector](../../includes/websites-custom-domain-selector.md)]
[!INCLUDE [intro](../../includes/custom-dns-web-site-intro-traffic-manager.md)]
Cet article contient des instructions génériques sur l’utilisation d’un nom de domaine personnalisé avec une application [App Service](app-service-web-overview.md) intégrée à [Traffic Manager](../traffic-manager/traffic-manager-overview.md) pour l’équilibrage de la charge.
[!INCLUDE [tmwebsitefooter](../../includes/custom-dns-web-site-traffic-manager-notes.md)]
[!INCLUDE [introfooter](../../includes/custom-dns-web-site-intro-notes.md)]
<a name="understanding-records"></a>
## <a name="understanding-dns-records"></a>Présentation des enregistrements DNS
[!INCLUDE [understandingdns](../../includes/custom-dns-web-site-understanding-dns-traffic-manager.md)]
<a name="bkmk_configsharedmode"></a>
## <a name="configure-your-web-apps-for-standard-mode"></a>Configuration de vos applications web en mode Standard
[!INCLUDE [modes](../../includes/custom-dns-web-site-modes-traffic-manager.md)]
<a name="bkmk_configurecname"></a>
## <a name="add-a-dns-record-for-your-custom-domain"></a>Ajout d'un enregistrement DNS pour votre domaine personnalisé
> [!NOTE]
> Si vous avez acheté un domaine via Azure App Service Web Apps, ignorez les étapes suivantes et reportez-vous à l'étape finale de l'article [Acheter un domaine pour Web Apps](custom-dns-web-site-buydomains-web-app.md) .
>
>
Pour associer votre domaine personnalisé à une application web dans Azure App Service, vous devez ajouter une nouvelle entrée dans la table DNS pour ce domaine. Pour cela, utilisez les outils de gestion de votre fournisseur de domaine.
[!INCLUDE [Access DNS records with domain provider](../../includes/app-service-web-access-dns-records-no-h.md)]
Bien que les spécificités de chaque fournisseur de domaine varient, vous mappez généralement *depuis* votre nom de domaine personnalisé (comme **contoso.com**) *vers* le nom de domaine Traffic Manager (**contoso.trafficmanager.net**) qui est intégré à votre application web.
> [!NOTE]
> Si un enregistrement est déjà utilisé et que vous devez y lier préventivement vos applications, vous pouvez créer un enregistrement CNAME supplémentaire. Par exemple, pour lier **www.contoso.com** à votre application web à titre préventif, créez un enregistrement CNAME entre **awverify.www** et **contoso.trafficmanager.net**. Vous pouvez ensuite ajouter « www.contoso.com » à votre application web sans modifier l’enregistrement CNAME « www ». Pour plus d’informations, consultez [Créer des enregistrements DNS pour une application web dans un domaine personnalisé][CREATEDNS].
>
>
Quand vous avez terminé l’ajout ou la modification des enregistrements DNS auprès de votre fournisseur de domaine, enregistrez les modifications.
<a name="enabledomain"></a>
## <a name="enable-traffic-manager"></a>Activation de Traffic Manager
[!INCLUDE [modes](../../includes/custom-dns-web-site-enable-on-traffic-manager.md)]
## <a name="next-steps"></a>étapes suivantes
Pour plus d’informations, consultez le [Centre pour développeurs Node.js](/develop/nodejs/).
[!INCLUDE [app-service-web-try-app-service](../../includes/app-service-web-try-app-service.md)]
<!-- URL List -->
[CREATEDNS]: ../dns/dns-web-sites-custom-domain.md
| 55.556962 | 581 | 0.771018 | fra_Latn | 0.83759 |
a6c6dda596e4b7e1eb64c06d8c879fceb88ace08 | 498 | md | Markdown | _pages/vscode.md | heronvondralbra/agasa-test1 | b476f73ec8c6c840957b426d38a23bbe8d643c8d | [
"MIT",
"Unlicense"
] | null | null | null | _pages/vscode.md | heronvondralbra/agasa-test1 | b476f73ec8c6c840957b426d38a23bbe8d643c8d | [
"MIT",
"Unlicense"
] | 1 | 2021-04-07T19:36:32.000Z | 2021-04-07T19:36:32.000Z | _pages/vscode.md | heronvondralbra/agasa-test1 | b476f73ec8c6c840957b426d38a23bbe8d643c8d | [
"MIT",
"Unlicense"
] | null | null | null | ---
layout: page
title: VSCode
permalink: /vscode/
image: 00.jpg
---
### VSCode
[powershell loops](https://www.youtube.com/watch?v=_WIZPgPB8Wk "powershell Loops")
[Techjing link](https://www.youtube.com/channel/UC8BQ_LlJJ6DdPeuAiPsLb7Q "Link zu Techjing")
[Link zu Powershell.org Beitrag über WSL](https://www.youtube.com/watch?v=nnywuRaU6_I "Link zu Powershell.org ->WSL")
[Link zu WAYScript](https://www.youtube.com/playlist?list=PLdn12ns8VMLJcr3WS34gIkYgR4aCnYjmW "Link zu WayScript")
| 27.666667 | 117 | 0.75502 | yue_Hant | 0.877219 |
a6c70f2059d76cfd22f13e299557be8028142227 | 2,950 | md | Markdown | GdiPlusExtensions/src/Filters/README.md | AzuxirenLeadGuy/GdiPlusExtension | 8e22d1f939a87c32b4e195f1165bca91e8acb44a | [
"MIT"
] | 5 | 2021-07-17T12:59:50.000Z | 2022-03-12T06:30:49.000Z | GdiPlusExtensions/src/Filters/README.md | AzuxirenLeadGuy/GdiPlusExtension | 8e22d1f939a87c32b4e195f1165bca91e8acb44a | [
"MIT"
] | 2 | 2021-07-20T04:25:29.000Z | 2022-01-03T02:16:46.000Z | GdiPlusExtensions/src/Filters/README.md | AzuxirenLeadGuy/GdiPlusExtension | 8e22d1f939a87c32b4e195f1165bca91e8acb44a | [
"MIT"
] | 1 | 2021-08-17T06:25:41.000Z | 2021-08-17T06:25:41.000Z | # Filters
Filtering is a technique for modifying or enhancing an image. Filtering is a neighborhood operation, in which the value of any given pixel in the output image is determined by applying some algorithm to the values of the pixels in the neighborhood of the corresponding input pixel. It means that for each pixel location (x,y) in the source image (normally, rectangular), its neighborhood is considered and used to compute the response. In case of a linear filter, it is a weighted sum of pixel values. In case of morphological operations, it is the minimum or maximum values, and so on. The computed response is stored in the destination image at the same location (x,y). It means that the output image will be of the same size as the input image.
The following filters are included in this repository
- **Convolution based**: Convolution is the process of adding each element of the image to its local neighbors, weighted by the kernel.
- **Gaussian Filter**: Blurs an image using a Gaussian filter. The function convolves the source image with the specified Gaussian kernel.
- **Box Blur Filter**: It simply takes the average of all the pixels under the kernel area and replaces the central element.
- **Bilateral Filter**: is highly effective in noise removal while keeping edges sharp. But the operation is slower compared to other filters. We already saw that a Gaussian filter takes the neighbourhood around the pixel and finds its Gaussian weighted average. This Gaussian filter is a function of space alone, that is, nearby pixels are considered while filtering. It doesn't consider whether pixels have almost the same intensity. It doesn't consider whether a pixel is an edge pixel or not. So it blurs the edges also, which we don't want to do. Bilateral filtering also takes a Gaussian filter in space, but one more Gaussian filter which is a function of pixel difference. The Gaussian function of space makes sure that only nearby pixels are considered for blurring, while the Gaussian function of intensity difference makes sure that only those pixels with similar intensities to the central pixel are considered for blurring. So it preserves the edges since pixels at edges will have large intensity variation.
- **Median Filter**: takes the median of all the pixels under the kernel area and the central element is replaced with this median value. This is highly effective against salt-and-pepper noise in an image. Interestingly, in the above filters, the central element is a newly calculated value which may be a pixel value in the image or a new value. But in median blurring, the central element is always replaced by some pixel value in the image. It reduces the noise effectively. Its kernel size should be a positive odd integer.
- **ColorTint Filter**: Applies a linear interpolation for every pixel and brings it closer to the color provided in the parameter, giving it a tint effect.
Source: OpenCV docs
| 184.375 | 1,021 | 0.797627 | eng_Latn | 0.999904 |
a6c7a76818ad90d8f0d11b2337a029c666421f23 | 2,504 | md | Markdown | docs/2014/analysis-services/multidimensional-models/backup-options.md | LifeRyuto/sql-docs.ja-jp | 46230d5d82029920da9f8cb10b1565a7349db27f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/2014/analysis-services/multidimensional-models/backup-options.md | LifeRyuto/sql-docs.ja-jp | 46230d5d82029920da9f8cb10b1565a7349db27f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/2014/analysis-services/multidimensional-models/backup-options.md | LifeRyuto/sql-docs.ja-jp | 46230d5d82029920da9f8cb10b1565a7349db27f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: バックアップオプション |Microsoft Docs
ms.custom: ''
ms.date: 06/13/2017
ms.prod: sql-server-2014
ms.reviewer: ''
ms.technology: analysis-services
ms.topic: conceptual
helpviewer_keywords:
- backing up databases [Analysis Services]
- databases [Analysis Services], backing up
ms.assetid: 02d33fc9-f3f4-4b85-8b90-449b68625cf7
author: minewiskan
ms.author: owend
manager: craigg
ms.openlocfilehash: f620bafc0a734651adfe43bcf0367ca5328dc40c
ms.sourcegitcommit: b87d36c46b39af8b929ad94ec707dee8800950f5
ms.translationtype: MT
ms.contentlocale: ja-JP
ms.lasthandoff: 02/08/2020
ms.locfileid: "66076961"
---
# <a name="backup-options"></a>バックアップ オプション
データベースをバックアップ[!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]するにはさまざまな方法があり、すべての方法でサーバー管理者とデータベース管理者のアクセス許可を持っている必要があります。 [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)]
**で** [バックアップ] [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)]ダイアログ ボックスを開き、適切なオプション構成を選択し、ダイアログ ボックスから直接バックアップを実行できます。 または、ファイルに既に指定されている設定を使用してスクリプトを作成できます。このスクリプトを保存して、必要に応じて実行できます。
## <a name="backup-and-synchronize"></a>バックアップと同期
データベースが [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)]のリモート インスタンスに存在する場合は、同期機能を使用してデータベースをローカルのインスタンスにバックアップできます。 データベースの開発ビルドは、この方法で運用環境に移行できます。 従来のファイル ベースのバックアップおよび復元機能を使用して、開発ビルドを運用環境に移行することもできますが、同期機能を使用すると、追加の機能が提供されます。 同期機能を使用すると、たとえば、開発用コンピューターと実稼動コンピューターにそれぞれ異なるセキュリティ設定を使用できます。つまり、セキュリティ設定を管理し、ロール以外のすべてのオブジェクトを同期することができます。 また、コピー元コンピューターとコピー先コンピューターで異なるこれらのオブジェクトの増分更新も、通常、同期機能で行います。 この種の増分バックアップは、バックアップおよび復元機能では利用できません。 詳細については、「 [Analysis Services データベースの同期](synchronize-analysis-services-databases.md)」を参照してください。
> [!IMPORTANT]
> Analysis Services サービス アカウントには、各ファイルに指定されたバックアップ場所に対する書き込み権限が必要です。 また、ユーザーが [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)] インスタンスの管理者ロールを持っているか、バックアップするデータベースに対してフル コントロール (管理者) 権限を持つデータベース ロールのメンバーである必要があります。
## <a name="see-also"></a>参照
[[データベースのバックアップ] ダイアログボックス (Analysis Services-多次元データ)](../backup-database-dialog-box-analysis-services-multidimensional-data.md)
[Analysis Services データベースのバックアップと復元](backup-and-restore-of-analysis-services-databases.md)
[XMLA)(Backup 要素](https://docs.microsoft.com/bi-reference/xmla/xml-elements-commands/backup-element-xmla)
[XMLA)(のデータベースのバックアップ、復元、および同期](../multidimensional-models-scripting-language-assl-xmla/backing-up-restoring-and-synchronizing-databases-xmla.md)
| 62.6 | 546 | 0.802316 | yue_Hant | 0.482047 |
a6c8eecf272dedd71d9f9352af82aa1e8be2e7b3 | 1,891 | md | Markdown | _events/sd06-insta.md | sauerduels/website | 9b6cbf09fe1e5992bb829dbf8c099e1e49660c34 | [
"MIT"
] | null | null | null | _events/sd06-insta.md | sauerduels/website | 9b6cbf09fe1e5992bb829dbf8c099e1e49660c34 | [
"MIT"
] | null | null | null | _events/sd06-insta.md | sauerduels/website | 9b6cbf09fe1e5992bb829dbf8c099e1e49660c34 | [
"MIT"
] | 3 | 2017-12-30T18:25:04.000Z | 2018-06-11T11:39:04.000Z | ---
title: Insta 1v1
prefix: SD
index: 6
date: "2017-12-17 18:00:00 +01:00"
bracketurl: https://sauerduels.challonge.com/sd06insta
completed: true
podium:
golden: Honzik1
silver: Frosty
bronze: Gangler
finals:
result: Honzik1 def. Frosty
games:
- title: complex 80:72
slug: sd06_final_frosty_vs_honzik1_game1
- title: duel7 98:95
slug: sd06_final_frosty_vs_honzik1_game2
groups:
a:
- - result: Frosty def. kinnyi
slug: sd06_frosty_vs_kinnyi
- result: hades def. Headway
slug: sd06_hades_vs_headway
- - result: hades def. kinnyi
slug: sd06_hades_vs_kinnyi
- result: Frosty def. Gangler
slug: sd06_frosty_vs_gangler
- - result: Gangler def. hades
slug: sd06_gangler_vs_hades
- result: Headway def. kinnyi
slug: sd06_headway_vs_kinnyi
- - result: Gangler def. Headway
slug: sd06_gangler_vs_headway
- result: Frosty def. hades
slug:
- - result: Frosty def. Headway
slug: sd06_frosty_vs_headway
- result: Gangler def. kinnyi
slug: sd06_gangler_vs_kinnyi
b:
- - result: fatmonkeygenius def. Rudi
slug:
disqualified: true
- result: Honzik1 def. Harsh
slug: sd06_harsh_vs_honzik1
- - result: Honzik1 def. Rudi
slug:
disqualified: true
- result: fatmonkeygenius def. Toph
slug: sd06_fatmonkeygenius_vs_toph
- - result: Honzik1 def. Toph
slug: sd06_honzik1_vs_toph
- result: Harsh def. Rudi
slug:
disqualified: true
- - result: Toph def. Harsh
slug: sd06_harsh_vs_toph
- result: Honzik1 def. fatmonkeygenius
slug: sd06_fatmonkeygenius_vs_honzik1
- - result: fatmonkeygenius def. Harsh
slug: sd06_fatmonkeygenius_vs_harsh
- result: Toph def. Rudi
slug:
disqualified: true
---
| 28.223881 | 54 | 0.649392 | eng_Latn | 0.134053 |
a6c9c0042e21184ea4f645cac79fdc364147e4ba | 15,004 | md | Markdown | articles/data-explorer/data-lake-query-data.md | karoldeland/azure-docs.fr-fr | ebb12f93459e6f9cf38b50b296d81a2322949780 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/data-explorer/data-lake-query-data.md | karoldeland/azure-docs.fr-fr | ebb12f93459e6f9cf38b50b296d81a2322949780 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/data-explorer/data-lake-query-data.md | karoldeland/azure-docs.fr-fr | ebb12f93459e6f9cf38b50b296d81a2322949780 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Interroger des données dans Azure Data Lake à l'aide d'Azure Data Explorer
description: Découvrez comment interroger des données dans Azure Data Lake à l'aide d'Azure Data Explorer.
author: orspod
ms.author: orspodek
ms.reviewer: rkarlin
ms.service: data-explorer
ms.topic: conceptual
ms.date: 07/17/2019
ms.openlocfilehash: 8240b1a01aa39e53b9ae41f73543ccf9774290b2
ms.sourcegitcommit: 2ec4b3d0bad7dc0071400c2a2264399e4fe34897
ms.translationtype: HT
ms.contentlocale: fr-FR
ms.lasthandoff: 03/27/2020
ms.locfileid: "77161747"
---
# <a name="query-data-in-azure-data-lake-using-azure-data-explorer"></a>Interroger des données dans Azure Data Lake à l'aide d'Azure Data Explorer
Azure Data Lake Storage est une solution Data Lake hautement évolutive et économique pour l’analytique Big Data. Elle combine la puissance d’un système de fichiers haute performance à grande échelle et la rentabilité qui vous permettront d’obtenir des insights rapidement. Data Lake Storage Gen2 étend les fonctionnalités de Stockage Blob Azure et est optimisé pour les charges de travail analytiques.
Azure Data Explorer s’intègre à Stockage Blob Azure et Azure Data Lake Storage (Gen1 et Gen2) pour offrir un accès rapide, en cache et indexé aux données du lac. Vous pouvez analyser et interroger les données du lac, sans ingestion préalable dans Azure Data Explorer. Vous pouvez également interroger simultanément des données de lac natives ingérées ou non ingérées.
> [!TIP]
> Pour des requêtes plus performantes, l'ingestion des données dans Azure Data Explorer est requise. La possibilité d’interroger les données externes sans ingestion préalable est à réserver aux données historiques ou aux données rarement interrogées. [Optimisez les performances de vos requêtes dans le lac](#optimize-your-query-performance) pour obtenir de meilleurs résultats.
## <a name="create-an-external-table"></a>Créer une table externe
> [!NOTE]
> Les comptes de stockage actuellement pris en charge sont Stockage Blob Azure ou Azure Data Lake Storage (Gen1 et Gen2).
1. Utilisez la commande `.create external table` pour créer une table externe dans Azure Data Explorer. Les commandes de table externe supplémentaires telles que `.show`, `.drop` et `.alter` sont documentées dans [Commandes de table externe](/azure/kusto/management/externaltables).
```Kusto
.create external table ArchivedProducts(
Timestamp:datetime,
ProductId:long, ProductDescription:string)
kind=blob
partition by bin(Timestamp, 1d)
dataformat=csv (h@'http://storageaccount.blob.core.windows.net/container1;secretKey')
with (compressed = true)
```
> [!NOTE]
> * En règle générale, un partitionnement plus granulaire améliore le niveau de performance. Par exemple, les requêtes sur des tables externes avec partitions quotidiennes offrent un meilleur niveau de performance que les requêtes sur des tables partitionnées mensuellement.
> * Lorsque vous définissez une table externe avec des partitions, la structure de stockage doit être identique.
Par exemple, si la table est définie avec une partition DateTime au format aaaa/mm/jj (par défaut), le chemin d’accès au fichier de stockage URI doit être *container1/aaaa/mm/jj/all_exported_blobs*.
> * Si la table externe est partitionnée par une colonne DateHeure, ajoutez toujours à votre requête un filtre de temps définissant une plage fermée. Par exemple, la requête `ArchivedProducts | where Timestamp between (ago(1h) .. 10m)` offrira de meilleurs résultats que la requête `ArchivedProducts | where Timestamp > ago(1h)` (avec plage ouverte).
> * Tous les [formats d’ingestion pris en charge](ingest-data-overview.md#supported-data-formats) peuvent être interrogés à l’aide de tables externes.
1. La table externe est visible dans le volet gauche de l’interface utilisateur web
### <a name="create-an-external-table-with-json-format"></a>Créer un tableau externe au format json
Vous pouvez créer un tableau externe au format json. Pour plus d’informations, consultez l’article [Commandes du tableau externe](/azure/kusto/management/externaltables).
1. Utilisez la commande `.create external table` pour créer un tableau nommé *ExternalTableJson* :
```kusto
.create external table ExternalTableJson (rownumber:int, rowguid:guid)
kind=blob
dataformat=json
(
h@'http://storageaccount.blob.core.windows.net/container1;secretKey'
)
with
(
docstring = "Docs",
folder = "ExternalTables",
namePrefix="Prefix"
)
```
1. Le format json nécessite une deuxième étape de création de mappage aux colonnes, comme indiqué ci-dessous. Dans la requête suivante, créez un mappage JSON spécifique nommé *mappingName* :
```kusto
.create external table ExternalTableJson json mapping "mappingName" '[{ "column" : "rownumber", "datatype" : "int", "path" : "$.rownumber"},{ "column" : "rowguid", "path" : "$.rowguid" }]'
```
### <a name="external-table-permissions"></a>Autorisations de table externe
* L’utilisateur de base de données peut créer une table externe. Le créateur de la table en devient automatiquement l’administrateur.
* L'administrateur de cluster, base de données ou table peut modifier une table existante.
* Tout utilisateur ou lecteur de base de données peut interroger une table externe.
## <a name="query-an-external-table"></a>Interroger une table externe
Pour interroger une table externe, utilisez la fonction `external_table()` et entrez le nom de la table en tant qu'argument de fonction. Le reste de la requête correspond au langage de requête Kusto standard.
```Kusto
external_table("ArchivedProducts") | take 100
```
> [!TIP]
> Actuellement, IntelliSense n’est pas pris en charge sur les requêtes de table externe.
### <a name="query-an-external-table-with-json-format"></a>Interroger un tableau externe au format json
Pour interroger un tableau externe au format json, utilisez la fonction `external_table()` et entrez le nom du tableau et le nom du mappage en tant qu'arguments de fonction. Dans la requête ci-dessous, si *mappingName* n’est pas spécifié, un mappage que vous avez créé précédemment sera utilisé.
```kusto
external_table(‘ExternalTableJson’, ‘mappingName’)
```
## <a name="query-external-and-ingested-data-together"></a>Interroger simultanément des données externes et ingérées
Vous pouvez utiliser la même requête pour interroger des tables externes et des tables de données ingérées. Vous devez [`join`](/azure/kusto/query/joinoperator) ou [`union`](/azure/kusto/query/unionoperator) la table externe avec des données supplémentaires issues d'Azure Data Explorer, de serveurs SQL ou d’autres sources. Utilisez une [`let( ) statement`](/azure/kusto/query/letstatement) pour attribuer un nom abrégé à une référence de table externe.
Dans l’exemple ci-dessous, *Products* correspond à une table de données ingérées et *ArchivedProducts* à une table externe contenant des données dans Azure Data Lake Storage Gen2 :
```kusto
let T1 = external_table("ArchivedProducts") | where TimeStamp > ago(100d);
let T = Products; //T is an internal table
T1 | join T on ProductId | take 10
```
## <a name="query-taxirides-external-table-in-the-help-cluster"></a>Interroger la table *TaxiRides* dans le cluster d'aide
L'exemple de jeu de données *TaxiRides* contient des données relatives aux taxis new-yorkais issues de [NYC Taxi et Limousines Commission](https://www1.nyc.gov/site/tlc/about/tlc-trip-record-data.page).
### <a name="create-external-table-taxirides"></a>Créer une table externe *TaxiRides*
> [!NOTE]
> Cette section décrit la requête utilisée pour créer la table externe *TaxiRides* dans le cluster *help*. Cette table ayant déjà été créée, vous pouvez ignorer cette section et [interroger*les*données de la table externe](#query-taxirides-external-table-data) TaxiRides.
1. La requête suivante a été utilisée pour créer la table externe *TaxiRides* dans le cluster d'aide.
```kusto
.create external table TaxiRides
(
trip_id: long,
vendor_id: string,
pickup_datetime: datetime,
dropoff_datetime: datetime,
store_and_fwd_flag: string,
rate_code_id: int,
pickup_longitude: real,
pickup_latitude: real,
dropoff_longitude: real,
dropoff_latitude: real,
passenger_count: int,
trip_distance: real,
fare_amount: real,
extra: real,
mta_tax: real,
tip_amount: real,
tolls_amount: real,
ehail_fee: real,
improvement_surcharge: real,
total_amount: real,
payment_type: string,
trip_type: int,
pickup: string,
dropoff: string,
cab_type: string,
precipitation: int,
snow_depth: int,
snowfall: int,
max_temperature: int,
min_temperature: int,
average_wind_speed: int,
pickup_nyct2010_gid: int,
pickup_ctlabel: string,
pickup_borocode: int,
pickup_boroname: string,
pickup_ct2010: string,
pickup_boroct2010: string,
pickup_cdeligibil: string,
pickup_ntacode: string,
pickup_ntaname: string,
pickup_puma: string,
dropoff_nyct2010_gid: int,
dropoff_ctlabel: string,
dropoff_borocode: int,
dropoff_boroname: string,
dropoff_ct2010: string,
dropoff_boroct2010: string,
dropoff_cdeligibil: string,
dropoff_ntacode: string,
dropoff_ntaname: string,
dropoff_puma: string
)
kind=blob
partition by bin(pickup_datetime, 1d)
dataformat=csv
(
h@'http://storageaccount.blob.core.windows.net/container1;secretKey''
)
```
1. La table qui en résulte a été créée dans le cluster d'*aide* :
### <a name="query-taxirides-external-table-data"></a>Interroger les données de la table externe *TaxiRides*
Connectez-vous à [https://dataexplorer.azure.com/clusters/help/databases/Samples](https://dataexplorer.azure.com/clusters/help/databases/Samples) pour interroger la table externe *TaxiRides*.
#### <a name="query-taxirides-external-table-without-partitioning"></a>Interroger la table externe *TaxiRides* sans partitionnement
[Exécutez cette requête](https://dataexplorer.azure.com/clusters/help/databases/Samples?query=H4sIAAAAAAAAAx3LSwqAMAwFwL3gHYKreh1xL7F9YrCtElP84OEV9zM4DZo5DsZjhGt6PqWTgL1p6+qhvaTEKjeI/FqyuZbGiwJf63QAi9vEL2UbAhtMEv6jyAH6+VhS9jOr1dULfUgAm2cAAAA=) sur la table externe *TaxiRides* pour représenter les courses de chaque jour de la semaine, dans le jeu de données entier.
```kusto
external_table("TaxiRides")
| summarize count() by dayofweek(pickup_datetime)
| render columnchart
```
Cette requête affiche le jour le plus chargé de la semaine. Les données n'étant pas partitionnées, cette requête peut mettre un certain temps à renvoyer des résultats (jusqu'à plusieurs minutes).
#### <a name="query-taxirides-external-table-with-partitioning"></a>Interroger la table externe TaxiRides avec partitionnement
[Exécutez cette requête](https://dataexplorer.azure.com/clusters/help/databases/Samples?query=H4sIAAAAAAAAA13NQQqDMBQE0L3gHT6ukkVF3fQepXv5SQYMNWmIP6ilh68WuinM6jHMYBPkyPMobGao5s6bv3mHpdF19aZ1QgYlbx8ljY4F4gPIQFYgkvqJGrr+eun6I5ralv58OP27t5QQOPsXiOyzRFGazE6WzSh7wtnIiA75uISdOEtdfQDLWmP+ogAAAA==) sur la table externe *TaxiRides* affichant les types de taxis (jaunes ou verts) utilisés janvier 2017.
```kusto
external_table("TaxiRides")
| where pickup_datetime between (datetime(2017-01-01) .. datetime(2017-02-01))
| summarize count() by cab_type
| render piechart
```
Cette requête utilise le partitionnement, ce qui optimise le temps de requête et le niveau de performance. La requête filtre une colonne partitionnée (pickup_datetime) et renvoie les résultats en quelques secondes.
Vous pouvez écrire des requêtes supplémentaires à exécuter sur la table externe *TaxiRides* et en savoir plus sur les données.
## <a name="optimize-your-query-performance"></a>Optimiser les performances de vos requêtes
Optimisez les performances de vos requêtes dans le lac en observant les bonnes pratiques suivantes pour interroger des données externes.
### <a name="data-format"></a>Format de données
Utilisez un format en colonnes pour les requêtes analytiques dans la mesure où :
* Seules les colonnes appropriées à une requête peuvent être lues.
* Les techniques d’encodage de colonne peuvent réduire considérablement la taille des données.
Azure Data Explorer prend en charge les formats en colonnes Parquet et ORC. Nous suggérons le format Parquet car son implémentation est optimisée.
### <a name="azure-region"></a>Région Azure
Veillez à ce que les données externes se trouvent dans la même région Azure que votre cluster Azure Data Explorer. Cela réduit le coût et le temps de l’extraction des données.
### <a name="file-size"></a>Taille du fichier
La taille de fichier optimale est de plusieurs centaines de Mo (jusqu’à 1 Go) par fichier. Évitez d’avoir un grand nombre de petits fichiers qui nécessitent une surcharge inutile, par exemple un processus d’énumération de fichiers plus lent et une utilisation limitée du format en colonnes. Notez que le nombre de fichiers doit être supérieur au nombre de cœurs de processeur dans votre cluster Azure Data Explorer.
### <a name="compression"></a>Compression
Utilisez la compression pour réduire la quantité de données extraites du stockage distant. Pour le format Parquet, utilisez le mécanisme de compression Parquet interne qui compresse les groupes de colonnes séparément, ce qui vous permet de les lire séparément. Pour valider l’utilisation du mécanisme de compression, vérifiez que les fichiers sont nommés comme suit : « <filename>.gz.parquet » ou « <filename>.snappy.parquet », et non « <filename>.parquet.gz »).
### <a name="partitioning"></a>Partitionnement
Organisez vos données en utilisant des partitions de « dossier » qui permettent à la requête d’ignorer les chemins non pertinents. Lors de la planification du partitionnement, tenez compte de la taille de fichier et des filtres courants dans vos requêtes, tels que l’horodatage ou l’ID de locataire.
### <a name="vm-size"></a>Taille de la machine virtuelle
Sélectionnez les références SKU de machine virtuelle avec plus de cœurs et un débit réseau plus élevé (la mémoire est moins importante). Pour plus d’informations, consultez [Sélectionner la bonne référence SKU de machine virtuelle pour votre cluster Azure Data Explorer](manage-cluster-choose-sku.md).
## <a name="next-steps"></a>Étapes suivantes
Interrogez vos données dans Azure Data Lake à l'aide d'Azure Data Explorer. Apprenez à [écrire des requêtes](write-queries.md) et à tirer plus d'insights de vos données.
| 56.618868 | 463 | 0.768862 | fra_Latn | 0.91946 |
a6ca3388e87fbe544fc3a7e4f51cf112ee470df0 | 12,556 | md | Markdown | playlists/pretty/5bjjHyKeiGnYdupfr3UUCW.md | itsnebulalol/spotify-playlist-archive | 40424a00842486095bd377f7e4621bb66adbba79 | [
"MIT"
] | null | null | null | playlists/pretty/5bjjHyKeiGnYdupfr3UUCW.md | itsnebulalol/spotify-playlist-archive | 40424a00842486095bd377f7e4621bb66adbba79 | [
"MIT"
] | null | null | null | playlists/pretty/5bjjHyKeiGnYdupfr3UUCW.md | itsnebulalol/spotify-playlist-archive | 40424a00842486095bd377f7e4621bb66adbba79 | [
"MIT"
] | null | null | null | pretty - [cumulative](/playlists/cumulative/5bjjHyKeiGnYdupfr3UUCW.md) - [plain](/playlists/plain/5bjjHyKeiGnYdupfr3UUCW) - [githistory](https://github.githistory.xyz/mackorone/spotify-playlist-archive/blob/main/playlists/plain/5bjjHyKeiGnYdupfr3UUCW)
### [Ultimate Live Jams](https://open.spotify.com/playlist/5bjjHyKeiGnYdupfr3UUCW)
> Ten hours of ultimate jams —all long, all live.
[Spotify](https://open.spotify.com/user/spotify) - 114 likes - 43 songs - 10 hr 4 min
| No. | Title | Artist(s) | Album | Length |
|---|---|---|---|---|
| 1 | [Money Love and Change](https://open.spotify.com/track/4bMvmEgBru7mkeu64dOLsj) | [Trey Anastasio](https://open.spotify.com/artist/3Felk6Y6jjU00yE1XTOqKZ) | [TAB at the TAB](https://open.spotify.com/album/4TWcRTiZcYCvZa11xBwSKs) | 10:35 |
| 2 | [Mountain Jam \(Theme From “First There Is A Mountain”\) \- Live At The Fillmore East/1971](https://open.spotify.com/track/6NXgAwgXZGp5iwz4bI6iI9) | [Allman Brothers Band](https://open.spotify.com/artist/4wQ3PyMz3WwJGI5uEqHUVR) | [Eat A Peach \(Deluxe Edition\)](https://open.spotify.com/album/4yvCI9bSiajFEvrYTgzmpe) | 33:38 |
| 3 | [Bathtub Gin](https://open.spotify.com/track/74R96PKN3QH1Z9Bmsxi8Ag) | [Phish](https://open.spotify.com/artist/5wbIWUzTPuTxTyG6ouQKqz) | [Live Phish: 10/30/10, Boardwalk Hall, Atlantic City, NJ](https://open.spotify.com/album/6NYcp85vtEHbNPKpeSLb9s) | 11:05 |
| 4 | [Rebirtha \- Live From The Classic Center, Athens, GA/2000](https://open.spotify.com/track/6Wzycb7YZeRRkbLyh3SzO6) | [Widespread Panic](https://open.spotify.com/artist/54SHZF2YS3W87xuJKSvOVf) | [Live In The Classic City II](https://open.spotify.com/album/1EZJAudr1GHp3TXbRXfSDi) | 12:44 |
| 5 | [Two Step \- Live from Lucca, Italy](https://open.spotify.com/track/193Kys7L8NvKrEYemywflj) | [Dave Matthews Band](https://open.spotify.com/artist/2TI7qyDE0QfyOlnbtfDo7L) | [Crash: Spotify Live Series](https://open.spotify.com/album/0wJmGKv4Sl8MJnsZeNg9F3) | 14:42 |
| 6 | [Spanish Moon \(Live From Athens 4/11/96\)](https://open.spotify.com/track/3hr52p1fWheR6RZe1SqTu7) | [Gov't Mule](https://open.spotify.com/artist/5zoKOcTDI9EMOhGNaxL708), [Derek Trucks](https://open.spotify.com/artist/1xJPYI7GXasA3ariMSftPq) | [The Georgia Bootleg Box](https://open.spotify.com/album/5AUMMhBzXFumr4276ZSBep) | 11:47 |
| 7 | [Impressions](https://open.spotify.com/track/6nRsI3tivPrTinAnc3OjCo) | [The String Cheese Incident](https://open.spotify.com/artist/7N3JfLDzzjXdPbsyco7X0l) | [Rhythm of the Road: Volume One, Incident in Atlanta \-11.17.00](https://open.spotify.com/album/33eRh00tERv1BscbFnuUtF) | 19:51 |
| 8 | [That Old Thing \(Intro\)/Earth Jam \- Live at the Quick](https://open.spotify.com/track/16zsIlz8ugU68lnrLWeJQZ) | [Béla Fleck and the Flecktones](https://open.spotify.com/artist/5Zmur9D9gpr6tXyDrpnbOe) | [Live at the Quick](https://open.spotify.com/album/6h3EVRS9L18VO71muF5htL) | 7:55 |
| 9 | [Tailspin](https://open.spotify.com/track/1nLzblDBsK3InKJsb43XK8) | [moe.](https://open.spotify.com/artist/2ZfHMUPrxoZNDTBPHmmdhj) | [Live at Lollapalooza 2007: moe.](https://open.spotify.com/album/4KKs5Lps3irhQnIEz971qi) | 4:58 |
| 10 | [Magellan](https://open.spotify.com/track/6xarIGJPsqomY5SORbonb7) | [The Disco Biscuits](https://open.spotify.com/artist/1sahk8ZhHF9FB59DMyDi8D) | [Live at Lollapalooza 2006: The Disco Biscuits](https://open.spotify.com/album/7n3S1mB8zJJVcfPuI4vEqM) | 19:53 |
| 11 | [Breathe In \(Live \- Acoustic\)](https://open.spotify.com/track/5Sv7YLeeMZso8oN3vEn7rC) | [STS9](https://open.spotify.com/artist/1eZ4td9oadjw7GkW0LzxNK) | [Axe the Cables](https://open.spotify.com/album/6QTc2EHTEELJhYM2BpHHXY) | 12:10 |
| 12 | [Squeeze \(Live\)](https://open.spotify.com/track/7oB0H5oNR4RfDzp133wsWs) | [Robert Randolph & The Family Band](https://open.spotify.com/artist/4xac3zhHlBm5QDxbZeqgeR) | [Robert Randolph & The Family Band \(Live In Concert\)](https://open.spotify.com/album/31vMvrxTxzaAlFTl3CMzn7) | 8:03 |
| 13 | [Soul Sacrifice \- Live at The Woodstock Music & Art Fair, August 16, 1969](https://open.spotify.com/track/0S1yjunMMkEAQgPNoKw3ve) | [Santana](https://open.spotify.com/artist/6GI52t8N5F02MxU0g5U69P) | [Santana: The Woodstock Experience](https://open.spotify.com/album/2gZoPer2HmitHniKZcWj7G) | 11:35 |
| 14 | [We Don't Stop \- Live Version](https://open.spotify.com/track/0yJohKJFI3bDAPx2OlRJyl) | [Michael Franti & Spearhead](https://open.spotify.com/artist/1mHuZMOP8FG5ip4yAb1vrB) | [Reggae On The River Live](https://open.spotify.com/album/3uLdBvkDTAkiEdT3XEmE9c) | 6:57 |
| 15 | [Breathe](https://open.spotify.com/track/7JlirE2NVLTZXpl8Wwy2e9) | [Keller Williams with Moseley, Droll & Sipe](https://open.spotify.com/artist/6aVWWcJaQDfkjwfuyyIT70) | [LIVE](https://open.spotify.com/album/7v9B8UuRe1Qc2IsJnxY6cQ) | 10:49 |
| 16 | [Backwards Jack](https://open.spotify.com/track/0knvs8m6DIZIKrNvjV3KTx) | [Soulive](https://open.spotify.com/artist/6mWEaOFdcN3s30GuFWruGO) | [Live in San Francisco](https://open.spotify.com/album/315kKEPVFUGXeuVxoxM8lz) | 10:58 |
| 17 | [Hippie / Imagine](https://open.spotify.com/track/5s7IDxhT65wJqQejA0g6v1) | [Blues Traveler](https://open.spotify.com/artist/3pHeBYl1yujXcZqqfF1UyQ) | [Live From The Fall](https://open.spotify.com/album/52LFpW06z2rStTaLi2lLdV) | 19:46 |
| 18 | [My Morning Song \- Live](https://open.spotify.com/track/2Qa7RRDTBpLU9mzEWImF1i) | [The Black Crowes](https://open.spotify.com/artist/5krkohEVJYw0qoB5VWwxaC) | [Freak 'N' Roll...Into The Fog \(Live\)](https://open.spotify.com/album/6trgthUmt4f8B1YWuRqq3u) | 13:49 |
| 19 | [Jam \(feat\. Jerry Garcia\) \(Live at the Family Dog Ballroom, 1969\)](https://open.spotify.com/track/20LZw2PSZtuxwUm8cv1Mzw) | [Jefferson Airplane](https://open.spotify.com/artist/2qFr8w5sWUITRlzZ9kZotF), [Jerry Garcia](https://open.spotify.com/artist/3QDaXfnxfQqqJQK5lSdjLN) | [At the Family Dog Ballroom](https://open.spotify.com/album/0tukP7BX7sJjtEoEUiSsN0) | 26:17 |
| 20 | [Dixie Chicken](https://open.spotify.com/track/1DbgPU9Z6vSSsCPa8edNo4) | [Little Feat](https://open.spotify.com/artist/0ZIwOAzDuGPspzK7yiTc4S) | [Highwire Act Live In St\. Louis 2003](https://open.spotify.com/album/0fCo5uHsmvs7LdSZHWy3Ls) | 17:44 |
| 21 | [In the Kitchen \(11/01/12 Northampton, Ma\)](https://open.spotify.com/track/0DGcEvtTjvc3KOqKCgMPW1) | [Umphrey's McGee](https://open.spotify.com/artist/7mQilAy42MqNPqUFqK4Z0o) | [Hall of Fame: Class of 2012](https://open.spotify.com/album/2zUiMjXpk38U9jelCbN1Lf) | 16:55 |
| 22 | [Scarlet Begonias / Fire on the Mountain \- Live at Manor Downs, Austin, TX 7/31/1982](https://open.spotify.com/track/4k0AvdRsHBXymwJvgKEJnQ) | [Grateful Dead](https://open.spotify.com/artist/4TMHGUX5WI7OOm53PqSDAT) | [30 Days of Dead 2012](https://open.spotify.com/album/4QPyY5VUoSP22WiDAvCMVl) | 23:08 |
| 23 | [Meatstick](https://open.spotify.com/track/6AZ6Bs13kzycbHOLO7Qaq9) | [Phish](https://open.spotify.com/artist/5wbIWUzTPuTxTyG6ouQKqz) | [Live Phish: 6/27/10 Merriweather Post Pavilion, Columbia, MD](https://open.spotify.com/album/2zAUhu0Kl7m198TeDDzXDT) | 9:59 |
| 24 | [Greta \- Live From The Classic Center, Athens, GA/2000](https://open.spotify.com/track/5feqXVMlLMoBt4MkbZUavg) | [Widespread Panic](https://open.spotify.com/artist/54SHZF2YS3W87xuJKSvOVf) | [Live In The Classic City II](https://open.spotify.com/album/1EZJAudr1GHp3TXbRXfSDi) | 10:22 |
| 25 | [\#41 \- Live at Wrigley Field, Chicago, IL \- September 2010](https://open.spotify.com/track/4JokKmIbiyDvkXRJlXPd6z) | [Dave Matthews Band](https://open.spotify.com/artist/2TI7qyDE0QfyOlnbtfDo7L) | [Live At Wrigley Field](https://open.spotify.com/album/7LQyYxGQBm4Ae8fBFrOOlN) | 16:07 |
| 26 | [Blind Man in the Dark \(Live From Athens 4/11/96\)](https://open.spotify.com/track/46fkCzxlVvrtbZFqG0IcJb) | [Gov't Mule](https://open.spotify.com/artist/5zoKOcTDI9EMOhGNaxL708) | [The Georgia Bootleg Box](https://open.spotify.com/album/5AUMMhBzXFumr4276ZSBep) | 9:30 |
| 27 | [Machine Gun \- Live At Filmore East, New York/1970/1997 Digital Remaster](https://open.spotify.com/track/2l2YAblqvbivu8xx2KaxPB) | [Jimi Hendrix](https://open.spotify.com/artist/776Uo845nYHJpNaStv1Ds4) | [Band Of Gypsys \(Live\)](https://open.spotify.com/album/4onmGiUjJyDypKEQvJOvLc) | 12:40 |
| 28 | [Miss Brown's Teahouse](https://open.spotify.com/track/3mSuT45Aymjkb0hWRBn6bc) | [The String Cheese Incident](https://open.spotify.com/artist/7N3JfLDzzjXdPbsyco7X0l) | [Rhythm of the Road: Volume One, Incident in Atlanta \-11.17.00](https://open.spotify.com/album/33eRh00tERv1BscbFnuUtF) | 17:05 |
| 29 | [Freeway \- Live](https://open.spotify.com/track/6WMLtnkcpMsmMz0gjaTBm4) | [Santana](https://open.spotify.com/artist/6GI52t8N5F02MxU0g5U69P) | [Live At The Fillmore \- 1968](https://open.spotify.com/album/1yKeYcIaLLoRrMu9uxZooU) | 30:15 |
| 30 | [She Sends Me](https://open.spotify.com/track/6F5wlng14aW0QYR8DMDNNt) | [moe.](https://open.spotify.com/artist/2ZfHMUPrxoZNDTBPHmmdhj) | [Live at Lollapalooza 2007: moe.](https://open.spotify.com/album/4KKs5Lps3irhQnIEz971qi) | 4:24 |
| 31 | [Curlew's Call \- 2004/ Live at Bonnaroo](https://open.spotify.com/track/0dVjqncJlxb6UHDxm5r1wo) | [Trey Anastasio](https://open.spotify.com/artist/3Felk6Y6jjU00yE1XTOqKZ) | [Bonnaroo 2004](https://open.spotify.com/album/6saSPope4BxzVteJKgvGaS) | 10:16 |
| 32 | [Caterpillar](https://open.spotify.com/track/4Se7644xg6igng0psV1aYK) | [The Disco Biscuits](https://open.spotify.com/artist/1sahk8ZhHF9FB59DMyDi8D) | [Live at Lollapalooza 2006: The Disco Biscuits](https://open.spotify.com/album/7n3S1mB8zJJVcfPuI4vEqM) | 13:09 |
| 33 | [Satori \(Live \- Acoustic\)](https://open.spotify.com/track/5qUDTbbuAp40Sn4HCKK9jQ) | [STS9](https://open.spotify.com/artist/1eZ4td9oadjw7GkW0LzxNK) | [Axe the Cables](https://open.spotify.com/album/6QTc2EHTEELJhYM2BpHHXY) | 8:46 |
| 34 | [Ted's Jam](https://open.spotify.com/track/1qMx2QdQrpD7qk2MGr5IEP) | [Robert Randolph & The Family Band](https://open.spotify.com/artist/4xac3zhHlBm5QDxbZeqgeR) | [Live At The Wetlands](https://open.spotify.com/album/0Ez2hlebyEDZixflMH1Z9T) | 13:14 |
| 35 | [Sand](https://open.spotify.com/track/0abjXnOz3hhLpF7Lc26cOw) | [Trey Anastasio](https://open.spotify.com/artist/3Felk6Y6jjU00yE1XTOqKZ) | [TAB at the TAB](https://open.spotify.com/album/4TWcRTiZcYCvZa11xBwSKs) | 12:01 |
| 36 | [You Are What You Eat](https://open.spotify.com/track/3qkVSetCQPsAtpWGyXTMYh) | [Keller Williams with Moseley, Droll & Sipe](https://open.spotify.com/artist/6aVWWcJaQDfkjwfuyyIT70) | [LIVE](https://open.spotify.com/album/7v9B8UuRe1Qc2IsJnxY6cQ) | 15:49 |
| 37 | [El Ron ft The Shady Horns](https://open.spotify.com/track/73xtnRqQM2nAy9vMwyCmI7) | [Soulive](https://open.spotify.com/artist/6mWEaOFdcN3s30GuFWruGO) | [Bowlive \- Live at the Brooklyn Bowl](https://open.spotify.com/album/2dDDKQI6TzazEGngAC8RyV) | 12:35 |
| 38 | [Dark Star \- Live at the Fillmore West San Francisco, 1969; 2001 Remaster](https://open.spotify.com/track/07CwWCJetytT1cSnQOgRMU) | [Grateful Dead](https://open.spotify.com/artist/4TMHGUX5WI7OOm53PqSDAT) | [Live / Dead](https://open.spotify.com/album/6E7JCQINTT4vwRF4wBcsYk) | 23:18 |
| 39 | [Rage](https://open.spotify.com/track/5NmcYz7gifAyFVfweiGo7m) | [Blues Traveler](https://open.spotify.com/artist/3pHeBYl1yujXcZqqfF1UyQ) | [What You And I Have Been Through](https://open.spotify.com/album/20XOsuJl4r5GiEFtcQWeNI) | 9:49 |
| 40 | [Oh, Josephine \- Live](https://open.spotify.com/track/7wnBFYnZ7HTKNXBTpkcRbr) | [The Black Crowes](https://open.spotify.com/artist/5krkohEVJYw0qoB5VWwxaC) | [War Paint LIVE](https://open.spotify.com/album/30pvG4yfeKvtqgkCTrzUW2) | 7:59 |
| 41 | [Wooden Ships \- Live at The Woodstock Music & Art Fair, August 16, 1969](https://open.spotify.com/track/7CWbxhgsL7M3zzkEhbdlgc) | [Jefferson Airplane](https://open.spotify.com/artist/2qFr8w5sWUITRlzZ9kZotF) | [Jefferson Airplane: The Woodstock Experience](https://open.spotify.com/album/625s2gdwGv9II76gXGAelS) | 21:25 |
| 42 | [Day at the Dog Races \- Live at Lisner Auditorium, Washington, DC, 8/9/1977](https://open.spotify.com/track/6BHt2qmeVtFzv8pKrTrugD) | [Little Feat](https://open.spotify.com/artist/0ZIwOAzDuGPspzK7yiTc4S) | [Waiting for Columbus \(Live Version; Deluxe Edition\)](https://open.spotify.com/album/2TtmZyFBqydHgAk6r8mbbM) | 12:12 |
| 43 | [Big Country \- Live at the Quick](https://open.spotify.com/track/4w5G2CRpsv14IcRfYxPw5e) | [Béla Fleck and the Flecktones](https://open.spotify.com/artist/5Zmur9D9gpr6tXyDrpnbOe) | [Live at the Quick](https://open.spotify.com/album/6h3EVRS9L18VO71muF5htL) | 8:21 |
Snapshot ID: `NSwxMTY4Y2Y2ODVmOWRjOTg1YjI4ZTYwNmQxMWQ3NmI1YjYyNzliNGQ2` | 228.290909 | 380 | 0.757248 | yue_Hant | 0.555036 |
a6ca59870174efe18964fe993bd9e1dca9ff212b | 2,026 | md | Markdown | _posts/3/2021-04-06-klaus-meine.md | chito365/ukdat | 382c0628a4a8bed0f504f6414496281daf78f2d8 | [
"MIT"
] | null | null | null | _posts/3/2021-04-06-klaus-meine.md | chito365/ukdat | 382c0628a4a8bed0f504f6414496281daf78f2d8 | [
"MIT"
] | null | null | null | _posts/3/2021-04-06-klaus-meine.md | chito365/ukdat | 382c0628a4a8bed0f504f6414496281daf78f2d8 | [
"MIT"
] | null | null | null | ---
id: 5385
title: Klaus Meine
date: 2021-04-06T19:48:21+00:00
author: Laima
layout: post
guid: https://ukdataservers.com/klaus-meine/
permalink: /04/06/klaus-meine
tags:
- Is Married?
- Is Single?
- Relationships
category: Family Guides
---
* some text
{: toc}
## Who is Klaus Meine
He rose to prominence as the lead singer of the German metal band Scorpions, which became known for the hit song “Rock You Like a Hurricane.”
## Prior to Popularity
He joined the Scorpions a year after their creation and had a strong tenor voice that worked well with the heavy metal sound the founders were going for.
## Random data
He and Rudolf Schenker are the only members of the Scorpions that have appeared on every one of the band’s albums.
## Family & Everyday Life of Klaus Meine
He married Gabi Meine in 1976. The couple has one son, Christian.
## People Related With Klaus Meine
He performed at the demolition of the Berlin Wall with Scorpions’ guitarist Matthias Jabs.
| 21.784946 | 153 | 0.374136 | eng_Latn | 0.998378 |
a6caa1366e88c0442e6f3381f6931ff07d72d18b | 2,383 | md | Markdown | things-batch-importer/README.md | stefferber/iot-things-examples | 56d8f95473a477b62dbca45df778e6b63630eb26 | [
"BSD-Source-Code"
] | 56 | 2016-10-25T12:19:39.000Z | 2019-12-13T13:43:22.000Z | things-batch-importer/README.md | stefferber/iot-things-examples | 56d8f95473a477b62dbca45df778e6b63630eb26 | [
"BSD-Source-Code"
] | 21 | 2017-01-05T13:46:28.000Z | 2019-10-30T07:44:25.000Z | things-batch-importer/README.md | stefferber/iot-things-examples | 56d8f95473a477b62dbca45df778e6b63630eb26 | [
"BSD-Source-Code"
] | 32 | 2016-12-28T15:14:17.000Z | 2019-11-27T10:05:43.000Z | # Bosch IoT Things - Batch Importer Tool
### Description
This tool is designed to import things from one or more files in a specific directory into a Bosch IoT Things service instance.
The file(s) should contain one thing per line in JSON format e.g.
`{ "thingId": "namespace:thing-name", "policyId": "namespace:policy-name", "attributes": { "foo": 1 }, "features": {...} }`
##### Prerequisites:
- Knowledge of Java
- Knowledge of Maven
- [Solution](https://docs.bosch-iot-suite.com/things/getting-started/booking/basic-data/) information like solutionId and apiToken have to be present.
- [Namespace](https://docs.bosch-iot-suite.com/things/getting-started/booking/manage-namespace/) in which the things should be imported, have to be created.
- Import file(s) with one thing per line in JSON format.
- [User of Bosch IoT Permissions](https://docs.bosch-iot-suite.com/things/examples-demo/createuser/) or - alternatively - [Public Key](https://docs.bosch-iot-suite.com/things/getting-started/booking/manage-key/) for authenticating the Things client.
- Websocket endpoint has to be configured in config.properties.
### Preparation
Create at least one [policy](https://docs.bosch-iot-suite.com/asset-communication/Initial-policy.html) which you can assigned to your things.\
Set your credentials under `/src/main/resources/config.properties`. You can use `src/main/resources/config-template.properties` as a template.
### How to build Things batch importer tool
Build the jar file with following command.
```bash
mvn clean install
```
### How to run Things batch importer tool
```$bash
cd target
java -Xms2G -Xmx4G -DthingsConfigFile="### absolutePathToConfig ###" -jar things-batch-importer-0-SNAPSHOT-jar-with-dependencies.jar "### absolutePathToUploadDirectory ###"
```
If the import is interrupted the import tool can just be re-executed. It then continues to import where it previously stopped.
### Created files during batch import
The import tool will create the following files during the batch import:
- completedFile.txt - contains all files which were uploaded successfully.
- errorFile - contains the error messages for the things which could not be uploaded.
- retryFile.txt - contains the things and the error message why it could not be uploaded, separated by a '#'.
# License
See the iot-things-examples top level README.md file for license details.
| 48.632653 | 249 | 0.762904 | eng_Latn | 0.972661 |
a6cac132b4f2a28cf9ad5757dc41f078fe3e8428 | 9,469 | md | Markdown | _posts/2010-5-19-曾节明：胡锦涛是导致中国大倒退的罪魁祸首.md | backup53/1984bbs | 152406c37afab79176f0d094de5ac4cb0c780730 | [
"MIT"
] | 18 | 2020-01-02T21:43:02.000Z | 2022-02-14T02:40:34.000Z | _posts/2010-5-19-曾节明：胡锦涛是导致中国大倒退的罪魁祸首.md | wzxwj/1984bbs | 152406c37afab79176f0d094de5ac4cb0c780730 | [
"MIT"
] | 3 | 2020-01-01T16:53:59.000Z | 2020-01-05T10:14:11.000Z | _posts/2010-5-19-曾节明：胡锦涛是导致中国大倒退的罪魁祸首.md | backup53/1984bbs | 152406c37afab79176f0d094de5ac4cb0c780730 | [
"MIT"
] | 13 | 2020-01-20T14:27:39.000Z | 2021-08-16T02:13:21.000Z | ---
layout: default
date: 2010-5-19
title: 曾节明：胡锦涛是导致中国大倒退的罪魁祸首
categories: 雅典学院
---
# 曾节明：胡锦涛是导致中国大倒退的罪魁祸首
再世关羽
1楼 大 中 小 发表于 2010-5-19 10:47 只看该作者
曾节明：胡锦涛是导致中国大倒退的罪魁祸首
文章摘要: 胡锦涛根本不是什么“开明派”，江泽民之后，中国社会发生的大幅倒退、中国人权状况的全面恶化，就是胡锦涛主导所为，就是胡锦涛的本意！
作者 : 曾节明,
發表時間：5/17/2010
胡锦涛上台近八年来，中国社会全面倒退十分明显：政治上重新集权，加强以党凌政、党控司法、重新强化居委会等基层党组织，新闻出版上扼杀江时期民营出版业萌芽、以“六四”后未有的力度整肃媒体和出版社、厉行媒体一律、大肆禁书、禁播、对互联网的封锁变本加厉，一再大幅升级...大大收紧言论钳制尺度，公开反对自由民主等“普世价值”、炮制《六个为什么》、恢复大规模直接意识形态洗脑，重判刘晓波、严酷镇压自由派知识分子，摧毁国内非政府NGO组织、大力封杀江后期隐然成型的市民社会，重树毛泽东旗帜、大力纵容毛左派、开“改革开放”三十年来镇压维权上访之先河，在经济上，扭转江泽民时期市场化方向，厉行
“国进民退”、重新扶持国企扩张、强化政府对土地垄断、制造房地产泡沫、纵容全面强迫拆迁、强迫征地，以卖地经济保政权....目睹如此恶劣的事实，近年来已在中国人权问题上态度温吞的美国，都作出了“中国人权状况全面恶化”的评价1。
倒退的趋势是如此的明显和恶劣，以致于许多看好胡锦涛的人，也不得不承认倒退的事实，但他们却普遍把胡锦涛上台以来发生的所有倒退，说成是江泽民“垂帘听政”的结果。
周亚辉先生就是持这种观点的典型：大约在2009年下半年，自称是澳大利亚华人的周亚辉先生出现博讯上，时常一日数贴地为胡锦涛辩护，周先生想当然地认定胡锦涛是改革派，并断定所有的倒退都是江泽民造成的，我感慨于周亚辉这样“海外华人”（如果他真是海外华人的话），对胡锦涛误解之深、对中共现政权常识之匮乏，因此愿在此关键处再做一番分析（尽管我以往多次剖析过胡锦涛其人本质真相），以供读者参考。
那种认为胡锦涛上台后的倒退是江泽民造成的观点，至少带有以下无法自圆的大破绽：
首先，江泽民时期的大部分时间（1992年——2002年），比胡锦涛时期开明和宽松是客观事实；江泽民真要倒退，在其任上何不轻松实行，反而在退职后费力地间接实施？
有人认为江泽民此举是要搞臭胡锦涛，再伺机“复位”，这种解释更站不住脚，一则因为中共政权与民意无关，倒退的臭名损害不了独裁者的权力，二则因为重趋集权的倒退只有利于胡锦涛独裁，而不利于江泽民卷土重来。那么，江泽民去搞这种费事不得好的极权倒退为哪般（如果江泽民真能“垂帘听政”搞倒退的话）？
第二，如果真如周亚辉先生所说的：胡锦涛上台后没有实权，一直是江泽民在幕后掌权，那么江泽民的铁杆亲信，上海护巢留守陈良宇怎么会倒台？江泽民的另一心腹黄菊怎么会失势？胡锦涛作为总书记、国家主席和军委主席，既然有权力抓捕陈良宇，八年来就没有权力减轻一点暴政？哪怕是一丝一毫的减轻？
第三，江泽民“退而不休”是事实，但江泽民远没有邓小平的权威也是公认的事实。稍有头脑的人可以看到这样的对比：当年胡耀邦、赵紫阳在邓小平、陈云领衔的
“中顾委”掣肘下，仍然可以保护“自由化”人士和团体、大力推进新闻出版自由、筹备党政分开、播出《河觞》...如果胡锦涛真是开明派的话，为什么他在能量远不及邓小平、陈云的江泽民的“掣肘”下，反而什么开明的举措都没有，有的只是极权倒退呢？
以上破绽是如此明显，但周亚辉先生却不愿面对，他的理由是：九常委中李长春、贾庆林、吴邦国、周永康、习近平都是江泽民的人马，胡锦涛在九常委中只有一票，因此，江泽民得以通过常委中的多数票制定了倒退政策；周亚辉先生还咬定：刘晓波是周永康抓判的，与胡锦涛无关。
这就反映出以周亚辉先生为典型的群体，对中共现政权常识性的无知。现今中共政权，意识形态早已破产，一把手的权威基本上是由职务衍生的职权之威，而非个人魅力和个人人格之威，邓小平之后的中共领导人，离开了职务很难有“权威”可言。在邓小平强人时代终结后，统治集团内已很少有人身依附关系的个人效忠，李长春、贾庆林、吴邦国、周永康等人过去与其说效忠江泽民，莫如说效忠他们自己的既得利益，一旦江泽民因失去了职权而不能再充分起到他们保护伞的作用，这些人为保既得利益，不可能不转投新皇帝胡锦涛所好，否则，贪腐劣迹斑斑的他们，就有步陈良宇后尘的危险。
这，在李长春、吴邦国身上体现得尤其明显，李长春八十年代时是地方干部中的改革派先锋，在江泽民时期也不是顽固派，现在却整一个左棍腔调；而老滑头吴邦国，在江时期主政上海时支持“思想解放”，现在却公开反对“普世价值”…贾庆林的情况也是如此。
由于江泽民远没有邓小平的淫威，没有能力在失去职位的情况下，通过常委中的人马主导中国倒退，李长春等人的转变不能不说是“上（胡锦涛）有所好，下必甚焉”。
周亚辉先生的另一大误解是认为中共总书记只有常委会一票的权力。众所周知，中共党内施行的也是假民主——或曰“民主集中制”，在下级服从上级的铁律下，民主是假，集中（独裁）是真，因此投票不过是过场，政治局常委会同样如此，投票之前，已经由一把手定调，常委会中，总书记举足轻重、一锤定音，而并非由多数常委说了算，例如：江泽民发起镇压法轮功，就没得到多数常委支持；既然没有多数支持，为何仍然推出了镇压法轮功的政策？这能说明中共总书记只有常委会一票的权力？
事实上，由于直接掌控宣传、军委、政法委大权，中共总书记拥有无上自主行事权，象收紧舆论控制、加强封网、军管“维稳”、镇压维权、扫荡NGO、批判“普世价值”、重树共产意识形态等极权倒退措施的施行，根本无须经过政治局常委会，集总书记、军委主席、国家主席三权于一身的胡锦涛完全可以在日常工作中自行其是。
认为刘晓波是周永康抓判的，与胡锦涛无关，则属于此种谬误中最为荒谬的观点。首先，依照中共政权的运作规矩，象刘晓波案这样具有重大国际影响的政治大案，属总书记和国家主席胡锦涛重点过问的大事，根本不是政法委书记周永康能够决定得了的；其次，按照中共组织原则，政法委书记在总书记领导下工作，因此，若没有一把手胡锦涛的批示，并没有多大能量和权威的周永康既不敢、也犯不着擅自做主把刘晓波抓起来重判十一年。
周亚辉先生对以上情况统统不察，为了证明胡锦涛是“改革派”，他还搬出胡耀邦提拔胡锦涛的往事。的确，胡耀邦于1985年，将胡锦涛由甘肃建委提拔至团中央是事实，但胡耀邦提拔胡锦涛，不能说明胡锦涛就是改革派；比如，胡耀邦还力排众议任用薄一波，薄一波是改革派吗？
事实上，胡锦涛是党内顽固派宋平、邓力群培养并大力举荐的人，他从来不是胡耀邦的追随者；宋平是中共顽固派大佬陈云的大徒弟，性格软弱的胡耀邦不敢不买陈云的帐。胡锦涛内心对胡耀邦可能怀有一些感激之情，但在治国理念上两人根本格格不入，这从两人对西藏的政策上可以充分地看出来。
胡锦涛从来就不是什么“改革派”，还可以从他的经历、性格和他的言行举止中看出来。胡锦涛思想塑形的大学时代，正是上世纪五十年代毛共的黄金岁月，他以其又红又专的楷模表现，被任用为大学辅导员，可见其毛共思想深入骨髓，而且，在整个毛时代，胡锦涛一帆风顺；这与戈尔巴乔夫青年时期深受赫鲁晓夫否定斯大林之启蒙，截然相反。
胡锦涛的人文素养也根本撑不起“改革派”的资质，与戈尔巴乔夫、赵紫阳博览西方名著相反，胡锦涛平时不学无术、熟读仅有卓娅与舒拉、斯大林和毛泽东的篇章。
从胡锦涛对刘军宁和老上级朱泽厚的态度可以看出，此人貌似忠厚，实则嫉妒心极强、心胸狭窄、残酷无情、手段阴狠；他和与人为善的胡耀邦根本是两种人，这样的人是不可能有推行政治改革的道德和胸襟的。
除了上台之初，立足未稳之际唱过两句“以人为本”、“依宪治国”的花腔外，胡锦涛上台后没有任何开明的作为，反而随着权力的巩固，倒退言论不断加重、倒退步伐不断地加大：上台伊始就发起远比江泽民“三讲”更左、更荒谬的“保先”运动、2004年九月接掌军委主席当天，即发表政治学朝鲜、古巴的讲话（即“九一九”讲话）2；2005年五月又发出杀气腾腾的五一五讲话，重提“反自由化”、斥巨资扶持高校马列学院…2008
下半年开始，更公开发起批判“普世价值”运动、并炮制《六个为什么》，再次施行大规模的意识形态洗脑工程……
分析这里，中国八年来大倒退的原因也就出来了，答案只有一个，且如秃子头上的虱子，那就是，胡锦涛根本不是什么“开明派”，江泽民之后，中国社会发生的大幅倒退、中国人权状况的全面恶化，就是胡锦涛主导所为，就是胡锦涛的本意！
最后需要说明的是：我做此番评析，不是要为江泽民辩护，而是希望提请同胞们克复中国人“麻将思维”的弱点，具体问题具体分析，不要搞笼统化、相对（无所谓）化，江泽民的罪归江泽民，而胡锦涛必须承担他上台八年来犯下的累累罪行。
我想特别提醒某些群体：当前当权的独裁者是胡锦涛而非别人，胡锦涛是一个标准的顽固派中共党棍，是比江泽民远为凶恶的中国民主化当前大敌，是中共现政权的驾驶员和中国极权势力的总代表，如果不旗帜鲜明地反对胡锦涛倒行逆施，反而把今天的迫害当成昨天的迫害，把2010
当作1999，继续对更凶恶的新独裁者浮想联翩的话，反迫害反专制的抗争就会无的放矢、就会陷于空泛化、泡沫化，甚至无意中沦为衬扶新独裁者的帮腔造势的工具。
曾节明 成稿于二〇一〇年五月十六日星期日下午于曼谷寓所
注1：2010年三月十二日美国之音报道，题：《美国国务院人权报告：中国人权状况恶化》
注2：《開放》2004年12月號，题：《胡錦濤四中全會講話曝光，嚴厲打擊自由化絕不手軟》，2004年九月十九日胡锦涛在四中全会上此话的原话为：“管理意識形態，我們要學習古巴和朝鮮。朝鮮經濟雖然遇到暫時困難，但政治上是一貫正確的。”
---
[Terminusbot](https://github.com/TerminusBot) 整理，讨论请前往 [2049bbs.xyz](http://2049bbs.xyz/)
---
写实
自由，就是宽容异端的思想言论
2楼 大 中 小 发表于 2010-5-19 10:53 只看该作者
极权倒退
花想容
依据用户管理细则，账号永久停用。
3楼 大 中 小 发表于 2010-5-19 10:56 只看该作者
太抬举胡锦涛了，他哪有那个能力？使中国倒退的正是自以为站起来了的中国人民。
咸鱼干
米国西太平洋大学性学博士、哥伦逼样大学女性心理学博导、加州理工大学前戏研究室主任
4楼 大 中 小 发表于 2010-5-19 10:56 只看该作者
江CORE是不是还有实权，其实从陈良宇被拿下就已经一目了然了。
nathansam
1984OR2012
5楼 大 中 小 发表于 2010-5-19 11:12 只看该作者
别的不知道，反正这几年的房价是嗖嗖的往上飞
光明的格里高利
八卦爱好者
6楼 大 中 小 发表于 2010-5-19 11:13 只看该作者
这种文章真没意思
碎碎
7楼 大 中 小 发表于 2010-5-19 11:15 只看该作者
完全不明真相的群众路过
只是单纯觉得粉笔胡表情狰狞邪恶
永远不要跟我扯强国的淡
8楼 大 中 小 发表于 2010-5-19 12:15 只看该作者
胡杂种万碎
毛妖魔、邓屠夫、江戏子、胡杂种
萧易寒
9楼 大 中 小 发表于 2010-5-19 12:17 只看该作者
集权体制都会越来越差，最终走向灭亡
彩虹咖啡馆
10楼 大 中 小 发表于 2010-5-19 12:20 只看该作者
叫我胡说八年四个字惨不忍睹。
我卖糕的 该用户已被删除
11楼 大 中 小 发表于 2010-5-19 13:08 只看该作者
写得不错。
反正中国前途黯淡
墙倒众人推
靠谱青年 暂时闭关一段时间
12楼 大 中 小 发表于 2010-5-19 13:10 只看该作者
刚上台还满心期望胡温新政，实在是失望透顶。真是一个比一个垃圾。
光明的格里高利
八卦爱好者
13楼 大 中 小 发表于 2010-5-19 14:27 只看该作者
咦，胡刚上台，我就没看好它，现在的确是如此
还是我眼光准，超过至少90%的知识分子
温一上台，我也没看好它，结果也是这样
二师兄
14楼 大 中 小 发表于 2010-5-19 19:25 只看该作者
管它什么鸟人，想什么鸟心思，造成倒退是事实～
U-TA
好人修电脑 坏人床上搞
15楼 大 中 小 发表于 2010-5-19 19:36 只看该作者
胡的确阴郁的厉害，看他的表情，总觉得毛骨悚然。
kb24
魔都人。去除赤化，恢复中华。
16楼 大 中 小 发表于 2010-5-19 19:51 只看该作者
引用:
> 原帖由 墙倒众人推 于 2010-5-19 13:10 发表
> 
> 刚上台还满心期望胡温新政，实在是失望透顶。真是一个比一个垃圾。
现在说起胡温新政这几个字真觉得是个大笑话。。。
Yak
17楼 大 中 小 发表于 2010-5-19 21:30 只看该作者
胡是热锅上的蚂蚁，但也可以证明共产党的死期快到了。
WJ87
无产阶级煽动家
18楼 大 中 小 发表于 2010-5-19 21:36 只看该作者
看过这篇之后，我恍惚中感觉自己倒退回了那个凭一个人的力量可以左右一个国家兴废的皇权时代。不知道有没有与我同感的朋友呢
大老宋
19楼 大 中 小 发表于 2010-5-19 21:37 只看该作者
都一个比样
‥莫風先生。
在这个不自由的时代，人人都会互为异见者，请多一些包容的情怀，攻击指责别人并不会让自己高高在上。
20楼 大 中 小 发表于 2010-5-19 23:16 只看该作者
哎！只有逃离专制大陆了！！
singlefabulous
21楼 大 中 小 发表于 2010-5-19 23:28 只看该作者
这种把希望/责任寄托在一个人身上的文章没意思。。。。讲到底中国还是喜欢讲人治，不理会制度
weke
挪威.奥斯陆
22楼 大 中 小 发表于 2010-5-19 23:49 只看该作者
写得不错。
magic7days
aeolus
23楼 大 中 小 发表于 2010-5-19 23:50 只看该作者
引用:
> 原帖由 花想容 于 2010-5-19 10:56 发表 
> 使中国倒退的正是自以为站起来了的中国人民。
+
须佐之男
24楼 大 中 小 发表于 2010-5-20 00:17 只看该作者
倒退？什么叫倒退？中国又变回旧中国了？
真正倒退的是我们这些人民的意识
文山八事
25楼 大 中 小 发表于 2010-5-20 00:36 只看该作者
引用:
> 原帖由 立春 于 2010-5-19 12:15 发表
> 
> 毛妖魔、邓屠夫、江戏子、胡杂种
G抢党的头都没有一个好人
花想容
依据用户管理细则，账号永久停用。
26楼 大 中 小 发表于 2010-5-20 03:00 只看该作者
引用:
> 原帖由 光明的格里高利 于 2010-5-19 14:27 发表
> 
>
> 咦，胡刚上台，我就没看好它，现在的确是如此
> 还是我眼光准，超过至少90%的知识分子
> 温一上台，我也没看好它，结果也是这样
哪有那90%存在？是编造的吧。周围问来问去，都是10%：）
singsingchow
27楼 大 中 小 发表于 2010-5-20 04:04 只看该作者
可惜手里没选票，上面怎么玩都行，换了谁都是一样打口炮
太变
偏听不信
28楼 大 中 小 发表于 2010-5-20 08:16 只看该作者
引用:
> 原帖由 kb24 于 2010-5-19 19:51 发表
> 
>
> 现在说起胡温新政这几个字真觉得是个大笑话。。。
现在只有苦笑的份了
光明的格里高利
八卦爱好者
29楼 大 中 小 发表于 2010-5-20 08:20 只看该作者
引用:
> 原帖由 花想容 于 2010-5-20 03:00 发表 
>
>
> 哪有那90%存在？是编造的吧。周围问来问去，都是10%：）
刚一上台时鼓吹的胡温新政，宣传力度不是盖的，都不止90%，这只是保守估计
那个砍柴还不出了篇舔屁沟文
丁春秋
30楼 大 中 小 发表于 2010-5-20 08:34 只看该作者
胡说八年
cslovejia
31楼 大 中 小 发表于 2010-5-20 08:51 只看该作者
被谁日翻在地不是日呢
讽冻人
32楼 大 中 小 发表于 2010-5-20 09:07 只看该作者
回复 29楼 太变 的话题
一下子都会想不出胡书记的“形状”来了
elephantdancing
33楼 大 中 小 发表于 2010-5-20 09:18 只看该作者
党控司法，现在县级法院以和谐稳定为最高目标，谁能闹，谁就能在官司上得到倾斜，或者完全扭曲，操！！！！
Caohexie
34楼 大 中 小 发表于 2010-5-20 09:38 只看该作者
万岁万岁万万岁！
千年王八万年龟。
smder
35楼 大 中 小 发表于 2010-5-20 10:34 只看该作者
恩，貌似就是这个样子滴。
platism
36楼 大 中 小 发表于 2010-5-20 12:49 只看该作者
宣传力度那是中宣部干的，和知识分子有啥关系。反过来说，当年“朝鲜在政治上是正确的”，此话一出，凡是可以称为知识分子的，个个心惊吧？不知道你的90%从何而来。
引用:
> 原帖由 光明的格里高利 于 2010-5-20 08:20 发表
> 
>
>
> 刚一上台时鼓吹的胡温新政，宣传力度不是盖的，都不止90%，这只是保守估计
>
> 那个砍柴还不出了篇舔屁沟文
stevenking
The real Slim Shady never stands up.
37楼 大 中 小 发表于 2010-5-20 21:36 只看该作者
不错不错。老子反正看戏。
| 7.82562 | 287 | 0.676523 | yue_Hant | 0.884233 |
a6cb79060fbc676434bca47b78c27d32180c2c4b | 1,695 | md | Markdown | docs/relational-databases/system-tables/sysmergearticlecolumns-transact-sql.md | Jteve-Sobs/sql-docs.de-de | 9843b0999bfa4b85e0254ae61e2e4ada1d231141 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/relational-databases/system-tables/sysmergearticlecolumns-transact-sql.md | Jteve-Sobs/sql-docs.de-de | 9843b0999bfa4b85e0254ae61e2e4ada1d231141 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/relational-databases/system-tables/sysmergearticlecolumns-transact-sql.md | Jteve-Sobs/sql-docs.de-de | 9843b0999bfa4b85e0254ae61e2e4ada1d231141 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
description: sysmergearticlecolumns (Transact-SQL)
title: sysmergearticlecolumns (Transact-SQL) | Microsoft-Dokumentation
ms.custom: ''
ms.date: 03/06/2017
ms.prod: sql
ms.prod_service: database-engine
ms.reviewer: ''
ms.technology: replication
ms.topic: language-reference
f1_keywords:
- sysmergearticlecolumns
- sysmergearticlecolumns_TSQL
dev_langs:
- TSQL
helpviewer_keywords:
- sysmergearticlecolumns system table
ms.assetid: 1ad8663f-a624-42a2-8641-fefac3433c97
author: CarlRabeler
ms.author: carlrab
ms.openlocfilehash: 8bae31473976690ea60575b7ab3ce902f46d3c32
ms.sourcegitcommit: e700497f962e4c2274df16d9e651059b42ff1a10
ms.translationtype: MT
ms.contentlocale: de-DE
ms.lasthandoff: 08/17/2020
ms.locfileid: "88427622"
---
# <a name="sysmergearticlecolumns-transact-sql"></a>sysmergearticlecolumns (Transact-SQL)
[!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
Die **sysmergearticlecolumns** -Tabelle enthält eine Zeile für jede Tabellenspalte, die in einer Mergeveröffentlichung veröffentlicht wird, und ordnet jede Spalte dem zugehörigen Mergeartikel zu. Diese Tabelle wird in der Veröffentlichungsdatenbank gespeichert.
|Spaltenname|Datentyp|BESCHREIBUNG|
|-----------------|---------------|-----------------|
|**artid**|**int**|Identifiziert einen Artikel.|
|**ColId**|**smallint**|Identifiziert eine Spalte in einem Artikel.|
## <a name="see-also"></a>Weitere Informationen
[Replikations Tabellen (Transact-SQL-)](../../relational-databases/system-tables/replication-tables-transact-sql.md)
[Replikationssichten (Transact-SQL)](../../relational-databases/system-views/replication-views-transact-sql.md)
| 39.418605 | 265 | 0.762242 | deu_Latn | 0.324826 |
a6cc077bd4aba78e73f58471ac98040ce98dd56d | 191 | md | Markdown | docs/04.技术/02.算法/02.B树.md | zoeminghong/zeros-tech | cafa2af3891f445383d8befc3f46e47e90c87e77 | [
"MIT"
] | 1 | 2020-03-22T15:25:35.000Z | 2020-03-22T15:25:35.000Z | docs/04.技术/02.算法/02.B树.md | zoeminghong/zeros-tech | cafa2af3891f445383d8befc3f46e47e90c87e77 | [
"MIT"
] | 1 | 2021-09-02T08:34:25.000Z | 2021-10-15T00:46:45.000Z | docs/04.技术/02.算法/02.B树.md | zoeminghong/zeros-tech | cafa2af3891f445383d8befc3f46e47e90c87e77 | [
"MIT"
] | null | null | null | ---
title: B树
date: 2021-02-08 09:57:36
permalink: /pages/8d4df3/
categories:
- 技术
- 算法
tags:
- null
comment: true
---
# B树
<https://blog.csdn.net/dazhong159/article/details/7963846> | 13.642857 | 58 | 0.664921 | fra_Latn | 0.077998 |
a6cc3b552ec0c4f82006d306b662d11b8deae7a1 | 5,951 | md | Markdown | _posts/2018-09-22-Download-popular-mechanics-101-things-that-go-fast-planes-trains-and-automobiles-you-can-make-and-ride.md | Camille-Conlin/26 | 00f0ca24639a34f881d6df937277b5431ae2dd5d | [
"MIT"
] | null | null | null | _posts/2018-09-22-Download-popular-mechanics-101-things-that-go-fast-planes-trains-and-automobiles-you-can-make-and-ride.md | Camille-Conlin/26 | 00f0ca24639a34f881d6df937277b5431ae2dd5d | [
"MIT"
] | null | null | null | _posts/2018-09-22-Download-popular-mechanics-101-things-that-go-fast-planes-trains-and-automobiles-you-can-make-and-ride.md | Camille-Conlin/26 | 00f0ca24639a34f881d6df937277b5431ae2dd5d | [
"MIT"
] | null | null | null | ---
layout: post
comments: true
categories: Other
---
## Download Popular mechanics 101 things that go fast planes trains and automobiles you can make and ride book
A The major's jaw quivered; his face colored. But it would be wonderful, stammering. of islands to 89 deg. It's a benefit that comes with my job Gaulitz nodded emphatically. The great evaporation from these pools, 'And what is your warning?' And they said, like popular mechanics 101 things that go fast planes trains and automobiles you can make and ride. The probable reason didn't require much guesswork; Earth's political history was riddled with instances of authorities provoking disturbances deliberately in order popular mechanics 101 things that go fast planes trains and automobiles you can make and ride justify tough responses in the eyes of their own people. questions, limp, the companies that built the shuttles and other hardware worked out the technical specifications because that was their business, and by the time that he had driven only three miles? [Illustration: THE STEAMER "FRASER. You don't have He nodded. Problem familiesвFiction. " of weathered granitic rocks, nor was there any in the city but betook himself to her, the blood was Cain's? She's a good kid! 221 of stones is carried on as a home industry, rocky masses. The only path to redemption that seemed open to him was his sister. More likely, and says, hast thou outraged my honour and entered my house and played the traitor with me and tookest no thought unto that which I have done thee of benefits?" "O king," answered the youth. " McKillian had been crawling up the ladder as she said this. I've got a client Even more remarkable was another prediction that followed from the Chironian symmetry relationships, but alot of the time, another had indicated the location of what she cane-clubbed body sprawled in that hat-lined bedroom, the Swedish prisoner-of-war, not at all surprised, high-backed chair facing him. Either they wouldn't spirit sewn to spirit with the strong thread of Curtis's reckless trust? " To Micky, thin material instead of fibrous spider-silk, the Smiling. ' Then do thou straightway knock at the Cadi's door, "that's what they're there for!" In the late-afternoon light, fine reputation, Paul withdrew a sheet someday, which is maybe pretty "He drinks because he drinks," she said, that would be far They have seldom a cross section of more than thirty or forty file:D|Documents20and20Settingsharry. " this realization that an iciness welled in his gut, you don't have a place Even the beginning of June was very cold. ] As a recreational site, between the Ob and the Yenisej. Anger's kept me going all my the river with curious glances. long, and his face popular mechanics 101 things that go fast planes trains and automobiles you can make and ride with guilt. It didn't mean anything! Sinsemilla's versions of Mother He half expected to hear Thomas Vanadium in the distance, but also the "I thought so," Angel said. Their eyes were only for each other, Mr, had been obtained in the same way. been given to criminals, eyes bleary but aware. I just thought you'd like to hear it! Needs must a thief revert to his vile origin, Fr. You performed this very month in South Africa, peering into the windows of the girl's soul, L, of course, like purpose before it. Without water, unmoving? He wasn't sharing his bed Tom Vanadium's uninflected but curiously hypnotic voice, choosing your partners rather than leaving them to chance, never saw eyes a fairer than it, calm again, he had nonetheless taken time. I don't know they showed good judgment and readiness of resource, is at risk of heatstroke. running in terror, favoring neither-except in-the matter of pie delivery, if not morally questionable. " Roughly 35 percent of Chiron's surface was land, had it done and hung out one sunny day before she knew what he was doing. Swedish consul-general regarding the day of our arrival, and to a land demolition expert swung a sledgehammer at a headlight. "They're probably in there. "And don't think you've been so lucky," he warned as the Chironian walked away. your glass?" pledges and tears and the slobbered caresses that followed them. "I was attractive in my day, ii, with the _Vega's_ weak steam-power, but the fact remained that somebody seemed to be exploring the potential for fomenting unrest among the Chironians. Skeleton of Rhytina, and set off down the valley towards the mine, p. "Scribe", Barty levered himself onto the seat beside her. ' And the king said, wails of anguish. " Bay-ice, one of them might retreat here to the bedroom. Since arriving on Chiron he had seen many such reminders of ways of life on Earth that nobody from Chiron had known. " The dinner guest leaned back into the car, and set off down the valley towards the mine! interpreter, by reason of that which she saw in their eyes of alteration, 'For aught I know, counting days as he goes. " Intentionally or unintentionally the contents of the sacks sour I'm not dead and buried in some unmarked grave, clear, mountain chain from the winds coming from that quarter, alternating with carpets of _Halianthus of little conspiracy here, ii. constantly in a cloud of watery vapour, I could learn! Old woman from a village inland, she pulled up her clothes and sitting down on the singer's yard, Wellesley said in a still angry voice to the popular mechanics 101 things that go fast planes trains and automobiles you can make and ride recording the proceedings. That green hill, only a against his arm, or it will be the cause of thy destruction; for I am certified that thou purposest my dishonour, which towards the interior of the island was marshy, and her green eyes clouded, you eat those Raisinets?" Jacob trusted no one but Agnes and Edom. finally succeeded in distilling spirits from a sugar-bearing plant guided Western medicine since Hippocrates, I understood how final it is. | 661.222222 | 5,784 | 0.792808 | eng_Latn | 0.999918 |
a6ccd670f42342da2edab8667b5eeff6c95717b8 | 405 | md | Markdown | README.md | pr0d1r2/homebrew-cask-apps | dc0bb30a19e8464b9958219524138938141b8462 | [
"MIT"
] | null | null | null | README.md | pr0d1r2/homebrew-cask-apps | dc0bb30a19e8464b9958219524138938141b8462 | [
"MIT"
] | null | null | null | README.md | pr0d1r2/homebrew-cask-apps | dc0bb30a19e8464b9958219524138938141b8462 | [
"MIT"
] | null | null | null | # homebrew-cask-apps
Casks with binary distributed apps.
# Usage
After you install homebrew-cask, run the following command:
```
$ brew tap pr0d1r2/cask-apps
```
You can now install apps.
### PYM Player
One of the best video players:
```
$ brew cask install pym_player
```
### OmniFocus (version 2)
In case for some reason, you want to use old OmniFocus:
```
$ brew cask install omnifocus2
```
| 13.5 | 59 | 0.703704 | eng_Latn | 0.996029 |
a6cce2d88dcb5e1e8bc5d1e4d699877724c49e37 | 4,285 | md | Markdown | doc/release-process.md | ghostcoinproject/ghostcoin | b1d4c0355a4dd6a960ec30e7cabd211cf4adac84 | [
"MIT"
] | null | null | null | doc/release-process.md | ghostcoinproject/ghostcoin | b1d4c0355a4dd6a960ec30e7cabd211cf4adac84 | [
"MIT"
] | null | null | null | doc/release-process.md | ghostcoinproject/ghostcoin | b1d4c0355a4dd6a960ec30e7cabd211cf4adac84 | [
"MIT"
] | 2 | 2018-01-24T13:46:10.000Z | 2020-09-08T14:25:52.000Z | Release Process
====================
* * *
###update (commit) version in sources
ghostcoin-qt.pro
contrib/verifysfbinaries/verify.sh
doc/README*
share/setup.nsi
src/clientversion.h (change CLIENT_VERSION_IS_RELEASE to true)
###tag version in git
git tag -s v0.8.8.0
###write release notes. git shortlog helps a lot, for example:
git shortlog --no-merges v0.8.7.7..v0.8.8.0
* * *
##perform gitian builds
From a directory containing the ghostcoin source, gitian-builder and gitian.sigs
export SIGNER=(your gitian key, ie bluematt, sipa, etc)
export VERSION=0.8.8.0
cd ./gitian-builder
Fetch and build inputs: (first time, or when dependency versions change)
mkdir -p inputs; cd inputs/
wget 'http://miniupnp.free.fr/files/download.php?file=miniupnpc-2.0.20170509.tar.gz' -O miniupnpc-2.0.20170509.tar.gz'
wget 'https://www.openssl.org/source/openssl-1.0.2l.tar.gz'
wget 'http://download.oracle.com/berkeley-db/db-5.3.28.NC.tar.gz'
wget 'http://zlib.net/zlib-1.2.11.tar.gz'
wget 'http://download.sourceforge.net/libpng/libpng-1.6.30.tar.gz'
wget 'http://fukuchi.org/works/qrencode/qrencode-3.4.4.tar.bz2'
wget 'http://downloads.sourceforge.net/project/boost/boost/1.55.0/boost_1_55_0.tar.bz2'
wget 'http://download.qt.io/official_releases/qt/4.8/4.8.7/qt-everywhere-opensource-src-4.8.7.tar.gz'
cd ..
./bin/gbuild ../ghostcoin/contrib/gitian-descriptors/boost-win32.yml
mv build/out/boost-*.zip inputs/
./bin/gbuild ../ghostcoin/contrib/gitian-descriptors/deps-win32.yml
mv build/out/ghostcoin*.zip inputs/
./bin/gbuild ../ghostcoin/contrib/gitian-descriptors/qt-win32.yml
mv build/out/qt*.zip inputs/
Build ghostcoind and ghostcoin-qt on Linux32, Linux64, and Win32:
./bin/gbuild --commit ghostcoin=v${VERSION} ../ghostcoin/contrib/gitian-descriptors/gitian.yml
./bin/gsign --signer $SIGNER --release ${VERSION} --destination ../gitian.sigs/ ../ghostcoin/contrib/gitian-descriptors/gitian.yml
pushd build/out
zip -r ghostcoin-${VERSION}-linux.zip *
mv ghostcoin-${VERSION}-linux.zip ../../
popd
./bin/gbuild --commit ghostcoin=v${VERSION} ../ghostcoin/contrib/gitian-descriptors/gitian-win32.yml
./bin/gsign --signer $SIGNER --release ${VERSION}-win32 --destination ../gitian.sigs/ ../ghostcoin/contrib/gitian-descriptors/gitian-win32.yml
pushd build/out
zip -r ghostcoin-${VERSION}-win32.zip *
mv ghostcoin-${VERSION}-win32.zip ../../
popd
Build output expected:
1. linux 32-bit and 64-bit binaries + source (ghostcoin-${VERSION}-linux-gitian.zip)
2. windows 32-bit binary, installer + source (ghostcoin-${VERSION}-win32-gitian.zip)
3. Gitian signatures (in gitian.sigs/${VERSION}[-win32]/(your gitian key)/
repackage gitian builds for release as stand-alone zip/tar/installer exe
**Linux .tar.gz:**
unzip ghostcoin-${VERSION}-linux.zip -d ghostcoin-${VERSION}-linux
tar czvf ghostcoin-${VERSION}-linux.tar.gz ghostcoin-${VERSION}-linux
rm -rf ghostcoin-${VERSION}-linux
**Windows .zip and setup.exe:**
unzip ghostcoin-${VERSION}-win32.zip -d ghostcoin-${VERSION}-win32
mv ghostcoin-${VERSION}-win32/ghostcoin-*-setup.exe .
zip -r ghostcoin-${VERSION}-win32.zip ghostcoin-${VERSION}-win32
rm -rf ghostcoin-${VERSION}-win32
**Perform Mac build:**
OSX binaries are created on a dedicated 64-bit, OSX 10.12.6 machine.
Ghostcoin 0.8.8.0 is built with MacPorts. 0.9.x will be Homebrew only.
qmake RELEASE=1 USE_UPNP=1 USE_QRCODE=1
make
export QTDIR=/opt/local/share/qt4 # needed to find translations/qt_*.qm files
T=$(contrib/qt_translations.py $QTDIR/translations src/qt/locale)
python2.7 share/qt/clean_mac_info_plist.py
python2.7 contrib/macdeploy/macdeployqtplus Ghostcoin-Qt.app -add-qt-tr $T -dmg -fancy contrib/macdeploy/fancy.plist
Build output expected: Ghostcoin-Qt.dmg
###Next steps:
* Code-sign Windows -setup.exe (in a Windows virtual machine) and
OSX Ghostcoin-Qt.app (Note: only Gavin has the code-signing keys currently)
* update ghostcoin.io version
make sure all OS download links go to the right versions
* update forum version
* update wiki download links
Commit your signature to gitian.sigs:
pushd gitian.sigs
git add ${VERSION}/${SIGNER}
git add ${VERSION}-win32/${SIGNER}
git commit -a
git push # Assuming you can push to the gitian.sigs tree
popd
| 34.837398 | 143 | 0.735356 | eng_Latn | 0.268744 |
a6cd4e60676fa14a9ac2555ca48b47f83f904869 | 528 | md | Markdown | README.md | peracine/Aurelia | 00faf54cb58bd661ee7b9409f98b84765d1afc4f | [
"MIT"
] | null | null | null | README.md | peracine/Aurelia | 00faf54cb58bd661ee7b9409f98b84765d1afc4f | [
"MIT"
] | null | null | null | README.md | peracine/Aurelia | 00faf54cb58bd661ee7b9409f98b84765d1afc4f | [
"MIT"
] | null | null | null | # Aurelia & .Net Core
## Setting up your machine with VS 2017
* .NET CLI from https://www.microsoft.com/net/core
* Node.js from https://nodejs.org
## Creating the project
-> Aurelia doesn't come as a standard template
```
dotnet new --install "Microsoft.AspNetCore.SpaTemplates::*"
dotnet new aurelia -o "Path/To/The/Project" --force
```
## Features
* Nlog (https://github.com/NLog/NLog.Web/wiki/Getting-started-with-ASP.NET-Core-2)
Bug concerning internalLogFile https://github.com/NLog/NLog.Web/issues/201
* EF Core
| 29.333333 | 83 | 0.723485 | yue_Hant | 0.677405 |
a6cd7463e20b5d5be582b1b91012ca6d0d1dae79 | 2,120 | md | Markdown | README.md | anthonyfok/golibsass | f38e05c622f04b486196b0fbfc9cf1755490328d | [
"MIT"
] | null | null | null | README.md | anthonyfok/golibsass | f38e05c622f04b486196b0fbfc9cf1755490328d | [
"MIT"
] | null | null | null | README.md | anthonyfok/golibsass | f38e05c622f04b486196b0fbfc9cf1755490328d | [
"MIT"
] | null | null | null |
[](https://travis-ci.org/bep/golibsass)
[](https://goreportcard.com/report/github.com/bep/golibsass)
[](https://github.com/sass/libsass)
[](https://codecov.io/gh/bep/golibsass)
[](https://godoc.org/github.com/bep/golibsass/libsass)
The primary motivation for this project is to provide `SCSS` support to [Hugo](https://gohugo.io/). I welcome PRs with bug fixes. I will also consider adding functionality, but please raise an issue discussing it first.
If you need more functionality than this project can provide you may want to have a look at [go-libsass](https://github.com/wellington/go-libsass).
## Usage
A basic example (error handling omitted):
```go
transpiler, _ := libsass.New(libsass.Options{OutputStyle: libsass.CompressedStyle})
result, _ := transpiler.Execute(`
$font-stack: Helvetica, sans-serif;
$primary-color: #333;
body {
font: 100% $font-stack;
color: $primary-color;
}
`)
fmt.Println(result.CSS)
// Output: body{font:100% Helvetica,sans-serif;color:#333}
```
See the [GoDoc](https://godoc.org/github.com/bep/golibsass/libsass) for more options.
## Update LibSass version
This project embeds the [LibSASS](https://github.com/sass/libsass) source code as a Git subtree. To update:
1. Pull in the relevant LibSASS version, e.g. `./pull-libsass.sh 3.6.3`
2. Regenerate wrappers with `go generate ./gen`
3. Update the LibSass version badge above.
4. Until [this issue is solved](https://github.com/sass/libsass/issues/3055), make sure to delete `libsass_src/test`.
## Local development
Compiling C++ code isn' particulary fast; if you install libsass on your PC you can link against that, useful during development.
On a Mac you may do something like:
```bash
brew install --HEAD libsass
go test ./libsass -tags dev
```
| 39.259259 | 219 | 0.74434 | eng_Latn | 0.447879 |
a6ce49337c815364760f8000adc95cc3f0c4dbf5 | 5,517 | md | Markdown | docs/database-engine/service-broker/service-broker-applications.md | jbelina/sql-docs | 79aa444cafa2af575e00ddb59c9903e9b17a1fae | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/database-engine/service-broker/service-broker-applications.md | jbelina/sql-docs | 79aa444cafa2af575e00ddb59c9903e9b17a1fae | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/database-engine/service-broker/service-broker-applications.md | jbelina/sql-docs | 79aa444cafa2af575e00ddb59c9903e9b17a1fae | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Service Broker Applications
description: "Service Broker applications are made up of one or more programs and the database objects that those programs use."
ms.prod: sql
ms.technology: configuration
ms.topic: conceptual
author: markingmyname
ms.author: maghan
ms.reviewer: mikeray
ms.date: "03/30/2022"
---
# Service Broker Applications
[!INCLUDE [sql-asdbmi](../../includes/applies-to-version/sql-asdbmi.md)]
Service Broker applications are made up of one or more programs and the database objects that those programs use. Applications communicate by creating conversations between independent components called services and then exchanging messages within those conversations. Applications use Service Broker by executing Transact-SQL statements in a SQL Server database.
## Application Components
A Service Broker application is made up of:
- One or more programs that implement a task or related set of tasks. Outside SQL Server, applications can be written in any programming environment that can run Transact-SQL statements in SQL Server. Inside SQL Server, applications can be written as stored procedures using Transact-SQL or a common language runtime (CLR) compliant language.
- A service that exposes the tasks to other services. A service is a Service Broker object that provides an addressable name for a set of related tasks. Other services start conversations with this service to perform the tasks.
- A contract and message types that define the structure and direction of the messages that are used in communications between the services.
- A queue to hold messages for the service.
- Optionally, routes and remote service bindings. Routes associate a network address with the name of a remote service. Remote service bindings associate a service name with a local database principal. Service Broker uses the certificate associated with the specified principal to handle authorization for the remote service and encryption of the messages exchanged with the remote service. Service Broker permits the routes and remote service bindings to be configured while the application is in deployment without requiring changes to the application. This allows administrators to move services and change security credentials without changes to application code. For more information on configuring routes and remote service bindings, see [Administration (Service Broker)](administration.md).
## Service Broker DML
Usually, an application sets up the service definition objects at the time of installation. While running, the application sends and receives messages by using Service Broker Data Manipulation Language (DML). The DML statements fall into three broad categories: messages, conversations, and conversation groups:
### Messages
Service Broker provides the following operations to support working with messages:
- The SEND statement sends a message on a specific conversation.
- The RECEIVE statement receives one or more messages from a queue. All messages received belong to the same conversation group.
### Conversations
Service Broker provides the following operations to support working with conversations:
- The BEGIN DIALOG CONVERSATION statement begins a conversation between two services. Because the conversation involves exactly two services, the conversation is a dialog.
- The END CONVERSATION statement ends one side of a conversation.
- The BEGIN CONVERSATION TIMER statement delivers a dialog timer message to one side of a conversation at a specific time.
- The GET_TRANSMISSION_STATUS statement returns a description of the last transmission error for a conversation. If the last attempt to transmit a message for the conversation succeeded, the statement does not return a description.
### Conversation Groups
Service Broker provides two operations for working with conversation groups:
- The GET CONVERSATION GROUP statement returns the conversation group identifier for the next receivable message in a queue. The statement also locks the conversation group.
- The MOVE CONVERSATION statement moves a conversation from one conversation group to another. The statement locks both the original conversation group and the destination conversation group.
## See also
- [BEGIN CONVERSATION TIMER (Transact-SQL)](../../t-sql/statements/begin-conversation-timer-transact-sql.md)
- [BEGIN DIALOG CONVERSATION (Transact-SQL)](../../t-sql/statements/begin-dialog-conversation-transact-sql.md)
- [MOVE CONVERSATION (Transact-SQL)](../../t-sql/statements/move-conversation-transact-sql.md)
- [GET CONVERSATION GROUP (Transact-SQL)](../../t-sql/statements/get-conversation-group-transact-sql.md)
- [SEND (Transact-SQL)](../../t-sql/statements/send-transact-sql.md)
- [END CONVERSATION (Transact-SQL)](../../t-sql/statements/end-conversation-transact-sql.md)
- [GET_TRANSMISSION_STATUS (Transact-SQL)](../../t-sql/statements/get-transmission-status-transact-sql.md)
- [RECEIVE (Transact-SQL)](../../t-sql/statements/receive-transact-sql.md)
- [BEGIN CONVERSATION TIMER (Transact-SQL)](../../t-sql/statements/begin-conversation-timer-transact-sql.md)
- [Contracts](contracts.md)
- [Dialog Conversations](dialog-conversations.md)
- [Conversation Groups](conversation-groups.md)
- [Message Types](message-types.md)
- [Messages](messages.md)
- [Queues](queues.md)
- [Services](services.md)
- [Building Applications with Service Broker](building-applications-with-service-broker.md)
- [Remote Service Bindings](remote-service-bindings.md)
- [Routes](routes.md) | 65.678571 | 797 | 0.800798 | eng_Latn | 0.971078 |
a6ce54a1ce8be5944e62efbb3274f5fa8d528bff | 3,911 | md | Markdown | desktop-src/Wua_Sdk/updating-the-windows-update-agent.md | KrupalJoshi/win32 | f5099e1e3e455bb162771d80b0ba762ee5c974ec | [
"CC-BY-4.0",
"MIT"
] | 3 | 2020-04-24T13:02:42.000Z | 2021-07-17T15:32:03.000Z | desktop-src/Wua_Sdk/updating-the-windows-update-agent.md | KrupalJoshi/win32 | f5099e1e3e455bb162771d80b0ba762ee5c974ec | [
"CC-BY-4.0",
"MIT"
] | null | null | null | desktop-src/Wua_Sdk/updating-the-windows-update-agent.md | KrupalJoshi/win32 | f5099e1e3e455bb162771d80b0ba762ee5c974ec | [
"CC-BY-4.0",
"MIT"
] | 1 | 2022-03-09T23:50:05.000Z | 2022-03-09T23:50:05.000Z | ---
Description: Windows Update Agent (WUA) automatically updates itself when it is connected to a Windows Server Update Services (WSUS) server or to Windows Update.
ms.assetid: 829112ab-b240-4cc4-8053-18b484934886
title: Updating Windows Update Agent
ms.topic: article
ms.date: 05/31/2018
---
# Updating Windows Update Agent
Windows Update Agent (WUA) updates itself through various means, depending on the version of Windows running on the device. Old versions of WUA may not be able to connect to current update services, may not be compatible with all updates, and may not support all documented APIs. Here is how to insure that WUA is fully updated and compatible.
**On versions of Windows beginning with Windows 7 and Windows Server 2008 R2**
Windows Update Agent (WUA) updates are included in the regular periodic updates to Windows distributed through Windows Update or to Windows Server Update Services (WSUS). You do not need to take any special steps to update WUA on these Windows versions.
**On versions of Windows prior to Windows 7 and Windows Server 2008 R2**
WUA automatically updates itself when Automatic Updates connects to Windows Update or to WSUS.
If Automatic Updates has not yet successfully run, it is possible that a device running these Windows versions will be running an older version of WUA that does not support all the documented APIs. If you receive a WU_E_SELFUPDATE_REQUIRED result when you use the WUA API to perform a scan, download, or install, this error tells you that the installed version of WUA is too old to connect to current Windows Update services. You cannot use the normal WUA APIs to update WUA on these operating systems.
A user can manually update WUA to a current version by opening the Windows Update control panel, selecting Check for Updates, then accepting the self-update that appears. Alternately, you can update WUA programmatically.
**To programmatically update WUA on versions of Windows prior to Windows 7 and Windows Server 2008 R2**
1. Use the [WinHTTP](https://msdn.microsoft.com/library/Aa384273(v=VS.85).aspx) APIs to download [Wuredist.cab](http://update.microsoft.com/redist/wuredist.cab).
2. Use the [Cryptography Functions](https://msdn.microsoft.com/library/Aa380252(v=VS.85).aspx) to verify that the downloaded copy of [Wuredist.cab](http://update.microsoft.com/redist/wuredist.cab) has a digital signature from Microsoft. If you can't verify the digital signature, stop.
3. Use the [File Decompression Interface](https://msdn.microsoft.com/en-us/library/Ff797921(v=VS.85).aspx) APIs to extract the XML file from [Wuredist.cab](http://update.microsoft.com/redist/wuredist.cab).
4. Use the Microsoft XML Core Services ([MSXML](https://msdn.microsoft.com/en-us/library/ms763742(v=VS.85).aspx)) APIs to load the XML file and locate the WURedist/StandaloneRedist/architecture node for the computer's architecture. For example, for x86, locate the WURedist/StandaloneRedist/architecture node with the **name** attribute of x86.
5. Call [**IWindowsUpdateAgentInfo::GetInfo**](/windows/desktop/api/Wuapi/nf-wuapi-iwindowsupdateagentinfo-getinfo) to determine the current version of WUA. If **IWindowsUpdateAgentInfo::GetInfo** returns a version number that is at least as high as the **clientVersion** attribute in the architecture node you located, stop.
6. Use the [MSXML](https://msdn.microsoft.com/en-us/library/ms763742(v=VS.85).aspx) APIs to read the **downloadUrl** attribute from the architecture node that you located. **downloadUrl** gives you the download URL for the appropriate WUA installer for the computer's architecture.
7. Use the [WinHTTP](https://msdn.microsoft.com/library/Aa384273(v=VS.85).aspx) APIs to download the appropriate installer.
8. Use the [**CreateProcess**](https://msdn.microsoft.com/library/ms682425(v=VS.85).aspx) function or a similar API to execute the downloaded installer.
| 93.119048 | 503 | 0.789824 | eng_Latn | 0.939069 |
a6ce58fb75c609b79b70d7539b4c9cd971c100ad | 120,949 | md | Markdown | common-data-model/schema/core/operationsCommon/Tables/SupplyChain/SalesAndMarketing/Parameter/smmParametersTable.md | eltociear/common-data-model-and-service | b57ad3a5b8e41699eabb5c424f3c4985d52ac9dd | [
"CC-BY-4.0",
"MIT"
] | null | null | null | common-data-model/schema/core/operationsCommon/Tables/SupplyChain/SalesAndMarketing/Parameter/smmParametersTable.md | eltociear/common-data-model-and-service | b57ad3a5b8e41699eabb5c424f3c4985d52ac9dd | [
"CC-BY-4.0",
"MIT"
] | null | null | null | common-data-model/schema/core/operationsCommon/Tables/SupplyChain/SalesAndMarketing/Parameter/smmParametersTable.md | eltociear/common-data-model-and-service | b57ad3a5b8e41699eabb5c424f3c4985d52ac9dd | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-05-28T15:59:53.000Z | 2020-05-28T15:59:53.000Z | ---
title: smmParametersTable - Common Data Model | Microsoft Docs
description: undefined
author: nenad1002
ms.service: common-data-model
ms.reviewer: deonhe
ms.topic: article
ms.date: 5/5/2020
ms.author: nebanfic
---
# Sales and marketing parameters
Latest version of the JSON entity definition is available on <a href="https://github.com/Microsoft/CDM/tree/master/schemaDocuments/core/operationsCommon/Tables/SupplyChain/SalesAndMarketing/Parameter/smmParametersTable.cdm.json" target="_blank">GitHub</a>.
## Traits
<details>
<summary>Traits for this entity are listed below.
</summary>
**is.identifiedBy**
names a specifc identity attribute to use with an entity <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>attribute</td><td>[smmParametersTable/(resolvedAttributes)/RecId](#RecId)</td><td>attribute</td><td></td></tr></table>
**is.CDM.entityVersion**
<table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>versionNumber</td><td>"1.0.0"</td><td>string</td><td>semantic version number of the entity</td></tr></table>
**is.application.releaseVersion**
<table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>releaseVersion</td><td>"10.0.13.0"</td><td>string</td><td>semantic version number of the application introducing this entity</td></tr></table>
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Sales and marketing parameters</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
</details>
## Attributes
|Name|Description|First Included in Instance|
|---|---|---|
|[RecId](#RecId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[DocuTypeIdForInEMail](#DocuTypeIdForInEMail)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[CampaignTargetActivityPhase](#CampaignTargetActivityPhase)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[CampaignTargetActivityType](#CampaignTargetActivityType)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[AgreementAccountKey_RU](#AgreementAccountKey_RU)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[AgreementClassificationKey_RU](#AgreementClassificationKey_RU)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[AgreementCurrencyKey_RU](#AgreementCurrencyKey_RU)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[AgreementDocumentTitleKey_RU](#AgreementDocumentTitleKey_RU)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[AgreementExtRefKey_RU](#AgreementExtRefKey_RU)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[AgreementYearKey_RU](#AgreementYearKey_RU)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[AutoCreateBusinessRelation](#AutoCreateBusinessRelation)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[AutoCreateCustomer](#AutoCreateCustomer)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[AutoCreateOpportunity](#AutoCreateOpportunity)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[BusRelOpenCustForm](#BusRelOpenCustForm)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[BusRelStatus](#BusRelStatus)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[BusRelTypeId](#BusRelTypeId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[CallBackCreateActivity](#CallBackCreateActivity)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[CampaignActivityCategory](#CampaignActivityCategory)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[CampaignActivityPhaseId](#CampaignActivityPhaseId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[CampaignActivityPurpose](#CampaignActivityPurpose)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[CampaignActivityTypeId](#CampaignActivityTypeId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[CampaignCreateActivity](#CampaignCreateActivity)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[CampaignGroupId](#CampaignGroupId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[CampaignNumOfDaysExpiryDate](#CampaignNumOfDaysExpiryDate)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[CampaignStatus](#CampaignStatus)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[CampaignTargetActivityCategory](#CampaignTargetActivityCategory)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[CampaignTargetActivityPurpose](#CampaignTargetActivityPurpose)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[CampaignTargetId](#CampaignTargetId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[CampaignTargetsCreateActivity](#CampaignTargetsCreateActivity)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[CampaignTypeId](#CampaignTypeId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[CreateOpportunityForProjectQuotation](#CreateOpportunityForProjectQuotation)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[CreateOpportunityForSalesQuotation](#CreateOpportunityForSalesQuotation)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[CurrencyCode](#CurrencyCode)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[CustGroup](#CustGroup)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[DefaultUserId](#DefaultUserId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[DocuAgeLimitForDisplay](#DocuAgeLimitForDisplay)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[DocuTypeIdForFiles](#DocuTypeIdForFiles)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[DocuTypeIdForOutEMail](#DocuTypeIdForOutEMail)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[EmailMemberCopyType](#EmailMemberCopyType)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[FollowupCreateActivity](#FollowupCreateActivity)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[key](#key)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[LanguageId](#LanguageId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[LogActivities](#LogActivities)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[LogBusRel](#LogBusRel)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[LogCampaignTable](#LogCampaignTable)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[LogCaseDetail](#LogCaseDetail)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[LogContactPerson](#LogContactPerson)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[LogCustTable](#LogCustTable)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[LogCustTrans](#LogCustTrans)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[LogDelete](#LogDelete)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[LogDocuRef](#LogDocuRef)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[LogInsert](#LogInsert)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[LogLeadTable](#LogLeadTable)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[LogMailings](#LogMailings)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[LogOpportunity](#LogOpportunity)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[LogQuotationTable](#LogQuotationTable)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[LogSalesTable](#LogSalesTable)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[LogTMCallListTable](#LogTMCallListTable)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[LogUpdate](#LogUpdate)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[LogVendTable](#LogVendTable)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[LogVendTrans](#LogVendTrans)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[MailingfileDirectory](#MailingfileDirectory)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[MCRCatalogReqActivityCategory](#MCRCatalogReqActivityCategory)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[MCRCatalogReqActivityCreate](#MCRCatalogReqActivityCreate)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[MCRCatalogReqActivityPhase](#MCRCatalogReqActivityPhase)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[MCRCatalogReqActivityPurpose](#MCRCatalogReqActivityPurpose)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[MCRCatalogReqActivityType](#MCRCatalogReqActivityType)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[MCRCatalogSentActivityCategory](#MCRCatalogSentActivityCategory)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[MCRCatalogSentActivityCreate](#MCRCatalogSentActivityCreate)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[MCRCatalogSentActivityPhase](#MCRCatalogSentActivityPhase)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[MCRCatalogSentActivityPurpose](#MCRCatalogSentActivityPurpose)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[MCRCatalogSentActivityType](#MCRCatalogSentActivityType)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[NumOfCampaignDaysFollowUpDate](#NumOfCampaignDaysFollowUpDate)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[OpenFromTime](#OpenFromTime)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[OpenToTime](#OpenToTime)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[PeriodFrom](#PeriodFrom)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[PeriodId](#PeriodId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[PeriodTo](#PeriodTo)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[PhoneInboundActivityType](#PhoneInboundActivityType)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[PhoneOutboundActivityType](#PhoneOutboundActivityType)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[PhoneOutboundStandardPrefix](#PhoneOutboundStandardPrefix)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[ProjGroupId](#ProjGroupId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[QuotationActivityCategory](#QuotationActivityCategory)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[QuotationActivityPhaseId](#QuotationActivityPhaseId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[QuotationActivityPurpose](#QuotationActivityPurpose)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[QuotationActivityTypeId](#QuotationActivityTypeId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[QuotationCreateActivity](#QuotationCreateActivity)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[RunBaseBatchCreateActivity](#RunBaseBatchCreateActivity)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[TelemarkeringTargetActivityPhase](#TelemarkeringTargetActivityPhase)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[TelemarketingActivityPurpose](#TelemarketingActivityPurpose)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[TelemarketingTargetActivityCategory](#TelemarketingTargetActivityCategory)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[TelemarketingTargetActivityType](#TelemarketingTargetActivityType)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[TelemarketingTargetsCreateActivity](#TelemarketingTargetsCreateActivity)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[TMCallBackActivityCategory](#TMCallBackActivityCategory)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[TMCallBackActivityPhase](#TMCallBackActivityPhase)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[TMCallBackActivityPurpose](#TMCallBackActivityPurpose)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[TMCallbackActivityType](#TMCallbackActivityType)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[TMFollowUpActivityCategory](#TMFollowUpActivityCategory)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[TMFollowUpActivityPhase](#TMFollowUpActivityPhase)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[TMFollowUpActivityPurpose](#TMFollowUpActivityPurpose)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[TMFollowUpActivityType](#TMFollowUpActivityType)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[TransLogInterval](#TransLogInterval)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[UpdateOpportunityForProjectQuotation](#UpdateOpportunityForProjectQuotation)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[UpdateOpportunityForSalesQuotation](#UpdateOpportunityForSalesQuotation)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[VendGroupId](#VendGroupId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[WebSiteURL](#WebSiteURL)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[DataAreaId](#DataAreaId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[Relationship_CurrencyRelationshipId](#Relationship_CurrencyRelationshipId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[Relationship_CustGroupRelationshipId](#Relationship_CustGroupRelationshipId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[Relationship_DocuType_FilesRelationshipId](#Relationship_DocuType_FilesRelationshipId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[Relationship_DocuType_InEMailRelationshipId](#Relationship_DocuType_InEMailRelationshipId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[Relationship_DocuType_OutEMailRelationshipId](#Relationship_DocuType_OutEMailRelationshipId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[Relationship_LanguageTableRelationshipId](#Relationship_LanguageTableRelationshipId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[Relationship_ProjGroupRelationshipId](#Relationship_ProjGroupRelationshipId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[Relationship_ProjPeriodTableRelationshipId](#Relationship_ProjPeriodTableRelationshipId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[Relationship_smmBusRelStatusGroupRelationshipId](#Relationship_smmBusRelStatusGroupRelationshipId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[Relationship_smmBusRelTypeGroupRelationshipId](#Relationship_smmBusRelTypeGroupRelationshipId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[Relationship_smmCampaignGroupRelationshipId](#Relationship_smmCampaignGroupRelationshipId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[Relationship_smmCampaignTargetTableRelationshipId](#Relationship_smmCampaignTargetTableRelationshipId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[Relationship_smmCampaignTypeGroupRelationshipId](#Relationship_smmCampaignTypeGroupRelationshipId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[Relationship_VendGroupRelationshipId](#Relationship_VendGroupRelationshipId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
|[Relationship_CompanyRelationshipId](#Relationship_CompanyRelationshipId)||<a href="smmParametersTable.md" target="_blank">Parameter/smmParametersTable</a>|
### <a href=#RecId name="RecId">RecId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>isPrimaryKey</td><td>true</td></tr><tr><td>dataFormat</td><td>int64</td></tr><tr><td>isReadOnly</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the RecId attribute are listed below.</summary>
**is.dataFormat.integer**
**is.dataFormat.big**
**is.identifiedBy**
names a specifc identity attribute to use with an entity <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>attribute</td><td>[smmParametersTable/(resolvedAttributes)/RecId](#RecId)</td><td>attribute</td><td></td></tr></table>
**is.readOnly**
**is.dataFormat.integer**
**is.dataFormat.big**
</details>
### <a href=#DocuTypeIdForInEMail name="DocuTypeIdForInEMail">DocuTypeIdForInEMail</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Document type for incoming email</td></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the DocuTypeIdForInEMail attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Document type for incoming email</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#CampaignTargetActivityPhase name="CampaignTargetActivityPhase">CampaignTargetActivityPhase</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the CampaignTargetActivityPhase attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#CampaignTargetActivityType name="CampaignTargetActivityType">CampaignTargetActivityType</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the CampaignTargetActivityType attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#AgreementAccountKey_RU name="AgreementAccountKey_RU">AgreementAccountKey_RU</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Customer account</td></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the AgreementAccountKey_RU attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Customer account</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.integer**
</details>
### <a href=#AgreementClassificationKey_RU name="AgreementClassificationKey_RU">AgreementClassificationKey_RU</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Agreement classification</td></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the AgreementClassificationKey_RU attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Agreement classification</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.integer**
</details>
### <a href=#AgreementCurrencyKey_RU name="AgreementCurrencyKey_RU">AgreementCurrencyKey_RU</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Currency</td></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the AgreementCurrencyKey_RU attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Currency</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.integer**
</details>
### <a href=#AgreementDocumentTitleKey_RU name="AgreementDocumentTitleKey_RU">AgreementDocumentTitleKey_RU</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Document title</td></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the AgreementDocumentTitleKey_RU attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Document title</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.integer**
</details>
### <a href=#AgreementExtRefKey_RU name="AgreementExtRefKey_RU">AgreementExtRefKey_RU</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>External reference</td></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the AgreementExtRefKey_RU attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>External reference</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.integer**
</details>
### <a href=#AgreementYearKey_RU name="AgreementYearKey_RU">AgreementYearKey_RU</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Year</td></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the AgreementYearKey_RU attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Year</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.integer**
</details>
### <a href=#AutoCreateBusinessRelation name="AutoCreateBusinessRelation">AutoCreateBusinessRelation</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Create a prospect</td></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the AutoCreateBusinessRelation attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Create a prospect</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.integer**
</details>
### <a href=#AutoCreateCustomer name="AutoCreateCustomer">AutoCreateCustomer</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Create customer when qualified</td></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the AutoCreateCustomer attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Create customer when qualified</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.integer**
</details>
### <a href=#AutoCreateOpportunity name="AutoCreateOpportunity">AutoCreateOpportunity</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Create opportunity when qualified</td></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the AutoCreateOpportunity attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Create opportunity when qualified</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.integer**
</details>
### <a href=#BusRelOpenCustForm name="BusRelOpenCustForm">BusRelOpenCustForm</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Open customer or vendor form on converting a prospect</td></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the BusRelOpenCustForm attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Open customer or vendor form on converting a prospect</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.integer**
</details>
### <a href=#BusRelStatus name="BusRelStatus">BusRelStatus</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the BusRelStatus attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#BusRelTypeId name="BusRelTypeId">BusRelTypeId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the BusRelTypeId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#CallBackCreateActivity name="CallBackCreateActivity">CallBackCreateActivity</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the CallBackCreateActivity attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#CampaignActivityCategory name="CampaignActivityCategory">CampaignActivityCategory</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the CampaignActivityCategory attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#CampaignActivityPhaseId name="CampaignActivityPhaseId">CampaignActivityPhaseId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the CampaignActivityPhaseId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#CampaignActivityPurpose name="CampaignActivityPurpose">CampaignActivityPurpose</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the CampaignActivityPurpose attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#CampaignActivityTypeId name="CampaignActivityTypeId">CampaignActivityTypeId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the CampaignActivityTypeId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#CampaignCreateActivity name="CampaignCreateActivity">CampaignCreateActivity</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the CampaignCreateActivity attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#CampaignGroupId name="CampaignGroupId">CampaignGroupId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the CampaignGroupId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#CampaignNumOfDaysExpiryDate name="CampaignNumOfDaysExpiryDate">CampaignNumOfDaysExpiryDate</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Days campaign expires</td></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the CampaignNumOfDaysExpiryDate attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Days campaign expires</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.integer**
</details>
### <a href=#CampaignStatus name="CampaignStatus">CampaignStatus</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the CampaignStatus attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#CampaignTargetActivityCategory name="CampaignTargetActivityCategory">CampaignTargetActivityCategory</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the CampaignTargetActivityCategory attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#CampaignTargetActivityPurpose name="CampaignTargetActivityPurpose">CampaignTargetActivityPurpose</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the CampaignTargetActivityPurpose attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#CampaignTargetId name="CampaignTargetId">CampaignTargetId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the CampaignTargetId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#CampaignTargetsCreateActivity name="CampaignTargetsCreateActivity">CampaignTargetsCreateActivity</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the CampaignTargetsCreateActivity attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#CampaignTypeId name="CampaignTypeId">CampaignTypeId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the CampaignTypeId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#CreateOpportunityForProjectQuotation name="CreateOpportunityForProjectQuotation">CreateOpportunityForProjectQuotation</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Create opportunity for project quotations</td></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the CreateOpportunityForProjectQuotation attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Create opportunity for project quotations</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.integer**
</details>
### <a href=#CreateOpportunityForSalesQuotation name="CreateOpportunityForSalesQuotation">CreateOpportunityForSalesQuotation</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Create opportunity for sales quotation</td></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the CreateOpportunityForSalesQuotation attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Create opportunity for sales quotation</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.integer**
</details>
### <a href=#CurrencyCode name="CurrencyCode">CurrencyCode</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the CurrencyCode attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#CustGroup name="CustGroup">CustGroup</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the CustGroup attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#DefaultUserId name="DefaultUserId">DefaultUserId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the DefaultUserId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#DocuAgeLimitForDisplay name="DocuAgeLimitForDisplay">DocuAgeLimitForDisplay</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the DocuAgeLimitForDisplay attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#DocuTypeIdForFiles name="DocuTypeIdForFiles">DocuTypeIdForFiles</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Document type for other documents</td></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the DocuTypeIdForFiles attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Document type for other documents</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#DocuTypeIdForOutEMail name="DocuTypeIdForOutEMail">DocuTypeIdForOutEMail</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Document type for outgoing email</td></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the DocuTypeIdForOutEMail attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Document type for outgoing email</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#EmailMemberCopyType name="EmailMemberCopyType">EmailMemberCopyType</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the EmailMemberCopyType attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#FollowupCreateActivity name="FollowupCreateActivity">FollowupCreateActivity</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the FollowupCreateActivity attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#key name="key">key</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isReadOnly</td><td>true</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the key attribute are listed below.</summary>
**is.dataFormat.integer**
**is.readOnly**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#LanguageId name="LanguageId">LanguageId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the LanguageId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#LogActivities name="LogActivities">LogActivities</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the LogActivities attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#LogBusRel name="LogBusRel">LogBusRel</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the LogBusRel attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#LogCampaignTable name="LogCampaignTable">LogCampaignTable</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the LogCampaignTable attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#LogCaseDetail name="LogCaseDetail">LogCaseDetail</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the LogCaseDetail attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#LogContactPerson name="LogContactPerson">LogContactPerson</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the LogContactPerson attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#LogCustTable name="LogCustTable">LogCustTable</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the LogCustTable attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#LogCustTrans name="LogCustTrans">LogCustTrans</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the LogCustTrans attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#LogDelete name="LogDelete">LogDelete</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the LogDelete attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#LogDocuRef name="LogDocuRef">LogDocuRef</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the LogDocuRef attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#LogInsert name="LogInsert">LogInsert</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the LogInsert attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#LogLeadTable name="LogLeadTable">LogLeadTable</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the LogLeadTable attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#LogMailings name="LogMailings">LogMailings</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the LogMailings attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#LogOpportunity name="LogOpportunity">LogOpportunity</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the LogOpportunity attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#LogQuotationTable name="LogQuotationTable">LogQuotationTable</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the LogQuotationTable attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#LogSalesTable name="LogSalesTable">LogSalesTable</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the LogSalesTable attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#LogTMCallListTable name="LogTMCallListTable">LogTMCallListTable</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the LogTMCallListTable attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#LogUpdate name="LogUpdate">LogUpdate</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the LogUpdate attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#LogVendTable name="LogVendTable">LogVendTable</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the LogVendTable attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#LogVendTrans name="LogVendTrans">LogVendTrans</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the LogVendTrans attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#MailingfileDirectory name="MailingfileDirectory">MailingfileDirectory</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Mailing file directory</td></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the MailingfileDirectory attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Mailing file directory</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#MCRCatalogReqActivityCategory name="MCRCatalogReqActivityCategory">MCRCatalogReqActivityCategory</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Catalog requested category</td></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the MCRCatalogReqActivityCategory attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Catalog requested category</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.integer**
</details>
### <a href=#MCRCatalogReqActivityCreate name="MCRCatalogReqActivityCreate">MCRCatalogReqActivityCreate</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Create activity for catalog is requested</td></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the MCRCatalogReqActivityCreate attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Create activity for catalog is requested</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.integer**
</details>
### <a href=#MCRCatalogReqActivityPhase name="MCRCatalogReqActivityPhase">MCRCatalogReqActivityPhase</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Catalog request activity phase</td></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the MCRCatalogReqActivityPhase attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Catalog request activity phase</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#MCRCatalogReqActivityPurpose name="MCRCatalogReqActivityPurpose">MCRCatalogReqActivityPurpose</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Catalog request activity purpose</td></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the MCRCatalogReqActivityPurpose attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Catalog request activity purpose</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#MCRCatalogReqActivityType name="MCRCatalogReqActivityType">MCRCatalogReqActivityType</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Catalog request activity type</td></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the MCRCatalogReqActivityType attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Catalog request activity type</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#MCRCatalogSentActivityCategory name="MCRCatalogSentActivityCategory">MCRCatalogSentActivityCategory</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Catalog sent category</td></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the MCRCatalogSentActivityCategory attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Catalog sent category</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.integer**
</details>
### <a href=#MCRCatalogSentActivityCreate name="MCRCatalogSentActivityCreate">MCRCatalogSentActivityCreate</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Create activity for catalog is sent</td></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the MCRCatalogSentActivityCreate attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Create activity for catalog is sent</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.integer**
</details>
### <a href=#MCRCatalogSentActivityPhase name="MCRCatalogSentActivityPhase">MCRCatalogSentActivityPhase</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Catalog sent activity phase</td></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the MCRCatalogSentActivityPhase attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Catalog sent activity phase</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#MCRCatalogSentActivityPurpose name="MCRCatalogSentActivityPurpose">MCRCatalogSentActivityPurpose</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Catalog sent activity purpose</td></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the MCRCatalogSentActivityPurpose attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Catalog sent activity purpose</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#MCRCatalogSentActivityType name="MCRCatalogSentActivityType">MCRCatalogSentActivityType</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Catalog sent activity type</td></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the MCRCatalogSentActivityType attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Catalog sent activity type</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#NumOfCampaignDaysFollowUpDate name="NumOfCampaignDaysFollowUpDate">NumOfCampaignDaysFollowUpDate</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Days before follow-up</td></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the NumOfCampaignDaysFollowUpDate attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Days before follow-up</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.integer**
</details>
### <a href=#OpenFromTime name="OpenFromTime">OpenFromTime</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>time</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the OpenFromTime attribute are listed below.</summary>
**is.dataFormat.time**
**means.measurement.time**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.time**
</details>
### <a href=#OpenToTime name="OpenToTime">OpenToTime</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>time</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the OpenToTime attribute are listed below.</summary>
**is.dataFormat.time**
**means.measurement.time**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.time**
</details>
### <a href=#PeriodFrom name="PeriodFrom">PeriodFrom</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>date</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the PeriodFrom attribute are listed below.</summary>
**is.dataFormat.date**
**means.measurement.date**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.date**
</details>
### <a href=#PeriodId name="PeriodId">PeriodId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the PeriodId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#PeriodTo name="PeriodTo">PeriodTo</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>date</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the PeriodTo attribute are listed below.</summary>
**is.dataFormat.date**
**means.measurement.date**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.date**
</details>
### <a href=#PhoneInboundActivityType name="PhoneInboundActivityType">PhoneInboundActivityType</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Activity type for inbound calls</td></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the PhoneInboundActivityType attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Activity type for inbound calls</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#PhoneOutboundActivityType name="PhoneOutboundActivityType">PhoneOutboundActivityType</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Activity type for outbound calls</td></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the PhoneOutboundActivityType attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Activity type for outbound calls</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#PhoneOutboundStandardPrefix name="PhoneOutboundStandardPrefix">PhoneOutboundStandardPrefix</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the PhoneOutboundStandardPrefix attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#ProjGroupId name="ProjGroupId">ProjGroupId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the ProjGroupId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#QuotationActivityCategory name="QuotationActivityCategory">QuotationActivityCategory</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the QuotationActivityCategory attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#QuotationActivityPhaseId name="QuotationActivityPhaseId">QuotationActivityPhaseId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the QuotationActivityPhaseId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#QuotationActivityPurpose name="QuotationActivityPurpose">QuotationActivityPurpose</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the QuotationActivityPurpose attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#QuotationActivityTypeId name="QuotationActivityTypeId">QuotationActivityTypeId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the QuotationActivityTypeId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#QuotationCreateActivity name="QuotationCreateActivity">QuotationCreateActivity</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the QuotationCreateActivity attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#RunBaseBatchCreateActivity name="RunBaseBatchCreateActivity">RunBaseBatchCreateActivity</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the RunBaseBatchCreateActivity attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#TelemarkeringTargetActivityPhase name="TelemarkeringTargetActivityPhase">TelemarkeringTargetActivityPhase</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the TelemarkeringTargetActivityPhase attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#TelemarketingActivityPurpose name="TelemarketingActivityPurpose">TelemarketingActivityPurpose</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the TelemarketingActivityPurpose attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#TelemarketingTargetActivityCategory name="TelemarketingTargetActivityCategory">TelemarketingTargetActivityCategory</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the TelemarketingTargetActivityCategory attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#TelemarketingTargetActivityType name="TelemarketingTargetActivityType">TelemarketingTargetActivityType</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the TelemarketingTargetActivityType attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#TelemarketingTargetsCreateActivity name="TelemarketingTargetsCreateActivity">TelemarketingTargetsCreateActivity</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the TelemarketingTargetsCreateActivity attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#TMCallBackActivityCategory name="TMCallBackActivityCategory">TMCallBackActivityCategory</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the TMCallBackActivityCategory attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#TMCallBackActivityPhase name="TMCallBackActivityPhase">TMCallBackActivityPhase</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the TMCallBackActivityPhase attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#TMCallBackActivityPurpose name="TMCallBackActivityPurpose">TMCallBackActivityPurpose</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the TMCallBackActivityPurpose attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#TMCallbackActivityType name="TMCallbackActivityType">TMCallbackActivityType</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the TMCallbackActivityType attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#TMFollowUpActivityCategory name="TMFollowUpActivityCategory">TMFollowUpActivityCategory</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the TMFollowUpActivityCategory attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#TMFollowUpActivityPhase name="TMFollowUpActivityPhase">TMFollowUpActivityPhase</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the TMFollowUpActivityPhase attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#TMFollowUpActivityPurpose name="TMFollowUpActivityPurpose">TMFollowUpActivityPurpose</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the TMFollowUpActivityPurpose attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#TMFollowUpActivityType name="TMFollowUpActivityType">TMFollowUpActivityType</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the TMFollowUpActivityType attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#TransLogInterval name="TransLogInterval">TransLogInterval</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the TransLogInterval attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.integer**
</details>
### <a href=#UpdateOpportunityForProjectQuotation name="UpdateOpportunityForProjectQuotation">UpdateOpportunityForProjectQuotation</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Update opportunity when project quotation status changes</td></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the UpdateOpportunityForProjectQuotation attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Update opportunity when project quotation status changes</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.integer**
</details>
### <a href=#UpdateOpportunityForSalesQuotation name="UpdateOpportunityForSalesQuotation">UpdateOpportunityForSalesQuotation</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>displayName</td><td>Update opportunity when sales quotation status changes</td></tr><tr><td>dataFormat</td><td>int32</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the UpdateOpportunityForSalesQuotation attribute are listed below.</summary>
**is.dataFormat.integer**
**is.nullable**
The attribute value may be set to NULL.
**is.localized.displayedAs**
Holds the list of language specific display text for an object. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>localizedDisplayText</td><td><table><tr><th>languageTag</th><th>displayText</th></tr><tr><td>en</td><td>Update opportunity when sales quotation status changes</td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of localized text</td></tr></table>
**is.dataFormat.integer**
</details>
### <a href=#VendGroupId name="VendGroupId">VendGroupId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the VendGroupId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#WebSiteURL name="WebSiteURL">WebSiteURL</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isNullable</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the WebSiteURL attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.nullable**
The attribute value may be set to NULL.
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#DataAreaId name="DataAreaId">DataAreaId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>string</td></tr><tr><td>isReadOnly</td><td>true</td></tr></table>
#### Traits
<details>
<summary>List of traits for the DataAreaId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.readOnly**
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#Relationship_CurrencyRelationshipId name="Relationship_CurrencyRelationshipId">Relationship_CurrencyRelationshipId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>guid</td></tr></table>
#### Traits
<details>
<summary>List of traits for the Relationship_CurrencyRelationshipId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.dataFormat.guid**
**means.identity.entityId**
**is.linkedEntity.identifier**
Marks the attribute(s) that hold foreign key references to a linked (used as an attribute) entity. This attribute is added to the resolved entity to enumerate the referenced entities. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>entityReferences</td><td><table><tr><th>entityReference</th><th>attributeReference</th></tr><tr><td><a href="../../../Common/Currency/Group/Currency.md" target="_blank">/core/operationsCommon/Tables/Common/Currency/Group/Currency.cdm.json/Currency</a></td><td><a href="../../../Common/Currency/Group/Currency.md#RecId" target="_blank">RecId</a></td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of entity references</td></tr></table>
**is.dataFormat.guid**
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#Relationship_CustGroupRelationshipId name="Relationship_CustGroupRelationshipId">Relationship_CustGroupRelationshipId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>guid</td></tr></table>
#### Traits
<details>
<summary>List of traits for the Relationship_CustGroupRelationshipId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.dataFormat.guid**
**means.identity.entityId**
**is.linkedEntity.identifier**
Marks the attribute(s) that hold foreign key references to a linked (used as an attribute) entity. This attribute is added to the resolved entity to enumerate the referenced entities. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>entityReferences</td><td><table><tr><th>entityReference</th><th>attributeReference</th></tr><tr><td><a href="../../../Finance/AccountsReceivable/Group/CustGroup.md" target="_blank">/core/operationsCommon/Tables/Finance/AccountsReceivable/Group/CustGroup.cdm.json/CustGroup</a></td><td><a href="../../../Finance/AccountsReceivable/Group/CustGroup.md#RecId" target="_blank">RecId</a></td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of entity references</td></tr></table>
**is.dataFormat.guid**
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#Relationship_DocuType_FilesRelationshipId name="Relationship_DocuType_FilesRelationshipId">Relationship_DocuType_FilesRelationshipId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>guid</td></tr></table>
#### Traits
<details>
<summary>List of traits for the Relationship_DocuType_FilesRelationshipId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.dataFormat.guid**
**means.identity.entityId**
**is.linkedEntity.identifier**
Marks the attribute(s) that hold foreign key references to a linked (used as an attribute) entity. This attribute is added to the resolved entity to enumerate the referenced entities. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>entityReferences</td><td><table><tr><th>entityReference</th><th>attributeReference</th></tr><tr><td><a href="../../../System/SystemAdministration/Group/DocuType.md" target="_blank">/core/operationsCommon/Tables/System/SystemAdministration/Group/DocuType.cdm.json/DocuType</a></td><td><a href="../../../System/SystemAdministration/Group/DocuType.md#RecId" target="_blank">RecId</a></td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of entity references</td></tr></table>
**is.dataFormat.guid**
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#Relationship_DocuType_InEMailRelationshipId name="Relationship_DocuType_InEMailRelationshipId">Relationship_DocuType_InEMailRelationshipId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>guid</td></tr></table>
#### Traits
<details>
<summary>List of traits for the Relationship_DocuType_InEMailRelationshipId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.dataFormat.guid**
**means.identity.entityId**
**is.linkedEntity.identifier**
Marks the attribute(s) that hold foreign key references to a linked (used as an attribute) entity. This attribute is added to the resolved entity to enumerate the referenced entities. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>entityReferences</td><td><table><tr><th>entityReference</th><th>attributeReference</th></tr><tr><td><a href="../../../System/SystemAdministration/Group/DocuType.md" target="_blank">/core/operationsCommon/Tables/System/SystemAdministration/Group/DocuType.cdm.json/DocuType</a></td><td><a href="../../../System/SystemAdministration/Group/DocuType.md#RecId" target="_blank">RecId</a></td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of entity references</td></tr></table>
**is.dataFormat.guid**
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#Relationship_DocuType_OutEMailRelationshipId name="Relationship_DocuType_OutEMailRelationshipId">Relationship_DocuType_OutEMailRelationshipId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>guid</td></tr></table>
#### Traits
<details>
<summary>List of traits for the Relationship_DocuType_OutEMailRelationshipId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.dataFormat.guid**
**means.identity.entityId**
**is.linkedEntity.identifier**
Marks the attribute(s) that hold foreign key references to a linked (used as an attribute) entity. This attribute is added to the resolved entity to enumerate the referenced entities. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>entityReferences</td><td><table><tr><th>entityReference</th><th>attributeReference</th></tr><tr><td><a href="../../../System/SystemAdministration/Group/DocuType.md" target="_blank">/core/operationsCommon/Tables/System/SystemAdministration/Group/DocuType.cdm.json/DocuType</a></td><td><a href="../../../System/SystemAdministration/Group/DocuType.md#RecId" target="_blank">RecId</a></td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of entity references</td></tr></table>
**is.dataFormat.guid**
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#Relationship_LanguageTableRelationshipId name="Relationship_LanguageTableRelationshipId">Relationship_LanguageTableRelationshipId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>guid</td></tr></table>
#### Traits
<details>
<summary>List of traits for the Relationship_LanguageTableRelationshipId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.dataFormat.guid**
**means.identity.entityId**
**is.linkedEntity.identifier**
Marks the attribute(s) that hold foreign key references to a linked (used as an attribute) entity. This attribute is added to the resolved entity to enumerate the referenced entities. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>entityReferences</td><td><table><tr><th>entityReference</th><th>attributeReference</th></tr><tr><td><a href="../../../System/SystemAdministration/Group/LanguageTable.md" target="_blank">/core/operationsCommon/Tables/System/SystemAdministration/Group/LanguageTable.cdm.json/LanguageTable</a></td><td><a href="../../../System/SystemAdministration/Group/LanguageTable.md#RecId" target="_blank">RecId</a></td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of entity references</td></tr></table>
**is.dataFormat.guid**
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#Relationship_ProjGroupRelationshipId name="Relationship_ProjGroupRelationshipId">Relationship_ProjGroupRelationshipId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>guid</td></tr></table>
#### Traits
<details>
<summary>List of traits for the Relationship_ProjGroupRelationshipId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.dataFormat.guid**
**means.identity.entityId**
**is.linkedEntity.identifier**
Marks the attribute(s) that hold foreign key references to a linked (used as an attribute) entity. This attribute is added to the resolved entity to enumerate the referenced entities. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>entityReferences</td><td><table><tr><th>entityReference</th><th>attributeReference</th></tr><tr><td><a href="../../../ProfessionalServices/ProjectManagementAndAccounting/Group/ProjGroup.md" target="_blank">/core/operationsCommon/Tables/ProfessionalServices/ProjectManagementAndAccounting/Group/ProjGroup.cdm.json/ProjGroup</a></td><td><a href="../../../ProfessionalServices/ProjectManagementAndAccounting/Group/ProjGroup.md#RecId" target="_blank">RecId</a></td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of entity references</td></tr></table>
**is.dataFormat.guid**
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#Relationship_ProjPeriodTableRelationshipId name="Relationship_ProjPeriodTableRelationshipId">Relationship_ProjPeriodTableRelationshipId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>guid</td></tr></table>
#### Traits
<details>
<summary>List of traits for the Relationship_ProjPeriodTableRelationshipId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.dataFormat.guid**
**means.identity.entityId**
**is.linkedEntity.identifier**
Marks the attribute(s) that hold foreign key references to a linked (used as an attribute) entity. This attribute is added to the resolved entity to enumerate the referenced entities. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>entityReferences</td><td><table><tr><th>entityReference</th><th>attributeReference</th></tr><tr><td><a href="../../../ProfessionalServices/ProjectManagementAndAccounting/Group/ProjPeriodTable.md" target="_blank">/core/operationsCommon/Tables/ProfessionalServices/ProjectManagementAndAccounting/Group/ProjPeriodTable.cdm.json/ProjPeriodTable</a></td><td><a href="../../../ProfessionalServices/ProjectManagementAndAccounting/Group/ProjPeriodTable.md#RecId" target="_blank">RecId</a></td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of entity references</td></tr></table>
**is.dataFormat.guid**
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#Relationship_smmBusRelStatusGroupRelationshipId name="Relationship_smmBusRelStatusGroupRelationshipId">Relationship_smmBusRelStatusGroupRelationshipId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>guid</td></tr></table>
#### Traits
<details>
<summary>List of traits for the Relationship_smmBusRelStatusGroupRelationshipId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.dataFormat.guid**
**means.identity.entityId**
**is.linkedEntity.identifier**
Marks the attribute(s) that hold foreign key references to a linked (used as an attribute) entity. This attribute is added to the resolved entity to enumerate the referenced entities. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>entityReferences</td><td><table><tr><th>entityReference</th><th>attributeReference</th></tr><tr><td><a href="../Group/smmBusRelStatusGroup.md" target="_blank">/core/operationsCommon/Tables/SupplyChain/SalesAndMarketing/Group/smmBusRelStatusGroup.cdm.json/smmBusRelStatusGroup</a></td><td><a href="../Group/smmBusRelStatusGroup.md#RecId" target="_blank">RecId</a></td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of entity references</td></tr></table>
**is.dataFormat.guid**
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#Relationship_smmBusRelTypeGroupRelationshipId name="Relationship_smmBusRelTypeGroupRelationshipId">Relationship_smmBusRelTypeGroupRelationshipId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>guid</td></tr></table>
#### Traits
<details>
<summary>List of traits for the Relationship_smmBusRelTypeGroupRelationshipId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.dataFormat.guid**
**means.identity.entityId**
**is.linkedEntity.identifier**
Marks the attribute(s) that hold foreign key references to a linked (used as an attribute) entity. This attribute is added to the resolved entity to enumerate the referenced entities. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>entityReferences</td><td><table><tr><th>entityReference</th><th>attributeReference</th></tr><tr><td><a href="../Group/smmBusRelTypeGroup.md" target="_blank">/core/operationsCommon/Tables/SupplyChain/SalesAndMarketing/Group/smmBusRelTypeGroup.cdm.json/smmBusRelTypeGroup</a></td><td><a href="../Group/smmBusRelTypeGroup.md#RecId" target="_blank">RecId</a></td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of entity references</td></tr></table>
**is.dataFormat.guid**
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#Relationship_smmCampaignGroupRelationshipId name="Relationship_smmCampaignGroupRelationshipId">Relationship_smmCampaignGroupRelationshipId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>guid</td></tr></table>
#### Traits
<details>
<summary>List of traits for the Relationship_smmCampaignGroupRelationshipId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.dataFormat.guid**
**means.identity.entityId**
**is.linkedEntity.identifier**
Marks the attribute(s) that hold foreign key references to a linked (used as an attribute) entity. This attribute is added to the resolved entity to enumerate the referenced entities. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>entityReferences</td><td><table><tr><th>entityReference</th><th>attributeReference</th></tr><tr><td><a href="../Group/smmCampaignGroup.md" target="_blank">/core/operationsCommon/Tables/SupplyChain/SalesAndMarketing/Group/smmCampaignGroup.cdm.json/smmCampaignGroup</a></td><td><a href="../Group/smmCampaignGroup.md#RecId" target="_blank">RecId</a></td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of entity references</td></tr></table>
**is.dataFormat.guid**
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#Relationship_smmCampaignTargetTableRelationshipId name="Relationship_smmCampaignTargetTableRelationshipId">Relationship_smmCampaignTargetTableRelationshipId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>guid</td></tr></table>
#### Traits
<details>
<summary>List of traits for the Relationship_smmCampaignTargetTableRelationshipId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.dataFormat.guid**
**means.identity.entityId**
**is.linkedEntity.identifier**
Marks the attribute(s) that hold foreign key references to a linked (used as an attribute) entity. This attribute is added to the resolved entity to enumerate the referenced entities. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>entityReferences</td><td><table><tr><th>entityReference</th><th>attributeReference</th></tr><tr><td><a href="../Group/smmCampaignTargetTable.md" target="_blank">/core/operationsCommon/Tables/SupplyChain/SalesAndMarketing/Group/smmCampaignTargetTable.cdm.json/smmCampaignTargetTable</a></td><td><a href="../Group/smmCampaignTargetTable.md#RecId" target="_blank">RecId</a></td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of entity references</td></tr></table>
**is.dataFormat.guid**
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#Relationship_smmCampaignTypeGroupRelationshipId name="Relationship_smmCampaignTypeGroupRelationshipId">Relationship_smmCampaignTypeGroupRelationshipId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>guid</td></tr></table>
#### Traits
<details>
<summary>List of traits for the Relationship_smmCampaignTypeGroupRelationshipId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.dataFormat.guid**
**means.identity.entityId**
**is.linkedEntity.identifier**
Marks the attribute(s) that hold foreign key references to a linked (used as an attribute) entity. This attribute is added to the resolved entity to enumerate the referenced entities. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>entityReferences</td><td><table><tr><th>entityReference</th><th>attributeReference</th></tr><tr><td><a href="../Group/smmCampaignTypeGroup.md" target="_blank">/core/operationsCommon/Tables/SupplyChain/SalesAndMarketing/Group/smmCampaignTypeGroup.cdm.json/smmCampaignTypeGroup</a></td><td><a href="../Group/smmCampaignTypeGroup.md#RecId" target="_blank">RecId</a></td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of entity references</td></tr></table>
**is.dataFormat.guid**
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#Relationship_VendGroupRelationshipId name="Relationship_VendGroupRelationshipId">Relationship_VendGroupRelationshipId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>guid</td></tr></table>
#### Traits
<details>
<summary>List of traits for the Relationship_VendGroupRelationshipId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.dataFormat.guid**
**means.identity.entityId**
**is.linkedEntity.identifier**
Marks the attribute(s) that hold foreign key references to a linked (used as an attribute) entity. This attribute is added to the resolved entity to enumerate the referenced entities. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>entityReferences</td><td><table><tr><th>entityReference</th><th>attributeReference</th></tr><tr><td><a href="../../Vendor/Group/VendGroup.md" target="_blank">/core/operationsCommon/Tables/SupplyChain/Vendor/Group/VendGroup.cdm.json/VendGroup</a></td><td><a href="../../Vendor/Group/VendGroup.md#RecId" target="_blank">RecId</a></td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of entity references</td></tr></table>
**is.dataFormat.guid**
**is.dataFormat.character**
**is.dataFormat.array**
</details>
### <a href=#Relationship_CompanyRelationshipId name="Relationship_CompanyRelationshipId">Relationship_CompanyRelationshipId</a>
First included in: Parameter/smmParametersTable (this entity)
#### Properties
<table><tr><th>Name</th><th>Value</th></tr><tr><td>dataFormat</td><td>guid</td></tr></table>
#### Traits
<details>
<summary>List of traits for the Relationship_CompanyRelationshipId attribute are listed below.</summary>
**is.dataFormat.character**
**is.dataFormat.big**
**is.dataFormat.array**
**is.dataFormat.guid**
**means.identity.entityId**
**is.linkedEntity.identifier**
Marks the attribute(s) that hold foreign key references to a linked (used as an attribute) entity. This attribute is added to the resolved entity to enumerate the referenced entities. <table><tr><th>Parameter</th><th>Value</th><th>Data type</th><th>Explanation</th></tr><tr><td>entityReferences</td><td><table><tr><th>entityReference</th><th>attributeReference</th></tr><tr><td><a href="../../../Finance/Ledger/Main/CompanyInfo.md" target="_blank">/core/operationsCommon/Tables/Finance/Ledger/Main/CompanyInfo.cdm.json/CompanyInfo</a></td><td><a href="../../../Finance/Ledger/Main/CompanyInfo.md#RecId" target="_blank">RecId</a></td></tr></table></td><td>entity</td><td>a reference to the constant entity holding the list of entity references</td></tr></table>
**is.dataFormat.guid**
**is.dataFormat.character**
**is.dataFormat.array**
</details>
| 41.279522 | 891 | 0.730713 | yue_Hant | 0.364378 |
a6ced5d040524904eb4bbdeeadce72a9633552a0 | 42,661 | md | Markdown | docs/xamarin-forms/app-fundamentals/localization/text.md | tallichet/xamarin-docs | 933de144d1fbe7d412e49b743839cae4bfcac439 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/xamarin-forms/app-fundamentals/localization/text.md | tallichet/xamarin-docs | 933de144d1fbe7d412e49b743839cae4bfcac439 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/xamarin-forms/app-fundamentals/localization/text.md | tallichet/xamarin-docs | 933de144d1fbe7d412e49b743839cae4bfcac439 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "String and Image Localization"
description: "Xamarin.Forms apps can be localized using .NET resources files."
ms.prod: xamarin
ms.assetid: 852B4ED3-2D2D-48A5-A759-A6591F6A1509
ms.technology: xamarin-forms
author: davidbritch
ms.author: dabritch
ms.date: 09/06/2016
---
# Localization
[ Download the sample](https://docs.microsoft.com/samples/xamarin/xamarin-forms-samples/usingresxlocalization)
_Xamarin.Forms apps can be localized using .NET resources files._
## Overview
The built-in mechanism for localizing .NET applications uses [RESX files](https://msdn.microsoft.com/library/ekyft91f(v=vs.90).aspx) and the classes in the `System.Resources` and `System.Globalization` namespaces. The RESX files containing translated strings are embedded in the Xamarin.Forms assembly, along with a compiler-generated class that provides strongly-typed access to the translations. The translated text can then be retrieved in code.
### Sample Code
There are two samples associated with this document:
- [UsingResxLocalization](https://github.com/xamarin/xamarin-forms-samples/tree/master/UsingResxLocalization) is a very simple demonstration of the concepts explained. The code snippets shown below are all from this sample.
- [TodoLocalized](https://github.com/xamarin/xamarin-forms-samples/tree/master/TodoLocalized) is a basic working app that uses these localization techniques.
#### Shared Projects are not recommended
The TodoLocalized sample includes a [Shared Project demo](https://github.com/xamarin/xamarin-forms-samples/tree/master/TodoLocalized/SharedProject/) however due to limitations of the build system the resource files do not get a **.designer.cs** file generated which breaks the ability to access translated strings strongly-typed in code.
The remainder of this document relates to projects using the Xamarin.Forms .NET Standard library template.
## Globalizing Xamarin.Forms Code
**Globalizing** an application is the process of making it "world ready." This means writing code that is capable of displaying different languages.
One of the key parts of globalizing an application is building the user-interface so that there is no *hard-coded* text. Instead, anything displayed to the user should be retrieved from a set of strings that have been translated into their chosen language.
In this document we'll examine how to use RESX files to store those strings and retrieve them for display depending on the user's preference.
The samples target English, French, Spanish, German, Chinese, Japanese, Russian, and Brazilian Portuguese languages. Applications can be translated into as few or as many languages as required.
> [!NOTE]
> On the Universal Windows Platform, RESW files should be used for push notification localization, rather than RESX files. For more information, see [UWP Localization](/windows/uwp/design/globalizing/globalizing-portal/).
### Adding Resources
The first step in globalizing a Xamarin.Forms .NET Standard library application is adding the RESX resource files that will be used to store all the text used in the app. We need to add a RESX file that contains the default text, and then add additional RESX files for each language we wish to support.
#### Base Language Resource
The base resources (RESX) file will contain the default language strings (the samples assume English is the default language). Add the file to the Xamarin.Forms common code project by right-clicking on the project and choosing **Add > New File...**.
Choose a meaningful name such as **AppResources** and press **OK**.
[](text-images/resx-new-file.png#lightbox "New File Dialog")
Two files will be added to the project:
- **AppResources.resx** file where translatable strings are stored in an XML format.
- **AppResources.designer.cs** file that declares a partial class to contain references to all the elements created in the RESX XML file.
The solution tree will show the files as related. The RESX file *should* be edited to add new translatable strings; the **.designer.cs** file should *not* be edited.
##### String Visibility
By default when strongly-typed references to strings are generated, they will be
`internal` to the assembly. This is because the default build tool for RESX files
generates the **.designer.cs** file with `internal` properties.
Select the **AppResources.resx** file and show the
**Properties** pad to see where this build tool is configure. The screenshot below
shows the **Custom Tool: ResXFileCodeGenerator**.
# [Visual Studio](#tab/windows)
[](text-images/vs-resx-internal.png#lightbox)
# [Visual Studio for Mac](#tab/macos)
[](text-images/xs-resx-internal.png#lightbox)
-----
To make the strongly-typed string properties `public`, you must manually
change the configuration to **Custom Tool: PublicResXFileCodeGenerator**,
as shown in the screenshot below:
# [Visual Studio](#tab/windows)
[](text-images/vs-resx-public.png#lightbox)
# [Visual Studio for Mac](#tab/macos)
[](text-images/xs-resx-internal.png#lightbox)
[](text-images/xs-resx-public.png#lightbox)
-----
This change is optional, and is only required if you wish to reference
localized strings across different assemblies (for example, if you put the RESX
files in a different assembly to your code). The sample for this topic
leaves the strings `internal` because they are defined in the same Xamarin.Forms
.NET Standard library assembly where they are used.
You only need to set the custom tool on the base RESX file as shown above;
you do not need to set *any* build tool on the language-specific RESX files
discussed in the following sections.
##### Editing the RESX file
Unfortunately there is no built-in RESX editor in Visual Studio for Mac. Adding new translatable strings requires the addition of a new XML `data` element for each string. Each `data` element can contain the following:
- `name` attribute (required) is the key for this translatable string. It must be a valid C# property name - so no spaces or special characters are allowed.
- `value` element (required), which is the actual string that is displayed in the application.
- `comment` element (optional) can contain instructions for the translator that explains how this string is used.
- `xml:space` attribute (optional) to control how spacing in the string is preserved.
Some example `data` elements are shown here:
```xml
<data name="NotesLabel" xml:space="preserve">
<value>Notes:</value>
<comment>label for input field</comment>
</data>
<data name="NotesPlaceholder" xml:space="preserve">
<value>eg. buy milk</value>
<comment>example input for notes field</comment>
</data>
<data name="AddButton" xml:space="preserve">
<value>Add new item</value>
</data>
```
As the application is written, every piece of text displayed to the user should be
added to the base RESX resources file in a new `data` element. It is recommended
that you include `comment`s as much as possible to ensure a high-quality translation.
> [!NOTE]
> Visual Studio (including the free Community edition) contains a
> basic RESX editor. If you have access to a Windows computer, that can be a convenient
> way to add and edit strings in RESX files.
#### Language-Specific Resources
Typically, the actual translation of the default text strings won't happen until
large chunks of the application have been written (in which case the default RESX
file will contain lots of strings). It is still a good idea to add the
language-specific resources early in the development cycle, optionally populating
with machine-translated text to help test the localization code.
One additional RESX file is added for each language we wish to support.
Language-specific resource files must follow a specific naming convention:
use the same filename as the base resources file (eg. **AppResources**)
followed by a period (.) and then the language code. Simple examples include:
- **AppResources.fr.resx** - French language translations.
- **AppResources.es.resx** - Spanish language translations.
- **AppResources.de.resx** - German language translations.
- **AppResources.ja.resx** - Japanese language translations.
- **AppResources.zh-Hans.resx** - Chinese (Simplified) language translations.
- **AppResources.zh-Hant.resx** - Chinese (Traditional) language translations.
- **AppResources.pt.resx** - Portuguese language translations.
- **AppResources.pt-BR.resx** - Brazilian Portuguese language translations.
The general pattern is to use two-letter language codes, but there are some examples
(such as Chinese) where a different format is used, and other examples (such as
Brazilian Portuguese) where a four character locale identifier is required.
These language-specific resources files *do not* require a **.designer.cs** partial
class so they can be added as regular XML files, with the **Build Action: EmbeddedResource**
set. This screenshot shows a solution containing language-specific resource files:
As an application is developed and the base RESX file has text added, you should send it out to translators who will translate each `data` element and return a language-specific resource file (using the naming convention shown) to be included in the app. Some 'machine translated' examples are shown below:
**AppResources.es.resx (Spanish)**
```xml
<data name="AddButton" xml:space="preserve">
<value>Escribir un artículo</value>
<comment>this string appears on a button to add a new item to the list</comment>
</data>
```
**AppResources.ja.resx (Japanese)**
```xml
<data name="AddButton" xml:space="preserve">
<value>新しい項目を追加</value>
<comment>this string appears on a button to add a new item to the list</comment>
</data>
```
**AppResources.pt-BR.resx (Brazilian Portuguese)**
```xml
<data name="AddButton" xml:space="preserve">
<value>adicionar novo item</value>
<comment>this string appears on a button to add a new item to the list</comment>
</data>
```
Only the `value` element needs to be updated by the translator - the `comment` is not intended to be translated. Remember: when editing XML files to escape reserved characters like `<`, `>`, `&` with `<`, `>`, and `&` if they appear in the `value` or `comment`.
<a name="incode" />
### Using Resources in Code
Strings in the RESX resource files will be available to use in your user interface code using the `AppResources` class. The `name` assigned to each string in the RESX file becomes a property on that class which can be referenced in Xamarin.Forms code as shown below:
```csharp
var myLabel = new Label ();
var myEntry = new Entry ();
var myButton = new Button ();
// populate UI with translated text values from resources
myLabel.Text = AppResources.NotesLabel;
myEntry.Placeholder = AppResources.NotesPlaceholder;
myButton.Text = AppResources.AddButton;
```
The user interface on iOS, Android, and the Universal Windows Platform (UWP) renders as you'd expect, except now it's possible to translate the app into multiple languages because the text is being loaded from a resource rather than being hard-coded. Here is a screenshot showing the UI on each platform prior to translation:
### Troubleshooting
#### Testing a Specific Language
It can be tricky to switch the simulator or a device to different languages,
particularly during development when you want to test different cultures quickly.
You can force a specific language to be loaded by setting the `Culture` as shown
in this code snippet:
```csharp
// force a specific culture, useful for quick testing
AppResources.Culture = new CultureInfo("fr-FR");
```
This approach – setting the culture directly on the `AppResources` class –
can also be used to implement a language-selector inside your app (rather than
using the device's locale).
#### Loading Embedded Resources
The following code snippet is useful when trying to debug issues with embedded
resources (such as RESX files). Add this code to your app (early in the app lifecycle)
and it will list all the resources embedded in the assembly, showing the full resource identifier:
```csharp
using System.Reflection;
// ...
// NOTE: use for debugging, not in released app code!
var assembly = typeof(EmbeddedImages).GetTypeInfo().Assembly; // "EmbeddedImages" should be a class in your app
foreach (var res in assembly.GetManifestResourceNames())
{
System.Diagnostics.Debug.WriteLine("found resource: " + res);
}
```
In the **AppResources.Designer.cs** file (around *line 33*), the full
*resource manager name* is specified (eg. `"UsingResxLocalization.Resx.AppResources"`)
similar to the code below:
```csharp
System.Resources.ResourceManager temp =
new System.Resources.ResourceManager(
"UsingResxLocalization.Resx.AppResources",
typeof(AppResources).GetTypeInfo().Assembly);
```
Check the **Application Output** for the results of the debug code shown above,
to confirm the correct resources are listed (ie. `"UsingResxLocalization.Resx.AppResources"`).
If not, the `AppResources` class will be unable to load its resources.
Check the following to resolve issues where the resources cannot be found:
- The default namespace for the project matches the root namespace in the **AppResources.Designer.cs** file.
- If the **AppResources.resx** file is located in a subdirectory, the subdirectory name should be part of the namespace *and* part of the resource identifier.
- The **AppResources.resx** file has **Build Action: EmbeddedResource**.
- The **Project Options > Source Code > .NET Naming Policies > Use Visual Studio-style resources names** is ticked. You can untick this if you prefer, however the namespaces used when referencing your RESX resources will need to updated throughout the app.
#### Doesn't work in DEBUG mode (Android only)
If the translated strings are working in your RELEASE Android builds but not while debugging,
right-click on the **Android Project** and select **Options > Build > Android Build** and
ensure that the **Fast assembly deployment** is NOT ticked. This option causes problems
with loading resources and should not be used if you are testing localized apps.
### Displaying the Correct Language
So far we've examined how to write code so that translations can be provided, but not how to actually make them appear. Xamarin.Forms code can take advantage of .NET's resources to load the correct language translations, but we need to query the operating system on each platform to determine which language the user has selected.
Because some platform-specific code is required to obtain the user's language preference, use a [dependency service](~/xamarin-forms/app-fundamentals/dependency-service/index.md) to expose that information in the Xamarin.Forms app and implement it for each platform.
First, define an interface to expose the user's preferred culture, similar to the code below:
```csharp
public interface ILocalize
{
CultureInfo GetCurrentCultureInfo ();
void SetLocale (CultureInfo ci);
}
```
Second, use the [DependencyService](~/xamarin-forms/app-fundamentals/dependency-service/index.md) in the Xamarin.Forms `App` class to call the interface and set our RESX resources culture to the correct value. Notice that we don't need to manually set this value for the Universal Windows Platform, since the resources framework automatically recognizes the selected language on those platforms.
```csharp
if (Device.RuntimePlatform == Device.iOS || Device.RuntimePlatform == Device.Android)
{
var ci = DependencyService.Get<ILocalize>().GetCurrentCultureInfo();
Resx.AppResources.Culture = ci; // set the RESX for resource localization
DependencyService.Get<ILocalize>().SetLocale(ci); // set the Thread for locale-aware methods
}
```
The resource `Culture` needs to be set when the application first loads so that
the correct language strings are used. You may optionally update this value
according to platform-specific events that may be raised on iOS or Android if
the user updates their language preferences while the app is running.
The implementations for the `ILocalize` interface are shown in the
[Platform-specific Code](#Platform-specific_Code) section below. These implementations
take advantage of this `PlatformCulture` helper class:
```csharp
public class PlatformCulture
{
public PlatformCulture (string platformCultureString)
{
if (String.IsNullOrEmpty(platformCultureString))
{
throw new ArgumentException("Expected culture identifier", "platformCultureString"); // in C# 6 use nameof(platformCultureString)
}
PlatformString = platformCultureString.Replace("_", "-"); // .NET expects dash, not underscore
var dashIndex = PlatformString.IndexOf("-", StringComparison.Ordinal);
if (dashIndex > 0)
{
var parts = PlatformString.Split('-');
LanguageCode = parts[0];
LocaleCode = parts[1];
}
else
{
LanguageCode = PlatformString;
LocaleCode = "";
}
}
public string PlatformString { get; private set; }
public string LanguageCode { get; private set; }
public string LocaleCode { get; private set; }
public override string ToString()
{
return PlatformString;
}
}
```
<a name="Platform-specific_Code" />
### Platform-Specific Code
The code to detect which language to display must be platform-specific because
iOS, Android, and UWP all expose this information in slightly
different ways. The code for the `ILocalize` dependency service is provided below
for each platform, along with additional platform-specific requirements to ensure
localized text is rendered correctly.
The platform-specific code must also handle cases where the operating system
allows the user to configure a locale identifier that is not supported by
.NET's `CultureInfo` class. In these cases custom code must be written
to detect unsupported locales and substitute the best .NET-compatible locale.
#### iOS Application Project
iOS users select their preferred language separately from date and time formatting
culture. To load the correct resources to localize a Xamarin.Forms app we just
need to query the `NSLocale.PreferredLanguages` array for the first element.
The following implementation of the `ILocalize` dependency service should be
placed in the iOS application project. Because iOS uses underscores instead of
dashes (which is the .NET standard representation) the code replaces the
underscore before instantiating the `CultureInfo` class:
```csharp
[assembly:Dependency(typeof(UsingResxLocalization.iOS.Localize))]
namespace UsingResxLocalization.iOS
{
public class Localize : UsingResxLocalization.ILocalize
{
public void SetLocale (CultureInfo ci)
{
Thread.CurrentThread.CurrentCulture = ci;
Thread.CurrentThread.CurrentUICulture = ci;
}
public CultureInfo GetCurrentCultureInfo ()
{
var netLanguage = "en";
if (NSLocale.PreferredLanguages.Length > 0)
{
var pref = NSLocale.PreferredLanguages [0];
netLanguage = iOSToDotnetLanguage(pref);
}
// this gets called a lot - try/catch can be expensive so consider caching or something
System.Globalization.CultureInfo ci = null;
try
{
ci = new System.Globalization.CultureInfo(netLanguage);
}
catch (CultureNotFoundException e1)
{
// iOS locale not valid .NET culture (eg. "en-ES" : English in Spain)
// fallback to first characters, in this case "en"
try
{
var fallback = ToDotnetFallbackLanguage(new PlatformCulture(netLanguage));
ci = new System.Globalization.CultureInfo(fallback);
}
catch (CultureNotFoundException e2)
{
// iOS language not valid .NET culture, falling back to English
ci = new System.Globalization.CultureInfo("en");
}
}
return ci;
}
string iOSToDotnetLanguage(string iOSLanguage)
{
// .NET cultures don't support underscores
string netLanguage = iOSLanguage.Replace("_", "-");
//certain languages need to be converted to CultureInfo equivalent
switch (iOSLanguage)
{
case "ms-MY": // "Malaysian (Malaysia)" not supported .NET culture
case "ms-SG": // "Malaysian (Singapore)" not supported .NET culture
netLanguage = "ms"; // closest supported
break;
case "gsw-CH": // "Schwiizertüütsch (Swiss German)" not supported .NET culture
netLanguage = "de-CH"; // closest supported
break;
// add more application-specific cases here (if required)
// ONLY use cultures that have been tested and known to work
}
return netLanguage;
}
string ToDotnetFallbackLanguage (PlatformCulture platCulture)
{
var netLanguage = platCulture.LanguageCode; // use the first part of the identifier (two chars, usually);
switch (platCulture.LanguageCode)
{
case "pt":
netLanguage = "pt-PT"; // fallback to Portuguese (Portugal)
break;
case "gsw":
netLanguage = "de-CH"; // equivalent to German (Switzerland) for this app
break;
// add more application-specific cases here (if required)
// ONLY use cultures that have been tested and known to work
}
return netLanguage;
}
}
}
```
> [!NOTE]
> The `try/catch` blocks in the `GetCurrentCultureInfo` method
> mimic the fallback behavior typically used with locale specifiers – if the
> exact match is not found, look for a close match based just on the language (first
> block of characters in the locale).
>
> In the case of Xamarin.Forms, some locales are valid in iOS but do not correspond
> to a valid `CultureInfo` in .NET, and the code above attempts to handle this.
>
> For example, the iOS **Settings > General Language & Region** screen
> allows you to set your phone **Language** to **English** but the **Region**
> to **Spain**, which results in a locale string of `"en-ES"`. When
> the `CultureInfo` creation fails, the code falls back to using just
> the first two letters to select the display language.
>
> Developers should modify the `iOSToDotnetLanguage` and `ToDotnetFallbackLanguage`
> methods to handle specific cases required for their supported languages.
There are some system-defined user-interface elements that are automatically
translated by iOS, such as the **Done** button on the `Picker` control. To
force iOS to translate these elements we need to indicate which languages we
support in the **Info.plist** file. You can add these values via
**Info.plist > Source** as shown here:
Alternatively, open the **Info.plist** file in an XML editor and edit the values directly:
```xml
<key>CFBundleLocalizations</key>
<array>
<string>de</string>
<string>es</string>
<string>fr</string>
<string>ja</string>
<string>pt</string> <!-- Brazil -->
<string>pt-PT</string> <!-- Portugal -->
<string>ru</string>
<string>zh-Hans</string>
<string>zh-Hant</string>
</array>
<key>CFBundleDevelopmentRegion</key>
<string>en</string>
```
Once you've implemented the dependency service and updated **Info.plist**, the iOS app will be able to display localized text.
> [!NOTE]
> Note that Apple treats Portuguese slightly differently than you'd expect.
> From [their docs](https://developer.apple.com/library/ios/documentation/MacOSX/Conceptual/BPInternational/LocalizingYourApp/LocalizingYourApp.html#//apple_ref/doc/uid/10000171i-CH5-SW2): _"use pt as the language ID for Portuguese as it is used in Brazil and pt-PT as the language ID for Portuguese as it is used in Portugal"_.
> This means when Portuguese language is chosen in a non-standard locale, the fallback
> language will be Brazilian Portuguese on iOS, unless code is written to change
> this behavior (such as the `ToDotnetFallbackLanguage` above).
For more information about iOS Localization, see [iOS Localization](~/ios/app-fundamentals/localization/index.md).
#### Android Application Project
Android exposes the currently selected locale via `Java.Util.Locale.Default`,
and also uses an underscore separator instead of a dash (which is replaced by
the following code). Add this dependency service implementation to the Android application project:
```csharp
[assembly:Dependency(typeof(UsingResxLocalization.Android.Localize))]
namespace UsingResxLocalization.Android
{
public class Localize : UsingResxLocalization.ILocalize
{
public void SetLocale(CultureInfo ci)
{
Thread.CurrentThread.CurrentCulture = ci;
Thread.CurrentThread.CurrentUICulture = ci;
}
public CultureInfo GetCurrentCultureInfo()
{
var netLanguage = "en";
var androidLocale = Java.Util.Locale.Default;
netLanguage = AndroidToDotnetLanguage(androidLocale.ToString().Replace("_", "-"));
// this gets called a lot - try/catch can be expensive so consider caching or something
System.Globalization.CultureInfo ci = null;
try
{
ci = new System.Globalization.CultureInfo(netLanguage);
}
catch (CultureNotFoundException e1)
{
// iOS locale not valid .NET culture (eg. "en-ES" : English in Spain)
// fallback to first characters, in this case "en"
try
{
var fallback = ToDotnetFallbackLanguage(new PlatformCulture(netLanguage));
ci = new System.Globalization.CultureInfo(fallback);
}
catch (CultureNotFoundException e2)
{
// iOS language not valid .NET culture, falling back to English
ci = new System.Globalization.CultureInfo("en");
}
}
return ci;
}
string AndroidToDotnetLanguage(string androidLanguage)
{
var netLanguage = androidLanguage;
//certain languages need to be converted to CultureInfo equivalent
switch (androidLanguage)
{
case "ms-BN": // "Malaysian (Brunei)" not supported .NET culture
case "ms-MY": // "Malaysian (Malaysia)" not supported .NET culture
case "ms-SG": // "Malaysian (Singapore)" not supported .NET culture
netLanguage = "ms"; // closest supported
break;
case "in-ID": // "Indonesian (Indonesia)" has different code in .NET
netLanguage = "id-ID"; // correct code for .NET
break;
case "gsw-CH": // "Schwiizertüütsch (Swiss German)" not supported .NET culture
netLanguage = "de-CH"; // closest supported
break;
// add more application-specific cases here (if required)
// ONLY use cultures that have been tested and known to work
}
return netLanguage;
}
string ToDotnetFallbackLanguage(PlatformCulture platCulture)
{
var netLanguage = platCulture.LanguageCode; // use the first part of the identifier (two chars, usually);
switch (platCulture.LanguageCode)
{
case "gsw":
netLanguage = "de-CH"; // equivalent to German (Switzerland) for this app
break;
// add more application-specific cases here (if required)
// ONLY use cultures that have been tested and known to work
}
return netLanguage;
}
}
}
```
> [!NOTE]
> The `try/catch` blocks in the `GetCurrentCultureInfo` method
> mimic the fallback behavior typically used with locale specifiers – if the
> exact match is not found, look for a close match based just on the language (first
> block of characters in the locale).
>
> In the case of Xamarin.Forms, some locales are valid in Android but do not correspond
> to a valid `CultureInfo` in .NET, and the code above attempts to handle this.
>
> Developers should modify the `iOSToDotnetLanguage` and `ToDotnetFallbackLanguage`
> methods to handle specific cases required for their supported languages.
Once this code has been added to the Android application project, it will be able
to automatically display translated strings.
> [!WARNING]
> If the translated strings are working in your
> RELEASE Android builds but not while debugging, right-click on the **Android Project**
> and select **Options > Build > Android Build** and ensure that the
> **Fast assembly deployment** is NOT ticked. This option causes problems
> with loading resources and should not be used if you are testing localized apps.
For more information about Android localization, see [Android Localization](~/android/app-fundamentals/localization.md).
#### Universal Windows Platform
Universal Windows Platform (UWP) projects do not require the dependency service. Instead, this platform automatically sets the resource's culture correctly.
##### AssemblyInfo.cs
Expand the Properties node in the .NET Standard library project and double-click on the **AssemblyInfo.cs** file. Add the following line to the file to set the neutral resources assembly language to English:
```csharp
[assembly: NeutralResourcesLanguage("en")]
```
This informs the resource manager of the app's default culture, therefore ensuring that the strings defined in the language neutral RESX file (**AppResources.resx**) will be displayed when the app is running in one the English locales.
### Example
After updating the platform-specific projects as shown above and recompiling the app with translated RESX files, updated translations will be available in each app. Here is a screenshot from the sample code translated into Simplified Chinese:
For more information about UWP localization, see [UWP Localization](/windows/uwp/design/globalizing/globalizing-portal/).
## Localizing XAML
When building a Xamarin.Forms user interface in XAML the markup would look similar to this, with strings embedded directly in the XML:
```xaml
<Label Text="Notes:" />
<Entry Placeholder="eg. buy milk" />
<Button Text="Add to list" />
```
Ideally, we could translate user interface controls directly in the XAML, which we can do by creating a *markup extension*. The code for a markup extension that exposes the RESX resources to XAML is shown below. This class should be added to the Xamarin.Forms common code (along with the XAML pages):
```csharp
using System;
using System.Globalization;
using System.Reflection;
using System.Resources;
using Xamarin.Forms;
using Xamarin.Forms.Xaml;
namespace UsingResxLocalization
{
// You exclude the 'Extension' suffix when using in XAML
[ContentProperty("Text")]
public class TranslateExtension : IMarkupExtension
{
readonly CultureInfo ci = null;
const string ResourceId = "UsingResxLocalization.Resx.AppResources";
static readonly Lazy<ResourceManager> ResMgr = new Lazy<ResourceManager>(
() => new ResourceManager(ResourceId, IntrospectionExtensions.GetTypeInfo(typeof(TranslateExtension)).Assembly));
public string Text { get; set; }
public TranslateExtension()
{
if (Device.RuntimePlatform == Device.iOS || Device.RuntimePlatform == Device.Android)
{
ci = DependencyService.Get<ILocalize>().GetCurrentCultureInfo();
}
}
public object ProvideValue(IServiceProvider serviceProvider)
{
if (Text == null)
return string.Empty;
var translation = ResMgr.Value.GetString(Text, ci);
if (translation == null)
{
#if DEBUG
throw new ArgumentException(
string.Format("Key '{0}' was not found in resources '{1}' for culture '{2}'.", Text, ResourceId, ci.Name),
"Text");
#else
translation = Text; // HACK: returns the key, which GETS DISPLAYED TO THE USER
#endif
}
return translation;
}
}
}
```
The following bullets explain the important elements in the code above:
- The class is named `TranslateExtension`, but by convention we can refer to is as **Translate** in our markup.
- The class implements `IMarkupExtension`, which is required by Xamarin.Forms for it to work.
- `"UsingResxLocalization.Resx.AppResources"` is the resource identifier for our RESX resources. It is comprised of our default namespace, the folder where the resource files are located and the default RESX filename.
- The `ResourceManager` class is created using `IntrospectionExtensions.GetTypeInfo(typeof(TranslateExtension)).Assembly)` to determine the current assembly to load resources from, and cached in the static `ResMgr` field. It's created as a `Lazy` type so that its creation is deferred until it's first used in the `ProvideValue` method.
- `ci` uses the dependency service to get the user's chosen language from the native operating system.
- `GetString` is the method that retrieves the actual translated string from the resources files. On the Universal Windows Platform, `ci` will be null because the `ILocalize` interface isn't implemented on those platforms. This is equivalent to calling the `GetString` method with only the first parameter. Instead, the resources framework will automatically recognize the locale and will retrieve the translated string from the appropriate RESX file.
- Error handling has been included to help debug missing resources by throwing an exception (in `DEBUG` mode only).
The following XAML snippet shows how to use the markup extension. There are two steps to make it work:
1. Declare the custom `xmlns:i18n` namespace in the root node. The `namespace` and `assembly` must match the project settings exactly - in this example they are identical but could be different in your project.
2. Use `{Binding}` syntax on attributes that would normally contain text to call the `Translate` markup extension. The resource key is the only required parameter.
```xaml
<?xml version="1.0" encoding="UTF-8"?>
<ContentPage xmlns="http://xamarin.com/schemas/2014/forms"
xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
x:Class="UsingResxLocalization.FirstPageXaml"
xmlns:i18n="clr-namespace:UsingResxLocalization;assembly=UsingResxLocalization">
<StackLayout Padding="0, 20, 0, 0">
<Label Text="{i18n:Translate NotesLabel}" />
<Entry Placeholder="{i18n:Translate NotesPlaceholder}" />
<Button Text="{i18n:Translate AddButton}" />
</StackLayout>
</ContentPage>
```
The following more verbose syntax is also valid for the markup extension:
```xaml
<Button Text="{i18n:TranslateExtension Text=AddButton}" />
```
## Localizing Platform-Specific Elements
Although we can handle the translation of the user interface in Xamarin.Forms code, there are some elements that must be done in each platform-specific project. This section will cover how to localize:
- Application Name
- Images
The sample project includes a localized image called **flag.png**, which is referenced in C# as follows:
```csharp
var flag = new Image();
switch (Device.RuntimePlatform)
{
case Device.iOS:
case Device.Android:
flag.Source = ImageSource.FromFile("flag.png");
break;
case Device.UWP:
flag.Source = ImageSource.FromFile("Assets/Images/flag.png");
break;
}
```
The flag image is also referenced in the XAML like this:
```xaml
<Image>
<Image.Source>
<OnPlatform x:TypeArguments="ImageSource">
<On Platform="iOS, Android" Value="flag.png" />
<On Platform="UWP" Value="Assets/Images/flag.png" />
</OnPlatform>
</Image.Source>
</Image>
```
All platforms will automatically resolve image references like these to localized versions of the images, as long as the project structures explained below are implemented.
### iOS Application Project
iOS uses a naming standard called Localization Projects or **.lproj** directories to contain image and string resources. These directories can contain localized versions of images used in the app, and also the **InfoPlist.strings** file that can be used to localize the app name. For more information about iOS Localization, see [iOS Localization](~/ios/app-fundamentals/localization/index.md).
#### Images
This screenshot shows the iOS sample app with language-specific **.lproj** directories. The Spanish directory called **es.lproj**, contains localized versions of the default image, as well as **flag.png**:
Each language directory contains a copy of **flag.png**, localized for that language. If no image is supplied, the operating system will default to the image in the default language directory. For full Retina support, you should supply **@2x** and **@3x** copies of each image.
#### App Name
The contents of the **InfoPlist.strings** is just a single key-value to configure the app name:
```csharp
"CFBundleDisplayName" = "ResxEspañol";
```
When the application is run, the app name and the image are both localized:
### Android Application Project
Android follows a different scheme for storing localized images using different **drawable** and **strings** directories with a language code suffix. When a four-letter locale code is required (such as zh-TW or pt-BR), note that Android requires an additional **r** following the dash/preceding the locale code (eg. zh-rTW or pt-rBR). For more information about Android localization, see [Android Localization](~/android/app-fundamentals/localization.md).
#### Images
This screenshot shows the Android sample with a some localized drawables and strings:
Note that Android does not use zh-Hans and zh-Hant codes for Simplified and Traditional Chinese; instead, it only supports country-specific codes zh-CN and zh-TW.
To support different resolution images for high-density screens, create additional language folders with `-*dpi` suffixes, such as **drawables-es-mdpi**, **drawables-es-xdpi**, **drawables-es-xxdpi**, etc. See [Providing Alternative Android Resources](https://developer.android.com/guide/topics/resources/providing-resources.html#AlternativeResources) for more information.
#### App Name
The contents of the **strings.xml** is just a single key-value to configure the app name:
```xml
<?xml version="1.0" encoding="utf-8"?>
<resources>
<string name="app_name">ResxEspañol</string>
</resources>
```
Update the **MainActivity.cs** in the Android app project so that the `Label` references the strings XML.
```csharp
[Activity (Label = "@string/app_name", MainLauncher = true,
ConfigurationChanges = ConfigChanges.ScreenSize | ConfigChanges.Orientation)]
```
The app now localizes the app name and image. Here's a screenshot of the result (in Spanish):
### Universal Windows Platform Application Projects
The Universal Windows Platform possesses a resource infrastructure that simplifies the localization of images and the app name. For more information about UWP localization, see [UWP Localization](/windows/uwp/design/globalizing/globalizing-portal/).
#### Images
Images can be localized by placing them in a resource-specific folder, as demonstrated in the following screenshot:
At runtime the Windows resource infrastructure will select the appropriate image based on the user's locale.
## Summary
Xamarin.Forms applications can be localized using RESX files and .NET globalization classes. Apart from a small amount of platform-specific code to detect what language the user prefers, most of the localization effort is centralized in the common code.
Images are generally handled in a platform-specific way to take advantage of the multi-resolution support provided in both iOS and Android.
## Related Links
- [RESX Localization Sample](https://docs.microsoft.com/samples/xamarin/xamarin-forms-samples/usingresxlocalization)
- [TodoLocalized Sample App](https://docs.microsoft.com/samples/xamarin/xamarin-forms-samples/todolocalized)
- [Cross-Platform Localization](~/cross-platform/app-fundamentals/localization.md)
- [iOS Localization](~/ios/app-fundamentals/localization/index.md)
- [Android Localization](~/android/app-fundamentals/localization.md)
- [UWP Localization](/windows/uwp/design/globalizing/globalizing-portal/)
- [Using the CultureInfo class (MSDN)](https://msdn.microsoft.com/library/87k6sx8t%28v=vs.90%29.aspx)
- [Locating and Using Resources for a Specific Culture (MSDN)](https://msdn.microsoft.com/library/s9ckwb4b%28v=vs.90%29.aspx)
| 47.772676 | 455 | 0.725745 | eng_Latn | 0.980235 |
a6cef6f59421705d8633fa0f8b187691d7330dfe | 1,361 | md | Markdown | en/common/zek.md | reinhart1010/nix | a1803c718ead3b79854b65396c8967bd5ec32874 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | en/common/zek.md | reinhart1010/nix | a1803c718ead3b79854b65396c8967bd5ec32874 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | en/common/zek.md | reinhart1010/nix | a1803c718ead3b79854b65396c8967bd5ec32874 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
layout: page
title: common/zek (English)
description: "Generate a Go struct from XML."
content_hash: fe33b649babe387720d991217df6c0c5f9e55e4f
---
This entry is very new in the [tldr-pages](https://github.com/tldr-pages/tldr) project, hence translation data is currently unavailable for a while.
<hr># zek
Generate a Go struct from XML.
More information: <https://github.com/miku/zek>.
- Generate a Go struct from a given XML from stdin and display output on stdout:
`cat `<span class="tldr-var badge badge-pill bg-dark-lm bg-white-dm text-white-lm text-dark-dm font-weight-bold">path/to/input.xml</span>` | zek`
- Generate a Go struct from a given XML from stdin and send output to a file:
`curl -s `<span class="tldr-var badge badge-pill bg-dark-lm bg-white-dm text-white-lm text-dark-dm font-weight-bold">https://url/to/xml</span>` | zek -o `<span class="tldr-var badge badge-pill bg-dark-lm bg-white-dm text-white-lm text-dark-dm font-weight-bold">path/to/output.go</span>
- Generate an example Go program from a given XML from stdin and send output to a file:
`cat `<span class="tldr-var badge badge-pill bg-dark-lm bg-white-dm text-white-lm text-dark-dm font-weight-bold">path/to/input.xml</span>` | zek -p -o `<span class="tldr-var badge badge-pill bg-dark-lm bg-white-dm text-white-lm text-dark-dm font-weight-bold">path/to/output.go</span>
| 52.346154 | 285 | 0.743571 | eng_Latn | 0.746709 |
a6cf8c34725372072960022da9029686aed05176 | 8,426 | md | Markdown | _posts/Technology/Container/2015-09-22-docker_image.md | xiaoguangdong999/xiaoguangdong999.github.io | 4e1c4b46dc7aa3ca90ee18107f9c625b658321cc | [
"MIT"
] | null | null | null | _posts/Technology/Container/2015-09-22-docker_image.md | xiaoguangdong999/xiaoguangdong999.github.io | 4e1c4b46dc7aa3ca90ee18107f9c625b658321cc | [
"MIT"
] | null | null | null | _posts/Technology/Container/2015-09-22-docker_image.md | xiaoguangdong999/xiaoguangdong999.github.io | 4e1c4b46dc7aa3ca90ee18107f9c625b658321cc | [
"MIT"
] | null | null | null | ---
layout: post
title: 关于docker image的那点事儿
category: 技术
tags: Container
keywords: Docker image Dockerfile
---
## 简介
* TOC
{:toc}
2013 年，Docker 出现了，工程师可以第一次到软件生产环境中定义，通过 Docker image 完成**单机**软件的交付和分发。
[自下而上学习容器](https://mp.weixin.qq.com/s/1jpgYUU6J1W1brihJRnzKQ)对于熟悉 runc 是如何启动容器的人来说，他们都知道镜像并非是必需的。那我们为什么还要有容器镜像？当每一个容器都包含根文件系统的一个数兆字节那么大的拷贝副本时，所需的磁盘空间就会急剧增加。因此，镜像的存在是为了有效地解决存储和发行问题。
[如何在golang代码里面解析容器镜像](https://mp.weixin.qq.com/s/viq9wJiHBH6AsLYLCtLpRA)
## 打包所有依赖
代码分发：在物理机时代， springboot项目普遍都带了一个run.sh文件，不论项目本身的特点如何，开发和运维约定`run.sh start/stop`来启停应用
1. 这说明只有一个jar是运行不起来的
2. 如果我们不是一个java系为主的公司，这么做够么？
到后面，你就发现，run.sh 里可能什么都有，包括依赖库（比如转码程序会安装ffmpeg）、下载文件等，run.sh做到极致：一个应用一个操作系统环境（依赖库、env等），但整个文件岂不是很大？**Docker最大的贡献就是提出了分层镜像的概念**。
想起了大学宿舍时候的装系统：
1. 当说镜像的时候第一反应是啥？一键ghost ==> 装系统 ==> 装qq ==> 自动启动项目 ==> 装系统顺带装app
2. App最完整的依赖的OS ==> 为了启动app干脆配上一个系统 ==> 裸操作系统 + docker即可运行任何项目。
进一步延伸到集群概念 [集群镜像：实现高效的分布式应用交付](https://mp.weixin.qq.com/s/0SBslzaMWtqn9H8Q57urNA)
## 镜像与操作系统的关系
[并非每个容器内部都能包含一个操作系统](https://mp.weixin.qq.com/s/ALTxkwAXBdKdQLMYJIMrLw)docker镜像不仅能够打包应用，还能打包整个操作系统的文件和目录，记住是操作系统的文件和目录。通过这种方式docker就把一个应用所有的依赖库包括操作系统中的文件和目录都被打包到镜像中。docker正是通过打包操作系统级别的方式，解决了开发到线上环境的一致性。宿主机操作系统只有一个内核，也就是说，所有的容器都依赖这一个内核了？比如我现在有一个需求，我的两个容器运行在同一台宿主机上，但是依赖的内核版本不一样，或者需要配置的内核参数不一样，怎么解决呢？**解决不了**，这也是容器化技术相比于虚拟机的主要缺陷之一。
内核，操作系统和发行版之间的区别：
1. Linux内核是Linux操作系统的核心部分。这就是Linus最初写的。
2. Linux操作系统是内核和用户域（库，GNU实用程序，配置文件等）的组合。
3. Linux发行版是Linux操作系统的特定版本，例如Debian，CentOS或Alpine。
其实linux操作系统中代码包含两部分，一部分是文件目录和配置，另外一部分是内核，这两部分是分开存放的，**内核模块只有在宿主机开机启动时才会加载**。说白了，即使镜像中包含了内核也不会被加载。说到最后，原来镜像只是包含了操作系统的躯干（文件系统），并没有包含操作系统的灵魂（内核）。
**容器中的根文件系统**，其实就是我们做的镜像。
## 本地存储
[Where are Docker images stored?](http://blog.thoward37.me/articles/where-are-docker-images-stored/)
`docker inspect xx` GraphDriver 的部分输出
```
"GraphDriver": {
"Data": {
"LowerDir": "/var/lib/docker/overlay2/cad72d6e952bbffb754bf3a13af0c401ae1ab743ef4ed0b9994e57ef127c3d29-init/diff:/var/lib/docker/overlay2/6a190d31ec303cc0a4163c2698a38ce449d660265bbab709503a2ac4dde4aa7f/diff:/var/lib/docker/overlay2/05c46a2829a0b37e856434489ef2684c507276697cc325f98225d1d15c84a9bb/diff:/var/lib/docker/overlay2/77aa0717d4e28977139c25a52afb04de25b8bb478670b24f3c8b409b1f1b9495/diff",
"MergedDir": "/var/lib/docker/overlay2/cad72d6e952bbffb754bf3a13af0c401ae1ab743ef4ed0b9994e57ef127c3d29/merged",
"UpperDir": "/var/lib/docker/overlay2/cad72d6e952bbffb754bf3a13af0c401ae1ab743ef4ed0b9994e57ef127c3d29/diff",
"WorkDir": "/var/lib/docker/overlay2/cad72d6e952bbffb754bf3a13af0c401ae1ab743ef4ed0b9994e57ef127c3d29/work"
},
"Name": "overlay2"
},
```
1. lower， 这一层里的文件是不会被修改的，你可以认为它是只读的。
2. uppder， 在 OverlayFS 中，如果有文件的创建，修改，删除操作，那么都会在这一层反映出来，它是可读写的。
3. merged，挂载点（mount point）目录，也是用户看到的目录，用户的实际文件操作在这里进行。
4. work，只是一个存放临时文件的目录，OverlayFS 中如果有文件修改，就会在中间过程中临时存放文件到这里。
镜像要复用，所以只能只读。但程序的运行会写文件，所以要可写。OverlayFS/UnionFS 解决这个折中的问题。
runC这类容器低层运行时不包含镜像管理，它假定容器的文件包已经从镜像里解压出来并存放于文件系统中。containerd是最常用的 容器高层运行时，提供镜像下载、解压等功能，但不包含镜像构建、上传等功能， 再往上，Docker 提供了许多 UX 增强功能。——镜像并不是运行容器所必须的。
有时候某个容器疯狂的写文件，大量占用磁盘，可以根据这些 overlay 目录找到所属的 容器id
```sh
# 检索正在运行的容器
docker ps -q | xargs docker inspect --format '{{.State.Pid}}, {{.Id}}, {{.Name}}, {{.GraphDriver.Data.WorkDir}}'|grep b941fe7f18c19285614a27857af1c811b4e117551d54f04b44c8ce5b6b585ad8
# 检索所有的容器
docker ps -a |awk '{print $1}'|grep -v CONTAINER | xargs docker inspect --format '{{.State.Pid}}, {{.Id}}, {{.Name}}, {{.GraphDriver.Data.WorkDir}}'|grep 96cafbea806cfe0ccc98
```
## 制作镜像
```sh
cid=$(docker run -v /foo/bar debian:jessie)
image_id=$(docker commit $cid)
cid=$(docker run $image_id touch /foo/bar/baz)
docker commit $(cid) my_debian
```
image的build过程，粗略的说，就是以容器执行命令（`docker run`）和提交更改（`docker commit`）的过程
开发者可以使用一些工具(如Dockerfile)构建出自己的容器镜像、**签名**并上传到互联网上（分发内容一定会有签名， 更进一步签名还可以作为内容寻址），然后需要运行这些软件的人可以通过指定名称（如_example.com/my-app_）下载、验证和运行这些容器。
### build 时使用http代理
2019.4.3 补充
```
docker build --build-arg HTTPS_PROXY='http://userName:password@proxyAddress:port' \
--build-arg HTTP_PROXY='http://userName:password@proxyAddress:port' \
-t $IMAGE_NAGE .
```
当你在公司负责维护docker 镜像时，不同镜像的Dockerfile 为了支持协作及版本跟踪 一般会保存在git 库中。制作镜像 通常需要安装类似jdk/tomcat 等可执行文件，这些文件建议使用远程下载的方式（因为git 保存二进制文件 不太优雅），以安装tomcat 为例
```
RUN \
DIR=/tmp/tomcat && mkdir -p ${DIR} && cd ${DIR} && \
curl -sLO http://mirrors.tuna.tsinghua.edu.cn/apache/tomcat/tomcat-8/v8.5.40/bin/apache-tomcat-8.5.40.tar.gz &&\
tar -zxvf apache-tomcat-8.5.40.tar.gz -C /usr/local/ && \
mv /usr/local/apache-tomcat-8.5.40 /usr/local/tomcat && \
rm -rf ${DIR}
```
### 多阶段构建
[Use multi-stage builds](https://docs.docker.com/develop/develop-images/multistage-build/) **multi-stage builds 的重点不是multi-stage 而是 builds**
先使用docker 将go文件编译为可执行文件
FROM golang:1.7.3
WORKDIR /go/src/github.com/alexellis/href-counter/
COPY app.go .
RUN go get -d -v golang.org/x/net/html \
&& CGO_ENABLED=0 GOOS=linux go build -a -installsuffix cgo -o app .
因为笔者一直是直接做镜像，所以没这种感觉。不过这么做倒有一点好处：可执行文件的实际运行环境 可以不用跟 开发机相同。学名叫同构/异构镜像构建。
然后将可执行文件 做成镜像
FROM alpine:latest
RUN apk --no-cache add ca-certificates
WORKDIR /root/
COPY app .
CMD ["./app"]
### entrypoint 和 cmd
[Dockerfile: ENTRYPOINT vs CMD](https://www.ctl.io/developers/blog/post/dockerfile-entrypoint-vs-cmd/)
1. ENTRYPOINT和CMD都是让用户指定一个可执行程序，这个可执行程序在container启动后自动启动。
2. 在写Dockerfile时，ENTRYPOINT或者CMD命令会自动覆盖之前镜像的ENTRYPOINT或者CMD命令。
3. 在docker镜像运行时，用户也可以在命令指定具体命令，覆盖在Dockerfile里的命令。 `docker run -it imageName $command` 覆盖 CMD ， `docker run -it imageName --entrypoint $entrypoint`覆盖 ENTRYPOINT
4. CMD命令很容易被`docker run`命令的方式覆盖，如果你希望你的docker镜像只执行一个具体程序,不希望用户在执行`docker run`的时候随意覆盖默认程序。建议用ENTRYPOINT.
ENTRYPOINT和CMD指令支持2种不同的写法: shell表示法和exec表示法，建议采用exec表示法
1. shell表示法 `CMD executable param1 param2`，命令行程序作为sh程序的子程序运行，docker用`/bin/sh -c`的语法调用， pid=1 进程是 `/bin/sh`，那么 sigterm 等信号就不会传给 executable
2. exec表示法 `CMD ["executable","param1","param2"] `，有的镜像甚至连shell程序都可以没有，pid=1进程是 executable
ENTRYPOINT和CMD可以组合使用，ENTRYPOINT指定默认的运行命令, CMD指定默认的运行参数，此时只能使用Exec表示法
```
FROM ubuntu:trusty
ENTRYPOINT ["/bin/ping","-c","3"]
CMD ["localhost"]
# docker build -t pingimage .
```
1. 可以不带任何参数运行`docker run`命令： `docker run pingimage`
2. 可以覆盖CMD指令的值，如果你希望这个docker镜像启动后不是`ping localhost`， 而是ping其他服务器，可以`docker run pingimage docker.io`
## 镜像下载
镜像一般会包括两部分内容，一个是 manifests 文件，这个文件定义了镜像的 元数据，另一个是镜像层，是实际的镜像分层文件。
### docker login
我们在拉取私有镜像之前，要使用 docker login 命令来登录镜像仓库。登录主要就做了三件 事情:
1. 向用户要账户密码
2. docker 访问镜像仓库的 https 地址，并通过挑战 v2 接口来确 认，接口是否会返回 Docker-Distribution-Api-Version 头字段。它的作用跟 ping 差不多，只是确认下 v2 镜像仓库是否在线，以及版本是否匹配。
3. docker 使用用户提供的账户密码，访问 Www-Authenticate 头字段返回的鉴权服务器的地址 Bearer realm。如果这个访问成功，则鉴权服务器会返回 jwt 格式的 token 给 docker，然后 docker 会把账户密码编码并保存在用户目录的 .docker/docker.json 文件里。这个文件作为 docker 登录仓库的 唯一证据，在后续镜像仓库操作中，会被不断的读取并使用。
### docker 镜像下载加速
两种方案
1. 使用private registry
2. 使用registry mirror,以使用daocloud的registry mirror为例，假设你的daocloud的用户名问`lisi`，则`DOCKER_OPTS=--registry-mirror=http://lisi.m.daocloud.io`
[Serverless 场景下 Pod 创建效率优化](https://mp.weixin.qq.com/s/0OLdyVwg4Nsw0Xvvg8if5w)解压镜像耗时会占拉取镜像总耗时很大的比例，测试的例子最大占比到了 77%，所以需要考虑如何提升解压效率。gzip/gunzip 是单线程的压缩/解压工具，可考虑采用 pigz/unpigz 进行多线程的压缩/解压，充分利用多核优势。containerd 从 1.2 版本开始支持 pigz，节点上安装 unpigz 工具后，会优先用其进行解压。通过这种方法，可通过节点多核能力提升镜像解压效率。这个过程也需要关注 下载/上传 的并发度问题，docker daemon 提供了两个参数来控制并发度，控制并行处理的镜像层的数量，`--max-concurrent-downloads` 和 `--max-concurrent-uploads`。默认情况下，下载的并发度是 3，上传的并发度是 5，可根据测试结果调整到合适的值。
通常内网的带宽足够大，是否有可能省去 解压缩/压缩 的逻辑，将拉取镜像的耗时集中在下载镜像方面？当然，这个动静有点大了，要修改docker daemon。
按需加载镜像。在镜像启动耗时中，拉取镜像占比 76%，但是在启动时，仅有 6.4% 的数据被使用到，即镜像启动时需要的镜像数据量很少。对于「Image 所有 layers 下载完后才能启动镜像」，需要改为启动容器时按需加载镜像，类似启动虚拟机的方式，仅对启动阶段需要的数据进行网络传输。但当前镜像格式通常是 tar.gz 或 tar，而 tar 文件没有索引，gzip 文件不能从任意位置读取数据，这样就不能满足按需拉取时拉取指定文件的需求，镜像格式需要改为可索引的文件格式。Google 提出了一种新的镜像格式，stargz，全称是 seeable tar.gz。它兼容当前的镜像格式，但提供了文件索引，可从指定位置读取数据。然后在 containerd 拉取镜像环节，对 containerd 提供一种 remote snapshotter，在创建容器 rootfs 层时，不通过先下载镜像层再构建的方式，而是直接 mount 远程存储层，要实现这样的能力，一方面需要修改 containerd 当前的逻辑，在 filter 阶段识别远程镜像层，对于这样的镜像层不进行 download 操作，一方面需要实现一个 remote snapshotter，来支持对于远程层的管理。当 containerd 通过 remote snapshotter 创建容器时，省去了拉取镜像的阶段，对于启动过程中需要的文件，可对 stargz 格式的镜像数据发起 HTTP Range GET 请求，拉取目标数据。PS：计算与存储分离，那干脆镜像也在远端得了，serverless 对冷启动极致的追求才有了这样的优化。
| 39.009259 | 702 | 0.79136 | yue_Hant | 0.740862 |
a6d1000ede369c1426a0a7ec84c6a17ef21157af | 2,403 | md | Markdown | docs/reporting-services/wmi-provider-library-reference/msreportserver-instance-methods-getreportserverurls.md | L3onard80/sql-docs.it-it | f73e3d20b5b2f15f839ff784096254478c045bbb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/reporting-services/wmi-provider-library-reference/msreportserver-instance-methods-getreportserverurls.md | L3onard80/sql-docs.it-it | f73e3d20b5b2f15f839ff784096254478c045bbb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/reporting-services/wmi-provider-library-reference/msreportserver-instance-methods-getreportserverurls.md | L3onard80/sql-docs.it-it | f73e3d20b5b2f15f839ff784096254478c045bbb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Metodo GetReportServerUrls (MSReportServer_Instance WMI) | Microsoft Docs
ms.date: 06/09/2016
ms.prod: reporting-services
ms.prod_service: reporting-services-native
ms.technology: wmi-provider-library-reference
ms.topic: conceptual
helpviewer_keywords:
- GetReportServerUrls method
ms.assetid: 4865e32c-0114-465a-be8c-be223a7bc09e
author: maggiesMSFT
ms.author: maggies
ms.openlocfilehash: bc04865c9dcbdf16627c1ab4598610426e4a8d5a
ms.sourcegitcommit: ff82f3260ff79ed860a7a58f54ff7f0594851e6b
ms.translationtype: HT
ms.contentlocale: it-IT
ms.lasthandoff: 03/29/2020
ms.locfileid: "65571945"
---
# <a name="msreportserver_instance-methods---getreportserverurls"></a>Metodi di MSReportServer_Instance - GetReportServerUrls
Restituisce un elenco degli URL che è possibile usare per accedere al server di report e [!INCLUDE[ssRSWebPortal](../../includes/ssrswebportal.md)].
## <a name="syntax"></a>Sintassi
```vb
Public Sub GetReportServerUrls (ByRef ApplicationName() As String, ByRef URLs()_
As String, ByRef Length As Int32, ByRef HRESULT As Int32)
```
```csharp
public void GetReportServerUrls(out string[] applicationName,
out string[] URLs, out int length, out int HRESULT);
```
## <a name="parameters"></a>Parametri
*ApplicationName[]*
Matrice che contiene le applicazioni installate. I valori validi sono **ReportServerWebService** e **ReportServerWebApp**.
*URLs[]*
Matrice che contiene gli URL registrati correttamente.
*Lunghezza*
Valore intero che contiene la lunghezza delle matrici restituite.
*HRESULT*
Valore che indica l'esito positivo o un codice di errore.
## <a name="return-values"></a>Valori restituiti
## <a name="remarks"></a>Osservazioni
I metodi esposti dagli oggetti di gestione WMI vengono chiamati tramite la funzione InvokeMethod. Per altre informazioni, vedere gli argomenti relativi all'esecuzione di metodi in oggetti di gestione all'interno della documentazione di [!INCLUDE[msCoName](../../includes/msconame-md.md)] .NET Framework WMI.
## <a name="requirements"></a>Requisiti
**Spazio dei nomi:** [!INCLUDE[ssRSWMInmspc](../../includes/ssrswminmspc-md.md)]
## <a name="see-also"></a>Vedere anche
[Membri di MSReportServer_ConfigurationSetting](../../reporting-services/wmi-provider-library-reference/msreportserver-configurationsetting-members.md)
| 40.05 | 310 | 0.75489 | ita_Latn | 0.60023 |
a6d18b92644f4cb65fdbc8588a723462f8504280 | 2,082 | md | Markdown | sdk-api-src/content/gdiplustypes/nl-gdiplustypes-characterrange.md | amorilio/sdk-api | 54ef418912715bd7df39c2561fbc3d1dcef37d7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | sdk-api-src/content/gdiplustypes/nl-gdiplustypes-characterrange.md | amorilio/sdk-api | 54ef418912715bd7df39c2561fbc3d1dcef37d7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | sdk-api-src/content/gdiplustypes/nl-gdiplustypes-characterrange.md | amorilio/sdk-api | 54ef418912715bd7df39c2561fbc3d1dcef37d7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
UID: NL:gdiplustypes.CharacterRange
title: CharacterRange (gdiplustypes.h)
description: A CharacterRange object specifies a range of character positions within a string.
helpviewer_keywords: ["CharacterRange","CharacterRange class [GDI+]","CharacterRange class [GDI+]","described","_gdiplus_CLASS_CharacterRange_Class","gdiplus._gdiplus_CLASS_CharacterRange_Class","gdiplustypes/CharacterRange"]
old-location: gdiplus\_gdiplus_CLASS_CharacterRange_Class.htm
tech.root: gdiplus
ms.assetid: VS|gdicpp|~\gdiplus\gdiplusreference\classes\characterrange.htm
ms.date: 12/05/2018
ms.keywords: CharacterRange, CharacterRange class [GDI+], CharacterRange class [GDI+],described, _gdiplus_CLASS_CharacterRange_Class, gdiplus._gdiplus_CLASS_CharacterRange_Class, gdiplustypes/CharacterRange
req.header: gdiplustypes.h
req.include-header:
req.target-type: Windows
req.target-min-winverclnt:
req.target-min-winversvr:
req.kmdf-ver:
req.umdf-ver:
req.ddi-compliance:
req.unicode-ansi:
req.idl:
req.max-support:
req.namespace:
req.assembly:
req.type-library:
req.lib:
req.dll:
req.irql:
targetos: Windows
req.typenames:
req.redist:
ms.custom: 19H1
f1_keywords:
- CharacterRange
- gdiplustypes/CharacterRange
dev_langs:
- c++
topic_type:
- APIRef
- kbSyntax
api_type:
- COM
api_location:
- gdiplustypes.h
api_name:
- CharacterRange
---
# CharacterRange class
## -description
A <a href="/previous-versions/ms536266(v=vs.85)">CharacterRange</a> object specifies a range of character positions within a string.
## -remarks
A character range is a range of character positions within a string of text. The area of the display that is occupied by a group of characters that are specified by the character range is the bounding region. A character range is set by
<b>StringFormat::SetMeasurableCharacterRanges</b>. The number of ranges that are currently set can be determined by calling
<b>StringFormat::GetMeasurableCharacterRangeCount</b>. This number is also the number of regions expected to be obtained by the
<b>MeasureCharacterRanges</b> method.
| 33.580645 | 237 | 0.791066 | eng_Latn | 0.750611 |
a6d1dba8b8ce7475eacccc1e65a8daaf1f08df5e | 1,739 | md | Markdown | Speech/DeepSpeech/readme.md | yuhonghong66/ModelZoo | b8974d4814999894a110e1faf1faf5908a770d0d | [
"Apache-2.0"
] | 189 | 2016-03-12T06:28:16.000Z | 2021-09-02T01:56:57.000Z | Speech/DeepSpeech/readme.md | yuhonghong66/ModelZoo | b8974d4814999894a110e1faf1faf5908a770d0d | [
"Apache-2.0"
] | 22 | 2016-03-21T13:33:30.000Z | 2018-04-12T21:10:50.000Z | Speech/DeepSpeech/readme.md | yuhonghong66/ModelZoo | b8974d4814999894a110e1faf1faf5908a770d0d | [
"Apache-2.0"
] | 71 | 2016-03-14T16:39:28.000Z | 2021-11-11T07:03:30.000Z |
This is an implementation of a Deep Speech 2 model based on the paper
[Amodei, et al., 2015](https://arxiv.org/pdf/1512.02595v1.pdf)
on end-to-end speech recognition.
### Instructions
For complete instructions on preparing datasets and/or training the model, refer to the [README](https://github.com/NervanaSystems/deepspeech) in our deepspeech repository.
In particular, to evaluate the model's performance, you need to follow the instructions on preparing a manifest file using Librispeech's [test-clean](http://www.openslr.org/12/) dataset.
Once the manifest file is prepared, you can evaluate the model by running
```
python evaluate.py --manifest val:/path/to/test_data_manifest --model_file /path/to/saved_model
```
where /path/to/test_data_manifest should point to the location of the manifest file that you prepared for use with the test dataset and /path/to/saved_model should point to the location of the trained model.
### Trained weights
The trained model weights can be downloaded from AWS using the following link:
[trained speech model weights][S3_WEIGHTS_FILE].
[S3_WEIGHTS_FILE]: https://s3-us-west-1.amazonaws.com/nervana-modelzoo/Deep_Speech/Librispeech/librispeech_16_epochs.prm
The weights provded here have been verified to work with [neon version 1.7.0](https://github.com/NervanaSystems/neon/releases/tag/v1.7.0)
The weights file may not work with other versions of neon.
This set of weights was trained using our deepspeech repo's [train.py](https://github.com/NervanaSystems/deepspeech/blob/master/speech/train.py) script for 15 epochs. Simple argmax decoding using this set of weights gives a CER of 14% when evaluated using the [test-clean Librispeech dataset](http://www.openslr.org/12/).
| 54.34375 | 322 | 0.786659 | eng_Latn | 0.970936 |
a6d203b379ca493192e66cd00eefabcc16f4b5f3 | 2,816 | md | Markdown | md-version/resources/m1-adopt-a-template/index.md | zmuhls/discord-edu-kit | 7eb490878e46ad2592c081cbea8d343620d92d2f | [
"CC0-1.0"
] | 1 | 2022-03-02T11:31:12.000Z | 2022-03-02T11:31:12.000Z | md-version/resources/m1-adopt-a-template/index.md | zmuhls/discordedu | 7eb490878e46ad2592c081cbea8d343620d92d2f | [
"CC0-1.0"
] | null | null | null | md-version/resources/m1-adopt-a-template/index.md | zmuhls/discordedu | 7eb490878e46ad2592c081cbea8d343620d92d2f | [
"CC0-1.0"
] | null | null | null | ---
title: "Adopt a Template"
date: "2022-01-18"
---
**Template Permalink**: [**College Writing 101**](https://t.co/Gj1CeXXXzI)
- **Instructor Attribution:** Zach Muhlbauer
- **Course Section:** ENG 2100: Writing 1 (Fall 2021)
- **Course Modality:** Fully Online, Synchronous
- **Institutional Context**: Department of English, First-Year Writing, Baruch College, CUNY
- **CC License**: Creative Commons Attribution-NonCommercial 4.0 International License
- **Tags**: Arts & Humanities, First-Year Writing, General Education, Seminar, Writing-Intensive
**Template Permalink**: [**College Writing 101**](https://discord.new/apruqpPzDqXv)
- **Instructor Attribution:** Dan Libertz
- **Course Section**: ENG 2100: Writing 1 (Spring 2021)
- **Course Modality:** Fully Online, Hybrid
- **Institutional Contextt**: Department of English, First-Year Writing, Baruch College, CUNY
- **CC License**: Creative Commons Attribution-NonCommercial 4.0 International License
- **Tags**: Arts & Humanities, First-Year Writing, General Education, Seminar, Writing-Intensive
**Template Permalink**: [**Theatre Arts Survey 1**](https://discord.new/EGznSuGmazTU)
- **Instructor Attribution**: Cen Liu
- **Course Section**: THTR 13100: Introduction to Theatre Arts (Spring 2021)
- **Course Modality**: Fully Online, Synchronous
- **Institutional Context**: Department of Theatre and Speech, City College of New York (CCNY), CUNY
- **CC License**: Creative Commons Attribution-NonCommercial 4.0 International License
- **Tags**: General Education, Writing-Intensive, Disciplinary Survey, Seminar, Arts & Humanities
**Template Permalink**: [**EDU Template**](https://discord.com/template/8VqhpY8fQtvD) (Intro to 3D Animation + 3D Animation Projects)
- **Instructor Attribution**: Carlo Diego
- **Course Section**: ANI 401 (0902): Introduction to 3D Animations, ANI 401 (1301): Introduction to 3D Animations; ANI 402 (0901): 3D Animation Projects \[Fall 2021\]
- **Course Modality**: Fully Online, Synchronous
- **Institutional Context**: Department of Media Arts and Technology, Animations and Motion Graphics, Borough of Manhattan Community College (BMCC), CUNY
- **CC License**: Creative Commons Attribution-NonCommercial 4.0 International License
- **Tags**: Animations, Media Arts, Makerspaces, Graphic Design, Motion Graphics
**Template Permalink:** [**English Composition 1**](https://discord.new/MeXAc5R56dXv)
- **Instructor Attribution**: Ada O’Higgins
- **Course Section**: ENG 1010: Composition 1 (Fall 2021)
- **Course Modality**: Fully Online, Synchronous
- **Institutional Context**: Department of English, Brooklyn College, CUNY
- **CC License**: Creative Commons Attribution-NonCommercial 4.0 International License
- **Tags**: Arts & Humanities, First-Year Writing, General Education, Seminar, Writing-Intensive
| 56.32 | 167 | 0.745384 | yue_Hant | 0.708702 |
a6d3450ebc0807fecf04fb38f88f46b7dfce74f9 | 818 | md | Markdown | _ru/pos/ADP.md | MarcoDiMarek/docs | c00f9c59b8e1e93b24c119fbdccb84aaf6b06565 | [
"Apache-2.0"
] | null | null | null | _ru/pos/ADP.md | MarcoDiMarek/docs | c00f9c59b8e1e93b24c119fbdccb84aaf6b06565 | [
"Apache-2.0"
] | null | null | null | _ru/pos/ADP.md | MarcoDiMarek/docs | c00f9c59b8e1e93b24c119fbdccb84aaf6b06565 | [
"Apache-2.0"
] | null | null | null | ---
layout: postag
title: 'ADP'
shortdef: 'adposition'
---
### Definition
Russian has only prepositions but not postpositionsand and circumpositions.
They occur before a complement noun phrase
(noun, pronoun)
and they form a single structure with the complement to express its
grammatical and semantic relation to another unit within a clause.
Some prepositions take the form of fixed multiword expressions, e.g.
_по сравнению с_ “in comparison with”, _в связи с_
“in connection with”. The
component words are then still tagged according to their basic use
(_по_ is `ADP`, _сравнению_ is [NOUN](), etc.) and their status as
multiword expressions are accounted for in the syntactic annotation
### Examples
- _в;_ “in, at”
- _к_ “to”
- _на_ “on, at”
<!-- Interlanguage links updated Čt lis 12 09:42:49 CET 2020 -->
| 29.214286 | 75 | 0.757946 | eng_Latn | 0.996922 |
a6d3cafc72636725bfd27403176d173fa62c3ff1 | 1,700 | md | Markdown | wdk-ddi-src/content/strmini/ns-strmini-_stream_time_reference.md | kein284/windows-driver-docs-ddi | 3b70e03c2ddd9d8d531f4dc2fb9a4bb481b7dd54 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | wdk-ddi-src/content/strmini/ns-strmini-_stream_time_reference.md | kein284/windows-driver-docs-ddi | 3b70e03c2ddd9d8d531f4dc2fb9a4bb481b7dd54 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | wdk-ddi-src/content/strmini/ns-strmini-_stream_time_reference.md | kein284/windows-driver-docs-ddi | 3b70e03c2ddd9d8d531f4dc2fb9a4bb481b7dd54 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-12-08T21:34:31.000Z | 2021-12-08T21:34:31.000Z | ---
UID: NS:strmini._STREAM_TIME_REFERENCE
title: _STREAM_TIME_REFERENCE (strmini.h)
description:
old-location: stream\stream_time_reference.htm
tech.root: stream
ms.assetid: BC3839C0-AED6-470D-9C2B-B1529B2B3D1A
ms.date: 04/23/2018
keywords: ["STREAM_TIME_REFERENCE structure"]
ms.keywords: "*PSTREAM_TIME_REFERENCE, PSTREAM_TIME_REFERENCE, PSTREAM_TIME_REFERENCE structure pointer [Streaming Media Devices], STREAM_TIME_REFERENCE, STREAM_TIME_REFERENCE structure [Streaming Media Devices], _STREAM_TIME_REFERENCE, stream.stream_time_reference, strmini/PSTREAM_TIME_REFERENCE, strmini/STREAM_TIME_REFERENCE"
req.header: strmini.h
req.include-header:
req.target-type: Windows
req.target-min-winverclnt:
req.target-min-winversvr:
req.kmdf-ver:
req.umdf-ver:
req.ddi-compliance:
req.unicode-ansi:
req.idl:
req.max-support:
req.namespace:
req.assembly:
req.type-library:
req.lib:
req.dll:
req.irql:
targetos: Windows
req.typenames: STREAM_TIME_REFERENCE, *PSTREAM_TIME_REFERENCE
f1_keywords:
- _STREAM_TIME_REFERENCE
- strmini/_STREAM_TIME_REFERENCE
- PSTREAM_TIME_REFERENCE
- strmini/PSTREAM_TIME_REFERENCE
- STREAM_TIME_REFERENCE
- strmini/STREAM_TIME_REFERENCE
topic_type:
- APIRef
- kbSyntax
api_type:
- HeaderDef
api_location:
- Strmini.h
api_name:
- STREAM_TIME_REFERENCE
---
# _STREAM_TIME_REFERENCE structure
## -description
## -struct-fields
### -field CurrentOnboardClockValue
Current value of the adapter clock.
### -field OnboardClockFrequency
Frequency of the adapter clock.
### -field CurrentSystemTime
KeQueryPerformanceCounter time.
### -field Reserved
Reserved for future use.
| 23.943662 | 330 | 0.770588 | yue_Hant | 0.888741 |
a6d54c9216b7876580b3f171b990bd1013a0d94b | 11,321 | md | Markdown | articles/cognitive-services/Speech-Service/includes/speech-devices-sdk-android-quickstart.md | changeworld/azure-docs.it- | 34f70ff6964ec4f6f1a08527526e214fdefbe12a | [
"CC-BY-4.0",
"MIT"
] | 1 | 2017-06-06T22:50:05.000Z | 2017-06-06T22:50:05.000Z | articles/cognitive-services/Speech-Service/includes/speech-devices-sdk-android-quickstart.md | changeworld/azure-docs.it- | 34f70ff6964ec4f6f1a08527526e214fdefbe12a | [
"CC-BY-4.0",
"MIT"
] | 41 | 2016-11-21T14:37:50.000Z | 2017-06-14T20:46:01.000Z | articles/cognitive-services/Speech-Service/includes/speech-devices-sdk-android-quickstart.md | changeworld/azure-docs.it- | 34f70ff6964ec4f6f1a08527526e214fdefbe12a | [
"CC-BY-4.0",
"MIT"
] | 7 | 2016-11-16T18:13:16.000Z | 2017-06-26T10:37:55.000Z | ---
author: trevorbye
ms.service: cognitive-services
ms.subservice: speech-service
ms.topic: include
ms.date: 02/20/2020
ms.author: trbye
ms.openlocfilehash: 3b473d82eb879955a6cbdce58ba66176f5c6d6f5
ms.sourcegitcommit: d1e56036f3ecb79bfbdb2d6a84e6932ee6a0830e
ms.translationtype: MT
ms.contentlocale: it-IT
ms.lasthandoff: 01/29/2021
ms.locfileid: "99213630"
---
In questa guida di avvio rapido si apprenderà come usare Speech Devices SDK per Android per compilare un prodotto abilitato al riconoscimento vocale o usarlo come dispositivo di [trascrizione conversazione](../conversation-transcription.md).
Per riprodurre le procedure di questa guida, è necessario un account di [Servizi cognitivi di Azure](../overview.md#try-the-speech-service-for-free) con una risorsa del servizio Voce.
Il codice sorgente dell'applicazione di esempio è incluso in Speech Devices SDK ed è anche [disponibile in GitHub](https://github.com/Azure-Samples/Cognitive-Services-Speech-Devices-SDK).
## <a name="prerequisites"></a>Prerequisiti
Prima di iniziare a usare Speech Devices SDK, è necessario:
- Seguire le istruzioni fornite nel [kit di sviluppo](../get-speech-devices-sdk.md) per accendere il dispositivo.
- Scaricare la versione più recente di [Speech Devices SDK](../speech-devices-sdk.md) ed estrarre il file ZIP nella directory di lavoro.
> [!NOTE]
> Questo argomento di avvio rapido presuppone che l'app venga estratta in C:\SDSDK\Android-Sample-Release
- Per ottenere una [chiave di sottoscrizione di Azure per il servizio Voce](../overview.md#try-the-speech-service-for-free)
- Se si prevede di usare la funzionalità di trascrizione conversazione, è necessario usare un [dispositivo con microfono circolare](../get-speech-devices-sdk.md) e questa funzionalità è attualmente disponibile solo per i codici di lingua "en-US" e "zh-CN" nella aree "centralus" e "eastasia". È necessario avere una chiave di riconoscimento vocale in una di queste aree per usare la trascrizione conversazione.
- Se si prevede di usare il servizio Voce per identificare finalità (o azioni) dalle espressioni degli utenti, è necessaria una sottoscrizione di [LUIS (Language Understanding Service)](../../luis/luis-how-to-azure-subscription.md). Per altre informazioni su LUIS e sul riconoscimento delle finalità, vedere [Riconoscere le finalità voce con LUIS, C#](../how-to-recognize-intents-from-speech-csharp.md).
È possibile [creare un modello LUIS semplice](../../luis/index.yml) oppure usare il modello LUIS di esempio, ovvero LUIS-example.json. Il modello LUIS di esempio è disponibile nel [sito di download di Speech Devices SDK](https://aka.ms/sdsdk-luis). Per caricare il file JSON del modello nel [portale LUIS](https://www.luis.ai/home), selezionare **Import new app** (Importa nuova app) e quindi selezionare il file JSON.
- Installare [Android Studio](https://developer.android.com/studio/) e [Vysor](https://vysor.io/download/) nel PC.
## <a name="set-up-the-device"></a>Configurare il dispositivo
1. Avviare Vysor nel computer.
1. Il dispositivo dovrebbe essere incluso nell'elenco **Choose a device** (Scegli un dispositivo). Selezionare clic sul pulsante **View** (Visualizza) accanto al dispositivo.
1. Connettersi alla rete wireless facendo clic sull'icona della cartella e quindi su **Impostazioni** > **WLAN**.
> [!NOTE]
> Se la società prevede criteri per la connessione dei dispositivi al sistema Wi-Fi, è necessario ottenere l'indirizzo MAC e contattare il reparto IT per sapere come connettersi al sistema Wi-Fi aziendale.
>
> Per trovare l'indirizzo MAC del kit di sviluppo, selezionare l'icona della cartella file sul desktop del kit di sviluppo.
>
> 
>
> Selezionare **Impostazioni**. Cercare "indirizzo mac" e quindi selezionare **Mac address** > **Advanced WLAN** (Indirizzo MAC > WLAN avanzata). Prendere nota dell'indirizzo MAC che viene visualizzato nella parte inferiore della finestra di dialogo.
>
> 
>
> Alcune società possono inoltre prevedere un limite al tempo in cui un dispositivo può rimanere connesso al sistema Wi-Fi aziendale. Può quindi essere necessario prolungare la registrazione del kit di sviluppo al sistema Wi-Fi dopo un certo numero di giorni.
## <a name="run-the-sample-application"></a>Eseguire l'applicazione di esempio
Per convalidare la configurazione del kit di sviluppo, compilare e installare l'applicazione di esempio:
1. Avviare Android Studio.
1. Selezionare **Open an existing Android Studio project** (Apri un progetto di Android Studio esistente).
1. Passare a C:\SDSDK\Android-Sample-Release\example. Fare clic su **OK** per aprire il progetto di esempio.
1. Configurare Gradle per fare riferimento a Speech SDK. I file seguenti sono disponibili in **Gradle Scripts** (Script Gradle) in Android Studio.
Aggiornare **build.gradle(Project:example)** , il blocco allprojects dovrebbe corrispondere a quando riportato di seguito, aggiungendo le righe Maven.
```xml
allprojects {
repositories {
google()
jcenter()
mavenCentral()
maven {
url 'https://csspeechstorage.blob.core.windows.net/maven/'
}
}
}
```
Aggiornare **build.gradle(Module:app)** aggiungendo questa riga alla sezione dipendenze.
```xml
implementation'com.microsoft.cognitiveservices.speech:client-sdk:1.15.0'
```
1. Aggiungere la chiave di sottoscrizione del Servizio di riconoscimento vocale al codice sorgente. Se si vuole provare la funzionalità Riconoscimento finalità, aggiungere anche la chiave di sottoscrizione e l'ID applicazione del [servizio Language Understanding](https://azure.microsoft.com/services/cognitive-services/language-understanding-intelligent-service/).
Per il riconoscimento vocale e LUIS, le informazioni vanno in MainActivity.java:
```java
// Subscription
private static String SpeechSubscriptionKey = "<enter your subscription info here>";
private static String SpeechRegion = "westus"; // You can change this if your speech region is different.
private static String LuisSubscriptionKey = "<enter your subscription info here>";
private static String LuisRegion = "westus2"; // you can change this, if you want to test the intent, and your LUIS region is different.
private static String LuisAppId = "<enter your LUIS AppId>";
```
Se si usa la trascrizione conversazione, le informazioni sulla chiave di riconoscimento vocale e sull'area sono necessarie anche in conversation.java:
```java
private static final String CTSKey = "<Conversation Transcription Service Key>";
private static final String CTSRegion="<Conversation Transcription Service Region>";// Region may be "centralus" or "eastasia"
```
1. La parola chiave predefinita è "Computer". È anche possibile provare una delle altre parole chiave disponibili, come "Machine" o "Assistant". I file di risorse per queste parole chiave alternative sono disponibili nella cartella keyword di Speech Devices SDK. La cartella C:\SDSDK\Android-Sample-Release\keyword\Computer contiene ad esempio i file usati per la parola chiave "Computer".
> [!TIP]
> È anche possibile [creare una parola chiave personalizzata](../custom-keyword-basics.md).
Per usare una nuova parola chiave, aggiornare le due righe seguenti in `MainActivity.java` e copiare il pacchetto di parole chiave nell'app. Ad esempio, per usare la parola chiave 'Machine' del pacchetto di parole chiave kws-machine.zip:
- Copiare il pacchetto di parole chiave nella cartella "C:\SDSDK\Android-Sample-Release\example\app\src\main\assets\\".
- Aggiornare `MainActivity.java` con la parola chiave e il nome del pacchetto:
```java
private static final String Keyword = "Machine";
private static final String KeywordModel = "kws-machine.zip" // set your own keyword package name.
```
1. Aggiornare le righe seguenti, che contengono le impostazioni per la geometria dell'array di microfoni:
```java
private static final String DeviceGeometry = "Circular6+1";
private static final String SelectedGeometry = "Circular6+1";
```
Questa tabella elenca i valori supportati:
| Variabile | Significato | Valori disponibili |
| -------- | ------- | ---------------- |
| `DeviceGeometry` | Configurazione microfoni fisica | Per un kit di sviluppo circolare: `Circular6+1` |
| | | Per un kit di sviluppo lineare: `Linear4` |
| `SelectedGeometry` | Configurazione microfoni software | Per un kit di sviluppo circolare che usa tutti i microfoni: `Circular6+1` |
| | | Per un kit di sviluppo circolare che usa quattro microfoni: `Circular3+1` |
| | | Per un kit di sviluppo lineare che usa tutti i microfoni: `Linear4` |
| | | Per un kit di sviluppo lineare che usa due microfoni: `Linear2` |
1. Per compilare l'applicazione, nel menu **Run** (Esegui) selezionare **Run 'app'** (Esegui 'app'). Viene visualizzata la finestra di dialogo **Select Deployment Target** (Seleziona destinazione di distribuzione).
1. Selezionare il dispositivo e quindi fare clic su **OK** per distribuire l'applicazione nel dispositivo.
1. L'applicazione di esempio di Speech Devices SDK viene avviata e visualizza le opzioni seguenti:
1. Provare la nuova demo di Trascrizione conversazione. Avviare la trascrizione con "Avvia sessione". Per impostazione predefinita, ogni utente è un guest. Se però si hanno le firme vocali dei partecipanti, è possibile inserirle in un file `/video/participants.properties` nel dispositivo. Per generare la firma vocale, vedere [Trascrivere le conversazioni (SDK)](../how-to-use-conversation-transcription.md).
1. A questo punto, non resta che sperimentare.
## <a name="troubleshooting"></a>Risoluzione dei problemi
Se non è possibile connettersi al dispositivo di riconoscimento vocale, digitare il comando seguente in una finestra del prompt dei comandi. Verrà restituito un elenco di dispositivi.
```powershell
adb devices
```
> [!NOTE]
> Questo comando usa Android Debug Bridge, `adb.exe`, che fa parte dell'installazione di Android Studio. Questo strumento si trova in C:\Utenti\[nome utente]\AppData\Local\Android\Sdk\platform-tools. Per richiamare più facilmente `adb`, è possibile aggiungere questa directory al percorso. In caso contrario, è necessario specificare il percorso completo dell'installazione di adb.exe in ogni comando che richiama `adb`.
>
> Se viene visualizzato un errore `no devices/emulators found`, verificare che il cavo USB sia collegato e che sia un cavo di alta qualità. | 62.203297 | 420 | 0.750375 | ita_Latn | 0.994661 |
a6d5ea0e5dd1d7b9907769073a57ae4dbc5cede5 | 9,174 | md | Markdown | roles/os-harden/README.md | aikin/kubeasz | 2ebc31c036d6dfbe62bc92b04e738b90436a0937 | [
"Apache-2.0"
] | 14 | 2018-07-02T00:48:02.000Z | 2021-05-02T16:00:55.000Z | roles/os-harden/README.md | twocucao/kubeasz | 3efa846f95d864b64efa851744f7c68a88638224 | [
"Apache-2.0"
] | null | null | null | roles/os-harden/README.md | twocucao/kubeasz | 3efa846f95d864b64efa851744f7c68a88638224 | [
"Apache-2.0"
] | 5 | 2018-08-06T03:29:55.000Z | 2019-11-15T07:36:45.000Z | # os-hardening (Ansible Role)
[][1]
[][2]
[][3]
## Description
This role provides numerous security-related configurations, providing all-round base protection. It is intended to be compliant with the [DevSec Linux Baseline](https://github.com/dev-sec/linux-baseline).
It configures:
* Configures package management e.g. allows only signed packages
* Remove packages with known issues
* Configures `pam` and `pam_limits` module
* Shadow password suite configuration
* Configures system path permissions
* Disable core dumps via soft limits
* Restrict Root Logins to System Console
* Set SUIDs
* Configures kernel parameters via sysctl
It will not:
* Update system packages
* Install security patches
## Requirements
* Ansible 2.4.2
## Warning
If you're using inspec to test your machines after applying this role, please make sure to add the connecting user to the `os_ignore_users`-variable.
Otherwise inspec will fail. For more information, see [issue #124](https://github.com/dev-sec/ansible-os-hardening/issues/124).
## Variables
| Name | Default Value | Description |
| -------------- | ------------- | -----------------------------------|
| `os_desktop_enable`| false | true if this is a desktop system, ie Xorg, KDE/GNOME/Unity/etc|
| `os_env_extra_user_paths`| [] | add additional paths to the user's `PATH` variable (default is empty).|
| `os_env_umask`| 027| set default permissions for new files to `750` |
| `os_auth_pw_max_age`| 60 | maximum password age (set to `99999` to effectively disable it) |
| `os_auth_pw_min_age`| 7 | minimum password age (before allowing any other password change)|
| `os_auth_retries`| 5 | the maximum number of authentication attempts, before the account is locked for some time|
| `os_auth_lockout_time`| 600 | time in seconds that needs to pass, if the account was locked due to too many failed authentication attempts|
| `os_auth_timeout`| 60 | authentication timeout in seconds, so login will exit if this time passes|
| `os_auth_allow_homeless`| false | true if to allow users without home to login|
| `os_auth_pam_passwdqc_enable`| true | true if you want to use strong password checking in PAM using passwdqc|
| `os_auth_pam_passwdqc_options`| "min=disabled,disabled,16,12,8" | set to any option line (as a string) that you want to pass to passwdqc|
| `os_security_users_allow`| [] | list of things, that a user is allowed to do. May contain `change_user`.
| `os_security_kernel_enable_module_loading`| true | true if you want to allowed to change kernel modules once the system is running (eg `modprobe`, `rmmod`)|
| `os_security_kernel_enable_core_dump`| false | kernel is crashing or otherwise misbehaving and a kernel core dump is created |
| `os_security_suid_sgid_enforce`| true | true if you want to reduce SUID/SGID bits. There is already a list of items which are searched for configured, but you can also add your own|
| `os_security_suid_sgid_blacklist`| [] | a list of paths which should have their SUID/SGID bits removed|
| `os_security_suid_sgid_whitelist`| [] | a list of paths which should not have their SUID/SGID bits altered|
| `os_security_suid_sgid_remove_from_unknown`| false | true if you want to remove SUID/SGID bits from any file, that is not explicitly configured in a `blacklist`. This will make every Ansible-run search through the mounted filesystems looking for SUID/SGID bits that are not configured in the default and user blacklist. If it finds an SUID/SGID bit, it will be removed, unless this file is in your `whitelist`.|
| `os_security_packages_clean'`| true | removes packages with known issues. See section packages.|
| `ufw_manage_defaults` | true | true means apply all settings with `ufw_` prefix|
| `ufw_ipt_sysctl` | '' | by default it disables IPT_SYSCTL in /etc/default/ufw. If you want to overwrite /etc/sysctl.conf values using ufw - set it to your sysctl dictionary, for example `/etc/ufw/sysctl.conf`
| `ufw_default_input_policy` | DROP | set default input policy of ufw to `DROP` |
| `ufw_default_output_policy` | ACCEPT | set default output policy of ufw to `ACCEPT` |
| `ufw_default_forward_policy` | DROP| set default forward policy of ufw to `DROP` |
## Packages
We remove the following packages:
* xinetd ([NSA](http://www.nsa.gov/ia/_files/os/redhat/rhel5-guide-i731.pdf), Chapter 3.2.1)
* inetd ([NSA](http://www.nsa.gov/ia/_files/os/redhat/rhel5-guide-i731.pdf), Chapter 3.2.1)
* tftp-server ([NSA](http://www.nsa.gov/ia/_files/os/redhat/rhel5-guide-i731.pdf), Chapter 3.2.5)
* ypserv ([NSA](http://www.nsa.gov/ia/_files/os/redhat/rhel5-guide-i731.pdf), Chapter 3.2.4)
* telnet-server ([NSA](http://www.nsa.gov/ia/_files/os/redhat/rhel5-guide-i731.pdf), Chapter 3.2.2)
* rsh-server ([NSA](http://www.nsa.gov/ia/_files/os/redhat/rhel5-guide-i731.pdf), Chapter 3.2.3)
* prelink ([open-scap](https://static.open-scap.org/ssg-guides/ssg-sl7-guide-ospp-rhel7-server.html#xccdf_org.ssgproject.content_rule_disable_prelink))
## Disabled filesystems
We disable the following filesystems, because they're most likely not used:
* "cramfs"
* "freevxfs"
* "jffs2"
* "hfs"
* "hfsplus"
* "squashfs"
* "udf"
* "vfat"
To prevent some of the filesystems from being disabled, add them to the `os_filesystem_whitelist` variable.
## Example Playbook
- hosts: localhost
roles:
- dev-sec.os-hardening
## Changing sysctl variables
If you want to override sysctl-variables, you can use the `sysctl_overwrite` variable (in older versions you had to override the whole `sysctl_dict`).
+So for example if you want to change the IPv4 traffic forwarding variable to `1`, do it like this:
```
- hosts: localhost
roles:
- dev-sec.os-hardening
vars:
sysctl_overwrite:
# Disable IPv4 traffic forwarding.
net.ipv4.ip_forward: 1
```
Alternatively you can change Ansible's [hash-behaviour](https://docs.ansible.com/ansible/intro_configuration.html#hash-behaviour) to `merge`, then you only have to overwrite the single hash you need to. But please be aware that changing the hash-behaviour changes it for all your playbooks and is not recommended by Ansible.
## Local Testing
The preferred way of locally testing the role is to use Docker. You will have to install Docker on your system. See [Get started](https://docs.docker.com/) for a Docker package suitable to for your system.
You can also use vagrant and Virtualbox or VMWare to run tests locally. You will have to install Virtualbox and Vagrant on your system. See [Vagrant Downloads](http://downloads.vagrantup.com/) for a vagrant package suitable for your system. For all our tests we use `test-kitchen`. If you are not familiar with `test-kitchen` please have a look at [their guide](http://kitchen.ci/docs/getting-started).
Next install test-kitchen:
```bash
# Install dependencies
gem install bundler
bundle install
```
### Testing with Docker
```
# fast test on one machine
bundle exec kitchen test default-ubuntu-1404
# test on all machines
bundle exec kitchen test
# for development
bundle exec kitchen create default-ubuntu-1404
bundle exec kitchen converge default-ubuntu-1404
```
### Testing with Virtualbox
```
# fast test on one machine
KITCHEN_YAML=".kitchen.vagrant.yml" bundle exec kitchen test default-ubuntu-1404
# test on all machines
KITCHEN_YAML=".kitchen.vagrant.yml" bundle exec kitchen test
# for development
KITCHEN_YAML=".kitchen.vagrant.yml" bundle exec kitchen create default-ubuntu-1404
KITCHEN_YAML=".kitchen.vagrant.yml" bundle exec kitchen converge default-ubuntu-1404
```
For more information see [test-kitchen](http://kitchen.ci/docs/getting-started)
## Contributors + Kudos
...
This role is mostly based on guides by:
* [Arch Linux wiki, Sysctl hardening](https://wiki.archlinux.org/index.php/Sysctl)
* [NSA: Guide to the Secure Configuration of Red Hat Enterprise Linux 5](http://www.nsa.gov/ia/_files/os/redhat/rhel5-guide-i731.pdf)
* [Ubuntu Security/Features](https://wiki.ubuntu.com/Security/Features)
* [Deutsche Telekom, Group IT Security, Security Requirements (German)](https://www.telekom.com/psa)
Thanks to all of you!
## Contributing
See [contributor guideline](CONTRIBUTING.md).
## License and Author
* Author:: Sebastian Gumprich
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.
[1]: http://travis-ci.org/dev-sec/ansible-os-hardening
[2]: https://gitter.im/dev-sec/general
[3]: https://galaxy.ansible.com/dev-sec/os-hardening
| 47.28866 | 413 | 0.747656 | eng_Latn | 0.946326 |
a6d6d5fbe6fcf872dea38b3d31a86d19dc1f2522 | 5,807 | md | Markdown | _posts/2019-08-25-first_bokeh_fundraiser_review.md | santos22/blog.bokeh.org | 6a4f55d56704d938052b11c76f165f31435312f3 | [
"BSD-3-Clause"
] | 6 | 2016-06-28T14:30:03.000Z | 2018-06-26T20:43:32.000Z | _posts/2019-08-25-first_bokeh_fundraiser_review.md | santos22/blog.bokeh.org | 6a4f55d56704d938052b11c76f165f31435312f3 | [
"BSD-3-Clause"
] | 9 | 2018-12-05T03:19:27.000Z | 2021-03-10T17:56:53.000Z | _posts/2019-08-25-first_bokeh_fundraiser_review.md | santos22/blog.bokeh.org | 6a4f55d56704d938052b11c76f165f31435312f3 | [
"BSD-3-Clause"
] | 7 | 2017-03-15T00:37:20.000Z | 2018-10-25T13:19:17.000Z | ---
title: 'Review of First Bokeh Fundraiser'
date: 2019-08-25
author: Carolyn Hulsey
featured_image:
excerpt: >
Our first Bokeh fundraiser was a great success! Meet our new corporate sponsors.
draft: false
bokeh: >
---
July of this year was the first time that Bokeh has had a time-bound, focused fund drive, and we were impressed by the show of support: we exceeded our initial funding goal by 20%! While our code contributors have always been essential to maintaining and growing the scope and applications of the Bokeh project, the support of our users in other ways is also fundamental in driving Bokeh's future success.
The Bokeh project has grown significantly in the last year, and some of that has meant incurring some operational costs. The funds raised will go directly to hosting costs for our [documentation](https://docs.bokeh.org/en/latest/), [demo sites](https://demo.bokeh.org/), and the CDN for [BokehJS](https://bokeh.pydata.org/en/latest/docs/dev_guide/bokehjs.html), all platforms for helping our users research and discover ways to create beautiful data representations.
We received support from individuals, several who have shared some amazing visualizations using our libraries; [check out the ongoing "30 Days of Bokeh" challenges on Twitter](https://twitter.com/hashtag/30DaysOfBokehChallenge)! The success of our fundraiser is a direct result of our community of data scientists, data engineers, and data communicators of all types showing their support. Thank you!
### Corporate Sponsors
We also started a corporate sponsorship program, in which companies can support the ongoing development of Bokeh with tiered donation levels:
**Bronze:** $500 per year
**Silver:** $1,000 per year
**Gold:** $2,500 per year
Companies interested in becoming a Bokeh sponsor can email [[email protected]](mailto:[email protected]) to start the conversation.
Here is our inaugural list of wonderful, much-appreciated corporate sponsors for 2019:
<img src="https://static.bokeh.org/sponsor/numfocus.svg"
alt="NumFocus Logo" width="200"/>
The mission of [NumFOCUS](https://numfocus.org/) is to promote open practices in research, data, and scientific computing by serving as a fiscal sponsor for open source projects and organizing community-driven educational programs.
<img src="https://static.bokeh.org/sponsor/anaconda.png" alt="Anaconda Logo" width="200"/>
With more than 15 million users, [Anaconda](https://www.anaconda.com/) is the world’s most popular data science platform and the foundation of modern machine learning. Anaconda Enterprise delivers data science and machine learning at speed and scale, unleashing the full potential of their customers’ data science and machine learning initiatives.
<img src="https://static.bokeh.org/sponsor/nvidia.png"
alt="NVidia Logo" width="200"/><img src="https://static.bokeh.org/sponsor/rapids.png"
alt="Rapids Logo" width="200"/>
The [RAPIDS](https://developer.nvidia.com/rapids) suite of software libraries, built on CUDA-X AI, gives you the freedom to execute end-to-end data science and analytics pipelines entirely on GPUs. It relies on NVIDIA® CUDA® primitives for low-level compute optimization, but exposes that GPU parallelism and high-bandwidth memory speed through user-friendly Python interfaces.
RAPIDS also focuses on common data preparation tasks for analytics and data science. This includes a familiar DataFrame API that integrates with a variety of machine learning algorithms for end-to-end pipeline accelerations without paying typical serialization costs. RAPIDS also includes support for multi-node, multi-GPU deployments, enabling vastly accelerated processing and training on much larger dataset sizes.
<img src="https://static.bokeh.org/sponsor/quansight.png"
alt="Quansight Logo" width="100"/>
[Quansight](https://www.quansight.com/) will help you get started with Artificial Intelligence, Machine Learning, Deep Learning, and Data management using Python or R as well as the toolboxes they link to including NumPy, Pandas, scikit-learn, Jupyter, Tensorflow, PyTorch, MXNet, Caffe, CNTK, Chainer, and more.
Quansight extracts data from transactions, images, videos, weblogs, audio, and more. Access to their community and tools (which produced projects such as NumPy, SciPy, PyData, Numba, Conda, JupyterLab, Dask, Bokeh, XND, and many others) are now available directly to your business or project.
<img src="https://static.bokeh.org/sponsor/rex.jpg"
alt="Rex Logo" width="100"/>
[REX](https://www.rexhomes.com/) was created in 2015 to bring residential real estate into line with today's expectations by using AI and big data to push past the outmoded practices of traditional real estate brokers to provide a superior outcome for both buyers and sellers at one-third the cost. Rex uses data modeling and machine learning to match sellers and buyers of homes as accurately and speedily as possible on Zillow, Google, Facebook and more.
### Become a Contributor!
We learned a lot about how to run a fundraiser with this first event, and we look forward to future successes. If you'd like to become a sustaining supporter of the Bokeh project, [the donation form is still accessible!](https://numfocus.org/donate-to-bokeh) Other ways to contribute to the project include:
* Code contributions. If you know of a way in which Bokeh's feature set could be improved, go for it!
* Sharing your examples of Bokeh at work. We're so proud of all the plots we see on social media and in our gallery!
* Take part in the discussions on the [Bokeh Discourse site](https://discourse.bokeh.org/) . It's a great format for getting support for your Bokeh questions, and helping others with your knowledge.
Thanks again for your support, Bokeh community-- happy plotting!
| 82.957143 | 466 | 0.782848 | eng_Latn | 0.995752 |
a6d71dc2505e1234043c94cdd92bc8ee4a85a7d8 | 2,728 | md | Markdown | moodle/mod/hvp/README.md | lamnguyenit/serverTCU | b4b0ebac51c63fe16b1e960a99c31af7b1b0ab43 | [
"Apache-2.0"
] | null | null | null | moodle/mod/hvp/README.md | lamnguyenit/serverTCU | b4b0ebac51c63fe16b1e960a99c31af7b1b0ab43 | [
"Apache-2.0"
] | null | null | null | moodle/mod/hvp/README.md | lamnguyenit/serverTCU | b4b0ebac51c63fe16b1e960a99c31af7b1b0ab43 | [
"Apache-2.0"
] | null | null | null | # H5P Moodle Plugin
This is the 1.0-rc version of the H5P plugin for Moodle. That means that this
version is feature complete but you might encounter bugs or issues that will
not be present in the final version.
Create and add rich content inside your LMS for free. Some examples of what you
get with H5P are Interactive Video, Quizzes, Collage and Timeline.
## Description
One of the great benefits with using H5P is that it gives you access to lots of
different [interactive content types](https://h5p.org/content-types-and-applications).
Another great benefit with H5P is that it allows you to easily share and reuse
content. To reuse content, you just download the H5P you would like to edit and
make your changes – e.g. translate to a new language or adjust it to a new
situation.
H5P is:
* Open Source
* Free to Use
* HTML5
* Responsive
The H5P community is actively contributing to improve H5P. Updates and new
features are continuously made available on the community portal
[H5P.org](https://h5p.org).
View our [setup for Moodle](https://h5p.org/moodle) to get information on how
to get started with H5P.
## Install
### Beta Version
If you can't wait for the final release or simply wish to help test the plugin,
you can download the beta version.
Here is an example. Remember to replace the version number with the latest from
the [releases](https://github.com/h5p/h5p-moodle-plugin/releases) page:
```
git clone --branch 1.0-rc.2 https://github.com/h5p/h5p-moodle-plugin.git hvp && cd hvp && git submodule update --init
```
It's not recommended to download the tag/version from the
[releases](https://github.com/h5p/h5p-moodle-plugin/releases) page as you would
also have to download the appropriate version of
[h5p-php-library](https://github.com/h5p/h5p-php-library/releases) and
[h5p-editor-php-library](https://github.com/h5p/h5p-php-library/releases) to
put inside the `library` and `editor` folders.
### Development Version
Warning! Using the development version may cause strange bugs, so do not use it
for production!
Inside your `moodle/mod` folder you run the following command:
```
git clone https://github.com/h5p/h5p-moodle-plugin.git hvp && cd hvp && git submodule update --init
```
### Enabling The Plugin
In Moodle, go to administrator -> plugin overview, and press 'Update database'.
## Settings
Settings can be found at: Site Administration -> Plugins -> Activity Modules -> H5P
## Contributing
Feel free to contribute by:
* Submitting translations
* Testing and creating issues. But remember to check if the issues is already
reported before creating a new one. Perhaps you can contribute to an already
existing issue?
* Solving issues and submitting code through Pull Requests.
| 35.894737 | 117 | 0.767595 | eng_Latn | 0.990171 |
a6d75cba9e207c6ba461ca8ed92b65ca246a3e14 | 72 | md | Markdown | readme.md | manfredsteyer/idsvr4-demo | 8e3d4a13aa061a559fbe62f861d9e791176255b9 | [
"Apache-2.0"
] | 2 | 2021-11-22T06:43:39.000Z | 2021-12-10T13:54:38.000Z | readme.md | manfredsteyer/idsvr4-demo-2021 | 4d573ba628b4db05e1dccbf1a702821269ac5eb0 | [
"Apache-2.0"
] | null | null | null | readme.md | manfredsteyer/idsvr4-demo-2021 | 4d573ba628b4db05e1dccbf1a702821269ac5eb0 | [
"Apache-2.0"
] | null | null | null | Modified fork of https://github.com/IdentityServer/IdentityServer4.Demo
| 36 | 71 | 0.847222 | yue_Hant | 0.519795 |
a6d799a03eed170d409a93718524d9ea05642bcf | 60 | md | Markdown | docker/runtime/ballerina/kubeless/Package.md | rich-jowett/kubeless | ab6f0c47e4dbcbc8226eb7e73f4897ff4e675a5f | [
"Apache-2.0"
] | 1 | 2019-02-28T12:41:26.000Z | 2019-02-28T12:41:26.000Z | docker/runtime/ballerina/kubeless/Package.md | rich-jowett/kubeless | ab6f0c47e4dbcbc8226eb7e73f4897ff4e675a5f | [
"Apache-2.0"
] | null | null | null | docker/runtime/ballerina/kubeless/Package.md | rich-jowett/kubeless | ab6f0c47e4dbcbc8226eb7e73f4897ff4e675a5f | [
"Apache-2.0"
] | null | null | null | # Kubeless
Types definition for Kubeless Events & Context.
| 15 | 47 | 0.783333 | eng_Latn | 0.645705 |
a6d7bba057ca07c58eee7033774f45e796d92839 | 1,643 | md | Markdown | sandbox/pubnub-example/CHANGELOG.md | rohitvishwakarma-sf/loopback4-microservice-catalog | b24c0ff3c874960d2ae2f16b42992fbc58fff633 | [
"MIT"
] | null | null | null | sandbox/pubnub-example/CHANGELOG.md | rohitvishwakarma-sf/loopback4-microservice-catalog | b24c0ff3c874960d2ae2f16b42992fbc58fff633 | [
"MIT"
] | null | null | null | sandbox/pubnub-example/CHANGELOG.md | rohitvishwakarma-sf/loopback4-microservice-catalog | b24c0ff3c874960d2ae2f16b42992fbc58fff633 | [
"MIT"
] | null | null | null | # Change Log
All notable changes to this project will be documented in this file.
See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
## 0.1.0 (2021-09-12)
* feat(sandbox): example of pubnub as a provider in notification service (#279) ([e30a0ed](https://github.com/sourcefuse/loopback4-microservice-catalog/commit/e30a0ed)), closes [#279](https://github.com/sourcefuse/loopback4-microservice-catalog/issues/279) [#208](https://github.com/sourcefuse/loopback4-microservice-catalog/issues/208) [#208](https://github.com/sourcefuse/loopback4-microservice-catalog/issues/208) [#0](https://github.com/sourcefuse/loopback4-microservice-catalog/issues/0) [#278](https://github.com/sourcefuse/loopback4-microservice-catalog/issues/278) [#211](https://github.com/sourcefuse/loopback4-microservice-catalog/issues/211) [#263](https://github.com/sourcefuse/loopback4-microservice-catalog/issues/263) [#280](https://github.com/sourcefuse/loopback4-microservice-catalog/issues/280) [#208](https://github.com/sourcefuse/loopback4-microservice-catalog/issues/208) [#208](https://github.com/sourcefuse/loopback4-microservice-catalog/issues/208) [#298](https://github.com/sourcefuse/loopback4-microservice-catalog/issues/298) [#208](https://github.com/sourcefuse/loopback4-microservice-catalog/issues/208) [#263](https://github.com/sourcefuse/loopback4-microservice-catalog/issues/263) [#280](https://github.com/sourcefuse/loopback4-microservice-catalog/issues/280) [#208](https://github.com/sourcefuse/loopback4-microservice-catalog/issues/208) [#208](https://github.com/sourcefuse/loopback4-microservice-catalog/issues/208)
| 182.555556 | 1,452 | 0.793061 | yue_Hant | 0.428724 |
a6d7da59226fb3d6f2f06b4b0774ed909c70b26b | 2,283 | md | Markdown | postgres/README.md | SimoTornioli/data-engineering | 377d67df5246297711485d096394990ad20db078 | [
"MIT"
] | null | null | null | postgres/README.md | SimoTornioli/data-engineering | 377d67df5246297711485d096394990ad20db078 | [
"MIT"
] | null | null | null | postgres/README.md | SimoTornioli/data-engineering | 377d67df5246297711485d096394990ad20db078 | [
"MIT"
] | null | null | null | # ETL for a Music Streaming App
### 1. Project Description
This project containts a few ETL scripts to create a Postgres database and to load streaming app data into it.
### 2. Database design
The database contains the following tables:
- *users*: dimension table containing users information, primary key: user_id
- *songs*: dimension table containing songs information, primary key: song_id
- *artists*: dimension table containing artists information, primary key: artist_id
- *time*: dimension table containing play-action timestamp information, primary key: start_time
- *songplays*: fact table that stores all the play events signed as "NextSong", primary_key: songplay_id
### 3. ETL Process
The ETL process is composed by 8 sequential steps:
1. Creating the database (sparkifydb) and the database tables, dropping them if they already exist.
3. Reading the song data from the json files stored in /data/song_data
4. Parsing the song data to retrieve songs and artists information, storing the information in the *songs* and *artists* tables
5. Reading the activity log data from the json files stored in /data/log_data
6. Filtering only activity type "NextSong"
7. Parsing the log data to retrieve times and users storing the information in the *time* and *users* tables
8. Creating the *songplays* table by aggregating the parsed log data, song_id (from songs) and artist_id (from artists).
### 4. Project Repository files
.
├── README.md
├── create_tables.py
├── data
│ ├── log_data
│ │ └── 2018
│ │ └── 11
│ │ ├── 2018-11-01-events.json
│ │ ├── ..
│ └── song_data
│ └── A
│ ├── A
│ │ ├── A
│ │ │ ├── TRAAAAW128F429D538.json
│ │ │ ├── ...
│ └── ...
├── etl.ipynb
├── etl.py
├── sql_queries.py
└── test.ipynb
### 5. How To Run the Project
1. move to the project folder in your commind line and run "python create_tables.py". This command will set up the database and tables (assuming you have postgres installed and the right user permissions)
2. run "python sql_queries.py". This command will parse the json files and will populate the database tables accordingly.
| 43.075472 | 204 | 0.672361 | eng_Latn | 0.984003 |
a6d81140ab2cbc4b19c1eb07222caa15d7c13fc0 | 3,680 | md | Markdown | wiki/python/DEVELOPER_GUIDE.md | tzemicheal/cuml | 377f3c2773e3fc64d93d3d64a3f2fcd6c8759044 | [
"Apache-2.0"
] | 1 | 2021-01-01T10:52:18.000Z | 2021-01-01T10:52:18.000Z | wiki/python/DEVELOPER_GUIDE.md | tzemicheal/cuml | 377f3c2773e3fc64d93d3d64a3f2fcd6c8759044 | [
"Apache-2.0"
] | null | null | null | wiki/python/DEVELOPER_GUIDE.md | tzemicheal/cuml | 377f3c2773e3fc64d93d3d64a3f2fcd6c8759044 | [
"Apache-2.0"
] | null | null | null | # cuML Python Developer Guide
This document summarizes guidelines and best practices for contributions to the python component of the library cuML, the machine learning component of the RAPIDS ecosystem. This is an evolving document so contributions, clarifications and issue reports are highly welcome.
## General
Please start by reading:
1. [CONTRIBUTING.md](../../CONTRIBUTING.md).
2. [C++ DEVELOPER_GUIDE.md](../cpp/DEVELOPER_GUIDE.md)
3. [Python cuML README.md](../../python/README.md)
## Thread safety
Refer to the section on thread safety in [C++ DEVELOPER_GUIDE.md](../cpp/DEVELOPER_GUIDE.md#thread-safety)
## Coding style
1. [PEP8](https://www.python.org/dev/peps/pep-0008) and [flake8](http://flake8.pycqa.org/en/latest/) is used to check the adherence to this style.
2. [sklearn coding guidelines](https://scikit-learn.org/stable/developers/contributing.html#coding-guidelines)
## Creating class for a new estimator or other ML algorithm
1. Make sure that this algo has been implemented in the C++ side. Refer to [C++ DEVELOPER_GUIDE.md](../cpp/DEVELOPER_GUIDE.md) for guidelines on developing in C++.
2. Refer to the [next section](DEVELOPER_GUIDE.md#creating-python-wrapper-class-for-an-existing-ml-algo) for the remaining steps.
## Creating python estimator wrapper class
1. Create a corresponding algoName.pyx file inside `python/cuml` folder.
2. Ensure that the folder structure inside here reflects that of sklearn's. Example, `pca.pyx` should be kept inside the `decomposition` sub-folder of `python/cuml`.
. Match the corresponding scikit-learn's interface as closely as possible. Refer to their [developer guide](https://scikit-learn.org/stable/developers/contributing.html#apis-of-scikit-learn-objects) on API design of sklearn objects for details.
3. Always make sure to have your class inherit from `cuml.Base` class as your parent/ancestor.
4. Ensure that the estimator's output fields follow the 'underscore on both sides' convention explained in the documentation of `cuml.Base`. This allows it to support configurable output types.
For an in-depth guide to creating estimators, see the [Estimator Guide](ESTIMATOR_GUIDE.md)
## Error handling
If you are trying to call into cuda runtime APIs inside `cuml.cuda`, in case of any errors, they'll raise a `cuml.cuda.CudaRuntimeError`. For example:
```python
from cuml.cuda import Stream, CudaRuntimeError
try:
s = Stream()
s.sync
except CudaRuntimeError as cre:
print("Cuda Error! '%s'" % str(cre))
```
## Logging
TBD
## Documentation
We mostly follow [PEP 257](https://www.python.org/dev/peps/pep-0257/) style docstrings for documenting the interfaces.
## Testing and Unit Testing
We use [https://docs.pytest.org/en/latest/]() for writing and running tests. To see existing examples, refer to any of the `test_*.py` files in the folder `cuml/test`.
## Device and Host memory allocations
TODO: talk about enabling RMM here when it is ready
## Asynchronous operations and stream ordering
If you want to schedule the execution of two algorithms concurrently, it is better to create two separate streams and assign them to separate handles. Finally, schedule the algorithms using these handles.
```python
import cuml
from cuml.cuda import Stream
s1 = Stream()
h1 = cuml.Handle()
h1.setStream(s1)
s2 = Stream()
h2 = cuml.Handle()
h2.setStream(s2)
algo1 = cuml.Algo1(handle=h1, ...)
algo2 = cuml.Algo2(handle=h2, ...)
algo1.fit(X1, y1)
algo2.fit(X2, y2)
```
To know more underlying details about stream ordering refer to the corresponding section of [C++ DEVELOPER_GUIDE.md](../../cpp/DEVELOPER_GUIDE.md#asynchronous-operations-and-stream-ordering)
## Multi GPU
TODO: Add more details.
| 49.72973 | 273 | 0.765761 | eng_Latn | 0.955579 |
a6d89d0366fce0150c70a465bbd4e8b1097783f4 | 1,501 | md | Markdown | README.md | freerunningtech/spree_inventory_sync | 738f2a2d450648f18c4b0cb0055534fa46245213 | [
"BSD-3-Clause"
] | null | null | null | README.md | freerunningtech/spree_inventory_sync | 738f2a2d450648f18c4b0cb0055534fa46245213 | [
"BSD-3-Clause"
] | null | null | null | README.md | freerunningtech/spree_inventory_sync | 738f2a2d450648f18c4b0cb0055534fa46245213 | [
"BSD-3-Clause"
] | null | null | null | SpreeInventorySync
===================
SpreeInventorySync provides functionality for importing inventory status from an external inventory system
More information can be found on the [wiki](https://github.com/freerunningtech/spree_inventory_sync/wiki)
Installation
------------
Add spree_inventory_sync to your Gemfile:
```rubygem
gem 'spree_inventory_sync', github: 'freerunningtech/spree_inventory_sync'
```
Bundle your dependencies and run the installation generator:
```shell
bundle
bundle exec rails g spree_inventory_sync:install
```
Configure your inventory sync by doing the following in your application:
In ``config/initializers/spree_inventory_sync.rb`
```ruby
Spree::InventorySync.configure do |config|
config.import_class = "" # A string containing the class to use for importing (i.e. Spree::InventorySync::Source::CoreWarhouse)
config.options = {} # A hash contianing options to be passed to the source
end
```
Support
-------
The following back ends are currently supported:
- Core Warehouse
Testing
-------
Be sure to bundle your dependencies and then create a dummy test app for the specs to run against.
```shell
bundle
bundle exec rake test_app
bundle exec rspec spec
```
When testing your applications integration with this extension you may use it's factories.
Simply add this require statement to your spec_helper:
```ruby
require 'spree_inventory_sync/factories'
```
Copyright (c) 2014 FreeRunning Technologies, released under the New BSD License
| 23.825397 | 129 | 0.767488 | eng_Latn | 0.94541 |
a6d9b169a16946ceb7af0bf60aa460d51c8f252a | 299 | md | Markdown | real_data/README.md | ZhaozhiQIAN/Single-Cause-Perturbation-NeurIPS-2021 | c1dd837bf4afc91d2a64a3afab759a21cbdc65cb | [
"MIT"
] | 8 | 2021-12-07T18:16:59.000Z | 2022-03-08T02:17:06.000Z | real_data/README.md | ZhaozhiQIAN/Single-Cause-Perturbation-NeurIPS-2021 | c1dd837bf4afc91d2a64a3afab759a21cbdc65cb | [
"MIT"
] | null | null | null | real_data/README.md | ZhaozhiQIAN/Single-Cause-Perturbation-NeurIPS-2021 | c1dd837bf4afc91d2a64a3afab759a21cbdc65cb | [
"MIT"
] | 1 | 2021-12-03T16:25:41.000Z | 2021-12-03T16:25:41.000Z | # COVID-19 Hospitalization in England Surveillance System (CHESS)
The semi-synthetic experiment in the paper uses the CHESS dataset, which is protected by a license (and cannot be shared here).
If you are interested in the dataset, please contact Public Health England (PHE) for more information.
| 59.8 | 127 | 0.799331 | eng_Latn | 0.99891 |
a6db0736b17451280caff5049cef63f382fe62b4 | 134 | md | Markdown | practice-micro-batch-framework/README.md | neko3cs/neko3cs-lab | b88a45e4918847232614c5d306bf0edec4311cf8 | [
"MIT"
] | null | null | null | practice-micro-batch-framework/README.md | neko3cs/neko3cs-lab | b88a45e4918847232614c5d306bf0edec4311cf8 | [
"MIT"
] | null | null | null | practice-micro-batch-framework/README.md | neko3cs/neko3cs-lab | b88a45e4918847232614c5d306bf0edec4311cf8 | [
"MIT"
] | null | null | null | # PlayMicroBatchFramework
MicroBatchFrameworkで遊んでみた
- [Cysharp/MicroBatchFramework](https://github.com/Cysharp/MicroBatchFramework)
| 22.333333 | 79 | 0.850746 | kor_Hang | 0.319566 |
a6db35fe39437a21c492f984b3ced04cb77558b0 | 122 | md | Markdown | case-studies.md | sighmon/open-archive.org-Website-2019 | 2fc9cd2472af9aa87c72a4f74e464672e8dc21ba | [
"CC-BY-3.0"
] | 3 | 2020-01-13T23:35:00.000Z | 2021-08-08T01:15:59.000Z | case-studies.md | sighmon/open-archive.org-Website-2019 | 2fc9cd2472af9aa87c72a4f74e464672e8dc21ba | [
"CC-BY-3.0"
] | 15 | 2020-05-06T00:54:23.000Z | 2022-03-01T13:08:22.000Z | case-studies.md | sighmon/open-archive.org-Website-2019 | 2fc9cd2472af9aa87c72a4f74e464672e8dc21ba | [
"CC-BY-3.0"
] | 6 | 2021-03-30T11:59:43.000Z | 2021-08-01T11:38:56.000Z | ---
layout: page
title: Case Studies
description:
permalink: /save/case-studies
---
<h1>Case Studies</h1>
<p>Text TK</p>
| 12.2 | 29 | 0.688525 | kor_Hang | 0.36988 |
a6dbc6f723b8b66e8da0d9633836035eb3e322a3 | 54 | md | Markdown | README.md | RescueStationCIC/Model4You | c2dd5480fdb8a66af71928ef6e98e6c52e5de049 | [
"MIT"
] | null | null | null | README.md | RescueStationCIC/Model4You | c2dd5480fdb8a66af71928ef6e98e6c52e5de049 | [
"MIT"
] | null | null | null | README.md | RescueStationCIC/Model4You | c2dd5480fdb8a66af71928ef6e98e6c52e5de049 | [
"MIT"
] | null | null | null | # Model4You
Parameterisable location aware AR display
| 18 | 41 | 0.851852 | eng_Latn | 0.848549 |
a6dc868e772c3da16b1524074eecc539b17c5e64 | 4,267 | md | Markdown | vendor/simplesamlphp/simplesamlphp/docs/simplesamlphp-metadata-extensions-rpi.md | tirazel/d8_composer_base | 6881fdaa306e8fc5f78f3a7f7c27449ab1687d3d | [
"MIT"
] | 1 | 2022-01-16T11:40:52.000Z | 2022-01-16T11:40:52.000Z | vendor/simplesamlphp/simplesamlphp/docs/simplesamlphp-metadata-extensions-rpi.md | tirazel/d8_composer_base | 6881fdaa306e8fc5f78f3a7f7c27449ab1687d3d | [
"MIT"
] | 19 | 2019-02-21T18:37:20.000Z | 2021-02-27T00:45:42.000Z | soe/acquia_dependencies/simplesamlphp/docs/simplesamlphp-metadata-extensions-rpi.md | SU-SOE/grunt-drupal-tasks | 6b56e589584cccd913a3903d9beb20701728b627 | [
"MIT"
] | 1 | 2019-12-04T10:33:30.000Z | 2019-12-04T10:33:30.000Z | SAML V2.0 Metadata Extensions for Registration and Publication Information
=============================
<!--
This file is written in Markdown syntax.
For more information about how to use the Markdown syntax, read here:
http://daringfireball.net/projects/markdown/syntax
-->
* Author: Jaime Perez [[email protected]](mailto:[email protected])
<!-- {{TOC}} -->
This is a reference for the SimpleSAMLphp implementation of the [SAML
V2.0 Metadata Extensions for Registration and Publication Information](http://docs.oasis-open.org/security/saml/Post2.0/saml-metadata-rpi/v1.0/saml-metadata-rpi-v1.0.html)
defined by OASIS.
This extension aims to provide information about the registrars and publishers of the metadata themselves, and it is therefore
available throught different endpoints and modules that provide metadata all along SimpleSAMLphp. More specifically, this
extension can be used for:
- metadata published for a [hosted service provider](./saml:sp).
- metadata published for a [hosted identity provider](./simplesamlphp-reference-idp-hosted).
- metadata collected and published by means of the [`aggregator`](./aggregator:aggregator) or [`aggregator2`](./aggregator2:aggregator2) modules.
Currently, only the `<mdrpi:RegistrationInfo>` element is supported.
Depending on the metadata set you want to add this extension to, you will have to configure it on the corresponding
configuration file:
- `metadata/saml20-idp-hosted.php` for hosted identity providers.
- `config/authsources.php` for hosted service providers.
- `config/module_aggregator.php` for the `aggregator` module.
- `config/module_aggregator2.php` for the `aggregator2` module.
RegistrationInfo Items
----------------------
The configuration is the same for all the different files, and consists of a single directive called `RegistrationInfo`, which
**must** be an indexed array with the following options:
`authority`
: A string containing an identifier of the authority who has registered this metadata. This parameter is **mandatory**.
`instant`
: A string containing the instant when the entity or entities where registered by the authority. This parameter is
optional, and must be expressed in the UTC timezone with the *zulu* (`Z`) timezone identifier. If omitted, there will be no
`registrationInstant` in the resulting metadata, except in the `aggregator2` module, which will use the instant when the metadata
was generated.
`policies`
: An indexed array containing URLs pointing to the policy under which the entity or entities where registered. Each
index must be the language code corresponding to the language of the URL. This parameter is optional, and will be omitted in the
resulting metadata if not configured.
Examples
--------
Service Provider:
'default-sp' => [
'saml:SP',
'entityID' => NULL,
...
'RegistrationInfo' => [
'authority' => 'urn:mace:sp.example.org',
'instant' => '2008-01-17T11:28:03.577Z',
'policies' => ['en' => 'http://sp.example.org/policy', 'es' => 'http://sp.example.org/politica'],
],
],
Identity Provider:
$metadata['__DYNAMIC:1__'] = [
'host' => '__DEFAULT__',
...
'RegistrationInfo' => [
'authority' => 'urn:mace:idp.example.org',
'instant' => '2008-01-17T11:28:03.577Z',
],
];
`aggregator` module:
$config = [
'aggregators' => [
...
],
'maxDuration' => 60*60*24*5,
'reconstruct' => FALSE,
...
'RegistrationInfo' => [
'authority' => 'urn:mace:example.federation',
'instant' => '2008-01-17T11:28:03Z',
'policies' => ['en' => 'http://example.org/federation_policy', 'es' => 'https://example.org/politica_federacion'],
],
];
`aggregator2` module:
$config = [
'example.org' => [
'sources' => [
...
],
'RegistrationInfo' => [
'authority' => 'urn:mace:example.federation',
'policies' => ['en' => 'http://example.org/federation_policy', 'es' => 'https://example.org/politica_federacion'],
],
],
];
| 37.761062 | 171 | 0.657605 | eng_Latn | 0.950447 |
a6ddb222dc115b1187b6153e19c847beec417ae5 | 182 | md | Markdown | README.md | SheriffWoody/HDSegmentScroll | 4d93127e7f69274011e2efada486e49d72457d40 | [
"MIT"
] | null | null | null | README.md | SheriffWoody/HDSegmentScroll | 4d93127e7f69274011e2efada486e49d72457d40 | [
"MIT"
] | null | null | null | README.md | SheriffWoody/HDSegmentScroll | 4d93127e7f69274011e2efada486e49d72457d40 | [
"MIT"
] | null | null | null | # HDSegmentScroll
## 安装
>`pod 'HDSegmentScroll'`
## 使用
HDSegmentControl支持夜间模式，在appdelegate中引入夜间模式配置文件
```obj-c
[DKColorTable sharedColorTable].file = @"HDColorTable.txt";
```
| 12.133333 | 59 | 0.730769 | yue_Hant | 0.698512 |
a6ddcb2df38f57c6f318ab0d24abe82af7e4a17c | 2,798 | md | Markdown | _posts/2019-04-09-Download-plant-physiology-by-salisbury-and-ross-pdf-download.md | Camille-Conlin/26 | 00f0ca24639a34f881d6df937277b5431ae2dd5d | [
"MIT"
] | null | null | null | _posts/2019-04-09-Download-plant-physiology-by-salisbury-and-ross-pdf-download.md | Camille-Conlin/26 | 00f0ca24639a34f881d6df937277b5431ae2dd5d | [
"MIT"
] | null | null | null | _posts/2019-04-09-Download-plant-physiology-by-salisbury-and-ross-pdf-download.md | Camille-Conlin/26 | 00f0ca24639a34f881d6df937277b5431ae2dd5d | [
"MIT"
] | null | null | null | ---
layout: post
comments: true
categories: Other
---
## Download Plant physiology by salisbury and ross pdf download book
She must have been teased thinking, and squealing brakes. Don't worry about Diamond. her aunt Geneva had said only the previous evening, who not only bottom of the lowest drawer. "Everyone calls me Jorry. " Here's the deal: If she fled to her room and barricaded the door, "I'm not. At a considerable plant physiology by salisbury and ross pdf download from the rivers it is for the most part Samoyeds is given above at page 100. On this account bathroom break, lacking a sprinkler system? When Victoria failed to answer the door, four aspirin. Luzula arctica BL. Nos. He had been invited. sometimes she sidled up to when she didn't have the nerve to approach it directlyвthe truth was that her pass before she noticed the pistol missing from the back of her closet, 1805-1806, 311 "Could I have more lemonade?" Leilani asked, in which I rest her eyes, and who would have expected it of a rich man, but it might recur when he "Clones," Curtis mutters. considerable depth in the open sea is perhaps uncertain, 'O Tuhfet es Sudour. to merely in passing. "This isn't wagering," Grace declared. the boatmen. Shadows flourished. "I'm with my dad. atrophy a long time ago, I would not think so, ii. It was telling on the crew of the Burroughs. plant physiology by salisbury and ross pdf download eye. In dully glowing dials to enter into senseless conversations with me, 21. "What'd you say, "who is this that presumeth upon me with this letter. Instead he took off his fur hat and laid it upon his heart, though it lay out under the bright sky and far above the peat soils. I came on board human hair. "I'd like to. She would have walked it a hundred times and still not been satisfied, and considering the injury she might have Forgetting to use the brace's mechanical knee joint, the police would have been at Junior's doorstep in minutes, suspicious of generalizings. "I love you, incomparably beautiful volcanic cone raise place, which was known as the Spindle and extended for over six miles from the base of the magnetic ram scoop funnel at its nose to the enormous parabolic reaction dish forming its tail. All but a few of them freeze at the sight of the Friday, explosions of dynamite hauling trucks He stopped to listen, feign thyself plant physiology by salisbury and ross pdf download again this night and lie down, which some blind people claimed to have. He wasn't wearing a shoe, and so is Phimie. All under this part of the city is that rock. She had appointed Those words, or selections from the most famous of the productions of version of the real world, is this fine young fella the Jay you were telling me about?" Hanlon asked! All appeared could be clean. | 310.888889 | 2,673 | 0.785561 | eng_Latn | 0.999909 |
a6de13238a829de2866fd730b0d1e5728da37de2 | 2,238 | md | Markdown | Flutter/BuildMode.md | DDYFlutter/LearnFlutter | 457c8b01b386bd19c5d81fa6311b363f65eacf6b | [
"MIT"
] | 8 | 2019-08-28T14:06:05.000Z | 2021-09-30T09:56:51.000Z | Flutter/BuildMode.md | DDYFlutter/LearnFlutter | 457c8b01b386bd19c5d81fa6311b363f65eacf6b | [
"MIT"
] | null | null | null | Flutter/BuildMode.md | DDYFlutter/LearnFlutter | 457c8b01b386bd19c5d81fa6311b363f65eacf6b | [
"MIT"
] | 2 | 2019-09-10T06:09:02.000Z | 2019-09-11T13:16:01.000Z | #### 四种运行模式
Flutter在编译App时有4种模式：Debug、Release、Profile、test，且编译阶段完全独立。但在移动端开发中只支持前三种，test只适用于桌面环境
> ##### Debug
Dubug模式特点
* App可被安装到真机、模拟器、仿真器上进行调试
* 开启断言
* 开启服务扩展(源码runApp->WidgetsFlutterBinding->initServiceExtension)
* 开启debuger aids 类似DevTools的工具可以连接到应用程序的进程中(如 Dart Observatory用来分析和调试，可以debugger，还可以检测性能等)
* 开启debugging信息
* 采用JIT编译，支持热重载HotRload
* 优化了快速develop/run循环，但没有优化执行速度、二进制大小和部署
* 可能存在性能上低效甚至卡顿
* 通过sky/tools/gn --android 或 sky/tools/gn --ios 来build
* 有时候也被叫做 checked 模式 或 slow模式
* 构建方式：flutter run 或 IDE中Debug->Start Debugging/Start Without Debugging
> ##### Release
Release模式特点
* 只能真机上运行，不能再模拟器、仿真器上调试
* 采用AOT编译，不能热重载(HotRload)
* 会关闭所有断言和debugging信息，及关闭所有debugger工具
* 禁用所有debugging aids 和服务扩展
* 优化了快速启动、快速执行和减小包体积
* 该模式目的是为了部署给最终用户使用
* 通过sky/tools/gn --android/--ios --runtime-mode=release来build
* 构建方式：
1. 命令flutter run --release 就是运行的该模式
2. IDE点击设备选择后面的main.dart按钮(默认文件)Edit Configurations 然后在Additional arguments加上 --release
3. 还可以用上面步骤增加主文件 如 main_debug.dart main_release.dart然后选择对应文件执行
4. 还可以Run->Flutter Run 'main.dart' in Release Mode
5. 使用flutter build apk/ios 构建相应release包
> ##### Profile
Profile模式是专门监控性能的。在Debug模式下，开启了很多额外功能，不能反映实际性能，但在Release模式下却没有监控功能，所以就有了Profile模式。
* 基本和Release一致，但启用了服务扩展和tracing，以及一些为了最低限度支持tracing运行的东西（如可以连接observatory到进程）
* Profile模式采用AOT编译，没有热重载(HotRload)
* web平台：资源文件没有被压缩，但整体性能已经优化
* flutter run --profile就是以这种模式运行的
* 通过sky/tools/gn --android/--ios --runtime-mode=profile来build
* 因为模拟器不能代表真实场景，所以不能在模拟器上运行
> ##### test
test模式特点
* test模式只能在桌面环境运行，基本和Debug模式一致
* flutter test 就是以该模式运行的
> ##### 判断是Debug还是Release
实际开发中，上面四种模式又分为两种：未优化的模式和优化过的模式。默认时未优化模式，如果要开启优化模式，build的时候命令行后面添加 --unoptimized 参数
我们可以用 dart.vm.product环境标识得知运行环境是否是Production
```
const bool inProduction = bool.fromEnviroment(dart.vm.product')
```
当运行在Release环境时，inProduction为true，否则(Debug/Profile)为false
* Release：const bool.fromEnvironment("dart.vm.product") = true；
* Debug：assert(() { ...; return true; });断言语句会被执行；
* Profile：上面的两种情况均不会发生。
> ##### 参考文章
[github flutter mode](https://github.com/flutter/flutter/wiki/Flutter's-modes)
[flutter 1.2 官方开发文档](https://www.bookstack.cn/read/flutter-1.2-zh/32f04f19acb7665f.md)
[flutter.dev build-modes](https://flutter.dev/docs/testing/build-modes) | 28.329114 | 90 | 0.789544 | yue_Hant | 0.864235 |
a6de4158b010566cad17a6bbe56910c2d65a5aae | 981 | md | Markdown | Day 6 - Book Author/README.md | POliveira29/30-Days-30-Sites | eef189907802eee187ca88720dec85a0a5dd4fa8 | [
"MIT"
] | null | null | null | Day 6 - Book Author/README.md | POliveira29/30-Days-30-Sites | eef189907802eee187ca88720dec85a0a5dd4fa8 | [
"MIT"
] | null | null | null | Day 6 - Book Author/README.md | POliveira29/30-Days-30-Sites | eef189907802eee187ca88720dec85a0a5dd4fa8 | [
"MIT"
] | null | null | null | 
<p align="center">Desafio 30 dias, 30 sites | Dia 6 - Autor de Livro</p>
## 🚀 Tecnologias
* [HTML5](https://developer.mozilla.org/pt-BR/docs/Web/HTML)
* [CSS3](https://developer.mozilla.org/pt-BR/docs/Web/CSS)
* [JavaScript](https://developer.mozilla.org/pt-BR/docs/Web/JavaScript)
## 💻 Projeto
É um site de um autor de livro, contendo suas obras, vídeos do seu canal, sobre ele.
## 🎨 Layout
Feito com base no site [James Patterson](https://www.jamespatterson.com/?utm_source=newsletter&utm_medium=email&utm_campaign=30_days_30_sites_day_6&utm_term=2021-02-11)
## Utilitários
- Fontes: [Libre Baskerville](https://fonts.google.com/specimen/Libre+Baskerville), [Roboto](https://fonts.google.com/specimen/Roboto), [Sacramento](https://fonts.google.com/specimen/Sacramento), [Oswald](https://fonts.google.com/specimen/Oswald)
| 46.714286 | 250 | 0.762487 | yue_Hant | 0.315919 |
a6df47cb32a73f0541fdb249e051500b6c617ba1 | 707 | md | Markdown | docs/scope/subOrFuncScope.md | lkl22/ExcelVbaStudy | b5e146b13b5c1a1ccbb3c386d5ecf68d4f5803ec | [
"Apache-2.0"
] | 2 | 2020-08-12T08:52:23.000Z | 2020-10-31T08:35:37.000Z | docs/scope/subOrFuncScope.md | lkl22/ExcelVbaStudy | b5e146b13b5c1a1ccbb3c386d5ecf68d4f5803ec | [
"Apache-2.0"
] | null | null | null | docs/scope/subOrFuncScope.md | lkl22/ExcelVbaStudy | b5e146b13b5c1a1ccbb3c386d5ecf68d4f5803ec | [
"Apache-2.0"
] | null | null | null | # VBA 过程或函数作用域
* [1.模块作用域](#模块作用域)
* [2.工程作用域](#工程作用域)
* [3.全局作用域](#全局作用域)
## <a name="模块作用域">1.模块作用域</a>
在模块中，使用 `Private` 关键词声明的过程或函数，具备模块作用域，只能在当前模块中使用。
```vba
Private Sub Test()
End Sub
```
## <a name="工程作用域">2.工程作用域</a>
在模块中，顶部声明 `Option Private Module` 修饰语句，并且直接声明或使用 `Public` 关键词声明的过程或函数，具备工程作用域，在当前工程的所有模块中使用。
```vba
Option Private Module
Sub Test1()
End Sub
Public Sub Test2()
End Sub
```
以上例子中，Test1 过程和 Test2 过程均具备工程作用域。**由于直接声明和使用关键词 Public 是等效的，因此可以省略 Public 关键词**。
## <a name="全局作用域">3.全局作用域</a>
在模块中，直接声明或使用 `Public` 关键词声明的过程或函数，具备全局作用域。例如，
```vba
Sub Test1()
End Sub
Public Sub Test2()
End Sub
```
以上例子中，`Test1` 过程和 `Test2` 过程均具备全局作用域，可以在打开的任何一个工作簿中使用。
此外，它们还能直接在工作簿宏列表中执行。
| 14.729167 | 92 | 0.697313 | yue_Hant | 0.899212 |
a6e0dbc5e8291465e23fe4a682e737fef90dd118 | 52,026 | md | Markdown | maximo/maximo调整到指定页或行/README.md | shoukaiseki/blogdoc | 0417ad53cb0c5069c1e85f60f9e7b4e40a541c42 | [
"Apache-2.0"
] | 1 | 2018-07-13T07:01:32.000Z | 2018-07-13T07:01:32.000Z | maximo/maximo调整到指定页或行/README.md | shoukaiseki/blogdoc | 0417ad53cb0c5069c1e85f60f9e7b4e40a541c42 | [
"Apache-2.0"
] | null | null | null | maximo/maximo调整到指定页或行/README.md | shoukaiseki/blogdoc | 0417ad53cb0c5069c1e85f60f9e7b4e40a541c42 | [
"Apache-2.0"
] | null | null | null | # maximo调整到指定页或行
主列表默认显示
按下第5页按钮之后
按下第205条记录按钮之后
## item.xml源代码
```Xml
<?xml version="1.0" encoding="UTF-8"?>
<presentation apphelp="com.ibm.mbs.doc,item/c_item_master_app.html" beanclass="org.shoukaiseki.webclient.beans.test.TestItemAppBean" id="item" keyattribute="itemnum" mboname="ITEM" resultstableid="results_showlist" version="7.1.0.0">
<page id="mainrec">
<include id="pageHeader"/>
<clientarea id="clientarea">
<tabgroup id="maintabs" style="form">
<tab default="true" id="results" label="列表" type="list">
<menubar event="search" id="actiontoolbar" sourcemethod="getAppSearchOptions"/>
<buttongroup id="main_altitem_table_2bb">
<pushbutton default="true" id="main_altitem_table_2_1bb" label="第5页" mxevent="moveto5page"/>
<pushbutton id="main_altitem_table_2_1bb2" label="第205条记录" mxevent="moveto205row"/>
<pushbutton id="main_altitem_table_2_1bb3" label="下一条记录" mxevent="movetonextrow"/>
</buttongroup>
<table beanclass="psdi.webclient.beans.item.ItemResultsBean" id="results_showlist" inputmode="readonly" label="项目" mboname="ITEM" selectmode="multiple">
<tablebody displayrowsperpage="20" filterable="true" filterexpanded="true" id="results_showlist_tablebody">
<tablecol dataattribute="itemnum" filterable="false" hidden="false" id="results_showlist_tablebody_1" mxevent="toggleselectrow" mxevent_desc="选择行{0}" sortable="false" type="event"/>
<tablecol dataattribute="itemnum" id="results_showlist_tablebody_2" menutype="item" mxevent="selectrecord" mxevent_desc="转到 %1" type="link" usefieldsizegroup="false"/>
<tablecol dataattribute="description" id="results_showlist_tablebody_3"/>
<tablecol dataattribute="commoditygroup" id="results_showlist_tablebody_4"/>
<tablecol dataattribute="rotating" id="results_showlist_tablebody_5"/>
<tablecol dataattribute="iskit" id="results_showlist_tablebody_6"/>
<tablecol dataattribute="conditionenabled" id="results_showlist_tablebody_7"/>
<tablecol dataattribute="status" id="results_showlist_tablebody_7a"/>
<tablecol filterable="false" hidden="false" id="results_bookmark" mxevent="BOOKMARK" mxevent_desc="添加到书签" mxevent_icon="btn_addtobookmarks.gif" sortable="false" type="event"/>
</tablebody>
</table>
</tab>
<tab id="main" label="项目" type="insert">
<section border="true" id="main_gridd">
<sectionrow id="main_gridg">
<sectioncol id="main_gride">
<section id="main_gridf">
<multiparttextbox dataattribute="ITEMNUM" descdataattribute="DESCRIPTION" id="main_grid2_1" longdescription="true" menutype="item"/>
<textbox dataattribute="ITEMSETID" id="main_grid2_2"/>
<multiparttextbox dataattribute="COMMODITYGROUP" descdataattribute="COMMODITYGROUP.DESCRIPTION" descinputmode="readonly" id="main_grid2_3" longdescreadonly="true" lookup="commoditygroup"/>
<multiparttextbox dataattribute="COMMODITY" descdataattribute="COMMODITIES.DESCRIPTION" descinputmode="readonly" id="main_grid2_4" longdescreadonly="true" lookup="commodities"/>
<multiparttextbox applink="metergrp" dataattribute="GROUPNAME" descdataattribute="METERGROUP.DESCRIPTION" descinputmode="readonly" id="main_grid2_5" longdescreadonly="true" lookup="metergroup" menutype="normal"/>
<multiparttextbox applink="meter" dataattribute="METERNAME" descdataattribute="METER.DESCRIPTION" descinputmode="readonly" id="main_grid2_6" longdescreadonly="true" lookup="meter" menutype="normal"/>
<textbox dataattribute="LOTTYPE" id="main_grid2_7" lookup="valuelist"/>
<textbox dataattribute="MAXISSUE" id="main_grid2_8"/>
<textbox dataattribute="ORDERUNIT" id="main_grid2_9" lookup="measureunit"/>
<textbox dataattribute="ISSUEUNIT" id="main_grid2_10" lookup="measureunit"/>
<textbox dataattribute="MSDSNUM" id="main_grid2_11"/>
<textbox dataattribute="RECEIPTTOLERANCE" id="main_grid2_11A"/>
</section>
</sectioncol>
<sectioncol id="main_gridh">
<section border="false" id="main_attachments">
<attachments id="doclinks"/>
<textbox dataattribute="STATUS" id="main_grid2_12" inputmode="readonly"/>
<checkbox dataattribute="ROTATING" id="main_grid2_14"/>
<checkbox dataattribute="CONDITIONENABLED" id="main_grid2_15"/>
<checkbox dataattribute="ISKIT" id="main_grid2_16"/>
<checkbox dataattribute="CAPITALIZED" id="main_grid2_18"/>
<checkbox dataattribute="INSPECTIONREQUIRED" id="main_grid2_19"/>
<checkbox dataattribute="SPAREPARTAUTOADD" id="main_grid2_20"/>
<checkbox dataattribute="ATTACHONISSUE" id="main_grid2_21"/>
<checkbox dataattribute="TAXEXEMPT" id="main_grid2_22"/>
</section>
</sectioncol>
<sectioncol id="main_gridj">
<section id="main_recordimage">
<recordimage height="120" id="main_recordimage_1" label="单击以实际大小查看图像" width="120"/>
</section>
</sectioncol>
</sectionrow>
</section>
<buttongroup id="main_altitem_table_2aa">
<pushbutton default="true" id="main_altitem_table_2_1aa" label="测试" mxevent="ASUS"/>
</buttongroup>
<table id="main_altitem_table" label="替代项目" relationship="ALTITEM">
<tablebody displayrowsperpage="10" filterable="true" id="main_altitem_table_tablebody">
<tablecol filterable="false" hidden="false" id="main_altitem_table_tablebody_1" mxevent="toggledetailstate" mxevent_desc="显示详细信息" sortable="false" type="event"/>
<tablecol dataattribute="altitemnum" id="main_altitem_table_tablebody_2">
<textbox dataattribute="altitemnum" id="altitem_item" lookup="itemwithitemset" menutype="itemwithitemset"/>
</tablecol>
<tablecol dataattribute="altitem.description" id="main_altitem_table_tablebody_3" sortable="false">
<textbox dataattribute="altitem.description" id="altitem_desc" inputmode="readonly" longdescreadonly="true" lookup="longdesc"/>
</tablecol>
<tablecol dataattribute="altitem.commoditygroup" id="main_altitem_table_tablebody_4" linkedcontrolid="main_altitem_table_1_grid3_3" sortable="false"/>
<tablecol dataattribute="altitem.commodity" id="main_altitem_table_tablebody_7" linkedcontrolid="main_altitem_table_1_grid3_5" sortable="false"/>
<tablecol dataattribute="altitem.rotating" id="main_altitem_table_tablebody_5" linkedcontrolid="main_altitem_table_1_grid3_4" sortable="false"/>
<tablecol filterable="false" hidden="false" id="main_altitem_table_tablebody_6" mxevent="toggledeleterow" mxevent_desc="标记要删除的行" mxevent_icon="btn_garbage.gif" sortable="false" type="event"/>
</tablebody>
<tabledetails id="main_altitem_table_1">
<section id="main_altitem_table_1_grid3" label="详细信息">
<sectionrow id="main_altitem_table_1_grid3a">
<sectioncol id="main_altitem_table_1_grid3b">
<section id="main_altitem_table_1_grid3c">
<multiparttextbox dataattribute="altitemnum" defaultfocus="true" descdataattribute="altitem.description" descinputmode="readonly" id="main_altitem_table_1_grid3_1" longdescreadonly="true" lookup="itemwithitemset" menutype="itemwithitemset"/>
<textbox dataattribute="altitem.commoditygroup" id="main_altitem_table_1_grid3_3" inputmode="readonly"/>
</section>
</sectioncol>
<sectioncol id="main_altitem_table_1_grid3d">
<section id="main_altitem_table_1_grid3e">
<textbox dataattribute="altitem.commodity" id="main_altitem_table_1_grid3_5" inputmode="readonly"/>
<checkbox dataattribute="altitem.rotating" id="main_altitem_table_1_grid3_4" inputmode="readonly"/>
</section>
</sectioncol>
</sectionrow>
</section>
</tabledetails>
<buttongroup id="main_altitem_table_2">
<pushbutton default="true" id="main_altitem_table_2_1" label="新建行" mxevent="addrow"/>
</buttongroup>
</table>
<table id="main_conditioncode_table" label="条件代码" relationship="ITEMCONDITION">
<tablebody displayrowsperpage="10" filterable="true" id="main_conditioncode_table_tablebody">
<tablecol filterable="false" hidden="false" id="main_conditioncode_table_tablebody_1" mxevent="toggledetailstate" mxevent_desc="显示详细信息" sortable="false" type="event"/>
<tablecol dataattribute="conditioncode" id="main_conditioncode_table_tablebody_2">
<textbox dataattribute="conditioncode" id="main_conditioncode_table_tablebody_2a" lookup="conditioncode"/>
</tablecol>
<tablecol dataattribute="description" id="main_conditioncode_table_tablebody_3">
<textbox dataattribute="description" id="main_conditioncode_table_tablebody_3a" lookup="longdesc"/>
</tablecol>
<tablecol dataattribute="condrate" id="main_conditioncode_table_tablebody_4"/>
<tablecol filterable="false" hidden="false" id="main_conditioncode_table_tablebody_5" mxevent="toggledeleterow" mxevent_desc="标记要删除的行" mxevent_icon="btn_garbage.gif" sortable="false" type="event"/>
</tablebody>
<tabledetails id="main_conditioncode_table_1">
<section id="main_conditioncode_table_1_grid3" label="详细信息">
<sectionrow id="main_conditioncode_table_1_grid3_row">
<sectioncol id="main_conditioncode_table_1_grid3_row_col1">
<section id="main_conditioncode_table_1_grid3_row_col1_sec">
<multiparttextbox dataattribute="conditioncode" defaultfocus="true" descdataattribute="description" id="main_conditioncode_table_1_grid3_1" lookup="conditioncode"/>
</section>
</sectioncol>
<sectioncol id="main_conditioncode_table_1_grid3_row_col2">
<section id="main_conditioncode_table_1_grid3_row_col2_sec">
<textbox dataattribute="condrate" id="main_conditioncode_table_1_grid3_3"/>
</section>
</sectioncol>
</sectionrow>
</section>
</tabledetails>
<buttongroup id="main_conditioncode_table_2">
<pushbutton default="true" id="main_conditioncode_table_2_1" label="新建行" mxevent="addrow"/>
</buttongroup>
</table>
</tab>
<tab id="storeroom" label="库房">
<section border="true" id="store_grida">
<sectionrow id="store_grida_1">
<sectioncol id="store_grida_1_1">
<section id="store_grida_1_1_1">
<multiparttextbox dataattribute="ITEMNUM" descdataattribute="DESCRIPTION" id="store_grid2_1" longdescription="true" menutype="item"/>
</section>
</sectioncol>
<sectioncol id="store_gridb">
<section id="store_gridc">
<textbox dataattribute="ITEMSETID" id="store_grid2_4"/>
</section>
</sectioncol>
</sectionrow>
</section>
<table id="storeroom_inventorytable" label="库房信息" relationship="INVENTORY">
<tablebody displayrowsperpage="10" filterable="true" id="storeroom_inventorytable_tablebody">
<tablecol dataattribute="location" id="storeroom_inventorytable_tablebody_1"/>
<tablecol dataattribute="category" id="storeroom_inventorytable_tablebody_2"/>
<tablecol dataattribute="invcost_cond.stdcost" id="storeroom_inventorytable_tablebody_3" inputmode="readonly" sortable="false"/>
<tablecol dataattribute="invcost_cond.avgcost" id="storeroom_inventorytable_tablebody_4" inputmode="readonly" sortable="false"/>
<tablecol dataattribute="invcost_cond.lastcost" id="storeroom_inventorytable_tablebody_5" inputmode="readonly" sortable="false"/>
<tablecol dataattribute="lifofifocost" id="storeroom_inventorytable_tablebody_6" inputmode="readonly" label="后进先出/先进先出单位成本" sortable="false"/>
<tablecol dataattribute="curbaltotal" filterable="false" id="storeroom_inventorytable_tablebody_7" sortable="false"/>
<tablecol dataattribute="binnum" id="storeroom_inventorytable_tablebody_8"/>
<tablecol dataattribute="status" id="storeroom_inventorytable_tablebody_9"/>
<tablecol dataattribute="siteid" id="storeroom_inventorytable_tablebody_10"/>
</tablebody>
</table>
</tab>
<tab id="vendors" label="供应商">
<section border="true" id="vendor_grida">
<sectionrow id="vendor_grida_1">
<sectioncol id="vendor_grida_1_1">
<section id="vendor_grida_1_1_1">
<multiparttextbox dataattribute="ITEMNUM" descdataattribute="DESCRIPTION" id="vendor_grid2_1" longdescription="true" menutype="item"/>
</section>
</sectioncol>
<sectioncol id="vendor_gridb">
<section id="vendor_gridc">
<textbox dataattribute="ITEMSETID" id="vendor_grid2_4"/>
</section>
</sectioncol>
</sectionrow>
</section>
<table id="vendors_prec_table" label="供应商" relationship="INVVENDOR" startrow="0">
<tablebody displayrowsperpage="5" filterable="true" id="vendors_prec_table_tablebody">
<tablecol filterable="false" hidden="false" id="vendors_prec_table_tablebody_1" mxevent="toggledetailstate" mxevent_desc="显示详细信息" sortable="false" type="event"/>
<tablecol applink="company" applinkkey="company" dataattribute="vendor" id="vendors_prec_table_tablebody_2" lookup="companies" menutype="normal"/>
<tablecol applink="company" dataattribute="manufacturer" id="vendors_prec_table_tablebody_3" lookup="companies" menutype="normal" smartfilloff="true"/>
<tablecol dataattribute="modelnum" id="vendors_prec_table_tablebody_4"/>
<tablecol dataattribute="catalogcode" id="vendors_prec_table_tablebody_5"/>
<tablecol dataattribute="lastcost" id="vendors_prec_table_tablebody_8"/>
<tablecol dataattribute="lastdate" id="vendors_prec_table_tablebody_9" lookup="datelookup"/>
<tablecol dataattribute="orderunit" id="vendors_prec_table_tablebody_10" lookup="measureunit"/>
<tablecol dataattribute="orgid" id="vendors_prec_table_tablebody_6" lookup="org"/>
<tablecol dataattribute="siteid" id="vendors_prec_table_tablebody_7" lookup="site"/>
<tablecol filterable="false" hidden="false" id="vendors_prec_table_tablebody_11" mxevent="toggledeleterow" mxevent_desc="标记要删除的行" mxevent_icon="btn_garbage.gif" sortable="false" type="event"/>
</tablebody>
<tabledetails id="vendors_prec_table_1">
<section id="vendors_prec_table_1_grid9" label="详细信息">
<sectionrow id="vendors_prec_table_1_grid9_row">
<sectioncol id="vendors_prec_table_1_grid9_row_col1">
<section id="vendors_prec_table_1_grid9_row_col1_sec">
<multiparttextbox applink="company" applinkkey="company" dataattribute="vendor" defaultfocus="true" descdataattribute="vendor.name" descinputmode="readonly" id="vendors_prec_table_1_grid9_1" longdescreadonly="true" lookup="companies" menutype="normal" title="供应商表窗口"/>
<multiparttextbox applink="company" dataattribute="manufacturer" descdataattribute="manufacturer.name" descinputmode="readonly" id="vendors_prec_table_1_grid9_3" longdescreadonly="true" lookup="companies" menutype="normal" smartfilloff="true" title="制造商表窗口"/>
<textbox dataattribute="modelnum" id="vendors_prec_table_1_grid9_5" title="型号表窗口"/>
<textbox dataattribute="catalogcode" id="vendors_prec_table_1_grid9_6" title="目录代码表窗口"/>
<textbox dataattribute="promdeliverytime" id="vendors_prec_table_1_grid9_7" title="承诺交货期表窗口"/>
<textbox dataattribute="tax1code" id="vendors_prec_table_1_grid9_11" lookup="taxcode" title="税代码表窗口"/>
<textbox dataattribute="vendor.currencycode" id="vendors_prec_table_1_grid9_8" inputmode="readonly" title="当前代码表窗口"/>
<textbox dataattribute="RECEIPTTOLERANCE" id="vendors_prec_table_1_grid9_11A"/>
<checkbox dataattribute="isdefault" id="vendors_prec_table_1_grid9_13" title="缺省供应商表窗口"/>
</section>
</sectioncol>
<sectioncol id="vendors_prec_table_1_grid9_row_col2">
<section id="vendors_prec_table_1_grid9_row_col2_sec">
<checkbox dataattribute="vendor.disabled" id="vendors_prec_table_1_grid9_12" inputmode="readonly" title="被取消资格的供应商表窗口"/>
<textbox dataattribute="lastcost" id="vendors_prec_table_1_grid9_9" title="最终价格表窗口"/>
<textbox dataattribute="lastdate" id="vendors_prec_table_1_grid9_10" lookup="datelookup" title="上次订购日期表窗口"/>
<textbox dataattribute="orderunit" id="vendors_prec_table_1_grid9_15" lookup="measureunit" title="订购单位表窗口"/>
<textbox dataattribute="catalogwebpage" id="vendors_prec_table_1_grid9_14" title="目录 Web 页面表窗口"/>
<checkbox dataattribute="TAXEXEMPT" id="vendors_prec_table_1_grid9_14a"/>
<textbox dataattribute="orgid" id="vendors_prec_table_1_grid9_16" lookup="org"/>
<textbox dataattribute="siteid" id="vendors_prec_table_1_grid9_17" lookup="site"/>
</section>
</sectioncol>
</sectionrow>
</section>
</tabledetails>
<buttongroup id="vendors_prec_table_2">
<pushbutton default="true" id="vendors_prec_table_2_1" label="新建行" mxevent="addrow"/>
</buttongroup>
</table>
</tab>
<tab id="specification" label="规范">
<section border="true" id="specifications_grid2_row_col1_sec">
<multiparttextbox dataattribute="ITEMNUM" descdataattribute="DESCRIPTION" id="specification_grid2_1" menutype="item"/>
<textbox applink="assetcat" dataattribute="CLASSSTRUCTURE.HIERARCHYPATH" id="specification_grid3_1_1_3" menutype="classification" ondatachange="resetchildren"/>
<textbox dataattribute="CLASSSTRUCTURE.description_class" id="specification_grid3_1_1_4" lookup="classification" ondatachange="resetchildren"/>
</section>
<table id="specification_itemspectable" label="规范" orderby="displaysequence" relationship="ITEMSPECCLASS">
<tablebody displayrowsperpage="10" filterable="true" id="specification_itemspectable_tablebody">
<tablecol filterable="false" hidden="false" id="specification_itemspectable_tablebody_1" mxevent="toggledetailstate" mxevent_desc="显示详细信息" sortable="false" type="event"/>
<tablecol dataattribute="assetattrid" id="specification_itemspectable_tablebody_2" lookup="assetattribute"/>
<tablecol dataattribute="assetattribute.description" id="specification_itemspectable_tablebody_3" inputmode="readonly" showfilterfield="true" sortable="false"/>
<tablecol dataattribute="assetattribute.datatype" id="specification_itemspectable_tablebody_4" linkedcontrolid="specification_itemspectable_1_griddetails_3" showfilterfield="true" sortable="false"/>
<tablecol dataattribute="alnvalue" id="specification_itemspectable_tablebody_5" linkedcontrolid="specification_itemspectable_1_griddetails_4"/>
<tablecol dataattribute="numvalue" id="specification_itemspectable_tablebody_6" linkedcontrolid="specification_itemspectable_1_griddetails_5"/>
<tablecol dataattribute="measureunitid" id="specification_itemspectable_tablebody_7" linkedcontrolid="specification_itemspectable_1_griddetails_6"/>
<tablecol dataattribute="tablevalue" id="specification_itemspectable_tablebody_8" linkedcontrolid="specification_itemspectable_1_griddetails_5a"/>
<tablecol filterable="false" hidden="false" id="specification_itemspectable_tablebody_9" mxevent="toggledeleterow" mxevent_desc="标记要删除的行" mxevent_icon="btn_garbage.gif" sortable="false" type="event"/>
</tablebody>
<tabledetails id="specification_itemspectable_1">
<section id="specification_itemspectable_1_griddetails" label="详细信息">
<sectionrow id="specifications_specifications_table_1_griddetails1_row">
<sectioncol id="specifications_specifications_table_1_griddetails1_row_col1">
<section id="specifications_specifications_table_1_griddetails1_row_col1_sec">
<multiparttextbox dataattribute="assetattrid" defaultfocus="true" descdataattribute="assetattribute.description" descinputmode="readonly" id="specification_itemspectable_1_griddetails_1" lookup="assetattribute"/>
<textbox dataattribute="assetattribute.datatype" id="specification_itemspectable_1_griddetails_3" inputmode="readonly"/>
</section>
</sectioncol>
<sectioncol id="specifications_specifications_table_1_griddetails1_row_col2">
<section id="specifications_specifications_table_1_griddetails1_row_col2_sec">
<textbox dataattribute="alnvalue" id="specification_itemspectable_1_griddetails_4" lookup="alndomain" smartfilloff="true"/>
<textbox dataattribute="numvalue" id="specification_itemspectable_1_griddetails_5" lookup="numericdomain" smartfilloff="true"/>
<textbox dataattribute="measureunitid" id="specification_itemspectable_1_griddetails_6" lookup="measureunit"/>
<textbox dataattribute="tablevalue" id="specification_itemspectable_1_griddetails_5a" menutype="normal"/>
<textbox dataattribute="section" id="specification_itemspectable_1_griddetails_7"/>
<textbox dataattribute="classspec.inheritedfrom" id="specification_itemspectable_1_griddetails_5b" inputmode="readonly"/>
<textbox dataattribute="classspec.applydownhier" id="specification_itemspectable_1_griddetails_5c" inputmode="readonly"/>
</section>
</sectioncol>
</sectionrow>
</section>
</tabledetails>
<buttongroup id="specification_itemspectable_2">
<pushbutton default="true" id="specification_itemspectable_2_1" label="新建行" mxevent="addrow"/>
</buttongroup>
</table>
</tab>
<tab id="ias_tab" label="项目组装结构">
<datasrc beanclass="psdi.webclient.beans.item.TopItemStructBean" id="ias" parentdatasrc="MAINRECORD" relationship="TOPITEMSTRUCT_1"/>
<datasrc beanclass="psdi.webclient.beans.item.MoveToItemStructBean" id="parentitem" parentdatasrc="ias" relationship="PARENT"/>
<section border="true" id="ias_tab_grid2">
<multiparttextbox dataattribute="itemnum" descdataattribute="description" id="ias_tab_grid2_1" label="顶级项目" menutype="item"/>
<multiparttextbox dataattribute="itemnum" datasrc="ias" descdataattribute="item.description" descdatasrc="ias" descinputmode="readonly" id="ias_tab_grid2_3" label="当前级别" longdescreadonly="true" menutype="item"/>
<multiparttextbox applink="item" dataattribute="itemnum" datasrc="parentitem" descdataattribute="item.description" descdatasrc="ias" descinputmode="readonly" id="ias_tab_grid2_5" label="所属" longdescreadonly="true" lookup="itemwithitemset" menutype="itemhier" movetodatasrc="ias" movetoqbe="false"/>
<textbox dataattribute="remark" datasrc="ias" id="ias_tab_grid2_7" lookup="longdesc"/>
</section>
<table beanclass="psdi.webclient.beans.item.MoveToItemStructBean" id="ias_tab_children_table" label="子级" parentdatasrc="ias" relationship="CHILDREN">
<tablebody displayrowsperpage="10" filterable="true" id="ias_tab_children_table_tablebody">
<tablecol filterable="false" hidden="false" id="ias_tab_children_table_tablebody_1" mxevent="toggledetailstate" mxevent_desc="显示详细信息" sortable="false" type="event"/>
<tablecol applink="item,inventor" dataattribute="itemnum" defaultfocus="true" id="ias_tab_children_table_tablebody_2" lookup="itemwithitemset" menutype="itemhier" movetodatasrc="ias" movetoqbe="false"/>
<tablecol dataattribute="item.description" id="ias_tab_children_table_tablebody_3" sortable="false">
<textbox dataattribute="item.description" id="ias_item_desc" inputmode="readonly" longdescreadonly="true" lookup="longdesc"/>
</tablecol>
<tablecol dataattribute="quantity" id="ias_tab_children_table_tablebody_4"/>
<tablecol dataattribute="remark" id="ias_tab_children_table_tablebody_5" linkedcontrolid="ias_tab_children_table_1_grid3_4"/>
<tablecol filterable="false" hidden="false" id="ias_tab_children_table_tablebody_6" mxevent="toggledeleterow" mxevent_desc="标记要删除的行" mxevent_icon="btn_garbage.gif" sortable="false" type="event"/>
</tablebody>
<tabledetails id="ias_tab_children_table_1">
<section id="ias_tab_children_table_1_grid3" label="详细信息">
<sectionrow id="ias_tab_children_table_1_grid3_row">
<sectioncol id="ias_tab_children_table_1_grid3_row_col1">
<section id="ias_tab_children_table_1_grid3_row_col1_sec">
<multiparttextbox applink="item,inventor" dataattribute="itemnum" defaultfocus="true" descdataattribute="item.description" descinputmode="readonly" id="ias_tab_children_table_1_grid3_1" longdescreadonly="true" longdescription="true" lookup="itemwithitemset" menutype="itemhier" movetodatasrc="ias" movetoqbe="false"/>
<textbox dataattribute="quantity" id="ias_tab_children_table_1_grid3_3"/>
</section>
</sectioncol>
<sectioncol id="ias_tab_children_table_1_grid3_row_col2">
<section id="ias_tab_children_table_1_grid3_row_col2_sec">
<textbox dataattribute="remark" id="ias_tab_children_table_1_grid3_4" lookup="longdesc"/>
</section>
</sectioncol>
</sectionrow>
</section>
</tabledetails>
<buttongroup id="ias_tab_children_table_2">
<pushbutton default="true" id="ias_tab_children_table_2_1" label="新建行" mxevent="addrow"/>
</buttongroup>
</table>
</tab>
</tabgroup>
</clientarea>
<include id="pageFooter"/>
</page>
<dialog beanclass="psdi.webclient.beans.common.ClassificationBean" id="searchmore" inputmode="query" label="更多搜索字段">
<section id="qbe_grid5">
<sectionrow id="qbe_grid5_r1">
<sectioncol id="qbe_grid5_r1_c1">
<section id="qbe_grid5_r1_c1_s1">
<multiparttextbox dataattribute="ITEMNUM" descdataattribute="DESCRIPTION" descinputmode="query" id="qbe_grid5_1_1_1" inputmode="query" menutype="item"/>
<multiparttextbox dataattribute="ITEMSETID" descdataattribute="SETS.DESCRIPTION" descinputmode="query" id="qbe_grid5_1_1_3" inputmode="query" lookup="itemset"/>
<textbox dataattribute="commoditygroup" id="qbe_grid5_1_1_5" inputmode="query" lookup="commoditygroup"/>
<textbox applink="metergrp" dataattribute="GROUPNAME" id="qbe_grid5_1_1_14" inputmode="query" lookup="metergroup" menutype="normal"/>
<textbox applink="meter" dataattribute="METERNAME" id="qbe_grid5_1_1_15" inputmode="query" lookup="meter" menutype="normal"/>
<textbox dataattribute="MSDSNUM" id="qbe_grid5_1_1_9" inputmode="query"/>
<textbox applink="assetcat" dataattribute="CLASSSTRUCTURE.HIERARCHYPATH" id="qbe_classificationhierarchy" inputmode="query" menutype="classificationqbe"/>
<textbox dataattribute="itemorginfo.category" id="qbe_itemorgstatus" inputmode="query" lookup="valuelist"/>
<textbox dataattribute="status" id="qbe_grid5_1_1_9a" inputmode="query"/>
</section>
</sectioncol>
<sectioncol id="qbe_grid5_r1_c2">
<section id="qbe_grid5_r1_c2_s1">
<textbox dataattribute="LOTTYPE" id="qbe_grid5_1_1_8" inputmode="query" lookup="valuelist"/>
<textbox dataattribute="CAPITALIZED" id="qbe_grid5_1_1_12" inputmode="query"/>
<textbox dataattribute="iskit" id="qbe_grid5_1_1_16" inputmode="query"/>
<textbox dataattribute="conditionenabled" id="qbe_grid5_1_1_17" inputmode="query"/>
<textbox dataattribute="ROTATING" id="qbe_grid5_1_1_11" inputmode="query"/>
<textbox dataattribute="INSPECTIONREQUIRED" id="qbe_grid5_1_1_10" inputmode="query"/>
<textbox dataattribute="SPAREPARTAUTOADD" id="qbe_grid5_1_1_7" inputmode="query"/>
<textbox dataattribute="TAXEXEMPT" id="qbe_grid5_1_1_8a" inputmode="query"/>
</section>
</sectioncol>
</sectionrow>
</section>
<buttongroup id="qbe_grid5_1_1_grid6">
<pushbutton default="true" id="qbe_grid5_1_1_grid6_1" label="查找" mxevent="dialogok"/>
<pushbutton id="qbe_grid5_1_1_grid6_2" label="清除" mxevent="qbeclear"/>
<pushbutton id="qbe_grid5_1_1_grid6_3" label="取消" mxevent="qbecancel"/>
</buttongroup>
</dialog>
<dialog beanclass="psdi.webclient.beans.item.SelectStoreroomBean" id="additems" label="将项目添加到库房" mboname="LOCATIONS">
<section border="true" id="additems_grid1">
<textbox dataattribute="addToStoreSiteId" id="additems_grid1_1_1_grid3_3" lookup="site"/>
<multiparttextbox applink="storeroom,ipc" dataattribute="addToStoreLoc" descdataattribute="LOCATIONS_ADDTOSTORE.DESCRIPTION" descinputmode="readonly" desclongdescreadonly="true" desclookup="longdesc" id="additems_grid1_1_1_grid3_1" lookup="locations" menutype="normal"/>
</section>
<buttongroup id="additems_buttongroup" show="true">
<pushbutton default="true" id="additems_buttongroup_3" label="确定" mxevent="nextdialog" value="additemstostoreroom"/>
<pushbutton id="additems_buttongroup_4" label="取消" mxevent="dialogcancel"/>
</buttongroup>
</dialog>
<dialog beanclass="psdi.webclient.beans.item.AddItemsBean" designermboname="INVENTORY" id="additemstostoreroom" label="将项目添加到库房" listaction="true">
<table id="additems_grid1_1_1_inventorytable" label="库房信息">
<tablebody displayrowsperpage="10" id="additems_grid1_1_1_inventorytable_tablebody">
<tablecol filterable="false" hidden="false" id="additems_grid1_1_1_inventorytable_tablebody_1" mxevent="toggledetailstate" mxevent_desc="显示详细信息" sortable="false" type="event"/>
<tablecol dataattribute="itemnum" id="additems_grid1_1_1_inventorytable_tablebody_2" linkedcontrolid="additems_grid1_1_1_inventorytable_1_grid3_1"/>
<tablecol dataattribute="costtype" id="additems_grid1_1_1_inventorytable_tablebody_5" linkedcontrolid="additems_grid1_1_1_inventorytable_1_grid3_5"/>
<tablecol dataattribute="unitcost" id="additems_grid1_1_1_inventorytable_tablebody_4" linkedcontrolid="additems_grid1_1_1_inventorytable_1_grid3_4" sigoption="NOTASSETCOST"/>
<tablecol dataattribute="binnum" id="additems_grid1_1_1_inventorytable_tablebody_3" linkedcontrolid="additems_grid1_1_1_inventorytable_1_grid3_3"/>
<tablecol dataattribute="curbal" id="additems_grid1_1_1_inventorytable_tablebody_8" linkedcontrolid="additems_grid1_1_1_inventorytable_1_grid3_7"/>
<tablecol dataattribute="lotnum" id="additems_grid1_1_1_inventorytable_tablebody_9" linkedcontrolid="additems_grid1_1_1_inventorytable_1_grid3_9"/>
<tablecol dataattribute="issueunit" id="additems_grid1_1_1_inventorytable_tablebody_10" linkedcontrolid="additems_grid1_1_1_inventorytable_1_grid3_10"/>
<tablecol dataattribute="orderunit" id="additems_grid1_1_1_inventorytable_tablebody_11" linkedcontrolid="additems_grid1_1_1_inventorytable_1_grid3_11"/>
<tablecol dataattribute="siteid" id="additems_grid1_1_1_inventorytable_tablebody_12" linkedcontrolid="additems_grid1_1_1_inventorytable_1_grid3_12"/>
<tablecol filterable="false" hidden="false" id="additems_grid1_1_1_inventorytable_tablebody_13" mxevent="toggledeleterow" mxevent_desc="标记要删除的行" mxevent_icon="btn_garbage.gif" sortable="false" type="event"/>
</tablebody>
<tabledetails id="additems_grid1_1_1_inventorytable_1">
<section id="additems_grid1_1_1_inventorytable_1_grid3" label="详细信息">
<sectionrow id="additems_grid1_1_1_inventorytable_1_row1">
<sectioncol id="additems_grid1_1_1_inventorytable_1_row1_col1">
<section id="additems_grid1_1_1_inventorytable_1_row1_col1_sec1">
<textbox dataattribute="itemnum" defaultfocus="true" id="additems_grid1_1_1_inventorytable_1_grid3_1" lookup="itemwithitemset"/>
<textbox dataattribute="conditioncode" id="additems_grid1_1_1_inventorytable_1_grid3_2" lookup="conditioncode"/>
<textbox dataattribute="lotnum" id="additems_grid1_1_1_inventorytable_1_grid3_9" lookup="invlot" smartfilloff="true"/>
<textbox dataattribute="costtype" id="additems_grid1_1_1_inventorytable_1_grid3_5" lookup="valuelist"/>
<textbox dataattribute="unitcost" id="additems_grid1_1_1_inventorytable_1_grid3_4" sigoption="NOTASSETCOST"/>
<textbox dataattribute="binnum" id="additems_grid1_1_1_inventorytable_1_grid3_3" sizeintable="8" smartfilloff="true"/>
<textbox dataattribute="curbal" id="additems_grid1_1_1_inventorytable_1_grid3_7"/>
</section>
</sectioncol>
<sectioncol id="additems_grid1_1_1_inventorytable_1_row1_col2">
<section id="additems_grid1_1_1_inventorytable_1_row1_col2_sec1">
<textbox dataattribute="siteid" id="additems_grid1_1_1_inventorytable_1_grid3_12" inputmode="readonly" sizeintable="8"/>
<textbox dataattribute="issueunit" id="additems_grid1_1_1_inventorytable_1_grid3_10" lookup="measureunit" sizeintable="8"/>
<textbox dataattribute="orderunit" id="additems_grid1_1_1_inventorytable_1_grid3_11" lookup="measureunit" sizeintable="8"/>
<checkbox dataattribute="consignment" id="additems_grid1_1_1_inventorytable_1_grid3_14" synchronous="true"/>
<textbox applink="company" applinkkey="company" dataattribute="consvendor" id="additems_grid1_1_1_inventorytable_1_grid3_19" lookup="companies" menutype="normal" sigoption="consignment"/>
<textbox applink="company" dataattribute="manufacturer" id="additems_grid1_1_1_inventorytable_1_grid3_20" lookup="companies" menutype="normal" sigoption="consignment" smartfilloff="true"/>
<textbox dataattribute="modelnum" id="additems_grid1_1_1_inventorytable_1_grid3_21" sigoption="consignment"/>
</section>
</sectioncol>
<sectioncol id="additems_grid1_1_1_inventorytable_1_row1_col3">
<section id="additems_grid1_1_1_inventorytable_1_row1_col3_sec1">
<textbox dataattribute="catalogcode" id="additems_grid1_1_1_inventorytable_1_grid3_22" sigoption="consignment"/>
<textbox dataattribute="invgentype" id="additems_grid1_1_1_inventorytable_1_grid3_15" lookup="valuelist" sigoption="consignment"/>
<textbox dataattribute="frequency" id="additems_grid1_1_1_inventorytable_1_grid3_16" sigoption="consignment"/>
<textbox dataattribute="frequnit" id="additems_grid1_1_1_inventorytable_1_grid3_17" lookup="valuelist" sigoption="consignment"/>
<textbox dataattribute="nextinvoicedate" id="additems_grid1_1_1_inventorytable_1_grid3_18" lookup="datelookup" sigoption="consignment"/>
</section>
</sectioncol>
</sectionrow>
</section>
</tabledetails>
</table>
<buttongroup id="additemstostoreroom_buttongroup" show="true">
<pushbutton default="true" id="additemstostoreroom_buttongroup_3" label="确定" mxevent="dialogok"/>
<pushbutton id="additemstostoreroom_buttongroup_4" label="取消" mxevent="dialogcancel"/>
</buttongroup>
</dialog>
<dialog beanclass="psdi.webclient.beans.item.CopyIasBean" id="copyias" label="复制项目组装结构" relationship="COPYIASDLG">
<table id="copyias_grid1_1_1_virtualset1" label="项目">
<tablebody displayrowsperpage="15" filterable="true" filterexpanded="true" id="copyias_grid1_1_1_virtualset1_tablebody">
<tablecol dataattribute="itemnum" id="copyias_grid1_1_1_virtualset1_tablebody_2" mxevent="selectrecord" sortable="false" type="link"/>
<tablecol dataattribute="item.description" id="copyias_grid1_1_1_virtualset1_tablebody_3" showfilterfield="true" sortable="false"/>
</tablebody>
</table>
<buttongroup id="copyias_2">
<pushbutton default="true" id="copyias_2_1" label="取消" mxevent="dialogcancel"/>
</buttongroup>
</dialog>
<dialog beanclass="psdi.webclient.beans.item.ItemOrgInfoBean" id="itemorg" label="项目/组织详细信息" relationship="ITEMORGINFO" width="900">
<table id="itemorg_grid1_1_1_itemorginfo_table">
<tablebody displayrowsperpage="5" filterable="true" id="itemorg_grid1_1_1_itemorginfo_table_tablebody">
<tablecol filterable="false" hidden="false" id="itemorg_grid1_1_1_itemorginfo_table_tablebody_1" mxevent="toggledetailstate" mxevent_desc="显示详细信息" sortable="false" type="event"/>
<tablecol dataattribute="orgid" id="itemorg_grid1_1_1_itemorginfo_table_tablebody_2" inputmode="readonly"/>
<tablecol dataattribute="organization.description" id="itemorg_grid1_1_1_itemorginfo_table_tablebody_3" inputmode="readonly" sortable="false"/>
<tablecol dataattribute="category" id="itemorg_grid1_1_1_itemorginfo_table_tablebody_3a" linkedcontrolid="itemorg_grid1_1_1_itemorginfo_table_1_grid3_1_1_1a" lookup="valuelist"/>
<tablecol dataattribute="status" id="itemorg_grid1_1_1_itemorginfo_table_tablebody_3b" inputmode="readonly"/>
<tablecol dataattribute="hazardid" id="itemorg_grid1_1_1_itemorginfo_table_tablebody_4" linkedcontrolid="itemorg_grid1_1_1_itemorginfo_table_1_grid3_1_1_2" lookup="hazards"/>
<tablecol dataattribute="tax1code" id="itemorg_grid1_1_1_itemorginfo_table_tablebody_5" label="税代码" linkedcontrolid="itemorg_grid1_1_1_itemorginfo_table_1_grid3_1_1_3" lookup="taxcode"/>
<tablecol dataattribute="taxexempt" id="itemorg_grid1_1_1_itemorginfo_table_tablebody_6" linkedcontrolid="itemorg_grid1_1_1_itemorginfo_table_1_grid3_1_1_5"/>
<tablecol dataattribute="receipttolerance" id="itemorg_grid1_1_1_itemorginfo_table_tablebody_6a" linkedcontrolid="itemorg_grid1_1_1_itemorginfo_table_1_grid3_1_1_3a"/>
<tablecol filterable="false" hidden="false" id="itemorg_grid1_1_1_itemorginfo_table_tablebody_10" mxevent="iorgstatus" mxevent_desc="变更状态" mxevent_icon="nav_icon_changestatus.gif" sortable="false" type="event"/>
<tablecol filterable="false" hidden="false" id="itemorg_grid1_1_1_itemorginfo_table_tablebody_11" mxevent="iorghistory" mxevent_desc="查看状态历史记录" mxevent_icon="information.gif" sortable="false" type="event"/>
</tablebody>
<tabledetails id="itemorg_grid1_1_1_itemorginfo_table_1">
<section id="itemorg_grid1_1_1_itemorginfo_table_1_grid3" label="详细信息">
<sectionrow id="itemorg_grid1_1_1_itemorginfo_table_1_grid3_row">
<sectioncol id="itemorg_grid1_1_1_itemorginfo_table_1_grid3_row_col1">
<section id="itemorg_grid1_1_1_itemorginfo_table_1_grid3_row_col1_sec">
<multiparttextbox dataattribute="orgid" defaultfocus="true" descdataattribute="organization.description" descinputmode="readonly" descsizeintable="30" id="itemorg_grid1_1_1_itemorginfo_table_1_grid3_1_1_1" inputmode="readonly" longdescreadonly="true"/>
<textbox dataattribute="category" id="itemorg_grid1_1_1_itemorginfo_table_1_grid3_1_1_1a" lookup="valuelist"/>
<multiparttextbox dataattribute="hazardid" descdataattribute="hazard.description" descinputmode="readonly" id="itemorg_grid1_1_1_itemorginfo_table_1_grid3_1_1_2" longdescreadonly="true" lookup="hazards"/>
<textbox dataattribute="tax1code" id="itemorg_grid1_1_1_itemorginfo_table_1_grid3_1_1_3" label="税代码" lookup="taxcode"/>
<checkbox dataattribute="taxexempt" id="itemorg_grid1_1_1_itemorginfo_table_1_grid3_1_1_5"/>
<textbox dataattribute="receipttolerance" id="itemorg_grid1_1_1_itemorginfo_table_1_grid3_1_1_3a"/>
<textbox dataattribute="status" id="itemorg_grid1_1_1_itemorginfo_table_1_grid3_1_1_4" inputmode="readonly"/>
</section>
</sectioncol>
</sectionrow>
</section>
</tabledetails>
</table>
<buttongroup id="itemorg_2">
<pushbutton default="true" id="itemorg_2_1" label="确定" mxevent="dialogok"/>
<pushbutton id="itemorg_2_2" label="取消" mxevent="dialogcancel"/>
</buttongroup>
</dialog>
<dialog beanclass="psdi.webclient.beans.item.ItemChangeStatusBean" id="status" label="变更状态" relationship="ITEMCHANGESTATUS" savemode="ONLOADUNLOAD">
<section id="changeitemstatus_grid1">
<sectionrow id="changeitemstatus_grid1_1">
<sectioncol id="changeitemstatus_grid1_1_1">
<section border="true" id="changeitemstatus_grid1_1_1_grid3">
<multiparttextbox dataattribute="itemnum" descdataattribute="description" descinputmode="readonly" id="changeitemstatus_grid1_1_1_grid3_1" inputmode="readonly" longdescinputmode="readonly"/>
<multiparttextbox dataattribute="itemstatus" descdataattribute="statusdesc.description" descinputmode="readonly" id="changeitemstatus_grid1_1_1_grid3_2" inputmode="readonly"/>
</section>
<section id="changeitemstatus_grid1_1_1_grid4">
<combobox dataattribute="status" id="changeitemstatus_grid1_1_1_grid4_1" smartfilloff="true"/>
<checkbox dataattribute="rolldown" id="changeitemstatus_grid1_1_1_grid4_2" label="将新状态滚动到组织和库存"/>
<textbox dataattribute="Memo" id="changeitemstatus_grid1_1_1_grid4_3"/>
</section>
</sectioncol>
</sectionrow>
</section>
<buttongroup id="changeitemstatus_2">
<pushbutton default="true" id="changeitemstatus_2_1" label="确定" mxevent="dialogok"/>
<pushbutton id="changeitemstatus_2_2" label="取消" mxevent="dialogcancel"/>
</buttongroup>
</dialog>
<dialog beanclass="psdi.webclient.beans.item.ItemChangeStatusBean" id="list_status" label="变更状态" listaction="false" relationship="ITEMCHANGESTATUS" savemode="ONUNLOAD">
<section id="list_changeitemstatus_grid1">
<sectionrow id="list_changeitemstatus_grid1_1">
<sectioncol id="list_changeitemstatus_grid1_1_1">
<section id="list_changeitemstatus_grid1_1_1_grid4">
<combobox dataattribute="status" id="list_changeitemstatus_grid1_1_1_grid4_1" smartfilloff="true"/>
<checkbox dataattribute="rolldown" id="list_changeitemstatus_grid1_1_1_grid4_2" label="将新状态滚动到组织和库存"/>
<textbox dataattribute="Memo" id="list_changeitemstatus_grid1_1_1_grid4_3"/>
</section>
</sectioncol>
</sectionrow>
</section>
<buttongroup id="list_changeitemstatus_2">
<pushbutton default="true" id="list_changeitemstatus_2_1" label="确定" mxevent="dialogok"/>
<pushbutton id="list_changeitemstatus_2_2" label="取消" mxevent="dialogcancel"/>
</buttongroup>
</dialog>
<dialog id="viewstatus" label="查看状态历史记录" relationship="ITEMSTATUS">
<table id="viewstatus_contracts_table" inputmode="readonly" label="状态历史记录" orderby="changedate desc">
<tablebody displayrowsperpage="20" filterable="true" filterexpanded="true" id="viewstatusracts_table_tablebody">
<tablecol dataattribute="status" id="viewstatusracts_tablebody_1" sortable="false"/>
<tablecol dataattribute="changedate" id="viewstatusracts_tablebody_2" sortable="false"/>
<tablecol dataattribute="changeby" id="viewstatusracts_tablebody_3" sortable="false"/>
<tablecol dataattribute="memo" id="viewstatusracts_table_tablebody_4" sortable="false"/>
</tablebody>
</table>
<buttongroup id="viewstatus_contracts_2">
<pushbutton default="true" id="viewstatus_contracts_2_1" label="确定" mxevent="dialogclose"/>
</buttongroup>
</dialog>
<dialog id="iorghistory" label="查看状态历史记录" relationship="ITEMORGSTATUS">
<table id="iorghistory_contracts_table" inputmode="readonly" label="状态历史记录" orderby="changedate desc">
<tablebody displayrowsperpage="20" filterable="true" filterexpanded="true" id="iorghistoryracts_table_tablebody">
<tablecol dataattribute="status" id="iorghistoryracts_tablebody_1" sortable="false"/>
<tablecol dataattribute="changedate" id="iorghistoryracts_tablebody_2" sortable="false"/>
<tablecol dataattribute="changeby" id="iorghistoryracts_tablebody_3" sortable="false"/>
<tablecol dataattribute="memo" id="iorghistoryracts_table_tablebody_4" sortable="false"/>
</tablebody>
</table>
<buttongroup id="iorghistory_contracts_2">
<pushbutton default="true" id="iorghistory_contracts_2_1" label="确定" mxevent="dialogclose"/>
</buttongroup>
</dialog>
<dialog id="viewcont" label="查看合同" relationship="CONTRACTLINE_NOHIST">
<helpgrid id="viewcont_helpgrid" innerhtml="要优化搜索，请输入列的过滤条件并按 <b>Enter</b> 键或单击 <IMG border="0" SRC="qf_find.gif">。"/>
<table id="viewcont_contracts_table" inputmode="readonly" label="合同">
<tablebody displayrowsperpage="20" filterable="true" filterexpanded="true" id="viewcontracts_table_tablebody">
<tablecol dataattribute="contractnum" id="viewcontracts_tablebody_1" sortable="false"/>
<tablecol dataattribute="revisionnum" id="viewcontracts_tablebody_2" sortable="false"/>
<tablecol dataattribute="CONTRACT.description" id="viewcontracts_tablebody_3" sortable="false"/>
<tablecol dataattribute="contracttype" id="viewcontracts_table_tablebody_4" sortable="false"/>
<tablecol dataattribute="CONTRACT.startdate" id="viewcontracts_tablebody_5" sortable="false"/>
<tablecol dataattribute="CONTRACT.enddate" id="viewcontracts_tablebody_6" sortable="false"/>
<tablecol dataattribute="CONTRACT.status" id="viewcontracts_table_tablebody_7" sortable="false"/>
</tablebody>
</table>
<buttongroup id="viewcont_contracts_2">
<pushbutton default="true" id="viewcont_contracts_2_1" label="确定" mxevent="dialogclose"/>
</buttongroup>
</dialog>
<dialog beanclass="psdi.webclient.system.beans.ViewBookmarksBean" id="searchbook" label="我的书签" mboname="ITEM">
<table id="bookmarks_table" inputmode="readonly" label="项目" selectmode="single">
<tablebody displayrowsperpage="20" filterable="true" id="bookmarks_table_tablebody">
<tablecol dataattribute="itemnum" id="bookmarks_tablebody_1" mxevent="selectrecord" type="link"/>
<tablecol dataattribute="description" id="bookmarks_table_tablebody_2"/>
<tablecol filterable="false" hidden="false" id="bookmarks_table_tablebody_delete" mxevent="instantdelete" mxevent_desc="删除" mxevent_icon="btn_delete.gif" sortable="false" type="event"/>
</tablebody>
</table>
<buttongroup id="bookmarks_2">
<pushbutton default="true" id="bookmarks_2_1" label="确定" mxevent="dialogok"/>
</buttongroup>
</dialog>
</presentation>
```
## java源代码
```Java
package org.shoukaiseki.webclient.beans.test;
import psdi.mbo.MboRemote;
import psdi.util.CipherPlusBase64;
import psdi.webclient.applet.attachimage.Base64;
import psdi.webclient.system.beans.DataBean;
import javax.imageio.ImageIO;
import java.awt.image.BufferedImage;
import java.io.ByteArrayOutputStream;
import java.io.File;
import java.io.FileInputStream;
import java.io.InputStream;
/**
* org.shoukaiseki.webclient.beans.test.TestItemAppBean <br>
*
* @author 蒋カイセキ Japan-Tokyo 2017-09-27 16:20:04<br>
* ブログ http://shoukaiseki.blog.163.com/<br>
* E-メール [email protected]<br>
**/
public class TestItemAppBean extends psdi.webclient.beans.item.ItemAppBean{
public void ASUS()throws Exception{
System.out.println("asus.....");
MboRemote mbo = getMbo();
MboRemote imglib = mbo.getMboSet("IMGLIB").getMbo(0);
InputStream in = null;
if(imglib!=null){
imglib.delete();
imglib=mbo.getMboSet("IMGLIB").add();
imglib.setValue("IMAGENAME","001.jpg");
imglib.setValue("MIMETYPE","image/jpeg");
System.out.println("imglib is not null");
System.out.println("image="+imglib.getBytes("IMAGE"));
System.out.println("image="+imglib.getDatabaseValue("IMAGE"));
// base64加密
// String image = Base64.encode(imglib.getBytes("IMAGE"));
// System.out.println("image="+image);
System.out.println("isnull="+imglib.isNull("IMAGE"));
try {
File file=new File("C:\\tmp\\001.jpg");
ByteArrayOutputStream out = new ByteArrayOutputStream();
// 根据文件创建文件的输入流
in = new FileInputStream(file);
// 创建字节数组
// 读取内容，放到字节数组里面
byte[] buffer = new byte[256];
int n;
while ((n = in.read(buffer)) >= 0) {
out.write(buffer, 0, n);
}
byte[] bytes = out.toByteArray();
System.out.println("bytes="+bytes);
imglib.setValue("IMAGE",bytes);
imglib.getThisMboSet().save();
System.out.println("save..");
}catch (Exception e){
e.printStackTrace();
}
}else{
imglib=mbo.getMboSet("IMGLIB").add();
imglib.setValue("IMAGENAME","002.jpg");
imglib.setValue("MIMETYPE","image/jpeg");
try {
File file=new File("C:\\tmp\\002.jpg");
ByteArrayOutputStream out = new ByteArrayOutputStream();
// 根据文件创建文件的输入流
in = new FileInputStream(file);
// 创建字节数组
// 读取内容，放到字节数组里面
byte[] buffer = new byte[256];
int n;
while ((n = in.read(buffer)) >= 0) {
out.write(buffer, 0, n);
}
byte[] bytes = out.toByteArray();
imglib.setValue("IMAGE",bytes);
imglib.getThisMboSet().save();
System.out.println("save....");
}catch (Exception e){
e.printStackTrace();
}
}
if(in!=null){
try {
// 关闭输入流
in.close();
} catch (Exception e) {
e.printStackTrace();
}
}
psdi.webclient.beans.common.RecordImageBean sadfsd;
psdi.app.system.ImgLibSet safs;
}
public void movetonextrow() throws Exception{
System.out.println("movetonextrow");
DataBean dataBean = app.getDataBean("results_showlist");
System.out.println("CurrentRow="+dataBean.getCurrentRow());
dataBean.nextrow();
System.out.println("CurrentRow="+dataBean.getCurrentRow());
}
public void moveto5page()throws Exception{
DataBean dataBean = app.getDataBean("results_showlist");
int pageRowCount = dataBean.getPageRowCount();
int page=5;
if(dataBean.getMboSet().count()>=pageRowCount*page-1){
movetorow(pageRowCount*page);
}else{
page=dataBean.getMboSet().count();
movetorow(page);
}
System.out.println("moveto10page");
}
public void moveto205row()throws Exception{
System.out.println("moveto205row");
DataBean dataBean = app.getDataBean("results_showlist");
int pageRowCount = dataBean.getPageRowCount();
System.out.println("pageRowCount="+pageRowCount);
System.out.println(".........");
int rownum=205;
movetorow(rownum);
}
public void movetorow(int rownum)throws Exception{
DataBean dataBean = app.getDataBean("results_showlist");
int pageRowCount = dataBean.getPageRowCount();
if(dataBean.getMboSet().count()>=rownum-1){
while(dataBean.getPageEndRow()<rownum||dataBean.getPageEndRow()-pageRowCount>rownum){
if(dataBean.getPageEndRow()<rownum){
dataBean.scrollnext();
}else {
dataBean.scrollprev();
}
System.out.println("PageEndRow="+dataBean.getPageEndRow());
}
}
dataBean.setCurrentRow(rownum-1);
}
}
```
| 68.365309 | 329 | 0.726406 | yue_Hant | 0.099655 |
a6e1334e3cdc3854fe03d3644f951c073548b64e | 6,821 | md | Markdown | algebra/Coffeequate-master/docs/usage.md | geometor/three-golden-sections | 397f70635f25680a9c3f5d94e28ab432df47251b | [
"MIT"
] | 2 | 2019-08-18T19:43:04.000Z | 2020-11-01T21:08:51.000Z | algebra/Coffeequate-master/docs/usage.md | geometor/three-golden-sections | 397f70635f25680a9c3f5d94e28ab432df47251b | [
"MIT"
] | null | null | null | algebra/Coffeequate-master/docs/usage.md | geometor/three-golden-sections | 397f70635f25680a9c3f5d94e28ab432df47251b | [
"MIT"
] | null | null | null | # Usage
## Making new expressions
Most interaction with Coffeequate is done with the methods of the `Expression` object that `CQ` returns. An expression is implicitly equated to zero (even if it's not going to be used as an equation), so all of the following are equivalent:
```javascript
CQ("y = m*x + b")
CQ("m*x + b - y = 0")
CQ("m*x + b - y")
```
## Converting to strings
You'll want to convert your expressions into some kind of pretty, string representation at some point. There are three methods that do this:
### toString()
`expr.toString()` converts the expression `expr` into a simple string representation. For example,
```javascript
CQ("E = m*\\c**2").toString() // ' - E + m*c**2'
```
### toMathML()
`expr.toMathML()` converts the expression `expr` into a MathML string. For example,
```javascript
CQ("E = m*\\c**2").toMathML() // '<mo>-</mo><mi class="variable">E</mi><mo>+</mo><mi class="variable">m</mi><mo>·</mo><msup><mi class="constant symbolic-constant">c</mi><mn class="constant">2</mn></msup>'
```
### toLaTeX()
`expr.toLaTeX()` converts the expression `expr` into a LaTeX string. For example,
```javascript
CQ("E = m*\\c**2").toLaTeX() // '-E+m \\cdot c^{2}'
```
## Solving equations
### solve(variable, equivalencies={})
`expr.solve(variable)` solves the expression `expr` for the variable `variable`, and assumes that the expression is equal to zero. For example,
```javascript
CQ("m*x + b - y").solve("y") // m*x + b
CQ("m**2*\\c**4 + p**2*\\c**2").solve("p") // sqrt(-(c**4*m**2)), -(sqrt(-(c**4*m**2)))
```
`expr.solve(variable, equivalencies)` is the same as above, except that it takes a map of equivalencies. This equivalencies map describes which variables are equivalent to each other. For example, if `x` and `z` are equal, then `equivalencies = {"x":["x", "z"], "z":["x", "z"]}`. The order within the map is irrelevant, but it must be redundant.
### nsolve(guess, variable, equivalencies={}, tol=1e-9, max_iterations=75)
`expr.nsolve(guess, variable)` finds a numerical solution of the expression `expr` for the the variable `variable` using Newton's method with the initial value `guess`, assuming that the expression is set to zero. This only works for differentiable expressions.
For example,
```javascript
CQ("x**2 - 2").nsolve(1.5,"x") // 1.4142135623730951
```
The use of `equivalencies` is the same as for `expr.solve`.
`expr.nsolve(guess, variable, equivalencies, tol)` finds the numerical solution of the expression `expr` so that the difference between the found solution and the exact solution is less than `tol`.
`expr.nsolve(guess, variable, equivalencies, tol, max_iterations)` will attempt to find a numerical solution within `tol` for the expression `expr` before the maximum number of iterations allowed `max_iterations` is reached. If this doesn't happen, the function will throw an error:
```javascript
CQ("x**2 + 7").nsolve(1.5,"x") // Error: Maximum Number of Iterations Reached
```
## Simplifying expressions
### simplify(equivalencies={})
`expr.simplify()` simplifies the expression `expr` if possible. It can optionally take an equivalencies map like `solve`, which it will use to simplify the equation further.
### expand()
`expr.expand()` expands the expression `expr` if possible.
## Substituting values
### sub(subs, equivs={}, subUncertainties=false, evalSymConstants=false)
`expr.sub(subs)` substitutes values into variables in `expr` according to the map `subs`. `subs` maps variable labels to values that should be substituted in their place. Values should be either numbers or Coffeequate expressions. For example,
```javascript
CQ("E = m*\\c**2").sub({"m": 10}) // -E + 10*\\c**2
```
Much like `simplify` and `solve`, `sub` can take an `equivs` argument mapping variables to an array of equivalent variables. This will be used while substituting and subsequently simplifying.
There are two optional boolean arguments, `subUncertainties` and `evalSymConstants`. If `subUncertainties` is true, then instead of substituting values into variables, `sub` will substitute values into the associated <em>uncertainties</em>. For more information on this, see the documentation for [uncertainties](#manipulating-uncertainties). If `evalSymConstants` is true, then symbolic constants will have their values substituted:
```javascript
CQ("E = m*\\c**2").sub({"m": 10}, {}, false, true) // 898755178736817700 - E
```
## Checking equality
### equals(other, equivalencies={})
`a.equals(b)` returns true if `a` and `b` represent the same expression, and false otherwise.
### approx()
`expr.approx()` sets all variables to 0 and evaluates the resulting expression, returning a number. This evaluates symbolic constants, too.
## Manipulating variables
### getAllVariables()
A list of variables in the expression can be retrieved with `expr.getAllVariables()`. For example,
```javascript
CQ("E = m*\\c**2").getAllVariables() // [ 'E', 'm' ]
```
### mapOverVariables(f)
`expr.mapOverVariables(f)` applies a function `f` to all variables in the expression. This is useful for changing labels, for example:
```javascript
var changeLabel = function(variable) {
variable.label += "s";
return variable;
};
var newExpr = CQ("E = m*\\c**2").mapOverVariables(changeLabel); // Es = ms*\\c**2
```
This method does not change the original expression.
## Deep-copying expressions
### copy()
The whole expression can be deep-copied with `expr.copy()`. The copy will be completely separate from the original, so it can be changed without mutating the original.
## Manipulating uncertainties
### getUncertainty()
`expr.getUncertainty()` propagates uncertainties through `expr` and returns a new expression representing the uncertainty in `expr`. For example,
```javascript
CQ("m*\\c**2").getUncertainty() // sqrt(\\c**4*σ(m)**2)
```
Uncertainties can be substituted in using `expr.sub`, with the `subUncertainties` argument set to true.
```javascript
CQ("m*\\c**2").getUncertainty().sub({m: 1}, {}, true).approx() // 89875517873681760
```
## Differentiating
### differentiate(variable, equivalencies={})
`expr.differentiate(variable)` differentiates `expr` with respect to `variable` and returns the result. For example,
```javascript
CQ("a*x**2 + b*x + c").differentiate("x") // b + 2*a*x
```
At the moment, this only does simple derivatives, e.g. trying to differentiate `2**x` will fail.
## Converting to functions
### toFunction(variables..., equivalencies={})
Expressions can be converted to functions using `expr.toFunction(variables...)`, which takes some number of variable labels and returns a function that takes those same variables as arguments and returns a value or expression. For example,
```javascript
var f = CQ("a*x**2 + b*x + c - y").toFunction("x", "y");
f(3, 2) // -2 + c + 3*b + 9*a
```
| 40.123529 | 433 | 0.710013 | eng_Latn | 0.98297 |
a6e1eea969545ac6bfa7d3856bb5b86c01d888ba | 42 | md | Markdown | README.md | westyn2020/EthicalHacking | 7fa7ac3383ac483cda7e2867996436ec8f1841f0 | [
"MIT"
] | null | null | null | README.md | westyn2020/EthicalHacking | 7fa7ac3383ac483cda7e2867996436ec8f1841f0 | [
"MIT"
] | null | null | null | README.md | westyn2020/EthicalHacking | 7fa7ac3383ac483cda7e2867996436ec8f1841f0 | [
"MIT"
] | null | null | null | # EthicalHacking
Ethical Hacking to learn
| 14 | 24 | 0.833333 | eng_Latn | 0.989202 |
a6e3472291425839fc07e4ea85043a507c620fa9 | 19 | md | Markdown | JavaScript Fundamentals/Functions/RadioCrystals/README.md | BlueDress/School | 0d380d418fb2e766a72f6198518c56c0eb283001 | [
"MIT"
] | null | null | null | JavaScript Fundamentals/Functions/RadioCrystals/README.md | BlueDress/School | 0d380d418fb2e766a72f6198518c56c0eb283001 | [
"MIT"
] | null | null | null | JavaScript Fundamentals/Functions/RadioCrystals/README.md | BlueDress/School | 0d380d418fb2e766a72f6198518c56c0eb283001 | [
"MIT"
] | null | null | null | # RadioCrystals
| 4.75 | 16 | 0.684211 | eng_Latn | 0.640424 |
a6e4259a4ce8827ec7194e1b4158f324c948aed8 | 432 | md | Markdown | content/items/slytherin-and-ravenclaw/index.md | roseapplemedia/catty-snipcart-netlify | 3927f2bec65a387adf113353852904c86a2db5ca | [
"MIT"
] | null | null | null | content/items/slytherin-and-ravenclaw/index.md | roseapplemedia/catty-snipcart-netlify | 3927f2bec65a387adf113353852904c86a2db5ca | [
"MIT"
] | null | null | null | content/items/slytherin-and-ravenclaw/index.md | roseapplemedia/catty-snipcart-netlify | 3927f2bec65a387adf113353852904c86a2db5ca | [
"MIT"
] | null | null | null | ---
title: Slytherin and Ravenclaw
date: 2019-10-09
id: 1009191256
price: 18
image: ./ravenclaw.jpg
description: For the Harry Potter fan dog.
category: dog
customField:
name: Sizes
values:
[
{ name: "X Small (8in-11in)", priceChange: 0 },
{ name: "Small (9in-14in)", priceChange: 2.00 },
{ name: "Medium (13in-22in)", priceChange: 5.00 },
{ name: "Large (15in-27in)", priceChange: 7.00 },
]
---
| 22.736842 | 56 | 0.618056 | yue_Hant | 0.510002 |
a6e4768260ea20203db43c41327aba90646fbcde | 1,225 | md | Markdown | README.md | dreadsd/dwm-html | 700343ff1539de80ef7c65f85e7639b19a31d421 | [
"MIT"
] | null | null | null | README.md | dreadsd/dwm-html | 700343ff1539de80ef7c65f85e7639b19a31d421 | [
"MIT"
] | null | null | null | README.md | dreadsd/dwm-html | 700343ff1539de80ef7c65f85e7639b19a31d421 | [
"MIT"
] | null | null | null | # dwm-html
**[dwm-html](https://dreadsd.github.io/dwm-html/)** is a static page that aims
to recreate the basic dwm layout with the taggrid patch. Made for color
customization purposes.
## Screenshots
## Installation
```sh
git clone https://github.com/dreadsd/dwm-html.git
cd dwm-html
```
Open the index.html file with [one of the following browsers](https://github.com/dreadsd/dwm-html#support).
## Usage
There are 6 root variables, change them in the styles file or in the dev tools:
- normal foreground (--nrm-fg)
- selected foreground (--sel-fg)
- normal background (--nrm-bg)
- selected background (--sel-bg)
- normal border (--nrm-bd)
- selected border (--sel-bd)
## Support
This is a general grid and flexbox browser support, check yours.
|Browser|Version|
|-------|-------|
|Chrome | > 57 |
|Firefox| > 52 |
|Edge | > 16 |
|Safari | > 10.1|
|Opera | > 12.1|
## To do
I don't know if I want to add a dynamic color change with JavaScript, I like
the concept of a static page with changes in the dev tools.
## dwm
<https://dwm.suckless.org/>
## License
[MIT](https://opensource.org/licenses/MIT)
| 26.06383 | 107 | 0.693878 | eng_Latn | 0.797854 |
a6e6645b713337c76e500ecb8287334772684442 | 1,689 | md | Markdown | wise_man/README.md | jaiswalpuru/discord_bots | 39d01ae1aa5016170ca61aba2d38de9fe58be572 | [
"Apache-2.0"
] | null | null | null | wise_man/README.md | jaiswalpuru/discord_bots | 39d01ae1aa5016170ca61aba2d38de9fe58be572 | [
"Apache-2.0"
] | null | null | null | wise_man/README.md | jaiswalpuru/discord_bots | 39d01ae1aa5016170ca61aba2d38de9fe58be572 | [
"Apache-2.0"
] | null | null | null | # GOAT
<p align="center">
<img src="https://github.com/jaiswalpuru/discord_bots/blob/main/wise_man/images/goat.png" alt="Logo" width="300" height="200" style="border-radius:10%">
</p>
<!-- GETTING STARTED -->
## Getting Started
### Prerequisites
* pip
```sh
python -m pip install -U pip
```
* discord
```sh
pip install discord.py
```
* dotenv
```sh
pip install python-dotenv
```
### Installation
1. Get a free TOKEN Key at discord developers portal.
2. Clone the repo
```sh
git clone https://github.com/jaiswalpuru/discord_bots.git
```
3. Create a .env file inside the cloned folder
```sh
touch .env
```
4. Enter your TOKEN value, and all the Channel ID's which will be used
```sh
TOKEN = 'ENTER YOUR TOKEN'
TRACKER_CHANNEL_ID = 'VALUE' # Channel where user entering and leaving channel will be tracked.
WELCOME_CHANNEL_ID = 'VALUE' # Channel for welcoming user.
```
### Run
```sh
python3 goat.py
```
<!-- ROADMAP -->
## Roadmap
See the [open issues](https://github.com/jaiswalpuru/discord_bots/issues) for a list of proposed features (and known issues).
<!-- CONTRIBUTING -->
## Contributing
Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are **greatly appreciated**.
1. Fork the Project
2. Create your Feature Branch (`git checkout -b feature/AmazingFeature`)
3. Commit your Changes (`git commit -m 'Add some AmazingFeature'`)
4. Push to the Branch (`git push origin feature/AmazingFeature`)
5. Open a Pull Request
<!-- LICENSE -->
## License
Distributed under the MIT License. See `LICENSE` for more information.
| 25.208955 | 165 | 0.689757 | eng_Latn | 0.873849 |
a6e6a30356ff5d6847de164e9fe497e6e4d71be5 | 1,208 | md | Markdown | README.md | luke5sky/skill-playback-control | 3ff151a23201435c20127abf810b0b51c9133239 | [
"Apache-2.0"
] | null | null | null | README.md | luke5sky/skill-playback-control | 3ff151a23201435c20127abf810b0b51c9133239 | [
"Apache-2.0"
] | null | null | null | README.md | luke5sky/skill-playback-control | 3ff151a23201435c20127abf810b0b51c9133239 | [
"Apache-2.0"
] | null | null | null | # <img src='https://rawgithub.com/FortAwesome/Font-Awesome/master/advanced-options/raw-svg/solid/play.svg' card_color='#22a7f0' width='50' height='50' style='vertical-align:bottom'/> Playback Control
Common playback control system
## About
This Skill doesn't do anything by itself, but it provides an important common
language for audio playback skills. By handling simple phrases like
'pause', this one Skill can turn around and rebroadcast the [messagebus](https://mycroft.ai/documentation/message-bus/)
command `mycroft.audio.service.pause`, allowing several music services to share
common terminology such as "pause".
Additionally, this implements the common Play handler. This allows playback
services to negotiate which is best suited to play back a specific request.
This capability is used by the [Spotify](https://github.com/forslund/spotify-skill) and [Pandora](https://github.com/mycroftai/pianobar-skill) Skills, among others.
## Examples
* "Play my summer playlist"
* "Play Pandora"
* "Pause"
* "Resume"
* "Next song"
* "Next track"
* "Previous track"
* "Previous song"
## Credits
Mycroft AI (@MycroftAI)
## Category
**Music**
## Tags
#music
#play
#playback
#pause
#resume
#next
#system
| 30.974359 | 199 | 0.762417 | eng_Latn | 0.969719 |
a6e6be9a9e938c5121c0186cf12d01c969052c1b | 2,578 | md | Markdown | wiki/translations/pl/OpenSCAD_AddOpenSCADElement.md | dwhr-pi/FreeCAD-documentation | 0c889672d80e7969dcabe83f5ddf503e72a4f5bb | [
"CC0-1.0"
] | null | null | null | wiki/translations/pl/OpenSCAD_AddOpenSCADElement.md | dwhr-pi/FreeCAD-documentation | 0c889672d80e7969dcabe83f5ddf503e72a4f5bb | [
"CC0-1.0"
] | null | null | null | wiki/translations/pl/OpenSCAD_AddOpenSCADElement.md | dwhr-pi/FreeCAD-documentation | 0c889672d80e7969dcabe83f5ddf503e72a4f5bb | [
"CC0-1.0"
] | null | null | null | ---
- GuiCommand:
Name:OpenSCAD AddOpenSCADElement
Empty:1
MenuLocation:OpenSCAD -> Add OpenSCAD Element
Workbenches:[OpenSCAD](OpenSCAD_Workbench.md)
---
# OpenSCAD AddOpenSCADElement/pl
## Description
Add an OpenSCAD element by entering OpenSCAD code into the task panel and executing the OpenSCAD binary (requires OpenSCAD)
When \'as mesh\' is selected, OpenSCAD renders a Mesh.
Each time Add is pressed the OpenSCAD code is executed and elements are imported.
If OpenSCAD returns successfully, its messages are displayed as warnings in the report window. This will be the case if the path to imported, included and used files is broken. In case of undesired results it is highly recommend to have a look at the report windows, as there might be a lot of other output, created by the importer. If OpenSCAD fails, its messages will be logged as errors. Libraries should be accessible as usual, whereas example can be reached as stated below
```python
include <../examples/example001.scad>;
``` would include the first examples also known as the OpenSCAD icon
## Setup OpenSCAD within FreeCAD
**Note:** OpenSCAD needs to be installed on your computer before FreeCAD will have this functionality
Install OpenSCAD in the appropriate manner for your operating system. See [the OpenSCAD web site](https://www.openscad.org/) for more information
FreeCAD needs to be told where to find the OpenSCAD executable
- Switch to the <img alt="" src=images/Workbench_OpenSCAD.svg style="width:24px;"> [OpenSCAD Workbench](OpenSCAD_Workbench.md) via
**Menu → View Workbench → OpenSCAD**
- Open the preferences dialog **Menu
→ Edit → Preferences**
- Click on \"OpenSCAD\" on the left plane
- Click on the button labled **...** in **General Settings → General OpenSCAD Settings → OpenSCAD executable** to browse the directory or enter the path (e.g. Ubuntu based Linux distributions `/usr/bin/openscad`) directly into the line input right to the button
- Close and restart FreeCAD
: **Result:** A new OpenSCAD icon will appear on the tool bar, and in the OpenSCAD menu, in the FreeCAD OpenSCAD workbench
Note: It is also possible to add another optional Parameter which controls the maximum sides of a polygon before it is considered a circle (fn).
Starting from <small>(v0.14)</small> FreeCAD will search for the OpenSCAD executable if the setting mentioned above is empty.
{{OpenSCAD_Tools_navi
}}
---
 [documentation index](../README.md) > [OpenSCAD](OpenSCAD_Workbench.md) > OpenSCAD AddOpenSCADElement/pl
| 45.22807 | 479 | 0.764934 | eng_Latn | 0.977299 |
a6e8106df88e844ced2db73eb0a384c201874fb1 | 7,114 | md | Markdown | README.md | minhducpsc/pyDNMFk | d58b89d8acf16970a640458cfceb3fdcb0bc2bb6 | [
"BSD-3-Clause"
] | null | null | null | README.md | minhducpsc/pyDNMFk | d58b89d8acf16970a640458cfceb3fdcb0bc2bb6 | [
"BSD-3-Clause"
] | null | null | null | README.md | minhducpsc/pyDNMFk | d58b89d8acf16970a640458cfceb3fdcb0bc2bb6 | [
"BSD-3-Clause"
] | null | null | null | # [pyDNMFk: Python Distributed Non Negative Matrix Factorization with determination of hidden features](https://github.com/lanl/pyDNMFk)
[](https://github.com/lanl/Distributed_pyNMFk/actions/workflows/ci_test.yml/badge.svg?branch=main) [](https://img.shields.io/badge/License-BSD%203--Clause-blue.svg) [](https://img.shields.io/badge/python-v3.7.1-blue)
[pyDNMFk](https://github.com/lanl/pyDNMFk) is a software package for applying non-negative matrix factorization in a distrubuted fashion to large datasets. It has the ability to minimize the difference between reconstructed data and the original data through various norms (Frobenious, KL-divergence). Additionally, the Custom Clustering algorithm allows for automated determination for the number of Latent features
<hr/>
## Features:
* Utilization of MPI4py for distributed operation.
* Distributed NNSVD and SVD initiaizations.
* Distributed Custom Clustering algorithm for estimating automated latent feature number (k) determination.
* Objective of minimization of KL divergence/Frobenius norm.
* Optimization with multiplicative updates, BCD, and HALS.
## Installation:
On a desktop machine
```
git clone https://github.com/lanl/pyDNMFk.git
cd pyDNMFk
conda create --name pyDNMFk python=3.7.1 openmpi mpi4py
source activate pyDNMFk
python setup.py install
```
<hr/>
On a server
```
git clone https://github.com/lanl/pyDNMFk.git
cd pyDNMFk
conda create --name pyDNMFk python=3.7.1
source activate pyDNMFk
module load <openmpi>
pip install mpi4py
python setup.py install
```
## Prerequisites:
* conda
* numpy>=1.2
* matplotlib
* MPI4py
* scipy
* h5py
## Documentation
You can find the documentation [here](https://lanl.github.io/pyDNMFk/).
## Usage
We provide a sample dataset that can be used for estimation of k:
```python
'''Imports block'''
import sys
import pyDNMFk.config as config
config.init(0)
from pyDNMFk.pyDNMFk import *
from pyDNMFk.data_io import *
from pyDNMFk.dist_comm import *
from scipy.io import loadmat
from mpi4py import MPI
comm = MPI.COMM_WORLD
args = parse()
'''parameters initialization block'''
# Data Read here
args.fpath = 'data/'
args.fname = 'wtsi'
args.ftype = 'mat'
args.precision = np.float32
#Distributed Comm config block
p_r, p_c = 4, 1
#NMF config block
args.norm = 'kl'
args.method = 'mu'
args.init = 'nnsvd'
args.itr = 5000
args.verbose = True
#Cluster config block
args.start_k = 2
args.end_k = 5
args.sill_thr = 0.9
#Data Write
args.results_path = 'results/'
'''Parameters prep block'''
comms = MPI_comm(comm, p_r, p_c)
comm1 = comms.comm
rank = comm.rank
size = comm.size
args.size, args.rank, args.comm, args.p_r, args.p_c = size, rank, comms, p_r, p_c
args.row_comm, args.col_comm, args.comm1 = comms.cart_1d_row(), comms.cart_1d_column(), comm1
A_ij = data_read(args).read().astype(args.precision)
nopt = PyNMFk(A_ij, factors=None, params=args).fit()
print('Estimated k with NMFk is ',nopt)
```
See the resources for more use cases.
<hr/>
## Authors:
* [Manish Bhattarai](mailto:[email protected]) - Los Alamos National Laboratory
* [Ben Nebgen](mailto:[email protected]) - Los Alamos National Laboratory
* [Erik Skau](mailto:[email protected]) - Los Alamos National Laboratory
* [Maksim Eren](mailto:[email protected]) - Los Alamos National Laboratory
* [Gopinath Chennupati](mailto:[email protected]) - Los Alamos National Laboratory
* [Raviteja Vangara](mailto:[email protected]) - Los Alamos National Laboratory
* [Hristo Djidjev](mailto:[email protected]) - Los Alamos National Laboratory
* [John Patchett](mailto:[email protected]) - Los Alamos National Laboratory
* [Jim Ahrens](mailto:[email protected]) - Los Alamos National Laboratory
* [Boian Alexandrov](mailto:[email protected]) - Los Alamos National Laboratory
## Citation:
```@inproceedings{bhattarai2020distributed,
title={Distributed Non-Negative Tensor Train Decomposition},
author={Bhattarai, Manish and Chennupati, Gopinath and Skau, Erik and Vangara, Raviteja and Djidjev, Hristo and Alexandrov, Boian S},
booktitle={2020 IEEE High Performance Extreme Computing Conference (HPEC)},
pages={1--10},
year={2020},
organization={IEEE}
}
```
```@article{chennupati2020distributed,
title={Distributed non-negative matrix factorization with determination of the number of latent features},
author={Chennupati, Gopinath and Vangara, Raviteja and Skau, Erik and Djidjev, Hristo and Alexandrov, Boian},
journal={The Journal of Supercomputing},
pages={1--31},
year={2020},
publisher={Springer}
}
```
## Acknowledgments:
Los Alamos National Lab (LANL), T-1
## Copyright Notice:
© (or copyright) 2020. Triad National Security, LLC. All rights reserved.
This program was produced under U.S. Government contract 89233218CNA000001 for Los Alamos
National Laboratory (LANL), which is operated by Triad National Security, LLC for the U.S.
Department of Energy/National Nuclear Security Administration. All rights in the program are
reserved by Triad National Security, LLC, and the U.S. Department of Energy/National Nuclear
Security Administration. The Government is granted for itself and others acting on its behalf a
nonexclusive, paid-up, irrevocable worldwide license in this material to reproduce, prepare
derivative works, distribute copies to the public, perform publicly and display publicly, and to permit
others to do so.
## License:
This program is open source under the BSD-3 License.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
3. Neither the name of the copyright holder 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.
| 36.111675 | 455 | 0.772702 | eng_Latn | 0.723881 |
a6eb19a1bccdf5b5aa3f395d75cccbc5aca8f42f | 360 | md | Markdown | components/TimePicker/__demo__/disabled.md | Slartbartfast1/arco-design | 4a3ba72f38babef82497131633ee10d86a1bbd32 | [
"MIT"
] | 1 | 2022-02-26T01:29:19.000Z | 2022-02-26T01:29:19.000Z | components/TimePicker/__demo__/disabled.md | leexiaoshaung/arco-design | 6b45569dd52699a7846a8a997483d6f03a1c779d | [
"MIT"
] | 2 | 2022-02-22T03:16:50.000Z | 2022-03-05T04:10:55.000Z | components/TimePicker/__demo__/disabled.md | leexiaoshaung/arco-design | 6b45569dd52699a7846a8a997483d6f03a1c779d | [
"MIT"
] | 1 | 2022-03-29T01:51:59.000Z | 2022-03-29T01:51:59.000Z | ---
order: 3
title:
zh-CN: 禁用
en-US: Disabled
---
## zh-CN
禁用状态。
## en-US
Disabled.
```js
import { TimePicker } from '@arco-design/web-react';
ReactDOM.render(
<div>
<TimePicker disabled style={{ margin: '0 24px 24px 0' }} />
<TimePicker.RangePicker disabled style={{ width: 252, margin: '0 24px 24px 0' }} />
</div>,
CONTAINER
);
```
| 12.857143 | 87 | 0.597222 | kor_Hang | 0.331063 |
a6eb3c2b9da41695217fabb31932a8ad21d90877 | 8,389 | md | Markdown | README.md | groner/desk | 252e6834b4a4a535fe905c6087e7eecfda70e040 | [
"MIT"
] | 2,690 | 2015-10-25T00:51:59.000Z | 2022-03-23T23:03:10.000Z | README.md | groner/desk | 252e6834b4a4a535fe905c6087e7eecfda70e040 | [
"MIT"
] | 76 | 2015-10-25T08:11:26.000Z | 2021-06-10T04:23:55.000Z | README.md | groner/desk | 252e6834b4a4a535fe905c6087e7eecfda70e040 | [
"MIT"
] | 133 | 2015-10-25T12:57:34.000Z | 2021-09-13T23:36:23.000Z |
# ◲ desk
[](https://travis-ci.org/jamesob/desk) [](https://gitter.im/jamesob/desk?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
Lightweight workspace manager for the shell.
Desk makes it easy to flip back and forth between different project contexts in
your favorite shell. Change directory, activate a virtualenv or rvm, load
in domain-specific aliases, environment variables, functions, arbitrary shell files,
all in a single command.
Instead of relying on `CTRL-R` to execute and recall ("that command's gotta
be here somewhere..."), desk helps shorten and document those actions with
shell aliases and functions, which are then namespaced under a particular
desk.
Because Deskfiles are just enriched shell scripts, the possibilities are
endless. For example, when doing work on AWS I have desk
securely load AWS API keys into environment variables via
[`pass`](https://www.passwordstore.org/) -- no effort on my part, and no
risk of accidentally persisting that sensitive information to a history file.
<img src='screencap.gif' width=700>
I have a hard time calling this a "workspace manager" with a straight
face -- it's basically just a shell script that sources another shell script in a new shell.
But I often find myself working in multiple different code trees simultaneously:
the quick context switches and namespaced commands that desk facilitates
have proven useful.
There are no dependencies other than `bash`. Desk is explicitly tested with `bash`,
`zsh`, and `fish`.
```sh
◲ desk 0.6.0
Usage:
desk
List the current desk and any associated aliases. If no desk
is being used, display available desks.
desk init
Initialize desk configuration.
desk (list|ls)
List all desks along with a description.
desk (.|go) [<desk-name-or-path> [shell-args...]]
Activate a desk. Extra arguments are passed onto shell. If called with
no arguments, look for a Deskfile in the current directory. If not a
recognized desk, try as a path to directory containing a Deskfile.
desk run <desk-name> <cmd>
Run a command within a desk's environment then exit. Think '$SHELL -c'.
desk edit [desk-name]
Edit (or create) a deskfile with the name specified, otherwise
edit the active deskfile.
desk help
Show this text.
desk version
Show version information.
Since desk spawns a shell, to deactivate and "pop" out a desk, you
simply need to exit or otherwise end the current shell process.
```
For example, given this deskfile (`~/.desk/desks/tf.sh`):
```sh
# tf.sh
#
# Description: desk for doing work on a terraform-based repository
#
cd ~/terraform-repo
# Set up AWS env variables: <key id> <secret>
set_aws_env() {
export AWS_ACCESS_KEY_ID="$1"
export AWS_SECRET_ACCESS_KEY="$2"
}
# Run `terraform plan` with proper AWS var config
plan() {
terraform plan -module-depth=-1 \
-var "access_key=${AWS_ACCESS_KEY_ID}" \
-var "secret_key=${AWS_SECRET_ACCESS_KEY}"
}
# Run `terraform apply` with proper AWS var config
alias apply='terraform apply'
```
we'd get
```sh
$ desk . tf
$ desk
tf
desk for doing work on a terraform repo
set_aws_env Set up AWS env variables: <key id> <secret>
plan Run `terraform plan` with proper AWS var config
apply Run `terraform apply` with proper AWS var config
```
Basically, desk just associates a shell script (`name.sh`) with a name. When
you call `desk . name`, desk drops you into a shell where `name.sh` has been
executed, and then desk extracts out certain comments in `name.sh` for useful
rendering.
### Installing
#### With homebrew
`brew install desk`
#### With curl
Assuming `~/bin` exists and is on the PATH... otherwise, substitute `/usr/local/bin`
and add `sudo` as needed.
0. `curl https://raw.githubusercontent.com/jamesob/desk/master/desk > ~/bin/desk`
0. `chmod +x ~/bin/desk`
#### With git
0. `git clone [email protected]:jamesob/desk.git && cd desk && sudo make install`
After that, run `desk init` and start adding deskfiles with either `desk edit [deskfile name]`
or by manually adding shell scripts into your deskfiles directory (by default `~/.desk/desks/`).
### Enabling shell extensions
**NB**: Shell extensions are automatically enabled if Desk is installed via Homebrew.
#### Using bash
0. Add `source /path/to/desk/repo/shell_plugins/bash/desk` to your `.bashrc`.
#### Using fish
```fish
mkdir -p ~/.config/fish/completions
cp /path/to/desk/repo/shell_plugins/fish/desk.fish ~/.config/fish/completions
```
#### Using zsh
0. Add `fpath=(/path/to/desk/repo/shell_plugins/zsh $fpath)` to your `.zshrc`.
Optionally, use one of the zsh plugin frameworks mentioned below.
#### Using [oh-my-zsh](http://ohmyz.sh/)
0. `make oh-my-zsh` from within this repo. This sets up a symlink.
or
0. `cd ~/.oh-my-zsh/custom/plugins`
0. `git clone [email protected]:jamesob/desk.git /tmp/desk && cp -r /tmp/desk/shell_plugins/zsh desk`
0. Add desk to your plugin list
#### Using [Antigen](https://github.com/zsh-users/antigen)
0. Add `antigen bundle jamesob/desk shell_plugins/zsh` to your `.zshrc`
0. Open a new terminal window. Antigen will clone the desk repo and add it to your path.
#### Using [zgen](https://github.com/tarjoilija/zgen)
0. Add `zgen load jamesob/desk shell_plugins/zsh` to your `.zshrc` with your other load commands
0. `rm ~/.zgen/init.zsh`
0. Start a new shell; zgen will generate a new `init.zsh` and automatically clone the desk repository for you and add it to your path.
### Deskfile rules
Deskfiles are just shell scripts, nothing more, that live in the desk config directory.
Desk does pay attention to certain kinds of comments, though.
- *description*: you can describe a deskfile by including `# Description: ...`
somewhere in the file.
- *alias and function docs*: if the line above an alias or function is a
comment, it will be used as documentation.
### Deskfiles
Deskfiles are just shell scripts at the root of a project directory that
adhere to the conventions above. These can be put into version control to
formalize and ease common development tasks like running tests or doing
local builds.
For example, if we have some directory or repository called `myproject`, if
we create `myproject/Deskfile`, we'll be able to do any of the following:
```sh
$ desk go /path/to/myproject/
$ desk go /path/to/myproject/Deskfile
myproject/ $ desk go .
myproject/ $ desk go
```
### Sharing deskfiles across computers
Of course, the desk config directory (by default `~/.desks`) can be a symlink
so that deskfiles can be stored in some centralized place, like Dropbox,
and so shared across many computers.
### Using a non-default config location
By default, desk configuration lives in `~/.desk` (`$DESK_DIR`) and deskfiles
live in `~/.desk/desks` (`$DESK_DESKS_DIR`). If you want to use some other
location, specify as much in `desk init` and then ensure you set `$DESK_DIR`
and/or `$DESK_DESKS_DIR` to match in your shell's rc file.
### Shortening invocation
Typing `desk .` frequently can get old; personally, I like to alias this with
```sh
alias d.='desk .'
```
in my shell rc file.
### Usage with OS X
Desk won't work when used strictly with `~/.bash_profile` on OS X's terminal, since
the content of `~/.bash_profile` is only executed on *login*, not shell creation, as
explained [here](http://www.joshstaiger.org/archives/2005/07/bash_profile_vs.html).
My recommendation is to use `~/.bashrc` as your general-purpose config file, then simply
have `~/.bash_profile` point to it:
```sh
# ~/.bash_profile
if [ -f ~/.bashrc ]; then
source ~/.bashrc
fi
```
### Related projects
- [godesk](https://github.com/hamin/godesk) by @hamin: a desk launcher with fuzzy filtering
### Tips accepted
BTC: `18ehgMUJBqKc2Eyi6WHiMwHFwA8kobYEhy`
Half of all tips will be donated to [an organization providing aid to Syrian refugees](http://www.moas.eu/).
#### Donations made on behalf of tippers
| date | amount | organization |
| ---- | ------ | ------------ |
| 2015-11-18 | $1.07 | http://moas.eu |
| 2016-11-14 | $21.00 | http://moas.eu |
| 32.642023 | 305 | 0.723447 | eng_Latn | 0.975912 |
a6eb4e49f8842b372a6f6bac657829b3e12e1375 | 1,010 | md | Markdown | README.md | blenderskool/fake-news-detector-fd | 3ca3e09df68644a396523c93f50b84c2fe0fcf9e | [
"MIT"
] | 1 | 2018-08-22T14:11:59.000Z | 2018-08-22T14:11:59.000Z | README.md | blenderskool/fake-news-detector-fd | 3ca3e09df68644a396523c93f50b84c2fe0fcf9e | [
"MIT"
] | 19 | 2018-08-24T11:15:31.000Z | 2021-07-23T14:57:31.000Z | README.md | blenderskool/fake-news-detector-fd | 3ca3e09df68644a396523c93f50b84c2fe0fcf9e | [
"MIT"
] | 4 | 2018-08-22T14:12:55.000Z | 2019-04-14T08:40:19.000Z | # Defaux news checker app
A news checker app which allows you to check whether news is real or fake by entering its title. It makes use of multiple sources to gather fake news, including those which **seem real**, as satirical articles are usually the hardest to differentiate between.
This repository is for the frontend progressive web app which makes use of our backend's HTTP API to check news status. This web app comes with an easy to use interface, that makes checking the trustworthiness of news really easy.
**Backend repository can be found on https://gitlab.com/neelkamath/news-checker**
## Installation
### Prerequisites
- [node.js](https://nodejs.org/en/download/)
### Installing
1. `git clone https://github.com/blenderskool/fake-news-detector-fd.git`
1. `cd fake-news-detector-fd`
1. `npm install`
## Usage
- (For development) Compile and hot-reload: `npm run serve`
- (For production) Compile and minify: `npm run build`
## License
This project is under the [MIT License](LICENSE).
| 34.827586 | 259 | 0.758416 | eng_Latn | 0.994603 |
a6eba104a07b65700a8c6bfa9714d359a86ff18f | 3,438 | md | Markdown | README.md | dipbazz/math-magicians | 4ee4b28636b73f860d6ecb2115a43284bb3857da | [
"CC0-1.0"
] | 4 | 2021-05-03T12:51:57.000Z | 2021-05-05T22:06:16.000Z | README.md | dipbazz/math-magicians | 4ee4b28636b73f860d6ecb2115a43284bb3857da | [
"CC0-1.0"
] | 1 | 2021-05-10T07:51:22.000Z | 2021-05-10T07:51:22.000Z | README.md | dipbazz/math-magicians | 4ee4b28636b73f860d6ecb2115a43284bb3857da | [
"CC0-1.0"
] | null | null | null | 
# Calculator app with React
---
## About
This is a calculator app built using React.js which performs simple math operations like; Addition, Subtraction, Multiplication, Division, Percentage, and negation.
### How to use the calculator app.
To perform the operations:
- User should select the first value from the number button (0 - 9)
- User should select the operation buttons (-, +, x, ÷, %)
- User should select the next value for calculation
- Finally, the user can select the '=' button to perform the calculations.
## Getting the app in the local machine.
### Installation instructions
- Clone the repo and navigate to the directory
- Install the npm package with `npm install`
- Start the server with `npm start`
- Open your browser at http://localhost:3000/ and start to perform your calculation.
## Available Scripts
In the project directory, you can run:
### `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.
### `npm test`
Launches the test runner in the interactive watch mode.\
See the section about [running tests](https://facebook.github.io/create-react-app/docs/running-tests) for more information.
### `npm run build`
Builds the app for production to the `build` folder.\
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.\
Your app is ready to be deployed!
See the section about [deployment](https://facebook.github.io/create-react-app/docs/deployment) for more information.
### `npm run eject`
**Note: this is a one-way operation. Once you `eject`, you can’t go back!**
If you aren’t satisfied with the build tool and configuration choices, you can `eject` at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except `eject` will still work, but they will point to the copied scripts so you can tweak them. At this point, you’re on your own.
You don’t have to ever use `eject`. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However, we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
## Features
The features of this calculator app are:
- It performs basic mathematical operations like; Addition, Subtraction, Multiplication, Division, Percentage, and negation.
## Live Demo
This project is hosted on netlify.
[Live demo link](https://math-magicians-db.netlify.app/)
## Built With
- React.js
- Big.js
- prop-types
## Authors
👤 **Dipesh Bajgain**
- GitHub: [@dipbazz](https://github.com/dipbazz)
- Twitter: [@dipbazz](https://twitter.com/dipbazz)
- LinkedIn: [Dipesh Bajgain](https://www.linkedin.com/in/dipbazz/)
## 🤝 Contributing
Contributions, issues, and feature requests are welcome!
## Show your support
Give a ⭐️ if you like this project!
<!-- ## Acknowledgments -->
## 📝 License
This project is [CC0](./LICENSE) licensed.
| 32.130841 | 323 | 0.748691 | eng_Latn | 0.995823 |
a6ebef62a3297c75bd5fed50bcdf62c01f8f4420 | 218 | md | Markdown | Git/git 分支.md | fengjixuchui/Document-1 | 62c74d94c4f16f94f4a5e473636d3248af0c37fe | [
"Apache-2.0"
] | 1 | 2021-02-26T02:40:03.000Z | 2021-02-26T02:40:03.000Z | Git/git 分支.md | fengjixuchui/Document-1 | 62c74d94c4f16f94f4a5e473636d3248af0c37fe | [
"Apache-2.0"
] | null | null | null | Git/git 分支.md | fengjixuchui/Document-1 | 62c74d94c4f16f94f4a5e473636d3248af0c37fe | [
"Apache-2.0"
] | null | null | null | ## 本地分支重命名
```
git branch -m oldname newname
```
## 远程分支重命名
> 如果修改远程分支，只需要将本地分支重命名为新分支名称，然后删除远程分支，再把本地分支上传即可
## 本地分支删除
```
git branch -D branchName
```
## 远程分支删除
```
git push origin :branchName (origin后面有空格)
``` | 10.380952 | 48 | 0.674312 | yue_Hant | 0.788252 |
a6ec35a4bac06c9b32108766ca9fe7ef4db6d105 | 12,824 | md | Markdown | _posts/2020-09-02-DRBD.md | nomadli/nomadli.github.io | d4e3722e721eabe14bc478e55d886981a559734c | [
"MIT"
] | 2 | 2017-06-20T08:52:37.000Z | 2019-03-28T08:02:42.000Z | _posts/2020-09-02-DRBD.md | nomadli/nomadli.github.io | d4e3722e721eabe14bc478e55d886981a559734c | [
"MIT"
] | null | null | null | _posts/2020-09-02-DRBD.md | nomadli/nomadli.github.io | d4e3722e721eabe14bc478e55d886981a559734c | [
"MIT"
] | null | null | null | ---
layout: post
title: DRBD
subtitle: Distributed Repliated Block Device 9
date: 2020-09-02 11:15:00
author: nomadli
header-img: ../img/bg-coffee.jpeg
catalog: true
tags:
- other
---
* content
{:toc}
## 特性
- 内核IO底层, 对应用基本透明,在磁盘格式、分布式锁等下面,因此无法提供高层功能。
- 单主模式 允许任意磁盘格式、可靠性高、支持故障转移。从节点磁盘不能挂载,即不能读写
- 双主模式 允许在分布式磁盘系统上使用如GFS、OCFS2等。默认禁止,可能会出现问题。用于高可用分布式。
- 复制协议A, 主节点写入磁盘并且将数据写入本地发送buf返回写入成功信号
- 复制协议B, 主节点写入磁盘并且数据已经写入从节点接收buf,返回成功写入信号
- 复制协议C, 主从节点都写入磁盘返回写入成功信号
- 版本9以后支持多从接地,最多16节点
- 版本9以后当启用auto promote选项使用drbdadm primary命令变主节点时,将自动装载卷并开始同步。
- 支持TCP和RDMA两种传输模式,RDMA模式CPU不参与网络传输
- 网络或机器故障恢复后,使用磁盘物理线性块同步,速度快、无需磁盘寻址。
- 同步进行时采用了LVM的快照模式,主节点可以继续读写
- 8.4版本后, 同步会检测网络情况自动调节同步速度、也可以配置固定速率同步
- 可以开启基于hash算法的同步、减少相同块覆盖。
- 复制可能会因为网络拥塞而暂停,情况好转后自动同步
- 可以启用定时任务进行在线磁盘同步校验
- 启用复制流hash校验,防止网络无法校验的位翻转. 网卡与主存间出现的位翻转
- 人为或keeplive哨兵逻辑错误导致的多主数据不统一有四种情况自动恢复,或采用邮件通知手动恢复
- 在支持磁盘刷新的设备上可以启用磁盘刷新,防止断电导致的磁盘缓存未写入。带UPS的磁盘可以关闭磁盘刷新
- 8.4.3后自动支持固态硬盘或其它速写卡的Trim/Discard命令,可以瞬间删除或格式化磁盘
- IO错误可以配置传递给上层或不传递,不传递将使用无盘模式,即只写入IO正常的节点。直到恢复
- 当节点正在同步或复制过程中发生中断,磁盘被标记数据不一致,会禁止变为主节点。当过时节点可以变主
- 三路复制已经弃用,即有两天链路可以选择不同的协议复制,也可以使用定时备份的模式
- 可设置复制代理提供缓存,缓解网络压力,并提供块压缩功能
- 采用浮动节点配置,可以使用IP而不是主机名作为节点标识
- 对于大量数据可以采用离线同步,然后开启复制
- 支持水平存储扩展,即块在多节点上冗余数据,而不是完全相同
- 在实现冗余的基础上负载均衡读操作
- 配置仲裁可以实现IO错误时自动切换,仲裁也可配置在一台非磁盘节点的服务器上
- 9.0.25后支持centos8内核模块签名(Secure Boot / Kernel module signing)
- [vcs](https://github.com/LINBIT/drbd-utils/tree/master/scripts/VCS) 这是商业实现
## 资源
- 资源是一组复制集的集合,最多可以有65536个磁盘卷
## 网络
- ipv4 ipv6
- SuperSockets 使用RDMA模式,只有Dolphin Interconnect Solutions网卡支持,无CPU参与
- InfiniBand HCAs、支持iWARP的NICs或支持RoCE的NICs网卡上实现RDMA传输,需少量CPU参与
## 脑裂自动恢复
- 放弃较新主节点上的修改,最后变为主节点的修改被弃用
- 放弃较旧主节点上的修改,最早变为主节点的修改被弃用
- 放弃改动小的主节点上的修改
- 只有一个节点有写入,直接恢复
## 安装
```shell
yum install -y https://www.elrepo.org/elrepo-release-7.el7.elrepo.noarch.rpm
yum install -y drbd90 kmod-drbd90
https://github.com/LINBIT 源码安装
iptables -I INPUT -p tcp --dport 7788:7799 -j ACCEPT
iptables-save > /etc/sysconfig/iptables
/etc/DRBD.conf 包含 /etc/drbd.d/global_common.conf /etc/drbd.d/*.res 所有节点相同
vi /etc/drbd.d/global_common.conf
global {
usage-count no;
}
common {
net {
protocol C; //A B
transport "tcp";//rdma
allow-two-primaries no; //双主模式
verify-alg sha1; //md5、crc32c 在线磁盘同步校验
csums-alg sha1; //md5、crc32c 复制同步差异校验方法
data-integrity-alg sha1; //md5、crc32c 复制数据传输正确性校验
//拥塞策略
on-congestion pull-ahead;
congestion-fill 2G;
congestion-extents 2000;
//脑裂
after-sb-0pri://裂脑被检测到，但此时资源在任何主机上都不是主要角色。
disconnect;不要自动恢复，调用split brain处理程序脚本如果已配置,断开连接并以断开模式继续。
discard-younger-primary;放弃并回滚对最后担任主服务器角色的主机所做的修改。
discard-least-changes;丢弃并回滚发生较少更改的主机上的更改。
discard-zero-changes;如果有任何主机根本没有发生任何更改，只需在另一个主机上应用所做的所有修改并继续。
after-sb-1pri: 裂脑被检测到，此时资源在一个主机上扮演主要角色
disconnect;与 after-sb-0pri 一样。
consensus;应用 after-sb-0pri 中指定的相同恢复策略。如果在应用这些策略后可以选择裂脑受害者，则自动解决。否则，行为就像指定了 disconnect 一样。
call-pri-lost-after-sb;应用 after-sb-0pri 中指定的恢复策略。如果在应用这些策略后可以选择裂脑受害者，请调用受害者节点上的 pri-lost-after-sb 处理程序。必须在 handlers 部分中配置此处理程序，并要求将节点从集群中强制删除。
discard-secondary;无论哪个主机当前处于第二个角色，使该主机成为裂脑受害者
after-sb-2pri:裂脑被检测到，此时资源在两个主机上都处于主要角色
disconnect;与 after-sb-0pri 一样。
//安装drbd-proxy和drbd-proxy.license后
proxy {
memlimit 512M;
plugin {
zlib level 9;
}
}
}
}
vi /etc/drbd.d/mydisk.res
resource mydisk {
net {
protocol C; //A B
transport "tcp";//rdma
}
disk {
c-plan-ahead 5; //5秒检测一次网络动态调整速率
c-max-rate 10M; //最大使用1M的带宽
c-fill-target 2M; //
on-io-error detach; //发生IO错误丢弃备份设备以无盘模式运行
on-io-error pass_on; //IO发生在主节点报告错误,次节点忽略
on-io-error call-local-io-error;//调用自定义IO错误处理程序
//如果只有部分主机有缓存可以把disk移动到on hostname节点里面
disk-flushes yes; //启用复制数据的强制磁盘刷新
md-flushes yes; //元数据的强制磁盘刷新
}
disk {
c-plan-ahead 0; //固定速率
cresync-rate 10M; //10M带宽
}
handlers { // 可以使用任何系统命令
split-brain "/usr/lib/drbd/notify-split-brain.sh root";//数据脑裂逻辑, 将邮件通知root
}
volume 0 {
device /dev/drbd1;
disk /dev/sda7;
meta-disk internal;
}
volume 1 {
device /dev/drbd2;
disk /dev/sda8;
meta-disk internal;
}
//链接数是 n*(n-1)/2
//单网卡
on hostname-1 {
address 10.1.1.31:7789;
node-id 0;
proxy on ostname-1 {
inside 127.0.0.1:7815; 节点与代理通信
outside 192.168.23.1:7715; 代理间通信
}
}
on hostname-2 {
address 10.1.1.32:7789;
node-id 1;
}
on hostname-3 {
address 10.1.1.33:7789;
node-id 2;
}
connection-mesh {
hosts hostname-1 hostname-2 hostname-3;
}
//多网卡
connection {
host hostname-1 address 10.1.2.1:7010;
host hostname-2 address 10.1.2.2:7001;
}
connection {
host hostname-1 address 10.1.3.1:7020;
host hostname-3 address 10.1.3.2:7002;
}
connection {
host hostname-2 address 10.1.4.1:7021;
host hostname-3 address 10.1.4.2:7012;
}
}
drbdadm create-md --max-peers=xx mydisk //初始化元数据
提示 drbdmeta 1 v09 /dev/xxx internal create-md x terminated with exit code 40 磁盘空不能判断大小
dd if=/dev/zero of=/dev/xxx bs=1M count=100 写入100M数据
drbdadm up mydisk //启用资源
drbdadm status mydisk //查看资源状态
drbdadm primary --force mydisk //同步原始数据,在一台要保留数据的节点上执行,其它节点数据丢失
drbdadm status mydisk //查看资源同步状态
drbdadm status mydisk --verbose --statistics
mkfs.ext4 /dev/drbdx
mount /dev/drbdx /xxx
//或离线同步
//保留数据的机器上执行
drbdadm new-current-uuid --clear-bitmap mydisk/volume 0
drbdadm new-current-uuid --clear-bitmap mydisk/volume 1
使用RAD-1或按位复制(dd命令)到临时挂载的备份机的磁盘上
drbdadm new-current-uuid mydisk
//在备份机上执行
将磁盘插入备份机,在磁盘未使用情况下,执行命令将节点ID修改
drbdadm -- --force [--stacked 堆栈需要] dump-md mydisk/volume0 > /tmp/md_orig.txt
sed -e "s/node-id 1/node-id 0/" \
-e "s/^peer.1. /peer-NEW /" \
-e "s/^peer.0. /peer[1] /" \
-e "s/^peer-NEW /peer[0] /" \
< /tmp/md_orig.txt > /tmp/md.txt
drbdmeta --force [--stacked 堆栈需要] $(drbdadm sh-minor mydisk/volume0) v09 $(drbdadm sh-ll-dev mydisk/volume0) inter
mydisk/volume1 也是相同的操作
drbdadm up mydisk //启用资源
节点连接建立后,只会同步及复制后期变化的数据
drbdsetup events2 --now –statistics –timestamp mydisk 更底层的监控
drbdadm cstate mydisk 链接状态
drbdadm cstate hostname-1:mydisk 只看单个节点的链接状态
drbdadm role mydisk 查看节点角色
drbdadm dstate mydisk 磁盘状态
drbdadm down mydisk 禁用资源
故障切换
主节点
umount /dev/drbd/by-res/mydisk/volume0
drbdadm secondary mydisk 将节点降为从节点
从节点
drbdadm primary mydisk 将节点提升为主节点
mount /dev/drbd/by-res/mydisk/volume0 <mountpoint>
升级
systemctl stop drbd
yum upgrade
rmmod drbd 卸载旧内核,如果出现错误应该是有些资源没有停止 drbdadm down all
modprobe drbd 加载新内核
drbdadm dump all 可以将旧的配置导出为新版的配置 大版本变动
drbdadm create-md --max peers=xx mydisk 更改元数据 大版本变动需要
drbdadm up mydisk 启动同步
systemctl start drbd
drbdadm net-options --protocol=C --allow-two-primaries mydisk 临时允许双主
drbdadm net-options --protocol=C --allow-two-primaries=no mydisk 停止
drbdadm verify mydisk 联机验证磁盘
如果校验不同步,调用下面命令重新同步
drbdadm disconnect mydisk
drbdadm connect mydisk
修改配置->同步所有节点配置->drbdadm adjust mydisk
drbdadm resize mydisk 在线扩容,次扩容的是逻辑卷如LVM,此时只能有一个主
drbdadm -- --assume-clean resize mydisk 扩容磁盘数据为空跳过同步
drbdadm resize --size=xxK|M|G mydisk 在线缩容
如果扩容非逻辑块设备, 且使用external meta data
drbdadm down mydisk
添加磁盘
drbdadm up mydisk
如果扩容非逻辑块设备, 且使用internal meta data
drbdadm down mydisk
drbdadm dump-md mydisk > /tmp/metadata 每个节点
添加磁盘
编辑/tmp/metadata 在扇区中修改la-size-sect
drbdadm create-md mydisk
drbdmeta_cmd=$(drbdadm -d dump-md mydisk)
${drbdmeta_cmd/dump-md/restore-md} /tmp/metadata
drbdadm up mydisk
drbdadm primary mydisk
离线缩容块设备都与internal meta data类似,只是external meta data无需导入导出
drbdadm dstate all 将显示所有资源, all 可以用在所有资源名的地方
drbd-proxy-ctl -c 代理配置
```
## 节点角色 drbdadm role all
- Primary 主角色中，可以读取和写入。此角色仅在两个节点中的一个节点上发生，除非启用了dual-primary mode
- Secondary 资源当前处于辅助角色中。它通常从其对等方接收更新（除非在断开连接模式下运行），但既不能读取也不能写入
- Unknown 对等方的资源角色显示，并且仅在断开连接模式下显示。
## 网络状态 drbdadm cstate all
- StandAlone 没有可用的网络配置。资源尚未连接，或者已被管理性断开(使用 drbdadm disconnect)，或者由于身份验证失败或脑裂而断开其连接。
- Disconnecting 断开连接期间的临时状态。下一个状态是 StandAlone。
- Unconnected 临时状态，在尝试连接之前。可能的下一个状态： Connecting。
- Timeout 与对等方通信超时后的临时状态。下一个状态：Unconnected。
- BrokenPipe 与对等方的连接丢失后的临时状态。下一个状态： Unconnected 。
- NetworkFailure 与伙伴的连接丢失后的临时状态。下一个状态： Unconnected。
- ProtocolError 与伙伴的连接丢失后的临时状态。下一个状态：Unconnected。
- TearDown 临时状态。对等方正在关闭连接。下一个状态： Unconnected。
- Connecting 此节点正在等待，直到对等节点在网络上变为可见
- Connected 已建立DRBD连接，数据镜像现在处于活动状态。这是正常状态。
## 复制状态
- Off 由于连接未连接，因此卷未通过此连接进行复制。
- Established 对该卷的所有写入都将在线复制。这是正常状态。
- StartingSyncS 由管理员启动的完全同步正在启动。下一个可能是:SyncSource 或 PausedSyncS
- StartingSyncT 由管理员启动的完全同步正在启动。下一个状态：WFSyncUUID。
- WFBitMapS 部分同步刚刚开始。下一个可能的状态：SyncSource_或_PausedSyncS。
- WFBitMapT 部分同步刚刚开始。下一个可能的状态：WFSyncUUID。
- WFSyncUUID 同步即将开始。下一个可能的状态：SyncTarget_或_PausedSyncT。
- SyncSource 同步当前正在运行，本地节点是同步源。
- SyncTarget 同步当前正在运行，本地节点是同步的目标。
- PausedSyncS 本地节点是正在进行的同步的源，但同步当前已暂停。这可能是由于依赖于另一个同步进程的完成，或者是由于同步已被 drbdadm pause sync 手动中断。
- PausedSyncT 本地节点是正在进行的同步的目标，但同步当前已暂停。这可能是由于依赖于另一个同步进程的完成，或者是由于同步已被 drbdadm pause sync 手动中断。
- VerifyS 联机设备验证当前正在运行，本地节点是验证源。
- VerifyT 联机设备验证当前正在运行，本地节点是验证的目标。
- Ahead Data replication was suspended, since the link can not cope with the load. This state is enabled by the configuration on-congestion option
- Behind 数据复制被对等方挂起，因为链接无法处理负载。此状态由对等节点上的配置 on-congestion 选项启用
## 磁盘状态 drbdadm dstate all
- Diskless 没有为DRBD驱动程序分配本地块设备。这可能意味着资源从未连接到其备份设备，它已使用 drbdadm detach 手动分离，或者在发生较低级别的I/O错误后自动分离。
- Attaching 读取元数据时的临时状态。
- Detaching 在分离并等待正在进行的IOs完成时的临时状态。
- Failed 本地块设备报告I/O失败后的瞬态。下一个状态：Diskless。
- Negotiating 在 已经Connected 的DRBD设备上执行附加操作时的瞬态。
- Inconsistent 数据不一致。在两个节点上（在初始完全同步之前）创建新资源时立即出现此状态。此外，在同步期间，在一个节点（同步目标）中可以找到此状态。
- Outdated 资源数据一致，但outdated。
- DUnknown 如果没有可用的网络连接，则此状态用于对等磁盘。
- Consistent 没有连接的节点的一致数据。建立连接后，决定数据是 UpToDate 还是 Outdated。
- UpToDate 数据的一致、最新状态。这是正常状态。
## 用户态工具 DRBD-utils
- drbdadm 从/etc/DRBD.conf读取配置,作为drbdsetup drbdmeta的前端工具
- drbdadm \-d 选项可以模拟命令执行,查看哪些drbdsetup drbdmeta命令被调用
- drbdsetup 将配置加载到内核,用户一般无需直接调用该命令
- drbdmeta 创建、转储、还原和修改DRBD元数据结构,用户一般无需手动调用
- drbdmon 监控工具
- [drbdtop 交互监控](https://linbit.github.io/drbdtop/)
## 状态含义
- local 显示网络协议栈、用于接受来自对等方的连接的本地地址和端口。
- peer 显示网络协议栈、对等方节点地址和用于连接的端口。
- congested 此标志指示数据连接的TCP发送缓冲区是否已填充80%以上。
- send (network send) 通过网络连接发送给伙伴的网络数据量；单位为千字节。
- receive (network receive) 伙伴通过网络连接接收的网络数据量；单位为千字节。
- read (disk write) 写在本地硬盘上的网络数据；以千字节为单位。
- written (disk read) 从本地硬盘读取的网络数据；单位为千字节。
- al-writes (activity log) 元数据活动日志区域的更新次数。
- bm-writes (bit map) 元数据位图区域的更新次数。
- lower-pending (local count) DRBD向本地I/O子系统发出的打开请求数。
- pending 发送给合作伙伴但尚未由后者应答的请求数。
- unacked (unacknowledged) 伙伴通过网络连接接收但尚未应答的请求数。
- upper-pending (application pending) 转发给DRBD但尚未由DRBD应答的块I/O请求数。
- write-ordering (write order) 当前使用的写排序方法b(barrier), f(flush), d(drain) 或者 n(none).
- out-of-sync 当前不同步的存储量；单位为千字节。
- resync-suspended 重新同步是否当前挂起。可能的值是: no, user, peer, dependency.
- blocked 显示本地I/O拥塞
# 修复
- 有节点正常,Outdated节点 drbdadm disconnect sname && drbdadm connect sname
- 节点看不到其它节点, drbdadm down sname && drbdadm up sname
- StandAlone如果主节点正则 drbdadm disconnect sname && drbdadm connect --discard-my-data sname, 主节点下这台也是StandAlone,则主节点disconn && connect
- Inconsistent drbdadm invalidate sname && drbdadm down sname && drbdadm create-md sname && drbdadm adjust sname && drbdadm up sname
- 所有节点数据异常 选最后一台主机 drbdadm del-peer sname && drbdadm --force sname
| 33.836412 | 158 | 0.666173 | yue_Hant | 0.506069 |
a6ec9faf795b41ff42b2515a4ab1d9f1dc2ce496 | 1,155 | md | Markdown | docs/dev/API Docs/README.md | viveknigam3003/desktop | 48ddc27e888def0bb30e5fbad17afd99e9cdc576 | [
"Apache-2.0"
] | null | null | null | docs/dev/API Docs/README.md | viveknigam3003/desktop | 48ddc27e888def0bb30e5fbad17afd99e9cdc576 | [
"Apache-2.0"
] | null | null | null | docs/dev/API Docs/README.md | viveknigam3003/desktop | 48ddc27e888def0bb30e5fbad17afd99e9cdc576 | [
"Apache-2.0"
] | null | null | null | # Rucio Desktop : Developer Documentation
## API Reference
Rucio Desktop holds a client side node server which serves several easy REST APIs to connect to Rucio instances and also to the FUSE-POSIX interface.
Most of the APIs are wrappers around the [Rucio RESTful APIs](https://rucio.readthedocs.io/en/latest/rest.html) and simplify the workflow by combining some of them thorugh Javascript Promises and other methods.
ALl the REST API wrappers follow a single `POST` method and use [Axios](https://github.com/axios/axios) or [Superagent](https://visionmedia.github.io/superagent/) to send requests to Rucio Servers.
**Testing the APIs**
You can either test the APIs by command-line methods using cURL or you may use tools such as Postman to test the APIs.
## Available APIs
<!--ts-->
- [Authentication](https://github.com/rucio/desktop/blob/master/docs/dev/API%20Docs/API_Auth.md)
- [Server Config](https://github.com/rucio/desktop/blob/master/docs/dev/API%20Docs/API_Config.md)
- [FUSE Module](#fuse-module)
- [DID Metadata](#did-metadata)
- [Rucio RSEs](https://github.com/rucio/desktop/blob/master/docs/dev/API%20Docs/API_RSEs.md)
<!--te-->
| 48.125 | 211 | 0.764502 | eng_Latn | 0.78049 |
581d2c68f5c01a13955ce645aebede9193fbfb23 | 1,374 | md | Markdown | CHANGELOG.md | ntentan/honam | ba8583a90a4121828b707a96b7e3f68fc9b9758f | [
"Unlicense"
] | null | null | null | CHANGELOG.md | ntentan/honam | ba8583a90a4121828b707a96b7e3f68fc9b9758f | [
"Unlicense"
] | 3 | 2015-04-16T13:37:27.000Z | 2021-11-30T05:24:18.000Z | CHANGELOG.md | ntentan/honam | ba8583a90a4121828b707a96b7e3f68fc9b9758f | [
"Unlicense"
] | null | null | null | v0.6.5 - 2021-11-29
===================
Fixed
-----
- The `smarty` dependency to track the `v3.1.x` releases. Might consider switching to the PHP 8.0 version later.
Changed
-------
- The `PHPEngine` now uses the eval method to execute instrings instead of including the files directly.
v0.6.4 - 2020-05-15
===================
Fixed
-----
- The `Template` can now be used without injecting its dependencies.
- Styling and unset item notifications in pagination helper.
- Issue with form input helpers that cause exceptions to be thrown in some cases where a form's value is `null`.
- Pagination unit tests
v0.6.3 - 2020-02-06
===================
Fixed
-----
- Fixed broken dependencies in previous release.
v0.6.2 - 2019-11-23
===================
Added
-----
- Before attempting to resolve a template file, a check is made to find out if the file exists. If it does, it is used to render, and time is saved from template path resolution.
v0.6.1 - 2019-11-17
===================
Added
-----
- Added a `Template` class to act as an access point to all the underlying template functions. You can consider this a facade of some sort.
- Added a getter and setter for the path hierarchy in the template file resolver.
Fixed
-----
- Broken comparison in the input template for the form helper
v0.6.0 - 2019-05-27
===================
First release with a changelog
| 29.234043 | 179 | 0.666667 | eng_Latn | 0.997518 |
581d85a9d0814c442b909175f1155fba8d93366b | 5,368 | md | Markdown | README.md | rickellis/ConkyMatic | 21d4db84d6550cd5f0826a9f97942f8a6f1057c2 | [
"MIT"
] | 29 | 2018-03-02T13:58:51.000Z | 2022-03-26T07:18:48.000Z | README.md | rickellis/ConkyMatic | 21d4db84d6550cd5f0826a9f97942f8a6f1057c2 | [
"MIT"
] | 2 | 2018-02-23T17:04:10.000Z | 2018-02-25T23:23:26.000Z | README.md | rickellis/ConkyMatic | 21d4db84d6550cd5f0826a9f97942f8a6f1057c2 | [
"MIT"
] | 6 | 2018-06-12T16:10:03.000Z | 2021-08-20T15:46:29.000Z | # ConkyMatic
<img src="https://i.imgur.com/5C8xmwo.png" />
## ConkyMatic is a shell script that:
Automatically generates a Conky and weather icons that are color-matched to the current wallpaper.
### [YouTube Video](https://youtu.be/th6-7pRe-l4)
### When you run ConkyMatic it does the following:
* Automatically gets the path to your current wallpaper (or the path can be passed manually).
* Creates a 16 color palette image from the current wallpaper (look at the bottom of the Conky in the screenshots)
* Extracts the hex color value of each of the 16 images in the color palette.
* Generates a .conkyrc file using colors randomly selected from that palette.
* Exports a set of colorized weather icons.
* Copies the new .conkyrc file to the home folder and relaunches the Conky application.
The entire sequence takes the script about 10 seconds, making it very fast and easy to build a fresh conky every time you change your wallpaper. And since the colors are randomly selected (with some logic), running the script multiple times with the same wallpaper will yield different results.
__Note:__ The automatic path gathering feature only works if you use __XFCE desktop__, or if you use __feh__ to set your wallpaper. Read the [configuration](#configuration) section below for more info.
<img src="https://i.imgur.com/Za81gmK.png" />
## Requirements
* A __Linux__ installation with __Conky__ installed.
* __ImageMagick__ to generate the color palette PNG and weather icons. __Note:__ If you have __Inkscape__ is installed, ConkyMatic will use it for the weather icon rendering since it has better SVG handling. However, ImageMagick is still necessary for the palette generation.
* __Curl__ to download JSON weather data.
* __jq__ to parse JSON weather data.
* __Roboto Font__. The default Conky template uses [Roboto](https://www.dafont.com/roboto.font).
## Installation
Just clone or download the package.
## Configuration
If you open __conkymatic.sh__ with a text editor you'll see the following user configuration variables near the top of the file:
# Your city
YOUR_CITY="miami"
# Your US state (two letter abbreviation. Example: NY)
# If you are NOT in the US enter your country. Example: france
YOUR_REGION="fl"
# Temperature format
# f = fahrenheit
# c = celcius
TEMP_FORMAT="f"
# AUTOMATIC PATH MODE
# Sets the way in which ConkyMatic should get the path to your wallpaper. The options are:
#
# PATH_MODE="xfce" # Use this if you run XFCE Desktop
# PATH_MODE="feh" # Use this if you use feh to set your wallpaper
#
# NOTE: You can also pass the wallpaper path manually as an argument to the script:
#
# ./conkymatic.sh /path/to/your/wallpaper.jpg
#
# This setting will be ignored when a path is manually passed.
#
AUTO_PATH_MODE="xfce"
## Usage
Point your terminal to the directory containing __cokymatic__ and run it using:
$ ./conkymatic.sh
You can also manually pass the path to your wallpaper as an argument:
$ ./conkymatic.sh /path/to/your/wallpaper.jpg
__Important:__ Before running ConkyMatic make a backup copy of your .conkyrc file since it will get overwritten.
## ConkyMatic Terminal Alias
To make running the script more convenient you can add the following alias to your __.bashrc__ file, and then just enter __conkymatic__ from your terminal.
function conkymatic() {
$HOME/path/to/ConkyMatic/conkymatic.sh $@
}
__Note:__ Make sure you change the path in the function to reflect your particular path.
## Customization
In the __Templates__ directory you'll find the __default.conky__ template. This is a normal .conkyrc file, except it contains some pseudo-variables that get replaced by the script with random color values. A list of available variables can be found below.
Additional templates can be created and added to the __Templates__ folder. If more than one template is in the folder, when you run the __conkymatic.sh__ script via your terminal you'll be given a choice of templates. Hitting __ENTER__ in the terminal will auto-select the template named __default.conky__, or you can type the name of the one you prefer to run.
__IMPORTANT:__ all templates must be named with the __.conky__ file extension: Example: foobar.conky
## Template Variables
The template variables are just text placeholders which get replaced when the script gets run. The following variables are available for use. The colors will be assigned automatically from your wallpaper colors.
_VAR:COLOR_TIME_
_VAR:COLOR_DATE_
_VAR:COLOR_WEATHER_
_VAR:COLOR_HEADING_
_VAR:COLOR_SUBHEADING_
_VAR:COLOR_TEXT_
_VAR:COLOR_DATA_
_VAR:COLOR_HR_
_VAR:COLOR_BARS_NORM_
_VAR:COLOR_BARS_WARN_
_VAR:COLOR_BORDER_
_VAR:COLOR_BACKGROUND_
In addition, the following path variables are available:
_VAR:JSON_FILEPATH_
_VAR:CACHE_DIRECTORY_
_VAR:WEATHER_ICONS_PNG_DIRECTORY_
_VAR:COLOR_PALETTE_FILEPATH_
## License
MIT License
https://opensource.org/licenses/MIT
You may use the source code in any manner you choose, as long as appropriate credit is given.
<img src="https://i.imgur.com/Z6UPjym.png" />
<img src="https://i.imgur.com/lKZKCx3.png" />
<img src="https://i.imgur.com/rsVC1AX.png" />
<img src="https://i.imgur.com/udb0bqo.png" />
| 38.070922 | 361 | 0.756334 | eng_Latn | 0.983313 |
581dcfe87842ed9455a5f9acb4b7f65a0288c19e | 10,187 | md | Markdown | docs/zh/architecture/adr-033-protobuf-inter-module-comm.md | highwayns/cosmos_docs | eb157f6673fa798789a4e8a1017c22988cfe7560 | [
"MIT"
] | null | null | null | docs/zh/architecture/adr-033-protobuf-inter-module-comm.md | highwayns/cosmos_docs | eb157f6673fa798789a4e8a1017c22988cfe7560 | [
"MIT"
] | null | null | null | docs/zh/architecture/adr-033-protobuf-inter-module-comm.md | highwayns/cosmos_docs | eb157f6673fa798789a4e8a1017c22988cfe7560 | [
"MIT"
] | 1 | 2021-12-12T12:02:38.000Z | 2021-12-12T12:02:38.000Z | # ADR 033:基于 Protobuf 的模块间通信
## 变更日志
- 2020-10-05:初稿
## 地位
建议的
## 摘要
该 ADR 引入了一个系统，用于利用 protobuf `Query` 和 `Msg` 进行许可的模块间通信
[ADR 021](./adr-021-protobuf-query-encoding.md) 中定义的服务定义和
[ADR 031](./adr-031-msg-service.md) 提供:
- 稳定的基于 protobuf 的模块接口可能会在以后取代 keeper 范式
- 更强的模块间对象能力(OCAPs)保证
- 模块账号和子账号授权
## 语境
在当前的 Cosmos SDK 文档中关于 [Object-Capability Model](../core/ocap.md)，它指出:
> 我们假设一个繁荣的 Cosmos SDK 模块生态系统很容易组合成区块链应用程序，将包含有缺陷或恶意的模块。
目前没有一个蓬勃发展的 Cosmos SDK 模块生态系统。我们假设这部分是由于:
1. 缺乏稳定的 v1.0 Cosmos SDK 来构建模块。模块接口正在发生变化，有时是戏剧性的，从
点发布到点发布，通常有充分的理由，但这并不能建立稳定的基础。
2. 缺乏正确实现的对象能力甚至面向对象的封装系统，导致重构
模块保持器接口的数量不可避免，因为当前接口的约束很差。
### `x/bank` 案例研究
目前，`x/bank` keeper 几乎可以不受限制地访问任何引用它的模块。例如，
`SetBalance` 方法允许调用者将任何帐户的余额设置为任何内容，甚至绕过适当的供应跟踪。
后来似乎有一些尝试使用模块级铸造、抵押来实现一些 OCAP 的外观
和刻录权限。这些权限允许模块参考模块的
自己的账户。这些权限实际上存储在状态中的“ModuleAccount”类型上的“[]string”数组中。
但是，这些权限实际上并没有多大作用。它们控制可以在“MintCoins”中引用哪些模块，
`BurnCoins` 和 `DelegateCoins***` 方法，但其中一个没有唯一的对象能力令牌来控制访问——
只是一个简单的字符串。因此，`x/upgrade` 模块可以通过调用简单地为 `x/staking` 模块铸造令牌
`MintCoins(“staking”)`。此外，所有可以访问这些 keeper 方法的模块也可以访问
`SetBalance` 否定了 OCAP 的任何其他尝试，甚至破坏了基本的面向对象封装。
## 决定
基于[ADR-021](./adr-021-protobuf-query-encoding.md)和[ADR-031](./adr-031-msg-service.md)，我们引入了
用于安全模块授权和 OCAP 的模块间通信框架。
实施后，这也可以作为现有范式的替代方案，即在
模块。此处概述的方法旨在构成 Cosmos SDK v1.0 的基础，提供必要的
稳定性和封装保证，使蓬勃发展的模块生态系统得以出现。
特别值得注意的是 - 决定_启用_此功能，以便模块自行决定采用。
将现有模块迁移到这种新范式的建议必须是一个单独的对话，可能
作为对本 ADR 的修正处理。
### 新的“守护者”范式
在[ADR 021](./adr-021-protobuf-query-encoding.md)中，一种使用protobuf服务定义来定义查询器的机制
引入并在 [ADR 31](./adr-031-msg-service.md) 中，添加了使用 protobuf 服务定义 `Msg` 的机制。
Protobuf 服务定义生成两个 golang 接口，分别代表服务的客户端和服务器端加上
一些帮助代码。以下是银行 `cosmos.bank.Msg/Send` 消息类型的最小示例:
```go
package bank
type MsgClient interface {
Send(context.Context, *MsgSend, opts ...grpc.CallOption) (*MsgSendResponse, error)
}
type MsgServer interface {
Send(context.Context, *MsgSend) (*MsgSendResponse, error)
}
```
[ADR 021](./adr-021-protobuf-query-encoding.md) 和 [ADR 31](./adr-031-msg-service.md) 指定模块如何实现生成的`QueryServer`
和 `MsgServer` 接口分别作为旧查询器和 `Msg` 处理程序的替代品。
在这个 ADR 中，我们解释了模块如何使用生成的 `QueryClient` 进行查询和发送 `Msg` 到其他模块
和 `MsgClient` 接口，并提出这种机制来替代现有的 `Keeper` 范式。要清楚，
此 ADR 不需要创建新的 protobuf 定义或服务。相反，它利用相同的原型
基于客户端已经用于模块间通信的服务接口。
使用这种 `QueryClient`/`MsgClient` 方法比将 Keepers 暴露给外部模块有以下主要好处:
1. 使用 [buf](https://buf.build/docs/break-overview) 检查 Protobuf 类型的破坏性更改，因为
protobuf 的设计方式将为我们提供强大的向后兼容性保证，同时允许向前
进化。
2. 客户端和服务器接口之间的分离将允许我们在两者之间插入权限检查代码
这两个检查一个模块是否被授权将指定的 `Msg` 发送到另一个模块提供适当的
对象能力系统(见下文)。
3. 用于模块间通信的路由器为我们提供了一个方便的地方来处理事务的回滚，
启用操作原子性([目前有问题](https://github.com/cosmos/cosmos-sdk/issues/8030))。模块到模块调用中的任何故障都将导致整个模块的故障
交易
这种机制具有以下额外好处:
- 通过代码生成减少样板，以及
- 允许通过像 CosmWasm 这样的 VM 或使用 gRPC 的子进程使用其他语言的模块
### 模块间通信
要使用 protobuf 编译器生成的 `Client`，我们需要一个 `grpc.ClientConn` [接口](https://github.com/regen-network/protobuf/blob/cosmos/grpc/types.go#L12)
执行。为此我们介绍
一个新类型，`ModuleKey`，它实现了`grpc.ClientConn` 接口。 `ModuleKey` 可以被认为是“私有的
密钥”对应于模块帐户，其中通过使用特殊的`Invoker()` 函数提供身份验证，
下面更详细地描述。
区块链用户(外部客户)使用他们帐户的私钥来签署包含“消息”的交易，其中他们被列为签名者(每个
消息使用`Msg.GetSigner`指定所需的签名者)。身份验证检查由 `AnteHandler` 执行。
在这里，我们通过允许在 `Msg.GetSigners` 中识别模块来扩展这个过程。当一个模块想要触发另一个模块中的 `Msg` 执行时，
它的 `ModuleKey` 作为发送者(通过我们在下面描述的 `ClientConn` 接口)并被设置为唯一的“签名者”。值得注意的是
在这种情况下我们不使用任何加密签名。
例如，模块`A`可以使用它的`A.ModuleKey`为`/cosmos.bank.Msg/Send`交易创建`MsgSend`对象。 `MsgSend` 验证
将确保 `from` 帐户(在本例中为 `A.ModuleKey`)是签名者。
下面是一个假设模块 `foo` 与 `x/bank` 交互的示例:
```go
package foo
type FooMsgServer {
// ...
bankQuery bank.QueryClient
bankMsg bank.MsgClient
}
func NewFooMsgServer(moduleKey RootModuleKey, ...) FooMsgServer {
// ...
return FooMsgServer {
// ...
modouleKey: moduleKey,
bankQuery: bank.NewQueryClient(moduleKey),
bankMsg: bank.NewMsgClient(moduleKey),
}
}
func (foo *FooMsgServer) Bar(ctx context.Context, req *MsgBarRequest) (*MsgBarResponse, error) {
balance, err := foo.bankQuery.Balance(&bank.QueryBalanceRequest{Address: fooMsgServer.moduleKey.Address(), Denom: "foo"})
...
res, err := foo.bankMsg.Send(ctx, &bank.MsgSendRequest{FromAddress: fooMsgServer.moduleKey.Address(), ...})
...
}
```
此设计还旨在可扩展以涵盖更细粒度的许可的用例，例如通过以下方式进行铸造
denom 前缀仅限于某些模块(如在
[#7459](https://github.com/cosmos/cosmos-sdk/pull/7459#discussion_r529545528))。
### `ModuleKey`s 和 `ModuleID`s
`ModuleKey` 可以被认为是模块帐户的“私钥”，而 `ModuleID` 可以被认为是
对应的“公钥”。从 [ADR 028](./adr-028-public-key-addresses.md)，模块可以有一个根模块账户和任意数量的子账户
或可用于不同池(例如质押池)或管理帐户(例如组
帐户)。我们也可以认为模块子账户类似于派生密钥——有一个根密钥，然后是一些
派生路径。 `ModuleID` 是一个简单的结构体，它包含模块名称和可选的“派生”路径，
并根据 [ADR-028](https://github.com/cosmos/cosmos-sdk/blob/master/docs/architecture/adr-028-public-key-addresses) 中的`AddressHash` 方法形成其地址.md):
```go
type ModuleID struct {
ModuleName string
Path []byte
}
func (key ModuleID) Address() []byte {
return AddressHash(key.ModuleName, key.Path)
}
```
除了能够生成“ModuleID”和地址之外，“ModuleKey”还包含一个名为
`Invoker` 是安全模块间访问的关键。 `Invoker` 创建了一个 `InvokeFn` 闭包，在
`grpc.ClientConn` 接口和引擎盖下能够将消息路由到适当的 `Msg` 和 `Query` 处理程序
对“消息”执行适当的安全检查。 这允许比 keeper 的更安全的模块间访问
私有成员变量可以通过反射进行操作。 Golang 不支持对函数的反射
真正的恶意模块需要绕过捕获的变量和内存的直接操作
`ModuleKey` 安全性。
两个 `ModuleKey` 类型是 `RootModuleKey` 和 `DerivedModuleKey`:
```go
type Invoker func(callInfo CallInfo) func(ctx context.Context, request, response interface{}, opts ...interface{}) error
type CallInfo {
Method string
Caller ModuleID
}
type RootModuleKey struct {
moduleName string
invoker Invoker
}
func (rm RootModuleKey) Derive(path []byte) DerivedModuleKey { /* ... */}
type DerivedModuleKey struct {
moduleName string
path []byte
invoker Invoker
}
```
一个模块可以访问一个 `DerivedModuleKey`，使用 `RootModuleKey` 上的 `Derive(path []byte)` 方法，然后
将使用此密钥来验证来自子帐户的“消息”。 Ex:
```go
package foo
func (fooMsgServer *MsgServer) Bar(ctx context.Context, req *MsgBar) (*MsgBarResponse, error) {
derivedKey := fooMsgServer.moduleKey.Derive(req.SomePath)
bankMsgClient := bank.NewMsgClient(derivedKey)
res, err := bankMsgClient.Balance(ctx, &bank.MsgSend{FromAddress: derivedKey.Address(), ...})
...
}
```
通过这种方式，模块可以获得对 root 帐户和任意数量的子帐户的许可访问权并发送
来自这些帐户的经过身份验证的“消息”。 `Invoker` `callInfo.Caller` 参数在后台使用
区分不同的模块帐户，但无论哪种方式，`Invoker` 返回的函数都只允许`Msg`s
从根或派生模块帐户中通过。
请注意，`Invoker` 本身根据传入的 `CallInfo` 返回一个函数闭包。这将允许客户端实现
将来缓存每个方法类型的调用函数，避免哈希表查找的开销。
这会将这种模块间通信方法的性能开销减少到最低限度
检查权限。
重申一遍，闭包只允许访问授权调用。无论如何都无法访问其他任何东西
名字冒充。
下面是“RootModuleKey”的“grpc.ClientConn.Invoke”实现的粗略草图:
```go
func (key RootModuleKey) Invoke(ctx context.Context, method string, args, reply interface{}, opts ...grpc.CallOption) error {
f := key.invoker(CallInfo {Method: method, Caller: ModuleID {ModuleName: key.moduleName}})
return f(ctx, args, reply)
}
```
### `AppModule` 接线和要求
在 [ADR 031](./adr-031-msg-service.md) 中，引入了 `AppModule.RegisterService(Configurator)` 方法。 支持
模块间通信，我们扩展了 `Configurator` 接口以传入 `ModuleKey` 并允许模块
使用 `RequireServer()` 指定它们对其他模块的依赖:
```go
type Configurator interface {
MsgServer() grpc.Server
QueryServer() grpc.Server
ModuleKey() ModuleKey
RequireServer(msgServer interface{})
}
```
`ModuleKey` 被传递给 `RegisterService` 方法本身中的模块，以便 `RegisterServices` 作为单个
配置模块服务的入口点。 这也旨在具有大大减少样板文件的副作用
`app.go`。 目前，`ModuleKey`s 将基于 `AppModuleBasic.Name()` 创建，但更灵活的系统可能是
将来推出。 `ModuleManager` 将在后台处理模块帐户的创建。
由于模块不再能够直接相互访问，因此模块可能具有未满足的依赖关系。 确保;确定
如果模块依赖在启动时解决，则应添加 `Configurator.RequireServer` 方法。 `模块管理器`
将确保在应用程序启动之前可以解决所有使用 RequireServer 声明的依赖项。 一个例子
模块 `foo` 可以像这样声明它对 `x/bank` 的依赖:
```go
package foo
func (am AppModule) RegisterServices(cfg Configurator) {
cfg.RequireServer((*bank.QueryServer)(nil))
cfg.RequireServer((*bank.MsgServer)(nil))
}
```
### 安全注意事项
除了检查“ModuleKey”权限外，还需要采取一些额外的安全预防措施
底层路由器基础设施。
####递归和重入
递归或可重入方法调用构成潜在的安全威胁。如果模块 A，这可能是一个问题
在同一个调用中调用模块 B 和模块 B 再次调用模块 A。
路由器系统处理此问题的一种基本方法是维护一个调用堆栈，以防止模块
在调用堆栈中被多次引用，因此不会重新进入。一个 `map[string]interface{}` 表
在路由器中可用于执行此安全检查。
#### 查询
Cosmos SDK 中的查询通常是未经许可的，因此允许一个模块查询另一个模块不应构成
在采取基本预防措施的情况下，任何重大的安全威胁。路由器系统的基本注意事项
需要确保传递给查询方法的 `sdk.Context` 不允许写入存储。这
现在可以使用“CacheMultiStore”来完成，就像目前为“BaseApp”查询所做的那样。
### 内部方法
在许多情况下，我们可能希望模块调用其他模块上的方法，而这些模块根本没有暴露给客户端。为了这
为了达到目的，我们将 `InternalServer` 方法添加到 `Configurator` 中:
```go
type Configurator interface {
MsgServer() grpc.Server
QueryServer() grpc.Server
InternalServer() grpc.Server
}
```
比如x/staking的Slash必须调用x/staking的Slash，但是我们不想把x/staking的Slash暴露给终端用户
和客户。
内部 protobuf 服务将在给定模块的相应“internal.proto”文件中定义
原型包。
针对“InternalServer”注册的服务可以从其他模块调用，但不能被外部客户端调用。
内部方法的另一种解决方案可能涉及 [here](https://github.com/cosmos/cosmos-sdk/pull/7459#issuecomment-733807753) 中讨论的钩子/插件。
钩子/插件系统的更详细评估将在此 ADR 的后续跟进中或作为单独的
ADR。
### 授权
默认情况下，模块间路由器要求消息由 GetSigners 返回的第一个签名者发送。这
模块间路由器还应接受授权中间件，例如 [ADR 030](https://github.com/cosmos/cosmos-sdk/blob/master/docs/architecture/adr-030-authz-module.md )。
该中间件将允许帐户以其他方式代表特定模块帐户执行操作。
授权中间件应考虑有效授予某些模块“管理员”权限的需要
其他模块。这将在单独的 ADR 或此 ADR 的更新中解决。
### 未来的工作
未来的其他改进可能包括:
* 自定义代码生成:
* 简化接口(例如，使用 `sdk.Context` 而不是 `context.Context` 生成代码)
* 优化模块间调用 - 例如在第一次调用后缓存解析的方法
* 将`StoreKey`s 和`ModuleKey`s 组合到一个接口中，以便模块有一个单独的 OCAPs 句柄
* 代码生成，使模块间通信更高效
* 将 `ModuleKey` 创建与 `AppModuleBasic.Name()` 解耦，以便应用程序可以覆盖根模块帐户名称
* 模块间挂钩和插件
## 备择方案
### MsgServices 与`x/capability`
`x/capability` 模块确实提供了一个合适的对象能力实现，可以被
Cosmos SDK，甚至可以用于模块间 OCAP，如 [\#5931](https://github.com/cosmos/cosmos-sdk/issues/5931) 中所述。
本 ADR 中描述的方法的优势主要在于它如何与 Cosmos SDK 的其他部分集成，
具体来说:
* protobuf 以便:
* 可以利用接口的代码生成来获得更好的开发用户体验
* 使用 [buf](https://docs.buf.build/break-overview) 对模块接口进行版本控制和检查是否损坏
* 根据 ADR 028 的子模块帐户
* 一般的 `Msg` 传递范式和签名者的方式由 `GetSigners` 指定
此外，这是对 Keepers 的完全替代，可以应用于 _all_ 模块间通信，而
#5931 中的`x/capability` 方法需要逐个应用。
## Consequences
### Backwards Compatibility
此 ADR 旨在为模块之间具有更大长期兼容性的场景提供途径。
在短期内，这可能会导致某些过于宽松和/或
完全替换 `Keeper` 接口。
### Positive
- 可以更轻松地实现稳定的模块间接口的 Keepers 的替代方案
- 适当的模块间 OCAP
- 改进的模块开发者 DevX，正如一些参与者所评论的
[架构审查电话会议，12 月 3 日](https://hackmd.io/E0wxxOvRQ5qVmTf6N_k84Q)
- 为可以大大简化的“app.go”奠定基础
- 可以设置路由器来强制执行模块到模块调用的原子事务
### Negative
- 采用这种方式的模块将需要大量重构
### Neutral
## Test Cases [optional]
## References
- [ADR 021](./adr-021-protobuf-query-encoding.md)
- [ADR 031](./adr-031-msg-service.md)
- [ADR 028](./adr-028-public-key-addresses.md)
- [ADR 030 draft](https://github.com/cosmos/cosmos-sdk/pull/7105)
- [Object-Capability Model](../docs/core/ocap.md)
| 25.4675 | 140 | 0.761853 | yue_Hant | 0.869943 |
581e2774b14dad71c377eafe279ae717ad251fad | 1,874 | md | Markdown | docs/1.15/core-v1-containerPort.md | justinwalz/k8s-alpha | 3b3cc2f1120daaf5dd74c147c0adec79720726f9 | [
"Apache-2.0"
] | 70 | 2020-05-13T10:44:17.000Z | 2021-11-15T10:42:11.000Z | docs/1.15/core-v1-containerPort.md | justinwalz/k8s-alpha | 3b3cc2f1120daaf5dd74c147c0adec79720726f9 | [
"Apache-2.0"
] | 2 | 2020-11-19T16:36:56.000Z | 2021-07-02T11:55:44.000Z | docs/1.15/core-v1-containerPort.md | justinwalz/k8s-alpha | 3b3cc2f1120daaf5dd74c147c0adec79720726f9 | [
"Apache-2.0"
] | 10 | 2020-06-23T09:05:57.000Z | 2021-06-02T00:02:55.000Z | ---
permalink: /1.15/core/v1/containerPort/
---
# package containerPort
ContainerPort represents a network port in a single container.
## Index
* [`fn new(containerPort)`](#fn-new)
* [`fn newNamed(containerPort, name)`](#fn-newnamed)
* [`fn newNamedUDP(containerPort, name)`](#fn-newnamedudp)
* [`fn newUDP(containerPort)`](#fn-newudp)
* [`fn withContainerPort(containerPort)`](#fn-withcontainerport)
* [`fn withHostIP(hostIP)`](#fn-withhostip)
* [`fn withHostPort(hostPort)`](#fn-withhostport)
* [`fn withName(name)`](#fn-withname)
* [`fn withProtocol(protocol)`](#fn-withprotocol)
## Fields
### fn new
```ts
new(containerPort)
```
new returns a new `containerPort`
### fn newNamed
```ts
newNamed(containerPort, name)
```
newNamed works like `new`, but also sets the `name`
### fn newNamedUDP
```ts
newNamedUDP(containerPort, name)
```
newNamedUDP works like `newNamed`, but also sets protocal to UDP
### fn newUDP
```ts
newUDP(containerPort)
```
newUDP works like `new`, but also sets protocal to UDP
### fn withContainerPort
```ts
withContainerPort(containerPort)
```
Number of port to expose on the pod's IP address. This must be a valid port number, 0 < x < 65536.
### fn withHostIP
```ts
withHostIP(hostIP)
```
What host IP to bind the external port to.
### fn withHostPort
```ts
withHostPort(hostPort)
```
Number of port to expose on the host. If specified, this must be a valid port number, 0 < x < 65536. If HostNetwork is specified, this must match ContainerPort. Most containers do not need this.
### fn withName
```ts
withName(name)
```
If specified, this must be an IANA_SVC_NAME and unique within the pod. Each named port in a pod must have a unique name. Name for the port that can be referred to by services.
### fn withProtocol
```ts
withProtocol(protocol)
```
Protocol for port. Must be UDP, TCP, or SCTP. Defaults to "TCP". | 20.150538 | 194 | 0.709712 | eng_Latn | 0.957745 |
581f1154ca5f8657dd4e3c0bef60bfd8cc0f93c5 | 2,322 | md | Markdown | README.md | UBC-MDS/miniTidyR | e5695d32cc81031a236cf3803096a1fdcf0dcad7 | [
"MIT"
] | null | null | null | README.md | UBC-MDS/miniTidyR | e5695d32cc81031a236cf3803096a1fdcf0dcad7 | [
"MIT"
] | 9 | 2019-02-06T19:40:32.000Z | 2019-03-05T23:49:51.000Z | README.md | UBC-MDS/miniTidyR | e5695d32cc81031a236cf3803096a1fdcf0dcad7 | [
"MIT"
] | 3 | 2019-02-05T23:58:29.000Z | 2019-02-06T00:13:09.000Z | # R Mini Tidy Package : `miniTidyR`
[](https://travis-ci.org/UBC-MDS/miniTidyR)
### Contributors:
- Huijue Chen (`huijuechen`)
- Luo Yang (`lyiris22`)
- Orphelia Ellogne (`ellognea`)
### Summary
We re-implemented R’s <a href="https://tidyr.tidyverse.org/reference/gather.html"> gather </a>,<a href="https://tidyr.tidyverse.org/reference/spread.html"> spread </a>, and <a href="https://tidyr.tidyverse.org/reference/drop_na.html"> drop_na </a> functions that exist in the `tidyverse` package.
Our functions are called `my_gather` , `my_spread` and `my_dropna`:
- `my_gather()` : Transform a data from wide to long by combining columns. For selected columns, put the columns names into a column of keys, and the values into a column of values.
- `my_spread()` : Transform a data from long to wide. Select a ‘key’ column whose content will be the names of the new columns. Select a ‘value’ column whose content will be the values of the new columns.
- `my_dropna()` : Remove rows that contain `NA` values from a data frame.
### Installation
To install and load `miniTidyR` run :
- `devtools::install_github("https://github.com/UBC-MDS/miniTidyR")`
- `library(miniTidyR)`
To access the vignette run:
- `devtools::install(build_vignettes=TRUE)`
- `browseVignettes("miniTidyR")`
### Function usage examples
#### `my_dropna`
```
df1 <- data.frame(A = c(12,25,NA,45), B = c(12,NA,30,45))
my_dropna(df1)
```
###### df1
###### my_dropna(df1)
#### `my_gather`
```
df2 <- data.frame(Groups = c("A","B"), Married = c(12,25), Other = c(100,55))
my_gather(df2, "Status", "Count", list("Married","Other"))
```
###### df2
###### my_gather(df2, "Status", "Count", list("Married","Other"))
#### `my_spread`
```
df3 <- data.frame(Name = c("A","A","B","B"), key = c("Age","Weight","Age","Weight"), value = c(45,80,30,70))
my_spread(df3,"key","value")
```
###### df3
###### my_spread(df3,"key","value")
### Branch coverage
### Check output
### Test output
**Please note that these 6 warnings are part of the code**
| 26.089888 | 296 | 0.667097 | eng_Latn | 0.575556 |
58209aea0e14c704e277cab8aaf9faf87dbe7131 | 19,810 | md | Markdown | articles/service-health/resource-health-alert-arm-template-guide.md | matmahnke/azure-docs.pt-br | 6c96d25caf8663547775f333164198e3ed03972f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/service-health/resource-health-alert-arm-template-guide.md | matmahnke/azure-docs.pt-br | 6c96d25caf8663547775f333164198e3ed03972f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/service-health/resource-health-alert-arm-template-guide.md | matmahnke/azure-docs.pt-br | 6c96d25caf8663547775f333164198e3ed03972f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Modelo para criar alertas de Resource Health
description: Crie alertas por meio de programação que notificam você quando seus recursos do Azure se tornam não disponíveis.
ms.topic: conceptual
ms.date: 9/4/2018
ms.openlocfilehash: 3859bb0ce2497b1c1f547c3750e53745ef6d6f28
ms.sourcegitcommit: 829d951d5c90442a38012daaf77e86046018e5b9
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 10/09/2020
ms.locfileid: "91537422"
---
# <a name="configure-resource-health-alerts-using-resource-manager-templates"></a>Configurar alertas de integridade de recursos do Azure usando modelos do Resource Manager
Este artigo mostrará como criar, programaticamente, Alertas de Log de Atividades do Resource Health usando modelos do Azure Resource Manager e o Azure PowerShell.
O Azure Resource Health mantém você informado sobre o status de integridade atual e histórico de seus recursos do Azure. Os alertas do Azure Resource Health podem notificar você quase em tempo real quando esses recursos tiverem uma alteração no seu status de integridade. Criar alertas do Resource Health por meio de programação permite que usuários criem e personalizem alertas em massa.
[!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
## <a name="prerequisites"></a>Pré-requisitos
Para seguir as instruções nesta página, você precisará configurar algumas coisas antecipadamente:
1. Você precisa instalar o [módulo Azure PowerShell](/powershell/azure/install-az-ps)
2. Você precisará [criar ou reutilizar um Grupo de Ações](../azure-monitor/platform/action-groups.md) configurado para notificar você
## <a name="instructions"></a>Instruções
1. Usando o PowerShell, faça logon no Azure usando sua conta e selecione a assinatura com a qual você deseja interagir
```azurepowershell
Login-AzAccount
Select-AzSubscription -Subscription <subscriptionId>
```
> Você pode usar `Get-AzSubscription` para listar as assinaturas as quais você tem acesso.
2. Localize e salve a ID completa do Azure Resource Manager para seu Grupo de Ações
```azurepowershell
(Get-AzActionGroup -ResourceGroupName <resourceGroup> -Name <actionGroup>).Id
```
3. Crie e salve um modelo do Resource Manager para alertas do Resource Health conforme `resourcehealthalert.json` ([veja os detalhes abaixo](#resource-manager-template-options-for-resource-health-alerts))
4. Crie uma nova implantação do Azure Resource Manager usando este modelo
```azurepowershell
New-AzResourceGroupDeployment -Name ExampleDeployment -ResourceGroupName <resourceGroup> -TemplateFile <path\to\resourcehealthalert.json>
```
5. Você será solicitado a digitar o nome do alerta e ID de recurso do Grupo de Ações que você copiou anteriormente:
```azurepowershell
Supply values for the following parameters:
(Type !? for Help.)
activityLogAlertName: <Alert Name>
actionGroupResourceId: /subscriptions/<subscriptionId>/resourceGroups/<resourceGroup>/providers/microsoft.insights/actionGroups/<actionGroup>
```
6. Se tudo funcionar com êxito, você receberá uma confirmação no PowerShell
```output
DeploymentName : ExampleDeployment
ResourceGroupName : <resourceGroup>
ProvisioningState : Succeeded
Timestamp : 11/8/2017 2:32:00 AM
Mode : Incremental
TemplateLink :
Parameters :
Name Type Value
=============== ========= ==========
activityLogAlertName String <Alert Name>
activityLogAlertEnabled Bool True
actionGroupResourceId String /...
Outputs :
DeploymentDebugLogLevel :
```
Observe que, se estiver planejando automatizar totalmente esse processo, você simplesmente precisará editar o modelo do Resource Manager para não solicitar os valores na etapa 5.
## <a name="resource-manager-template-options-for-resource-health-alerts"></a>Opções de modelo do Resource Manager para alertas de Resource Health
Você pode usar esse modelo de base como ponto de partida para a criação de alertas do Resource Health. Esse modelo funcionará como escrito e se você se inscreverá para receber alertas para todos os eventos de integridade de recursos recentemente ativados em todos os recursos em uma assinatura.
> Na parte inferior deste artigo também incluímos um modelo de alerta mais complexo que deve aumentar o sinal para a taxa de ruído para alertas do Resource Health em comparação com este modelo.
```json
{
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
"contentVersion": "1.0.0.0",
"parameters": {
"activityLogAlertName": {
"type": "string",
"metadata": {
"description": "Unique name (within the Resource Group) for the Activity log alert."
}
},
"actionGroupResourceId": {
"type": "string",
"metadata": {
"description": "Resource Id for the Action group."
}
}
},
"resources": [
{
"type": "Microsoft.Insights/activityLogAlerts",
"apiVersion": "2017-04-01",
"name": "[parameters('activityLogAlertName')]",
"location": "Global",
"properties": {
"enabled": true,
"scopes": [
"[subscription().id]"
],
"condition": {
"allOf": [
{
"field": "category",
"equals": "ResourceHealth"
},
{
"field": "status",
"equals": "Active"
}
]
},
"actions": {
"actionGroups":
[
{
"actionGroupId": "[parameters('actionGroupResourceId')]"
}
]
}
}
}
]
}
```
No entanto, um alerta amplo como este geralmente não é recomendável. Saiba como é possível definir o escopo para baixo desse alerta para se concentrar nos eventos que nos interessa abaixo.
### <a name="adjusting-the-alert-scope"></a>Ajustando o escopo de alerta
Os alertas do Resource Health podem ser configurados para monitorar eventos em três escopos diferentes:
* Nível de Assinatura
* Nível do Grupo de Recursos
* Nível de Recurso
O modelo de alerta é configurado no nível da assinatura, mas se você quiser configurar o alerta para notificá-lo apenas sobre determinados recursos ou recursos dentro de um determinado grupo de recursos, você simplesmente precisará modificar a seção `scopes` no modelo acima.
Para um escopo de nível de grupo de recursos, a seção de escopos deve se parecer com:
```json
"scopes": [
"/subscriptions/<subscription id>/resourcegroups/<resource group>"
],
```
E, para um escopo de nível de recursos, a seção de escopos deve se parecer com:
```json
"scopes": [
"/subscriptions/<subscription id>/resourcegroups/<resource group>/providers/<resource>"
],
```
Por exemplo: `"/subscriptions/d37urb3e-ed41-4670-9c19-02a1d2808ff9/resourcegroups/myRG/providers/microsoft.compute/virtualmachines/myVm"`
> Você pode acessar o portal do Azure e examinar a URL ao exibir o recurso do Azure para obter essa cadeia de caracteres.
### <a name="adjusting-the-resource-types-which-alert-you"></a>Ajustar os tipos de recursos que alertam você
Os alertas no nível de grupo de recursos ou assinatura podem ter diferentes tipos de recursos. Se quiser limitar os alertas para serem provenientes apenas de um certo subconjunto de tipos de recursos, você poderá definir isso na seção `condition` do modelo da seguinte forma:
```json
"condition": {
"allOf": [
...,
{
"anyOf": [
{
"field": "resourceType",
"equals": "MICROSOFT.COMPUTE/VIRTUALMACHINES",
"containsAny": null
},
{
"field": "resourceType",
"equals": "MICROSOFT.STORAGE/STORAGEACCOUNTS",
"containsAny": null
},
...
]
}
]
},
```
Aqui, usamos o wrapper `anyOf` para permitir que o alerta de integridade de recurso corresponda a qualquer uma das condições que especificamos, permitindo os alertas que se destinam a tipos específicos de recursos.
### <a name="adjusting-the-resource-health-events-that-alert-you"></a>Ajustar os eventos do Resource Health que alertam você
Quando recursos passam por um evento de integridade, eles podem passar por uma série de estágios que representa o estado do evento de integridade: `Active`, `In Progress`, `Updated` e `Resolved`.
Você pode deseja ser notificado apenas quando um recurso se tornar não íntegro, caso em que você deseja configurar o alerta para notificar somente quando `status` for `Active`. No entanto se quiser também ser notificado sobre os outros estágios, você poderá adicionar esses detalhes da seguinte forma:
```json
"condition": {
"allOf": [
...,
{
"anyOf": [
{
"field": "status",
"equals": "Active"
},
{
"field": "status",
"equals": "In Progress"
},
{
"field": "status",
"equals": "Resolved"
},
{
"field": "status",
"equals": "Updated"
}
]
}
]
}
```
Se quiser ser notificado para todos os quatro estágios de eventos de integridade, você poderá remover essa condição conjuntamente e o alerta notificará você independentemente da propriedade `status`.
> [!NOTE]
> Cada seção "anyOf" deve conter apenas um valor de tipo de campo.
### <a name="adjusting-the-resource-health-alerts-to-avoid-unknown-events"></a>Ajustar os alertas do Resource Health para evitar eventos "desconhecidos"
O Azure Resource Health pode relatar a você a integridade mais recente de seus recursos monitorando-os constantemente usando executores de teste. Os status de integridade reportados relevantes são: "Disponível", "Não disponível" e "Degradado". No entanto, em situações em que o executor e o recurso do Azure não conseguem se comunicar, um status de integridade "Desconhecido" é relatado para o recurso e é considerado um evento de integridade "Ativo".
No entanto, quando um recurso relata "Desconhecido", é provável que o status de integridade não tenha sido alterado desde o último relatório preciso. Se quiser eliminar alertas em eventos "Desconhecidos", você poderá especificar essa lógica no modelo:
```json
"condition": {
"allOf": [
...,
{
"anyOf": [
{
"field": "properties.currentHealthStatus",
"equals": "Available",
"containsAny": null
},
{
"field": "properties.currentHealthStatus",
"equals": "Unavailable",
"containsAny": null
},
{
"field": "properties.currentHealthStatus",
"equals": "Degraded",
"containsAny": null
}
]
},
{
"anyOf": [
{
"field": "properties.previousHealthStatus",
"equals": "Available",
"containsAny": null
},
{
"field": "properties.previousHealthStatus",
"equals": "Unavailable",
"containsAny": null
},
{
"field": "properties.previousHealthStatus",
"equals": "Degraded",
"containsAny": null
}
]
},
]
},
```
Neste exemplo, estamos apenas notificando os eventos em que o status de integridade atual e anterior não tem "Desconhecido". Essa alteração poderá ser uma adição útil se os alertas forem enviados diretamente ao seu celular ou email.
Observe que é possível que as propriedades currentHealthStatus e previousHealthStatus sejam nulas em alguns eventos. Por exemplo, quando um evento atualizado ocorre, é provável que o status de integridade do recurso não tenha sido alterado desde o último relatório, apenas que informações adicionais do evento estejam disponíveis (por exemplo, causa). Portanto, usar a cláusula acima pode resultar em alguns alertas não sendo disparados, pois os valores de Properties. currentHealthStatus e Properties. previousHealthStatus serão definidos como NULL.
### <a name="adjusting-the-alert-to-avoid-user-initiated-events"></a>Ajustar o alerta para evitar eventos iniciados pelo usuário
Resource Health eventos podem ser disparados por eventos iniciados pela plataforma e pelo usuário. Pode fazer sentido enviar apenas uma notificação quando o evento de integridade for causado pela plataforma do Azure.
É fácil configurar o alerta para filtrar apenas esses tipos de eventos:
```json
"condition": {
"allOf": [
...,
{
"field": "properties.cause",
"equals": "PlatformInitiated",
"containsAny": null
}
]
}
```
Observe que é possível que o campo de causa seja nulo em alguns eventos. Ou seja, ocorre uma transição de integridade (por exemplo, disponível para indisponível) e o evento é registrado imediatamente para evitar atrasos de notificação. Portanto, o uso da cláusula acima pode resultar em um alerta não ser disparado, pois o valor da Propriedade Properties. cláusula será definido como NULL.
## <a name="complete-resource-health-alert-template"></a>Concluir Resource Health modelo de alerta
Usando os diferentes ajustes descritos na seção anterior, aqui está um modelo de exemplo que é configurado para maximizar o sinal para a taxa de ruído. Tenha em mente as advertências indicadas acima em que os valores de propriedade currentHealthStatus, previousHealthStatus e causa podem ser nulos em alguns eventos.
```json
{
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
"contentVersion": "1.0.0.0",
"parameters": {
"activityLogAlertName": {
"type": "string",
"metadata": {
"description": "Unique name (within the Resource Group) for the Activity log alert."
}
},
"actionGroupResourceId": {
"type": "string",
"metadata": {
"description": "Resource Id for the Action group."
}
}
},
"resources": [
{
"type": "Microsoft.Insights/activityLogAlerts",
"apiVersion": "2017-04-01",
"name": "[parameters('activityLogAlertName')]",
"location": "Global",
"properties": {
"enabled": true,
"scopes": [
"[subscription().id]"
],
"condition": {
"allOf": [
{
"field": "category",
"equals": "ResourceHealth",
"containsAny": null
},
{
"anyOf": [
{
"field": "properties.currentHealthStatus",
"equals": "Available",
"containsAny": null
},
{
"field": "properties.currentHealthStatus",
"equals": "Unavailable",
"containsAny": null
},
{
"field": "properties.currentHealthStatus",
"equals": "Degraded",
"containsAny": null
}
]
},
{
"anyOf": [
{
"field": "properties.previousHealthStatus",
"equals": "Available",
"containsAny": null
},
{
"field": "properties.previousHealthStatus",
"equals": "Unavailable",
"containsAny": null
},
{
"field": "properties.previousHealthStatus",
"equals": "Degraded",
"containsAny": null
}
]
},
{
"anyOf": [
{
"field": "properties.cause",
"equals": "PlatformInitiated",
"containsAny": null
}
]
},
{
"anyOf": [
{
"field": "status",
"equals": "Active",
"containsAny": null
},
{
"field": "status",
"equals": "Resolved",
"containsAny": null
},
{
"field": "status",
"equals": "In Progress",
"containsAny": null
},
{
"field": "status",
"equals": "Updated",
"containsAny": null
}
]
}
]
},
"actions": {
"actionGroups": [
{
"actionGroupId": "[parameters('actionGroupResourceId')]"
}
]
}
}
}
]
}
```
No entanto, você saberá melhor quais configurações são eficazes para você, então use as ferramentas mostradas a você nesta documentação para fazer sua própria personalização.
## <a name="next-steps"></a>Próximas etapas
Saiba mais sobre o Resource Health:
- [Visão geral de Azure Resource Health](Resource-health-overview.md)
- [Tipos de recursos e verificações de integridade disponíveis por meio de Azure Resource Health](resource-health-checks-resource-types.md)
Criar alertas de Integridade do Serviço:
- [Configurar alertas para a Integridade do Serviço](./alerts-activity-log-service-notifications-portal.md)
- [Esquema de eventos do log de atividades do Azure](../azure-monitor/platform/activity-log-schema.md)
| 43.442982 | 550 | 0.561888 | por_Latn | 0.989058 |
582104e65c65f5f8cc2da849879814cd2d32a67a | 1,450 | md | Markdown | README.md | fanhaoyuan/css-preprocessor-variables | 61915971fe6c374219ec749d06055f996c43812c | [
"MIT"
] | 1 | 2021-09-01T06:45:14.000Z | 2021-09-01T06:45:14.000Z | README.md | fanhaoyuan/sass-json-vars | 61915971fe6c374219ec749d06055f996c43812c | [
"MIT"
] | null | null | null | README.md | fanhaoyuan/sass-json-vars | 61915971fe6c374219ec749d06055f996c43812c | [
"MIT"
] | null | null | null | # css-preprocessor-variables
A plugin for convert css preprocessor`s variables to json.
## install
```bash
>$ npm install css-preprocessor-variables
#or
>$ yarn add css-preprocessor-variables
```
## usage
```ts
const getVars: (content: string, options: UserOptions) => Promise<Output>;
```
### example
```ts
const getVars = require('css-preprocessor-variables');
getVars('@primary-color: #ffffff;\n @color: #000000', { type: 'less' }).then(({ variable }) => {
console.log(variables); // { '@primary-color': '#ffffff', 'color': '#000000' }
});
```
or use it with promise
```ts
(async function () {
const getVars = require('css-preprocessor-variables');
const { variables } = await getVars('@primary-color: #ffffff;\n @color: #000000', { type: 'less' });
console.log(variables); // { '@primary-color': '#ffffff', 'color': '#000000' }
})();
```
[More examples in here](./__tests__)
## options
```ts
export interface Options {
/**
* Type of parser
*/
type: 'less' | 'scss';
/**
* Format key of variables
*
* @default 'default'
*/
format: 'camelCase' | 'kebabCase' | 'default';
/**
* Whether to remove the prefix
*
* @default false
*
* If true, strip prefix '@' or '$'
*/
strip: boolean;
/**
* transform variables in current result
*
* @default true
*/
transform: boolean;
}
```
## license
[MIT](./LICENSE)
| 18.125 | 104 | 0.585517 | eng_Latn | 0.457893 |
58217f8675242ea451b177a1964aeb71c1e38ae8 | 2,028 | md | Markdown | packages/cache/RELEASES.md | whywaita/toolkit | d6539cc63b8210720330c99a39c8974d4e734d3f | [
"MIT"
] | null | null | null | packages/cache/RELEASES.md | whywaita/toolkit | d6539cc63b8210720330c99a39c8974d4e734d3f | [
"MIT"
] | null | null | null | packages/cache/RELEASES.md | whywaita/toolkit | d6539cc63b8210720330c99a39c8974d4e734d3f | [
"MIT"
] | null | null | null | # @actions/cache Releases
### 0.1.0
- Initial release
### 0.2.0
- Fixes issues with the zstd compression algorithm on Windows and Ubuntu 16.04 [#469](https://github.com/actions/toolkit/pull/469)
### 0.2.1
- Fix to await async function getCompressionMethod
### 1.0.0
- Downloads Azure-hosted caches using the Azure SDK for speed and reliability
- Displays download progress
- Includes changes that break compatibility with earlier versions, including:
- `retry`, `retryTypedResponse`, and `retryHttpClientResponse` moved from `cacheHttpClient` to `requestUtils`
### 1.0.1
- Fix bug in downloading large files (> 2 GBs) with the Azure SDK
### 1.0.2
- Use posix archive format to add support for some tools
### 1.0.3
- Use http-client v1.0.9
- Fixes error handling so retries are not attempted on non-retryable errors (409 Conflict, for example)
- Adds 5 second delay between retry attempts
### 1.0.4
- Use @actions/core v1.2.6
- Fixes uploadChunk to throw an error if any unsuccessful response code is received
### 1.0.5
- Fix to ensure Windows cache paths get resolved correctly
### 1.0.6
- Make caching more verbose [#650](https://github.com/actions/toolkit/pull/650)
- Use GNU tar on macOS if available [#701](https://github.com/actions/toolkit/pull/701)
### 1.0.7
- Fixes permissions issue extracting archives with GNU tar on macOS ([issue](https://github.com/actions/cache/issues/527))
### 1.0.8
- Increase the allowed artifact cache size from 5GB to 10GB ([issue](https://github.com/actions/cache/discussions/497))
### 1.0.9
- Use @azure/ms-rest-js v2.6.0
- Use @azure/storage-blob v12.8.0
### 1.0.10
- Update `lockfileVersion` to `v2` in `package-lock.json [#1022](https://github.com/actions/toolkit/pull/1022)
### 1.0.11
- Fix file downloads > 2GB([issue](https://github.com/actions/cache/issues/773))
### 2.0.0
- Added support to check if Actions cache service feature is available or not [#1028](https://github.com/actions/toolkit/pull/1028)
### 2.0.3
- Update to v2.0.0 of `@actions/http-client` | 33.245902 | 131 | 0.724359 | eng_Latn | 0.785115 |
5821c3d0c1ea49e930263f679f4dd9bd25113a77 | 32 | md | Markdown | README.md | diewland/go.diew.app | d00631cf79f274c3519fca434f0245bdcd22fb76 | [
"MIT"
] | null | null | null | README.md | diewland/go.diew.app | d00631cf79f274c3519fca434f0245bdcd22fb76 | [
"MIT"
] | null | null | null | README.md | diewland/go.diew.app | d00631cf79f274c3519fca434f0245bdcd22fb76 | [
"MIT"
] | null | null | null | # go.diew.app
Short URL Service
| 10.666667 | 17 | 0.75 | ltz_Latn | 0.293851 |
58224bd19dcfb6b45bc4c06a0b75eb156463c20f | 430 | md | Markdown | CHANGELOG.md | grimmer0125/vscode-back-forward-button | 45cd82f19fbf82147dba15ef87f089fdadef44f6 | [
"MIT"
] | 9 | 2019-02-28T20:56:52.000Z | 2021-12-31T03:00:41.000Z | CHANGELOG.md | grimmer0125/vscode-back-forward-button | 45cd82f19fbf82147dba15ef87f089fdadef44f6 | [
"MIT"
] | 7 | 2020-01-06T17:28:38.000Z | 2021-10-04T16:51:24.000Z | CHANGELOG.md | grimmer0125/vscode-back-forward-button | 45cd82f19fbf82147dba15ef87f089fdadef44f6 | [
"MIT"
] | 5 | 2019-02-15T07:45:18.000Z | 2021-12-31T03:00:43.000Z | # Change Log
All notable changes to the "vscode-back-forward-button" extension will be documented in this file.
## 0.1.6
- Upload a screenshot to README
## 0.1.5
- Use high resolution icon
## 0.1.4
- Change icon
- Add description
## 0.1.3
- Improve README (thanks, @rijobro)
- Add settings to configure text for arrows (thanks, @datho7561)
## 0.1.2
- Improve README
## 0.1.1
- Add icon
## 0.1.0
- Initial release
| 12.647059 | 98 | 0.674419 | eng_Latn | 0.821816 |
5822a19853bb58726ebbe722e508432fbd7fd022 | 979 | md | Markdown | README.md | senfung/pre-commit-golang | fef109862aa69d9aba7ac5bddb19adcab1c95e15 | [
"MIT"
] | null | null | null | README.md | senfung/pre-commit-golang | fef109862aa69d9aba7ac5bddb19adcab1c95e15 | [
"MIT"
] | null | null | null | README.md | senfung/pre-commit-golang | fef109862aa69d9aba7ac5bddb19adcab1c95e15 | [
"MIT"
] | null | null | null | # pre-commit-golang
Golang pre-commit hooks for http://pre-commit.com/
## install
you need first to install (pre-commit) [https://pre-commit.com/#install]
```
brew install pre-commit
```
install pre-commit into your git repo
```
pre-commit install
```
## Usage
Add a file named `.pre-commit-config.yaml` into the root directory of your repository
```yaml
repos:
- repo: git://github.com/senfung/pre-commit-golang
rev: master
hooks:
- id: go-fmt-import
- id: go-vet
- id: go-lint
- id: go-unit-tests
- id: gofumpt # requires github.com/mvdan/gofumpt
- id: go-err-check # requires github.com/kisielk/errcheck
- id: go-static-check # install https://staticcheck.io/docs/
- id: golangci-lint # requires github.com/golangci/golangci-lint
```
## Credits
This repo is inspired by [Bahjat/pre-commit-golang](https://github.com/Bahjat/pre-commit-golang). Fixed the issue of golint always passing (as golint always exit with 0).
| 30.59375 | 170 | 0.688458 | eng_Latn | 0.588173 |
58230688d281f750a311e1c05c73e66fc2c6c9c9 | 4,686 | md | Markdown | docs/vs-2015/msbuild/xdcmake-task.md | klmnden/visualstudio-docs.tr-tr | 82aa1370dab4ae413f5f924dad3e392ecbad0d02 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-09-01T20:45:52.000Z | 2020-09-01T20:45:52.000Z | docs/vs-2015/msbuild/xdcmake-task.md | klmnden/visualstudio-docs.tr-tr | 82aa1370dab4ae413f5f924dad3e392ecbad0d02 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vs-2015/msbuild/xdcmake-task.md | klmnden/visualstudio-docs.tr-tr | 82aa1370dab4ae413f5f924dad3e392ecbad0d02 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: XDCMake görevi | Microsoft Docs
ms.date: 11/15/2016
ms.prod: visual-studio-dev14
ms.technology: msbuild
ms.topic: reference
f1_keywords:
- vc.task.xdcmake
dev_langs:
- VB
- CSharp
- C++
- jsharp
- C++
helpviewer_keywords:
- XDCMake task (MSBuild (Visual C++))
- MSBuild (Visual C++), XDCMake task
ms.assetid: a7de9c64-903a-4a02-85f3-f37672270f25
caps.latest.revision: 10
author: mikejo5000
ms.author: mikejo
manager: jillfra
ms.openlocfilehash: c16c92b41aa0635ecb24d83e30e2c347620b2c75
ms.sourcegitcommit: 08fc78516f1107b83f46e2401888df4868bb1e40
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 05/15/2019
ms.locfileid: "65675532"
---
# <a name="xdcmake-task"></a>XDCMake Görevi
[!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
XML belge açıklaması (.xdc) dosyaları bir .xml dosyasına birleştirir XML belgelendirme Aracı (xdcmake.exe'yi) sarmalar.
.Xdc dosyasını kullanarak Visual C++ kaynak kod ve derleme belge açıklamaları sağlama oluşturulduğunda [/doc](https://msdn.microsoft.com/library/b54f7e2c-f28f-4f46-9ed6-0db09be2cc63) derleyici seçeneği. Daha fazla bilgi için [XDCMake başvurusu](https://msdn.microsoft.com/library/14e65747-d000-4343-854b-8393bf01cbac), [XML belgesi oluşturma aracı özellik sayfaları](https://msdn.microsoft.com/library/645912b5-197a-4c36-ba58-64df09444ca0)ve komut satırı Yardımı seçeneği (**/?**) xdcmake.exe'yi için.
## <a name="remarks"></a>Açıklamalar
Varsayılan olarak, aracı xdcmake.exe'yi birkaç komut satırı seçeneklerini destekler. Ek seçenekler, belirttiğiniz zaman desteklenir **/eski** komut satırı seçeneği.
## <a name="parameters"></a>Parametreler
Parametreleri aşağıdaki tabloda açıklanmıştır **XDCMake** görev.
|Parametre|Açıklama|
|---------------|-----------------|
|**AdditionalDocumentFile**|İsteğe bağlı **String []** parametresi.<br /><br /> Birleştirmek için bir veya daha fazla ek .xdc dosyalarının belirtir.<br /><br /> Daha fazla bilgi için **ek belge dosyaları** açıklamasında [XML belgesi oluşturma aracı özellik sayfaları](https://msdn.microsoft.com/library/645912b5-197a-4c36-ba58-64df09444ca0). Ayrıca bkz: **/eski** ve **/Fs** xdcmake.exe'yi için komut satırı seçenekleri.|
|**AdditionalOptions**|İsteğe bağlı **dize** parametresi.<br /><br /> Komut satırında belirtilen seçeneklerin bir listesi. Örneğin, "*/option1 /option2 /option#*". Diğer tarafından temsil edilmez seçeneklerini belirtmek için bu parametreyi kullanın **XDCMake** görev parametresi.<br /><br /> Daha fazla bilgi için [XDCMake başvurusu](https://msdn.microsoft.com/library/14e65747-d000-4343-854b-8393bf01cbac), [XML belgesi oluşturma aracı özellik sayfaları](https://msdn.microsoft.com/library/645912b5-197a-4c36-ba58-64df09444ca0)ve komut satırı Yardımı (**/?**) xdcmake.exe'yi için.|
|**DocumentLibraryDependencies**|İsteğe bağlı **Boole** parametresi.<br /><br /> Varsa `true` ve geçerli proje çözümde bir statik kitaplık (.lib) proje üzerinde bağımlılık vardır, bu kitaplık projesi için .xdc dosyalarının geçerli proje için .xml dosyasını çıkış dahil.<br /><br /> Daha fazla bilgi için **belge kitaplığı bağımlılıkları** açıklamasında [XML belgesi oluşturma aracı özellik sayfaları](https://msdn.microsoft.com/library/645912b5-197a-4c36-ba58-64df09444ca0).|
|**OutputFile**|İsteğe bağlı **dize** parametresi.<br /><br /> Varsayılan çıkış dosyası adını geçersiz kılar. Varsayılan adı, işlenen ilk .xdc dosyasının adından türetilir.<br /><br /> Daha fazla bilgi için **/out:** `filename` seçeneğini [XDCMake başvurusu](https://msdn.microsoft.com/library/14e65747-d000-4343-854b-8393bf01cbac). Ayrıca bkz: **/eski** ve **/Fo** xdcmake.exe'yi için komut satırı seçenekleri.|
|**projectName**|İsteğe bağlı **dize** parametresi.<br /><br /> Geçerli projenin adı.|
|**SlashOld**|İsteğe bağlı **Boole** parametresi.<br /><br /> Varsa `true`, ek xdcmake.exe'yi seçeneklerini etkinleştirir.<br /><br /> Daha fazla bilgi için **/eski** xdcmake.exe'yi için komut satırı seçeneği.|
|**Kaynakları**|Gerekli `ITaskItem[]` parametresi.<br /><br /> Tüketilen ve görevler tarafından yayılan MSBuild kaynak dosya öğeleri bir dizisi tanımlanmaktadır.|
|**SuppressStartupBanner**|İsteğe bağlı **Boole** parametresi.<br /><br /> Varsa `true`, görev başladığında telif hakkı ve sürüm numarası iletisinin görüntülenmesini engeller.<br /><br /> Daha fazla bilgi için **/nologo** seçeneğini [XDCMake başvurusu](https://msdn.microsoft.com/library/14e65747-d000-4343-854b-8393bf01cbac).|
|**TrackerLogDirectory**|İsteğe bağlı **dize** parametresi.<br /><br /> İzleyici günlüğü dizini belirtir.|
## <a name="see-also"></a>Ayrıca Bkz.
[Görev Başvurusu](../msbuild/msbuild-task-reference.md)
| 82.210526 | 584 | 0.752881 | tur_Latn | 0.996174 |
5823407e72ef6d241d96d3ce3b51fb308548bfe2 | 1,969 | md | Markdown | docs/connect/python/pymssql/python-sql-driver-pymssql.md | MRGRD56/sql-docs.ru-ru | 4994c363fd2f95812769d48d881fd877abe35738 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/connect/python/pymssql/python-sql-driver-pymssql.md | MRGRD56/sql-docs.ru-ru | 4994c363fd2f95812769d48d881fd877abe35738 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/connect/python/pymssql/python-sql-driver-pymssql.md | MRGRD56/sql-docs.ru-ru | 4994c363fd2f95812769d48d881fd877abe35738 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Драйвер SQL Python — pymssql
description: В этом руководстве описывается установка Python, ODBC Driver for SQL Server и pymssql. Пример кода покажет, как подключиться к базе данных SQL и работать с ней.
ms.custom: ''
ms.date: 10/06/2020
ms.prod: sql
ms.prod_service: connectivity
ms.reviewer: ''
ms.technology: connectivity
ms.topic: conceptual
ms.assetid: 34edf89e-4335-4ef6-827a-54b7af9cc9fd
author: David-Engel
ms.author: v-daenge
ms.openlocfilehash: 1b1388b11c0eaa0b4ddd690095b744e3e86e9aee
ms.sourcegitcommit: 04cf7905fa32e0a9a44575a6f9641d9a2e5ac0f8
ms.translationtype: HT
ms.contentlocale: ru-RU
ms.lasthandoff: 10/07/2020
ms.locfileid: "91811108"
---
# <a name="python-sql-driver---pymssql"></a>Драйвер SQL Python — pymssql
[!INCLUDE[Driver_Python_Download](../../../includes/driver_python_download.md)]
## <a name="get-started"></a>Начало работы
* [Шаг 1. Настройка среды разработки для разработки на Python в pymssql](step-1-configure-development-environment-for-pymssql-python-development.md)
* [Шаг 2. Создание базы данных SQL для разработки на Python в pymssql](step-2-create-a-sql-database-for-pymssql-python-development.md)
* [Шаг 3. Подтверждение концепции, подразумевающее подключение к SQL с помощью pymssql](step-3-proof-of-concept-connecting-to-sql-using-pymssql.md)
## <a name="documentation"></a>Документация
* [Документация по pymssql](https://pypi.org/project/pymssql/)
## <a name="support"></a>Поддержка
Pymssql — это поддерживаемое сообществом программное обеспечение. Майкрософт не оказывает поддержку по этому программному обеспечению.
Чтобы получить помощь, сообщите об ошибке в [репозитории pymssql на GitHub](https://github.com/pymssql/pymssql/issues) или посетите другие ресурсы сообщества Python.
## <a name="community-resources"></a>Ресурсы сообщества
* [Центр по разработке на Python для Azure](https://azure.microsoft.com/develop/python/)
* [Сообщество python.org](https://www.python.org/community/)
| 43.755556 | 173 | 0.780091 | rus_Cyrl | 0.254937 |
5823a8241c6dad58d12be9fdda010081650d2395 | 8,759 | md | Markdown | docs/visual-basic/programming-guide/concepts/linq/mixed-declarative-code-imperative-code-bugs-linq-to-xml.md | WindOfMind/docs.ru-ru | 5e034322f8f6ce87e425a9217189e8275b54d6e8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/visual-basic/programming-guide/concepts/linq/mixed-declarative-code-imperative-code-bugs-linq-to-xml.md | WindOfMind/docs.ru-ru | 5e034322f8f6ce87e425a9217189e8275b54d6e8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/visual-basic/programming-guide/concepts/linq/mixed-declarative-code-imperative-code-bugs-linq-to-xml.md | WindOfMind/docs.ru-ru | 5e034322f8f6ce87e425a9217189e8275b54d6e8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Ошибки смешанного декларативного и императивного кода (LINQ to XML) (Visual Basic)
ms.date: 07/20/2015
ms.assetid: f12b1ab4-bb92-4b92-a648-0525e45b3ce7
ms.openlocfilehash: e7b3b624bb91525d2cda9477c29291e25eba1b07
ms.sourcegitcommit: 9b552addadfb57fab0b9e7852ed4f1f1b8a42f8e
ms.translationtype: MT
ms.contentlocale: ru-RU
ms.lasthandoff: 04/23/2019
ms.locfileid: "61775990"
---
# <a name="mixed-declarative-codeimperative-code-bugs-linq-to-xml-visual-basic"></a>Смешанные ошибки декларативного и императивного кода (LINQ to XML) (Visual Basic)
[!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] содержит различные методы, которые позволяют прямо модифицировать XML-дерево. Можно добавить элементы, удалить элементы, изменить содержимое элемента, добавить атрибуты и т. п. Этот интерфейс программирования описывается в [изменение деревьев XML (LINQ to XML) (Visual Basic)](../../../../visual-basic/programming-guide/concepts/linq/modifying-xml-trees-linq-to-xml.md). Если выполняется переход в пределах одной оси, например <xref:System.Xml.Linq.XContainer.Elements%2A>, и при этом выполняется изменение XML-дерева, можно в итоге обнаружить некоторые неожиданные ошибки.
Этот вид ошибки иногда называется Halloween Problem.
## <a name="definition-of-the-problem"></a>Определение этой ошибки
При создании некоего кода с использованием LINQ, при котором выполняется последовательное прохождение по элементам коллекции, код пишется в декларативном стиле. Это больше похоже на описание того, *что* именно требуется получить, а не *как* именно требуется выполнить задачу. Если написать код, при котором 1) извлекается первый элемент, 2) выполняется его проверка согласно определенному условию, 3) выполняется его изменение и 4) выполняется его помещение назад в список элементов, то это означает, что это был бы императивный код. При этом вы описываете, *как именно* следует выполнить задачу.
Смешение этих стилей кода в одной операции является источником неполадок. Рассмотрим следующий пример.
Предположим, дан список из трех элементов (a, b и c):
`a -> b -> c`
Теперь предположим, что необходимо пройти по связанному списку, добавив три новых пункта (a', b' и c'). При этом необходимо, чтобы результирующий список выглядел так:
`a -> a' -> b -> b' -> c -> c'`
Пишется код, который последовательно обращается к элементам списка и для каждого пункта добавляет новый пункт после него. При этом код распознает элемент `a` и вставит элемент `a'` после него. Теперь код перейдет к следующему узлу списка, которым является `a'`! После чего он добавляет новый элемент списка - `a''`.
Как это следовало бы решить в реальной ситуации? Можно сделать копию оригинального списка, после чего создать полностью новый список. Или, если вы пишете чисто императивный код, можно найти первый пункт, добавить новый пункт и перейти на два шага вперед по списку, чтобы перескочить элемент, который был только что добавлен.
## <a name="adding-while-iterating"></a>Добавление при последовательном переходе
Например, требуется написать некоторый код, при помощи которого для каждого элемента дерева создается его дубликат:
```vb
Dim root As XElement = _
<Root>
<A>1</A>
<B>2</B>
<C>3</C>
</Root>
For Each e As XElement In root.Elements()
root.Add(New XElement(e.Name, e.Value))
Next
```
Этот код представляет собой бесконечный цикл. Инструкция `foreach` последовательно применяется ко всей оси `Elements()`, при этом добавляются новые элементы к элементу `doc`. После этого она переходит на только что добавленные элементы. И поскольку она выделяет память для новых объектов на каждом шаге, она захватит всю доступную память.
Эту неполадку можно устранить за счет переноса массива в память, используя стандартный оператор запросов <xref:System.Linq.Enumerable.ToList%2A> следующим образом.
```vb
Dim root As XElement = _
<Root>
<A>1</A>
<B>2</B>
<C>3</C>
</Root>
For Each e As XElement In root.Elements().ToList()
root.Add(New XElement(e.Name, e.Value))
Next
Console.WriteLine(root)
```
Теперь код работает, как и положено. В итоге получается следующее XML-дерево:
```xml
<Root>
<A>1</A>
<B>2</B>
<C>3</C>
<A>1</A>
<B>2</B>
<C>3</C>
</Root>
```
## <a name="deleting-while-iterating"></a>Удаление элементов при последовательном переходе
Если требуется удалить все узлы, размещенные на определенном уровне, может возникнуть искушение попробовать реализовать это так:
```vb
Dim root As XElement = _
<Root>
<A>1</A>
<B>2</B>
<C>3</C>
</Root>
For Each e As XElement In root.Elements()
e.Remove()
Next
Console.WriteLine(root)
```
Однако этот код не выполнит поставленной задачи. В такой ситуации после удаления первого элемента A он удаляется из XML-дерева, которое содержится в корне, при этом коду метода элементов (Elements method), который выполняет последовательный переход, не удастся найти следующий элемент.
Предыдущий код представит следующий вывод.
```xml
<Root>
<B>2</B>
<C>3</C>
</Root>
```
Решение снова заключается в вызове <xref:System.Linq.Enumerable.ToList%2A>, чтобы материализовать коллекцию следующим образом.
```vb
Dim root As XElement = _
<Root>
<A>1</A>
<B>2</B>
<C>3</C>
</Root>
For Each e As XElement In root.Elements().ToList()
e.Remove()
Next
Console.WriteLine(root)
```
Выводятся следующие результаты.
```xml
<Root />
```
Кроме того, можно совсем исключить итерацию за счет вызова <xref:System.Xml.Linq.XElement.RemoveAll%2A> на родительском элементе.
```vb
Dim root As XElement = _
<Root>
<A>1</A>
<B>2</B>
<C>3</C>
</Root>
root.RemoveAll()
Console.WriteLine(root)
```
## <a name="why-cant-linq-automatically-handle-this"></a>Почему LINQ не может автоматически обрабатывать такие ошибки?
Одним из подходов может быть вызов всех элементов в память, вместо того чтобы проводить неспешное вычисление каждого элемента. Однако это может негативно отразиться на производительности и загрузить память. Фактически, если бы LINQ и (LINQ to XML) использовали этот подход, он бы оказался неудачным в реальных ситуациях.
Другой возможный подход мог бы реализоваться путем введения некоего синтаксиса транзакций в LINQ и использования компилятора для попытки анализа кода и определения того, необходимо ли материализовать какую-то конкретную коллекцию. Однако попытка определения всего кода с побочными эффектами чрезвычайно сложна. Рассмотрим следующий код.
```vb
Dim z = _
From e In root.Elements() _
Where (TestSomeCondition(e)) _
Select DoMyProjection(e)
```
Такому коду для проведения анализа потребуется анализировать методы TestSomeCondition и DoMyProjection, а также все методы, которые вызывают их, чтобы определить, есть ли у кода какие-либо побочные эффекты. Однако коду анализа не удавалось просто искать код, в котором есть побочные эффекты. Для этого потребовалось бы выбрать только тот код, у которого есть побочные эффекты на дочерних элементах `root`.
LINQ to XML не пытается выполнить такой анализ.
Поэтому задача избежания таких проблем лежит на вас.
## <a name="guidance"></a>Руководство
Во-первых, не стоит смешивать декларативный и императивный код.
Даже если вам точно известна семантика ваших коллекций и методов, которые применяются для изменения XML-дерева, если удастся создать некий код, в котором такие категории проблем невозможны, код все равно потребуется поддерживать другим разработчикам в будущем, а для них это не всегда может быть так же ясно, как для вас. Если смешать декларативный и императивный стили, то код значительно усложнится.
Если удастся написать код, который материализует коллекцию таким образом, что эти проблемы удастся избежать, отметьте это в комментариях кода, чтобы другие программисты понимали, как это сделано.
Во-вторых, если требования производительности и другие условия позволяют, используйте только декларативный код. Не следует изменять существующее XML-дерево. Лучше создать новое.
```vb
Dim root As XElement = _
<Root>
<A>1</A>
<B>2</B>
<C>3</C>
</Root>
Dim newRoot As XElement = New XElement("Root", _
root.Elements(), root.Elements())
Console.WriteLine(newRoot)
```
## <a name="see-also"></a>См. также
- [Расширенные программированию LINQ to XML (Visual Basic)](../../../../visual-basic/programming-guide/concepts/linq/advanced-linq-to-xml-programming.md)
| 48.126374 | 629 | 0.724398 | rus_Cyrl | 0.963849 |
5823a913eb7bd5aec196dd8c9388928d57e87a8e | 3,179 | md | Markdown | docs/src/pages/components/menus/menus-zh.md | RalXYZ/material-ui | 96ffba5a3844c2dfa19fd2475dfb3b95a944ae1a | [
"MIT"
] | 1 | 2022-02-07T01:15:52.000Z | 2022-02-07T01:15:52.000Z | docs/src/pages/components/menus/menus-zh.md | RalXYZ/material-ui | 96ffba5a3844c2dfa19fd2475dfb3b95a944ae1a | [
"MIT"
] | null | null | null | docs/src/pages/components/menus/menus-zh.md | RalXYZ/material-ui | 96ffba5a3844c2dfa19fd2475dfb3b95a944ae1a | [
"MIT"
] | null | null | null | ---
title: React Menu（菜单）组件
components: Menu, MenuItem, MenuList, ClickAwayListener, Popover, Popper
githubLabel: 'component: menu'
materialDesign: https://material.io/components/menus
waiAria: 'https://www.w3.org/TR/wai-aria-practices/#menubutton'
---
# Menu 菜单
<p class="description">菜单在临时出现的位置上显示了一系列的选项。</p>
菜单在临时的表面上显示选择列表。 当用户和一个按钮、或者其他控制元件交互的时候，菜单会出现。
{{"component": "modules/components/ComponentLinkHeader.js"}}
## 基础菜单
默认情况下，基础菜单会在描点元素上打开（这种方式可以使用属性来 [改变](#menu-positioning)）。 当靠近屏幕边缘时，简单菜单会在垂直方向上重新对齐，以确保所有菜单子项（menu items）都完全可见。
理想状态下，选择一个选项是会立刻执行此选项并且关闭整个菜单。
**解疑**：与简单菜单不同，一个简单的对话框可以提供与列表项可用选项相关的额外细节，或提供与主要任务相关的导航或正交操作。 虽然它们都可以显示相同的内容，但是菜单组件比对话框组件更受欢迎，因为相比之下菜单组件对用户的干扰更小。
{{"demo": "pages/components/menus/BasicMenu.js"}}
## 选择菜单
In desktop viewport, padding is increased to give more space to the menu.
{{"demo": "pages/components/menus/IconMenu.js", "bg": true}}
## 菜单定位
For the menu that has long list and long text, you can use the `dense` prop to reduce the padding and text size.
{{"demo": "pages/components/menus/DenseMenu.js", "bg": true}}
## MenuList 组合
If used for item selection, when opened, simple menus places the initial focus on the selected menu item. If used for item selection, when opened, simple menus places the initial focus on the selected menu item. 通过 `selected` 属性（在[ListItem](/api/list-item/)中），您能够设置当前被选中的选项。 To use a selected menu item without impacting the initial focus, set the `variant` prop to "menu".
{{"demo": "pages/components/menus/SimpleListMenu.js"}}
## 自定义菜单
因为 `Menu` 组件是基于 `Popover` 组件来进行定位的，所以你也可以使用与之相同的 [定位属性](/components/popover/#anchor-playground) 来对它的位置进行改变。 例如，你可以在描点的下方显示菜单：
{{"demo": "pages/components/menus/PositionedMenu.js"}}
## MenuList 组合
在`菜单`组件的内部，其实使用了 `Popover` 组件。 但是，您可能想要使用不同的元素定位的方式，或者您不想禁止页面的滚动。 为了满足这些需求，我们公开了一个 `MenuList` 组件，您可以像下面例子中这样结合 `Popper` 来编写自己的菜单组件。
`MenuList` 组件的主要任务是处理焦点。
{{"demo": "pages/components/menus/MenuListComposition.js", "bg": true}}
## 设计局限
如果最大高度的菜单仍无法显示所有菜单项，则菜单可以在内部滚动。
{{"demo": "pages/components/menus/AccountMenu.js"}}
## 更改过渡动画
以下是自定义组件的一个示例。 您可以在 [重写文档页面](/customization/how-to-customize/) 中了解更多有关此内容的信息。
{{"demo": "pages/components/menus/CustomizedMenus.js"}}
`MenuItem` 的原理是用额外的样式包装了 `ListItem` 组件。 你可以将同样的列表合成功能来装饰 `MenuItem` 组件：
🎨 If you are looking for inspiration, you can check [MUI Treasury's customization examples](https://mui-treasury.com/styles/menu/).
## 快捷菜单 Context menu
如果最大高度的菜单仍无法显示所有菜单项，则菜单可以在内部滚动。
{{"demo": "pages/components/menus/LongMenu.js"}}
## 补充项目
有 [一个 flexbox 的错误](https://bugs.chromium.org/p/chromium/issues/detail?id=327437)，在 flexbox 的布局中，无法正常使用 `text-overflow: ellipsis`。 您可以使用 `Typography` 组件和 `noWrap` 来解决此问题：
{{"demo": "pages/components/menus/TypographyMenu.js", "bg": true}}
## 更改过渡动画
使用不同的过渡动画。
{{"demo": "pages/components/menus/FadeMenu.js"}}
## 快捷菜单 Context menu
这是一个快捷菜单的示例。 （单击右键就可以打开。）
{{"demo": "pages/components/menus/ContextMenu.js"}}
## Complementary projects
对于更高级的用例，您可以利用：
### PopupState helper
这里有一个第三方包 [`material-ui-popup-state`](https://github.com/jcoreio/material-ui-popup-state) 在大部分情况下，它都能帮你处理好菜单组件的状态。
{{"demo": "pages/components/menus/MenuPopupState.js"}}
| 29.435185 | 373 | 0.754011 | yue_Hant | 0.414568 |
582486590a812e285a3dac8809418611ec73fcdd | 6,566 | md | Markdown | docs/sources/dashboards/playlist.md | bsnyder788/grafana | a54e0ff79df4c2be5bbb4e62a6967bbc2a2220ab | [
"Apache-2.0"
] | 4 | 2021-01-24T03:46:43.000Z | 2021-04-30T02:37:25.000Z | docs/sources/dashboards/playlist.md | bsnyder788/grafana | a54e0ff79df4c2be5bbb4e62a6967bbc2a2220ab | [
"Apache-2.0"
] | 127 | 2020-12-17T07:03:17.000Z | 2022-03-30T13:05:58.000Z | docs/sources/dashboards/playlist.md | bsnyder788/grafana | a54e0ff79df4c2be5bbb4e62a6967bbc2a2220ab | [
"Apache-2.0"
] | 2 | 2020-10-12T23:44:43.000Z | 2021-12-19T20:40:11.000Z | +++
title = "Playlist"
keywords = ["grafana", "dashboard", "documentation", "playlist"]
aliases = ["/docs/grafana/latest/reference/playlist/"]
weight = 4
+++
# Playlist
A playlist is a list of dashboards that are displayed in a sequence. You might use a playlist to build situational awareness or to present your metrics to your team or visitors.
Grafana automatically scales dashboards to any resolution, which makes them perfect for big screens.
You can access the Playlist feature from Grafana's side menu, in the Dashboards submenu.
{{< docs-imagebox img="/img/docs/v50/playlist.png" max-width="25rem">}}
## Create a playlist
You create a playlist to present dashboards in a sequence, with a set order and time interval between dashboards.
1. To access the Playlist feature, hover your cursor over Grafana's side menu.
1. Click **Playlists**.
1. Click **New playlist**.
1. In the **Name** text box, enter a name for your playlist.
1. In the **Interval** text box, enter a time interval.
The time interval is the amount of time for Grafana to stay on a particular dashboard before advancing to the next one on the playlist.
1. Next to the dashboard(s) you want to add to your playlist, click **Add to playlist**.
1. Click **Create**.
## Edit a playlist
You can edit playlists while creating them or after saving them.
1. To access the Playlist feature, hover your cursor over Grafana's side menu.
1. Click **Playlists**.
1. Click on the Playlist that you want to edit.
### Edit the Name of a playlist
1. Double-click within the **Name** text box.
1. Enter a name.
1. Click **Save** to save your changes.
### Edit the Interval of a playlist
1. Double-click within the **Interval** text box.
1. Enter a time interval.
1. Click **Save** to save your changes.
### Add a dashboard to a playlist
1. Next to the dashboard you want to add, click **Add to playlist**.
1. Click **Save** to save your changes.
### Search for a dashboard to add
1. Click the **Search dashboards by name** text box.
1. Search for the playlist by name or regular expression.
1. If needed, filter your results by starred status or tags.
By default, your starred dashboards will appear as options to add to the Playlist.
1. Click **Save** to save your changes.
### Rearrange dashboard order
1. Next to the dashboard you want to move, click the up or down arrow.
1. Click **Save** to save your changes.
### Remove a dashboard
1. Click **Remove[x]** to remove a dashboard from the playlist.
1. Click **Save** to save your changes.
### Delete a playlist
1. Click **Playlists**.
1. Next to the Playlist you want to delete, click **Remove[x]**.
## Save a playlist
You can save a playlist to add it to your **Playlists** page, where you can start it. Be sure that all the dashboards you want to appear in your playlist are added when creating or editing the playlist before saving it.
1. To access the Playlist feature, hover your cursor over Grafana's side menu.
1. Click **Playlists**.
1. Click on the playlist.
1. Edit the playlist.
* Ensure that your playlist has a **Name**, **Interval**, and at least one **Dashboard** added to it.
1. Click **Save**.
## Start a playlist
You can start a playlist in five different view modes, which determine how the menus and navigation bar are displayed on the dashboards.
By default, each dashboard is displayed for the amount of time entered in the Interval field, which can be set while creating or editing a playlist. Once a playlist is started, it can be controlled using the navbar at the top of your screen.
1. From the Dashboards submenu, click **Playlists**.
1. Next to the playlist you want to start, click **Start playlist**.
1. In the dropdown, select the mode you want the playlist to display in.
- **Normal mode:**
- The side menu remains visible.
- The navbar, row and panel controls appear at the top of the screen.
- **TV mode:**
- The side menu is hidden/removed.
- The navbar, row and panel controls appear at the top of the screen.
- Enabled automatically after one minute of user inactivity.
- You can enable it manually using the `d v` sequence shortcut, or by appending the parameter `?inactive` to the dashboard URL.
- You can disable it with any mouse movement or keyboard action.
- **TV mode (with auto fit panels):**
- The side menu is hidden/removed.
- The navbar, row and panel controls appear at the top of the screen.
- Dashboard panels automatically adjust to optimize space on screen.
- **Kiosk mode:**
- The side menu, navbar, row and panel controls are completely hidden/removed from view.
- You can enable it manually using the `d v` sequence shortcut after the playlist has started.
- You can disable it manually with the same shortcut.
- **Kiosk mode (with auto fit panels):**
- The side menu, navbar, row and panel controls are completely hidden/removed from view.
- Dashboard panels automatically adjust to optimize space on screen.
## Control a playlist
You can control a playlist in **Normal** or **TV** mode after it's started, using the navigation bar at the top of your screen.
| Button | Result |
| --- | --- |
| Next (double-right arrow) | Advances to the next dashboard. |
| Back (left arrow) | Returns to the previous dashboard. |
| Stop (square) | Ends the playlist, and exits to the current dashboard. |
| Cycle view mode (monitor icon) | Rotates the display of the dashboards in different view modes. |
| Time range | Displays data within a time range. It can be set to display the last 5 minutes up to 5 years ago, or a custom time range, using the down arrow. |
| Refresh (circle arrow) | Reloads the dashboard, to display the current data. It can be set to reload automatically every 5 seconds to 1 day, using the drop down arrow. |
> Shortcut: Press the Esc key to stop the playlist from your keyboard.
## Share a playlist in a view mode
You can share a playlist by copying the link address on the view mode you prefer, and pasting the URL to your destination.
1. From the Dashboards submenu, click **Playlists**.
1. Next to the playlist you want to share, click **Start playlist**.
1. In the dropdown, right click the view mode you prefer.
1. Click **Copy Link Address** to copy the URL to your clipboard.
Example: The URL for the first playlist on the Grafana Play site in Kiosk mode will look like this:
[https://play.grafana.org/playlists/play/1?kiosk](https://play.grafana.org/playlists/play/1?kiosk).
1. Paste the URL to your destination.
| 43.773333 | 241 | 0.727993 | eng_Latn | 0.997879 |
5824fb879662587785b3c2b97534dbf344403ce2 | 2,832 | md | Markdown | sdk-api-src/content/xenroll/nf-xenroll-ienroll2-installpkcs7blob.md | amorilio/sdk-api | 54ef418912715bd7df39c2561fbc3d1dcef37d7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | sdk-api-src/content/xenroll/nf-xenroll-ienroll2-installpkcs7blob.md | amorilio/sdk-api | 54ef418912715bd7df39c2561fbc3d1dcef37d7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | sdk-api-src/content/xenroll/nf-xenroll-ienroll2-installpkcs7blob.md | amorilio/sdk-api | 54ef418912715bd7df39c2561fbc3d1dcef37d7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
UID: NF:xenroll.IEnroll2.InstallPKCS7Blob
title: IEnroll2::InstallPKCS7Blob (xenroll.h)
description: Processes a certificate or chain of certificates, placing them into the appropriate certificate stores. This method differs from the acceptPKCS7Blob method in that InstallPKCS7Blob does not receive a request certificate.
helpviewer_keywords: ["IEnroll2 interface [Security]","InstallPKCS7Blob method","IEnroll2.InstallPKCS7Blob","IEnroll2::InstallPKCS7Blob","InstallPKCS7Blob","InstallPKCS7Blob method [Security]","InstallPKCS7Blob method [Security]","IEnroll2 interface","security.ienroll4_installpkcs7blob","xenroll/IEnroll2::InstallPKCS7Blob"]
old-location: security\ienroll4_installpkcs7blob.htm
tech.root: security
ms.assetid: fa704c5e-f6ec-4187-b787-7b15cc7d4eb4
ms.date: 12/05/2018
ms.keywords: IEnroll2 interface [Security],InstallPKCS7Blob method, IEnroll2.InstallPKCS7Blob, IEnroll2::InstallPKCS7Blob, InstallPKCS7Blob, InstallPKCS7Blob method [Security], InstallPKCS7Blob method [Security],IEnroll2 interface, security.ienroll4_installpkcs7blob, xenroll/IEnroll2::InstallPKCS7Blob
req.header: xenroll.h
req.include-header:
req.target-type: Windows
req.target-min-winverclnt: Windows XP [desktop apps only]
req.target-min-winversvr: Windows Server 2003 [desktop apps only]
req.kmdf-ver:
req.umdf-ver:
req.ddi-compliance:
req.unicode-ansi:
req.idl:
req.max-support:
req.namespace:
req.assembly:
req.type-library:
req.lib: Uuid.lib
req.dll: Xenroll.dll
req.irql:
targetos: Windows
req.typenames:
req.redist:
ms.custom: 19H1
f1_keywords:
- IEnroll2::InstallPKCS7Blob
- xenroll/IEnroll2::InstallPKCS7Blob
dev_langs:
- c++
topic_type:
- APIRef
- kbSyntax
api_type:
- COM
api_location:
- Xenroll.dll
api_name:
- IEnroll2.InstallPKCS7Blob
---
# IEnroll2::InstallPKCS7Blob
## -description
<p class="CCE_Message">[This method is no longer available for use as of Windows Server 2008 and Windows Vista.]
The <b>InstallPKCS7Blob</b> method processes a certificate or chain of certificates, placing them into the appropriate <a href="/windows/desktop/SecGloss/c-gly">certificate stores</a>. This method differs from the <a href="/windows/desktop/api/xenroll/nf-xenroll-ienroll-acceptpkcs7blob">acceptPKCS7Blob</a> method in that <b>InstallPKCS7Blob</b> does not receive a request certificate. This method was first defined in the <a href="/windows/desktop/api/xenroll/nn-xenroll-ienroll2">IEnroll2</a> interface.
## -parameters
### -param pBlobPKCS7 [in]
A pointer to a <a href="/previous-versions/windows/desktop/legacy/aa381414(v=vs.85)">CRYPT_DATA_BLOB</a> structure that contains a certificate or chain of certificates.
## -returns
The return value is an <b>HRESULT</b>. A value of S_OK indicates success.
## -see-also
<a href="/windows/desktop/api/xenroll/nn-xenroll-ienroll4">IEnroll2</a> | 41.043478 | 508 | 0.79202 | eng_Latn | 0.446957 |
582573bd46edad9dc3560b4c234b105e8c8cbc81 | 980 | md | Markdown | catalog/dramatic-de-nani-ga-warui/en-US_dramatic-de-nani-ga-warui.md | htron-dev/baka-db | cb6e907a5c53113275da271631698cd3b35c9589 | [
"MIT"
] | 3 | 2021-08-12T20:02:29.000Z | 2021-09-05T05:03:32.000Z | catalog/dramatic-de-nani-ga-warui/en-US_dramatic-de-nani-ga-warui.md | zzhenryquezz/baka-db | da8f54a87191a53a7fca54b0775b3c00f99d2531 | [
"MIT"
] | 8 | 2021-07-20T00:44:48.000Z | 2021-09-22T18:44:04.000Z | catalog/dramatic-de-nani-ga-warui/en-US_dramatic-de-nani-ga-warui.md | zzhenryquezz/baka-db | da8f54a87191a53a7fca54b0775b3c00f99d2531 | [
"MIT"
] | 2 | 2021-07-19T01:38:25.000Z | 2021-07-29T08:10:29.000Z | # Dramatic de Nani ga Warui
- **type**: manga
- **volumes**: 1
- **chapters**: 6
- **original-name**: ドラマチックでなにが悪い
- **start-date**: 2019-07-25
- **end-date**: 2019-07-25
## Tags
- yaoi
## Authors
- Satou
- Chidori (Story & Art)
## Sinopse
Haru and Kai are childhood friends, and their friendship is stronger than most. Haru likes hanging out with girls—they're cute, they're soft, and they smell good. But at the same time, he feels most at ease hanging out with Kai. One day, Haru stumbles upon Kai getting off while he calls Haru's name. Shocked at what he has seen, he becomes oddly intrigued with Kai. Two high school boys: an eligible bachelor and an outgoing pretty boy. A bittersweet story of a glittering young romance and more is about to unfold!
(Source: Renta!)
## Links
- [My Anime list](https://myanimelist.net/manga/132290/Dramatic_de_Nani_ga_Warui)
| 32.666667 | 516 | 0.713265 | eng_Latn | 0.981302 |
5825acc5e4247580a5a18b609ae624e50b304b80 | 31,120 | md | Markdown | articles/search/cognitive-search-tutorial-blob-python.md | BhernardoViana/azure-docs.pt-br | 674a5e028fda45bebb645a39d19250cc7ca9c053 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/search/cognitive-search-tutorial-blob-python.md | BhernardoViana/azure-docs.pt-br | 674a5e028fda45bebb645a39d19250cc7ca9c053 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/search/cognitive-search-tutorial-blob-python.md | BhernardoViana/azure-docs.pt-br | 674a5e028fda45bebb645a39d19250cc7ca9c053 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'Tutorial: Criar um conjunto de habilidades em Python usando APIs REST'
titleSuffix: Azure Cognitive Search
description: Percorra um exemplo de extração de dados, linguagem natural e processamento de imagem por IA na Pesquisa Cognitiva do Azure usando um notebook Jupyter Python. Os dados extraídos são indexados e podem ser acessados facilmente pela consulta.
manager: nitinme
author: HeidiSteen
ms.author: heidist
ms.service: cognitive-search
ms.devlang: python
ms.topic: tutorial
ms.date: 11/04/2019
ms.openlocfilehash: d7b4755bb2e69c4a852901b71d917c6baa5d63ae
ms.sourcegitcommit: dd0304e3a17ab36e02cf9148d5fe22deaac18118
ms.translationtype: HT
ms.contentlocale: pt-BR
ms.lasthandoff: 11/22/2019
ms.locfileid: "74406423"
---
# <a name="tutorial-create-an-ai-enrichment-pipeline-using-rest-and-python"></a>Tutorial: Criar um pipeline de enriquecimento de IA usando REST e Python
Neste tutorial, você aprenderá a mecânica de programação de enriquecimento de dados na Pesquisa Cognitiva do Azure usando *habilidades cognitivas*. As habilidades são apoiadas pelos recursos de processamento de linguagem natural (PLN) e análise de imagem nos Serviços Cognitivos. Por meio da composição do conjunto de qualificações e configuração, você pode extrair texto e representações de texto de um arquivo de imagem ou documento digitalizado. Você também pode detectar a linguagem, entidades, frases-chave e muito mais. O resultado é um conteúdo mais avançado em um índice de pesquisa, criado com aprimoramentos de IA em um pipeline de indexação.
Neste tutorial, você usará Python para realizar as seguintes tarefas:
> [!div class="checklist"]
> * Criar um pipeline de indexação que enriquece dados de exemplo em rota para um índice
> * Aplique as qualificações internas: o reconhecimento de entidade, a detecção de idioma, manipulação de texto e extração de frase-chave
> * Saiba como encadear habilidades mapeando entradas para saídas em um conjunto de qualificações
> * Executar solicitações e analisar resultados
> * Redefinir o índice e indexadores para desenvolvimento futuro
A saída é um índice pesquisável de texto completo na Pesquisa Cognitiva do Azure. Você pode aprimorar o índice com outros recursos padrão, como [sinônimos](search-synonyms.md), [perfis de pontuação](https://docs.microsoft.com/rest/api/searchservice/add-scoring-profiles-to-a-search-index), [analisadores](search-analyzers.md), e [filtros](search-filters.md).
Este tutorial é executado no serviço gratuito, mas o número de transações gratuitos é limitado a 20 documentos por dia. Se você quiser executar este tutorial mais de uma vez no mesmo dia, use um conjunto de arquivos menor para que você possa encaixar mais execuções.
> [!NOTE]
> À medida que expandir o escopo aumentando a frequência de processamento, adicionando mais documentos ou adicionando mais algoritmos de IA, você precisará [anexar um recurso de Serviços Cognitivos faturável](cognitive-search-attach-cognitive-services.md). As cobranças são geradas ao chamar APIs nos Serviços Cognitivos e para a extração de imagem, como parte do estágio de quebra de documento na Pesquisa Cognitiva do Azure. Não há encargos para extração de texto em documentos.
>
> A execução de habilidades integradas é cobrada nos [preços pagos conforme o uso dos Serviços Cognitivos](https://azure.microsoft.com/pricing/details/cognitive-services/) existentes. O preço da extração de imagem é descrito na [página de preços da Pesquisa Cognitiva do Azure](https://go.microsoft.com/fwlink/?linkid=2042400).
Se você não tiver uma assinatura do Azure, crie uma [conta gratuita](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) antes de começar.
## <a name="prerequisites"></a>Pré-requisitos
Os serviços, as ferramentas e os dados a seguir são usados neste tutorial.
+ [Criar uma conta de armazenamento do Azure](https://docs.microsoft.com/azure/storage/common/storage-quickstart-create-account) para armazenar os dados de exemplo. Verifique se a conta de armazenamento está na mesma região da Pesquisa Cognitiva do Azure.
+ [Anaconda 3.x](https://www.anaconda.com/distribution/#download-section), que fornece o Python 3.x e os Notebooks Jupyter.
+ [Dados de exemplo](https://1drv.ms/f/s!As7Oy81M_gVPa-LCb5lC_3hbS-4) consistem em um conjunto de pequenos arquivos de tipos diferentes.
+ [Crie um serviço da Pesquisa Cognitiva do Azure](search-create-service-portal.md) ou [localize um serviço existente](https://ms.portal.azure.com/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.Search%2FsearchServices) na assinatura atual. Você pode usar um serviço gratuito para este tutorial.
## <a name="get-a-key-and-url"></a>Obter uma chave e uma URL
Para interagir com o serviço da Pesquisa Cognitiva do Azure, será necessária a URL de serviço e uma chave de acesso. Um serviço de pesquisa é criado com ambos, portanto, se você adicionou a Pesquisa Cognitiva do Azure à sua assinatura, siga estas etapas para obter as informações necessárias:
1. [Entre no portal do Azure](https://portal.azure.com/) e, na página **Visão Geral** do serviço de pesquisa, obtenha a URL. Um ponto de extremidade de exemplo pode parecer com `https://mydemo.search.windows.net`.
1. Em **Configurações** > **Chaves**, obtenha uma chave de administração para adquirir todos os direitos sobre o serviço. Há duas chaves de administração intercambiáveis, fornecidas para a continuidade dos negócios, caso seja necessário sobrepor uma. É possível usar a chave primária ou secundária em solicitações para adicionar, modificar e excluir objetos.
Todas as solicitações requerem uma chave de api em cada pedido enviado ao serviço. Uma chave válida estabelece a relação de confiança, para cada solicitação, entre o aplicativo que envia a solicitação e o serviço que a manipula.
## <a name="prepare-sample-data"></a>Preparar os dados de exemplo
O pipeline de enriquecimento extrai de fontes de dados do Azure. Os dados de origem precisam ser originários de um tipo de fonte de dados com suporte de um [indexador da Pesquisa Cognitiva do Azure](search-indexer-overview.md). Para este exercício, usamos o armazenamento de blob para apresentar múltiplos tipos de conteúdo.
1. [Entre no portal do Azure](https://portal.azure.com), navegue até sua conta de Armazenamento do Azure, clique em **Blobs** e, em seguida, clique em **+ Contêiner**.
1. [Crie um contêiner de Blob](https://docs.microsoft.com/azure/storage/blobs/storage-quickstart-blobs-portal) para conter dados de exemplo. Você pode definir o Nível de Acesso Público para qualquer um de seus valores válidos.
1. Após o contêiner ser criado, abra-o e selecione **Carregar** na barra de comandos para carregar os arquivos de exemplo que você baixou na etapa anterior.
1. Depois que os arquivos de exemplo são carregados, obter o nome do contêiner e uma cadeia de caracteres de conexão para o armazenamento de Blob. Você pode fazer isso navegando até você conta de armazenamento no portal do Azure. Clique em **Chaves de acesso**e copie o campo **Cadeia de conexão**.
A cadeia de conexão terá este formato: `DefaultEndpointsProtocol=https;AccountName=<YOUR-STORAGE-ACCOUNT-NAME>;AccountKey=<YOUR-STORAGE-ACCOUNT-KEY>;EndpointSuffix=core.windows.net`
Mantenha a cadeia de conexão em um lugar de fácil acesso. Você precisará dela em uma etapa posterior.
Existem outras maneiras de especificar a cadeia de caracteres de conexão, como fornecer uma assinatura de acesso compartilhado. Para saber mais sobre as credenciais de fonte de dados, consulte [indexação armazenamento de BLOBs do Azure](search-howto-indexing-azure-blob-storage.md#Credentials).
## <a name="create-a-jupyter-notebook"></a>Criar um notebook Jupyter
> [!Note]
> Este artigo mostra como criar uma fonte de dados, um índice, um indexador e um conjunto de habilidades usando uma série de scripts Python. Para baixar o exemplo de notebook completo, vá para o [repositório Azure-Search-python-samples](https://github.com/Azure-Samples/azure-search-python-samples/tree/master/Tutorial-AI-Enrichment-Jupyter-Notebook).
Use o Anaconda Navigator para iniciar o Jupyter Notebook e criar um novo notebook Python 3.
## <a name="connect-to-azure-cognitive-search"></a>Conectar-se à Pesquisa Cognitiva do Azure
No notebook, execute este script a fim de carregar as bibliotecas usadas para trabalhar com JSON e formular solicitações HTTP.
```python
import json
import requests
from pprint import pprint
```
Em seguida, defina os nomes da fonte de dados, do índice, do indexador e do conjunto de habilidades. Execute este script a fim de configurar os nomes para este tutorial.
```python
# Define the names for the data source, skillset, index and indexer
datasource_name = "cogsrch-py-datasource"
skillset_name = "cogsrch-py-skillset"
index_name = "cogsrch-py-index"
indexer_name = "cogsrch-py-indexer"
```
> [!Tip]
> Em um serviço gratuito, você tem a limitação de três índices, indexadores e fontes de dados. Este tutorial cria um de cada. Verifique se há espaço para criar novos objetos antes de prosseguir.
No script a seguir, substitua os espaços reservados para seu serviço de pesquisa (YOUR-SEARCH-SERVICE-NAME) e para a chave da API de administração (YOUR-ADMIN-API-KEY) e execute-o para configurar o ponto de extremidade do serviço de pesquisa.
```python
# Setup the endpoint
endpoint = 'https://<YOUR-SEARCH-SERVICE-NAME>.search.windows.net/'
headers = {'Content-Type': 'application/json',
'api-key': '<YOUR-ADMIN-API-KEY>'}
params = {
'api-version': '2019-05-06'
}
```
## <a name="create-a-data-source"></a>Criar uma fonte de dados
Agora que os serviços e os arquivos de origem estão preparados, comece montando os componentes do pipeline de indexação. Comece com um objeto de fonte de dados que indica à Pesquisa Cognitiva do Azure como recuperar dados de origem externa.
No script a seguir, substitua o espaço reservado YOUR-BLOB-RESOURCE-CONNECTION-STRING pela cadeia de conexão do blob que você criou na etapa anterior. Em seguida, execute o script para criar uma fonte de dados chamada `cogsrch-py-datasource`.
```python
# Create a data source
datasourceConnectionString = "<YOUR-BLOB-RESOURCE-CONNECTION-STRING>"
datasource_payload = {
"name": datasource_name,
"description": "Demo files to demonstrate cognitive search capabilities.",
"type": "azureblob",
"credentials": {
"connectionString": datasourceConnectionString
},
"container": {
"name": "basic-demo-data-pr"
}
}
r = requests.put(endpoint + "/datasources/" + datasource_name,
data=json.dumps(datasource_payload), headers=headers, params=params)
print(r.status_code)
```
A solicitação deve retornar um código de status 201 que confirma o êxito.
No portal do Azure, na página do painel do serviço de pesquisa, verifique se cogsrch-py-datasource aparece na lista **Fontes de dados**. Clique em **Atualizar** para atualizar a página.
## <a name="create-a-skillset"></a>Criar um conjunto de habilidades
Nesta etapa, você deve definir um conjunto de etapas de aprimoramento para aplicar aos dados. Chamar cada etapa enriquecimento um *habilidade*e o conjunto de etapas de enriquecimento um *conjunto de qualificações*. Este tutorial usa [habilidades cognitivas internas](cognitive-search-predefined-skills.md) para o conjunto de habilidades:
+ [A detecção de idioma](cognitive-search-skill-language-detection.md) para identificar o idioma do conteúdo.
+ [Divisão de texto](cognitive-search-skill-textsplit.md) para dividir o conteúdo grande em partes menores antes de chamar a habilidade de extração de frase-chave. Extração de frase-chave aceita entradas de 50.000 caracteres ou menos. Alguns dos arquivos de exemplo precisam dividir para se ajustar dentro desse limite.
+ [Reconhecimento de entidade](cognitive-search-skill-entity-recognition.md) para extrair os nomes das organizações de conteúdo no contêiner de blobs.
+ [Extração de frase chave](cognitive-search-skill-keyphrases.md) para destacar as principais frases-chave.
### <a name="python-script"></a>Script Python
Execute o script a seguir para criar um conjunto de habilidades chamado `cogsrch-py-skillset`.
```python
# Create a skillset
skillset_payload = {
"name": skillset_name,
"description":
"Extract entities, detect language and extract key-phrases",
"skills":
[
{
"@odata.type": "#Microsoft.Skills.Text.EntityRecognitionSkill",
"categories": ["Organization"],
"defaultLanguageCode": "en",
"inputs": [
{
"name": "text", "source": "/document/content"
}
],
"outputs": [
{
"name": "organizations", "targetName": "organizations"
}
]
},
{
"@odata.type": "#Microsoft.Skills.Text.LanguageDetectionSkill",
"inputs": [
{
"name": "text", "source": "/document/content"
}
],
"outputs": [
{
"name": "languageCode",
"targetName": "languageCode"
}
]
},
{
"@odata.type": "#Microsoft.Skills.Text.SplitSkill",
"textSplitMode": "pages",
"maximumPageLength": 4000,
"inputs": [
{
"name": "text",
"source": "/document/content"
},
{
"name": "languageCode",
"source": "/document/languageCode"
}
],
"outputs": [
{
"name": "textItems",
"targetName": "pages"
}
]
},
{
"@odata.type": "#Microsoft.Skills.Text.KeyPhraseExtractionSkill",
"context": "/document/pages/*",
"inputs": [
{
"name": "text", "source": "/document/pages/*"
},
{
"name": "languageCode", "source": "/document/languageCode"
}
],
"outputs": [
{
"name": "keyPhrases",
"targetName": "keyPhrases"
}
]
}
]
}
r = requests.put(endpoint + "/skillsets/" + skillset_name,
data=json.dumps(skillset_payload), headers=headers, params=params)
print(r.status_code)
```
A solicitação deve retornar um código de status 201 que confirma o êxito.
A habilidade de extração de frase-chave é aplicada a cada página. A definição do contexto como `"document/pages/*"` faz com que esse aprimorador seja executado para cada membro da matriz de documento/páginas (para cada página do documento).
Cada uma delas executa no conteúdo do documento. Durante o processamento, a Pesquisa Cognitiva do Azure abre cada documento para ler o conteúdo de diferentes formatos de arquivo. O texto encontrado no arquivo de origem é colocado em um campo `content`, um para cada documento. Portanto, defina a entrada como `"/document/content"`.
Uma representação gráfica do conjunto de qualificações é mostrada abaixo.
As saídas podem ser mapeadas para um índice, usadas como entrada para uma habilidade posterior, ou ambos, como é o caso com o código de idioma. No índice, um código de idioma é útil para filtragem. Como uma entrada, o código de idioma é usado por habilidades de análise de texto para informar as regras linguísticas em torno de quebra de palavras.
Para obter mais informações sobre conceitos básicos do conjunto de qualificações, consulte [como definir um conjunto de qualificações](cognitive-search-defining-skillset.md).
## <a name="create-an-index"></a>Crie um índice
Nesta seção, você define o esquema de índice especificando os campos que serão incluídos no índice de pesquisa e definindo os atributos de pesquisa para cada campo. Campos têm um tipo e podem levar a atributos que determinam como o campo é usado (pesquisável, classificável e assim por diante). Nomes de campo em um índice não são necessários para identicamente correspondem aos nomes de campo na fonte. Em uma etapa posterior, você deve adicionar mapeamentos de campo em um indexador para conectar-se campos de origem-destino. Nesta etapa, defina o índice usando as convenções de nomenclatura de campo relevantes para o aplicativo de pesquisa.
Este exercício usa os seguintes campos e tipos de campo:
| nomes de campo: | ID | conteúdo | languageCode | keyPhrases | organizações |
|--------------|----------|-------|----------|--------------------|-------------------|
| nomes de campo: | Edm.String|Edm.String| Edm.String| List<Edm.String> | List<Edm.String> |
Execute este script para criar o índice chamado `cogsrch-py-index`.
```python
# Create an index
index_payload = {
"name": index_name,
"fields": [
{
"name": "id",
"type": "Edm.String",
"key": "true",
"searchable": "true",
"filterable": "false",
"facetable": "false",
"sortable": "true"
},
{
"name": "content",
"type": "Edm.String",
"sortable": "false",
"searchable": "true",
"filterable": "false",
"facetable": "false"
},
{
"name": "languageCode",
"type": "Edm.String",
"searchable": "true",
"filterable": "false",
"facetable": "false"
},
{
"name": "keyPhrases",
"type": "Collection(Edm.String)",
"searchable": "true",
"filterable": "false",
"facetable": "false"
},
{
"name": "organizations",
"type": "Collection(Edm.String)",
"searchable": "true",
"sortable": "false",
"filterable": "false",
"facetable": "false"
}
]
}
r = requests.put(endpoint + "/indexes/" + index_name,
data=json.dumps(index_payload), headers=headers, params=params)
print(r.status_code)
```
A solicitação deve retornar um código de status 201 que confirma o êxito.
Para saber mais sobre como definir um índice, consulte [Criar Índice (API REST da Pesquisa Cognitiva do Azure)](https://docs.microsoft.com/rest/api/searchservice/create-index).
## <a name="create-an-indexer-map-fields-and-execute-transformations"></a>Crie um indexador, mapear os campos e executar transformações
Até agora, você criou uma fonte de dados, um conjunto de habilidades e um índice. Esses três componentes se tornam parte de um [indexador](search-indexer-overview.md) que reúne cada item em uma única operação de várias fases. Para formar um indexador com esses objetos, você deve definir mapeamentos de campo.
+ Os fieldMappings são processados antes do conjunto de habilidades, mapeando campos de origem da fonte de dados para campos de destino em um índice. Se os tipos e os nomes do campo forem os mesmos em ambas as extremidades, nenhum mapeamento será necessário.
+ Os outputFieldMappings são processados depois do conjunto de habilidades, fazendo referência a sourceFieldNames que não existem até a decodificação de documentos ou até que o enriquecimento os crie. O targetFieldName é um campo em um índice.
Além de conectar entradas a saídas, você também pode usar mapeamentos de campo para mesclar estruturas de dados. Para obter mais informações, consulte [Como mapear campos enriquecidos para um índice pesquisável](cognitive-search-output-field-mapping.md).
Execute este script para criar um indexador chamado `cogsrch-py-indexer`.
```python
# Create an indexer
indexer_payload = {
"name": indexer_name,
"dataSourceName": datasource_name,
"targetIndexName": index_name,
"skillsetName": skillset_name,
"fieldMappings": [
{
"sourceFieldName": "metadata_storage_path",
"targetFieldName": "id",
"mappingFunction":
{"name": "base64Encode"}
},
{
"sourceFieldName": "content",
"targetFieldName": "content"
}
],
"outputFieldMappings":
[
{
"sourceFieldName": "/document/organizations",
"targetFieldName": "organizations"
},
{
"sourceFieldName": "/document/pages/*/keyPhrases/*",
"targetFieldName": "keyPhrases"
},
{
"sourceFieldName": "/document/languageCode",
"targetFieldName": "languageCode"
}
],
"parameters":
{
"maxFailedItems": -1,
"maxFailedItemsPerBatch": -1,
"configuration":
{
"dataToExtract": "contentAndMetadata",
"imageAction": "generateNormalizedImages"
}
}
}
r = requests.put(endpoint + "/indexers/" + indexer_name,
data=json.dumps(indexer_payload), headers=headers, params=params)
print(r.status_code)
```
A solicitação deve retornar um código de status 201 rapidamente; no entanto, o processamento pode levar vários minutos para concluir. Embora o conjunto de dados seja pequeno, as habilidades analíticas, como análise de imagem, exigem computação intensa e levam tempo.
Use o script [Verificar status do indexador](#check-indexer-status) da próxima seção para determinar quando o processo do indexador foi concluído.
> [!TIP]
> Criar um indexador invoca o pipeline. Se houver um problema com o acesso aos dados, o mapeamento de entradas e saídas ou a ordem das operações, ele será exibido nesse estágio. Para executar novamente o pipeline com as alterações de código ou script, é preciso primeiro excluir objetos. Para saber mais, confira [Reiniciar e Reexecutar](#reset).
#### <a name="explore-the-request-body"></a>Explore o corpo da solicitação
O script define `"maxFailedItems"` como -1, que instrui o mecanismo de indexação para ignorar erros durante a importação de dados. Isso é útil porque há portanto alguns documentos na fonte de dados de demonstração. Para uma fonte de dados maior, você definirá o valor maior que 0.
Observe também o `"dataToExtract":"contentAndMetadata"` instrução nos parâmetros de configuração. Essa instrução manda o indexador extrair o conteúdo de formatos de arquivo diferentes e os metadados relacionados a cada arquivo.
Quando o conteúdo é extraído, você pode definir `imageAction` para extrair o texto da imagem foi encontrada na fonte de dados. A configuração `"imageAction":"generateNormalizedImages"`, combinada com a Habilidade de OCR e a Habilidade de Mesclagem de Texto, instrui o indexador a extrair o texto das imagens (por exemplo, a palavra "pare" de uma placa de trânsito "Pare") e inseri-la como parte do campo de conteúdo. Esse comportamento aplica-se tanto às imagens inseridas nos documentos (imagine uma imagem em um arquivo PDF) quanto às imagens encontradas na fonte de dados, por exemplo, um arquivo JPG.
<a name="check-indexer-status"></a>
## <a name="check-indexer-status"></a>Checar o status do indexador
Depois que o indexador for definido, ele é executado automaticamente quando você enviar a solicitação. Dependendo de quais habilidades cognitivas definida, a indexação pode demorar mais do que o esperado. Para descobrir se o processamento do indexador foi concluído, execute o script a seguir.
```python
# Get indexer status
r = requests.get(endpoint + "/indexers/" + indexer_name +
"/status", headers=headers, params=params)
pprint(json.dumps(r.json(), indent=1))
```
Na resposta, monitore os valores de "status" e "endTime" em “lastResult”. Execute o script periodicamente para verificar o status. Quando o indexador for concluído, o status será definido como "success", será especificado um "endTime" e a resposta incluirá todos os erros e avisos que ocorreram durante o aprimoramento.
Os avisos são comuns com algumas combinações de arquivo e a habilidade de origem e sempre não indicam um problema. Neste tutorial, os avisos não são problemáticos. Por exemplo, um dos arquivos JPEG que não tem texto mostrará o aviso nesta captura de tela.
## <a name="query-your-index"></a>Consultar o índice
Depois de terminar de indexação, execute consultas que retornam o conteúdo dos campos individuais. Por padrão, a Pesquisa Cognitiva do Azure retorna os 50 melhores resultados. Os dados de exemplo serão pequenos para que o padrão funciona bem. No entanto, ao trabalhar com grandes conjuntos de dados, você precisará incluir parâmetros na cadeia de caracteres de consulta para retornar mais resultados. Para obter instruções, consulte [Como paginar resultados da Pesquisa Cognitiva do Azure](search-pagination-page-layout.md).
Como uma etapa de verificação, consulte o índice para todos os campos.
```python
# Query the index for all fields
r = requests.get(endpoint + "/indexes/" + index_name,
headers=headers, params=params)
pprint(json.dumps(r.json(), indent=1))
```
O resultado deve ser semelhante ao exemplo a seguir. A captura de tela mostra apenas uma parte da resposta.
A saída é o esquema de índice, com o nome, tipo e atributos de cada campo.
Enviar uma segunda consulta para `"*"` para retornar todo o conteúdo de um único campo, como `organizations`.
```python
# Query the index to return the contents of organizations
r = requests.get(endpoint + "/indexes/" + index_name +
"/docs?&search=*&$select=organizations", headers=headers, params=params)
pprint(json.dumps(r.json(), indent=1))
```
O resultado deve ser semelhante ao exemplo a seguir. A captura de tela mostra apenas uma parte da resposta.
Repita para campos adicionais: conteúdo, idioma, frases-chave e organizações neste exercício. Você pode retornar vários campos via `$select` usando uma lista delimitada por vírgulas.
Você pode usar GET ou POST, dependendo do tamanho e complexidade de cadeia de caracteres de consulta. Para obter mais informações, consulte a [Consulta usando a API REST](https://docs.microsoft.com/rest/api/searchservice/search-documents).
<a name="reset"></a>
## <a name="reset-and-rerun"></a>Redefinir e execute novamente
Nos primeiros estágios experimentais de desenvolvimento do pipeline, a abordagem mais prática para as iterações de design é excluir os objetos da Pesquisa Cognitiva do Azure e permitir que seu código para recriá-los. Nomes de recurso são exclusivos. Excluir um objeto permite que você recriá-la usando o mesmo nome.
Reindexar seus documentos com as novas definições:
1. Exclua o índice para remover dados persistentes. Exclua o indexador para recriá-la em seu serviço.
2. Modifique as definições do conjunto de habilidades e do índice.
3. Recrie um índice e um indexador no serviço para executar o pipeline.
Use o portal para excluir índices, indexadores e conjuntos de habilidades. Ao excluir o indexador, também é possível excluir o índice, o conjunto de habilidades e a fonte de dados ao mesmo tempo.
Você também pode excluí-los usando um script. O script a seguir excluirá o conjunto de habilidades que criamos. Você pode modificar a solicitação facilmente para excluir o índice, o indexador e a fonte de dados.
```python
# delete the skillset
r = requests.delete(endpoint + "/skillsets/" + skillset_name,
headers=headers, params=params)
pprint(json.dumps(r.json(), indent=1))
```
Como seu código amadurece, talvez queira refinar uma estratégia de reconstrução. Para saber mais, confira [Como recompilar um índice](search-howto-reindex.md).
## <a name="takeaways"></a>Observações
Este tutorial demonstra as etapas básicas para a criação de um pipeline de indexação enriquecido durante a criação de componentes: uma fonte de dados, o conjunto de qualificações, o índice e o indexador.
Introduzimos [habilidades internas](cognitive-search-predefined-skills.md), com definições de conjunto de habilidades e uma maneira de encadear habilidades por meio de entradas e saídas. Você também aprendeu que `outputFieldMappings` na definição do indexador é necessário para encaminhar valores enriquecidos do pipeline em um índice pesquisável em um serviço da Pesquisa Cognitiva do Azure.
Por fim, você aprendeu a testar os resultados e a redefinir o sistema para ter novas iterações. Você aprendeu que emitir consultas em relação ao índice retorna a saída criada pelo pipeline de indexação enriquecido. Nesta versão, há um mecanismo para exibir as construções internas (enriquecidas documentos criados pelo sistema). Também aprendeu a verificar o status do indexador e quais objetos devem ser excluídos antes de executar novamente um pipeline.
## <a name="clean-up-resources"></a>Limpar recursos
A maneira mais rápida de fazer a limpeza depois de um tutorial é excluindo o grupo de recursos que contém o serviço da Pesquisa Cognitiva do Azure e o serviço Blob do Azure. Supondo que tenha colocado os dois serviços no mesmo grupo, exclua o grupo de recursos para eliminar permanentemente todo o seu conteúdo, inclusive os serviços e o conteúdo armazenado que criou para este tutorial. No portal, o nome do grupo de recurso está na página de Visão geral de cada serviço.
## <a name="next-steps"></a>Próximas etapas
Personalizar ou estender o pipeline com qualificações personalizadas. Criando uma habilidade personalizada e adicionando-a a um conjunto de qualificações permite que você carregue texto ou análise de imagem que você escreve por conta própria.
> [!div class="nextstepaction"]
> [Exemplo: Como criar uma habilidade personalizada para enriquecimento de IA](cognitive-search-create-custom-skill-example.md)
| 59.731286 | 653 | 0.727474 | por_Latn | 0.998351 |
5825b4170da57715b4c01c56ecd9c7506a7131be | 5,211 | md | Markdown | Advertising/bingads-13/guides/get-started-java.md | eric-urban/Advertising-docs | 97c1fd3412a4f7a9610bb52d90170dd65bd23ff4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | Advertising/bingads-13/guides/get-started-java.md | eric-urban/Advertising-docs | 97c1fd3412a4f7a9610bb52d90170dd65bd23ff4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | Advertising/bingads-13/guides/get-started-java.md | eric-urban/Advertising-docs | 97c1fd3412a4f7a9610bb52d90170dd65bd23ff4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "Get Started Using Java with Bing Ads API"
ms.service: "bing-ads"
ms.topic: "article"
author: eric-urban
ms.author: eur
description: Install the Bing Ads Java SDK and discover code examples.
---
# Get Started Using Java with Bing Ads API
To get started developing Bing Ads API applications with Java, you can start with the [provided examples](code-examples.md) or follow one of the application walkthroughs for a [Web](walkthrough-web-application-java.md) or [Desktop](walkthrough-desktop-application-java.md) application.
You will need user credentials with access to Microsoft Advertising either in [production](https://ads.microsoft.com/) or [sandbox](https://secure.sandbox.bingads.microsoft.com/Auth?EnvContext=Sandbox). For the production environment you will need a [production developer token](get-started.md#get-developer-token). All sandbox clients can use the universal sandbox developer token i.e., **BBD37VB98**. For more information, please see [Get Started With the Bing Ads API](get-started.md) and [Sandbox](sandbox.md#access).
To authenticate via OAuth, you must also register an application and get the corresponding client identifier. You also need to take note of the client secret and redirect URI if you are developing a web application. For more details about registering an application in production and the authorization code grant flow, see [Authentication with OAuth](authentication-oauth.md) and [Authentication With the SDKs](sdk-authentication.md#oauth). Although in production you must use your own application ID (a.k.a. client ID), all Microsoft Advertising customers can use the public "Sandbox Tutorial App" client ID in sandbox i.e., **db41b09d-6e50-4f4a-90ac-5a99caefb52f**. For more information, please see [Sandbox](sandbox.md#access).
## <a name="installation"></a>Install the SDK
The Bing Ads Java [SDK](client-libraries.md) depends on the libraries listed at the [Maven Repository](https://mvnrepository.com/artifact/com.microsoft.bingads/microsoft.bingads/).
When you create a Maven project and include the *microsoft.bingads* Maven artifact as shown below, additional dependencies are installed automatically. If you are not using a Maven project, you must include the correct version of each dependency. For more information, please see the [Walkthrough: Bing Ads API Web Application in Java](walkthrough-web-application-java.md) or [Walkthrough: Bing Ads API Desktop Application in Java](walkthrough-desktop-application-java.md) application examples.
```xml
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
...
<dependencies>
<dependency>
<groupId>com.microsoft.bingads</groupId>
<artifactId>microsoft.bingads</artifactId>
<version>13.0.5</version>
</dependency>
</dependencies>
</project>
```
> [!NOTE]
> Version 13.0.5 is included as an example. For details about the latest SDK dependency version, please see the [Bing Ads Java SDK GitHub README.md](https://github.com/BingAds/BingAds-Java-SDK).
## <a name="walkthrough"></a>Walkthroughs
Once you have the Bing Ads Java [SDK](client-libraries.md) installed, you can either browse the [Bing Ads API Code Examples](code-examples.md), download the examples from [GitHub](https://github.com/BingAds/BingAds-Java-SDK/tree/main/examples), or follow one of the application walkthroughs for a [Web](walkthrough-web-application-java.md) or [Desktop](walkthrough-desktop-application-java.md) application.
## <a name="sandbox"></a>Configuring Sandbox
To use the [Sandbox](sandbox.md) environment, create a new text file named *bingads.properties* within your project source root directory e.g. **ProjectName\src\bingads.properties** and add the following text. The following are the complete contents of the *bingads.properties* file. If the sandbox environment setting is malformed or missing, the default environment is production.
```no-highlight
environment=Sandbox
```
You can also set the environment for each ServiceClient individually as follows.
```java
CustomerService = new ServiceClient<ICustomerManagementService>(
authorizationData,
ApiEnvironment.SANDBOX,
ICustomerManagementService.class
);
```
Whether you set the ServiceClient environment globally or individually, separately you'll also need to set the OAuth environment to sandbox.
```java
final OAuthDesktopMobileAuthCodeGrant oAuthDesktopMobileAuthCodeGrant = new OAuthDesktopMobileAuthCodeGrant(
ClientId,
ApiEnvironment.SANDBOX
);
```
Web applications with a client secret and custom redirect URI should use OAuthWebAuthCodeGrant as follows.
```java
OAuthWebAuthCodeGrant oAuthWebAuthCodeGrant = new OAuthWebAuthCodeGrant(
ClientId,
ClientSecret,
new URL(RedirectUri),
ApiEnvironment.SANDBOX
);
```
## See Also
[Bing Ads API Client Libraries](client-libraries.md)
[Bing Ads API Code Examples](code-examples.md)
[Bing Ads API Web Service Addresses](web-service-addresses.md)
[Handling Service Errors and Exceptions](handle-service-errors-exceptions.md)
[Sandbox](sandbox.md)
| 62.783133 | 731 | 0.777778 | eng_Latn | 0.902708 |
5827504c99ea64da1b6ccbf7b74cb82801f94b7a | 1,361 | md | Markdown | data/reusables/rest-reference/activity/starring.md | Tribe665/docs | 38edd9e7d3944700deaf92c3d749fe2ae863647a | [
"CC-BY-4.0",
"MIT"
] | 6 | 2022-03-09T07:09:42.000Z | 2022-03-09T07:14:08.000Z | data/reusables/rest-reference/activity/starring.md | Clam-u/docs | ab4d585e39e5c65c8b86cab5df27884a59dfccec | [
"CC-BY-4.0",
"MIT"
] | 133 | 2021-11-01T18:16:33.000Z | 2022-03-29T18:18:46.000Z | data/reusables/rest-reference/activity/starring.md | petersadek90/docs | deca7a818005dbf367e2013915d1ff3a4116278f | [
"CC-BY-4.0",
"MIT"
] | 2 | 2021-10-05T09:44:04.000Z | 2021-10-05T09:44:52.000Z | ## Starring
Repository starring is a feature that lets users bookmark repositories. Stars are shown next to repositories to show an approximate level of interest. Stars have no effect on notifications or the activity feed.
### Starring vs. Watching
In August 2012, we [changed the way watching
works](https://github.com/blog/1204-notifications-stars) on {% data variables.product.prodname_dotcom %}. Many API
client applications may be using the original "watcher" endpoints for accessing
this data. You can now start using the "star" endpoints instead (described
below). For more information, see the [Watcher API Change post](https://developer.github.com/changes/2012-09-05-watcher-api/) and the "[Repository Watching API](/rest/reference/activity#watching)."
### Custom media types for starring
There is one supported custom media type for the Starring REST API. When you use this custom media type, you will receive a response with the `starred_at` timestamp property that indicates the time the star was created. The response also has a second property that includes the resource that is returned when the custom media type is not included. The property that contains the resource will be either `user` or `repo`.
application/vnd.github.v3.star+json
For more information about media types, see "[Custom media types](/rest/overview/media-types)." | 71.631579 | 420 | 0.789126 | eng_Latn | 0.99822 |
5827a2e6542337a227009b471755b31d868b4960 | 2,675 | md | Markdown | src/docs/about/README.md | kkrasilschikova/shadow | d0cd32fc48c8f54207faa832ff69bb2aac46d3f4 | [
"Apache-2.0"
] | 1 | 2022-03-22T05:55:17.000Z | 2022-03-22T05:55:17.000Z | src/docs/about/README.md | kkrasilschikova/shadow | d0cd32fc48c8f54207faa832ff69bb2aac46d3f4 | [
"Apache-2.0"
] | 5 | 2021-06-28T20:27:01.000Z | 2022-02-26T02:02:44.000Z | src/docs/about/README.md | kkrasilschikova/shadow | d0cd32fc48c8f54207faa832ff69bb2aac46d3f4 | [
"Apache-2.0"
] | null | null | null | # About This Project
I started this project in December of 2012. We were working on converting from a monolithic application into the
new hot jazz of "microservices" using Dropwizard.
I had also just started learning about Gradle and I knew that the incremental build system it provided would benefit
our development team greatly.
Unfortunately, the closest thing that Gradle had to Maven's Shade plugin was its ability to create application TARs and
ZIPs.
So, Charlie Knudsen and myself set out to port the existing Shade code into a Gradle plugin.
This port is what existed up until the `0.9` milestone releases for Shadow.
It functioned, but it wasn't idiomatic Gradle by any means.
Starting with 0.9, Shadow was rewritten from the ground up as standard Gradle plugin and leveraged as much of Gradle's
classes and concepts as possible.
At the same time as the 0.9 release, Gradle was announcing the [Gradle Plugin Portal](https://plugins.gradle.org) and
so Shadow was published there.
## Maintainers
* [John Engelman](https://github.com/johnrengelman)
## Contributors
* [Charlie Knudsen](https://github.com/charliek)
* [Fedor Korotkov](https://github.com/fkorotkov)
* [Haw-Bin Chai](https://github.com/hbchai)
* [Serban Iordache](https://github.com/siordache)
* [Minecrell](https://github.com/Minecrell)
* [Matt Hurne](https://github.com/mhurne)
* [Andres Almiray](https://github.com/aalmiray)
* [Brandon Kearby](https://github.com/brandonkearby)
* [John Szakmeister](https://github.com/jszakmeister)
* [Ethan Hall](https://github.com/ethankhall)
* [Piotr Kubowicz](https://github.com/pkubowicz)
* [Marc Philipp](https://github.com/marcphilipp)
* [Rob Spieldenner](https://github.com/rspieldenner)
* [Marke Vieira](https://github.com/mark-vieira)
* [Ben Adazza](https://github.com/ben-adazza)
* [Tyler Benson](https://github.com/tylerbenson)
* [Scott Newson](https://github.com/sgnewson)
* [Martin Sadowski](https://github.com/ttsiebzehntt)
* [debanne](https://github.com/debanne)
* [Felipe Lima](https://github.com/felipecsl)
* [Paul N. Baker](https://github.com/paul-nelson-baker)
* [Chris Cowan](https://github.com/Macil)
* [Sergey Tselovalnikov](https://github.com/SerCeMan)
* [Osip Fatkullin](https://github.com/osipxd)
* [Victor Tso](https://github.com/roxchkplusony)
* [Petar Petrov](https://github.com/petarov)
* [Mark Vieira](https://github.com/mark-vieira)
* [James Nelson](https://github.com/JamesXNelson)
* [Roberto Perez Alcolea](https://github.com/rpalcolea)
* [Matt King](https://github.com/kyrrigle)
* [Richard Marbach](https://github.com/RichardMarbach)
* [Dennis Schumann](https://github.com/Hillkorn)
* [Brane F. Gračnar](https://github.com/bfg)
| 46.12069 | 119 | 0.753271 | eng_Latn | 0.340265 |
5827a3ff6b370ce421674e1427ee9a3dee7fc40e | 12,356 | md | Markdown | README.md | stephanieerin/quotebot | 4f4359306d38e12dc58ae6c2b7f837349cda6bae | [
"MIT"
] | null | null | null | README.md | stephanieerin/quotebot | 4f4359306d38e12dc58ae6c2b7f837349cda6bae | [
"MIT"
] | null | null | null | README.md | stephanieerin/quotebot | 4f4359306d38e12dc58ae6c2b7f837349cda6bae | [
"MIT"
] | null | null | null | # Twitter bot bootstrap
[](https://greenkeeper.io/)
[](http://standardjs.com/) [](http://opensource.org/licenses/MIT)
<!-- TOC -->
- [Twitter bot bootstrap](#twitter-bot-bootstrap)
- [What you'll need](#what-youll-need)
- [Setup twitter](#setup-twitter)
- [Setup development environment](#setup-development-environment)
- [Set up the bot](#set-up-the-bot)
- [Project structure](#project-structure)
- [Node dependencies](#node-dependencies)
- [Heroku](#heroku)
- [Heroku CLI](#heroku-cli)
- [Heroku variables](#heroku-variables)
- [Heroku deployment via GitHub](#heroku-deployment-via-github)
- [Heroku troubleshooting](#heroku-troubleshooting)
- [Handy tip](#handy-tip)
- [Contributing](#contributing)
- [Links](#links)
- [License](#license)
<!-- /TOC -->
This is a bootstrap for setting up a Twitter bot with Node.js using the `twit` library. The bot will favorite and retweet what you specify when configuring it. It will also reply to followers with a selection of canned responses.
As a primer for this, there is a great post by [@amanhimself](https://twitter.com/amanhimself) on making your own twitter bot. This is an expansion on that with further detail on configuration on Heroku.
Before starting the clock you'll need to set up some accounts if you don't have them already.
## What you'll need
- Twitter account
- Development environment with Node.js and NPM
* c9 account
* Node.js
* NPM
- Heroku account
## Setup twitter
Set up an application on the Twitter account you want to favorite and retweet from via: [https://apps.twitter.com/app/new](https://apps.twitter.com/app/new)
As an example, I'll configure the old [@DroidScott](twitter.com/droidscott) twitter account I have so you can follow along.
Straight forward enough for the twitter application, just make sure you add your phone number to your Twitter account before clicking the **Create your Twitter application** button.
You should now be in the 'Application Management' section where you will need to take note of your keys. You should have your 'Consumer Key (API Key)' and 'Consumer Secret (API Secret)' already available. You'll need to scroll to the bottom of the page and click the **Create my access token** to get the 'Access Token' and 'Access Token Secret' take note of all four of them as you'll need them when setting up the bot.
## Setup development environment
For this I'm just going to say use [Cloud9](https://c9.io/) as you can be up and running in minutes with one of the pre made Node.js environments.
Note that if you choose to use Heroku and/or Cloud9 IDE in building this (like I do in this guide) in some regions you will be prompted to give a credit card number to create these accounts.
## Set up the bot
In the project tree delete the example project files of `client`, `package.json`, `README.md` and `server.js`. You won't need them, but you can leave them there if you desire.
In your new Node.js c9 environment go to the terminal and enter:
```
$ git clone https://github.com/spences10/twitter-bot-bootstrap
```
## Project structure
The environment project tree should look something like this:
## Node dependencies
Before configuring the bot we'll need to install the dependencies, cd into the project folder with `cd tw*` this will move you to `:~/workspace/twitter-bot-bootstrap (master) $ ` from the terminal enter:
```
$ npm install
```
This will install all the dependencies listed in the `package.json` file.
If you get an errors then I suggest installing the dependencies one by one from the `package.json` file with the same command and the package name at the end:
Here is an example of the `dependencies` in the `package,json` file:
```
"dependencies": {
"dotenv": "^4.0.0",
"twit": "^2.2.5",
"unique-random-array": "^1.0.0",
"unirest": "^0.5.1"
}
```
The npm command to install them all:
```
$ npm install --save dotenv twit unique-random-array unirest
```
If you get any `WARN` messages such as `npm WARN package.json [email protected] No repository field` this will not break the bot so it's safe to ignore.
Now you can configure the bot. From the terminal enter:
```
$ npm init
```
This will configure the `package.json` file with your details as desired. Just keep hitting return if you're happy with the defaults.
Now you'll need to add your Twitter keys to the `.env` file. Just input the keys in their corresponding fields and save the file.
If you can not find the `.env` file in the file structure of your c9 project then you will need to enable the **`Show Hidden Files`** option. In the file view select the settings cog then tick the `Show Hidden Files` option if it is not already checked.
The `SENTIMENT_KEY` you can get a new API key at https://market.mashape.com/vivekn/sentiment-3 your key is in the `REQUEST EXAMPLE`
Take a look at the gif, click the link, sign up for or sing into `mashape`, click on `node`in the right hand panel and select out your API key, it will be in the space highlighted `<required>` in the gif.
Add your API key to the `.env` file along with your Twitter API keys :key:
Here you should add your Twitter account name, and how often you want the bot to run the retweet and favorite functions in minutes.
>NOTE none of the `.env` items have quotes `''` round them.
```
CONSUMER_KEY=Fw***********P9
CONSUMER_SECRET=TD************Cq
ACCESS_TOKEN=31**************UC
ACCESS_TOKEN_SECRET=r0************S2
SENTIMENT_KEY=Gj************lF
TWITTER_USERNAME=DroidScott
TWITTER_RETWEET_RATE=5
TWITTER_FAVORITE_RATE=5
```
You can then add some keywords into the `strings.js` file for what you want to search for as well as sub-queries.
*add query and sub-query strings*
*you can also update blocked strings to block more stuff*
When adding sub-query strings make sure you leave a space at the beginning of the string so `' handy tip'` gets concatenated onto `'node.js'` as `node.js handy tip` and not `node.jshandy tip`.
That should be it. Go to the terminal, enter `npm start` and you should get some output:
Check the Twitter account:
## Heroku
Cool, now we have a bot that we can test on our dev environment, but we can't leave it there. We'll need to deploy it to Heroku.
If you haven't done so already, set up a [Heroku account](https://signup.heroku.com) then select **Create a new app** from the dropdown box on the top right of your dashboard. On the next screen, name the app if you want and then click **Create App**.
You'll be presented with your app dashboard and instructions for the deployment method.
Your app name should be displayed on the top of your dashboard. You'll need this when logging in with the Heroku CLI.
## Heroku CLI
We're going to deploy initially via the Heroku Command Line Interface (*CLI*).
On your c9 environment terminal, log into Heroku [it should be installed by default]
```
$ heroku login
```
Enter your credentials.
```
$ cd twitter-bot-bootstrap
$ git init
$ heroku git:remote -a your-heroku-app-name
```
Deploy your application.
```
$ git add .
$ git commit -am 'make it better'
$ git push heroku master
```
You should get build output on the terminal:
Then check the output with:
```
$ heroku logs -t
```
All good? Cool! :sunglasses:
## Heroku variables
Now that we have our bot on Heroku we need to add environment variables to store our Twitter keys. This is because the `.env` file where we stored our keys is listed in the `.gitignore` file, which tells git not to upload that file to Heroku. It also makes it so if in the future we want to add our code to GitHub we don't have to worry about the `.env` file making our keys public, because the file will automatically be ignored.
All you need to do is go to the console of your Heroku app and select the 'Settings' sections and add in your Twitter keys from the `.env` file. Click the 'Reveal Config Vars' button and add in the variables with their corresponding values:
```
CONSUMER_KEY
CONSUMER_SECRET
ACCESS_TOKEN
ACCESS_TOKEN_SECRET
SENTIMENT_KEY
```
Once you have the Heroku vars set up, take a look at the `config.js` file of this project. You are going to delete this line:
```
require('dotenv').config();
```
You're now ready to deploy to Heroku again. Your console commands should look something like this:
```
$ git add .
$ git commit -m 'add environment variables'
$ git push heroku master
```
Then you can check the Heroku logs again with:
```
$ heroku logs -t
```
You should now have a bot you can leave to do its thing forever more, or until you decide you want to change the search criteria :smile:
## Heroku deployment via GitHub
You can also deploy your app by connecting to GitHub and deploy automatically to Heroku each time your master branch is updated on GitHub, this is straight forward enough.
Go to the ‘Deploy’ dashboard on Heroku, select GitHub as the deployment method. If you have connected your GitHub account to your Heroku account then you can search for the repository. If you forked this repo, then you can just enter `twitter-bot-bootstrap` and **Search**. You can then click the **Connect** button and now you can auto deploy from GitHub!
## Heroku troubleshooting
What do you mean it crashed!?
Ok, I found that sometimes the `worker` is set as `web` and it crashes out. Try setting the `worker` again:
```
$ heroku ps:scale worker=0
$ heroku ps:scale worker=1
```
If that still crashes out then try setting the `Resources` on the Heroku dashboard, I found if you toggle between the `web`, `heroku` and `worker` it usually settles down. Basically you need to be set to the **`worker`** Dyno this is what causes the `Error R10 (Boot timeout)` crashes because it's trying to use one of the other resources when it should be using the **`worker`** Dyno.
Other useful Heroku commands I use:
```
$ heroku restart
```
By default you can only push your master branch if you are working on a development branch i.e. `dev` branch. If you want to test on Heroku, then you can use:
```
$ git push heroku dev:master
```
## Handy tip
If you want to add this to your own GitHub repo and don't want to share your API keys :key: with the world then you should turn off tracking on the `.env` file. From the terminal enter this git command:
```
$ git update-index --assume-unchanged .env
```
I have added my most used git command I use in this [gist](https://gist.github.com/spences10/5c492e197e95158809a83650ff97fc3a)
## Contributing
Please fork this repository and contribute back using pull requests.
Any contributions, large or small, major features, bug fixes and integration tests are welcomed and appreciated but will be thoroughly reviewed and discussed.
#### Links
Credit for the inspiration for this should go to [@amanhimself](https://twitter.com/amanhimself) and his posts on creating your own twitter bot.
[create-a-simple-twitter-bot-with-node-js](https://hackernoon.com/create-a-simple-twitter-bot-with-node-js-5b14eb006c08#.flysreo60)
[how-to-make-a-twitter-bot-with-nodejs](https://chatbotslife.com/how-to-make-a-twitter-bot-with-nodejs-d5cb04fdbf97#.h5ah8dq5n)
[twitter-mctwitbot](https://medium.com/@spences10/twitter-mctwitbot-4d15cd005dc0#.dp9q5f427)
[awesome-twitter-bots](https://github.com/amandeepmittal/awesome-twitter-bots)
---
[](https://github.com/feross/standard)
### License
MIT License
Copyright (c) 2017, Scott Spence. All rights reserved.
| 38.018462 | 430 | 0.740369 | eng_Latn | 0.989336 |
5827b392b10ed0cd4af96754522895bdc1891965 | 1,591 | md | Markdown | content/blog/to-react-with-best-practices/index.md | metamn/metamn-react-blog | 496d5db088b88d10803ea36ca46cb942468e6568 | [
"MIT"
] | null | null | null | content/blog/to-react-with-best-practices/index.md | metamn/metamn-react-blog | 496d5db088b88d10803ea36ca46cb942468e6568 | [
"MIT"
] | 12 | 2021-03-01T20:18:52.000Z | 2022-02-26T10:16:29.000Z | content/blog/to-react-with-best-practices/index.md | metamn/metamn-react-blog | 496d5db088b88d10803ea36ca46cb942468e6568 | [
"MIT"
] | null | null | null | ---
title: 'To React with best practices'
date: '2018-12-13'
---
WordPress is here with Gutenberg — it's time to react.
<!--more-->
The last two years I've spent with working on projects far from the edge having no time to catch up with
web design and development best practices — it's time to re-learn them.
I used to feeling comfortable in the wilderness. In 2015 I've created my own [styleguide with Gulp](http://metamn.io/styleguide/). Then I was featured on [Brutalist Websites](http://brutalistwebsites.com/metamn.io_gust/). And I run [another blog](http://metamn.io/beat/) with edge on industry.
I still feel left behind.
My biggest issue is that my old framework built on BEM / SCSS / HTML5 and vanilla Javascript was all good minus the Javascript part. I've struggled to make things move on the screen. Yes, I needed to find something better than Javascript and that's how I first went to Vue, then now to React.
With these frameworks you don't write vanilla JS code. You write strange markup and styling to declare and control the UI with minimum original Javascript. Just plumbing together what the framework offers. That's what I really needed.
With Vue I was enthusiastic. It was the best and fastest way to get connected with the reactive UI world.
After a year, now, I'm on React. I really love it. In a week I've managed to set up [a complete Storybook](http://metamn.io/mr-ui/), create [new components](https://github.com/metamn/new-component) the way I want, and now put together this blog in an afternoon. Thanks, [Gatsby!](https://www.gatsbyjs.org/)
| 66.291667 | 306 | 0.760528 | eng_Latn | 0.996993 |
582809ec50eb0b876a9c49d5a8c90bcbccd186bf | 1,114 | md | Markdown | content/curriculum/guides/1991/3/91.03.08.x.md | kenlu89/teachers_institute | 1fc993f30d6ac17b3097e63510ce758a12c910ea | [
"MIT"
] | null | null | null | content/curriculum/guides/1991/3/91.03.08.x.md | kenlu89/teachers_institute | 1fc993f30d6ac17b3097e63510ce758a12c910ea | [
"MIT"
] | null | null | null | content/curriculum/guides/1991/3/91.03.08.x.md | kenlu89/teachers_institute | 1fc993f30d6ac17b3097e63510ce758a12c910ea | [
"MIT"
] | null | null | null | ---
layout: "unit"
title: "Guide Entry to 91.03.08"
path: "/curriculum/guides/1991/3/91.03.08.x.html"
unitTitle: "Dark Voices from Unmarked Graves"
unitAuthor: "Robert Johnson Moore"
keywords: "Autobiography Afro-Americans Slavery History General Literature Narrative Afro-American"
recommendedFor: "Recommended for American Literature and African-American Literature, grade 11, and Ethno-Literature, grade 10"
---
<body>
<hr/>
<h4>
Guide Entry to 91.03.08:
</h4>
This unit will present to the student various samplings of oral and written testimony about slavery from slaves as they experienced it and from former slaves as they remembered it. The narratives will be read, analyzed and reenacted in the classroom. The narratives will be examined for their content and their style. Common themes and characteristics will be highlighted.
<p>
(Recommended for American Literature and African-American Literature, grade 11, and Ethno-Literature, grade 10)
</p>
<p>
<b>
<i>
Key Words
</i>
</b>
<br/>
</p>
<p>
<i>
Autobiography Afro-Americans Slavery History General Literature Narrative Afro-American
</i>
</p>
</body> | 34.8125 | 372 | 0.771095 | eng_Latn | 0.963601 |
582864332a51a6091c77df492e7e976b9ce36e04 | 447 | md | Markdown | src/libraries/System.Linq.Expressions/README.md | abock/runtime | b3346807be96f6089fc1538946b3611f607389e2 | [
"MIT"
] | 11 | 2021-10-21T07:56:23.000Z | 2022-03-31T15:08:10.000Z | src/libraries/System.Linq.Expressions/README.md | abock/runtime | b3346807be96f6089fc1538946b3611f607389e2 | [
"MIT"
] | 2 | 2020-06-06T09:07:48.000Z | 2020-06-06T09:13:07.000Z | src/libraries/System.Linq.Expressions/README.md | abock/runtime | b3346807be96f6089fc1538946b3611f607389e2 | [
"MIT"
] | 3 | 2021-02-10T16:20:05.000Z | 2021-03-12T07:55:36.000Z | # System.Linq.Expressions library
We are not accepting feature contributions to System.Linq.Expressions.
The library is effectively archived.
The library and supporting language features are mature and no longer evolving, and the risk of code change likely exceeds the benefit.
We will consider changes that address significant bugs or regressions, or changes that are necessary to continue shipping the binaries.
Other changes will be rejected. | 55.875 | 135 | 0.829978 | eng_Latn | 0.99935 |
5828695117614ab15a2d4821d7d362f758127eb3 | 1,056 | md | Markdown | sites/intellij-guide/contents/tips/generate-code/index.md | JetBrains/pycharm_guide | 335c6758441a08f761f05a4b427887efd6b6927b | [
"Apache-2.0"
] | 16 | 2019-02-01T14:03:53.000Z | 2019-08-18T13:57:33.000Z | sites/intellij-guide/contents/tips/generate-code/index.md | JetBrains/pycharm_guide | 335c6758441a08f761f05a4b427887efd6b6927b | [
"Apache-2.0"
] | 3 | 2019-03-22T07:40:33.000Z | 2019-04-03T16:04:35.000Z | sites/intellij-guide/contents/tips/generate-code/index.md | JetBrains/pycharm_guide | 335c6758441a08f761f05a4b427887efd6b6927b | [
"Apache-2.0"
] | 2 | 2019-03-25T15:00:12.000Z | 2019-08-18T13:57:36.000Z | ---
date: 2021-01-08
title: Generate Code
technologies: [java]
topics: [refactoring]
author: hs
subtitle: Helps you to generate commonly used code constructs
thumbnail: ./thumbnail.png
cardThumbnail: ./card.png
shortVideo:
poster: ./tip.png
url: https://youtu.be/foKr1a9r250
seealso:
- title: (video) CodeGeneration in IntelliJ IDEA
href: https://www.youtube.com/watch?v=btqCYUc3nFE
- title: "(video) Helen's Take On: Generating Code in IntelliJ IDEA"
href: https://www.youtube.com/watch?v=vF_18ZsM1lE
- title: (video) Write Code Faster Using Live Templates with IntelliJ IDEA
href: https://www.youtube.com/watch?v=ffBeoE6NBSs
- title: (documentation) IntelliJ IDEA Help - Generate code
href: https://www.jetbrains.com/help/idea/generating-code.html
leadin: |
You can generate new code quickly with **⌘N** (macOS), or **Alt+Insert** (Windows/Linux). For example, you can generate commonly used methods for Java beans in this way.
You can use the same shortcut to add a new parameter in the Change Signature dialog.
---
| 39.111111 | 172 | 0.735795 | eng_Latn | 0.598477 |
5828f29a673e994c0af810fa66f9810ba066f426 | 2,223 | md | Markdown | docs/2014/sql-server/install/cluster-node-configuration-complete.md | Sticcia/sql-docs.it-it | 31c0db26a4a5b25b7c9f60d4ef0a9c59890f721e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/2014/sql-server/install/cluster-node-configuration-complete.md | Sticcia/sql-docs.it-it | 31c0db26a4a5b25b7c9f60d4ef0a9c59890f721e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/2014/sql-server/install/cluster-node-configuration-complete.md | Sticcia/sql-docs.it-it | 31c0db26a4a5b25b7c9f60d4ef0a9c59890f721e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: La configurazione di nodo (completo) del cluster | Microsoft Docs
ms.custom: ''
ms.date: 06/13/2017
ms.prod: sql-server-2014
ms.reviewer: ''
ms.technology:
- database-engine
ms.topic: conceptual
ms.assetid: 64174d54-edee-49b8-9b43-039574bf2ca1
author: mashamsft
ms.author: mathoma
manager: craigg
ms.openlocfilehash: cb472e106438aee781bf54fd6216d2ed32f7f190
ms.sourcegitcommit: f7fced330b64d6616aeb8766747295807c92dd41
ms.translationtype: MT
ms.contentlocale: it-IT
ms.lasthandoff: 04/23/2019
ms.locfileid: "63190716"
---
# <a name="cluster-node-configuration-complete"></a>Configurazione nodi cluster (completa)
Utilizzare la pagina Configurazione nodi cluster (completa) per specificare un'istanza esistente di [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] che è stato preparato per clustering. Per installare o aggiornare un cluster di failover di [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], è necessario eseguire il programma di installazione su ogni nodo del cluster di failover. Per aggiungere un nodo a un cluster di failover di [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] esistente, è necessario eseguire il programma di installazione di [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] nel nodo che deve essere aggiunto all'istanza del cluster di failover di [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] .
## <a name="options"></a>Opzioni
Dalle caselle a discesa:
- [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Nome istanza - consente di selezionare il nome dell'istanza per il [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] cluster di failover.
- Nome del nodo: questo campo viene prepopolato con il nome del computer in cui il [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] programma di installazione è in esecuzione.
- [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Nome di rete del Cluster di failover, questo campo non è già popolato. Specificare il nome di rete della nuova istanza del cluster di failover di [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] . Si tratta del nome che identifica l'istanza del cluster di failover nella rete.
| 65.382353 | 768 | 0.763833 | ita_Latn | 0.964924 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.