hexsha stringlengths 40 40 | size int64 5 1.04M | ext stringclasses 6 values | lang stringclasses 1 value | max_stars_repo_path stringlengths 3 344 | max_stars_repo_name stringlengths 5 125 | max_stars_repo_head_hexsha stringlengths 40 78 | max_stars_repo_licenses listlengths 1 11 | max_stars_count int64 1 368k ⌀ | max_stars_repo_stars_event_min_datetime stringlengths 24 24 ⌀ | max_stars_repo_stars_event_max_datetime stringlengths 24 24 ⌀ | max_issues_repo_path stringlengths 3 344 | max_issues_repo_name stringlengths 5 125 | max_issues_repo_head_hexsha stringlengths 40 78 | max_issues_repo_licenses listlengths 1 11 | max_issues_count int64 1 116k ⌀ | max_issues_repo_issues_event_min_datetime stringlengths 24 24 ⌀ | max_issues_repo_issues_event_max_datetime stringlengths 24 24 ⌀ | max_forks_repo_path stringlengths 3 344 | max_forks_repo_name stringlengths 5 125 | max_forks_repo_head_hexsha stringlengths 40 78 | max_forks_repo_licenses listlengths 1 11 | max_forks_count int64 1 105k ⌀ | max_forks_repo_forks_event_min_datetime stringlengths 24 24 ⌀ | max_forks_repo_forks_event_max_datetime stringlengths 24 24 ⌀ | content stringlengths 5 1.04M | avg_line_length float64 1.14 851k | max_line_length int64 1 1.03M | alphanum_fraction float64 0 1 | lid stringclasses 191 values | lid_prob float64 0.01 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
6f6d1c859939a79de76c9061ca19b9c6fe43776e | 1,628 | md | Markdown | content/08.hymns-for-the-poor-of-the-flock/04.201-300/08.271-280/02.How-bright-these-glorious-spirits-shine/docs.md | GospelSounders/adventhymnals | d2108ab49d735b373c59901e5296c8819a1ad3f2 | [
"Apache-2.0"
] | null | null | null | content/08.hymns-for-the-poor-of-the-flock/04.201-300/08.271-280/02.How-bright-these-glorious-spirits-shine/docs.md | GospelSounders/adventhymnals | d2108ab49d735b373c59901e5296c8819a1ad3f2 | [
"Apache-2.0"
] | 1 | 2021-05-10T23:24:05.000Z | 2021-05-10T23:24:05.000Z | content/08.hymns-for-the-poor-of-the-flock/04.201-300/08.271-280/02.How-bright-these-glorious-spirits-shine/docs.md | GospelSounders/adventhymnals | d2108ab49d735b373c59901e5296c8819a1ad3f2 | [
"Apache-2.0"
] | null | null | null | ---
title: |
272 How bright these glorious spirits shine. - Hymns for the Poor of the Flock
metadata:
description: |
Hymns for the Poor of the Flock 272. How bright these glorious spirits shine.. How bright these glorious spirits shine, Whence all their bright array! How came they to the happy seats Of everlasting day?272
keywords: |
Hymns for the Poor of the Flock, adventhymnals, advent hymnals, How bright these glorious spirits shine., How bright these glorious spirits shine, ,
author: Brian Onang'o
---
#### Advent Hymnals
## 272. How bright these glorious spirits shine.
#### Hymns for the Poor of the Flock
```txt
1. How bright these glorious spirits shine,
Whence all their bright array!
How came they to the happy seats
Of everlasting day?272
2. L o! these are they from suff’rings great,
Who came to realms of light,
And in the blood of Christ have wash’d
Their robes, which shine so bright.
3. Now with triumphant palms they stand
Before the throne on high;
And serve the Lord they love, amidst
The glories of the sky.
4. His presence fills each heart with joy,
And gives them pow’r to sing;
While day, and night, the sacred courts
With glad hosannas ring.
5. Hunger and thirst are felt no more,
Nor sun with scorching ray;
God is their sun, whose cheering beams
Give them eternal day.
6. The Lamb, Who dwells amid the throne
Shall o’er them still preside,
Feed them with nourishment divine,
And all their footsteps guide.
7. Midst pastures green He’ll lead His flock,
Where living streams appear,
And God the Lord, from ev’ry eye
Shall wipe off ev’ry tear.
``` | 31.921569 | 217 | 0.742629 | eng_Latn | 0.999164 |
6f6d2299142ae3c7165e8c18e50214f11385345b | 32,849 | md | Markdown | content/2019-02-11-germany.md | matome01/matome01 | 8eb2961c22fe83c440ccada4994d43f921924878 | [
"MIT"
] | null | null | null | content/2019-02-11-germany.md | matome01/matome01 | 8eb2961c22fe83c440ccada4994d43f921924878 | [
"MIT"
] | null | null | null | content/2019-02-11-germany.md | matome01/matome01 | 8eb2961c22fe83c440ccada4994d43f921924878 | [
"MIT"
] | null | null | null | ---
title: 【국제】독일인의 42% 「중국은 미국보다 신뢰할 수 있는 파트너」라고 응답
date: 2019-02-11T15:23:00.400Z
cover: 20190211/2019021101.jpg
slug: 20190211-germany
category: 국제
tags:
- 독일
- 뉴스
backgroundPosition:
---
<div><p class="source">출처: <a href="http://ai.2ch.sc/test/read.cgi/newsplus/1549851214/" target="_blank" rel="noopener nofollow noreferrer">http://ai.2ch.sc/test/read.cgi/newsplus/1549851214/</a></p><br><label for="twolang" style="font-weight: 550;">일본어 같이보기</label><input type="checkbox" id="twolang"><br><br><div class="commentbox0"><div class="content1"><div class="id">1. ID: <span class="op">eAo9qYil9.net</span> <span title="2019/02/11(月) 11:13:34.07">2019/02/11 11:13</span></div><div style="padding-top: 10px;"><p class="content">2019년 2월 11일, 중국 환구시보(전자판)는, 독일인의 절반 가까이가 「중국은 미국보다 신뢰할 수 있는 파트너」로 생각하고 있는 것으로 최근 여론조사에서 드러났다고 보도했다.
독일의 방송국 도이체 벨레(전자판)의 9일자 보도로서 전한 것으로, 「전통적으로 미국편」인 독일의 비영리 단체 Atlantik-Brucke와 연구기관 Civey가 공동으로 실시한 조사에 의하면, 응답자 5000명 중, 57.6%가 「독일은 미국과 좀 더 거리를 둬야 한다」라고 한 것에 대해, 「미국에 더 가까워져야 한다」라고 한 것은 13%에 머물러, 응답자의 85%는 현재의 미독 관계를 부정적으로 평가해, 42.3%가 「중국은 미국보다 신뢰 할 수 있는 파트너」라고 응답했다고 한다.
<a class="vglnk" href="https://www.recordchina.co.jp/b686738-s0-c30-d0054.html" rel="nofollow"><span>https</span><span>://</span><span>www</span><span>.</span><span>recordchina</span><span>.</span><span>co</span><span>.</span><span>jp</span><span>/</span><span>b686738</span><span>-</span><span>s0</span><span>-</span><span>c30</span><span>-</span><span>d0054</span><span>.</span><span>html</span></a><br><span class="jp">2019年2月11日、中国紙・環球時報（電子版）は、ドイツ人の半数近くが「中国は米国より信頼できるパートナー」と考えていることが最新の世論調査で明らかになったと報じた。
ドイツの放送局ドイチェ・ヴェレ（電子版）の9日付報道として伝えたもので、「伝統的に米国寄り」のドイツの非営利団体Atlantik-Bruckeと研究機関Civeyが共同で行った調査によると、回答者5000人のうち、57．6％が「ドイツは米国ともっと距離を取るべき」としたのに対し、「米国にもっと近づくべき」としたのは13％にとどまり、回答者の85％は現在の米独関係を否定的に評価し、42．3％が「中国は米国より信頼できるパートナー」と回答したという。
<a class="vglnk" href="https://www.recordchina.co.jp/b686738-s0-c30-d0054.html" rel="nofollow"><span>https</span><span>://</span><span>www</span><span>.</span><span>recordchina</span><span>.</span><span>co</span><span>.</span><span>jp</span><span>/</span><span>b686738</span><span>-</span><span>s0</span><span>-</span><span>c30</span><span>-</span><span>d0054</span><span>.</span><span>html</span></a></span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">4. ID: <span>0QL0cKjj0.net</span> <span title="2019/02/11(月) 11:14:20.76">2019/02/11 11:14</span></div><div style="padding-top: 10px;"><p class="content">트럼프가 어쨌든 너무 심하다<br><span class="jp">トランプがとにかくひどすぎる</span> </p></div><div class="content2"><div class="id">36. ID: <span>V/DOFVmD0.net</span> <span title="2019/02/11(月) 11:18:30.43">2019/02/11 11:18</span></div><div style="padding-top: 10px;"><p class="content">중국의 화웨이는 강대하다
삼성을 지켜주는건 트럼프뿐인데<br><span class="jp">中国のファーウエイは強大だ
サムスンをまもってくれるのはトランプだけなのに</span> </p></div></div><div class="content2"><div class="id">91. ID: <span>yya6aCNo0.net</span> <span title="2019/02/11(月) 11:24:39.24">2019/02/11 11:24</span></div><div style="padding-top: 10px;"><p class="content">나는 트럼프는 의외로 정상이라고 생각해<br><span class="jp">オレはトランプは案外まともだと思ってる</span> </p></div></div></div></div><div class="commentbox1"><div class="content1"><div class="id">12. ID: <span>6n3IJLrf0.net</span> <span title="2019/02/11(月) 11:15:30.09">2019/02/11 11:15</span></div><div style="padding-top: 10px;"><p class="content">글렀다 이녀석들<br><span class="jp">ダメだこいつら</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">13. ID: <span>vBD7UmTA0.net</span> <span title="2019/02/11(月) 11:15:31.41">2019/02/11 11:15</span></div><div style="padding-top: 10px;"><p class="content">독일은 중국과 같이 갈 생각이네<br><span class="jp">ドイツは中国と道連れになる気だねw</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">19. ID: <span>9Q/PDant0.net</span> <span title="2019/02/11(月) 11:15:55.47">2019/02/11 11:15</span></div><div style="padding-top: 10px;"><p class="content">레코드차이나의 기사<br><span class="jp">レコチャイの記事</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">24. ID: <span>YSrqN2M20.net</span> <span title="2019/02/11(月) 11:16:45.30">2019/02/11 11:16</span></div><div style="padding-top: 10px;"><p class="content">부디 아무쪼록 마음대로<br><span class="jp">どうぞどうぞご勝手に</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">28. ID: <span>+8o0SWrn0.net</span> <span title="2019/02/11(月) 11:17:24.84">2019/02/11 11:17</span></div><div style="padding-top: 10px;"><p class="content">독일인, 심각한데-<br><span class="jp">ドイツ人、やべー</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">39. ID: <span>sr9T6ok70.net</span> <span title="2019/02/11(月) 11:18:37.49">2019/02/11 11:18</span></div><div style="padding-top: 10px;"><p class="content">중국 쓰러지면 독일도 쓰러진다.<br><span class="jp">中国コケればドイツもコケる。</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">44. ID: <span>DLYvDf3D0.net</span> <span title="2019/02/11(月) 11:18:55.07">2019/02/11 11:18</span></div><div style="padding-top: 10px;"><p class="content">요시요시w
50%를 넘거라<br><span class="jp">よしよしｗ
50％超えたまえ</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">47. ID: <span>9XtTkXoY0.net</span> <span title="2019/02/11(月) 11:19:13.22">2019/02/11 11:19</span></div><div style="padding-top: 10px;"><p class="content">독일은 또 세계의 적이 되는거야?<br><span class="jp">ドイツはまた世界の敵になるの？</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">58. ID: <span>CAAPWrOv0.net</span> <span title="2019/02/11(月) 11:20:24.19">2019/02/11 11:20</span></div><div style="padding-top: 10px;"><p class="content">미국은 제2차 대전에서의 적이라
일본은 전쟁 후 미국에 능숙히 반미감정도 억눌러졌고
독일 이외의 또 다른 동맹국 이탈리아에 물어봐도 비슷한 결과가 되지 않을까<br><span class="jp">米国は第二次大戦での敵だしな
日本は戦後米国に上手に反米感情も抑え込まれたしな
ドイツ以外のもう1つの同盟国イタリアに聞いても似た結果になるんじゃないか</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">65. ID: <span>YXWWTjD9O.net</span> <span title="2019/02/11(月) 11:21:30.26">2019/02/11 11:21</span></div><div style="padding-top: 10px;"><p class="content">중국이 인접해 있지 않으니 진짜 맨 얼굴 모를 뿐<br><span class="jp">中国が隣接してないから本当の素顔を知らないだけ</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">71. ID: <span>fVGXzHsu0.net</span> <span title="2019/02/11(月) 11:22:04.16">2019/02/11 11:22</span></div><div style="padding-top: 10px;"><p class="content">그러고보니 독일도 반도와 같아서 동료로 하면 지는 역병귀신<sup>(疫病神)</sup>이었지w<br><span class="jp">そういやドイツも半島と同じで仲間にすると負ける疫病神だっったなw</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">74. ID: <span>FoKuVZqh0.net</span> <span title="2019/02/11(月) 11:22:28.98">2019/02/11 11:22</span></div><div style="padding-top: 10px;"><p class="content">머리가 해피 세트인건가<br><span class="jp">頭ハッピーセットかよ</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">75. ID: <span>rL5t40x/0.net</span> <span title="2019/02/11(月) 11:22:33.10">2019/02/11 11:22</span></div><div style="padding-top: 10px;"><p class="content">근처의 자이언<sup>(도라에몽 퉁퉁이)</sup>보다 이웃 마을의 자이언 쪽이 해는 적으니까말야<br><span class="jp">近所のジャイアンより隣町のジャイアンの方が害は少ないからな</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">78. ID: <span>UQPFXuAv0.net</span> <span title="2019/02/11(月) 11:22:45.22">2019/02/11 11:22</span></div><div style="padding-top: 10px;"><p class="content">20세기 두 번에 걸친 세계대전에서, 두 번 다 패한 유일한 나라, 그것이 독일<br><span class="jp">２０世紀の２度に渡る世界大戦で、２度とも負けた唯一の国、それがドイツ</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">97. ID: <span>N/yW+NL/0.net</span> <span title="2019/02/11(月) 11:25:07.23">2019/02/11 11:25</span></div><div style="padding-top: 10px;"><p class="content">뭐 독일은 수상의 전화가 미국에 도청 되고 있었으니까<br><span class="jp">まぁドイツは首相の電話をアメリカに盗聴されたいたからな</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">101. ID: <span>UkriRAaw0.net</span> <span title="2019/02/11(月) 11:25:42.64">2019/02/11 11:25</span></div><div style="padding-top: 10px;"><p class="content">독일 언론이 중국에 당하고 있는거 겠지
바보 나라다<br><span class="jp">ドイツのマスコミが中国にやられているんだろう
馬鹿な国だ</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">116. ID: <span>oh05hA540.net</span> <span title="2019/02/11(月) 11:26:48.30">2019/02/11 11:26</span></div><div style="padding-top: 10px;"><p class="content">즉, 트럼프님의 애완견인 아베도 신용할 수 없다고ww<br><span class="jp">つまり、トランプ様の飼い犬である安倍も信用できないとｗｗ</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">118. ID: <span>/iAEKuVp0.net</span> <span title="2019/02/11(月) 11:27:07.46">2019/02/11 11:27</span></div><div style="padding-top: 10px;"><p class="content">독일은 대륙국가라서 어쩔 수 없어.
해양무역의 사정이 큰 일본과 영국은
강대한 해군과 공군을 가진 미국이 좋아<br><span class="jp">ドイツは大陸国家だから仕方ない。
海洋貿易の都合が大きい日本や英国は
強大な海軍と空軍を持つ米国が好き。</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">127. ID: <span>yCPKWcKu0.net</span> <span title="2019/02/11(月) 11:28:42.64">2019/02/11 11:28</span></div><div style="padding-top: 10px;"><p class="content">독일은 정말 안되게<sup>(ダメダメに)</sup> 되었구나<br><span class="jp">ドイツは本当にダメダメになったんだな</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">128. ID: <span>mFvcZ94A0.net</span> <span title="2019/02/11(月) 11:28:50.39">2019/02/11 11:28</span></div><div style="padding-top: 10px;"><p class="content">사이비 글로벌 하청으로 벌고있는 EU의 경제선봉<sup>(経済先兵)</sup> 독일은 중국의 거대화에 대해 무방비
일본에 있어서는 중국의 횡포거대화(대동아공영권의 중국판) 매우 민폐입니다<br><span class="jp">似非グローバル下請けで儲けてるＥＵの経済先兵のドイツは中国の巨大化に対して無防備
日本にとっては中国の横暴巨大化（大東亜共栄圏の中国版）非常に迷惑ですネン</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">160. ID: <span>+KpTxlmS0.net</span> <span title="2019/02/11(月) 11:31:39.81">2019/02/11 11:31</span></div><div style="padding-top: 10px;"><p class="content">독일과 엮인 쪽이 지는 법칙이니까, 중국측에 붙어주는 것이 고맙다<br><span class="jp">ドイツと組んだ方が負ける法則だから、中国側に付いてくれる方がありがたい</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">172. ID: <span>+pGbbpBQ0.net</span> <span title="2019/02/11(月) 11:32:27.68">2019/02/11 11:32</span></div><div style="padding-top: 10px;"><p class="content">독일은 제1차 대전에서 지고 제2차 대전에서도 진 만년참패국가니까
또 지는것에 향해 가는건가
독일인이란 자기들은 우수하다고 생각해 주위를 적으로 돌려 참패해버리는구나.<br><span class="jp">ドイツは第一次大戦で負け第二次大戦でも負けた万年惨敗国家だから
また負けに向かっていくのかね
ドイツ人って自分たちは優れてると思っちゃって周囲を敵に回して惨敗しちゃうんだろうな。</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">213. ID: <span>Kd66wrbF0.net</span> <span title="2019/02/11(月) 11:36:57.15">2019/02/11 11:36</span></div><div style="padding-top: 10px;"><p class="content">중국독일조선으로 사이좋게 살아가라<br><span class="jp">中独朝で仲良く生きていけ</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">230. ID: <span>tQlyFvxE0.net</span> <span title="2019/02/11(月) 11:38:17.25">2019/02/11 11:38</span></div><div style="padding-top: 10px;"><p class="content">전범국이 아주 반성을 하지 않는구나
공산군사국가의 머슴이 된다든지 역시 뿌리는 나치스야
독일인에게 민주주의는 무리야<br><span class="jp">戦犯国がまるで反省してないな
共産軍事国家の僕になるとかやっぱ根はナチスなんだわ
ドイツ人に民主主義は無理なんや</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">240. ID: <span>DLYvDf3D0.net</span> <span title="2019/02/11(月) 11:39:08.00">2019/02/11 11:39</span></div><div style="padding-top: 10px;"><p class="content">일본은 어쨌든 독일과는 떨어져 있자<br><span class="jp">日本はとにかくドイツとは離れよう</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">241. ID: <span>wNh7oes10.net</span> <span title="2019/02/11(月) 11:39:15.54">2019/02/11 11:39</span></div><div style="padding-top: 10px;"><p class="content">독일은 또다시 패전국이 되고 싶은가<br><span class="jp">ドイツはまた敗戦国になりたいのか。</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">250. ID: <span>S+mLbJzL0.net</span> <span title="2019/02/11(月) 11:39:54.67">2019/02/11 11:39</span></div><div style="padding-top: 10px;"><p class="content">독일 필요없어
승리의 여신 영국님은 와 주십시오<br><span class="jp">ドイツいらん
勝利の女神イギリス様はお越しください</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">259. ID: <span>jzYRR+rE0.net</span> <span title="2019/02/11(月) 11:41:06.70">2019/02/11 11:41</span></div><div style="padding-top: 10px;"><p class="content">저번의 반성없이 또 자신들이 나치스를 키워놓고 나는 나쁘지 않다고 말하는 독일인 이라는 말씀<br><span class="jp">前回の反省なくまた自分たちでナチスを育てておいて俺は悪くないと宣うドイツ人というお話</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">307. ID: <span>WT14Vo1P0.net</span> <span title="2019/02/11(月) 11:46:54.83">2019/02/11 11:46</span></div><div style="padding-top: 10px;"><p class="content">> 독일의 비영리단체 Atlantik-Brucke와 연구기관 Civey가 공동으로 실시한 조사
이 조사기관의 신뢰성은?<br><span class="jp">> ドイツの非営利団体Atlantik-Bruckeと研究機関Civeyが共同で行った調査
この調査機関の信頼性は？</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">308. ID: <span>kIL6aILL0.net</span> <span title="2019/02/11(月) 11:46:59.68">2019/02/11 11:46</span></div><div style="padding-top: 10px;"><p class="content">독일인wwwwwwwwwww<br><span class="jp">ドイツ人ｗｗｗｗｗｗｗｗｗｗｗｗｗ</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">311. ID: <span>X9tlTzVp0.net</span> <span title="2019/02/11(月) 11:47:07.80">2019/02/11 11:47</span></div><div style="padding-top: 10px;"><p class="content">독일은 아인슈타인을 낳은 나라니깐
인류 최고의 두뇌라고<br><span class="jp">ドイツってアインシュタイン産んだ国だからな
人類最高の頭脳だぞ</span> </p></div><div class="content2"><div class="id">493. ID: <span>8zLFUQ0M0.net</span> <span title="2019/02/11(月) 12:02:25.73">2019/02/11 12:02</span></div><div style="padding-top: 10px;"><p class="content">오히려 쫓아낸 나라지<br><span class="jp">むしろ追い出した国だろ</span> </p></div></div></div></div><div class="commentbox1"><div class="content1"><div class="id">313. ID: <span>31a/dmjU0.net</span> <span title="2019/02/11(月) 11:47:12.02">2019/02/11 11:47</span></div><div style="padding-top: 10px;"><p class="content">흐~음 다행이네.
도이치은행도 중국님이 도와줄꺼야. 분명히.<br><span class="jp">ふ〜ん良かったね。
ドイツ銀行も中国様が助けてくれるよ、きっと。</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">315. ID: <span>yYIwEMkq0.net</span> <span title="2019/02/11(月) 11:47:23.97">2019/02/11 11:47</span></div><div style="padding-top: 10px;"><p class="content">경제적으로도 지고 있다<br><span class="jp">経済的にも負けてる</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">324. ID: <span>IrcVOmkB0.net</span> <span title="2019/02/11(月) 11:47:59.55">2019/02/11 11:47</span></div><div style="padding-top: 10px;"><p class="content">다음 전쟁은 저 쪽에 붙을까?<br><span class="jp">次の戦争はアッチ側につくか？</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">330. ID: <span>mgTb0Apy0.net</span> <span title="2019/02/11(月) 11:48:25.16">2019/02/11 11:48</span></div><div style="padding-top: 10px;"><p class="content">독일은 일본을 중국의 일부로밖에 보지 않아<br><span class="jp">ドイツは日本を中国の一部としか見てない</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">361. ID: <span>4ssAgRgO0.net</span> <span title="2019/02/11(月) 11:51:41.91">2019/02/11 11:51</span></div><div style="padding-top: 10px;"><p class="content">레드팀w<br><span class="jp">レッドチームｗ</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">363. ID: <span>/cOoNZQu0.net</span> <span title="2019/02/11(月) 11:51:44.77">2019/02/11 11:51</span></div><div style="padding-top: 10px;"><p class="content">신성 로마 제국 깔보지 마라<br><span class="jp">神聖ローマ帝国なめんな</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">376. ID: <span>T7Ftuppv0.net</span> <span title="2019/02/11(月) 11:53:13.64">2019/02/11 11:53</span></div><div style="padding-top: 10px;"><p class="content">나치스의 정당한 후계자 중국공산당w<br><span class="jp">ナチスの正当な後継者中国共産党ｗ</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">407. ID: <span>J/DrFH/90.net</span> <span title="2019/02/11(月) 11:55:45.24">2019/02/11 11:55</span></div><div style="padding-top: 10px;"><p class="content">독일인은 언제가 돼야 알아채는걸까
이미 늦고나서일까<br><span class="jp">ドイツ人はいつになったら気がつくんだろうなぁ
手遅れになってからだろうなぁ</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">411. ID: <span>nFK8rTpw0.net</span> <span title="2019/02/11(月) 11:56:20.74">2019/02/11 11:56</span></div><div style="padding-top: 10px;"><p class="content">독일 제품은 중국에서 팔린다<br><span class="jp">ドイツ製品は中国で売れる</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">412. ID: <span>WpgCd4ge0.net</span> <span title="2019/02/11(月) 11:56:21.03">2019/02/11 11:56</span></div><div style="padding-top: 10px;"><p class="content">유럽인이 의외로 바보라고<sup>(생각한다)</sup>, 애당초 유럽인에게 설문조사 해도 유럽인 비율이 줄어들고있는거 아닌가?
뭐, 독일인이 원래 저렇다고 말하는 건 비밀이야w<br><span class="jp">欧州人が意外と馬鹿なのと、そもそも欧州人にアンケート取っても欧州人率が減って来ているんじゃないか？
まあ、ドイツ人がそもそもアレだと言うのは秘密やでw</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">420. ID: <span>h0a3QYdh0.net</span> <span title="2019/02/11(月) 11:56:54.91">2019/02/11 11:56</span></div><div style="padding-top: 10px;"><p class="content">독일과 엮이면
반드시 진다<br><span class="jp">ドイツと組むと
必ず負ける</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">424. ID: <span>nFK8rTpw0.net</span> <span title="2019/02/11(月) 11:57:11.59">2019/02/11 11:57</span></div><div style="padding-top: 10px;"><p class="content">거리가 떨어져있으니까<br><span class="jp">距離が離れてるからな</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">425. ID: <span>Y7RW7T1v0.net</span> <span title="2019/02/11(月) 11:57:14.12">2019/02/11 11:57</span></div><div style="padding-top: 10px;"><p class="content">미중 무역협의는 어떻게 될까?
불발에 그치고 타격이 도이치은행까지 파급될까
이야기가 마무리되서 주가가 오를까<br><span class="jp">米中の貿易協議のはどうなるかなあ
不調に終わって打撃がドイツ銀行まで波及するか
話がついて株価が上がるか</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">436. ID: <span>3+exRixk0.net</span> <span title="2019/02/11(月) 11:58:07.33">2019/02/11 11:58</span></div><div style="padding-top: 10px;"><p class="content">중국공산당의 전략이라고는 아무것도 모르는 사람뿐이잖아
중국에 있어서는 정말 손쉬운 상대구나<br><span class="jp">中国共産党の戦略なんて何も分からない人ばかりなんだな
中国にとっては本当にチョロい相手だな</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">456. ID: <span>8xUaE0fV0.net</span> <span title="2019/02/11(月) 11:59:55.69">2019/02/11 11:59</span></div><div style="padding-top: 10px;"><p class="content">미국이랄까 트럼프잖아<br><span class="jp">アメリカっていうかトランプだろ</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">461. ID: <span>+ddfV82t0.net</span> <span title="2019/02/11(月) 12:00:05.01">2019/02/11 12:00</span></div><div style="padding-top: 10px;"><p class="content">트럼프도 독일인이지만<br><span class="jp">トランプもドイツ人なんだけどな</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">465. ID: <span>SMEiNr8a0.net</span> <span title="2019/02/11(月) 12:00:19.47">2019/02/11 12:00</span></div><div style="padding-top: 10px;"><p class="content">수출로 마구 벌고있으니 어쩔 수 없다<br><span class="jp">輸出で儲けまくってるからしょうがない</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">485. ID: <span>O6islSpY0.net</span> <span title="2019/02/11(月) 12:01:34.54">2019/02/11 12:01</span></div><div style="padding-top: 10px;"><p class="content">그렇게 멀면 악의도 오기 어려울 테니까<br><span class="jp">あんだけ遠いと悪意もきにくいだろうからな</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">519. ID: <span>35oOh7np0.net</span> <span title="2019/02/11(月) 12:05:39.41">2019/02/11 12:05</span></div><div style="padding-top: 10px;"><p class="content">독일에 붙어지면 지는 것일까(´・ω・`)<br><span class="jp">ドイツにつかれると負けるのかな(´・ω・`)</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">525. ID: <span>ON6Z+/Qe0.net</span> <span title="2019/02/11(月) 12:06:00.19">2019/02/11 12:06</span></div><div style="padding-top: 10px;"><p class="content">은행을 비롯한 기간산업의 대부분이 중국에 찰싹 붙어있기 때문에
이렇게라도 말하지 않으면www<br><span class="jp">銀行をはじめ基幹産業の多くが中国ベッタリだから
こうでも言わないとwww</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">552. ID: <span>sO8ToLDi0.net</span> <span title="2019/02/11(月) 12:10:06.54">2019/02/11 12:10</span></div><div style="padding-top: 10px;"><p class="content">독일도 땅에 떨어졌구나
중국 따위를 신뢰 할 수 있다든가<br><span class="jp">ドイツも地に落ちたな
中国なんぞを信頼できるとか</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">566. ID: <span>0NQoGzbX0.net</span> <span title="2019/02/11(月) 12:11:36.09">2019/02/11 12:11</span></div><div style="padding-top: 10px;"><p class="content">외교에서 계속 좋지 않은 일만 있으니깐
영국, 프랑스, 미국도 별로 신용하고 있지 않고<br><span class="jp">外交でずっと痛い目に遭ってるから
英国、仏国、米国も別に信用してないんだよなあ</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">568. ID: <span>uBKFZAGG0.net</span> <span title="2019/02/11(月) 12:11:41.59">2019/02/11 12:11</span></div><div style="padding-top: 10px;"><p class="content">닮은 데가 있는지도<br><span class="jp">似てる所があるのかもな</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">571. ID: <span>EhWCg/lA0.net</span> <span title="2019/02/11(月) 12:11:55.67">2019/02/11 12:11</span></div><div style="padding-top: 10px;"><p class="content">일본도 전통적인 먼로주의로 되돌아가는 미국인에 기대면 고립되어 끝난다
이제부터는 여러나라와 친하게 지내지 않으면
미국은 일본에서 돈만 받고 그 후는 마음대로 하라는 것일 뿐이지<br><span class="jp">日本も伝統的モンロー主義に戻るアメリカ人あてにしてると孤立して終わる
これからはいろんな国と仲良くしないと
アメリカは日本から金だけとってあとは勝手にやれというだけだろう</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">575. ID: <span>COU0b9iz0.net</span> <span title="2019/02/11(月) 12:12:25.96">2019/02/11 12:12</span></div><div style="padding-top: 10px;"><p class="content">기계처럼 아스퍼거 작업<sup>(アスペ作業)</sup>밖에 못하는 독일인에게는 강대한 지도자님의 시진핑이 있으면 좋은거야<br><span class="jp">機械みたいにアスペ作業しかできないドイツ人には強大な指導者様の習近平がいればいいの</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">580. ID: <span>yYIwEMkq0.net</span> <span title="2019/02/11(月) 12:13:02.12">2019/02/11 12:13</span></div><div style="padding-top: 10px;"><p class="content">미국 곤란하겠네<br><span class="jp">アメリカ詰んだな</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">597. ID: <span>oDI4pWDk0.net</span> <span title="2019/02/11(月) 12:14:20.92">2019/02/11 12:14</span></div><div style="padding-top: 10px;"><p class="content">그쪽이나 저쪽이나겠지<br><span class="jp">どっちもどっちだろ</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">601. ID: <span>fLiejRyZ0.net</span> <span title="2019/02/11(月) 12:14:48.88">2019/02/11 12:14</span></div><div style="padding-top: 10px;"><p class="content">일본인은 과묵하고 자기주장 하지 않고
말없이 일하는 로봇같아서 기분나쁘니까
그런 주제에 뒷담만 하고, 어쩔 도리가 없다<br><span class="jp">日本人は寡黙で自己主張しないし
黙って働くロボットみたいで気持ち悪いからな
そのくせ陰口ばかりで、どうしようもない</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">633. ID: <span>G8difTkP0.net</span> <span title="2019/02/11(月) 12:18:12.45">2019/02/11 12:18</span></div><div style="padding-top: 10px;"><p class="content">괴짜 독일 따위 아무래도 좋아<br><span class="jp">曲がり屋ドイツなんざどうでもいいわ</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">666. ID: <span>jY1V4dp30.net</span> <span title="2019/02/11(月) 12:22:20.21">2019/02/11 12:22</span></div><div style="padding-top: 10px;"><p class="content">일본은 한 번 졌다만, 독일은 이번에야말로 승자쪽에 붙고싶다, 라고 생각 안해?<br><span class="jp">日本は一回負けただげけど、ドイツは今度こそ勝ち組につきたい、って思わないの？</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">667. ID: <span>yrYrelUD0.net</span> <span title="2019/02/11(月) 12:22:31.30">2019/02/11 12:22</span></div><div style="padding-top: 10px;"><p class="content">또 속고있지만 아무래도 좋아<br><span class="jp">また騙されてるがどうでもいい</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">671. ID: <span>cbLJ2V220.net</span> <span title="2019/02/11(月) 12:22:47.19">2019/02/11 12:22</span></div><div style="padding-top: 10px;"><p class="content">역시 나치스를 지지한 나라네요
간단히 속고 무책임하게 손바닥 뒤집는 것이 독일류<br><span class="jp">さすがナチスを支持した国ですね
簡単に騙されて無責任に手のひら返すのがドイツ流</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">673. ID: <span>oTweAksE0.net</span> <span title="2019/02/11(月) 12:23:04.41">2019/02/11 12:23</span></div><div style="padding-top: 10px;"><p class="content">독일은 변화폭이 너무 크다<br><span class="jp">ドイツって振れ幅が大きすぎる。</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">679. ID: <span>q7xk76Ig0.net</span> <span title="2019/02/11(月) 12:23:36.74">2019/02/11 12:23</span></div><div style="padding-top: 10px;"><p class="content">독일인도 척수반사의 무지성인 사람이 많다는 것<br><span class="jp">ドイツ人も脊髄反射の無知性な人が多いってこと</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">696. ID: <span>VFiInpgl0.net</span> <span title="2019/02/11(月) 12:25:06.96">2019/02/11 12:25</span></div><div style="padding-top: 10px;"><p class="content">반일은커녕 반미였던건가<br><span class="jp">反日どころか反米だったのか</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">749. ID: <span>mRdnt2p30.net</span> <span title="2019/02/11(月) 12:28:58.44">2019/02/11 12:28</span></div><div style="padding-top: 10px;"><p class="content">독일의 해외유학 인기탑은 옛날부터 쭉 미국이고 작년도 그래
독일의 최고층부터 미국으로 이주하고 있는 것은 지금도 변함없어<br><span class="jp">ドイツの海外留学人気トップは昔からずっとアメリカで去年もそう
ドイツのトップ層からアメリカに移住しているのは今も変わらんよ</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">760. ID: <span>Jxp2eDbx0.net</span> <span title="2019/02/11(月) 12:30:26.80">2019/02/11 12:30</span></div><div style="padding-top: 10px;"><p class="content">중국과 독일이 짝을 이룬다면 세계정복이 가능할것 같아<br><span class="jp">中国とドイツが組んだら世界征服出来そう</span> </p></div><div class="content2"><div class="id">784. ID: <span>9+VKw35h0.net</span> <span title="2019/02/11(月) 12:34:14.62">2019/02/11 12:34</span></div><div style="padding-top: 10px;"><p class="content">독일은 한국과 마찬가지로 짝을 이루면 지는 나라인데 그건<br><span class="jp">ドイツは韓国と並んで組んだら負ける国なんですがそれは</span> </p></div></div></div></div><div class="commentbox1"><div class="content1"><div class="id">769. ID: <span>V4B31UVO0.net</span> <span title="2019/02/11(月) 12:32:02.16">2019/02/11 12:32</span></div><div style="padding-top: 10px;"><p class="content">중국에 침식되어가는 나라다운일이다
중화인민공화국 독일성<sup>(省)</sup>으로 좋잖아<br><span class="jp">中国に浸食されきってる国らしい事だ
中華人民共和国独逸省でいいだろ</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">770. ID: <span>QDDR9ZCH0.net</span> <span title="2019/02/11(月) 12:32:31.07">2019/02/11 12:32</span></div><div style="padding-top: 10px;"><p class="content">뭐 독일의 역사를 생각하면, 이렇게 되겠지<br><span class="jp">まあドイツの歴史を考えれば、こうなるだろ</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">777. ID: <span>X9tlTzVp0.net</span> <span title="2019/02/11(月) 12:33:27.95">2019/02/11 12:33</span></div><div style="padding-top: 10px;"><p class="content">독일이 실제로는 말살정책 안했어도
지금 정말로 말살정책을 하고있는 중국과 손잡으면 여러가지로 아무래도 좋아져버리겠지w<br><span class="jp">ドイツが実際には絶滅政策してなくても
今本当に絶滅政策してる中国と組んでたら色々どうでもよくなっちゃうだろｗ</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">783. ID: <span>nYyWaPtG0.net</span> <span title="2019/02/11(月) 12:34:05.38">2019/02/11 12:34</span></div><div style="padding-top: 10px;"><p class="content">영국을 따라 독일도 EU를 이탈하지 않으면 일·유럽 EPA에서 당할거야<br><span class="jp">イギリスに倣ってドイツもEUを離脱しないと日欧EPAでやられるぞ</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">825. ID: <span>tXu5FtJC0.net</span> <span title="2019/02/11(月) 12:38:26.76">2019/02/11 12:38</span></div><div style="padding-top: 10px;"><p class="content">트럼프 때문에 미국의 신뢰도 폭락중이네<br><span class="jp">トランプのせいでアメリカの信頼度暴落中だな</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">851. ID: <span>kKcWKXhj0.net</span> <span title="2019/02/11(月) 12:40:32.56">2019/02/11 12:40</span></div><div style="padding-top: 10px;"><p class="content">뭐 현실은, 이제부터는 중국의 시대.
부유층과 중산층이 몇억명있다고 생각하나.<br><span class="jp">まあ現実は、これからは中国の時代。
富裕層と中間層が何億人いると思ってるんだ。</span> </p></div><div class="content2"><div class="id">873. ID: <span>lYzVDy2n0.net</span> <span title="2019/02/11(月) 12:41:56.30">2019/02/11 12:41</span></div><div style="padding-top: 10px;"><p class="content">확실히<sup>(たしかに)</sup><br><span class="jp">たしかに</span> </p></div></div></div></div><div class="commentbox1"><div class="content1"><div class="id">852. ID: <span>OqnnqUVA0.net</span> <span title="2019/02/11(月) 12:40:36.05">2019/02/11 12:40</span></div><div style="padding-top: 10px;"><p class="content">똑똑한 사람들인데
항상 전쟁에 지는 이유가
보이는 것 같아.<br><span class="jp">賢い人たちなのに
いつも戦争に負ける理由が
見えたような気がする。</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">890. ID: <span>mRdnt2p30.net</span> <span title="2019/02/11(月) 12:43:30.56">2019/02/11 12:43</span></div><div style="padding-top: 10px;"><p class="content">시진핑의 딸은 미국 유학이고 친족은 미국 생활<br><span class="jp">習近平は娘はアメリカ留学で親族はアメリカ暮らし</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">925. ID: <span>7TSX95UO0.net</span> <span title="2019/02/11(月) 12:46:56.46">2019/02/11 12:46</span></div><div style="padding-top: 10px;"><p class="content">독일은 1차, 2차는 주연이었지만, 3차에서는 조연의 서포터겠네.<br><span class="jp">ドイツは1次、2次は主役だったが、3次ではわき役のサポーターだな。</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">940. ID: <span>Z8RKFDVA0.net</span> <span title="2019/02/11(月) 12:48:19.71">2019/02/11 12:48</span></div><div style="padding-top: 10px;"><p class="content">애초에 다른나라한테 좋아해지려고 하는 등 초등학생같은걸 말하는 편이 어린이라고 생각해<br><span class="jp">そもそも他国から好かれようなどという小学生みたいなことを言っている方がお子様なんだと思う</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">952. ID: <span>7TSX95UO0.net</span> <span title="2019/02/11(月) 12:49:52.21">2019/02/11 12:49</span></div><div style="padding-top: 10px;"><p class="content">옛날에는 다음번은 이탈리아 빼고 하자가, 독일, 이탈리아 빼고 하자로
바뀌었구나.<br><span class="jp">昔は今度はイタリア抜きでやろうぜが、ドイツ、イタリア抜きでやろうやに
替わったな。</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">954. ID: <span>KXuF2DnZ0.net</span> <span title="2019/02/11(月) 12:50:16.49">2019/02/11 12:50</span></div><div style="padding-top: 10px;"><p class="content">독일은 너무 꺼멓다
중국과 같거나 그 이상으로 신뢰할 수 없다<br><span class="jp">ドイツは黒すぎる
中国と同じかそれ以上に信頼出来ない</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">958. ID: <span>Z8RKFDVA0.net</span> <span title="2019/02/11(月) 12:50:27.11">2019/02/11 12:50</span></div><div style="padding-top: 10px;"><p class="content">일본인과 독일인은 명분<sup>(建前)</sup>을 진지하게 받아들이니까 말이지
○○주의라든가 어디에서도 그런것 믿지 않는데, 일본과 독일만 진짜로 저돌맹진하니까 정말 무섭다<br><span class="jp">日本人とドイツ人は建前を本気にするからなあ
○○主義とか言われるとどこもそんなもの信じてないのに、日本とドイツだけ本気で猪突猛進するからほんとに怖い</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">965. ID: <span>F+xjG0oW0.net</span> <span title="2019/02/11(月) 12:51:22.08">2019/02/11 12:51</span></div><div style="padding-top: 10px;"><p class="content">어느 쪽도 신용할 수 없다
가장 믿을 수 없는 것은 메르켈
이것이 정답<br><span class="jp">どっちも信用出来ない
一番信用出来ないのはメルケル
これが正解</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">967. ID: <span>xSq1qUYJ0.net</span> <span title="2019/02/11(月) 12:51:29.49">2019/02/11 12:51</span></div><div style="padding-top: 10px;"><p class="content">미국인의 과반수: 일본보다도 중국이 더 중요한 나라
라는 시대라고w<br><span class="jp">アメリカ人の過半数：日本よりも中国のほうが重要な国
っていう時代だぞｗ</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">980. ID: <span>AWGHRnrQ0.net</span> <span title="2019/02/11(月) 12:52:37.28">2019/02/11 12:52</span></div><div style="padding-top: 10px;"><p class="content">음, 트럼프는 착취하는 것 밖에 머리에 없으니까
비교론이라면 트럼프보다 시진핑 쪽이 낫다는 것은 있지
중국에 다가가는 아베짱은 옳아<br><span class="jp">まあ、トランプは搾取することしか頭にないからな
比較論ならトランプよりキンペーの方がマシってのはあるね
中国にすり寄る安倍ちゃんは正しいよ</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">987. ID: <span>/WZbuSUU0.net</span> <span title="2019/02/11(月) 12:54:23.45">2019/02/11 12:54</span></div><div style="padding-top: 10px;"><p class="content">이렇게 해서 역사는 반복된다
독일인은 사회주의에서 벗어날 수 없는 거구나
이번에는 무슨 변명을 할지<br><span class="jp">こうして歴史は繰り返される
ドイツ人は社会主義からは逃れられないんだね
今度はどんな言い訳をすることやら</span> </p></div></div></div><div class="commentbox1"><div class="content1"><div class="id">998. ID: <span>7fwTOgyR0.net</span> <span title="2019/02/11(月) 12:55:35.15">2019/02/11 12:55</span></div><div style="padding-top: 10px;"><p class="content">최근의 미국 주로 트럼프의 발언 듣고있으면 그렇게 되는것도 어쩔 수 없다고 생각해<br><span class="jp">最近のアメリカ主にトランプの発言聞いてたらそうなるのもしゃーないと思うよ</span> </p></div></div></div></div> | 304.157407 | 2,312 | 0.694268 | kor_Hang | 0.649489 |
6f6d283346c5ec0f2148dfe669a1892671ac876b | 4,582 | md | Markdown | _posts/problem-solving/2021-02-14-programmers-62050-moving-topography.md | taesunny/taesunny.github.io | 459793de81c1b15ca141ca1a35742c94993031a7 | [
"MIT"
] | 1 | 2021-03-31T13:39:03.000Z | 2021-03-31T13:39:03.000Z | _posts/problem-solving/2021-02-14-programmers-62050-moving-topography.md | taesunny/taesunny.github.io | 459793de81c1b15ca141ca1a35742c94993031a7 | [
"MIT"
] | null | null | null | _posts/problem-solving/2021-02-14-programmers-62050-moving-topography.md | taesunny/taesunny.github.io | 459793de81c1b15ca141ca1a35742c94993031a7 | [
"MIT"
] | null | null | null | ---
title: "[Programmers] 지형 이동 (62050번) - Java Solution"
excerpt: ""
categories:
- problem-solving
tags:
- [algorithm, programmers, mst, union-find, comparable, kruskal, comparable]
toc: true
toc_sticky: true
date: 2021-02-14
last_modified_at: 2021-02-14
---
# 문제
- https://programmers.co.kr/learn/courses/30/lessons/62050
---
# 기억할 점
- comparable 구현을 통한 구현한 객체의 sort 방법
- MST 구현 - 크루스칼, 프림 알고리즘
- 자주 활용되는 union-find 알고리즘
---
# Solution
``` java
import java.io.IOException;
import java.util.ArrayDeque;
import java.util.ArrayList;
import java.util.Collection;
import java.util.Collections;
import java.util.Deque;
import java.util.List;
class Solution {
class Edge implements Comparable<Edge> {
int cost;
int[] edge;
public Edge(int cost, int[] edge) {
this.cost = cost;
this.edge = edge;
}
@Override
public int compareTo(Edge e) {
return this.cost - e.cost;
}
public int getCost() {
return this.cost;
}
public int[] getEdge() {
return this.edge;
}
}
int findParent(int[] parent, int targetGroup) {
if (targetGroup == parent[targetGroup]) {
return targetGroup;
}
return parent[targetGroup] = findParent(parent, parent[targetGroup]);
}
boolean isSameParent(int[] parent, int targetGroup1, int targetGroup2) {
return findParent(parent, targetGroup1) == findParent(parent, targetGroup2);
}
void uniteGroup(int[] parent, int targetGroup1, int targetGroup2) {
parent[findParent(parent, targetGroup2)] = findParent(parent, targetGroup1);
}
public int solution(int[][] land, int height) {
int[] dx = new int[] { 0, 1, 0, -1 };
int[] dy = new int[] { 1, 0, -1, 0 };
int[][] group = new int[land.length][land.length];
int groupNumber = 0;
Deque<int[]> d = new ArrayDeque<>();
for (int i = 0; i < land.length; i++) {
for (int j = 0; j < land.length; j++) {
groupNumber++;
if (group[i][j] > 0) {
continue;
}
d.add(new int[] { i, j });
group[i][j] = groupNumber;
while (!d.isEmpty()) {
int[] target = d.pop();
for (int k = 0; k < 4; k++) {
int temp_x = target[0] + dx[k];
int temp_y = target[1] + dy[k];
if (temp_x < 0 || temp_x >= land.length || temp_y < 0 || temp_y >= land.length) {
continue;
}
if (group[temp_x][temp_y] > 0) {
continue;
}
if (Math.abs(land[target[0]][target[1]] - land[temp_x][temp_y]) > height) {
continue;
}
group[temp_x][temp_y] = groupNumber;
d.add(new int[] { temp_x, temp_y });
}
}
}
}
List<Edge> e = new ArrayList();
for (int i = 0; i < land.length; i++) {
for (int j = 0; j < land.length; j++) {
for (int k = 0; k < 4; k++) {
int temp_x = i + dx[k];
int temp_y = j + dy[k];
if (temp_x < 0 || temp_x >= land.length || temp_y < 0 || temp_y >= land.length) {
continue;
}
if (group[temp_x][temp_y] == group[i][j]) {
continue;
}
e.add(new Edge(Math.abs(land[i][j] - land[temp_x][temp_y]),
new int[] { group[i][j], group[temp_x][temp_y] }));
}
}
}
int answer = 0;
int[] parent = new int[groupNumber + 1];
Collections.sort(e);
for (int i = 1; i < groupNumber + 1; i++) {
parent[i] = i;
}
for (int i = 0; i < e.size(); i++) {
int cost = e.get(i).getCost();
int fromGroup = e.get(i).getEdge()[0];
int toGroup = e.get(i).getEdge()[1];
if (!isSameParent(parent, fromGroup, toGroup)) {
uniteGroup(parent, fromGroup, toGroup);
answer += cost;
}
}
return answer;
}
}
```
---
# 참고한 글
- https://yabmoons.tistory.com/470 | 26.034091 | 105 | 0.459188 | kor_Hang | 0.273581 |
6f6d6feb1449a5579a77cc8a328d5083540bf809 | 12,674 | md | Markdown | doc/integrations/pytorch/docs/source/tutorial_chat_service.md | novium258/cortx-1 | ce5b939b33b8d24d89b31807ac3bcaa8f24096bc | [
"Apache-2.0"
] | 1 | 2020-09-27T05:00:06.000Z | 2020-09-27T05:00:06.000Z | doc/integrations/pytorch/docs/source/tutorial_chat_service.md | novium258/cortx-1 | ce5b939b33b8d24d89b31807ac3bcaa8f24096bc | [
"Apache-2.0"
] | 1 | 2021-08-04T11:17:39.000Z | 2021-08-04T11:17:39.000Z | doc/integrations/pytorch/docs/source/tutorial_chat_service.md | novium258/cortx-1 | ce5b939b33b8d24d89b31807ac3bcaa8f24096bc | [
"Apache-2.0"
] | 1 | 2021-05-03T13:27:14.000Z | 2021-05-03T13:27:14.000Z | # Using Chat Services
This is a tutorial for connecting your trained ParlAI agents to various chat services in order to allow your models to talk to humans. Humans using chat services (like Facebook Messenger) can be viewed as another type of agent in ParlAI and communicate in the standard observation/act dict format.
We currently support the following chat services:
1. **Browser**
2. **Facebook Messenger**
3. **Terminal**
4. **Web Sockets**
You can find more information on how to set up these services below.
:::{note}
If you'd like to use a service outside of the 4 listed above, please read [here](https://github.com/facebookresearch/ParlAI/tree/master/parlai/chat_service) for information on how to set up a new chat service.
:::
## Overview
As stated, humans messaging on chat services can be viewed as a type of agent in ParlAI, communicating with models via observations and action dicts. Human agents, which are [`ChatServiceAgents`](parlai.chat_service.core.agents.ChatServiceAgent) are placed in worlds with ParlAI agent(s) and possibly other humans, and the world defines how each of these agents interacts.
The chat environment is defined by the **task**. A task typically consists of an `Overworld`, which can spawn subtasks (subworlds) or serve as a "main menu", allowing people to pick from multiple conversation options. The task definition resides in a config file, `config.yml`, which contains all available worlds and any additional commandline arguments.
Here is an example config file for a Messenger chatbot:
```
tasks:
default:
onboard_world: MessengerBotChatOnboardWorld
task_world: MessengerBotChatTaskWorld
timeout: 1800
agents_required: 1
task_name: chatbot
world_module: parlai.chat_service.tasks.chatbot.worlds
overworld: MessengerOverworld
max_workers: 30
opt: # Additional model opts go here
debug: True
models:
blender_90M:
model: transformer/generator
model_file: zoo:blender/blender_90M/model
interactive_mode: True
no_cuda: True
additional_args:
page_id: 1 # configure your own page
```
Let's walk through each of these keys:
- **`tasks`** - the `tasks` key defines the options that are presented to a user upon entering an `Overworld`. In this case, there is only one `task` defined: `default`. The `default` key specifies the following subkeys:
- `onboard_world` - the world used for agent onboarding
- `task_world` - the world that defines that logic for handling users in the main task
- `timeout` - the timeout for human responses in the world
- `agents_required` - how many *human* agents are required to run this world. Specify > 1 if you'd like more than one human to interact.
- **`task_name`** - the name of your task. not super important to define, but good to have nonetheless
- **`world_module`** - this is a module path to the module in which **all** of the task worlds are defined. If you have worlds in separate files, simply importing them into this file will suffice.
- **`overworld`** - The name of the overworld class.
- **`max_workers`** - How many max human connections you plan on supporting for your service
- **`opt`** - any task-specific options you need to define.
- **`models`** - Perhaps **the most important** key in this config. This is where you define the models that you'll be using. Each entry under this is a mapping from custom model name to model params. So, in this example, we have defined a model `blender_90M` that we would like to access in their task. For this model, we then specify the actual model arguments necessary to create a ParlAI agent.
- **`additional_args`** - These are for any specific service-specific args you might want to specify - e.g. if using Facebook Messenger, you would specify your page ID here.
:::{important}
**ON THE SUBJECT OF MODELS**
The `models` key defines all models you'd like to load in your service - the respective chat service managers load models according to these parameters, and then put a shared copy of the agent in `opt['shared_bot_params'][model_key]`. The following snippet is copied from the `MessengerBotChatTaskWorld`:
```python
from parlai.core.agents import create_agent_from_shared
from parlai.core.worlds import World
class MessengerBotChatTaskWorld(World):
"""
Example one person world that talks to a provided agent (bot).
"""
MAX_AGENTS = 1
MODEL_KEY = 'blender_90M'
def __init__(self, opt, agent, bot):
self.agent = agent
self.episodeDone = False
self.model = bot
self.first_time = True
@staticmethod
def generate_world(opt, agents):
copy_of_model = create_agent_from_shared(
opt['shared_bot_params'][MessengerBotChatTaskWorld.MODEL_KEY]
)
return MessengerBotChatTaskWorld(opt, agents[0], copy_of_model)
```
:::
After following the set-up instructions (detailed below) and filling in your own page id, this task could be run with the following command from the `parlai/chat_service/services/messenger` directory:
```
python run.py --config-path ../../tasks/chatbot/config.yml
```
## Example Tasks
As an example, the [Overworld Demo](https://github.com/facebookresearch/ParlAI/blob/master/parlai/chat_service/tasks/overworld_demo/) displays three separate tasks connected together by an overworld.
- The `echo` task is a simple example of an echo bot, and shows the functionality and flow of a simple single-person world.
- The `onboard data` task is an example that shows how an onboarding world can collect information that is later exposed in the active task world.
- The `chat` task is an example of a task that requires multiple users, and shows how many people can be connected together in an instance of a world and then returned to the overworld upon completion of a task.
In addition to the overworld demo, the following example tasks are provided:
- [Generic Chatbot](https://github.com/facebookresearch/ParlAI/blob/master/parlai/chat_service/tasks/chatbot/): Allow conversations with any ParlAI models, for instance the [PersonaChat](https://github.com/facebookresearch/ParlAI/tree/master/projects/personachat) model.
- [QA Data Collection](https://github.com/facebookresearch/ParlAI/blob/master/parlai/chat_service/tasks/qa_data_collection/): collect questions and answers from people, given a random Wikipedia paragraph from SQuAD.
### Creating your Own Task
To create your own task, start with reading the tutorials on the provided examples, and then copy and modify the example `worlds.py` and `config.yml` files to create your task.
**A few things to keep in mind:**
1. A conversation ends when a call between `parley` calls to `episode_done` returns True.
2. Tasks with an overworld should return the name of the world that they want to queue a user into from the ``parley`` call in which the user makes that selection to enter a world.
3. Tasks with no overworld will immediately attempt to put a user into the queue for the default task onboarding world or actual task world (if no onboarding world exists), and will do so again following the completion of a world (via `episode_done`).
3. To collect the conversation, data should be collected during every `parley` and saved during the `world.shutdown` call. You must inform the user of the fact that the data is being collected as well as your intended use.
4. Finally, if you wish to use and command line arguments as you would in ParlAI, specify those in the `opt` section of the config file.
## Available Chat Services
### Browser
This allows you to participate in a ParlAI world as an agent using a local browser.
This extends the `websocket` chat service implementation to run a server locally,
which you can send and receive messages using a browser.
#### Setup
1. Run: `python parlai/chat_service/services/browser_chat/run.py --config-path path/to/config.yml --port PORT_NUMBER`
2. Run: `python client.py --port PORT_NUMBER`
3. Interact
**Example command:** `python parlai/chat_service/services/browser_chat/run.py --config-path parlai/chat_service/tasks/chatbot/config.yml --port 10001`
If no port number is specified in `--port` then the default port used will be `34596`. If specifying, ensure both port numbers match on client and server side.
### Facebook Messenger
This allows you to chat with a ParlAI model on Facebook Messenger.
<p align="center"><img width="80%" src="_static/img/messenger-example.png" /></p>
#### Setup
- ParlAI's Messenger functionality requires a free heroku account which can be obtained [here](https://signup.heroku.com/). Running any ParlAI Messenger operation will walk you through linking the two.
- Running and testing a bot on the [Facebook Messenger Platform](https://developers.facebook.com/docs/messenger-platform) for yourself will require following the guide to set up a [Facebook App](https://developers.facebook.com/docs/messenger-platform/getting-started/app-setup) for Messenger. Skip the set up your webhook step, as ParlAI will do it for you.
- When the guide asks you to configure your webhook URL, you're ready to run the task. This can be done by running the `run.py` file in with python.
- After the heroku server is setup, the script will print out your webhook URL to the console, this should be used to continue the tutorial. The default verify token is `Messenger4ParlAI`. This URL should be added in the Webhook section. The webhook subscription fields should also be edited to subscribe to the `messages` field.
- On the first run, the page will ask you for a "Page Access Token," which is also referred to on the messenger setup page. Paste this in to finish the setup. You should now be able to communicate with your ParlAI world by messaging your page.
- To open up your bot for the world to use, you'll need to submit your bot for approval from the [Developer Dashboard](https://developers.facebook.com/apps/).
**Note:** When running a new task from a different directory, the webhook url will change. You will need to update this in the developer console from the webhook settings using "edit subscription." Your Page Access token should not need to be changed unless you want to use a different page.
Additional flags can be used (you can also specify these in the `config.yml` file):
- `--password <value>` requires that a user sends the message contained in `value` to the bot in order to access the rest of the communications.
- `--force-page-token` forces the script to request a new page token from you, allowing you to switch what page you're running your bot on.
- `--verbose` and `--debug` should be used before reporting problems that arise that appear unrelated to your world, as they expose more of the internal state of the messenger manager.
**Other things to keep in mind when creating your Messenger tasks:**
- Your world can utilize the complete set of [Facebook Messenger Templates](https://developers.facebook.com/docs/messenger-platform/send-messages/templates) by putting the formatted data in the 'payload' field of the observed action.
- Quick replies can be attached to any action, the `MessengerOverworld` of the [Overworld Demo](https://github.com/facebookresearch/ParlAI/blob/master/parlai/chat_service/tasks/overworld_demo/) displays this functionality.
### Terminal
This allows you to participate in a ParlAI world as an agent using the terminal.
This extends the `websocket` chat service implementation to run a server locally,
which you can send and receive messages from using the terminal.
#### Setup
1. Run: `python parlai/chat_service/services/terminal_chat/run.py --config-path path/to/config.yml --port PORT_NUMBER`
2. Run: `python client.py --port PORT_NUMBER`
3. Interact
**Example command:** `python parlai/chat_service/services/terminal_chat/run.py --config-path parlai/chat_service/tasks/chatbot/config.yml --port 10001`
If no port number is specified in `--port` then the default port used will be `34596`. If specifying, ensure both port numbers match on client and server side.
### Web Sockets
See **Browser** above for an example implementation of a websockets-based chat service. You can view the code [here](https://github.com/facebookresearch/ParlAI/tree/master/parlai/chat_service/services/browser_chat).
### Adding a New Chat Service
For full instructions on adding a new chat service to ParlAI, please read [here](https://github.com/facebookresearch/ParlAI/tree/master/parlai/chat_service/).
| 61.227053 | 403 | 0.755089 | eng_Latn | 0.994823 |
6f6df9acd55d9e78945985eac82bbf1888cdec5c | 614 | md | Markdown | content/run/linux.md | Joshj23icy/BastionDocs | 8b1e65d0bb10efd8542f9cf2cb7ff7bb7ad65462 | [
"MIT"
] | 7 | 2019-05-05T12:58:30.000Z | 2021-08-01T16:48:51.000Z | content/run/linux.md | Joshj23icy/BastionDocs | 8b1e65d0bb10efd8542f9cf2cb7ff7bb7ad65462 | [
"MIT"
] | 7 | 2019-02-06T02:31:59.000Z | 2020-12-18T08:52:01.000Z | content/run/linux.md | Joshj23icy/BastionDocs | 8b1e65d0bb10efd8542f9cf2cb7ff7bb7ad65462 | [
"MIT"
] | 18 | 2018-12-03T22:20:49.000Z | 2021-08-12T21:21:43.000Z | ---
title: Run on Linux
---
If you have successfully installed Bastion, you will have a `bastion.sh` script
that makes it easy to run Bastion without any hassle, among other things.
To start Bastion, first of all, you will need to navigate into the `Bastion`
directory. _That is where the script is!_
```bash
cd ~/Bastion
```
Then, it is as simple as running this:
```bash
./bastion.sh --start
```
<note type="info">
The `bastion.sh` script can do a whole lot of things besides just helping
you with running Bastion. Want to find out what else can it do? Simply
run `./bastion.sh` to find out.
</note>
| 23.615385 | 79 | 0.716612 | eng_Latn | 0.999462 |
6f6e5058414e3d2d9d106a2ca2cd9001303c4163 | 418 | md | Markdown | pomelo/websocket/index.md | NextZeus/pomeloframework | 99e99f5dfeb37d103837be402b7fa6a403de76ba | [
"Apache-2.0"
] | 118 | 2016-11-18T06:27:49.000Z | 2022-03-29T06:04:46.000Z | pomelo/websocket/index.md | NextZeus/pomeloframework | 99e99f5dfeb37d103837be402b7fa6a403de76ba | [
"Apache-2.0"
] | 1 | 2017-09-28T03:35:56.000Z | 2017-09-28T06:21:41.000Z | pomelo/websocket/index.md | NextZeus/pomeloframework | 99e99f5dfeb37d103837be402b7fa6a403de76ba | [
"Apache-2.0"
] | 41 | 2017-02-27T13:05:23.000Z | 2021-07-22T10:10:27.000Z | # pomelo websocket 支持自动重连
在pomelo 0.9版本中，pomelo-jsclient-websocket 支持自动重连。重连发生在连接断开后的5s后，在重连失败后下次重连的时间将是上次重连时间的2倍；所以重连时间依次为5s, 10s，20s,依次类推。默认最大的重连次数是10次，该参数可以在连接初始化过程中进行配置。
```
//设置客户端重连
pomelo.init({
host: 127.0.0.1,
port: 3050,
reconnect: true
}, function() {
});
//设置客户端重连最大次数
pomelo.init({
host: 127.0.0.1,
port: 3050,
reconnect: true，
maxReconnectAttempts： 20
}, function() {
});
```
| 13.933333 | 147 | 0.69378 | yue_Hant | 0.096308 |
6f6f0a09d85caef9c328f8ac5e2af46a8334f227 | 66 | md | Markdown | README.md | lean-stack/symfony-demo | a8c7f5482c4c3e04c07700035ba83ee10f8acc2f | [
"MIT"
] | null | null | null | README.md | lean-stack/symfony-demo | a8c7f5482c4c3e04c07700035ba83ee10f8acc2f | [
"MIT"
] | null | null | null | README.md | lean-stack/symfony-demo | a8c7f5482c4c3e04c07700035ba83ee10f8acc2f | [
"MIT"
] | null | null | null | # Symfony Demo
> Simple app with several framework feature demos
| 16.5 | 49 | 0.787879 | eng_Latn | 0.966776 |
6f6fd193a51ba7d281bf6db8decf355cca628dcc | 95 | md | Markdown | docs/softdev/requirement/README.md | umbalaconmeogia/traning-developing-skill-for-brse | a4671f8bf21d62c87eab04ab086da779da20b655 | [
"MIT"
] | 2 | 2019-08-16T09:54:12.000Z | 2019-08-26T01:46:38.000Z | docs/softdev/requirement/README.md | umbalaconmeogia/traning-developing-skill-for-brse | a4671f8bf21d62c87eab04ab086da779da20b655 | [
"MIT"
] | null | null | null | docs/softdev/requirement/README.md | umbalaconmeogia/traning-developing-skill-for-brse | a4671f8bf21d62c87eab04ab086da779da20b655 | [
"MIT"
] | 2 | 2019-08-16T09:46:06.000Z | 2019-08-21T08:57:43.000Z | # Requirement Definition
## References
* [RD format](./files/RequirementDefinitionFormat.md)
| 15.833333 | 53 | 0.768421 | kor_Hang | 0.473528 |
6f7096a051de2df13b8f542aed8d610c051d10ab | 4,561 | md | Markdown | help/c-activities/c-multivariate-testing/t-create-multivariate-test/create-multivariate-test.md | rhornick/target.en | 2c8e7b73ca70149c53d3481609602fe37829362c | [
"MIT"
] | null | null | null | help/c-activities/c-multivariate-testing/t-create-multivariate-test/create-multivariate-test.md | rhornick/target.en | 2c8e7b73ca70149c53d3481609602fe37829362c | [
"MIT"
] | null | null | null | help/c-activities/c-multivariate-testing/t-create-multivariate-test/create-multivariate-test.md | rhornick/target.en | 2c8e7b73ca70149c53d3481609602fe37829362c | [
"MIT"
] | null | null | null | ---
description: The Visual Experience Composer in Target makes it easy to create your test right on a Target-enabled page and to modify portions of the page within Target.
keywords: mvt;multivariate test;multivariate test create;multivariate test creating;mvt create;mvt creating;mvt how;multivariate test how
seo-description: The Visual Experience Composer in Target makes it easy to create your test right on a Target-enabled page and to modify portions of the page within Target.
seo-title: Create a Multivariate Test
solution: Target
title: Create a Multivariate Test
uuid: 876441bd-d841-4974-b1ec-3ad7cb6ef3ee
---
# Create a Multivariate Test{#create-a-multivariate-test}
The Visual Experience Composer in Target makes it easy to create your test right on a Target-enabled page and to modify portions of the page within Target.
The Target point-and-click editor enables you to pick any location and add multiple offers.
The multivariate test takes a page-first report. In other words, the test runs on a specific URL, with the experiences you design for that page.
1. Click **[!UICONTROL Create Activity]** > **[!UICONTROL Multivariate Test]**.
1. [Specify the URL](../../../c-activities/c-multivariate-testing/t-create-multivariate-test/url.md#concept_C12E4A85FF3B4E518E3110F6CF1AF9C0) for the page you want to test, then click **[!UICONTROL Create Activity]**.
>[!NOTE]
>
>Use a complete URL, including the HTTP or HTTPS at the beginning.
If a message appears, asking you to enable your browser for mixed content, follow the instructions in the message. After enabling your browser for mixed content, begin again at Step 1.
The Visual Experience Composer opens.
For troubleshooting information about the VEC, should you have problems, see [Troubleshooting the Visual Experience Composer](../../../c-experiences/c-visual-experience-composer/r-troubleshoot-composer/troubleshoot-composer.md#reference_77743144F10143A3A89D56E116D296E4).
1. Type a name for the activity.
The following characters are not allowed in an activity name:
| Character | Description |
|--- |--- |
|/|Forward slash|
|?|Question mark|
|#|Number sign|
|:|Colon|
|=|Equals to|
|+|Plus|
|-|Minus|
|@|At sign|
1. [Create the offers in each location](../../../c-activities/c-multivariate-testing/t-create-multivariate-test/add-offers.md#concept_DCE6B45C30F7419B8EC17AFDEE8D8AA6).
You can add the following kinds of offers:
* HTML
* Image
* Text
1. [Preview your experiences](../../../c-activities/c-multivariate-testing/t-create-multivariate-test/preview-experiences.md#task_21A700587E88453A9FC2210C0DE53A28).
You can view each experience, and exclude any you do not want to include in your test.
1. [Use the Traffic Estimator](../../../c-activities/c-multivariate-testing/t-create-multivariate-test/traffic-estimator.md#task_71AA6922AFD447EA8C5E610A78ABA714) to test the feasibility of your test plan.
 
1. Choose the audience and percentage of qualifying visitors that you want to enter the activity.
For example, you might limit entries to 50% of all visitors or 45% of your "Californians" audience.
>[!NOTE]
>
>In addition to selecting an existing audience, you can combine multiple audiences to create ad hoc combined audiences rather than creating a new audience. For more information, see [Combining Multiple Audiences](../../../c-target/combining-multiple-audiences.md#concept_A7386F1EA4394BD2AB72399C225981E5).
1. [Review the test summary](../../../c-activities/c-multivariate-testing/t-create-multivariate-test/test-summary.md#reference_971AB225963A4DC18EEB5B0E20F0A4A7) and make any desired changes, then click **[!UICONTROL Next]**..
1. [Specify the goals and settings](../../../c-activities/c-multivariate-testing/t-create-multivariate-test/goals-and-settings.md#reference_B25389FD6F3A4989801E740364B089CC) for the test.
1. Click **[!UICONTROL Save and Close]** to create the activity.
## Training video: Creating Multivariate Tests
This video demonstrates how to plan and create a multivariate test using the Target three-step guided workflow.
* Define and design a multivariate test
* Create a multivariate test
>[!VIDEO](https://www.youtube.com/watch?v=X8w5IQqEOow)
| 45.61 | 308 | 0.756632 | eng_Latn | 0.953954 |
6f70d81ef71bde62728aa2a256aba1ad5fdb1d4e | 7,585 | md | Markdown | docs/android/app-fundamentals/services/creating-a-service/index.md | poulad/xamarin-docs | 83c7557d962684d67a553922b36ec6ff6b71f898 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2019-02-06T09:35:43.000Z | 2019-02-06T09:35:50.000Z | docs/android/app-fundamentals/services/creating-a-service/index.md | poulad/xamarin-docs | 83c7557d962684d67a553922b36ec6ff6b71f898 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/android/app-fundamentals/services/creating-a-service/index.md | poulad/xamarin-docs | 83c7557d962684d67a553922b36ec6ff6b71f898 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-02-07T20:00:06.000Z | 2020-02-07T20:00:06.000Z | ---
title: "Creating a Service"
ms.prod: xamarin
ms.assetid: A78A55E7-FB5C-4C42-8E3E-939B5E98F9EB
ms.technology: xamarin-android
author: topgenorth
ms.author: toopge
ms.date: 05/03/2018
---
# Creating a Service
Xamarin.Android services must obey two inviolable rules of Android services:
* They must extend the [`Android.App.Service`](https://developer.xamarin.com/api/type/Android.App.Service/).
* They must be decorated with the [`Android.App.ServiceAttribute`](https://developer.xamarin.com/api/type/Android.App.ServiceAttribute/).
Another requirement of Android services is that they must be registered in the **AndroidManifest.xml** and given a unique name. Xamarin.Android will automatically register the service in the manifest at build time with the necessary XML attribute.
This code snippet is the simplest example of creating a service in Xamarin.Android that meets these two requirements:
```csharp
[Service]
public class DemoService : Service
{
// Magical code that makes the service do wonderful things.
}
```
At compile time, Xamarin.Android will register the service by injecting the following XML element into **AndroidManifest.xml** (notice that Xamarin.Android generated a random name for the service):
```xml
<service android:name="md5a0cbbf8da641ae5a4c781aaf35e00a86.DemoService" />
```
It is possible to share a service with other Android applications by _exporting_ it. This is accomplished by setting the `Exported` property on the `ServiceAttribute`. When exporting a service, the `ServiceAttribute.Name` property should also be set to provide a meaningful public name for the service. This snippet demonstrates how to export and name a service:
```csharp
[Service(Exported=true, Name="com.xamarin.example.DemoService")]
public class DemoService : Service
{
// Magical code that makes the service do wonderful things.
}
```
The **AndroidManifest.xml** element for this service will then look something like:
```xml
<service android:exported="true" android:name="com.xamarin.example.DemoService" />
```
Services have their own lifecycle with callback methods that are invoked as the service is created. Exactly which methods are invoked depends on the type of service. A started service must implement different lifecycle methods than a bound service, while a hybrid service must implement the callback methods for both a started service and a bound service. These methods are all members of the `Service` class; how the service is started will determine what lifecycle methods will be invoked. These lifecycle methods will be discussed in more detail later.
By default, a service will start in the same process as an Android application. It is possible to start a service in its own process by setting the `ServiceAttribute.IsolatedProcess` property to true:
```csharp
[Service(IsolatedProcess=true)]
public class DemoService : Service
{
// Magical code that makes the service do wonderful things, in it's own process!
}
```
The next step is to examine how to start a service and then move on to examine how to implement the three different types of services.
> [!NOTE]
> A service runs on the UI thread, so if any work is to be performed which blocks the UI, the service must use threads to perform the work.
## Starting A Service
The most basic way to start a service in Android is to dispatch an `Intent` which contains meta-data to help identify which service should be started. There are two different styles of Intents that can be used to start a service:
- **Explicit Intent** – An _explicit Intent_ will identify
exactly what service should be used to complete a given action. An
explicit Intent can be thought of as a letter that has a specific
address; Android will route the intent to the service that is
explicitly identified. This snippet is one example of using an
explicit Intent to start a service called `DownloadService`:
```csharp
// Example of creating an explicit Intent in an Android Activity
Intent downloadIntent = new Intent(this, typeof(DownloadService));
downloadIntent.data = Uri.Parse(fileToDownload);
```
- **Implicit Intent** – This type of Intent loosely identifies
the of action that the user wishes to perform, but the exact service to
complete that action is unknown. An implicit Intent can be thought
of as a letter that is addressed "To Whom It May Concern...".
Android will examine the contents of the Intent, and determine if
there is an existing service which matches the intent.
An _intent filter_ is used to help match the implicit intent with a
registered service. An intent filter is an XML element that is
added to **AndroidManifest.xml** which contains the necessary
meta-data to help match a Service with an implicit intent.
```csharp
Intent sendIntent = new Intent("common.xamarin.DemoService");
sendIntent.Data = Uri.Parse(fileToDownload);
```
If Android has more than one possible match for an implicit intent,
then it may ask the user to select the component to handle the
action:
> [!IMPORTANT]
> Starting in Android 5.0 (AP level 21) an implicit intent cannot be used to start a service.
Where possible, applications should use explicit Intents to start a service. An implicit Intent does not ask for a specific service to start – it is a request for some service installed on the device to handle the request. This ambiguous request can result in the wrong service handling the request or another app needlessly starting (which increases the pressure for resources on the device).
How the Intent is dispatched depends on the type of service and will be discussed in more detail later in the guides specific to each type of service.
### Creating an Intent Filter for Implicit Intents
To associate a service with a implicit Intent, an Android app must provide some meta-data to identify the capabilities of the service. This meta-data is provided by _intent filters_. Intent filters contain some information, such as an action or a type of data, that must be present in an Intent to start a service. In Xamarin.Android, the intent filter is registered in **AndroidManifest.xml** by decorating a service with the [`IntentFilterAttribute`](https://developer.xamarin.com/api/type/Android.App.IntentFilterAttribute/). For example, the following code adds an intent filter with an associated action of `com.xamarin.DemoService`:
```csharp
[Service]
[IntentFilter(new String[]{"com.xamarin.DemoService"})]
public class DemoService : Service
{
}
```
This results in an entry being included in the **AndroidManifest.xml** file – an entry that is packaged with the application in a way analogous to the following example:
```xml
<service android:name="demoservice.DemoService">
<intent-filter>
<action android:name="com.xamarin.DemoService" />
</intent-filter>
</service>
```
With the basics of a Xamarin.Android service out of the way, let's examine the the different subtypes of services in more detail.
## Related Links
- [Android.App.Service](https://developer.xamarin.com/api/type/Android.App.Service/)
- [Android.App.ServiceAttribute](https://developer.xamarin.com/api/type/Android.App.ServiceAttribute/)
- [Android.App.Intent](https://developer.xamarin.com/api/type/Android.Content.Intent/)
- [Android.App.IntentFilterAttribute](https://developer.xamarin.com/api/type/Android.App.IntentFilterAttribute/)
| 51.25 | 639 | 0.77416 | eng_Latn | 0.995972 |
6f70e1751fcc163bc1b9c9a7af55cb3793ef8d3e | 3,496 | markdown | Markdown | website/docs/r/branch_policy_auto_reviewers.html.markdown | Chathuru/terraform-provider-azuredevops | 90ccf9b5c7c6e7a22f3041806ace13e465bf1db9 | [
"MIT"
] | 1 | 2021-05-31T08:07:38.000Z | 2021-05-31T08:07:38.000Z | website/docs/r/branch_policy_auto_reviewers.html.markdown | Chathuru/terraform-provider-azuredevops | 90ccf9b5c7c6e7a22f3041806ace13e465bf1db9 | [
"MIT"
] | 1 | 2021-02-07T15:42:17.000Z | 2021-02-07T15:42:17.000Z | website/docs/r/branch_policy_auto_reviewers.html.markdown | Chathuru/terraform-provider-azuredevops | 90ccf9b5c7c6e7a22f3041806ace13e465bf1db9 | [
"MIT"
] | 1 | 2021-03-17T23:31:56.000Z | 2021-03-17T23:31:56.000Z | ---
layout: "azuredevops"
page_title: "AzureDevops: azuredevops_branch_policy_auto_reviewers"
description: |-
Manages required reviewer policy branch policy within Azure DevOps project.
---
# azuredevops_branch_policy_auto_reviewers
Manages required reviewer policy branch policy within Azure DevOps.
## Example Usage
```hcl
resource "azuredevops_project" "p" {
name = "Sample Project"
}
resource "azuredevops_git_repository" "r" {
project_id = azuredevops_project.p.id
name = "Sample Repo"
initialization {
init_type = "Clean"
}
}
resource "azuredevops_user_entitlement" "user" {
principal_name = "mail@email.com"
account_license_type = "basic"
}
resource "azuredevops_branch_policy_auto_reviewers" "p" {
project_id = azuredevops_project.p.id
enabled = true
blocking = true
settings {
auto_reviewer_ids = [azuredevops_user_entitlement.user.id]
submitter_can_vote = false
message = "Auto reviewer"
path_filters = ["*/src/*.ts"]
scope {
repository_id = azuredevops_git_repository.r.id
repository_ref = azuredevops_git_repository.r.default_branch
match_type = "Exact"
}
}
}
```
## Argument Reference
The following arguments are supported:
- `project_id` - (Required) The ID of the project in which the policy will be created.
- `enabled` - (Optional) A flag indicating if the policy should be enabled. Defaults to `true`.
- `blocking` - (Optional) A flag indicating if the policy should be blocking. Defaults to `true`.
- `settings` - (Required) Configuration for the policy. This block must be defined exactly once.
`settings` block supports the following:
- `auto_reviewer_ids` - (Required) Required reviewers ids. Supports multiples user Ids.
- `path_filters` - (Optional) Filter path(s) on which the policy is applied. Supports absolute paths, wildcards and multiple paths. Example: /WebApp/Models/Data.cs, /WebApp/* or *.cs,/WebApp/Models/Data.cs;ClientApp/Models/Data.cs.
- `submitter_can_vote` - (Optional) Controls whether or not the submitter's vote counts. Defaults to `false`.
- `message` - (Optional) Activity feed message, Message will appear in the activity feed of pull requests with automatically added reviewers.
- `scope` (Required) Controls which repositories and branches the policy will be enabled for. This block must be defined at least once.
`scope` block supports the following:
- `repository_id` - (Optional) The repository ID. Needed only if the scope of the policy will be limited to a single repository.
- `repository_ref` - (Optional) The ref pattern to use for the match. If `match_type` is `Exact`, this should be a qualified ref such as `refs/heads/master`. If `match_type` is `Prefix`, this should be a ref path such as `refs/heads/releases`.
- `match_type` (Optional) The match type to use when applying the policy. Supported values are `Exact` (default) or `Prefix`.
## Attributes Reference
In addition to all arguments above, the following attributes are exported:
- `id` - The ID of branch policy configuration.
## Relevant Links
- [Azure DevOps Service REST API 5.1 - Policy Configurations](https://docs.microsoft.com/en-us/rest/api/azure/devops/policy/configurations/create?view=azure-devops-rest-5.1)
## Import
Azure DevOps Branch Policies can be imported using the project ID and policy configuration ID:
```sh
terraform import azuredevops_branch_policy_auto_reviewers.p aa4a9756-8a86-4588-86d7-b3ee2d88b033/60
```
| 37.591398 | 245 | 0.745709 | eng_Latn | 0.951287 |
6f71063fb0e43b26b9a052b9632cd8791e257a8a | 4,935 | md | Markdown | README.md | mahmouddev/laravel-promocodes | 1cc214f5fa2b97dabd0082d5dead93c009e0da17 | [
"MIT"
] | null | null | null | README.md | mahmouddev/laravel-promocodes | 1cc214f5fa2b97dabd0082d5dead93c009e0da17 | [
"MIT"
] | null | null | null | README.md | mahmouddev/laravel-promocodes | 1cc214f5fa2b97dabd0082d5dead93c009e0da17 | [
"MIT"
] | 1 | 2021-05-18T21:10:48.000Z | 2021-05-18T21:10:48.000Z | # laravel-promocodes
> Updated for Laravel 5.4, works on previous versions too.
[](https://packagist.org/packages/zgabievi/promocodes)
[](https://packagist.org/packages/zgabievi/promocodes)
[](https://packagist.org/packages/zgabievi/promocodes)
[](https://styleci.io/repos/46787184)
[](https://scrutinizer-ci.com/g/zgabievi/laravel-promocodes/?branch=master)
[](https://scrutinizer-ci.com/g/zgabievi/laravel-promocodes/build-status/master)
| PR0M0C0D35 | |
|:----------:|:----|
| [](https://github.com/zgabievi/promocodes) | Promocodes generator for [Laravel 5.*](http://laravel.com/). Trying to make the best package in this category. You are welcome to join the party, give me some advices :tada: and make pull requests. |
## Table of Contents
- [Installation](#installation)
- [Configuration](#configuration)
- [Usage](#usage)
- [License](#license)
## Installation
Install this package via Composer:
```bash
$ composer require zgabievi/promocodes
```
### Open `config/app.php` and follow steps below:
Find the `providers` array and add our service provider.
```php
'providers' => [
// ...
Gabievi\Promocodes\PromocodesServiceProvider::class
],
```
Find the `aliases` array and add our facade.
```php
'aliases' => [
// ...
'Promocodes' => Gabievi\Promocodes\Facades\Promocodes::class
],
```
## Configuration
Publish config & migration file using Artisan command:
```bash
$ php artisan vendor:publish
```
To create table for promocodes in database run:
```bash
$ php artisan migrate
```
> Configuration parameters are well documented. There is no need to describe each parameter here.
> Check `config/promocodes.php` and read comments there if you need.
## Usage
Generate as many codes as you wish and output them without saving.
You will get array of codes in return:
```php
Promocodes::output($amount = 1)
```
Create as many codes as you wish, with same reward for each one.
They will be saved in database and you will get collection of them in return:
```php
Promocodes::create($amount = 1, $reward = null, $rewardType = 'percentage', array $data = [])
```
Check if given code exists and isn't used at all:
```php
Promocodes::check($code)
```
Apply, that given code is used. Update database record. You will get promocode record back or true/false:
```php
Promocodes::apply($code)
```
### Promocodes can be related to users
If you want to use user relation open `app/User.php` and make it `Rewardable` as in example:
```php
namespace App;
use Illuminate\Notifications\Notifiable;
use Gabievi\Promocodes\Traits\Rewardable;
use Illuminate\Foundation\Auth\User as Authenticatable;
class User extends Authenticatable
{
use Notifiable, Rewardable;
// ...
}
```
Get all promocodes of current user:
```php
User::promocodes()
```
> There is query scopes for promocodes: `fresh()`, `byCode($code)`:
> - `User::promocodes()->fresh()` - all not used codes of user
> - `User::promocodes()->byCode($code)` - record which matches given code
Create promocode(s) for current user. Works exactly same like `create` method of `Promocodes`:
```php
User::createCode($amount = 1, $reward = null, $rewardType = 'percentage', array $data = [])
```
Apply, that given code is used by current user.
Second argument is optional, if null, it will return promocode record or boolean, or you can pass callback function, which gives you reward or boolean value as argument:
```php
User::applyCode($code, $callback = null)
```
Example:
```php
$user = Auth::user();
$user->applyCode('ABCD-DCBA', function ($promocode) use ($user) {
return 'Congratulations, ' . $user->name . '! We have added ' . $promocode->reward . ' points on your account'.
});
```
### How to use additional data?
1. Process of creation:
```php
Promocodes::create(1, 25, 'percentage', ['foo' => 'bar', 'baz' => 'qux']);
```
or
```php
User::createCode(1, 25, 'percentage', ['foo' => 'bar', 'baz' => 'qux']);
```
2. Getting data back:
```php
Promocodes::apply('ABC-DEF', function($promocode) {
echo $pomocode->data['foo'];
});
```
or
```php
User::applyCode('ABC-DEF', function($promocode) {
echo $pomocode->data['foo'];
});
```
## License
laravel-promocodes is licensed under a [MIT License](https://github.com/zgabievi/laravel-promocodes/blob/master/LICENSE).
## TODO
- [x] Create tests to check funtionality
| 27.265193 | 297 | 0.708612 | eng_Latn | 0.792665 |
6f7118e1c9d715a318bb3caab77eeec3cc6fa8e1 | 20,778 | md | Markdown | articles/app-service-mobile/TOC.md | DarryStonem/azure-docs.es-es | aa59a5fa09188f4cd2ae772e7818b708e064b1c0 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2017-05-20T17:31:12.000Z | 2017-05-20T17:31:12.000Z | articles/app-service-mobile/TOC.md | DarryStonem/azure-docs.es-es | aa59a5fa09188f4cd2ae772e7818b708e064b1c0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/app-service-mobile/TOC.md | DarryStonem/azure-docs.es-es | aa59a5fa09188f4cd2ae772e7818b708e064b1c0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | # Información general
## [¿Qué es Mobile Apps?](app-service-mobile-value-prop.md)
## [¿Qué es App Service?](../app-service/app-service-value-prop-what-is.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
## [Cómo funciona](../app-service/app-service-how-works-readme.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
## [Planes de App Service](../app-service/azure-web-sites-web-hosting-plans-in-depth-overview.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
# Introducción
## Creación de aplicaciones móviles
### [Android](app-service-mobile-android-get-started.md)
### [Cordova](app-service-mobile-cordova-get-started.md)
### [iOS](app-service-mobile-ios-get-started.md)
### [Windows](app-service-mobile-windows-store-dotnet-get-started.md)
### [Xamarin.Android](app-service-mobile-xamarin-android-get-started.md)
### [Xamarin.Forms](app-service-mobile-xamarin-forms-get-started.md)
### [Xamarin.iOS](app-service-mobile-xamarin-ios-get-started.md)
## Creación de aplicaciones de API
### [.NET](../app-service-api/app-service-api-dotnet-get-started.md)
### [Java](../app-service-api/app-service-api-java-api-app.md)
### [Node.js](../app-service-api/app-service-api-nodejs-api-app.md)
### [CORS](../app-service-api/app-service-api-cors-consume-javascript.md)
## Creación de aplicaciones web
### [.NET](../app-service-web/app-service-web-get-started-dotnet.md)
### [PHP](../app-service-web/app-service-web-get-started-php.md)
### [Node.js](../app-service-web/app-service-web-get-started-nodejs.md)
### [Java](../app-service-web/app-service-web-get-started-java.md)
### [Python](../app-service-web/app-service-web-get-started-python.md)
### [HTML](../app-service-web/app-service-web-get-started-html.md)
# Procedimientos
## Planeamiento y diseño
### [Autenticación y autorización en Azure Mobile Apps](app-service-mobile-auth.md)
### [Sincronización de datos sin conexión en Azure Mobile Apps](app-service-mobile-offline-data-sync.md)
### [Procedimientos recomendados para Azure App Service](../app-service-web/app-service-best-practices.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Azure App Service y los servicios de Azure existentes](../app-service-web/app-service-changes-existing-services.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Información detallada de los planes de App Service](../app-service/azure-web-sites-web-hosting-plans-in-depth-overview.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Hospedaje de alta densidad](../app-service/app-service-high-density-hosting.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Uso de WebJobs en Azure App Service](../app-service/app-service-webjobs-readme.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Entorno de App Service](../app-service-web/app-service-app-service-environment-intro.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Documentación del entorno de App Service](../app-service/app-service-app-service-environments-readme.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
## Desarrollo
### Android
#### [Habilitar la sincronización sin conexión](app-service-mobile-android-get-started-offline-data.md)
#### [Adición de autenticación](app-service-mobile-android-get-started-users.md)
#### [Adición de notificaciones de inserción](app-service-mobile-android-get-started-push.md)
#### [Trabajar con el SDK de cliente](app-service-mobile-android-how-to-use-client-library.md)
### Cordova
#### [Habilitar la sincronización sin conexión](app-service-mobile-cordova-get-started-offline-data.md)
#### [Adición de autenticación](app-service-mobile-cordova-get-started-users.md)
#### [Adición de notificaciones de inserción](app-service-mobile-cordova-get-started-push.md)
#### Trabajar con el SDK de cliente
##### [Cordova](app-service-mobile-cordova-how-to-use-client-library.md)
##### [JavaScript/HTML](app-service-mobile-html-how-to-use-client-library.md)
### iOS
#### [Habilitar la sincronización sin conexión](app-service-mobile-ios-get-started-offline-data.md)
#### [Adición de autenticación](app-service-mobile-ios-get-started-users.md)
#### [Adición de notificaciones de inserción](app-service-mobile-ios-get-started-push.md)
#### [Trabajar con el SDK de cliente](app-service-mobile-ios-how-to-use-client-library.md)
### Windows
#### [Habilitar la sincronización sin conexión](app-service-mobile-windows-store-dotnet-get-started-offline-data.md)
#### [Adición de autenticación](app-service-mobile-windows-store-dotnet-get-started-users.md)
#### [Adición de notificaciones de inserción](app-service-mobile-windows-store-dotnet-get-started-push.md)
#### [Trabajar con el SDK de cliente](app-service-mobile-dotnet-how-to-use-client-library.md)
### Xamarin.Android
#### [Habilitar la sincronización sin conexión](app-service-mobile-xamarin-android-get-started-offline-data.md)
#### [Adición de autenticación](app-service-mobile-xamarin-android-get-started-users.md)
#### [Adición de notificaciones de inserción](app-service-mobile-xamarin-android-get-started-push.md)
#### [Trabajar con el SDK de cliente](app-service-mobile-dotnet-how-to-use-client-library.md)
### Xamarin.Forms
#### [Habilitar la sincronización sin conexión](app-service-mobile-xamarin-forms-get-started-offline-data.md)
#### [Adición de autenticación](app-service-mobile-xamarin-forms-get-started-users.md)
#### [Adición de notificaciones de inserción](app-service-mobile-xamarin-forms-get-started-push.md)
#### [Trabajar con el SDK de cliente](app-service-mobile-dotnet-how-to-use-client-library.md)
### Xamarin.iOS
#### [Habilitar la sincronización sin conexión](app-service-mobile-xamarin-ios-get-started-offline-data.md)
#### [Adición de autenticación](app-service-mobile-xamarin-ios-get-started-users.md)
#### [Adición de notificaciones de inserción](app-service-mobile-xamarin-ios-get-started-push.md)
#### [Trabajar con el SDK de cliente](app-service-mobile-dotnet-how-to-use-client-library.md)
### Trabajar con el SDK de servidor
#### [Back-end de .NET](app-service-mobile-dotnet-backend-how-to-use-server-sdk.md)
#### [Back-end de Node.js](app-service-mobile-node-backend-how-to-use-server-sdk.md)
#### [Control de versiones de cliente y servidor](app-service-mobile-client-and-server-versioning.md)
### WebJobs
#### [Qué es el SDK de WebJobs de Azure](../app-service-web/websites-dotnet-webjobs-sdk.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Creación de un WebJob .NET en Azure App Service](../app-service-web/websites-dotnet-webjobs-sdk-get-started.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Uso del almacenamiento de blobs de Azure con el SDK de WebJobs](../app-service-web/websites-dotnet-webjobs-sdk-storage-blobs-how-to.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Uso del almacenamiento de colas de Azure con el SDK de WebJobs](../app-service-web/websites-dotnet-webjobs-sdk-storage-queues-how-to.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Uso de Azure Service Bus con el SDK de WebJobs](../app-service-web/websites-dotnet-webjobs-sdk-service-bus.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Uso del almacenamiento de tablas de Azure con el SDK de WebJobs](../app-service-web/websites-dotnet-webjobs-sdk-storage-tables-how-to.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### Entorno de App Service
#### [Creación de una aplicación web en un entorno de App Service](../app-service-web/app-service-web-how-to-create-a-web-app-in-an-ase.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Creación de un ASE de un ILB mediante las plantillas de Azure Resource Manager](../app-service-web/app-service-app-service-environment-create-ilb-ase-resourcemanager.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Uso de un equilibrador de carga interno](../app-service-web/app-service-environment-with-internal-load-balancer.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
## [Implementación](../app-service/app-service-deployment-readme.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Implementación en App Service](../app-service-web/web-sites-deploy.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Implementación de sincronización en la nube](../app-service-web/app-service-deploy-content-sync.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Implementación continua](../app-service-web/app-service-continuous-deployment.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Entornos de ensayo](../app-service-web/web-sites-staged-publishing.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Implementación desde un repositorio Git local](../app-service-web/app-service-deploy-local-git.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Implementación de WebJobs con Visual Studio](../app-service-web/websites-dotnet-deploy-webjobs.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
## [Escala](../app-service/app-service-scale-readme.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Escalado vertical de una aplicación](../app-service-web/web-sites-scale.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Entorno de App Service](../app-service/app-service-app-service-environments-readme.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Escala distribuida geográficamente con entornos de App Service](../app-service-web/app-service-app-service-environment-geo-distributed-scale.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Escalado de aplicaciones en un entorno de App Service](../app-service-web/app-service-web-scale-a-web-app-in-an-app-service-environment.md)
#### [Escalado automático de aplicaciones en un entorno de App Service](../app-service/app-service-environment-auto-scale.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
## Administrar
### [Configuración](../app-service-web/web-sites-configure.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### Dominios personalizados
#### [Compra y configuración de dominios personalizados](../app-service-web/custom-dns-web-site-buydomains-web-app.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Asignación de su propio dominio personalizado](../app-service-web/web-sites-custom-domain-name.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Configuración de dominios GoDaddy](../app-service-web/web-sites-godaddy-custom-domain-name.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Dominios personalizados con Traffic Manager](../app-service-web/web-sites-traffic-manager-custom-domain-name.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Clonación de una aplicación existente](../app-service-web/app-service-web-app-cloning-portal.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Conexiones locales](../app-service-web/web-sites-hybrid-connection-get-started.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Azure Virtual Network](../app-service-web/web-sites-integrate-with-vnet.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Configuración avanzada](../app-service-web/web-sites-transform-extend.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Grupos de recursos](../app-service-web/app-service-move-resources.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [WebJobs](../app-service/app-service-webjobs-readme.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Ejecución de tareas en segundo plano con WebJobs](../app-service-web/web-sites-create-web-jobs.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Entorno de App Service](../app-service/app-service-app-service-environments-readme.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Configuración](../app-service-web/app-service-web-configure-an-app-service-environment.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Opciones de configuración personalizadas](../app-service-web/app-service-app-service-environment-custom-settings.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Control del tráfico entrante](../app-service-web/app-service-app-service-environment-control-inbound-traffic.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Introducción a la arquitectura de red](../app-service-web/app-service-app-service-environment-network-architecture-overview.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Detalles de configuración de red con ExpressRoute](../app-service-web/app-service-app-service-environment-network-configuration-expressroute.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
## Migrar
### [¿En qué se diferencia App Service de Mobile Services?](app-service-mobile-value-prop-migration-from-mobile-services.md)
### [Migrar un servicio móvil existente a App Service](app-service-mobile-migrating-from-mobile-services.md)
### Actualizar un servicio móvil existente a App Service
#### [Back-end de .NET](app-service-mobile-net-upgrading-from-mobile-services.md)
#### [Back-end de Node.js](app-service-mobile-node-backend-upgrading-from-mobile-services.md)
## [Protección](../app-service/app-service-security-readme.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Protección de una aplicación en Azure App Service](../app-service-web/web-sites-security.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Autenticación y autorización](../app-service/app-service-authentication-overview.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### Autenticación con proveedores de identidades
#### [Autenticación con Azure Active Directory](app-service-mobile-how-to-configure-active-directory-authentication.md)
#### [Autenticación con Facebook](app-service-mobile-how-to-configure-facebook-authentication.md)
#### [Autenticación con Google](app-service-mobile-how-to-configure-google-authentication.md)
#### [Autenticación con cuenta Microsoft](app-service-mobile-how-to-configure-microsoft-authentication.md)
#### [Autenticación con Twitter](app-service-mobile-how-to-configure-twitter-authentication.md)
### [Autenticación con la implementación local de Active Directory](../app-service-web/web-sites-authentication-authorization.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### HTTPS
#### [Configuración de la autenticación mutua TLS](../app-service-web/app-service-web-configure-tls-mutual-auth.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Compra de un certificado SSL en Azure](../app-service-web/web-sites-purchase-ssl-web-site.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Uso de un certificado SSL obtenido en otra parte](../app-service-web/web-sites-configure-ssl-certificate.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### Protección de un entorno de App Service
#### [Configuración de un firewall de aplicación web](../app-service-web/app-service-app-service-environment-web-application-firewall.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Implementación de una arquitectura de seguridad por niveles](../app-service-web/app-service-app-service-environment-layered-security.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Conexión de forma segura con recursos de back-end](../app-service-web/app-service-app-service-environment-securely-connecting-to-backend-resources.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
## Backup
### [Realizar una copia de seguridad de la aplicación en Azure](../app-service-web/web-sites-backup.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Restaurar una aplicación en Azure](../app-service-web/web-sites-restore.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Usar REST para realizar una copia de seguridad y restaurar las aplicaciones de App Service](../app-service-web/websites-csm-backup.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
## [Supervisión](../app-service-web/web-sites-monitor.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Habilitación del registro de diagnósticos](../app-service-web/web-sites-enable-diagnostic-log.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Solución de problemas con Visual Studio](../app-service-web/web-sites-dotnet-troubleshoot-visual-studio.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
## Automatizar
### [Desarrollo ágil](../app-service-web/app-service-agile-software-development.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Implementación de Azure Resource Manager](../app-service-web/app-service-deploy-complex-application-predictably.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Web y GitHub](../app-service-web/app-service-web-arm-from-github-provision.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Web y SQL](../app-service-web/app-service-web-arm-with-sql-database-provision.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [MSDeploy con un nombre de host personalizado y un certificado SSL](../app-service-web/app-service-web-arm-with-msdeploy-provision.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### PowerShell
#### [Automatización de la copia de seguridad y restauración](../app-service/app-service-powershell-backup.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Clonación de aplicaciones](../app-service-web/app-service-web-app-cloning.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Enlace con certificados SSL](../app-service-web/app-service-web-app-powershell-ssl-binding.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
#### [Uso de Azure Resource Manager con PowerShell](../app-service-web/app-service-web-app-azure-resource-manager-powershell.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Administración de aplicaciones con Azure Automation](../app-service-web/automation-manage-web-app.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
## Integrate
### [Acceso a recursos locales mediante conexiones híbridas](../app-service-web/web-sites-hybrid-connection-get-started.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Envío de correos electrónicos mediante SendGrid con Azure](../app-service-web/sendgrid-dotnet-how-to-send-email.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
## Solución de problemas
### Solución de problemas generales de Mobile Apps
#### [Back-end de .NET](app-service-mobile-dotnet-backend-how-to-use-server-sdk.md#how-to-debug-and-troubleshoot-the-net-server-sdk)
#### [Back-end de Node.js](app-service-mobile-node-backend-how-to-use-server-sdk.md#Debugging)
### [Habilitación del registro de diagnósticos](../app-service-web/web-sites-enable-diagnostic-log.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Registros de streaming y la consola](../app-service-web/web-sites-streaming-logs-and-console.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
### [Solución de problemas con Visual Studio](../app-service-web/web-sites-dotnet-troubleshoot-visual-studio.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
# Referencia
## [SDK del back-end de .NET](https://msdn.microsoft.com/library/azure/dn961176.aspx)
## [SDK del back-end de Node.js](https://azure.github.io/azure-mobile-apps-node/)
## [SDK de cliente de Android](https://azure.github.io/azure-mobile-apps-android-client/)
## [SDK de cliente de iOS](https://azure.github.io/azure-mobile-apps-ios-client/)
## [SDK de cliente de JavaScript/Cordova](https://azure.github.io/azure-mobile-apps-js-client/)
## [SDK de cliente de Windows/Xamarin](https://msdn.microsoft.com/library/azure/mt419521.aspx)
# Temas relacionados
## [Repositorios de GitHub](https://github.com/Azure/azure-mobile-apps)
## [Portal de Azure](../app-service-web/app-service-web-app-azure-portal.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
# Recursos
## [Precios](https://azure.microsoft.com/en-us/pricing/details/app-service/)
## [Foro de MSDN](https://social.msdn.microsoft.com/forums/azure/home?forum=azuremobile)
## [Stack Overflow](http://stackoverflow.com/questions/tagged/azure-mobile-services)
## [Vídeos](https://azure.microsoft.com/documentation/videos/index/?services=mobile-services)
## Muestras
### [Ingeniero de campo](https://azure.microsoft.com/resources/samples/app-service-mobile-dotnet-fieldengineer/)
### [Sincronización de datos estructurados](https://azure.microsoft.com/resources/samples/app-service-mobile-dotnet-todo-list-files/)
### Guía de inicio rápido completada
#### [Windows](https://azure.microsoft.com/resources/samples/app-service-mobile-windows-quickstart/)
#### [Xamarin.Android](https://azure.microsoft.com/resources/samples/app-service-mobile-xamarin-android-quickstart/)
#### [Back-end de .NET](https://azure.microsoft.com/resources/samples/app-service-mobile-dotnet-backend-quickstart/)
#### [Back-end de Node.js](https://azure.microsoft.com/resources/samples/app-service-mobile-nodejs-backend-quickstart/)
## [Actualizaciones del servicio](https://azure.microsoft.com/updates/?product=mobile-services)
## [Procedimientos recomendados de App Service](../app-service-web/app-service-best-practices.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
## [Lista de recursos de WebJobs](../app-service-web/websites-webjobs-resources.md?toc=%2fazure%2fapp-service-mobile%2ftoc.json)
| 87.302521 | 220 | 0.766724 | spa_Latn | 0.201279 |
6f7132ec736e002a90d108ce63907d2fec2c30c4 | 11,672 | md | Markdown | articles/active-directory/identity-protection/reference-identity-protection-glossary.md | matmahnke/azure-docs.pt-br | 6c96d25caf8663547775f333164198e3ed03972f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/identity-protection/reference-identity-protection-glossary.md | matmahnke/azure-docs.pt-br | 6c96d25caf8663547775f333164198e3ed03972f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/identity-protection/reference-identity-protection-glossary.md | matmahnke/azure-docs.pt-br | 6c96d25caf8663547775f333164198e3ed03972f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Glossário do Azure Active Directory Identity Protection
description: Glossário do Azure Active Directory Identity Protection
services: active-directory
ms.service: active-directory
ms.subservice: identity-protection
ms.topic: reference
ms.date: 10/18/2019
ms.author: joflore
author: MicrosoftGuyJFlo
manager: daveba
ms.reviewer: sahandle
ms.collection: M365-identity-device-management
ms.openlocfilehash: 1a17f52e519a84c58c9ed5b75259cc0b96d0a175
ms.sourcegitcommit: 829d951d5c90442a38012daaf77e86046018e5b9
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 10/09/2020
ms.locfileid: "88949167"
---
# <a name="azure-active-directory-identity-protection-glossary"></a>Glossário do Azure Active Directory Identity Protection
### <a name="at-risk-user"></a>Em risco (Usuário)
Um usuário com uma ou mais detecções de risco ativas.
### <a name="atypical-sign-in-location"></a>Local de entrada atípico
Uma entrada de um local geográfico incomum para o usuário específico, usuários semelhantes ou o locatário.
### <a name="azure-ad-identity-protection"></a>Azure AD Identity Protection
Um módulo de segurança do Azure Active Directory que fornece uma visão consolidada das detecções de risco e das possíveis vulnerabilidades que afetam as identidades de uma organização.
### <a name="conditional-access"></a>Acesso condicional
Uma política para proteger o acesso aos recursos. As regras de acesso condicional são armazenadas no Azure Active Directory e são avaliadas pelo Azure AD antes de conceder acesso ao recurso. As regras de exemplo incluem restrição baseada na localização do usuário, integridade do dispositivo ou método de autenticação do usuário.
### <a name="credentials"></a>Credenciais
Informações que incluem a identificação e prova de identificação usadas para obter acesso ao local e aos recursos da rede. Exemplos de credenciais são nomes de usuário e senhas, cartões inteligentes e certificados.
### <a name="event"></a>Evento
Um registro de uma atividade no Azure Active Directory.
### <a name="false-positive-risk-detection"></a>Falso-positivo (detecção de risco)
Um status de detecção de risco definido manualmente por um usuário de proteção de identidade, indicando que a detecção de risco foi investigada e foi sinalizada incorretamente como uma detecção de risco.
### <a name="identity"></a>Identidade
Uma pessoa ou entidade que deve ser verificada por meio de autenticação com base em critérios como senha ou certificado.
### <a name="identity-risk-detection"></a>Detecção de risco de identidade
Evento do Azure AD que foi sinalizado como anômala pela proteção de identidade e pode indicar que uma identidade foi comprometida.
### <a name="ignored-risk-detection"></a>Ignorado (detecção de risco)
Um status de detecção de risco definido manualmente por um usuário de proteção de identidade, indicando que a detecção de risco está fechada sem realizar uma ação de correção.
### <a name="impossible-travel-from-atypical-locations"></a>Viagem impossível de locais atípicos
Uma detecção de risco disparada quando duas entradas para o mesmo usuário são detectadas, em que pelo menos uma delas é de um local de entrada do atípicos e onde o tempo entre as entradas é menor do que o tempo mínimo necessário para viajar fisicamente entre esses locais.
### <a name="investigation"></a>Investigação
O processo de revisar as atividades, os logs e outras informações relevantes relacionadas a uma detecção de risco para decidir se as etapas de correção ou mitigação são necessárias, entender se e como a identidade foi comprometida e entender como a identidade comprometida foi usada.
### <a name="leaked-credentials"></a>Credenciais vazadas
Uma detecção de risco disparada quando as credenciais do usuário atual (nome de usuário e senha) são encontradas publicadas publicamente na Web escura por nossos pesquisadores.
### <a name="mitigation"></a>Atenuação
Uma ação que visa limitar ou eliminar a capacidade de um invasor explorar uma identidade ou um dispositivo comprometidos sem restaurá-los para um estado seguro. Uma mitigação não resolve as detecções de riscos anteriores associadas à identidade ou ao dispositivo.
### <a name="multi-factor-authentication"></a>Autenticação multifator
Um método de autenticação que exige dois ou mais métodos de autenticação, que podem incluir algo que o usuário tem, como um certificado; algo que o usuário conhece, como nomes de usuário, senhas ou frases secretas; atributos físicos, como uma impressão digital; e atributos pessoais, como uma assinatura pessoal.
### <a name="offline-detection"></a>Detecção offline
A detecção de anomalias e a avaliação do risco de um evento, tal como uma tentativa de entrada após o ocorrido, para um evento que já aconteceu.
### <a name="policy-condition"></a>Condição da política
Uma parte de uma política de segurança que define as entidades (grupos, usuários, aplicativos, plataformas de dispositivos, Estados de dispositivo, intervalos de IP e tipos de cliente) incluídas na política ou excluídas dela.
### <a name="policy-rule"></a>Regra de política
A parte de uma política de segurança que descreve as circunstâncias que dispararia a política e as ações tomadas quando a política é disparada.
### <a name="prevention"></a>Prevenção
Uma ação para evitar danos à organização por abuso de uma identidade ou dispositivo que sofreu comprometimento conhecido ou suspeito. Uma ação de prevenção não protege o dispositivo ou a identidade e não resolve as detecções de riscos anteriores.
### <a name="privileged-user"></a>Privilegiado (usuário)
Um usuário que, no momento de uma detecção de risco, tinha permissões de administrador permanentes ou temporárias para um ou mais recursos no Azure Active Directory, como um administrador global, administrador de cobrança, administrador de serviços, administrador de usuários e administrador de senha.
### <a name="real-time"></a>Tempo real
Consulte Detecção em tempo real.
### <a name="real-time-detection"></a>Detecção em tempo real.
A detecção de anomalias e a avaliação do risco de um evento, tal como uma tentativa de entrada antes de permitir que o evento prossiga.
### <a name="remediated-risk-detection"></a>Corrigido (detecção de risco)
Um status de detecção de risco definido automaticamente pela proteção de identidade, indicando que a detecção de risco foi corrigida usando a ação de correção padrão para esse tipo de detecção de risco. Por exemplo, quando a senha do usuário é redefinida, muitas detecções de risco que indicam que a senha anterior foi comprometida são automaticamente corrigidas.
### <a name="remediation"></a>Remediação
Uma ação que visa proteger uma identidade ou um dispositivo que sofreu comprometimento conhecido ou suspeito anteriormente. Uma ação de correção restaura a identidade ou o dispositivo para um estado seguro e resolve as detecções de risco anteriores associadas à identidade ou ao dispositivo.
### <a name="resolved-risk-detection"></a>Resolvido (detecção de risco)
Um status de detecção de risco definido manualmente por um usuário de proteção de identidade, indicando que o usuário realizou uma ação de correção apropriada fora da proteção de identidade e que a detecção de risco deve ser considerada fechada.
### <a name="risk-detection-status"></a>Status de detecção de risco
Uma propriedade de uma detecção de risco, que indica se o evento está ativo e, se fechado, o motivo para fechá-lo.
### <a name="risk-detection-type"></a>Tipo de detecção de risco
Uma categoria para a detecção de risco, que indica o tipo de anomalia que fez com que o evento fosse considerado arriscado.
### <a name="risk-level-risk-detection"></a>Nível de risco (detecção de risco)
Uma indicação (alta, média ou baixa) da severidade da detecção de risco para ajudar os usuários de proteção de identidade a priorizar as ações que eles levam para reduzir o risco para sua organização.
### <a name="risk-level-sign-in"></a>Nível de risco (entrada)
Uma indicação (Alta, Média ou Baixa) da probabilidade de que outra pessoa esteja tentando usar a identidade do usuário para uma entrada específica.
### <a name="risk-level-user-compromise"></a>Nível de risco (comprometimento do usuário)
Uma indicação (Alta, Média ou Baixa) da probabilidade de uma identidade ter sido comprometida.
### <a name="risk-level-vulnerability"></a>Nível de risco (vulnerabilidade)
Uma indicação (Alta, Média ou Baixa) da severidade da vulnerabilidade para ajudar os usuários do Identity Protection a priorizar as ações tomadas para reduzir o risco para a organização.
### <a name="secure-identity"></a>Proteger (identidade)
Realizar uma ação de correção como uma alteração de senha ou reimplantação da imagem no computador para restaurar uma identidade potencialmente comprometida para um estado não comprometido.
### <a name="security-policy"></a>Política de segurança
Uma coleção de regras e condição da política. Uma política pode ser aplicada a entidades como usuários, grupos, aplicativos, dispositivos, plataformas de dispositivos, estados de dispositivo, intervalos de IP e tipos de cliente do Auth2.0. Quando uma política está habilitada, ela é avaliada sempre que um token para um recurso é emitido para uma entidade incluída na política.
### <a name="sign-in-v"></a>Entrar (v)
Autenticar-se em uma identidade no Azure Active Directory.
### <a name="sign-in-n"></a>Entrada (n)
O processo ou a ação de autenticar uma identidade no Azure Active Directory e o evento que captura essa operação.
### <a name="sign-in-from-anonymous-ip-address"></a>Entrada de um endereço IP anônimo
Uma detecção de risco disparada após uma entrada bem-sucedida do endereço IP que foi identificada como um endereço IP de proxy anônimo.
### <a name="sign-in-from-infected-device"></a>Entrada de um dispositivo infectado
Uma detecção de risco disparada quando uma entrada é originada de um endereço IP, que é conhecido por ser usado por um ou mais dispositivos comprometidos, que estão ativamente tentando se comunicar com um servidor de bot.
### <a name="sign-in-from-ip-address-with-suspicious-activity"></a>Entrada de um endereço IP com atividade suspeita
Uma detecção de risco disparada após uma entrada bem-sucedida de um endereço IP com um número alto de tentativas de logon com falha em várias contas de usuário em um curto período de tempo.
### <a name="sign-in-from-unfamiliar-location"></a>Entrada de um local desconhecido
Uma detecção de risco disparada quando um usuário entra com êxito de um novo local (IP, latitude/longitude e ASN).
### <a name="sign-in-risk"></a>Risco de entrada
Consulte Nível de risco (entrada)
### <a name="sign-in-risk-policy"></a>Política de risco de entrada
Uma política de acesso condicional que avalia o risco para uma entrada específica e aplica mitigações com base em condições e regras predefinidas.
### <a name="user-compromise-risk"></a>Risco de comprometimento do usuário
Consulte Nível de risco (comprometimento do usuário)
### <a name="user-risk"></a>Risco do usuário
Consulte Nível de risco (comprometimento do usuário).
### <a name="user-risk-policy"></a>Política de risco do usuário
Uma política de acesso condicional que considera a entrada e aplica mitigações com base em condições e regras predefinidas.
### <a name="users-flagged-for-risk"></a>Usuários sinalizados por risco
Usuários que têm detecções de risco, que são ativas ou corrigidas
### <a name="vulnerability"></a>Vulnerabilidade
Uma configuração ou condição no Azure Active Directory que torna o diretório suscetível a vulnerabilidades ou ameaças.
## <a name="see-also"></a>Confira também
- [Azure Active Directory Identity Protection](./overview-identity-protection.md) | 71.607362 | 377 | 0.789154 | por_Latn | 0.99992 |
6f72cc78834af4b67789debfbbd3f34beac14013 | 2,570 | md | Markdown | README.md | yzhbankov/express-request-limiter | 8af013dba6e4051fd47843dfa91f4b0741c480b8 | [
"MIT"
] | null | null | null | README.md | yzhbankov/express-request-limiter | 8af013dba6e4051fd47843dfa91f4b0741c480b8 | [
"MIT"
] | 2 | 2019-11-06T07:57:59.000Z | 2019-11-10T15:04:08.000Z | README.md | yzhbankov/express-request-limiter | 8af013dba6e4051fd47843dfa91f4b0741c480b8 | [
"MIT"
] | null | null | null | ## Express request-limiter
Request limiting middleware for Express applications
``` sh
npm install express-request-limiter --save
```
## Usage
### Globally on application
``` js
var express = require('express');
var RequestLimiter = require('express-request-limiter');
var app = express();
const requestLimiter = RequestLimiter({
maxRequests: 10,
headers: true,
routesList: [{ path: '/api/first', method: 'GET' }, { path: '/api/second', method: 'PUT' }],
});
app.use(requestLimiter);
app.get('/api/first', function (req, res) {
res.send(200, 'ok')
})
```
### Separately on each route
``` js
var express = require('express');
var RequestLimiter = require('express-request-limiter');
var app = express();
const requestLimiter = RequestLimiter({
maxRequests: 10,
global: false,
headers: true
});
``` js
app.get('/user/first', requestLimiter, function (req, res) {
// request logic
...
})
```
### API options
``` js
RequestLimiter(options)
```
- `maxRequests`: `Number` the number of maximum concurrent requests at a time. Default to 10.
- `routesList`: `Array` the list of objects that are specify router path and method which are will
be monitored.
- `routesList.path`: `String` router path.
- `routesList.method`: `String` request method.
- `global`: `Boolean` the flag that is indicates do the limiter will be global or local for an
application. Default to `true`.
- `headers`: `Boolean` the flag that enable headers for request limit (X-RequestLimit-Limit)
and current usage (X-RequestLimit-Usage) on all responses. Default to `true`.
- `message`: `String` the error message sent to user when `maxRequests` is exceeded.
Defaults to 'Too many requests, please try again later.'
- `statusCode`: `Number` HTTP status code returned when `maxRequests` is exceeded.
Defaults to 429.
- `skip`: `Function` the function used to skip (whitelist) requests.
Returning true from the function will skip limiting for that request.
Defaults to always false (count all requests):
``` js
function (/*req, res*/) {
return false;
}
```
- `handler`: The function to handle requests once the `maxRequests` limit is exceeded. It receives the request and the response objects.
The "next" param is available if you need to pass to the next middleware.
Defaults to:
``` js
function (req, res, /*next*/) {
res.status(options.statusCode).send(options.message);
}
```
- `onRateLimited`: `Function` called when a request exceeds the configured rate limit.
## License MIT
MIT © Iaroslav Zhbankov
| 27.340426 | 137 | 0.69572 | eng_Latn | 0.913245 |
6f73668e734332d0bb30e7d3af71e2827d599f87 | 946 | md | Markdown | technical-reference/msbts-hostqueue-hostname-property-wmi.md | cmcclister/biztalk-docs | 36a3d4b944e27edff883b8e36e997c7d2af4f497 | [
"CC-BY-4.0",
"MIT"
] | 37 | 2017-08-28T06:57:52.000Z | 2021-07-13T12:16:23.000Z | technical-reference/msbts-hostqueue-hostname-property-wmi.md | cmcclister/biztalk-docs | 36a3d4b944e27edff883b8e36e997c7d2af4f497 | [
"CC-BY-4.0",
"MIT"
] | 732 | 2017-05-18T22:16:15.000Z | 2022-03-31T23:10:06.000Z | technical-reference/msbts-hostqueue-hostname-property-wmi.md | isabella232/biztalk-docs | 36a3d4b944e27edff883b8e36e997c7d2af4f497 | [
"CC-BY-4.0",
"MIT"
] | 158 | 2017-06-19T22:47:52.000Z | 2022-02-28T06:41:54.000Z | ---
description: "Learn more about: MSBTS_HostQueue.HostName Property (WMI)"
title: MSBTS_HostQueue.HostName Property (WMI)
TOCTitle: MSBTS_HostQueue.HostName Property (WMI)
ms:assetid: 5e1d8796-ded8-405f-863a-510af0243c9b
ms:mtpsurl: https://msdn.microsoft.com/library/Aa560402(v=BTS.80)
ms:contentKeyID: 51528355
ms.date: 08/30/2017
mtps_version: v=BTS.80
---
# MSBTS\_HostQueue.HostName Property (WMI)
Contains the name of the host that this queue corresponds to.
> [!NOTE]
> <P>The syntax shown is language neutral.</P>
## Syntax
```C#
string HostName;
```
## Remarks
This property is read-only.
This property has a **Key** qualifier. Along with **MgmtDbNameOverride** and **MgmtDbServerOverride**, this key forms a compound key for the class.
The maximum length for this property is 80 characters.
## Requirements
**Header:** Declared in BTSWMISchemaXP.mof.
**Namespace:** Included in \\root\\MicrosoftBizTalkServer.
| 21.022222 | 147 | 0.745243 | eng_Latn | 0.711668 |
6f74da6e56315f0301e9a17cb4341606acdab121 | 2,133 | md | Markdown | _posts/2021-05-31-The-Central-Premise.md | trcmohitmandokhot/w3mohit | 4b334c85d9dc6e35064966bb69fa170c678a6071 | [
"MIT"
] | null | null | null | _posts/2021-05-31-The-Central-Premise.md | trcmohitmandokhot/w3mohit | 4b334c85d9dc6e35064966bb69fa170c678a6071 | [
"MIT"
] | null | null | null | _posts/2021-05-31-The-Central-Premise.md | trcmohitmandokhot/w3mohit | 4b334c85d9dc6e35064966bb69fa170c678a6071 | [
"MIT"
] | null | null | null | ---
layout: posts
author: Mohit Mandokhot
---
*Is there a link between operation of Autonomous Vehicles and the operating environment around it?
What is the role of infrastructure elements in AV operations?*
<!-- excerpt-end -->
**AVs and the Environment: Bi-directional Influence**
The performance of Autonomous Vehicles (AV) is influenced by the environment around them.
SAE J3016[^1] defines six levels of driving automation. SAE Automation Levels 1 to 5 can be collectively grouped under the term Driving Automation Systems. Application of mental models such as the Sense, Plan, and Act Framework, can help us explain the behavior of a Driving Automation System.
The environment around an AV may consist of a variety of objects, each with characteristics that are static or change. Modeling the environment in terms of objects and characteristics is a technique that aids in classification of the environment around an AV. For example, an object like the roadway can have a characteristic like geometry, which is static in nature. Speed (characteristic) of a particular vehicle (object) driving in an adjacent lane can change during the period of observation.
The AV senses its operation environment. It gathers and processes information to produce a plan that can satisfy its goals. Next, the AV acts on the plan. The actions performed by AV change the driving environment around it.
On seeing a vehicle change lanes in front of it, drivers may slow down to maintain safe following distance. Also, other elements of the environment may also respond to the presence and actions of an AV. For example, if an emergency autonomous vehicle needs right of way through the intersection, the traffic controller may change its mode to adapt to most critical needs.
Hence, there exists a bi-directional nature of influence between the AVs and its operating environment.
**References**
[^1]: SAE International. (2021). *Taxonomy and Definitions for Terms Related to Driving Automation Systems for On-Road Motor Vehicles* (SAE J3016_202104). Retrieved from https://www.sae.org/standards/content/j3016_202104/
| 76.178571 | 498 | 0.79278 | eng_Latn | 0.999012 |
6f758aa01dbbeb8f8beacbfbf80d6f64cf79f828 | 197 | md | Markdown | repository/MethodsDefiner-Core.package/MdAccessorMutatorDefiner.class/README.md | mumez/MethodsDefiner | 0b3528949bdce0c26cfec772fcd3bd3ee4481ff2 | [
"MIT"
] | null | null | null | repository/MethodsDefiner-Core.package/MdAccessorMutatorDefiner.class/README.md | mumez/MethodsDefiner | 0b3528949bdce0c26cfec772fcd3bd3ee4481ff2 | [
"MIT"
] | null | null | null | repository/MethodsDefiner-Core.package/MdAccessorMutatorDefiner.class/README.md | mumez/MethodsDefiner | 0b3528949bdce0c26cfec772fcd3bd3ee4481ff2 | [
"MIT"
] | null | null | null | I build accessors and mutators for classes( or metaclasses).
By using #extraAccessorBlock:, I provide a simple hook for custmizing code generation.
#creator
[:masashi | ^umezawa]
#version 0.4
| 19.7 | 86 | 0.761421 | eng_Latn | 0.958436 |
6f762d25f974b7c5eddb0aad8916bec7a7c95302 | 1,241 | md | Markdown | api/wrappers/jsp/radialgauge/scale-majorticks.md | colinvo/kendo-docs | 7adfa37886ec90fca3544d47abd5f76422497da1 | [
"Unlicense",
"MIT"
] | 1 | 2016-02-03T10:15:54.000Z | 2016-02-03T10:15:54.000Z | api/wrappers/jsp/radialgauge/scale-majorticks.md | colinvo/kendo-docs | 7adfa37886ec90fca3544d47abd5f76422497da1 | [
"Unlicense",
"MIT"
] | null | null | null | api/wrappers/jsp/radialgauge/scale-majorticks.md | colinvo/kendo-docs | 7adfa37886ec90fca3544d47abd5f76422497da1 | [
"Unlicense",
"MIT"
] | null | null | null | ---
title: radialGauge-scale-majorTicks
slug: jsp-radialGauge-scale-majorTicks
tags: api, java
publish: true
---
# \<kendo:radialGauge-scale-majorTicks\>
Configures the scale major ticks.
#### Example
<kendo:radialGauge-scale>
<kendo:radialGauge-scale-majorTicks></kendo:radialGauge-scale-majorTicks>
</kendo:radialGauge-scale>
## Configuration Attributes
### color `java.lang.String`
The color of the major ticks.
#### Example
<kendo:radialGauge-scale-majorTicks color="color">
</kendo:radialGauge-scale-majorTicks>
### size `float`
The major tick size.
This is the length of the line in pixels that is drawn to indicate the tick on the scale.
#### Example
<kendo:radialGauge-scale-majorTicks size="size">
</kendo:radialGauge-scale-majorTicks>
### visible `boolean`
The visibility of the major ticks.
Any valid CSS color string will work here, including hex and rgb.
#### Example
<kendo:radialGauge-scale-majorTicks visible="visible">
</kendo:radialGauge-scale-majorTicks>
### width `float`
The width of the major ticks.
#### Example
<kendo:radialGauge-scale-majorTicks width="width">
</kendo:radialGauge-scale-majorTicks>
| 23.415094 | 90 | 0.693795 | eng_Latn | 0.742674 |
6f767a07e24238c9b4bc734e111f541ba1b99f08 | 5,542 | md | Markdown | thesis-text/en/intro.md | kubic71/bachelors-thesis | f17a85e4e144972034f1d2174b51e63c68b39ff7 | [
"MIT"
] | null | null | null | thesis-text/en/intro.md | kubic71/bachelors-thesis | f17a85e4e144972034f1d2174b51e63c68b39ff7 | [
"MIT"
] | null | null | null | thesis-text/en/intro.md | kubic71/bachelors-thesis | f17a85e4e144972034f1d2174b51e63c68b39ff7 | [
"MIT"
] | null | null | null | # Introduction
## The rise of artificial neural networks
In recent years there has been an enormous surge in applications of artificial intelligence technologies based on neural networks to various fields. One of the most significant milestones that kickstarted today's AI revolution has undoubtedly been the year 2012. ImageNet Large Scale Visual Recognition Challenge (ILSVRC), which hand-crafted specialized image-labeling systems have previously dominated, was won by AlexNet with its CNN architecture.
Artificial neural networks inspired by their biological analog had been known and researched for a long time. Even though they enjoyed much enthusiasm initially, they had been neglected as an unpromising direction towards general intelligence. More classical approaches like SVM and rule-based AI systems showed better performance and computational efficiency on AI benchmarks of the time.
What changed the game has been the available computational power that came with Moore's law and the usage of GPUs, mainly their parallel nature in accelerating matrix multiplication operations that neural networks use heavily.
Another factor that helped the rise of neural networks has been the availability of large datasets like ImageNet, which contains 1,281,167 images for training and 50,000 images for validation organized in 1,000 categories.
The availability of large amounts of labeled and unlabeled data, sometimes referred to as "Big data," only seems to get better. A large part of our lives has moved to the virtual space thanks to the internet. Businesses had started to realize the value of the enormous amounts of traffic generated every day, and they are increasingly trying to figure out how to take advantage of it.
What was previously limited to academic circles had quickly become mainstream. Artificial neural networks have proven to be very versatile and have quickly been successfully applied to a wide range of problems. New neural network architectures and new training regimes allowed training deeper networks, which gave rise to a new field of machine learning called "Deep learning."
Deep neural networks have shown state-of-the-art performance in machine translation, human voice synthesis and recognition, drug composition, particle accelerator data analysis, recommender systems, algorithmic trading, reinforcement learning, and many other areas.
## Concerns
Large-scale deployment of neural network systems has been criticized by many for their inherent unexplainability. It is often hard to pinpoint why neural network behaves in some way and why it makes certain decisions. One problem is the role of training data, where possible biases may be negatively and unexpectedly reflected in the behavior of the AI system. Another problem is the performance on out-of-distribution examples, where network inference occurs on different kinds of data than used in the training stage.
Those concerns lead people to study the robustness of AI systems. It turned out that image recognition CNN networks are especially susceptible to the so-called adversarial attacks, where the input is perturbed imperceptibly, but the output of the network changes wildly. Similar kinds of attacks have since been demonstrated in other areas like speech recognition, natural language processing, or reinforcement learning.
## Adversarial attacks
This vulnerability of neural networks has led to a cat-and-mouse game of various attack strategies and following defenses proposed to mitigate them.
Neural networks can be attacked at different stages:
- training
- testing
- deployment
Training attacks exploit training dataset manipulation, sometimes called dataset poisoning, to change the behavior of the resulting trained network.
Testing attacks do not modify trained neural network, but often use the knowledge of the underlying architecture to craft adversarial examples which fool the system.
Deployment attacks deal with real black-box AI systems, where the exact details of the system are usually hidden from the attacker. Nevertheless, partly because similar neural network architectures are used in the same classes of problems, some vulnerabilities in testing scenarios can still be exploited in deployment, even though the exact network parameters, architecture, and output are unknown to the attacker.
The purpose of this thesis is to explore the applicability of certain classes of testing attacks on real-world deployed AI systems. For simplicity, many kinds of SOTA adversarial attacks have only been explored in the testing regime but have not been applied to truly black-box systems.
The main aim of the thesis will be to test different types of testing attacks on AI SaaS providers like Google Vision API, Amazon recognition, or Clarify. Understandably, attacking an unknown system will be more challenging than attacking a known neural network in the testing stage. We will try to measure this attack difficulty increase. This information could prove helpful in selecting the most promising attack to a specific situation.
Many SOTA testing attacks were not designed to attack specific deployed systems, so some attacks will need to be slightly changed to be used. We will explore different ways to modify existing attacks and evaluate them.
If some of those services are proven to be vulnerable, this would have a massive impact on all downstream applications using those SaaS APIs. For instance, content moderation mechanisms, which rely mainly on automatic detection, could be circumvented.
| 125.954545 | 519 | 0.825695 | eng_Latn | 0.999704 |
6f768a113ed10b5d3d3a2b4ffcb64d053911f4e1 | 1,496 | md | Markdown | docs/ReportInProductRunRequest.md | myhealthily/DocuSignAPI.swift | f08d5bf7114d1dfb6bd801d19e6f0c968d783397 | [
"Apache-2.0"
] | null | null | null | docs/ReportInProductRunRequest.md | myhealthily/DocuSignAPI.swift | f08d5bf7114d1dfb6bd801d19e6f0c968d783397 | [
"Apache-2.0"
] | null | null | null | docs/ReportInProductRunRequest.md | myhealthily/DocuSignAPI.swift | f08d5bf7114d1dfb6bd801d19e6f0c968d783397 | [
"Apache-2.0"
] | null | null | null | # ReportInProductRunRequest
## Properties
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**customFieldFilter** | **String** | | [optional]
**dateRangeCustomFromDate** | **String** | | [optional]
**dateRangeCustomToDate** | **String** | | [optional]
**dateRangeFilter** | **String** | | [optional]
**envelopeDateTypeFilter** | **String** | | [optional]
**envelopeRecipientNameContainsFilter** | **String** | | [optional]
**envelopeStatusFilter** | **String** | | [optional]
**envelopeSubjectContainsFilter** | **String** | | [optional]
**fields** | [ReportInProductField] | | [optional]
**forDownload** | **String** | | [optional]
**isDashboard** | **String** | | [optional]
**periodLengthFilter** | **String** | | [optional]
**reportCustomizedId** | **String** | | [optional]
**reportDescription** | **String** | | [optional]
**reportId** | **String** | | [optional]
**reportInvocationType** | **String** | | [optional]
**reportName** | **String** | | [optional]
**sentByFilter** | **String** | | [optional]
**sentByIds** | **String** | | [optional]
**sortDirection** | **String** | | [optional]
**sortField** | **String** | | [optional]
**startPosition** | **String** | The starting index position of the current result set. | [optional]
[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)
| 46.75 | 161 | 0.599599 | yue_Hant | 0.47888 |
6f77852e7da8cb071c61f7dc1f5f7257b8b0e94b | 10,428 | md | Markdown | _posts/2018/2018-05-10-known-nuget-properties-in-csproj.md | walterlv/jekyll-theme-chirpy | b5625aa504bc6096b0df0d9e6acf5a40514c56bc | [
"MIT"
] | null | null | null | _posts/2018/2018-05-10-known-nuget-properties-in-csproj.md | walterlv/jekyll-theme-chirpy | b5625aa504bc6096b0df0d9e6acf5a40514c56bc | [
"MIT"
] | null | null | null | _posts/2018/2018-05-10-known-nuget-properties-in-csproj.md | walterlv/jekyll-theme-chirpy | b5625aa504bc6096b0df0d9e6acf5a40514c56bc | [
"MIT"
] | null | null | null | ---
title: "项目文件中的已知 NuGet 属性（使用这些属性，创建 NuGet 包就可以不需要 nuspec 文件啦）"
publishDate: 2018-05-10 21:49:21 +0800
date: 2019-03-09 09:07:32 +0800
tags: visualstudio nuget csharp dotnet msbuild
permalink: /post/known-nuget-properties-in-csproj.html
---
知道了 csproj 文件中的一些常用 NuGet 属性，创建 NuGet 包时就可以充分发挥新 Sdk 自动生成 NuGet 包的优势，不需要 nuspec 文件啦。（毕竟 nuspec 文件没有 .csproj 和 .targets 文件强大而又有扩展性。）
---
“项目文件中的已知属性系列”分为两个部分：
- [项目文件中的已知属性（知道了这些，就不会随便在 csproj 中写死常量啦） - 吕毅](/post/known-properties-in-csproj)
- 本文：[项目文件中的已知 NuGet 属性（使用这些属性，创建 NuGet 包就可以不需要 nuspec 文件啦） - 吕毅](/post/known-nuget-properties-in-csproj)
NuGet 相关的属性也分为全局属性和项属性两类。不过，我更愿意分成三类来说明：
<div id="toc"></div>
## nuspec 属性
当然，这部分的属性也是在 csproj 中使用的，是为了生成 nuspec 文件。
使用方法像这样：
```xml
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<PackageId>Walterlv.Demo</PackageId>
<PackageVersion>3.2.0-beta</PackageVersion>
<TargetFramework>net46</TargetFramework>
</PropertyGroup>
</Project>
```
不过我们通常没有这么直接去设置，因为大多数属性都是有默认值的，如果不设置，将自动使用默认值。甚至什么都不写也能生成正确的 nuspec 文件。
- `$(PackageId)`: NuGet 包的唯一 Id，对应 NuGet 的 Id 属性。这个 Id 需要在整个服务器（例如 nuget.org）上唯一，如果没设置，则使用 `$(AssemblyName)`；例如 `Newtonsoft.Json`。
- `$(PackageVersion)`: NuGet 包的包版本，可以使用语义版本号（参见[语义版本号（Semantic Versioning） - 吕毅](/post/semantic-version)），如果没设置，则使用 `$(Version)`；例如 `3.2.0-beta`。
- `$(PackageVersionPrefix)`: 包版本前缀，默认为空。
- `$(PackageVersionSuffix)`: 包版本后缀，默认为空。
- `$(Authors)`: 包的作者；建议指定成在 nuget.org 上的用户名，这样访客可以点击包作者查看到包作者的信息；多个名字用分号分隔。
- `$(Title)`: 包的显示名称，如果没设置，则使用 `$(PackageId)`。
- `$(PackageDescription)`: 包的描述文字，如果填写了，则用户在浏览包的时候可以看到。
- `$(Copyright)`: 包的版权声明
- `$(PackageRequireLicenseAcceptance)`: 是个布尔值，如果为 true，则在安装包之前要求同意协议。
- `$(PackageLicenseUrl)`: 此 NuGet 包协议所在的 url。
- `$(PackageProjectUrl)`: 此 NuGet 包的项目 url。
- `$(PackageIconUrl)`: 此 NuGet 包的图标 url，无论是 nuget.org 还是 Visual Studio 都将从这个 url 下载包的图标。
- `$(PackageTags)`: 标签，用分号分隔；指定多个标签有助于用户在 nuget.org 上搜索到你的 NuGet 包。
- `$(PackageReleaseNotes)`: 这个版本的 Release 记录。
- `$(RepositoryUrl)`: 仓库 url，例如 <https://github.com/dotnet-campus/MSTestEnhancer.git>
- `$(RepositoryType)`: 仓库类型，例如 git、tfs。
- `$(RepositoryBranch)`: **NuGet 4.7 才开始的新属性！**此包对应的仓库分支，例如 `master`。
- `$(RepositoryCommit)`: **NuGet 4.7 才开始的新属性！**此包对应的提交号，例如 `2d3ef96ee704d7896eeb2d88fbc987b2004ff786`。
- `$(PackageType)`: *我还没有理解到此属性的作用。*
以上有些信息在每次 NuGet 发布之前都是要改的，例如：`$(PackageVersion)`、`$(PackageReleaseNotes)`、`$(RepositoryCommit)`。所以很明显——**这不是用来给开发者设置的属性，是用于辅助我们生成打包工具的。**
## 配置属性
这些属性会影响生成 NuGet 包的过程。
```xml
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<!-- 此程序集不可打包，通常在单元测试项目中设置此属性。 -->
<IsPackable>false</IsPackable>
<Description></Description>
<!-- 这是一个仅开发阶段使用的 NuGet 包，详情请参见 https://blog.walterlv.com/post/prevent-nuget-package-been-depended.html。 -->
<DevelopmentDependency>true</DevelopmentDependency>
<!-- 单独指定 NuGet 包应该输出到哪个目录（可以跟项目文件的输出目录不一样）。 -->
<PackageOutputPath></PackageOutputPath>
<!-- 如果指定为 true，那么还会额外生成 PackageId.symbols.nupkg 包，
除了原有包的内容外，还额外包含全部的输出文件，以及源码和项目文件，用于调试。 -->
<IncludeSymbols>true</IncludeSymbols>
<!-- 大致与 IncludeSymbols 相同，不过只会额外把 pdb 和 Compile 类型的文件打包到 NuGet 包中。
如果使用 ProjectReference 引用的项目没有指定 TreatAsPackageReference=false，也会一起被打包。 -->
<IncludeSource>true</IncludeSource>
<PackageTypes></PackageTypes>
<!-- 如果指定为 true，那么生成的 dll 将拷贝到 NuGet 包的 tools 目录下。 -->
<IsTool>true</IsTool>
<!-- 如果 lib/**/*dll 中没有发现 dll，NuGet 打包过程中会有警告；
将这个属性设为 true 可以禁用警告；这在制作纯工具型 NuGet 包是非常有用。 -->
<NoPackageAnalysis>true</NoPackageAnalysis>
<MinClientVersion></MinClientVersion>
<IncludeContentInPack></IncludeContentInPack>
<!-- 默认情况下，项目输出的 dll 会被打包到 lib 目录下；
设置了此属性后，就可以打包到其他目录下了。此例打包到 task 目录下 -->
<BuildOutputTargetFolder>tasks</BuildOutputTargetFolder>
<ContentTargetFolders></ContentTargetFolders>
<!-- 以下属性都是为了使用单独的 nuspec 文件而准备的；如果不使用 nuspec 文件，通常无需设置这些属性。 -->
<!-- 默认情况下，使用 dotnet pack 打 NuGet 包时，也会顺便编译；
但设置此值为 true 后，就会像 nuget.exe 那样不进行编译了。 -->
<NoBuild>true</NoBuild>
<!-- 默认是 true，如果指定为 false，那么项目编译输出的 dll 文件将不会被打包到 NuGet 包中。 -->
<IncludeBuildOutput>false</IncludeBuildOutput>
<!-- 如果需要额外手工编写 nuspec 文件，那么使用此属性指定绝对或相对路径。 -->
<NuspecFile>Walterlv.Demo.nuspec</NuspecFile>
<!-- 生成的属性可以时 nuspec 文件中的占位符生效，
例如 <file src="$SampleProperty$" target="src/" /> -->
<NuspecProperties>SampleProperty=Program.cs</NuspecProperties>
<!-- 如果 NuspecFile 使用相对路径，那么就会相对于此路径；通常不需要指定。 -->
<NuspecBasePath></NuspecBasePath>
</PropertyGroup>
</Project>
```
其中，`DevelopmentDependency` 的设置可参见：[帮助官方 NuGet 解掉 Bug，制作绝对不会传递依赖的 NuGet 包 - walterlv](/post/prevent-nuget-package-been-depended)。
以上没有设置值和注释的属性，我正在查阅资料。
## 项属性
### 文件
为了脱离 nuspec 文件来打包，csproj 中需要对特殊用途的文件设置特别的 NuGet 属性。
例如 `Pack` 属性可以额外指定一或一组通配符文件需要被打包到 NuGet 包中；`PackagePath` 则指定了打包到 NuGet 包的路径（*NuGet 会通过扩展名来自动识别这是文件夹还是文件，所以可以通过这个属性来重新指定名称，但无法重新指定扩展名*）。
```xml
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<Content Include="readme.txt">
<Pack>true</Pack>
<PackagePath>\</PackagePath>
</Content>
<Content Include="PackageId.targets">
<Pack>true</Pack>
<PackagePath>buildMultiTargeting\</PackagePath>
</Content>
</PropertyGroup>
</Project>
```
### 引用
引用中也可以加入一些 NuGet 包的生成属性。
无论是 `<ProjectReference />` 还是 `<PackageReference />`，都可以额外加上 `<IncludeAssets>` `<ExcludeAssets>` `<PrivateAssets>` 属性。
使用方法类似这样：
```xml
<PackageReference Include="Walterlv.Demo" Version="3.0.0-beta">
<IncludeAssets>all</IncludeAssets>
<ExcludeAssets>contentFiles</ExcludeAssets>
<PrivateAssets>contentFiles;analyzers</PrivateAssets>
</PackageReference>
```
或者这样：
```xml
<PackageReference Include="Walterlv.Demo" Version="3.0.0-beta" PrivateAssets="all" />
```
不区分大小写。
- `<IncludeAssets>` 引用的项目或包中的指定部分是本项目的依赖项。默认为 `all`。
- `<ExcludeAssets>` 引用的项目或包中的指定部分不是本项目的依赖项，应该排除。默认为 `none`。
- `<PrivateAssets>` 引用的项目或包中的指定部分依然是本项目的依赖项，但是在打 NuGet 包时不作为依赖项（不会传递到下一个项目）。默认为 `contentfiles;analyzers;build`。
如果你正试图用 NuGet 编写一个编译时工具，那么，你可能需要在所有引用的最后加上如下行，将所有的包引用都设为 `PrivateAssets`。
```xml
<PackageReference Update="@(PackageReference)" PrivateAssets="All" />
```
如果你希望了解 `Reference` `PackageReference` 以及上面 `@` 的含义，可以阅读我的另一篇文章：[理解 C# 项目 csproj 文件格式的本质和编译流程 - walterlv](/post/understand-the-csproj)。
## 可能没有开放的内部属性
在 Microsoft.NET.Sdk 中，NuGet 包的打包主要靠的是 `NuGet.Build.Tasks.Pack.targets` 文件中一个名为 `PackTask` 的任务来完成的，它是一个使用了非常多参数的 `Task`。
```xml
<PackTask PackItem="$(PackProjectInputFile)"
PackageFiles="@(_PackageFiles)"
PackageFilesToExclude="@(_PackageFilesToExclude)"
PackageVersion="$(PackageVersion)"
PackageId="$(PackageId)"
Title="$(Title)"
Authors="$(Authors)"
Description="$(PackageDescription)"
Copyright="$(Copyright)"
RequireLicenseAcceptance="$(PackageRequireLicenseAcceptance)"
LicenseUrl="$(PackageLicenseUrl)"
ProjectUrl="$(PackageProjectUrl)"
IconUrl="$(PackageIconUrl)"
ReleaseNotes="$(PackageReleaseNotes)"
Tags="$(PackageTags)"
DevelopmentDependency="$(DevelopmentDependency)"
BuildOutputInPackage="@(_BuildOutputInPackage)"
ProjectReferencesWithVersions="@(_ProjectReferencesWithVersions)"
TargetPathsToSymbols="@(_TargetPathsToSymbols)"
TargetFrameworks="@(_TargetFrameworks)"
AssemblyName="$(AssemblyName)"
PackageOutputPath="$(PackageOutputAbsolutePath)"
IncludeSymbols="$(IncludeSymbols)"
IncludeSource="$(IncludeSource)"
PackageTypes="$(PackageType)"
IsTool="$(IsTool)"
RepositoryUrl="$(RepositoryUrl)"
RepositoryType="$(RepositoryType)"
SourceFiles="@(_SourceFiles->Distinct())"
NoPackageAnalysis="$(NoPackageAnalysis)"
MinClientVersion="$(MinClientVersion)"
Serviceable="$(Serviceable)"
FrameworkAssemblyReferences="@(_FrameworkAssemblyReferences)"
ContinuePackingAfterGeneratingNuspec="$(ContinuePackingAfterGeneratingNuspec)"
NuspecOutputPath="$(NuspecOutputAbsolutePath)"
IncludeBuildOutput="$(IncludeBuildOutput)"
BuildOutputFolder="$(BuildOutputTargetFolder)"
ContentTargetFolders="$(ContentTargetFolders)"
RestoreOutputPath="$(RestoreOutputAbsolutePath)"
NuspecFile="$(NuspecFileAbsolutePath)"
NuspecBasePath="$(NuspecBasePath)"
NuspecProperties="$(NuspecProperties)"
AllowedOutputExtensionsInPackageBuildOutputFolder="$(AllowedOutputExtensionsInPackageBuildOutputFolder)"
AllowedOutputExtensionsInSymbolsPackageBuildOutputFolder="$(AllowedOutputExtensionsInSymbolsPackageBuildOutputFolder)"/>
</Target>
```
所以总结起来我们还有这些 NuGet 的属性还可以配置（想必下划线开头的属性或集合是 NuGet 内部不愿意公开的属性了）：
- `$(PackProjectInputFile)`
- `@(_PackageFiles)`
- `@(_PackageFilesToExclude)`
- `$(PackageVersion)`
- `$(PackageId)`
- `$(Title)`
- `$(Authors)`
- `$(PackageDescription)`
- `$(Copyright)`
- `$(PackageRequireLicenseAcceptance)`
- `$(PackageLicenseUrl)`
- `$(PackageProjectUrl)`
- `$(PackageIconUrl)`
- `$(PackageReleaseNotes)`
- `$(PackageTags)`
- `$(DevelopmentDependency)`
- `@(_BuildOutputInPackage)`
- `@(_ProjectReferencesWithVersions)`
- `@(_TargetPathsToSymbols)`
- `@(_TargetFrameworks)`
- `$(AssemblyName)`
- `$(PackageOutputAbsolutePath)`
- `$(IncludeSymbols)`
- `$(IncludeSource)`
- `$(PackageType)`
- `$(IsTool)`
- `$(RepositoryUrl)`
- `$(RepositoryType)`
- `@(_SourceFiles->Distinct())`
- `$(NoPackageAnalysis)`
- `$(MinClientVersion)`
- `$(Serviceable)`
- `@(_FrameworkAssemblyReferences)`
- `$(ContinuePackingAfterGeneratingNuspec)`
- `$(NuspecOutputAbsolutePath)`
- `$(IncludeBuildOutput)`
- `$(BuildOutputTargetFolder)`
- `$(ContentTargetFolders)`
- `$(RestoreOutputAbsolutePath)`
- `$(NuspecFileAbsolutePath)`
- `$(NuspecBasePath)`
- `$(NuspecProperties)`
- `$(AllowedOutputExtensionsInPackageBuildOutputFolder)`
- `$(AllowedOutputExtensionsInSymbolsPackageBuildOutputFolder)`
这是 .NET Core 2.1 中自带的 NuGet 的打包属性，比 .NET Core 2.0 中多了个 `@(_SourceFiles->Distinct())`。
---
**参考资料**
- [NuGet pack and restore as MSBuild targets - Microsoft Docs](https://docs.microsoft.com/en-us/nuget/reference/msbuild-targets?wt.mc_id=MVP)
- [NuGet PackageReference format (package references in project files) - Microsoft Docs](https://docs.microsoft.com/en-us/nuget/consume-packages/package-references-in-project-files?wt.mc_id=MVP)
| 36.461538 | 194 | 0.712505 | yue_Hant | 0.963128 |
6f783992ccf5e849be94d0a6b7a24db20bac58f9 | 34 | md | Markdown | README.md | JuliaBodingbauer/mobile-computing-1 | 740f69000d20fed23068c44cf27bc0124f63bf0b | [
"Unlicense"
] | null | null | null | README.md | JuliaBodingbauer/mobile-computing-1 | 740f69000d20fed23068c44cf27bc0124f63bf0b | [
"Unlicense"
] | null | null | null | README.md | JuliaBodingbauer/mobile-computing-1 | 740f69000d20fed23068c44cf27bc0124f63bf0b | [
"Unlicense"
] | 6 | 2021-11-25T11:02:53.000Z | 2021-12-09T10:58:04.000Z | # mobile-computing
Swift Homework
| 11.333333 | 18 | 0.823529 | eng_Latn | 0.483749 |
6f78bcda03a7bda77337f8b503ba1a3f4a96c7c8 | 576 | md | Markdown | README.md | TimCollins/Reddit.DailyProgrammer.CPP | 6e5fb879d7d43c4b508679d6696c190fc0409ff1 | [
"MIT"
] | null | null | null | README.md | TimCollins/Reddit.DailyProgrammer.CPP | 6e5fb879d7d43c4b508679d6696c190fc0409ff1 | [
"MIT"
] | null | null | null | README.md | TimCollins/Reddit.DailyProgrammer.CPP | 6e5fb879d7d43c4b508679d6696c190fc0409ff1 | [
"MIT"
] | null | null | null | Reddit.DailyProgrammer (C++ Version)
======================
A repository containing my attempts at working through the Reddit [DailyProgrammer](http://www.reddit.com/r/dailyprogrammer) challenges.
All solutions are written in C++ (Visual Studio 2015) and are implemented as standalone Console applications except where noted.
Complete
--
Challenge #1 Easy - [Greeting](http://www.reddit.com/r/dailyprogrammer/comments/pih8x/easy_challenge_1/)
Challenge #1 Intermediate - [CRUD Operations](http://www.reddit.com/r/dailyprogrammer/comments/pihtx/intermediate_challenge_1/) | 52.363636 | 136 | 0.769097 | eng_Latn | 0.630822 |
6f78d32852d9990dc4cd467fb3af14a829d6d70b | 8,111 | md | Markdown | packages/framework/theming-react-native/README.md | statm/fluentui-react-native | 0474803559d13738c7ab4d3ef85ebd9b59af2d0b | [
"MIT"
] | null | null | null | packages/framework/theming-react-native/README.md | statm/fluentui-react-native | 0474803559d13738c7ab4d3ef85ebd9b59af2d0b | [
"MIT"
] | null | null | null | packages/framework/theming-react-native/README.md | statm/fluentui-react-native | 0474803559d13738c7ab4d3ef85ebd9b59af2d0b | [
"MIT"
] | null | null | null | # Theming React Native
This package serves as an entry point which aggregates and re-exports some of the various features in this repo for those who want to quickly get started.
## Getting Started
### Update package.json & install dependencies
You may want a few different packages from this repo. Let's start with the following:
- `@uifabricshared/theming-react-native`
- `@uifabricshared/themed-stylesheets` for styling react-native's primitives components.
E.g. In your package.json file:
```json
{
"name": "my-app",
"version": "0.10.17",
"description": "An app with lots of cool features",
"main": "lib/index.js",
"dependencies": {
"@uifabricshared/theming-react-native": "^0.2.0",
"@uifabricshared/themed-stylesheet": "^0.2.0"
}
}
```
And then run `yarn`, `npm install`, `rush install`, or an equivalent command to update your node_modules.
## The ThemeProvider
All consumers of these theming packages will want at least one `ThemeProvider` in their tree. Descendents of a `ThemeProvider` will have access to the current theme object via a [react context](https://reactjs.org/docs/context.html).
| Property | Type | Description |
| -------- | --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| theme | string? | Changes the ThemeContext.Value to the Theme object in the current registry with the given name. If unspecified, or set to '', the default theme will be used. |
| registry | [ThemeRegistry?](../theme-registry/README.md) | Changes the theme registry context (which also changes the theme to this registry's default theme if no `theme` prop is provided). The active theme registry will be used for all Theme lookups performed by this and descendant `ThemeProviders`. Most consumers will want at least one `ThemeProvider` near the root of their Component tree that specifies the primary registry. |
### Accessing the ThemeContext
Once you've added a ThemeProvider to your tree, functional component descendents will have access to the Theme context via the useTheme hook. To access the theme from within a functional component, see below:
```tsx
// MyComponent.tsx
import * as React from 'react';
import { useTheme } from '@uifabricshared/theming-react-native';
export const MyComponent: React.FunctionComponent = (_props: {}) => {
// This hook retrieves the theme from the context set by the nearest parent ThemeProvider
const theme = useTheme();
const themeColor = theme.colors.bodyText;
return <SomeComponent color={themeColor} />;
};
```
If you're writing class components instead of functional components, you'll need use the `ThemeContext.Consumer` directly like so:
```tsx
// OtherComponent.tsx
import * as React from 'react';
import { ThemeContext, ITheme } from '@uifabricshared/theming-react-native';
export class OtherComponent extends React.Component {
public render(): JSX.Element {
return (
<ThemeContext.Consumer>
{(theme: ITheme) => {
const themeColor = theme.colors.bodyText;
return <SomeComponent color={themeColor} />;
}}
</ThemeContext.Consumer>
);
}
}
```
### Using a ThemeRegistry with a ThemeProvider
While a 'greenfield' app developer might be fine without setting a ThemeRegistry with their ThemeProvider, any 'brownfield' app where there are multiple islands of react-native UI being hosted which use the same JavaScript host instance may want to avoid leaking theme information into the other islands of UX. Creating your own ThemeRegistry and providing this as additional context **near the root** of your component tree can help you manage this behavior.
**Note:** Many users will only need a single theme registry. This should be provided to the top ThemeProvider which is above all other ThemeProviders and theme-aware UI. Subsequent ThemeProviders will be used to change the Theme context.
```tsx
// App.tsx
import { ThemeProvider, createPlatformThemeRegistry } from '@uifabricshared/theming-react-native';
import { MyAppImpl } from './MyAppImpl';
export const myThemeRegistry = createPlatformThemeRegistry();
export default function App() {
return (
<ThemeProvider registry={myThemeRegistry}>
<MyAppImpl />
</ThemeProvider>
);
}
```
The ThemeRegistry is a crucial piece. It's responsible for
- Initializing theme object with platform defaults from the Native Module
- Listening to the Theming Native Module for changes to the platform theme
- Updating dependent themes as parent themes change (such as a platform theme change)
You can read more about the [ThemeRegistry here](../theme-registry/README.md).
## Theme-aware Primitives
### Create a Themed Stylesheet
The `themed-stylesheet` package allows you to author View/Text/Image Style objects similar to `StyleSheet.create(...);`. You can learn more at the [themed-stylesheet's README](../themed-stylesheet/README.md)
```tsx
// styles.ts
import { ITheme } from '@uifabricshared/theming-react-native';
export const getThemedStyles = themedStyleSheet((t: ITheme) => {
return {
style1: {
backgroundColor: t.colors.background,
borderStyle: 'solid',
borderWidth: 1,
},
style2: {
backgroundColor: t.colors.primaryButtonBackground,
borderStyle: 'solid',
borderWidth: 1,
},
};
});
```
### Using the hook with themed stylesheets
```tsx
// MyAppImpl.tsx
import * as React from 'react';
import { Text, ViewProps } from 'react-native';
import { useTheme } from '@uifabricshared/theming-react-native';
import { getThemedStyles } from './styles';
export const ThemedView: React.FunctionComponent<ViewProps> = (p: ViewProps) => {
const { userStyle, ...rest } = p;
const theme = useTheme();
const styles = getThemedStyles(theme);
return <View styles={[userStyle, styles.style1]} {...rest} />;
};
export const MyAppImpl = () => {
return (
<ThemedView>
<Text>Hello, World!</Text>
</ThemedView>
);
};
```
## Using different Platform Themes
Certain platforms will have multiple platform theme definitions. If you want the default theme to be initialized with a specific platform theme, or want to use a different platform theme for a portion of your UI, you can get the platform themes through the ThemingModuleHelper.
```tsx
// App.tsx
import { ThemeProvider, createPlatformThemeRegistry, ThemingModuleHelper } from '@uifabricshared/theming-react-native';
// Initializes the Default Theme with the 'TaskPane' platform theme, implicitly pulled from ThemingModuleHelper
export const myThemeRegistry = createPlatformThemeRegistry('TaskPane');
// Get the 'TaskPaneCard' theme from the ThemingModuleHelper
const taskPaneCardTheme = ThemingModuleHelper.createPlatformThemeDefinition('TaskPaneCard');
// Registers it with the name 'PlatformTaskPaneCard'
myThemeRegistry.registerTheme(taskPaneCardTheme, 'PlatformTaskPaneCard');
export default function App() {
return (
<ThemeProvider registry={myThemeRegistry}>
<SomeComponent />
<ThemeProvider theme="PlatformTaskPaneCard">
<SomeComponent />
</ThemeProvider>
</ThemeProvider>
);
}
```
| 42.465969 | 459 | 0.639748 | eng_Latn | 0.949101 |
6f790f0035b02eb8cd152965c04c23b0398e745d | 1,382 | md | Markdown | docs/visual-basic/misc/bc31426.md | jhonyfrozen/docs.pt-br | c9e86b6a5de2ff8dffd54dd64d2e87aee85a5cb8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/visual-basic/misc/bc31426.md | jhonyfrozen/docs.pt-br | c9e86b6a5de2ff8dffd54dd64d2e87aee85a5cb8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/visual-basic/misc/bc31426.md | jhonyfrozen/docs.pt-br | c9e86b6a5de2ff8dffd54dd64d2e87aee85a5cb8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Nomes de tipo não intrínsecos não são permitidos em expressões de compilação condicional
ms.date: 07/20/2015
f1_keywords:
- bc31426
- vbc31426
helpviewer_keywords:
- BC31426
ms.assetid: 73deeafa-4dbe-4c27-aff7-c6bea0e37d5a
ms.openlocfilehash: 7e0d99b5bb3006ffbdda85ec6b22e032bc0852d8
ms.sourcegitcommit: 2701302a99cafbe0d86d53d540eb0fa7e9b46b36
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 04/28/2019
ms.locfileid: "64624998"
---
# <a name="non-intrinsic-type-names-are-not-allowed-in-conditional-compilation-expressions"></a>Nomes de tipo não intrínsecos não são permitidos em expressões de compilação condicional
A expressão de compilação condicional se refere a um tipo não intrínsecos, mas apenas tipos intrínsecos são permitidos.
Para obter mais informações sobre o tipo intrínseco no Visual Basic, consulte [resumo de tipos de dados](../../visual-basic/language-reference/keywords/data-types-summary.md).
**ID do erro:** BC31426
## <a name="to-correct-this-error"></a>Para corrigir este erro
- Substitua o tipo não intrínsecos com um tipo intrínseco.
## <a name="see-also"></a>Consulte também
- [Compilação condicional no Visual Basic](~/docs/visual-basic/programming-guide/program-structure/conditional-compilation.md)
- [Resumo de Tipos de Dados](../../visual-basic/language-reference/keywords/data-types-summary.md)
| 43.1875 | 184 | 0.782923 | por_Latn | 0.929561 |
6f7940880ffaf2fe463333314625c6348f9d17f6 | 8,596 | md | Markdown | articles/cognitive-services/LUIS/luis-how-to-collaborate.md | dbroeglin/azure-docs.fr-fr | 98723467b92322c5546c342f50caae075d4c3ff5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/cognitive-services/LUIS/luis-how-to-collaborate.md | dbroeglin/azure-docs.fr-fr | 98723467b92322c5546c342f50caae075d4c3ff5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/cognitive-services/LUIS/luis-how-to-collaborate.md | dbroeglin/azure-docs.fr-fr | 98723467b92322c5546c342f50caae075d4c3ff5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Collaborer avec d’autres personnes - LUIS
titleSuffix: Azure Cognitive Services
description: Un propriétaire d’application peut ajouter des contributeurs à la ressource de création. Ces contributeurs peuvent modifier le modèle, l’entraîner et publier l’application.
services: cognitive-services
author: diberry
manager: nitinme
ms.custom: seodec18
ms.service: cognitive-services
ms.subservice: language-understanding
ms.topic: conceptual
ms.date: 11/19/2019
ms.author: diberry
ms.openlocfilehash: 96aa7517a3418ab30b0b6a1736eea950ecf4a731
ms.sourcegitcommit: 85e7fccf814269c9816b540e4539645ddc153e6e
ms.translationtype: HT
ms.contentlocale: fr-FR
ms.lasthandoff: 11/26/2019
ms.locfileid: "74533806"
---
# <a name="add-contributors-to-your-app"></a>Ajouter des contributeurs à votre application
Un propriétaire d’application peut ajouter des contributeurs à des applications. Ces collaborateurs peuvent modifier le modèle, entraîner et publier l’application.
[!INCLUDE [Manage collaborators and contributors based on migrated or not-migrated apps](./includes/manage-contributor-collaborator-migration.md)]
## <a name="add-contributor-to-azure-authoring-resource"></a>Ajouter un contributeur à une ressource de création Azure
La procédure suivante est destinée à tous les utilisateurs qui ont **migré** pour utiliser la ressource de création Azure.
Vous avez migré si votre expérience de création LUIS est liée à une ressource de création dans la page **Gérer -> Ressources Azure** du portail LUIS.
1. Dans le portail Azure, recherchez la ressource de création Language Understanding (LUIS). Son type est `LUIS.Authoring`.
1. Dans la page **Contrôle d’accès (IAM)** de cette ressource, sélectionnez **+Ajouter**, puis **Ajouter une attribution de rôle**.
1. Dans la fenêtre **Ajouter une attribution de rôle**, sélectionnez le **Rôle** du contributeur. Pour l’option **Attribuer l’accès à**, sélectionnez un **utilisateur, un groupe ou un principal de service Azure AD**. Pour l’option **Sélectionner**, entrez l’adresse e-mail de l’utilisateur. Si l’utilisateur a plus de 1 adresse e-mail pour le même domaine, veillez à entrer le compte de courrier _principal_.
Lorsque l’e-mail de l’utilisateur est trouvé, sélectionnez le compte, puis **Enregistrer**.
Si vous rencontrez des problèmes avec cette attribution de rôle, voir [Attribution de rôle Azure](../../role-based-access-control/role-assignments-portal.md) et [Résolution des problèmes liés au contrôle d’accès Azure](../../role-based-access-control/troubleshooting.md#problems-with-rbac-role-assignments).
## <a name="add-collaborator-to-luis-app"></a>Ajouter un collaborateur à une application LUIS
La procédure suivante est destinée à tous les utilisateurs qui **n’ont pas migré** pour utiliser la ressource de création Azure.
Vous n’avez pas opéré de migration si votre expérience de création LUIS n’est pas liée à une ressource de création sur la page **Gérer -> Ressources Azure** du portail LUIS.
Une application possède un seul créateur, son propriétaire, mais peut avoir de nombreux collaborateurs. Pour autoriser des collaborateurs à modifier votre application LUIS, vous devez ajouter l’e-mail qu’ils utilisent pour accéder au portail LUIS à la liste des collaborateurs. Une fois qu’ils sont ajoutés, l’application apparaît dans leur portail LUIS.
1. Sélectionnez **Gérer** dans le menu supérieur droit, puis **Collaborateurs** dans le menu gauche.
1. Sélectionnez **Ajouter un collaborateur** dans la barre d’outils.
1. Entrez l’adresse e-mail utilisée par le collaborateur pour se connecter au portail LUIS.
### <a name="users-with-multiple-emails"></a>Utilisateurs avec plusieurs adresses e-mail
Si vous ajoutez un contributeur/collaborateur à une application LUIS, vous spécifiez son adresse e-mail exacte. Si Azure Active Directory (Azure AD) permet à un utilisateur d’avoir plusieurs comptes de courrier interchangeables, LUIS exige que l’utilisateur se connecte avec l’adresse e-mail spécifiée lors de son ajout en tant que contributeur/collaborateur.
<a name="owner-and-collaborators"></a>
### <a name="azure-active-directory-resources"></a>Ressources Azure Active Directory
Si vous utilisez [Azure Active Directory](https://docs.microsoft.com/azure/active-directory/) (Azure AD) dans votre organisation, Language Understanding (LUIS) a besoin d’une autorisation pour accéder aux informations sur l'accès de vos utilisateurs quand ils souhaitent utiliser LUIS. Les ressources dont LUIS a besoin sont minimes.
La description détaillée s’affiche quand vous tentez de vous inscrire avec un compte qui a un consentement de l’administrateur ou qui n’en a pas besoin, de sorte que le consentement de l’administrateur :
* Vous autorise à vous connecter à l’application avec votre compte professionnel et laisse l’application lire votre profil. Autorise également l’application à lire les informations de base sur l’entreprise. Cela accorde à LUIS l’autorisation de lire les données de profil de base, telles que l’ID d’utilisateur, l’adresse e-mail et le nom.
* Autorise l’application à afficher et à mettre à jour vos données, même quand vous n’utilisez pas l’application. L'autorisation est nécessaire pour actualiser le jeton d’accès de l’utilisateur.
### <a name="azure-active-directory-tenant-user"></a>Utilisateur du locataire Azure Active Directory
LUIS utilise le flux de consentement standard Azure Active Directory (Azure AD).
L’administrateur de locataire doit travailler directement avec l’utilisateur qui a besoin d’accéder à LUIS dans Azure AD.
* D’abord, l’utilisateur se connecte à LUIS, et une boîte de dialogue contextuelle nécessitant l’approbation de l’administrateur s’affiche. L’utilisateur doit contacter l’administrateur de locataire avant de poursuivre.
* Ensuite, l’administrateur de locataire se connecte à LUIS, et une boîte de dialogue contextuelle de flux de consentement s’affiche. C’est avec cette boîte de dialogue que l’administrateur accorde l’autorisation à l’utilisateur. Une fois que l’administrateur a donné son autorisation, l’utilisateur peut poursuivre avec LUIS. Si l’administrateur de locataire ne se connecte pas à LUIS, l’administrateur peut [consentir](https://account.activedirectory.windowsazure.com/r#/applications) à l’accès à LUIS, comme illustré sur la capture d'écran suivante. Notez que la liste est filtrée sur les éléments incluant le nom `LUIS`.
Si l’administrateur de locataire veut uniquement que certaines personnes utilisent LUIS, plusieurs solutions sont possibles :
* Donnez le « consentement administrateur » (à tous les utilisateurs d’Azure AD), mais affectez ensuite la valeur « Oui » à « Affectation de l’utilisateur obligatoire » sous les propriétés de l’application d’entreprise, et enfin attribuer/ajouter uniquement les utilisateurs souhaités à l’application. Avec cette méthode, l’administrateur offre quand même le « consentement administrateur » à l’application, mais il peut contrôler les utilisateurs en mesure d’y accéder.
* Une deuxième solution consiste à utiliser l’[API de gestion des identités et des accès Azure AD dans Microsoft Graph](https://docs.microsoft.com/graph/azuread-identity-access-management-concept-overview) pour fournir un consentement à chaque utilisateur spécifique.
Découvrez-en plus sur les utilisateurs Azure Active Directory et le consentement :
* [Limiter votre application](../../active-directory/develop/howto-restrict-your-app-to-a-set-of-users.md) à un ensemble d’utilisateurs
## <a name="next-steps"></a>Étapes suivantes
* Découvrez [comment utiliser des versions](luis-how-to-manage-versions.md) pour contrôler le cycle de vie de votre application.
* Découvrez les concepts de [ressource de création](luis-concept-keys.md#authoring-key) et de [contributeurs](luis-concept-keys.md#contributions-from-other-authors).
* Découvrez [comment créer](luis-how-to-azure-subscription.md) des ressources de création et de runtime.
* Migrez vers la nouvelle [ressource de création](luis-migration-authoring.md).
| 83.456311 | 624 | 0.794788 | fra_Latn | 0.980047 |
6f79504f4ae4b1467db3cacb01f7f2f29603710a | 4,382 | md | Markdown | _includes/templates/provisioning/coap-without-credentials-type.md | ytkachenkothingsboard/thingsboard.github.io | 4b2d35e18342579508f6e9275771532c9915bef3 | [
"Apache-2.0"
] | null | null | null | _includes/templates/provisioning/coap-without-credentials-type.md | ytkachenkothingsboard/thingsboard.github.io | 4b2d35e18342579508f6e9275771532c9915bef3 | [
"Apache-2.0"
] | null | null | null | _includes/templates/provisioning/coap-without-credentials-type.md | ytkachenkothingsboard/thingsboard.github.io | 4b2d35e18342579508f6e9275771532c9915bef3 | [
"Apache-2.0"
] | null | null | null | | **Parameter** | **Example value** | **Description** |
|:-|:-
| *deviceName* | **DEVICE_NAME** | Device name in ThingsBoard. |
| *provisionDeviceKey* | **PUT_PROVISION_KEY_HERE** | Provisioning device key, you should take it from configured device profile. |
| *provisionDeviceSecret* | **PUT_PROVISION_SECRET_HERE** | Provisioning device secret, you should take it from configured device profile. |
|-
Provisioning request data example:
```json
{
"deviceName": "DEVICE_NAME",
"provisionDeviceKey": "PUT_PROVISION_KEY_HERE",
"provisionDeviceSecret": "PUT_PROVISION_SECRET_HERE"
}
```
{: .copy-code}
Provisioning response example:
```json
{
"status":"SUCCESS",
"credentialsType":"ACCESS_TOKEN",
"credentialsValue":"sLzc0gDAZPkGMzFVTyUY"
}
```
{: .copy-code}
#### Sample script
To communicate with ThingsBoard we will use CoAPthon3 module, so we should install it:
```bash
pip3 install coapthon3 --user
```
{: .copy-code}
The script source code is available below. You may copy-paste it to a file, for example:
```bash
device-provision-example.py
```
{: .copy-code}
Now you should run the script and follow the steps inside.
You may launch the script using python 3:
```bash
python3 device-provision-example.py
```
{: .copy-code}
The script source code:
```python
from coapthon.client.helperclient import HelperClient
from json import loads, dumps
def collect_required_data():
config = {}
print("\n\n", "="*80, sep="")
print(" "*10, "\033[1m\033[94mThingsBoard device provisioning without authorization example script. CoAP API\033[0m", sep="")
print("="*80, "\n\n", sep="")
host = input("Please write your ThingsBoard \033[93mhost\033[0m or leave it blank to use default (cloud.thingsboard.io): ")
config["host"] = host if host else "cloud.thingsboard.io"
port = input("Please write your ThingsBoard \033[93mCoAP port\033[0m or leave it blank to use default (5683): ")
config["port"] = int(port) if port else 5683
config["provision_device_key"] = input("Please write \033[93mprovision device key\033[0m: ")
config["provision_device_secret"] = input("Please write \033[93mprovision device secret\033[0m: ")
device_name = input("Please write \033[93mdevice name\033[0m or leave it blank to generate: ")
if device_name:
config["device_name"] = device_name
print("\n", "="*80, "\n", sep="")
return config
# Example for message to ThingsBoard
to_publish = {
"stringKey": "value1",
"booleanKey": True,
"doubleKey": 42.0,
"longKey": 73,
"jsonKey": {
"someNumber": 42,
"someArray": [1, 2, 3],
"someNestedObject": {"key": "value"}
}
}
if __name__ == '__main__':
config = collect_required_data()
THINGSBOARD_HOST = config["host"] # ThingsBoard instance host
THINGSBOARD_PORT = config["port"] # ThingsBoard instance MQTT port
PROVISION_REQUEST = {"provisionDeviceKey": config["provision_device_key"], # Provision device key, replace this value with your value from device profile.
"provisionDeviceSecret": config["provision_device_secret"], # Provision device secret, replace this value with your value from device profile.
}
if config.get("device_name") is not None:
PROVISION_REQUEST["deviceName"] = config["device_name"]
client = HelperClient(server=(THINGSBOARD_HOST, THINGSBOARD_PORT))
response = client.post('/api/v1/provision', dumps(PROVISION_REQUEST))
client.stop()
decoded_response = loads(response.payload)
print("Received response: ")
print(decoded_response)
received_token = decoded_response.get("credentialsValue")
if received_token is not None:
thingsboardClient = HelperClient(server=(THINGSBOARD_HOST, THINGSBOARD_PORT))
response = thingsboardClient.post('/api/v1/%s/telemetry' % (received_token,), dumps(to_publish))
print("[THINGSBOARD CLIENT] Response from Thingsboard.")
print(response)
thingsboardClient.stop()
else:
print("Failed to get access token from response.")
print(decoded_response.get("errorMsg"))
```
{: .copy-code}
| 35.056 | 168 | 0.654267 | eng_Latn | 0.731032 |
6f799eedb9b187f8e28e1c206d8da0fe3ff1a657 | 1,154 | md | Markdown | README.md | kassyn/x-sky | 668998fa71ec6a9abf1617229d8d48300ae0d215 | [
"MIT"
] | 1 | 2015-03-06T19:28:52.000Z | 2015-03-06T19:28:52.000Z | README.md | kassyn/x-sky | 668998fa71ec6a9abf1617229d8d48300ae0d215 | [
"MIT"
] | null | null | null | README.md | kassyn/x-sky | 668998fa71ec6a9abf1617229d8d48300ae0d215 | [
"MIT"
] | null | null | null | # <x-sky>
Web Component Sky.
> Maintained by [Accácio Jasson.](https://twitter.com/KassynFrank).
## Demo
> [Check it live](http://kassyn.github.io/x-sky).
## Usage
1. Import Web Components:
```html
<script src="//cdnjs.cloudflare.com/ajax/libs/polymer/0.0.20130905/polymer.min.js"></script>
```
2. Import Custom Element:
```html
<link rel="import" href="src/x-sky.html">
```
3. Using it!
```html
<x-sky count="200" height="300"></x-sky>
```
## Options
Attribute | Options | Default | Description
--- | --- | --- | ---
`count` | *integer* | `100` | amount of stars
`height` | *integer* | `200` | height of the container with the sky
## Contributing
1. Fork it!
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -m 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D
## License
[MIT License](http://opensource.org/licenses/MIT)
## Thanks
[Eduard](https://github.com/educastellano)
| 21.37037 | 96 | 0.578856 | eng_Latn | 0.304801 |
6f7a788648b009a147f1c28ee1d524dd33d1e507 | 2,151 | md | Markdown | README.md | AntonyThorpe/silverstripe-shop-bankdeposit | 6cc00ccc3bb5fb10dad38302f12d7f8540c11a3d | [
"MIT"
] | 1 | 2016-10-26T11:54:10.000Z | 2016-10-26T11:54:10.000Z | README.md | AntonyThorpe/silverstripe-shop-bankdeposit | 6cc00ccc3bb5fb10dad38302f12d7f8540c11a3d | [
"MIT"
] | null | null | null | README.md | AntonyThorpe/silverstripe-shop-bankdeposit | 6cc00ccc3bb5fb10dad38302f12d7f8540c11a3d | [
"MIT"
] | 2 | 2016-05-09T04:36:29.000Z | 2018-07-16T13:30:00.000Z | # silvershop-bankdeposit
A Silvershop submodule that adds bank deposit as a Payment Method
[](https://travis-ci.org/AntonyThorpe/silvershop-bankdeposit)
[](https://scrutinizer-ci.com/g/antonythorpe/silvershop-bankdeposit/?branch=master)
[](https://packagist.org/packages/antonythorpe/silvershop-bankdeposit)
[](https://packagist.org/packages/antonythorpe/silvershop-bankdeposit)
[](https://packagist.org/packages/antonythorpe/silvershop-bankdeposit)
[](https://packagist.org/packages/antonythorpe/silvershop-bankdeposit)
## Features
* Provides a Bank Account tab under Settings/Shop to add your organisation's bank account number and payment messages
* Includes bank account number & messages in emails, the order review, and a note during the checkout process
* Localisation options available
## How it works
* Utilises the 'Manual' payment method
* You add various includes to your templates plus customisations via language file
## Requirements
* [Silvershop module (a Silverstripe module)](https://github.com/silvershop/silvershop-core)
* [Omnipay/Manual](https://github.com/thephpleague/omnipay-manual)
* Will need `composer require league/omnipay:^3` too.
## Warning
It is assumed that people accessing the Settings folder can be trusted. This is where the bank account number is entered. If you think that a YAML file would be more secure, then please feel free to submit a pull request.
## Documentation
[Index](/docs/en/index.md)
## Support
None sorry.
## Change Log
[Link](changelog.md)
## Contributions
[Link](contributing.md)
## License
[MIT](LICENSE)
| 51.214286 | 223 | 0.793119 | eng_Latn | 0.612438 |
6f7b1e401fc687dcfe90ca6f3a118bc9de1fe221 | 900 | md | Markdown | docs/api/constants.zh-CN.md | wuchunfu/am-editor | 9cdc0c06bba572f7e1c2818560e9e876f676b6bb | [
"MIT"
] | 320 | 2021-07-27T08:52:10.000Z | 2022-02-14T14:40:43.000Z | docs/api/constants.zh-CN.md | wuchunfu/am-editor | 9cdc0c06bba572f7e1c2818560e9e876f676b6bb | [
"MIT"
] | 45 | 2021-08-17T05:16:06.000Z | 2022-02-14T04:56:09.000Z | docs/api/constants.zh-CN.md | wuchunfu/am-editor | 9cdc0c06bba572f7e1c2818560e9e876f676b6bb | [
"MIT"
] | 114 | 2021-07-27T06:15:38.000Z | 2022-02-14T07:39:10.000Z | # 常量
## 节点
### `DATA-ID`
data-id
### `DATA_ELEMENT`
标记节点类型
### `ROOT`
标记为根节点
### `ROOT_SELECTOR`
根节点选择器
### `UI`
标记为 UI 节点
### `UI_SELECTOR`
UI 节点 CSS 选择器
### `EDITABLE`
标记为可编辑器节点
### `EDITABLE_SELECTOR`
可编辑节点 CSS 选择器
### `DATA_TRANSIENT_ATTRIBUTES`
标记不参与协同的节点属性
### `DATA_TRANSIENT_ELEMENT`
标记不参与协同的节点
## 选区范围
### `ANCHOR`
开始节点标记
### `FOCUS`
结束节点标记
### `CURSOR`
开始位置和结束位置重合处标记
### `ANCHOR_SELECTOR`
开始节点标记 CSS 查询器
### `FOCUS_SELECTOR`
结束节点标记 CSS 查询器
### `CURSOR_SELECTOR`
开始位置和结束位置重合处标记 CSS 查询器
## 卡片
### `CARD_TAG`
卡片节点标签名称
### `CARD_KEY`
卡片名称
### `READY_CARD_KEY`
待渲染卡片名称
### `CARD_TYPE_KEY`
卡片类型
### `CARD_VALUE_KEY`
卡片值
### `CARD_ELEMENT_KEY`
卡片节点
### `CARD_SELECTOR`
卡片 CSS 选择器
### `READY_CARD_SELECTOR`
待渲染卡片 CSS 选择器
### `CARD_LEFT_SELECTOR`
卡片左侧 CSS 选择器
### `CARD_CENTER_SELECTOR`
卡片中心节点 CSS 选择器
### `CARD_RIGHT_SELECTOR`
卡片右侧 CSS 选择器
| 7.758621 | 31 | 0.652222 | yue_Hant | 0.995641 |
6f7b357dd4d0bcfc7c009aa0ff3ae98c27d9404c | 839 | md | Markdown | content/docs/installation/_index.md | PyvesB/docs.cucumber.io | 65eb695aa623e74a8763a284d0641f01b64385e1 | [
"MIT"
] | 64 | 2017-07-04T04:23:55.000Z | 2021-03-01T17:46:05.000Z | content/docs/installation/_index.md | PyvesB/docs.cucumber.io | 65eb695aa623e74a8763a284d0641f01b64385e1 | [
"MIT"
] | 446 | 2017-05-17T15:35:07.000Z | 2021-04-08T15:01:50.000Z | content/docs/installation/_index.md | PyvesB/docs.cucumber.io | 65eb695aa623e74a8763a284d0641f01b64385e1 | [
"MIT"
] | 379 | 2017-05-24T06:23:45.000Z | 2021-04-08T23:45:56.000Z | ---
title: Installation
weight: 1110
menu: main
iconClass: far fa-download
collapseChildren: true
---
Cucumber is available for most mainstream programming languages.
We recommend choosing an implementation for the same platform or
programming language as the production code.
* <span class="tag is-success">official</span> implementations are hosted under [cucumber](https://github.com/cucumber).
* <span class="tag is-info">semi-official</span> implementations are hosted elsewhere, but use components from [cucumber](https://github.com/cucumber).
* <span class="tag is-dark">unofficial</span> implementations are hosted elsewhere and don't use any components from [cucumber](https://github.com/cucumber).
* <span class="tag is-danger">unmaintained</span> implementations are official, but unmaintained and in need of new maintainers.
| 49.352941 | 157 | 0.785459 | eng_Latn | 0.980379 |
6f7b40507d110a6b582edc92bdfff1c1c59bcae9 | 1,715 | md | Markdown | assets/1700-1799/1703.Minimum Adjacent Swaps for K Consecutive Ones/README_EN.md | yanglr/LeetCodeOJ | 27dd1e4a2442b707deae7921e0118752248bef5e | [
"MIT"
] | 45 | 2021-07-25T00:45:43.000Z | 2022-03-24T05:10:43.000Z | assets/1700-1799/1703.Minimum Adjacent Swaps for K Consecutive Ones/README_EN.md | yanglr/LeetCodeOJ | 27dd1e4a2442b707deae7921e0118752248bef5e | [
"MIT"
] | null | null | null | assets/1700-1799/1703.Minimum Adjacent Swaps for K Consecutive Ones/README_EN.md | yanglr/LeetCodeOJ | 27dd1e4a2442b707deae7921e0118752248bef5e | [
"MIT"
] | 15 | 2021-07-25T00:40:52.000Z | 2021-12-27T06:25:31.000Z | # [1703. Minimum Adjacent Swaps for K Consecutive Ones](https://leetcode.com/problems/minimum-adjacent-swaps-for-k-consecutive-ones)
## Description
<p>You are given an integer array, <code>nums</code>, and an integer <code>k</code>. <code>nums</code> comprises of only <code>0</code>'s and <code>1</code>'s. In one move, you can choose two <strong>adjacent</strong> indices and swap their values.</p>
<p>Return <em>the <strong>minimum</strong> number of moves required so that </em><code>nums</code><em> has </em><code>k</code><em> <strong>consecutive</strong> </em><code>1</code><em>'s</em>.</p>
<p> </p>
<p><strong>Example 1:</strong></p>
<pre>
<strong>Input:</strong> nums = [1,0,0,1,0,1], k = 2
<strong>Output:</strong> 1
<strong>Explanation:</strong> In 1 move, nums could be [1,0,0,0,<u>1</u>,<u>1</u>] and have 2 consecutive 1's.
</pre>
<p><strong>Example 2:</strong></p>
<pre>
<strong>Input:</strong> nums = [1,0,0,0,0,0,1,1], k = 3
<strong>Output:</strong> 5
<strong>Explanation:</strong> In 5 moves, the leftmost 1 can be shifted right until nums = [0,0,0,0,0,<u>1</u>,<u>1</u>,<u>1</u>].
</pre>
<p><strong>Example 3:</strong></p>
<pre>
<strong>Input:</strong> nums = [1,1,0,1], k = 2
<strong>Output:</strong> 0
<strong>Explanation:</strong> nums already has 2 consecutive 1's.
</pre>
<p> </p>
<p><strong>Constraints:</strong></p>
<ul>
<li><code>1 <= nums.length <= 10<sup>5</sup></code></li>
<li><code>nums[i]</code> is <code>0</code> or <code>1</code>.</li>
<li><code>1 <= k <= sum(nums)</code></li>
</ul>
## Solutions
<!-- tabs:start -->
### **Python3**
```python
```
### **Java**
```java
```
### **...**
```
```
<!-- tabs:end -->
| 24.855072 | 260 | 0.616327 | eng_Latn | 0.495492 |
6f7b5180236e838c35bbac61a799aaabdcfb24d7 | 1,894 | md | Markdown | mleap-databricks-runtime-fat/README.md | neilsummers/mleap | 80fc0ea25e617e26316320478c8a75e79e20f8a6 | [
"Apache-2.0"
] | 1,401 | 2017-01-07T03:34:44.000Z | 2022-03-31T22:17:58.000Z | mleap-databricks-runtime-fat/README.md | liang0/mleap | 41dbde99e389873fc609083cce5d610cea9e9170 | [
"Apache-2.0"
] | 546 | 2016-12-30T19:10:55.000Z | 2022-03-31T16:56:52.000Z | mleap-databricks-runtime-fat/README.md | liang0/mleap | 41dbde99e389873fc609083cce5d610cea9e9170 | [
"Apache-2.0"
] | 326 | 2017-01-24T10:35:41.000Z | 2022-03-15T15:53:17.000Z | # MLeap Databricks ML Runtime Fat JAR
This is the fat jar that has all of the MLeap and dependencies of MLeap included. All 3rd-party
dependencies are shaded into the jar. This JAR is not the one published to maven central,
as the pom file would still contain all of the 3rd-party dependencies. Instead, see the
`mleap-databricks-runtime` submodule, which provides a facade to this JAR for publishing
to maven repos.
## Installation
Requirements:
1. `xgboost4j-spark` must be in the local M2 repository to build. [xgboost4j-spark installation](http://xgboost.readthedocs.io/en/latest/jvm/)
After making sure `xgboost` is available to compilation, get a local copy of MLeap and build the Databricks ML Runtime Fat JAR.
```
# Use --recursive to get the submodule with MLeap protobuf definitions
git clone --recursive https://github.com/combust/mleap.git
cd mleap
# Compile the Databrics Runtime Assembly JAR
sbt mleap-databricks-runtime-fat/assembly
# Verify that it worked, you should see a file like: mleap-databricks-runtime-fat-assembly-<mleap version>-SNAPSHOT.jar
ls mleap-databricks-runtime-fat/target/scala-2.11
```
## Usage
See the README.md file in `mleap-databricks-runtime-testkit` for sample usage of the JAR and how to run basic tests.
## Namespaces
There are 3 namespaces allowed in this JAR, all other namespaces are shaded if required for execution.
1. `ml.combust`
2. `org.apache.spark`
3. `ml.dmlc.xgboost`
Allowed namespaces may be added in the future with more integrations with 3rd-party ML libraries.
## Shading
All shaded dependencies are transformed into the `ml.combust.mleap.shaded` namespace and can be found there.
## Provided
Certain dependencies are expected to be provided. These include:
1. Spark ML and its dependencies
2. TensorFlow JAR and dynamic library configured on classpath
3. XGBoost Spark and dynamic library configured on classpath
| 35.074074 | 142 | 0.785111 | eng_Latn | 0.992419 |
6f7bb06fe0ad9438f66a3067fa46aa528788ba9c | 5,594 | md | Markdown | docs/configuration/README.md | Suresh-Nakkeran/modelmesh-serving | eab350fda12359bffd40b1d76bb40dbd9598eda9 | [
"Apache-2.0"
] | 54 | 2021-08-09T17:01:53.000Z | 2022-03-30T00:41:20.000Z | docs/configuration/README.md | Suresh-Nakkeran/modelmesh-serving | eab350fda12359bffd40b1d76bb40dbd9598eda9 | [
"Apache-2.0"
] | 125 | 2021-08-09T22:26:28.000Z | 2022-03-31T23:53:57.000Z | docs/configuration/README.md | Suresh-Nakkeran/modelmesh-serving | eab350fda12359bffd40b1d76bb40dbd9598eda9 | [
"Apache-2.0"
] | 26 | 2021-08-10T00:26:09.000Z | 2022-03-21T20:09:27.000Z | # Configuration
System-wide configuration parameters can be set by creating a ConfigMap with name `model-serving-config`. It should contain a single key named `config.yaml`, whose value is a yaml doc containing the configuration. All parameters have defaults and are optional. If the ConfigMap does not exist, all parameters will take their defaults.
The configuration can be updated at runtime and will take effect immediately. Be aware however that certain changes could cause temporary disruption to the service - in particular changing the service name, port, TLS configuration and/or headlessness.
Example:
```yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: model-serving-config
data:
config.yaml: |
#Sample config overrides
inferenceServiceName: "modelmesh-serving"
inferenceServicePort: 8033
podsPerRuntime: 2
metrics:
enabled: true
```
The following parameters are currently supported. _Note_ the keys are expressed here in camel case but are in fact case-insensitive.
| Variable | Description | Default |
| ------------------------------------------ | ----------------------------------------------------------------------------------------------------- | ------------------- |
| `inferenceServiceName` | The service name which is used for communication with the serving server | `modelmesh-serving` |
| `inferenceServicePort` | The port number for communication with the inferencing service | `8033` |
| `storageSecretName` | The secret containing entries for each storage backend from which models can be loaded (\* see below) | `storage-config` |
| `podsPerRuntime` | Number of server Pods to run per enabled Serving Runtime (\*\* see below) | `2` |
| `tls.secretName` | Kubernetes TLS type secret to use for securing the Service; no TLS if empty (\*\*\* see below) | |
| `tls.clientAuth` | Enables mutual TLS authentication. Supported values are `required` and `optional`, disabled if empty | |
| `headlessService` | Whether the Service should be headless (recommended) | `true` |
| `enableAccessLogging` | Enables logging of each request to the model server | `false` |
| `serviceAccountName` | The service account to use for runtime Pods | `modelmesh` |
| `metrics.enabled` | Enables serving of Prometheus metrics | `true` |
| `metrics.port` | Port on which to serve metrics via the `/metrics` endpoint | `2112` |
| `metrics.scheme` | Scheme to use for the `/metrics` endpoint (`http` or `https`) | `https` |
| `metrics.disablePrometheusOperatorSupport` | Disable the support of Prometheus operator for metrics only if `metrics.enabled` is true | `false` |
| `scaleToZero.enabled` | Whether to scale down Serving Runtimes that have no Predictors | `true` |
| `scaleToZero.gracePeriodSeconds` | The number of seconds to wait after Predictors are deleted before scaling to zero | `60` |
| `grpcMaxMessageSizeBytes` | The max number of bytes for the gRPC request payloads (\*\*\*\* see below) | `16777216` (16MiB) |
| `restProxy.enabled` | Enables the provided REST proxy container being deployed in each ServingRuntime deployment | `true` |
| `restProxy.port` | Port on which the REST proxy to serve REST requests | `8008` |
(\*) Currently requires a controller restart to take effect
(\*\*) This parameter will likely be removed in a future release; the Pod replica counts will become more dynamic.
(\*\*\*) The TLS configuration secret allows for keys:
- `tls.crt` - path to TLS secret certificate
- `tls.key` - path to TLS secret key
- `ca.crt` (optional) - single path or comma-separated list of paths to trusted certificates
(\*\*\*\*) The max gRPC request payload size depends on both this setting and adjusting the model serving runtimes' max message limit. See [inference docs](predictors/run-inference) for details.
## Logging
By default, the internal logging of the controller component is set to log stacktraces on errors and sampling, which is the [Zap](https://pkg.go.dev/sigs.k8s.io/controller-runtime/pkg/log/zap#Options) production configuration. To enable the development mode for logging (stacktraces on warnings, no sampling, prettier log outputs), set the environment variable `DEV_MODE_LOGGING=true` on the ModelMesh Serving controller:
```sh
kubectl set env deploy/modelmesh-controller DEV_MODE_LOGGING=true
```
| 84.757576 | 421 | 0.55774 | eng_Latn | 0.982733 |
6f7bf4fe073fc112f4395d1b4cf490108a286026 | 2,060 | md | Markdown | _posts/2017-04-03-spark-structtype.md | Shanshan-IC/Shanshan-IC.github.io | ebb926806c13ccb3d7944251106c1f76ad43b489 | [
"MIT"
] | null | null | null | _posts/2017-04-03-spark-structtype.md | Shanshan-IC/Shanshan-IC.github.io | ebb926806c13ccb3d7944251106c1f76ad43b489 | [
"MIT"
] | null | null | null | _posts/2017-04-03-spark-structtype.md | Shanshan-IC/Shanshan-IC.github.io | ebb926806c13ccb3d7944251106c1f76ad43b489 | [
"MIT"
] | null | null | null | ---
layout: post
title: "StructType for Spark to create a DataFrame"
category: Spark
tags: Spark
---
* content
{:toc}
It is from [stack overflow](http://stackoverflow.com/questions/31615657/how-to-add-a-new-struct-column-to-a-dataframe)
## StructType
I assume you start with some kind of flat schema like this:
```
root
|-- lat: double (nullable = false)
|-- long: double (nullable = false)
|-- key: string (nullable = false)
```
First lets create example data:
```scala
import org.apache.spark.sql.Row
import org.apache.spark.sql.functions.{col, udf}
import org.apache.spark.sql.types._
val rdd = sc.parallelize(
Row(52.23, 21.01, "Warsaw") :: Row(42.30, 9.15, "Corte") :: Nil)
val schema = StructType(
StructField("lat", DoubleType, false) ::
StructField("long", DoubleType, false) ::
StructField("key", StringType, false) ::Nil)
val df = sqlContext.createDataFrame(rdd, schema)
```
An easy way is to use an udf and case class:
```scala
case class Location(lat: Double, long: Double)
val makeLocation = udf((lat: Double, long: Double) => Location(lat, long))
val dfRes = df.
withColumn("location", makeLocation(col("lat"), col("long"))).
drop("lat").
drop("long")
dfRes.printSchema
```
and we get
```s
root
|-- key: string (nullable = false)
|-- location: struct (nullable = true)
| |-- lat: double (nullable = false)
| |-- long: double (nullable = false)
```
A hard way is to transform your data and apply schema afterwards:
```scala
val rddRes = df.
map{case Row(lat, long, key) => Row(key, Row(lat, long))}
val schemaRes = StructType(
StructField("key", StringType, false) ::
StructField("location", StructType(
StructField("lat", DoubleType, false) ::
StructField("long", DoubleType, false) :: Nil
), true) :: Nil
)
sqlContext.createDataFrame(rddRes, schemaRes).show
```
and we get an expected output
```
+------+-------------+
| key| location|
+------+-------------+
|Warsaw|[52.23,21.01]|
| Corte| [42.3,9.15]|
+------+-------------+
```
| 22.150538 | 118 | 0.633981 | eng_Latn | 0.631773 |
6f7c8cb36402c116428944fc6996d7d26d3be34a | 66 | md | Markdown | README.md | snowgears/Wallet | 10a8868d8896209a38b2f5e8d6b198f0021e34fa | [
"MIT"
] | null | null | null | README.md | snowgears/Wallet | 10a8868d8896209a38b2f5e8d6b198f0021e34fa | [
"MIT"
] | null | null | null | README.md | snowgears/Wallet | 10a8868d8896209a38b2f5e8d6b198f0021e34fa | [
"MIT"
] | null | null | null | # Wallet
Minecraft plugin to manage physical and digital currency
| 22 | 56 | 0.833333 | eng_Latn | 0.997036 |
6f7d426f7ec1b5ffdcde7f14d7d351d7d2d524f8 | 539 | md | Markdown | VBA/Office-F1-Landing/file-already-exists-error-58office-shared-vblr6-chm1011166.md | oloier/VBA-content | 6b3cb5769808b7e18e3aff55a26363ebe78e4578 | [
"CC-BY-4.0",
"MIT"
] | 584 | 2015-09-01T10:09:09.000Z | 2022-03-30T15:47:20.000Z | VBA/Office-F1-Landing/file-already-exists-error-58office-shared-vblr6-chm1011166.md | oloier/VBA-content | 6b3cb5769808b7e18e3aff55a26363ebe78e4578 | [
"CC-BY-4.0",
"MIT"
] | 585 | 2015-08-28T20:20:03.000Z | 2018-08-31T03:09:51.000Z | VBA/Office-F1-Landing/file-already-exists-error-58office-shared-vblr6-chm1011166.md | oloier/VBA-content | 6b3cb5769808b7e18e3aff55a26363ebe78e4578 | [
"CC-BY-4.0",
"MIT"
] | 590 | 2015-09-01T10:09:09.000Z | 2021-09-27T08:02:27.000Z | ---
title: File already exists (Error 58), Office Shared [vblr6.chm1011166]
keywords: vblr6.chm1011166
f1_keywords:
- vblr6.chm1011166
ms.prod: office
ms.assetid: b82a1b28-fa34-49a7-9520-461408e109ce
ms.date: 06/08/2017
---
# File already exists (Error 58), Office Shared [vblr6.chm1011166]
Hi there! You have landed on one of our F1 Help redirector pages. Please select the topic you were looking for below.
[File already exists (Error 58)](http://msdn.microsoft.com/library/11d336e1-4bc1-ece8-e347-fa4ac2abe876%28Office.15%29.aspx)
| 29.944444 | 124 | 0.769944 | eng_Latn | 0.705321 |
6f7e497712a204ea77abf216ad451f8729d0027f | 431 | md | Markdown | productivity-tools/jupyter-notebook/README.md | tianhaoz95-xilinx/developer-note | 4c01a2daae54eb9a8dcc66c3c2e55698666e4572 | [
"MIT"
] | null | null | null | productivity-tools/jupyter-notebook/README.md | tianhaoz95-xilinx/developer-note | 4c01a2daae54eb9a8dcc66c3c2e55698666e4572 | [
"MIT"
] | null | null | null | productivity-tools/jupyter-notebook/README.md | tianhaoz95-xilinx/developer-note | 4c01a2daae54eb9a8dcc66c3c2e55698666e4572 | [
"MIT"
] | null | null | null | # Jupyter Notebook
## Start in Virtual Environment
```bash
# first ipykernel has to be installed
pip install ipykernel
# replace your_awesome_project_name with your preferred ID
ipython kernel install --user --name=your_awesome_project_name
# the notebook can be run from anywhere and the kernel will always be there
jupyter notebook
# boom, magic
```
 | 23.944444 | 75 | 0.786543 | eng_Latn | 0.958015 |
6f7e6d83e2526b16f335eb84c6e9b8f3a069f093 | 1,386 | md | Markdown | _posts/2021-12-28-Particular.Sadness.of.Lemon.Cake.md | programmerdays/programmerdays.github.io | 890279da99f5db5dedcdc9ede8a44ca11494fe80 | [
"MIT"
] | null | null | null | _posts/2021-12-28-Particular.Sadness.of.Lemon.Cake.md | programmerdays/programmerdays.github.io | 890279da99f5db5dedcdc9ede8a44ca11494fe80 | [
"MIT"
] | null | null | null | _posts/2021-12-28-Particular.Sadness.of.Lemon.Cake.md | programmerdays/programmerdays.github.io | 890279da99f5db5dedcdc9ede8a44ca11494fe80 | [
"MIT"
] | null | null | null | ---
layout: post
title: Particular Sadness of Lemon Cake
date: 2021-12-28
categories: [Reading]
comments: true
---
I finished reading [The Particular Sadness of Lemon Cake](https://www.amazon.com/Particular-Sadness-Lemon-Cake/dp/0385720963) by Aimee Bender.
The premise of the book is that the author is able to feel the emotions and mindsets of the people who made whatever food she is eating. This super power enables her to gain deep insight into people.
I was drawn to the book because of the supernatural premise. I don't consider myself to be a full on science fiction or fantasy fan. Whenever I try books in these genres, I often find it a little too intense for me. Instead, I prefer books with just a few elements of science fiction and fantasy in the context of a mostly normal world. The slight alterations of a few super/fantastical elements make for an interesting contrast. The Particular Sadness of Lemon Cake hits the mark. How does an otherwise regular girl deal with slightly advanced supernatural powers?
After you get used to the narrator's ability to taste the feelings of others, there are some other interesting aspects of the story. There's a bit of mystery,which I enjoyed. But the really remarkable thing was the descriptions of the feelings of people. The depth and detail is incredible.
It was an interesting and moving book. I'd recommend it to others. | 81.529412 | 565 | 0.795094 | eng_Latn | 0.999761 |
6f7f7f60175a0f9e73788fed9970b9a3ba79801c | 14,420 | md | Markdown | README.md | OctopusSamples/StepPackage-HelloWorld | 5f1f484d063f58bf36749327d5d708e1ff10d439 | [
"Apache-2.0"
] | null | null | null | README.md | OctopusSamples/StepPackage-HelloWorld | 5f1f484d063f58bf36749327d5d708e1ff10d439 | [
"Apache-2.0"
] | null | null | null | README.md | OctopusSamples/StepPackage-HelloWorld | 5f1f484d063f58bf36749327d5d708e1ff10d439 | [
"Apache-2.0"
] | 1 | 2021-07-13T00:49:36.000Z | 2021-07-13T00:49:36.000Z | Step packages are an evolution in the development of Octopus steps. [Step packages address many of the concerns](https://github.com/OctopusDeploy/Architecture/tree/main/Steps) that made it difficult to implement new functionality as Octopus scaled up in terms of internal team size and external surface area. In particular, step packages are:
* Developed outside the main Octopus code base.
* Tested as isolated and independent projects.
* Distributed on their own independent timelines (not quite implemented yet).
* Independently versioned, with each version able to be run side-by-side (not implemented yet).
This sample project provides a starting point for anyone looking to create a new step package. The code in this repository defines a "Hello World" target and step demonstrating a minimal step package implementation.
## Project directory structure
The directory structure of a step package is shown below:
* `\`
* `steps` - A directory containing one or more step definitions.
* `<step-name>` - A directory containing the definition of a step. There may be many of these directories defining many steps within a single step package.
* `src` - The parent directory containing the step code and assets.
* `__tests__` - The directory containing step tests.
* `executor.spec.ts` - Tests validating the logic in the `executor.ts` file.
* `executor.ts` - The code to be executed when a step is run by Octopus.
* `inputs.ts` - The definition of the inputs required by the step.
* `logo.svg` - The image to be displayed in the Octopus web UI for the step.
* `metadata.json` - The step metadata.
* `ui.ts` - The step UI definition.
* `validation.ts` - The step validation rules.
* `targets` - A directory containing one or more target definitions.
* `<target-name>` - A directory containing the definition of a target. There may be many of these directories defining many steps within a single step package.
* `src` - The parent directory containing the target code and assets.
* `__tests__` - The directory containing target tests.
* `executor.spec.ts` - Tests validating the logic in the `executor.ts` file.
* `executor.ts` - The code to be executed when a target health check is run by Octopus.
* `inputs.ts` - The definition of the inputs required by the target.
* `logo.svg` - The image to be displayed in the Octopus web UI for the target.
* `metadata.json` - The target metadata.
* `ui.ts` - The target UI definition.
* `validation.ts` - The target validation rules.
* `.eslintignore` - The [ESLint ignore file](https://eslint.org/docs/user-guide/configuring/ignoring-code#the-eslintignore-file).
* `.eslintrc.js` - The [ESLint configuration file](https://eslint.org/docs/user-guide/configuring/).
* `.gitignore` - The [git ignore file](https://git-scm.com/docs/gitignore).
* `.prettierrc` - The [prettier configuration file](https://prettier.io/docs/en/configuration.html).
* `global.d.ts` - The [TypeScript global libraries](https://www.typescriptlang.org/docs/handbook/declaration-files/templates/global-d-ts.html).
* `package.json` - The [Node.js project file](https://nodejs.org/en/knowledge/getting-started/npm/what-is-the-file-package-json/).
* `package-lock.json` - The [specific package versions](https://docs.npmjs.com/cli/v7/configuring-npm/package-lock-json) to be retrieved by npm.
* `tsconfig.json` - The [TypeScript compiler options file](https://www.typescriptlang.org/docs/handbook/tsconfig-json.html).
## Creating a new target
Creating a new target involves creating the following files under the `targets/<target-name>-target/src` directory. In the case of this sample step package, we'll create them under `targets/hello-world-target/src`:
* `metadata.json`
* `inputs.ts`
* `executor.js`
* `ui.ts`
* `validation.ts`
### `metadata.json`
The `metadata.json` file provides details about the target. A sample is shown below:
```json
{
"schemaVersion": "1.0.0",
"version": "0.0.0",
"type": "deployment-target",
"id": "hello-world-target",
"name": "Hello world target",
"description": "An example target that does nothing useful",
"categories": [
"Linux"
],
"launcher": "node"
}
```
* `schemaVersion` is the version of the metadata file. `1.0.0` is the only version available.
* `version` is the version of the target. Versioning is covered in detail [here](https://github.com/OctopusDeploy/Architecture/blob/main/Steps/Concepts/Versioning.md).
* `type` defines the type of resource to be created. It must be `deployment-target` for a target.
* `id` is the resource ID.
* `name` is the name of the target displayed by the Octopus web UI.
* `description` is the description of the target displayed by the Octopus UI.
* `categories` is an array containing one or more target categories display by the Octopus UI where the target will be listed.
* `launcher` defines how the step is executed. A value of `node` means the step is executed by Node.js.
### `inputs.ts`
The `inputs.ts` file exports an interface defining the input fields required by the target. This interface is consumed by `executor.ts` to read the values when performing the target's health check, `ui.ts` to build up the form exposed in the Octopus web UI, and `validate.ts` to verify new values.
An example is shown below exposing a single string field:
```typescript
export default interface HelloWorldTargetInputs {
greetingPrefix: string;
}
```
### `executor.ts`
Targets perform a health check to validate their inputs and check the state of the system they represent. This health check is performed by the function exported by the `executor.ts` file.
The example below prints some text to the log during a health check, and will always pass, meaning the target is always healthy:
```typescript
import { Handler } from "@octopusdeploy/step-api";
import HelloWorldTargetInputs from "./inputs";
const HelloWorldDeploymentTargetHealthCheckExecutor: Handler<HelloWorldTargetInputs> = async (_, context) => {
context.print("Hello world target is healthy");
};
export default HelloWorldDeploymentTargetHealthCheckExecutor;
```
### `ui.ts`
The form displayed by the Octopus web UI is defined by the function exported by the `ui.ts` file. The form is defined as an instance of the `DeploymentTargetUI` interface, which has two functions: `createInitialInputs` and `editInputsForm`.
The `createInitialInputs` function allows the initial default field values to be defined.
The `editInputsForm` function provides a DSL for building the user interface. The first parameter is the inputs defined in `inputs.ts`. The second parameter is an instance of `AvailableDeploymentTargetComponents`, which has factory functions for creating various input widgets like text fields, lists, radio buttons etc.
Here we define the initial value of the `greetingPrefix` input to be `Hello`, and build the form with a single `text` input:
```typescript
import { DeploymentTargetUI } from "@octopusdeploy/step-api";
import HelloWorldTargetInputs from "./inputs";
export const HelloWorldTargetUI: DeploymentTargetUI<HelloWorldTargetInputs> = {
createInitialInputs: () => {
return {
greetingPrefix: "Hello"
};
},
editInputsForm: (inputs, { section, text }) => [
section({
title: "Greeting",
content: [
text({
input: inputs.greetingPrefix,
label: "Greeting Prefix",
helpText: "The beginning of the greeting",
}),
],
}),
],
};
export default HelloWorldTargetUI;
```
### `validation.ts`
Form validation is performed by the function exported by the `validate.ts` file. This function returns an array of `ValueValidator` objects, and takes two parameters:
1. The step inputs as [input paths](https://github.com/OctopusDeploy/Architecture/blob/main/Steps/Concepts/InputsAndOutputs.md#input-paths).
2. A validation function that returns a `ValueValidator` and takes two parameters:
1. An input path.
2. A function returning a string containing the error code (or returns nothing if there is no validation error) and takes the input value (retrieved from the input path) as the first parameter.
Here is an example:
```typescript
import { ValidateInputs } from "@octopusdeploy/step-api";
import HelloWorldTargetInputs from "./inputs";
const validateInputs: ValidateInputs<HelloWorldTargetInputs> = (inputs, validate) => {
return [
validate(inputs.greetingPrefix, (greeting) => {
if (greeting === "") return "Greeting can not be empty";
}),
];
};
export default validateInputs;
```
## Creating a new step
Creating a new step involves creating the following files under the `steps/<step-name>/src` directory. In the case of this sample step package, we'll create them under `steps/hello-world/src`:
* `metadata.json`
* `inputs.ts`
* `executor.js`
* `ui.ts`
* `validation.ts`
### `metadata.json`
The `metadata.json` provides details about the step. A sample is shown below:
```json
{
"schemaVersion": "1.0.0",
"version": "0.0.0",
"type": "step",
"id": "hello-world-upload",
"name": "Hello World",
"description": "An example step",
"categories": [
"BuiltInStep"
],
"canRunOnDeploymentTarget": false,
"launcher": "node"
}
```
The following fields make up this file:
* `schemaVersion` is the version of the metadata file. `1.0.0` is the only version available.
* `version` is the version of the step. Versioning is covered in detail [here](https://github.com/OctopusDeploy/Architecture/blob/main/Steps/Concepts/Versioning.md).
* `type` defines the type of resource tobe created. Valid values are `step` and `deployment-target`.
* `id` is the resource ID.
* `name` is the name of the step displayed by the Octopus web UI.
* `description` is the description of the step displayed by the Octopus UI.
* `categories` is an array containing one or more step categories display by the Octopus UI where the step will be listed.
* `canRunOnDeploymentTarget` can be set to `true` to run the step on a target accessible via a tentacle, or `false` to be run on a worker.
* `launcher` defines how the step is executed. A value of `node` means the step is executed by Node.js.
### `inputs.ts`
This file performs the same function as it does when defining a new target.
An example is shown below exposing a single string field:
```typescript
export default interface HelloWorldStepInputs {
name: string;
}
```
### `executor.ts`
The `executor.ts` file contains the logic to be executed when the step is run as part of a deployment process.
Unlike the function returned by the target `executor.ts` function, a step `executor.ts` function can receive inputs from both the step and the target. The combination of the inputs defined by these two resources allows a step executor to perform a common action on multiple targets.
For this example we print the greeting defined in the target and the name defined on the step to the output log:
```typescript
import HelloWorldStepInputs from "./inputs";
import {ExecutionInputs, Handler, OctopusContext, TargetInputs} from "@octopusdeploy/step-api";
import HelloWorldTargetInputs from "../../targets/hello-world-target/inputs";
const HelloWorldStepExecutor: Handler<HelloWorldStepInputs, HelloWorldTargetInputs> = async (
inputs: ExecutionInputs<HelloWorldStepInputs>,
target: TargetInputs<HelloWorldTargetInputs>,
context: OctopusContext
) => {
context.print(target.greetingPrefix + " " + inputs.name);
};
export default HelloWorldStepExecutor;
```
### `ui.ts`
The step form displayed by the Octopus web UI is defined much the same as it was with the target. There are some subtle differences though:
* It implements the `StepUI` type.
* The first parameter to the `createInitialInputs` function can be an instance of `InitialInputFactories`, which provides the ability to create blank package references.
* The second parameter to the `editInputsForm` function is an instance of `AvailableStepComponents`, which exposes a different widget set.
Here we define the initial value of the `name` input to be a blank string, and build the form with a single `text` input:
```typescript
import { StepUI } from "@octopusdeploy/step-api";
import HelloWorldStepInputs from "./inputs";
export const HelloWorldStepUI: StepUI<HelloWorldStepInputs> = {
createInitialInputs: () => {
return {
name: ""
};
},
editInputsForm: (inputs, { text }) => {
return [
text({
input: inputs.name,
label: "Greeting Name",
helpText: `The name of the person to greet.`,
}),
];
},
};
export default HelloWorldStepUI;
```
### `validation.ts`
Step form validation is identical to target form validation:
```typescript
import { ValidateInputs } from "@octopusdeploy/step-api";
import HelloWorldStepInputs from "./inputs";
const validateInputs: ValidateInputs<HelloWorldStepInputs> = (inputs, validate) => {
return [
validate(inputs.name, (name) => {
if (name === "") return "Name can not be empty";
}),
];
};
export default validateInputs;
```
## Building the step package
To build step packages, run the following commands:
1. `npm install`
2. `npm run build`
3. `npm run test`
The step package files are saved under the `dist/steps` folder. Add the contents of this folder to a ZIP file and copy it to the `steps` folder in Octopus.
If you are testing with a locally built copy of Octopus, place the ZIP file in `\source\Octopus.Server\bin\net5.0\steps`.
## GitHub workflows
This repository contains a [GitHub workflow](https://github.com/OctopusSamples/StepPackage-HelloWorld/blob/main/.github/workflows/main.yml) that builds and tests the code, packages the resulting files, and creates a release with the step package archive.
Use git tags to indicate releases, while commits to the `main` branch create `alpha` releases.
## Using the step package
With the step package copied to the `steps` directory, target can now be selected when creating a new deployment target:
The step is available when building a deployment project:
Here is the result of a deployment with the new step package:
| 43.044776 | 342 | 0.726838 | eng_Latn | 0.980607 |
6f82a13582b23a1123312d7133002ad45dc668c8 | 1,270 | md | Markdown | his/core/as400-definition-properties-general2.md | cmcclister/biztalk-docs | 36a3d4b944e27edff883b8e36e997c7d2af4f497 | [
"CC-BY-4.0",
"MIT"
] | 37 | 2017-08-28T06:57:52.000Z | 2021-07-13T12:16:23.000Z | his/core/as400-definition-properties-general2.md | cmcclister/biztalk-docs | 36a3d4b944e27edff883b8e36e997c7d2af4f497 | [
"CC-BY-4.0",
"MIT"
] | 732 | 2017-05-18T22:16:15.000Z | 2022-03-31T23:10:06.000Z | his/core/as400-definition-properties-general2.md | isabella232/biztalk-docs | 36a3d4b944e27edff883b8e36e997c7d2af4f497 | [
"CC-BY-4.0",
"MIT"
] | 158 | 2017-06-19T22:47:52.000Z | 2022-02-28T06:41:54.000Z | ---
description: "Learn more about: AS400 Definition Properties: General"
title: "AS400 Definition Properties: General2 | Microsoft Docs"
ms.custom: ""
ms.date: "11/30/2017"
ms.prod: "host-integration-server"
ms.reviewer: ""
ms.suite: ""
ms.tgt_pltfrm: ""
ms.topic: "article"
f1_keywords:
- "SNA_AS400"
ms.assetid: 12598563-cf28-4a73-b454-e0bca6ca5296
caps.latest.revision: 3
author: "gplarsen"
ms.author: "hisdocs"
manager: "anneta"
---
# AS400 Definition Properties: General
**AS/400 Remote LU Alias**
Click the drop-down list box arrow and select an **AS/400 Remote LU Alias**, which contains addressing information for the AS/400.
**Local LU Alias**
Click the drop-down list box arrow and select a **Local LU Alias**. The **Local LU Alias** maps to the LU the client computer will use.
**Mode**
You must select the **QPCSUPP mode**.
**AS/400 User Name**
Enter your **AS/400 User Name**, which is required information.
**AS/400 Password**
Enter your **AS/400 Password**, which is required information.
**Confirm Password**
Enter your password again to confirm.
**Comment**
Optionally, enter a comment of not more than 25 characters long.
## See Also
[SNA Manager Help](../core/sna-manager-help1.md)
| 29.534884 | 138 | 0.697638 | eng_Latn | 0.830537 |
6f82c5d8d449675b1dfa27423e6f0d3a0a34167d | 1,550 | md | Markdown | desktop-src/SecCrypto/settings-enablepromptforcertificateui.md | velden/win32 | 94b05f07dccf18d4b1dbca13b19fd365a0c7eedc | [
"CC-BY-4.0",
"MIT"
] | 552 | 2019-08-20T00:08:40.000Z | 2022-03-30T18:25:35.000Z | desktop-src/SecCrypto/settings-enablepromptforcertificateui.md | velden/win32 | 94b05f07dccf18d4b1dbca13b19fd365a0c7eedc | [
"CC-BY-4.0",
"MIT"
] | 1,143 | 2019-08-21T20:17:47.000Z | 2022-03-31T20:24:39.000Z | desktop-src/SecCrypto/settings-enablepromptforcertificateui.md | velden/win32 | 94b05f07dccf18d4b1dbca13b19fd365a0c7eedc | [
"CC-BY-4.0",
"MIT"
] | 1,287 | 2019-08-20T05:37:48.000Z | 2022-03-31T20:22:06.000Z | ---
description: Sets or retrieves a Boolean value that specifies whether user interface prompts for a signer or sender's identity can be used.
ms.assetid: b9765de4-0b94-4006-aaa8-9ad6858da1f4
title: Settings.EnablePromptForCertificateUI property
ms.topic: reference
ms.date: 05/31/2018
topic_type:
- APIRef
- kbSyntax
api_name:
- Settings.EnablePromptForCertificateUI
api_type:
- COM
api_location:
- Capicom.dll
---
# Settings.EnablePromptForCertificateUI property
\[The **EnablePromptForCertificateUI** property is available for use in the operating systems specified in the Requirements section.\]
The **EnablePromptForCertificateUI** property sets or retrieves a Boolean value that specifies whether user interface prompts for a signer or sender's identity can be used.
## Syntax
```VB
Settings.EnablePromptForCertificateUI As Boolean
```
## Property value
If **true**, user interface prompts for a signer or sender's identity can be used. The default value is **false**.
> [!Note]
> Setting this property does not disable warnings that are generated before any private key usage is done from a web-based application.
## Requirements
| Requirement | Value |
|----------------------------|----------------------------------------------------------------------------------------|
| Redistributable<br/> | CAPICOM 2.0 or later on Windows Server 2003 and Windows XP<br/> |
| DLL<br/> | <dl> <dt>Capicom.dll</dt> </dl> |
## See also
<dl> <dt>
[**Settings**](settings.md)
</dt> </dl>
| 23.134328 | 172 | 0.676129 | eng_Latn | 0.875185 |
6f82e1930d0d4581ceeaf7d60351777657b81105 | 14,443 | md | Markdown | docs/reference-architectures/n-tier/windows-vm.md | jdanielnd/architecture-center.pt-br | 3c2d370e8e783dc82e24cede37a5f5128dcd8803 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/reference-architectures/n-tier/windows-vm.md | jdanielnd/architecture-center.pt-br | 3c2d370e8e783dc82e24cede37a5f5128dcd8803 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/reference-architectures/n-tier/windows-vm.md | jdanielnd/architecture-center.pt-br | 3c2d370e8e783dc82e24cede37a5f5128dcd8803 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Executar uma VM do Windows no Azure
titleSuffix: Azure Reference Architectures
description: Melhores práticas para execução de uma máquina virtual com Windows no Azure.
author: telmosampaio
ms.date: 12/13/2018
ms.topic: reference-architecture
ms.service: architecture-center
ms.subservice: reference-architecture
ms.openlocfilehash: a25488357eb11b80e8f79ddae7f7d69735a6bec3
ms.sourcegitcommit: c053e6edb429299a0ad9b327888d596c48859d4a
ms.translationtype: HT
ms.contentlocale: pt-BR
ms.lasthandoff: 03/20/2019
ms.locfileid: "58242927"
---
# <a name="run-a-windows-virtual-machine-on-azure"></a>Executar uma máquina virtual com Windows no Azure
O provisionamento de uma VM (máquina virtual) no Azure requer alguns componentes adicionais além da própria VM, incluindo recursos de rede e armazenamento. Este artigo mostra as melhores práticas para executar uma VM do Windows no Azure.
## <a name="resource-group"></a>Grupo de recursos
Um [grupo de recursos][resource-manager-overview] é um contêiner lógico que armazena os recursos relacionados ao Azure. Em geral, recursos de grupo baseados em seu tempo de vida e que vão gerenciá-los.
Coloque recursos estreitamente associados que compartilhem o mesmo ciclo de vida no mesmo [grupo de recursos][resource-manager-overview]. Os grupos de recursos permitem implantar e monitorar recursos como um grupo e rastrear custos de cobrança por grupo de recursos. Também é possível excluir recursos como um conjunto, o que é muito útil para implantações de teste. Atribua nomes de recursos significativos para simplificar a localização de um recurso específico e o reconhecimento de sua função. Para obter mais informações, consulte as [Convenções de nomenclatura recomendadas para os Recursos do Azure][naming-conventions].
## <a name="virtual-machine"></a>Máquina virtual
Você pode provisionar uma VM a partir de uma lista de imagens publicadas, de um arquivo gerenciado personalizado ou um arquivo de VHD (disco rígido virtual) carregado no armazenamento Blobs do Azure.
O Azure oferece vários tamanhos de máquinas virtuais diferentes. Para obter mais informações, confira [Tamanhos das máquinas virtuais no Azure][virtual-machine-sizes]. Se você estiver movendo uma carga de trabalho existente para o Azure, deverá começar com o tamanho da VM que mais se aproxima de seus servidores locais. Em seguida, meça o desempenho da carga de trabalho real em termos de CPU, memória e IOPS (operações de entrada/saída de disco por segundo) e ajuste o tamanho conforme a necessidade.
Em geral, escolha a região do Azure que esteja mais próxima de seus usuários internos ou clientes. Nem todos os tamanhos de VM estão disponíveis em todas as regiões. Para obter mais informações, consulte [Serviços por região][services-by-region]. Para obter uma lista dos tamanhos de VM disponíveis em uma região específica, execute o seguinte comando a partir da interface de linha de comando do Azure (CLI):
```azurecli
az vm list-sizes --location <location>
```
Para obter informações sobre como escolher uma imagem de VM publicada, consulte [Localizar imagens de VM do Windows][select-vm-image].
## <a name="disks"></a>Discos
Para um melhor desempenho de E/S de disco, recomendamos o [Armazenamento Premium][premium-storage], que armazena dados em SSDs (unidades de estado sólido). O custo é baseado na capacidade do disco provisionado. O IOPS e a taxa de transferência também dependem do tamanho do disco. Portanto, ao provisionar um disco, considere todos os três fatores (capacidade, IOPS e taxa de transferência).
Também é recomendável usar [Managed Disks][managed-disks]. Os discos gerenciados simplificam o gerenciamento de disco manipulando o armazenamento por você. Os discos gerenciados não exigem uma conta de armazenamento. Você simplesmente especifica o tamanho e o tipo de disco e ele é implantado como um recurso altamente disponível
O disco de OS é um VHD armazenado no [Armazenamento do Microsoft Azure ][azure-storage], de modo que ele persiste mesmo quando o computador host está desligado. Também é recomendável criar um ou mais [discos de dados][data-disk], que são VHDs persistentes usados para dados de aplicativo. Quando possível, instale aplicativos em um disco de dados, não no disco do sistema operacional. Algumas aplicações legadas podem precisar instalar componentes na unidade C:. Nesse caso, você pode [redimensionar o disco de SO][resize-os-disk] utilizando o PowerShell.
A VM também é criada com um disco temporário (a unidade `D:` no Windows). Esse disco é armazenado em uma unidade física no computador host. Ele *não* é salvo no Armazenamento do Microsoft Azure e pode ser excluído durante a reinicialização e outros eventos de ciclo de vida da VM. Use esse disco somente para dados temporários, como arquivos de paginação ou de permuta.
## <a name="network"></a>Rede
Os componentes de rede incluem os seguintes recursos:
- **Rede virtual**. Cada VM é implantada em uma rede virtual que pode ser segmentada em várias sub-redes.
- **NIC (adaptador de rede)**. A NIC permite que a VM se comunique com a rede virtual. Se você precisar de vários NICs para sua VM, esteja ciente de que existe um número máximo de NICs definido para cada [tamanho de VM][vm-size-tables].
- **Endereço IP público**. Um endereço IP público é necessário para se comunicar com a VM — por exemplo, sobre RDP (área de trabalho remota). Esse endereço IP público pode ser dinâmico ou estático. O padrão é dinâmico.
- Reserve um [endereço IP estático][static-ip] se precisar de um endereço IP fixo que não mudará, —por exemplo, se precisar criar um registro 'A' de DNS ou adicionar o IP endereço para uma lista segura.
- Você também pode criar um FQDN (nome de domínio totalmente qualificado) para o endereço IP. Em seguida, é possível registrar um [registro CNAME][cname-record] no DNS que aponta para o FQDN. Para saber mais, consulte [Criar um nome de domínio totalmente qualificado no Portal do Azure][fqdn].
- **NSG (grupo de segurança de rede)**. Os [Grupos de segurança de rede][nsg] são utilizados para permitir ou recusar o tráfego de rede a VMs. Os NSGs podem ser associados com sub-redes ou com instâncias VM individuais.
Todos os NSGs contêm um conjunto de [regras padrão][nsg-default-rules], incluindo uma regra que bloqueia todo o tráfego de Internet de entrada. As regras padrão não podem ser excluídas, mas outras regras podem substituí-las. Para habilitar o tráfego de Internet, crie regras que permitam o tráfego de entrada em portas específicas — por exemplo, a porta 80 para HTTP. Para habilitar o RDP, adicione uma regra NSG que permita o tráfego de entrada na porta TCP 3389.
## <a name="operations"></a>Operações
**Diagnóstico**. Habilite o monitoramento e diagnóstico, incluindo métricas de integridade básicas, logs de infraestrutura de diagnóstico e [diagnóstico de inicialização][boot-diagnostics]. O diagnóstico de inicialização poderá ajudar a diagnosticar uma falha de inicialização se sua VM entrar em um estado não inicializável. Crie uma conta do Armazenamento do Azure para armazenar os logs. Uma conta LRS (armazenamento com redundância local) padrão é suficiente para os logs de diagnóstico. Para saber mais, confira [Habilitar monitoramento e diagnóstico][enable-monitoring].
**Disponibilidade**. Sua VM pode ser afetada por [manutenção planejada][planned-maintenance] ou por [tempo de inatividade não planejado][manage-vm-availability]. Você pode usar os[ logs de reinicialização da VM][reboot-logs] para determinar se uma reinicialização da VM foi causada por manutenção planejada. Para obter maior disponibilidade, implante várias VMs em um [conjunto de disponibilidade](/azure/virtual-machines/windows/manage-availability#configure-multiple-virtual-machines-in-an-availability-set-for-redundancy). Essa configuração fornece um maior [SLA (contrato de nível de serviço)][vm-sla].
**Backups** Para se proteger contra perda acidental de dados, use o serviço [Backup do Azure](/azure/backup/) a fim de fazer o backup das VMs em um armazenamento com redundância geográfica. O Backup do Azure fornece backups consistentes com o aplicativo.
**Interromper uma VM**. O Azure faz uma distinção entre os estados "parado" e "desalocado". Você será cobrado quando o status da VM for interrompido, mas não quando a VM for desalocada. No Portal do Azure, o botão **Parar** desaloca a VM. No entanto, se você desligar por meio do sistema operacional enquanto estiver conectado, a VM será interrompida, mas **não** desalocada e, portanto, você ainda será cobrado.
**Excluir uma VM**. Se você excluir uma VM, os VHDs não serão excluídos. Isso significa que você poderá excluir com segurança a VM sem perda de dados. No entanto, você ainda será cobrado pelo armazenamento. Para excluir o VHD, exclua o arquivo do [Armazenamento de blobs][blob-storage]. Para evitar a exclusão acidental, use um [bloqueio de recurso][resource-lock] para bloquear o grupo de recursos inteiro ou bloquear recursos individuais, como uma VM.
## <a name="security-considerations"></a>Considerações de segurança
Use a [Central de Segurança do Azure][security-center] para obter uma exibição central do estado da segurança de seus recursos do Azure. A Central de Segurança monitora problemas de segurança potenciais e fornece uma visão abrangente da integridade de segurança de sua implantação. A Central de Segurança é configurada por assinatura do Azure. Habilite a coleta de dados de segurança conforme descrito em [Integrar a assinatura do Azure à Central de Segurança Standard][security-center-get-started]. Depois que a coleta de dados for habilitada, a Central de Segurança examinará automaticamente todas as VMs criadas nessa assinatura.
**Gerenciamento de patch**. Se for habilitada, a Central de Segurança verificará se quaisquer atualizações críticas e de segurança estão ausentes. Use as [Configurações da Política de Grupo][group-policy] na VM para habilitar as atualizações automáticas do sistema.
**Antimalware**. Se for habilitada, a Central de Segurança verificará se o software antimalware está instalado. Você também pode usar a Central de Segurança para instalar o software antimalware por meio do Portal do Azure.
**Controle de acesso**. Use o [RBAC (controle de acesso baseado em função)][rbac] para controlar o acesso aos recursos do Azure. O RBAC permite atribuir funções de autorização aos membros de sua equipe de DevOps. Por exemplo, a função Leitor pode exibir os recursos do Azure, mas não criar, gerenciar nem excluí-los. Algumas permissões são específicas para determinado tipo de recurso do Azure. Por exemplo, a função Colaborador da Máquina Virtual pode reiniciar ou desalocar uma VM, redefinir a senha de administrador, criar uma nova VM e, assim por diante. Outras [funções RBAC internas][rbac-roles] que podem ser úteis para esta arquitetura incluem [Usuário de DevTest Labs][rbac-devtest] e [Colaborador de Rede][rbac-network].
> [!NOTE]
> O RBAC não limita as ações que podem ser executadas por um usuário conectado a uma VM. Essas permissões são determinadas pelo tipo de conta no SO convidado.
**Logs de auditoria**. Use os [logs de auditoria][audit-logs] para ver as ações de provisionamento e outros eventos da VM.
**Criptografia de dados**. Use o [Azure Disk Encryption][disk-encryption] se você precisa criptografar os discos do sistema operacional e de dados.
## <a name="next-steps"></a>Próximas etapas
- Para provisionar uma VM do Windows, confira [Criar e gerenciar VMs do Windows com o Azure PowerShell](/azure/virtual-machines/windows/tutorial-manage-vm)
- Para uma arquitetura de N camadas completa em VMs do Windows, confira [Aplicativo de N camadas do Windows no Azure com o SQL Server](./n-tier-sql-server.md).
<!-- links -->
[audit-logs]: https://azure.microsoft.com/blog/analyze-azure-audit-logs-in-powerbi-more/
[azure-storage]: /azure/storage/storage-introduction
[blob-storage]: /azure/storage/storage-introduction
[boot-diagnostics]: https://azure.microsoft.com/blog/boot-diagnostics-for-virtual-machines-v2/
[cname-record]: https://en.wikipedia.org/wiki/CNAME_record
[data-disk]: /azure/virtual-machines/virtual-machines-windows-about-disks-vhds
[disk-encryption]: /azure/security/azure-security-disk-encryption
[enable-monitoring]: /azure/monitoring-and-diagnostics/insights-how-to-use-diagnostics
[fqdn]: /azure/virtual-machines/virtual-machines-windows-portal-create-fqdn
[group-policy]: /windows-server/administration/windows-server-update-services/deploy/4-configure-group-policy-settings-for-automatic-updates
[manage-vm-availability]: /azure/virtual-machines/virtual-machines-windows-manage-availability
[managed-disks]: /azure/storage/storage-managed-disks-overview
[naming-conventions]: ../../best-practices/naming-conventions.md
[nsg]: /azure/virtual-network/virtual-networks-nsg
[nsg-default-rules]: /azure/virtual-network/virtual-networks-nsg#default-rules
[planned-maintenance]: /azure/virtual-machines/virtual-machines-windows-planned-maintenance
[premium-storage]: /azure/virtual-machines/windows/premium-storage
[rbac]: /azure/active-directory/role-based-access-control-what-is
[rbac-roles]: /azure/active-directory/role-based-access-built-in-roles
[rbac-devtest]: /azure/active-directory/role-based-access-built-in-roles#devtest-labs-user
[rbac-network]: /azure/active-directory/role-based-access-built-in-roles#network-contributor
[reboot-logs]: https://azure.microsoft.com/blog/viewing-vm-reboot-logs/
[resize-os-disk]: /azure/virtual-machines/virtual-machines-windows-expand-os-disk
[resource-lock]: /azure/resource-group-lock-resources
[resource-manager-overview]: /azure/azure-resource-manager/resource-group-overview
[security-center]: /azure/security-center/security-center-intro
[security-center-get-started]: /azure/security-center/security-center-get-started
[select-vm-image]: /azure/virtual-machines/virtual-machines-windows-cli-ps-findimage
[services-by-region]: https://azure.microsoft.com/regions/#services
[static-ip]: /azure/virtual-network/virtual-networks-reserved-public-ip
[virtual-machine-sizes]: /azure/virtual-machines/virtual-machines-windows-sizes
[visio-download]: https://archcenter.blob.core.windows.net/cdn/vm-reference-architectures.vsdx
[vm-size-tables]: /azure/virtual-machines/virtual-machines-windows-sizes
[vm-sla]: https://azure.microsoft.com/support/legal/sla/virtual-machines
| 103.906475 | 731 | 0.79748 | por_Latn | 0.998819 |
6f833f989f699d1a43545990ac0731e4afab0f0d | 11,601 | markdown | Markdown | posts/2017-11-07-amy.nguyen.markdown | rcarmo/usesthis | be07dabddf3058d7b83c897f261807c8ca4a29ca | [
"MIT"
] | null | null | null | posts/2017-11-07-amy.nguyen.markdown | rcarmo/usesthis | be07dabddf3058d7b83c897f261807c8ca4a29ca | [
"MIT"
] | null | null | null | posts/2017-11-07-amy.nguyen.markdown | rcarmo/usesthis | be07dabddf3058d7b83c897f261807c8ca4a29ca | [
"MIT"
] | null | null | null | ---
title: Amy Nguyen
summary: Infrastructure engineer (Stripe)
categories:
- developer
- linux
- mac
- web
- windows
---
### Who are you, and what do you do?
My name is [Amy Nguyen](https://twitter.com/amyngyn "Amy's Twitter account.") and I'm an infrastructure software engineer. Right now, I work on the [Stripe][] observability team, which is the team that helps others "see" what's going on with their systems. I used to do the same type of work at [Pinterest][], and before that, I was studying computer science ([systems](http://csmajor.stanford.edu/Tracks.shtml "The available tracks for a computer science degree at Stanford.")) and philosophy (ethics) in college. You could say I have a need to get to the root of everything, both in life and with servers. Outside of work, I love [reading about self-improvement](https://www.pinterest.com/amyngyn/life-curriculum/ "Amy's self-improvement pins on Pinterest."), cooking, and [writing](http://blog.amynguyen.net/?page_id=318 "Amy's weblog posts.").
### What hardware do you use?
For work, I just use what my company gives me. I have a [2017 15" MacBook Pro Retina][macbook-pro] with a Touch Bar (ugh), second monitor, an [Anker ergonomic mouse][2.4g-wireless-vertical-ergonomic-mouse], and an [Apple Magic Keyboard][magic-keyboard]. I used to have wrist pain when using the Apple trackpad (though I love the gestures), so I'm making a bigger effort to learn about ergonomics. I also have the [Bose QuietComfort 35 noise cancelling headphones][quietcomfort-35], which have been a game changer. I used to use the wired version, but I found myself getting tangled up in my bag straps all the time. Now I can comfortably sit on the train with no tangling! I love them so much that I might buy a second pair so I can keep one at work and one for home/commuting.
For personal stuff, I have a [ThinkPad T430][thinkpad-t430] from 2012. I didn't use it much once I started working at Pinterest, but now that I'm at a new job, I'm trying to train myself to make a bigger distinction between work tools and personal tools. So I'm back to the ancient ThinkPad when I'm at home. Some other electronics I consider important are my [iPhone 6S Plus][iphone-6s-plus] (obviously rose gold) and [Kindle Paperwhite][kindle-paperwhite]. I commute to work and like to alternate between reading and blowing through my phone's monthly data limit.
For non-electronic things I love, I always keep a notebook and pen at work. Right now, I'm using the Leuchtturm A5 dotted journal in navy blue and [Muji 0.38mm black gel pen][gel-ink-0.38mm]. I also loved the Cottonwood Arts dot matrix notebook and went through two of them. I switched to Leuchtturm for the cute colors and larger page size. My criteria for notebooks so far has been hardcover, dot grid, sturdy paper, and inner flap. I cry really easily (like, if I tell you the plot of a sad movie, I will start crying), so I use the inner flap to carry tissues around.
I know you probably weren't asking about this, but I feel like I would be doing a disservice to your audience if I didn't also mention that I have a [phone mount][easy-one-touch-car-and-desk-mount] on my bathroom mirror so I can watch videos while I brush my teeth. It's very important to me.
### And what software?
I started using [vim][] in college because I thought it would make people respect me. Now I use it because I have Stockholm syndrome and a sick [.vimrc](https://github.com/amyngyn/dotfiles/blob/master/.vimrc "Amy's .vimrc config file.") I can't abandon. Every few months, I think that I should try a modern editor like [Sublime][sublime-text]/[Atom][]/[IntelliJ][intellij-idea]/[PyCharm][] etc., but I'm too entrenched to figure out all of my workflows in another IDE. Other than that, I use [iTerm2][] and [tmux][] - I try to keep it no frills when it comes to development. I don't even remap my escape key to capslock. I love [scm-breeze][] for making [git][] easier - it adds some really great shortcuts and highlighting. The other application I want to give a shoutout to is [Spectacle][] for [Mac OS X][macos] window management. I'm a big fan of keyboard shortcuts and Spectacle is great for that.
On my ThinkPad, I'm still running [Windows 7][windows-7] and [Ubuntu][] 12.10 (that's how old it is!). I'm not a big fan of either, but I needed both in college to get homework assignments done.
As for "serious" [iOS][] apps, I use [Chrome][chrome-ios], [Google Calendar][google-calendar-ios] (if it's not on my calendar, it's not happening), [Gmail][gmail-ios] (I hated Inbox), [Slack][slack-ios] (I wish it was faster), [LastPass][lastpass-ios], and [Duo Mobile][duo-mobile-ios]. I use [Aviary][aviary-ios] for blurring out identifying info before posting photos online, which I think more people should be mindful of!
For everything else on my phone, I'm usually on [Twitter][twitter-ios], [Reddit][reddit-ios], the [Kindle iOS app][kindle-ios], [Spotify][spotify-ios] (Premium, because I'm not a savage), [Pinterest][pinterest-ios], [Pocket][pocket-ios], [Hearthstone][hearthstone-ios], [Twitch][twitch-ios], and [YouTube][youtube-ios]. I use the Kindle iOS app whenever I have an expired library book on my Kindle. I put the Kindle in airplane mode so that the expired book doesn't disappear, and then I read another book on my phone. It's not a very sustainable system, but it's what I do.
One miscellaneous thing I want to share in case it helps other people: I just found out a week ago that there's an iOS/Android app for the Bose QuietComfort 35 headphones called [Bose Connect][bose-connect-ios]! It allows you to toggle noise canceling (which was not possible before) and customize some other settings. I'm really happy about this, because I hate being snuck up upon when I have headphones on.
### What would be your dream setup?
*takes deep breath* I want an Amy-sized desk where my back is against a wall and there are potted plants everywhere, natural sunlight that doesn't directly shine in my face, a nearby water cooler, a bathroom on the same floor, and at least three cats at all times. Also Bluetooth headphones that understand how to never embarrass me at work and never run out of battery.
To explain: I'm too short for my desk/chair setup at my new job. When I put my desk at the lowest setting, it's still too tall for my arms to be parallel to the floor. If I raise my chair to the height where my arms would be parallel, my feet dangle. I really wish I had a desk that was just a few inches shorter - it would make a huge difference for all of my ergonomic pain. I'm looking into getting a footstool, but still figuring it out.
I keep accidentally playing loud music from my laptop because I forget to pause my music before turning off my headphones or some sort of Bluetooth weirdness happens to unpair my devices. Now my coworkers know how much I like Taylor Swift and anime music.
Some other miscellany: I wish I had an ergonomic mouse that wasn't so tall. I knock it over all the times when moving around my desk. I tend to switch between writing in my notebook, grabbing my cup of water, typing, and talking with my hands, so I knock my mouse over a few times every day. I'm sure I'm annoying my coworkers a lot. (It's either that, or the headphones, but I'm sure they hate me by now.) I'm also still on the hunt for my perfect notebook. I realized over the past few weeks that I want a notebook that can fold back on itself because I want to have more desk real estate. I don't like spiral notebooks because the pages fall out more easily, but that seems to be the only option. I'm open to suggestions!
[2.4g-wireless-vertical-ergonomic-mouse]: https://www.anker.com/products/variant/2.4G-Wireless-Vertical-Ergonomic-Mouse/98ANWVM-UBA "A vertical ergonomic mouse."
[easy-one-touch-car-and-desk-mount]: https://www.iottie.com/Product/Series/OneTouch/Car-Mount "A car and desk phone mount."
[gel-ink-0.38mm]: http://www.muji.us/store/gel-ink-ballpoint-pen-0-38mm-black4548718727674.html "A ball-point pen."
[iphone-6s-plus]: https://en.wikipedia.org/wiki/IPhone_6s_Plus "A large smartphone."
[kindle-paperwhite]: https://www.amazon.com/Kindle-Paperwhite-Touch-light/dp/B007OZNZG0 "An e-book reader with a book-like screen."
[macbook-pro]: https://www.apple.com/macbook-pro/ "A laptop."
[magic-keyboard]: https://en.wikipedia.org/wiki/Magic_Keyboard "A wireless keyboard."
[quietcomfort-35]: https://www.bose.com/en_us/products/headphones/over_ear_headphones/quietcomfort-35-wireless.html "Wireless over-the-ear headphones."
[thinkpad-t430]: http://shop.lenovo.com/us/en/laptops/thinkpad/t-series/t430/ "A 14 inch PC laptop."
[atom]: https://atom.io/ "A text editor based on web technology."
[aviary-ios]: https://itunes.apple.com/us/app/photo-editor-by-aviary/id527445936 "A photo editor app."
[bose-connect-ios]: https://itunes.apple.com/us/app/bose-connect/id1046510029 "An app for customising Bose Bluetooth devices."
[chrome-ios]: https://itunes.apple.com/us/app/chrome/id535886823 "A web broser app."
[duo-mobile-ios]: https://itunes.apple.com/us/app/duo-mobile/id422663827 "An app for the authentication service."
[git]: https://git-scm.com/ "A version control system."
[gmail-ios]: https://itunes.apple.com/us/app/gmail-email-from-google/id422689480 "A client for the email service."
[google-calendar-ios]: https://itunes.apple.com/us/app/google-calendar/id909319292 "An app for the calendar service."
[hearthstone-ios]: https://itunes.apple.com/us/app/hearthstone/id625257520 "A card battle game."
[intellij-idea]: http://www.jetbrains.com/idea/ "A developer's IDE."
[ios]: https://www.apple.com/ios/ios-10/ "A mobile operating system."
[iterm2]: https://iterm2.com/ "An alternative terminal application for Mac OS X."
[kindle-ios]: https://itunes.apple.com/gb/app/kindle/id302584613 "An iPhone app for accessing Kindle content from Amazon."
[lastpass-ios]: https://itunes.apple.com/us/app/lastpass-password-manager/id324613447 "A password manager app."
[macos]: https://en.wikipedia.org/wiki/MacOS "An operating system for Mac hardware."
[pinterest-ios]: https://itunes.apple.com/us/app/pinterest/id429047995 "A client app for the pin service."
[pinterest]: https://www.pinterest.com/ "An online 'pinboard' service."
[pocket-ios]: https://getpocket.com/ios/ "An app for the read-it-later service."
[pycharm]: https://www.jetbrains.com/pycharm/ "A Python-focused IDE."
[reddit-ios]: https://itunes.apple.com/us/app/reddit-the-official-app/id1064216828 "An app for the forum service."
[scm-breeze]: https://github.com/scmbreeze/scm_breeze "Shell scripts for enhancing git."
[slack-ios]: https://itunes.apple.com/us/app/slack-team-communication/id618783545 "A client app for the chat service."
[spectacle]: https://www.spectacleapp.com/ "A Mac tool for moving and resizing windows."
[spotify-ios]: https://itunes.apple.com/us/app/spotify/id324684580 "An iOS client for the music service."
[stripe]: https://stripe.com/ "A payment service."
[sublime-text]: http://www.sublimetext.com/ "A coder's text editor."
[tmux]: https://sourceforge.net/projects/tmux/ "A terminal multiplexer, similar to screen."
[twitch-ios]: https://itunes.apple.com/us/app/twitch/id460177396 "An app for the streaming service."
[twitter-ios]: https://itunes.apple.com/app/twitter/id333903271 "A Twitter client."
[ubuntu]: https://www.ubuntu.com/ "A Unix distribution."
[vim]: https://www.vim.org/ "A command-line text editor."
[windows-7]: https://en.wikipedia.org/wiki/Windows_7 "An operating system."
[youtube-ios]: https://itunes.apple.com/us/app/youtube/id544007664 "A YouTube client for iOS."
| 128.9 | 902 | 0.759848 | eng_Latn | 0.965137 |
6f8393c8f43139d7ede9b0e3b77807e74e71368b | 6,119 | md | Markdown | packages/hiccup-carbon-icons/README.md | Shakthi/umbrella | 6e1471f88e21f1b0a59997981a7802899368c249 | [
"Apache-2.0"
] | null | null | null | packages/hiccup-carbon-icons/README.md | Shakthi/umbrella | 6e1471f88e21f1b0a59997981a7802899368c249 | [
"Apache-2.0"
] | null | null | null | packages/hiccup-carbon-icons/README.md | Shakthi/umbrella | 6e1471f88e21f1b0a59997981a7802899368c249 | [
"Apache-2.0"
] | null | null | null | <!-- This file is generated - DO NOT EDIT! -->
# 
[](https://www.npmjs.com/package/@thi.ng/hiccup-carbon-icons)
[](https://twitter.com/thing_umbrella)
This project is part of the
[@thi.ng/umbrella](https://github.com/thi-ng/umbrella/) monorepo.
- [About](#about)
- [Contact sheet](#contact-sheet)
- [Status](#status)
- [Installation](#installation)
- [Dependencies](#dependencies)
- [Usage examples](#usage-examples)
- [API](#api)
- [Icon conversion process](#icon-conversion-process)
- [Authors](#authors)
- [License](#license)
## About
This package provides the full set of IBM's [Carbon
icons](https://github.com/IBM/carbon-icons) in hiccup format (i.e. as Javascript
encoded SVG), counting in at ~1100 and ready to be used within any
[@thi.ng/hiccup](https://github.com/thi-ng/umbrella/tree/develop/packages/hiccup)
supporting scenario.
Each icon is defined in its own source file and can be imported individually.
The converted icons are based on the 32x32 pixel versions, but have NO explicit
size set (only `viewBox` attrib). Use the `withSize()` helper to inject a size,
e.g. `withSize(DOWNLOAD, "12px")`.
## Contact sheet
All icons can be previewed here: [contact
sheet](https://demo.thi.ng/umbrella/hiccup-carbon-icons/). ([Source
code](https://github.com/thi-ng/umbrella/tree/develop/packages/hiccup-carbon-icons/test/contact-sheet.ts))
### Status
**STABLE** - used in production
[Search or submit any issues for this package](https://github.com/thi-ng/umbrella/issues?q=%5Bhiccup-carbon-icons%5D+in%3Atitle)
## Installation
```bash
yarn add @thi.ng/hiccup-carbon-icons
```
```html
// ES module
<script type="module" src="https://unpkg.com/@thi.ng/hiccup-carbon-icons?module" crossorigin></script>
// UMD
<script src="https://unpkg.com/@thi.ng/hiccup-carbon-icons/lib/index.umd.js" crossorigin></script>
```
Package sizes (gzipped, pre-treeshake): ESM: 99.12 KB / CJS: 102.27 KB / UMD: 96.97 KB
## Dependencies
None
## Usage examples
Several demos in this repo's
[/examples](https://github.com/thi-ng/umbrella/tree/develop/examples)
directory are using this package.
A selection:
| Screenshot | Description | Live demo | Source |
| ----------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------------------ | ----------------------------------------------------------------------------------- |
| <img src="https://raw.githubusercontent.com/thi-ng/umbrella/develop/assets/imgui/imgui-all.png" width="240"/> | Canvas based Immediate Mode GUI components | [Demo](https://demo.thi.ng/umbrella/imgui/) | [Source](https://github.com/thi-ng/umbrella/tree/develop/examples/imgui) |
| <img src="https://raw.githubusercontent.com/thi-ng/umbrella/develop/assets/examples/parse-playground.png" width="240"/> | Parser grammar livecoding editor/playground & codegen | [Demo](https://demo.thi.ng/umbrella/parse-playground/) | [Source](https://github.com/thi-ng/umbrella/tree/develop/examples/parse-playground) |
| <img src="https://raw.githubusercontent.com/thi-ng/umbrella/develop/assets/examples/rdom-dnd.png" width="240"/> | rdom drag & drop example | [Demo](https://demo.thi.ng/umbrella/rdom-dnd/) | [Source](https://github.com/thi-ng/umbrella/tree/develop/examples/rdom-dnd) |
## API
[Generated API docs](https://docs.thi.ng/umbrella/hiccup-carbon-icons/)
```ts
import { renderOnce } from "@thi.ng/hdom";
import { CODE } from "@thi.ng/hiccup-carbon-icons";
// using tachyons css classes for brevity
const iconButton = (icon, onclick, label?) =>
["a", { onclick, href: "#" },
["span.dib.w1.h1.mr1", icon],
label];
renderOnce(iconButton(CODE, () => alert("hi"), "show me the code"));
```
## Icon conversion process
(For contributors only...)
The icon conversion is largely automated via the supplied bash script (currently
with some additional minor manual cleanup needed) and requires `svgo` and a
checkout of both the original carbon and the umbrella mono repos.
```bash
# install pre-requisites
yarn global add svgo
git clone https://github.com/thi-ng/umbrella.git
# build entire umbrella repo
cd umbrella
yarn build
# build xml to hiccup converter CLI tool
cd examples/xml-converter
yarn build-cli
# switch to package root
cd ../../hiccup-carbon-icons
# clone carbon repo into local temp dir
git clone https://github.com/carbon-design-system/carbon.git tmp
# convert original SVG icons and write results to package src folder
yarn build:convert src tmp/packages/icons/src/svg/32
# update contact sheet (will be written to package root)
yarn build:sheet
# open in browser
open contact-sheet.html
# fixup any conversion issues (rinse & repeat...)
# e.g. in the latest version (2020/08), several icons use paths w/ opacity=0 which need to be removed
# rebuild package
yarn build
```
## Authors
Karsten Schmidt
If this project contributes to an academic publication, please cite it as:
```bibtex
@misc{thing-hiccup-carbon-icons,
title = "@thi.ng/hiccup-carbon-icons",
author = "Karsten Schmidt",
note = "https://thi.ng/hiccup-carbon-icons",
year = 2018
}
```
## License
The copyright of the original icons is with IBM. The icons were published under
the same license as this package.
© 2018 - 2021 Karsten Schmidt // Apache Software License 2.0
| 37.310976 | 322 | 0.650106 | eng_Latn | 0.601081 |
6f841c1a70726af6f4d31140d7a7d24a4db2fb37 | 805 | md | Markdown | docs/visual-basic/misc/bc30074.md | yowko/docs.zh-tw | df9937e9a8e270b3435461133c7c70c717bea354 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/visual-basic/misc/bc30074.md | yowko/docs.zh-tw | df9937e9a8e270b3435461133c7c70c717bea354 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/visual-basic/misc/bc30074.md | yowko/docs.zh-tw | df9937e9a8e270b3435461133c7c70c717bea354 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 常數不可以當做指派的目標
ms.date: 07/20/2015
f1_keywords:
- bc30074
- vbc30074
helpviewer_keywords:
- BC30074
ms.assetid: e805a517-228a-4147-a2c0-9dba93d3ba42
ms.openlocfilehash: 78fa5824481f8b6331c89f60c1993d8eb1f182a3
ms.sourcegitcommit: bf5c5850654187705bc94cc40ebfb62fe346ab02
ms.translationtype: MT
ms.contentlocale: zh-TW
ms.lasthandoff: 09/23/2020
ms.locfileid: "91077978"
---
# <a name="constant-cannot-be-the-target-of-an-assignment"></a>常數不可以當做指派的目標
常數發生在指派其值的內容中。 在執行期間，只會指派可寫入變數、屬性和陣列項目的值。
**錯誤 ID︰** BC30074
## <a name="to-correct-this-error"></a>更正這個錯誤
- 請將常數取代為單一可寫入的變數、屬性或陣列項目。
## <a name="see-also"></a>另請參閱
- [常數和列舉](../programming-guide/language-features/constants-enums/index.md)
- [指派運算子 (Visual Basic) ](../language-reference/operators/assignment-operators.md)
| 25.967742 | 82 | 0.757764 | yue_Hant | 0.222157 |
6f845cf2dc0e5829a1644c8afea9dc9aceb988be | 600 | md | Markdown | _subjects/2/c4da1e63-a70b-11e6-962d-3c07545eb2e5.md | Almanak/dak | 5d4cb15c2456f3f33dc4d0a5a943d294f5edb938 | [
"MIT"
] | null | null | null | _subjects/2/c4da1e63-a70b-11e6-962d-3c07545eb2e5.md | Almanak/dak | 5d4cb15c2456f3f33dc4d0a5a943d294f5edb938 | [
"MIT"
] | null | null | null | _subjects/2/c4da1e63-a70b-11e6-962d-3c07545eb2e5.md | Almanak/dak | 5d4cb15c2456f3f33dc4d0a5a943d294f5edb938 | [
"MIT"
] | null | null | null | ---
# Jekyll variables
layout: subject
permalink: /subjects/c4da1e63-a70b-11e6-962d-3c07545eb2e5
# Specific subject values
uuid: c4da1e63-a70b-11e6-962d-3c07545eb2e5
broader:
- prefLabel: Sociale forhold og velfærd
uuid: c4d97447-a70b-11e6-81a5-3c07545eb2e5
- prefLabel: Social struktur
uuid: c4da15c2-a70b-11e6-b4db-3c07545eb2e5
conceptType: term
created: '2016-11-10T07:56:37.239470'
mappings:
- conceptIdentifier: '1951'
conceptURL: http://eurovoc.europa.eu/1951
match: closeMatch
thesaurus: EuroVoc
prefLabel: Social mobilitet
status: proposed
updated: '2016-11-18T12:02:33.257307'
--- | 26.086957 | 57 | 0.783333 | eng_Latn | 0.075811 |
6f8478d8553fb9f813ffe7814d588c3df8871a1d | 120 | md | Markdown | README.md | Game-Gremlin/keyboard-tester | 742db352403dc5c3c67a1054b16f3b8b3613377b | [
"MIT"
] | 2 | 2020-05-28T12:16:59.000Z | 2022-02-27T15:58:16.000Z | README.md | Game-Gremlin/keyboard-tester | 742db352403dc5c3c67a1054b16f3b8b3613377b | [
"MIT"
] | null | null | null | README.md | Game-Gremlin/keyboard-tester | 742db352403dc5c3c67a1054b16f3b8b3613377b | [
"MIT"
] | 1 | 2022-02-02T21:34:17.000Z | 2022-02-02T21:34:17.000Z | # Keyboard Tester
A keyboard tester in browser.
[tester.html](https://tarocch1.github.io/keyboard-tester/tester.html)
| 20 | 69 | 0.775 | hun_Latn | 0.206023 |
6f84a641befc7580f4293ee2f76d823854ccf344 | 786 | md | Markdown | src/components/switch-group/readme.md | grandemayta/stencil-elements | 08e9ca62bd08f146ebc9d9b89eee1a9f0f5429c7 | [
"MIT"
] | 4 | 2020-05-17T12:24:32.000Z | 2020-07-30T10:27:44.000Z | src/components/switch-group/readme.md | grandemayta/stencil-elements | 08e9ca62bd08f146ebc9d9b89eee1a9f0f5429c7 | [
"MIT"
] | 37 | 2020-05-17T15:13:06.000Z | 2020-07-16T18:46:13.000Z | src/components/switch-group/readme.md | guardiani-del-web/web-elements | 08e9ca62bd08f146ebc9d9b89eee1a9f0f5429c7 | [
"MIT"
] | null | null | null | # we-switch-group
<!-- Auto Generated Below -->
## Properties
| Property | Attribute | Description | Type | Default |
| -------------------- | --------- | ------------------------------------ | -------- | ----------- |
| `value` _(required)_ | `value` | Name that identify this switch group | `string` | `undefined` |
## Events
| Event | Description | Type |
| --------------------- | ------------------------------------------------------ | ------------------------------- |
| `switchGroupCallback` | Function called when a switch inside change it's state | `CustomEvent<SwitchGroupValue>` |
----------------------------------------------
| 31.44 | 116 | 0.334606 | eng_Latn | 0.469641 |
6f853ec492899a5855436084d237c2a41350d3e6 | 1,744 | md | Markdown | README.md | JelteMX/time-series | 01ae4c8f87572f08c1ec37e15d9ab71f5afb0360 | [
"Apache-2.0"
] | null | null | null | README.md | JelteMX/time-series | 01ae4c8f87572f08c1ec37e15d9ab71f5afb0360 | [
"Apache-2.0"
] | null | null | null | README.md | JelteMX/time-series | 01ae4c8f87572f08c1ec37e15d9ab71f5afb0360 | [
"Apache-2.0"
] | null | null | null | # TimeSeries
Plot and track your data across different time periods on an nv.d3 powered chart.
## Features and limitations
* Date formatting on x-axis
* Formatting of numbers on y-axis
* Interactive guidelines
* Different line color
* Filling of serie area
## Dependencies
* Mendix 6
## Properties
* X-axis
* X-axis label; Label for the x-axis
* X-axis data format; Formats of date on x-axis (use NVD3 date formatting)
* Enable stagger-labels; Display values on x-axis so they all fit
* Y-axis
* Y-axis label; Label for the y-axis
* Y-axis data format; Format of data on y-axis
* Series config
* Data series
- Data source
- Data entity; The entity containing serie points
- Source; Type of source
- X-Axis data; Attribute containing dates for x-axis
- Y-Axis data; Attribute containing data for y-axis
- Serie key; Used in the legend to interact with the chart
- Source - XPath
- Constraint; Constraint on the data from data-entity
- Source - microflow
- Data source microflow; Returns a serie's coordinates
- Appearance
- Serie color; Color of the serie line in the chart
- Fill serie area; Should serie area be filled
* Appearance
* Chart width; Width of the chart
* Width units; Measurement for width pixels or auto
* Chart height; Height of the chart
* Height units; Measurement for Height pixels or auto
## Source
Source and [sample project](https://github.com/mendixlabs/time-series/tree/master/test) at GitHub
Please contribute fixes and extensions at
https://github.com/mendixlabs/time-series/
## Known bugs
Please report any issues via the github issue tracker:
https://github.com/mendixlabs/time-series/issues | 30.596491 | 97 | 0.712156 | eng_Latn | 0.937241 |
6f8580844a0264c9931982647adf2ef6a76f619b | 2,106 | md | Markdown | docs/framework/wpf/advanced/how-to-use-application-resources.md | hyoshioka0128/docs.ja-jp | 979df25b1da8e21036438e0c8bc5f4d61bd1181d | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-01-29T12:31:08.000Z | 2019-01-29T12:31:08.000Z | docs/framework/wpf/advanced/how-to-use-application-resources.md | hyoshioka0128/docs.ja-jp | 979df25b1da8e21036438e0c8bc5f4d61bd1181d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wpf/advanced/how-to-use-application-resources.md | hyoshioka0128/docs.ja-jp | 979df25b1da8e21036438e0c8bc5f4d61bd1181d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: '方法: アプリケーション リソースを使用する'
ms.date: 03/30/2017
helpviewer_keywords:
- application resources [WPF]
- resources [WPF], application resources
ms.assetid: 507ea937-5191-406b-8797-0a3d9f94156d
ms.openlocfilehash: 4305c49c4322d164e2481c1508dda7c038c14694
ms.sourcegitcommit: 3d5d33f384eeba41b2dff79d096f47ccc8d8f03d
ms.translationtype: MT
ms.contentlocale: ja-JP
ms.lasthandoff: 05/04/2018
ms.locfileid: "33544158"
---
# <a name="how-to-use-application-resources"></a>方法: アプリケーション リソースを使用する
この例では、アプリケーション リソースを使用する方法を示します。
## <a name="example"></a>例
次の例は、アプリケーション定義ファイルを示しています。 アプリケーション定義ファイルは、リソース セクションを定義します (値を<xref:System.Windows.Application.Resources%2A>プロパティ)。 アプリケーション レベルで定義されているリソースには、そのアプリケーションの一部であるその他すべてのページからアクセスできます。 この例では、リソースは宣言済みのスタイルです。 この例は省略内で定義されているコントロールのテンプレートをコントロール テンプレートを含む完全なスタイル指定できますが、時間がかかるため、<xref:System.Windows.Controls.ContentControl.ContentTemplate%2A>スタイルのプロパティ set アクセス操作子。
[!code-xaml[ResourcesApplication#PreTemplateResource](../../../../samples/snippets/csharp/VS_Snippets_Wpf/ResourcesApplication/CS/app.xaml#pretemplateresource)]
[!code-xaml[ResourcesApplication#PostTemplateResource](../../../../samples/snippets/csharp/VS_Snippets_Wpf/ResourcesApplication/CS/app.xaml#posttemplateresource)]
次の例は、[!INCLUDE[TLA2#tla_xaml](../../../../includes/tla2sharptla-xaml-md.md)]前の例で定義されているアプリケーション レベル リソースを参照するページ。 使用して、リソースが参照されている、 [StaticResource マークアップ拡張機能](../../../../docs/framework/wpf/advanced/staticresource-markup-extension.md)要求されたリソースの一意のリソース キーを指定します。 "GelButton" というキーを持つリソースが、現在のページで見つからないため、要求されているリソースのリソース ルックアップ スコープは、現在のページを越えて、定義されているアプリケーション レベルのリソースまで継続されます。
[!code-xaml[ResourcesApplication#ConsumingPage](../../../../samples/snippets/csharp/VS_Snippets_Wpf/ResourcesApplication/CS/page1.xaml#consumingpage)]
## <a name="see-also"></a>関連項目
[XAML リソース](../../../../docs/framework/wpf/advanced/xaml-resources.md)
[アプリケーション管理の概要](../../../../docs/framework/wpf/app-development/application-management-overview.md)
[方法トピック](../../../../docs/framework/wpf/advanced/resources-how-to-topics.md)
| 65.8125 | 383 | 0.783951 | yue_Hant | 0.76537 |
6f87153f6e1c9e50a4fc7f634a907b6b64242367 | 209 | md | Markdown | __tests__/tag/test-data/read.md | strongishllama/populate-pull-request | c2e6f3be6aa1bdfb98399747478d4105da9f79eb | [
"MIT"
] | null | null | null | __tests__/tag/test-data/read.md | strongishllama/populate-pull-request | c2e6f3be6aa1bdfb98399747478d4105da9f79eb | [
"MIT"
] | 12 | 2022-02-11T07:13:42.000Z | 2022-03-25T16:16:31.000Z | __tests__/tag/test-data/read.md | strongishllama/populate-pull-request | c2e6f3be6aa1bdfb98399747478d4105da9f79eb | [
"MIT"
] | null | null | null | # Changelog
- First change.
- Second change.
- Third change.
<!-- POPULATE PULL REQUEST START TAG -->
# Resources
- [Test Key]()
- [Other Test Key](Other Test Value)
<!-- POPULATE PULL REQUEST END TAG -->
| 14.928571 | 40 | 0.655502 | yue_Hant | 0.693481 |
6f8741e948a1c6d063c0ff7f5fa21907c723b380 | 135 | md | Markdown | content/en/location/sendai/index.md | metatek/ywamjapan.org | 6327bed1196b7bb222a42334352f44f1234a0142 | [
"MIT"
] | null | null | null | content/en/location/sendai/index.md | metatek/ywamjapan.org | 6327bed1196b7bb222a42334352f44f1234a0142 | [
"MIT"
] | null | null | null | content/en/location/sendai/index.md | metatek/ywamjapan.org | 6327bed1196b7bb222a42334352f44f1234a0142 | [
"MIT"
] | 1 | 2020-05-12T07:25:05.000Z | 2020-05-12T07:25:05.000Z | ---
title: YWAM Sendai
summary: Location | Sendai City, Miyagi, Tohoku
type: "widget_page"
tags: ["Explore", "Tohoku", "Location"]
---
| 19.285714 | 47 | 0.681481 | eng_Latn | 0.317484 |
6f87f359258aefea15ce9a6cf756bd10e0f3b71e | 686 | md | Markdown | docs/data-sources/project.md | davidji99/terraform-provider-rollbar | 98aac1e8197829bde03062bc0300a7aceedab1f2 | [
"Apache-2.0"
] | 5 | 2020-02-20T00:33:09.000Z | 2021-01-14T12:01:50.000Z | docs/data-sources/project.md | davidji99/terraform-provider-rollbar | 98aac1e8197829bde03062bc0300a7aceedab1f2 | [
"Apache-2.0"
] | 58 | 2020-02-09T00:37:47.000Z | 2022-03-31T21:08:17.000Z | docs/data-sources/project.md | davidji99/terraform-provider-rollbar | 98aac1e8197829bde03062bc0300a7aceedab1f2 | [
"Apache-2.0"
] | 3 | 2020-03-11T21:46:07.000Z | 2021-01-20T11:55:21.000Z | ---
layout: "rollbar"
page_title: "Rollbar: rollbar_project"
sidebar_current: "docs-rollbar-datasource-project-x"
description: |-
Get information on a Rollbar Project.
---
# Data Source: rollbar_project
Use this data source to get information about a Rollbar Project.
## Example Usage
```hcl-terraform
data "rollbar_project" "foobar" {
name = "my_project"
}
```
## Argument Reference
The following arguments are supported:
* `name` - (Required) The project name
## Attributes Reference
In addition to all arguments above, the following attributes are exported:
* `id` - The project id
* `status` - The project status
* `account_id` - The account id the project belongs to
| 20.176471 | 74 | 0.737609 | eng_Latn | 0.925325 |
6f880416615e06d119b64eb2989fbc47dcd7fea4 | 1,202 | md | Markdown | src/tab-bar/index.md | cqkqinfo/ui | a0d6a0fcf941b8cc08ca1c364b67a5be81e8a151 | [
"MIT"
] | 24 | 2021-09-18T08:21:30.000Z | 2022-03-16T03:26:08.000Z | src/tab-bar/index.md | cqkqinfo/ui | a0d6a0fcf941b8cc08ca1c364b67a5be81e8a151 | [
"MIT"
] | 19 | 2021-12-11T13:28:30.000Z | 2022-03-31T12:10:38.000Z | src/tab-bar/index.md | cqkqinfo/ui | a0d6a0fcf941b8cc08ca1c364b67a5be81e8a151 | [
"MIT"
] | 7 | 2021-10-12T01:48:55.000Z | 2022-01-13T04:31:31.000Z | ---
nav:
title: 组件
path: /components
group:
title: 数据显示
path: /data-display
---
## TabBar 底部导航栏
底部导航栏
```tsx
import React, { useState } from 'react';
import { Space, TabBar, PartTitle, Icon } from '@kqinfo/ui';
export default () => {
const tabData = [
{
icon: <Icon name={'kq-search'} />,
index: 0,
title: '首页',
},
{
icon: <Icon name={'kq-loading'} />,
index: 1,
title: '工作台',
},
{
icon: <Icon name={'kq-down'} />,
index: 2,
title: '我的',
},
];
const tabData2 = [
{
icon: <Icon name={'kq-search'} />,
index: 0,
title: '首页',
},
{
icon: () => (
<Space style={{ transform: 'translateY(-30%)' }}>
<Icon name={'kq-zengjia'} color={'#2780d9'} size={100} />
</Space>
),
index: 1,
},
{
icon: <Icon name={'kq-down'} />,
index: 2,
title: '我的',
},
];
return (
<Space vertical size={'10px'}>
<PartTitle>一般用法</PartTitle>
<TabBar items={tabData} />
<PartTitle>自定义渲染</PartTitle>
<TabBar items={tabData2} />
</Space>
);
};
```
<API exports='["default", "tabBarItemProps"]'></API>
| 17.676471 | 67 | 0.476705 | kor_Hang | 0.218098 |
6f883e74f203f1a719bcc2e8993edf1d47b142f1 | 1,143 | md | Markdown | README.md | Kaushaldevy/tasks-lister | 9ed82b58176e13426d59e4e1647a7402d36b7078 | [
"Apache-2.0"
] | 7 | 2015-12-14T02:38:46.000Z | 2020-10-13T23:40:03.000Z | README.md | lukyth/tasks-lister | 9ed82b58176e13426d59e4e1647a7402d36b7078 | [
"Apache-2.0"
] | null | null | null | README.md | lukyth/tasks-lister | 9ed82b58176e13426d59e4e1647a7402d36b7078 | [
"Apache-2.0"
] | 19 | 2016-03-08T04:45:36.000Z | 2022-03-14T12:18:05.000Z | # Tasks Lister
> A kernel module that lists all current tasks in a Linux system
This is a project for my Operating System class, Computer Engineering, Kasetsart University.
The assignments are from a book "Operating System Concepts, 9th Edition", Chapter 3 - Process Concept, Project 2 - Linux Kernel Module for Listing Tasks.
### Part I Assignment
Design a kernel module that iterates through all tasks in the system using the `for_each_process()` macro. Make the contents appear in the kernel log buffer.
### Part II Assignment
The same as Part I but use DFS tree instead.
## Installation
```
$ git clone https://github.com/lukyth/tasks-lister.git
$ cd tasks-lister/
```
## How to use
```
$ cd src/[linear|dfs]
$ make # Make module
$ insmod tasks_lister_[linear|dfs].ko # Install module
$ dmesg # Show message
$ rmmod tasks_lister_[linear|dfs] # Remove module
$ dmesg # Show message
$ dmesg -C # Clear message
```
## License
Apache 2.0
Copyright 2015 [Kanitkorn Sujautra](https://kanitkorn.com)
| 32.657143 | 157 | 0.655293 | eng_Latn | 0.774256 |
6f88d33191ae789175caca73e3cbe1d293bde1b7 | 6,297 | md | Markdown | articles/api-management/api-management-policy-reference.md | huiw-git/azure-content-zhtw | f20103dc3d404c9c929c155b36c5a47aee5baed6 | [
"CC-BY-3.0"
] | null | null | null | articles/api-management/api-management-policy-reference.md | huiw-git/azure-content-zhtw | f20103dc3d404c9c929c155b36c5a47aee5baed6 | [
"CC-BY-3.0"
] | null | null | null | articles/api-management/api-management-policy-reference.md | huiw-git/azure-content-zhtw | f20103dc3d404c9c929c155b36c5a47aee5baed6 | [
"CC-BY-3.0"
] | 1 | 2020-11-04T04:34:56.000Z | 2020-11-04T04:34:56.000Z | <properties
pageTitle="Azure API 管理原則參考文件"
description="了解可用來設定 API 管理的原則。"
services="api-management"
documentationCenter=""
authors="steved0x"
manager="dwrede"
editor=""/>
<tags
ms.service="api-management"
ms.workload="mobile"
ms.tgt_pltfrm="na"
ms.devlang="na"
ms.topic="article"
ms.date="02/16/2016"
ms.author="sdanie"/>
# Azure API 管理原則參考文件
本節提供 [API 管理原則參考文件][]中原則的索引。如需有關新增和設定原則的資訊，請參閱 [API 管理中的原則][]。
如果原則不另行指定，則可以在任何 API 管理原則中，使用原則運算式做為屬性值或文字值。某些原則是以原則運算式為基礎，例如[控制流程][]和[設定變數][]原則。如需詳細資訊，請參閱[進階原則][]和[原則運算式][]。
## 原則參考索引
- [存取限制原則][]
- [檢查 HTTP 標頭][] - 強制必須存在和/或強制採用 HTTP 標頭的值。
- [依訂閱限制呼叫率][] - 以訂閱為單位，限制呼叫率以避免 API 使用量暴增。
- [依金鑰限制呼叫率](https://msdn.microsoft.com/library/azure/dn894078.aspx#LimitCallRateByKey) - 以金鑰為單位，限制呼叫率以避免 API 使用量暴增。
- [限制呼叫端 IP][] - 篩選 (允許/拒絕) 來自特定 IP 位址和/或位址範圍的呼叫。
- [依訂閱設定使用量配額][] - 以訂閱為單位，讓您可以強制採用可續訂或有存留期呼叫量與 (或) 頻寬配額。
- [依金鑰設定使用量配額](https://msdn.microsoft.com/library/azure/dn894078.aspx#SetUsageQuotaByKey) - 以金鑰為單位，讓您可以強制採用可續訂或有存留期呼叫量與 (或) 頻寬配額。
- [驗證 JWT][] - 強制擷取自指定 HTTP 標頭或指定查詢參數的 JWT 必須存在且有效。
- [進階原則][]
- [控制流程][] - 根據布林值[運算式][]的評估結果，有條件地套用原則陳述式。
- [轉寄要求][] - 將要求轉寄至後端服務。
- [記錄至事件中樞][] - 將指定格式的訊息傳送至[記錄器](https://msdn.microsoft.com/library/azure/mt592020.aspx#Logger)實體所定義的訊息目標。
- [傳回回應](https://msdn.microsoft.com/library/azure/dn894085.aspx#ReturnResponse) - 中止管線執行，並將指定的回應直接傳回呼叫者。
- [傳送單向要求](https://msdn.microsoft.com/library/azure/dn894085.aspx#SendOneWayRequest) - 將要求傳送到指定的 URL，無須等待回應。
- [傳送要求](https://msdn.microsoft.com/library/azure/dn894085.aspx#SendRequest) - 將要求傳送到指定的 URL。
- [設定要求方法](https://msdn.microsoft.com/library/azure/dn894085.aspx#SetRequestMethod) - 允許您變更要求的 HTTP 方法。
- [設定狀態碼](https://msdn.microsoft.com/library/azure/dn894085.aspx#SetStatus) - 將 HTTP 狀態碼變更為指定的值。
- [設定變數][] - 保存具名 [context][] 變數中的值，供日後存取使用。
- [等候](https://msdn.microsoft.com/library/azure/dn894085.aspx#Wait) - 等候括住的 Send 要求、取得快取的值或控制流程原則於完成後再繼續。
- [驗證原則][]
- [使用基本驗證進行驗證][] - 使用基本驗證來驗證後端服務。
- [使用用戶端憑證進行驗證][] - 使用用戶端憑證來驗證後端服務。
- [快取原則][]
- [從快取中取得][] - 執行快取查閱並傳回有效的快取回應 (如果有的話)。
- [儲存至快取][] - 根據指定的快取控制組態來快取回應。
- [從快取取得值](https://msdn.microsoft.com/library/azure/dn894086.aspx#GetFromCacheByKey) - 依金鑰擷取快取的項目。
- [儲存快取中的值](https://msdn.microsoft.com/library/azure/dn894086.aspx#StoreToCacheByKey) -依金鑰儲存快取中的項目。
- [跨網域原則][]
- [允許跨網域呼叫][] - 將 API 設為可供 Adobe Flash 和 Microsoft Silverlight 瀏覽器型用戶端存取。
- [CORS][] - 將跨原始來源資源分享 (CORS) 支援加入至操作或 API，以允許來自瀏覽器型用戶端的跨網域呼叫。
- [JSONP][] - 將 JSON 與補充的 (JSONP) 支援加入至操作或 API，以允許來自 JavaScript 瀏覽器型用戶端的跨網域呼叫。
- [轉換原則][]
- [將 JSON 轉換成 XML][] - 將要求或回應內文從 JSON 轉換成 XML。
- [將 XML 轉換成 JSON][] - 將要求或回應內文從 XML 轉換成 JSON。
- [在內文中尋找並取代字串][] - 尋找要求或回應子字串，並替換為其他子字串。
- [遮罩內容中的 URL][] - 重寫 (遮罩) 回應內文與位置標頭中的連結，使其經由閘道指向同等的連結。
- [設定後端服務][] - 變更傳入要求的後端服務。
- [設定本文][] - 設定傳入和傳出要求的訊息本文。
- [設定 HTTP 標頭][] - 指派值給現有的回應及/或要求標頭，或加入新的回應及/或要求標頭。
- [設定查詢字串參數][] - 新增、取代值或刪除要求查詢字串參數。
- [重寫 URL][] - 將要求 URL 從公用格式轉換成 Web 服務所需的格式。
## 後續步驟
如需原則運算式的詳細資訊，請觀看以下影片。
> [AZURE.VIDEO policy-expressions-in-azure-api-management]
[存取限制原則]: https://msdn.microsoft.com/library/azure/dn894078.aspx
[檢查 HTTP 標頭]: https://msdn.microsoft.com/library/azure/034febe3-465f-4840-9fc6-c448ef520b0f#CheckHTTPHeader
[依訂閱限制呼叫率]: https://msdn.microsoft.com/library/azure/034febe3-465f-4840-9fc6-c448ef520b0f#LimitCallRate
[限制呼叫端 IP]: https://msdn.microsoft.com/library/azure/034febe3-465f-4840-9fc6-c448ef520b0f#RestrictCallerIPs
[依訂閱設定使用量配額]: https://msdn.microsoft.com/library/azure/034febe3-465f-4840-9fc6-c448ef520b0f#SetUsageQuota
[驗證 JWT]: https://msdn.microsoft.com/library/azure/034febe3-465f-4840-9fc6-c448ef520b0f#ValidateJWT
[進階原則]: https://msdn.microsoft.com/library/azure/dn894085.aspx
[控制流程]: https://msdn.microsoft.com/library/azure/dn894085.aspx#choose
[設定變數]: https://msdn.microsoft.com/library/azure/dn894085.aspx#set_variable
[運算式]: https://msdn.microsoft.com/library/azure/dn910913.aspx
[context]: https://msdn.microsoft.com/library/azure/ea160028-fc04-4782-aa26-4b8329df3448#ContextVariables
[轉寄要求]: https://msdn.microsoft.com/library/azure/dn894085.aspx#ForwardRequest
[記錄至事件中樞]: https://msdn.microsoft.com/library/azure/dn894085.aspx#log-to-eventhub
[驗證原則]: https://msdn.microsoft.com/library/azure/dn894079.aspx
[使用基本驗證進行驗證]: https://msdn.microsoft.com/library/azure/061702a7-3a78-472b-a54a-f3b1e332490d#Basic
[使用用戶端憑證進行驗證]: https://msdn.microsoft.com/library/azure/061702a7-3a78-472b-a54a-f3b1e332490d#ClientCertificate
[快取原則]: https://msdn.microsoft.com/library/azure/dn894086.aspx
[從快取中取得]: https://msdn.microsoft.com/library/azure/8147199c-24d8-439f-b2a9-da28a70a890c#GetFromCache
[儲存至快取]: https://msdn.microsoft.com/library/azure/8147199c-24d8-439f-b2a9-da28a70a890c#StoreToCache
[跨網域原則]: https://msdn.microsoft.com/library/azure/dn894084.aspx
[允許跨網域呼叫]: https://msdn.microsoft.com/library/azure/7689d277-8abe-472a-a78c-e6d4bd43455d#AllowCrossDomainCalls
[CORS]: https://msdn.microsoft.com/library/azure/7689d277-8abe-472a-a78c-e6d4bd43455d#CORS
[JSONP]: https://msdn.microsoft.com/library/azure/7689d277-8abe-472a-a78c-e6d4bd43455d#JSONP
[轉換原則]: https://msdn.microsoft.com/library/azure/dn894083.aspx
[將 JSON 轉換成 XML]: https://msdn.microsoft.com/library/azure/7406a8ce-5f9c-4fae-9b0f-e574befb2ee9#ConvertJSONtoXML
[將 XML 轉換成 JSON]: https://msdn.microsoft.com/library/azure/7406a8ce-5f9c-4fae-9b0f-e574befb2ee9#ConvertXMLtoJSON
[在內文中尋找並取代字串]: https://msdn.microsoft.com/library/azure/7406a8ce-5f9c-4fae-9b0f-e574befb2ee9#Findandreplacestringinbody
[遮罩內容中的 URL]: https://msdn.microsoft.com/library/azure/7406a8ce-5f9c-4fae-9b0f-e574befb2ee9#MaskURLSContent
[設定後端服務]: https://msdn.microsoft.com/library/azure/7406a8ce-5f9c-4fae-9b0f-e574befb2ee9#SetBackendService
[設定本文]: https://msdn.microsoft.com/library/azure/dn894083.aspx#SetBody
[設定 HTTP 標頭]: https://msdn.microsoft.com/library/azure/7406a8ce-5f9c-4fae-9b0f-e574befb2ee9#SetHTTPheader
[設定查詢字串參數]: https://msdn.microsoft.com/library/azure/7406a8ce-5f9c-4fae-9b0f-e574befb2ee9#SetQueryStringParameter
[重寫 URL]: https://msdn.microsoft.com/library/azure/7406a8ce-5f9c-4fae-9b0f-e574befb2ee9#RewriteURL
[API 管理中的原則]: api-management-howto-policies.md
[API 管理原則參考文件]: https://msdn.microsoft.com/library/azure/dn894081.aspx
[原則運算式]: https://msdn.microsoft.com/library/azure/dn910913.aspx
<!---HONumber=AcomDC_0218_2016--> | 51.614754 | 130 | 0.760521 | yue_Hant | 0.947416 |
6f8922ad6ed824f055fbf46bace7fd0743331ca2 | 1,211 | md | Markdown | README.md | SRINIVAS-B-SINDAGI/react-oidc-client-js | 76fd43b46c565ec7b8869d1e97879cf737aba572 | [
"MIT"
] | 180 | 2018-07-13T12:58:15.000Z | 2022-03-29T01:45:25.000Z | README.md | SRINIVAS-B-SINDAGI/react-oidc-client-js | 76fd43b46c565ec7b8869d1e97879cf737aba572 | [
"MIT"
] | 23 | 2019-03-29T11:59:35.000Z | 2022-03-31T07:59:17.000Z | README.md | SRINIVAS-B-SINDAGI/react-oidc-client-js | 76fd43b46c565ec7b8869d1e97879cf737aba572 | [
"MIT"
] | 73 | 2018-09-18T12:13:26.000Z | 2022-03-14T10:02:54.000Z | 
# React-oidc-client-js
> OpenID Connect (OIDC) client with React and typescript
- This is sample application that contains [oidc-client-js](https://github.com/IdentityModel/oidc-client-js) and `React` with `Typescript`.
- The application is based on `create-react-app` - [Create React App](https://github.com/facebook/create-react-app)
# Project status
[](https://ci.appveyor.com/project/JanSkoruba/react-oidc-client-js)
# Installation
## Cloning app
- `git clone https://github.com/skoruba/react-oidc-client-js.git`
- `cd src/`
## Install dependecies
- Install dependecies - `yarn install`
## Running app
- `yarn start` - start the web server that is running on [http://localhost:4200](http://localhost:4200)
- The application is connected to `OpenID Connect Provider` that is running on [https://demo.identityserver.io/](https://demo.identityserver.io/)
- This STS has configured a SPA client to run on http://localhost:4200, therefore a sample application will be running on this port `4200`.
## App preview
| 34.6 | 153 | 0.748142 | eng_Latn | 0.666406 |
6f893c476c2272a86e9eb41f11c07d860f90837d | 2,426 | md | Markdown | docs/visual-basic/programming-guide/language-features/control-flow/index.md | MarktW86/dotnet.docs | 178451aeae4e2c324aadd427ed6bf6850e483900 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/visual-basic/programming-guide/language-features/control-flow/index.md | MarktW86/dotnet.docs | 178451aeae4e2c324aadd427ed6bf6850e483900 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/visual-basic/programming-guide/language-features/control-flow/index.md | MarktW86/dotnet.docs | 178451aeae4e2c324aadd427ed6bf6850e483900 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "Control Flow in Visual Basic | Microsoft Docs"
ms.custom: ""
ms.date: "2015-07-20"
ms.prod: .net
ms.reviewer: ""
ms.suite: ""
ms.technology:
- "devlang-visual-basic"
ms.topic: "article"
dev_langs:
- "VB"
helpviewer_keywords:
- "statements [Visual Basic], control flow"
- "control flow"
- "control structures"
- "structures, control"
- "conditional statements, control flow"
ms.assetid: 5623ef47-52b1-4202-befd-9af36422ec6f
caps.latest.revision: 14
author: dotnet-bot
ms.author: dotnetcontent
translation.priority.ht:
- "cs-cz"
- "de-de"
- "es-es"
- "fr-fr"
- "it-it"
- "ja-jp"
- "ko-kr"
- "pl-pl"
- "pt-br"
- "ru-ru"
- "tr-tr"
- "zh-cn"
- "zh-tw"
---
# Control Flow in Visual Basic
Left unregulated, a program proceeds through its statements from beginning to end. Some very simple programs can be written with only this unidirectional flow. However, much of the power and utility of any programming language comes from the ability to change execution order with control statements and loops.
Control structures allow you to regulate the flow of your program's execution. Using control structures, you can write [!INCLUDE[vbprvb](../../../../csharp/programming-guide/concepts/linq/includes/vbprvb_md.md)] code that makes decisions or that repeats actions. Other control structures let you guarantee disposal of a resource or run a series of statements on the same object reference.
## In This Section
[Decision Structures](../../../../visual-basic/programming-guide/language-features/control-flow/decision-structures.md)
Describes control structures used for branching.
[Loop Structures](../../../../visual-basic/programming-guide/language-features/control-flow/loop-structures.md)
Discusses control structures used to repeat processes.
[Other Control Structures](../../../../visual-basic/programming-guide/language-features/control-flow/other-control-structures.md)
Describes control structures used for resource disposal and object access.
[Nested Control Structures](../../../../visual-basic/programming-guide/language-features/control-flow/nested-control-structures.md)
Covers control structures inside other control structures.
## Related Sections
[Control Flow Summary](../../../../visual-basic/language-reference/keywords/control-flow-summary.md)
Provides links to language reference pages on this subject. | 40.433333 | 391 | 0.729184 | eng_Latn | 0.897383 |
6f8a955aed14be37290d53569202c77ba4b3be58 | 1,183 | md | Markdown | readme.md | tomdries/content-analysis-tools | d4eaec2ae952b4bb93725ae06330485e6c0fdd13 | [
"BSD-3-Clause"
] | null | null | null | readme.md | tomdries/content-analysis-tools | d4eaec2ae952b4bb93725ae06330485e6c0fdd13 | [
"BSD-3-Clause"
] | null | null | null | readme.md | tomdries/content-analysis-tools | d4eaec2ae952b4bb93725ae06330485e6c0fdd13 | [
"BSD-3-Clause"
] | null | null | null | # Content analysis tools
This repo contains code to analyse text that contains tagged content, which I used to analyse an [interview with driving examiners](https://www.researchgate.net/publication/355393718_Driving_examiners'_views_on_data-driven_assessment_of_test_candidates_An_interview_study).
For a demonstration of the package with a mockup interview transcript, see `demo.ipynb`. This notebook can be executed in the browser with binder:
[](https://mybinder.org/v2/gh/tomdries/content-analysis-tools/HEAD?filepath=demo.ipynb)
Currently, it supports loading strings and word (docx) documents, and it assumes all text in the document is preceded by participant numbers (formatted as, for example, `P1:`), and tagged with the following grammar `#tag-stem.suffix1.suffix2{elaborate comment}`.
## Usage
Please cite the following article:
Driessen, T., Picco, A., Dodou, D., de Waard, D., & de Winter, J. (2021). Driving examiners’ views on data-driven assessment of test candidates: An interview study. Transportation Research Part F: Traffic Psychology and Behaviour, 83, 60–79. https://doi.org/10.1016/j.trf.2021.09.021
| 65.722222 | 283 | 0.786137 | eng_Latn | 0.902999 |
6f8ab38b7654ba39d9fbb81b5fd77c09c14cdb4d | 4,212 | md | Markdown | _posts/2019-07-04-Download-the-unmade-bed-of-architecture.md | Kirsten-Krick/Kirsten-Krick | 58994392de08fb245c4163dd2e5566de8dd45a7a | [
"MIT"
] | null | null | null | _posts/2019-07-04-Download-the-unmade-bed-of-architecture.md | Kirsten-Krick/Kirsten-Krick | 58994392de08fb245c4163dd2e5566de8dd45a7a | [
"MIT"
] | null | null | null | _posts/2019-07-04-Download-the-unmade-bed-of-architecture.md | Kirsten-Krick/Kirsten-Krick | 58994392de08fb245c4163dd2e5566de8dd45a7a | [
"MIT"
] | null | null | null | ---
layout: post
comments: true
categories: Other
---
## Download The unmade bed of architecture book
" significant he had not objected to the use of his nickname. Starck, gliding off into the night where the drums thudded in distant darkness, has no consequences unless we insist on empowering it by not living entirely in the future, a brutish face. was granted by the Russian government to Hutchinson, Gelluk knew that once planned, nevertheless she had the And that's why I sold her. Enlarged knuckles, they would be at once face-to-face. Poriferan, but he had not raised his hand, sure, lost it as he found it, p. the unmade bed of architecture the interstate highway in Utah, a couple of nobody, too. After the the unmade bed of architecture moves, as though trouble lurks in every direction. Lover's quarrel, and a slab of blackness swung shut upon the exit he had "He does not understand that. " "Does he have nice teeth?" she asked. had sprouted with life during the week after the departure of the Burroughs. " He went to the large black Wathort? etc. His hands slipped from months at sea, Nolly had an air of toughness worthy of Sam Spade, i? start to move. one, and the arena crew turns off the blowers. And that had been one of the No one. oversees maintenance of the ghost town, to be in the lock's innermost parts of Polar America. Not right away. It doesn't matter so much whether the course of action to "Your mother's wise," Paul said. Her I chuckled and sat on the edge of the bed. " When she closed her eyes, four ones. 2020LeGuin20-20Tales20From20Earthsea. Soon afterward he began to sound out sources of support, leaving her employed she sits on a part of the skin and stretches out the other The pending storm had broken, has placed the home of canopy and angles the unmade bed of architecture the buildings? will return to you, much in the same way as we eat bread. She says there isn't. as though Junior had grabbed her knockers and had tried to shove his tongue easily, boy?" without some sort of exhaust, philosophize about pie, in the course of which a covey of "More. Brushing past her, "is this story more extraordinary than that of the thief who believed the woman and sought refuge with God against falling in with her like? silenced himself! the vessels parted company, with any difficulty. gnomes. It's quite different from the others. Too cowardly for hand-to-hand combat, and he was disappointed. " Lechat stared at her, if they didn't mind being squeezed a little. " Then she took leave of me and I of her, and it had been only a matter of minutes before lift-off when one of the flight-crew noticed that suddenly they weren't there-any the unmade bed of architecture them. ' And he answered, slipping around the comer ahead of him, boiled 34 living, I guess if you were going to just plug him, pale "I know, basing every choice on instinct в which brought them eventually to a dead end, I don't know what I'm supposed to say, hoping that a minim of mother-daughter bonding might occur. You look the unmade bed of architecture Bette Davis. Sooner than she expected, 3RD MARCH preschool children she's tortured and murdered. some people go into denial and nevertheless resort to a style of speech hardly the Polar travellers' vessel is hindered by impenetrable masses of Somewhere in the world he had a deadly enemy: Bartholomew, forming a league of mages. He knew nothing at all about women. The black guillemots "No, All these attempts to force a passage in the open sea from the "September 27. 291). More disturbing than the unmade bed of architecture plate returned was the penguin taken. Barry?" Island on Spitzbergen, because they believed that God was angry with muscles protest to watch, but that she generally is. bare but determined hands. They linked arms and stood staring up at the sky. Disgusting. He stabbed Prosser, The unmade bed of architecture oldest Maps of the North--Herbertstein's account of With only half the town behind them, not only in and they won't be distracted. about something or other, I'd be all for it if we were better Sinsemilla, consisting partly of a large number (at a hero, and newspapers featured his photograph in most stories. | 468 | 4,108 | 0.786325 | eng_Latn | 0.999941 |
6f8b3900a83fb1f5042d76a705680435e994a413 | 1,218 | md | Markdown | plugins/attributes.md | johanbrook/lumeland.github.io | 36bc6b0e9c9e101495f05e7aaade35a07980d369 | [
"MIT"
] | null | null | null | plugins/attributes.md | johanbrook/lumeland.github.io | 36bc6b0e9c9e101495f05e7aaade35a07980d369 | [
"MIT"
] | null | null | null | plugins/attributes.md | johanbrook/lumeland.github.io | 36bc6b0e9c9e101495f05e7aaade35a07980d369 | [
"MIT"
] | null | null | null | ---
title: Attributes
description: To manage attributes and class names of HTML elements
---
This plugin **is disabled by default** so to enable it, you have to edit your
`_config.js` file:
```js
import lume from "lume/mod.ts";
import attributes from "lume/plugins/attributes.ts";
const site = lume();
site.use(attributes());
```
The `attributes` plugin register two template filters to normalize the
attributes of your HTML. The included filters are:
## attr
Provide a convenient way to work with HTML attributes.
```html
---
link:
title: Go to GitHub
href: https://github.com
target: _blank
---
<a {{ link | attr | safe }}>
```
You can also filter the attributes names:
```html
---
link:
text: Go to GitHub
href: https://github.com
target: _blank
noopen: true
class:
- link
- link-external
---
<a {{ link | attr('href', 'target', 'noopen', 'class') | safe }}>
{{ link.text }}
</a>
```
## class
To work with HTML class names:
```html
---
styles:
- btn
- btn-primary
---
<a class="{{ styles | class }}">
```
You can use objects to enable/disable classes:
```html
---
styles:
btn: true
btn-primary: true
is-disabled: false
---
<a class="{{ styles | class }}">
```
| 15.037037 | 77 | 0.644499 | eng_Latn | 0.933347 |
6f8b592dddb9cde44aec1ab2988ef596c6cff5a5 | 49 | md | Markdown | docs/src/advanced/type-inference.md | hash-org/lang | d5e9328279b090255b7fe22520b042dd47b0302b | [
"MIT"
] | 7 | 2021-04-28T17:50:02.000Z | 2022-02-05T23:03:51.000Z | docs/src/advanced/type-inference.md | hash-org/lang | d5e9328279b090255b7fe22520b042dd47b0302b | [
"MIT"
] | 66 | 2021-04-28T21:12:07.000Z | 2022-02-22T15:47:25.000Z | docs/src/advanced/type-inference.md | hash-org/lang | d5e9328279b090255b7fe22520b042dd47b0302b | [
"MIT"
] | null | null | null | # Type inference
🚧 Still under construction! 🚧
| 12.25 | 30 | 0.714286 | eng_Latn | 0.926708 |
6f8b9d6aadffc517ed182ee8ad2cc13d3fd27859 | 11,888 | md | Markdown | articles/active-directory/active-directory-v2-devquickstarts-android.md | OpenLocalizationTestOrg/azure-docs-pr15_it-IT | a5b6eb257721d6a02db53be2d3b2bee1d9e5aa1c | [
"CC-BY-3.0",
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/active-directory-v2-devquickstarts-android.md | OpenLocalizationTestOrg/azure-docs-pr15_it-IT | a5b6eb257721d6a02db53be2d3b2bee1d9e5aa1c | [
"CC-BY-3.0",
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/active-directory-v2-devquickstarts-android.md | OpenLocalizationTestOrg/azure-docs-pr15_it-IT | a5b6eb257721d6a02db53be2d3b2bee1d9e5aa1c | [
"CC-BY-3.0",
"CC-BY-4.0",
"MIT"
] | null | null | null | <properties
pageTitle="Azure Active Directory app di Android v 2.0 | Microsoft Azure"
description="Come creare un'app Android accede gli utenti che dispongono sia personale account Microsoft e lavoro o dell'istituto di istruzione account e le chiamate API grafico utilizzando le raccolte di terze parti."
services="active-directory"
documentationCenter=""
authors="brandwe"
manager="mbaldwin"
editor=""/>
<tags
ms.service="active-directory"
ms.workload="identity"
ms.tgt_pltfrm="na"
ms.devlang="na"
ms.topic="article"
ms.date="09/16/2016"
ms.author="brandwe"/>
# <a name="add-sign-in-to-an-android-app-using-a-third-party-library-with-graph-api-using-the-v20-endpoint"></a>Aggiungere l'accesso a un'app di Android con una raccolta di terze parti API grafico utilizzando l'endpoint v 2.0
La piattaforma identità Microsoft utilizza standard aperti, ad esempio OAuth2 e OpenID connettersi. Gli sviluppatori possono utilizzare raccolta per l'integrazione con i servizi. Per consentire agli sviluppatori di utilizzare la piattaforma con altre raccolte, abbiamo scritto alcune procedure dettagliate analogo al seguente per dimostrare come configurare le librerie di terze parti per connettersi alla piattaforma Microsoft identità. La maggior parte delle raccolte in cui implementano [specifiche RFC6749 OAuth2](https://tools.ietf.org/html/rfc6749) possono connettersi alla piattaforma di identità di Microsoft.
Con l'applicazione creata in questa procedura dettagliata, gli utenti possono accedere alla propria organizzazione e quindi cercare per se stessi all'interno dell'organizzazione tramite l'API di grafico.
Se si conosce OAuth2 o OpenID connettersi, la maggior parte di questo esempio di configurazione non può avere senso all'utente. È consigliabile leggere [2.0 protocolli - OAuth 2.0 autorizzazione codice flusso](active-directory-v2-protocols-oauth-code.md) per lo sfondo.
> [AZURE.NOTE] Alcune caratteristiche della piattaforma che dispongono di un'espressione in standard OAuth2 o OpenID connettersi, ad esempio accesso condizionato e gestione di criteri Intune, è necessario usare il nostro Apri origine librerie di identità di Microsoft Azure.
Endpoint v 2.0 non supporta tutti gli scenari di Azure Active Directory e funzionalità.
> [AZURE.NOTE] Per determinare se è necessario utilizzare l'endpoint v 2.0, informazioni sulle [limitazioni v 2.0](active-directory-v2-limitations.md).
## <a name="download-the-code-from-github"></a>Scaricare il codice dal GitHub
Il codice per questa esercitazione viene mantenuto [sul GitHub](https://github.com/Azure-Samples/active-directory-android-native-oidcandroidlib-v2). Per seguire, è possibile [scaricare struttura dell'app come un file ZIP](https://github.com/Azure-Samples/active-directory-android-native-oidcandroidlib-v2/archive/skeleton.zip) o duplicare la struttura:
```
git clone --branch skeleton git@github.com:Azure-Samples/active-directory-android-native-oidcandroidlib-v2.git
```
È anche possibile scaricare il campione e iniziare immediatamente:
```
git@github.com:Azure-Samples/active-directory-android-native-oidcandroidlib-v2.git
```
## <a name="register-an-app"></a>Registrare un'app
Creare una nuova app [portale di registrazione dell'applicazione](https://apps.dev.microsoft.com/?referrer=https://azure.microsoft.com/documentation/articles&deeplink=/appList)o seguire la procedura dettagliata su [come registrare un'app all'endpoint v 2.0](active-directory-v2-app-registration.md). Assicurarsi di:
- Copiare l' **Id applicazione di** assegnare all'app perché sarà necessario breve.
- Aggiungere la piattaforma **Mobile** per l'app.
> Nota: Il portale di registrazione applicazione rappresenta un valore **URI reindirizzare la chiamata** . In questo esempio è necessario utilizzare il valore predefinito di `https://login.microsoftonline.com/common/oauth2/nativeclient`.
## <a name="download-the-nxoauth2-third-party-library-and-create-a-workspace"></a>Scaricare la raccolta di terze parti NXOAuth2 e creare un'area di lavoro
Per questa procedura dettagliata, occorre usare OIDCAndroidLib da GitHub, ovvero una raccolta di OAuth2 in base al codice OpenID connessione di Google. Implementa il profilo di applicazione nativa e supporta l'endpoint di autorizzazione dell'utente. Si tratta di tutti gli elementi che è necessario per l'integrazione con la piattaforma di identità di Microsoft.
Duplicare repo OIDCAndroidLib nel computer in uso.
```
git@github.com:kalemontes/OIDCAndroidLib.git
```
## <a name="set-up-your-android-studio-environment"></a>Configurare l'ambiente di Studio Android
1. Creare un nuovo progetto di Studio Android e accettare le impostazioni predefinite della procedura guidata.
2. Per configurare i moduli di progetto, spostare repo duplicato al percorso del progetto. È possibile anche creare il progetto e quindi duplicare direttamente al percorso del progetto.
3. Aprire le impostazioni di moduli di progetto tramite il menu di scelta rapida oppure usando lo scelta rapida Ctrl + Alt + Maj + S.
4. Rimuovere il modulo di app predefinita dal momento che solo le impostazioni del contenitore di progetto.
5. Importare i moduli da repo duplicato al progetto corrente.
6. Ripetere questi passaggi per la `oidlib-sample` modulo.
7. Verificare se le dipendenze oidclib il `oidlib-sample` modulo.
8. Fare clic su **OK** e Attendi la sincronizzazione di gradle.
Il settings.gradle dovrebbe essere simile:
9. Creare l'applicazione di esempio per assicurarsi che il codice di esempio in esecuzione correttamente.
Non sarà possibile usare ancora con Azure Active Directory. È necessario configurare alcuni endpoint prima di tutto. In questo modo viene che non si dispone un problemi Studio Android prima di iniziare la personalizzazione di applicazione di esempio.
10. Creare ed eseguire `oidlib-sample` con quello di destinazione in Studio Android.
11. Eliminare la `app ` directory che è stato lasciato quando si rimuove il modulo dal progetto perché Studio Android non si elimina per la sicurezza.
12. Aprire il menu **Modifica configurazioni** per rimuovere la configurazione di esecuzione che è stata lasciata anche quando si rimuove il modulo dal progetto.
## <a name="configure-the-endpoints-of-the-sample"></a>Configurare gli endpoint del campione
Dopo avere creato la `oidlib-sample` eseguito correttamente, modifica alcuni endpoint per ottenere il lavoro con Azure Active Directory.
### <a name="configure-your-client-by-editing-the-oidcclientconfxml-file"></a>Configurare il client modificando il file oidc_clientconf.xml
1. Perché si siano utilizzando flussi di OAuth2 solo per ottenere un token e chiamare l'API di grafico, impostare il client per eseguire solo OAuth2. OIDC venga recapitata in un secondo esempio.
```xml
<bool name="oidc_oauth2only">true</bool>
```
2. Configurare l'ID client ricevuti dal portale di registrazione.
```xml
<string name="oidc_clientId">86172f9d-a1ae-4348-aafa-7b3e5d1b36f5</string>
<string name="oidc_clientSecret"></string>
```
3. Configurare il reindirizzamento URI con quella riportata di seguito.
```xml
<string name="oidc_redirectUrl">https://login.microsoftonline.com/common/oauth2/nativeclient</string>
```
4. Configurare i propri ambiti necessari per accedere all'API di grafico.
```xml
<string-array name="oidc_scopes">
<item>openid</item>
<item>https://graph.microsoft.com/User.Read</item>
<item>offline_access</item>
</string-array>
```
Il `User.Read` valore in `oidc_scopes` consente di leggere la firma di base del profilo utente.
Sono disponibili ulteriori su tutti gli ambiti disponibili in [Microsoft Graph ambiti di autorizzazione](https://graph.microsoft.io/docs/authorization/permission_scopes).
Se si preferisce spiegazioni sul `openid` o `offline_access` come ambiti OpenID Connetti, vedere la sezione [2.0 protocolli - OAuth 2.0 autorizzazione codice flusso](active-directory-v2-protocols-oauth-code.md).
### <a name="configure-your-client-endpoints-by-editing-the-oidcendpointsxml-file"></a>Configurare gli endpoint client modificando il file oidc_endpoints.xml
- Aprire la `oidc_endpoints.xml` file e apportare le modifiche seguenti:
```xml
<!-- Stores OpenID Connect provider endpoints. -->
<resources>
<string name="op_authorizationEnpoint">https://login.microsoftonline.com/common/oauth2/v2.0/authorize</string>
<string name="op_tokenEndpoint">https://login.microsoftonline.com/common/oauth2/v2.0/token</string>
<string name="op_userInfoEndpoint">https://www.example.com/oauth2/userinfo</string>
<string name="op_revocationEndpoint">https://www.example.com/oauth2/revoketoken</string>
</resources>
```
Se si utilizza OAuth2 come il protocollo non devono mai cambiare gli endpoint.
> [AZURE.NOTE]
I punti finali per `userInfoEndpoint` e `revocationEndpoint` non sono attualmente supportati da Azure Active Directory. Se si omette con il valore di example.com predefinito, si verrà avvertiti che non sono disponibili nel campione :-)
## <a name="configure-a-graph-api-call"></a>Configurare una chiamata all'API di grafico
- Aprire la `HomeActivity.java` file e apportare le modifiche seguenti:
```Java
//TODO: set your protected resource url
private static final String protectedResUrl = "https://graph.microsoft.com/v1.0/me/";
```
In questo caso una chiamata API grafico semplice restituisce le informazioni.
Queste sono tutte le modifiche che è necessario eseguire. Eseguire il `oidlib-sample` applicazione, fare clic su **Accedi**.
Dopo che è stato autenticato, selezionare il pulsante **Richiedi risorsa protetta** per testare le chiamate all'API di grafico.
## <a name="get-security-updates-for-our-product"></a>Ottenere gli aggiornamenti di sicurezza per il prodotto
È consigliabile ottenere notifiche relative ai problemi di protezione per visitare [TechCenter di sicurezza](https://technet.microsoft.com/security/dd252948) e la sottoscrizione per gli avvisi di avviso di sicurezza.
| 58.851485 | 617 | 0.780871 | ita_Latn | 0.989394 |
6f8bfe10603dd9b66f53a40ddf1c6dd5694019d4 | 943 | md | Markdown | docs/tests/scroll_tests.md | jwestfall69/ddragon-diag | 847c8cb4a447196eec895e7d608e412602c6fbc2 | [
"Unlicense"
] | null | null | null | docs/tests/scroll_tests.md | jwestfall69/ddragon-diag | 847c8cb4a447196eec895e7d608e412602c6fbc2 | [
"Unlicense"
] | null | null | null | docs/tests/scroll_tests.md | jwestfall69/ddragon-diag | 847c8cb4a447196eec895e7d608e412602c6fbc2 | [
"Unlicense"
] | null | null | null | # Scroll Tests
---
There is hardware support for scrolling the background layer. The background
layer is 512x512 pixels in size. Scrolling is handled by setting an X and Y
offset that sets the view port into the background layer. The background layer
has seamless edges, such that if you scroll off the side it will wrap around to
the other side.
The range of the offset values is 0 to 512, which is 9 bits. The lower 8 bits
are written to REG_SCROLLX ($3809) and REG_SCROLLY ($380a). The 9th bit is
handled by writing to REG_BANKSWITCH ($3808), with bit 0 being for scroll x,
and bit 1 for scroll y.
The Scroll Tests consists of filling the entire background layer with a
checkerboard of magenta tiles. The current scroll X and Y offsets are printed
on screen in hex. The joystick can then be used to scroll the background.
If scrolling is not smooth its an indication of a problem.
| 44.904762 | 79 | 0.777306 | eng_Latn | 0.999604 |
6f8c92b2efd3d153054eb1daf8cd752e4870d3f4 | 111 | md | Markdown | hsweb-examples/hsweb-examples-oauth2/hsweb-examples-oauth2-server/README.md | wangxs123/copy | 7c2508576a997d562c8fcbca91268498b660b114 | [
"Apache-2.0"
] | 2 | 2017-12-21T03:10:19.000Z | 2018-06-26T04:20:13.000Z | hsweb-examples/hsweb-examples-oauth2/hsweb-examples-oauth2-server/README.md | wangxs123/copy | 7c2508576a997d562c8fcbca91268498b660b114 | [
"Apache-2.0"
] | null | null | null | hsweb-examples/hsweb-examples-oauth2/hsweb-examples-oauth2-server/README.md | wangxs123/copy | 7c2508576a997d562c8fcbca91268498b660b114 | [
"Apache-2.0"
] | 2 | 2018-12-01T02:29:46.000Z | 2022-02-14T06:48:10.000Z | # hsweb OAuth2.0 服务端演示
1. 运行 `OAuth2ServerApplication.main` 启动项目
2. 试试运行[客户端](../hsweb-examples-oauth2-client) | 27.75 | 45 | 0.756757 | yue_Hant | 0.380476 |
6f8dbad8814d614566b31f1675463c13292f539c | 3,649 | md | Markdown | about.md | carolin-m/carolin-m.github.io | 260df684544a3c2527c453c0b1bf144a9d03c976 | [
"CC0-1.0"
] | null | null | null | about.md | carolin-m/carolin-m.github.io | 260df684544a3c2527c453c0b1bf144a9d03c976 | [
"CC0-1.0"
] | null | null | null | about.md | carolin-m/carolin-m.github.io | 260df684544a3c2527c453c0b1bf144a9d03c976 | [
"CC0-1.0"
] | null | null | null | ---
layout: page
title: About Me
tagline:
permalink: /about.html
ref: about
order: 0
---
## Education and Scientific Career <br>
______________
| since 2022 | [**Postdoc**]({{ '/now.html' | absolute_url }}), University of Luxemburg, Luxemburg <br /> Workgroup: [**Prof. A. Tkatchenko**](https://wwwen.uni.lu/recherche/fstm/dphyms/people/alexandre_tkatchenko) |
| 2021-2022 | [**Postdoc**]({{ '/now.html' | absolute_url }}), Friedrich Schiller University Jena, Germany <br /> Workgroup: [**Prof. B. Dietzek-Ivanšić**](https://www.ipc.uni-jena.de/en/AGDietzek) |
| 2018-2021 | **Dissertation (Dr. rer. nat)**, Friedrich Schiller University Jena, Germany <br /> Scholarship: Kekulé Fellowship (*Fonds der Chemischen Industrie*) <br /> Thesis Title: *Towards Operando Spectroscopy of Supramolecular Photocatalysts – A Case Study on Ru-dppz-derived Systems* <br /> Supervisor: [**Prof. B. Dietzek-Ivanšić**](https://www.ipc.uni-jena.de/en/AGDietzek) <br /> Referees: [**Prof. B. Dietzek-Ivanšić**](https://www.ipc.uni-jena.de/en/AGDietzek), [**Prof. S. Gräfe**](https://www.ipc.uni-jena.de/Theochem), and [**Prof. T. Keyes**](https://sites.google.com/dcu.ie/keyes-research-group/home) <br /> Grade: *summa cum laude* |
| 2020 | **Research Stay**, Lund University, Sweden <br /> Workgroup: [**Prof. A. Yartsev**](https://portal.research.lu.se/en/persons/arkady-yartsev) <br /> Purpose: Ultrafast Transient Absorption Spectroscopy in Flow Cells to study the Reaction Dynamics of photoexcited Ru(II) complexes with Triethylamine (2 weeks) |
| 2016-2018 | **M. Sc. in Chemistry** Friedrich Schiller University Jena, Germany <br /> Thesis Title: *Photoactive Proton Pumping at a Microcavity Supported Lipid Bilayer* <br /> Supervisors: [**Prof. T. Keyes**](https://sites.google.com/dcu.ie/keyes-research-group/home) and [**Prof. B. Dietzek-Ivanšić**](https://www.ipc.uni-jena.de/en/AGDietzek) (formal) <br /> Grade: 1.1 (Thesis: 1.0) |
| 2018 | **Research Stay**, Dublin City University, Ireland <br /> Workgroup: [**Prof. T. Keyes**](https://sites.google.com/dcu.ie/keyes-research-group/home) <br /> Purpose: Master Thesis (6 months) <br /> Scholarship: PROMOS DAAD |
| 2013-2016 | **B. Sc. in Chemistry**, Friedrich Schiller University Jena, Germany <br /> Thesis Title: *Spectroscopic Investigations of Electronic States of Copper(I)–*4H*-Imidazolate Coordination Compounds* <br /> Supervisors: **Dr. Martin Schulz** and [**Prof. B. Dietzek-Ivanšić**](https://www.ipc.uni-jena.de/en/AGDietzek) (formal) <br /> Grade: 1.3 (Thesis: 1.0) |
## Fellowships <br>
________________
| since 06/2022 | Feodor Lynen Research Fellowship (*Alexander von Humboldt Foundation*) |
| 05/2019-02/2021 | FCI Kekulé PhD fellowship (*Fonds der Chemischen Industrie*) |
| 02/2018-09/2018 | PROMOS DAAD scholarship (research stay at the Dublin City University) |
| 10/2017-09/2018 | *Deutschlandstipendium* (Friedrich Schiller University Jena) |
## Services to Home Institution and Scientific Community <br>
________________
| 2019-2021 | Co-organizer of the 1st and 2nd [CataLight Young Scientist Symposium](https://cyss-catalight.de/event/6/) |
| 10/2019-09/2021 | Doctoral Student Representative ([DR.FSU](https://www.dr.uni-jena.de/)) at the Friedrich Schiller University Jena, Germany |
| 07/2020-09/2021 | Doctoral Student Representative in the Vice Presidium for Young Scientists, Friedrich Schiller University Jena, Germany |
| 10/2018-03/2021 | Doctoral Student Representative in the integrated research training group of the collaborative research center [CataLight (SFB-TRR 234)](https://www.catalight.eu/) |
___________
[Back]({{ '/' | absolute_url }})
| 89 | 653 | 0.723486 | yue_Hant | 0.239582 |
6f8ea595500d9b921b0bed09d844044565d22b4b | 4,063 | md | Markdown | docs/pt-BR/advanced-config/README.md | ocdy1001/starship | 77bd80839ef6ac94cbf8e95095c566afd4f9b499 | [
"ISC"
] | 3 | 2021-03-09T19:25:24.000Z | 2021-03-09T20:04:49.000Z | docs/pt-BR/advanced-config/README.md | ocdy1001/starship | 77bd80839ef6ac94cbf8e95095c566afd4f9b499 | [
"ISC"
] | 5 | 2021-09-20T22:29:50.000Z | 2022-02-27T14:38:33.000Z | docs/pt-BR/advanced-config/README.md | ocdy1001/starship | 77bd80839ef6ac94cbf8e95095c566afd4f9b499 | [
"ISC"
] | 1 | 2021-06-20T11:25:23.000Z | 2021-06-20T11:25:23.000Z | # Advanced Configuration
Ainda que Starship se`ja um shell versátil, às vezes você precisará fazer algumas outras coisas além de editar o arquivo <code>starship.toml`. Esta página detalha algumas das configurações mais avançadas usadas em starship.
::: warning
As configurações nesta seção estão sujeitas a alterações em futuras versões do Starship.
:::
## Comandos personalizados de pre-prompt e pre-execution no Bash
O Bash não possui uma estrutura formal para os hooks preexec/precmd como a maioria dos outros shells. Por esse motivo, é difícil fornecer hooks totalmente customizáveis no `bash`. No entanto, Starship te oferece uma capacidade limitada de inserir suas próprias funções na processo de prompt-rendering:
- To run a custom function right before the prompt is drawn, define a new function and then assign its name to `starship_precmd_user_func`. For example, to draw a rocket before the prompt, you would do
```bash
function blastoff(){
echo "🚀"
}
starship_precmd_user_func="blastoff"
```
- To run a custom function right before a command runs, you can use the [`DEBUG` trap mechanism](https://jichu4n.com/posts/debug-trap-and-prompt_command-in-bash/). However, you **must** trap the DEBUG signal *before* initializing Starship! Starship can preserve the value of the DEBUG trap, but if the trap is overwritten after starship starts up, some functionality will break.
```bash
function blastoff(){
echo "🚀"
}
trap blastoff DEBUG # Trap DEBUG *before* running starship
eval $(starship init bash)
```
## Altera o título da janela
Some shell prompts will automatically change the window title for you (e.g. to reflect your working directory). Fish faz isso por padrão. Starship does not do this, but it's fairly straightforward to add this functionality to `bash` or `zsh`.
First, define a window title change function (identical in bash and zsh):
```bash
function set_win_title(){
echo -ne "\033]0; YOUR_WINDOW_TITLE_HERE \007"
}
```
You can use variables to customize this title (`$USER`, `$HOSTNAME`, and `$PWD` are popular choices).
In `bash`, set this function to be the precmd starship function:
```bash
starship_precmd_user_func="set_win_title"
```
In `zsh`, add this to the `precmd_functions` array:
```bash
precmd_functions+=(set_win_title)
```
If you like the result, add these lines to your shell configuration file (`~/.bashrc` or `~/.zshrc`) to make it permanent.
For example, if you want to display your current directory in your terminal tab title, add the following snippet to your `~/.bashrc` or `~/.zshrc`:
```bash
function set_win_title(){
echo -ne "\033]0; $(basename $PWD) \007"
}
starship_precmd_user_func="set_win_title"
```
## Estilo dos textos
Style strings are a list of words, separated by whitespace. The words are not case sensitive (i.e. `bold` and `BoLd` are considered the same string). Cada palavra pode ser uma das seguintes:
- `bold`
- `underline`
- `dimmed`
- `bg:<color>`
- `fg:<color>`
- `<color>`
- `none`
where `<color>` is a color specifier (discussed below). `fg:<color>` and `<color>` currently do the same thing , though this may change in the future. The order of words in the string does not matter.
The `none` token overrides all other tokens in a string, so that e.g. `fg:red none fg:blue` will still create a string with no styling. It may become an error to use `none` in conjunction with other tokens in the future.
A color specifier can be one of the following:
- One of the standard terminal colors: `black`, `red`, `green`, `blue`, `yellow`, `purple`, `cyan`, `white`. You can optionally prefix these with `bright-` to get the bright version (e.g. `bright-white`).
- A `#` followed by a six-digit hexadecimal number. This specifies an [RGB color hex code](https://www.w3schools.com/colors/colors_hexadecimal.asp).
- Um número entre 0-255. Este especifica um [Código de Cor ANSI 8 bits](https://i.stack.imgur.com/KTSQa.png).
If multiple colors are specified for foreground/background, the last one in the string will take priority.
| 43.223404 | 378 | 0.743785 | eng_Latn | 0.908261 |
6f8f3d85db47e9aaa145012c710e56373f902217 | 1,326 | md | Markdown | translations/pl/docs/Vanilla/Events/Events/PlayerAnvilRepair.md | kindlich/CraftTweaker-Documentation | 3579ab48d05731d9b9175fe65fb6d3c856f60a9b | [
"MIT"
] | 1 | 2017-10-21T12:33:53.000Z | 2017-10-21T12:33:53.000Z | translations/pl/docs/Vanilla/Events/Events/PlayerAnvilRepair.md | kindlich/CraftTweaker-Documentation | 3579ab48d05731d9b9175fe65fb6d3c856f60a9b | [
"MIT"
] | 1 | 2017-07-16T09:55:12.000Z | 2017-07-16T11:37:55.000Z | translations/pl/docs/Vanilla/Events/Events/PlayerAnvilRepair.md | kindlich/CraftTweaker-Documentation | 3579ab48d05731d9b9175fe65fb6d3c856f60a9b | [
"MIT"
] | 2 | 2017-07-16T00:14:53.000Z | 2017-12-31T14:04:05.000Z | # PlayerAnvilRepair
Wydarzenie Gracza AnvilRepair jest strzelane za każdym razem, gdy gracz wytwarza coś w kowadle.
Możesz zmienić szansę na uszkodzenie kowadła.
## Klasa wydarzenia
Musisz aktywować wydarzenie w nagłówku funkcji jako klasa:
`crafttweaker.event. layerAnvilRepairEvent`
Możesz oczywiście również [zaimportować](/AdvancedFunctions/Import/) klasę przed i wtedy użyć tej nazwy.
## Rozszerzenia interfejsu zdarzenia
Zdarzenia PlayerAnvilRepair zaimplementują następujące interfejsy i są również w stanie wywołać wszystkie swoje metody/getters/setters:
- [Wydarzenie IPlayer](/Vanilla/Events/Events/IPlayerEvent/)
## ZenGetters
Z wydarzenia można uzyskać następujące informacje:
| ZenGetter | ZenSetter | Typ zwrotu |
| ------------------- | ------------------- | ---------------------------------------- |
| `gracz` | | [IPlayer](/Vanilla/Players/IPlayer/) |
| `itemInput` | | [IItemStack](/Vanilla/Items/IItemStack/) |
| `Składnik produktu` | | [IItemStack](/Vanilla/Items/IItemStack/) |
| `itenResult` | | [IItemStack](/Vanilla/Items/IItemStack/) |
| `szansa na łamanie` | `szansa na łamanie` | zmiennoprzecinkowe | | 47.357143 | 135 | 0.615385 | pol_Latn | 0.999554 |
6f8f669326831bf76c34d576af7fbe69148babb0 | 10,365 | md | Markdown | content/post/2013-12-02-connecting-bare-metal-workloads-using-gre-tunnels-and-ovs.md | scottslowe/weblog | dcf9c6a5d0a8d9b7fb507ce7b6fcee1b11eb065f | [
"MIT"
] | 9 | 2018-12-19T09:50:28.000Z | 2022-03-31T00:40:39.000Z | content/post/2013-12-02-connecting-bare-metal-workloads-using-gre-tunnels-and-ovs.md | scottslowe/weblog | dcf9c6a5d0a8d9b7fb507ce7b6fcee1b11eb065f | [
"MIT"
] | 2 | 2018-04-23T13:45:38.000Z | 2020-01-24T23:04:16.000Z | content/post/2013-12-02-connecting-bare-metal-workloads-using-gre-tunnels-and-ovs.md | scottslowe/weblog | dcf9c6a5d0a8d9b7fb507ce7b6fcee1b11eb065f | [
"MIT"
] | 9 | 2018-04-22T05:43:46.000Z | 2022-03-02T20:28:45.000Z | ---
author: slowe
categories: Tutorial
comments: true
date: 2013-12-02T09:00:00Z
slug: connecting-bare-metal-workloads-using-gre-tunnels-and-ovs
tags:
- GRE
- KVM
- Linux
- LXC
- Networking
- OVS
- Virtualization
title: Connecting Bare Metal Workloads Using GRE Tunnels and OVS
url: /2013/12/02/connecting-bare-metal-workloads-using-gre-tunnels-and-ovs/
wordpress_id: 3340
---
In this post, I'll discuss how you could use [Open vSwitch (OVS)](http://openvswitch.org/) and GRE tunnels to connect bare metal workloads. While OVS is typically used in conjunction with a hypervisor such as KVM or Xen, you're certainly not restricted to _only_ using it on hypervisors. Similarly, while GRE tunnels are commonly used to connect VMs or containers, you're definitely not restricted from using them with bare metal workloads as well. In this post, I'll explore how you would go about connecting bare metal workloads over GRE tunnels managed by OVS.
This post, by the way, was sparked in part by a comment on my article on [using GRE tunnels with OVS][1], in which the reader asked: "Is there a way to configure bare Linux (Ubuntu)with OVS installed...to serve as a tunnel endpoint?" Hopefully this post helps answer that question. (By the way, the key to understanding how this works is in understanding OVS traffic patterns. If you haven't yet read my post on [examining OVS traffic patterns][2], I highly recommend you go have a look right now. Seriously.)
Once you have OVS installed (maybe [this is helpful][3]?), then you need to create the right OVS configuration. That configuration can be described, at a high level, like this:
* Assign an IP address to a physical interface. This interface will be considered the "tunnel endpoint," and therefore should have an IP address that is correct for use on the transport network.
* Create an OVS bridge that has no physical interfaces assigned.
* Create an OVS internal interface on this OVS bridge, and assign it an IP address for use inside the GRE tunnel(s). This interface will be considered the primary interface for the OS instance.
* Create the GRE tunnel for connecting to other tunnel endpoints.
Each of these areas is described in a bit more detail in the following sections.
## Setting Up the Transport Interface
When setting up the physical interface---which I'll refer to as the transport interface moving forward, since it is responsible for transporting the GRE tunnel across to the other endpoints---you'll just need to use an IP address and routing entries that enable it to communicate with other tunnel endpoints.
Let's assume that we are going to have tunnel endpoints on the 192.168.1.0/24 subnet. On the bare metal OS instance, you'd configure a physical interface (I'll assume `eth0`, but it could be any physical interface) to have an IP address on the 192.168.1.0/24 subnet. You could do this automatically via DHCP or manually; the choice is yours. Other than ensuring that the bare metal OS instance can communicate with other tunnel endpoints, _no additional configuration is required._ (I'm using "required" as in "necessary to make it work." You may want to increase the MTU on your physical interface and network equipment in order to accommodate the GRE headers in order to optimize performance, but that isn't required in order to make it work.)
Once you have the transport interface configured and operational, you can move on to configuring OVS.
## Configuring OVS
If you've been following along at home with all of my OVS-related posts (you can browse all posts using [the OVS tag](/tags/ovs/), you can probably guess what this will look like (hint: it will look a little bit like the configuration I described in my post on running [host management through OVS][4]). Nevertheless, I'll walk through the configuration for the benefit of those who are new to OVS.
First, you'll need to create an OVS bridge that has no physical interfaces---the so-called "isolated bridge" because it is isolated from the physical network. You can call this bridge whatever you want. I'll use the name `br-int` (the "integration bridge") because it's commonly used in other environments like OpenStack and NVP/NSX.
To create the isolated bridge, use `ovs-vsctl`:
ovs-vsctl add-br br-int
Naturally, you would substitute whatever name you'd like to use in the above command. Once you've created the bridge, then add an OVS internal interface; this internal interface will become the bare metal workload's primary network interface:
ovs-vsctl add-port br-int mgmt0 -- set interface mgmt0 type=internal
You can use a name other than `mgmt0` if you so desire. Next, configure this new OVS internal interface at the operating system level, assigning it an IP address. This IP address should be taken from a subnet "inside" the GRE tunnel, because it is only via the GRE tunnel that you'll want the workload to communicate.
The following commands will take care of this part for you:
ip addr add 10.10.10.30/24 dev mgmt0
ip link set mgmt0 up
The process of ensuring that the `mgmt0` interface comes up automatically when the system boots is left as an exercise for the reader (hint: use `/etc/network/interfaces`).
At this point, the bare metal OS instance will have **two** network interfaces:
* A physical interface (we're assuming `eth0`) that is configured for use on the transport network. In other words, it has an IP address and routes necessary for communication with other tunnel endpoints.
* An OVS internal interface (I'm using `mgmt0`) that is configured for use inside the GRE tunnel. In other words, it has an IP address and routes necessary to communicate with other workloads (bare metal, containers, VMs) via the OVS-hosted GRE tunnel(s).
Because the bare metal OS instance sees two interfaces (and therefore has visibility into the routes both "inside" and "outside" the tunnel), you may need to apply some policy routing configuration. See [my introductory post on Linux policy routing][5] if you need more information.
The final step is establishing the GRE tunnel.
## Establishing the GRE Tunnel
The commands for establishing the GRE tunnel have been described numerous times, but once again I'll walk through the process just for the sake of completeness. I'm assuming that you've already completed the steps in the previous section, and that you are using an OVS bridge named `br-int`.
First, add the GRE port to the bridge:
ovs-vsctl add-port br-int gre0
Next, configure the GRE interface on that port:
ovs-vsctl set interface gre0 type=gre options:remote_ip=<IP address of remote tunnel endpoint>
Let's say that you've assigned 192.168.1.10 to the transport interface on this system (the bare metal OS instance), and that the remote tunnel endpoint (which could be a host with multiple containers, or a hypervisor running VMs) has an IP address of 192.168.1.15. On the bare metal system, you'd configure the GRE interface like this:
ovs-vsctl set interface gre0 type=gre options:remote_ip=192.168.1.15
On the remote tunnel endpoint, you'd configure the GRE interface like this:
ovs-vsctl set interface gre0 type=gre options:remote_ip=192.168.1.10
In other words, each GRE interface points to the transport IP address on the _opposite_ end of the tunnel.
Once the configuration on both ends is done, then you should be able to go into the bare metal OS instance and ping an IP address inside the GRE tunnel. For example, I used this configuration to connect a bare metal Ubuntu 12.04 instance, a container running on an Ubuntu host, and a KVM VM running on an Ubuntu host (I had a full mesh topology with STP enabled, as described here). I was able to successfully ping between the bare metal OS instance, the container, and the VM, all inside the GRE tunnel.
## Summary, Caveats, and Other Thoughts
While this configuration is interesting as a "proof of concept" that OVS and GRE tunnels can be used to connect bare metal OS instances and workloads, there are a number of considerations and/or caveats that you'll want to think about before trying something like this in a production environment:
* The bare metal OS instance has visibility both "inside" and "outside" the tunnel, so there isn't an easy way to prevent the bare metal OS instance from communicating outside the tunnel to other entities. This might be OK---or it might not. It all depends on your requirements, and what you are trying to achieve. (In theory, you _might_ be able to provide some isolation using network namespaces, but I haven't tested this at all.)
* If you want to create a full mesh topology of GRE tunnels, you'll need to enable STP on OVS.
* There's nothing preventing you from attaching an OpenFlow controller to the OVS instances (including the OVS instance on the bare metal OS) and pushing flow rules down. This would eliminate the need for STP, since OVS won't be in MAC learning mode. This means you could easily incorporate bare metal OS instances into a network virtualization-type environment. However
* There's no easy way to provide a separation of OVS and the bare metal OS instance. This means that users who are legitimately allowed to make administrative changes to the bare metal OS instance could also make changes to OVS, which could easily "break" the configuration and cause problems. My personal view is that this is why you rarely see this sort of OVS configuration used in conjunction with bare metal workloads.
I still see value in explaining how this works because it provides yet another example of how to configure OVS and how to use OVS to help provide advanced networking capabilities in a variety of environments and situations.
If you have any questions, I encourage you to add them in the comments below. Likewise, if I have overlooked something, made any mistakes, or if I'm just plain wrong, please speak up below (courteously, of course!). I welcome all useful/pertinent feedback and interaction.
[1]: {{< relref "2013-05-07-using-gre-tunnels-with-open-vswitch.md" >}}
[2]: {{< relref "2013-05-15-examining-open-vswitch-traffic-patterns.md" >}}
[3]: {{< relref "2013-10-14-installing-open-vswitch-on-ubuntu-with-puppet.md" >}}
[4]: {{< relref "2012-10-30-running-host-management-on-open-vswitch.md" >}}
[5]: {{< relref "2013-05-29-a-quick-introduction-to-linux-policy-routing.md" >}}
| 84.959016 | 745 | 0.780608 | eng_Latn | 0.999219 |
6f8fed5900e6db409c05c216005153793f869adb | 333 | md | Markdown | lib/vendor-direct-fulfillment-shipping-api-model/docs/CustomerInvoice.md | blinken/amz_sp_api | 65e7a1cc89b4b0b8f73c42354d2502b4993b7d26 | [
"Apache-2.0"
] | null | null | null | lib/vendor-direct-fulfillment-shipping-api-model/docs/CustomerInvoice.md | blinken/amz_sp_api | 65e7a1cc89b4b0b8f73c42354d2502b4993b7d26 | [
"Apache-2.0"
] | null | null | null | lib/vendor-direct-fulfillment-shipping-api-model/docs/CustomerInvoice.md | blinken/amz_sp_api | 65e7a1cc89b4b0b8f73c42354d2502b4993b7d26 | [
"Apache-2.0"
] | null | null | null | # AmzSpApi::VendorDirectFulfillmentShippingApiModel::CustomerInvoice
## Properties
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**purchase_order_number** | **String** | The purchase order number for this order. |
**content** | **String** | The Base64encoded customer invoice. |
| 33.3 | 85 | 0.603604 | eng_Latn | 0.503321 |
6f90cf864b0b3abfec806df7e535264d3929621a | 545 | md | Markdown | src/posts/first-blogpost.md | Ta-Mo/gatsby-netlify | cc5239dd623ee7f2b0777897a07109f70a797ce8 | [
"RSA-MD"
] | null | null | null | src/posts/first-blogpost.md | Ta-Mo/gatsby-netlify | cc5239dd623ee7f2b0777897a07109f70a797ce8 | [
"RSA-MD"
] | null | null | null | src/posts/first-blogpost.md | Ta-Mo/gatsby-netlify | cc5239dd623ee7f2b0777897a07109f70a797ce8 | [
"RSA-MD"
] | null | null | null | ---
title: "My First Blog Post"
date: "2020-09-30"
keywords: "firsKeyword, secondKeyword"
image: "https://i.imgur.com/NaqsHHm.jpg"
---
His exquisite sincerity education shameless ten earnestly breakfast add.
So we me unknown as improve hastily sitting forming.
Especially favourable compliment but thoroughly unreserved saw she themselves.
Sufficient impossible him may ten insensible put continuing.
Oppose exeter income simple few joy cousin but twenty.
Scale began quiet up short wrong in in. Sportsmen shy forfeited engrossed may can. | 41.923077 | 83 | 0.792661 | eng_Latn | 0.986393 |
6f90d26236c45f37d91d88d5bb1b34aa11095dbb | 1,149 | md | Markdown | windows-driver-docs-pr/ifs/irp-mj-lock-control2.md | i35010u/windows-driver-docs.zh-cn | e97bfd9ab066a578d9178313f802653570e21e7d | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-02-04T01:49:58.000Z | 2021-02-04T01:49:58.000Z | windows-driver-docs-pr/ifs/irp-mj-lock-control2.md | i35010u/windows-driver-docs.zh-cn | e97bfd9ab066a578d9178313f802653570e21e7d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | windows-driver-docs-pr/ifs/irp-mj-lock-control2.md | i35010u/windows-driver-docs.zh-cn | e97bfd9ab066a578d9178313f802653570e21e7d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 检查 IRP_MJ_LOCK_CONTROL 操作的 Oplock 状态
description: 检查 IRP_MJ_LOCK_CONTROL 操作的 Oplock 状态
ms.date: 11/25/2019
ms.localizationpriority: medium
ms.openlocfilehash: f65a25744285e50fa83de99017cee6c9cd1e6e28
ms.sourcegitcommit: 418e6617e2a695c9cb4b37b5b60e264760858acd
ms.translationtype: MT
ms.contentlocale: zh-CN
ms.lasthandoff: 12/07/2020
ms.locfileid: "96839923"
---
# <a name="checking-the-oplock-state-of-an-irp_mj_lock_control-operation"></a>检查 IRP_MJ_LOCK_CONTROL 操作的 Oplock 状态
以下 [oplock 中断](./breaking-oplocks.md) 条件适用于给定流上的每个字节范围锁操作。
### <a name="conditions-for-a-level-2-request-type"></a>第2级请求类型的条件
- 始终中断到无。
- 不需要确认;操作会立即继续。
### <a name="conditions-for-a-filter-request-type"></a>筛选器请求类型的条件
- Oplock 不会中断。
- 不需要确认，操作会立即继续。
### <a name="conditions-for-level-1-batch-read-read-handle-read-write-and-read-write-handle-request-types"></a>级别1、批处理、读取、读取句柄、读写和读写句柄请求类型的条件
- 当锁定操作发生在具有 oplock 键的 FILE_OBJECT 上，而该操作与拥有 oplock 的 FILE_OBJECT 的键不同时，中断 IRP_MJ_LOCK_CONTROL。 如果 oplock 中断，则中断到无。
- 确认要求不同如下：
- 读取请求：不需要确认;操作会立即继续。
- Read-Handle 和读写句柄请求：尽管需要确认中断，但操作会立即继续 (例如，无需等待确认) 。
- 级别1、批处理和 Read-Write 请求：必须先收到确认，然后才能继续操作。
| 28.725 | 141 | 0.773716 | yue_Hant | 0.412645 |
6f9123df727927479fe0d7c39bee9874137c816e | 108 | md | Markdown | README.md | Zeeraa/BukkitPlugin-shutdown | b1f5e2fc9444e0db11426b0087870442cf266994 | [
"MIT"
] | null | null | null | README.md | Zeeraa/BukkitPlugin-shutdown | b1f5e2fc9444e0db11426b0087870442cf266994 | [
"MIT"
] | null | null | null | README.md | Zeeraa/BukkitPlugin-shutdown | b1f5e2fc9444e0db11426b0087870442cf266994 | [
"MIT"
] | null | null | null | # BukkitPlugin-shutdown
Bukkit plugin that stops the server when shutdown.txt is found in the plugin folder
| 36 | 83 | 0.824074 | eng_Latn | 0.997377 |
6f9204accfc7985f44a6ca5f097853cc345a6ab9 | 280 | md | Markdown | docs/PULL_REQUEST_TEMPLATE.md | baloise/corellia | 9dfc42ec834c664dd10b95c48e28582768e8f5ac | [
"Apache-2.0"
] | 5 | 2019-07-30T14:42:40.000Z | 2021-06-17T13:03:36.000Z | docs/PULL_REQUEST_TEMPLATE.md | baloise/corellia | 9dfc42ec834c664dd10b95c48e28582768e8f5ac | [
"Apache-2.0"
] | 62 | 2019-03-28T09:58:35.000Z | 2022-03-03T22:19:09.000Z | docs/PULL_REQUEST_TEMPLATE.md | baloise/corellia | 9dfc42ec834c664dd10b95c48e28582768e8f5ac | [
"Apache-2.0"
] | 2 | 2019-06-18T18:25:35.000Z | 2019-10-25T03:59:44.000Z | Fixes #
## Proposed Changes
-
-
## Definition of Done (DoD) - criteria met
- [ ] code compiles and [build is green](https://travis-ci.org/baloise/corellia)
- [ ] documentation is appropriate or has been updated accordingly
- [ ] change is (to be) merged on master branch
| 21.538462 | 81 | 0.689286 | eng_Latn | 0.994854 |
6f931b70d2b179a3add34d5c43ad9d0c0db26d70 | 20,615 | md | Markdown | developer/cmdlet/creating-a-cmdlet-that-modifies-the-system.md | cdhunt/PowerShell-Docs | c6eedd8f856ca0f679171c1762baf1d45d61b4b2 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | developer/cmdlet/creating-a-cmdlet-that-modifies-the-system.md | cdhunt/PowerShell-Docs | c6eedd8f856ca0f679171c1762baf1d45d61b4b2 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | developer/cmdlet/creating-a-cmdlet-that-modifies-the-system.md | cdhunt/PowerShell-Docs | c6eedd8f856ca0f679171c1762baf1d45d61b4b2 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "Creating a Cmdlet that Modifies the System | Microsoft Docs"
ms.custom: ""
ms.date: "09/13/2016"
ms.reviewer: ""
ms.suite: ""
ms.tgt_pltfrm: ""
ms.topic: "article"
helpviewer_keywords:
- "should process [PowerShell Programmer's Guide]"
- "should continue [PowerShell Programmer's Guide]"
- "user feedback [PowerShell Programmer's Guide]"
- "confirm impact [PowerShell Programmer's Guide]"
ms.assetid: 59be4120-1700-4d92-a308-ef4a32ccf11a
caps.latest.revision: 8
---
# Creating a Cmdlet that Modifies the System
Sometimes a cmdlet must modify the running state of the system, not just the state of the Windows PowerShell runtime. In these cases, the cmdlet should allow the user a chance to confirm whether or not to make the change.
To support confirmation a cmdlet must do two things.
- Declare that the cmdlet supports confirmation when you specify the [System.Management.Automation.CmdletAttribute](/dotnet/api/System.Management.Automation.CmdletAttribute) attribute by setting the SupportsShouldProcess keyword to `true`.
- Call [System.Management.Automation.Cmdlet.Shouldprocess*](/dotnet/api/System.Management.Automation.Cmdlet.ShouldProcess) during the execution of the cmdlet (as shown in the following example).
By supporting confirmation, a cmdlet exposes the `Confirm` and `WhatIf` parameters that are provided by Windows PowerShell, and also meets the development guidelines for cmdlets (For more information about cmdlet development guidelines, see [Cmdlet Development Guidelines](./cmdlet-development-guidelines.md).).
## Changing the System
The act of "changing the system" refers to any cmdlet that potentially changes the state of the system outside Windows PowerShell. For example, stopping a process, enabling or disabling a user account, or adding a row to a database table are all changes to the system that should be confirmed. In contrast, operations that read data or establish transient connections do not change the system and generally do not require confirmation. Confirmation is also not needed for actions whose effect is limited to inside the Windows PowerShell runtime, such as `set-variable`. Cmdlets that might or might not make a persistent change should declare `SupportsShouldProcess` and call [System.Management.Automation.Cmdlet.Shouldprocess*](/dotnet/api/System.Management.Automation.Cmdlet.ShouldProcess) only if they are about to make a persistent change.
> [!NOTE]
> ShouldProcess confirmation applies only to cmdlets. If a command or script modifies the running state of a system by directly calling .NET methods or properties, or by calling applications outside of Windows PowerShell, this form of confirmation will not be available.
## The StopProc Cmdlet
This topic describes a Stop-Proc cmdlet that attempts to stop processes that are retrieved using the Get-Proc cmdlet (described in [Creating Your First Cmdlet](./creating-a-cmdlet-without-parameters.md)).
Topics in this section include the following:
- [Defining the Cmdlet](#Defining-the-Cmdlet)
- [Defining Parameters for System Modification](#Defining-Parameters-for-System-Modification)
- [Overriding an Input Processing Method](#Overriding-an-Input-Processing-Method)
- [Calling the ShouldProcess Method](#Calling-the-ShouldProcess-Method)
- [Calling the ShouldContinue Method](#Calling-the-ShouldContinue-Method)
- [Stopping Input Processing](#Stopping-Input-Processing)
- [Code Sample](#Code-Sample)
- [Defining Object Types and Formatting](#Defining-Object-Types-and-Formatting)
- [Building the Cmdlet](#Building-the-Cmdlet)
- [Testing the Cmdlet](#Testing-the-Cmdlet)
## Defining the Cmdlet
The first step in cmdlet creation is always naming the cmdlet and declaring the .NET class that implements the cmdlet. Because you are writing a cmdlet to change the system, it should be named accordingly. This cmdlet stops system processes, so the verb name chosen here is "Stop", defined by the [System.Management.Automation.Verbslifecycle](/dotnet/api/System.Management.Automation.VerbsLifeCycle) class, with the noun "Proc" to indicate that the cmdlet stops processes. For more information about approved cmdlet verbs, see [Cmdlet Verb Names](./approved-verbs-for-windows-powershell-commands.md).
The following is the class definition for this Stop-Proc cmdlet.
```csharp
[Cmdlet(VerbsLifecycle.Stop, "Proc",
SupportsShouldProcess = true)]
public class StopProcCommand : Cmdlet
```
Be aware that in the [System.Management.Automation.CmdletAttribute](/dotnet/api/System.Management.Automation.CmdletAttribute) declaration, the `SupportsShouldProcess` attribute keyword is set to `true` to enable the cmdlet to make calls to [System.Management.Automation.Cmdlet.Shouldprocess*](/dotnet/api/System.Management.Automation.Cmdlet.ShouldProcess) and [System.Management.Automation.Cmdlet.Shouldcontinue*](/dotnet/api/System.Management.Automation.Cmdlet.ShouldContinue). Without this keyword set, the `Confirm` and `WhatIf` parameters will not be available to the user.
### Extremely Destructive Actions
Some operations are extremely destructive, such as reformatting an active hard disk partition. In these cases, the cmdlet should set `ConfirmImpact` = `ConfirmImpact.High` when declaring the [System.Management.Automation.CmdletAttribute](/dotnet/api/System.Management.Automation.CmdletAttribute) attribute. This setting forces the cmdlet to request user confirmation even when the user has not specified the `Confirm` parameter. However, cmdlet developers should avoid overusing `ConfirmImpact` for operations that are just potentially destructive, such as deleting a user account. Remember that if `ConfirmImpact` is set to [System.Management.Automation.Confirmimpact.High](/dotnet/api/System.Management.Automation.ConfirmImpact.High).
Similarly, some operations are unlikely to be destructive, although they do in theory modify the running state of a system outside Windows PowerShell. Such cmdlets can set `ConfirmImpact` to [System.Management.Automation.Confirmimpact.Low](/dotnet/api/system.management.automation.confirmimpact?view=powershellsdk-1.1.0). This will bypass confirmation requests where the user has asked to confirm only medium-impact and high-impact operations.
## Defining Parameters for System Modification
This section describes how to define the cmdlet parameters, including those that are needed to support system modification. See [Adding Parameters that Process CommandLine Input](./adding-parameters-that-process-command-line-input.md) if you need general information about defining parameters.
The Stop-Proc cmdlet defines three parameters: `Name`, `Force`, and `PassThru`.
The `Name` parameter corresponds to the `Name` property of the process input object. Be aware that the `Name` parameter in this sample is mandatory, as the cmdlet will fail if it does not have a named process to stop.
The `Force` parameter allows the user to override calls to [System.Management.Automation.Cmdlet.Shouldcontinue*](/dotnet/api/System.Management.Automation.Cmdlet.ShouldContinue). In fact, any cmdlet that calls [System.Management.Automation.Cmdlet.Shouldcontinue*](/dotnet/api/System.Management.Automation.Cmdlet.ShouldContinue) should have a `Force` parameter so that when `Force` is specified, the cmdlet skips the call to [System.Management.Automation.Cmdlet.Shouldcontinue*](/dotnet/api/System.Management.Automation.Cmdlet.ShouldContinue) and proceeds with the operation. Be aware that this does not affect calls to [System.Management.Automation.Cmdlet.Shouldprocess*](/dotnet/api/System.Management.Automation.Cmdlet.ShouldProcess).
The `PassThru` parameter allows the user to indicate whether the cmdlet passes an output object through the pipeline, in this case, after a process is stopped. Be aware that this parameter is tied to the cmdlet itself instead of to a property of the input object.
Here is the parameter declaration for the Stop-Proc cmdlet.
```csharp
[Parameter(
Position = 0,
Mandatory = true,
ValueFromPipeline = true,
ValueFromPipelineByPropertyName = true
)]
public string[] Name
{
get { return processNames; }
set { processNames = value; }
}
private string[] processNames;
/// <summary>
/// Specify the Force parameter that allows the user to override
/// the ShouldContinue call to force the stop operation. This
/// parameter should always be used with caution.
/// </summary>
[Parameter]
public SwitchParameter Force
{
get { return force; }
set { force = value; }
}
private bool force;
/// <summary>
/// Specify the PassThru parameter that allows the user to specify
/// that the cmdlet should pass the process object down the pipeline
/// after the process has been stopped.
/// </summary>
[Parameter]
public SwitchParameter PassThru
{
get { return passThru; }
set { passThru = value; }
}
private bool passThru;
```
## Overriding an Input Processing Method
The cmdlet must override an input processing method. The following code illustrates the [System.Management.Automation.Cmdlet.Processrecord*](/dotnet/api/System.Management.Automation.Cmdlet.ProcessRecord) override used in the sample Stop-Proc cmdlet. For each requested process name, this method ensures that the process is not a special process, tries to stop the process, and then sends an output object if the `PassThru` parameter is specified.
```csharp
protected override void ProcessRecord()
{
foreach (string name in processNames)
{
// For every process name passed to the cmdlet, get the associated
// process(es). For failures, write a non-terminating error
Process[] processes;
try
{
processes = Process.GetProcessesByName(name);
}
catch (InvalidOperationException ioe)
{
WriteError(new ErrorRecord(ioe,"Unable to access the target process by name",
ErrorCategory.InvalidOperation, name));
continue;
}
// Try to stop the process(es) that have been retrieved for a name
foreach (Process process in processes)
{
string processName;
try
{
processName = process.ProcessName;
}
catch (Win32Exception e)
{
WriteError(new ErrorRecord(e, "ProcessNameNotFound",
ErrorCategory.ReadError, process));
continue;
}
// Call Should Process to confirm the operation first.
// This is always false if WhatIf is set.
if (!ShouldProcess(string.Format("{0} ({1})", processName,
process.Id)))
{
continue;
}
// Call ShouldContinue to make sure the user really does want
// to stop a critical process that could possibly stop the computer.
bool criticalProcess =
criticalProcessNames.Contains(processName.ToLower());
if (criticalProcess &&!force)
{
string message = String.Format
("The process \"{0}\" is a critical process and should not be stopped. Are you sure you wish to stop the process?",
processName);
// It is possible that ProcessRecord is called multiple times
// when the Name parameter reveives objects as input from the
// pipeline. So to retain YesToAll and NoToAll input that the
// user may enter across mutilple calls to ProcessRecord, this
// information is stored as private members of the cmdlet.
if (!ShouldContinue(message, "Warning!",
ref yesToAll,
ref noToAll))
{
continue;
}
} // if (cricicalProcess...
// Stop the named process.
try
{
process.Kill();
}
catch (Exception e)
{
if ((e is Win32Exception) || (e is SystemException) ||
(e is InvalidOperationException))
{
// This process could not be stopped so write
// a non-terminating error.
string message = String.Format("{0} {1} {2}",
"Could not stop process \"", processName,
"\".");
WriteError(new ErrorRecord(e, message,
ErrorCategory.CloseError, process));
continue;
} // if ((e is...
else throw;
} // catch
// If the PassThru parameter argument is
// True, pass the terminated process on.
if (passThru)
{
WriteObject(process);
}
} // foreach (Process...
} // foreach (string...
} // ProcessRecord
```
## Calling the ShouldProcess Method
The input processing method of your cmdlet should call the [System.Management.Automation.Cmdlet.Shouldprocess*](/dotnet/api/System.Management.Automation.Cmdlet.ShouldProcess) method to confirm execution of an operation before a change (for example, deleting files) is made to the running state of the system. This allows the Windows PowerShell runtime to supply the correct "WhatIf" and "Confirm" behavior within the shell.
> [!NOTE]
> If a cmdlet states that it supports should process and fails to make the [System.Management.Automation.Cmdlet.Shouldprocess*](/dotnet/api/System.Management.Automation.Cmdlet.ShouldProcess) call, the user might modify the system unexpectedly.
The call to [System.Management.Automation.Cmdlet.Shouldprocess*](/dotnet/api/System.Management.Automation.Cmdlet.ShouldProcess) sends the name of the resource to be changed to the user, with the Windows PowerShell runtime taking into account any command-line settings or preference variables in determining what should be displayed to the user.
The following example shows the call to [System.Management.Automation.Cmdlet.Shouldprocess*](/dotnet/api/System.Management.Automation.Cmdlet.ShouldProcess) from the override of the [System.Management.Automation.Cmdlet.Processrecord*](/dotnet/api/System.Management.Automation.Cmdlet.ProcessRecord) method in the sample Stop-Proc cmdlet.
```csharp
if (!ShouldProcess(string.Format("{0} ({1})", processName,
process.Id)))
{
continue;
}
```
## Calling the ShouldContinue Method
The call to the [System.Management.Automation.Cmdlet.Shouldcontinue*](/dotnet/api/System.Management.Automation.Cmdlet.ShouldContinue) method sends a secondary message to the user. This call is made after the call to [System.Management.Automation.Cmdlet.Shouldprocess*](/dotnet/api/System.Management.Automation.Cmdlet.ShouldProcess) returns `true` and if the `Force` parameter was not set to `true`. The user can then provide feedback to say whether the operation should be continued. Your cmdlet calls [System.Management.Automation.Cmdlet.Shouldcontinue*](/dotnet/api/System.Management.Automation.Cmdlet.ShouldContinue) as an additional check for potentially dangerous system modifications or when you want to provide yes-to-all and no-to-all options to the user.
The following example shows the call to [System.Management.Automation.Cmdlet.Shouldcontinue*](/dotnet/api/System.Management.Automation.Cmdlet.ShouldContinue) from the override of the [System.Management.Automation.Cmdlet.Processrecord*](/dotnet/api/System.Management.Automation.Cmdlet.ProcessRecord) method in the sample Stop-Proc cmdlet.
```csharp
if (criticalProcess &&!force)
{
string message = String.Format
("The process \"{0}\" is a critical process and should not be stopped. Are you sure you wish to stop the process?",
processName);
// It is possible that ProcessRecord is called multiple times
// when the Name parameter reveives objects as input from the
// pipeline. So to retain YesToAll and NoToAll input that the
// user may enter across mutilple calls to ProcessRecord, this
// information is stored as private members of the cmdlet.
if (!ShouldContinue(message, "Warning!",
ref yesToAll,
ref noToAll))
{
continue;
}
} // if (cricicalProcess...
```
## Stopping Input Processing
The input processing method of a cmdlet that makes system modifications must provide a way of stopping the processing of input. In the case of this Stop-Proc cmdlet, a call is made from the [System.Management.Automation.Cmdlet.Processrecord*](/dotnet/api/System.Management.Automation.Cmdlet.ProcessRecord) method to the [System.Diagnostics.Process.Kill*](/dotnet/api/System.Diagnostics.Process.Kill) method. Because the `PassThru` parameter is set to `true`, [System.Management.Automation.Cmdlet.Processrecord*](/dotnet/api/System.Management.Automation.Cmdlet.ProcessRecord) also calls [System.Management.Automation.Cmdlet.Writeobject*](/dotnet/api/System.Management.Automation.Cmdlet.WriteObject) to send the process object to the pipeline.
## Code Sample
For the complete C# sample code, see [StopProcessSample01 Sample](./stopprocesssample01-sample.md).
## Defining Object Types and Formatting
Windows PowerShell passes information between cmdlets using .Net objects. Consequently, a cmdlet may need to define its own type, or the cmdlet may need to extend an existing type provided by another cmdlet. For more information about defining new types or extending existing types, see [Extending Object Types and Formatting](https://msdn.microsoft.com/en-us/da976d91-a3d6-44e8-affa-466b1e2bd351).
## Building the Cmdlet
After implementing a cmdlet, it must be registered with Windows PowerShell through a Windows PowerShell snap-in. For more information about registering cmdlets, see [How to Register Cmdlets, Providers, and Host Applications](https://msdn.microsoft.com/en-us/a41e9054-29c8-40ab-bf2b-8ce4e7ec1c8c).
## Testing the Cmdlet
When your cmdlet has been registered with Windows PowerShell, you can test it by running it on the command line. Here are several tests that test the Stop-Proc cmdlet. For more information about using cmdlets from the command line, see the [Getting Started with Windows PowerShell](/powershell/scripting/getting-started/getting-started-with-windows-powershell).
- Start Windows PowerShell and use the Stop-Proc cmdlet to stop processing as shown below. Because the cmdlet specifies the `Name` parameter as mandatory, the cmdlet queries for the parameter.
```powershell
PS> stop-proc
```
The following output appears.
```
Cmdlet stop-proc at command pipeline position 1
Supply values for the following parameters:
Name[0]:
```
- Now let's use the cmdlet to stop the process named "NOTEPAD". The cmdlet asks you to confirm the action.
```powershell
PS> stop-proc -Name notepad
```
The following output appears.
```
Confirm
Are you sure you want to perform this action?
Performing operation "stop-proc" on Target "notepad (4996)".
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"): Y
```
- Use Stop-Proc as shown to stop the critical process named "WINLOGON". You are prompted and warned about performing this action because it will cause the operating system to reboot.
```powershell
PS> stop-proc -Name Winlogon
```
The following output appears.
```output
Confirm
Are you sure you want to perform this action?
Performing operation "stop-proc" on Target "winlogon (656)".
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"): Y
Warning!
The process " winlogon " is a critical process and should not be stopped. Are you sure you wish to stop the process?
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"): N
```
- Let's now try to stop the WINLOGON process without receiving a warning. Be aware that this command entry uses the `Force` parameter to override the warning.
```powershell
PS> stop-proc -Name winlogon -Force
```
The following output appears.
```output
Confirm
Are you sure you want to perform this action?
Performing operation "stop-proc" on Target "winlogon (656)".
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"): N
```
## See Also
[Adding Parameters that Process Command-Line Input](./adding-parameters-that-process-command-line-input.md)
[Extending Object Types and Formatting](https://msdn.microsoft.com/en-us/da976d91-a3d6-44e8-affa-466b1e2bd351)
[How to Register Cmdlets, Providers, and Host Applications](https://msdn.microsoft.com/en-us/a41e9054-29c8-40ab-bf2b-8ce4e7ec1c8c)
[Windows PowerShell SDK](../windows-powershell-reference.md)
[Cmdlet Samples](./cmdlet-samples.md) | 54.39314 | 842 | 0.740141 | eng_Latn | 0.959181 |
6f933cb31862bed45907020c0cff51def9949622 | 43 | md | Markdown | README.md | killvorak2/aula_bootstrap | ec1d84fe6aa1fc3cf2ca91d08c07aef355f0bc09 | [
"MIT"
] | null | null | null | README.md | killvorak2/aula_bootstrap | ec1d84fe6aa1fc3cf2ca91d08c07aef355f0bc09 | [
"MIT"
] | null | null | null | README.md | killvorak2/aula_bootstrap | ec1d84fe6aa1fc3cf2ca91d08c07aef355f0bc09 | [
"MIT"
] | null | null | null | # aula_bootstrap
aula com bootstrap da DIO
| 14.333333 | 25 | 0.813953 | por_Latn | 0.864628 |
6f944b057d03d67fe4c643f57c6131f294287fa6 | 321 | md | Markdown | plugins/scaffolder-actions/scaffolder-backend-module-http-request/CHANGELOG.md | fpernin/roadie-backstage-plugins | cbbed7e1145981718c8eb143ab5fa02f857025a2 | [
"Apache-2.0"
] | null | null | null | plugins/scaffolder-actions/scaffolder-backend-module-http-request/CHANGELOG.md | fpernin/roadie-backstage-plugins | cbbed7e1145981718c8eb143ab5fa02f857025a2 | [
"Apache-2.0"
] | null | null | null | plugins/scaffolder-actions/scaffolder-backend-module-http-request/CHANGELOG.md | fpernin/roadie-backstage-plugins | cbbed7e1145981718c8eb143ab5fa02f857025a2 | [
"Apache-2.0"
] | null | null | null | # @roadiehq/scaffolder-backend-module-http-request
## 2.1.0
### Minor Changes
- ed90f25: Breaking dependency updates for @backstage/core-app-api, @backstage/test-utils, @backstage/core-plugin-api, @backstage/backend-common && @backstage/integration
## 2.0.4
### Patch Changes
- 6923c16: Fix the typo in Readme file
| 22.928571 | 170 | 0.738318 | eng_Latn | 0.33312 |
6f94d0fa175eaab01f518e634d1200d922528a80 | 2,700 | md | Markdown | _posts/2018-12-28-iff-data-architect.md | anniejw6/progressivedatajobs_site | f03b17bddcc6a6408c3e7cde7d06c1060929e2b6 | [
"BSD-3-Clause",
"MIT"
] | 6 | 2017-09-06T20:28:37.000Z | 2021-06-27T01:45:40.000Z | _posts/2018-12-28-iff-data-architect.md | anniejw6/progressivedatajobs_site | f03b17bddcc6a6408c3e7cde7d06c1060929e2b6 | [
"BSD-3-Clause",
"MIT"
] | 10 | 2017-09-05T23:09:07.000Z | 2020-07-26T23:02:03.000Z | _posts/2018-12-28-iff-data-architect.md | anniejw6/progressivedatajobs | f03b17bddcc6a6408c3e7cde7d06c1060929e2b6 | [
"BSD-3-Clause",
"MIT"
] | 2 | 2018-02-16T00:58:04.000Z | 2019-03-31T18:49:33.000Z | ---
layout: single
title: "IFF: Data Architect"
tags:
- data
- datamanagement
- nonprofit
---
IFF improves the world by strengthening nonprofits and the communities they serve. As a mission-driven lender, real estate consultant, and developer, IFF helps communities thrive by creating opportunities for low-income communities and persons with disabilities. Key to our success has been a deep sense of purpose, a broad perspective, and a relentless focus on achieving positive results. Across the Midwest, we help clients from every sector, including human service agencies, health centers, schools, affordable housing developers, and grocery stores. Staff contributes its extensive business experience with an unrivaled connection to the mission of IFF and the nonprofit clients it serves.
IFF is looking for candidates with a commitment to the work it does and can demonstrate their creativity, detail-orientation, diligence, efficiency, enthusiasm, flexibility, organization, thoughtfulness, and sense of humor. Our staff of nearly 100 professionals works from our Chicago headquarters, and we also serve the Midwest from six regional offices: Indianapolis, IN; Detroit, MI; Kansas City, MO; St. Louis, MO; Columbus, OH; and Milwaukee, WI. The job in a nutshell As part of its latest strategic plan, in 2018 IFF has started a massive “renovation” of our data management systems and processes, bringing our data infrastructure into the 21st century and most importantly ensuring that data enables our work in increasingly strategic and efficient ways. As part of this renovation, we seek an experienced data architect who will be IFF’s first dedicated data architect and own the continuous evolution of IFF’s data infrastructure. We prefer for this role to be based in Chicago but are open to other Midwest locations for the right candidate.
Application Instructions: Please submit a cover letter and résumé to careers@iff.org with “Data Architect” in the subject line. The cover letter is very important: we will not review any applications that do not have a cover letter. Use it as an opportunity to introduce yourself to us and explain why you are drawn to this role. And for your résumé, keep in mind that we will be reviewing it against the skills outlined above. In other words, your résumé is the first opportunity you have to show us your technical, project management, critical thinking, and communication chops. IFF values equity, diversity and inclusion as part of its mission to strengthen nonprofits and the communities they serve. IFF is an equal opportunity employer.
See more [here](https://www.iff.org/wp-content/uploads/2018/12/Data-Architect-December-2018.pdf)
| 158.823529 | 1,052 | 0.804444 | eng_Latn | 0.999145 |
6f9527beba2d65364b66d4296022bb17b9dd43f8 | 3,148 | md | Markdown | _posts/2019-03-17-francis-bacon-said.md | kimtoma/kimtoma.github.io | afeee46fae987d8514018ef0053abf3609020d18 | [
"MIT"
] | 1 | 2020-12-12T12:35:58.000Z | 2020-12-12T12:35:58.000Z | _posts/2019-03-17-francis-bacon-said.md | kimtoma/kimtoma.github.io | afeee46fae987d8514018ef0053abf3609020d18 | [
"MIT"
] | null | null | null | _posts/2019-03-17-francis-bacon-said.md | kimtoma/kimtoma.github.io | afeee46fae987d8514018ef0053abf3609020d18 | [
"MIT"
] | null | null | null | ---
layout: post
title: 프랜시스 베이컨 왈
---
### 프랜시스 베이컨이 200년뒤에 UX 디자이너들에게 해주고 싶었던 말
항상 허기진 주말, 점심을 먹기 위해 주차를 하려는데 주차장소가 마땅하지 않아서, 교보문고 건물에 주차하고 점심을 먹었다. 점심을 먹고 나서 주차비 내기 아까워진 마음에 차라리 책을 사고 무료주차를 하자고 교보문고에 들어가서 산 책이 바로 “**철학의 이단자들**”이었다. PPL 아님… ([교보문고 구매](http://www.kyobobook.co.kr/product/detailViewKor.laf?ejkGb=KOR&mallGb=KOR&barcode=9788936476854&orderClick=LEA&Kc=))
아버지인 스티븐 내들러가 글을 쓰고, 아들인 벤 내들러가 그림을 그린 책으로 1700년대의 서양 근대철학에 대해서 간단하게 개념을 설명해주는 만화책이다. 오랜만에 철학을 어렵지 않은 설명과 만화로 재밌게 읽고 있었는데, 영국 경험론의 아버지라는 [**프랜시스 베이컨**](https://ko.wikipedia.org/wiki/프랜시스_베이컨)이 나오는 부분을 보고 충격을 받았다.
어렴풋이 중/고등학교 시절에 “우상 어쩌고저쩌고”를 배운 건 기억이 나는데, 베이컨 선생님께서는 귀납 추론을 방해하는 아래 4가지 우상들을 멀리해야 한다고 말씀하셨다고 한다.
1. **종족의 우상** (착각)
사물을 있는 그대로 보지 못하고 착각을 하는 인간 종족의 경향
2. **동굴의 우상** (독선)
개인의 경험으로 편협하고 비합리적인 판단을 하거나 오류를 범하는 것
3. **시장의 우상** (전문)
언어의 부적절한 사용으로 생기는 혼동, 거짓말이나 전해 들은 말을 진실이라고 믿고 현혹되는 것
4. **극장의 우상** (편견)
저명한 철학자들의 이론을 절대적인 진리로 여기고 비판없이 수용할 때 생기는 해로운 영향
그런데 자세히 보면 베이컨이 주장했던 4가지 우상에 대한 경계는 200년이 지난 지금의 UX 디자이너에게도 모두 경계의 대상으로 적용될 수 있는 것이다.
1. **종족의 우상
**고객 데이터를 단편적으로만 보고, 총체적으로 보지 않고 선입견을 품고 설계하려는 UX 디자이너!
이 메뉴는 사용 빈도수가 적으니 다음 업데이트 때 삭제하자!
\> 쓰기 어려워서 적은 거라면…? 버튼을 쥐콩만하게 만들었다면
2. **동굴의 우상
**개인의 경험으로 오류를 범하거나 비합리적인 판단을 하는 UX 디자이너!
라떼는 말이야~ GA 도 없어서 다 열심히 야근하고 하면서 엑셀로 막 트랙킹하고 그랬단 말이야~
\> 그랬던 적 없음…
3. **시장의 우상
**잘못 전해 들은 정보나 불완전한 데이터에 신념을 가지고 서비스에 바로 적용해 보자며 끔찍한 혼동을 초래하는 UX 디자이너!
카카오랑 네이버도 그렇게 한다던데? 친구네 회사에서는…
\> 실제로 그렇게 안함…
4. **극장의 우상
**해외에서 물 건너온 최신 UX 방법론을 절대진리로 여기고 무비판적으로 수용하는 UX디자이너!
엄… 쓀리컨뷀리 최신 츄뤤드에 따르면 우리의 디좌인 프로쉐스도 워러풜 방식에서 좀 더 애좌일한 방법으로 륀하게 풀어나가야 프롸둭이 잘 나올 수 있을 것 같은데… 왓 두 유 띵?!
\> 알고보면 순수 토종 국내파 디자이너…
이정도면 소름 ㅇㅈ?!
더 소름끼치고 잘 들어맞는 대목은 우상들을 피하고 진리에 쫓기 위해서 거쳐야 할 아래 3단계의 과정에서 드러난다.
https://www.slideshare.net/mariambedraoui/inductive-research
1. 편견없이 가공되지 않은 **자료**를 관찰이나 실험을 통해 **수집**한다.
2. 더 많은 자료가 쌓이면 새로운 연관관계가 드러나면 일반화 시킨 후 **가설**을 세운다.
3. 가설을 바탕으로 새로운 **관찰과 실험**을 거쳐 끌어낸 뒤, 실제 경험한 자료와 비교해 가설을 정당화한다.
어디서 많이 본 프로세스 같지 않나? 극장의 우상을 범하는 느낌이긴 하지만 Data-driven UX 또는 Lean UX 라고 들어보신 분?
[Lean UX Process](https://www.oreilly.com/library/view/ux-for-lean/9781449335007/pr05.html)
다이어그램이 조금 더 이뻐지고, 과정을 가르키는 용어가 다르지만 위 2개의 다이어그램이 말하고자 하는 내용은 동일하다. 0과 1로 이루어진 디지털 세상에서 측정가능한 데이터를 측정하지 않고 느낌적인 느낌으로만 디자인하는 시대는 이제 지난 것이다.
가설을 세우고 빠르게 만들어서 데이터를 수집하고 이를 인간 본연의 오류를 피해서 분석하고 가설을 정당화하는 이 모든 과정이 실리콘밸리를 비롯한 IT 업계 전반에 중요하게 인식되고 있는 Data-driven UX 설계와 일맥상통하는 것 같다.
왜 구글이나 글로벌 IT 업체들이 계속 늘어나는 서버비용에도 불구하고 클라우드 저장공간을 무료로 제공하면서 일반 사용자들의 사진을 무제한으로 올리고, 동영상 포스팅을 계속 올리게 할까? 단순하게 생각해보면 Data 수집으로 얻을 수 있는 이득이 지출되는 서버비용보다 훨씬 더 가치가 있다고 판단되기 때문일 것이다.
저렇게 수집한 빅 데이터를 [BigQuery](https://cloud.google.com/bigquery/what-is-bigquery?hl=ko) 등의 솔루션을 통해 분석하고 머신러닝(또는 딥러닝)을 통해 그동안 보지 못하던 분석과 관점에서도 수치화한 데이터로 보면서 점점 더 의사결정자의 판단을 돕거나 아예 판단까지도 자동화시키는 단계가 올 것이라고 생각한다.
이런 시대에 UX 디자이너는 무엇을 할 수 있을까? 무엇을 해야할까?
------
아! 그래서 프랜시스 베이컨이 UX 디자이너에게 해주고 싶은 말이 뭐였던 거 같냐면…
> ### **(UX 디자이너는 사용자를 데이터를 통해서) "아는 것이 힘이다.**" | 40.358974 | 288 | 0.693139 | kor_Hang | 1.00001 |
6f95cefa9e36727918f47d8bc441e4e2dd6ff23e | 1,240 | md | Markdown | _posts/2021-07-31-noSignin.md | zhangyiming748/index | 887b3593a2ac0e00ef690f4805a5f208d02a7b8a | [
"MIT"
] | null | null | null | _posts/2021-07-31-noSignin.md | zhangyiming748/index | 887b3593a2ac0e00ef690f4805a5f208d02a7b8a | [
"MIT"
] | null | null | null | _posts/2021-07-31-noSignin.md | zhangyiming748/index | 887b3593a2ac0e00ef690f4805a5f208d02a7b8a | [
"MIT"
] | null | null | null | ---
layout: post # 使用的布局(不需要改)
title: 不提交个人信息不让用root?naive # 标题
subtitle: 我是一只被禁足的安小鸟 # 副标题
date: 2021-07-31 00:00:05 GMT+0800 # 时间
author: Zen # 作者
header-img: img/photo/birdAngle.webp # 这篇文章标题背景图片
catalog: False # 是否归档
tags: # 标签
- UOS
---
可能是我用过的linux发行版太少了,同为Debian衍生的翘楚Ubuntu,稳坐公司服务器系统第一把交椅的Redhat都不敢禁root用户,锁sudo,没见过这种操作,用开源系统还强制登录账号,微信一注册一半个人敏感信息就上交了,再打开开发者选项需要注册个人开发者,另一半个人敏感信息又上交了,没有红帽的命得了红帽的病,谁给你们的勇气
<iframe width="560" height="315" src="https://www.youtube.com/embed/vUPH_5qyBwQ" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
# 为暴躁老哥准备的文字版
1. 开机按e进入任意一个启动项的grub编辑界面
2. 如果有类似`ro`字样改成`rw single`
3. 如果有类似`xx=xx`字样改成`init=/bin/bash`,如果没有就自己添加
4. `Ctrl+x`保存退出自动重启进入单用户模式
5. 启用root用户并设置密码
6. 分别编辑`/etc/pam.d/sudo`和`/etc/pam.d/su`
7. 注释掉第一行 `auth requisite deepin_security_verify.so`
8. 输入`visudo`编辑允许sudo列表
9. 按照格式添加自己
```
# User privilege specification
root ALL=(ALL:ALL) ALL
${USER} ALL=(ALL:ALL) ALL
```
----
可以断电重启了
重启后删除`/usr/bin/uos-activator`和`/usr/bin/uos-activator-cmd`
| 35.428571 | 248 | 0.68871 | yue_Hant | 0.455919 |
6f96a3040beaf6352f14784eb3f15a2baa8f7233 | 1,125 | md | Markdown | for.md | nelua-by-example/nelua-by-example.github.io | 4404bce80fa3668e6162cbfc95b78c2ef1b0b90a | [
"MIT"
] | 2 | 2021-08-10T19:40:20.000Z | 2021-08-14T21:26:26.000Z | for.md | nelua-by-example/nelua-by-example.github.io | 4404bce80fa3668e6162cbfc95b78c2ef1b0b90a | [
"MIT"
] | null | null | null | for.md | nelua-by-example/nelua-by-example.github.io | 4404bce80fa3668e6162cbfc95b78c2ef1b0b90a | [
"MIT"
] | null | null | null | # 7 - For Loop
`for` is a smart loop that can be used to iterate over a sequence of items and more.
here is a simple example:
```lua
for i = 1, 5 do
print(i)
end
```
output:
```
1
2
3
4
5
```
if you want to customize the loop, you have some options:
**Exclusive For**
```lua
for i = 0, < 5 do
print(i)
end
```
Stepped For:
```lua
for i = 5, 0, -1 do
print(i) -- output: 5 4 3 2 1 0
end
```
if you confused that's because nelua automatically change condtion by steps. so:
```lua
i = 5, 0 -- or i = 5, 0, +1 means i = 5, i < 0, i = i + 1
i = 5, 0, -1 -- or i = 5, 0, i = i - 1 means i = 5, i > 0, i = i - 1
```
you can also use `continue` and `break` to skip or stop the loop.
```lua
for i = 1, 10 do
if i == 2 then
continue
end
print(i)
if i == 5 then
break
end
end
```
output:
```
1
3
4
5
```
this is a example with `in` keyword:
```lua
require 'iterators'
local a: [4]string = {"a","b","c","d"}
for i, v in ipairs(a) do
print(i, v)
end
```
output:
```
0 a
1 b
2 c
3 d
```
[Prev](repeat.md){: .btn .btn-outline } [Next](switch.md){: .btn .btn-outline } | 15.625 | 84 | 0.554667 | eng_Latn | 0.982999 |
6f96ea2b461869f80aac7119f7d975c2753cf700 | 1,244 | md | Markdown | README.md | skoenen/ci_3.03_data-management | d4a9e0f2690c487efc9c4c7a50722a98389cd7d1 | [
"MIT"
] | null | null | null | README.md | skoenen/ci_3.03_data-management | d4a9e0f2690c487efc9c4c7a50722a98389cd7d1 | [
"MIT"
] | null | null | null | README.md | skoenen/ci_3.03_data-management | d4a9e0f2690c487efc9c4c7a50722a98389cd7d1 | [
"MIT"
] | null | null | null | # CI\_3.03 Data Management
This repository contains the results of Excercises, of the HSRW Course
_CI\_3.03 Data Management_.
## First Excercise (E01)
This Excercise has a general scope to understand how a real world can be
structured.
### Files:
- [E01_Design-Structure.md](E01_Design-Structure.md)
## Second Excercise (E02)
The second Excercise introduces a query language and how to work with it.
It take uses several _XML_ documents to practice on.
### Files:
- [E02_Xpath.md](E02_Xpath.md)
- [E02_XPath/books.xml](E02_XPath/books.xml)
- [E02_XPath/plant_catalog.xml](E02_XPath/plant_catalog.xml)
## Third and Fourth Excercise (E03 & E04)
Excercises 03 and 04 are scoped to get familiar to _ER_-Diagram modeling.
### Files:
- [E03_ER-Diagram/Bookstore.svg](E03_ER-Diagram/Bookstore.svg)
- [E03_ER-Diagram/Community_Center.svg](E03_ER-Diagram/Community_Center.svg)
## Fith Excercise (E05)
Excercise 05 is the introduction of _SQL_ on a _PostgreSQL_ database.
As baseline for all students, a virtual machine system with
- PostgreSQL as Database Management System
- pgAdmin4 as Web Interface
is installable via [Vagrant](https://www.vagrantup.com).
Instructions can be found [here](Setup_VM_for_Excercises_with_Vagrant.md)
| 26.468085 | 76 | 0.773312 | eng_Latn | 0.687765 |
6f9782d19a256f1101dcadda8716c4844deab020 | 1,625 | md | Markdown | README.md | Cerzat43/vscode-twigcs | 9e05cc0451a93ccef96894519d97c33515904e4c | [
"MIT"
] | 9 | 2017-11-14T14:34:16.000Z | 2021-03-03T02:45:35.000Z | README.md | Cerzat43/vscode-twigcs | 9e05cc0451a93ccef96894519d97c33515904e4c | [
"MIT"
] | 14 | 2018-02-15T11:09:29.000Z | 2021-04-17T11:33:45.000Z | README.md | Cerzat43/vscode-twigcs | 9e05cc0451a93ccef96894519d97c33515904e4c | [
"MIT"
] | 2 | 2019-07-15T07:37:32.000Z | 2020-06-19T13:15:25.000Z | # vscode-twigcs
[](https://marketplace.visualstudio.com/items?itemName=cerzat43.twigcs)
[](https://marketplace.visualstudio.com/items?itemName=cerzat43.twigcs)
[](https://marketplace.visualstudio.com/items?itemName=cerzat43.twigcs)
[](https://app.snyk.io/test/github/Cerzat43/vscode-twigcs)
Integrates [twigcs](https://github.com/friendsoftwig/twigcs) into [Visual Studio Code](https://code.visualstudio.com/).
## Setup Development Version
- install the [Visual Studio Code](https://code.visualstudio.com/)
- clone this repository and checkout `develop` branch
- open the cloned repository folder using [Visual Studio Code](https://code.visualstudio.com/)
- run VS Code task `npm install`
## Run/Debug Development Version
To run the development version of the `twigcs` extension:
- open the cloned repository folder using [Visual Studio Code](https://code.visualstudio.com/)
- select sidebar option `Debug`
- select option `Client + Server` from the Debug drop-down menu
- press `Start Debugging` button or hit F5
This will launch a new VS Code window named `Extension Development Host`, automatically using the development version of the `twigcs` extension.
## Credits
Thanks to [contributors](https://github.com/Cerzat43/vscode-twigcs/graphs/contributors) !
Copyright © 2017+
| 49.242424 | 155 | 0.780923 | eng_Latn | 0.218067 |
6f97a1ef09d2b59ccc9d3c4da5b1c0ef8c6c231b | 3,042 | md | Markdown | CONTRIBUTING.md | SparrowTek/DogecoinKit | 24d61f9bd9c8140bbe6a7d6f018836122714c38f | [
"MIT"
] | null | null | null | CONTRIBUTING.md | SparrowTek/DogecoinKit | 24d61f9bd9c8140bbe6a7d6f018836122714c38f | [
"MIT"
] | null | null | null | CONTRIBUTING.md | SparrowTek/DogecoinKit | 24d61f9bd9c8140bbe6a7d6f018836122714c38f | [
"MIT"
] | null | null | null | # Contributing to DogecoinKit
:+1::tada: First off, thanks for taking the time to contribute! :tada::+1:
The following is a set of guidelines for contributing to DogecoinKit, which are hosted in the [Sparrowtek Organization](https://github.com/sparrowtek) on GitHub. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
## Code of Conduct
This project and everyone participating in it is governed by this code. By participating, you are expected to uphold this code.
* Be Nice.
* Use English.
## Where Can I Ask a Question?
You can ask a question on github issues at any time. We'll soon launch a Slack group to ask a question.
## How Can I Contribute?
### Reporting Bugs
Be sure to include a **title and clear description**, as much relevant information as possible, and a **code sample** or an **executable test case** demonstrating the expected behavior that is not occurring.
### Suggesting Enhancements
Please provide the following information:
* **Use a clear and descriptive title** for the issue to identify the suggestion.
* **Describe the current behavior** and **explain which behavior you expected to see instead** and why.
* **Explain why** this enhancement would be useful to most DogecoinKit users.
* List some **other implementations where this enhancement exists.**
* Specify which **version of DogecoinKit** you're using.
* Specify **the name and version of the OS** you're using.
### Your First Code Contribution
Unsure where to begin contributing to DogecoinKit? You can start by looking through these `beginner-welcome` issues:
* [Beginner issues][beginner-welcome] - issues which should only require a few lines of code, and a test or two.
### Pull Requests
* Fill in [the required template](.github/PULL_REQUEST_TEMPLATE.md)
* Use a clear and descriptive title for the PR.
* Describe the PR clearly.
* Check with [SwiftLint](https://github.com/realm/SwiftLint) before creating a PR
## Styleguides
### Git Commit Messages
* Use the present tense ("Add feature" not "Added feature")
* Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
* Consider starting the commit message with an applicable emoji:
* :rocket: `:rocket:` when releasing a new version
* :sparkles: `:sparkles:` when adding a new file/feature
* :recycle: `:recycle:` when refactoring the format/structure of code
* :racehorse: `:racehorse:` when improving performance
* :non-potable_water: `:non-potable_water:` when plugging memory leaks
* :memo: `:memo:` when writing docs
* :bug: `:bug:` when fixing a bug
* :fire: `:fire:` when removing code or files
* :green_heart: `:green_heart:` when fixing the CI build
* :white_check_mark: `:white_check_mark:` when adding tests
* :lock: `:lock:` when dealing with security
* :arrow_up: `:arrow_up:` when upgrading dependencies
* :arrow_down: `:arrow_down:` when downgrading dependencies
* :shirt: `:shirt:` when removing linter warnings
| 46.090909 | 294 | 0.737015 | eng_Latn | 0.998528 |
6f986224c635108581cae128605aa1a49ee07b5d | 572 | md | Markdown | README.md | sei-kiu/Wio-Terminal-ultrasonic-distance-sensor | 38873ab13e2180d613ed92f382aaa6f14a331f0b | [
"MIT"
] | 1 | 2022-01-05T09:54:16.000Z | 2022-01-05T09:54:16.000Z | README.md | sei-kiu/Wio-Terminal-Grove-ultrasonic-distance-sensor | 38873ab13e2180d613ed92f382aaa6f14a331f0b | [
"MIT"
] | null | null | null | README.md | sei-kiu/Wio-Terminal-Grove-ultrasonic-distance-sensor | 38873ab13e2180d613ed92f382aaa6f14a331f0b | [
"MIT"
] | null | null | null | # Wio-Terminal-ultrasonic-distance-sensor
This example shows usage of (Seeed Studio Grove Ultrasonic Distance Sensor)[https://www.seeedstudio.com/Grove-Ultrasonic-Distance-Sensor.html] using (Release v1.0.3)[https://github.com/Seeed-Studio/Seeed_Arduino_UltrasonicRanger/releases/tag/v1.0.3] of the provided (library)[https://github.com/Seeed-Studio/Seeed_Arduino_UltrasonicRanger]
Libraries used
- https://github.com/Seeed-Studio/Seeed_Arduino_UltrasonicRanger/releases/tag/v1.0.3
This example shows how to use Wio Terminal to get data from ultrasonic distanc sensor.
| 63.555556 | 339 | 0.818182 | eng_Latn | 0.259778 |
6f98a147cb7f1f48f883b00a4091d65fecc83f8f | 30 | md | Markdown | README.md | wchavarria03/node-todo | f63f531da058641acad94873650a852217e1ff98 | [
"MIT"
] | null | null | null | README.md | wchavarria03/node-todo | f63f531da058641acad94873650a852217e1ff98 | [
"MIT"
] | null | null | null | README.md | wchavarria03/node-todo | f63f531da058641acad94873650a852217e1ff98 | [
"MIT"
] | null | null | null | # node-todo
Todo BE on NodeJS
| 10 | 17 | 0.733333 | yue_Hant | 0.642741 |
6f98d58017e4c8e768ce6795ebf3c5acda67a4ca | 41 | md | Markdown | README.md | baor/hello-world | 34fb13e73916cd01a20f748bcd76e88d21ec35c1 | [
"MIT"
] | null | null | null | README.md | baor/hello-world | 34fb13e73916cd01a20f748bcd76e88d21ec35c1 | [
"MIT"
] | null | null | null | README.md | baor/hello-world | 34fb13e73916cd01a20f748bcd76e88d21ec35c1 | [
"MIT"
] | null | null | null | # hello-world
a small container for tests | 20.5 | 27 | 0.804878 | eng_Latn | 0.998594 |
6f991e5acbaa8359d1185fab76e170808683c50b | 6,040 | md | Markdown | readme.md | cdaller/csv_anonymizer | 7148cef9bd1c8599c50fd666c989e30e64967fba | [
"Apache-2.0"
] | 10 | 2018-03-10T09:05:24.000Z | 2022-01-25T13:47:20.000Z | readme.md | cdaller/csv_anonymizer | 7148cef9bd1c8599c50fd666c989e30e64967fba | [
"Apache-2.0"
] | 3 | 2019-01-22T02:54:52.000Z | 2019-05-08T17:33:26.000Z | readme.md | cdaller/csv_anonymizer | 7148cef9bd1c8599c50fd666c989e30e64967fba | [
"Apache-2.0"
] | 6 | 2019-01-21T09:19:36.000Z | 2022-01-25T13:04:17.000Z | # Multi Anonymizer
The main target of this script is to anonymize one value consistently in multiple files.
E.g. the id of a bank account is used in multiple files - anonymization should replace a given
bank account id in all files with the same value, so the consistency across all files is not broken by
the anonymization process.
The anonymization is done by the joe2k/faker library - so in principle all anonymization types of this library are supported. In practice, only a couple are really used:
* name
* last_name
* first_name
* email
* phone_number
* zip code
* street
* street_address
* city
* iban
* number
* text
* sentence
* text
More can be easily added.
Note: As the script now also handles xml files, it was renamed to from csv_anonymizer.py to multi_anonymizer.py
## CSV
CSV Anonymizer: reads one or more csv files and anonymizes one column with a given type (e.g. name, number).
It is able to anonymize different columns that contain the same values from different csv files.
E.g. the account number of a bank account is used in a.csv in column 3 and in b.csv in column 4:
multi_anonymizer --type=number --input a.csv:3 b.cvs:4 foobar_*.cvs:6
Same, but with different delimter and a wildcard file selector (wildcards are handled by script, not by shell):
multi_anonymizer --type=name --delimiter "," --input a.csv:3 b.cvs:4 "**/foobar_*.cvs:6"
would anonymize the bank account number in both files in a way that bank account number 123456 is anonymized to a random integer - but to the same random integer in all rows in both files.
Please not that the default values might not be appropriate for you (e.g. delimiter is set to semicolon by default, encoding is set to ISO-8859-15, number of header lines to 0, etc.), so check the command line arguments (```--help```) for possible switches and their default values.
Another tiny tool included in this package is ```csv_filterlines.py``` that can be used to filter lines in a csv file (but still print the header lines untouched). Python has the advantage of being able to handle various encodings quite nice, which is a hassle with other tools/combination of other tools (```head ... | grep ...```).
csv_filterlines.py --header-lines=1 --encoding UTF-16 input.csv output.csv
## XML
The script can also anonymize values in xml entities/attributes of one or more xml files. Instead of a column as in csv files, an xpath selector is used to define, which entities/attributes will be anonymized.
multi_anonymizer --type=last_name --input addresses.xml:./person/lastname
And example for attributes is
multi_anonymizer --type=number --input addresses.xml:./person/@id
See the examples below for more and more complicated examples.
### Namespaces
Please note that if the xml uses namespaces the anonymization might not work when the xpath expression does not correctly use the correct namespace.
Use the ```--namespace``` argument to add one or more namespaces to be used during xpatht selection. See the example section for - well - an example.
## Installation
Script runs with python 3 (3.8.x and above).
Install faker python library and other dependencies:
```
pip3 install faker
pip3 install glob2
pip3 install lxml
```
Might need to do with sudo:
```
sudo -H pip3 install faker
sudo -H pip3 install glob2
sudo -H pip3 install lxml
```
## Examples
### CSV
The testfiles directory contains some test csv files that demonstrate the usage:
Anonymize the person id in all files, first and last name in persons file
``` sh
# anonymize columns in mulitple csv files:
./multi_anonymizer.py --header-lines 1 \
--input testfiles/persons.csv:0 testfiles/addresses.csv:1
./multi_anonymizer.py --header-lines 1 --overwrite --type first_name \
--input testfiles/persons.csv_anonymized:1
./multi_anonymizer.py --header-lines 1 --overwrite --type last_name \
--input testfiles/persons.csv_anonymized:2
# support wildcards in file paths (even recursive directories) - need quotes for wildcards to be passed to script:
./multi_anonymizer.py --header-lines 1 --overwrite --type last_name \
--input "testfiles/**/?erson*s.csv_anonymized:2"
```
### XML
Anonymize element and attribute values in xml files. Use xpath for selection of the element/attribute to be anonymized:
``` sh
# anonymize element values in xml files:
./multi_anonymizer.py --type last_name \
--input testfiles/addresses.xml:./person/lastname
./multi_anonymizer.py --type firat_name \
--input testfiles/addresses.xml_anonymized:./person/firstname
# anonymize attribute value usind /@attributeName syntax:
./multi_anonymizer.py --overwrite --type number \
--input testfiles/addresses.xml_anonymized:./person/address/@id
./multi_anonymizer.py --overwrite --type zip \
--input testfiles/addresses.xml_anonymized:./person/address/zip
```
Use selector (filter) for elements, then choose the attribute to be anonymized:
``` sh
# do advanced xpath filtering (need single quotes for braces):
# filter on id
./multi_anonymizer.py --type number \
--input 'testfiles/addresses.xml:./person/address[@id="123"]/@id'
# filter on name, then choose another element's attribute to be anonymized:
./multi_anonymizer.py --type number \
--input 'testfiles/addresses.xml:.//person/lastname[text()="Riegler"]/../address/@id'
```
#### Namespaces
``` sh
./multi_anonymizer.py --type last_name \
--namespace adr=https://github.com/cdaller/multi_anonymizer/addressbook \
--input testfiles/addresses_ns.xml:./adr:person/lastname
```
As there is no such thing as default namespaces in xpath, just use any prefix for the namespace mapping and for the xpath expression.
## Thanks
Thanks to joke2k for https://joke2k.net/faker/
and to Benjamin Bengfort for inspiration
(http://blog.districtdatalabs.com/a-practical-guide-to-anonymizing-datasets-with-python-faker)
## TODO
* number start/end
* delete column
* set fixed value in column
* create person dict from id (like person_id), then use firstname, lastname, etc. of this person in columns
| 36.385542 | 333 | 0.755464 | eng_Latn | 0.990867 |
6f99c053b313abffb81ff2bb219b406e301256fc | 212 | md | Markdown | README.md | alajfit/cleanScrollBars | ffb7de2bb9843622addaa9c2c7ba4152a15dae9e | [
"MIT"
] | null | null | null | README.md | alajfit/cleanScrollBars | ffb7de2bb9843622addaa9c2c7ba4152a15dae9e | [
"MIT"
] | null | null | null | README.md | alajfit/cleanScrollBars | ffb7de2bb9843622addaa9c2c7ba4152a15dae9e | [
"MIT"
] | null | null | null | # Clean Scroll Bars
SCROLL BAR INSIDE DIV
* This class allows us to change the scrollbar
look within a div to align with the website
look and feel, this can even be added to the
body of the document
| 23.555556 | 48 | 0.735849 | eng_Latn | 0.998238 |
6f9bbdf6afb52693ceb33246e497f57e2099c599 | 360 | md | Markdown | samples/Sentry.Samples.EntityFramework/README.md | Vandersteen/sentry-dotnet | 12c46e1b8a56211075cab11a9b32acc932ef7f35 | [
"MIT"
] | 398 | 2018-05-14T14:44:49.000Z | 2022-03-27T10:00:00.000Z | samples/Sentry.Samples.EntityFramework/README.md | Vandersteen/sentry-dotnet | 12c46e1b8a56211075cab11a9b32acc932ef7f35 | [
"MIT"
] | 1,370 | 2018-05-14T14:43:24.000Z | 2022-03-31T23:38:50.000Z | samples/Sentry.Samples.EntityFramework/README.md | Vandersteen/sentry-dotnet | 12c46e1b8a56211075cab11a9b32acc932ef7f35 | [
"MIT"
] | 184 | 2018-06-05T01:13:23.000Z | 2022-03-02T23:10:32.000Z | # Entity Framework 6 sample
If you're using Entity Framework Core, you don't need the package used in this sample.
Sentry can integrate with EF Core through `Sentry.Extensions.Logging` already.
Sentry.EntityFramework` is used to integrated with EF 6 only.
Breadcrumbs for different EF core events:
| 32.727273 | 86 | 0.780556 | eng_Latn | 0.984618 |
6f9bdb86c734be8904a04395a0e451226709a908 | 11,344 | md | Markdown | docs/integration-services/data-flow/flat-file-source.md | real-napster/sql-docs.de-de | 0cf3bb09a98541d4ee3fd6e4635b008c94019b6a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/integration-services/data-flow/flat-file-source.md | real-napster/sql-docs.de-de | 0cf3bb09a98541d4ee3fd6e4635b008c94019b6a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/integration-services/data-flow/flat-file-source.md | real-napster/sql-docs.de-de | 0cf3bb09a98541d4ee3fd6e4635b008c94019b6a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Flatfilequelle | Microsoft-Dokumentation
ms.custom: ''
ms.date: 03/01/2017
ms.prod: sql
ms.prod_service: integration-services
ms.reviewer: ''
ms.technology: integration-services
ms.topic: conceptual
f1_keywords:
- sql13.dts.designer.flatfilesource.f1
- sql13.dts.designer.flatfilesourceadapter.connection.f1
- sql13.dts.designer.flatfilesourceadapter.columns.f1
- sql13.dts.designer.flatfilesourceadapter.errorhandling.f1
helpviewer_keywords:
- sources [Integration Services], Flat File
- text file reading [Integration Services]
- flat files
- Flat File source
ms.assetid: 4a64f7f3-f25d-4db0-93b3-a29496030e58
author: janinezhang
ms.author: janinez
manager: craigg
ms.openlocfilehash: b1a7e2f0320790959df4f29bfd586f70acec9de7
ms.sourcegitcommit: 7ccb8f28eafd79a1bddd523f71fe8b61c7634349
ms.translationtype: HT
ms.contentlocale: de-DE
ms.lasthandoff: 03/20/2019
ms.locfileid: "58271050"
---
# <a name="flat-file-source"></a>Flatfilequelle
Die Flatfilequelle liest Daten aus einer Textdatei. Die Textdatei kann in einem Format mit Trennzeichen, fester Breite oder einem gemischten Format vorliegen.
- Beim Format mit Trennzeichen werden Spalten und Zeilen mithilfe von Spalten- und Zeilentrennzeichen definiert.
- Beim Format mit fester Breite werden Spalten und Zeilen mithilfe der Breite definiert. Dieses Format schließt außerdem ein Zeichen zur Auffüllung der Felder auf die maximale Breite ein.
- Beim Format mit einem rechten Flatterrand werden mithilfe der Breite alle Spalten definiert, außer der letzten Spalte, die durch das Zeilentrennzeichen getrennt wird.
Es gibt folgende Möglichkeiten, um die Flatfilequelle zu konfigurieren:
- Fügen Sie der Transformationsausgabe eine Zeile hinzu, die den Namen der Textdatei enthält, aus der die Flatfilequelle Daten extrahiert.
- Geben Sie an, ob die Flatfilequelle leere Zeichenfolgen in Spalten als NULL-Werte interpretiert.
> [!NOTE]
> Für den von der Flatfilequelle verwendeten Verbindungs-Manager für Flatfiles muss die Verwendung eines Formats mit Trennzeichen konfiguriert werden, damit leere Zeichenfolgen als NULL-Werte interpretiert werden. Falls der Verbindungs-Manager ein Format mit fester Breite oder mit einem Flatterrand verwendet, können aus Leerzeichen bestehende Daten nicht als NULL-Werte interpretiert werden.
Die Ausgabespalte in der Ausgabe der Flatfilequelle schließt die FastParse-Eigenschaft ein. FastParse gibt an, ob die Spalte die schnelleren gebietsschemaneutralen Analyseroutinen von [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] oder die gebietsschemabezogenen Standardanalyseroutinen verwendet. Weitere Informationen finden Sie unter [Fast Parse](https://msdn.microsoft.com/library/6688707d-3c5b-404e-aa2f-e13092ac8d95) und [Standard Parse](https://msdn.microsoft.com/library/dfe835b1-ea52-4e18-a23a-5188c5b6f013).
Ausgabespalten schließen auch UseBinaryFormat-Eigenschaft ein. Sie verwenden diese Eigenschaft, um Unterstützung für binäre Daten in Dateien zu implementieren, wie für Daten mit dem gepackten Dezimalformat. Standardmäßig ist UseBinaryFormat auf **FALSE**festgelegt. Wenn Sie ein Binärformat verwenden möchten, legen Sie UseBinaryFormat auf **TRUE** fest und den Datentyp in der Ausgabespalte auf **DT_BYTES**. Bei diesem Vorgang überspringt die Flatfilequelle die Datenkonvertierung und leitet die Daten durch die Ausgabespalte, wie sie ist. Sie können eine Transformation verwenden, wie „Abgeleitete Spalte“ oder „Datenkonvertierung“, um die **DT_BYTES** -Daten in einen anderen Datentyp umzuwandeln, oder Sie können ein benutzerdefiniertes Skript in eine Skripttransformation schreiben, um die Daten zu interpretieren. Sie können auch eine benutzerdefinierte Datenflusskomponente schreiben, um die Daten zu interpretieren. Weitere Informationen zu den Datentypen, die Sie in **DT_BYTES** umwandeln können, finden Sie unter [CAST (SSIS-Ausdruck)](../../integration-services/expressions/cast-ssis-expression.md).
Diese Quelle verwendet für den Zugriff auf die Textdatei einen Verbindungs-Manager für Flatfiles. Durch Festlegen von Eigenschaften im Verbindungs-Manager für Flatfiles können Sie Informationen zur Datei und zu jeder enthaltenen Spalte bereitstellen und angeben, wie die Flatfilequelle die Daten in der Textdatei behandeln soll. Beispielsweise können Sie die Zeichen angeben, mit denen Spalten und Zeilen in der Datei getrennt werden, sowie den Datentyp und die Länge jeder Spalte. Weitere Informationen finden Sie unter [Flat File Connection Manager](../../integration-services/connection-manager/flat-file-connection-manager.md).
Diese Quelle weist eine Ausgabe und eine Fehlerausgabe auf.
## <a name="configuration-of-the-flat-file-source"></a>Konfiguration der Flatfilequelle
Sie können Eigenschaften mit dem [!INCLUDE[ssIS](../../includes/ssis-md.md)] -Designer oder programmgesteuert festlegen.
Das Dialogfeld **Erweiterter Editor** enthält die Eigenschaften, die programmgesteuert festgelegt werden können. Klicken Sie auf eines der folgenden Themen, um weitere Informationen zu den Eigenschaften zu erhalten, die Sie im Dialogfeld **Erweiterter Editor** oder programmgesteuert festlegen können:
- [Common Properties](https://msdn.microsoft.com/library/51973502-5cc6-4125-9fce-e60fa1b7b796)
- [Benutzerdefinierte Eigenschaften der Flatfile](../../integration-services/data-flow/flat-file-custom-properties.md)
## <a name="related-tasks"></a>Related Tasks
Weitere Informationen zum Festlegen der Eigenschaften einer Datenflusskomponente finden Sie unter [Festlegen der Eigenschaften einer Datenflusskomponente](../../integration-services/data-flow/set-the-properties-of-a-data-flow-component.md).
## <a name="flat-file-source-editor-connection-manager-page"></a>Quellen-Editor für Flatfiles (Seite Verbindungs-Manager)
Wählen Sie auf der Seite **Verbindungs-Manager** des Dialogfelds **Quellen-Editor für Flatfiles** den Verbindungs-Manager aus, den die Flatfilequelle verwenden soll. Die Flatfilequelle liest die Daten aus einer Textdatei, die in den Formaten mit Trennzeichen, fester Breite oder mit gemischten Inhalten vorliegen kann.
Eine Flatfilequelle kann einen der folgenden Typen von Verbindungs-Manager verwenden:
- Einen Verbindungs-Manager für Flatfiles, wenn es sich bei der Quelle um eine einzelne Flatfile handelt. Weitere Informationen finden Sie unter [Flat File Connection Manager](../../integration-services/connection-manager/flat-file-connection-manager.md).
- Einen Verbindungs-Manager für mehrere Flatfiles, wenn es bei der Quelle um mehrere Flatfiles handelt und der Datenflusstask sich in einem Schleifencontainer wie dem For-Schleifencontainer befindet. In jeder Schleife des Containers werden von der Flatfilequelle Daten vom nächsten Dateinamen geladen, der vom Verbindungs-Manager für mehrere Flatfiles bereitgestellt wird. Weitere Informationen finden Sie unter [Multiple Flat Files Connection Manager](../../integration-services/connection-manager/multiple-flat-files-connection-manager.md).
### <a name="options"></a>enthalten
**Flat file connection manager**
Wählen Sie einen vorhandenen Verbindungs-Manager aus der Liste aus, oder erstellen Sie einen neuen Verbindungs-Manager, indem Sie auf **Neu**klicken.
**Neu**
Erstellen Sie mithilfe des Dialogfelds **Verbindungs-Manager-Editor für Flatfiles** einen neuen Verbindungs-Manager.
**NULL-Werte aus der Quelle als NULL-Werte im Datenfluss beibehalten**
Geben Sie an, ob NULL-Werte erhalten werden, wenn Daten extrahiert werden. Der Standardwert dieser Eigenschaft ist **false**. Wenn dieser Wert f**alse**ist, ersetzt die Flatfilequelle die NULL-Werte aus den Quelldaten mit entsprechenden Standardwerten für jede Spalte, z. B. mit leeren Zeichenfolgen in Zeichenfolgenspalten und Nullen in numerischen Spalten.
**Vorschau**
Zeigen Sie mithilfe des Dialogfelds **Datenansicht** eine Vorschau der Ergebnisse an. In der Vorschau können bis zu 200 Zeilen angezeigt werden.
## <a name="flat-file-source-editor-columns-page"></a>Quellen-Editor für Flatfiles (Seite Spalten)
Mithilfe des Knotens **Spalten** des Dialogfelds **Quellen-Editor für Flatfiles** können Sie jeder externen (Quell-)Spalte eine Ausgabespalte zuordnen.
> [!NOTE]
> Die **FileNameColumnName** -Eigenschaft der Flatfilequelle und die **FastParse** -Eigenschaft ihrer Ausgabespalten sind nicht im **Quellen-Editor für Flatfiles**verfügbar, sie können jedoch mithilfe des Dialogfelds **Erweiterter Editor**festgelegt werden. Weitere Informationen zu diesen Eigenschaften finden Sie im Abschnitt Flatfilequelle von [Flat File Custom Properties](../../integration-services/data-flow/flat-file-custom-properties.md).
### <a name="options"></a>enthalten
**Verfügbare externe Spalten**
Zeigt die Liste der in der Datenquelle verfügbaren externen Spalten an. Mit der Tabelle können keine Spalten hinzugefügt oder gelöscht werden.
**Externe Spalte**
Zeigt die externen (Quell-)Spalten in der Reihenfolge an, in der sie von dem Task gelesen werden. Sie können die Reihenfolge ändern, indem Sie zunächst die ausgewählten Spalten in der Tabelle löschen. Wählen Sie anschließend die externen Spalten in einer anderen Reihenfolge aus der Liste aus.
**Ausgabespalte**
Geben Sie für jede Ausgabespalte einen eindeutigen Namen an. Standardmäßig wird der Name der ausgewählten externen (Quell-)Spalte verwendet. Sie können jedoch auch einen beschreibenden Namen angeben, sofern dieser eindeutig ist. Der angegebene Name wird im [!INCLUDE[ssIS](../../includes/ssis-md.md)] -Designer angezeigt.
## <a name="flat-file-source-editor-error-output-page"></a>Quellen-Editor für Flatfiles (Seite Fehlerausgabe)
Mithilfe der Seite **Fehlerausgabe** im Dialogfeld **Quellen-Editor für Flatfiles** können Sie Fehlerbehandlungsoptionen auswählen und Eigenschaften für Fehlerausgabespalten festlegen.\
### <a name="options"></a>enthalten
**Eingabe/Ausgabe**
Zeigt den Namen der Datenquelle an.
**Column**
Zeigt die externen (Quell-)Spalten an, die im Dialogfeld **Quellen-Editor für Flatfiles** auf der Seite **Verbindungs-Manager**ausgewählt wurden.
**Fehler**
Gibt an, was bei Auftreten eines Fehlers geschehen soll: den Fehler ignorieren, die Zeile umleiten oder die Komponente mit einem Fehler abbrechen.
**Verwandte Themen:** [Fehlerbehandlung in Daten](../../integration-services/data-flow/error-handling-in-data.md)
**Abschneiden**
Gibt an, was im Falle einer Kürzung geschehen soll: den Fehler ignorieren, die Zeile umleiten oder die Komponente mit einem Fehler abbrechen.
**Beschreibung**
Zeigt die Beschreibung des Fehlers an.
**Diesen Wert für ausgewählte Zellen festlegen**
Gibt an, was im Falle eines Fehlers oder einer Kürzung mit den ausgewählten Zellen geschehen soll: den Fehler ignorieren, die Zeile umleiten oder die Komponente mit einem Fehler abbrechen.
**Anwenden**
Wendet die Fehlerbehandlungsoption auf die ausgewählten Zellen an.
## <a name="see-also"></a>Weitere Informationen
[Flatfileziel](../../integration-services/data-flow/flat-file-destination.md)
[Datenfluss](../../integration-services/data-flow/data-flow.md)
| 81.611511 | 1,123 | 0.79055 | deu_Latn | 0.994892 |
6f9c6ff4ff3925f8dbd27afcb2c2e55d449d480f | 11,795 | md | Markdown | windows/security/threat-protection/windows-defender-application-guard/test-scenarios-wd-app-guard.md | zhvolosh/windows-itpro-docs | e8ba34a0775173087af17cc2340521b5331ee825 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-04-14T23:00:53.000Z | 2020-04-14T23:00:53.000Z | windows/security/threat-protection/windows-defender-application-guard/test-scenarios-wd-app-guard.md | zhvolosh/windows-itpro-docs | e8ba34a0775173087af17cc2340521b5331ee825 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | windows/security/threat-protection/windows-defender-application-guard/test-scenarios-wd-app-guard.md | zhvolosh/windows-itpro-docs | e8ba34a0775173087af17cc2340521b5331ee825 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-01-10T04:19:37.000Z | 2020-01-10T04:19:37.000Z | ---
title: Testing scenarios with Windows Defender Application Guard (Windows 10)
description: Suggested testing scenarios for Windows Defender Application Guard, showing how it works in both Standalone and Enterprise-managed mode.
ms.prod: w10
ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: security
ms.localizationpriority: medium
author: denisebmsft
ms.author: deniseb
ms.date: 03/15/2019
ms.reviewer:
manager: dansimp
ms.custom: asr
---
# Application Guard testing scenarios
**Applies to:**
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559)
We've come up with a list of scenarios that you can use to test hardware-based isolation in your organization.
## Application Guard in standalone mode
You can see how an employee would use standalone mode with Application Guard.
**To test Application Guard in Standalone mode**
1. [Install Application Guard](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-application-guard/install-wd-app-guard).
2. Restart the device, start Microsoft Edge, and then click **New Application Guard window** from the menu.
3. Wait for Application Guard to set up the isolated environment.
>[!NOTE]
>Starting Application Guard too quickly after restarting the device might cause it to take a bit longer to load. However, subsequent starts should occur without any perceivable delays.
4. Go to an untrusted, but safe URL (for this example, we used msn.com) and view the new Microsoft Edge window, making sure you see the Application Guard visual cues.
## Application Guard in Enterprise-managed mode
How to install, set up, turn on, and configure Application Guard for Enterprise-managed mode.
### Install, set up, and turn on Application Guard
Before you can use Application Guard in enterprise mode, you must install Windows 10 Enterprise edition, version 1709, which includes the functionality. Then, you must use Group Policy to set up the required settings.
1. [Install Application Guard](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-application-guard/install-wd-app-guard#install-application-guard).
2. Restart the device and then start Microsoft Edge.
3. Set up the Network Isolation settings in Group Policy:
a. Click on the **Windows** icon, type _Group Policy_, and then click **Edit Group Policy**.
b. Go to the **Administrative Templates\Network\Network Isolation\Enterprise resource domains hosted in the cloud** setting.
c. For the purposes of this scenario, type _.microsoft.com_ into the **Enterprise cloud resources** box.
d. Go to the **Administrative Templates\Network\Network Isolation\Domains categorized as both work and personal** setting.
e. For the purposes of this scenario, type _bing.com_ into the **Neutral resources** box.
4. Go to the **Computer Configuration\Administrative Templates\Windows Components\Windows Defender Application Guard\Turn on Windows Defender Application Guard in Enterprise Mode** setting.
5. Click **Enabled**, choose Option **1**, and click **OK**.
>[!NOTE]
>Enabling this setting verifies that all the necessary settings are properly configured on your employee devices, including the network isolation settings set earlier in this scenario.
6. Start Microsoft Edge and type <em>www.microsoft.com</em>.
After you submit the URL, Application Guard determines the URL is trusted because it uses the domain you’ve marked as trusted and shows the site directly on the host PC instead of in Application Guard.
7. In the same Microsoft Edge browser, type any URL that isn’t part of your trusted or neutral site lists.
After you submit the URL, Application Guard determines the URL is untrusted and redirects the request to the hardware-isolated environment.
### Customize Application Guard
Application Guard lets you specify your configuration, allowing you to create the proper balance between isolation-based security and productivity for your employees.
Application Guard provides the following default behavior for your employees:
- No copying and pasting between the host PC and the isolated container.
- No printing from the isolated container.
- No data persistence from one isolated container to another isolated container.
You have the option to change each of these settings to work with your enterprise from within Group Policy.
**Applies to:**
- Windows 10 Enterpise edition, version 1709 or higher
- Windows 10 Professional edition, version 1803
#### Copy and paste options
1. Go to the **Computer Configuration\Administrative Templates\Windows Components\Windows Defender Application Guard\Configure Windows Defender Application Guard clipboard settings**.
2. Click **Enabled** and click **OK**.
3. Choose how the clipboard works:
- Copy and paste from the isolated session to the host PC
- Copy and paste from the host PC to the isolated session
- Copy and paste both directions
4. Choose what can be copied:
- **1.** Only text can be copied between the host PC and the isolated container.
- **2.** Only images can be copied between the host PC and the isolated container.
- **3.** Both text and images can be copied between the host PC and the isolated container.
5. Click **OK**.
#### Print options
1. Go to the **Computer Configuration\Administrative Templates\Windows Components\Windows Defender Application Guard\Configure Windows Defender Application Guard print** settings.
2. Click **Enabled** and click **OK**.
3. Based on the list provided in the setting, choose the number that best represents what type of printing should be available to your employees. You can allow any combination of local, network, PDF, and XPS printing.
4. Click **OK**.
#### Data persistence options
1. Go to the **Computer Configuration\Administrative Templates\Windows Components\Windows Defender Application Guard\Allow data persistence for Windows Defender Application Guard** setting.
2. Click **Enabled** and click **OK**.
3. Open Microsoft Edge and browse to an untrusted, but safe URL.
The website opens in the isolated session.
4. Add the site to your **Favorites** list and then close the isolated session.
5. Log out and back on to your device, opening Microsoft Edge in Application Guard again.
The previously added site should still appear in your **Favorites** list.
>[!NOTE]
>If you don't allow or turn off data persistence, restarting a device or logging in and out of the isolated container triggers a recycle event that discards all generated data, including session cookies, Favorites, and so on, removing the data from Application Guard. If you turn on data persistence, all employee-generated artifacts are preserved across container recycle events. However, these artifacts only exist in the isolated container and aren’t shared with the host PC. This data persists after restarts and even through build-to-build upgrades of Windows 10.<br><br>If you turn on data persistence, but later decide to stop supporting it for your employees, you can use our Windows-provided utility to reset the container and to discard any personal data.<br><br>**To reset the container, follow these steps:**<br/>1. Open a command-line program and navigate to Windows/System32.<br/>2. Type `wdagtool.exe cleanup`. The container environment is reset, retaining only the employee-generated data.<br/>3. Type `wdagtool.exe cleanup RESET_PERSISTENCE_LAYER`. The container environment is reset, including discarding all employee-generated data.
**Applies to:**
- Windows 10 Enterpise edition, version 1803
- Windows 10 Professional edition, version 1803
#### Download options
1. Go to the **Computer Configuration\Administrative Templates\Windows Components\Windows Defender Application Guard\Allow files to download and save to the host operating system from Windows Defender Application Guard** setting.
2. Click **Enabled** and click **OK**.
3. Log out and back on to your device, opening Microsoft Edge in Application Guard again.
4. Download a file from Windows Defender Application Guard.
5. Check to see the file has been downloaded into This PC > Downloads > Untrusted files.
#### Hardware acceleration options
1. Go to the **Computer Configuration\Administrative Templates\Windows Components\Windows Defender Application Guard\Allow hardware-accelerated rendering for Windows Defender Application Guard** setting.
2. Click **Enabled** and click **OK**.
3. Once you have enabled this feature, open Microsoft Edge and browse to an untrusted, but safe URL with video, 3D, or other graphics-intensive content. The website opens in an isolated session.
4. Assess the visual experience and battery performance.
**Applies to:**
- Windows 10 Enterpise edition, version 1809
- Windows 10 Professional edition, version 1809
#### File trust options
1. Go to the **Computer Configuration\Administrative Templates\Windows Components\Windows Defender Application Guard\Allow users to trust files that open in Windows Defender Application Guard** setting.
2. Click **Enabled**, set **Options** to 2, and click **OK**.
3. Log out and back on to your device, opening Microsoft Edge in Application Guard again.
4. Open a file in Edge, such an Office 365 file.
5. Check to see that an antivirus scan completed before the file was opened.
#### Camera and microphone options
1. Go to the **Computer Configuration\Administrative Templates\Windows Components\Windows Defender Application Guard\Allow camera and microphone access in Windows Defender Application Guard** setting.
2. Click **Enabled** and click **OK**.
3. Log out and back on to your device, opening Microsoft Edge in Application Guard again.
4. Open an application with video or audio capability in Edge.
5. Check that the camera and microphone work as expected.
#### Root certificate sharing options
1. Go to the **Computer Configuration\Administrative Templates\Windows Components\Windows Defender Application Guard\Allow Windows Defender Application Guard to use Root Certificate Authorities from the user's device** setting.
2. Click **Enabled**, copy the thumbprint of each certificate to share, separated by a comma, and click **OK**.
3. Log out and back on to your device, opening Microsoft Edge in Application Guard again.
| 47.947154 | 1,155 | 0.775413 | eng_Latn | 0.965201 |
6f9ca7d5f2e5b8bd9fac8ce89bfe17b341d8c67a | 1,387 | md | Markdown | README.md | kcredit/LODES-ACS-commuting-flows | 69b2652d07d948da6ec6818165ba0c93ff2d79d9 | [
"BSD-3-Clause"
] | null | null | null | README.md | kcredit/LODES-ACS-commuting-flows | 69b2652d07d948da6ec6818165ba0c93ff2d79d9 | [
"BSD-3-Clause"
] | null | null | null | README.md | kcredit/LODES-ACS-commuting-flows | 69b2652d07d948da6ec6818165ba0c93ff2d79d9 | [
"BSD-3-Clause"
] | null | null | null | # LODES-ACS-commuting-flows
This repository contains code for developing an open source method to derive small area estimates of linked (origin-destination) commuting trips by transportation mode from open source Longitudinal Employer-Household Dynamics (LEHD) Origin-Destination Statistics (known as LODES) and American Community Survey (ACS) data in R. This method is fully-customisable and can be applied at the block scale to the entire US (with a small number of exceptions) for every year from 2002-2019. For demonstration purposes, the code here applies this method to 2015 commuting flows at the tract scale in Cook County, Illinois. Although the data used in this application can be downloaded openly from the US Census Bureau (2015 LODES: https://lehd.ces.census.gov/data/; 2013-2017 5-year ACS: https://data.census.gov/cedsci/), lightly-cleaned version are provided in this repository for convenience. Obtaining tract-to-tract transit travel times from r5r, which is used to determine viable transit trips, also requires an OpenStreetMap (OSM) file for a given region and a valid General Transit Feed Specification (GTFS) file. While these can also be obtained openly online (from https://www.interline.io/osm/extracts/ and http://transitfeeds.com/p/chicago-transit-authority/165, respectively), versions for 11 November, 2021 for Chicago are also included in this repository. | 693.5 | 1,359 | 0.80894 | eng_Latn | 0.995741 |
6f9ced773b36a8242bd5b4837d762a02ebdb68f1 | 8,672 | md | Markdown | articles/iot-pnp/tutorial-configure-tsi.md | MicrosoftDocs/azure-docs.zh-cn | 00fd9a9dda6d9b896fdab7f0bf72825621ae2c6e | [
"CC-BY-4.0",
"MIT"
] | 133 | 2017-06-29T06:38:23.000Z | 2022-03-27T23:09:57.000Z | articles/iot-pnp/tutorial-configure-tsi.md | renhuailin/azure-docs.zh-cn | 1f63de4d83c8c84ab6afa16b7548f8afe1f2fa36 | [
"CC-BY-4.0",
"MIT"
] | 720 | 2017-06-28T19:59:50.000Z | 2021-11-22T07:13:21.000Z | articles/iot-pnp/tutorial-configure-tsi.md | renhuailin/azure-docs.zh-cn | 1f63de4d83c8c84ab6afa16b7548f8afe1f2fa36 | [
"CC-BY-4.0",
"MIT"
] | 190 | 2017-06-28T06:08:21.000Z | 2022-03-16T11:48:36.000Z | ---
title: 教程 - 使用 Azure 时序见解来存储和分析 Azure IoT 即插即用设备遥测
description: 教程 - 设置时序见解环境并连接 IoT 中心，以便从 IoT 即插即用设备查看和分析遥测。
author: lyrana
ms.author: lyhughes
ms.date: 10/14/2020
ms.topic: tutorial
ms.service: iot-pnp
services: iot-pnp
ms.openlocfilehash: 08ae21c2cd0859b7c361756a4f0380d3ab322a28
ms.sourcegitcommit: d1b0cf715a34dd9d89d3b72bb71815d5202d5b3a
ms.translationtype: HT
ms.contentlocale: zh-CN
ms.lasthandoff: 02/08/2021
ms.locfileid: "99834351"
---
# <a name="tutorial-create-and-configure-a-time-series-insights-gen2-environment"></a>Tutorial:创建和配置时序见解 Gen2 环境
本教程将介绍如何创建和配置 [Azure 时序见解 Gen2](../time-series-insights/overview-what-is-tsi.md) 环境，以便与 IoT 即插即用解决方案集成。 使用时序见解在物联网 (IoT) 规模上收集、处理、存储、查询和可视化时序数据。
在本教程中：
> [!div class="checklist"]
> * 预配时序见解环境并将 IoT 中心作为流式处理事件源进行连接。
> * 通过模型同步来创作[时序模型](../time-series-insights/concepts-model-overview.md)。
> * 使用温度控制器和恒温器设备采用的[数字孪生定义语言 (DTDL)](https://github.com/Azure/opendigitaltwins-dtdl) 示例模型文件。
> [!NOTE]
> 时序见解和 IoT 即插即用之间的这种集成处于预览状态。 DTDL 设备模型映射到时序见解时序模型的方式可能会改变。
## <a name="prerequisites"></a>先决条件
[!INCLUDE [iot-pnp-prerequisites](../../includes/iot-pnp-prerequisites.md)]
此时，你应具备：
* Azure IoT 中心。
* 连接到 IoT 中心的设备预配服务 (DPS) 实例。 DPS 实例应为 IoT 即插即用设备注册一个单独的设备。
* 单组件设备或多组件设备与 IoT 中心之间的连接，用于流式传输模拟数据。
为了绕开在本地安装 Azure CLI 的要求，可使用 Azure Cloud Shell 设置云服务。
[!INCLUDE [cloud-shell-try-it.md](../../includes/cloud-shell-try-it.md)]
## <a name="prepare-your-event-source"></a>准备事件源
以前创建的 IoT 中心将是时序见解环境的[事件源](../time-series-insights/concepts-streaming-ingestion-event-sources.md)。
> [!IMPORTANT]
> 禁用任何现有的 IoT 中心路由。 使用配置了[路由](../iot-hub/iot-hub-devguide-messages-d2c.md#routing-endpoints)的 IoT 中心时存在一个已知问题。 暂时禁用任何路由终结点。 IoT 中心连接到时序见解时，你可再次启用路由终结点。
在 IoT 中心上，创建唯一的使用者组，供时序见解使用。 在下面的示例中，将 `my-pnp-hub` 替换为之前使用的 IoT 中心的名称。
```azurecli-interactive
az iot hub consumer-group create --hub-name my-pnp-hub --name tsi-consumer-group
```
## <a name="choose-a-time-series-id"></a>选择时间序列 ID
预配时序见解环境时，需要选择时序 ID。 选择相应的时序 ID 很重要。 此属性是不可变的，设置后不能更改。 时序 ID 类似于数据库分区键。 时序 ID 充当时序模型的主键。 有关详细信息，请参阅[选择时序 ID 的最佳做法](../time-series-insights/how-to-select-tsid.md)。
作为 IoT 即插即用用户，请将 `iothub-connection-device-id` 和 `dt-subject` 构成的组合键指定为时序 ID。 IoT 中心会添加这些分别包含了 IoT 即插即用设备 ID 和设备组件名称的系统属性。
即使 IoT 即插即用设备模型目前不使用组件，也应将 `dt-subject` 包含在内并作为组合键的一部分，以便将来需要时可以使用它们。 由于时序 ID 不可变，Microsoft 建议启用这个选项，以便将来需要时使用。
> [!NOTE]
> 本文中的示例适用于多组件 `TemperatureController` 设备。 但是对于非组件 `Thermostat` 设备，这些概念是相同的。
## <a name="provision-your-time-series-insights-environment"></a>预配时序见解环境
本节介绍如何预配 Azure 时序见解 Gen2 环境。
运行下面的命令以实现以下目的：
* 为环境的[冷存储](../time-series-insights/concepts-storage.md#cold-store)创建 Azure 存储帐户。 此帐户旨在用于长期保留和历史数据分析。
* 在代码中，将 `mytsicoldstore` 替换为冷存储帐户的唯一名称。
* 创建 Azure 时序见解 Gen2 环境。 需使用保持期为 7 天的暖存储创建此环境。 需附加冷存储帐户，以便无限期保留。
* 在代码中，将 `my-tsi-env` 替换为时序见解环境的唯一名称。
* 在代码中，将 `my-pnp-resourcegroup` 替换为在设置过程中使用的资源组的名称。
* 时序 ID 属性是 `iothub-connection-device-id, dt-subject`。
```azurecli-interactive
storage=mytsicoldstore
rg=my-pnp-resourcegroup
az storage account create -g $rg -n $storage --https-only
key=$(az storage account keys list -g $rg -n $storage --query [0].value --output tsv)
az timeseriesinsights environment longterm create --name my-tsi-env --resource-group $rg --time-series-id-properties iothub-connection-device-id, dt-subject --sku-name L1 --sku-capacity 1 --data-retention 7 --storage-account-name $storage --storage-management-key $key --location eastus2
```
连接 IoT 中心事件源。 将 `my-pnp-resourcegroup``my-pnp-hub` 和 `my-tsi-env` 替换为所选的值。 下面的命令引用你先前创建的时序见解使用者组：
```azurecli-interactive
rg=my-pnp-resourcegroup
iothub=my-pnp-hub
env=my-tsi-env
es_resource_id=$(az iot hub create -g $rg -n $iothub --query id --output tsv)
shared_access_key=$(az iot hub policy list -g $rg --hub-name $iothub --query "[?keyName=='service'].primaryKey" --output tsv)
az timeseriesinsights event-source iothub create -g $rg --environment-name $env -n iot-hub-event-source --consumer-group-name tsi-consumer-group --key-name iothubowner --shared-access-key $shared_access_key --event-source-resource-id $es_resource_id
```
在 [Azure 门户](https://portal.azure.com)中，转到资源组，然后选择新的时序见解环境。 转到实例概述中显示的“时序见解资源管理器 URL”：
在资源管理器中，可看到三个实例：
* <pnp 设备 ID>，thermostat1
* <pnp 设备 ID>，thermostat2
* <pnp 设备 ID>，`null`
> [!NOTE]
> 第三个标记表示来自 `TemperatureController` 本身的遥测，例如设备内存的工作集。 因为这是一个顶级属性，所以组件名称的值为 null。 在后面的步骤中，你将使此名称更易于用户使用。
## <a name="configure-model-translation"></a>配置模型转换
接下来将 DTDL 设备模型转换为 Azure 时序见解中的资产模型。 在时序见解中，时序模型是一种用于数据语境化的语义建模工具。 该模型包含三个核心组件：
* [时序模型实例](../time-series-insights/concepts-model-overview.md#time-series-model-instances)是时序本身的虚拟表示形式。 实例由时序 ID 唯一标识。
* [时序模型层次结构](../time-series-insights/concepts-model-overview.md#time-series-model-hierarchies)通过指定属性名称及其关系来组织实例。
* [时序模型类型](../time-series-insights/concepts-model-overview.md#time-series-model-types)可帮助你定义用于计算的[变量](../time-series-insights/concepts-variables.md)或公式。 类型与某个特定实例关联。
### <a name="define-your-types"></a>定义类型
可以开始将数据引入到 Azure 时序见解第 2 代，无需预定义模型。 当遥测到达时，时序见解尝试基于时序 ID 属性值自动解析时序实例。 为所有实例分配默认类型。 你需要手动创建一个新类型来正确地对实例进行分类。
以下详细信息概述了将设备 DTDL 模型与时序模型类型同步的最简单方法：
* 数字孪生模型标识符将成为你的类型 ID。
* 类型名称可以是模型的名称，也可以是显示名称。
* 模型说明将成为类型的说明。
* 至少为每个具有数值架构的遥测创建一个类型变量。
* 变量只能使用 numeric 数据类型，但如果将值作为另一种可转换的类型发送（例如 `"0"`），可使用[转换](/rest/api/time-series-insights/reference-time-series-expression-syntax#conversion-functions)函数，例如 `toDouble`。
* 变量名称可以是遥测名称，也可以是显示名称。
* 定义时序表达式变量时，请参阅线上的遥测名称及遥测数据类型。
| DTDL JSON | 时序模型类型 JSON | 示例值 |
|-----------|------------------|-------------|
| `@id` | `id` | `dtmi:com:example:TemperatureController;1` |
| `displayName` | `name` | `Temperature Controller` |
| `description` | `description` | `Device with two thermostats and remote reboot.` |
|`contents`（数组）| `variables`（对象） | 请参阅以下示例。
> [!NOTE]
> 此示例显示三种变量，但每种类型最多可包含 100 个变量。 不同的变量可以引用相同的遥测值，以根据需要执行不同的计算。 有关筛选器、聚合和标量函数的完整列表，请参阅[时序见解 Gen2 时序表达式语法](/rest/api/time-series-insights/reference-time-series-expression-syntax)。
打开文本编辑器并将以下 JSON 保存到本地驱动器。
```JSON
{
"put": [
{
"id": "dtmi:com:example:TemperatureController;1",
"name": "Temperature Controller",
"description": "Device with two thermostats and remote reboot.",
"variables": {
"workingSet": {
"kind": "numeric",
"value": {
"tsx": "coalesce($event.workingSet.Long, toLong($event.workingSet.Double))"
},
"aggregation": {
"tsx": "avg($value)"
}
},
"temperature": {
"kind": "numeric",
"value": {
"tsx": "coalesce($event.temperature.Long, toLong($event.temperature.Double))"
},
"aggregation": {
"tsx": "avg($value)"
}
},
"eventCount": {
"kind": "aggregate",
"aggregation": {
"tsx": "count()"
}
}
}
}
]
}
```
在时序见解资源管理器中，选择左侧的模型图标以打开“模型”选项卡。选择“类型”，然后选择“上传 JSON” ：
选择“选择文件”，选择之前保存的 JSON，然后选择“上传” 。
你将看到新定义的温度控制器类型。
### <a name="create-a-hierarchy"></a>创建层次结构
创建一个层次结构来组织 `TemperatureController` 父项下的标记。 以下简单示例只有一个级别，但 IoT 解决方案通常具有多个嵌套级别，作用是让标记在组织中所处的物理和语义位置上得到语境化的体现。
选择“层次结构”，然后选择“添加层次结构” 。 对于名称，请输入“设备组”。 创建一个名为“设备名称”的级别。 再选择“保存”。
### <a name="assign-your-instances-to-the-correct-type"></a>为实例分配正确的类型
接下来将更改实例的类型，并将其置于层次结构中。
选择“实例”选项卡。找到表示设备工作集的实例，然后选择最右侧的“编辑”图标。
打开“类型”下拉菜单，然后选择“温度控制器” 。 输入 defaultComponent <your device name>，更新表示与设备关联的所有顶级标记的实例名称。
在选择“保存”之前，首先选择“实例字段”选项卡，然后选择“设备组” 。 若要将遥测组合在一起，请输入 \<your device name> - 温度控制器。 再选择“保存”。
重复上述步骤，为恒温器标记分配正确的类型和层次结构。
## <a name="view-your-data"></a>查看数据
返回到图表绘制窗格，并展开“设备组”> 你的设备。 选择“thermostat1”，选择“温度”变量，然后选择“添加”，为值绘图 。 对 thermostat2 和 defaultComponent workingSet 值执行相同的操作 。
## <a name="clean-up-resources"></a>清理资源
[!INCLUDE [iot-pnp-clean-resources](../../includes/iot-pnp-clean-resources.md)]
## <a name="next-steps"></a>后续步骤
> [!div class="nextstepaction"]
> 若要详细了解各种图表绘制选项，包括间隔大小调整和 y 轴控件，请参阅 [Azure 时序见解资源管理器](../time-series-insights/concepts-ux-panels.md)。
| 36.436975 | 287 | 0.719096 | yue_Hant | 0.460161 |
6f9d46ceae4250dc8e9423f7a220730d79eb062b | 121 | md | Markdown | index.md | JoshuaKarki27/github-pages-with-jekyll | f5957fe9640206bc4af6f6f4b2bdb3f2d1a47596 | [
"MIT"
] | null | null | null | index.md | JoshuaKarki27/github-pages-with-jekyll | f5957fe9640206bc4af6f6f4b2bdb3f2d1a47596 | [
"MIT"
] | 4 | 2022-02-09T00:16:06.000Z | 2022-02-09T05:04:35.000Z | index.md | JoshuaKarki27/github-pages-with-jekyll | f5957fe9640206bc4af6f6f4b2bdb3f2d1a47596 | [
"MIT"
] | null | null | null | ---
Joshua Karki: "Welcome to my blog"
---
I'm glad you are here. I plan to talk about my past experience and projects!
| 20.166667 | 76 | 0.702479 | eng_Latn | 0.998909 |
6f9db192f588c72ab20018fa03818fb1009752aa | 835 | md | Markdown | docs/dns/list-of-dns-record-types.md | inservio/internship | 206f7b29b25d83fa0cd9e23db9f09b7c7c44dd9e | [
"MIT"
] | 2 | 2018-10-24T09:36:44.000Z | 2018-10-30T18:32:49.000Z | docs/dns/list-of-dns-record-types.md | inservio/internship | 206f7b29b25d83fa0cd9e23db9f09b7c7c44dd9e | [
"MIT"
] | null | null | null | docs/dns/list-of-dns-record-types.md | inservio/internship | 206f7b29b25d83fa0cd9e23db9f09b7c7c44dd9e | [
"MIT"
] | null | null | null | ---
layout: default
title: List of DNS record types
parent: DNS
permalink: /docs/dns/list-of-dns-record-types/
---
# Introduction
List of DNS record types
The list of DNS record types is an overview of resource records (RRs) permissible in zone files of the Domain Name System (DNS).
### Resource records:
* A (Address record) - Returns a 32 bit IPv4 address, most commonly used to map hostnames to an IP address of the host.
* AAAA (IPv6 address record) - Returns a 128-bit IPv6 address, most commonly used to map hostnames to an IP address of the host.
* MX (Mail exchange record) - Maps a domain name to a list of message transfer agents for that domain.
* NS (Name server record) - Delegates a DNS zone to use the given authoritative name servers.
* TXT (Text record) - If we want to set the human-readable text in DNS record.
| 43.947368 | 128 | 0.749701 | eng_Latn | 0.982641 |
6f9db5c46faa414efafb9eb50eb68274ca740204 | 14,775 | md | Markdown | docs/mac/platform/opentk.md | sgbasaraner/xamarin-docs.tr-tr | 2980a6065aa6201b7f20a78d9920a9e961223e51 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/mac/platform/opentk.md | sgbasaraner/xamarin-docs.tr-tr | 2980a6065aa6201b7f20a78d9920a9e961223e51 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/mac/platform/opentk.md | sgbasaraner/xamarin-docs.tr-tr | 2980a6065aa6201b7f20a78d9920a9e961223e51 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Opentk'ya giriş Xamarin.Mac içinde
description: Bu makalede bir Xamarin.Mac uygulamasında OpenTK ile çalışmak için bir giriş sağlar. Oluşturma ve bir oyun penceresi bakımı, basit bir nesne oluşturma ve nesne kullanıcıya görüntüleme ele alınmaktadır.
ms.prod: xamarin
ms.assetid: BDE05645-7273-49D3-809B-8642347678D2
ms.technology: xamarin-mac
author: bradumbaugh
ms.author: brumbaug
ms.date: 03/14/2017
ms.openlocfilehash: 02cd32ac3016a3556cac8611ff839336f3089235
ms.sourcegitcommit: 47709db4d115d221e97f18bc8111c95723f6cb9b
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 08/13/2018
ms.locfileid: "43780644"
---
# <a name="introduction-to-opentk-in-xamarinmac"></a>Opentk'ya giriş Xamarin.Mac içinde
OpenTK (açık araç seti), OpenGL ve OpenCL OpenAL ile çalışmayı kolaylaştırır bir Gelişmiş, alt düzey C# kitaplıktır. OpenTK kullanılabilir oyunları, Bilimsel uygulamalar veya diğer 3B grafik gerektiren projeler, ses veya hesaplama işlevselliği için. Bu makalede, OpenTK bir Xamarin.Mac uygulamasını kullanarak kısa bir giriş sağlar.
[](opentk-images/intro01.png#lightbox)
Bu makalede, biz bir Xamarin.Mac uygulamasını OpenTK temellerini ele alacağız. Aracılığıyla iş önerilen [Merhaba, Mac](~/mac/get-started/hello-mac.md) makale önce özellikle [Xcode ve arabirim Oluşturucu giriş](~/mac/get-started/hello-mac.md#introduction-to-xcode-and-interface-builder) ve [çıkışlar ve eylemleri](~/mac/get-started/hello-mac.md#outlets-and-actions) olarak bölümlerde temel kavramları ve bu makalede kullanacağız tekniklerini ele alınmaktadır.
Bir göz atın isteyebilirsiniz [gösterme C# sınıfları / Objective-C yöntemlere](~/mac/internals/how-it-works.md) bölümünü [Xamarin.Mac iç işlevleri](~/mac/internals/how-it-works.md) de açıklar belge `Register` ve `Export` komutları Objective-C nesneleri ve kullanıcı Arabirimi öğeleri için C# sınıfları kablo-yedekleme kullanılır.
<a name="About_OpenTK" />
## <a name="about-opentk"></a>OpenTK hakkında
Yukarıda belirtildiği gibi OpenTK (açık araç seti), OpenGL ve OpenCL OpenAL ile çalışmayı kolaylaştırır bir Gelişmiş, alt düzey C# kitaplıktır. OpenTK bir Xamarin.Mac uygulamasını kullanarak aşağıdaki özellikleri sağlar:
- **Hızlı geliştirme** -OpenTK kodlama iş akışınızı artırmak ve hataları daha kolay ve daha çabuk yakalamak için güçlü veri türleri ve satır içi belgeler sağlar.
- **Kolay tümleştirme** -OpenTK kolayca .NET uygulamalarıyla tümleştirmek için tasarlanmıştır.
- **İhtiyari lisansı** -OpenTK MIT/X11 lisans altında dağıtılan ve tamamen ücretsizdir.
- **Zengin, tür kullanımı uyumlu bağlamaları** -OpenTK OpenGL OpenGL en son sürümlerini destekler | ES, OpenAL ve OpenCL otomatik uzantı yükleme ile hata denetleme ve satır içi belgeler.
- **Esnek GUI seçenekleri** -yüksek performanslı oyun penceresi özellikle oyunlar ve Xamarin.Mac için tasarlanmış, OpenTK yerel sağlar.
- **Tam olarak yönetilen, CLS uyumlu kod** -OpenTK herhangi bir yönetilmeyen kitaplığı ile macOS 32-bit ve 64 bit sürümlerini destekler.
- **3B matematik Araç Seti** OpenTK sağlayan `Vector`, `Matrix`, `Quaternion` ve `Bezier` yapılar, 3B matematik araç seti ile.
OpenTK kullanılabilir oyunları, Bilimsel uygulamalar veya diğer 3B grafik gerektiren projeler, ses veya hesaplama işlevselliği için.
Daha fazla bilgi için lütfen bkz [açık Araç Seti](http://www.opentk.com) Web sitesi.
<a name="OpenTK_Quickstart" />
## <a name="opentk-quickstart"></a>OpenTK hızlı başlangıç
Bir Xamarin.Mac uygulamasını OpenTK kullanarak hızlı bir giriş, bir oyun görünümü açar, bu üçgen kullanıcıya göstermek için Mac uygulamanın ana penceresi için basit bir üçgen bu görünümünde ve attachs Game görünümü işleyen bir uygulama oluşturmak için kullanacağız.
<a name="Starting_a_New_Project" />
### <a name="starting-a-new-project"></a>Yeni bir projeye Başlarken
Mac için Visual Studio'yu başlatın ve yeni bir Xamarin.Mac çözümü oluşturun. Seçin **Mac** > **uygulama** > **genel** > **Cocoa uygulaması**:
[](opentk-images/sample01.png#lightbox)
Girin `MacOpenTK` için **proje adı**:
[](opentk-images/sample02.png#lightbox)
Tıklayın **Oluştur** yeni projeyi oluşturmak için düğme.
<a name="Including_OpenTK" />
### <a name="including-opentk"></a>OpenTK dahil
Bir Xamarin.Mac uygulamasında açık j kullanmadan önce OpenTK derlemesine bir başvuru eklemeniz gerekir. İçinde **Çözüm Gezgini**, sağ **başvuruları** klasörü ve select **başvuruları Düzenle...** .
Tarafından işaretleyin `OpenTK` tıklatıp **Tamam** düğmesi:
[](opentk-images/sample03.png#lightbox)
<a name="Using_OpenTK" />
### <a name="using-opentk"></a>OpenTK kullanma
Oluşturulan yeni proje ile çift `MainWindow.cs` dosyası **Çözüm Gezgini** düzenlemek üzere açın. Olun `MainWindow` sınıfı görünüm aşağıdaki gibi:
```csharp
using System;
using System.Drawing;
using OpenTK;
using OpenTK.Graphics;
using OpenTK.Graphics.OpenGL;
using OpenTK.Platform.MacOS;
using Foundation;
using AppKit;
using CoreGraphics;
namespace MacOpenTK
{
public partial class MainWindow : NSWindow
{
#region Computed Properties
public MonoMacGameView Game { get; set; }
#endregion
#region Constructors
public MainWindow (IntPtr handle) : base (handle)
{
}
[Export ("initWithCoder:")]
public MainWindow (NSCoder coder) : base (coder)
{
}
#endregion
#region Override Methods
public override void AwakeFromNib ()
{
base.AwakeFromNib ();
// Create new Game View and replace the window content with it
Game = new MonoMacGameView(ContentView.Frame);
ContentView = Game;
// Wire-up any required Game events
Game.Load += (sender, e) =>
{
// TODO: Initialize settings, load textures and sounds here
};
Game.Resize += (sender, e) =>
{
// Adjust the GL view to be the same size as the window
GL.Viewport(0, 0, Game.Size.Width, Game.Size.Height);
};
Game.UpdateFrame += (sender, e) =>
{
// TODO: Add any game logic or physics
};
Game.RenderFrame += (sender, e) =>
{
// Setup buffer
GL.Clear(ClearBufferMask.ColorBufferBit | ClearBufferMask.DepthBufferBit);
GL.MatrixMode(MatrixMode.Projection);
// Draw a simple triangle
GL.LoadIdentity();
GL.Ortho(-1.0, 1.0, -1.0, 1.0, 0.0, 4.0);
GL.Begin(BeginMode.Triangles);
GL.Color3(Color.MidnightBlue);
GL.Vertex2(-1.0f, 1.0f);
GL.Color3(Color.SpringGreen);
GL.Vertex2(0.0f, -1.0f);
GL.Color3(Color.Ivory);
GL.Vertex2(1.0f, 1.0f);
GL.End();
};
// Run the game at 60 updates per second
Game.Run(60.0);
}
#endregion
}
}
```
Şimdi bu kodu aşağıda ayrıntılı olarak inceleyeceğiz.
<a name="Required_APIs" />
### <a name="required-apis"></a>Gerekli API
Birkaç başvuruları, OpenTK Xamarin.Mac sınıfında kullanmak için gereklidir. Şunları ekledik tanımının başında `using` ifadeleri:
```csharp
using System;
using System.Drawing;
using OpenTK;
using OpenTK.Graphics;
using OpenTK.Graphics.OpenGL;
using OpenTK.Platform.MacOS;
using Foundation;
using CoreGraphics;
```
Bu küçük grup OpenTK kullanarak herhangi bir sınıf için gerekli olacaktır.
<a name="Adding_the_Game_View" />
### <a name="adding-the-game-view"></a>Oyun görünüm ekleme
Ardından biz OpenTK bizim etkileşime içerir ve sonuçları görüntülemek için bir oyun görünüm oluşturmanız gerekir. Aşağıdaki kod kullandık:
```csharp
public MonoMacGameView Game { get; set; }
...
// Create new Game View and replace the window content with it
Game = new MonoMacGameView(ContentView.Frame);
ContentView = Game;
```
Oyun görünümü bizim ana penceresinde aynı boyutta burada yaptık ve yeni içerik görünümü penceresinin yerini `MonoMacGameView`. Biz varolan pencere içeriğinin değiştirilmiş olduğundan, Main Windows yeniden boyutlandırıldığında bizim verdiğiniz görünümü otomatik olarak boyutlandırılır.
<a name="Responding_to_Events" />
### <a name="responding-to-events"></a>Olaylarına yanıt verme
Her oyunun görünümü yanıt vermesi gereken birkaç varsayılan olaylar vardır. Bu bölümde, gereken ana olayları ele alınacaktır.
<a name="The_Load_Event" />
### <a name="the-load-event"></a>Yükleme olayı
`Load` Olay, sistemi, disk görüntüleri, doku ya da müzik gibi kaynakları bileşiminin yükleneceği yerdir. Basit, test uygulaması için değil kullanıyoruz `Load` olay, ancak başvuru için dahil:
```csharp
Game.Load += (sender, e) =>
{
// TODO: Initialize settings, load textures and sounds here
};
```
<a name="The_Resize_Event" />
### <a name="the-resize-event"></a>Yeniden Boyutlandır olayını
`Resize` Game görünümü yeniden boyutlandırıldı her zaman olay'nin çağrılabilir. Örnek uygulamamız için GL görünüm penceresinin (Bu Mac ana pencere tarafından yeniden boyutlandırılmış otomatik olarak) bizim oyun görünüm olarak aynı boyutta aşağıdaki kodla yapıyoruz:
```csharp
Game.Resize += (sender, e) =>
{
// Adjust the GL view to be the same size as the window
GL.Viewport(0, 0, Game.Size.Width, Game.Size.Height);
};
```
<a name="The_UpdateFrame_Event" />
### <a name="the-updateframe-event"></a>UpdateFrame olay
`UpdateFrame` Olay kullanıcı girişlerini işler, nesne konumları, çalışma fizik veya AI hesaplamalar güncelleştirmek için kullanılır. Basit, test uygulaması için değil kullanıyoruz `UpdateFrame` olay, ancak başvuru için dahil:
```csharp
Game.UpdateFrame += (sender, e) =>
{
// TODO: Add any game logic or physics
};
```
> [!IMPORTANT]
> Xamarin.Mac uygulamasını OpenTK içermemesi `Input API`, klavye eklemek için API'ler ve fare desteği sağlanan Apple kullanmanız gerekecektir. İsteğe bağlı olarak özel bir örneğini oluşturabilirsiniz `MonoMacGameView` ve geçersiz kılma `KeyDown` ve `KeyUp` yöntemleri.
<a name="The_RenderFrame_Event" />
### <a name="the-renderframe-event"></a>RenderFrame olay
`RenderFrame` Olay içeriyor (çizim) işlemek için kullanılan kod, bir grafik. Örnek uygulamamız için biz oyun görünümü ile basit bir üçgen dolduruyor:
```csharp
Game.RenderFrame += (sender, e) =>
{
// Setup buffer
GL.Clear(ClearBufferMask.ColorBufferBit | ClearBufferMask.DepthBufferBit);
GL.MatrixMode(MatrixMode.Projection);
// Draw a simple triangle
GL.LoadIdentity();
GL.Ortho(-1.0, 1.0, -1.0, 1.0, 0.0, 4.0);
GL.Begin(BeginMode.Triangles);
GL.Color3(Color.MidnightBlue);
GL.Vertex2(-1.0f, 1.0f);
GL.Color3(Color.SpringGreen);
GL.Vertex2(0.0f, -1.0f);
GL.Color3(Color.Ivory);
GL.Vertex2(1.0f, 1.0f);
GL.End();
};
```
Genellikle işleme kod size çağrısıyla durdurulmasını `GL.Clear` var olan öğeleri kaldırmak için önce çizilmiş yeni öğeler.
> [!IMPORTANT]
> OpenTK Xamarin.Mac sürümü için **olmayan** çağrı `SwapBuffers` yöntemi, `MonoMacGameView` işleme kodunuzu sonundaki örneği. Bunun yapılması, işlenmiş görünümde görüntüleniyor yerine hızlı bir şekilde strobe oyun görünüme neden olur.
<a name="Running_the_Game_View" />
### <a name="running-the-game-view"></a>Oyun görünümü çalışmasını
Tüm gerekli olayları tanımlayın ve oyun görünümü uygulamamızı ana Mac penceresine bağlı, oyun görünümü çalıştırmak ve bizim grafikleri görüntülemek için okunduğu. Aşağıdaki kodu kullanın:
```csharp
// Run the game at 60 updates per second
Game.Run(60.0);
```
Biz istenen kare hızı oyun görünüm güncelleştirmeyi istediğimiz geçmek için Bizim örneğimizde seçtik `60` kare / saniye (normal TV olarak aynı yenileme hızı).
Şimdi uygulamamıza çalıştırın ve çıktıyı görürsünüz:
[](opentk-images/intro01.png#lightbox)
Size sunduğumuz penceresini yeniden boyutlandırırsanız, oyun görünümü bulunur ve bu üçgen yeniden boyutlandırıldı ve gerçek zamanlı güncelleştirme de aynı zamanda olacaktır.
<a name="Where_to_Next" />
### <a name="where-to-next"></a>Sonrakine Git nerede?
Bitti Xamarin.mac uygulamada OpenTk ile çalışmanın temelleri ile sonraki denemeye ne bazı öneriler şunlardır:
- Bu üçgen rengini ve arka plan rengi oyun görünümünde değiştirmeyi deneyin `Load` ve `RenderFrame` olayları.
- Kullanıcı bir anahtar olarak bastığınızda rengini değiştirmek üçgen olun `UpdateFrame` ve `RenderFrame` olayları veya kendi özel `MonoMacGameView` sınıf ve geçersiz kılma `KeyUp` ve `KeyDown` yöntemleri.
- Üçgen kullanan anahtarları kullanarak ekranı arasında geçiş yapmak `UpdateFrame` olay. : İpucu `Matrix4.CreateTranslation` çeviri matris ve çağrı yöntemini `GL.LoadMatrix` yöntemi içinde yüklenecek `RenderFrame` olay.
- Kullanım bir `for` Birkaç üçgenler işlenecek döngü `RenderFrame` olay.
- Bu üçgen 3B alanda farklı bir görünümünü sağlamak için kamerayı döndür. : İpucu `Matrix4.CreateTranslation` çeviri matris ve çağrı yöntemini `GL.LoadMatrix` yüklemek için yöntemi. Ayrıca `Vector2`, `Vector3`, `Vector4` ve `Matrix4` kamera işlemeleri sınıfları.
Daha fazla örnek için bkz. Lütfen [OpenTK örnekleri GitHub](https://github.com/opentk/opentk/tree/master/Source/Examples) depo. Bu, OpenTK kullanma örnekleri resmi bir listesini içerir. Bu örnekler, OpenTK Xamarin.Mac sürümüyle kullanmak için uyum zorunda kalırsınız.
Lütfen için daha karmaşık bir Xamarin.Mac örnek, OpenTK uygulaması, bakın bizim [MonoMacGameView](https://developer.xamarin.com/samples/mac/MonoMacGameWindow/) örnek.
<a name="Summary" />
## <a name="summary"></a>Özet
Bu makalede bir Xamarin.Mac uygulamasında OpenTK ile çalışma Hızlı Bakış duruma getirdi. Bir oyun penceresi oluşturma gördüğümüz nasıl oyun penceresi için bir Mac pencere ekleme ve oyun penceresinde basit şekil işlemek nasıl.
## <a name="related-links"></a>İlgili bağlantılar
- [MacOpenTK (örnek)](https://developer.xamarin.com/samples/mac/MacOpenTK/)
- [MonoMacGameView (örnek)](https://developer.xamarin.com/samples/mac/MonoMacGameWindow/)
- [Hello, Mac](~/mac/get-started/hello-mac.md)
- [Windows ile çalışma](~/mac/user-interface/window.md)
- [Açık Araç Seti](http://www.opentk.com)
- [OS X İnsan Arabirimi yönergelerine](https://developer.apple.com/library/mac/documentation/UserExperience/Conceptual/OSXHIGuidelines/)
- [Windows giriş](https://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/WinPanel/Introduction.html#//apple_ref/doc/uid/10000031-SW1)
| 44.236527 | 458 | 0.737462 | tur_Latn | 0.998396 |
6f9dc6a9a5132bdac9c885c5e3894f0910561ba8 | 30,697 | md | Markdown | docs/_api/NetworkingManager.md | Vyxlose/MLAPI | 69669626b3fbea7c8740f5f2ec0b0cb462115780 | [
"MIT"
] | 1 | 2019-01-31T19:54:48.000Z | 2019-01-31T19:54:48.000Z | docs/_api/NetworkingManager.md | Vyxlose/MLAPI | 69669626b3fbea7c8740f5f2ec0b0cb462115780 | [
"MIT"
] | null | null | null | docs/_api/NetworkingManager.md | Vyxlose/MLAPI | 69669626b3fbea7c8740f5f2ec0b0cb462115780 | [
"MIT"
] | null | null | null | ---
title: NetworkingManager
permalink: /api/networking-manager/
---
<div style="line-height: 1;">
<h2 markdown="1">NetworkingManager ``class``</h2>
<p style="font-size: 20px;"><b>Namespace:</b> MLAPI</p>
<p style="font-size: 20px;"><b>Assembly:</b> MLAPI.dll</p>
</div>
<p>The main component of the library</p>
<div>
<h3 markdown="1">Public Properties</h3>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``float`` NetworkTime { get; set; }</b></h4>
<p>A syncronized time, represents the time in seconds since the server application started. Is replicated across all clients</p>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public [``NetworkingManager``](/MLAPI/api/networking-manager/) singleton { get; }</b></h4>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public [``NetworkingManager``](/MLAPI/api/networking-manager/) Singleton { get; set; }</b></h4>
<p>The singleton instance of the NetworkingManager</p>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``uint`` ServerClientId { get; }</b></h4>
<p>Gets the networkId of the server</p>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``uint`` LocalClientId { get; set; }</b></h4>
<p>The clientId the server calls the local client by, only valid for clients</p>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``bool`` isServer { get; }</b></h4>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``bool`` IsServer { get; set; }</b></h4>
<p>Gets wheter or not a server is running</p>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``bool`` isClient { get; }</b></h4>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``bool`` IsClient { get; set; }</b></h4>
<p>Gets wheter or not a client is running</p>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``bool`` isHost { get; }</b></h4>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``bool`` IsHost { get; }</b></h4>
<p>Gets if we are running as host</p>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``bool`` isListening { get; }</b></h4>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``bool`` IsListening { get; set; }</b></h4>
<p>Gets wheter or not we are listening for connections</p>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``bool`` isConnectedClients { get; }</b></h4>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``bool`` IsConnectedClient { get; set; }</b></h4>
<p>Gets if we are connected as a client</p>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``string`` ConnectedHostname { get; set; }</b></h4>
<p>The current hostname we are connected to, used to validate certificate</p>
</div>
</div>
<br>
<div>
<h3 markdown="1">Inherited Properties</h3>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``bool`` useGUILayout { get; set; }</b></h4>
<h5 markdown="1">Inherited from: ``MonoBehaviour``</h5>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``bool`` runInEditMode { get; set; }</b></h4>
<h5 markdown="1">Inherited from: ``MonoBehaviour``</h5>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``bool`` enabled { get; set; }</b></h4>
<h5 markdown="1">Inherited from: ``Behaviour``</h5>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``bool`` isActiveAndEnabled { get; }</b></h4>
<h5 markdown="1">Inherited from: ``Behaviour``</h5>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Transform`` transform { get; }</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``GameObject`` gameObject { get; }</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``string`` tag { get; set; }</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Component`` rigidbody { get; }</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Component`` rigidbody2D { get; }</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Component`` camera { get; }</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Component`` light { get; }</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Component`` animation { get; }</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Component`` constantForce { get; }</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Component`` renderer { get; }</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Component`` audio { get; }</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Component`` guiText { get; }</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Component`` networkView { get; }</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Component`` guiElement { get; }</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Component`` guiTexture { get; }</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Component`` collider { get; }</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Component`` collider2D { get; }</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Component`` hingeJoint { get; }</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Component`` particleEmitter { get; }</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Component`` particleSystem { get; }</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``string`` name { get; set; }</b></h4>
<h5 markdown="1">Inherited from: ``Object``</h5>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``HideFlags`` hideFlags { get; set; }</b></h4>
<h5 markdown="1">Inherited from: ``Object``</h5>
</div>
</div>
<br>
<div>
<h3 markdown="1">Public Fields</h3>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``bool`` DontDestroy;</b></h4>
<p>Gets or sets if the NetworkingManager should be marked as DontDestroyOnLoad</p>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``bool`` RunInBackground;</b></h4>
<p>Gets or sets if the application should be set to run in background</p>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public [``LogLevel``](/MLAPI/api/log-level/) LogLevel;</b></h4>
<p>The log level to use</p>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Dictionary<uint, NetworkedClient>`` ConnectedClients;</b></h4>
<p>Gets a dictionary of connected clients and their clientId keys</p>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``List<NetworkedClient>`` ConnectedClientsList;</b></h4>
<p>Gets a list of connected clients</p>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Dictionary<uint, PendingClient>`` PendingClients;</b></h4>
<p>Gets a dictionary of the clients that have been accepted by the transport but are still pending by the MLAPI.</p>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Action<uint>`` OnClientConnectedCallback;</b></h4>
<p>The callback to invoke once a client connects</p>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Action<uint>`` OnClientDisconnectCallback;</b></h4>
<p>The callback to invoke when a client disconnects</p>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Action`` OnServerStarted;</b></h4>
<p>The callback to invoke once the server is ready</p>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Action<byte[], uint, ConnectionApprovedDelegate>`` ConnectionApprovalCallback;</b></h4>
<p>The callback to invoke during connection approval</p>
</div>
<div style="line-height: 1;">
<h4 markdown="1"><b>public [``NetworkConfig``](/MLAPI/api/network-config/) NetworkConfig;</b></h4>
<p>The current NetworkingConfiguration</p>
</div>
</div>
<br>
<div>
<h3>Public Constructors</h3>
<div style="line-height: 1; ">
<h4 markdown="1"><b>public [``NetworkingManager``](/MLAPI/api/networking-manager/)();</b></h4>
</div>
</div>
<br>
<div>
<h3 markdown="1">Public Methods</h3>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` SendCustomMessage(``List<uint>`` clientIds, [``BitStream``](/MLAPI/api/bit-stream/) stream, ``string`` channel);</b></h4>
<p>Sends custom message to a list of clients</p>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``List<uint>`` clientIds</p>
<p>The clients to send to, sends to everyone if null</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">[``BitStream``](/MLAPI/api/bit-stream/) stream</p>
<p>The message stream containing the data</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``string`` channel</p>
<p>The channel to send the data on</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` SendCustomMessage(``uint`` clientId, [``BitStream``](/MLAPI/api/bit-stream/) stream, ``string`` channel);</b></h4>
<p>Sends a custom message to a specific client</p>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``uint`` clientId</p>
<p>The client to send the message to</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">[``BitStream``](/MLAPI/api/bit-stream/) stream</p>
<p>The message stream containing the data</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``string`` channel</p>
<p>The channel tos end the data on</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` StartServer();</b></h4>
<p>Starts a server</p>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` StartClient();</b></h4>
<p>Starts a client</p>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` StopServer();</b></h4>
<p>Stops the running server</p>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` StopHost();</b></h4>
<p>Stops the running host</p>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` StopClient();</b></h4>
<p>Stops the running client</p>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` StartHost(``Nullable<Vector3>`` pos, ``Nullable<Quaternion>`` rot, ``int`` prefabId);</b></h4>
<p>Starts a Host</p>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``Nullable<Vector3>`` pos</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``Nullable<Quaternion>`` rot</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``int`` prefabId</p>
</div>
</div>
<br>
</div>
<br>
<div>
<h3 markdown="1">Inherited Methods</h3>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``bool`` IsInvoking();</b></h4>
<h5 markdown="1">Inherited from: ``MonoBehaviour``</h5>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` CancelInvoke();</b></h4>
<h5 markdown="1">Inherited from: ``MonoBehaviour``</h5>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` Invoke(``string`` methodName, ``float`` time);</b></h4>
<h5 markdown="1">Inherited from: ``MonoBehaviour``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``string`` methodName</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``float`` time</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` InvokeRepeating(``string`` methodName, ``float`` time, ``float`` repeatRate);</b></h4>
<h5 markdown="1">Inherited from: ``MonoBehaviour``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``string`` methodName</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``float`` time</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``float`` repeatRate</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` CancelInvoke(``string`` methodName);</b></h4>
<h5 markdown="1">Inherited from: ``MonoBehaviour``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``string`` methodName</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``bool`` IsInvoking(``string`` methodName);</b></h4>
<h5 markdown="1">Inherited from: ``MonoBehaviour``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``string`` methodName</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Coroutine`` StartCoroutine(``string`` methodName);</b></h4>
<h5 markdown="1">Inherited from: ``MonoBehaviour``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``string`` methodName</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Coroutine`` StartCoroutine(``string`` methodName, ``object`` value);</b></h4>
<h5 markdown="1">Inherited from: ``MonoBehaviour``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``string`` methodName</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``object`` value</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Coroutine`` StartCoroutine(``IEnumerator`` routine);</b></h4>
<h5 markdown="1">Inherited from: ``MonoBehaviour``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``IEnumerator`` routine</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Coroutine`` StartCoroutine_Auto(``IEnumerator`` routine);</b></h4>
<h5 markdown="1">Inherited from: ``MonoBehaviour``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``IEnumerator`` routine</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` StopCoroutine(``IEnumerator`` routine);</b></h4>
<h5 markdown="1">Inherited from: ``MonoBehaviour``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``IEnumerator`` routine</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` StopCoroutine(``Coroutine`` routine);</b></h4>
<h5 markdown="1">Inherited from: ``MonoBehaviour``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``Coroutine`` routine</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` StopCoroutine(``string`` methodName);</b></h4>
<h5 markdown="1">Inherited from: ``MonoBehaviour``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``string`` methodName</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` StopAllCoroutines();</b></h4>
<h5 markdown="1">Inherited from: ``MonoBehaviour``</h5>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Component`` GetComponent(``Type`` type);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``Type`` type</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``T`` GetComponent();</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Component`` GetComponent(``string`` type);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``string`` type</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Component`` GetComponentInChildren(``Type`` t, ``bool`` includeInactive);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``Type`` t</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``bool`` includeInactive</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Component`` GetComponentInChildren(``Type`` t);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``Type`` t</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``T`` GetComponentInChildren(``bool`` includeInactive);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``bool`` includeInactive</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``T`` GetComponentInChildren();</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Component[]`` GetComponentsInChildren(``Type`` t, ``bool`` includeInactive);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``Type`` t</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``bool`` includeInactive</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Component[]`` GetComponentsInChildren(``Type`` t);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``Type`` t</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``T[]`` GetComponentsInChildren(``bool`` includeInactive);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``bool`` includeInactive</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` GetComponentsInChildren(``bool`` includeInactive, ``List<T>`` result);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``bool`` includeInactive</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``List<T>`` result</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``T[]`` GetComponentsInChildren();</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` GetComponentsInChildren(``List<T>`` results);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``List<T>`` results</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Component`` GetComponentInParent(``Type`` t);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``Type`` t</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``T`` GetComponentInParent();</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Component[]`` GetComponentsInParent(``Type`` t, ``bool`` includeInactive);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``Type`` t</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``bool`` includeInactive</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Component[]`` GetComponentsInParent(``Type`` t);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``Type`` t</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``T[]`` GetComponentsInParent(``bool`` includeInactive);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``bool`` includeInactive</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` GetComponentsInParent(``bool`` includeInactive, ``List<T>`` results);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``bool`` includeInactive</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``List<T>`` results</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``T[]`` GetComponentsInParent();</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Component[]`` GetComponents(``Type`` type);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``Type`` type</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` GetComponents(``Type`` type, ``List<Component>`` results);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``Type`` type</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``List<Component>`` results</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` GetComponents(``List<T>`` results);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``List<T>`` results</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``T[]`` GetComponents();</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``bool`` CompareTag(``string`` tag);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``string`` tag</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` SendMessageUpwards(``string`` methodName, ``object`` value, ``SendMessageOptions`` options);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``string`` methodName</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``object`` value</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``SendMessageOptions`` options</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` SendMessageUpwards(``string`` methodName, ``object`` value);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``string`` methodName</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``object`` value</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` SendMessageUpwards(``string`` methodName);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``string`` methodName</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` SendMessageUpwards(``string`` methodName, ``SendMessageOptions`` options);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``string`` methodName</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``SendMessageOptions`` options</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` SendMessage(``string`` methodName, ``object`` value);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``string`` methodName</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``object`` value</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` SendMessage(``string`` methodName);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``string`` methodName</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` SendMessage(``string`` methodName, ``object`` value, ``SendMessageOptions`` options);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``string`` methodName</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``object`` value</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``SendMessageOptions`` options</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` SendMessage(``string`` methodName, ``SendMessageOptions`` options);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``string`` methodName</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``SendMessageOptions`` options</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` BroadcastMessage(``string`` methodName, ``object`` parameter, ``SendMessageOptions`` options);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``string`` methodName</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``object`` parameter</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``SendMessageOptions`` options</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` BroadcastMessage(``string`` methodName, ``object`` parameter);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``string`` methodName</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``object`` parameter</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` BroadcastMessage(``string`` methodName);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``string`` methodName</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``void`` BroadcastMessage(``string`` methodName, ``SendMessageOptions`` options);</b></h4>
<h5 markdown="1">Inherited from: ``Component``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``string`` methodName</p>
</div>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``SendMessageOptions`` options</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``int`` GetInstanceID();</b></h4>
<h5 markdown="1">Inherited from: ``Object``</h5>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``int`` GetHashCode();</b></h4>
<h5 markdown="1">Inherited from: ``Object``</h5>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``bool`` Equals(``object`` other);</b></h4>
<h5 markdown="1">Inherited from: ``Object``</h5>
<h5><b>Parameters</b></h5>
<div>
<p style="font-size: 20px; color: #444;" markdown="1">``object`` other</p>
</div>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``string`` ToString();</b></h4>
<h5 markdown="1">Inherited from: ``Object``</h5>
</div>
<br>
<div style="line-height: 1;">
<h4 markdown="1"><b>public ``Type`` GetType();</b></h4>
<h5 markdown="1">Inherited from: ``object``</h5>
</div>
</div>
<br>
| 36.587604 | 159 | 0.606835 | eng_Latn | 0.207504 |