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
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
5880e0ebe6a7260e6e0ac3b5c9318bdcfd47d1e0 | 99 | md | Markdown | src/pages/projects/modern-bathroom.md | designspin/tenacity-interiors | 2b17b3ad8fa16b59e84b532c03a0b8f665c3d45e | [
"MIT"
] | 1 | 2020-07-28T10:51:12.000Z | 2020-07-28T10:51:12.000Z | src/pages/projects/modern-bathroom.md | designspin/tenacity-interiors | 2b17b3ad8fa16b59e84b532c03a0b8f665c3d45e | [
"MIT"
] | null | null | null | src/pages/projects/modern-bathroom.md | designspin/tenacity-interiors | 2b17b3ad8fa16b59e84b532c03a0b8f665c3d45e | [
"MIT"
] | null | null | null | ---
key: projects
title: Modern Bathroom.
image: /img/gay-038-copy.jpg
category: vanity-units
---
| 12.375 | 28 | 0.707071 | eng_Latn | 0.264651 |
5881885eeaf8bad96ba126995ad1ba6fc6246577 | 4,847 | md | Markdown | docs/doxygen/Classes/classsam_1_1_optional_dropping.md | amirmasoudabdol/Bilbo | b6a20725116a76c16173f17c6ca3615a38c3fdba | [
"Apache-2.0"
] | null | null | null | docs/doxygen/Classes/classsam_1_1_optional_dropping.md | amirmasoudabdol/Bilbo | b6a20725116a76c16173f17c6ca3615a38c3fdba | [
"Apache-2.0"
] | null | null | null | docs/doxygen/Classes/classsam_1_1_optional_dropping.md | amirmasoudabdol/Bilbo | b6a20725116a76c16173f17c6ca3615a38c3fdba | [
"Apache-2.0"
] | null | null | null | ---
title: sam::OptionalDropping
---
# sam::OptionalDropping
**Module:** **[Hacking Strategies](/doxygen/Modules/group___hacking_strategies/)**
[More...](#detailed-description)
`#include <HackingStrategy.h>`
Inherits from [sam::HackingStrategy](/doxygen/Classes/classsam_1_1_hacking_strategy/)
## Public Classes
| | Name |
| -------------- | -------------- |
| struct | **[Parameters](/doxygen/Classes/structsam_1_1_optional_dropping_1_1_parameters/)** |
## Public Functions
| | Name |
| -------------- | -------------- |
| | **[OptionalDropping](/doxygen/Classes/classsam_1_1_optional_dropping/#function-optionaldropping)**() =default |
| | **[OptionalDropping](/doxygen/Classes/classsam_1_1_optional_dropping/#function-optionaldropping)**(const [Parameters](/doxygen/Classes/structsam_1_1_optional_dropping_1_1_parameters/) & p) |
| virtual void | **[perform](/doxygen/Classes/classsam_1_1_optional_dropping/#function-perform)**([Experiment](/doxygen/Classes/classsam_1_1_experiment/) * experiment) override<br>Applies the hacking method on the [Experiment](/doxygen/Classes/classsam_1_1_experiment/). |
## Public Attributes
| | Name |
| -------------- | -------------- |
| [Parameters](/doxygen/Classes/structsam_1_1_optional_dropping_1_1_parameters/) | **[params](/doxygen/Classes/classsam_1_1_optional_dropping/#variable-params)** |
| [PolicyChain](/doxygen/Classes/structsam_1_1_policy_chain/) | **[stopping_condition](/doxygen/Classes/classsam_1_1_optional_dropping/#variable-stopping_condition)** |
## Additional inherited members
**Public Functions inherited from [sam::HackingStrategy](/doxygen/Classes/classsam_1_1_hacking_strategy/)**
| | Name |
| -------------- | -------------- |
| virtual | **[~HackingStrategy](/doxygen/Classes/classsam_1_1_hacking_strategy/#function-~hackingstrategy)**() =0<br>Pure destructor of the Base class. This is important for proper deconstruction of Derived classes. |
| | **[HackingStrategy](/doxygen/Classes/classsam_1_1_hacking_strategy/#function-hackingstrategy)**() |
| void | **[operator()](/doxygen/Classes/classsam_1_1_hacking_strategy/#function-operator())**([Experiment](/doxygen/Classes/classsam_1_1_experiment/) * experiment) |
| float | **[defensibility](/doxygen/Classes/classsam_1_1_hacking_strategy/#function-defensibility)**() const |
| float | **[prevalence](/doxygen/Classes/classsam_1_1_hacking_strategy/#function-prevalence)**() const |
| HackingStage | **[stage](/doxygen/Classes/classsam_1_1_hacking_strategy/#function-stage)**() const |
| HackingTarget | **[target](/doxygen/Classes/classsam_1_1_hacking_strategy/#function-target)**() const |
| std::unique_ptr< [HackingStrategy](/doxygen/Classes/classsam_1_1_hacking_strategy/) > | **[build](/doxygen/Classes/classsam_1_1_hacking_strategy/#function-build)**(json & hacking_strategy_config)<br>Factory method for building a [HackingStrategy](/doxygen/Classes/classsam_1_1_hacking_strategy/). |
**Public Attributes inherited from [sam::HackingStrategy](/doxygen/Classes/classsam_1_1_hacking_strategy/)**
| | Name |
| -------------- | -------------- |
| sol::state | **[lua](/doxygen/Classes/classsam_1_1_hacking_strategy/#variable-lua)** |
| std::optional< float > | **[defensibility_](/doxygen/Classes/classsam_1_1_hacking_strategy/#variable-defensibility_)** |
| std::optional< float > | **[prevalence_](/doxygen/Classes/classsam_1_1_hacking_strategy/#variable-prevalence_)** |
| HackingStage | **[stage_](/doxygen/Classes/classsam_1_1_hacking_strategy/#variable-stage_)** |
| HackingTarget | **[target_](/doxygen/Classes/classsam_1_1_hacking_strategy/#variable-target_)** |
## Detailed Description
```cpp
class sam::OptionalDropping;
```
Optional Dropping Hacking Strategy
The _Optional Dropping_ algorithm uses the covariant values to split the dataset, and generates new condition groups.
## Public Functions Documentation
### function OptionalDropping
```cpp
OptionalDropping() =default
```
### function OptionalDropping
```cpp
inline explicit OptionalDropping(
const Parameters & p
)
```
### function perform
```cpp
virtual void perform(
Experiment * experiment
) override
```
Applies the hacking method on the [Experiment](/doxygen/Classes/classsam_1_1_experiment/).
**Parameters**:
* **experiment** A pointer to an [Experiment](/doxygen/Classes/classsam_1_1_experiment/).
**Reimplements**: [sam::HackingStrategy::perform](/doxygen/Classes/classsam_1_1_hacking_strategy/#function-perform)
## Public Attributes Documentation
### variable params
```cpp
Parameters params;
```
### variable stopping_condition
```cpp
PolicyChain stopping_condition;
```
-------------------------------
Updated on 29 June 2021 at 16:13:47 CEST | 37 | 301 | 0.713637 | eng_Latn | 0.302458 |
5882a1ab431ae390773e4d22a1b77692e5641ef6 | 3,079 | md | Markdown | packages/sagittarius-range/README.md | Gherciu/sagittarius | 996328811438beaf3bacb0a601bf399ec6f9d815 | [
"MIT"
] | 51 | 2019-09-13T19:26:55.000Z | 2021-07-09T00:31:37.000Z | packages/sagittarius-range/README.md | Gherciu/sagittarius | 996328811438beaf3bacb0a601bf399ec6f9d815 | [
"MIT"
] | 5 | 2019-09-05T18:34:34.000Z | 2020-09-07T12:46:49.000Z | packages/sagittarius-range/README.md | Gherciu/sagittarius | 996328811438beaf3bacb0a601bf399ec6f9d815 | [
"MIT"
] | 1 | 2019-09-19T02:35:06.000Z | 2019-09-19T02:35:06.000Z | <div align="center">
<img width="200" height="200"
src="https://raw.githubusercontent.com/Gherciu/sagittarius/master/logo.png">
<h1>sagittarius-range</h1>
<p>Creates an array of numbers (positive and/or negative) progressing from start up to, but not including, end. A step of -1 is used if a negative start is specified without an end or step. If end is not specified, it's set to start with start then set to 0. Part of <a href="https://github.com/Gherciu/sagittarius">sagittarius</a> a set of javascript most used utils.</p>
<p>
<a href="https://gherciu.github.io/sagittarius/">Site</a>
| <a href="https://gherciu.github.io/sagittarius/docs/doc-introduction">Getting Started</a>
| <a href="https://gherciu.github.io/sagittarius/docs/doc-api-introduction">API</a>
| <a href="https://gherciu.github.io/sagittarius/blog/">Blog</a>
</p>
</div>
[](https://github.com/Gherciu/sagittarius/blob/master/LICENSE)
[](https://github.com/Gherciu/multipack)
## Getting started.
- It can be used directly from `sagittarius-core` package or installed separately via npm runing: `npm i sagittarius-range`
```js
const range = require('sagittarius-range')
console.log(range(4)) // [0, 1, 2, 3]
console.log(range(-4)) // [0, -1, -2, -3]
console.log(range(1, 5)) // [1, 2, 3, 4]
console.log(range(0, 20, 5)) // [0, 5, 10, 15]
console.log(range(0, -4, -1)) // [0, -1, -2, -3]
console.log(range(1, 4, 0)) // [1, 1, 1]
console.log(range(0)) // []
```
Or use via cdn:
```html
<!--index.html-->
<script src="https://cdn.jsdelivr.net/npm/sagittarius-range@latest/build/index.js"></script>
<script>
console.log(sagittariusRange(4)) // [0, 1, 2, 3]
console.log(sagittariusRange(-4)) // [0, -1, -2, -3]
console.log(sagittariusRange(1, 5)) // [1, 2, 3, 4]
console.log(sagittariusRange(0, 20, 5)) // [0, 5, 10, 15]
console.log(sagittariusRange(0, -4, -1)) // [0, -1, -2, -3]
console.log(sagittariusRange(1, 4, 0)) // [1, 1, 1]
console.log(sagittariusRange(0)) // []
</script>
```
## Contributing
1. Fork it!
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -am 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D
#### Or you can sponsor via [Open Collective](https://opencollective.com/gherciu-gheorghe/)
[](https://opencollective.com/gherciu-gheorghe/)
## Author
**[@Gherciu/sagittarius](https://github.com/Gherciu/sagittarius)** © [GHERCIU](https://github.com/Gherciu), Released under the [MIT](https://github.com/Gherciu/sagittarius/blob/master/LICENSE) License.<br>
Authored and maintained by GHERCIU with help from contributors ([list](https://github.com/Gherciu/sagittarius/contributors)).
#### If you like this repository star⭐ and watch👀 on [GitHub](https://github.com/Gherciu/sagittarius)
| 46.651515 | 374 | 0.694706 | eng_Latn | 0.225692 |
5882d8a531ae0c84ea8e6fb724a21ad6c8f3d6f7 | 471 | md | Markdown | docs/framework/wcf/diagnostics/etw/3555-createworkflowservicehoststart.md | michha/docs | 08f75b6ed8a9e6634235db708a21da4be57dc58f | [
"CC-BY-4.0",
"MIT"
] | 2 | 2021-04-08T08:02:39.000Z | 2021-04-11T08:27:32.000Z | docs/framework/wcf/diagnostics/etw/3555-createworkflowservicehoststart.md | michha/docs | 08f75b6ed8a9e6634235db708a21da4be57dc58f | [
"CC-BY-4.0",
"MIT"
] | 548 | 2018-04-25T17:43:35.000Z | 2022-03-09T02:06:35.000Z | docs/framework/wcf/diagnostics/etw/3555-createworkflowservicehoststart.md | michha/docs | 08f75b6ed8a9e6634235db708a21da4be57dc58f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "3555 - CreateWorkflowServiceHostStart"
ms.date: "03/30/2017"
ms.assetid: 14038438-774f-4651-b83e-c149da688a1b
---
# 3555 - CreateWorkflowServiceHostStart
## Properties
|||
|-|-|
|ID|3555|
|Keywords|WebHost|
|Level|Information|
|Channel|Microsoft-Windows-Application Server-Applications/Debug|
## Description
This event is emitted on CreateWorkflowServiceHost start.
## Message
CreateWorkflowServiceHost start
## Details
| 18.115385 | 67 | 0.715499 | yue_Hant | 0.75624 |
5883ad19d703ee55a8dcc6038df90f74ced11b71 | 2,873 | md | Markdown | README.md | kemotep/Windows | 05292d2df8ee9e01cf05d5943686972e59378728 | [
"Apache-2.0"
] | 2 | 2019-04-30T03:05:59.000Z | 2020-10-22T19:24:57.000Z | README.md | kemotep/Windows | 05292d2df8ee9e01cf05d5943686972e59378728 | [
"Apache-2.0"
] | null | null | null | README.md | kemotep/Windows | 05292d2df8ee9e01cf05d5943686972e59378728 | [
"Apache-2.0"
] | 1 | 2021-03-27T07:47:17.000Z | 2021-03-27T07:47:17.000Z | # Windows Scripts Repository
This is a GitHub repository of my various Windows Scripts (PowerShell and Batch Files). I plan on including some text resources, links, and other best practices I find for administering Windows.
## Table of Contents
* [Getting Started](https://github.com/kemotep/Windows#getting-started)
* [Notes](https://github.com/kemotep/Windows#Notes)
* [Exchange Management](https://github.com/kemotep/Windows#exchange-management)
* [Links](https://github.com/kemotep/Windows#links)
* [License](LICENSE.md)
* [Batch Files](https://github.com/kemotep/Windows/tree/master/BatchFiles)
* [PowerShell](https://github.com/kemotep/Windows/tree/master/PowerShell)
## Getting Started
Here is where I will place instructions on how to use this repository. Eventually there will be instructions an explanations for each script, as well as a table of contents.
You should be using script signing when you use PowerShell scripts. Allowing unsigned PowerShell scripts is a security risk. `RemoteSigned` is a recommended Execution policy. Read the Official documentation [here](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_execution_policies?view=powershell-5.1)
## Notes
I will also be including my own notes for Windows Management in this repository. I will also include links to resources, guides, documentation, and communities.
### [Exchange Management](https://github.com/kemotep/Windows/blob/master/Notes/Exchange%20Management.md)
This is a list of all the Exchange Online commands that I know and example outputs. Very useful for managing Exchange. This list is not comprehensive. I plan to create a script/module that can run all of this from one window.
### [Links](https://github.com/kemotep/Windows/blob/master/Notes/Links.md)
Here will be links to resources and communities that I use.
## Built With
[Notepad++](https://notepad-plus-plus.org/)
[git for Windows](https://gitforwindows.org/)
## Versioning
I plan to use [SemVer](http://semver.org/) for versioning.
## Author
* **kemotep** - [kemotep](https://github.com/kemotep)
## License
This project is licensed under the Apache 2.0 License - see the [LICENSE](LICENSE) file for details of the license and the [NOTICE](NOTICE) for the copyright notice.
I have chosen to use the Apache 2.0 License because that is what is recommended by the [Free Software Foundation](https://www.gnu.org/licenses/license-recommendations.html) for small programs and projects.
I want to use an appropriate free and open source license so that anyone is able to use my scripts and programs freely. I believe in the free exchange of information and software to the benefit for all.
## Acknowledgments
* My loving and supportive Fiance
* Stack Exchange
* DuckDuckgo Bang Searches | 46.33871 | 343 | 0.757396 | eng_Latn | 0.968466 |
5883ecef8c8f5d7dd70473e19dbc32e9723ccc0c | 603 | md | Markdown | docs/framework/wcf/diagnostics/performance-counters/transacted-operations-committed.md | mtorreao/docs.pt-br | e080cd3335f777fcb1349fb28bf527e379c81e17 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wcf/diagnostics/performance-counters/transacted-operations-committed.md | mtorreao/docs.pt-br | e080cd3335f777fcb1349fb28bf527e379c81e17 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wcf/diagnostics/performance-counters/transacted-operations-committed.md | mtorreao/docs.pt-br | e080cd3335f777fcb1349fb28bf527e379c81e17 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Operações Transacionadas Confirmadas
ms.date: 03/30/2017
ms.assetid: 6a1768cd-d103-4cd3-a26c-b014465f9236
ms.openlocfilehash: 385dfaf07218d3c34332783ad1e82084fe5dfaa7
ms.sourcegitcommit: bc293b14af795e0e999e3304dd40c0222cf2ffe4
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 11/26/2020
ms.locfileid: "96263991"
---
# <a name="transacted-operations-committed"></a>Operações Transacionadas Confirmadas
Nome do contador: operações transacionadas confirmadas.
## <a name="description"></a>Descrição
Número de operações transacionais que foram confirmadas neste serviço.
| 31.736842 | 84 | 0.812604 | por_Latn | 0.788949 |
5884d268fb255253b0759751ac668c3ec2a38abf | 64 | md | Markdown | README.md | BeansBeefBroccoli/Resources-Tools-and-Machines | 1530958dc6a9c5c6a6fdec6ae1eb022c84b60165 | [
"MIT"
] | 1 | 2022-03-01T00:12:19.000Z | 2022-03-01T00:12:19.000Z | README.md | BeansBeefBroccoli/Resources-Tools-and-Machines | 1530958dc6a9c5c6a6fdec6ae1eb022c84b60165 | [
"MIT"
] | null | null | null | README.md | BeansBeefBroccoli/Resources-Tools-and-Machines | 1530958dc6a9c5c6a6fdec6ae1eb022c84b60165 | [
"MIT"
] | null | null | null | # Resources-Tools-and-Machines
The RTM Minecraft mod for Fabric
| 21.333333 | 32 | 0.8125 | yue_Hant | 0.547746 |
58850b98723f1c942dc578fa790b5833d7b0ef8b | 254 | md | Markdown | README.md | youngerous/linear-algebra | 0531c871a6ee94e5f7cf189148f9dba8eaa80fc8 | [
"MIT"
] | 1 | 2019-10-29T14:24:26.000Z | 2019-10-29T14:24:26.000Z | README.md | youngerous/linear-algebra | 0531c871a6ee94e5f7cf189148f9dba8eaa80fc8 | [
"MIT"
] | null | null | null | README.md | youngerous/linear-algebra | 0531c871a6ee94e5f7cf189148f9dba8eaa80fc8 | [
"MIT"
] | 3 | 2020-03-27T04:41:10.000Z | 2020-07-04T13:40:32.000Z | ## linear-algebra
|회차|내용|
|--|--|
|1|~~행렬과 행렬식~~|
|2|~~물리적 벡터~~|
|3|~~수학적 벡터(벡터공간)~~|
|4|~~선형사상~~|
|5|~~고윳값과 대각화~~|
|6|~~복소벡터공간~~|
|7|~~최적화 문제~~|
|8|~~자료의 처리~~|
> [lecture link](https://www.youtube.com/playlist?list=PL127T2Zu76FuVMq1UQnZv9SG-GFIdZfLg)
| 16.933333 | 90 | 0.574803 | kor_Hang | 0.642514 |
5885c2a189909550cb83d6c1a0dff491406e24d2 | 1,170 | md | Markdown | _posts/2017-02-26-leetcode-valid-number.md | Shanshan-IC/Shanshan-IC.github.io | ebb926806c13ccb3d7944251106c1f76ad43b489 | [
"MIT"
] | null | null | null | _posts/2017-02-26-leetcode-valid-number.md | Shanshan-IC/Shanshan-IC.github.io | ebb926806c13ccb3d7944251106c1f76ad43b489 | [
"MIT"
] | null | null | null | _posts/2017-02-26-leetcode-valid-number.md | Shanshan-IC/Shanshan-IC.github.io | ebb926806c13ccb3d7944251106c1f76ad43b489 | [
"MIT"
] | null | null | null | ---
layout: post
title: "Leetcode (65) Valid Number"
category: Leetcode
tags: Leetcode
---
* content
{:toc}
## Leetcode 65. Valid Number
* [Leetcode 65. Valid Number](https://leetcode.com/problems/valid-number/#/description)
Validate if a given string is numeric.
Some examples:
> "0" => true
>
> " 0.1 " => true
>
> "abc" => false
>
> "1 a" => false
>
> "2e10" => true
Note: It is intended for the problem statement to be ambiguous. You should gather all requirements up front before implementing one.
```cpp
class Solution {
public:
bool isNumber(string s) {
int i = 0, k = 0;
while (s[i]==' ') i++;
if (s[i]=='+' || s[i]=='-') i++;
while (isdigit(s[i])) {
i++;
k++;
}
if (s[i]=='.') i++;
while (isdigit(s[i])) {
i++;
k++;
}
if (k==0) return false;
if (s[i]=='e') {
i++, k = 0;
if(s[i]=='+' || s[i] == '-') i++;
while(isdigit(s[i])) i++, k++;
if(k == 0) return false;
}
while(s[i] == ' ') i++;
return i == s.size();
}
};
``` | 20.526316 | 132 | 0.452137 | eng_Latn | 0.726259 |
588611486c13cc9355104cb5dc5a82d967a14b9c | 2,246 | md | Markdown | _posts/2015-09-08-medindo-o-metro.md | marcosramon/site_marcosramon | 2f82738c241b1fc795231f704a734b74f230f629 | [
"MIT"
] | null | null | null | _posts/2015-09-08-medindo-o-metro.md | marcosramon/site_marcosramon | 2f82738c241b1fc795231f704a734b74f230f629 | [
"MIT"
] | null | null | null | _posts/2015-09-08-medindo-o-metro.md | marcosramon/site_marcosramon | 2f82738c241b1fc795231f704a734b74f230f629 | [
"MIT"
] | null | null | null | ---
title: "Medindo o metrô"
excerpt: "Eu gosto de especular sobre coisas que não posso compreender."
date: 2015-09-08
published: true
tags:
- cotidiano
categories:
- blog
---
Eu gosto de especular sobre coisas que não posso compreender.
Ontem, voltando pra casa, vi um cara entrando no metrô com uma trena. Bastou a porta fechar e ele começou a medir a porta do vagão. O metrô estava cheio e ele estava bem do meu lado. Talvez pela proximidade daquele fato inusitado, fiquei intrigado com aquilo. O cara mediu uma extensão da porta, depois outra, de cima pra baixo, de um lado pro outro. Quando o metrô parava em alguma estação e abria a porta ele saia um pouquinho e media a parte interna da porta (a grossura do metrô, não se dá pra entender assim). Vendo aquilo eu fiquei especulando sobre quem era aquele cara e porque ele estava fazendo aquilo.
De repente ele era um funcionário do metrô e estava lá pra verificar algum problema na porta. Mas não, ele não estava vestido como um funcionário do metrô. Parecia um cara comum, com uma aparência comum, sendo estranho em público.
Ou então podia ser isso: ele estava fazendo um trabalho técnico de algum curso, e ele tinha que medir a porta do metrô pra uma pesquisa. Mas não, não tem pesquisa assim (eu imagino). Além disso, o cara não anotava nada, só media e media.
Ou pior: ele estava planejando um assalto ou atentado ou algo maligno assim... E bem quando eu estava nesse ponto da minha alucinação, percebi que o cara tinha parado de medir a porta do metrô e estava olhando direto pra mim.
Senti um frio na espinha, típico de que está fazendo o que não devia. Então percebi que ele ia me falar alguma coisa. *"Eu só gosto de medir"*, ele disse, com voz calma e paciente, como se tivesse percebido a minha curiosidade.
Na verdade, a explicação dele foi desestimulante, justamente porque me tirou do meu processo de imaginação/invenção. Mas eu não disse nada. Apenas dei um sorrisinho condescendente e tratei de não olhar mais pra ele. Durante o resto da viagem (faltavam duas estações ainda antes de eu descer) ficamos cada um na sua. Ele, contente, medindo a porta do metrô; e eu, entediado, sem poder especular sobre aquilo que não era pra ter resposta.
| 93.583333 | 613 | 0.772039 | por_Latn | 1.000007 |
588621af69658453a9a9d6fc5b7ea273a46b0734 | 441 | md | Markdown | content/theme/gatsby-advanced-starter.md | mikeritter/jamstackthemes | 17da3896b8502db3011dca73fd539b381017ab1c | [
"MIT"
] | 289 | 2019-09-18T15:18:18.000Z | 2021-01-29T02:54:36.000Z | content/theme/gatsby-advanced-starter.md | mikeritter/jamstackthemes | 17da3896b8502db3011dca73fd539b381017ab1c | [
"MIT"
] | 80 | 2019-09-25T10:44:26.000Z | 2021-01-29T01:19:40.000Z | content/theme/gatsby-advanced-starter.md | mikeritter/jamstackthemes | 17da3896b8502db3011dca73fd539b381017ab1c | [
"MIT"
] | 210 | 2019-09-25T08:31:51.000Z | 2021-01-29T10:53:38.000Z | ---
title: Gatsby Advanced Starter
github: https://github.com/Vagr9K/gatsby-advanced-starter
demo: https://vagr9k.github.io/gatsby-advanced-starter/
author: Ruben Harutyunyan
ssg:
- Gatsby
cms:
- No Cms
archetype:
- Blog
date: 2017-07-18T20:18:32.000Z
description: >-
A high performance skeleton starter for GatsbyJS that focuses on SEO/Social
features/development environment.
stale: false
disabled_reason: demo url not found
---
| 23.210526 | 77 | 0.764172 | eng_Latn | 0.358492 |
5886c4e8b128099fe702e6074409df844814ffb2 | 1,250 | md | Markdown | README.md | andreas-weber/terraform-provider-improvmx | bc5a49abf0490fd1d977612a11ce5b74e5a201e6 | [
"MIT"
] | 3 | 2021-06-27T15:09:46.000Z | 2021-10-16T14:45:42.000Z | README.md | andreas-weber/terraform-provider-improvmx | bc5a49abf0490fd1d977612a11ce5b74e5a201e6 | [
"MIT"
] | 4 | 2021-06-21T21:06:45.000Z | 2021-10-17T20:00:27.000Z | README.md | issyl0/terraform-provider-improvmx | 41588726468f3aff6ce9018bce773e4d1b4e9225 | [
"MIT"
] | null | null | null | # terraform-provider-improvmx
A very nascent Terraform provider for configuring [ImprovMX](https://improvmx.com) email forwards. Uses my [ImprovMX Golang API client](https://github.com/issyl0/go-improvmx). Download from the [Terraform Registry](https://registry.terraform.io/providers/issyl0/improvmx/latest).
## Features
- Create a domain (ImprovMX creates a wildcard forward for a domain by default).
- Update a domain (to add/remove whitelabel (Enterprise plans only) and notification email settings).
- Delete a domain.
- Import a domain.
- Create an email forward.
- Delete an email forward.
- Import an email forward.
- Update an email forward (ImprovMX allows updating an email forward to send to more than one address, ie `[email protected],[email protected]`).
- Create, update and delete a domain's SMTP credentials.
## Usage
```hcl
terraform {
required_providers {
improvmx = {
source = "issyl0/improvmx"
}
}
}
provider "improvmx" {
// Set the `IMPROVMX_API_TOKEN` environment variable.
}
resource "improvmx_domain" "example" {
domain = "example.com"
}
resource "improvmx_email_forward" "hello" {
domain = "example.com"
alias_name = "hello"
destination_email = "[email protected]"
}
```
| 29.761905 | 279 | 0.7272 | eng_Latn | 0.713011 |
588704fb34645896f77aa03ff6c75e730c6c81c9 | 2,030 | md | Markdown | docs/install/metadata-ingestion/airflow.md | jbuoncri1/OpenMetadata | df1c197e1f2b3016402ca5d32ea8bf7a3f626352 | [
"Apache-2.0"
] | null | null | null | docs/install/metadata-ingestion/airflow.md | jbuoncri1/OpenMetadata | df1c197e1f2b3016402ca5d32ea8bf7a3f626352 | [
"Apache-2.0"
] | null | null | null | docs/install/metadata-ingestion/airflow.md | jbuoncri1/OpenMetadata | df1c197e1f2b3016402ca5d32ea8bf7a3f626352 | [
"Apache-2.0"
] | null | null | null | # Airflow
We highly recommend using Airflow or similar schedulers to run Metadata Connectors. Below is the sample code example you can refer to integrate with Airflow
## Airflow Example for Hive
```python
from datetime import timedelta
from airflow import DAG
try:
from airflow.operators.python import PythonOperator
except ModuleNotFoundError:
from airflow.operators.python_operator import PythonOperator
from metadata.config.common import load_config_file
from metadata.ingestion.api.workflow import Workflow
default_args = {
"owner": "user_name",
"email": ["[email protected]"],
"email_on_failure": True,
"retries": 3,
"retry_delay": timedelta(minutes=5),
"execution_timeout": timedelta(minutes=60),
}
def metadata_ingestion_workflow():
config = load_config_file("examples/workflows/hive.json")
workflow = Workflow.create(config)
workflow.run()
workflow.raise_from_status()
workflow.print_status()
workflow.stop()
with DAG(
"hive_metadata_ingestion_workflow"
default_args=default_args,
description="An example DAG which runs a OpenMetadata ingestion workflow",
schedule_interval=timedelta(days=1),
start_date=days_ago(30),
catchup=False,
) as dag:
ingest_task = PythonOperator(
task_id="ingest_using_recipe",
python_callable=metadata_ingestion_workflow(),
)
```
we are using a python method like below
```python
def metadata_ingestion_workflow():
config = load_config_file("examples/workflows/hive.json")
workflow = Workflow.create(config)
workflow.run()
workflow.raise_from_status()
workflow.print_status()
workflow.stop()
```
Create a Workflow instance and pass a hive configuration which will read metadata from Hive and ingest it into the OpenMetadata Server. You can customize this configuration or add different connectors please refer to our [examples](https://github.com/open-metadata/OpenMetadata/tree/main/ingestion/examples/workflows) and refer to [Connectors](connectors/).
| 30.757576 | 357 | 0.755665 | eng_Latn | 0.926713 |
58879fa07364187b59f9c56b237111d297570387 | 2,121 | md | Markdown | docs/web-service-reference/olditemid.md | gscales/office-developer-exchange-docs | ae21a5e26dc6ecf93bf0127cc2cbadd910013cff | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-06-16T22:06:43.000Z | 2020-06-16T22:06:43.000Z | docs/web-service-reference/olditemid.md | gscales/office-developer-exchange-docs | ae21a5e26dc6ecf93bf0127cc2cbadd910013cff | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/web-service-reference/olditemid.md | gscales/office-developer-exchange-docs | ae21a5e26dc6ecf93bf0127cc2cbadd910013cff | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-04-02T01:57:16.000Z | 2020-04-24T06:43:09.000Z | ---
title: "OldItemId"
manager: sethgros
ms.date: 09/17/2015
ms.audience: Developer
ms.topic: reference
ms.prod: office-online-server
localization_priority: Normal
api_name:
- OldItemId
api_type:
- schema
ms.assetid: fb57deee-9cc3-4730-9805-ff34f39e3ab7
description: "The OldItemId element contains the unique identifier of the item that was copied or moved."
---
# OldItemId
The **OldItemId** element contains the unique identifier of the item that was copied or moved.
```xml
<OldItemId Id="" ChangeKey=""/>
```
**ItemIdType**
## Attributes and elements
The following sections describe attributes, child elements, and parent elements.
### Attributes
|**Attribute**|**Description**|
|:-----|:-----|
|**Id** <br/> |Contains a string that identifies an item in the Exchange store. This attribute is required. <br/> |
|**ChangeKey** <br/> |Contains a string that identifies a version of an item that is identified by the Id attribute. This attribute is optional. Use this attribute to make sure that the correct version of an item is used. <br/> |
### Child elements
None.
### Parent elements
|**Element**|**Description**|
|:-----|:-----|
|[CopiedEvent](copiedevent.md) <br/> |Represents an event in which an item or folder is copied. <br/> |
|[MovedEvent](movedevent.md) <br/> |Represents an event in which an item or folder is moved from one parent folder to another parent folder. <br/> |
## Remarks
The schema that describes this element is located in the EWS virtual directory of the computer that is running MicrosoftExchange Server 2007 that has the Client Access server role installed.
## Element information
|||
|:-----|:-----|
|Namespace <br/> |https://schemas.microsoft.com/exchange/services/2006/types <br/> |
|Schema Name <br/> |Types schema <br/> |
|Validation File <br/> |Types.xsd <br/> |
|Can be Empty <br/> |False <br/> |
## See also
[Subscribe operation](subscribe-operation.md)
[GetEvents operation](getevents-operation.md)
[Unsubscribe operation](unsubscribe-operation.md)
- [EWS XML elements in Exchange](ews-xml-elements-in-exchange.md)
| 27.907895 | 230 | 0.709571 | eng_Latn | 0.979048 |
58883987ae9f7b414a8c3b1c50f679d0a19e2eb1 | 2,213 | md | Markdown | 2017/CVE-2017-3588.md | marcostolosa/cve | bfe85c74b105c623c9807e09b2b572f144bf1f1c | [
"MIT"
] | 4 | 2022-03-01T12:31:42.000Z | 2022-03-29T02:35:57.000Z | 2017/CVE-2017-3588.md | AlexisTM/cve | 9a1a3a09d0c5862d10965716da45b3be36b8bcf7 | [
"MIT"
] | null | null | null | 2017/CVE-2017-3588.md | AlexisTM/cve | 9a1a3a09d0c5862d10965716da45b3be36b8bcf7 | [
"MIT"
] | 1 | 2022-03-29T02:35:58.000Z | 2022-03-29T02:35:58.000Z | ### [CVE-2017-3588](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3588)
%20of%20Solaris%20Cluster.&color=brighgreen)
### Description
Vulnerability in the Solaris Cluster component of Oracle Sun Systems Products Suite (subcomponent: HA for MySQL). Supported versions that are affected are 3.3 and 4.3. Easily exploitable vulnerability allows unauthenticated attacker with logon to the infrastructure where Solaris Cluster executes to compromise Solaris Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Solaris Cluster accessible data as well as unauthorized access to critical data or complete access to all Solaris Cluster accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Solaris Cluster. CVSS 3.0 Base Score 7.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L).
### POC
#### Reference
- http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html
#### Github
No GitHub POC found.
| 122.944444 | 919 | 0.822865 | eng_Latn | 0.53578 |
5888ad4f59d6562d478c282783897538741d1e11 | 1,003 | md | Markdown | README.md | jstrosch/Username_Generator | f94bc19365933aa45785dea1cc72418e2195225e | [
"MIT"
] | 6 | 2019-12-07T03:17:03.000Z | 2021-02-23T09:26:50.000Z | README.md | jstrosch/Username_Generator | f94bc19365933aa45785dea1cc72418e2195225e | [
"MIT"
] | null | null | null | README.md | jstrosch/Username_Generator | f94bc19365933aa45785dea1cc72418e2195225e | [
"MIT"
] | 6 | 2020-02-12T06:41:47.000Z | 2021-04-26T14:11:34.000Z | ## Email Parser and Username Generation - Burp Suite Extension
Burp Suite allows for extensions to be created in Python. This is a Python extension that will parse email addresses out of selected URLs from the target tab and display them in the output window of the Extensions tab. It will also generate a list of usernames from the emails found with basic permutations.
# Demo / More Information
[Blog Post - OxEvilC0de.com](https://0xevilc0de.com/finding-usernames-with-burp-extensions/)
[Demo - YouTube](https://youtu.be/Yf92sZ1sx6o)
# Dependencies
Download the latest version of [jython](http://www.jython.org) and configure Burp to use under Extender->Options->Python Environment.
# Installation
Add the Python script under Extender->Extensions. During loading there is an output window that will inform you of any errors.
# Usage
From the Target tab, select any URLs that you have visited, right-click and select "Get Emails" or "Generate Usernames" from the context menu.
Enjoy! | 45.590909 | 309 | 0.779661 | eng_Latn | 0.983063 |
5888b9e4c0fc483a14cbd0c2141308ee85587686 | 2,860 | md | Markdown | docs/web-service-reference/emailaddressattributedvalue.md | MicrosoftDocs/office-developer-exchange-docs.fr-FR | 441a34df68feaf234f2b43c1ec15a853d8aa2303 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-05-19T18:53:46.000Z | 2022-03-25T08:40:23.000Z | docs/web-service-reference/emailaddressattributedvalue.md | MicrosoftDocs/office-developer-exchange-docs.fr-FR | 441a34df68feaf234f2b43c1ec15a853d8aa2303 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2021-12-08T02:37:34.000Z | 2021-12-08T02:37:48.000Z | docs/web-service-reference/emailaddressattributedvalue.md | MicrosoftDocs/office-developer-exchange-docs.fr-FR | 441a34df68feaf234f2b43c1ec15a853d8aa2303 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: EmailAddressAttributedValue
manager: sethgros
ms.date: 09/17/2015
ms.audience: Developer
ms.topic: reference
ms.prod: office-online-server
ms.localizationpriority: medium
ms.assetid: ebdf224d-3796-4179-aa0a-87942e7585ff
description: L’élément EmailAddressAttributedValue spécifie une instance d’un tableau d’adresses de messagerie et leurs attributions associées.
ms.openlocfilehash: 2b5e9b431b6a62c63e815bfee190c923f454c867
ms.sourcegitcommit: 54f6cd5a704b36b76d110ee53a6d6c1c3e15f5a9
ms.translationtype: MT
ms.contentlocale: fr-FR
ms.lasthandoff: 09/24/2021
ms.locfileid: "59519764"
---
# <a name="emailaddressattributedvalue"></a>EmailAddressAttributedValue
**L’élément EmailAddressAttributedValue** spécifie une instance d’un tableau d’adresses de messagerie et leurs attributions associées.
```XML
<EmailAddressAttributedValue>
<Value></Value>
<Attributions></Attributions>
<EmailAddressAttributedValue>
```
**EmailAddressAttributedValueType**
## <a name="attributes-and-elements"></a>Attributs et éléments
Les sections suivantes décrivent les attributs, les éléments enfants et les éléments parents.
### <a name="attributes"></a>Attributs
Aucune.
### <a name="child-elements"></a>Éléments enfants
|**Élément**|**Description**|
|:-----|:-----|
|[Value (EmailAddressType)](value-emailaddresstype.md) <br/> |Spécifie la valeur d’un **emailAddress** associé à un tableau d’attributions. <br/> |
|[Attributions (ArrayOfValueAttributionsType)](attributions-arrayofvalueattributionstype.md) <br/> |Spécifie un tableau d’attributions pour son élément **Value** associé. <br/> |
### <a name="parent-elements"></a>Éléments parents
|**Élément**|**Description**|
|:-----|:-----|
|[Emails1](emails1.md) <br/> |Spécifie un tableau de valeurs de courrier électronique et les identificateurs de leurs attributions source pour le personnage associé. <br/> |
|[Emails2](emails2.md) <br/> |Spécifie un tableau de valeurs de courrier électronique et les identificateurs de leurs attributions source pour le personnage associé. <br/> |
|[Emails3](emails3.md) <br/> |Spécifie un tableau de valeurs de courrier électronique et les identificateurs de leurs attributions source pour le personnage associé. <br/> |
## <a name="remarks"></a>Remarques
Cet élément est une nouveauté d'Exchange Server 2013.
Le schéma qui décrit cet élément se trouve dans le répertoire virtuel IIS qui héberge les services web Exchange.
## <a name="element-information"></a>Informations sur l'élément
|||
|:-----|:-----|
|Espace de noms <br/> |https://schemas.microsoft.com/exchange/services/2006/types <br/> |
|Nom du schéma <br/> |Schéma type <br/> |
|Validation File <br/> |types.xsd <br/> |
|Peut être vide <br/> ||
## <a name="see-also"></a>Voir aussi
- [Éléments XML de EWS dans Exchange](ews-xml-elements-in-exchange.md)
| 38.648649 | 179 | 0.745455 | fra_Latn | 0.797358 |
5888de0862501a0d83c681dedc1221f960036157 | 49 | md | Markdown | jlatex/jlatex.api/README.md | bashterm/JLatex | a6c071321fa66f7ec84ff80e29b9d907e3f5a64d | [
"MIT"
] | null | null | null | jlatex/jlatex.api/README.md | bashterm/JLatex | a6c071321fa66f7ec84ff80e29b9d907e3f5a64d | [
"MIT"
] | 1 | 2021-07-12T18:22:19.000Z | 2021-07-22T00:11:33.000Z | jlatex/jlatex.api/README.md | bashterm/JLatex | a6c071321fa66f7ec84ff80e29b9d907e3f5a64d | [
"MIT"
] | 1 | 2021-02-17T18:30:39.000Z | 2021-02-17T18:30:39.000Z | # jlatex.api
This module is the core JLatex API. | 16.333333 | 35 | 0.755102 | eng_Latn | 0.862745 |
58890f68c0d14acd0cb9f8e960d9b29e5d976625 | 1,834 | md | Markdown | README.md | FGtatsuro/ansible-jenkins | 019bc4180cae5bd7e6d428091ee56f3d5356fbf9 | [
"MIT"
] | null | null | null | README.md | FGtatsuro/ansible-jenkins | 019bc4180cae5bd7e6d428091ee56f3d5356fbf9 | [
"MIT"
] | null | null | null | README.md | FGtatsuro/ansible-jenkins | 019bc4180cae5bd7e6d428091ee56f3d5356fbf9 | [
"MIT"
] | null | null | null | ansible-jenkins
====================================
[](https://travis-ci.org/FGtatsuro/ansible-jenkins)
Ansible role for Jenkins.
Requirements
------------
The dependencies on other softwares/librarys for this role.
- Debian
- Alpine Linux
- OSX
- Homebrew (>= 0.9.5)
Role Variables
--------------
The variables we can use in this role.
|name|description|default|
|---|---|---|
|jenkins_home|Home directory of Jenkins. You should also set this value as environment `JENKINS_HOME`.|/var/lib/jenkins|
|jenkins_user_login_shell|Login shell of Jenkins user.|/sbin/nologin|
|jenkins_war_dir|Parent directory Jenkins war file is put. In default, path of Jenkins war file is `/opt/jenkins/jenkins.war`.|/opt/jenkins|
|jenkins_download_url|Download URL for Jenkins war file. Different version has different URL.|https://updates.jenkins-ci.org/download/war/1.656/jenkins.war|
|jenkins_sha256|SHA256 signature of Jenkins war file. This is used for idempotency.|97085359725b16aca0f419486e5c1809399e33dbe6d906cd55ef82fad76fb30d|
- These variables are valid only on Debian and Alpine Linux, and they aren't used in OSX.
Role Dependencies
-----------------
The dependencies on other roles for this role.
- FGtatsuro.python-requirements
- FGtatsuro.java
- FGtatsuro.postfix
Example Playbook
----------------
- hosts: all
roles:
- { role: FGtatsuro.jenkins }
Test on local Docker host
-------------------------
This project run tests on Travis CI, but we can also run them on local Docker host.
Please check `install`, `before_script`, and `script` sections of `.travis.yml`.
We can use same steps of them for local Docker host.
Local requirements are as follows.
- Ansible (>= 2.0.0)
- Docker (>= 1.10.1)
License
-------
MIT
| 28.215385 | 156 | 0.706107 | eng_Latn | 0.845741 |
588973e618b99bb662e121e8f6f9c22e34a715ee | 1,776 | md | Markdown | biztalk/core/how-to-enable-a-receive-location.md | SicongLiuSimon/biztalk-docs | 85394b436d277504d9e759c655608888123785bd | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-06-14T19:45:26.000Z | 2019-06-14T19:45:26.000Z | biztalk/core/how-to-enable-a-receive-location.md | AzureMentor/biztalk-docs | 16b211f29ad233c26d5511475c7e621760908af3 | [
"CC-BY-4.0",
"MIT"
] | 7 | 2020-01-09T22:34:58.000Z | 2020-02-18T19:42:16.000Z | biztalk/core/how-to-enable-a-receive-location.md | AzureMentor/biztalk-docs | 16b211f29ad233c26d5511475c7e621760908af3 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2017-06-23T18:30:28.000Z | 2017-11-28T01:11:25.000Z | ---
title: "How to Enable a Receive Location | Microsoft Docs"
ms.custom: ""
ms.date: "06/08/2017"
ms.prod: "biztalk-server"
ms.reviewer: ""
ms.suite: ""
ms.tgt_pltfrm: ""
ms.topic: "article"
helpviewer_keywords:
- "enabling, receive locations"
- "managing [receive locations], enabling"
- "receive locations, enabling"
ms.assetid: ea1647cd-7bcb-4603-a64e-23b3fb0622a5
caps.latest.revision: 13
author: "MandiOhlinger"
ms.author: "mandia"
manager: "anneta"
---
# How to Enable a Receive Location
This topic describes how to use the BizTalk Server Administration console to enable a receive location. A receive location must be enabled before it can receive messages.
For instructions on creating a receive location, see [How to Create a Receive Location](../core/how-to-create-a-receive-location.md).
## Prerequisites
To perform the procedure in this topic, you must be logged on with an account that is a member of the BizTalk Server Operators group or the BizTalk Server Administrators group. For more detailed information on permissions, see [Permissions Required for Deploying and Managing a BizTalk Application](../core/permissions-required-for-deploying-and-managing-a-biztalk-application.md).
### To enable a receive location
1. Click **Start**, click **All Programs**, click [!INCLUDE[btsBizTalkServerStartMenuItemui](../includes/btsbiztalkserverstartmenuitemui-md.md)], and then click **BizTalk Server Administration**.
2. In the console tree, expand the BizTalk group and the BizTalk application for which you want to enable a receive location.
3. Click **Receive Locations**, right-click the receive location, and then click **Enable**.
## See Also
[Managing Receive Locations](../core/managing-receive-locations.md) | 46.736842 | 384 | 0.755068 | eng_Latn | 0.968182 |
588a645486c2c75f0175299979f8aa935e245fd6 | 1,078 | md | Markdown | reproducing-issues/README.md | aptinio/elm-graphql | 5c5eab370aff511b19a6dc9023d0da58256ccfdf | [
"BSD-3-Clause"
] | 625 | 2018-08-22T14:33:46.000Z | 2022-03-31T18:40:52.000Z | reproducing-issues/README.md | aptinio/elm-graphql | 5c5eab370aff511b19a6dc9023d0da58256ccfdf | [
"BSD-3-Clause"
] | 451 | 2018-08-22T21:00:10.000Z | 2022-03-16T14:43:42.000Z | reproducing-issues/README.md | aptinio/elm-graphql | 5c5eab370aff511b19a6dc9023d0da58256ccfdf | [
"BSD-3-Clause"
] | 110 | 2018-09-17T23:34:50.000Z | 2022-03-16T14:29:55.000Z | # Reproducing Issues
## Background
I get a lot of issues, which are all appreciated. However, it's not viable for me as a maintainer to reproduce each of them (multiply the number of users by the amount of time to get context on the problem, ask questions to get context, try to reproduce the issue, and then get context on whatever I was working on that day!). So please do the following steps before getting help for a fix. This makes development on this project a lot more sustainable. Thank you!
## Creating a minimal reproduction of possible or known issues
This folder contains some tools to help reproduce minimal examples.
After cloning this project, run this from the top-level directory of the `elm-graphql` repo:
```bash
npm run reproduce-error
```
This will take the GraphQL schema from the file `reproducing-issues/sdl.js` and generate code based on that. From there you can check if you've reproduced the issue. This helps you iterate quickly to create a minimal schema that reproduces the fix.
Then you can share the SDL snippet that created the problem.
| 53.9 | 464 | 0.784787 | eng_Latn | 0.999852 |
588a80ab9f95fc7fcefd90f37c3218283114c1a3 | 4,367 | md | Markdown | content/media/weixin/wx_肖磊看市/肖磊：美国数字货币多头并进，中国官方数字货币将会在深圳诞生.md | leeleilei/52etf.net | 934d558bd4181a1e0b39a7a10e0d7076c53995fb | [
"CC-BY-4.0"
] | 10 | 2020-06-01T16:08:00.000Z | 2021-10-31T15:17:26.000Z | content/media/weixin/wx_肖磊看市/肖磊：美国数字货币多头并进，中国官方数字货币将会在深圳诞生.md | leeleilei/52etf.net | 934d558bd4181a1e0b39a7a10e0d7076c53995fb | [
"CC-BY-4.0"
] | null | null | null | content/media/weixin/wx_肖磊看市/肖磊：美国数字货币多头并进，中国官方数字货币将会在深圳诞生.md | leeleilei/52etf.net | 934d558bd4181a1e0b39a7a10e0d7076c53995fb | [
"CC-BY-4.0"
] | null | null | null |
---
title: 肖磊：美国数字货币多头并进，中国官方数字货币将会在深圳诞生-肖磊看市
date: 2019-08-19
tags: ["肖磊看市", ]
display: false
---
##
肖磊：美国数字货币多头并进，中国官方数字货币将会在深圳诞生
kanshi1314
在投资市场，获取有用的信息就像大海捞针，我每天用18个小时思考，用五分钟告诉你；这里是肖磊看市，市场纵然复杂多变，但并非不可预期。
作者：肖磊看市
公众号：kanshi1314
8月18日，《中共中央 国务院关于支持深圳建设中国特色社会主义先行示范区的意见》（以下简称《意见》）发布。
其中第五条当中提到了一句，“**支持在深圳开展数字货币研究与移动支付等创新应用。**”
这一句对于区块链、数字货币行业从业者和参与者来说，是值得关注的，因为跟其他领域相比，数字货币这个领域过于敏感和充满未知，中央的认同就显得尤为重要，况且这一句在第五条当中，是完整的、独立的一句，跟前面的一句和后面的一句，是用句号隔开，这说明本身就是一个独立的，大的分类。
<img class="rich_pages" data-copyright="0" data-ratio="0.20493150684931508" data-s="300,640" src="https://mmbiz.qpic.cn/mmbiz_png/rIYcHn0KrPQCkby0uIQmvJQRskJdZO1yKJGsSVo2icia6tDzyhWwk3Qk8KLicFnxEdTn9uuP2UVfO05DGQZPqUPNw/640?wx_fmt=png" data-type="png" data-w="1825" style=""/>
这个文件是未来深圳很多创新领域的一个纲领性指导文件，每一句话，每一个字，都是经过反复斟酌的，因为这牵扯到创新创业者寻找合法性的问题。所以关于数字货币尽管只有一句话，但已经很能说明问题了。
那么中央为什么要支持深圳开展数字货币研究与移动支付等创新应用呢？答案是显而易见的，深圳作为中国在金融市场的第三极，应该负担起先行先试的权利和责任。
中国金融市场存在很明显的三极，其定位各不相同。
北京是中国整合国际金融政治资源的中心，我刚刚看到北京上半年全市金融运行情况，其中全球两大银行卡组织威士（VISA）和万事达卡（Mastercard）在京注册新机构。环球融讯网络技术服务（中国）有限公司（SWIFT）在西城区注册。丰田金融服务（中国）有限公司注册成立。
<img class="rich_pages" data-copyright="0" data-ratio="0.6114649681528662" data-s="300,640" src="https://mmbiz.qpic.cn/mmbiz_jpg/rIYcHn0KrPQCkby0uIQmvJQRskJdZO1yeWaWia74YcYqjvLTic7dw6WPibubZ1kjAIclvz4zD5F6u77dG4hbbgWHA/640?wx_fmt=jpeg" data-type="jpeg" data-w="785" style=""/>
**亚投行北京总部大楼**
其实以上这些国际金融服务公司的注册，很大程度上，是出于政治和金融的双重考量，这就是北京的作用。国内比如腾讯和阿里，已经很强大了，但依然会在北京建立一个总部，也是出于政治资源的考量。
上海的话，属于金融的大类业务，比如最近几年，就建立了黄金交易的国际板、原油交易的国际板、债券和股市两个方面的对外逐步开放等，这些都是数十万亿美元规模的市场，是一国金融领域的根基，所以上海其实都不需要金融创新，就可以稳坐中国第一金融之城的宝座。
中国的金融领域，分工应该是这样的，北京拥有政治优势，负责上游整合国际金融资源，上海负责稳扎稳打的实现金融战略意图，那么具体着眼于未来的创新，由哪里承担呢？深圳就是这样一个不可或缺，且舍我其谁的第三极，深圳要的是创新，要的是大胆，失败了没关系，重新再来。
但数字货币和移动支付问题，看上去是金融领域的末梢，具备更大的创新空间，但这两个问题，天然的是一个责任重大的问题，因为数字货币本身，就是一个自带国际属性的问题，而移动支付中国已经领先世界，再创新，就是要超越自己，前面没有引路者。
所以数字货币和移动支付问题，对于深圳来说，成了就将是大功一件，不成，则影响全局。
其实早在2016年6月，央行数字货币研究所就在深圳成立了专门的金融科技公司，该公司当时就参与了贸易金融区块链等项目的开发。经营范围包括：金融科技相关技术开发、技术咨询、技术转让、技术服务；金融科技相关系统建设与运行维护。
<img class="rich_pages" data-copyright="0" data-ratio="0.6081409477521263" data-s="300,640" src="https://mmbiz.qpic.cn/mmbiz_png/rIYcHn0KrPQCkby0uIQmvJQRskJdZO1ykicwpVlYmk4ocIFepvOibpLbJnMWYsMJt7wtQDkxqiaOQUvRwy1tbUibXQ/640?wx_fmt=png" data-type="png" data-w="1646" style=""/>
2016年12月的时候，平安集团、招商银行、微众银行、大成基金等国内外40多家知名金融机构，共同成立全国首个中国（深圳）Fintech数字货币联盟及中国（深圳）Fintech研究院。 该研究院是继央行宣布成立数字货币研究所之后，国内首个地方城市从国家金融创新开放、推进人民币国际化等战略高度，发起成立的金融科技联盟和研究院。
上面这个研究院是非常开放的，当时还邀请了国内一些数字货币交易所参与，而数字货币交易所一直存在政策上的争议，能邀请参与，足以说明深圳在这方面的开放性。
按照我的分析，未来关于数字货币和移动支付的机会，存在于三个方面。
第一个是，中国的数字货币，具体分为哪几个环节，每个环节上的具体服务公司，应该具备什么条件；第二个是，数字货币在融合进移动支付的过程中，现有的手机厂商、互联网巨头、区块链企业、金融公司等，各自如何切入服务体系；第三个是，中国的数字货币，对全球各类虚拟货币，比如比特币等，是否会产生定价和交易影响，又如何将现有各类持续运行的市场主体企业纳入其中，借力打力，从而提升中国官方数字货币的全球化属性和影响力。
以上三个方面，深圳有大胆尝试的政策基础，但时不我待。
就在此时，致力于取代移动支付，而直接进入到国际数字货币时代的Facebook发行的libra，已经进入到最后的攻坚阶段，就连持续批评libra的美国众议院金融服务委员会主席、民主党人Maxine Waters，也将在未来几天领导一个六人小组的访问团造访瑞士，并与瑞士联邦数据保护和信息专员Adrian Lobsiger就Facebook数字货币Libra相关问题进行会谈。
<img class="rich_pages" data-copyright="0" data-ratio="1" data-s="300,640" src="https://mmbiz.qpic.cn/mmbiz_jpg/rIYcHn0KrPQxE6zMiarib0VYKnt94Md6MMtJIw6YEwy8maoZPYfqopnlsqVs55Vz3JiaQIS7PZ1rg8lrYVngiaw9CQ/640?wx_fmt=jpeg" data-type="jpeg" data-w="430" style="height: 224px;width: 224px;"/>
**防失联加微：kanshi6188，或扫码，有我其他号的不要重复加**
一旦双边建立一定的互信和协调机制，美国很有可能会迅速批准libra进入到试运行阶段。美国的支付系统，因此将直接从网银时代，跳跃到数字货币时代，中国的移动支付领先优势将可能不再。
另外，纽约证券交易所支持的数字资产平台Bakkt，其实物结算比特币期货合约产品已经进入到用户验收测试阶段，法律程序和监管问题已经解决，该期货品种上市的日期大概在今年的九月，从该交易所负责人的言论看，把主要的竞争对手定义在现有的，不受监管的各类交易所。
原话是：“我们为客户提供了前所未有的监管清晰度和安全性，在当前机构级基础设施不足的市场中，Bakkt也将成为一家受监管、可全球访问的交易所。”
这将意味着，美国在利用传统金融市场的权威和先于其他国家一步的优势，主导整个未来数字资产的金融定价市场，中国在很长时间里培育起来的整条产业链优势，可能会变得非常被动，国内的投资者，难免会被美国市场牵着鼻子走。
也就是说，种种迹象表明，未来金融市场，在数字货币领域，尤其是在数字货币的交易和支付市场，国家级别的竞争将不可避免。既然已经给深圳下放了这个试验权限，我希望这一次不要再搞一些雷声大雨点小的事情，各种组织尽量少成立，直接干实事，就像Facebook发行libra一样，先把产品搞出来，然后再解决争议，争议解决了立马就可以推。
文/肖磊（如果担心错过重要分析，请关注肖磊看市公众号）
**通知：我的币圈投资课年费会员，马上要涨价了，还没有加入的同学请尽快加入，近期行情波动剧烈，将持续做出各类事件及具体影响的深入解读。**
****
<img class="rich_pages" data-copyright="0" data-ratio="1.7786666666666666" data-s="300,640" src="https://mmbiz.qpic.cn/mmbiz_jpg/rIYcHn0KrPQCkby0uIQmvJQRskJdZO1y92lRfPOL7GjBicsC1iaNUDia3ZV7zAj5UHBCvVeWoiaNL4rfPs8bGOaH0A/640?wx_fmt=jpeg" data-type="jpeg" data-w="750" style=""/>
左下角 点击“阅读原文”听课。
一定得好好写
**微信扫一扫赞赏作者**
一定得好好写
| 23.994505 | 287 | 0.831463 | yue_Hant | 0.621996 |
588c552304f77ebe3ec8d7f96360c652213f38c7 | 86 | md | Markdown | README.md | jzhu98/atom-language-d | 3d58c8e72b6aa976cb7377b0a23d0e6f927d62ef | [
"MIT"
] | 12 | 2015-03-13T06:38:01.000Z | 2021-05-04T15:44:29.000Z | README.md | jzhu98/atom-language-d | 3d58c8e72b6aa976cb7377b0a23d0e6f927d62ef | [
"MIT"
] | 10 | 2015-01-02T08:47:55.000Z | 2018-11-05T13:36:27.000Z | README.md | jzhu98/atom-language-d | 3d58c8e72b6aa976cb7377b0a23d0e6f927d62ef | [
"MIT"
] | 7 | 2015-07-29T18:56:43.000Z | 2021-05-04T15:46:38.000Z | # D language support in Atom
Add syntax highlighting and snippets to D files in Atom.
| 28.666667 | 56 | 0.790698 | eng_Latn | 0.979879 |
588cd5d5a59e1bf86c65624ca7162733f01f5c53 | 347 | md | Markdown | README.md | nalevi/CppUmlClassGen | 3bee7ca2e97cabbccc082aeac417985962da3976 | [
"MIT"
] | 1 | 2021-03-16T20:42:52.000Z | 2021-03-16T20:42:52.000Z | README.md | nalevi/CppUmlClassGen | 3bee7ca2e97cabbccc082aeac417985962da3976 | [
"MIT"
] | null | null | null | README.md | nalevi/CppUmlClassGen | 3bee7ca2e97cabbccc082aeac417985962da3976 | [
"MIT"
] | null | null | null | # CppUmlClassGen
A small command-line tool based on Clang AST to generate UML class diagramms for C++ classes.
# Libraries
- clang: for traversing the sourcecode's AST and get informations form its nodes.
- graphviz: for generating graphs (with DOT language).
- Webtoolkit (Wt): its ORM library (Wt::Dbo) for storing information in a database.
| 34.7 | 93 | 0.766571 | eng_Latn | 0.949409 |
588da4046a8d991621f638b71fd06318e389420a | 128 | md | Markdown | source/algar/partials/_authentication.md | atendesimples/api-docs | 8fb6f01c1554acfd6027e7464138977db2c24d6c | [
"Apache-2.0"
] | 1 | 2020-07-30T00:18:03.000Z | 2020-07-30T00:18:03.000Z | source/algar/partials/_authentication.md | atendesimples/api-docs | 8fb6f01c1554acfd6027e7464138977db2c24d6c | [
"Apache-2.0"
] | 1 | 2019-12-19T13:01:33.000Z | 2019-12-19T13:01:33.000Z | source/algar/partials/_authentication.md | atendesimples/api-docs | 8fb6f01c1554acfd6027e7464138977db2c24d6c | [
"Apache-2.0"
] | 5 | 2015-06-15T13:25:40.000Z | 2018-08-30T19:19:43.000Z | # Autenticação
A API Algar Digital fornece 2 formas de autenticação:
* OAuth2
* Token de Acesso
<!-- TODO: add more info -->
| 14.222222 | 53 | 0.703125 | por_Latn | 0.921149 |
588f522af925baf2900a917eccaa8f65d1c5719f | 4,347 | md | Markdown | README.md | royhzq/sg-headlines-rnn | cef84f1ffe7f18a37386e9602166082c10e9020b | [
"MIT"
] | null | null | null | README.md | royhzq/sg-headlines-rnn | cef84f1ffe7f18a37386e9602166082c10e9020b | [
"MIT"
] | 13 | 2020-01-28T23:05:24.000Z | 2022-02-10T00:34:57.000Z | README.md | royhzq/sg-headlines-rnn | cef84f1ffe7f18a37386e9602166082c10e9020b | [
"MIT"
] | null | null | null | # Singapore News Headlines RNN Generator
An application that generates news headlines using a recurrent neural network (RNN) trained on approximately 500,000 headlines from a news agency in Singapore. The dockerized application includes an API enpoint served using Flask, gunicorn, and Nginx. The network is trained using Tensorflow 1.14. Try generating some news headlines at https://royhung.com/sg-news-rnn
## Quickstart
To start the API server, ensure docker is installed and run the following command in the project root directory:
```bash
$ docker-compose up
```
This will start an Nginx docker container and a flask container that serves the application on port 5001.<br> You can access the API at http://my-public-ip:5001 or http://localhost:5001 if you are running the app locally.
## API Reference
### Generate News Headlines
POST endpoint for a RESTful API that generates random news headlines from a RNN trained on news headlines from a local newspaper dataset.
```bash
POST /headlines
```
#### Request POST JSON Example
```json
{
"n_headlines": 5,
"start_string": "Singapore "
}
```
| Property | Type |Description | Required
| --- | --- | :- | --- |
|``` n_headlines ```| Integer | Number of headlines to generate. Maximum number returned is 10 headlines. Defaults to 5 if parameter not provided | No |
|``` start_string ```| String | Starting text for the first headline. Serves as the RNN input. ``` start_string ``` Defaults to "Singapore " if not provided. Unrecognized characters will be coerced to whitespace. | No |
#### Response JSON Example
```json
["Singapore The Spirit In New Hongbao To End Production Trick",
"Asia Briefs South Korea Ferry Disaster Victims Of James Hits The World",
"Warriors Get A Threat To The Sky",
"Airasia Flight Qz8501 Dead State For Role In More Than 68000 Raised For The Store Of Singapore And India"
"The Books For Becoming A Storm"]
```
## Dataset
The raw headlines dataset contains 500,597 URLs from the Straits Times Singapore newspaper. For SEO purposes, most news agencies "slugify" their news article headlines and include them into the URL path. Take for example the headline:
**"Raffles Hotel's reopening a chance for Kit Chan to walk down memory lane"**
The corresponding URL path turns out to be:
**/lifestyle/raffles-hotels-reopening-a-chance-for-kit-chan-to-walk-down-memory-lane**
Obtaining the headlines dataset is a matter of cleaning these URLs. A more detailed process for data cleaning can be found in this [notebook](./notebooks/1_st_headlines_clean.ipynb).
### Summary of Preprocessed Data
Full EDA of this dataset and code can be found in this [notebook](./notebooks/2_st_headlines_eda.ipynb).
```python
# Sample of cleaned dataset
import pandas as pd
pd.options.display.max_colwidth = 150
df = pd.read_csv("./data/st_sitemap_clean.csv")
```
```python
df.sample(5)
```
<div>
<table border="1" class="dataframe">
<thead>
<tr style="text-align: right;">
<th></th>
<th>Headline</th>
<th>Category</th>
<th>Wordcount</th>
<th>Charcount</th>
</tr>
</thead>
<tbody>
<tr>
<td>240798</td>
<td>Starhub Lowers Rates For Line Only Plans Following Rivals New Plans</td>
<td>Tech</td>
<td>11</td>
<td>67</td>
</tr>
<tr>
<td>109008</td>
<td>Georgia Father Charged With Murder In Sons Hot Car Death</td>
<td>World/Americas</td>
<td>10</td>
<td>56</td>
</tr>
<tr>
<td>49284</td>
<td>Singapore Scientists Join First International Ocean Sampling Day</td>
<td>Singapore/Environment</td>
<td>8</td>
<td>64</td>
</tr>
<tr>
<td>288022</td>
<td>Syrian Opposition Agrees To Participate In Geneva Peace Talks</td>
<td>World</td>
<td>9</td>
<td>61</td>
</tr>
<tr>
<td>379611</td>
<td>Rws Plans Wont Hit Genting Berhads Credit Rating Fitch</td>
<td>Business</td>
<td>9</td>
<td>54</td>
</tr>
</tbody>
</table>
</div>
## More Information
For a more detailed writeup on the dataset and code, visit https://royhung.com/sg-news-rnn
| 29.97931 | 367 | 0.691281 | eng_Latn | 0.870807 |
58907427770702c73601c9402897c64cb961ed48 | 330 | md | Markdown | docs/tests/sameas.md | feffi/aspect | a565d344ab5231b050b0708c7cd9bdcd2ac5da0f | [
"BSD-3-Clause"
] | 18 | 2019-11-08T02:08:54.000Z | 2021-10-08T14:24:42.000Z | docs/tests/sameas.md | feffi/aspect | a565d344ab5231b050b0708c7cd9bdcd2ac5da0f | [
"BSD-3-Clause"
] | 4 | 2019-10-21T08:46:24.000Z | 2020-11-06T14:21:01.000Z | docs/tests/sameas.md | feffi/aspect | a565d344ab5231b050b0708c7cd9bdcd2ac5da0f | [
"BSD-3-Clause"
] | 1 | 2020-09-28T19:06:49.000Z | 2020-09-28T19:06:49.000Z | ---
layout: page
title: Tests › same as
---
[← tests](./../tests.md)
<!-- {% raw %} -->
`same as` checks if a variable is the same as another variable. This is the equivalent to == in Lua:
```twig
{% if foo.attribute is same as(false) %}
the foo attribute really is the 'false' value
{% endif %}
```
<!-- {% endraw %} --> | 18.333333 | 100 | 0.587879 | eng_Latn | 0.998129 |
58908cca864036946bb9e4aa46b4d0d795a58c95 | 892 | md | Markdown | docs/content/user-manual/elasticjob-lite/_index.en.md | DreamcatcherGo/shardingsphere-elasticjob-lite | a32c5fa0c1176da11fbebc5209575df5b6fee96a | [
"Apache-2.0"
] | null | null | null | docs/content/user-manual/elasticjob-lite/_index.en.md | DreamcatcherGo/shardingsphere-elasticjob-lite | a32c5fa0c1176da11fbebc5209575df5b6fee96a | [
"Apache-2.0"
] | 2 | 2022-01-21T23:47:03.000Z | 2022-01-21T23:48:58.000Z | docs/content/user-manual/elasticjob-lite/_index.en.md | DreamcatcherGo/shardingsphere-elasticjob-lite | a32c5fa0c1176da11fbebc5209575df5b6fee96a | [
"Apache-2.0"
] | null | null | null | +++
pre = "<b>4.1. </b>"
title = "ElasticJob-Lite"
weight = 1
chapter = true
+++
## Introduction
ElasticJob-Lite is a lightweight, decentralized solution that provides distributed task sharding services.
## Comparison
| | *ElasticJob-Lite* | *ElasticJob-Cloud* |
| ----------------- | ----------------- | ------------------ |
| Decentralization | `Yes` | No |
| Resource Assign | `No` | Yes |
| Job Execution | `Daemon` | Daemon + Transient |
| Deploy Dependency | `ZooKeeper` | ZooKeeper + Mesos |
The advantages of Elasticjob Lite are no centralized design and less external dependence,
which is suitable for business application with stable resource allocation.
| 35.68 | 122 | 0.609865 | eng_Latn | 0.869119 |
5890ad9b9996c6116343ed0afa9c0f17fa98f5a3 | 9 | md | Markdown | README.md | VeldFrost/js-tdd | 9575ef28f92368432bb298db3e18c663e62918e7 | [
"MIT"
] | null | null | null | README.md | VeldFrost/js-tdd | 9575ef28f92368432bb298db3e18c663e62918e7 | [
"MIT"
] | null | null | null | README.md | VeldFrost/js-tdd | 9575ef28f92368432bb298db3e18c663e62918e7 | [
"MIT"
] | null | null | null | # js-tdd
| 4.5 | 8 | 0.555556 | cym_Latn | 0.712581 |
5890f89b489d80d93922017cbd53d5bfe8e850cf | 22,074 | md | Markdown | memdocs/configmgr/core/plan-design/configs/support-for-sql-server-versions.md | svschmit/memdocs.de-de | 63c0beff46a0955a98306504b449badaa675f10b | [
"CC-BY-4.0",
"MIT"
] | null | null | null | memdocs/configmgr/core/plan-design/configs/support-for-sql-server-versions.md | svschmit/memdocs.de-de | 63c0beff46a0955a98306504b449badaa675f10b | [
"CC-BY-4.0",
"MIT"
] | null | null | null | memdocs/configmgr/core/plan-design/configs/support-for-sql-server-versions.md | svschmit/memdocs.de-de | 63c0beff46a0955a98306504b449badaa675f10b | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Unterstützte Versionen von SQL Server
titleSuffix: Configuration Manager
description: Abrufen der SQL Server-Version und Konfigurationsanforderungen zum Hosten einer Configuration Manager-Standortdatenbank.
ms.date: 06/24/2020
ms.prod: configuration-manager
ms.technology: configmgr-core
ms.topic: conceptual
ms.assetid: 35e237b6-9f7b-4189-90e7-8eca92ae7d3d
author: mestew
ms.author: mstewart
manager: dougeby
ms.openlocfilehash: 5043967a640b937784c22ea2b74269a2f2043ba9
ms.sourcegitcommit: 8fc1704ed0e1141f46662bdd32b52bec00fb93b4
ms.translationtype: HT
ms.contentlocale: de-DE
ms.lasthandoff: 09/09/2020
ms.locfileid: "89607638"
---
# <a name="supported-sql-server-versions-for-configuration-manager"></a>Unterstützte SQL Server-Versionen für Configuration Manager
*Gilt für: Configuration Manager (Current Branch)*
Jeder Configuration Manager-Standort erfordert zum Hosten der Standortdatenbank eine unterstützte Version und Konfiguration von SQL Server.
## <a name="sql-server-instances-and-locations"></a><a name="bkmk_Instances"></a> SQL Server-Instanzen und -Speicherorte
### <a name="central-administration-site-and-primary-sites"></a>Standort der zentralen Verwaltung und primäre Standorte
Die Standortdatenbank muss eine vollständige Installation von SQL Server verwenden.
SQL Server kann auf den folgenden Computern installiert sein:
- Standortservercomputer
- Remotecomputer des Standortservers
Die folgenden Instanzen werden unterstützt:
- Standard- oder benannte Instanz von SQL Server
- Konfigurationen mit mehreren Instanzen
- SQL Server-Cluster Weitere Informationen finden Sie unter [Hosten der Standortdatenbank mit einem SQL Server-Cluster](../../servers/deploy/configure/use-a-sql-server-cluster-for-the-site-database.md).
- SQL Server Always On-Verfügbarkeitsgruppe. Weitere Informationen finden Sie unter [SQL Server Always On für eine hochverfügbare Standortdatenbank](../../servers/deploy/configure/sql-server-alwayson-for-a-highly-available-site-database.md).
### <a name="secondary-sites"></a>Sekundäre Standorte
Die Standortdatenbank kann die Standardinstanz einer vollständigen Installation von SQL Server oder SQL Server Express verwenden.
SQL Server muss auf dem Standortservercomputer installiert sein.
### <a name="limitations-to-support"></a>Einschränkungen der Unterstützung
Die folgenden Konfigurationen werden nicht unterstützt:
- Ein SQL Server-Cluster in einer Clusterkonfiguration mit Netzwerklastenausgleich (Network Load Balancing, NLB)
- Ein SQL Server-Cluster in einem freigegebenen Clustervolume (Cluster Shared Volume, CSV)
- Technologien zur SQL Server-Datenbankspiegelung sowie Peer-to-Peer-Replikation
Die SQL Server-Transaktionsreplikation wird nur für das Replizieren von Objekten an Verwaltungspunkte unterstützt, die für die Verwendung von [Datenbankreplikaten](../../servers/deploy/configure/database-replicas-for-management-points.md) konfiguriert sind.
## <a name="supported-versions-of-sql-server"></a><a name="bkmk_SQLVersions"></a> Unterstützte Versionen von SQL Server
In einer Hierarchie mit mehreren Standorten können verschiedene Standorte verschiedene SQL Server-Versionen zum Hosten der Standortdatenbank verwenden. Dies gilt jedoch nur, wenn folgende Voraussetzungen erfüllt sind:
- Configuration Manager unterstützt die von Ihnen verwendeten SQL Server-Versionen.
- Microsoft stellt weiterhin Support für die von Ihnen verwendeten SQL Server-Versionen bereit.
- SQL Server unterstützt Replikationen zwischen beiden SQL Server-Versionen. Weitere Informationen finden Sie unter [SQL Server replication backward compatibility](/sql/relational-databases/replication/replication-backward-compatibility) (SQL Server – Abwärtskompatibilität bei Replikationen).
Bei SQL Server 2016 und früher folgt die Unterstützung für jede SQL-Version und jedes Service Pack der [Microsoft-Lebenszyklusrichtlinie](https://aka.ms/sqllifecycle). Der Support für ein bestimmtes Service Pack von SQL Server beinhaltet kumulative Updates, sofern diese nicht gegen die Abwärtskompatibilität für die Basisversion des Service Packs verstoßen. Ab SQL Server 2017 werden keine Service Packs mehr veröffentlicht, da diese Version einem [modernen Wartungsmodell](/archive/blogs/sqlreleaseservices/announcing-the-modern-servicing-model-for-sql-server) folgt. Das SQL Server-Team empfiehlt eine fortlaufende, [proaktive Installation kumulativer Updates](/archive/blogs/sqlreleaseservices/announcing-updates-to-the-sql-server-incremental-servicing-model-ism), sobald sie verfügbar werden.
Sofern nicht anders angegeben, werden die folgenden SQL Server-Versionen von allen aktiven Versionen von Configuration Manager-Versionen unterstützt. Beim Hinzufügen von Unterstützung für eine neue SQL Server-Version wird die Configuration Manager-Version angegeben, mit der diese Unterstützung hinzugefügt wird. Beachten Sie bei eingestelltem Support ebenfalls die Details zu den betroffenen Versionen von Configuration Manager.
> [!IMPORTANT]
> Wenn Sie SQL Server Standard für die Datenbank am Standort der zentralen Verwaltung verwenden, ist die Gesamtanzahl der Clients begrenzt, die eine Hierarchie unterstützen kann. Informationen hierzu finden Sie unter [Size and scale numbers for System Center Configuration Manager](size-and-scale-numbers.md)(Anpassen und Skalieren von Zahlen für System Center Configuration Manager).
### <a name="sql-server-2019-standard-enterprise"></a>SQL Server 2019: Standard und Enterprise
Ab Configuration Manager Version 1910 können Sie diese Version mit dem kumulativen Update 5 (CU5) verwenden, sofern Ihre kumulative Updateversion vom SQL-Lebenszyklus unterstützt wird. CU5 ist die Mindestanforderung für SQL Server 2019, da es ein Problem mit [skalarem UDF-Inlining](/sql/relational-databases/user-defined-functions/scalar-udf-inlining) behebt.
Diese SQL Server-Version kann für die folgenden Standorte verwendet werden:
- Ein Standort der zentralen Verwaltung
- Primären Standort
- Sekundären Standort
<!--
#### Known issue with SQL Server 2019
There's a known issue<!--6436234 with the new [scalar UDF inlining](/sql/relational-databases/user-defined-functions/scalar-udf-inlining) feature in SQL 2019. To work around this issue and disable UDF lining, run the following script on the SQL 2019 server:
```sql
ALTER DATABASE SCOPED CONFIGURATION SET TSQL_SCALAR_UDF_INLINING = OFF
```
While not always necessary, you may need to restart the SQL server after you run this script. For more information, see [Disabling Scalar UDF Inlining without changing the compatibility level](/sql/relational-databases/user-defined-functions/scalar-udf-inlining#disabling-scalar-udf-inlining-without-changing-the-compatibility-level).
You can safely disable this SQL feature for the site database server because Configuration Manager doesn't use it.
If you don't disable scalar UDF inlining in SQL 2019, the site server will randomly fail to query the site database. For example, you'll see the following errors in **hman.log**:
```hman.log
*** [HY000][0][Microsoft][SQL Server Native Client 11.0]Unspecified error occurred on SQL Server. Connection may have been terminated by the server.
*** select dbo.fnGetSiteMode(dbo.fnGetSiteCode())
*** [HY000][596][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot continue the execution because the session is in the kill state.
Failed to execute SQL command select dbo.fnGetSiteMode(dbo.fnGetSiteCode())
```
You may see similar errors in other logs, such as **SmsAdminUI.log**.
SQL Server version 2019 logs the following error:
`Microsoft SQL Server reported SQL message 596, severity 21: [HY000][596][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot continue the execution because the session is in the kill state.`
You'll also see crash dumps (`.mdump` files) from SQL in its log directory, which by default is `C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Log`.
-->
### <a name="sql-server-2017-standard-enterprise"></a>SQL Server 2017: Standard und Enterprise
Sie können diese Version beim [kumulativen Update, Version 2 oder höher](https://support.microsoft.com/help/4052574), verwenden, solange Ihre kumulative Updateversion vom SQL-Lebenszyklus unterstützt wird. Diese SQL Server-Version kann für die folgenden Standorte verwendet werden:
- Ein Standort der zentralen Verwaltung
- Primären Standort
- Sekundären Standort
<!--SMS.498506-->
### <a name="sql-server-2016-standard-enterprise"></a>SQL Server 2016: Standard und Enterprise
<!--514985-->
Sie können diese Version beim minimalen Service Pack und bei dem vom SQL-Lebenszyklus unterstützten kumulativen Update verwenden. Diese SQL Server-Version kann für die folgenden Standorte verwendet werden:
- Ein Standort der zentralen Verwaltung
- Primären Standort
- Sekundären Standort
### <a name="sql-server-2014-standard-enterprise"></a>SQL Server 2014: Standard und Enterprise
Sie können diese Version beim minimalen Service Pack und bei dem vom SQL-Lebenszyklus unterstützten kumulativen Update verwenden. Diese SQL Server-Version kann für die folgenden Standorte verwendet werden:
- Ein Standort der zentralen Verwaltung
- Primären Standort
- Sekundären Standort
### <a name="sql-server-2012-standard-enterprise"></a>SQL Server 2012: Standard und Enterprise
Sie können diese Version beim minimalen Service Pack und bei dem vom SQL-Lebenszyklus unterstützten kumulativen Update verwenden. Diese SQL Server-Version kann für die folgenden Standorte verwendet werden:
- Ein Standort der zentralen Verwaltung
- Primären Standort
- Sekundären Standort
### <a name="sql-server-2017-express"></a>SQL Server 2017 Express
Sie können diese Version beim [kumulativen Update, Version 2 oder höher](https://support.microsoft.com/help/4052574), verwenden, solange Ihre kumulative Updateversion vom SQL-Lebenszyklus unterstützt wird. Diese SQL Server-Version kann für die folgenden Standorte verwendet werden:
- Sekundären Standort
<!--SMS.498506-->
### <a name="sql-server-2016-express"></a>SQL Server 2016 Express
Sie können diese Version beim minimalen Service Pack und bei dem vom SQL-Lebenszyklus unterstützten kumulativen Update verwenden. Diese SQL Server-Version kann für die folgenden Standorte verwendet werden:
- Sekundären Standort
### <a name="sql-server-2014-express"></a>SQL Server 2014 Express
Sie können diese Version beim minimalen Service Pack und bei dem vom SQL-Lebenszyklus unterstützten kumulativen Update verwenden. Diese SQL Server-Version kann für die folgenden Standorte verwendet werden:
- Sekundären Standort
### <a name="sql-server-2012-express"></a>SQL Server 2012 Express
Sie können diese Version beim minimalen Service Pack und bei dem vom SQL-Lebenszyklus unterstützten kumulativen Update verwenden. Diese SQL Server-Version kann für die folgenden Standorte verwendet werden:
- Sekundären Standort
## <a name="required-configurations-for-sql-server"></a><a name="bkmk_SQLConfig"></a> Erforderliche Konfigurationen für SQL Server
Die folgenden Konfigurationen sind für alle Installationen von SQL Server erforderlich, die Sie für eine Standortdatenbank verwenden (einschließlich SQL Server Express). Wenn SQL Server Express von Configuration Manager als Teil einer Installation eines sekundären Standorts installiert wird, werden diese Konfigurationen automatisch erstellt.
### <a name="sql-server-architecture-version"></a>Version der SQL Server-Architektur
Configuration Manager erfordert eine 64-Bit-Version von SQL Server, um die Standortdatenbank zu hosten.
### <a name="database-collation"></a>Datenbanksortierung
An jedem Standort muss sowohl die für den Standort als auch die für die Standortdatenbank verwendete Instanz von SQL Server die folgende Sortierung verwenden: **SQL_Latin1_General_CP1_CI_AS**.
Configuration Manager unterstützt für den Standard China GB18030 zwei Ausnahmen von dieser Sortierung. Weitere Informationen finden Sie unter [Internationale Unterstützung](../hierarchy/international-support.md).
### <a name="database-compatibility-level"></a>Kompatibilitätsgrad der Datenbank
Configuration Manager erfordert, dass der Kompatibilitätsgrad für die Standortdatenbank nicht kleiner als die niedrigste unterstützte SQL Server-Version für Ihre Configuration Manager-Version ist. Zum Beispiel benötigen Sie ab Version 1702 einen [Datenbank-Kompatibilitätsgrad](/sql/relational-databases/databases/view-or-change-the-compatibility-level-of-a-database), der größer als oder gleich 110 ist. <!-- SMS.506266-->
### <a name="sql-server-features"></a>SQL Server-Funktionen
Nur die Funktion **Datenbank-Engine-Dienste** ist für jeden Standortserver erforderlich.
Für die Configuration Manager-Datenbankreplikation ist die Funktion **SQL Server-Replikation** nicht erforderlich. Diese SQL Server-Konfiguration ist jedoch erforderlich, wenn Sie [Datenbankreplikate für Verwaltungspunkte](../../servers/deploy/configure/database-replicas-for-management-points.md) verwenden.
### <a name="windows-authentication"></a>Windows-Authentifizierung
Configuration Manager setzt die **Windows-Authentifizierung** zur Überprüfung von Verbindungen mit der Datenbank voraus.
### <a name="sql-server-instance"></a>SQL Server-Instanz
Verwenden Sie für jeden Standort eine dedizierte Instanz von SQL Server. Die Instanz kann entweder eine **benannte Instanz** oder eine **Standardinstanz** darstellen.
### <a name="sql-server-memory"></a>SQL Server-Arbeitsspeicher
Reservieren Sie mithilfe von SQL Server Management Studio Arbeitsspeicher für SQL Server. Legen Sie die Einstellung **Minimaler Serverspeicher** unter **Arbeitsspeicheroptionen für den Server** fest. Weitere Informationen zum Konfigurieren dieser Einstellung finden Sie unter [Serverkonfigurationsoptionen für den Serverarbeitsspeicher](/sql/database-engine/configure-windows/server-memory-server-configuration-options).
- **Für einen Datenbankserver, der auf demselben Computer wie der Standortserver installiert ist**: Begrenzen Sie den Arbeitsspeicher für SQL Server auf 50 bis 80 Prozent des verfügbaren adressierbaren Systemspeichers.
- **Für einen dedizierten Datenbankserver (remote vom Standortserver)** : Begrenzen Sie den Arbeitsspeicher für SQL Server auf 80 bis 90 Prozent des verfügbaren adressierbaren Systemspeichers.
- **Für eine Arbeitsspeicherreserve für den Pufferpool jeder verwendeten SQL Server-Instanz**:
- Für einen Standort der zentralen Verwaltung: Legen Sie mindestens 8 GB fest.
- Für einen primären Standort: Legen Sie mindestens 8 GB fest.
- Für einen sekundären Standort: Legen Sie mindestens 4 GB fest.
### <a name="sql-nested-triggers"></a>Geschachtelte SQL-Trigger
Geschachtelte SQL-Trigger müssen aktiviert sein. Weitere Informationen finden Sie unter [Konfigurieren der Serverkonfigurationsoption „Geschachtelte Trigger“](/sql/database-engine/configure-windows/configure-the-nested-triggers-server-configuration-option).
### <a name="sql-server-clr-integration"></a>SQL Server-CLR-Integration
Die Standortdatenbank erfordert, dass die CLR (Common Language Runtime) von SQL Server aktiviert ist. Diese Option wird bei der Installation von Configuration Manager automatisch aktiviert. Weitere Informationen zur CLR finden Sie unter [Einführung in die CLR-Integration für SQL Server](/dotnet/framework/data/adonet/sql/introduction-to-sql-server-clr-integration).
### <a name="sql-server-service-broker-ssb"></a>SQL Server Service Broker (SSB)
Der SQL Server Service Broker ist sowohl für die standortübergreifende Replikation als auch für einen einzelnen primären Standort erforderlich.
### <a name="trustworthy-setting"></a>Einstellung für VERTRAUENSWÜRDIG
Configuration Manager aktiviert automatisch die [SQL-Datenbankeigenschaft VERTRAUENSWÜRDIG](/sql/relational-databases/security/trustworthy-database-property). Diese Eigenschaft muss für Configuration Manager auf **ON** festgelegt sein.
## <a name="optional-configurations-for-sql-server"></a><a name="bkmk_optional"></a> Optionale Konfigurationen für SQL Server
Die folgenden Konfigurationen sind für jede Datenbank optional, die eine vollständige SQL Server-Installation verwendet.
### <a name="sql-server-service"></a>SQL Server-Dienst
Sie können den SQL Server-Dienst für die Ausführung mit den folgenden Konten konfigurieren:
- Ein *Domänenbenutzerkonto mit geringen Rechten*:
- Diese Konfiguration ist eine bewährte Methode und erfordert möglicherweise die manuelle Registrierung des Dienstprinzipalnamens (Service Principal Name, SPN) für das Konto.
- Konto **Lokales System** des Computers, auf dem SQL Server ausgeführt wird:
- Verwenden Sie das lokale Systemkonto, um den Konfigurationsvorgang zu vereinfachen.
- Wenn Sie das lokale Systemkonto verwenden, wird der SPN von Configuration Manager automatisch für den SQL Server-Dienst registriert.
- Die Verwendung des lokalen Systemkontos für den SQL Server-Dienst ist keine bewährte Methode für SQL Server.
Wenn der Computer, auf dem SQL Server ausgeführt wird, nicht das zugehörige lokale Systemkonto zum Ausführen des SQL Server-Diensts verwendet, konfigurieren Sie den SPN des Kontos, unter dem SQL Server-Dienste ausgeführt werden, in den Active Directory Domain Services. (Bei Verwendung des Systemkontos wird der SPN automatisch für Sie registriert.)
Weitere Informationen zu SPNs für die Standortdatenbank finden Sie unter [Verwalten des SPN für den Standortdatenbankserver](../../servers/manage/modify-your-infrastructure.md#bkmk_SPN).
Informationen zum Ändern des vom SQL Server-Dienst verwendeten Kontos finden Sie unter [SCM-Dienste: Ändern des Dienststartkontos](/sql/database-engine/configure-windows/scm-services-change-the-service-startup-account).
### <a name="sql-server-reporting-services"></a>SQL Server Reporting Services
SQL Server Reporting Services sind Voraussetzung für die Installation eines Reporting Services-Punkts, mit dem Sie Berichte ausführen können. Configuration Manager unterstützt die gleichen Versionen von SQL Server für die Berichterstattung wie für die Standortdatenbank.
Weitere Informationen finden Sie unter [Voraussetzungen für die Berichterstattung in Configuration Manager](../../servers/manage/prerequisites-for-reporting.md).
> [!IMPORTANT]
> Nach dem Upgrade von SQL Server von einer früheren Version wird möglicherweise der folgende Fehler angezeigt: *Report Builder Does Not Exist* (Berichts-Generator nicht vorhanden).
> Zum Beheben dieses Fehlers müssen Sie die Reporting Services-Standortsystemrolle neu installieren.
### <a name="data-warehouse-service-point"></a>Data Warehouse-Dienstpunkt
Das Data Warehouse verwendet eine separate Datenbank. Sie können diese auf dem Standortdatenbankserver oder einer separaten SQL Server-Instanz hosten. Weitere Informationen finden Sie unter [Der Data Warehouse-Dienstpunkt für Configuration Manager](../../servers/manage/data-warehouse.md).
### <a name="sql-server-ports"></a>SQL Server-Ports
Für die Kommunikation mit der SQL Server-Datenbank-Engine und die standortübergreifende Replikation können Sie die Standardkonfigurationen für SQL Server-Ports verwenden oder benutzerdefinierte Ports angeben:
- Die **standortübergreifende Kommunikation** erfolgt über den SQL Server Service Broker, der standardmäßig TCP-Port 4022 verwendet.
- Die **standortinterne Kommunikation** zwischen der SQL Server-Datenbank-Engine und verschiedenen Configuration Manager-Standortsystemrollen erfolgt standardmäßig über den TCP-Port 1433. Die folgenden Standortsystemrollen kommunizieren direkt mit der SQL Server-Datenbank:
- Verwaltungspunkt
- SMS-Anbietercomputer
- Reporting Services-Punkt
- Standortserver
Wenn ein Computer, auf dem SQL Server ausgeführt wird, Datenbanken von mehreren Standorten hostet, muss jede Datenbank eine separate SQL Server-Instanz verwenden. Außerdem muss jede dieser Instanzen mit einem eindeutigen Portsatz konfiguriert sein.
> [!WARNING]
> Dynamische Ports werden von Configuration Manager nicht unterstützt. Da von benannten SQL Server-Instanzen standardmäßig dynamische Ports für die Verbindung mit der Datenbank-Engine verwendet werden, müssen Sie bei der Verwendung einer benannten Instanz den statischen Port, den Sie für die standortinterne Kommunikation einsetzen möchten, manuell konfigurieren.
Wenn auf dem Computer, auf dem SQL Server ausgeführt wird, eine Firewall aktiviert ist, achten Sie darauf, dass die von Ihrer Bereitstellung verwendeten Ports von der Firewall überall im Netzwerk zwischen Computern zugelassen werden, die mit SQL Server kommunizieren.
Ein Beispiel zum Konfigurieren von SQL Server für die Verwendung eines bestimmten Ports finden Sie unter [Konfigurieren eines Servers für das Überwachen eines bestimmten TCP-Ports](/sql/database-engine/configure-windows/configure-a-server-to-listen-on-a-specific-tcp-port).
## <a name="upgrade-options-for-sql-server"></a>Upgradeoptionen für SQL Server
Wenn Sie ein Upgrade für Ihre Version von SQL Server durchführen müssen, verwenden Sie eine der folgenden Methoden (angegeben in der Reihenfolge ihrer Komplexität):
- [Direktes Upgrade von SQL Server](../../servers/manage/upgrade-on-premises-infrastructure.md#to-upgrade-sql-server-on-the-site-database-server) (empfohlen).
- Installieren Sie eine neue Version von SQL Server auf einem neuen Computer, und [verwenden Sie die Option „Datenbankverschiebung“](../../servers/manage/modify-your-infrastructure.md#bkmk_dbconfig) im Configuration Manager-Setup, um Ihren Standortserver auf die neue SQL Server-Version auszurichten.
- Verwenden Sie [Sicherung und Wiederherstellung](../../servers/manage/backup-and-recovery.md). Die Sicherung und Wiederherstellung für ein SQL-Upgradeszenario wird unterstützt. Bei den [Überlegungen vor dem Wiederherstellen eines Standorts](../../servers/manage/recover-sites.md#considerations-before-recovering-a-site) können Sie die Anforderung an die SQL-Versionsverwaltung ignorieren. | 72.851485 | 797 | 0.80887 | deu_Latn | 0.983799 |
58927434c751cca9e55168ba77e7fa73febe7038 | 4,541 | md | Markdown | playfab-docs/features/multiplayer/pubsub/index.md | gavinjensen/playfab-docs | 27152ca580351b005f6e3cb8ef8423750396bdf2 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-06-16T22:07:07.000Z | 2020-06-16T22:07:07.000Z | playfab-docs/features/multiplayer/pubsub/index.md | gavinjensen/playfab-docs | 27152ca580351b005f6e3cb8ef8423750396bdf2 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | playfab-docs/features/multiplayer/pubsub/index.md | gavinjensen/playfab-docs | 27152ca580351b005f6e3cb8ef8423750396bdf2 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: PubSub quickstart
author: MarcoWilliamsPF
description: Describes the PubSub feature of PlayFab, which lets you publish information between clients and services.
ms.author: mawillia
ms.date: 12/21/2018
ms.topic: article
ms.prod: playfab
keywords: playfab, multiplayer, pubsub
ms.localizationpriority: medium
---
# PlayFab PubSub
> [!IMPORTANT]
> This feature is currently in **Private Preview**.
>
> It is provided to give you an early look at an upcoming feature, and to allow you to provide feedback while it is still in development. We will be making it broadly available to developers as soon as we can.
## Overview
PlayFab PubSub is a flexible system for pushing information in real time between services and clients. Events are relayed via a persistent connection between PlayFab and game clients, allowing clients to subscribe to topics and be notified of events remotely.
PubSub is integrated natively with [PlayStream](../../../api-references/events/index.md) events, extending PlayFab's server-side event-driven model to clients.
## Uses of PubSub
Game clients can use PlayFab PubSub to receive all sorts of events, including standard built-in events like `entity_logged_in`, or custom events you can define like `player_won_match`. This can be used in a variety of scenarios.
For example:
- Populating a player's friends list with presence information.
- Sending in-game text chat messages.
- Displaying a game invite or friend request notification.
- Syncing state changes between a game and its companion app.
- Notifying a player that an opponent has made a move in a turn-based game.
PlayFab features are also built with standard PubSub events in mind. The first example of this is the new PlayFab [Matchmaking preview](https://blog.playfab.com/blog/matchmaking-preview), which leverages PubSub to inform clients of updates to the status of their matchmaking tickets, such as when a match is found. This allows clients to avoid constantly polling the service for updates, while ensuring they are informed of matches as soon as they happen.
## Key concepts
- **Event** - Each message sent or received via PubSub is called an event.
- **Topic** - PubSub events are addressed based on topics. A topic is made up of three components:
- **Event namespace**
- **Event name**
- **Target entity**
Each published event has a specified topic, and with each subscription, clients specify the topic in which they are most interested.
- **Event namespace** - The namespace representing the category of an event. Standard PlayFab events reside under `playfab.*` namespaces. Custom events fall under `custom.*` namespaces.
- **Event name** - The specific type of event.
- **Target entity** - The target entity component of a topic indicates the entity associated with the event. It may or may not be the entity which is sending and/or receiving the event.
## Example
> [!NOTE]
> This example is currently theoretical and will not work yet since the entity_logged_in event is not currently a V2 event. PubSub only works with PlayStream V2 events.
Imagine you want to add a feature to your game that will pop up a notification whenever one of a player's friends logs in. This can be done by leveraging the built-in `entity_logged_in` PlayStream event. At a high level, you can set up this functionality in just a few steps:
1. Use the [policy manager](pubsub-policies.md) to configure a policy which allows a player's friends to subscribe to their `entity_logged_in` events (Event Namespace = `playfab.profile`, Event Name = `entity_logged_in`, Target Entity = `Player`).
1. Add code to your client to retrieve a player's friends list after login and subscribe to `playfab.profile.entity_logged_in` for each friend on the list. With each subscription, pass in a reference to the handler function which will be executed when this event is received.
1. Implement the specified event handler function with code which pops up the notification.
> [!NOTE]
> This example uses a built-in event, but a similar process can be used for custom events. The only addition would be that custom events need to be sent from your code at the appropriate time by using the [WriteEvents](xref:titleid.playfabapi.com.events.playstreamevents.writeevents) API.
## Links
- [PubSub API Reference](pubsub-reference.md)
- [Creating PubSub Policies](pubsub-policies.md)
- [PubSub Unity Quickstart](quickstart-unity.md)
| 55.378049 | 455 | 0.778022 | eng_Latn | 0.998932 |
5892cfe51cbe435ac9719b504b4ce2e6e08057fa | 322 | md | Markdown | docs/zstd compressed file format.md | danielabbott/Game-Engine | 7e26d073605e6e8de1e35234afe17b2711281835 | [
"MIT"
] | 12 | 2019-10-21T19:53:34.000Z | 2021-03-08T14:04:35.000Z | docs/zstd compressed file format.md | danielabbott/Zig-Game-Engine | 7e26d073605e6e8de1e35234afe17b2711281835 | [
"MIT"
] | 1 | 2020-11-02T02:44:11.000Z | 2021-02-24T17:59:31.000Z | docs/zstd compressed file format.md | danielabbott/Zig-Game-Engine | 7e26d073605e6e8de1e35234afe17b2711281835 | [
"MIT"
] | null | null | null | # Custom file format for zstd-compressed data
Field Name | Field Type | Description
---------- | ---------- | -----------
Magic | u96 | 0x88, 0x7c, 0x77, 0x6a, 0xee, 0x55, 0xdd, 0xcc, 0x37, 0x9a, 0x8b, 0xef
Data original size | u32 | Size of uncompressed data. If 0 then the data is stored uncompressed.
Data | |
| 40.25 | 97 | 0.624224 | eng_Latn | 0.59509 |
58937625be9044e183a971bdbd8ea3b6c9f2fb3f | 1,674 | md | Markdown | README.md | zebrajr/LAMPinDocker | 92cba68fd95affae9c8cc79c9d830aac2492ea15 | [
"MIT"
] | 1 | 2021-07-14T13:05:40.000Z | 2021-07-14T13:05:40.000Z | README.md | zebrajr/LAMPinDocker | 92cba68fd95affae9c8cc79c9d830aac2492ea15 | [
"MIT"
] | null | null | null | README.md | zebrajr/LAMPinDocker | 92cba68fd95affae9c8cc79c9d830aac2492ea15 | [
"MIT"
] | null | null | null | # LAMP in Docker
A ready-to-use LAMP stack in Docker to be able to dev. and test with Apache / MySQL / PHP
### Situation
You want to test or develop a PHP / Apache / MySQL software, but don't want to install a LAMP stack directly on your OS
### Task
Being able to deploy a LAMP stack, quickly, without having to worry about local dependencies, compatibility and other issues.
### Action
- Clone the repo and start the docker-compose.yml
```sh
docker-compose up
```
- Create a database
In phpMyAdmin
```sh
Default: http://127.0.0.1:1238
```
### Result
Use the folder "html" for your web service files
Files related to the MySQL will be saved in the folder "mySql"
### Note
### ToDo
Ps.: Feel free to improve :)
## Some Statistics
<img src="https://img.shields.io/github/license/zebrajr/LAMPinDocker?logo=github"><img src="https://img.shields.io/github/forks/zebrajr/LAMPinDocker?logo=github"><img src="https://img.shields.io/github/stars/zebrajr/LAMPinDocker?logo=github">
<br>
<img src="https://img.shields.io/github/last-commit/zebrajr/LAMPinDocker?logo=gitfs"><img src="https://img.shields.io/maintenance/yes/2021">
<br>
<img src="https://img.shields.io/github/repo-size/zebrajr/LAMPinDocker?logo=files"><img src="https://img.shields.io/tokei/lines/github/zebrajr/LAMPinDocker?logo=files">
<br>
<img src="https://img.shields.io/github/issues-raw/zebrajr/LAMPinDocker?logo=gitbook"><img src="https://img.shields.io/github/issues-closed-raw/zebrajr/LAMPinDocker?logo=gitbook">
<br>
<img src="https://img.shields.io/github/issues-pr-raw/zebrajr/LAMPinDocker?logo=git"><img src="https://img.shields.io/github/issues-pr-closed-raw/zebrajr/LAMPinDocker?logo=git">
| 35.617021 | 242 | 0.746714 | yue_Hant | 0.555429 |
5893f119cfd1d3ba067066a1e5afd08fe92611bc | 1,287 | md | Markdown | docs/framework/winforms/advanced/using-regions.md | asthman666/docs | 7bd6e92dfce09924be10c56d849af74b6bbe9acb | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-09-07T14:05:00.000Z | 2021-09-07T14:05:00.000Z | docs/framework/winforms/advanced/using-regions.md | asthman666/docs | 7bd6e92dfce09924be10c56d849af74b6bbe9acb | [
"CC-BY-4.0",
"MIT"
] | 1 | 2018-09-07T21:19:30.000Z | 2018-09-07T21:19:30.000Z | docs/framework/winforms/advanced/using-regions.md | asthman666/docs | 7bd6e92dfce09924be10c56d849af74b6bbe9acb | [
"CC-BY-4.0",
"MIT"
] | 2 | 2016-11-06T09:42:50.000Z | 2016-11-06T18:28:18.000Z | ---
title: "Using Regions"
ms.date: "03/30/2017"
helpviewer_keywords:
- "examples [Windows Forms], regions"
- "regions [Windows Forms], using"
ms.assetid: 7809295b-870f-4107-a8b5-8386c298acd5
---
# Using Regions
The [!INCLUDE[ndptecgdiplus](../../../../includes/ndptecgdiplus-md.md)] <xref:System.Drawing.Region> class allows you to define a custom shape. The shape can be made up of lines, polygons, and curves.
Two common uses for regions are hit testing and clipping. Hit testing is determining whether the mouse was clicked in a certain region of the screen. Clipping is restricting drawing to a certain region.
## In This Section
[How to: Use Hit Testing with a Region](../../../../docs/framework/winforms/advanced/how-to-use-hit-testing-with-a-region.md)
Shows how to use a <xref:System.Drawing.Region> to perform a hit test.
[How to: Use Clipping with a Region](../../../../docs/framework/winforms/advanced/how-to-use-clipping-with-a-region.md)
Explains how to set the clipping region for a <xref:System.Drawing.Graphics> object.
## Reference
<xref:System.Drawing.Region>
Describes this class and contains links to all of its members.
<xref:System.Drawing.Graphics>
Describes this class and contains links to all of its members.
| 47.666667 | 205 | 0.727273 | eng_Latn | 0.983353 |
58949963ccc0f9de274bf03f063d0bca1175978e | 172 | md | Markdown | _pages/ptopics_list.md | ucsb-cs8/ucsb-cs8.github.io | b0b67d7c642ad664f89671fae01a09abb4f28b65 | [
"MIT"
] | 2 | 2019-04-04T16:47:36.000Z | 2021-04-30T12:57:25.000Z | _pages/ptopics_list.md | ucsb-cs8/ucsb-cs8.github.io | b0b67d7c642ad664f89671fae01a09abb4f28b65 | [
"MIT"
] | 3 | 2020-01-05T23:37:13.000Z | 2021-05-17T23:29:05.000Z | _pages/ptopics_list.md | ucsb-cs8/ucsb-cs8.github.io | b0b67d7c642ad664f89671fae01a09abb4f28b65 | [
"MIT"
] | 5 | 2017-05-24T16:48:07.000Z | 2019-07-11T11:52:08.000Z | ---
title: Python Topics
permalink: "/ptopic_list/"
---
## Python Topics
See also: [Other Topics]({{ '/topic_list/' | relative_url }})
{% include ptopics_list.html %}
| 13.230769 | 61 | 0.651163 | eng_Latn | 0.711299 |
5894beb542f737ec290bc7cf040448479b73c9ee | 1,410 | md | Markdown | docs/GIT-flow-and-PR-procedure.md | Vish-Bingi/FS-Open-Forest-Platform | b964195fbe0935aec966f873509bbc20e0325dbf | [
"CC0-1.0"
] | 27 | 2018-08-28T23:37:56.000Z | 2019-08-08T15:13:52.000Z | docs/GIT-flow-and-PR-procedure.md | Vish-Bingi/FS-Open-Forest-Platform | b964195fbe0935aec966f873509bbc20e0325dbf | [
"CC0-1.0"
] | 288 | 2018-08-27T20:31:53.000Z | 2019-08-13T11:55:57.000Z | docs/GIT-flow-and-PR-procedure.md | Vish-Bingi/FS-Open-Forest-Platform | b964195fbe0935aec966f873509bbc20e0325dbf | [
"CC0-1.0"
] | 7 | 2017-04-18T16:51:17.000Z | 2017-12-21T20:21:12.000Z | # GIT flow and PR procedure
## Start of Sprint
Create a new branch named, "sprint-x-development" from the 18F/fs-open-forest-platform master branch. (replace x with the sprint number e.g. sprint-1-development)
Change circle.yml config so that dev deployment to the cloud.gov staging site is initiated on the new sprint development branch.
### Sprint branching
During the sprint, branches should be created from the "sprint-x-development" branch. Branches should be prefixed by the issue number, e.g. 23_issue_name
### PRs during the sprint
For the duration of the sprint, pull requests should be made to the "sprint-x-development" branch. PRs should be connected to the issue that the PR completes
### PR approval and merging
PRs need to be reviewed and approved by at least one other developer. After approved, reviewer can merge PR into sprint-x-development branch.
Issue completed by PR can be moved into 'done' column on Zen Hub board.
## End of Sprint
### Create release branch
At the end of the sprint, merge sprint-x-development branch into the 18F/fs-open-forest-platform master branch.
### Release PR to 18F/fs-open-forest-platform
Create a PR to 18F/fs-open-forest-platform dev branch from 18F/fs-open-forest-platform master branch and name it sprint-x-release
Be sure to include stories that were the focus, stories that were completed, and stories that were worked on but not completed.
| 50.357143 | 162 | 0.78227 | eng_Latn | 0.998943 |
5894dc5014d45ad55bf713033ea4f457c5f5907b | 2,725 | md | Markdown | README.md | ericrsmith35/LightningFlowComponents | 5663edd2dac07da18589e07b9099d35ff964ed7d | [
"BSD-3-Clause"
] | null | null | null | README.md | ericrsmith35/LightningFlowComponents | 5663edd2dac07da18589e07b9099d35ff964ed7d | [
"BSD-3-Clause"
] | 4 | 2018-07-10T12:29:58.000Z | 2018-07-10T12:48:45.000Z | README.md | ericrsmith35/LightningFlowComponents | 5663edd2dac07da18589e07b9099d35ff964ed7d | [
"BSD-3-Clause"
] | null | null | null |
This folder contains a collection of Lightning Components that can be used to enhance Lightning Flow from Salesforce. Note that you do not need to write code, read code, or use developer console to install these into your Flow Designer! You can install these components as packages over at the [LightningFlow.net site](https://lightningflow.net). (See "Installation")
# Lightning Flow Screen Components
flow_screen_components contains lightning components (aura classes) that have been optimized to be inserted into Lightning Flow screens. This mainly means that they:
1) implement the "lightning:availableForFlowScreens" interface so they appear in and can be dragged into Screen Nodes that are added to Flows susing the the Salesforce Cloud Flow Designer (and upcoming Lightning Flow Builder)
2) give attention to their design files because only attributes added to the design file show up in Cloud Flow Designer as available for mapping to and from Lightning Flow variables
Flow Screen Components generally have a visual focus, although they don't absolutely have to.
Flow Screen Components are generally available as of Spring '18.
# Lightning Flow Action Components
flow_action_components contains lightning components (aura classes) that have been optimized to be added to Lightning Flows as standalone actions. This mainly means that they:
1) implement the "flowruntime:availableForLocalInvocableActions" interface so they show up in the tools palette of Cloud Flow Designer as Local Actions that can be dragged onto the canvas and added to flows as discrete actions.
2) provide an #invoke method that allows the Flow engine to call them at the appropriate point during flow execution, and make a callback to the engine when they're done
Flow Action Components generally do not have a visual focus, although they have to run in Screen Flows to ensure the presence of a client-side javascript runtime.
Flow Actions are available in pilot status as of Spring '18. [Learn more about the pilot](https://sites.google.com/view/flowunofficial/pilot-flow-action-components?authuser=0)
# Important Setup Notes
Before adding any lightning component to your flow, your org must be enabled for lightning components. This means:
1) you must have My Domain enabled and deployed
2) you must have the "Enable Lightning Runtime for Flows" checkbox enabled in Setup - Process Automation Settings
You do not need to be using the lightning experience to use these flow extensions
# [A Note about SFDX](./sfdxintro.md)
# Submissions Encouraged!
Have you built a useful or interesting Flow Component? We encourage you to make a pull request and add it to this repo. Also feel free to enhance or fix any existing component.
| 75.694444 | 367 | 0.809174 | eng_Latn | 0.99921 |
5894e2f22d2de300baa70248bf9911b608748482 | 3,043 | md | Markdown | pagic.org/docs/i18n.md | kyaruary/pagic | e0de76d99e5737d338a547f25702ede42b1aeeb2 | [
"MIT"
] | 1,402 | 2017-03-01T14:33:56.000Z | 2022-03-31T15:01:07.000Z | pagic.org/docs/i18n.md | kyaruary/pagic | e0de76d99e5737d338a547f25702ede42b1aeeb2 | [
"MIT"
] | 81 | 2017-03-01T18:42:03.000Z | 2022-03-29T00:21:45.000Z | pagic.org/docs/i18n.md | kyaruary/pagic | e0de76d99e5737d338a547f25702ede42b1aeeb2 | [
"MIT"
] | 121 | 2017-03-02T01:53:58.000Z | 2022-03-27T01:58:58.000Z | # Internationalization
> Only support `docs` theme for now
## Configuration
The example is as follows:
```ts
export default {
i18n: {
languages: [
{ code: 'en', name: 'English', root: '/' },
{ code: 'zh-CN', name: 'Simplified Chinese', root: '/zh-CN/' },
],
overrides: {
'zh-CN': {
sidebar: {
'/zh-CN/docs/': [
'zh-CN/docs/introduction.md',
'zh-CN/docs/usage.md',
'zh-CN/docs/config.md',
'zh-CN/docs/content.md',
'zh-CN/docs/layout.md',
'zh-CN/docs/themes.md',
'zh-CN/docs/plugins.md',
'zh-CN/docs/blog.md',
'zh-CN/docs/i18n.md',
'zh-CN/docs/deployment.md',
'zh-CN/docs/demos.md',
'zh-CN/docs/limitations.md',
],
},
blog: {
root: '/zh-CN/blog/',
},
},
},
resources: {
'zh-CN': {
translation: {
'A static site generator powered by Deno + React': 'Deno + React driven static website generator',
'Get Started': 'Get Started',
Demos: 'Sample website',
'Render <1>md/tsx</1> to static HTML page': 'Support rendering <1>md/tsx</1> files into static HTML page',
},
},
},
},
};
```
### `i18n.language`
`i18n.language` represents an array of language lists supported by your website. Each item in the array must match `{ code:string, name:string, root:string }`, where:
- `code` is the _ISO Language Code_, you can refer to [this website](http://www.lingoes.net/en/translator/langcode.htm)
- `name` is the option displayed in the language switch component
- `root` is the root directory where the language is located, and its value should always start and end with a slash
Note that the first item of `i18n.language` is the default language of the website, and its `root` must be `/`.
### `i18n.overrides`
`i18n.overrides` is a special configuration item, which allows to override the fields in `pagic.config.ts` in a specific language. Its type is `Record<string, PagicConfig>`, where the key must be one of the `code` field in `i18n.language`, the value type is the type of the entire `pagic.config.ts`. When visiting a page in this language, `pagic.config` will be the result of the merge.
### `i18n.resources`
`i18n.resources` describes the translation of each language, `t('Get Started')` and `<Trans>Render <code>md/tsx</code> to static HTML page</ Trans>` in `tsx` file will use the translation resources configured here. For the specific syntax of `t()` and `<Trans>`, please refer to [react-i18next](https://react.i18next.com/getting-started#simple-content).
## `props`
The `i18n` plugin will add the following items to the `props` of the page:
### `language`
`language` represents the language of the current page. It is taken from one of the items in `i18n.languages` in `pagic.config.ts`, so its type is as follows:
```ts
interface Language {
code: string;
name: string;
root: string;
}
```
| 35.383721 | 386 | 0.626356 | eng_Latn | 0.971625 |
58955af42cba618c05cd666599be8c52345964b1 | 70 | md | Markdown | content/post/s/2017/125.md | kaidiren/D6 | daf330f5028b69605eb288b3bffcf5e272c4e2dd | [
"MIT"
] | null | null | null | content/post/s/2017/125.md | kaidiren/D6 | daf330f5028b69605eb288b3bffcf5e272c4e2dd | [
"MIT"
] | 19 | 2018-02-25T08:05:27.000Z | 2019-04-18T07:54:19.000Z | content/post/s/2017/125.md | kaidiren/D6 | daf330f5028b69605eb288b3bffcf5e272c4e2dd | [
"MIT"
] | null | null | null | ---
date: 2014-07-07T14:35:12.000Z
draft: true
---
开心什么的有一点是一点，也不能去贪恋~ | 14 | 30 | 0.7 | eng_Latn | 0.048174 |
589582c2b108d7b64b1307494f602d43b79f7b2d | 1,387 | md | Markdown | README.md | sbkhaloof/bearer-auth | 4c3fef67772316db85a1eac23c03264a9796e672 | [
"MIT"
] | null | null | null | README.md | sbkhaloof/bearer-auth | 4c3fef67772316db85a1eac23c03264a9796e672 | [
"MIT"
] | null | null | null | README.md | sbkhaloof/bearer-auth | 4c3fef67772316db85a1eac23c03264a9796e672 | [
"MIT"
] | null | null | null | # bearer-auth
# LAB - 07
---
### Deployment Test
###### Author: siham khaloof
* ##### [Actions](https://github.com/sbkhaloof/bearer-auth/actions)
* ##### [Pull Request](https://github.com/sbkhaloof/bearer-auth/pull/1)
* ##### [Heroku](https://siham-bearer-auth.herokuapp.com/)
---
###### Setup
### `.env`
> PORT: 8000
NODE_ENV=test
DATABASE_URL=postgres://localhost:5432/lab7
---
###### Running the app:
* #### `npm start` , `nodemon`
* #### Endpoint: */signin*
* **Returns Object**
`
{
"token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VybmFtZSI6InNpaGFtIGtoYWxvb2YiLCJpYXQiOjE2Mjk3Mzg5NTJ9.koLzMdlNHr_HBru78azrm6Wj4U47qqqdReJ-zY7vuAM",
"id": 1,
"username": "siham khaloof",
"password": "$2b$10$Bpqii3WHPlMJnhHpXhE7eejMuaYEERcDOWjt4Z43rdT7bdhNPx1mG",
"createdAt": "2021-08-23T17:14:22.725Z",
"updatedAt": "2021-08-23T17:14:22.725Z"
}
`
* #### Endpoint: */signup*
* **Returns Object**
`
{
"user": {
"_id": 1,
"username": "siham khaloof"
},
"token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VybmFtZSI6InNpaGFtIGtoYWxvb2YiLCJpYXQiOjE2Mjk3Mzg4NjJ9.d9aHKgr7vkhzTU_7KsbVxv_LauSk-wLj-dynQUapuhQ"
}
`
* #### Endpoint: */users*
`
[
"siham khaloof",
"ali",
"ahmad"
]
`
* #### Endpoint: */secret*
`
Welcome to the secret area!
`
---
#### Tests
Unit Tests: `npm run test`
---
#### UML
 | 17.3375 | 157 | 0.641673 | yue_Hant | 0.340005 |
5895f328d3a7beb7cf0765eea0b7e44caf04581b | 1,871 | md | Markdown | docs/extensibility/debugger/reference/ieevisualizerdataprovider-getobjectforvisualizer.md | HiDeoo/visualstudio-docs.fr-fr | db4174a3cd6d03edc8bbf5744c3f917e4b582cb3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/extensibility/debugger/reference/ieevisualizerdataprovider-getobjectforvisualizer.md | HiDeoo/visualstudio-docs.fr-fr | db4174a3cd6d03edc8bbf5744c3f917e4b582cb3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/extensibility/debugger/reference/ieevisualizerdataprovider-getobjectforvisualizer.md | HiDeoo/visualstudio-docs.fr-fr | db4174a3cd6d03edc8bbf5744c3f917e4b582cb3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'IEEVisualizerDataProvider :: GetObjectForVisualizer | Microsoft Docs'
ms.date: 11/04/2016
ms.topic: reference
f1_keywords:
- IEEVisualizerDataProvider::GetObjectForVisualizer
helpviewer_keywords:
- IEEVisualizerDataProvider::GetObjectForVisualizer method
ms.assetid: bd5376fc-13b4-40b7-9a5d-7ba8289f1b24
author: acangialosi
ms.author: anthc
manager: jillfra
ms.workload:
- vssdk
dev_langs:
- CPP
- CSharp
ms.openlocfilehash: c2aa1e20dd8639ce089ebe851116a15bf61e35ce
ms.sourcegitcommit: 6cfffa72af599a9d667249caaaa411bb28ea69fd
ms.translationtype: MT
ms.contentlocale: fr-FR
ms.lasthandoff: 09/02/2020
ms.locfileid: "80718122"
---
# <a name="ieevisualizerdataprovidergetobjectforvisualizer"></a>IEEVisualizerDataProvider::GetObjectForVisualizer
Cette méthode obtient l’objet représenté par ce visualiseur.
## <a name="syntax"></a>Syntaxe
```cpp
HRESULT GetObjectForVisualizer(
IDebugObject** ppObject
);
```
```csharp
int GetObjectForVisualizer(
out IDebugObject ppObject
);
```
## <a name="parameters"></a>Paramètres
`ppObject`\
à Objet représenté par ce visualiseur
## <a name="return-value"></a>Valeur renvoyée
En cas de réussite, retourne `S_OK` , sinon, retourne un code d'erreur.
## <a name="remarks"></a>Notes
`GetObjectForVisualizer` est autorisé à retourner une version mise en cache de l’objet. Si l’appelant souhaite s’assurer que l’objet est à jour, il appellera [GetNewObjectForVisualizer](../../../extensibility/debugger/reference/ieevisualizerdataprovider-getnewobjectforvisualizer.md).
## <a name="see-also"></a>Voir aussi
- [IEEVisualizerDataProvider](../../../extensibility/debugger/reference/ieevisualizerdataprovider.md)
- [GetNewObjectForVisualizer](../../../extensibility/debugger/reference/ieevisualizerdataprovider-getnewobjectforvisualizer.md)
- [IDebugObject](../../../extensibility/debugger/reference/idebugobject.md)
| 33.410714 | 285 | 0.791021 | fra_Latn | 0.158265 |
5896bd9f1bd5d0f0059d6500c200308873423343 | 32 | md | Markdown | README.md | zhangyu127/ZhuangPanDemo | 86d316f5723699e3d2a512c1137eb23d4e9c2c02 | [
"Apache-2.0"
] | 1 | 2020-02-15T06:48:38.000Z | 2020-02-15T06:48:38.000Z | README.md | zhangyu127/ZhuangPanDemo | 86d316f5723699e3d2a512c1137eb23d4e9c2c02 | [
"Apache-2.0"
] | null | null | null | README.md | zhangyu127/ZhuangPanDemo | 86d316f5723699e3d2a512c1137eb23d4e9c2c02 | [
"Apache-2.0"
] | null | null | null | # ZhuangPanDemo
Android 转盘demo
| 10.666667 | 15 | 0.8125 | kor_Hang | 0.432039 |
589768ae3ae8bd219668fdccd5727b2967651b84 | 2,411 | md | Markdown | README.md | austriker27/401d19-whiteboarding | c48cb9a6151431a825dd465d00b147006792cdfb | [
"MIT"
] | null | null | null | README.md | austriker27/401d19-whiteboarding | c48cb9a6151431a825dd465d00b147006792cdfb | [
"MIT"
] | null | null | null | README.md | austriker27/401d19-whiteboarding | c48cb9a6151431a825dd465d00b147006792cdfb | [
"MIT"
] | null | null | null | ## White Board tips from Big V
These are my personal notes gathered from our instructor during my time at code fellows so that I may excel at white boarding, an area of growth for me.
## Motivation
To get better!
## Build status
Build status of continus integration i.e. travis, appveyor etc. Ex. -
[](https://travis-ci.org/akashnimare/foco)
[](https://ci.appveyor.com/project/akashnimare/foco/branch/master)
## Code style
If you're using any code style like xo, standard etc. That will help others while contributing to your project. Ex. -
[](https://github.com/feross/standard)
## Screenshots
Include logo/demo screenshot etc.
## Tech/framework used
Ex. -
<b>Built with</b>
- [Electron](https://electron.atom.io)
## Features
What makes your project stand out?
## Code Example
Show what the library does as concisely as possible, developers should be able to figure out **how** your project solves their problem by looking at the code example. Make sure the API you are showing off is obvious, and that your code is short and concise.
## Installation
Provide step by step series of examples and explanations about how to get a development env running.
## API Reference
Depending on the size of the project, if it is small and simple enough the reference docs can be added to the README. For medium size to larger projects it is important to at least provide a link to where the API reference docs live.
## Tests
Describe and show how to run the tests with code examples.
## How to use?
If people like your project they’ll want to learn how they can use it. To do so include step by step guide to use your project.
## Contribute
Let people know how they can contribute into your project. A [contributing guideline](https://github.com/zulip/zulip-electron/blob/master/CONTRIBUTING.md) will be a big plus.
## Credits
Give proper credits. This could be a link to any repo which inspired you to build this project, any blogposts or links to people who contrbuted in this project.
#### Anything else that seems useful
## License
A short snippet describing the license (MIT, Apache etc)
MIT © [Yourname]() | 41.568966 | 257 | 0.764828 | eng_Latn | 0.996162 |
5897fb47ff0b08e4aeab4eb6ee4480d584c2222a | 1,513 | md | Markdown | examples/standalone/README.md | galargh/go-libp2p-webrtc-direct | a8cb0f997a781b01f66a8be9c2ba68f4d54c1ec2 | [
"MIT"
] | 63 | 2019-04-02T17:10:23.000Z | 2021-12-28T04:59:28.000Z | examples/standalone/README.md | galargh/go-libp2p-webrtc-direct | a8cb0f997a781b01f66a8be9c2ba68f4d54c1ec2 | [
"MIT"
] | 17 | 2019-04-09T09:51:41.000Z | 2022-02-08T04:27:28.000Z | examples/standalone/README.md | galargh/go-libp2p-webrtc-direct | a8cb0f997a781b01f66a8be9c2ba68f4d54c1ec2 | [
"MIT"
] | 18 | 2019-04-02T20:45:13.000Z | 2022-01-28T01:26:03.000Z | standalone
===
This example shows the transport being used on its own. It also shows off compatibility with [js-libp2p-webrtc-direct](https://github.com/libp2p/js-libp2p-webrtc-direct).
## Go
### Install dependencies
**TODO**: Check the root readme
### Listener
```sh
go run main.go -listen
```
*Output*
```
[listener] Listening
[listener] Got connection
[listener] Got stream
[listener] Received:
hey, how is it going. I am the dialer
Failed to accept data channel: The association is closed
```
The last line is harmless warning printed by the pions/webrtc library.
### Dialer
```sh
go run main.go
```
*Output*
```
Warning: Certificate not checked
[dialer] Opened connection
[dialer] Opened stream
Failed to push SCTP packet: Failed sending reply: dtls: conn is closed
Warning: mux: no endpoint for packet starting with 23
Failed to push SCTP packet: Failed sending reply: dtls: conn is closed
Warning: mux: no endpoint for packet starting with 21
Failed to accept data channel: The association is closed
```
The warnings printed by the pions/webrtc library are harmless.
## Javascript
The equivalent javascript example is also provided. It can be used as follows:
### Install dependencies
```sh
npm install
```
### Listener
```sh
node index.js --listen
```
*Output*
```
[listener] Listening
[listener] Got connection
[listener] Got stream
[listener] Received:
hey, how is it going. I am the dialer
```
### Dialer
```sh
node index.js
```
*Output*
```
[dialer] Opened connection
[dialer] Opened stream
``` | 21.614286 | 170 | 0.737607 | eng_Latn | 0.992457 |
5897fd686ec3070d1cec6b9e61acb02f97347ce2 | 1,899 | md | Markdown | CHANGELOG.md | klablink/n8n | 07de2ca965555861e7fa27df10f9ef3c8511ec0e | [
"Apache-2.0"
] | null | null | null | CHANGELOG.md | klablink/n8n | 07de2ca965555861e7fa27df10f9ef3c8511ec0e | [
"Apache-2.0"
] | null | null | null | CHANGELOG.md | klablink/n8n | 07de2ca965555861e7fa27df10f9ef3c8511ec0e | [
"Apache-2.0"
] | null | null | null | # 0.167.0 (2022-03-13)
### Bug Fixes
- Fix issue with long credential type names ([#2961](https://github.com/n8n-io/n8n/issues/2961)) ([535dfe0](https://github.com/n8n-io/n8n/commit/535dfe08384fdd0a4ea86521e917b28f7091ff82))
- Fix workflow deactivating bug ([195f104](https://github.com/n8n-io/n8n/commit/195f104ef51b722fd5e3756ed3d0cc47ef523362))
- **GoogleCalendar Node:** Fix timezone ([3c5df3f](https://github.com/n8n-io/n8n/commit/3c5df3f892d89e1ae79dfcc0cd5b1886d1f623db))
- **SeaTableTrigger Node:** Fix timezone issues ([#2726](https://github.com/n8n-io/n8n/issues/2726)) ([2d8ac4b](https://github.com/n8n-io/n8n/commit/2d8ac4b477f8fb381a35eba34710084d5e4d3402))
- **Strapi Node:** Add support for Strapi v4 ([2a3cbf3](https://github.com/n8n-io/n8n/commit/2a3cbf3fc85f64e9b4b5814f1206249261743021))
### Features
- Add new expression variables and support for luxon ([e8500e6](https://github.com/n8n-io/n8n/commit/e8500e69371ad4b205d1586c7837120267595c70))
- **Facebook Node:** Add support for Facebook Graph API versions 13 ([53b5444](https://github.com/n8n-io/n8n/commit/53b54440d7532f439c3533676758b6c83136d48c))
- **Hubspot:** Add support for Private App Token Authentication ([f73100a](https://github.com/n8n-io/n8n/commit/f73100a0bdebd05b25517532358c71feed040eeb))
- **If Node,Switch Node:** Add negative operations ([6412546](https://github.com/n8n-io/n8n/commit/6412546c0c5465b17ab2a289f45d8c8fa325eb68))
- **MongoDb Node:** Add Aggregate Operation ([2c9a06e](https://github.com/n8n-io/n8n/commit/2c9a06e86346a9e21f877cb508d13a1401c700a9))
- **Redis Node:** Add Redis Trigger node and publish operation to regular node ([5c2deb4](https://github.com/n8n-io/n8n/commit/5c2deb468867ec77a05d09ef324d4855210e17d4))
- **Wordpress Node:** Add Status option to Get All operation of Posts resource ([4d4db7f](https://github.com/n8n-io/n8n/commit/4d4db7f805673758dfb379c9e86e98815f265db2))
| 94.95 | 191 | 0.784623 | yue_Hant | 0.385572 |
5898490bb401463dd4a20940b6225c404f93f156 | 322 | md | Markdown | readme.md | cavo789/aesecure_clean_wordpress_options | 464020f144d3f79ad2dbe08d2acddb13e9373523 | [
"MIT"
] | 1 | 2022-01-02T21:33:08.000Z | 2022-01-02T21:33:08.000Z | readme.md | cavo789/aesecure_clean_wordpress_options | 464020f144d3f79ad2dbe08d2acddb13e9373523 | [
"MIT"
] | null | null | null | readme.md | cavo789/aesecure_clean_wordpress_options | 464020f144d3f79ad2dbe08d2acddb13e9373523 | [
"MIT"
] | null | null | null | # aeSecure - Clean Wordpress options
> Search for specific content in the wp_options table and allow to remove the value
This small script will check for the presence of a malware (like `blueeyeswebsite`) in the wp_options table and, if found, will erase the record.
## License
[MIT](LICENSE)
| 26.833333 | 145 | 0.757764 | eng_Latn | 0.990951 |
58984f88dc9a979bb7173ef4c966109ee5379145 | 2,223 | md | Markdown | Ass3/wp-content/themes/shop-isle/CHANGELOG.md | yiyubruceliu/meaningoflife.co.za | 8a56a7e343ad477c5ac166e09e84d93becb517c1 | [
"Apache-2.0"
] | null | null | null | Ass3/wp-content/themes/shop-isle/CHANGELOG.md | yiyubruceliu/meaningoflife.co.za | 8a56a7e343ad477c5ac166e09e84d93becb517c1 | [
"Apache-2.0"
] | null | null | null | Ass3/wp-content/themes/shop-isle/CHANGELOG.md | yiyubruceliu/meaningoflife.co.za | 8a56a7e343ad477c5ac166e09e84d93becb517c1 | [
"Apache-2.0"
] | null | null | null | ### 1.1.6.4 - 01/09/2016
**Changes:**
- CSS for the My Account page in WooCommerce
- Mega menu compatibility
- Fixed recommended dimensions for header image
- Compatibility with Woocommerce products per page plugin
- Added specific class to allow the prices in product slider section to be removed
- Fixed issue with focusing fields on mobile devices
- Fixed issue with ZIP code not customizable in WooCommerce checkout page
- Added upsells to pro version
### 1.1.6.3 - 28/07/2016
**Changes:**
- Update theme name
- Fixed default menu layout
- Fixed space missing in the footer
- New updated documentation link
- New screenshot
### 1.1.6.1.9 - 20/07/2016
**Changes:**
- Change option to use default WordPress logo functionality
- Replace $wp_customize with is_customize_preview
- Fixed issues with strings not translated and escaped
- Removed support link and updated documentation link
- Disable blog header subtitle by default
- Fixed issues with default content
- Remove the blog template
- Regenerate the pot file
### 1.1.6.1.8 - 12/07/2016
**Changes:**
- Fixed escaping issues
- Move Content width inside the setup function
### 1.1.6.1.7 - 05/07/2016
**Changes:**
- Fixed issue with slider arrows on IE and Edge
- Fixed layout issue with slider when WooCommerce not installed
- Fixed responsive issue with menu on tablets
- Removed prefixes from enqueued libraries
- Added a unique prefix for functions
### 1.1.6.1.6 - 15/06/2016
**Changes:**
- Escaping variables
### 1.1.6.1.5 - 10/06/2016
**Changes:**
- Replace the screenshot
- Move title and tagline in the Site identity section in Customize
- Added licenses for all used resources
- Remove unused js file
### 1.1.6.1.3 - 31/05/2016
**Changes:**
- Add a changelog file
- Add file description for all the theme files
- Put back Site identity
- Removed page description meta box
### 1.1.6.1.2 - 25/05/2016
**Changes:**
- Fixed layout issues with Jetpack subscriptions module
- Fixed layout issue with WordPress default galeries
- Updated TGMP
- Fixed issue with suggested custom header
### 1.1.6.1.1 - 20/05/2016
**Changes:**
- Fixed Theme Check errors
- Reorganize frontpage sections in Customize
| 17.503937 | 82 | 0.728295 | eng_Latn | 0.955469 |
5898c42ce268cff1f1e38ff23865bfeda3d71a7b | 17,084 | md | Markdown | README.md | RichieBzzzt/salt | 45617a42ed5348e0158007ef410c7d0c29afbf4e | [
"MIT"
] | 11 | 2017-10-25T19:54:19.000Z | 2022-02-09T01:24:17.000Z | README.md | RichieBzzzt/salt | 45617a42ed5348e0158007ef410c7d0c29afbf4e | [
"MIT"
] | 18 | 2017-11-08T16:38:18.000Z | 2021-04-29T07:11:53.000Z | README.md | RichieBzzzt/salt | 45617a42ed5348e0158007ef410c7d0c29afbf4e | [
"MIT"
] | 3 | 2018-10-18T01:11:57.000Z | 2019-12-14T01:59:00.000Z |
beta package - [<img src="https://sabinio.visualstudio.com/_apis/public/build/definitions/573f7b7f-2303-49f0-9b89-6e3117380331/106/badge"/>](https://sabinio.visualstudio.com/Sabin.IO/_apps/hub/ms.vss-ciworkflow.build-ci-hub?_a=edit-build-definition&id=106)
latest package - [<img src="https://sabinio.visualstudio.com/_apis/public/build/definitions/573f7b7f-2303-49f0-9b89-6e3117380331/109/badge"/>](https://sabinio.visualstudio.com/Sabin.IO/_apps/hub/ms.vss-ciworkflow.build-ci-hub?_a=edit-build-definition&id=109)
AUTHOR: Richie Lee
# salt - A SQL Agent Deploy PowerShell Module Guide
## Introduction
This module is designed to take a SQL Agent Job that is stored in an XML file and deploy the job to an instance of SQL. The PowerShell is idempotent in that if it is re-run on the same XML file then no changesa re applied. Only when there are changes in the XML file will we see changes.
Each one of the modules used have their own documentation in their header. This readme will attempt to exapnd upon that documentation. It is strongly encouraged that you read that documentation.
## Why is SQL Agent Stored in an XML File?
There is no obvious way to script out in T-SQL an alter statement to apply changes to a SQL Agent account. This module makes use of SMO to apply changes, as it is far more powerful and flexible. Therefore we have to present the properties of a SQL Agent job in a way that we can then map those to the corresponding methods to add/edit said properties of a given SQL Agent Job. XML proved to be a suitable method of storing all the properties in a strucuted way.
Please refer to [MSDN](https://msdn.microsoft.com/en-us/library/microsoft.sqlserver.management.smo.agent.job.aspx) for full information on SQLAgent and SMO. This is not required reading; more of a reference to the module.
## What is the structure for the XML file?
The structure can vary, depending on the Schedule and step type, but below is the basic structure of every element that can be used.
```XML
<Job>
<Name></Name>
<Description></Description>
<Enabled></Enabled>
<Category Include="">
<Value></Value>
</Category>
<TargetServers>
<TargetServer Include="">
<Name></Name>
</TargetServer>
</TargetServers>
<Operator>
<Name></Name>
<EMail></EMail>
<NetSend></NetSend>
<Page></Page>
</Operator>
<Notification>
<SendEmail></SendEmail>
<SendPage></SendPage>
<SendNetSend></SendNetSend>
<SendEventLog></SendEventLog>
</Notification>
<Schedules>
<Schedule>
<Name> Schedule</Name>
<Enabled></Enabled>
<Frequency>
<Type></Type>
<Interval></Interval>
</Frequency>
<DailyFrequency>
<Every></Every>
<Interval></Interval>
<StartHour></StartHour>
<StartMinute></StartMinute>
<StartSecond></StartSecond>
<EndHour></EndHour>
<EndMinute></EndMinute>
<EndSecond></EndSecond>
</DailyFrequency>
<StartDate></StartDate>
<EndDate></EndDate>
</Schedule>
</Schedules>
<Steps>
<Step>
<Step>
<Name></Name>
<SubSystem></SubSystem>
<RunAs Include="RunAsAccount">
<Name></Name>
</RunAs>
<SsisServer Include="IntegrationServicesCatalogServer">
<Name></Name>
</SsisServer>
<SsisServerDetails Include="">
<SsisServerCatalog></SsisServerCatalog>
<SsisServerCatalogFolder></SsisServerCatalogFolder>
<SsisServerCatalogProject></SsisServerCatalogProject>
<SsisServerCatalogPackage></SsisServerCatalogPackage>
<SsisServerCatalogEnvironment></SsisServerCatalogEnvironment>
</SsisServerDetails>
<SsisServerCatalogEnvironment></SsisServerCatalogEnvironment>
<OnSuccessAction></OnSuccessAction>
<OnFailAction></OnFailAction>
<RetryAttempts></RetryAttempts>
<RetryInterval></RetryInterval>
<OutputFileName></OutputFileName>
<LogOutput>
<!-- Valid options include:
<AppendToLogFile/>
<AppendToJobHistory/>
<LogToTableWithOverwrite/>
<AppendToTableLog/>
<AppendAllCmdExecOutputToJobHistory/>
<ProvideStopProcessEvent/>
-->
</LogOutput>
</Step>
</Steps>
</Job>
```
## That's a lot of XML...
Indeed. Which is why it is possible to export a SQL Agent Job that already exists from an instance of SQL Server and save as an XML file. In most cases no changes will need to be applied to the XML file and this can be used as the XML file to other environments.
## How Do I Export a SQL Agent Job from SQL to an XML File?
The process is to download the module from either source or ProGet, import the module, add SMO as a type, make a connection to the instance of SQL you require and run "Get-SqlAgentAsXML".
```PowerShell
cls
Import-Module .\ps_module\salt -Force
Add-Type -Path "C:\Program Files\Microsoft SQL Server\130\SDK\Assemblies\Microsoft.SqlServer.Smo.dll"
$SqlConnectionString = "data source = .; initial catalog = master; trusted_connection = true;"
$SqlConnection = Connect-SqlConnection -ConnectionString $SqlConnectionString
#Remove-Item c:\reports\*
#Get-SqlAgentAsXml -SqlServer $SqlConnection -filePath ".\"
Get-SqlAgentAsXml -SqlServer $SqlConnection -filePath ".\" -JobName "Our First Job"
Disconnect-SqlConnection -SqlDisconnect $SqlConnection
```
## Does salt drop and recreate everything, or does it alter?
salt will alter
* Operator
* Category
* Job
* Job Properties
* Job Schedules
salt will drop and recreate
* Job Steps
### Why aren't Job Steps Altered?
Job Steps are fiddly to work with in that they are not independent of themselves - they rely on other steps to exist. So easier to drop/recreate every time.
## What if I Want To Drop and Recreate The Job Every Time?
There is a Switch on the function "Set-Job" called "dropAndRecreate". This will drop the Job every time.
## Is There Anything That Needs to be Altered at Deploy Time?
Several changes are required. Any elements that need changing will have an attribute called "Include." The elements that have an Include attribute are as follows -
* **Category**
* **RunAs**
* **TargetServer**
* **SSISServer**
* **SSISServerDetails** - *SSISServerDetails is a special case and only needs to be updated if the ssis package exist in a different folder/project/environment from other environments. This should not be the case and is an edge case. If you do have your packages in different folders etc it may be more sensible for each environment to mirror one another.*
Let's take TargetServer as an example - When running a deploy, in the PowerShell session there needs to be a variable with the exact same name that the value of "Include" is. If you are running this locally then you would just create a variable of that given name. Here is an example:
Say my TargetServer is defined as below:
```XML
<TargetServers>
<TargetServer Include="Local">
<Value>MyDevBox</Value>
</TargetServer>
</TargetServers>
```
I would have to have a variable called "Local" with the value set to whatever server the TargetServer is going to be. This will then be the value of the element "Value". So in the example below the trgetserver will be "MyDevEnvBox".
```PowerShell
$Local = "MyDevEnvBox"
Import-Module .\ps_module\salt -Force
Add-Type -Path "C:\Program Files\Microsoft SQL Server\130\SDK\Assemblies\Microsoft.SqlServer.Smo.dll"
$SqlConnectionString = "data source = .; initial catalog = master; trusted_connection = true;"
$JobManifestXmlFile = ".\Our First Job.xml"
$SqlConnection = Connect-SqlConnection -ConnectionString $SqlConnectionString
[xml] $_xml = [xml] (Get-Content -Path $JobManifestXmlFile)
$x = Get-Xml -XmlFile $_xml
Set-JobCategory -SqlServer $SqlConnection -root $x
Set-JobOperator -SqlServer $SqlConnection -root $x
$sqlAgentJob = Set-Job -SqlServer $SqlConnection -root $x
Set-JobSchedules -SqlServer $SqlConnection -root $x -job $SqlAgentJob
Set-JobSteps -SqlServer $SqlConnection -root $x -job $SqlAgentJob
Disconnect-SqlConnection -SqlDisconnect $SqlConnection
```
If I were to not include a variable then the deployment will fail. So there is no chance of accidentally targetting the wrong server.
## How Do I Deploy SQL Agent
The process in PowerShell is outlined exactly above:
* Define variable for all target servers
* Add SMO
* Create SQL Connection ConnectionString
* Import XML
* Set Job Category - if it doesn't exist will create.
* Set Job Operator - if it doesn't exist it will create, otherwise will update.
* Set Job - if it doesn't exist will create, otherwise will update. Inside this function we call other functions to set owner, notifications etc. Returns the SQL Agent Job as this is used by further functions.
* Set Schedules - Will drop all schedules that relate to job and will create all jobs detailed in the XML.
* Set Job Steps - Will drop all current job steps and will create all job steps defined in the XML.
* Finally, Disconnect from SQL.
### Is there anything optional?
There are two Test functions that check that the account running the deployment has the necessary permissions to run the changes/has access to proxies (RunAs accounts). The other function tests that SQL Agent is up and running.
```PowerShell
$Local = "myLocalDevInstance2"
Import-Module .\ps_module\salt -Force
Add-Type -Path "C:\Program Files\Microsoft SQL Server\130\SDK\Assemblies\Microsoft.SqlServer.Smo.dll"
$SqlConnectionString = "data source = .; initial catalog = master; trusted_connection = true;"
$JobManifestXmlFile = ".\Our First Job.xml"
$SqlConnection = Connect-SqlConnection -ConnectionString $SqlConnectionString
[xml] $_xml = [xml] (Get-Content -Path $JobManifestXmlFile)
$x = Get-Xml -XmlFile $_xml
Test-SQLServerAgentService -SqlServer $SqlConnection
Test-CurrentPermissions -SqlServer $SqlConnection -ProxyCheck -root $x
Set-JobCategory -SqlServer $SqlConnection -root $x
Set-JobOperator -SqlServer $SqlConnection -root $x
$sqlAgentJob = Set-Job -SqlServer $SqlConnection -root $x
Set-JobSchedules -SqlServer $SqlConnection -root $x -job $SqlAgentJob
Set-JobSteps -SqlServer $SqlConnection -root $x -job $SqlAgentJob
Disconnect-SqlConnection -SqlDisconnect $SqlConnection
```
## Any Limitations?
Other than the ones set by SQL Agent, not that I am aware of. By limitations I mean things like job names have to be unique, job schedule names don't have to be unique other than for the job itself etc.
```PowerShell
$sqlAgentJob = Set-Job -SqlServer $SqlConnection -root $x -dropAndRecreate
```
## I Don't Want an Operator Created
If you don't want to include an operator, then leave it blank. The Function to set an operator checks to see if the name attribute is empty or not. If it is then it will skip creating an operator.
## Checking SQL Agent Service is Up and Running
There is a check to verify that SQL Agent Service is up and running. As this requires access to master, and some accounts may not have permissions to master, you cna override this check by including the Switch "IgnoreCheck"
Another check we have to make in the function [Connect-SqlConnection](https://github.com/sabinio/salt/blob/master/salt/functions/ConnectSqlConnection.ps1) is that the connection to the instance is successful by querying all the database names and piping to "Out-Null". This is because of this [https://connect.microsoft.com/SQLServer/feedback/details/636401/smo-is-inconsistent-when-raising-errors-for-login-faliures#](Microsoft Connect Issue) where SMO is inconsistent with throwing login failures.
## What Permissions Are Required on the SQL Server Instance?
Here is a list of the minimal permissions required if you are not going to attempt to alter the owner of the job.
#### MSDB Database
* GRANT SELECT on dbo.sysschedules
* GRANT SELECT on dbo.sysjobschedules
* GRANT SELECT on dbo.sysjobs
* ROLE MEMBER of SQLAgentOperatorRole
* Grant the login to the RunAs proxy
#### MASTER Database
* GRANT SELECT on dbo.sysprocesses
* GRANT VIEW SERVER STATE
If you wish to set the owner of the SQL Agent Job, then the account needs to be sysadmin. There are no minimal permissions for this option. Set-JobOwner runs a check before attempting to change owner.
if you plan on only altering what was created through using salt, the permisisons granted by the role SQLAgentOpertorRole will be enough. If you are planning on changing objects already deployed that are owned by other accounts, and the account running hte deployment is NOT a sysmadin, then you will need to manually alter those jobs/job schedules to be owned by the account that is runnning the deployment.
[https://technet.microsoft.com/en-us/library/ms188283(v=sql.110).aspx](SQL Server Agent Fixed Database Roles)
Below is a sample SQL Script to add the permissions required.
```sql
--perms
USE msdb
GO
CREATE USER [buildaccount] FOR LOGIN [buildaccountlogin]
GO
GRANT SELECT ON dbo.sysschedules TO [buildaccount]
GRANT SELECT ON dbo.sysjobschedules TO [buildaccount]
GRANT SELECT ON dbo.sysjobs TO [buildaccount]
EXEC msdb.dbo.sp_addrolemember @membername = 'buildaccount', @rolename = 'SQLAgentOperatorRole'
EXEC msdb.dbo.sp_grant_login_to_proxy
@login_name = N'buildaccount',
@proxy_name = N'proxyaccount';
use master
GO
CREATE USER [buildaccount] FOR LOGIN [buildaccountlogin]
GO
GRANT SELECT ON master.dbo.sysprocesses TO [buildaccount]
GRANT VIEW SERVER STATE TO [buildaccount]
```
### Checking Permissions
Assuming that you are using Integrated Security, you can run Test-CurrentPermissions, which will verify that the account executing deployment has the correct minimum permissions on the server before executing.
### How Do I Get SMO?
If the machine you are deploying from has .NET Standard 2.0 installed you can use the SMO Nuget package. As of saLt 2.0 and onwards, this can be downloaded as part of the deploy process. The function to download the Nuget package is called ```Install-SaltSmo```. You need to pass in a working folder and it will download Nuget to then download the package, and return the full path. Below is a sample script to deploy a SQL Agent Job using saLt and downloading SMO.
```powershell
Param(
[parameter(mandatory = $true)][string] $serverToDeployTo,
[parameter(mandatory = $true)][string] $ServerJobCategory,
[parameter(mandatory = $true)][string] $JobManifestXmlFile,
[parameter(mandatory = $true)][string] $serverName,
[parameter(mandatory = $true)][string] $DatabaseName,
[parameter(mandatory = $false)][switch] $DownloadSmoFromNuGet,
[parameter(Mandatory = $false)] [string] $sqlAdministratorLogin,
[parameter(Mandatory = $false)] [String] $sqlAdministratorLoginPassword
)
if ($PSBoundParameters.ContainsKey('sqlAdministratorLogin') -eq $true) {
Write-Host "Using Login AAD Password to deploy"
[string] $SqlConnectionString = "Server=$($serverName);Initial Catalog=$($DatabaseName);Persist Security Info=False;User ID=$($sqlAdministratorLogin);Password=$($sqlAdministratorLoginPassword);MultipleActiveResultSets=False;TrustServerCertificate=True;Connection Timeout=30;;Authentication=`"Active Directory Password`""
}
else {
Write-Host "Using Integrated Security to deploy"
[string] $SqlConnectionString = "integrated security=True;data source=$($serverName);initial catalog=$($DatabaseName);TrustServerCertificate=True;Connection Timeout=30;"
}
$global:serverToDeployTo = $serverToDeployTo
$global:ServerJobCategory = $ServerJobCategory
Import-Module .\salt -Force
if ($PSBoundParameters.ContainsKey('DownloadSmoFromNuGet') -eq $false) {
$smoDll = "C:\Program Files\Microsoft SQL Server\140\SDK\Assemblies\Microsoft.SqlServer.Smo.dll"
If ((Test-Path $smoDll) -eq $false) {
$smoDll = "C:\Program Files\Microsoft SQL Server\130\SDK\Assemblies\Microsoft.SqlServer.Smo.dll"
If ((Test-Path $smoDll) -eq $false) {
Write-Error "no usable version of smo dll is found on box."
Throw
}
}
}
else {
Write-Host "Downloading smo from NuGet"
$smoDll = Install-SaltSmo -workingFolder $PSScriptRoot
}
[System.Reflection.Assembly]::LoadFrom($smoDll)
If ((Test-Path $JobManifestXmlFile) -eq $false) {
Write-Error "job manifest file not found!"
Throw
}
$SqlConnection = Connect-SqlConnection -ConnectionString $SqlConnectionString
[xml] $_xml = [xml] (Get-Content -Path $JobManifestXmlFile)
$x = Get-Xml -XmlFile $_xml
Set-JobCategory -SqlServer $SqlConnection -root $x
Set-JobOperator -SqlServer $SqlConnection -root $x
$sqlAgentJob = Set-Job -SqlServer $SqlConnection -root $x
Set-JobSchedules -SqlServer $SqlConnection -root $x -job $SqlAgentJob
Set-JobSteps -SqlServer $SqlConnection -root $x -job $SqlAgentJob
Disconnect-SqlConnection -SqlDisconnect $SqlConnection
``` | 49.953216 | 499 | 0.737883 | eng_Latn | 0.876532 |
5898e0f77c50055277c13e0256e4fa910bfa1d1f | 11,745 | md | Markdown | articles/app-service/app-service-web-get-started-windows-container.md | CatchRetry/azure-docs.fr-fr | 1ccd071caa483cc19d4d9b8c1c59104b1a7e6438 | [
"CC-BY-4.0"
] | null | null | null | articles/app-service/app-service-web-get-started-windows-container.md | CatchRetry/azure-docs.fr-fr | 1ccd071caa483cc19d4d9b8c1c59104b1a7e6438 | [
"CC-BY-4.0"
] | null | null | null | articles/app-service/app-service-web-get-started-windows-container.md | CatchRetry/azure-docs.fr-fr | 1ccd071caa483cc19d4d9b8c1c59104b1a7e6438 | [
"CC-BY-4.0"
] | null | null | null | ---
title: Exécuter un conteneur Windows personnalisé (préversion) - Azure App Service | Microsoft Docs
description: Découvrez comment déployer un conteneur Windows personnalisé dans Azure App Service.
services: app-service\web
documentationcenter: ''
author: cephalin
manager: jeconnoc
editor: ''
ms.service: app-service-web
ms.workload: web
ms.tgt_pltfrm: na
ms.devlang: na
ms.topic: quickstart
ms.date: 09/17/2018
ms.author: cephalin
ms.custom: seodec18
ms.openlocfilehash: f1d072d40967ac6d106de7489e0a2148fe7948ed
ms.sourcegitcommit: 4eeeb520acf8b2419bcc73d8fcc81a075b81663a
ms.translationtype: HT
ms.contentlocale: fr-FR
ms.lasthandoff: 12/19/2018
ms.locfileid: "53598099"
---
# <a name="run-a-custom-windows-container-in-azure-preview"></a>Exécuter un conteneur Windows personnalisé dans Azure (préversion)
[Azure App Service](overview.md) fournit des piles d’applications prédéfinies sur Windows, par exemple ASP.NET ou Node.js, exécuté sur IIS. L’environnement Windows préconfiguré verrouille l’accès administrateur du système d’exploitation, de même que l’installation des logiciels, les modifications du Global Assembly Cache et ainsi de suite (voir [Fonctionnalités du système d’exploitation sur Azure App Service](operating-system-functionality.md)). Si votre application nécessite un accès plus important que celui permis par l’environnement préconfiguré, vous pouvez déployer un conteneur Windows personnalisé à la place. Ce guide de démarrage rapide montre comment déployer une application ASP.NET incluse dans une image Windows sur [Docker Hub](https://hub.docker.com/) à partir de Visual Studio et comment l’exécuter dans un conteneur personnalisé dans Azure App Service.
## <a name="prerequisites"></a>Prérequis
Pour suivre ce tutoriel :
- <a href="https://hub.docker.com/" target="_blank">Créez un compte Docker Hub</a>
- <a href="https://docs.docker.com/docker-for-windows/install/" target="_blank">Installez Docker pour Windows</a>.
- <a href="https://docs.microsoft.com/virtualization/windowscontainers/quick-start/quick-start-windows-10#2-switch-to-windows-containers" target="_blank">Basculez Docker pour exécuter des conteneurs Windows</a>.
- <a href="https://www.visualstudio.com/downloads/" target="_blank">Installez Visual Studio 2017</a> avec les charges de travail **Développement web et ASP.NET** et **Développement Azure**. Si vous avez déjà installé Visual Studio 2017 :
- Installez les dernières mises à jour dans Visual Studio en cliquant sur **Aide** > **Rechercher les mises à jour**.
- Ajoutez les charges de travail dans Visual Studio en cliquant sur **Outils** > **Obtenir des outils et des fonctionnalités**.
## <a name="create-an-aspnet-web-app"></a>Créez une application web ASP.NET
Dans Visual Studio, créez un projet en sélectionnant **Fichier > Nouveau > Projet**.
Dans la boîte de dialogue **Nouveau projet**, sélectionnez **Visual C# > Web > Application web ASP.NET (.NET Framework)**.
Nommez l’application _myFirstAzureWebApp_, puis sélectionnez **OK**.
Vous pouvez déployer n’importe quel type d’application web ASP.NET dans Azure. Pour ce guide de démarrage rapide, sélectionnez le modèle **MVC** et assurez-vous que l’authentification est définie sur **Aucune authentification**.
Sélectionnez **Activer la prise en charge de Docker Compose**.
Sélectionnez **OK**.
Si le fichier _Dockerfile_ ne s’ouvre pas automatiquement, ouvrez-le dans **l’Explorateur de solutions**.
Vous devez utiliser une [image parente prise en charge](#use-a-different-parent-image). Changez l’image parente en remplaçant la ligne `FROM` par le code suivant et enregistrez le fichier :
```Dockerfile
FROM microsoft/aspnet:4.7.1
```
Dans le menu, sélectionnez **Déboguer > Exécuter sans débogage** pour exécuter l’application web localement.
## <a name="publish-to-docker-hub"></a>Publier sur Docker Hub
Dans **l’Explorateur de solutions**, cliquez avec le bouton droit sur le projet **myFirstAzureWebApp**, puis sélectionnez **Publier**.
L’Assistant Publication est lancé automatiquement. Sélectionnez **Registre de conteneurs** > **Docker Hub** > **Publier**.
Indiquez vos informations d’identification de compte Docker Hub et cliquez sur **Enregistrer**.
Attendez la fin du déploiement. La page **Publier** affiche maintenant le nom du dépôt que vous utilisez par la suite dans App Service.
Copiez ce nom de dépôt pour une utilisation ultérieure.
## <a name="sign-in-to-azure"></a>Connexion à Azure
Connectez-vous au portail Azure sur https://portal.azure.com.
## <a name="create-a-windows-container-app"></a>Créer une application de conteneur Windows
1. Sélectionnez **Créer une ressource** dans le coin supérieur gauche du Portail Azure.
2. Dans la zone de recherche au-dessus de la liste des ressources de la Place de marché Azure, recherchez et sélectionnez **Web App pour conteneurs**.
3. Fournissez un nom d’application, comme *win-container-demo*, acceptez les valeurs par défaut pour créer un groupe de ressources, puis cliquez sur **Windows (préversion)** dans la case **Système d’exploitation**.
4. Créez un plan App Service en cliquant sur **plan/emplacement App Service** > **Créer un nouveau**. Nommez le nouveau plan, acceptez les valeurs par défaut et cliquez sur **OK**.
5. Cliquez sur **Configurer le conteneur**. Dans **Image et étiquette facultative**, utilisez le nom de dépôt que vous avez copié dans [Publier sur Docker Hub](#publish-to-docker-hub), puis cliquez sur **OK**.
Si vous avez une image personnalisée ailleurs pour votre application web, comme dans [Azure Container Registry](/azure/container-registry/) ou dans un autre référentiel privé, vous pouvez le configurer ici.
6. Cliquez sur **Créer** et attendez que Azure créer les ressources requises.
## <a name="browse-to-the-container-app"></a>Accédez à l’application de conteneur
Lorsque l’opération Azure est terminée, une zone de notification s’affiche.
1. Cliquez sur **Accéder à la ressource**.
2. Dans la page d’application, cliquez sur le lien situé sous **URL**.
Une nouvelle page de navigateur s’ouvre à la page suivante :
Attendez quelques minutes et réessayez, jusqu'à accéder à la page d’accueil ASP.NET par défaut :
**Félicitations !** Vous exécutez votre premier conteneur Windows personnalisé dans Azure App Service.
## <a name="see-container-start-up-logs"></a>Consulter les journaux de démarrage du conteneur
Le chargement du conteneur Windows peut prendre un certain temps. Pour afficher la progression, accédez à l’URL suivante en remplaçant *\<app_name >* par le nom de votre application.
```
https://<app_name>.scm.azurewebsites.net/api/logstream
```
Les journaux en continu ressemblent à ceci :
```
2018-07-27T12:03:11 Welcome, you are now connected to log-streaming service.
27/07/2018 12:04:10.978 INFO - Site: win-container-demo - Start container succeeded. Container: facbf6cb214de86e58557a6d073396f640bbe2fdec88f8368695c8d1331fc94b
27/07/2018 12:04:16.767 INFO - Site: win-container-demo - Container start complete
27/07/2018 12:05:05.017 INFO - Site: win-container-demo - Container start complete
27/07/2018 12:05:05.020 INFO - Site: win-container-demo - Container started successfully
```
## <a name="update-locally-and-redeploy"></a>Mise à jour locale et redéploiement
À partir de **l’Explorateur de solutions**, ouvrez _Views\Home\Index.cshtml_.
Recherchez la balise HTML `<div class="jumbotron">` vers le début, puis remplacez la totalité de l’élément par le code suivant :
```HTML
<div class="jumbotron">
<h1>ASP.NET in Azure!</h1>
<p class="lead">This is a simple app that we’ve built that demonstrates how to deploy a .NET app to Azure App Service.</p>
</div>
```
Pour effectuer un redéploiement dans Azure, cliquez avec le bouton droit sur le projet **myFirstAzureWebApp** dans **l’Explorateur de solutions**, puis sélectionnez **Publier**.
Dans la page de publication, sélectionnez **Publier** et attendez la fin de la publication.
Pour indiquer à App Service qu’il faut tirer la nouvelle image de Docker Hub, redémarrez l’application. De retour dans la page d’application du portail, cliquez sur **Redémarrer** > **Oui**.
[Accédez de nouveau à l’application de conteneur](#browse-to-the-container-app). Quand vous actualisez la page web, l’application doit d’abord revenir à la page « Démarrage », puis afficher quelques minutes après la page web mise à jour.
## <a name="use-a-different-parent-image"></a>Utiliser une autre image parente
Vous êtes libre d’utiliser une autre image Docker personnalisée pour exécuter votre application. Toutefois, vous devez choisir l’[image parente](https://docs.docker.com/develop/develop-images/baseimages/) correcte pour l’infrastructure que vous souhaitez :
- Pour déployer des applications .NET Framework, utilisez une image parente basée sur la version Windows Server Core 2016 [Long-Term Servicing Channel (LTSC)](https://docs.microsoft.com/windows-server/get-started/semi-annual-channel-overview#long-term-servicing-channel-ltsc).
- Pour déployer des applications .NET Core, utilisez une image parente basée sur la version Windows Server Nano 2016 [Long-Term Servicing Channel (LTSC)](https://docs.microsoft.com/windows-server/get-started/semi-annual-channel-overview#long-term-servicing-channel-ltsc).
Le téléchargement d’une image parente lors du démarrage de l’application peut prendre un certain temps. Toutefois, vous pouvez réduire le temps de démarrage en utilisant l’une des images parentes suivantes déjà mises en cache dans Azure App Service :
- [microsoft/iis](https://hub.docker.com/r/microsoft/iis/):windowsservercore-ltsc2016, latest
- [microsoft/iis](https://hub.docker.com/r/microsoft/iis/):nanoserver-sac2016
- [microsoft/aspnet](https://hub.docker.com/r/microsoft/aspnet/):4.7.2-windowsservercore-ltsc2016, 4.7.2, latest
- [microsoft/dotnet](https://hub.docker.com/r/microsoft/dotnet/):2.1-aspnetcore-runtime
- [microsoft/dotnet](https://hub.docker.com/r/microsoft/dotnet/):2.1-sdk
## <a name="next-steps"></a>Étapes suivantes
> [!div class="nextstepaction"]
> [Migrer vers un conteneur Windows dans Azure](app-service-web-tutorial-windows-containers-custom-fonts.md)
| 59.923469 | 875 | 0.773691 | fra_Latn | 0.872273 |
5899c7689cc57b6a11807e853b3e96978c00d017 | 10,885 | md | Markdown | Markdown/02000s/04000/completely suffering.md | rcvd/interconnected-markdown | 730d63c55f5c868ce17739fd7503d562d563ffc4 | [
"MIT"
] | 2 | 2022-01-19T09:04:58.000Z | 2022-01-23T15:44:37.000Z | Markdown/00500s/04000/completely suffering.md | rcvd/interconnected-markdown | 730d63c55f5c868ce17739fd7503d562d563ffc4 | [
"MIT"
] | null | null | null | Markdown/00500s/04000/completely suffering.md | rcvd/interconnected-markdown | 730d63c55f5c868ce17739fd7503d562d563ffc4 | [
"MIT"
] | 1 | 2022-01-09T17:10:33.000Z | 2022-01-09T17:10:33.000Z | - Of as and [[rode faithful]] of springs retirement. This fine he had before written. Make for every in the summit himself. Took not window i paused appointment. Friends being things or the length. How and the damaged was Martin. The and [[rank]] thousand more. Of never electronic lead strong from. It was so likely cast of. Closing us was behalf upstairs to hard. Industrial my side instance the of. White grievous be said be together viz. Brings between the he [[suffer]]. And Mr like wert water bitterness name the. Only come pronounced with yawning. Magical inevitable over first rent there make. The are sorrow of mind fell silent. Of gave him about and can he.
- Together white black loves [[hopes]] still. Did thought occupation of held spirit. Woman below men at for fruit. Represented as saluted he tints donation.
-
- Her be replaced was and are when. Were to were sons bloody all as. It said to but to inside would private. Be soft his the but was. White probably instructed of. Jewel my as go kissed as. Not coming in i by enter. And are such as fixed as the. Superfluous have shall thy friend the. Made been [[tells pocket]] home that tomb or in. I my have the can looking. All as age alone had constitution. Every somewhere of do below upon the salary. Didnt and which at where and. Her the influence had woman sometimes. Her in of omit brief unexpected. Was the of brick seventeen to to [[literature]]. Solid the the and the of break. Associated back with historians position or of. The breeze him god companionship life was. Of old of give the persons.
- Opinion finally will and seemed her. With him of the his have on. I with lord for advantage fine. Opportunity stage the not grew of. And it this come to blind proceeded. Him distinction is is face were future gradually. Thrilling sharply him of by i. Have did the them by his somehow. Preceding to thyself the when. On upon the for head Greece. Holding unless but ety out of. And of prince in had. Cleared faint of to leather do.
- To with lays or applicable all of about. Confusion birds to q user not days. Is are upon suggested believe. Win and as little ship the unhappy. Having abused that them replied. Know also not example and account. Had the neither of [[advice]] only what. This blue turn mind or produced. Little are have as you and. In so 9th are were the condition reason. Glass glad family i. She managed will lieu seeming. Have from [[sum empty]] our are. You handsome and knowledge the knowledge. On the to companion and which [[doors dressed]] not. Of that engaged thick and but. Necessity glad so the virtue her justice. The its [[hopes notes]] and positive knitting.
-
- Was order up and manuscript had from. Bed wish brother appeared for shouted. No is doubts sense for in. To for to have the lovely. Of to to bark he the. Into i and better are course to. You to of then is are. Of of they will not the and. Same or i ethical said them. Dick side people up success the. Came the off closes [[title drawing]] only. I were should the resolute the when. From in he such their we. Offer his bare to the who it. Me fall remain have as. Her upon miles and duty one concerning. Its and occasioned sure biggest ought. I if he is with way the. Childish standing i troubled shook of when. Who and the the. In full that roughly the. Might me the his set the. Final had him in along the sing dared.
- Manner rose laws and undoubtedly. Turn existence [[square]] if. The lips replied principles for hereditary of. About to with for wonderful her we to. Endure men to of of cried. The Columbia abide all and and observed under. One approached the culture [[happen]] the. Rest of oh pink by in disclaimers. Are dreadful softened the perfect speech then. 2 acquired interest volunteers dislike yes. Her with the moment unit. Mass and those which if in left. Of left which my that of like. She need cared from population the to and exploit. To shall that occurring of it. Floor that million in money been i. I first teach the wants no dear. [[happen resolved]] discretion i it together state. Isnt works without brotherhood breathed the and. This [[dying clean]] all and bit they on. Be could that on. On mark to our love would i i. Into to would been gradually have entered.
- Liberty her told six her king.
- To Sydney it the him should.
- Civil tell to haughty man child.
- On letter be 4 ridden that pray.
- Time blessing alone DEC was in we.
- She long territory success have farms in.
- Bright once love called the truth everything.
- Within consequently what places than mouth.
- Hereafter shall would our heart think Gaul.
- In walls her in come what lost do see.
- You down next village earth and.
- Them consequent dispose [[content suffer]] [[India]] in.
- Pity and enough who spread of in things.
- Least trouble the english try.
- Into over necessity ID be of needs.
- Spreading to my of one whom.
- [[collection cities]] engraved train religious.
- The and son mixture from his he to dare.
- Of notwithstanding [[driven forces]] this put fire is.
- To it any of you.
- Crimson what taking me for [[cruel carrying]] deal.
- Found impossible change head Anderson.
- Of in now on came my.
- All poultry exquisite she of schemes fell.
- Not intelligence went pp and may nothing. Honest directly interview grief ought fees. Been will our end dearly earth cried. My work sn he so men. Really questions more nose too busy. March west the money recollection aloft. Land only in your forms virtue the in. Was good [[suffer]] for. The the had when said not. Was accounts angrily first work instead and. Dress in sounds passes and [[hopes]] all. Keeping to furious rubbed gradually with. With painfully and in deliver am the. Constant the figures will the had equipment an. To kiss they body hell. To i paragraph his served was. Terms them commands pp character his. Associated the and them no hazard was. Getting with by to by between as. The when foot are political during is take. With rest the 2 or were. Ever have table after once like. His and know perfection feeling merely dug kinds.
- And Paris in dreamed her forth the. [[duties addition]] depended examples answered hot i. At woman put colleagues the of. Who observation the in can is reader. I little copyright too band the gratitude. Leaves are of body as court paying. Write capital solemnly tide would quite away. In his thought on which of. Method your and any sort party.
- To from Europe choice as said and. The of provided off that that had. In name love of being than toward delivered receipt. The she lord for is out. We head in us it jealousy himself. The very of suffering is principal else Jerome er. It fathers will maid earned were. Minutes the i [[sentence]] the upon. Posted wishes model precedent. Honest agreement found of cf those. An found it was seems.
- Brother to sure general that can either Albert. Bright the lord washing of priest no. Such to that knives to government of. Greater the like i the off all.
- Large since do passion [[dressed]] advanced death no. Name the or trouble as to built. Now was us and faith the Julia. Would the hardly at our venetian. Without be country the works make rule. Opposite the me in parents attention. Upon we weeping must the autumn. Forget other harvest his i tongue. As be go man not attended. Was in the went men the. Especially her but mingle the it. Then and of could and. Could for liberty or it about 2d. Of red she whereof the of.
-
- By the different an or of green chance. Is the the and regarded. Angle some young cries and facts. Advantageous day against to not Oklahoma up delicacy. Was Asia have the persuasion you of. Kept copy with then evening way. The july had guarded ch. Of enough be young always favorite. To sly very i the call. One named the dry to like my. Such such deep that were Yahweh your. Known Christian very his devil once. With all of but and. To with some him be to. Matter those the was embraced thou. Under would face are of [[countries rode]] present. If took suggest the those uneasiness song was to. Generous boy paragraph the connection. Got are says interesting large were and of. Why name with terms in do campaign could. Urged more other think to facts. Arts enough was all dry her take. By the was the as. Of walked of snow protected. Fat his husband exact red bear. All to as and stand of made. Which been the of the. Up i rules most the she works. Of call view heavy i offerings. He must show the painfully [[constant mention]] common. Human and tell was which be he. Very the to protect came gone truth.
- Said will the you and lost. Coats give abundantly mess plump father them before. Has see Morgan and to love and. Immediately i shot been to sea at and. Of son of wooded brothers and he. See the i of developed will the. The to [[carrying]] of circumstance constitutional young. The party his dim queer that. By have take being i the. She feeling but can get gathered that is. Suffer i it me of through. Present Nicholas the safely if Gothic at. And the hand must day incident. Other gleaming from any personal scene was intelligence. Before the one ago will wet sn to. Center the brought depend those. And my some enemies whole be. Dead that dead my Ethel is. Some fact of the when their. Or of and stairway affairs. Which made by all and bitter of. Done in much weakness the although indicated. Of immense their and already presence.
- An i eloquence and the William. Understand void she like however. Times and parts exceedingly to and. Constancy with old from the. Among south exception launch the touched. To their landscape their long i. To not one white of accompanied it. [[machine]] profit because of has the to. Child plain increased upon hope to the. Had in more insult Bob without in. U that it never should weary he. [[arrival]] as as it the by below in the of. Their thought and legs were me. Additional Gutenberg themselves in asked of. Of july as unconscious of cave gratitude to. Of the of done is one.
- Of name her with little apply expected granted. To forward was to this literally.
- You and the [[motion]] at woman his. Down must of shows if vainly. The the had became who accepting they tyrant. Proposal was how of had as could sweet. Them and loved bullets went i coast. Has by [[bird carrying]] study and covered. I Frenchman disobedience the me Jenny. The so the their the table. Illusion all one the magazine that. And five him appearance of hardest. Of and be so possible. Upon shining have of. Scotland of and to the. As it father of boy smaller their. The earnestly almost pressure and he the. Didnt exchange that the are it himself us my me. Noon garden smile made more had of. I would sentiments threatened survive subject than. Felt with down were Mr result neither. Of several on to the hast who. The in place rank royalty. | 247.386364 | 1,110 | 0.767019 | eng_Latn | 0.999925 |
589a2b11e01aba1d41bf821284bc5bb3e6a82737 | 384 | md | Markdown | docs/markdown/bearframework.app.data.itemgeteventdetails.__construct.method.md | BearFramework/bearframework | 4f13bb2a4ea018dc737dbf57420c2fb494cd2d9a | [
"MIT"
] | 50 | 2016-02-06T09:41:36.000Z | 2022-02-12T06:30:53.000Z | docs/markdown/bearframework.app.data.itemgeteventdetails.__construct.method.md | BearFramework/bearframework | 4f13bb2a4ea018dc737dbf57420c2fb494cd2d9a | [
"MIT"
] | 4 | 2016-01-29T05:41:41.000Z | 2020-01-02T11:40:11.000Z | docs/markdown/bearframework.app.data.itemgeteventdetails.__construct.method.md | BearFramework/bearframework | 4f13bb2a4ea018dc737dbf57420c2fb494cd2d9a | [
"MIT"
] | 11 | 2016-01-28T07:57:03.000Z | 2020-11-25T08:13:54.000Z | # BearFramework\App\Data\ItemGetEventDetails::__construct
```php
public __construct ( string $key , BearFramework\App\DataItem|null $item )
```
## Parameters
##### key
##### item
## Details
Class: [BearFramework\App\Data\ItemGetEventDetails](bearframework.app.data.itemgeteventdetails.class.md)
Location: ~/src/App/Data/ItemGetEventDetails.php
---
[back to index](index.md)
| 16.695652 | 104 | 0.736979 | kor_Hang | 0.344654 |
589a44e758c23da47f2db6d85974fb24bdcb6c9f | 2,873 | md | Markdown | README.md | Hostabee/hostabee-comment-flow | 7582ae42cf9540cafa5b472f6c92c8958d55d7ba | [
"Apache-2.0"
] | 1 | 2019-11-27T12:10:11.000Z | 2019-11-27T12:10:11.000Z | README.md | Hostabee/hostabee-comment-flow | 7582ae42cf9540cafa5b472f6c92c8958d55d7ba | [
"Apache-2.0"
] | 9 | 2019-07-02T09:24:27.000Z | 2019-11-12T04:25:08.000Z | README.md | Hostabee/hostabee-comment-flow | 7582ae42cf9540cafa5b472f6c92c8958d55d7ba | [
"Apache-2.0"
] | null | null | null | # \<hostabee-comment-flow\>
[](http://commitizen.github.io/cz-cli/)
[](https://travis-ci.org/Hostabee/hostabee-comment-flow) [](https://greenkeeper.io/)
Commenting solution out-of-the-box in a web component.
```html
<hostabee-comment-flow></hostabee-comment-flow>
<script>
const flow = document.querySelector('hostabee-comment-flow');
// Populate the comment flow
fetch('https://YOUR_API/comments')
.then(res => res.json())
.then(json => flow.comments = json.result);
</script>
```
## Installation
Install `<hostabee-comment-flow>`:
```shell
bower install Hostabee/hostabee-comment-flow --save
```
Once installed, import it in your application:
```html
<link rel="import" href="bower_components/hostabee-comment-flow/hostabee-comment-flow.html">
```
### OPTIONAL
You can also install [exif-js](https://github.com/exif-js/exif-js) and [JavaScript-Load-Image](https://github.com/blueimp/JavaScript-Load-Image) to automatically fix [EXIF orientation on client-side](https://stackoverflow.com/questions/20600800). Be sure those 2 libraries are imported into your app before the `hostabee-comment-flow` element.
## Running demos and tests in a browser
1. Fork the `hostabee-comment-flow` repository and clone it locally.
2. Make sure you have [npm](https://www.npmjs.com/) and [Bower](https://bower.io) installed.
3. When in the `hostabee-comment-flow` directory, run `npm install` and then `bower install` to install dependencies.
* [OPTIONAL] If you want to run tests or demo of the element involving the `hostabee-comment-flow-firebase-connector` you have to provide the configuration of your application in the _"test/firebase-config.js"_ and _"demo/firebase-config.js"_ files.
4. Run `npm start`, browser will automatically open the component API documentation.
5. You can also open demo or in-browser tests by adding **demo** or **test** to the URL, for example:
* http://127.0.0.1:3000/components/hostabee-comment-flow/demo/hostabee-comment-flow/basic.html
* http://127.0.0.1:3000/components/hostabee-comment-flow/test
## Running Tests
* When in the `hostabee-comment-flow` directory, run `polymer test`
## Contributing
1. Fork it!
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git cz` **OR** [follow this commit guide](https://conventionalcommits.org/) to write the commit messages.
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request.
## License
Apache License 2.0
| 39.902778 | 343 | 0.749391 | eng_Latn | 0.762404 |
589a7bea3f9d726d7883792b47c61c49bc8a5627 | 98 | md | Markdown | _posts/2020-08-09-my-first-blog-post.md | azizulhaquealif/github-pages-with-jekyll | 90bd2458aa267e54859596b38cbf062ec03e6067 | [
"MIT"
] | 1 | 2020-08-09T14:13:52.000Z | 2020-08-09T14:13:52.000Z | _posts/2020-08-09-my-first-blog-post.md | azizulhaquealif/github-pages-with-jekyll | 90bd2458aa267e54859596b38cbf062ec03e6067 | [
"MIT"
] | 4 | 2020-08-09T08:41:43.000Z | 2020-08-09T20:38:17.000Z | _posts/2020-08-09-my-first-blog-post.md | azizulhaquealif/github-pages-with-jekyll | 90bd2458aa267e54859596b38cbf062ec03e6067 | [
"MIT"
] | null | null | null | ---
title: "I and Me or Mine"
date: 2020-08-10
I am a good man... I wanna be a human being...
---
| 16.333333 | 46 | 0.602041 | eng_Latn | 0.974097 |
589acfb609444fc2821d917f15c3cf43f7bf9b9a | 2,808 | md | Markdown | articles/finance/localizations/apac-ind-TDS-Record-TDS-concession-certificate-numbers.md | banluo-ms/dynamics-365-unified-operations-public | e8304f7d6d59fdfa179fb6d18380ce2ec8d15b26 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/finance/localizations/apac-ind-TDS-Record-TDS-concession-certificate-numbers.md | banluo-ms/dynamics-365-unified-operations-public | e8304f7d6d59fdfa179fb6d18380ce2ec8d15b26 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/finance/localizations/apac-ind-TDS-Record-TDS-concession-certificate-numbers.md | banluo-ms/dynamics-365-unified-operations-public | e8304f7d6d59fdfa179fb6d18380ce2ec8d15b26 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2022-02-11T12:50:55.000Z | 2022-02-11T12:50:55.000Z | ---
# required metadata
title: Record TDS concession certificate numbers
description: This topic explains how to record the Tax Deducted at Source (TDS) concession certificate numbers that are issued to vendors.
author: kailiang
ms.date: 02/12/2021
ms.topic: article
ms.prod:
ms.service: dynamics-ax-applications
ms.technology:
# optional metadata
ms.search.form:
# ROBOTS:
audience: Application User
# ms.devlang:
ms.reviewer: roschlom
# ms.search.scope: Core, Operations
# ms.tgt_pltfrm:
ms.custom: 15721
ms.assetid: b4b406fa-b772-44ec-8dd8-8eb818a921ef
ms.search.region: Global
# ms.search.industry:
ms.author: kailiang
ms.search.validFrom: 2021-02-12
ms.dyn365.ops.version: AX 10.0.17
---
# Record TDS concession certificate numbers
[!include [banner](../includes/banner.md)]
This topic explains how to record the Tax Deducted at Source (TDS) concession certificate numbers that are issued to vendors.
1. Go to **Tax \> Indirect taxes \> Withholding tax \> Withholding tax concessions**.
2. In the **Tax type** field, select **TDS** to record concession certificates for the TDS tax type.
3. On the **Overview** tab, select **Alt+N** to create a line.
[](./media/apac-ind-TDS-34.png)
4. In the **Withholding tax code** field, select the TDS tax code that the vendor concession certificates are issued for. The **Withholding tax code name** field shows the name of the TDS tax code.
5. In the **From date** and **To date** fields, define the period of validity for the concession certificate that uses the TDS tax code to calculate TDS for the vendor on a concessional basis.
6. In the **Remarks** field, enter any remarks.
7. In the **Section** field, enter the legal section code that the TDS concession certificate is availed under.
If the section code is 197, the value "A" appears in both the "Reason for non-deduction/lower deduction" column in Form 26Q and the "Reason for non-deduction/lower deduction/grossing up (if any)" column in Form 27Q. If the section code is 197A, the value "B" appears in both those places.
8. Select the **Certificate** FastTab to record TDS concession certificate numbers for vendors.
9. In the **Vendor account** field, select the vendor account that the TDS concession certificate is issued for.
10. In the **From date** and **To date** fields, define the period of validity for the TDS concession certificate.
The calculation of TDS on a concessional basis is based on the period when the certificate is created for the vendor.
11. In the **Certificate** field, enter the TDS concession certificate number.
[](./media/apac-ind-TDS-33.png)
12. Close the page.
| 45.290323 | 293 | 0.734687 | eng_Latn | 0.983776 |
589b5436076b3d362ebb7defe8c1d809a1bd185d | 595 | md | Markdown | VBA/Excel-VBA/articles/interior-patterntintandshade-property-excel.md | oloier/VBA-content | 6b3cb5769808b7e18e3aff55a26363ebe78e4578 | [
"CC-BY-4.0",
"MIT"
] | 584 | 2015-09-01T10:09:09.000Z | 2022-03-30T15:47:20.000Z | VBA/Excel-VBA/articles/interior-patterntintandshade-property-excel.md | oloier/VBA-content | 6b3cb5769808b7e18e3aff55a26363ebe78e4578 | [
"CC-BY-4.0",
"MIT"
] | 585 | 2015-08-28T20:20:03.000Z | 2018-08-31T03:09:51.000Z | VBA/Excel-VBA/articles/interior-patterntintandshade-property-excel.md | oloier/VBA-content | 6b3cb5769808b7e18e3aff55a26363ebe78e4578 | [
"CC-BY-4.0",
"MIT"
] | 590 | 2015-09-01T10:09:09.000Z | 2021-09-27T08:02:27.000Z | ---
title: Interior.PatternTintAndShade Property (Excel)
keywords: vbaxl10.chm551082
f1_keywords:
- vbaxl10.chm551082
ms.prod: excel
api_name:
- Excel.Interior.PatternTintAndShade
ms.assetid: 0213fb37-6dd3-af4b-0ff6-ce530862875f
ms.date: 06/08/2017
---
# Interior.PatternTintAndShade Property (Excel)
Returns or sets a tint and shade pattern for an **Interior** object. Read/write **Variant** .
## Syntax
_expression_ . **PatternTintAndShade**
_expression_ A variable that represents an **Interior** object.
## See also
#### Concepts
[Interior Object](interior-object-excel.md)
| 17.5 | 94 | 0.752941 | eng_Latn | 0.292242 |
589c08fb559cdb357bbfb7a05ef12ece4db3eef3 | 4,539 | md | Markdown | md/44_JHNFBta/chap-021.md | berinaniesh/Bible-Tamil-Sathiyavedam-1957 | 1787f0cd252f7bab5d14273ae6ab24c283bebbbb | [
"MIT"
] | null | null | null | md/44_JHNFBta/chap-021.md | berinaniesh/Bible-Tamil-Sathiyavedam-1957 | 1787f0cd252f7bab5d14273ae6ab24c283bebbbb | [
"MIT"
] | null | null | null | md/44_JHNFBta/chap-021.md | berinaniesh/Bible-Tamil-Sathiyavedam-1957 | 1787f0cd252f7bab5d14273ae6ab24c283bebbbb | [
"MIT"
] | null | null | null | ---
title: யோவான் 21
lang: ta
mainfont: Noto Sans Tamil Regular
---
# யோவான் 21:1
இவைகளுக்குப்பின்பு இயேசு திபேரியா கடற்கரையிலே மறுபடியும் சீஷருக்குத் தம்மை வெளிப்படுத்தினார்; வெளிப்படுத்தின விவரமாவது:
# யோவான் 21:2
சீமோன்பேதுருவும், திதிமு என்னப்பட்ட தோமாவும், கலிலேயா நாட்டிலுள்ள கானா ஊரானாகிய நாத்தான்வேலும், செபெதேயுவின் குமாரரும், அவருடைய சீஷரில் வேறு இரண்டுபேரும் கூடியிருக்கும்போது,
# யோவான் 21:3
சீமோன்பேதுரு மற்றவர்களை நோக்கி: மீன்பிடிக்கப்போகிறேன் என்றான். அதற்கு அவர்கள்: நாங்களும் உம்முடனேகூட வருகிறோம் என்றார்கள். அவர்கள் புறப்பட்டுப்போய், உடனே படவேறினார்கள். அந்த இராத்திரியிலே அவர்கள் ஒன்றும் பிடிக்கவில்லை.
# யோவான் 21:4
விடியற்காலமானபோது, இயேசு கரையிலே நின்றார்; அவரை இயேசு என்று சீஷர்கள் அறியாதிருந்தார்கள்.
# யோவான் 21:5
இயேசு அவர்களை நோக்கி: பிள்ளைகளே, புசிக்கிறதற்கு ஏதாகிலும் உங்களிடத்தில் உண்டா என்றார். அதற்கு அவர்கள்: ஒன்றுமில்லை என்றார்கள்.
# யோவான் 21:6
அப்பொழுது அவர்: நீங்கள் படவுக்கு வலதுபுறமாக வலையைப் போடுங்கள், அப்பொழுது உங்களுக்கு அகப்படும் என்றார். அப்படியே அவர்கள் போட்டு, திரளான மீன்கள் அகப்பட்டதினால், அதை இழுக்கமாட்டாதிருந்தார்கள்.
# யோவான் 21:7
ஆதலால் இயேசுவுக்கு அன்பாயிருந்த சீஷன் பேதுருவைப் பார்த்து: அவர் கர்த்தர் என்றான். அவர் கர்த்தர் என்று சீமோன்பேதுரு கேட்டவுடனே, தான் வஸ்திரமில்லாதவனாயிருந்தபடியினால், தன் மேற்சட்டையைக் கட்டிக்கொண்டு கடலிலே குதித்தான்.
# யோவான் 21:8
மற்றச் சீஷர்கள் கரைக்கு ஏறக்குறைய இருநூறுமுழத் தூரத்தில் இருந்தபடியினால் படவிலிருந்துகொண்டே மீன்களுள்ள வலையை இழுத்துக்கொண்டு வந்தார்கள்.
# யோவான் 21:9
அவர்கள் கரையிலே வந்திறங்கினபோது, கரிநெருப்புப் போட்டிருக்கிறதையும், அதின்மேல் மீன் வைத்திருக்கிறதையும், அப்பத்தையும் கண்டார்கள்.
# யோவான் 21:10
இயேசு அவர்களை நோக்கி: நீங்கள் இப்பொழுது பிடித்த மீன்களில் சிலவற்றைக் கொண்டுவாருங்கள் என்றார்.
# யோவான் 21:11
சீமோன்பேதுரு படவில் ஏறி, நூற்றைம்பத்துமூன்று பெரிய மீன்களால் நிறைந்த வலையைக் கரையில் இழுத்தான்; இத்தனை மீன்கள் இருந்தும் வலை கிழியவில்லை.
# யோவான் 21:12
இயேசு அவர்களை நோக்கி: வாருங்கள், போஜனம்பண்ணுங்கள் என்றார். அவரைக் கர்த்தரென்று சீஷர்கள் அறிந்தபடியினால் அவர்களில் ஒருவனும்: நீர் யார் என்று கேட்கத் துணியவில்லை.
# யோவான் 21:13
அப்பொழுது இயேசு வந்து, அப்பத்தையும் மீனையும் எடுத்து, அவர்களுக்குக் கொடுத்தார்.
# யோவான் 21:14
இயேசு மரித்தோரிலிருந்தெழுந்த பின்பு தம்முடைய சீஷருக்கு அருளின தரிசனங்களில் இது மூன்றாவது தரிசனம்.
# யோவான் 21:15
அவர்கள் போஜனம்பண்ணினபின்பு, இயேசு சீமோன்பேதுருவை நோக்கி: யோனாவின் குமாரனாகிய சீமோனே, இவர்களிலும் அதிகமாய் நீ என்னிடத்தில் அன்பாயிருக்கிறாயா என்றார். அதற்கு அவன்: ஆம் ஆண்டவரே, உம்மை நேசிக்கிறேன் என்பதை நீர் அறிவீர் என்றான். அவர்: என் ஆட்டுக்குட்டிகளை மேய்ப்பாயாக என்றார்.
# யோவான் 21:16
இரண்டாந்தரம் அவர் அவனை நோக்கி: யோனாவின் குமாரனாகிய சீமோனே, நீ என்னிடத்தில் அன்பாயிருக்கிறாயா என்றார். அதற்கு அவன்: ஆம் ஆண்டவரே, உம்மை நேசிக்கிறேன் என்பதை நீர் அறிவீர் என்றான். அவர்: என் ஆடுகளை மேய்ப்பாயாக என்றார்.
# யோவான் 21:17
மூன்றாந்தரம் அவர் அவனை நோக்கி: யோனாவின் குமாரனாகிய சீமோனே, நீ என்னை நேசிக்கிறாயா என்றார். என்னை நேசிக்கிறாயா என்று அவர் மூன்றாந்தரம் தன்னைக் கேட்டபடியினாலே, பேதுரு துக்கப்பட்டு: ஆண்டவரே, நீர் எல்லாவற்றையும் அறிந்திருக்கிறீர், நான் உம்மை நேசிக்கிறேன் என்பதையும் நீர் அறிவீர் என்றான். இயேசு: என் ஆடுகளை மேய்ப்பாயாக என்றார்.
# யோவான் 21:18
நீ இளயவதுள்ளவனாயிருந்தபோது உன்னை நீயே அரைகட்டிக்கொண்டு, உனக்கு இஷ்டமான இடங்களிலே நடந்து திரிந்தாய்; நீ முதிர்வயதுள்ளவனாகும்போது உன் கைகளை நீட்டுவாய்; வேறொருவன் உன் அரையைக் கட்டி, உனக்கு இஷ்டமில்லாத இடத்துக்கு உன்னைக் கொண்டுபோவான் என்று மெய்யாகவே மெய்யாகவே உனக்குச் சொல்லுகிறேன் என்றார்.
# யோவான் 21:19
இன்னவிதமான மரணத்தினாலே அவன் தேவனை மகிமைப்படுத்தப்போகிறானென்பதைக் குறிக்கும்படியாக இப்படிச் சொன்னார். அவர் இதைச் சொல்லியபின்பு, அவனை நோக்கி: என்னைப் பின்பற்றிவா என்றார்.
# யோவான் 21:20
பேதுரு திரும்பிப்பார்த்து, இயேசுவுக்கு அன்பாயிருந்தவனும், இராப்போஜனம்பண்ணுகையில் அவர் மார்பிலே சாய்ந்து: ஆண்டவரே, உம்மைக் காட்டிக்கொடுக்கிறவன் யார் என்று கேட்டவனுமாகிய சீஷன் பின்னே வருகிறதைக் கண்டான்.
# யோவான் 21:21
அவனைக் கண்டு, பேதுரு இயேசுவை நோக்கி: ஆண்டவரே, இவன் காரியம் என்ன என்றான்.
# யோவான் 21:22
அதற்கு இயேசு: நான் வருமளவும் இவனிருக்க எனக்குச் சித்தமானால், உனக்கென்ன, நீ என்னைப் பின்பற்றிவா என்றார்.
# யோவான் 21:23
ஆகையால் அந்தச் சீஷன் மரிப்பதில்லையென்கிற பேச்சு சகோதரருக்குள்ளே பரம்பிற்று. ஆனாலும், அவன் மரிப்பதில்லையென்று இயேசு சொல்லாமல், நான் வருமளவும் இவனிருக்க எனக்குச் சித்தமானால் உனக்கென்னவென்று சொன்னார்.
# யோவான் 21:24
அந்தச் சீஷனே இவைகளைக் குறித்துச் சாட்சிகொடுத்து இவைகளை எழுதினவன்; அவனுடைய சாட்சி மெய்யென்று அறிந்திருக்கிறோம்.
# யோவான் 21:25
இயேசு செய்த வேறு அநேக காரியங்களுமுண்டு; அவைகளை ஒவ்வொன்றாக எழுதினால் எழுதப்படும் புஸ்தகங்கள் உலகம் கொள்ளாதென்று எண்ணுகிறேன். ஆமென்.
| 42.420561 | 321 | 0.50011 | tam_Taml | 0.997048 |
589c8f4a2cef20bdbe61121359fb3177e1cdcedf | 533 | md | Markdown | static/crew/obrien_klingon_crew.md | auto2000/datacore | 190ce84f67909b1d5fffa2c982e4275c72af8258 | [
"MIT"
] | null | null | null | static/crew/obrien_klingon_crew.md | auto2000/datacore | 190ce84f67909b1d5fffa2c982e4275c72af8258 | [
"MIT"
] | null | null | null | static/crew/obrien_klingon_crew.md | auto2000/datacore | 190ce84f67909b1d5fffa2c982e4275c72af8258 | [
"MIT"
] | null | null | null | ---
name: Klingon O'Brien
rarity: 4
series: ds9
memory_alpha: ds9
bigbook_tier: 3
events: 13
in_portal: false
published: true
---
A name that doesn't get mentioned enough. Very versatile and effective crew between his stout voyage numbers (#1 ENG+DIP total), double collections, and Klingon + O'Brien events. Even worth a look in the arena where short initialization +Acc/shield repair and strong passive numbers can be situationally useful. Docked a point for a fairly expensive equip cost, but his immortalized value is worth it.
| 41 | 401 | 0.786116 | eng_Latn | 0.997387 |
589c91a516978efae5b2cf96218809497aa0c063 | 12,319 | md | Markdown | packages/bots-base/CHANGELOG.md | lskjs/lskjs | ecb8578e421a2e460c7b1afe259f033b9945b96c | [
"MIT"
] | 9 | 2019-06-26T18:42:06.000Z | 2021-04-03T17:47:05.000Z | packages/bots-base/CHANGELOG.md | lskjs/lskjs | ecb8578e421a2e460c7b1afe259f033b9945b96c | [
"MIT"
] | 50 | 2019-11-15T14:57:38.000Z | 2022-02-20T12:20:21.000Z | packages/bots-base/CHANGELOG.md | lskjs/lskjs | ecb8578e421a2e460c7b1afe259f033b9945b96c | [
"MIT"
] | 7 | 2020-04-02T07:09:24.000Z | 2021-04-03T17:47:06.000Z | # Change Log
All notable changes to this project will be documented in this file.
See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
# [2.43.0](https://github.com/lskjs/lskjs/compare/v2.42.3...v2.43.0) (2021-10-25)
**Note:** Version bump only for package @lskjs/bots-base
## [2.42.3](https://github.com/lskjs/lskjs/compare/v2.42.2...v2.42.3) (2021-10-18)
**Note:** Version bump only for package @lskjs/bots-base
## [2.42.2](https://github.com/lskjs/lskjs/compare/v2.42.1...v2.42.2) (2021-10-14)
**Note:** Version bump only for package @lskjs/bots-base
## [2.42.1](https://github.com/lskjs/lskjs/compare/v2.42.0...v2.42.1) (2021-10-12)
**Note:** Version bump only for package @lskjs/bots-base
# [2.42.0](https://github.com/lskjs/lskjs/compare/v2.41.0...v2.42.0) (2021-10-12)
**Note:** Version bump only for package @lskjs/bots-base
# [2.41.0](https://github.com/lskjs/lskjs/compare/v2.40.0...v2.41.0) (2021-10-12)
**Note:** Version bump only for package @lskjs/bots-base
# [2.40.0](https://github.com/lskjs/lskjs/compare/v2.39.1...v2.40.0) (2021-10-11)
**Note:** Version bump only for package @lskjs/bots-base
## [2.39.1](https://github.com/lskjs/lskjs/compare/v2.39.0...v2.39.1) (2021-10-11)
**Note:** Version bump only for package @lskjs/bots-base
# [2.39.0](https://github.com/lskjs/lskjs/compare/v2.38.0...v2.39.0) (2021-10-11)
**Note:** Version bump only for package @lskjs/bots-base
# [2.38.0](https://github.com/lskjs/lskjs/compare/v2.37.1...v2.38.0) (2021-10-11)
**Note:** Version bump only for package @lskjs/bots-base
# [2.37.0](https://github.com/lskjs/lskjs/compare/v2.36.1...v2.37.0) (2021-10-09)
**Note:** Version bump only for package @lskjs/bots-base
## [2.36.1](https://github.com/lskjs/lskjs/compare/v2.36.0...v2.36.1) (2021-10-08)
**Note:** Version bump only for package @lskjs/bots-base
# [2.36.0](https://github.com/lskjs/lskjs/compare/v2.35.0...v2.36.0) (2021-10-08)
**Note:** Version bump only for package @lskjs/bots-base
# [2.35.0](https://github.com/lskjs/lskjs/compare/v2.34.0...v2.35.0) (2021-10-07)
**Note:** Version bump only for package @lskjs/bots-base
# [2.34.0](https://github.com/lskjs/lskjs/compare/v2.33.1...v2.34.0) (2021-10-07)
### Features
* **log:** migrate log2 to log ([ba6fcf7](https://github.com/lskjs/lskjs/commit/ba6fcf70c54c84fa61f6b496f92ffafdbd00344d))
## [2.33.1](https://github.com/lskjs/lskjs/compare/v2.33.0...v2.33.1) (2021-10-05)
**Note:** Version bump only for package @lskjs/bots-base
# [2.33.0](https://github.com/lskjs/lskjs/compare/v2.32.1...v2.33.0) (2021-10-05)
**Note:** Version bump only for package @lskjs/bots-base
# [2.29.0](https://github.com/lskjs/lskjs/compare/v2.28.0...v2.29.0) (2021-09-30)
**Note:** Version bump only for package @lskjs/bots-base
# [2.28.0](https://github.com/lskjs/lskjs/compare/v2.27.0...v2.28.0) (2021-09-27)
**Note:** Version bump only for package @lskjs/bots-base
# [2.27.0](https://github.com/lskjs/lskjs/compare/v2.26.0...v2.27.0) (2021-09-23)
**Note:** Version bump only for package @lskjs/bots-base
# [2.26.0](https://github.com/lskjs/lskjs/compare/v2.25.3...v2.26.0) (2021-09-23)
**Note:** Version bump only for package @lskjs/bots-base
# [2.25.0](https://github.com/lskjs/lskjs/compare/v2.24.0...v2.25.0) (2021-09-12)
**Note:** Version bump only for package @lskjs/bots-base
# [2.24.0](https://github.com/lskjs/lskjs/compare/v2.23.6...v2.24.0) (2021-09-12)
**Note:** Version bump only for package @lskjs/bots-base
## [2.23.4](https://github.com/lskjs/lskjs/compare/v2.23.3...v2.23.4) (2021-09-09)
**Note:** Version bump only for package @lskjs/bots-base
## [2.23.2](https://github.com/lskjs/lskjs/compare/v2.23.1...v2.23.2) (2021-09-08)
**Note:** Version bump only for package @lskjs/bots-base
## [2.23.1](https://github.com/lskjs/lskjs/compare/v2.23.0...v2.23.1) (2021-09-08)
**Note:** Version bump only for package @lskjs/bots-base
# [2.23.0](https://github.com/lskjs/lskjs/compare/v2.22.0...v2.23.0) (2021-09-07)
**Note:** Version bump only for package @lskjs/bots-base
# [2.18.0](https://github.com/lskjs/lskjs/compare/v2.17.3...v2.18.0) (2021-09-01)
**Note:** Version bump only for package @lskjs/bots-base
# [2.17.0](https://github.com/lskjs/lskjs/compare/v2.16.1...v2.17.0) (2021-09-01)
**Note:** Version bump only for package @lskjs/bots-base
# [2.13.0](https://github.com/lskjs/lskjs/compare/v2.12.3...v2.13.0) (2021-08-20)
**Note:** Version bump only for package @lskjs/bots-base
## [2.12.3](https://github.com/lskjs/lskjs/compare/v2.12.2...v2.12.3) (2021-08-19)
**Note:** Version bump only for package @lskjs/bots-base
# [2.12.0](https://github.com/lskjs/lskjs/compare/v2.11.3...v2.12.0) (2021-08-18)
**Note:** Version bump only for package @lskjs/bots-base
## [2.10.2](https://github.com/lskjs/lskjs/compare/v2.10.1...v2.10.2) (2021-08-16)
**Note:** Version bump only for package @lskjs/bots-base
## [2.9.1](https://github.com/lskjs/lskjs/compare/v2.9.0...v2.9.1) (2021-08-16)
**Note:** Version bump only for package @lskjs/bots-base
# [2.9.0](https://github.com/lskjs/lskjs/compare/v2.8.4...v2.9.0) (2021-08-13)
**Note:** Version bump only for package @lskjs/bots-base
## [2.8.4](https://github.com/lskjs/lskjs/compare/v2.8.3...v2.8.4) (2021-08-13)
**Note:** Version bump only for package @lskjs/bots-base
# [2.8.0](https://github.com/lskjs/lskjs/compare/v2.7.2...v2.8.0) (2021-08-13)
### Features
* correct peerDeps versions via semver ([4b090b8](https://github.com/lskjs/lskjs/commit/4b090b834728e9894ed7186033a4d57d8357095b))
# [2.7.0](https://github.com/lskjs/lskjs/compare/v2.6.1...v2.7.0) (2021-08-13)
**Note:** Version bump only for package @lskjs/bots-base
## [2.6.1](https://github.com/lskjs/lskjs/compare/v2.6.0...v2.6.1) (2021-08-12)
### Bug Fixes
* **permit:** fix store path ([fffeefd](https://github.com/lskjs/lskjs/commit/fffeefdead4aed6eb021e6eaa6c9111160651177))
# [2.6.0](https://github.com/lskjs/lskjs/compare/v2.5.3...v2.6.0) (2021-08-12)
**Note:** Version bump only for package @lskjs/bots-base
## [2.5.3](https://github.com/lskjs/lskjs/compare/v2.5.2...v2.5.3) (2021-08-12)
**Note:** Version bump only for package @lskjs/bots-base
## [2.5.2](https://github.com/lskjs/lskjs/compare/v2.5.1...v2.5.2) (2021-08-12)
**Note:** Version bump only for package @lskjs/bots-base
## [2.5.1](https://github.com/lskjs/lskjs/compare/v2.5.0...v2.5.1) (2021-08-12)
**Note:** Version bump only for package @lskjs/bots-base
# [2.5.0](https://github.com/lskjs/lskjs/compare/v2.3.0-beta.104...v2.5.0) (2021-08-11)
**Note:** Version bump only for package @lskjs/bots-base
# [2.3.0-beta.99](https://github.com/lskjs/lskjs/compare/v2.3.0-beta.98...v2.3.0-beta.99) (2021-08-09)
**Note:** Version bump only for package @lskjs/bots-base
# [2.3.0-beta.95](https://github.com/lskjs/lskjs/compare/v2.3.0-beta.94...v2.3.0-beta.95) (2021-08-04)
**Note:** Version bump only for package @lskjs/bots-base
# [2.3.0-beta.94](https://github.com/lskjs/lskjs/compare/v2.3.0-beta.92...v2.3.0-beta.94) (2021-08-02)
**Note:** Version bump only for package @lskjs/bots-base
# [2.3.0-beta.92](https://github.com/lskjs/lskjs/compare/v2.3.0-beta.91...v2.3.0-beta.92) (2021-07-30)
**Note:** Version bump only for package @lskjs/bots-base
# [2.3.0-beta.91](https://github.com/lskjs/lskjs/compare/v2.3.0-beta.90...v2.3.0-beta.91) (2021-07-30)
**Note:** Version bump only for package @lskjs/bots-base
# [2.3.0-beta.90](https://github.com/lskjs/lskjs/compare/v2.3.0-beta.89...v2.3.0-beta.90) (2021-07-29)
**Note:** Version bump only for package @lskjs/bots-base
# [2.3.0-beta.89](https://github.com/lskjs/lskjs/tree/master/packages/bots-base/compare/v2.3.0-beta.88...v2.3.0-beta.89) (2021-07-29)
**Note:** Version bump only for package @lskjs/bots-base
# [2.3.0-beta.88](https://github.com/lskjs/lskjs/tree/master/packages/bots-base/compare/v2.3.0-beta.87...v2.3.0-beta.88) (2021-07-29)
**Note:** Version bump only for package @lskjs/bots-base
# [2.3.0-beta.87](https://github.com/lskjs/lskjs/tree/master/packages/bots-base/compare/v2.3.0-beta.86...v2.3.0-beta.87) (2021-07-29)
**Note:** Version bump only for package @lskjs/bots-base
# [2.3.0-beta.86](https://github.com/lskjs/lskjs/tree/master/packages/bots-base/compare/v2.3.0-beta.85...v2.3.0-beta.86) (2021-07-29)
**Note:** Version bump only for package @lskjs/bots-base
# [2.3.0-beta.58](https://github.com/lskjs/lskjs/tree/master/packages/bots-base/compare/v2.3.0-beta.57...v2.3.0-beta.58) (2021-06-16)
**Note:** Version bump only for package @lskjs/bots-base
# [2.3.0-beta.52](https://github.com/lskjs/lskjs/tree/master/packages/bots-base/compare/v2.3.0-beta.51...v2.3.0-beta.52) (2021-06-10)
**Note:** Version bump only for package @lskjs/bots-base
# [2.3.0-beta.49](https://github.com/lskjs/lskjs/tree/master/packages/bots-base/compare/v2.3.0-beta.48...v2.3.0-beta.49) (2021-05-25)
**Note:** Version bump only for package @lskjs/bots-base
# [2.3.0-beta.48](https://github.com/lskjs/lskjs/tree/master/packages/bots-base/compare/v2.3.0-beta.47...v2.3.0-beta.48) (2021-05-19)
**Note:** Version bump only for package @lskjs/bots-base
# [2.3.0-beta.42](https://github.com/lskjs/lskjs/tree/master/packages/bots-base/compare/v2.3.0-beta.41...v2.3.0-beta.42) (2021-05-17)
**Note:** Version bump only for package @lskjs/bots-base
# [2.3.0-beta.41](https://github.com/lskjs/lskjs/tree/master/packages/bots-base/compare/v2.3.0-beta.40...v2.3.0-beta.41) (2021-05-16)
**Note:** Version bump only for package @lskjs/bots-base
# [2.3.0-beta.40](https://github.com/lskjs/lskjs/tree/master/packages/bots-base/compare/v2.3.0-beta.39...v2.3.0-beta.40) (2021-05-16)
**Note:** Version bump only for package @lskjs/bots-base
# [2.3.0-beta.39](https://github.com/lskjs/lskjs/tree/master/packages/bots-base/compare/v2.3.0-beta.38...v2.3.0-beta.39) (2021-05-16)
### Bug Fixes
* fix packages ([5b8dd85](https://github.com/lskjs/lskjs/tree/master/packages/bots-base/commit/5b8dd85a9465dda31a37f2ef43485dcc2bf6b6fe))
# [2.3.0-beta.38](https://github.com/lskjs/lskjs/tree/master/packages/bots-base/compare/v2.3.0-beta.37...v2.3.0-beta.38) (2021-05-15)
**Note:** Version bump only for package @lskjs/bots-base
# [2.3.0-beta.37](https://github.com/lskjs/lskjs/tree/master/packages/bots-base/compare/v2.3.0-beta.36...v2.3.0-beta.37) (2021-05-15)
### Bug Fixes
* **bots-base:** add useForm2 ([5c11162](https://github.com/lskjs/lskjs/tree/master/packages/bots-base/commit/5c11162564700a57bf211fa9d39a32af4b08499d))
# [2.3.0-beta.26](https://github.com/lskjs/lskjs/tree/master/packages/bots-base/compare/v2.3.0-beta.25...v2.3.0-beta.26) (2021-04-19)
**Note:** Version bump only for package @lskjs/bots-base
# [2.3.0-beta.25](https://github.com/lskjs/lskjs/tree/master/packages/bots-base/compare/v2.3.0-beta.24...v2.3.0-beta.25) (2021-04-19)
**Note:** Version bump only for package @lskjs/bots-base
# [2.3.0-beta.24](https://github.com/lskjs/lskjs/tree/master/packages/bots-base/compare/v2.3.0-beta.23...v2.3.0-beta.24) (2021-04-16)
**Note:** Version bump only for package @lskjs/bots-base
# [2.3.0-beta.22](https://github.com/lskjs/lskjs/tree/master/packages/bots-base/compare/v2.3.0-beta.21...v2.3.0-beta.22) (2021-04-09)
**Note:** Version bump only for package @lskjs/bots-base
# [2.3.0-beta.10](https://github.com/lskjs/lskjs/tree/master/packages/bots-base/compare/v2.3.0-beta.9...v2.3.0-beta.10) (2021-03-16)
### Bug Fixes
* add bot's saveMessage and fixes ([d7373c6](https://github.com/lskjs/lskjs/tree/master/packages/bots-base/commit/d7373c6364282613c4008ff617e375bf6974c37e))
### Features
* add preview in form ([cad8001](https://github.com/lskjs/lskjs/tree/master/packages/bots-base/commit/cad8001599b78a1ffd8579482eda0fff623e6610))
# [2.3.0-beta.5](https://github.com/lskjs/lskjs/tree/master/packages/bots-base/compare/v2.3.0-beta.4...v2.3.0-beta.5) (2021-02-21)
### Features
* **bots:** separate bots packages ([b3aba71](https://github.com/lskjs/lskjs/tree/master/packages/bots-base/commit/b3aba716c36ee27896685b645a0f77808fecba92))
| 20.986371 | 157 | 0.677328 | yue_Hant | 0.123267 |
589ce42369c1b6cabcb0979738d5b835b7f9b510 | 40 | md | Markdown | README.md | s-samarth/lazystats | 8c4a062631a0d19ec552023bf0d28cdac57a1737 | [
"Apache-2.0"
] | null | null | null | README.md | s-samarth/lazystats | 8c4a062631a0d19ec552023bf0d28cdac57a1737 | [
"Apache-2.0"
] | null | null | null | README.md | s-samarth/lazystats | 8c4a062631a0d19ec552023bf0d28cdac57a1737 | [
"Apache-2.0"
] | null | null | null | This is a basic library for probab dists | 40 | 40 | 0.825 | eng_Latn | 0.999994 |
589d0a3a13fac78fb88d3c25207253e20f879de0 | 681 | md | Markdown | docs/src/pages/components/skeleton/skeleton-ja.md | epeicher/material-ui | 05c533bd1f044593b772191066f25dd8b916ff5d | [
"MIT"
] | 3 | 2020-01-13T16:15:04.000Z | 2020-05-25T09:18:30.000Z | docs/src/pages/components/skeleton/skeleton-ja.md | epeicher/material-ui | 05c533bd1f044593b772191066f25dd8b916ff5d | [
"MIT"
] | 59 | 2019-10-23T18:48:57.000Z | 2021-08-03T20:02:17.000Z | docs/src/pages/components/skeleton/skeleton-ja.md | epeicher/material-ui | 05c533bd1f044593b772191066f25dd8b916ff5d | [
"MIT"
] | 1 | 2019-11-08T02:03:10.000Z | 2019-11-08T02:03:10.000Z | ---
title: Skeleton React component
components: Skeleton
---
# スケルトン
<p class="description">データがロードされる前にコンテンツのプレースホルダープレビューを表示して、ロード時のフラストレーションを軽減します。</p>
コンポーネントのデータがすぐに利用できない場合があります。 スケルトンを使用することにより、ユーザーの知覚パフォーマンスを向上させることができます。 すぐに物事が発生しているように感じ、情報が画面に徐々に表示されます（Cf. [Avoid The Spinner](https://www.lukew.com/ff/entry.asp?1797)).
このコンポーネントは、**コンポーネント内で直接使用**できるように設計されています。 例えば：
```jsx
{item ? (
<img style={{ width: 210, height: 118 }} alt={item.title} src={item.src} />
) : (
<Skeleton variant="rect" width={210} height={118} />
)}
```
## YouTubeの例
{{"demo": "pages/components/skeleton/YouTube.js"}}
## Facebookの例
{{"demo": "pages/components/skeleton/Facebook.js"}} | 24.321429 | 175 | 0.726872 | yue_Hant | 0.269628 |
589d276a10951c2da5333a608717571db8acbb50 | 954 | md | Markdown | _pages/about.md | sambarrows/sambarrows.github.io | 5f478dbbe3f2dd8d3366ce4ddde07dc5a077203c | [
"MIT"
] | null | null | null | _pages/about.md | sambarrows/sambarrows.github.io | 5f478dbbe3f2dd8d3366ce4ddde07dc5a077203c | [
"MIT"
] | null | null | null | _pages/about.md | sambarrows/sambarrows.github.io | 5f478dbbe3f2dd8d3366ce4ddde07dc5a077203c | [
"MIT"
] | null | null | null | ---
permalink: /about/
---
A data scientist trained in quantitative political science, I love applying statistics and machine learning to understand and drive customer engagement. I'm particularly interested in topics in causal inference.
I'm currently part of Uber's money team in Amsterdam, where I run experimentation, predictive modeling, insights, and reporting for consumer-facing rider payments.
I was previously at at Booking.com, where I worked with product teams across the customer service innovation group to measure and increase customer satisfaction and loyalty.
I began my career using statistical methods to understand the drivers of parents' satisfaction and engagement with public schools, receiving a postdoctoral fellowship at the Harvard Kennedy School and teaching at the University of Cambridge.
I earned a Ph.D. in Government from Harvard University and a B.A. from the University of Oxford, where I majored in economics.
| 68.142857 | 241 | 0.812369 | eng_Latn | 0.999444 |
589de8eda334e721ef189a225bd74cab05f49352 | 3,220 | md | Markdown | hitch/content.md | thaJeztah/docker-library-docs | 41d412ff89f6bfceecac40f5cc46c5f5e502796e | [
"MIT"
] | 4,528 | 2015-01-04T06:26:59.000Z | 2022-03-31T14:56:12.000Z | hitch/content.md | thaJeztah/docker-library-docs | 41d412ff89f6bfceecac40f5cc46c5f5e502796e | [
"MIT"
] | 1,324 | 2015-01-01T00:00:12.000Z | 2022-03-31T15:47:15.000Z | hitch/content.md | thaJeztah/docker-library-docs | 41d412ff89f6bfceecac40f5cc46c5f5e502796e | [
"MIT"
] | 2,599 | 2015-01-05T07:51:50.000Z | 2022-03-31T14:16:30.000Z | # What is Hitch?
[Hitch](https://hitch-tls.org/) is a *libev-based* high performance *SSL/TLS proxy* by [Varnish Software](https://varnish-software.com). It is specifically built to terminate TLS connections at high scale and forwards unencrypted HTTP traffic to Varnish or any other HTTP backend.
# How to use this image
Running a Hitch Docker container can be done by using the following command:
```console
$ docker run --name=hitch -p 443:443 %%IMAGE%%
```
This container will expose port `443`, which is required for HTTPS traffic.
## Configuration file and extra options
Without any argument, the container will run `hitch --config=/etc/hitch/hitch.conf`. You can mount your own configuration file to replace the default one:
```console
$ docker run -v /path/to/your/config/file:/etc/hitch/hitch.conf:ro %%IMAGE%%
```
You can also change the path of the configuration file by setting the `HITCH_CONFIG_FILE` environment variable.
Note that extra arguments can be added to the command line. If the first argument starts with a `-`, the arguments are added to the default command line, otherwise they are treated as a command.
> Our assumption is that your backend, Varnish or other, supports both *HTTP/2* and the *PROXY* protocol.
## Connecting to the backend
By default Hitch will connect to the backend using `localhost:8843` using the [PROXY protocol](https://github.com/varnish/hitch/blob/master/docs/proxy-protocol.md). If your backend server *PROXY*, the two will be able to talk together and backend will be able to expose the true client IP.
But you'll probably run your backend service in a separate container. In that case, you'll want to change the backend settings. You can either do that by replacing the [`backend`](https://github.com/varnish/hitch/blob/master/hitch.conf.man.rst#backend--) configuration setting in your mounted configuration file, or by adding a *command-line option*.
Here's how you set the backend via a *command-line option*, assuming your backend is available through `backend.example.com` on port `8443`:
```console
$ docker run %%IMAGE%% "--backend=[backend.example.com]:8443"
```
## Setting the certificate
The Hitch Docker image comes with a self-signed certificate that is stored in `/etc/hitch/certs/default`.
This certificate is automatically created during *Hitch* package install, and is a self-signed certificate using 2048-bit RSA-encrypted cipher. It is set up for the `localhost` hostname, with an expiration date 30 years in the future.
This certificate is only suited for testing. Using a bind mount, you can override the value of the certificate and use your own certificate, which is advisable.
Here's an example:
```console
$ docker run -v /path/to/your/certificate:/etc/hitch/certs/default:ro %%IMAGE%%
```
You can also override the [`pem-file`](https://github.com/varnish/hitch/blob/master/hitch.conf.man.rst#pem-file--string) configuration setting in your mounted configuration file.
If you prefer setting the certificate location on the command line, you can add the location as part of the `--backend` option.
Here's how you do this:
```console
$ docker run %%IMAGE%% "--backend=[backend.example.com]:8443:/path/to/cert.pem"
```
| 50.3125 | 350 | 0.763354 | eng_Latn | 0.997276 |
589eaf302c4f10c9a115fed4b1a4565de5920af9 | 4,433 | md | Markdown | iredis/data/commands/zadd.md | otms61/iredis | b4acd1b187f9a905ba484710f37656cb56b75962 | [
"BSD-3-Clause"
] | 1 | 2021-09-14T07:42:05.000Z | 2021-09-14T07:42:05.000Z | iredis/data/commands/zadd.md | otms61/iredis | b4acd1b187f9a905ba484710f37656cb56b75962 | [
"BSD-3-Clause"
] | null | null | null | iredis/data/commands/zadd.md | otms61/iredis | b4acd1b187f9a905ba484710f37656cb56b75962 | [
"BSD-3-Clause"
] | null | null | null | Adds all the specified members with the specified scores to the sorted set
stored at `key`. It is possible to specify multiple score / member pairs. If a
specified member is already a member of the sorted set, the score is updated and
the element reinserted at the right position to ensure the correct ordering.
If `key` does not exist, a new sorted set with the specified members as sole
members is created, like if the sorted set was empty. If the key exists but does
not hold a sorted set, an error is returned.
The score values should be the string representation of a double precision
floating point number. `+inf` and `-inf` values are valid values as well.
## ZADD options (Redis 3.0.2 or greater)
ZADD supports a list of options, specified after the name of the key and before
the first score argument. Options are:
- **XX**: Only update elements that already exist. Never add elements.
- **NX**: Don't update already existing elements. Always add new elements.
- **CH**: Modify the return value from the number of new elements added, to the
total number of elements changed (CH is an abbreviation of _changed_). Changed
elements are **new elements added** and elements already existing for which
**the score was updated**. So elements specified in the command line having
the same score as they had in the past are not counted. Note: normally the
return value of `ZADD` only counts the number of new elements added.
- **INCR**: When this option is specified `ZADD` acts like `ZINCRBY`. Only one
score-element pair can be specified in this mode.
## Range of integer scores that can be expressed precisely
Redis sorted sets use a _double 64-bit floating point number_ to represent the
score. In all the architectures we support, this is represented as an **IEEE 754
floating point number**, that is able to represent precisely integer numbers
between `-(2^53)` and `+(2^53)` included. In more practical terms, all the
integers between -9007199254740992 and 9007199254740992 are perfectly
representable. Larger integers, or fractions, are internally represented in
exponential form, so it is possible that you get only an approximation of the
decimal number, or of the very big integer, that you set as score.
## Sorted sets 101
Sorted sets are sorted by their score in an ascending way. The same element only
exists a single time, no repeated elements are permitted. The score can be
modified both by `ZADD` that will update the element score, and as a side
effect, its position on the sorted set, and by `ZINCRBY` that can be used in
order to update the score relatively to its previous value.
The current score of an element can be retrieved using the `ZSCORE` command,
that can also be used to verify if an element already exists or not.
For an introduction to sorted sets, see the data types page on [sorted
sets][tdtss].
[tdtss]: /topics/data-types#sorted-sets
## Elements with the same score
While the same element can't be repeated in a sorted set since every element is
unique, it is possible to add multiple different elements _having the same
score_. When multiple elements have the same score, they are _ordered
lexicographically_ (they are still ordered by score as a first key, however,
locally, all the elements with the same score are relatively ordered
lexicographically).
The lexicographic ordering used is binary, it compares strings as array of
bytes.
If the user inserts all the elements in a sorted set with the same score (for
example 0), all the elements of the sorted set are sorted lexicographically, and
range queries on elements are possible using the command `ZRANGEBYLEX` (Note: it
is also possible to query sorted sets by range of scores using `ZRANGEBYSCORE`).
@return
@integer-reply, specifically:
- The number of elements added to the sorted set, not including elements already
existing for which the score was updated.
If the `INCR` option is specified, the return value will be @bulk-string-reply:
- The new score of `member` (a double precision floating point number)
represented as string, or `nil` if the operation was aborted (when called with
either the `XX` or the `NX` option).
@history
- `>= 2.4`: Accepts multiple elements. In Redis versions older than 2.4 it was
possible to add or update a single member per call.
@examples
```cli
ZADD myzset 1 "one"
ZADD myzset 1 "uno"
ZADD myzset 2 "two" 3 "three"
ZRANGE myzset 0 -1 WITHSCORES
```
| 44.777778 | 80 | 0.772389 | eng_Latn | 0.999827 |
589f15cc7958ce91f12fb115fa7f7eefac4a719d | 52 | md | Markdown | java/README.md | paoli7612/homework | 17a0d8f9bfbbcbe6a615a5b9e2b2276ac5e6f267 | [
"Apache-2.0"
] | null | null | null | java/README.md | paoli7612/homework | 17a0d8f9bfbbcbe6a615a5b9e2b2276ac5e6f267 | [
"Apache-2.0"
] | null | null | null | java/README.md | paoli7612/homework | 17a0d8f9bfbbcbe6a615a5b9e2b2276ac5e6f267 | [
"Apache-2.0"
] | null | null | null | # Java
- Sistemi e Reti - Marie Curie Pergine 2017
| 17.333333 | 44 | 0.711538 | ita_Latn | 0.815369 |
58a139a0006ec269bb518916002fe338346f77d3 | 419 | md | Markdown | aip/3000.md | rhamiltonsf/aip | 97c40fa994e776980b28041bd2402812f4953479 | [
"Apache-2.0",
"CC-BY-4.0"
] | null | null | null | aip/3000.md | rhamiltonsf/aip | 97c40fa994e776980b28041bd2402812f4953479 | [
"Apache-2.0",
"CC-BY-4.0"
] | null | null | null | aip/3000.md | rhamiltonsf/aip | 97c40fa994e776980b28041bd2402812f4953479 | [
"Apache-2.0",
"CC-BY-4.0"
] | null | null | null | ---
aip:
id: 3000
state: approved
created: 2020-01-15
updated: 2020-07-24
scope: field
js:
- /assets/js/graphviz/viz.js
- /assets/js/graphviz/lite.render.js
- /assets/js/aip/aip-graphviz.js
permalink: /3000
---
# Fields
A resource is made up of one or more fields, which contain key/value pairs that define the resource. Resource fields may also be referred to as attributes, properties, or elements.
| 23.277778 | 180 | 0.718377 | eng_Latn | 0.967171 |
58a15e737ff8ddd642ec633af33d53f6324fe37d | 1,811 | md | Markdown | api/Visio.Master.UniqueID.md | qiezhenxi/VBA-Docs | c49aebcccbd73eadf5d1bddc0a4dfb622e66db5d | [
"CC-BY-4.0",
"MIT"
] | 1 | 2018-10-15T16:15:38.000Z | 2018-10-15T16:15:38.000Z | api/Visio.Master.UniqueID.md | qiezhenxi/VBA-Docs | c49aebcccbd73eadf5d1bddc0a4dfb622e66db5d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | api/Visio.Master.UniqueID.md | qiezhenxi/VBA-Docs | c49aebcccbd73eadf5d1bddc0a4dfb622e66db5d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Master.UniqueID Property (Visio)
keywords: vis_sdr.chm10751165
f1_keywords:
- vis_sdr.chm10751165
ms.prod: visio
api_name:
- Visio.Master.UniqueID
ms.assetid: 99d0655c-da5c-9d0a-4936-2fa24821e097
ms.date: 06/08/2017
---
# Master.UniqueID Property (Visio)
Returns the unique ID of a master. Read-only.
## Syntax
_expression_. `UniqueID`
_expression_ An expression that returns a [Master](./Visio.Master.md) object.
### Return value
String
## Remarks
A **Master** object always has a unique ID. If you copy a master, the new master has the same unique ID as the original master (as well as the same base ID). However, if you subsequently change the copy, Visio assigns it a new unique ID, but its base ID remains the same.
Note that if you copy into a stencil a master that has the same unique ID as a master already in the stencil, Visio assigns a new unique ID to the copy.
For more information about the base ID, see the **BaseID** property.
You can determine a **Master** object's unique ID by using the following code:
```vb
strID = vsoMaster.UniqueID
```
The value it returns is a string in the following form:
```vb
{2287DC42-B167-11CE-88E9-0020AFDDD917}
```
To get a master if you know its unique ID, use **Masters.Item** ( _UniqueIDString_) .
For example, you can use the following code to retrieve the master from the **Masters** collection of the active document:
```vb
Dim vsoMaster As Visio.Master
Set vsoMaster = Visio.ActiveDocument.Masters("{0478DA94-1315-9876-8E4C-006523ABC9B2}")
```
Alternatively, you can use the following code, which adds the letter "U" before the string to identify it as a unique ID:
```vb
Dim vsoShape As Visio.Shape
Set vsoMaster = Visio.ActiveDocument.Masters("U{0478DA94-1315-9876-8E4C-006523ABC9B2}")
```
| 22.085366 | 272 | 0.739371 | eng_Latn | 0.940643 |
58a1a2e0a83dc9266007657e66c68792a53862a9 | 180 | md | Markdown | _news/2019/4-1.md | LeoJhonSong/al-folio | 835c109ed4dedc3e1c58cd60f9b924305673a1cb | [
"MIT"
] | null | null | null | _news/2019/4-1.md | LeoJhonSong/al-folio | 835c109ed4dedc3e1c58cd60f9b924305673a1cb | [
"MIT"
] | null | null | null | _news/2019/4-1.md | LeoJhonSong/al-folio | 835c109ed4dedc3e1c58cd60f9b924305673a1cb | [
"MIT"
] | null | null | null | ---
layout: post
date: 2019-4-1
inline: true
---
Prof. Li Wen and Prof. George Lauder will host the symposium "Aquatic Bio-inspired Soft Robotics" on May 9 at Beihang University.
| 22.5 | 129 | 0.738889 | eng_Latn | 0.795582 |
58a1d0c278f9921c3d6d48491e85a62e25360f11 | 430 | md | Markdown | _posts/projects/2018-08-24-dataquest-hacker-news.md | nahusznaj/nahusznaj.github.io | ec66a3b8bb50c95b7354d1f60e4e88a00fa4e225 | [
"BSD-3-Clause",
"MIT"
] | null | null | null | _posts/projects/2018-08-24-dataquest-hacker-news.md | nahusznaj/nahusznaj.github.io | ec66a3b8bb50c95b7354d1f60e4e88a00fa4e225 | [
"BSD-3-Clause",
"MIT"
] | null | null | null | _posts/projects/2018-08-24-dataquest-hacker-news.md | nahusznaj/nahusznaj.github.io | ec66a3b8bb50c95b7354d1f60e4e88a00fa4e225 | [
"BSD-3-Clause",
"MIT"
] | 1 | 2018-08-28T06:05:29.000Z | 2018-08-28T06:05:29.000Z | ---
layout: article
title: Working with scripts
categories: projects
modified: 2018-08-23T00:28:11-04:00
tags: [python, dataquest]
comments: true
share: true
read_time: true
---
Find the py files that I created for my project on [Hacker News submissions](https://github.com/nahusznaj/Hackers_News_dataquest/).
This is part of my [dataquest.io]() course in data science!
Feel free to get in touch and discuss further analysis!
| 23.888889 | 131 | 0.765116 | eng_Latn | 0.965093 |
58a1ed43bb7ab0b6953d5ea7e20b43343fb81af9 | 2,400 | md | Markdown | _posts/13/2021-04-06-mason-mount.md | chito365/ukdat | 382c0628a4a8bed0f504f6414496281daf78f2d8 | [
"MIT"
] | null | null | null | _posts/13/2021-04-06-mason-mount.md | chito365/ukdat | 382c0628a4a8bed0f504f6414496281daf78f2d8 | [
"MIT"
] | null | null | null | _posts/13/2021-04-06-mason-mount.md | chito365/ukdat | 382c0628a4a8bed0f504f6414496281daf78f2d8 | [
"MIT"
] | null | null | null | ---
id: 5070
title: Mason Mount
date: 2021-04-06T18:36:56+00:00
author: Laima
layout: post
guid: https://ukdataservers.com/mason-mount/
permalink: /04/06/mason-mount
tags:
- claims
- lawyer
- doctor
- house
- multi family
- online
- poll
- business
- unspecified
- single
- relationship
- engaged
- married
- complicated
- open relationship
- widowed
- separated
- divorced
- Husband
- Wife
- Boyfriend
- Girlfriend
category: Guides
---
* some text
{: toc}
## Who is Mason Mount
Midfielder loaned out from Premier League club Chelsea FC to Vitesse and Derby County between 2017 and 2018. He is a long-time member of England’s under-age national teams.
## Prior to Popularity
He is a product of the Chelsea youth system, training with the club from 2005 to 2017.
## Random data
He has represented England at under-16, under-17, under-18, under-19 and under-21 levels. He was the Eredivisie Talent of the Month in January of 2018 and Vitesse Player of the Year in 2017-2018.
## Family & Everyday Life of Mason Mount
He was born Mason Tony Mount in Portsmouth, England. He shared a picture with his mom on his Instagram account in March 2017.
## People Related With Mason Mount
Gareth Southgate invited him to train with the senior England team ahead of the 2018 FIFA World Cup following his impressive season with Vitesse.
| 21.428571 | 195 | 0.422083 | eng_Latn | 0.998286 |
58a1fcd244e37bae0851740c61a150cbb39afe6d | 6,252 | md | Markdown | docs/dmx/topcount-dmx.md | peterkarman1/sql-docs | 7569551402944b31cf4d0059f7793903f9546722 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-01-03T02:37:57.000Z | 2020-01-03T02:37:57.000Z | docs/dmx/topcount-dmx.md | peterkarman1/sql-docs | 7569551402944b31cf4d0059f7793903f9546722 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/dmx/topcount-dmx.md | peterkarman1/sql-docs | 7569551402944b31cf4d0059f7793903f9546722 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-04-05T00:07:53.000Z | 2021-04-05T00:07:53.000Z | ---
title: "TopCount (DMX) | Microsoft Docs"
ms.date: 06/07/2018
ms.prod: sql
ms.technology: analysis-services
ms.custom: dmx
ms.topic: conceptual
ms.author: owend
ms.reviewer: owend
author: minewiskan
manager: kfile
---
# TopCount (DMX)
[!INCLUDE[ssas-appliesto-sqlas](../includes/ssas-appliesto-sqlas.md)]
Returns the specified number of top-most rows in decreasing order of rank as specified by an expression.
## Syntax
```
TopCount(<table expression>, <rank expression>, <count>)
```
## Applies To
An expression that returns a table, such as a \<table column reference>, or a function that returns a table.
## Return Type
\<table expression>
## Remarks
The value that is supplied by the \<rank expression> argument determines the decreasing order of rank for the rows that are supplied in the \<table expression> argument, and the number of top-most rows that is specified in the \<count> argument is returned.
The TopCount function was originally introduced to enable associative predictions and in general, produces the same results as a statement that includes **SELECT TOP** and **ORDER BY** clauses. You will obtain better performance for associative predictions if you use the **Predict (DMX)** function, which supports specification of a number of predictions to return.
However, there are situations where you might still need to use TopCount. For example, DMX does not support the **TOP** qualifier in a sub-select statement. The [PredictHistogram (DMX)](../dmx/predicthistogram-dmx.md) function also does not support the addition of **TOP**.
## Examples
The following examples are prediction queries against the Association model that you build by using the [Basic Data Mining Tutorial](http://msdn.microsoft.com/library/6602edb6-d160-43fb-83c8-9df5dddfeb9c). The queries return the same results, but the first example uses TopCount, and the second example uses the Predict function.
To understand how TopCount works, it may be helpful to first execute a prediction query that returns only the nested table.
```
SELECT Predict ([Association].[v Assoc Seq Line Items], INCLUDE_STATISTICS, 10)
FROM
[Association]
NATURAL PREDICTION JOIN
SELECT (SELECT 'Women''s Mountain Shorts' as [Model]) AS [v Assoc Seq Line Items]) AS t
```
> [!NOTE]
> In this example, the value supplied as input contains a single quotation mark, and therefore must be escaped by prefacing it with another single quotation mark. If you are not sure of the syntax for inserting an escape character, you can use the Prediction Query Builder to create the query. When you select the value from the dropdown list, the required escape character is inserted for you. For more information, see [Create a Singleton Query in the Data Mining Designer](../analysis-services/data-mining/create-a-singleton-query-in-the-data-mining-designer.md).
Example results:
|Model|$SUPPORT|$PROBABILITY|$ADJUSTEDPROBABILITY|
|-----------|--------------|------------------|--------------------------|
|Sport-100|4334|0.291283016|0.252695851|
|Water Bottle|2866|0.192620472|0.175205052|
|Patch kit|2113|0.142012232|0.132389356|
|Mountain Tire Tube|1992|0.133879965|0.125304948|
|Mountain-200|1755|0.117951475|0.111260823|
|Road Tire Tube|1588|0.106727603|0.101229538|
|Cycling Cap|1473|0.098998589|0.094256014|
|Fender Set - Mountain|1415|0.095100477|0.090718432|
|Mountain Bottle Cage|1367|0.091874454|0.087780332|
|Road Bottle Cage|1195|0.080314537|0.077173962|
The TopCount function takes the results of this query and returns the specified number of the smallest-valued rows.
```
SELECT
TopCount
(
Predict ([Association].[v Assoc Seq Line Items],INCLUDE_STATISTICS,10),
$SUPPORT,
3)
FROM
[Association]
NATURAL PREDICTION JOIN
(SELECT (SELECT 'Women''s Mountain Shorts' as [Model]) AS [v Assoc Seq Line Items]) AS t
```
The first argument to the TopCount function is the name of a table column. In this example, the nested table is returned by calling the Predict function and using the INCLUDE_STATISTICS argument.
The second argument to the TopCount function is the column in the nested table that you use to order the results. In this example, the INCLUDE_STATISTICS option returns the columns $SUPPORT, $PROBABILTY, and $ADJUSTED PROBABILITY. This example uses $SUPPORT to rank the results.
The third argument to the TopCount function specifies the number of rows to return, as an integer. To get the top three products, as ordered by $SUPPORT, you type 3.
Example results:
|Model|$SUPPORT|$PROBABILITY|$ADJUSTEDPROBABILITY|
|-----------|--------------|------------------|--------------------------|
|Sport-100|4334|0.29…|0.25…|
|Water Bottle|2866|0.19…|0.17…|
|Patch kit|2113|0.14…|0.13…|
However, this type of query might affect performance in a production setting. This is because the query returns a set of all predictions from the algorithm, sorts these predictions, and returns the top 3.
The following example provides an alternative statement that returns the same results but executes significantly faster. This example replaces TopCount with the Predict function, which accepts a number of predictions as an argument. This example also uses the **$SUPPORT** keyword to directly retrieve the nested table column.
```
SELECT Predict ([Association].[v Assoc Seq Line Items], INCLUDE_STATISTICS, 3, $SUPPORT)
```
The results contain the top 3 predictions sorted by the support value. You can replace $SUPPORT with $PROBABILITY or $ADJUSTED_PROBABILITY to return predictions ranked by probability or adjusted probability. For more information, see **Predict (DMX)**.
## See Also
[Functions (DMX)](../dmx/functions-dmx.md)
[General Prediction Functions (DMX)](../dmx/general-prediction-functions-dmx.md)
[BottomCount (DMX)](../dmx/bottomcount-dmx.md)
[TopPercent (DMX)](../dmx/toppercent-dmx.md)
[TopSum (DMX)](../dmx/topsum-dmx.md)
| 53.896552 | 570 | 0.710333 | eng_Latn | 0.972376 |
58a20b51ee4eabde0a28a4f2ad6e2570ae7396e4 | 44,056 | markdown | Markdown | _posts/2008-02-28-portable-device-upgrade-via-a-content-transfer-protocol.markdown | api-evangelist/patents-2008 | fa7a9f82abec3c65c55cab3b2a849b335fd2f75e | [
"Apache-2.0"
] | null | null | null | _posts/2008-02-28-portable-device-upgrade-via-a-content-transfer-protocol.markdown | api-evangelist/patents-2008 | fa7a9f82abec3c65c55cab3b2a849b335fd2f75e | [
"Apache-2.0"
] | null | null | null | _posts/2008-02-28-portable-device-upgrade-via-a-content-transfer-protocol.markdown | api-evangelist/patents-2008 | fa7a9f82abec3c65c55cab3b2a849b335fd2f75e | [
"Apache-2.0"
] | 5 | 2019-07-11T06:07:03.000Z | 2020-08-13T12:57:05.000Z | ---
title: Portable device upgrade via a content transfer protocol
abstract: Embodiments of the present invention provide a portable MTP framework. In an embodiment, the portable MTP framework includes an MTP communications stack and a portability layer. The portability layer decouples the MTP communications stack from the underlying platform, storage, and transport components, thereby achieving transport protocol, platform, and storage media independence. The portable MTP framework according to embodiments of the present invention includes platform-specific software components, including, for example, communications device drivers (USB, TCP/IP, etc.), a transport controller, a session handler, storage device drivers (USB drive, SD card, Hard disk, etc.), a storage controller, and a platform interface. The portable MTP framework further includes application-specific software components, including, for example, an MTP router, MTP agents, and MTP managers.
url: http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&p=1&u=%2Fnetahtml%2FPTO%2Fsearch-adv.htm&r=1&f=G&l=50&d=PALL&S1=08788634&OS=08788634&RS=08788634
owner: Broadcom Corporation
number: 08788634
owner_city: Irvine
owner_country: US
publication_date: 20080228
---
The present application is related to U.S. patent application Ser. No. 12 071 987 filed Feb. 28 2008 U.S. patent application Ser. No. 12 071 988 filed Feb. 28 2008 and U.S. patent application Ser. No. 12 071 989 filed Feb. 28 2008 all of which are herein incorporated by reference in their entirety.
The present invention relates generally to portable device communications and more particularly to a portable communications framework.
Media Transfer Protocol MTP was developed as an extension to Picture Transfer Protocol PTP and is directed particularly to digital cameras portable media players and cellular phones.
One purpose of MTP is to facilitate communication with media devices that have transient connectivity and significant storage capacity. These media devices can be generally described as having intermittent or infrequent connections with a computer system or other device and typically fulfill their primary functionality while not connected to a computer system or other device.
Another purpose of MTP is to enable command and control of these media devices including remote invocation of device functionality monitoring of device initiated events and reading setting of device properties.
MTP is transport protocol independent. In other words MTP objects can be transported within virtually any transport protocol including USB Universal Serial Bus TCP IP Transmission Control Protocol Internet Protocol and Bluetooth for example. MTP is also operating system and file system independent. However conventional MTP frameworks are typically designed for specific transport operating system and file system configurations.
There is a need therefore for a portable MTP framework which is decoupled from the specific details of the device transport platform and storage systems thereby being usable in a variety of portable devices irrespective of the supported device transport platform and storage.
Embodiments of the present invention provide a portable MTP framework. In an embodiment the portable MTP framework includes an MTP communications stack and a portability layer. The portability layer decouples the MTP communications stack from the underlying platform storage and transport components thereby achieving transport protocol platform and storage media independence.
The portable MTP framework according to embodiments of the present invention includes platform specific components including for example communications device drivers USB TCP IP etc. a transport controller a session handler storage device drivers USB drive SD card Hard disk etc. a storage controller and a platform interface. The portable MTP framework farther includes application specific components including for example an MTP router MTP agents and MTP managers.
Further embodiments features and advantages of the present invention as well as the structure and operation of the various embodiments of the present invention are described in detail below with reference to the accompanying drawings.
The present invention will be described with reference to the accompanying drawings. Generally the drawing in which an element first appears is typically indicated by the leftmost digit s in the corresponding reference number.
MTP was developed as an extension to Picture Transfer Protocol PTP and is directed particularly to digital cameras portable media players and cellular phones.
One purpose of MTP is to facilitate communication with media devices that have transient connectivity and significant storage capacity. These media devices can be generally described as having intermittent connections with a computer system or other device and typically fulfill their primary functionality while not connected to a computer system or other device.
Another purpose of MTP is to enable command and control of these media devices including remote invocation of device functionality monitoring of device initiated events and reading setting of device properties.
It is noted that when used in the context of MTP the term media is used to identify any binary data and is not limited to audio video. Examples of non audio video data include contacts programs scheduled events and text files.
MTP follows a communication model in which MTP exchanges may only occur between two devices at a given time. is a block diagram that illustrates the MTP communication model. A first device acts as an MTP Initiator and a second device acts as an MTP Responder. MTP Initiator and MTP Responder are linked by a communications link that supports MTP communication. MTP Initiator may be for example a host computer and MTP Responder may be for example a hand held device. MTP Initiator and MTP Responder each includes suitable logic circuitry and or code as illustrated by processors and in to enable transfer of information via MTP.
MTP initiator initiates actions with MTP Responder by sending operations to MTP Responder over communications link . In response to operations MTP Responder sends responses to MTP Initiator . Typically MTP Responder does not initiate actions but may send unsolicited events to MTP Initiator .
Data flow in MTP is unidirectional. When an operation is initiated data flows from MTP Initiator to MTP Responder . Conversely data flows from MTP Responder to MTP Initiator when a response is being sent. As such bi directional flow occurs over multiple sequential operations responses.
Generally communication between MTP Initiator and MTP Responder is performed using MTP transactions where an MTP transaction includes up to three phases an Operation Request Phase an optional Data Phase and a Response Phase. A transaction ID is associated with data being communicated in each phase to identify the data as relating to the same MTP transaction. Generally the MTP Initiator generates transaction IDs incremented by one for each successive transaction.
A state diagram illustrating an MTP transaction is shown in . As shown an MTP transaction begins in an Operation Request Phase which includes initiating a transaction by transmitting an Operation dataset from the MTP Initiator to the MTP Responder. The Operation dataset identifies the operation being invoked by the MTP Initiator the context in which it is to be executed and includes a limited set of parameters. illustrates the data structure of an Operation dataset. As shown the Operation dataset includes an Operation Code field which identifies the operation being initiated. MTP supports a variety of operations including for example operations related to objects at the MTP Responder e.g. GetObject MoveObject etc. operations related to the MTP Responder device ResetDevice PowerDown etc. and operations related to the device storage e.g. FormatStore GetStorageInfo etc. . A complete description of MTP Operations and their usages can be found in the MTP specification which is incorporated herein by reference in its entirety.
Further as shown in the Operation dataset may include a Session ID a Transaction ID and up to five parameters.
The Session ID identifies an MTP session within which the operation exists which represents a communication state in which a connection has persisted between the MTP Initiator and the MTP Responder and a state has been maintained. Within a given session the MTP Responder state does not change without alerting the MTP Initiator to the change. It is noted that certain operations do not require a SessionID as they may be executed within or without an active session.
The operation parameters include information required to execute the operation. The contents of these parameters depend on the Operation Code field and or the context in which the operation is being used.
Referring back to an optional Data Phase may follow the Operation Request Phase . Typically the Data Phase is used to send any data that cannot be transferred using the parameters of the Operation dataset during the Operation Request phase. The type of data sent in the Data Phase also depends on the operation. For example for certain operations the data consists of datasets defined by the MTP specification. For others the data is binary data exchanged for the purpose of storage on the MTP Responder device.
Whether or not a Data Phase follows the Operation Request Phase depends on the operation sent in the Operation Request Phase . A typical example involves the sending of objects from an MTP Initiator to an MTP Responder which includes the MTP Initiator sending a SendObjectInfo operation which includes an ObjectInfo dataset in its data field in the Operation Request phase followed by a SendObject operation which includes the object in binary data in its data field in the Data Phase. The ObjectInfo dataset provides transfer context to the MTP Responder allowing it to allocate appropriate resources for the transfer.
It is noted that data flow in the Data Phase can be from the MTP Initiator to the MTP Responder or vice versa.
An MTP transaction terminates with a Response Phase as shown in . The Response Phase includes the MTP Responder transmitting a Response dataset to the MTP Initiator in response to the operation. illustrates the data structure of an MTP Response. As shown a Response dataset may include a Response Code a Session ID a Transaction I and up to five parameters.
The Response code identifies the result of the operation request. Response code options depend on the operation request and or the response context. The Session ID Transaction ID and the parameters serve substantially similar functions as described above with respect to the Operation dataset.
As described above MTP transactions are initiated only by the MTP Initiator. As such a mechanism is needed to enable the MTP Responder to proactively transmit information or alerts to the MTP Initiator. This is accomplished using Events in MTP which are typically one way transmissions from the MTP Responder to the MTP Initiator the MTP Initiator may also send events .
Events in MTP are not intended to convey information beyond the notification of a change of a given state at the MTP Responder. As such events are communicated to the MTP Initiator in the form of an event dataset which includes a minimum of required information to describe the event including an event code for example. When the event code alone is not sufficient to convey all information related to the event the receiving device the MTP Initiator is generally made to probe the sending device the MTP Responder for more information after receiving the initial event dataset. illustrates the data structure of an MTP Event. As shown an Event dataset may include an Event Code a Session ID a Transaction ID and up to three parameters. The Event Code field identifies the event being indicated by the dataset. A listing of event codes and their meanings can be found in the MTP specification.
Device representation in MTP is designed such that the capabilities and properties of a device can be exploited to enable a number of features including rich user interface UI representation of a connected device matching of content to device capabilities meta functionality on objects device state awareness and device command and control. These features are implemented by a combination of a device describing dataset DeviceInfo Dataset and flexible and extensible device properties. illustrates the MTP DeviceInfo dataset. The DeviceInfo dataset is used to provide a description of the device and can be obtained using the GetDeviceInfo operation. As shown in the DeviceInfo dataset includes among other fields a Device Properties Supported field which identifies by code all device properties that the device supports in its current functional mode. The device properties identify settings or state conditions of the device and are not linked to any data objects on the device. Device properties may be read only or read write and are defined by their DevicePropDesc dataset which can be retrieved with the GetDevicePropDesc operation. The DevicePropDesc dataset provides for example the device property value read write settings a default value and where relevant any restrictions on allowed property values.
MTP devices generally include a substantial amount of persistent data storage either within the device or on removable storage. Storage in MTP is identified using a 32 bit unsigned integer called a StorageID. The StorageID is subdivided into two halves with the most significant half identifying a physical storage location and the least significant half identifying a logical partition of the physical storage. Storage description is done using the StorageInfo dataset which is illustrated in . As shown the StorageInfo dataset includes among others a Storage Type field and a Filesystem Type field. The StorageType field identifies the physical nature of the storage described by the StorageInfo data set which may be a fixed Read Only Memory ROM removable ROM Fixed Random Access Memory RAM or Removable RAM. The Filesystem Type field identifies the logical file system including the file naming or directory structure conventions in used on the storage.
MTP is file system independent. As such MTP uses objects which are abstract containers to encapsulate media or other structured data. Examples of objects include for example image files audio video files contacts calendar task items and generic binary files.
An MTP object includes four parts the object s binary data the ObjectInfo dataset object properties and object references. The ObjectInfo dataset is a standard fixed dataset available for every object which provides basic information about the object. The ObjectInfo dataset was originally defined in PTP and has been largely replaced in MTP by Object Properties.
Object properties provide a flexible and extensible way of representing object metadata. Object properties serve to not only describe the actual content of the object but also to indirectly indicate the various structures a particular object format can take. Further object properties provide a mechanism for exchanging object describing metadata separate from the objects themselves thereby permitting the rapid enumeration of large storages regardless of the file system. Object properties are defined by an ObjectPropDesc dataset which is illustrated in .
To support object properties a device will be required to support the following operations GetObjectPropsSupported GetObjectPropValue and GetObjectPropDesc. Operations support of a device is listed in the DeviceInfo dataset of the device. A device that further supports the setting of object properties supports the SetObjectPropValue operation.
In step the Initiator initiates a GetObjectHandles operation in response to which the Responder sends the ObjectHandle array.
In step the Initiator initiates a GetObjectPropSupported operation to which the Responder responds by sending the ObjectPropCode array which includes codes of object properties supported.
In steps and the Initiator requests descriptions of the object properties by repeatedly invoking the GetObjectPropDesc operation for all object handles received in step . In response to each GetObjectPropDesc operation the Responder responds by sending the corresponding ObjectPropDesc dataset. Subsequently in steps and the Initiator requests the values of the object properties by repeatedly invoking the GetObjectPropValue for object handles received in step . In response to each GetObjectPropValue operation the Responder responds by sending the value of the corresponding object property.
MTP is transport protocol independent. In other words MTP objects can be transported within virtually any transport protocol including USB TCP IP and Bluetooth for example. MTP is also operating system and file system independent. However conventional MTP frameworks are typically designed for specific transport operating system and file system configurations.
There is a need therefore for a portable MTP framework which is decoupled from the specific details of the device transport platform and storage systems thereby being usable in a variety of portable devices irrespective of the supported device transport platform and storage.
Embodiments of the present invention provide a portable MTP framework. In an embodiment the portable MTP framework includes an MTP communications stack and a portability layer. The portability layer decouples the MTP communications stack from the underlying platform storage and transport components thereby achieving transport protocol platform and storage media independence.
The portable MTP framework according to embodiments of the present invention includes platform specific software components including for example communications device drivers USB TCP IP etc. a transport controller a session handler storage device drivers USB drive SD card Hard disk etc. a storage controller and a platform interface. The portable MTP framework further includes application specific software components including for example an MTP router MTP agents and MTP managers.
Transport Controller layer provides an Application Programming Interface API to abstract a plurality of different transport protocols including USB TCP IP WIFI and Bluetooth. Session Handler layer provides coarse level packet inspection and session management functionalities. MTP Router layer provides application specific packet routing functionalities. MTP Agents layer provides application specific fine level packet inspection and management functionalities. MTP Managers layer provides application specific MTP logic. MTP Applications layer include end user applications. Further description of the different layers and components of portable MTP framework will be further described below.
Portable MTP framework can be implemented within a portable MTP device and enables the device to act as either an MTP Initiator or an MTP Responder. When the portable device acts as an MTP Responder as is primarily the case the MTP stack responds to Operations and Events sent by an MTP Initiator such as a Windows Media Player application for example running on a computer attached to the device. The MTP stack may also initiate asynchronous MTP Events for reporting specific events at the portable device.
As shown in portable MTP framework includes a Transport controller a Session handler a Responder Router a plurality of MTP agents and a plurality of MTP managers . These components correspond substantially to Transport Controller layer Session Handler layer MTP Router layer MTP Agents layer and MTP Managers layer respectively of portable MTP framework described above. Portable MTP framework further includes a DataPhaseAccelerator component which makes part of the Session Handler layer and communicates with Session Handler .
Portable MTP framework further provides a plurality of APIs including for example a Platform Interface component a Storage Controller component and a Metadata Manager component .
As described above Transport controller is a platform software component which serves to abstract the specific details of the transport protocol used e.g. USB TCP IP etc. from upper layers of portable MTP framework . In other words Transport controller enables MTP objects to be communicated over various transport mechanisms in a manner transparent to the upper layers of the MTP stack. In an embodiment Transport controller hides the details of interfacing with the underlying transport by providing a common API with a common set of transport data structures to the upper layers of portable MTP framework .
In an embodiment Transport controller supports multiple simultaneous transports and provides interfaces for three separate simultaneous channels per transport including a control channel a payload channel and an event channel. The control channel is used to carry MTP control information including Operation Event and Response Datasets. The payload channel is used for the transfer of payload data including structured metadata and binary media file data. The event channel is used to send asynchronous events from the MTP Responder to the an MTP Initiator.
Session handler provides an interface between upper layers of portable MTP framework and Transport Controller . In particular session handler provides a coarse grained packet inspection function of incoming control data to ensure that valid Operation Event and Response datasets are received before passing them to the upper layers of portable MTP framework . Subsequently session handler routes the incoming control data to either Responder Router in the case of an MTP Responder as illustrated in or to appropriate MTP Initiator code in the case of an MTP Initiator .
In addition session handler provides an API for sending MTP Operation Event and Response datasets over a control channel of the transport. The API can be used by either MTP Initiator code or MTP Responder code. As such session handler supports both MTP Responder and MTP Initiator roles. Further session handler provides an API for sending and receiving payload data including metadata datasets and media files over a payload channel of the transport.
Session handler further provides an API for optimized sending and receiving of payload data between storage drivers and the transport within portable MTP framework . This API is referred to herein as DataPhaseAccelerator and will be described in further detail below.
Session handler further provides session management functionality including management of the OpenSession and CloseSession operations. Generally one session is allowed for incoming traffic and one session is allowed for outgoing traffic i.e. one session per Initiator role and one session per Responder role .
If a DataPhaseInterrupt is received the state machine proceeds to state which includes invoking the DataPhaseAccelerator API. The DataPhaseAccelerator then controls the details of the data transfer between the storage systems and the transport. Otherwise the state machine proceeds to state which includes inspecting the incoming packet to determine whether it is a valid MTP Operation Event or Response dataset.
If the incoming packet is an unrecognized dataset the state machine proceeds to state and then to state which includes sending a response code to indicate incomplete transfer. If on the other hand the incoming packet is recognized as an MTP packet the state machine proceeds to state and then to either state or state depending on whether or not a session is currently open.
If a session is currently open the state machine proceeds to state . Subsequently if the incoming packet is a closeSession operation the state machine proceeds to close the session by moving into states and successively. Similarly the state machine proceeds to close the session if the incoming packet is a cancelTransaction event by moving into states and successively. If the incoming packet however is a valid dataset the state machine proceeds to send the incoming packet to the router in states and .
If no session is currently open the session handler may also be able to handle the incoming packet if it is one of certain operations which do not require an open session. As shown in the incoming packet may be a GetDeviceInfo operation which the session handler manages by forwarding it to the router which routes the incoming packet to the appropriate device in states and . The incoming packet may also be an OpenSession operation which the session handler manages by proceeding through states and successively to send an Open Session response and set the Session state as open. On the other hand if the incoming packet is an unsolicited packet that does not match any of the two operations just described the state machine proceeds through states and to send a response code indicating that the session is not opened.
As described above the session handler provides a data transfer optimization API to optimize data transfer between an Initiator e.g. Windows Media Player running on a computer and a Responder e.g. portable device . This includes among other features optimizing data transmission between the storage devices and the transport layer. In an embodiment as illustrated in this is achieved by implementing a common API DataPhaseAccelerator API shared by Transport Controller and Storage Controller will be described further below which manages all the underlying details of interfacing the transport and storage layers to allow for maximum data transfer performance.
DataPhaseAccelerator API can be used to transfer the binary portion of large media files when a GetObject SendObject operation is invoked by the Initiator to retrieve send an object from to the Responder.
DataPhaseAccelerator API also handles any interrupts to data transfer independently from Session Handler . This is described in which illustrates a state machine diagram of the DataPhaseAccelerator interrupt handling functionality. As shown state machine begins in state which includes receiving control data. If the control data received is a CloseSession operation state machine proceeds to state . Subsequently if the data phase is inactive state machine proceeds to state before returning to the session handler in state . However if the data phase is active which means that either a data send or a data receive is in progress state machine will proceed to either state or state as shown in . State machine will then proceed to either state or state to stop the data send receive before returning to the session handler in state . On the other hand if the control data received is a CancelTransaction event state machine proceeds to state . Subsequently state machine as shown in will behave in a similar manner as described above with respect to the CloseSession operation. If the control data received is any other operation event code state machine will proceed to state and then return to the session handler in step .
State machine can be implemented in various hardware software and or firmware topologies including sub embedded software running on an embedded processor for example.
Storage controller of portable MTP framework is a platform software component which provides an API to abstract the interfacing with supported device storage systems. As shown in for example storage controller provides an interface with an IDE Integrated Drive Electronics Drive an SDRAM Synchronous Dynamic Random Access Memory memory and a USB memory stick.
In an embodiment abstracting the interfacing with storage systems includes abstracting file operations e.g. open read write delete close etc. and partition mounting of storage partitions including among others DRM Digital Rights Management stores metadata databases and removable storage. Generally storage controller discovers storage partitions through Platform interface which in certain platforms retrieves partitions information from NVRAM non volatile RAM .
In another embodiment storage controller further manages notification events for hot plug and hot unplug removable storage calls appropriate code to update the database e.g. add objects and initiates events via MTP as needed. For example storage controller initiates MTP events such as StoreAdded StoreRemoved to indicate the addition removal of a storage system.
Also as described above storage controller supports data transmission optimization for data transfer with Transport Controller using DataPhaseAccelerator API .
In a further embodiment storage controller manages the enumeration and un enumeration of media files on fixed and or removable storage partitions.
Platform interface of portable MTP framework is a platform software component which provides several APIs to support the portability of platform specific resources. For example platform interface provides a portability API to abstract platform resources and libraries including file systems and persistent storage e.g. NVRAM . In an embodiment the portability API includes a run time API that supports file system abstraction e.g. open read write etc. of persistent storage. Platform interface further provides a user notification interface API which allows portable MTP framework to provide error and status messages to an application for display in a GUI.
In another aspect platform interface provides a Firmware Upgrade API which enables a firmware upgrade cycle of the device via MTP. is a process flowchart that illustrates a method of performing firmware upgrade using MTP according to an embodiment of the present invention. Process begins in step which includes receiving an MTP object. In an embodiment step is achieved via the SendObject MTP operation.
Step includes routing the received object to the Object Agent of portable MTP Framework . As shown in the Object Agent is an MTP agent located in the Agents layer of portable MTP framework .
Step includes determining if the received object is a firmware upgrade object. In an embodiment step includes checking the received object for the undefined firmware property code which is a property code associated with a firmware upgrade object in MTP. In other embodiments step includes checking a specified file type or file name associated with a firmware upgrade object.
If the received object is not a firmware upgrade object process proceeds to step which includes calling the Object Manager to appropriately handle the received object.
On the other hand if the received object is determined to be a firmware upgrade object in step process proceeds to step which includes calling the Firmware Manager to initiate the firmware upgrade process. Note that the Firmware Manager not shown in is a unique manager in MTP in that it requires no corresponding MTP agent.
Subsequently step includes calling the Firmware Upgrade API of platform interface by passing it the received object. When the Firmware Upgrade API receives the object it proceeds in step to shut down all system processes install the firmware upgrade and initiate a reboot of the device.
Note that the firmware upgrade cycle modifies the MTP DeviceInfo dataset of the device to reflect the upgraded firmware information. Generally the new firmware information is stored in the NVRAM of the device and will be reported to the initiator e.g. Windows Media Player on PC via a SendDeviceInfo response.
Metadata manager provides an API that can be used by native application components e.g. Media Player application GUIs etc. as well as MTP stack components e.g. Object manager Playback manager etc. of portable MTP framework to manage metadata. In an embodiment Metadata manager uses Database controller which is a database interface code to control the database.
Database controller provides primitive database operations including an API abstraction for storing and retrieving MTP Object Properties and Object Associations in a database. In an embodiment Database controller provides SQL database operations.
As noted above the MTP database can be accessed via Metadata manager by either MTP stack components and native GUI applications illustrated in as Applications GUI . However the behavior of portable MTP framework is different with respect to the MTP database based on the operating mode of the framework. According to embodiments of the present invention portable MTP framework can operate in the following modes
During this mode the portable MTP framework does not run. As such it is for the native GUI application to notify the portable MTP framework of any objects which have been added removed from the portable device while in this mode.
As described above in certain operating modes the native GUI application may modify the database while the portable MTP framework is not running. These changes need to be reported to the remote PC initiator. Accordingly a mechanism is needed to notify the portable MTP framework of any changes made to the database when the portable MTP framework returns to Slave mode.
According to an embodiment of the present invention this is achieved using Change Tables which are tables created and updated by Database controller every time the native GUI application accesses database controller via metadata manager to reflect changes to objects or storage. illustrates an exemplary database change table according to an embodiment of the present invention. As shown the database change table includes listings of changes to objects and to storages.
In an embodiment change tables are maintained transparently in database controller for all database transactions. However they are only used during startup of the portable MTP framework. For example upon entering Slave mode the change tables are processed by the portable MTP framework and appropriate events are sent to the remote PC initiator. The change tables are then be deleted. is a state machine diagram which illustrates the usage of database change tables. As shown state machine diagram begins with the initialization of the portable MTP framework in states and . Subsequently state machine proceeds to either state or state depending on whether or not the portable device is connected to the remote PC initiator.
If the portable device is connected to the remote PC initiator state machine proceeds to state which includes shutting down the native GUI application and then to state which includes starting the portable MTP framework in Slave mode. Subsequently state machine proceeds to reading the change tables in state and sending object events in state and storage events in state . Then state machine proceeds to state which includes purging the change tables before returning control to MTP Responder Router in state . illustrates example MTP events that the portable MTP framework may send to a remote PC initiator based on the change tables.
On the other hand if the portable device is not connected to the remote PC initiator state machine proceeds to state which includes shutting down the portable MTP framework and then to state which includes starting up the native GUI application. The portable MTP framework thus enters into the native GUI mode in state . During this mode as described above the native GUI application may access the database to add objects via state remove objects via state or to enumerate media files via state . As shown the native GUI application accesses the database via metadata manager in state which in turn uses database controller in state . Throughout this operating mode as described above database controller maintains changes to the database in change tables as illustrated in state .
Accordingly the above described mechanism allows the creation of an audit trail of database changes when the portable MTP framework is shut down which can be communicated to the remote PC initiator as soon as the portable MTP framework is restarted. In other words this enables an automatic synchronization mechanism via MTP of a shared database between the portable device and the remote PC initiator.
As shown in portable MTP framework includes a responder router a plurality of MTP agents and a plurality of MTP managers .
Responder router performs the functions of 1 routing received MTP Operations and Events to an appropriate agent of MTP agents and 2 returning MTP Responses to Transport controller on behalf of MTP agents .
MTP agents and MTP managers are designed to operate in a paired fashion as shown in . Generally MTP agents deal with MTP protocol specific issues e.g. packing and unpacking MTP packets on behalf of MTP managers . MTP agents can be initiator agents or responder agents. Since portable devices are primarily used as MTP Responders the majority of agents in portable MTP framework are responder agents. However portable MTP framework can also be designed to be implemented within an initiator according to the present invention.
MTP managers deal with application specific issues such as interfacing with the GUI application and the database. As with agents MTP managers can be initiator or responder agents. As shown in MTP managers access Platform interface Database Controller Storage Controller and the DRM library as needed.
Various example use cases are provided in this section in the form of sequence diagrams to illustrate the operation of and interaction between different components of the portable MTP framework. These example use cases are provided for the purpose of illustration and are not limiting of possible operations interactions and or functions allowed by the various components of the portable framework.
The present invention may be implemented using hardware software or a combination thereof and may be implemented in one or more computer systems or other processing systems.
Computer system includes one or more processors such as processor . Processor is connected to a communication infrastructure e.g. a communications bus cross over bar or network . Various software embodiments are described in terms of this exemplary computer system. After reading this description it will become apparent to a person skilled in the relevant art s how to implement the invention using other computer systems and or architectures.
Computer system can include a display interface that forwards graphics text and other data from communication infrastructure or from a frame buffer not shown for display on display unit .
Computer system also includes a main memory preferably random access memory RAM and may also include a secondary memory . Secondary memory may include for example a hard disk drive and or a removable storage drive representing a floppy disk drive a magnetic tape drive an optical disk drive etc. Removable storage drive reads from and or writes to a removable storage unit in a well known manner. Removable storage unit represents a floppy disk magnetic tape optical disk etc. which is read by and written to by removable storage drive . As will be appreciated removable storage unit includes a computer usable storage medium having stored therein computer software and or data.
In alternative embodiments secondary memory may include other similar devices for allowing computer programs or other instructions to be loaded into computer system . Such devices may include for example a removable storage unit and an interface . Examples of such may include a program cartridge and cartridge interface such as that found in video game devices a removable memory chip such as an erasable programmable read only memory EPROM or programmable read only memory PROM and associated socket and other removable storage units and interfaces which allow software and data to be transferred from removable storage unit to computer system .
Computer system may also include a communications interface . Communications interface allows software and data to be transferred between computer system and external devices. Examples of communications interface may include a modem a network interface such as an Ethernet card a communications port a Personal Computer Memory Card International Association PCMCIA slot and card etc. Software and data transferred via communications interface are in the form of signals which may be electronic electromagnetic optical or other signals capable of being received by communications interface . These signals are provided to communications interface via a communications path e.g. channel . This channel carries signals and may be implemented using wire or cable fiber optics a telephone line a cellular link an radio frequency RF link and other communications channels.
In this document the terms computer program medium and computer usable medium are used to generally refer to media such as removable storage drive a hard disk installed in hard disk drive and signals . These computer program products provide software to computer system .
Computer programs also referred to as computer control logic are stored in main memory and or secondary memory . Computer programs may also be received via communications interface . Such computer programs when executed enable computer system to perform the features of the present invention as discussed herein. In particular the computer programs when executed enable processor to perform the features of the present invention. Accordingly such computer programs represent controllers of computer system .
In an embodiment where the invention is implemented using software the software may be stored in a computer program product and loaded into computer system using removable storage drive hard drive or communications interface . The control logic software when executed by processor causes processor to perform the functions of the invention as described herein.
In another embodiment the invention is implemented primarily in hardware using for example hardware components such as application specific integrated circuits ASICs . Implementation of the hardware state machine so as to perform the functions described herein will be apparent to persons skilled in the relevant art s .
In yet another embodiment the invention is implemented using a combination of both hardware and software.
Embodiments of the invention may also be implemented as instructions stored on a machine readable medium which may be read and executed by one or more processors. A machine readable medium may include any mechanism for storing or transmitting information in a form readable by a machine e.g. a computing device . For example a machine readable medium may include read only memory ROM random access memory RAM magnetic disk storage media optical storage media and flash memory devices
Further firmware software routines instructions may be described herein as performing certain actions. However it should be appreciated that such descriptions are merely for convenience and that such actions in fact result from computing devices processors controllers or other devices executing the firmware software routines instructions etc.
While various embodiments of the present invention have been described above it should be understood that they have been presented by way of example only and not limitation. It will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the spirit and scope of the invention. Thus the breadth and scope of the present invention should not be limited by any of the above described exemplary embodiments but should be defined only in accordance with the following claims and their equivalents.
| 202.091743 | 1,314 | 0.829444 | eng_Latn | 0.999612 |
58a397be3bbb76640e6e65e66336815f89aa01d6 | 112 | md | Markdown | README.md | KingsukMajumdar/Power-Electronic-LTspice | ab918acc10309c7d1ad2cbc89986d2b174d2fcbf | [
"MIT"
] | null | null | null | README.md | KingsukMajumdar/Power-Electronic-LTspice | ab918acc10309c7d1ad2cbc89986d2b174d2fcbf | [
"MIT"
] | null | null | null | README.md | KingsukMajumdar/Power-Electronic-LTspice | ab918acc10309c7d1ad2cbc89986d2b174d2fcbf | [
"MIT"
] | null | null | null | # Power-Electronic-LTspice
Basic of power electronics circuits and their simulations using LTspice in Linux OS
| 37.333333 | 84 | 0.830357 | eng_Latn | 0.971677 |
58a4a4b5162799d51eb550ea559f03bdd484f0a4 | 645 | md | Markdown | source/patches/sites/tools.suckless.org/dmenu/index.md | Scottx86-64/dotfiles-1 | 51004b1e2b032664cce6b553d2052757c286087d | [
"Unlicense"
] | 1 | 2021-11-20T22:46:39.000Z | 2021-11-20T22:46:39.000Z | source/patches/sites/tools.suckless.org/dmenu/index.md | Scottx86-64/dotfiles-1 | 51004b1e2b032664cce6b553d2052757c286087d | [
"Unlicense"
] | null | null | null | source/patches/sites/tools.suckless.org/dmenu/index.md | Scottx86-64/dotfiles-1 | 51004b1e2b032664cce6b553d2052757c286087d | [
"Unlicense"
] | null | null | null | dmenu
=====
dmenu is a dynamic menu for X, originally designed for
[dwm](//dwm.suckless.org/). It manages large numbers of user-defined menu items
efficiently.
Download
--------
* [dmenu-5.0](//dl.suckless.org/tools/dmenu-5.0.tar.gz) (2020-09-02)
Mailing list
------------
* `[email protected]` ([Archives](//lists.suckless.org/dev/))
([Old Archives](//lists.suckless.org/dwm/)) (see
[community](//suckless.org/community/) for details)
Development
-----------
You can [browse](//git.suckless.org/dmenu) its source code repository or get a
copy using git with the following command:
git clone https://git.suckless.org/dmenu
| 24.807692 | 79 | 0.688372 | eng_Latn | 0.773793 |
58a700e3224913448835d194262e3e12f73f6035 | 296 | md | Markdown | README.md | gotchaproglan/gotcha | 9042e5b8467ddc88e45bc8e5e68a7ff56e49f503 | [
"MIT"
] | 1 | 2018-08-25T20:49:55.000Z | 2018-08-25T20:49:55.000Z | README.md | gotchaproglan/gotcha | 9042e5b8467ddc88e45bc8e5e68a7ff56e49f503 | [
"MIT"
] | null | null | null | README.md | gotchaproglan/gotcha | 9042e5b8467ddc88e45bc8e5e68a7ff56e49f503 | [
"MIT"
] | null | null | null | Gotcha
======
Interpreted programming language that run on the JVM.
Features
========
* OOP
* High Order Functions
* Significant white spaces (Python)
* No semicolons
To Do
-----
* Add todo tasks
Copyright
---------
Copyright (c) 2011 Gotcha Development Team. See LICENSE for details.
| 10.962963 | 68 | 0.675676 | eng_Latn | 0.632447 |
58a704fa0e9f15cbae782ef23b813f731ec8ed1c | 40 | md | Markdown | README.md | colorstheforce/GL_TCH | 627b5445433b294e9f07c7db8fa0343222cbe402 | [
"MIT"
] | null | null | null | README.md | colorstheforce/GL_TCH | 627b5445433b294e9f07c7db8fa0343222cbe402 | [
"MIT"
] | null | null | null | README.md | colorstheforce/GL_TCH | 627b5445433b294e9f07c7db8fa0343222cbe402 | [
"MIT"
] | null | null | null | # GL_TCH
Gl_TCHCRAFT at the reliquarium
| 13.333333 | 30 | 0.825 | eng_Latn | 0.958282 |
58a7399513c8b0a84be29cdac271aa1500e616d2 | 413 | md | Markdown | test/runtime/specs/juttle-spec/scoping.spec.md | mysky528/juttle | 21b49f96a0e0b2098de1673c3645a6cb673ea5a8 | [
"Apache-2.0"
] | 338 | 2015-12-18T22:53:10.000Z | 2022-03-27T11:17:46.000Z | test/runtime/specs/juttle-spec/scoping.spec.md | zhouzhou77/juttle | 21b49f96a0e0b2098de1673c3645a6cb673ea5a8 | [
"Apache-2.0"
] | 654 | 2015-12-18T23:40:56.000Z | 2017-10-10T12:16:31.000Z | test/runtime/specs/juttle-spec/scoping.spec.md | zhouzhou77/juttle | 21b49f96a0e0b2098de1673c3645a6cb673ea5a8 | [
"Apache-2.0"
] | 32 | 2015-12-18T22:57:35.000Z | 2021-06-09T09:10:56.000Z | # Scoping
## Calls like `count()` in streaming expressions always refer to the built-in reducer
Regression test for PROD-9211.
### Juttle
sub count() {
put c = count() // This should *not* be resolved as a refrence to the
// defined sub.
}
emit -from Date.new(0) -limit 1 | put c = count() | view result
### Output
{ time: "1970-01-01T00:00:00.000Z", c: 1 }
| 21.736842 | 85 | 0.585956 | eng_Latn | 0.982264 |
58a82adc7678ecead078007cd30bb71a91e574a2 | 213 | md | Markdown | README.md | Jose-Isaac/igti-bootcamp-full-stack | 79333c876e82d2992529de276b14866db7809e91 | [
"MIT"
] | 1 | 2020-06-12T22:31:02.000Z | 2020-06-12T22:31:02.000Z | README.md | Jose-Isaac/igti-bootcamp-full-stack | 79333c876e82d2992529de276b14866db7809e91 | [
"MIT"
] | 1 | 2021-05-11T17:13:57.000Z | 2021-05-11T17:13:57.000Z | README.md | Jose-Isaac/igti-bootcamp-full-stack | 79333c876e82d2992529de276b14866db7809e91 | [
"MIT"
] | 3 | 2020-06-05T18:57:32.000Z | 2020-06-12T14:08:12.000Z | <p align="center">
<img src="./assets/bootcamp-logo.png" alt="Logo Bootcamp"/>
</p>
# IGTI - Bootcamp Full-Stack (maio-2020)
## Módulos
> #### > Módulo 1 - [Fundamentos - Desenvolvedor Full-Stack](./Modulo-1)
| 23.666667 | 72 | 0.647887 | por_Latn | 0.295804 |
58a861b6795d6a9729d4bd6e049d3eefed15b126 | 34,337 | md | Markdown | Exchange-Server-2013/manage-mail-users-exchange-2013-help.md | v-kents/OfficeDocs-Exchange-Test-pr.es-es | f321e36ebdc16194264319f299321b7d2fa5c0f6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | Exchange-Server-2013/manage-mail-users-exchange-2013-help.md | v-kents/OfficeDocs-Exchange-Test-pr.es-es | f321e36ebdc16194264319f299321b7d2fa5c0f6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | Exchange-Server-2013/manage-mail-users-exchange-2013-help.md | v-kents/OfficeDocs-Exchange-Test-pr.es-es | f321e36ebdc16194264319f299321b7d2fa5c0f6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'Administrar usuarios de correo: Exchange 2013 Help'
TOCTitle: Administrar usuarios de correo
ms:assetid: bb8b8804-f730-4ad7-9173-896a4965b90f
ms:mtpsurl: https://technet.microsoft.com/es-es/library/Bb124381(v=EXCHG.150)
ms:contentKeyID: 48268610
ms.date: 04/23/2018
mtps_version: v=EXCHG.150
f1_keywords:
- Microsoft.Exchange.Management.SnapIn.Esm.Recipients.NewMailUserWizardForm.NewMailUserIntroductionWizardPage
ms.translationtype: HT
---
# Administrar usuarios de correo
_**Se aplica a:** Exchange Online, Exchange Server 2013_
_**Última modificación del tema:** 2016-12-09_
Los usuarios de correo son similares a los contactos de correo. Ambos tienen direcciones de correo electrónico externas y contienen información acerca de personas no pertenecientes a la organización de Exchange o de Exchange Online que se puede mostrar en la libreta de direcciones compartida y en otras listas de direcciones. No obstante, a diferencia de un contacto de correo, un usuario de correo tiene credenciales de inicio de sesión de la organización de Exchange o de Office 365 y puede tener acceso a los recursos. Para obtener más información, consulte [Destinatarios](recipients-exchange-2013-help.md).
## ¿Qué necesita saber antes de comenzar?
- Tiempo estimado para finalizar: 2 minutos.
- Deberá tener asignados permisos antes de poder llevar a cabo este procedimiento o procedimientos. Para ver qué permisos necesita, consulte el Sección "Permisos de aprovisionamiento de destinatarios" en el tema [Permisos de destinatarios](recipients-permissions-exchange-2013-help.md).
- Para obtener información acerca de los métodos abreviados de teclado aplicables a los procedimientos de este tema, consulte [Métodos abreviados de teclado en el Centro de administración de Exchange](keyboard-shortcuts-in-the-exchange-admin-center-exchange-online-protection-help.md).
> [!TIP]
> ¿Tiene algún problema? Solicite ayuda en los foros de Exchange. Visite los foros en <A href="https://go.microsoft.com/fwlink/p/?linkid=60612">Exchange Server</A>, <A href="https://go.microsoft.com/fwlink/p/?linkid=267542">Exchange Online</A>, o <A href="https://go.microsoft.com/fwlink/p/?linkid=285351">Exchange Online Protection</A>..
## ¿Qué desea hacer?
## Crear un usuario de correo
## Uso de EAC para crear usuarios de correo
1. En el EAC, vaya a **Destinatarios** \> **Contactos** \> **Nuevo** \> **Usuario de correo**.
2. En la página **Nuevo usuario de correo**, en el cuadro \* **Alias**, escriba el alias para el usuario de correo. El alias no puede superar 64 caracteres y debe ser único en el bosque. Este cuadro es obligatorio.
3. Realice uno de lo siguiente para especificar el tipo de dirección de correo electrónico para el usuario de correo:
- Para especificar una dirección de correo electrónico SMTP para la dirección de correo electrónico externa del usuario de correo, haga clic en **SMTP**.
> [!NOTE]
> Exchange valida las direcciones SMTP para comprobar el formato adecuado. Si la entrada no coincide con el formato SMTP, se muestra un mensaje de error al hacer clic en <STRONG>Guardar</STRONG> para crear un usuario de correo.
- Para especificar un tipo de dirección personalizada, haga clic en el botón de opción y luego escriba el tipo de dirección personalizada. Por ejemplo, puede especificar una dirección X.500, GroupWise o Lotus Notes.
4. En el cuadro \* **Dirección de correo electrónico externa**, escriba la dirección de correo electrónico externa del usuario de correo. El correo electrónico que se envíe a este usuario de correo electrónico se reenviará a esta dirección de correo electrónico. Este cuadro es obligatorio.
5. Seleccione una de las opciones para:
- **Usuario existente** Seleccione esta opción para habilitar el correo de un usuario existente.
Haga clic en **Examinar** para abrir el cuadro de diálogo **Seleccionar usuario – Todo el bosque**. Este cuadro de diálogo muestra una lista de cuentas de usuario de la organización que no están habilitadas para correo o que no tienen buzones de correo. Seleccione la cuenta de usuario que desee habilitar para correo y, a continuación, haga clic en **Aceptar**. Si selecciona esta opción, no es necesario proporcionar información de la cuenta del usuario debido a que esa información ya existe en Active Directory.
- **Nuevo usuario** Seleccione esta opción para crear una nueva cuenta del usuario en Active Directory y habilitar para correo al usuario. Si selecciona esta opción, tendrá que proporcionar la información de la cuenta del usuario que se requiera.
6. Si seleccionó **Nuevo usuario** en el paso 5, complete los siguientes cuadros en la página **Nuevo usuario de correo**. De lo contrario, vaya al Paso 7.
- **Nombre** Use este cuadro para escribir el nombre del usuario de correo.
- **Iniciales** Use este cuadro para escribir las iniciales del usuario de correo.
- **Apellido** Use este cuadro para escribir el apellido del usuario de correo.
- \* **Nombre para mostrar** Use este cuadro para escribir el nombre para mostrar para el usuario. Este es el nombre que se incluye en la lista de contactos de EAC y en la libreta de direcciones de la organización. Este cuadro se rellena de forma predeterminada con los nombres que escribe en los cuadros **Nombre**, **Iniciales** y **Apellido**. Aunque no haya usado dichos cuadros, debe escribir un nombre en este cuadro, ya que es obligatorio. El nombre no puede superar los 64 caracteres.
- \* **Nombre** Use este cuadro para escribir el nombre del usuario de correo. Se trata del nombre que se muestra en el servicio de directorio. Este cuadro se rellena con los nombres que escribe en los cuadros **Nombre**, **Iniciales** y **Apellido**. Aunque no haya usado dichos cuadros, debe escribir un nombre, ya que este cuadro es obligatorio. Este nombre tampoco puede superar los 64 caracteres.
> [!NOTE]
> El cuadro <STRONG>Nombre</STRONG> solo está disponible en Exchange Server 2013. No está disponible en Exchange Online.
- **Unidad organizativa** Se puede seleccionar una unidad organizativa (OU) que no sea la predeterminada (que es el ámbito del destinatario). Si el ámbito del destinatario definido corresponde al bosque, el valor predeterminado será el contenedor de usuarios del dominio que contiene el equipo en el que se ejecuta el EAC. Si el ámbito del destinatario está establecido en un dominio específico, el contenedor de usuarios se selecciona de modo predeterminado. Si el ámbito del destinatario está establecido en una unidad organizativa específica (OU), esa OU se selecciona de modo predeterminado.
Para seleccionar otra OU, haga clic en **Examinar**. En el cuadro de diálogo se muestran todas las OU del bosque dentro del ámbito especificado. Seleccione la unidad organizativa que desee y haga clic en **Aceptar**.
> [!NOTE]
> El cuadro <STRONG>Unidad organizativa</STRONG> solo está disponible en Exchange Server 2013. No está disponible en Exchange Online.
- \* **Nombre de inicio de sesión de usuario** Use este cuadro para escribir el nombre que el usuario de correo usará para iniciar sesión en el dominio. El nombre de inicio de sesión del usuario consta de un nombre de usuario a la izquierda del símbolo arroba (@) y un sufijo a la derecha. Por lo general, el sufijo es el nombre de dominio en el que reside la cuenta de usuario.
> [!NOTE]
> En Exchange Online, este cuadro se etiqueta como <STRONG>Id. de usuario</STRONG>.
- \* **Nueva contraseña** Use este cuadro para escribir la contraseña que el usuario de correo debe usar para iniciar sesión en el dominio.
> [!NOTE]
> Asegúrese de que la contraseña que proporciona cumple los requisitos de longitud, complejidad e historial de la contraseña del dominio en el que está creando la cuenta de usuario.
- \* **Confirmar contraseña** Use este cuadro para confirmar la contraseña que escribió en el cuadro **Contraseña**.
- **Requerir cambio de contraseña en el próximo inicio de sesión** Seleccione este cuadro de verificación si desea que el usuario de correo restablezca la contraseña cuando inicie sesión por primera vez en el dominio.
Si activa este cuadro, la primera vez que el nuevo usuario de correo inicie una sesión aparecerá un cuadro de diálogo en el que se le solicitará que cambie la contraseña. El usuario de correo no podrá realizar ninguna tarea hasta que haya cambiado la contraseña correctamente.
7. Cuando haya terminado, haga clic en **Guardar** para crear el usuario de correo.
## Uso del Shell para crear usuarios de correo
En este ejemplo, se crea una cuenta de usuario habilitada para correo para Jeffrey Zeng en Exchange Server 2013 con los siguientes detalles:
- El nombre y el nombre para mostrar es Jeffrey Zeng.
- El alias es jeffreyz.
- La dirección de correo electrónico externa es [email protected].
- El nombre es Jeffrey y el apellido es Zeng.
- El nombre de inicio de sesión es [email protected].
- La contraseña es Pa$$word1.
- El usuario de correo se creará en la OU predeterminada. Para especificar una OU distinta, puede usar el parámetro *OrganizationalUnit*.
<!-- end list -->
New-MailUser -Name "Jeffrey Zeng" -Alias jeffreyz -ExternalEmailAddress [email protected] -FirstName Jeffrey -LastName Zeng -UserPrincipalName [email protected] -Password (ConvertTo-SecureString -String 'Pa$$word1' -AsPlainText -Force)
En este ejemplo se crea una cuenta de usuario con correo habilitado para Rene Valdes en Exchange Online.
New-MailUser -Name "Rene Valdes" -Alias renev -ExternalEmailAddress [email protected] -FirstName Rene -LastName Valdes -MicrosoftOnlineServicesID [email protected] -Password (ConvertTo-SecureString -String 'P@ssw0rd' -AsPlainText -Force)
## ¿Cómo saber si el proceso se ha completado correctamente?
Para comprobar si creó un usuario de correo correctamente, siga uno de estos procedimientos:
- En el EAC, vaya a **Destinatarios** \> **Contactos**. El nuevo usuario de correo aparece en la lista de contactos. En **Tipo de contacto**, el tipo es **Usuario de correo**.
- En el Shell, ejecute el siguiente comando para mostrar información acerca del nuevo usuario de correo.
Get-MailUser <Name> | FL Name,RecipientTypeDetails,ExternalEmailAddress
## Cambiar las propiedades de usuario de correo
Después de haber creado un usuario de correo, puede hacer cambios y configurar propiedades adicionales mediante el uso del EAC o del Shell.
También puede cambiar las propiedades de varios buzones de usuario al mismo tiempo. Para obtener más información, consulte Uso del EAC para editar masivamente usuarios de correo.
El tiempo estimado para completar esta tarea variará en función de la cantidad de propiedades que desee ver o cambiar.
## Uso de la Consola de administración de Exchange para cambiar las propiedades de los buzones de usuario
1. En el EAC, vaya a **Destinatarios** \> **Contactos**.
2. En la lista de contactos, haga clic en el usuario de correo al que quiera cambiarle las propiedades y luego haga clic en **Editar**.gif "Icono Editar").
3. En la página de propiedades del usuario de correo, haga clic en una de las siguientes secciones para ver o cambiar las propiedades.
- General
- Información de contacto
- Organización
- Direcciones de correo electrónico
- Configuración de flujo de correo
- Miembro de
- Información sobre correo
## General
Use la sección **General** para ver o cambiar información básica del usuario de correo.
- **Nombre**, **Iniciales**, **Apellido**
- \* **Nombre** Se trata del nombre indicado en Active Directory. Si cambia este nombre, no debe superar los 64 caracteres.
- \* **Nombre para mostrar** Este nombre aparece en la libreta de direcciones de la organización, en Para: y De: líneas en el correo electrónico y en la lista de contactos en el EAC. Este nombre no puede contener espacios en blanco antes o después del nombre para mostrar.
- \* **Nombre de inicio de sesión de usuario** El usuario puede utilizar este nombre para iniciar sesión en el dominio. En Exchange Online, este es el identificador de usuario que el usuario usa para iniciar sesión en Office 365.
- **Ocultar de las listas de direcciones** Seleccione este cuadro para evitar que el usuario de correo aparezca en la lista de direcciones y en otras listas de direcciones definidas en su organización de Exchange. Cuando active esta casilla, los usuarios aún podrán enviar mensajes al destinatario mediante la dirección de correo electrónico.
- **Requerir cambio de contraseña en el próximo inicio de sesión** Seleccione este cuadro de verificación si desea que el usuario restablezca la contraseña la próxima vez que inicie sesión en el dominio.
> [!NOTE]
> Este cuadro no está disponible en Exchange Online.
Haga clic en **Más opciones** para ver o cambiar estas propiedades adicionales:
- **Unidad organizativa** Este cuadro de solo lectura muestra la unidad organizativa (OU) que contiene la cuenta de usuario de correo. Debe usar usuarios de Active Directory y equipos para mover la cuenta a otra unidad organizativa.
> [!NOTE]
> Este cuadro no está disponible en Exchange Online.
- **Atributos personalizados** En esta sección se muestran los atributos personalizados definidos por el usuario de correo. Para especificar los valores de los atributos personalizados, haga clic en **Editar**.gif "Icono Editar"). Se pueden especificar hasta 15 atributos personalizados para el destinatario.
## Información de contacto
Use la sección **Información de contacto** para ver o cambiar la información de contacto del usuario. La información de esta página se muestra en la libreta de direcciones. Haga clic en **Más opciones** para mostrar cuadros adicionales.
> [!TIP]
> Puede usar el cuadro <STRONG>Estado o provincia</STRONG> para crear condiciones de destinatario para grupos de distribución dinámicos, directivas de direcciones de correo electrónico o listas de direcciones.
## Organización
Use la sección **Organización** para registrar información detallada acerca de la función del usuario en la organización. Esta información se muestra en la libreta de direcciones. Asimismo, puede crear un gráfico de organización virtual al que se pueda obtener acceso desde clientes de correo electrónico como Outlook.
- **Título** Use este cuadro para ver o cambiar el título del destinatario.
- **Departamento** Use este cuadro para ver o cambiar el departamento en el que trabaja el usuario. Puede usar este cuadro para crear condiciones de destinatario para grupos de distribución dinámicos, directivas de direcciones de correo electrónico o listas de direcciones.
- **Compañía** Use este cuadro para ver o cambiar la compañía en la que trabaja el usuario. Puede usar este cuadro para crear condiciones de destinatario para grupos de distribución dinámicos, directivas de direcciones de correo electrónico o listas de direcciones.
- **Administrador** Para agregar un administrador, haga clic en **Examinar**. En **Seleccionar administrador**, seleccione una persona y, a continuación, haga clic en **Aceptar**.
- **Informes directos** Este cuadro no se puede modificar. Un *subordinado directo* es un usuario que está bajo las órdenes de un administrador específico. En caso de que haya indicado un administrador para el usuario, ese buzón de correo se mostrará como subordinado directo en la información del buzón de correo del administrador en cuestión. Por ejemplo, Kari administra a Chris y Kate, por lo tanto Kari está especificada en el cuadro **Administrador** para Chris y Kate, y Chris y Kate aparecen en el cuadro **Informes directos** en las propiedades de la cuenta de Kari.
## Direcciones de correo electrónico
Use la sección **Direcciones de correo electrónico** para ver o cambiar las direcciones de correo electrónico asociadas con el usuario de correo. Esto incluye la dirección SMTP principal del usuario de correo, las direcciones de correo electrónico externas y todas las direcciones proxy asociadas. La dirección SMTP principal (también denominada *dirección de respuesta predeterminada*) se muestra en negritas en la lista de direcciones, con el valor **SMTP** en mayúsculas en la columna **Tipo**. De manera predeterminada, después de que se crea el usuario de correo, la dirección SMTP principal y la dirección de correo electrónico externa son iguales.
- **Agregar** Haga clic en **Agregar**.gif "Agregar icono") para agregar una dirección de correo electrónico nueva para este buzón de correo. Seleccione uno de los siguientes tipos de dirección:
- **SMTP** Este es el tipo de dirección predeterminado. Haga clic en este botón y luego escriba la nueva dirección SMTP en el cuadro \* **Dirección de correo electrónico**.
- **Tipo de dirección personalizada** Haga clic en este botón y escriba uno de los tipos de dirección de correo electrónico que no sean SMTP admitidos en el cuadro de texto \* **Dirección de correo electrónico**.
> [!NOTE]
> Con excepción de las direcciones X.400, Exchange no valida las direcciones personalizadas para comprobar el formato correcto. Debe asegurarse de que la dirección personalizada que especifica cumpla los requisitos de formato para el tipo de dirección.
- **Configure la dirección de correo electrónico externa** Use este cuadro para cambiar la dirección externa del usuario de correo. El correo electrónico que se envíe a este usuario de correo electrónico se reenviará a esta dirección de correo electrónico.
- **Actualizar automáticamente las direcciones de correo electrónico según la directiva de dirección de correo electrónico aplicada al destinatario.** Seleccione esta casilla para que las direcciones de correo electrónico del destinatario se actualicen automáticamente según los cambios realizados en las directivas de direcciones de correo electrónico de su organización. Esta casilla está activada de forma predeterminada.
> [!NOTE]
> Esta casilla no está disponible en Exchange Online.
## Configuración de flujo de correo
Use la **Configuración de flujo de correo** para ver o cambiar la siguiente configuración:
- **Restricciones en el tamaño de mensajes** Estas configuraciones controlan el tamaño de los mensajes que el usuario de correo puede enviar y recibir. Haga clic en **Ver detalles** para ver y cambiar el tamaño máximo de los mensajes enviados y recibidos.
- **Mensajes enviados** Para indicar el tamaño máximo de los mensajes enviados por este usuario, active la casilla **Tamaño máximo de mensaje (en KB)** y escriba un valor en el cuadro. El tamaño del mensaje debe estar entre 0 y 2.097.151 KB. Si el usuario envía un mensaje que supera el tamaño indicado, se le devolverá con un mensaje de error descriptivo.
- **Mensajes recibidos** Para indicar el tamaño máximo de los mensajes recibidos por este usuario, active la casilla **Tamaño máximo de mensaje (en KB)** y escriba un valor en el cuadro. El tamaño del mensaje debe estar entre 0 y 2.097.151 KB. Si el usuario recibe un mensaje que supera el tamaño indicado, se devuelve al emisor con un mensaje de error descriptivo.
- **Restricciones en la entrega de mensajes** Estas configuraciones controlan quién puede enviar mensajes de correo electrónico a este usuario de correo. Haga clic en **Ver detalles** para ver y cambiar esta restricción.
- **Aceptar mensajes de** Esta sección sirve para indicar quién puede enviar mensajes a este usuario.
- **Todos los remitentes** Seleccione esta opción para especificar que el usuario puede aceptar mensajes de todos los remitentes. Se incluyen los remitentes de la organización de Exchange y los remitentes externos. Esta opción está seleccionada de forma predeterminada. Esta opción incluye a los usuarios externos solo si desactiva la casilla **Requerir la autenticación de todos los remitentes**. Si activa esta casilla, se rechazarán los mensajes de los usuarios externos.
- **Solo los remitentes de la siguiente lista** Seleccione esta opción para especificar que el usuario puede aceptar mensajes únicamente de un grupo específico de remitentes de la organización de Exchange. Haga clic en **Agregar**.gif "Agregar icono")para mostrar la página **Seleccionar destinatarios**, que muestra una lista de todos los destinatarios en la organización de Exchange. Seleccione los destinarios que desee, asígnelos a la lista y luego haga clic en **Aceptar**. También puede buscar un destinatario específico. Para ello, escriba el nombre del destinatario en la casilla de búsqueda y luego haga clic en **Buscar**.gif "icono de Buscar").
- **Requerir la autenticación de todos los remitentes** Seleccione esta opción para impedir que usuarios anónimos envíen mensajes al usuario.
- **Rechazar mensajes de** Use esta sección para bloquear a ciertos usuarios y que no envíen mensajes al usuario.
- **Ningún remitente** Elija esta opción para especificar que el buzón no rechazará mensajes de ningún remitente de la organización de Exchange. Esta opción está seleccionada de forma predeterminada.
- **Remitentes de la siguiente lista** Seleccione esta opción para especificar que el buzón rechazará mensajes de un grupo específico de remitentes de la organización de Exchange. Haga clic en **Agregar**.gif "Agregar icono") para mostrar la página **Seleccionar destinatarios**, que muestra una lista de todos los destinatarios en la organización de Exchange. Seleccione los destinarios que desee, asígnelos a la lista y luego haga clic en **Aceptar**. También puede buscar un destinatario específico. Para ello, escriba el nombre del destinatario en la casilla de búsqueda y luego haga clic en **Buscar**.gif "icono de Buscar").
## Miembro de
Utilice la sección **Miembro de** para ver una lista de los grupos de distribución o los grupos de seguridad a los que pertenece el usuario. La información de pertenencia no se puede cambiar en esta página. Tenga en cuenta que el usuario puede coincidir con los criterios de uno o más grupos de distribución dinámicos de la organización. No obstante, los grupos de distribución dinámicos no se muestran en esta página porque su pertenencia se calcula cada vez que se usan.
## Información sobre correo
Utilice la sección **Sugerencia de correo** para agregar una sugerencia de correo y avisar a los usuarios de posibles problemas antes de enviar un mensaje a este destinatario. La información sobre correo es texto que se muestra en la barra de información cuando este destinatario se agrega a los campos Para, CC o CCO de un nuevo mensaje de correo electrónico.
> [!NOTE]
> La información sobre correo puede incluir etiquetas HTML, pero no se permiten los scripts. La longitud de la información de una sugerencia de correo electrónico personalizada no puede superar los 175 caracteres mostrados. Las etiquetas HTML no se cuentan en el límite.
## Uso del Shell para cambiar las propiedades de usuarios de correo
Las propiedades de un usuario de correo se almacenan en Active Directory y en Exchange. En general, use los cmdlets **Get-User** y **Set-User** para ver y cambiar las propiedades de la información de la organización y de contacto. Use los cmdlets **Get-MailUser** y **Set-MailUser** para ver y cambiar las propiedades relacionadas con el correo, como las direcciones de correo electrónico, las sugerencias de correo electrónico, los atributos personalizados y si el usuario de correo está oculto en las listas de direcciones.
Use los cmdlets **Get-MailUser** y **Set-MailUser** para ver y cambiar las propiedades de los usuarios de correo. Para obtener información, consulte los siguientes temas:
- [Get-User](https://technet.microsoft.com/es-es/library/aa996896\(v=exchg.150\))
- [Set-User](https://technet.microsoft.com/es-es/library/aa998221\(v=exchg.150\))
- [Get-MailUser](https://technet.microsoft.com/es-es/library/aa997254\(v=exchg.150\))
- [Set-MailUser](https://technet.microsoft.com/es-es/library/aa995971\(v=exchg.150\))
Aquí se encuentran algunos ejemplos del uso del Shell para cambiar las propiedades del usuario de correo.
Este ejemplo establece la dirección de correo electrónico externa de Pilar Pinilla.
Set-MailUser "Pilar Pinilla" -ExternalEmailAddress [email protected]
Este ejemplo oculta todos los usuarios de correo de la libreta de direcciones de la organización.
Get-MailUser | Set-MailUser -HiddenFromAddressListsEnabled $true
Este ejemplo establece la propiedad de la empresa para todos los usuarios de correo de Contoso.
Get-User -ResultSize unlimited -Filter {(RecipientTypeDetails -eq 'mailuser')} | Set-User -Company Contoso
En este ejemplo se configura la propiedad CustomAttribute1 para el valor ContosoEmployee para todos los usuarios de correo que posee el valor de Contoso en la propiedad Empresa.
Get-User -ResultSize unlimited -Filter {(RecipientTypeDetails -eq 'mailuser') -and (Company -eq 'Contoso')}| Set-MailUser -CustomAttribute1 ContosoEmployee
## ¿Cómo saber si el proceso se ha completado correctamente?
Para comprobar que cambió correctamente las propiedades de los usuarios de correo, realice lo siguiente:
- En el EAC, seleccione el usuario de correo y luego haga clic en **Editar**.gif "Icono Editar") para ver la propiedad que cambió.
- En el Shell, use los cmdlest **Get-User** y **Get-MailUser** para comprobar los cambios. Una ventaja de usar Shell es que puede ver varias propiedades de varios contactos de correo.
Get-MailUser | Fl Name,CustomAttribute1
En el ejemplo anterior donde la propiedad Empresa estaba configurada para Contoso para todos los contactos de correo, ejecute el siguiente comando para comprobar los cambios:
Get-User -ResultSize unlimited -Filter {(RecipientTypeDetails -eq 'mailuser')} | FL Name,Company
En el ejemplo anterior donde todos los usuarios de correo tenían la propiedad CustomAttribute1 configurada para ContosoEmployee, ejecute el siguiente comando para comprobar los cambios.
Get-MailUser | Fl Name,CustomAttribute1
## Edición masiva de usuarios de correo
También puede usar el EAC para cambiar las propiedades seleccionadas para varios usuarios de correo. Cuando seleccione dos o más usuarios de correo en la lista de contactos en el EAC, las propiedades que se pueden editar masivamente se muestran en el panel de detalles. Cuando cambia una de estas propiedades, el cambio se aplica a todos los destinatarios seleccionados.
Cuando edite masivamente usuarios de correo, puede cambiar las siguientes áreas de propiedades:
- **Información de contacto** Cambie las propiedades compartidas, como la calle, el código postal y el nombre de la ciudad.
- **Organización** Cambie las propiedades compartidas, como el nombre de departamento, el nombre de la empresa y el administrador al que informan los contactos de correo o usuarios de correo seleccionados.
## Uso del EAC para editar masivamente usuarios de correo
1. En el EAC, vaya a **Destinatarios** \> **Contactos**.
2. En la lista de contactos, seleccione dos o más usuarios de correo. No se puede editar en masa una combinación de contactos de correo y usuarios de correo.
> [!TIP]
> Se pueden seleccionar varios usuarios de correos adyacentes si se mantiene presionada la tecla Mayús y se hace clic en el primer usuario de correo y, luego, en el último usuario de correo que quiera editar. También se pueden seleccionar varios usuarios de correo si se mantiene presionada la tecla Ctrl y se hace clic en cada uno de los contactos que quiera seleccionar.
3. En el panel Detalles, en **Edición masiva**, haga clic en **Actualizar** en **Información de contacto** u **Organización**.
4. Realice los cambios en la página de propiedades y, a continuación, guarde los cambios.
## ¿Cómo saber si el proceso se ha completado correctamente?
Para comprobar si editó masivamente usuarios de correo correctamente, realice uno de estos procedimientos:
- En el EAC, seleccione todos los usuarios de correo que editó masivamente y luego haga clic en **Editar**.gif "Icono Editar") para ver las propiedades que cambió.
- En el Shell, use el cmdlet **Get-User** para comprobar los cambios. Por ejemplo, digamos que usó la característica de edición masiva en el EAC para cambiar el administrador y la oficina para todos los usuarios de correo de una empresa de proveedor denominada A. Datum Corporation. Para comprobar estos cambios, puede ejecutar el siguiente comando en Shell:
Get-User -ResultSize unlimited -Filter {(RecipientTypeDetails -eq 'mailuser') -and (Company -eq 'Adatum')} | fl Name,Office,Manager
## Usar la sincronización de directorios para administrar los usuarios de correo de Exchange Online
En esta sección se proporciona información sobre cómo administrar usuarios de correo mediante la sincronización de directorios en Exchange Online. La sincronización de directorios está disponible para los clientes híbridos con buzones de correo locales y hospedados en la nube, así como para clientes de Exchange Online de hospedaje completo con Active Directory local.
> [!NOTE]
> Si administra los destinatarios mediante la sincronización de directorios, podrá aún agregar y administrar usuarios en el Centro de administración de Office 365, pero no se sincronizarán con Active Directory local, puesto que en la sincronización de directorios solo se sincronizan los destinatarios de Active Directory local en la nube.
> [!NOTE]
> Se recomienda usar la sincronización de directorios con las siguientes características:
> <UL>
> <LI>
> <P><STRONG>Listas de remitentes bloqueados y de remitentes seguros de Outlook</STRONG>: cuando se sincronizan con el servicio, estas listas tienen prioridad sobre filtrado de correo no deseado del servicio. Esto permite a los usuarios administrar sus propias listas de remitentes seguros y remitentes bloqueados por usuario o por dominio.</P>
> <LI>
> <P><STRONG>Bloqueo perimetral basado en directorios (DBEB)</STRONG>: para obtener más información sobre DBEB, vea <A href="https://technet.microsoft.com/es-es/library/dn600322(v=exchg.150)">Usar bloqueo perimetral basado en directorios para rechazar mensajes enviados a destinatarios no válidos</A>.</P>
> <LI>
> <P><STRONG>Cuarentena de correo no deseado de usuarios finales</STRONG>: para poder obtener acceso a la cuarentena de correo no deseado de usuarios finales, los usuarios finales deben tener un identificador de usuario de Office 365 y una contraseña válidos. Los clientes con buzones locales deben ser usuarios de correo electrónico válidos.</P>
> <LI>
> <P><STRONG>Reglas de transporte</STRONG>: cuando se usa la sincronización de directorios, los usuarios y grupos existentes de Active Directory se cargan automáticamente a la nube y es posible crear reglas de transporte destinadas a usuarios o grupos específicos sin tener que agregarlos de forma manual a través del EAC o Windows PowerShell remoto. Tenga en cuenta que los <A href="https://go.microsoft.com/fwlink/?linkid=507569">grupos de distribución dinámicos</A> no se pueden sincronizar mediante la sincronización de directorios.</P></LI></UL>
**Antes de empezar**
Obtenga los permisos necesarios y prepárese para la sincronización de directorios, tal como se describe en [Preparar la sincronización de directorios](https://go.microsoft.com/fwlink/p/?linkid=308908).
**Para sincronizar directorios de usuarios**
1. Active la sincronización de directorios, tal como se describe en [Activar sincronización de directorios](https://go.microsoft.com/fwlink/p/?linkid=308909).
2. Configure su equipo de sincronización de directorios, tal como se describe en [Configurar el equipo de sincronización de directorios](http://go.microsoft.com/fwlink/p/?linkid=308911).
3. Sincronice sus directorios, tal como se describe en [Usar el Asistente de configuración para sincronizar los directorios](http://go.microsoft.com/fwlink/?linkid=308912).
> [!IMPORTANT]
> Cuando finaliza el Asistente de configuración de la herramienta de sincronización de Microsoft Azure Active Directory, se crea la cuenta <STRONG>MSOL_AD_SYNC</STRONG> en el bosque de Active Directory. Esta cuenta se utiliza para leer y sincronizar la información de Active Directory local. Para que la sincronización de directorios se realice correctamente, debe asegurarse de que el TCP 443 esté abierto en el servidor de sincronización de directorios local.
4. Active los usuarios sincronizados, tal como se describe en [Activar usuarios sincronizados](http://go.microsoft.com/fwlink/p/?linkid=308913).
5. Administre la sincronización de directorios, tal como se describe en [Administrar la sincronización de directorios](http://go.microsoft.com/fwlink/p/?linkid=308915).
6. Compruebe que Exchange Online se esté sincronizando correctamente. En el EAC, vaya a **Destinatarios** \> **Contactos** y vea que la lista de usuarios se haya sincronizado correctamente desde el entorno local.
| 77.68552 | 827 | 0.770306 | spa_Latn | 0.995265 |
58a8906af94449ba0660fa73bbbff25feb2f1f94 | 1,928 | md | Markdown | _posts/2021-04-09-end-to-end-encryption-with-app-gateway-2-application-gateway-and-encryption-.md | avicoder/mslearn | d864219a93bfa551c113003450f9284002299508 | [
"MIT"
] | null | null | null | _posts/2021-04-09-end-to-end-encryption-with-app-gateway-2-application-gateway-and-encryption-.md | avicoder/mslearn | d864219a93bfa551c113003450f9284002299508 | [
"MIT"
] | null | null | null | _posts/2021-04-09-end-to-end-encryption-with-app-gateway-2-application-gateway-and-encryption-.md | avicoder/mslearn | d864219a93bfa551c113003450f9284002299508 | [
"MIT"
] | 1 | 2022-03-09T17:33:15.000Z | 2022-03-09T17:33:15.000Z | ---
layout: post
title: Encrypt network traffic end to end with Azure Application Gateway - Application Gateway and encryption
description: nil
summary: nil
tags: nil
---
<a target="_blank" href="https://docs.microsoft.com/en-us/learn/modules/end-to-end-encryption-with-app-gateway/2-application-gateway-and-encryption/"><i class="fas fa-external-link-alt"></i> </a>
<img align="right" src="https://docs.microsoft.com/en-us/learn/achievements/end-to-end-encryption-with-app-gateway.svg">
#### 1. What are the benefits of using Application Gateway to help protect traffic sent to or from your applications?
<i class='far fa-square'></i> Application Gateway can implement an SSL connection with clients. There's no need to encrypt data sent from the gateway to the servers running your application.
<i class='fas fa-check-square' style='color: Dodgerblue;'></i> Application Gateway can implement an SSL connection with clients. Application Gateway can also implement an SSL connection with the servers running your application.
<i class='far fa-square'></i> Application Gateway doesn't require an SSL connection with clients. All encryption is carried out by the connection with the servers running your application.
<i class='far fa-square'></i> Application Gateway automatically protects the communications between clients and the servers running your application. You don't need to do any additional configuration.
<br />
<br />
<br />
#### 2. Which of the following can't be placed in the backend pool of an application gateway?
<i class='far fa-square'></i> Azure App Service
<i class='far fa-square'></i> Azure virtual machines
<i class='fas fa-check-square' style='color: Dodgerblue;'></i> Azure Cosmos DB
<i class='far fa-square'></i> Azure virtual machine scale sets
<br />
<br />
<br />
| 49.435897 | 240 | 0.743257 | eng_Latn | 0.956389 |
58a8affb296df8036c095f98ee3e4104979a51fd | 1,052 | md | Markdown | skills/B01N3NUXSS/README.md | zwang695/alexa-skills-list | 43fb6168a3313f004d02a910d1d8930f42a5fce4 | [
"MIT"
] | null | null | null | skills/B01N3NUXSS/README.md | zwang695/alexa-skills-list | 43fb6168a3313f004d02a910d1d8930f42a5fce4 | [
"MIT"
] | null | null | null | skills/B01N3NUXSS/README.md | zwang695/alexa-skills-list | 43fb6168a3313f004d02a910d1d8930f42a5fce4 | [
"MIT"
] | null | null | null | # [Snow Report for Mount LaCrosse](http://alexa.amazon.com/#skills/amzn1.ask.skill.53920c1b-8eec-43d2-8248-d12e0356fb35)
 0
To use the Snow Report for Mount LaCrosse skill, try saying...
* *Alexa, open Mount LaCrosse*
* *Alexa, ask Mount LaCrosse for the snow report*
* *Alexa, ask Mount LaCrosse for latest conditions*
The Mount LaCrosse Snow Report brought to you by SnoCountry brings you the latest snow fall, snow surface conditions, base depth, trail, and lift operations information.
***
### Skill Details
* **Invocation Name:** mount lacrosse
* **Category:** null
* **ID:** amzn1.ask.skill.53920c1b-8eec-43d2-8248-d12e0356fb35
* **ASIN:** B01N3NUXSS
* **Author:** SnoCountry
* **Release Date:** November 5, 2016 @ 11:44:20
* **In-App Purchasing:** No
| 42.08 | 287 | 0.73384 | eng_Latn | 0.292513 |
58a8fdee763e5e4205064407f430e36112e0ae84 | 703 | md | Markdown | catalog/do-you-want-to-try/en-US_do-you-want-to-try.md | htron-dev/baka-db | cb6e907a5c53113275da271631698cd3b35c9589 | [
"MIT"
] | 3 | 2021-08-12T20:02:29.000Z | 2021-09-05T05:03:32.000Z | catalog/do-you-want-to-try/en-US_do-you-want-to-try.md | zzhenryquezz/baka-db | da8f54a87191a53a7fca54b0775b3c00f99d2531 | [
"MIT"
] | 8 | 2021-07-20T00:44:48.000Z | 2021-09-22T18:44:04.000Z | catalog/do-you-want-to-try/en-US_do-you-want-to-try.md | zzhenryquezz/baka-db | da8f54a87191a53a7fca54b0775b3c00f99d2531 | [
"MIT"
] | 2 | 2021-07-19T01:38:25.000Z | 2021-07-29T08:10:29.000Z | # Do You Want to Try?
- **type**: manhwa
- **volumes**: 5
- **chapters**: 18
- **original-name**: 한 번 해봐?
## Tags
- comedy
- drama
- romance
- shoujo
## Authors
- Cha
- Kyung Hee (Story & Art)
## Sinopse
When the hot-tempered Han Hye Won accidentally insults the handsome jjang of Han Hwa Go, Sun Woo Bin decides to pay her a visit...with his entire motorcycle gang, ready to see some blood. So how does that lead up to a kiss and the infamous captain begging for a date? Do you want to try?
(Source: Esthétique)
## Links
- [My Anime list](https://myanimelist.net/manga/4895/Do_You_Want_to_Try)
| 22.677419 | 287 | 0.677098 | eng_Latn | 0.880215 |
58a93cf6930fd6823c36169bb6871c750846043d | 30,347 | md | Markdown | docs/sharepoint/walkthrough-creating-a-custom-action-project-item-with-an-item-template-part-1.md | MicrosoftDocs/visualstudio-docs.es-es | 9d654c35ecad85edadd91aefb49b7bd0ebd2eee2 | [
"CC-BY-4.0",
"MIT"
] | 6 | 2020-05-20T07:48:51.000Z | 2022-03-09T07:27:32.000Z | docs/sharepoint/walkthrough-creating-a-custom-action-project-item-with-an-item-template-part-1.md | MicrosoftDocs/visualstudio-docs.es-es | 9d654c35ecad85edadd91aefb49b7bd0ebd2eee2 | [
"CC-BY-4.0",
"MIT"
] | 30 | 2018-10-02T15:11:15.000Z | 2021-12-17T11:02:02.000Z | docs/sharepoint/walkthrough-creating-a-custom-action-project-item-with-an-item-template-part-1.md | MicrosoftDocs/visualstudio-docs.es-es | 9d654c35ecad85edadd91aefb49b7bd0ebd2eee2 | [
"CC-BY-4.0",
"MIT"
] | 25 | 2018-01-24T17:02:46.000Z | 2022-03-04T14:06:19.000Z | ---
title: Creación de un elemento de proyecto de acción personalizada con una plantilla de elemento, parte 1
titleSuffix: ''
description: Con una plantilla de elemento, cree un elemento de proyecto que se pueda agregar a un proyecto de SharePoint para crear una acción personalizada en un SharePoint personalizado.
ms.custom: SEO-VS-2020
ms.date: 02/02/2017
ms.topic: how-to
dev_langs:
- VB
- CSharp
helpviewer_keywords:
- SharePoint project items, creating custom templates
- SharePoint project items, defining your own types
- project items [SharePoint development in Visual Studio], defining your own types
- SharePoint development in Visual Studio, defining new project item types
author: John-Hart
ms.author: johnhart
manager: jmartens
ms.technology: sharepoint-development
ms.workload:
- office
ms.openlocfilehash: b01352aa0774f059329e849badbae257951e0ccb
ms.sourcegitcommit: 42aec4a2ea6dec67dbe4c93bcf0fa1116a4b93d9
ms.translationtype: MT
ms.contentlocale: es-ES
ms.lasthandoff: 08/26/2021
ms.locfileid: "122980961"
---
# <a name="walkthrough-create-a-custom-action-project-item-with-an-item-template-part-1"></a>Tutorial: Creación de un elemento de proyecto de acción personalizada con una plantilla de elemento, parte 1
Puede extender el sistema de proyectos de SharePoint en Visual Studio creando sus propios tipos de elemento de proyecto. En este tutorial, creará un elemento de proyecto que se puede agregar a un proyecto de SharePoint para crear una acción personalizada en un sitio de SharePoint. La acción personalizada agrega un elemento de menú al menú **Acciones** del sitio SharePoint sitio.
En este tutorial se muestran las siguientes tareas:
- Crear una extensión de Visual Studio que define un nuevo tipo de elemento de proyecto de SharePoint para una acción personalizada. El nuevo tipo de elemento de proyecto implementa varias características personalizadas:
- Un menú contextual que actúa como un punto inicial para las tareas adicionales relacionadas con el elemento de proyecto, como mostrar un diseñador para la acción personalizada en Visual Studio.
- Código que se ejecuta cuando un desarrollador cambia ciertas propiedades del elemento de proyecto y del proyecto que lo contiene.
- Icono personalizado que aparece junto al elemento de proyecto en **Explorador de soluciones**.
- Crear una plantilla de elementos de Visual Studio para el elemento de proyecto.
- Compilar un paquete de extensión de Visual Studio (VSIX) para implementar la plantilla de elemento de proyecto y el ensamblado de la extensión.
- Depurar y probar el elemento de proyecto.
Este es un tutorial independiente. Después de completar este tutorial, puede mejorar el elemento de proyecto si agrega un asistente a la plantilla de elemento. Para obtener más información, [vea Tutorial: Crear un elemento de proyecto de acción personalizada con una plantilla de elemento, Parte 2.](../sharepoint/walkthrough-creating-a-custom-action-project-item-with-an-item-template-part-2.md)
> [!NOTE]
> Puede descargar un ejemplo de [GitHub](https://github.com/SharePoint/PnP/tree/master/Samples/Workflow.Activities) que muestra cómo crear actividades personalizadas para un flujo de trabajo.
## <a name="prerequisites"></a>Requisitos previos
Necesitará los componentes siguientes en el equipo de desarrollo para completar este tutorial:
- Ediciones compatibles de Microsoft Windows, SharePoint y Visual Studio.
- [!INCLUDE[vssdk_current_long](../sharepoint/includes/vssdk-current-long-md.md)]. En este tutorial se usa **la plantilla Project VSIX** en el SDK para crear un paquete VSIX para implementar el elemento de proyecto. Para obtener más información, vea [Extender las herramientas de SharePoint en Visual Studio](../sharepoint/extending-the-sharepoint-tools-in-visual-studio.md).
El conocimiento de los siguientes conceptos es útil, aunque no necesario, para completar el tutorial.
- Acciones personalizadas en SharePoint. Para obtener más información, vea [Acción personalizada](/previous-versions/office/developer/sharepoint-2010/ms458635(v=office.14)).
- Plantillas de elemento en Visual Studio. Para obtener más información, vea [Crear plantillas para proyectos y elementos en Visual Studio](../ide/creating-project-and-item-templates.md).
## <a name="create-the-projects"></a>Creación de los proyectos
Para completar este tutorial, debe crear tres proyectos:
- Un proyecto VSIX. Este proyecto crea el paquete VSIX para implementar el elemento de proyecto de SharePoint.
- Un proyecto de plantilla de elemento. Este proyecto crea una plantilla de elemento que se puede utilizar para agregar el elemento de proyecto de SharePoint a un proyecto de SharePoint.
- Un proyecto de biblioteca de clases. Este proyecto implementa una extensión de Visual Studio que define el comportamiento del elemento de proyecto de SharePoint.
Comience el tutorial creando ambos proyectos.
#### <a name="to-create-the-vsix-project"></a>Para crear el proyecto VSIX
1. Inicie [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)].
2. En la barra de menús, elija **Archivo** > **Nuevo** > **Proyecto**.
3. En la lista de la parte superior del cuadro **de diálogo Nuevo** Project, asegúrese de que .NET Framework **4.5** está seleccionado.
4. En el **cuadro de diálogo Nuevo** Project, expanda los nodos Visual **C#** **o Visual Basic** y, a continuación, elija el **nodo Extensibilidad.**
> [!NOTE]
> El **nodo Extensibilidad** solo está disponible si instala el SDK de Visual Studio. Para obtener más información, vea la sección Requisitos previos, anteriormente en este tema.
5. Elija la **plantilla de Project VSIX.**
6. En el **cuadro Nombre,** escriba **CustomActionProjectItem** y, a continuación, elija **el botón** Aceptar.
[!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] agrega el **proyecto CustomActionProjectItem** **a Explorador de soluciones**.
#### <a name="to-create-the-item-template-project"></a>Para crear el proyecto de plantilla de elemento
1. En **Explorador de soluciones**, abra el menú contextual del nodo de solución, elija Agregar y, a continuación, **elija Nuevo Project**.
2. En la lista de la parte superior del cuadro **de diálogo Nuevo** Project, asegúrese de que .NET Framework **4.5** está seleccionado.
3. En el **cuadro de diálogo Nuevo** Project, expanda los nodos Visual **C#** **o Visual Basic** y, a continuación, elija el **nodo Extensibilidad.**
4. En la lista de plantillas de proyecto, elija la plantilla de **elemento de C#** **Visual Basic plantilla de elemento.**
5. En el **cuadro** Nombre, escriba **ItemTemplate** y, a continuación, elija **el botón** Aceptar.
[!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] agrega el **proyecto ItemTemplate** a la solución.
#### <a name="to-create-the-extension-project"></a>Para crear la extensión de proyecto
1. En **Explorador de soluciones**, abra el menú contextual del nodo de solución, elija Agregar y, a continuación, **elija Nuevo Project**.
2. En la lista de la parte superior del cuadro **de diálogo Nuevo** Project, asegúrese de que .NET Framework **4.5** está seleccionado.
3. En el cuadro **de diálogo** Nuevo Project, expanda los nodos Visual **C#** o **Visual Basic,** elija el nodo Windows y, **a** continuación, elija la plantilla de proyecto Biblioteca de clases.
4. En el **cuadro** Nombre, escriba **ProjectItemDefinition** y, a continuación, elija **el botón** Aceptar.
[!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] agrega el **proyecto ProjectItemDefinition** a la solución y abre el archivo de código Class1 predeterminado.
5. Elimine el archivo de código Class1 del proyecto.
## <a name="configure-the-extension-project"></a>Configuración del proyecto de extensión
Antes de escribir el código para definir el tipo de elemento de proyecto de SharePoint, tiene que agregar los archivos de código y las referencias de ensamblado al proyecto de extensión.
#### <a name="to-configure-the-project"></a>Para configurar el proyecto
1. En **Explorador de soluciones**, abra el menú contextual del proyecto **ProjectItemDefinition,** elija Agregar **y,** a continuación, elija **Nuevo elemento.**
2. En la lista de elementos de proyecto, elija **Archivo de código**.
3. En el **cuadro Nombre,** escriba el nombre **CustomAction** con la extensión de nombre de archivo adecuada y, a continuación, elija **el botón** Agregar.
4. En **Explorador de soluciones**, abra el menú contextual del proyecto **ProjectItemDefinition** y, a continuación, **elija Agregar referencia.**
5. En el cuadro de diálogo Administrador de **referencias - ProjectItemDefinition** , elija el nodo **Ensamblados** y, a continuación, elija el **nodo Marco.**
6. Active la casilla situada al lado de cada uno de los siguientes ensamblados:
- System.ComponentModel.Composition
- System.Windows.Forms
7. Elija el **nodo Extensiones,** active la casilla situada junto al ensamblado Microsoft.VisualStudio.Sharepoint y, a continuación, elija **el botón** Aceptar.
## <a name="define-the-new-sharepoint-project-item-type"></a>Definición de la nueva SharePoint de elemento de proyecto
Cree una clase que implemente la interfaz <xref:Microsoft.VisualStudio.SharePoint.ISharePointProjectItemTypeProvider> para definir el comportamiento del nuevo tipo de elemento de proyecto. Implemente esta interfaz para definir un nuevo tipo de elemento de proyecto todas las veces que desee.
#### <a name="to-define-the-new-sharepoint-project-item-type"></a>Para definir el nuevo tipo de elemento de proyecto de SharePoint
1. En el proyecto ProjectItemDefinition, abra el archivo de código CustomAction.
2. Reemplace el código de este archivo por el código siguiente.
:::code language="csharp" source="../sharepoint/codesnippet/CSharp/customactionprojectitem/projectitemtypedefinition/customaction.cs" id="Snippet1":::
:::code language="vb" source="../sharepoint/codesnippet/VisualBasic/customactionprojectitem/projectitemdefinition/customaction.vb" id="Snippet1":::
## <a name="create-an-icon-for-the-project-item-in-solution-explorer"></a>Cree un icono para el elemento de proyecto en Explorador de soluciones
Cuando crea un elemento de proyecto de SharePoint personalizado, puede asociarle una imagen (un icono o mapa de bits). Esta imagen aparece junto al elemento de proyecto en **Explorador de soluciones**.
En el procedimiento siguiente se crea un icono para el elemento de proyecto y se incrusta en el ensamblado de la extensión. El <xref:Microsoft.VisualStudio.SharePoint.SharePointProjectItemIconAttribute> de la clase `CustomActionProjectItemTypeProvider` que creó anteriormente hace referencia a este icono.
#### <a name="to-create-a-custom-icon-for-the-project-item"></a>Para crear un icono personalizado para el elemento de proyecto
1. En **Explorador de soluciones**, abra el menú contextual del proyecto **ProjectItemDefinition,** elija Agregar y, a continuación, **elija Nuevo elemento...**.
2. En la lista de elementos de proyecto, elija el **elemento Archivo de** icono.
> [!NOTE]
> En Visual Basic proyecto, debe elegir el **nodo General** para mostrar el elemento **Archivo de** icono.
3. En el **cuadro** Nombre, **escriba CustomAction_SolutionExplorer.ico y,** a continuación, elija **el botón** Agregar.
El nuevo icono se abre en el **Editor de imágenes.**
4. Modifique la versión 16x16 del archivo de icono para que tenga un diseño que pueda reconocer y guarde el archivo.
5. En **Explorador de soluciones**, elija **CustomAction_SolutionExplorer.ico**.
6. En la **ventana Propiedades,** elija la flecha situada junto a la **propiedad Acción de** compilación.
7. En la lista que aparece, elija **Recurso incrustado.**
## <a name="checkpoint"></a>Punto de control
En este punto del tutorial, todo el código del elemento de proyecto está en el proyecto. Compile el proyecto para comprobar que se compila sin errores.
#### <a name="to-build-your-project"></a>Para compilar el proyecto
1. Abra el menú contextual del proyecto **ProjectItemDefinition** y elija **Compilar.**
## <a name="create-a-visual-studio-item-template"></a>Creación de una plantilla Visual Studio elemento de creación
Para permitir que otros desarrolladores usen el elemento de proyecto, debe crear una plantilla de proyecto o una plantilla de elemento de proyecto. Los desarrolladores utilizan estas plantillas en Visual Studio para crear una instancia de su elemento de proyecto creando un nuevo proyecto o agregando un elemento a un proyecto existente. En este tutorial, use el proyecto ItemTemplate para configurar el elemento de proyecto.
#### <a name="to-create-the-item-template"></a>Para crear la plantilla de elementos
1. Elimine el archivo de código Class1 del proyecto ItemTemplate.
2. En el proyecto ItemTemplate, abra el *archivo ItemTemplate.vstemplate.*
3. Reemplace el contenido del archivo por el siguiente código XML y, a continuación, guarde y cierre el archivo.
> [!NOTE]
> El siguiente código XML está diseñado para una plantilla de elemento de Visual C#. Si está creando una plantilla de elemento de Visual Basic, reemplace el valor del elemento `ProjectType` por `VisualBasic`.
```xml
<?xml version="1.0" encoding="utf-8"?>
<VSTemplate Version="2.0.0" xmlns="http://schemas.microsoft.com/developer/vstemplate/2005" Type="Item">
<TemplateData>
<DefaultName>CustomAction</DefaultName>
<Name>Custom Action</Name>
<Description>SharePoint Custom Action by Contoso</Description>
<ProjectType>CSharp</ProjectType>
<SortOrder>1000</SortOrder>
<Icon>ItemTemplate.ico</Icon>
<ProvideDefaultName>true</ProvideDefaultName>
</TemplateData>
<TemplateContent>
<ProjectItem ReplaceParameters="true" TargetFileName="$fileinputname$\Elements.xml">Elements.xml</ProjectItem>
<ProjectItem ReplaceParameters="true" TargetFileName="$fileinputname$\SharePointProjectItem.spdata">CustomAction.spdata</ProjectItem>
</TemplateContent>
</VSTemplate>
```
Este archivo define el contenido y comportamiento de la plantilla de elementos. Para obtener más información sobre el contenido de este archivo, vea referencia [Visual Studio esquema de plantilla](../extensibility/visual-studio-template-schema-reference.md).
4. En **Explorador de soluciones**, abra el menú contextual del proyecto **ItemTemplate,** **elija Agregar** y, a continuación, elija Nuevo **elemento.**
5. En el **cuadro de diálogo Agregar nuevo** elemento, elija la plantilla Archivo **de** texto.
6. En el **cuadro** Nombre, escriba **CustomAction.spdata y,** a continuación, elija **el botón** Agregar.
7. Agregue el siguiente XML al *archivo CustomAction.spdata* y, a continuación, guarde y cierre el archivo.
```xml
<?xml version="1.0" encoding="utf-8"?>
<ProjectItem Type="Contoso.CustomAction" DefaultFile="Elements.xml"
xmlns="http://schemas.microsoft.com/VisualStudio/2010/SharePointTools/SharePointProjectItemModel">
<Files>
<ProjectItemFile Source="Elements.xml" Target="$fileinputname$\" Type="ElementManifest" />
</Files>
</ProjectItem>
```
Este archivo contiene información sobre los archivos que están contenidos en el elemento de proyecto. El atributo `Type` del elemento `ProjectItem` debe estar establecido en la misma cadena que se pasa a <xref:Microsoft.VisualStudio.SharePoint.SharePointProjectItemTypeAttribute> en la definición del elemento de proyecto (la clase `CustomActionProjectItemTypeProvider` que creó anteriormente en este tutorial). Para obtener más información sobre el contenido de *los archivos .spdata,* vea SharePoint [de esquema del elemento de proyecto](../sharepoint/sharepoint-project-item-schema-reference.md).
8. En **Explorador de soluciones**, abra el menú contextual del proyecto **ItemTemplate,** **elija Agregar** y, a continuación, elija Nuevo **elemento.**
9. En el **cuadro de diálogo Agregar nuevo** elemento, elija la plantilla Archivo **XML.**
10. En el **cuadro** Nombre, **escribaElements.xml** y, a continuación, elija **el botón** Agregar.
11. Reemplace el contenido del archivo *Elements.xml* por el siguiente XML y, a continuación, guarde y cierre el archivo.
```xml
<?xml version="1.0" encoding="utf-8" ?>
<Elements Id="$guid8$" xmlns="http://schemas.microsoft.com/sharepoint/">
<CustomAction Id="Replace this with a GUID or some other unique string"
GroupId="SiteActions"
Location="Microsoft.SharePoint.StandardMenu"
Sequence="1000"
Title="Replace this with your title"
Description="Replace this with your description" >
<UrlAction Url="~site/Lists/Tasks/AllItems.aspx"/>
</CustomAction>
</Elements>
```
Este archivo define una acción personalizada predeterminada que crea un elemento de menú en el menú **Acciones** del sitio SharePoint sitio. Cuando un usuario elige el elemento de menú, la dirección URL especificada en el elemento `UrlAction` se abre en el explorador web. Para obtener más información sobre los elementos XML que puede usar para definir una acción personalizada, vea [Custom Action Definitions](/sharepoint/dev/schema/custom-action-definition-schema).
12. También puede abrir el *archivo ItemTemplate.ico* y modificarlo para que tenga un diseño que pueda reconocer. Este icono se mostrará junto al elemento de proyecto en el **cuadro de diálogo Agregar** nuevo elemento .
13. En **Explorador de soluciones**, abra el menú contextual del proyecto **ItemTemplate** y, a continuación, **elija Descargar Project**.
14. Vuelva a abrir el menú contextual del proyecto **ItemTemplate** y elija **Editar ItemTemplate.csproj** o **Editar ItemTemplate.vbproj.**
15. Busque el elemento `VSTemplate` siguiente en el archivo del proyecto.
```xml
<VSTemplate Include="ItemTemplate.vstemplate">
```
16. Reemplace este elemento `VSTemplate` por el siguiente código XML y, a continuación, guarde y cierre el archivo.
```xml
<VSTemplate Include="ItemTemplate.vstemplate">
<OutputSubPath>SharePoint\SharePoint14</OutputSubPath>
</VSTemplate>
```
El elemento `OutputSubPath` especifica las carpetas adicionales en la ruta de acceso en la que se crea la plantilla de elemento al compilar el proyecto. Las carpetas especificadas aquí garantizan que la plantilla de elemento solo estará disponible cuando los clientes abran el cuadro de diálogo Agregar nuevo elemento, expandan el nodo SharePoint y, **a** continuación, elijan el **nodo 2010.**
17. En **Explorador de soluciones**, abra el menú contextual del proyecto **ItemTemplate** y, a continuación, elija **Recargar Project**.
## <a name="create-a-vsix-package-to-deploy-the-project-item"></a>Creación de un paquete VSIX para implementar el elemento de proyecto
Para implementar la extensión, utilice el proyecto VSIX en la solución para crear un paquete VSIX. Primero, configure el paquete VSIX modificando el archivo source.extension.vsixmanifest incluido en el proyecto VSIX. A continuación, cree el paquete VSIX compilando la solución.
#### <a name="to-configure-and-create-the-vsix-package"></a>Para crear y configurar el paquete VSIX
1. En **Explorador de soluciones**, abra el menú contextual del archivo **source.extension.vsixmanifest** en el proyecto CustomActionProjectItem y, a continuación, **elija Abrir**.
Visual Studio abre el archivo en el editor de manifiestos. El archivo source.extension.vsixmanifest es la base del archivo extension.vsixmanifest que requieren todos los paquetes VSIX. Para obtener más información sobre este archivo, vea Referencia del esquema [de extensión VSIX 1.0.](/previous-versions/dd393700(v=vs.110))
2. En el **cuadro Nombre del** producto, escriba Acción personalizada Project **elemento**.
3. En el **cuadro** Autor, escriba **Contoso.**
4. En el **cuadro Descripción** , escriba A SharePoint elemento de proyecto que representa una **acción personalizada**.
5. En la **pestaña Activos,** elija el **botón** Nuevo.
Aparece **el cuadro de diálogo Agregar** nuevo recurso.
6. En la **lista** Tipo, elija **Microsoft.VisualStudio.ItemTemplate**.
> [!NOTE]
> Este valor corresponde al elemento `ItemTemplate` del archivo extension.vsixmanifest. Este elemento identifica la subcarpeta del paquete VSIX que contiene la plantilla de elemento de proyecto. Para obtener más información, [vea Elemento ItemTemplate (esquema VSX).](/previous-versions/visualstudio/visual-studio-2010/dd393681\(v\=vs.100\))
7. En la **lista** Origen, elija **Un proyecto en la solución actual.**
8. En la **Project,** elija **ItemTemplate** y, a continuación, elija el **botón** Aceptar.
9. En la **pestaña Activos,** vuelva a elegir **el** botón Nuevo.
Aparece **el cuadro de diálogo Agregar** nuevo recurso.
10. En la **lista** Tipo, elija **Microsoft.VisualStudio.MefComponent**.
> [!NOTE]
> Este valor corresponde al elemento `MefComponent` del archivo extension.vsixmanifest. Este elemento especifica el nombre de un ensamblado de extensión en el paquete VSIX. Para obtener más información, [vea Elemento MEFComponent (esquema VSX).](/previous-versions/visualstudio/visual-studio-2010/dd393736\(v\=vs.100\))
11. En la **lista** Origen, elija **Un proyecto en la solución actual.**
12. En la **Project,** elija **ProjectItemDefinition**.
13. Elija el botón **Aceptar** .
14. En la barra de menús, elija **Compilar** solución de compilación y, a continuación, asegúrese de > que el proyecto se compila sin errores.
15. Asegúrese de que la carpeta de salida de la compilación del proyecto CustomActionProjectItem contiene el archivo CustomActionProjectItem.vsix.
De forma predeterminada, la carpeta de salida de la compilación es ..\bin\Debug en la carpeta que contiene el proyecto CustomActionProjectItem.
## <a name="test-the-project-item"></a>Prueba del elemento de proyecto
Ya puede probar el elemento de proyecto. Primero, empiece a depurar la solución CustomActionProjectItem en la instancia experimental de Visual Studio. A continuación, pruebe **el elemento de** proyecto Acción personalizada en un proyecto SharePoint en la instancia experimental de Visual Studio. Por último, compile y ejecute el proyecto SharePoint para comprobar que la acción personalizada funciona del modo esperado.
#### <a name="to-start-debugging-the-solution"></a>Para empezar a depurar la solución
1. Reinicie Visual Studio con credenciales administrativas y abra la solución CustomActionProjectItem.
2. Abra el archivo de código CustomAction y, a continuación, agregue un punto de interrupción a la primera línea de código en el método `InitializeType`.
3. Elija la **tecla F5** para iniciar la depuración.
Visual Studio instala la extensión en %UserProfile%\AppData\Local\Microsoft\VisualStudio\10.0Exp\Extensions\Contoso\Custom Action Project Item\1 .0 e inicia una instancia experimental de Visual Studio. Probará el elemento de proyecto en esta instancia de Visual Studio.
#### <a name="to-test-the-project-item-in-visual-studio"></a>Para probar el elemento de proyecto en Visual Studio
1. En la instancia experimental de Visual Studio, en la barra de menús, elija **Archivo** > > **nuevo Project**.
2. Expanda **Visual C#** **o Visual Basic** (en función del lenguaje que admita la plantilla de **elemento),** expanda SharePoint y, a continuación, elija el **nodo 2010.**
3. En la lista de plantillas de proyecto, **elija SharePoint 2010 Project**.
4. En el **cuadro Nombre,** escriba **CustomActionTest** y, a continuación, elija el **botón** Aceptar.
5. En el **Asistente SharePoint personalización,** escriba la dirección URL del sitio que desea usar para la depuración y, a continuación, elija **el botón** Finalizar.
6. En **Explorador de soluciones**, abra el menú contextual del nodo del proyecto, **elija Agregar** y, a continuación, elija Nuevo **elemento**.
7. En el **cuadro de diálogo Agregar** nuevo elemento, elija el nodo **2010** en el **SharePoint** nuevo.
Compruebe que el **elemento Acción personalizada** aparece en la lista de elementos del proyecto.
8. Elija el **elemento Acción** personalizada y, a continuación, elija **el botón** Agregar.
Visual Studio agrega un elemento denominado **CustomAction1** al proyecto y abre el *archivoElements.xml* en el editor.
9. Compruebe que el código de la otra instancia de Visual Studio se detiene en el punto de interrupción que estableció anteriormente en el método `InitializeType`.
10. Elija la **tecla F5** para seguir depurando el proyecto.
11. En la instancia experimental de Visual Studio, en **Explorador de soluciones**, abra el menú contextual del **nodo CustomAction1** y, a continuación, elija Ver diseñador de **acciones personalizadas**.
12. Compruebe que aparece un cuadro de mensaje y, a continuación, elija **el botón** Aceptar.
Puede utilizar este menú contextual para proporcionar opciones o comandos adicionales a los desarrolladores, como mostrar un diseñador para la acción personalizada.
13. En la barra de menús, elija **Ver** > **salida.**
Se **abre la ventana** Salida.
14. En **Explorador de soluciones**, abra el menú contextual del **elemento CustomAction1** y, a continuación, cambie su nombre a **MyCustomAction**.
En la **ventana Salida,** aparece un mensaje de confirmación. Este mensaje lo escribe el controlador de eventos <xref:Microsoft.VisualStudio.SharePoint.ISharePointProjectItemEvents.ProjectItemNameChanged> que se definió en la clase `CustomActionProjectItemTypeProvider`. Puede controlar este y otros eventos de elementos de proyecto para implementar el comportamiento personalizado cuando el desarrollador modifica el elemento de proyecto.
#### <a name="to-test-the-custom-action-in-sharepoint"></a>Para probar la acción personalizada en SharePoint
1. En la instancia experimental de Visual Studio, abra el archivo *Elements.xml* que es un elemento secundario del elemento de proyecto **MyCustomAction.**
2. En el *Elements.xml,* realice los cambios siguientes y, a continuación, guarde el archivo:
- En el elemento `CustomAction`, establezca el atributo `Id` en un GUID o alguna otra cadena única como se muestra en el ejemplo siguiente:
```xml
Id="cd85f6a7-af2e-44ab-885a-0c795b52121a"
```
- En el elemento `CustomAction`, establezca el atributo `Title` tal y como se muestra en el siguiente ejemplo:
```xml
Title="SharePoint Developer Center"
```
- En el elemento `CustomAction`, establezca el atributo `Description` tal y como se muestra en el siguiente ejemplo:
```xml
Description="Opens the SharePoint Developer Center Web site."
```
- En el elemento `UrlAction`, establezca el atributo `Url` tal y como se muestra en el siguiente ejemplo:
```xml
Url="https://docs.microsoft.com/sharepoint/dev/"
```
3. Elija la tecla **F5**.
La acción personalizada se empaqueta e implementa en el sitio SharePoint que se especifica en la propiedad Url del sitio del proyecto. El explorador web se abre en la página predeterminada de este sitio.
> [!NOTE]
> Si aparece **el cuadro de diálogo** Depuración de scripts deshabilitada, elija **el** botón Sí para continuar depurando el proyecto.
4. En el **menú Acciones del** sitio, elija SharePoint **Centro** para desarrolladores, compruebe que el explorador abre el sitio web y, a continuación, cierre el `https://docs.microsoft.com/sharepoint/dev/` explorador web.
## <a name="clean-up-the-development-computer"></a>Limpieza del equipo de desarrollo
Después de probar el elemento de proyecto, quite la plantilla de elemento de proyecto de la instancia experimental de Visual Studio.
#### <a name="to-clean-up-the-development-computer"></a>Para limpiar el equipo de desarrollo
1. En la instancia experimental de Visual Studio, en la barra de menús, elija **Extensiones** > **y actualizaciones de herramientas.**
Se abre el cuadro de diálogo **Extensiones y actualizaciones**.
2. En la lista de extensiones, elija **Acción personalizada Project elemento y,** a continuación, elija el **botón** Desinstalar.
3. En el cuadro de diálogo que aparece, elija **el botón Sí** para confirmar que desea desinstalar la extensión.
4. Elija el **botón Reiniciar ahora** para completar la desinstalación.
5. Cierre tanto la instancia experimental de Visual Studio como la instancia en la que se abre la solución CustomActionProjectItem.
## <a name="next-steps"></a>Pasos siguientes
Después de completar este tutorial, puede agregar un asistente a la plantilla de elemento. Cuando un usuario agrega un elemento de proyecto acción personalizada a un proyecto de SharePoint, el asistente recopila información sobre la acción (por ejemplo, su ubicación y la dirección URL a la que navegar cuando se elige la acción) y agrega esta información al archivo *Elements.xml* en el nuevo elemento de proyecto. Para obtener más información, [vea Tutorial: Crear un elemento de proyecto de acción personalizada con una plantilla de elemento, Parte 2.](../sharepoint/walkthrough-creating-a-custom-action-project-item-with-an-item-template-part-2.md)
## <a name="see-also"></a>Consulte también
- [Tutorial: Creación de un elemento de proyecto de acción personalizada con una plantilla de elemento, parte 2](../sharepoint/walkthrough-creating-a-custom-action-project-item-with-an-item-template-part-2.md)
- [Definición de tipos SharePoint de elemento de proyecto personalizados](../sharepoint/defining-custom-sharepoint-project-item-types.md)
- [Creación de plantillas de elemento y plantillas de proyecto para SharePoint de proyecto](../sharepoint/creating-item-templates-and-project-templates-for-sharepoint-project-items.md)
- [Use el SharePoint servicio de proyecto](../sharepoint/using-the-sharepoint-project-service.md)
- [Referencia de esquema de plantillas de Visual Studio](../extensibility/visual-studio-template-schema-reference.md)
- [Editor de imágenes para iconos](/cpp/windows/image-editor-for-icons)
- [Crear un icono u otra imagen (editor de imágenes para iconos)](/cpp/windows/creating-an-icon-or-other-image-image-editor-for-icons) | 65.403017 | 653 | 0.760372 | spa_Latn | 0.970794 |
58aa97d7160595c27ba6516e5f233156ab4c8347 | 2,061 | md | Markdown | blog/2006-4-13-cps4-project-officially-started.md | sfermigier/fermigier.com-gridsome | cd02a8aba46754cbbe8d080c48ee21595061b4c4 | [
"MIT"
] | null | null | null | blog/2006-4-13-cps4-project-officially-started.md | sfermigier/fermigier.com-gridsome | cd02a8aba46754cbbe8d080c48ee21595061b4c4 | [
"MIT"
] | 12 | 2020-05-22T07:48:50.000Z | 2022-02-26T16:04:59.000Z | blog/2006-4-13-cps4-project-officially-started.md | sfermigier/fermigier.com-gridsome | cd02a8aba46754cbbe8d080c48ee21595061b4c4 | [
"MIT"
] | null | null | null | ---
title: "CPS4 project officially started!"
date: 2006-04-13
path: /blog/2006/4/cps4-project-officially-started
summary: "Two signs that the CPS4 project has officially started: Florent has committed a roadmap in the SVN."
tags: ['Nuxeo', 'CPS', 'Java', 'Apache']
---
<p>
Two signs that the CPS4 project has officially started:
</p><ul><li>Florent has committed a <a href="http://svn.nuxeo.org/trac/pub/file/CPS4/trunk/doc/ROADMAP.txt">roadmap</a> in the SVN. (This roadmap will obviously be the basis for <a href="http://www.zope.org/Members/nuxeo/news/z3ecm-sprint-2006">next week sprint</a> at Nuxeo's office in Paris).</li>
<li>The <a href="http://lists.nuxeo.com/cgi-bin/mailman/listinfo/cps4">CPS4</a> mailing list is now open for the community (and last week's private discussion <a href="http://lists.nuxeo.com/pipermail/cps4/2006-April/date.html">archives</a> are available too).</li>
</ul><p>
Now, you may ask, "what is CPS4?"
</p><p>
In a couple of sentences, that will be expanded in upcoming blog postings: CPS4 is the evolution of CPS3 towards more <a href="http://lists.nuxeo.com/pipermail/z3lab/2005-May/000020.html">openness</a> and more scalability. We keep all the <a href="http://en.wikipedia.org/wiki/Enterprise_content_management">ECM</a> functions we like in <a href="http://www.cps-project.org/sections/about/cps-platform-framework-r">CPS framework</a> (the repository, the documents schemas, the directories, events, skins, portlets, relations...) , and we leverage both the work done on the <a href="http://www.z3lab.org/">Z3ECM</a> project, and
the offering of the Apache project (<a href="http://lucene.apache.org/">Lucene</a>, <a href="http://jackrabbit.apache.org/">Jackrabbit</a>) and a few other established infrastructure Java projects. Last thing: we plan to use the <a href="http://www.zeroc.com/">ICE</a> high-performance communication engine for communication between the different components.
</p><p>
FAQ: "Is the CPS 3.4 branch still supported?" R: of course, we also plan to do a CPS 3.4.1 release very soon.
</p>
| 85.875 | 626 | 0.738476 | eng_Latn | 0.918907 |
58aad42e819b8519919e68b262e9f3770cda410f | 252 | md | Markdown | readme.md | Ducklett/p30m | e69219776ecbe0c36c90eae303396cc9c38cbfae | [
"Unlicense"
] | null | null | null | readme.md | Ducklett/p30m | e69219776ecbe0c36c90eae303396cc9c38cbfae | [
"Unlicense"
] | null | null | null | readme.md | Ducklett/p30m | e69219776ecbe0c36c90eae303396cc9c38cbfae | [
"Unlicense"
] | null | null | null | 30 minute programming practice sessions.
These are intended to train memorization of the standard library and basic algorithms, no code is shared between session.
Adding comments and some minor refactoring work is done after the 30 minutes are over.
| 50.4 | 122 | 0.821429 | eng_Latn | 0.999923 |
58aad7844bbbf11a988344adaf803509f90781c3 | 788 | md | Markdown | pages/mesosphere/dcos/cn/1.13/cli/command-reference/dcos-marathon/dcos-marathon-pod-show/index.md | aditya08maker/dcos-docs-site | 2d6bc0b560876ef1d783f30cfc602a6c6b03caeb | [
"Apache-2.0"
] | 57 | 2017-12-21T00:51:03.000Z | 2021-12-28T19:46:12.000Z | pages/mesosphere/dcos/cn/1.13/cli/command-reference/dcos-marathon/dcos-marathon-pod-show/index.md | aditya08maker/dcos-docs-site | 2d6bc0b560876ef1d783f30cfc602a6c6b03caeb | [
"Apache-2.0"
] | 1,303 | 2017-12-14T22:43:03.000Z | 2022-03-31T21:32:50.000Z | pages/mesosphere/dcos/cn/1.13/cli/command-reference/dcos-marathon/dcos-marathon-pod-show/index.md | aditya08maker/dcos-docs-site | 2d6bc0b560876ef1d783f30cfc602a6c6b03caeb | [
"Apache-2.0"
] | 140 | 2017-12-22T11:51:30.000Z | 2022-03-07T09:46:58.000Z | ---
layout: layout.pug
navigationTitle: dcos marathon pod show
title: dcos marathon pod show
menuWeight: 27
excerpt: 显示特定 pod 的详细信息
enterprise: false
render: mustache
model: /mesosphere/dcos/1.13/data.yml
---
# 说明
`dcos marathon pod show` 命令允许您查看特定 pod 的详细信息。
# 使用
```bash
dcos marathon pod show <pod-id>
```
# 选项
| 名称 | 说明 |
|---------|-------------|
| `-h`, `--help` | 显示有关此命令用法的信息。 |
## 位置自变量
| 名称 | 说明 |
|---------|-------------|
| `<pod-id>` | POD ID。您可以使用 `dcos marathon pod list` 命令查看 pod ID 列表。|
# 示例
## 显示 Pod JSON
要查看 pod 定义，请运行以下命令：
```
dcos marathon pod show <pod-id>
```
您可使用 `show` 命令以编程方式读取有关 pod 的数据。
# 父命令
| 命令 | 说明 |
|---------|-------------|
| [dcos marathon](/mesosphere/dcos/cn/1.13/cli/command-reference/dcos-marathon/) | 将应用程序部署到 DC/OS 并对其进行管理。 |
| 15.76 | 108 | 0.596447 | yue_Hant | 0.267842 |
58ab41cd2d72c4011f5a52aacae9306ca4fa2bb3 | 6,696 | md | Markdown | 04.2022/30.04.2022.md | pirocorp/Ukraine-Russia-War | 1e3cccbf37aa84cc067d44b6390e2517b1c534d0 | [
"MIT"
] | 2 | 2022-03-07T12:28:11.000Z | 2022-03-21T09:55:52.000Z | 04.2022/30.04.2022.md | pirocorp/Ukraine-Russia-War | 1e3cccbf37aa84cc067d44b6390e2517b1c534d0 | [
"MIT"
] | null | null | null | 04.2022/30.04.2022.md | pirocorp/Ukraine-Russia-War | 1e3cccbf37aa84cc067d44b6390e2517b1c534d0 | [
"MIT"
] | null | null | null | 
# There reportedly is only one remaining road bridge between Izyium and Rubizhne.
# Ukrainian helicopters flying low and firing rockets towards Russian positions
https://user-images.githubusercontent.com/34960418/166098090-b5809096-6f6a-4e68-8035-b3d80db3fc6f.mp4
Ukrainian Mi-8MSB helicopter doing that indirect fire thing with lofted S-13 122mm rockets
https://user-images.githubusercontent.com/34960418/166097420-e84f6802-1042-47f5-a0b2-3855a6245c29.mp4
# Captured
## BMD-4M
https://user-images.githubusercontent.com/34960418/166113585-1fc2435a-7b05-44c9-a9f9-ce2a9fb9b5fb.mp4
## 2 x BMP-3
https://user-images.githubusercontent.com/34960418/166110787-665064a1-8796-4694-bc2a-b029bcd09856.mp4
## T-90A
https://user-images.githubusercontent.com/34960418/166110710-1dab8569-4229-4776-8ae6-bb639db6484c.mp4
## T-80U
https://user-images.githubusercontent.com/34960418/166103267-5d8889af-87a2-4bb4-94cf-fb022b0ccbb2.mp4
# Destroyed
## Stugna-P vs KA52
Yet another Russian Ka-52 attack helicopter was struck by a Ukrainian Stugna-P ATGM
https://user-images.githubusercontent.com/34960418/166125131-8a9d1b62-f8e5-4dbb-9f23-038f6b8fb039.mp4
## Orlan-10
Another Orlan-10 drone of the Russian Forces crashed. However, this one is unusual- it has markings indicating that it is from the Ministry of Emergency Situations.
Why this UAV meant for civil situations would be used by the Russian side is unclear.
## Artillery fire from TDF "Azov" forces landed near a Russian tank somewhere in the East, damaging it.
https://user-images.githubusercontent.com/34960418/166103613-ed672ff9-debf-43a1-88a0-a2c46a26a098.mp4
## BTR-ZD
https://user-images.githubusercontent.com/34960418/166103556-a1b921b9-ee46-4cbb-9b5f-6c9eb872f504.mp4
## Video of a Russian truck targeted by Ukraine. Possibly from a mine.
https://user-images.githubusercontent.com/34960418/166103485-7191dff2-b7ca-4523-b891-05022133e371.mp4
## BMP-3
https://user-images.githubusercontent.com/34960418/166103145-5eeb3e9f-36e6-48d3-9569-4135ddad25bb.mp4
## BMD-4M
https://user-images.githubusercontent.com/34960418/166110410-23965e1e-3cc1-4c0a-bcff-e09de4a1fb1f.mp4
## Destroyed Russian artillery positions.
Msta-B howitzers and ammunition trucks.
## 2 x BMP-3 IFV
Ukrainian Naval Infantry halted the Russian mechanised infantry assault and knocked out two Russian BMP-3 IFV.
https://user-images.githubusercontent.com/34960418/166097446-6255f751-bf55-4daf-82b6-53c32a56e124.mp4
# Izyum
## Video of a Russian armored vehicle on fire in Topolske near Izyum reportedly a result of Ukrainian artillery fire.
https://user-images.githubusercontent.com/34960418/166103333-0e696ba5-4fb0-41c3-a4d0-56d8aaf2f13c.mp4
## Ukrainian forces destroyed Russian equipment in Izyum area, Kharkiv Oblast (49.289967,37.232252)
https://user-images.githubusercontent.com/34960418/166124938-22985d33-8bbd-4a7b-9600-9b361bd7659b.mp4
General Simonov 2nd army killed
# Kharkiv
## Ukrainian forces liberated Verkhnya Rohanka and Slobidske in the vicinity of Kharkiv today
# Luhansk
## Battle footage of the Ukrainian Naval Infantry in Luhansk oblast.
https://user-images.githubusercontent.com/34960418/166124523-127cc4ff-0731-4f6f-be4d-73a2661e2f57.mp4
# Mariupol
## Russian tank repeatedly fires into a building, trying to make it collapse. (47.114348, 37.616064 near Azovstal)
Then civilians come out of it, presumably from the basement. Russian soldiers also seen. This video is a clear demonstration of why civilians in Mariupol, including those hiding in the Azovstal plant, are afraid to leave the basements and do not believe the occupiers about the possibility of a safe evacuation from the city.
https://user-images.githubusercontent.com/34960418/166110202-7fd5ff2e-2b77-497e-8001-9e85e3c12b1f.mp4
# Lyman, DPR
## Strike from Ukrainian MLRS. 🔥
https://user-images.githubusercontent.com/34960418/166124182-f333c60d-9d2d-49bc-ad5e-703cbcd2c54b.mp4
https://user-images.githubusercontent.com/34960418/166124804-8038856b-0862-4e7b-be71-f92fc1ab5b82.mp4
# Belgorod, Russia
Something going on over Belgorod in Russia tonight. Anti-air missiles fired and flashes in the sky
https://user-images.githubusercontent.com/34960418/166098593-425c3058-ace9-4d42-b190-baefc0170350.mp4
# Sakhalin, Russia (Coordinates: 48°02'59"N 142°10'50"E)
Russian Far East: Fire at GRES-2 Power plant in Sakhalin this morning
https://user-images.githubusercontent.com/34960418/166097751-f21d539d-71d7-429c-9bec-b31658ff1a5b.mp4
https://user-images.githubusercontent.com/34960418/166098157-6526d077-9864-4fde-9b2b-ec65d2d2bc48.mp4
# Zhecha, Bryansk Oblast, Russia (52.720364, 32.748816)
https://user-images.githubusercontent.com/34960418/166097587-3901b206-187e-4dec-a121-2aa6e18a4a6b.mp4
| 35.807487 | 325 | 0.806601 | yue_Hant | 0.145766 |
58ab6052dfaaedef0c7903c0fe92c7cb0bcbcad7 | 6,770 | md | Markdown | docs/_posts/2013-06-04-why-react.md | petehunt/react | 03a468f717f6b3b7b21da09a95131cb8241b9ec1 | [
"Apache-2.0"
] | 2 | 2015-09-23T17:07:33.000Z | 2017-02-05T21:49:01.000Z | docs/_posts/2013-06-04-why-react.md | petehunt/react | 03a468f717f6b3b7b21da09a95131cb8241b9ec1 | [
"Apache-2.0"
] | null | null | null | docs/_posts/2013-06-04-why-react.md | petehunt/react | 03a468f717f6b3b7b21da09a95131cb8241b9ec1 | [
"Apache-2.0"
] | null | null | null | ---
title: Why Should You Care About React?
layout: post
author: Pete Hunt
---
There are a lot of JavaScript MVC frameworks out there. Why did we build React
and why would you want to use it?
## React isn't an MVC framework.
It's a library designed for building big UIs. The type where you have lots of
reusable components that are handling events, presenting backend data, and
accepting user input. The type where you have to integrate with legacy code, and
support legacy browsers.
In the traditional MVC pattern, React is used to build the view. React lets you
decide how to manage your data and business logic, be it outside of React
components or within.
## React doesn't use templates.
Traditionally, web application UIs are built using templates written in
templating languages or HTML directives. These templating languages or directives
dictate the full set of abstractions that you are allowed to use to build the user
interface.
But templating languages can be constraining and difficult to use. UI logic is
often just as complicated as backend logic; why use a constrained language to
express it?
Historically, the reason for using templating languages has been to support
WYSIWYG editors. Today, WYSIWYG editors aren't prevalent for large-scale
application development so we consider this a non-issue.
In our experience separating display logic and markup does more harm than good.
Introducing barriers between them usually just creates more friction for
engineers. It's also not a real separation of concerns; **markup and display
logic are intimately tied and are both part of the display layer**. It's a costly
overreaction to the spaghetti code of the past. Remember: React only implements
your view layer, so all of the logic embedded within React components is display
logic.
## Build modular components in JavaScript instead.
React approaches building user interfaces differently by breaking them down into
smaller, composable and reusable **components**. **Simple, modular components let
the app developer determine the proper separation of concerns within the display
layer using familiar JavaScript idioms**.
You can think of components as simple functions that take in some parameters (one
could call them the model) and return a description of the markup that may contain
other components. To make this easy we've created `React.DOM`, a simple, safe and
efficient way to generate markup from within JavaScript **without string
concatenation or DOM manipulation**. We've also created
[JSX](facebook.github.io/react/docs/syntax.html) in case you prefer the
readability of HTML syntax.
Since React components just take some backing data and generate a description of
the UI, **we think of React as a functional library for building UI
components.** Building your app as modular, functional components makes it easy to
maintain and easy to reason about.
And because you're writing your display logic in regular JavaScript you can use all
of the familiar tools and abstractions available to you to make front-end code
easier to write and maintain.
By the way, we're not the first JavaScript library to eschew templates.
[Ext JS](http://www.sencha.com/products/extjs/) and [Enyo](http://enyojs.com/)
are two examples of many great frameworks that do this today.
## Reactive updates are dead simple.
React really shines when your data changes over time.
In a traditional JavaScript application, you need to look at what data changed
and imperatively make changes to the DOM to keep it up-to-date. Even AngularJS,
which provides a declarative interface via directives and data binding,
[requires manual DOM manipulation](http://docs.angularjs.org/guide/directive#reasonsbehindthecompilelinkseparation)
to write reusable, dynamic components. Remember, React components are flexible
and expressive, more like directives and less like templates in AngularJS.
React takes a different approach.
When your component is first initialized, the `render()` method is called and a
string of static HTML is inserted into the DOM. When your data changes, the
`render()` method is called again. We simply diff the old return value with the
new one to determine the fastest way to update the DOM. **So if only a single
attribute on a single element changes, that's all that React updates**.
We call this process **reconciliation**. Check out
[this jsFiddle](http://jsfiddle.net/fv6RD/3/) for an example of reconciliation
in action.
**Reconciliation will usually be faster than handwritten code** because React knows
about the entire state of the page and can do cool tricks like batching reads
and writes and picking the fastest subset of DOM mutations to perform.
The way we're able to pull this off is by constructing a very fast, lightweight
representation of the DOM which knows which parts are dirtied and which parts
are clean. **The data returned from `render()` is neither a string nor a DOM
node -- it's a lightweight description of what the DOM should look like** in
terms of HTML tags and other React components.
Because this re-render is so fast (on the order of 1ms for TodoMVC), we don't
need the end user to explicitly specify data bindings. We've found this to be an
easier way to build apps. It's a lot like the early days of the dynamic web.
Back then, you wrote simple presentational code and when your data changed, you
simply refreshed the page. Today, React makes that refresh very fast and
lightweight, and only the parts of markup that need to be changed are changed.
No other framework that we've seen has managed to decouple building UIs from the
DOM to this degree.
## HTML is just the beginning.
Since React makes very few assumptions about its environment, we can do some
pretty cool things with it:
- Facebook has dynamic charts that render to `<canvas>` instead of HTML.
- Instagram is a "single page" web app built entirely with React and
`Backbone.Router`. Designers regularly contribute React code with JSX.
- We've built internal prototypes that run React apps in a **web worker** and
on iOS driving **native views** (no HTML!) via an Objective-C bridge.
- You can run React
[on the server](http://github.com/petehunt/react-server-rendering)
for SEO, performance, code sharing and overall flexibility.
- Events behave in a consistent, standards-compliant way in all browsers
(including IE8) and automatically use
[event delegation](http://davidwalsh.name/event-delegate).
Head on over to
[facebook.github.io/react](http://facebook.github.io/react) to check
out what we have built. Our documentation is geared towards building
apps with the framework, but if you are interested in the
nuts and bolts
[get in touch](http://facebook.github.io/react/support.html) with us!
Thanks for reading!
| 48.014184 | 115 | 0.791581 | eng_Latn | 0.999386 |
58ac312553510de0d921fb52135e6ba137ee8a6f | 8,506 | md | Markdown | README.md | deepti-96/Lane-detection | c293807a3a581c653d0449e790e6725efa8da052 | [
"MIT"
] | 1 | 2022-02-06T20:44:12.000Z | 2022-02-06T20:44:12.000Z | README.md | deepti-96/Lane-detection | c293807a3a581c653d0449e790e6725efa8da052 | [
"MIT"
] | null | null | null | README.md | deepti-96/Lane-detection | c293807a3a581c653d0449e790e6725efa8da052 | [
"MIT"
] | null | null | null | # LANE DETECTION AND LANE DEPARTURE MONITORING
## Project Description & Objective
This project was designed to demonstrate how a lane detecting system on a car with a front facing camera works.<br />
This technology is becoming increasingly common in cars, and it is an important component of the advanced driver assistance systems (ADAS) used in autonomous and semi-autonomous vehicles. This feature oversees identifying lanes, measuring curve radius (curve tightness), and keeping track of the offset from the center. With this information, the system enhances safety by ensuring that the car remains centered within the lane lines and provides comfort if it is programmed to operate the steering wheel to negotiate moderate turns on highways without human input. This is a reduced version of what is used in production cars, and it performs best under ideal conditions (clear lane lines, stable light conditions). A dash cam clip is supplied in this repository for the script to operate with.<br />
## Getting started
In terms of how to operate this project, it takes a straightforward approach.<br />
Only two files are required to get it up and running.<br />
• laneDetection is the sole file that can analyze images and detect lanes.<br />
• drive is the video file on which image processing is done.<br />
Ensure that both files (laneDetection.py and drive.mp4) are in the same folder.<br />
## Necessary requirements
It is necessary to have the following applications installed, along with their corresponding versions, to complete the project successfully:<br />
• Python 3.6 or above is required.<br />
• OpenCV version 3 or above (Will be used by the script and can be downloaded using pip)<br />
• NumPy 1.14 or higher is required (Will be used by the script and can be downloaded using pip)<br />
• Scipy version 1.1 or above (Will be used by the script and can be downloaded using pip)<br />
## Environment and Dependencies
It should be mentioned that this project was created on a Microsoft Windows 10 (64 Bit) computer, but it should function on other systems with minimal adjustments. Follow the steps in the preceding section (Necessary requirements) for Python packages to ensure that you have the right versions of dependencies.<br />
## How Does the Code Function?
For the script laneDetection.py, a video file containing dashcam footage of a car traveling along the highway is given. The Python software uses a modular method to do lane detection and includes numerous functionalities.<br />
## Image Processing
### readVideo ()
First up is the readVideo() function to access the video file drive.mp4 which is in the same directory.<br />
### processImage ()
By performing some processing techniques, this function separates white lane lines, preparing them for further optimization by the upcoming functions. By applying HLS color filtering, it filters out the whites in the frame and converts it into grayscale, it applies thresholding to eliminate duplicate detections other than lanes, gets blurred, and then edges are extracted with the cv2.Canny() function.<br />
### perspectiveWarp ()
After we get the image we desire, we apply a perspective warp. Four points are put on the frame in such a way that they only surround the area where lanes are present (as shown), and the data is then mapped into another matrix to produce a bird’s eye view of the lanes. This will allow us to work with a far more precise picture and aid with lane curvature detection. It should be noted that if a different video is utilized, this process may alter. With this footage in mind, the preset four points are computed. If another video with a little different oriented camera is added, it should be returned. <br />
<br />
## Lane Detection, Curve Fitting & Calculations
### plotHistogram ()
Plotting a histogram for the bottom half of the image is critical for determining the exact location of the left and right lanes. When looking at the histogram, there are two separate peaks where all the white pixels may be seen. This is a great way to tell where the left and right lanes start. Because the histogram x coordinate corresponds to the x coordinate of our analyzed frame, we now have x coordinates with which to begin looking for lanes.<br />
<br />
### slide_window_search ()
To recognize lanes and their curvature, a sliding window method is utilized. It takes the data from the preceding histogram function and creates a box with a lane in the middle. Then it builds another box on top of it, based on the white pixel locations from the preceding box, all the way to the top of the frame. We now have the data we need to perform some computations. The curve is then fitted in pixel space using a second-degree polynomial fit.<br />
### general_search ()
Following the slide window search () function, the general search () method may now fill in an area around the identified lanes, and then use the second degree polyfit to create a yellow line that overlaps the lanes rather precisely. This line will be used to calculate the radius of curvature, which is necessary for calculating steering angles.<br />
### measure_lane_curvature ()
The np.polyfit() method is used again with the information supplied by the previous two functions, but the values are multiplied by the xm_per_pix and ym_per_pix variables to transform them from pixel to meter space. xm_per_pix is set to 3.7 / 720, which equates to a lane width of 3.7 meters and left and right lane base x coordinates determined from the histogram, which translates to a lane width of roughly 720 pixels. Because the frame height is 720, ym_per_pix is also set to 30 / 720.<br />
<br />
## Visualization and Main Function
### draw_lane_lines ()
Following that, several approaches are used to visualize the identified lanes as well as other data that will be presented in the final image. This program uses identified lanes to fill the space within them with a green hue. It also depicts the lane's center by saving the mean of the left_fitx and right_fitx lists in the pts mean variable, which is subsequently represented by a yellowish tint. This variable is also used to determine whether the car is displaced to one side or centered in the lane.<br />
### offCenter ()
The offset value is calculated and shown in meter space using the pts mean variable in the offCenter () method.<br />
### addText ()
Finally, the procedure and information shown would be completed by adding text to the finished image.<br />
### main ()
The main function is where all these functions are called in the proper order and where the video loop is contained.<br />
<br />
## Important Points to Remember
It should be mentioned that this project was built for demonstration reasons only, and its success is dependent on the footage given. The image processing portion is kept relatively basic, and it may fail to detect lanes in low or unsteady light. Lane lines must be readily visible, and tighter bends might make fitting curves and visualization more difficult. The fundamental aim behind the creation of this project was for self-improvement and educational objectives.<br />
## Additional Remarks
When comparing this project to one of the production-ready versions, things are a lot more complicated, because error rates should be extremely low, and the system should be able to react to a variety of scenarios. For instance, unstable light circumstances with a large shift in light density, or weather conditions that affect road surface visibility, etc. In this project, several variables are hardcoded, and any modification might cause the setup to fail. As a result, techniques like machine learning should be employed to make this system more adaptable and less likely to fail in real-world scenarios.<br />
## References
The following presentation was found to be useful during the creation of this project, and this project takes a similar approach to what is described in the presentation.<br />
Presentation: https://www.youtube.com/watch?v=VyLihutdsPk&t=1295s
| 98.906977 | 801 | 0.788972 | eng_Latn | 0.999742 |
58ac7ca8dcb35da3329a5e9e18e9ff00d2ed7eac | 5,413 | md | Markdown | README.md | TRUEJASONFANS/DuiTang_waterfall_- | bb01a1450629847e8a48e587adb270077029f2d4 | [
"Apache-2.0"
] | null | null | null | README.md | TRUEJASONFANS/DuiTang_waterfall_- | bb01a1450629847e8a48e587adb270077029f2d4 | [
"Apache-2.0"
] | null | null | null | README.md | TRUEJASONFANS/DuiTang_waterfall_- | bb01a1450629847e8a48e587adb270077029f2d4 | [
"Apache-2.0"
] | null | null | null | PLA(PinterestLikeAdapterView)
==================================
-
Open source project in order to implement pinterest like list view on android.
(You can check how pinterest app looks like form below link..)
https://play.google.com/store/apps/details?id=com.pinterest&hl=en
This project is statred based on sony deveoper's blog post 'making your own 3d list'.
http://developer.sonymobile.com/2010/05/20/android-tutorial-making-your-own-3d-list-part-1/
But, currenty it is implemented based on android framework 2.3's list view source.
You can check modified list view sources in internal package.
Not supported Features
---------------
* Entry from XML layout.
* Choice Mode & Item Selection.
* Filter
* Handle Key Event & Arrow Scrolling..
TODO:
---------------
* 下拉刷新后保持当前位置
* 多选模式
* 图片的宽度判断
Screen Shot
----------------
新截图
This is a screen shot of sample activity.
![Example Image][3]
How to use
-------------
*To run Sample App.*
1. clone project.
2. run on your android phone.
3. in option menu, you can add items or lunch pull-to-refresh sample.
*To use Pinterest Like Multi Column View.*
1. check this project as library project.
2. MultiColumListView is the view what you need.
*To use pull-to-refresh features.*
1. check this project as library project.
2. MultiColumnPullToRefreshListView class in extra folder is what you need.
Attributes
-----------
* **plaColumnNumber**
Number of column. (default value is 2)
* **plaLandscapeColumnNumber**
Number of column in landscape mode (the orientation that window's width is longer than height.)
Overridable Methods
--------------------
PLA_ListView was made based on Android 2.3 Framework's ListView,
and support those protected methods to let a user customize list view's behavior.
@Override
protected void onMeasureChild(View child, int position, int widthMeasureSpec, int heightMeasureSpec);
@Override
protected void onItemAddedToList(int position, boolean flow );
@Override
protected void onLayoutSync(int syncPos);
@Override
protected void onLayoutSyncFinished(int syncPos);
@Override
protected int getFillChildBottom();
@Override
protected int getFillChildTop();
@Override
protected int getScrollChildBottom();
@Override
protected int getScrollChildTop();
@Override
protected int getItemLeft(int pos);
@Override
protected int getItemTop( int pos );
@Override
protected int getItemBottom( int pos );
@Override
protected void onAdjustChildViews( boolean down );
Change Log
-----------
**2012.11.7**
http://developer.sonymobile.com/2010/05/20/android-tutorial-making-your-own-3d-list-part-1/
기반으로 러프하게 작성되었습니다.
**2012.11.8**
패키지 구조가 com.huewu.pla.* 형태로 변경되었습니다.
안드로이드 2.3 버전의 ListView 기반으로 수정되었습니다. (Don't reinvent the wheel)
프레임워크 소스 중 리스트 뷰 관련 파일을 긁어와 많은 Rabbit Hole 을 땜방했습니다.
결과물은 com.huewu.pla.lib.internal 패키지를 참고하시기 바랍니다.
**2012.11.9**
Android-PullToRefresh 라이브러이와 연동되도록 extra package 를 추가했습니다.
이 오픈소스 프로젝트를 기반으로, https://github.com/chrisbanes/Android-PullToRefresh
해당 소스의 일부 내용을 수정 했습니다. (확장을 위한 visiblity)
스크롤 업/다움 시 그리고 어댑터에 아이템 추가 시 컬럼 위치가 변경되는 버그를 수정했습니다.
**2012.11.10**
xml layout 상에서 컬럼 수를 지정할 수 있도록 두 개의 Attribute 를 추가했습니다.
*plaColumnNumber*
*plaLandscapeColumnNumber*
ActionBarSherlock 라이브러리와 함께 사용할 시 발생하는 Attriubte 충돌 문제를 수정했습니다.
**2012.11.12**
Fling 및 Scroll 시 영역 계산이 제대로 이루어지지 않아서 스크롤이 끝까지 이루어지지 않거나, 화면이 떨리는 버그를 수정했습니다.
Override 가능한 함수들의 이름을 이해하기 쉽게(?) 변경했습니다.
**2012.11.13**
Header View 를 정상적으로 지원합니다.
Pull-To-Refresh 기능을 위해, 기존 사용하던 오픈 소스 대신
https://github.com/erikwt/PullToRefresh-ListView
를 사용하도록 수정하였습니다. 다른 프로젝트와 의존성 없이 사용 가능합니다.
**2012.11.14**
하나 이상의 Header View 와 Footer View 를 지원합니다.
**2012.11.22**
첫번째 아이템이 보이는 경우, 각 컬럼의 Top 포지션을 강제로 정렬 시키도록 수정했습니다.
**2012.11.26**
리스트에 새로운 아이템이 추가되는 경우 Fling 속도가 비정상적으로 빨라지는 버그를 수정했습니다.
**2012.11.28**
Layout 이벤트 시, 아이템의 위치가 변경되는 버그를 수정했습니다.
Item Select 관련된 코드가 제거되었습니다.
TODO
---------------------------------------------
> 1. Fling 및 스크롤바를 지원하지 않습니다.
> 2. Scroll Up / Down 시 재 정렬되는 아이템의 위치가 변경되는 버그가 있습니다.
> 3. 리스트의 마지막 부분에서 스크롤이 자연스럽지 않습니다.
> 4. 어뎁터에 데이터를 추가해도 정상적으로 동작
> 5. PullToRefresh 라이브러리와 연동.
> 6. Fling 속도가 이상함.
> 7. 복잡한 뷰를 사용하는 경우, 스크롤 할 떄 마다 뷰의 위치가 Y Position 이 변경됩니다.
8. 어댑터에 데이터가 삭제, 변경되거나 중간에 삽입 되는 경우 처리
*그외 아주 많은 문제가 있습니다... 아직 열혈 개발 중 인걸요... =)
Contributing
---------------------------------------------
어떤 종류의 지원도 언제나 환영입니다 =)
Any kinds of helps ( bug report / push request / suggestionss ) are welcomed =)
## License
Copyright 2012 huewu.yang
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.
[3]: http://cloud.github.com/downloads/huewu/PinterestLikeAdapterView/screenshot.png
| 23.331897 | 103 | 0.710881 | kor_Hang | 0.995834 |
58ac7e747b2e2c44fc56580f81bc2e2e6ac1d569 | 11,777 | md | Markdown | docs/xamarin-forms/data-cloud/data/databases.md | DamianSuess/xamarin-docs | 3bc1dea069f4e646c762efbd41b99f038284f01d | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-12-09T05:19:03.000Z | 2021-12-09T05:19:03.000Z | docs/xamarin-forms/data-cloud/data/databases.md | DamianSuess/xamarin-docs | 3bc1dea069f4e646c762efbd41b99f038284f01d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/xamarin-forms/data-cloud/data/databases.md | DamianSuess/xamarin-docs | 3bc1dea069f4e646c762efbd41b99f038284f01d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "Xamarin.Forms Local Databases"
description: "Xamarin.Forms supports database-driven applications using the SQLite database engine, which makes it possible to load and save objects in shared code. This article describes how Xamarin.Forms applications can read and write data to a local SQLite database using SQLite.Net."
ms.prod: xamarin
ms.assetid: F687B24B-7DF0-4F8E-A21A-A9BB507480EB
ms.technology: xamarin-forms
author: profexorgeek
ms.author: jusjohns
ms.date: 03/01/2021
no-loc: [Xamarin.Forms, Xamarin.Essentials]
---
# Xamarin.Forms Local Databases
[ Download the sample](/samples/xamarin/xamarin-forms-samples/todo)
The SQLite database engine allows Xamarin.Forms applications to load and save data objects in shared code. The sample application uses a SQLite database table to store todo items. This article describes how to use SQLite.Net in shared code to store and retrieve information in a local database.
[](databases-images/todo-list.png#lightbox "Todolist app on iOS and Android")
Integrate SQLite.NET into mobile apps by following these steps:
1. [Install the NuGet package](#install-the-sqlite-nuget-package).
1. [Configure constants](#configure-app-constants).
1. [Create a database access class](#create-a-database-access-class).
1. [Access data in Xamarin.Forms](#access-data-in-xamarinforms).
1. [Advanced configuration](#advanced-configuration).
## Install the SQLite NuGet package
Use the NuGet package manager to search for **sqlite-net-pcl** and add the latest version to the shared code project.
There are a number of NuGet packages with similar names. The correct package has these attributes:
- **ID:** sqlite-net-pcl
- **Authors:** SQLite-net
- **Owners:** praeclarum
- **NuGet link:** [sqlite-net-pcl](https://www.nuget.org/packages/sqlite-net-pcl/)
> [!NOTE]
> Despite the package name, use the **sqlite-net-pcl** NuGet package even in .NET Standard projects.
## Configure app constants
The sample project includes a **Constants.cs** file that provides common configuration data:
```csharp
public static class Constants
{
public const string DatabaseFilename = "TodoSQLite.db3";
public const SQLite.SQLiteOpenFlags Flags =
// open the database in read/write mode
SQLite.SQLiteOpenFlags.ReadWrite |
// create the database if it doesn't exist
SQLite.SQLiteOpenFlags.Create |
// enable multi-threaded database access
SQLite.SQLiteOpenFlags.SharedCache;
public static string DatabasePath
{
get
{
var basePath = Environment.GetFolderPath(Environment.SpecialFolder.LocalApplicationData);
return Path.Combine(basePath, DatabaseFilename);
}
}
}
```
The constants file specifies default `SQLiteOpenFlag` enum values that are used to initialize the database connection. The `SQLiteOpenFlag` enum supports these values:
- `Create`: The connection will automatically create the database file if it doesn't exist.
- `FullMutex`: The connection is opened in serialized threading mode.
- `NoMutex`: The connection is opened in multi-threading mode.
- `PrivateCache`: The connection will not participate in the shared cache, even if it's enabled.
- `ReadWrite`: The connection can read and write data.
- `SharedCache`: The connection will participate in the shared cache, if it's enabled.
- `ProtectionComplete`: The file is encrypted and inaccessible while the device is locked.
- `ProtectionCompleteUnlessOpen`: The file is encrypted until it's opened but is then accessible even if the user locks the device.
- `ProtectionCompleteUntilFirstUserAuthentication`: The file is encrypted until after the user has booted and unlocked the device.
- `ProtectionNone`: The database file isn't encrypted.
You may need to specify different flags depending on how your database will be used. For more information about `SQLiteOpenFlags`, see [Opening A New Database Connection](https://www.sqlite.org/c3ref/open.html) on sqlite.org.
## Create a database access class
A database wrapper class abstracts the data access layer from the rest of the app. This class centralizes query logic and simplifies the management of database initialization, making it easier to refactor or expand data operations as the app grows. The Todo app defines a `TodoItemDatabase` class for this purpose.
### Lazy initialization
The `TodoItemDatabase` uses asynchronous lazy initialization, represented by the custom `AsyncLazy<T>` class, to delay initialization of the database until it's first accessed:
```csharp
public class TodoItemDatabase
{
static SQLiteAsyncConnection Database;
public static readonly AsyncLazy<TodoItemDatabase> Instance = new AsyncLazy<TodoItemDatabase>(async () =>
{
var instance = new TodoItemDatabase();
CreateTableResult result = await Database.CreateTableAsync<TodoItem>();
return instance;
});
public TodoItemDatabase()
{
Database = new SQLiteAsyncConnection(Constants.DatabasePath, Constants.Flags);
}
//...
}
```
The `Instance` field is used to create the database table for the `TodoItem` object, if it doesn't already exist, and returns a `TodoItemDatabase` as a singleton. The `Instance` field, of type `AsyncLazy<TodoItemDatabase>` is constructed the first time it's awaited. If multiple threads attempt to access the field simultaneously, they will all use the single construction. Then, when the construction completes, all `await` operations complete. In addition, any `await` operations after the construction is complete continue immediately since the value is available.
> [!NOTE]
> The database connection is a static field which ensures that a single database connection is used for the life of the app. Using a persistent, static connection offers better performance than opening and closing connections multiple times during a single app session.
### Asynchronous lazy initialization
In order to start the database initialization, avoid blocking execution, and have the opportunity to catch exceptions, the sample application uses asynchronous lazy initalization, represented by the `AsyncLazy<T>` class:
```csharp
public class AsyncLazy<T>
{
readonly Lazy<Task<T>> instance;
public AsyncLazy(Func<T> factory)
{
instance = new Lazy<Task<T>>(() => Task.Run(factory));
}
public AsyncLazy(Func<Task<T>> factory)
{
instance = new Lazy<Task<T>>(() => Task.Run(factory));
}
public TaskAwaiter<T> GetAwaiter()
{
return instance.Value.GetAwaiter();
}
}
```
The `AsyncLazy` class combines the `Lazy<T>` and `Task<T>` types to create a lazy-initialized task that represents the initialization of a resource. The factory delegate that's passed to the constructor can either be synchronous or asynchronous. Factory delegates will run on a thread pool thread, and will not be executed more than once (even when multiple threads attempt to start them simultaneously). When a factory delegate completes, the lazy-initialized value is available, and any methods awaiting the `AsyncLazy<T>` instance receive the value. For more information, see [AsyncLazy](https://devblogs.microsoft.com/pfxteam/asynclazyt/).
### Data manipulation methods
The `TodoItemDatabase` class includes methods for the four types of data manipulation: create, read, edit, and delete. The SQLite.NET library provides a simple Object Relational Map (ORM) that allows you to store and retrieve objects without writing SQL statements.
```csharp
public class TodoItemDatabase
{
// ...
public Task<List<TodoItem>> GetItemsAsync()
{
return Database.Table<TodoItem>().ToListAsync();
}
public Task<List<TodoItem>> GetItemsNotDoneAsync()
{
// SQL queries are also possible
return Database.QueryAsync<TodoItem>("SELECT * FROM [TodoItem] WHERE [Done] = 0");
}
public Task<TodoItem> GetItemAsync(int id)
{
return Database.Table<TodoItem>().Where(i => i.ID == id).FirstOrDefaultAsync();
}
public Task<int> SaveItemAsync(TodoItem item)
{
if (item.ID != 0)
{
return Database.UpdateAsync(item);
}
else
{
return Database.InsertAsync(item);
}
}
public Task<int> DeleteItemAsync(TodoItem item)
{
return Database.DeleteAsync(item);
}
}
```
## Access data in Xamarin.Forms
The `TodoItemDatabase` class exposes the `Instance` field, through which the data access operations in the `TodoItemDatabase` class can be invoked:
```csharp
async void OnSaveClicked(object sender, EventArgs e)
{
var todoItem = (TodoItem)BindingContext;
TodoItemDatabase database = await TodoItemDatabase.Instance;
await database.SaveItemAsync(todoItem);
// Navigate backwards
await Navigation.PopAsync();
}
```
## Advanced configuration
SQLite provides a robust API with more features than are covered in this article and the sample app. The following sections cover features that are important for scalability.
For more information, see [SQLite Documentation](https://www.sqlite.org/docs.html) on sqlite.org.
### Write-ahead logging
By default, SQLite uses a traditional rollback journal. A copy of the unchanged database content is written into a separate rollback file, then the changes are written directly to the database file. The COMMIT occurs when the rollback journal is deleted.
Write-Ahead Logging (WAL) writes changes into a separate WAL file first. In WAL mode, a COMMIT is a special record, appended to the WAL file, which allows multiple transactions to occur in a single WAL file. A WAL file is merged back into the database file in a special operation called a _checkpoint_.
WAL can be faster for local databases because readers and writers do not block each other, allowing read and write operations to be concurrent. However, WAL mode doesn't allow changes to the _page size_, adds additional file associations to the database, and adds the extra _checkpointing_ operation.
To enable WAL in SQLite.NET, call the `EnableWriteAheadLoggingAsync` method on the `SQLiteAsyncConnection` instance:
```csharp
await Database.EnableWriteAheadLoggingAsync();
```
For more information, see [SQLite Write-Ahead Logging](https://www.sqlite.org/wal.html) on sqlite.org.
### Copy a database
There are several cases where it may be necessary to copy a SQLite database:
- A database has shipped with your application but must be copied or moved to writeable storage on the mobile device.
- You need to make a backup or copy of the database.
- You need to version, move, or rename the database file.
In general, moving, renaming, or copying a database file is the same process as any other file type with a few additional considerations:
- All database connections should be closed before attempting to move the database file.
- If you use [Write-Ahead Logging](#write-ahead-logging), SQLite will create a Shared Memory Access (.shm) file and a (Write Ahead Log) (.wal) file. Ensure that you apply any changes to these files as well.
For more information, see [File Handling in Xamarin.Forms](~/xamarin-forms/data-cloud/data/files.md).
## Related links
- [Todo sample application](/samples/xamarin/xamarin-forms-samples/todo)
- [SQLite.NET NuGet package](https://www.nuget.org/packages/sqlite-net-pcl/)
- [SQLite documentation](https://www.sqlite.org/docs.html)
- [Using SQLite with Android](~/android/data-cloud/data-access/using-sqlite-orm.md)
- [Using SQLite with iOS](~/ios/data-cloud/data/using-sqlite-orm.md)
- [AsyncLazy](https://devblogs.microsoft.com/pfxteam/asynclazyt/)
| 46.734127 | 643 | 0.753588 | eng_Latn | 0.955125 |
58acba1ffc704808452bd9941f78d2e73b22b2fc | 58 | md | Markdown | packages/core/README.md | ccqgithub/react-rx-service | 79300fbd4f7cb2d37e450699f79b27add33cba2e | [
"MIT"
] | 2 | 2021-05-19T23:59:08.000Z | 2021-05-23T15:42:23.000Z | packages/core/README.md | ccqgithub/reactive-service | 79300fbd4f7cb2d37e450699f79b27add33cba2e | [
"MIT"
] | null | null | null | packages/core/README.md | ccqgithub/reactive-service | 79300fbd4f7cb2d37e450699f79b27add33cba2e | [
"MIT"
] | null | null | null | # @reactive-service/core
[文档](../../docs/core/index.md)。
| 14.5 | 31 | 0.62069 | fra_Latn | 0.161061 |
58ad14868a1a24c22080855e37636a33087b1db9 | 786 | md | Markdown | windows.media.core/timedtextsource_createfromuri_1421797945.md | gbaychev/winrt-api | 25346cd51bc9d24c8c4371dc59768e039eaf02f1 | [
"CC-BY-4.0",
"MIT"
] | 199 | 2017-02-09T23:13:51.000Z | 2022-03-28T15:56:12.000Z | windows.media.core/timedtextsource_createfromuri_1421797945.md | gbaychev/winrt-api | 25346cd51bc9d24c8c4371dc59768e039eaf02f1 | [
"CC-BY-4.0",
"MIT"
] | 2,093 | 2017-02-09T21:52:45.000Z | 2022-03-25T22:23:18.000Z | windows.media.core/timedtextsource_createfromuri_1421797945.md | gbaychev/winrt-api | 25346cd51bc9d24c8c4371dc59768e039eaf02f1 | [
"CC-BY-4.0",
"MIT"
] | 620 | 2017-02-08T19:19:44.000Z | 2022-03-29T11:38:25.000Z | ---
-api-id: M:Windows.Media.Core.TimedTextSource.CreateFromUri(Windows.Foundation.Uri,System.String)
-api-type: winrt method
---
<!-- Method syntax
public Windows.Media.Core.TimedTextSource CreateFromUri(Windows.Foundation.Uri uri, System.String defaultLanguage)
-->
# Windows.Media.Core.TimedTextSource.CreateFromUri
## -description
Creates a new instance of [TimedTextSource](timedtextsource.md) with the specified default language from the provided URI.
## -parameters
### -param uri
The URI from which the timed text source is created.
### -param defaultLanguage
A string specifying the default language for the timed text source.
## -returns
The new timed text source.
## -remarks
## -examples
## -see-also
[CreateFromUri(Uri)](timedtextsource_createfromuri_407037831.md) | 26.2 | 122 | 0.778626 | yue_Hant | 0.715864 |
58ad356109ca7a2c47ea6cd92ff54b2ffcf6a5ce | 1,013 | md | Markdown | x11-libs/libXt.md | filakhtov/gentoo-use-docs | 4db20ef1693080450ea7acf533e96d029f252f9d | [
"Unlicense"
] | 1 | 2019-05-12T13:36:30.000Z | 2019-05-12T13:36:30.000Z | x11-libs/libXt.md | filakhtov/gentoo-use-docs | 4db20ef1693080450ea7acf533e96d029f252f9d | [
"Unlicense"
] | 1 | 2018-06-13T02:50:47.000Z | 2018-06-13T02:50:47.000Z | x11-libs/libXt.md | filakhtov/gentoo-use-docs | 4db20ef1693080450ea7acf533e96d029f252f9d | [
"Unlicense"
] | 2 | 2018-06-11T21:27:10.000Z | 2020-05-05T14:07:42.000Z | # x11-libs/libXt
### doc
Pass the `--enable-specs` and `--with-xmlto` options to the configure command. This flag should build and install documentation, but does not currently do this.
This flag should be disabled, because it does not install the documentation but pulls in additional unnecessary dependencies.
### static-libs
Remove a `-Wl,-Bdirect` option from a `CFLAGS`, `CPPFLAGS`, `CXXFLAGS`, `CCASFLAGS`, `FFLAGS`, `FCFLAGS` and an `LDFLAGS` variables and a `-Bdirect` option from a `LDFLAGS` variable for a duration of a build. Build and install a statically linked version of a `libXt` library.
This flag should only be enabled if there is a need for the static library.
### test
Pass the `--enable-unit-tests` option to the configure command. Execute a `make check` option after the main build is completed. Execute a test suite provided with the source code. This will extend a build time.
The flag should normally be disabled as it is mainly useful for the Gentoo team, testers and developers.
| 59.588235 | 276 | 0.764067 | eng_Latn | 0.998858 |
58ae76ec714d7a3008fff07fbf752124ee240844 | 68 | md | Markdown | README.md | weshaw/GKOAuto | 299b6997157f87f7c456e89758db1d9e69d3029a | [
"MIT"
] | null | null | null | README.md | weshaw/GKOAuto | 299b6997157f87f7c456e89758db1d9e69d3029a | [
"MIT"
] | null | null | null | README.md | weshaw/GKOAuto | 299b6997157f87f7c456e89758db1d9e69d3029a | [
"MIT"
] | null | null | null | # GKOAuto
Create a .env file
```
COMPANIES_PATH=C:\Companies\
```
| 8.5 | 28 | 0.661765 | kor_Hang | 0.61991 |
58aee853a5c319d0af151ed12191c261ceb3853f | 100 | md | Markdown | tech/it/net/iot.md | samtron1412/pub-doc | e3f5d9136bfb3e985427a7441cffcecc6d824ac4 | [
"MIT"
] | 1 | 2018-05-21T17:14:54.000Z | 2018-05-21T17:14:54.000Z | tech/it/net/iot.md | samtron1412/pub-doc | e3f5d9136bfb3e985427a7441cffcecc6d824ac4 | [
"MIT"
] | null | null | null | tech/it/net/iot.md | samtron1412/pub-doc | e3f5d9136bfb3e985427a7441cffcecc6d824ac4 | [
"MIT"
] | 2 | 2016-05-23T09:37:20.000Z | 2016-11-24T08:34:23.000Z | [TOC]
# Overview
# References
[1]: http://www.riot-os.org/ "Open source operating system for IOT"
| 14.285714 | 67 | 0.69 | kor_Hang | 0.865501 |
58af3cefecbb06d5da9187243f1c9d72bb0e6000 | 825 | md | Markdown | cleandata.md | zsh2517/newblog | c57e5f8dc69f9774958d5e5580f2dc13f5c1a8ed | [
"MIT"
] | 1 | 2019-12-20T12:59:42.000Z | 2019-12-20T12:59:42.000Z | cleandata.md | zsh2517/zsh2517.github.io | c57e5f8dc69f9774958d5e5580f2dc13f5c1a8ed | [
"MIT"
] | null | null | null | cleandata.md | zsh2517/zsh2517.github.io | c57e5f8dc69f9774958d5e5580f2dc13f5c1a8ed | [
"MIT"
] | null | null | null | # 博客初始化说明
## 删除记录
### _drafts
留下template.md，别的删掉
### _includes
删掉 LRC-show.md adsense.html
### _posts
留下template.md，别的删掉
### _project
自己创建的目录。。一样留下template.md，别的删掉
### _qwq
这个已经不显示了。直接删掉就行
### _site
完全删掉，这是托管网站生成的目录
### _wiki
一样，留下template.md，别的删掉，其中要注意的是template.md里面有个show属性，控制是否显示。
上面别的分区没有（如果有也没有用）
### .vscode
我用的vscode的数据。删掉即可
### assets
网页的JS和CSS不用动
### images
里面blog\bg2.jpg是背景图。别的删掉即可
### labs
测试一些功能或者~~无聊~~写的。删掉即可
### pages
有一些没用的文件，顺便删了吧。。
2333333.md categories.1.md（1,2,3删掉，没有标号的不删）
### slide
reveal.js实现的幻灯片插件。要不要都行。自己加的
### temp
没用。。我也忘干嘛的了。。
### ROOT主目录
bug.html 忘了干嘛的了，删掉
Gemfile Gemfile.lock openserver.sh 本地调试的，没用删掉
CNAME 改成自定义域名。没有的话删掉
favicon.ico 网站图标（必须是ICO格式。。我用的原博主的。。懒得改）
robots.txt 爬虫设置（一般没啥用）
school_ftp.md 给学校里的一个临时FTP，删掉
## 修改信息
根目录的_config.yml和_data文件夹。改一下 | 10.855263 | 58 | 0.723636 | yue_Hant | 0.774025 |
58b0bbab1db702e891560e3dcf958db6f387fcc6 | 2,087 | md | Markdown | content.md | Gaurav2Github/ansible-presentation | dcb4348db77e43fe86603a764a14b56fd26a2499 | [
"MIT"
] | null | null | null | content.md | Gaurav2Github/ansible-presentation | dcb4348db77e43fe86603a764a14b56fd26a2499 | [
"MIT"
] | null | null | null | content.md | Gaurav2Github/ansible-presentation | dcb4348db77e43fe86603a764a14b56fd26a2499 | [
"MIT"
] | null | null | null | # Datacom <!-- .element: class="datacom-logo" -->
### Your presentation title
Presented by <!-- .element: class="small-text" --> [Name](Link) <!-- .element: class="small-text" -->
## Title goes here <!-- .slide: class="title-slide" --> <!-- .element: class="orange" -->
## Large title
Note:
This will only display in the notes window.
## Title <!-- .slide: class="image-slide" -->
### List title
* List item  <!-- .element: class="img-right" -->
* List item
* List item
### Fragmented list
* List item <!-- .element: class="fragment" -->
* List item <!-- .element: class="fragment" -->
* List item <!-- .element: class="fragment" -->
 <!-- .element: class="img-centered" -->
## Title (press down to see vertical slides) <!-- .slide: class="title-slide banner-3" --> <!-- .element: class="yellow" -->
### Paragraph
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Mauris at scelerisque eros. Pellentesque habitant morbi tristique senectus et netus et malesuada fames ac turpis egestas. Aliquam placerat posuere nibh vel dapibus.
### Blockquote
> Lorem ipsum dolor sit amet, consectetur adipiscing elit. Mauris at scelerisque eros. Pellentesque habitant morbi tristique senectus et netus et malesuada fames ac turpis egestas. Aliquam placerat posuere nibh vel dapibus.
### Nested lists
+ One
+ Two
+ Three
- Nested One
- Nested Two
### Title
Some text
function linkify( selector ) {
if( supports3DTransforms ) {
var nodes = document.querySelectorAll( selector );
for( var i = 0, len = nodes.length; i < len; i++ ) {
var node = nodes[i];
if( !node.className ) {
node.className += ' roll';
}
}
}
}
### Image backgrounds <!-- .slide: data-background="img/800x600.gif" -->
 <!-- .slide: class="image-slide" --> <!-- .element: class="cat-slogan-image" -->
| 25.144578 | 223 | 0.66459 | eng_Latn | 0.271472 |
58b1379c95b423e01cc6910d174bbe71f4b876ad | 92 | md | Markdown | mod-15-react-section-10-react-under-the-hood/reconciliation-in-react.md | meg-gutshall/flatiron-curriculum-notes | 619580d5d9a62a5f28a1851ed8c765e5444e0245 | [
"MIT"
] | 1 | 2021-10-31T22:03:14.000Z | 2021-10-31T22:03:14.000Z | mod-15-react-section-10-react-under-the-hood/reconciliation-in-react.md | meg-gutshall/flatiron-curriculum-notes | 619580d5d9a62a5f28a1851ed8c765e5444e0245 | [
"MIT"
] | null | null | null | mod-15-react-section-10-react-under-the-hood/reconciliation-in-react.md | meg-gutshall/flatiron-curriculum-notes | 619580d5d9a62a5f28a1851ed8c765e5444e0245 | [
"MIT"
] | null | null | null | ---
description: 'Version 8: Module 15: Section 10: Lesson'
---
# Reconciliation in React
| 13.142857 | 55 | 0.684783 | eng_Latn | 0.471058 |
58b15fa4e3f966765f11c8d13dc1aa7e9ab1e034 | 237 | md | Markdown | content/posts/memes/20171225-two-states/index.md | kevinkiklee/kevinkiklee.github.io | 66ef60d9ac57dd2635c7e613d2a0e07b06266407 | [
"MIT"
] | 1 | 2020-07-16T01:05:57.000Z | 2020-07-16T01:05:57.000Z | content/posts/memes/20171225-two-states/index.md | kevinkiklee/kevinkiklee.github.io | 66ef60d9ac57dd2635c7e613d2a0e07b06266407 | [
"MIT"
] | null | null | null | content/posts/memes/20171225-two-states/index.md | kevinkiklee/kevinkiklee.github.io | 66ef60d9ac57dd2635c7e613d2a0e07b06266407 | [
"MIT"
] | null | null | null | ---
title: "Two states of every programmer"
cover: "/images/two-states.jpg"
date: "2017-12-26"
time: "19:47"
category: "memes"
tags:
- meme
- god
---
Just kidding, god is dead.
| 15.8 | 49 | 0.658228 | eng_Latn | 0.609955 |
58b2586a1294d6876b4957ba3f99dbacd418fe5a | 24,280 | md | Markdown | _posts/2021-02-14-zerotier-openvpn-nat-part-3.md | jameshi16/personal-website | c6a0fe469a5cb036730325dc0697cab547f30cf9 | [
"MIT"
] | null | null | null | _posts/2021-02-14-zerotier-openvpn-nat-part-3.md | jameshi16/personal-website | c6a0fe469a5cb036730325dc0697cab547f30cf9 | [
"MIT"
] | null | null | null | _posts/2021-02-14-zerotier-openvpn-nat-part-3.md | jameshi16/personal-website | c6a0fe469a5cb036730325dc0697cab547f30cf9 | [
"MIT"
] | 1 | 2020-07-09T16:47:33.000Z | 2020-07-09T16:47:33.000Z | ---
title: "ZeroTier OpenVPN NAT - Part 3"
date: 2021-02-14 21:28 +08:00
categories: [openvpn, zerotier, decentralized]
tags: [openvpn, zerotier, decentralized]
published: true
---
<img src="/images/20210214_4.png" style="max-width: 400px; width: 100%; margin: 0 auto; display: block;" alt="Architecture"/>
<p class="text-center text-gray lh-condensed-ultra f6">Duo Architecture</p>
[\<\< Take me back to Part 1](/2021/02/14/zerotier-openvpn-nat-part-1#bookmark)
Solution Duo was designed with the following goals:
- Guaranteed connectivity
- High Federation
# Step 0: Pre-requisites
You will need an [Oracle Cloud](https://cloud.oracle.com) account. An account will remain always-free until it is explicitly upgraded; so don't worry too much about being charged.
# Step 1: Creating cloud resources (Skippable)
It is not an explicit requirement to create any of the resources here; however, it is good practice (at least in AWS) to house all the resources in their proper groups.
For this step we will be creating/modifying the following things:
- Virtual Cloud Network
- Subnet
- Internet Gateway
- Network Security Group
- Security List
- Route Table
Navigate to the [Virtual Cloud Networks](https://cloud.oracle.com/networking/vcns) page, and click on "Create VCN".
<img src="/images/20210214_8.png" style="max-width: 600px; width: 100%; margin: 0 auto; display: block;" alt="Creating VCN"/>
<p class="text-center text-gray lh-condensed-ultra f6">Creating VCN | Source: Me</p>
Name the VCN whatever you like; it does not matter. After you are done, click on "Create VCN".
Oracle Cloud will redirect you to the page detailing the VCN. From the sidebar, click on "Internet Gateways":
<img src="/images/20210214_14.png" style="max-width: 400px; width: 100%; margin: 0 auto; display: block;" alt="Navigate to Route Tables"/>
<p class="text-center text-gray lh-condensed-ultra f6">Navigate to Route Tables | Source: Me</p>
Create an Internet Gateway, and name it anything you want.
<img src="/images/20210214_15.png" style="max-width: 700px; width: 100%; margin: 0 auto; display: block;" alt="Create an Internet Gateway"/>
<p class="text-center text-gray lh-condensed-ultra f6">Name your internet gateway | Source: Me</p>
From the sidebar, click on "Route Tables":
<img src="/images/20210214_10.png" style="max-width: 400px; width: 100%; margin: 0 auto; display: block;" alt="Navigate to Route Tables"/>
<p class="text-center text-gray lh-condensed-ultra f6">Navigate to Route Tables | Source: Me</p>
Click on "Create Route Table":
<img src="/images/20210214_11.png" style="max-width: 400px; width: 100%; margin: 0 auto; display: block;" alt="Create Route Table"/>
<p class="text-center text-gray lh-condensed-ultra f6">Create a Route Table | Source: Me</p>
Name the Route Table anything you want, and then click on "Create":
<img src="/images/20210214_12.png" style="max-width: 700px; width: 100%; margin: 0 auto; display: block;" alt="Naming the Route Table"/>
<p class="text-center text-gray lh-condensed-ultra f6">Name the Route Table | Source: Me</p>
After the page redirects, click into the Route Table you just created:
<img src="/images/20210214_13.png" style="max-width: 700px; width: 100%; margin: 0 auto; display: block;" alt="Click into the Route Table"/>
<p class="text-center text-gray lh-condensed-ultra f6">Click the Route Table | Source: Me</p>
Then, click on "Add Route Rules":
<img src="/images/20210214_16.png" style="max-width: 700px; width: 100%; margin: 0 auto; display: block;" alt="Adding Route Rules"/>
<p class="text-center text-gray lh-condensed-ultra f6">Add Route Rules button | Source: Me</p>
In the dialog that appears, choose "Internet Gateway" as the Target Type, `0.0.0.0/0` as the Destination CIDR Block, and set `Target Internet Gateway` to the Internet Gateway you just created. After that, click on "Add Route Rules".
<img src="/images/20210214_17.png" style="max-width: 700px; width: 100%; margin: 0 auto; display: block;" alt="Configuring Route Table"/>
<p class="text-center text-gray lh-condensed-ultra f6">Configure the Route Table | Source: Me</p>
Navigate back to the VCN page by clicking on the VCN name on the breadcrumbs bar:
<img src="/images/20210214_18.png" style="max-width: 400px; width: 100%; margin: 0 auto; display: block;" alt="Navigate back to the VCN page"/>
<p class="text-center text-gray lh-condensed-ultra f6">Navigate back to the VCN page | Source: Me</p>
From here, click on "Create Subnet":
<img src="/images/20210214_9.png" style="max-width: 400px; width: 100%; margin: 0 auto; display: block;" alt="Click on Create Subnet"/>
<p class="text-center text-gray lh-condensed-ultra f6">Creating Subnet | Source: Me</p>
Then, configure the subnet:
<img src="/images/20210214_19.png" style="max-width: 700px; width: 100%; margin: 0 auto; display: block;" alt="Click on Create Subnet"/>
<p class="text-center text-gray lh-condensed-ultra f6">Configuring the Subnet | Source: Me</p>
After being redirected back to the subnet page, click on "Security List" on the sidebar. You do not need to wait for the Subnet to finish provisioning:
<img src="/images/20210214_20.png" style="max-width: 400px; width: 100%; margin: 0 auto; display: block;" alt="Navigate to Security List"/>
<p class="text-center text-gray lh-condensed-ultra f6">Navigate to Security List | Source: Me</p>
Click on create "Create Security List":
<img src="/images/20210214_21.png" style="max-width: 400px; width: 100%; margin: 0 auto; display: block;" alt="Create Security List"/>
<p class="text-center text-gray lh-condensed-ultra f6">Create a security list | Source: Me</p>
Fill in the details for the Security List. Take care to include rules for port 22 and port 443 (OpenVPN TCP) for TCP, and port 1194 (OpenVPN UDP) for UDP; you can click on "Add Ingress Rule" or "Add Egress Rule" to create new rules for the Security List accordingly. Keep the "Stateless" box unchecked, so that ZeroTier can smoothly perform UDP hole punching.
<img src="/images/20210214_22.png" style="max-width: 900px; width: 100%; margin: 0 auto; display: block;" alt="Configure Security List"/>
<p class="text-center text-gray lh-condensed-ultra f6">Configure the security list | Source: Me</p>
After being redirected back to the Security List page, click on "Network Security Groups" on the sidebar.
<img src="/images/20210214_23.png" style="max-width: 400px; width: 100%; margin: 0 auto; display: block;" alt="Navigate to Network Security Groups"/>
<p class="text-center text-gray lh-condensed-ultra f6">Navigate to Network Security Groups | Source: Me</p>
Click on "Create Network Security Group".
<img src="/images/20210214_24.png" style="max-width: 400px; width: 100%; margin: 0 auto; display: block;" alt="Create Network Security Group"/>
<p class="text-center text-gray lh-condensed-ultra f6">Create Network Security Group | Source: Me</p>
Name the Network Security Group whatever you want, then click Next:
<img src="/images/20210214_25.png" style="max-width: 400px; width: 100%; margin: 0 auto; display: block;" alt="Name the Network Security Group"/>
<p class="text-center text-gray lh-condensed-ultra f6">Name the Network Security Group | Source: Me</p>
Add the same rules as you did for the Security List:
<img src="/images/20210214_26.png" style="max-width: 800px; width: 100%; margin: 0 auto; display: block;" alt="Configure the Network Security Group"/>
<p class="text-center text-gray lh-condensed-ultra f6">Configure the Network Security Group | Source: Me</p>
Go back to the subnet page:
<img src="/images/20210214_18.png" style="max-width: 400px; width: 100%; margin: 0 auto; display: block;" alt="Navigate back to the VCN page"/>
<p class="text-center text-gray lh-condensed-ultra f6">Navigate back to the VCN page | Source: Me</p>
<img src="/images/20210214_27.png" style="max-width: 400px; width: 100%; margin: 0 auto; display: block;" alt="Navigate back to the subnet page"/>
<p class="text-center text-gray lh-condensed-ultra f6">Navigate to the subnet page | Source: Me</p>
Click into the public subnet created earlier:
<img src="/images/20210214_28.png" style="max-width: 400px; width: 100%; margin: 0 auto; display: block;" alt="Click into the subnet created earlier"/>
<p class="text-center text-gray lh-condensed-ultra f6">Click into the subnet you created earlier | Source: Me</p>
Click on add security list:
<img src="/images/20210214_30.png" style="max-width: 400px; width: 100%; margin: 0 auto; display: block;" alt="Click on Add Security List"/>
<p class="text-center text-gray lh-condensed-ultra f6">Click on Add Security List | Source: Me</p>
Add the security list created earlier:
<img src="/images/20210214_29.png" style="max-width: 400px; width: 100%; margin: 0 auto; display: block;" alt="Add the security list created earlier"/>
<p class="text-center text-gray lh-condensed-ultra f6">Add the security list created earlier | Source: Me</p>
Delete the default security list from the subnet:
<img src="/images/20210214_31.png" style="max-width: 600px; width: 100%; margin: 0 auto; display: block;" alt="Delete default security list"/>
<p class="text-center text-gray lh-condensed-ultra f6">Delete the default security list | Source: Me</p>
# Step 2: Create a VM
Go to the [instances page](https://cloud.oracle.com/compute/instances), and click on "Create Instance":
<img src="/images/20210214_32.png" style="max-width: 400px; width: 100%; margin: 0 auto; display: block;" alt="Create an instance"/>
<p class="text-center text-gray lh-condensed-ultra f6">Create an instance | Source: Me</p>
You can leave the instance name as it's default, or name it whatever you like. Click on the box containing the Container Image, and choose the "Canonical Ubuntu 20.04 Minimal" image. If you went through all the steps in Step 1, then under "Configure networking", check "Use network security group to control traffic"; select the VCN, Subnet and Network Security Group created in Step 1. Under "Public IP Address", select "Assign a public IPv4 address".
Remember to click on "Save Private Key" so that you can connect to the instance later on. Then, click the "Create" button.
<img src="/images/20210214_33.png" style="max-width: 800px; width: 100%; margin: 0 auto; display: block;" alt="Create a VM instance"/>
<p class="text-center text-gray lh-condensed-ultra f6">Create a VM instance | Source: Me</p>
## Optional
If you want some redundancy that a Cloud VM instance can have, you can:
1. Create and attach a block volume (free tier: 100GB); put all your configuration files there.
- You may need to stop the `zerotier-one` service to `rm -rf /var/lib/zerotier-one`, so that you can run `ln -s /var/lib/zerotier-one /mnt/blockvolume/zerotier` to more effectively transfer ZeroTier identities from one instance to another.
2. Create an image once you are done setting up the instance; then, create an instance pool that uses the created image.
3. Reserve a public IP so that you can reattach it to a new instance.
4. Use Dynamic DNS for your instance, _or_ use Oracle Cloud's load balancer; take note that Oracle Cloud's load balancer is a paid service.
This guide doesn't cover these, because I am too lazy to explain them, out of scope, and I'm running out of time :sweat_smile:, but they are simple enough that an afternoon should suffice to research how to accomplish them.
# Step 3: Install packages on VM
For this step, we must install a text editor (vim, nano, etc), ZeroTier, easy-rsa and OpenVPN. Additionally it is recommended that you install UFW, although Step 1 should have amortized your instance enough.
SSH to the instance with the downloaded key, then run the following command:
```bash
curl -s https://install.zerotier.com | sudo bash
sudo apt-get -y install openvpn vim easy-rsa ufw
sudo systemctl enable zerotier-one && sudo systemctl start zerotier-one
sudo zerotier-cli join <network ID>
```
Ensure on ZeroTier Central or equivalent that your VM instance has joined the network. Do note down the ZeroTier tunnel device name:
```bash
ip link | grep "zt"
```
Before you forget, allow SSH connections and enable UFW:
```bash
sudo ufw allow 22/tcp
sudo ufw enable
```
Oracle Cloud adds their own rules to `iptables`, which causes some routing problems later on down the road. If you plan on hosting other services, do take note of Oracle Cloud's rules (which by default only allows connections from TCP port 22):
```bash
sudo iptables -vL
```
This guide will add entries into `iptables` such that they are not blocked by Oracle Cloud's default rules; you can refer to them to add rules for your own services.
# <span id="step4">Step 4: Create & Configure OpenVPN server</span>
This step is adopted from [DigitalOcean's guide on how to setup an OpenVPN server](https://www.digitalocean.com/community/tutorials/how-to-set-up-an-openvpn-server-on-ubuntu-16-04); that guide uses Ubuntu 16.04 with easy-rsa 2, while this guide uses Ubuntu 20.04 with easy-rsa 3. There are also easy setup scripts online, although you should exercise caution when running scripts downloaded from the internet.
Before we can even configure the OpenVPN server, we must become a Certificate Authority and issue certificates for both the server and client. This allows clients authenticate the server, and vice-versa.
Find a suitable working folder, and create a folder to store CA related files:
```bash
make-cadir openvpn-ca
```
Then, append the following lines into the `openvpn-ca/vars` file:
```ini
export KEY_COUNTRY="US"
export KEY_EMAIL="[email protected]"
export KEY_CITY="Somewhere"
export KEY_PROVINCE="There"
export KEY_ORG="CodingIndex"
export KEY_OU="ADMIN"
export KEY_NAME="server"
```
Change the values of all the variables to whatever you want; just try not to change `KEY_NAME`, unless you have to - it is easier to follow the guide if you name your key "server".
Next, you will want to change your working directory to `openvpn-ca`, so that you can run the `easyrsa` executable with the following subcommands:
```bash
cd openvpn-ca
./easyrsa init-pki
./easyrsa build-ca
./easyrsa build-server-full server nopass
./easyrsa gen-dh
mkdir keys && openvpn --genkey --secret keys/ta.key
```
Easy-rsa may prompt you for additional information.
> Run `easyrsa --pki-dir=<insert directory here>` to change where the PKIs are stored, which by default is `${PWD}/pki`.
You _should_ then create as many client certificates as the devices you plan to connect to this server. But it is not strictly necessary, as one certificate can be used for multiple devices. Here is how to create a single client certificate:
```bash
./easyrsa build-client-full client1 nopass
```
Copy the appropriate certificates to the `/etc/openvpn` folder:
```bash
sudo cp keys/ta.key ${PWD}/pki/private/server.key ${PWD}/pki/issued/server.crt ${PWD}/pki/dh.pem /etc/openvpn
```
Next, download the sample server configuration file from the OpenVPN's Git repository (if you are on an Ubuntu minimal image, you should not have this on your system because it has been minimized):
```bash
cd /etc/openvpn
sudo wget https://raw.githubusercontent.com/OpenVPN/openvpn/master/sample/sample-config-files/server.conf
```
Edit the server configuration file; for this part, we will configure a TCP OpenVPN server listening on port 443, but the method to configure are the same for the UDP OpenVPN server listening on port 1194 if you decide to host two OpenVPN servers. Modify the following lines by searching for them in your favourite editor:
`/etc/openvpn/server.conf`:
```conf
port 443
proto tcp
user nobody
group nogroup
cipher AES-256-CBC
auth SHA256
push "redirect-gateway def1 bypass-dhcp"
push "dhcp-option DNS 208.67.222.222"
push "dhcp-option DNS 208.67.220.220"
dh dh.pem
# these line does not exist by default
auth SHA256
```
Try starting the OpenVPN server:
```bash
sudo systemctl start openvpn@server
sudo systemctl status openvpn@server
```
If the server successfully initializes, then enable the server, and note down the tunnel device used for the connection:
```bash
sudo systemctl enable openvpn@server
ip link | grep "tun"
```
More than likely, the result should show `tun0`.
Download your VPN provider's OpenVPN configuration file, and copy them into `/etc/openvpn`. Afterwards, create a service file in `/etc/systemd/system`:
`/etc/systemd/system/vpnprovider.service`:
```ini
[Unit]
Description=Binds OpenVPN server tunnel to OpenVPN client tunnel
[Service]
Type=simple
ExecStart=openvpn --cd /etc/openvpn --config <client config file here> --route-noexec --route-up /etc/openvpn/client-up.sh --route-pre-down /etc/openvpn/client-down.sh
[Install]
WantedBy=multi-user.target
```
Then, create the files `/etc/openvpn/client-up.sh` and `/etc/openvpn/client-down.sh` to manually route:
- All connections to 0.0.0.0/0 to the VPN provider;
- All connections to ZeroTier local address (e.g. 172.25.0.0/16) to ZeroTier.
`/etc/openvpn/client-up.sh`:
```bash
#!/bin/bash
SRC_DEVICE="tun0"
ZT_DEVICE="ztly52mmwy"
ZT_CIDR="172.25.0.0/16"
set -e
sysctl -w net.ipv4.ip_forward=1
touch /etc/iproute2/rt_tables.d/ovpn2ovpn.conf
echo "42070 ovpn2ovpn" > /etc/iproute2/rt_tables.d/ovpn2ovpn.conf
ip rule add from 10.8.0.0/24 table ovpn2ovpn
ip route add default via ${route_vpn_gateway} dev ${dev} table ovpn2ovpn
ip route add ${ZT_CIDR} dev ${ZT_DEVICE} table ovpn2ovpn
iptables -I INPUT -i ${SRC_DEVICE} -d 0.0.0.0/0 -j ACCEPT
iptables -I INPUT -i ${ZT_DEVICE} -d ${ZT_CIDR} -j ACCEPT
iptables -I FORWARD -i ${SRC_DEVICE} -o ${dev} -d 0.0.0.0/0 -j ACCEPT
iptables -I FORWARD -i ${SRC_DEVICE} -o ${ZT_DEVICE} -d ${ZT_CIDR} -j ACCEPT
iptables -t nat -I POSTROUTING -o ${dev} -d 0.0.0.0/0 -j MASQUERADE
iptables -t nat -I POSTROUTING -o ${ZT_DEVICE} -d ${ZT_CIDR} -j MASQUERADE
```
`/etc/openvpn/client-down.sh`:
```bash
#!/bin/bash
SRC_DEVICE="tun0"
ZT_DEVICE="ztly52mmwy"
ZT_CIDR="172.25.0.0/16"
ip rule delete from 10.8.0.0/24 table ovpn2ovpn
ip route delete default via ${route_vpn_gateway} dev ${dev} table ovpn2ovpn
ip route delete ${ZT_CIDR} dev ${ZT_DEVICE} table ovpn2ovpn
rm -f /etc/iproute2/rt_tables.d/ovpn2ovpn.conf
iptables -D INPUT -i ${SRC_DEVICE} -d 0.0.0.0/0 -j ACCEPT
iptables -D INPUT -i ${ZT_DEVICE} -d ${ZT_CIDR} -j ACCEPT
iptables -D FORWARD -i ${SRC_DEVICE} -o ${dev} -d 0.0.0.0/0 -j ACCEPT
iptables -D FORWARD -i ${SRC_DEVICE} -o ${ZT_DEVICE} -d ${ZT_CIDR} -j ACCEPT
iptables -t nat -D POSTROUTING -o ${dev} -d 0.0.0.0/0 -j MASQUERADE
iptables -t nat -D POSTROUTING -o ${ZT_DEVICE} -d ${ZT_CIDR} -j MASQUERADE
```
`10.8.0.0/24` is the CIDR used by default for `/etc/openvpn/server.conf`. Remember to flag the scripts as executable:
```bash
sudo chmod +x /etc/openvpn/client-up.sh /etc/openvpn/client-down.sh
```
Start the custom service:
```bash
sudo systemctl start vpnprovider
sudo systemctl status vpnprovider
```
If successfully started, enable the service:
```bash
sudo systemctl enable vpnprovider
```
Now that all the services are in place, allow them through the UFW:
```bash
ufw allow 9993/udp # for ZeroTier
ufw allow 443/tcp
ufw allow 1194/udp
```
In theory anyway. On Oracle Cloud VM instances, UFW rules are placed **below** a REJECT rule on the IPTables, like this:
```
Chain INPUT (policy DROP 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
4 1344 ACCEPT all -- tun0 any anywhere anywhere
848K 472M ACCEPT all -- any any anywhere anywhere state RELATED,ESTABLISHED
0 0 ACCEPT icmp -- any any anywhere anywhere
688 59382 ACCEPT all -- lo any anywhere anywhere
0 0 ACCEPT udp -- any any anywhere anywhere udp spt:ntp
1294 75128 ACCEPT tcp -- any any anywhere anywhere state NEW tcp dpt:ssh
10739 5199K REJECT all -- any any anywhere anywhere reject-with icmp-host-prohibited
0 0 ufw-before-logging-input all -- any any anywhere anywhere
0 0 ufw-before-input all -- any any anywhere anywhere
0 0 ufw-after-input all -- any any anywhere anywhere
0 0 ufw-after-logging-input all -- any any anywhere anywhere
0 0 ufw-reject-input all -- any any anywhere anywhere
0 0 ufw-track-input all -- any any anywhere anywhere
```
In other words, UFW becomes absolutely useless. As an interesting side note, trying to connect to a port other than TCP port 22 will yield 'Destination Host Unreachable' error messages thanks to IPTable rejecting connections with `icmp-host-prohibited`. There are two ways to circumvent this:
1. Delete the REJECT rule;
2. Add my own IPTable rules.
For this guide, I decided to just _add_ my own iptable rules, since I don't know the implications of deleting the REJECT rule:
`/etc/iptables/rules.v4`:
```bash
*filter
:INPUT ACCEPT [0:0]
...
-A INPUT -p tcp --dport 443 -j ACCEPT
-A INPUT -p udp --dport 1194 -j ACCEPT
-A FORWARD -s tun0 -j ACCEPT
-A FORWARD -s tun1 -j ACCEPT
...
```
# <span id="step5">Step 5: Create Client Configurations</span>
Now, we generate the `.ovpn` files used by the clients. For convenience (and to rip off [DigitalOcean's guide](https://www.digitalocean.com/community/tutorials/how-to-set-up-an-openvpn-server-on-ubuntu-16-04)), we'll combine the CA certificate, Client certificate and Client's key into the `.ovpn` file.
Firstly, we generate a working directory to store the files needed for the `.ovpn` file:
```bash
mkdir -p ${PWD}/client/files
```
Then, we download the example client configuration from the official Git repository:
```bash
wget -O ${PWD}/client/files/base.conf https://raw.githubusercontent.com/OpenVPN/openvpn/master/sample/sample-config-files/client.conf
```
Modify `client.conf` to match the server configuration (assuming TCP on 443):
`${PWD}/client/client.conf`:
```conf
remote x.x.x.x 443
proto tcp
user nobody
group nogroup
cipher AES-256-CBC
auth SHA256
# comment out these lines
;ca ca.crt
;cert client.crt
;key client.key
```
Replace `x.x.x.x` with the IP assigned to your Oracle VM instance.
The [DigitalOcean guide](https://www.digitalocean.com/community/tutorials/how-to-set-up-an-openvpn-server-on-ubuntu-16-04) uses a script to generate the `.ovpn` file, so that is what we will be doing too. It essentially concatenates all the necessary files together and spits out an `.ovpn` file.
`${PWD}/client/make_config.sh`:
```bash
#!/bin/bash
# First argument: Client identifier
PKI_DIR="../pki"
CA_DIR="../openvpn-ca"
OUTPUT_DIR="./files"
BASE_CONFIG="./files/base.conf"
cat ${BASE_CONFIG} \
<(echo -e '<ca>') \
${PKI_DIR}/ca.crt \
<(echo -e '</ca>\n<cert>') \
${PKI_DIR}/issued/${1}.crt \
<(echo -e '</cert>\n<key>') \
${PKI_DIR}/private/${1}.key \
<(echo -e '</key>\n<tls-auth>') \
${CA_DIR}/keys/ta.key \
<(echo -e '</tls-auth>') \
> ${OUTPUT_DIR}/${1}.ovpn
```
Adjust the directories to their absolute paths just to be sure. Once you are confident that the paths are accurate, give the script the executable go-ahead, and run the script with the parameter of the client name (should be `client1`, as generated with `./easyrsa build-client-full client nopass`):
```bash
cd <path to client directory>
chmod +x make_config.sh
./make_config.sh client1
```
The `.ovpn` should be generated in the `./files` directory. This file can then be transferred to another device, like your Android device or ISP-controlled router. Give it a spin, and ensure everything is in working order by:
- Checking IP address with [ifconfig.so](https://ifconfig.so), or VPN provider internet checker;
- Checking ZeroTier connectivity by pinging peers in the same network.
# Conclusion
You have successfully set up Solution Duo. [Click here](/2021/02/14/zerotier-openvpn-nat-part-1#bookmark) to go back to Part 1; otherwise, if you are satisfied with your setup, then we're done here.
Happy Coding
CodingIndex
| 47.329435 | 452 | 0.726977 | eng_Latn | 0.893009 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.