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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
d3b522da0af13bbab17f94d29f29bac99c00cb89 | 472 | md | Markdown | configs/tmux_config/README.md | xiaolitongxue666/script_tool_and_config | d542b0e3be1be79f902bb9edc9dad33dea9ddaee | [
"MIT"
] | null | null | null | configs/tmux_config/README.md | xiaolitongxue666/script_tool_and_config | d542b0e3be1be79f902bb9edc9dad33dea9ddaee | [
"MIT"
] | null | null | null | configs/tmux_config/README.md | xiaolitongxue666/script_tool_and_config | d542b0e3be1be79f902bb9edc9dad33dea9ddaee | [
"MIT"
] | null | null | null | # Tmux short key
- tmux : ``` <Ctrl + b> + s ``` : Show sessions list
- tmux : ``` <Ctrl + b> + d ``` : Detach session
- tmux : ``` <Ctrl + b> + a ``` : Attach seesion
- tmux : ``` <Ctrl + b> + <Ctrl + space> ``` : Change pane layout
- tmux : ``` <Ctrl + b> + <Ctrl + s> ``` : Plug save sessions
- tmux : ``` <Ctrl + b> + <Ctrl + r> ``` : Plug restre sessions
- terminal : ``` tmux ls ``` : Show all alice sessions
- terminal : ``` tmux kill-server ``` : Close sessions
| 42.909091 | 65 | 0.527542 | kor_Hang | 0.234631 |
d3b664921322f1c2f7c794d6cb0ec77b5a51dec6 | 1,315 | md | Markdown | site/src/main/tut/apis/scala/collection/immutable/scala.Product_productArity_-1245243894.md | marchub/scala-doc-microsite | ac2eb6b323d9da0dd0f6e582804bf3e0f102846a | [
"MIT"
] | null | null | null | site/src/main/tut/apis/scala/collection/immutable/scala.Product_productArity_-1245243894.md | marchub/scala-doc-microsite | ac2eb6b323d9da0dd0f6e582804bf3e0f102846a | [
"MIT"
] | null | null | null | site/src/main/tut/apis/scala/collection/immutable/scala.Product_productArity_-1245243894.md | marchub/scala-doc-microsite | ac2eb6b323d9da0dd0f6e582804bf3e0f102846a | [
"MIT"
] | null | null | null | //
<ol>
<li><a href="https://www.scala-lang.org/api/2.12.3/scala/collection/immutable/List.html#productArity:Int">scala.Product#productArity</a></li>
<li name="scala.Product#productArity" visbl="pub" class="indented0 " data-isabs="true" fullcomment="yes" group="Ungrouped"> <a id="productArity:Int"></a> <span class="permalink"> <a href="../../../scala/collection/immutable/List.html#productArity:Int" title="Permalink"> <i class="material-icons"></i> </a> </span> <span class="modifier_kind"> <span class="modifier">abstract </span> <span class="kind">def</span> </span> <span class="symbol"> <span class="name">productArity</span><span class="result">: <a href="../../Int.html" class="extype" name="scala.Int">Int</a></span> </span> <p class="shortcomment cmt">The size of this product.</p>
<div class="fullcomment">
<div class="comment cmt">
<p>The size of this product.</p>
</div>
<dl class="paramcmts block">
<dt>
returns
</dt>
<dd class="cmt">
<p>for a product <code>A(x<sub>1</sub>, ..., x<sub>k</sub>)</code>, returns <code>k</code></p>
</dd>
</dl>
<dl class="attributes block">
<dt>
Definition Classes
</dt>
<dd>
<a href="../../Product.html" class="extype" name="scala.Product">Product</a>
</dd>
</dl>
</div> </li>
</ol>
### Examples
| 39.848485 | 643 | 0.631939 | yue_Hant | 0.324572 |
d3b775c283c45f032a35a1d7d766e4c4637d24ba | 2,056 | md | Markdown | README.md | jackphillipsjmu/spring-boot-example | b7f2e3d5b20599ff6564a17b99383b1e8db1df37 | [
"MIT"
] | null | null | null | README.md | jackphillipsjmu/spring-boot-example | b7f2e3d5b20599ff6564a17b99383b1e8db1df37 | [
"MIT"
] | null | null | null | README.md | jackphillipsjmu/spring-boot-example | b7f2e3d5b20599ff6564a17b99383b1e8db1df37 | [
"MIT"
] | null | null | null | ## Spring Boot Example
Demo application developed to build knowledge surrounding Spring Boot and it's components
## Frameworks
### Front-end
#### Twitter Bootstrap
For rapidly creating prototypes of a web application, a UI toolkit or library will become really handy. There are many choices available, and for this example I chose Twitter Bootstrap.
#### AngularJS
AngularJS is a MVC based framework for web applications, written in JavaScript. It makes it possible to use the Model-View-Controller pattern on the front-end. It also comes with several additional modules. In this example I'm also using **angular-resource**, which is a simple factory-pattern based module for creating REST clients.
### Back-end
#### Spring Boot
One of the hassles while creating web applications using the Spring Framework is that it involves a lot of configuration. Spring Boot makes it possible to write configuration-less web application because it does a lot for you out of the box.
For example, if you add HSQLDB as a dependency to your application, it will automatically provide a datasource to it.
If you add the spring-boot-starter-web dependency, then you can start writing controllers for creating a web application.
#### Spring Data JPA
Spring Data JPA allows you to create repositories for your data without even having to write a lot of code. The only code you need is a simple interface that extends from another interface and then you're done.
With Spring Boot you can even leave the configuration behind for configuring Spring Data JPA, so now it's even easier.
## Installation
Installation is quite easy, first you will have to install some front-end dependencies using Bower:
```
bower install
```
Build the Gradle depencies
```
gradle clean build
```
Then you can run using Gradle
```
gradle bootRun
```
Or run the Application.java class from your IDE of choice
## Swagger
Once the Spring Boot application is running navigate to [localhost:8080/swagger-ui.html](http://localhost:8080/swagger-ui.html) to run API operations using the Swagger UI | 48.952381 | 333 | 0.788424 | eng_Latn | 0.997184 |
d3b791b35efa4589def955fefe1391654335df92 | 2,015 | md | Markdown | docs/framework/wpf/app-development/ienumrawinputdevice.md | AlejandraHM/docs.es-es | 5f5b056e12f9a0bcccbbbef5e183657d898b9324 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wpf/app-development/ienumrawinputdevice.md | AlejandraHM/docs.es-es | 5f5b056e12f9a0bcccbbbef5e183657d898b9324 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wpf/app-development/ienumrawinputdevice.md | AlejandraHM/docs.es-es | 5f5b056e12f9a0bcccbbbef5e183657d898b9324 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: IEnumRAWINPUTDEVICE
ms.date: 03/30/2017
helpviewer_keywords:
- IEnumRAWINPUTDEVICE interface [WPF]
ms.assetid: 88c8b389-a48b-46b9-b895-8ed7b1e26fea
ms.openlocfilehash: e465193d6a91848a27c2832dda454c6c45837e92
ms.sourcegitcommit: 6b308cf6d627d78ee36dbbae8972a310ac7fd6c8
ms.translationtype: MT
ms.contentlocale: es-ES
ms.lasthandoff: 01/23/2019
ms.locfileid: "54530030"
---
# <a name="ienumrawinputdevice"></a>IEnumRAWINPUTDEVICE
Esta interfaz enumera los dispositivos de entrada sin formato y solo la utiliza PresentationHost.exe.
> [!NOTE]
> Esta API solo está destinada y es compatible con el equipo cliente local
## <a name="members"></a>Miembros
|Miembro|Descripción|
|------------|-----------------|
|[IEnumRAWINPUTDEVIC:Next](../../../../docs/framework/wpf/app-development/ienumrawinputdevic-next.md)|Enumera los elementos `celt` siguientes (es decir, las estructuras RAWINPUTDEVICE) de la lista del enumerador y los devuelve en `rgelt` junto con el número real de elementos enumerados en `pceltFetched`.|
|[IEnumRAWINPUTDEVIC:Skip](../../../../docs/framework/wpf/app-development/ienumrawinputdevic-skip.md)|Indica al enumerador para omitir la próxima `celt` elementos de la enumeración para que la siguiente llamada a [IEnumRAWINPUTDEVIC:Next](../../../../docs/framework/wpf/app-development/ienumrawinputdevic-next.md) no devolverá los elementos.|
|[IEnumRAWINPUTDEVIC:Reset](../../../../docs/framework/wpf/app-development/ienumrawinputdevic-reset.md)|Restablece la secuencia de enumeración al principio.|
|[IEnumRAWINPUTDEVIC:Clone](../../../../docs/framework/wpf/app-development/ienumrawinputdevic-clone.md)|Crea otro enumerador de dispositivo de entrada sin formato con el mismo estado que el enumerador actual para crear una iteración por la misma lista.|
## <a name="see-also"></a>Vea también
- [Acerca de la entrada sin formato](https://msdn.microsoft.com/library/default.asp?url=/library/winui/winui/windowsuserinterface/userinput/rawinput/aboutrawinput.asp)
| 65 | 344 | 0.766749 | spa_Latn | 0.702368 |
d3b7ae822f9cd88aa9987105ea650dace7bfd667 | 2,590 | md | Markdown | _posts/2022-05-02-freecache.md | liamgheng/liamgheng.github.io | 928dff0d550784195132a8c8112163e0bcec5e17 | [
"MIT"
] | null | null | null | _posts/2022-05-02-freecache.md | liamgheng/liamgheng.github.io | 928dff0d550784195132a8c8112163e0bcec5e17 | [
"MIT"
] | null | null | null | _posts/2022-05-02-freecache.md | liamgheng/liamgheng.github.io | 928dff0d550784195132a8c8112163e0bcec5e17 | [
"MIT"
] | null | null | null | ---
layout: post
title: "FreeCache 源码分析"
description: ""
comments: true
keywords: "源码分析, Golang"
---
## 题外话
我从小学开始打了二十几年乒乓球了，但也总是瞎打，没有正规练过。最近上了一节 45min 的乒乓球体验课，教练帮我纠正了一直以来正手攻球的错误动作，纠正之后再和小伙伴打，命中率和质量有不错的提升。
这件事情给我的启发是专业 Coach 的作用，在很短的时间之内可以获得他人积累了几十年的经验，我想软件开发是否也是这样？
软件开发中也有 Coach，但我并非指培训班，而是各种源码。质量好的源码集中了世界各地高手的思考，阅读这些源码学习他人的设计思路，是非常好的学习途径。
## 源码分析
### 核心数据结构
- cache，代表一个固定大小的 cache 实例，分为 256 个 segment，分为多个 segment 主要目的是因为修改数据需要加锁，分为多个 segment 可以使用分片锁降低锁粒度从而提高性能。
- segment。
- 包括一个固定大小的 ringbuf 存储 kv，每个 kv 包含三部分：header（一些 key 附加信息，比如过期时间，最近访问时间等），key，value。
- 另外还有 slot 信息，每个 segment 分为 256 个 slot，之所以分 slot，原因是加快查询速度。如果都挤在一个 slot，则二分查找一个 key 时扫描的数据较多，并且为了可以二分查找，需要有个地方按照 key hash16 排列，如果都挤在一起，那么每次插入需要移动的数据量也大，所以再细分 slot 让 key 分散可以加快读的过程，代价是需要额外维护 slot 的信息（比如每个 slot 的长度），这也是空间换时间的一种思想。slot 是一个 []entryPtr，len 记录在 slotLens，cap 是 slotCap，这里设计也有意思，如果我来设计会为了避免空间浪费，会让 slot 的 cap 等于 len，不够了再扩容，但是问题是这样容易频繁分配内存，这里的实现是让所有 slot 的 cap 等于最大的 slotCap，额外花费一些空间来尽量避免重复分配内存（避免重复分配内存的优化在很多项目可以看到影子，比如 golang 的 stringbuilder，redis 的动态字符串）。
### Zero GC
如果运行期间在堆上创建太多的数据，则会增大 Golang GC 的负担。这里的实现中保证了无论存储多少 kv，只会创建 256 * 2 个指针，256 是因为有 256 个 segment，2 是每个 segment 需要 ringbuf 和 entryPtr 两个 slice 来分别存储 kv 数据和 slot 信息。
### 写实现
1. 对 key hash 之后得到 segmentId
2. 对 segment 加写锁，保证并发安全
3. 根据 key hash 得到 slotId，从 slotsData 中切片拿到 slot
4. 因为 slot 中按照 key hash 排列 key，所以可以二分查找来找到之前 key 是否存在，如果不存在，则：
1. 生成 header
2. 调用 seg.evacuate 方法确保 ringbuf 中有空间存放 kv（seg.evacuate 中细节较多，因为 ringbuf 要腾出空间，所以 slotsData 中记录的 key 在 ringbuf 中的偏移量也要改变）
3. 在 ringbuf 中写入 header，key，value
### 过期 key 删除策略
《Redis 设计与实现》9.5 总结了三种删除策略：
- 定时删除。在设置过期时间同时设置一个定时器，让定时器在 key 过期时间到达时对 key 执行删除。这样的优点是可以及时删除过期的 key，缺点是耗费 CPU。如果内存不紧张但是 CPU 紧张，则会对性能有影响。
- 惰性删除。放任过期的 key 不管，每次获取时检查是否过期，如果过期则删除。这样对 CPU 友好，但是对内存不友好，如果 key 过期了，但是一直没有读则 key 不会被删除从而浪费了内存。FreeCache 采用的这个方案。
- 定期删除。每隔一段时间，对数据库进行一次检查，删除过期 key。可以权衡 CPU 和内存，Redis 采用了这个方案。
FreeCache 除了采用惰性删除之外，还结合了标记删除。虽然过期 key 在 slot 里面真正删除了，但是在 ringbuf 中没有物理删除，而是把 key 的 header.deleted 标记为 True，只有当 ringbuf 中的空间不足以容纳新的 kv 才会物理删除。这样可以降低 ringbuf 和 slot 数据 copy 频率。
### 淘汰策略
LRU 策略。完整的 LRU 需要 hashmap 存储 value + 双向链表存储最近访问时间顺序来达到 O1 时间复杂度，但这样空间成本提高了，并且链表会在堆上产生较多数据增加 GC 压力。
所以工程中可以采用近似 LRU 算法。在 Redis 中，会随机选出 N 个 key，然后选择最久没访问的释放掉。虽然命中率不如完整的 LRU 策略，但是好在性能高，也是一种工程上的权衡。
FreeCache 的 LRU 实现也有意思：
``` golang
leastRecentUsed := int64(oldHdr.accessTime)*atomic.LoadInt64(&seg.totalCount) <= atomic.LoadInt64(&seg.totalTime)
```
如果 key 的最近获取时间比平均 key 的获取时间小，就可以淘汰了。
## 阅读源码使用的技巧
为了方便理解数据结构，尝试构造了几个场景：
- 修改源码把 segment 从 256 个缩小为 1 个，方便观察数据，slot 同理。
- 填满 ringbuf ，触发删除的场景。 | 39.242424 | 471 | 0.787259 | yue_Hant | 0.69673 |
d3b8dfaa817e86edc1ef804220477c79304df7ae | 4,002 | md | Markdown | src/content/posts/performance-review-remote-teams.md | 2betafactor/performance-reviews-software | dc98955d6f67cc13ccb30f369d61c5dfd66e3f0b | [
"MIT"
] | null | null | null | src/content/posts/performance-review-remote-teams.md | 2betafactor/performance-reviews-software | dc98955d6f67cc13ccb30f369d61c5dfd66e3f0b | [
"MIT"
] | null | null | null | src/content/posts/performance-review-remote-teams.md | 2betafactor/performance-reviews-software | dc98955d6f67cc13ccb30f369d61c5dfd66e3f0b | [
"MIT"
] | null | null | null | ---
template: blog-post
title: How to improve Performance Reviews for Remote Teams
slug: /performance-review-improvements/
date: 2021-03-19 12:46
description: With the increased reliance on remote teams, performance reviews
have become more important than ever.
featuredImage: /assets/best-practices-performance-reviews.JPG
---
[With the increased reliance on remote teams, performance reviews have become more important than ever.](https://hbr.org/2014/12/getting-virtual-teams-right) The key to a successful performance review process is to ensure that all employees are engaged and feel comfortable in the process. This is especially important for [remote workers who may feel disconnected from the organization.](https://www.flexjobs.com/employer-blog/signs-remote-employees-feel-isolated/)
## How to Improve Performance Reviews for Remote Teams
Here are some tips to make performance reviews successful for remote workers:
1. Use a software platform that allows you to manage your team’s performance reviews in one place.
2. Use a software platform that allows you to track employee performance against goals and objectives.
3. Use a software platform that allows you to schedule performance review meetings with team members.
4. Use a software platform that allows you to provide feedback both verbally and in writing.
5. Use a software platform that allows you to record and track employee progress over time.
6. Use a software platform that allows you to give feedback both verbally and in writing.
## Remote work and new ways of thinking
There is a silver lining to all of this, as remote working has opened up a new way of thinking about performance reviews. [Companies have been forced to think about how they can best ensure that they are reviewing their employees fairly and consistently.](https://hbr.org/2016/10/the-performance-management-revolution)
A good place to start is by having a clear understanding of the purpose of the performance review.
The purpose of the performance review is to provide feedback on the employee's performance, and to set performance targets for the next period. This feedback and these targets are used by the employee to improve their performance.
Performance reviews are not an opportunity for managers to give positive or negative feedback on an employee's personality or character, or for them to set targets that are unrealistic. It is important that managers keep these things in mind when they are reviewing their teams.
Another thing to consider is how much time should be spent on the performance review itself. It is important that managers don't let this meeting become a burden for them or their employees. As such, it is a good idea to keep the performance review as short as possible, and to make it easier for employees by allowing them to contribute to the review process.
For example, if an employee has been working from home over the past year, it would be a good idea for them to provide their manager with some examples of how they have been contributing to the company's goals from home. This will make it easier for their manager to write up their review, as well as make it easier for them to understand what they need to do in order to improve.
Employees can also benefit from being involved in setting their own performance targets. This will make it easier for them to understand what is expected of them, and will also help them feel more in control of their work life. However, it is important that managers do not give employees unrealistic targets, as this will only lead to disappointment and frustration.
The same logic applies when setting goals for remote workers in general. Managers should not set goals that assume that everyone works in an office environment, and remote workers should not be penalized if they work from home one day because they have childcare responsibilities. Instead, managers should work with remote workers to set goals that are relevant and achievable given their circumstances. | 102.615385 | 466 | 0.809595 | eng_Latn | 0.999884 |
d3b9a02a757eb3e96bb5eee4ab7a1fa7301acc8d | 7,866 | md | Markdown | README.md | victorvogelpoel/Serilog.Sinks.MFilesSysUtilsEventLog | ed6bed751875842ac89014cae57b6e0b9c6eeae7 | [
"Apache-2.0"
] | null | null | null | README.md | victorvogelpoel/Serilog.Sinks.MFilesSysUtilsEventLog | ed6bed751875842ac89014cae57b6e0b9c6eeae7 | [
"Apache-2.0"
] | null | null | null | README.md | victorvogelpoel/Serilog.Sinks.MFilesSysUtilsEventLog | ed6bed751875842ac89014cae57b6e0b9c6eeae7 | [
"Apache-2.0"
] | null | null | null | # Serilog.Sinks.MFilesSysUtilsEventLog
[](https://www.nuget.org/packages/Serilog.Sinks.MFilesSysUtilsEventLog)
A Serilog sink wrapper to write to the Windows EventLog using the SysUtils.ReportXToEventLog() in an M-Files Vault Application.
To use the sink, install the **Serilog.Sinks.MFilesSysUtilsEventLog nupkg** into your vault application solution; see below or browse to the [sample vault application code in this repository](samples/SampleVaultApplication/VaultApplication.cs) for pointers how to use it. And here is the nuget.org page for [Serilog.Sinks.MFilesSysUtilsEventLog](https://www.nuget.org/packages/Serilog.Sinks.MFilesSysUtilsEventLog/).
**IMPORTANT:** this sink can only be used in an M-Files Vault Application, as it uses the Vault Application Framework SysUtils.ReportXXXToEventLog() functions.
*Please note that this library is provided "as-is" and with no warranty, explicit or otherwise. You should ensure that the functionality meets your requirements, and thoroughly test them, prior to using in any production scenarios.*
## Use case
An vault application is an addon for an M-Files Vault which has been created using the [M-Files Vault Application Framework](https://developer.m-files.com/Frameworks/Vault-Application-Framework/).
The currently only supported way of logging is using the [SysUtils Event Log reporting helper](https://developer.m-files.com/Frameworks/Vault-Application-Framework/Helpers/SysUtils/#event-log-reporting).
The **Serilog.Sinks.MFilesSysUtilsEventLog** sink makes it possible to use *Serilog structured logging* in an M-Files vault application. For more information about Serilog, see [Serilog.net](https://serilog.net/) and [https://github.com/serilog/serilog](https://github.com/serilog/serilog).
```csharp
Log.Logger = new LoggerConfiguration()
.WriteTo.MFilesSysUtilsEventLogSink()
.CreateLogger();
Log.Information("Hello from the Vault Application");
```
## Dependencies
The Serilog.Sinks.MFilesSysUtilsEventLog sink uses [MFiles.VAF version 2.2.0.11](https://www.nuget.org/packages/MFiles.VAF/2.2.0.11) and [Serilog 2.10.0](https://www.nuget.org/packages/Serilog/2.10.0).
## How to add Serilog.Sinks.MFilesSysUtilsEventLog to your vault application
1. Open your vault application solution in Visual Studio and choose `Manage NuGet packages...`. Browse for package `Serilog.Sinks.MFilesSysUtilsEventLog` and add it to your solution.
1. Add `using Serilog;` at the top of your application class.
1. In your VaultApplication.cs class, override InitializeApplication(Vault vault) and add a logging configuration bulder, where you write to the `MFilesSysUtilsEventLogSink` (see below)
1. Add Serilog Log.xxx() statements in your vault application use case code. See [Serilog wiki](https://github.com/serilog/serilog/wiki/Writing-Log-Events) about writing log events.
The sample vault application in this repository uses the sink and even allows for changing the logging level in the vault application configuration in M-Files Admin.
## Example use in a Vault Application
```csharp
using Serilog;
namespace DemoVaultApplication
{
/// <summary>
/// The entry point for this Vault Application Framework application.
/// </summary>
/// <remarks>Examples and further information available on the developer portal: http://developer.m-files.com/. </remarks>
public class VaultApplication : ConfigurableVaultApplicationBase<Configuration>
{
protected override void InitializeApplication(Vault vault)
{
base.InitializeApplication(vault);
// Configure logging
Log.Logger = new LoggerConfiguration()
.WriteTo.MFilesSysUtilsEventLogSink()
.CreateLogger();
}
[EventHandler(MFEventHandlerType.MFEventHandlerBeforeCheckInChangesFinalize,
ObjectType = (int)MFBuiltInObjectType.MFBuiltInObjectTypeDocument)]
public void BeforeCheckInChangesFinalizeUpdateLogDemo(EventHandlerEnvironment env)
{
Log.Information("User {UserID} has checked in document {DisplayID} at {TimeStamp}",
env.CurrentUserID,
env.DisplayID,
DateTime.Now);
}
}
}
```
When a user checks in a document in the vault where the vault application is installed. the Log.Information statement will produce a Windows Event log entry similarly to below:
```text
DemoVault {D449E438-89EE-42BB-9769-B862E9B1B140}
DemoVaultApp 0.1 (Process ID: 35700)
----
User 1 has checked in document 1 at 05/29/2021 23:04:00
```
## Cloud vault
Your vault application can be installed on either a local M-Files server or on a cloud vault. With the local server, you'll have access to the Windows Event log and the logging from your application.
A cloud vault is operated by the M-Files CloudOps team and you do not have direct access to the Windows Event log on the (Azure) server where the vault runs. If you want your vault application's logging, you'll have to request it from M-Files support. It's hardly ideal, but at least you're using structured logging with Serilog in your application now!
I have another logging solution coming up that will help in logging scenarios in cloud vault application.
## Sample vault application
The sample vault application writes some log messages upon startup and with firing of the MFEventHandlerBeforeCheckInChangesFinalize event for an Document ObjectType.
It has not one but **two** MFilesSysUtilsEventLogSinks configured, one with the default output message template and the other with the RenderedCompactJsonFormatter which outputs the log event in *JSON format* to the Windows event log as well and shows *all* log event properties.
Because of the two sinks, the Windows Event Log will contain the **same** log event twice, but formatted differently. It demonstrates that a log pipeline can be build with multiple sinks, even the same sink with different parameters.
```text
// The FIRST will only show the log event message; the "MFEventType" property is not shown, because it is not part of the default message template.
// "User 33 has checked in document 506 at 06/01/2021 21:15:10"
```
```text
// The SECOND will show the JSON rendering of the log event, INCLUDING the "MFEventType" property that was added from the LogContext.
// {"@t":"2021-06-01T21:15:10.9941533Z","@m":"User 33 has checked in document 506 at 06/01/2021 21:15:10","@i":"5cf5a3bc","UserID":33,"DisplayID":506,,"TimeStamp":"2021-06-01T21:15:10.9931527+02:00"","MFEventType":"MFEventHandlerBeforeCheckInChangesFinalize"}
```
These screen shots are from the Windows Event log on a local M-Files server and from the M-Files Admin.
**Starting up: Logging something in vault initialization**
```csharp
// And log some information about this VaultApp
Log.Information("Starting up VaultApp {VaultAppName} build version {VaultAppBuildVersion} in vault {VaultName}",
thisVaultApp.Name,
_buildFileVersion,
vault.Name);
```
**Starting up: M-Files server has loaded sample vault application**
**Changing log level in M-Files Admin**
**Logging from event handler**
```csharp
Log.Information("User {UserID} has checked in document {DisplayID} at {TimeStamp}",
env.CurrentUserID,
env.DisplayID,
DateTime.Now);
```
| 53.510204 | 416 | 0.749428 | eng_Latn | 0.781994 |
d3ba286c80eb2c18da59c3a7ca35eb27d4209187 | 51,352 | md | Markdown | articles/event-hubs/security-baseline.md | Myhostings/azure-docs.tr-tr | 536eaf3b454f181f4948041d5c127e5d3c6c92cc | [
"CC-BY-4.0",
"MIT"
] | 16 | 2017-08-28T08:29:36.000Z | 2022-01-02T16:46:30.000Z | articles/event-hubs/security-baseline.md | Ahmetmaman/azure-docs.tr-tr | 536eaf3b454f181f4948041d5c127e5d3c6c92cc | [
"CC-BY-4.0",
"MIT"
] | 470 | 2017-11-11T20:59:16.000Z | 2021-04-10T17:06:28.000Z | articles/event-hubs/security-baseline.md | Ahmetmaman/azure-docs.tr-tr | 536eaf3b454f181f4948041d5c127e5d3c6c92cc | [
"CC-BY-4.0",
"MIT"
] | 25 | 2017-11-11T19:39:08.000Z | 2022-03-30T13:47:56.000Z | ---
title: Event Hubs için Azure Güvenlik temeli
description: Event Hubs güvenlik temeli, Azure Güvenlik kıyaslaması 'nda belirtilen güvenlik önerilerini uygulamaya yönelik yordamsal kılavuz ve kaynaklar sağlar.
author: msmbaldwin
ms.service: event-hubs
ms.topic: conceptual
ms.date: 02/17/2021
ms.author: mbaldwin
ms.custom: subject-security-benchmark
ms.openlocfilehash: 33417a9bda9ad4ce36dd6e14f74a53911f3c3473
ms.sourcegitcommit: 272351402a140422205ff50b59f80d3c6758f6f6
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 04/17/2021
ms.locfileid: "107587162"
---
# <a name="azure-security-baseline-for-event-hubs"></a>Event Hubs için Azure Güvenlik temeli
Bu güvenlik temeli, Event Hubs için [Azure Güvenlik kıyaslama sürüm 1,0](../security/benchmarks/overview-v1.md) ' den rehberlik uygular. Azure Güvenlik Karşılaştırması, Azure üzerindeki bulut çözümlerinizin güvenliğini sağlamaya yönelik öneriler sunar.
İçerik, Azure Güvenlik kıyaslaması tarafından tanımlanan **güvenlik denetimlerine** ve Event Hubs için geçerli olan ilgili kılavuza göre gruplandırılır. Event Hubs için geçerli olmayan **denetimler** dışlandı.
Event Hubs Azure Güvenlik kıyaslaması ile tamamen nasıl eşlendiğini görmek için, [tam Event Hubs güvenlik temeli eşleme dosyasına](https://github.com/MicrosoftDocs/SecurityBenchmarks/tree/master/Azure%20Offer%20Security%20Baselines)bakın.
## <a name="network-security"></a>Ağ Güvenliği
*Daha fazla bilgi için bkz. [Azure Güvenlik Karşılaştırması: Ağ Güvenliği](../security/benchmarks/security-control-network-security.md).*
### <a name="11-protect-azure-resources-within-virtual-networks"></a>1,1: sanal ağlar içindeki Azure kaynaklarını koruma
**Kılavuz**: Azure Event Hubs sanal ağ hizmet uç noktaları ile tümleştirme, sanal ağlara bağlı sanal makineler gibi iş yüklerinden gelen, her iki uçta da güvenli hale getirilen ağ trafiği yolu ile güvenli erişim olanağı sağlar.
En az bir sanal ağ alt ağ hizmeti uç noktasına bağlandıktan sonra, ilgili Event Hubs ad alanı artık trafiği sanal ağlardaki her yerden kabul etmez. Sanal ağ perspektifinden, Event Hubs ad alanınızı bir hizmet uç noktasına bağlamak, sanal ağ alt ağından mesajlaşma hizmetine yalıtılmış bir ağ tüneli yapılandırır.
Ayrıca, Azure özel bağlantı hizmeti 'ni kullanarak, hizmeti Event Hubs özel olarak ve güvenli bir şekilde bağlayan bir ağ arabirimi olan özel bir uç nokta da oluşturabilirsiniz. Özel uç nokta, sanal ağınızdan hizmeti etkin bir şekilde sanal ağınıza getiren özel bir IP adresi kullanır. Hizmete giden tüm trafik özel uç nokta aracılığıyla yönlendirilebilir, bu nedenle ağ geçitleri, NAT cihazları, ExpressRoute veya VPN bağlantıları ya da genel IP adresleri gerekmez.
Azure Event Hubs ad alanınızı güvenlik duvarları kullanarak da güvenli hale getirebilirsiniz. Event Hubs, gelen güvenlik duvarı desteği için IP tabanlı erişim denetimlerini destekler. Azure portal, Azure Resource Manager şablonlarını veya Azure CLı veya Azure PowerShell aracılığıyla güvenlik duvarı kuralları belirleyebilirsiniz.
- [Azure Event Hubs sanal ağ hizmet uç noktalarını kullanma](event-hubs-service-endpoints.md)
- [Azure Event Hubs Azure özel bağlantısı ile tümleştirme](private-link-service.md)
- [Azure Event Hubs ad alanları için IP güvenlik duvarı kurallarını yapılandırma](event-hubs-ip-filtering.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: [Azure Güvenlik kıyaslaması](/azure/governance/policy/samples/azure-security-benchmark) , Güvenlik Merkezi için varsayılan Ilke girişimidir ve [Güvenlik Merkezi 'nin önerilerine](/azure/security-center/security-center-recommendations)yöneliktir. Bu denetimle ilgili Azure Ilke tanımları, Güvenlik Merkezi tarafından otomatik olarak etkinleştirilir. Bu denetimle ilgili uyarılar, ilgili hizmetler için bir [Azure Defender](/azure/security-center/azure-defender) planı gerektirebilir.
**Azure ilkesi yerleşik tanımları-Microsoft. EventHub**:
[!INCLUDE [Resource Policy for Microsoft.EventHub 1.1](../../includes/policy/standards/asb/rp-controls/microsoft.eventhub-1-1.md)]
### <a name="12-monitor-and-log-the-configuration-and-traffic-of-virtual-networks-subnets-and-network-interfaces"></a>1,2: sanal ağların, alt ağların ve ağ arabirimlerinin yapılandırma ve trafiğini izleme ve günlüğe kaydetme
**Rehberlik**: Azure Güvenlik Merkezi 'ni kullanın ve azure 'daki Event Hubs kaynaklarınızın güvenliğini sağlamaya yardımcı olmak için ağ koruma önerilerini izleyin. Olay Hub 'larınızı erişmek için Azure sanal makineleri kullanıyorsanız, ağ güvenlik grubu akış günlüklerini etkinleştirin ve trafik denetimi için günlükleri bir depolama hesabına gönderin.
- [NSG akış günlüklerini etkinleştirme](../network-watcher/network-watcher-nsg-flow-logging-portal.md)
- [Azure Güvenlik Merkezi tarafından sunulan ağ güvenliğini anlama](../security-center/security-center-network-recommendations.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="14-deny-communications-with-known-malicious-ip-addresses"></a>1,4: bilinen kötü amaçlı IP adresleriyle iletişimleri reddetme
**Rehberlik**: dağıtılmış hizmet reddi (DDoS) saldırılarına karşı koruma sağlamak için, Olay Hub 'larınızla ilişkili sanal ağlarda DDoS koruma standardını etkinleştirin. Bilinen kötü amaçlı veya kullanılmayan Internet IP adresleriyle iletişimleri reddetmek için Azure Güvenlik Merkezi tümleşik tehdit zekasını kullanın.
- [DDoS korumasını yapılandırma](../ddos-protection/manage-ddos-protection.md)
- [Azure Güvenlik Merkezi tümleşik tehdit bilgileri hakkında daha fazla bilgi için](../security-center/azure-defender.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="15-record-network-packets"></a>1,5: ağ paketlerini kaydetme
**Rehberlik**: Olay Hub 'larınızı erişmek için Azure sanal makinelerini kullanıyorsanız, ağ güvenlik grubu akış günlüklerini etkinleştirin ve trafik denetimi için günlükleri bir depolama hesabına gönderin. Ayrıca, bir Log Analytics çalışma alanına ağ güvenlik grubu akış günlükleri gönderebilir ve Azure bulutunuzda trafik akışına Öngörüler sağlamak için Trafik Analizi kullanabilirsiniz. Trafik Analizi avantajlarından bazıları, ağ etkinliğini görselleştirme ve etkin noktaları belirlemek, güvenlik tehditlerini belirlemek, trafik akışı düzenlerini anlamak ve ağ yapılandırmalarını saptamak için kullanılır.
Anormal etkinlikleri araştırmak için gerekliyse, ağ Izleyicisi paket yakalamayı etkinleştirin.
- [NSG akış günlüklerini etkinleştirme](../network-watcher/network-watcher-nsg-flow-logging-portal.md)
- [Trafik Analizi etkinleştirme ve kullanma](../network-watcher/traffic-analytics.md)
- [Ağ İzleyicisini etkinleştirme](../network-watcher/network-watcher-create.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="16-deploy-network-based-intrusion-detectionintrusion-prevention-systems-idsips"></a>1,6: ağ tabanlı yetkisiz giriş algılama/yetkisiz erişim önleme sistemleri (KIMLIKLER/IP 'ler) dağıtma
**Rehberlik**: Olay Hub 'larınız için Azure sanal makineleri kullanıyorsanız, yük İnceleme ÖZELLIKLERINE sahip kimlikleri/IP 'Leri destekleyen Azure Marketi 'nden bir teklif seçin. Kuruluşunuz için yük incelemesini temel alan yetkisiz giriş algılama ve/veya önleme gerekmiyorsa Azure Event Hubs ' yerleşik güvenlik duvarı özelliğini kullanabilirsiniz. Güvenlik duvarı kurallarını kullanarak, sınırlı bir IP adresi aralığı veya belirli bir IP adresi için Event Hubs ad uzayına erişimi sınırlayabilirsiniz.
- [Azure Market](https://azuremarketplace.microsoft.com/marketplace/?term=Firewall)
- [Belirli bir IP adresi için Event Hubs bir güvenlik duvarı kuralı ekleme](event-hubs-ip-filtering.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="19-maintain-standard-security-configurations-for-network-devices"></a>1,9: ağ cihazları için standart güvenlik yapılandırmalarının bakımını yapma
**Kılavuz**: Azure Ilkesi ile Azure Event Hubs ad boşluklarınızla ilişkili ağ kaynakları için standart güvenlik yapılandırması tanımlayın ve uygulayın. Event Hubs ad alanlarınızın ağ yapılandırmasını denetlemek veya zorlamak üzere özel ilke tanımları oluşturmak için **Microsoft. EventHub** ve **Microsoft. Network** ad alanlarında Azure ilke diğer adlarını kullanın. Ayrıca, Azure Event Hubs ile ilgili yerleşik ilke tanımlarından da yararlanabilirsiniz, örneğin:
- Olay Hub 'ı bir sanal ağ hizmeti uç noktası kullanmalıdır.
Ek bilgiler başvurulan bağlantılarda bulunabilir.
- [Azure İlkesi'ni yapılandırma ve yönetme](../governance/policy/tutorials/create-and-manage.md)
- [Event Hubs ad alanı için Azure yerleşik Ilkesi](../governance/policy/samples/built-in-policies.md#event-hub)
- [Ağ için Azure Ilke örnekleri](../governance/policy/samples/built-in-policies.md#network)
- [Azure Blueprint oluşturma](../governance/blueprints/create-blueprint-portal.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="110-document-traffic-configuration-rules"></a>1,10: belge trafiği yapılandırma kuralları
**Rehberlik**: sanal ağlar ve Olay Hub 'larınızla ilişkili ağ güvenliği ve trafik akışıyla ilgili diğer kaynaklar için Etiketler kullanın.
- [Etiketler oluşturma ve kullanma](../azure-resource-manager/management/tag-resources.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="111-use-automated-tools-to-monitor-network-resource-configurations-and-detect-changes"></a>1,11: ağ kaynağı yapılandırmasını izlemek ve değişiklikleri algılamak için otomatikleştirilmiş araçları kullanın
**Kılavuz**: Azure etkinlik günlüğü 'nü kullanarak ağ kaynak yapılandırmasını Izleyin ve Azure Event Hubs ile ilgili ağ kaynaklarına yönelik değişiklikleri tespit edin. Kritik ağ kaynaklarında yapılan değişiklikler yürürlüğe girdiğinde tetiklenecek Azure Izleyici içinde uyarılar oluşturun.
- [Azure etkinlik günlüğü olaylarını görüntüleme ve alma](../azure-monitor/essentials/activity-log.md#view-the-activity-log)
- [Azure Izleyici 'de uyarı oluşturma](../azure-monitor/alerts/alerts-activity-log.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
## <a name="logging-and-monitoring"></a>Günlüğe Kaydetme ve İzleme
*Daha fazla bilgi için bkz. [Azure Güvenlik kıyaslaması: günlüğe kaydetme ve izleme](../security/benchmarks/security-control-logging-monitoring.md).*
### <a name="22-configure-central-security-log-management"></a>2,2: Merkezi güvenlik günlüğü yönetimini yapılandırma
**Kılavuz**: Azure izleyici 'de, olayları bir Log Analytics çalışma alanına veya uzun vadeli arşiv depolamaya yönelik bir depolama hesabına göndermek Için etkinlik günlüğü ve Olay Hub 'ı Tanılama ayarları içindeki olay hub 'ları ile ilgili günlükleri yapılandırın.
- [Azure Event Hubs için tanılama ayarlarını yapılandırma](event-hubs-diagnostic-logs.md)
- [Azure etkinlik günlüğünü anlama](../azure-monitor/essentials/platform-logs-overview.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="23-enable-audit-logging-for-azure-resources"></a>2,3: Azure kaynakları için denetim günlüğünü etkinleştirme
**Kılavuz**: Azure Event Hubs ad alanınız için tanılama ayarlarını etkinleştirin. Azure Event Hubs için üç tanılama ayarı kategorisi vardır: Arşiv günlükleri, Işletimsel Günlükler ve otomatik ölçeklendirme günlükleri. İşlem günlüklerini, Olay Hub 'ı oluşturma, kullanılan kaynaklar ve işlem durumu dahil olmak üzere Event Hubs işlemleri sırasında oluşan işlemler, özellikle de işlem türü hakkında bilgi yakalamak için etkinleştirin.
Ayrıca, Azure etkinlik günlüğü tanılama ayarlarını etkinleştirebilir ve bunları bir Azure depolama hesabına, Olay Hub 'ına veya Log Analytics çalışma alanına gönderebilirsiniz. Etkinlik günlükleri, Azure Event Hubs ve diğer kaynaklarda gerçekleştirilen işlemlere ilişkin öngörüler sağlar. Etkinlik günlüklerini kullanarak, Azure Event Hubs ad boşluklarında herhangi bir yazma işlemi (PUT, POST, SILME) için "ne, kim ve ne zaman" i belirleyebilirsiniz.
- [Azure Event Hubs için tanılama ayarlarını etkinleştirme](event-hubs-diagnostic-logs.md)
- [Azure etkinlik günlüğü için tanılama ayarlarını etkinleştirme](../azure-monitor/essentials/activity-log.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: [Azure Güvenlik kıyaslaması](/azure/governance/policy/samples/azure-security-benchmark) , Güvenlik Merkezi için varsayılan Ilke girişimidir ve [Güvenlik Merkezi 'nin önerilerine](/azure/security-center/security-center-recommendations)yöneliktir. Bu denetimle ilgili Azure Ilke tanımları, Güvenlik Merkezi tarafından otomatik olarak etkinleştirilir. Bu denetimle ilgili uyarılar, ilgili hizmetler için bir [Azure Defender](/azure/security-center/azure-defender) planı gerektirebilir.
**Azure ilkesi yerleşik tanımları-Microsoft. EventHub**:
[!INCLUDE [Resource Policy for Microsoft.EventHub 2.3](../../includes/policy/standards/asb/rp-controls/microsoft.eventhub-2-3.md)]
### <a name="25-configure-security-log-storage-retention"></a>2,5: güvenlik günlüğü depolama bekletmesini yapılandırma
**Kılavuz**: Azure izleyici 'de, Olay Hub 'ı ile ilgili olayları yakalamak ve gözden geçirmek için kuruluşunuzun uyumluluk düzenlemelerine göre Log Analytics çalışma alanı saklama süresini ayarlayın.
- [Log Analytics çalışma alanları için günlük saklama parametrelerini ayarlama](../azure-monitor/logs/manage-cost-storage.md#change-the-data-retention-period)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="26-monitor-and-review-logs"></a>2,6: günlükleri izleme ve gözden geçirme
**Rehberlik**: anormal davranış için günlükleri çözümleyin ve izleyin ve Olay Hub 'larıyla ilgili sonuçları düzenli olarak gözden geçirin. Günlükleri gözden geçirmek ve günlük verilerinde sorgular gerçekleştirmek için Azure Izleyici Log Analytics kullanın. Alternatif olarak, Azure Sentinel veya bir üçüncü taraf sistem bilgileri ve olay yönetimi çözümünde veri ve şirket içi verileri etkinleştirebilir.
- [Log Analytics çalışma alanı hakkında daha fazla bilgi için](../azure-monitor/logs/log-analytics-tutorial.md)
- [Azure Izleyici 'de özel sorgular gerçekleştirme](../azure-monitor/logs/get-started-queries.md)
- [Azure Sentinel 'i ekleme](../sentinel/quickstart-onboard.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="27-enable-alerts-for-anomalous-activities"></a>2,7: anormal etkinlikler için uyarıları etkinleştir
**Kılavuz**: Azure izleyici 'de, etkinlik günlüğü içinde Azure Event Hubs ile ilgili günlükleri yapılandırın ve bir Log Analytics çalışma alanına veya uzun vadeli arşiv depolaması için bir depolama hesabına Günlükler göndermek üzere tanılama ayarlarını Event Hubs. Güvenlik günlükleri ve olayları 'nda bulunan anormal etkinlikler için uyarı oluşturmak üzere Log Analytics çalışma alanını kullanın.
Alternatif olarak, Azure Sentinel 'de ve yerleşik verileri etkinleştirebilir.
- [Azure etkinlik günlüğünü anlama](../azure-monitor/essentials/platform-logs-overview.md)
- [Azure Event Hubs için tanılama ayarlarını yapılandırma](event-hubs-diagnostic-logs.md)
- [Log Analytics çalışma alanı günlük verilerinde uyarı alma](../azure-monitor/alerts/tutorial-response.md)
- [Azure Sentinel 'i ekleme](../sentinel/quickstart-onboard.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
## <a name="identity-and-access-control"></a>Kimlik ve Erişim Denetimi
*Daha fazla bilgi için bkz. [Azure Güvenlik kıyaslaması: kimlik ve Access Control](../security/benchmarks/security-control-identity-access-control.md).*
### <a name="31-maintain-an-inventory-of-administrative-accounts"></a>3,1: yönetim hesaplarının envanterini tutma
**Rehberlik**: Azure Active Directory (Azure AD), açıkça atanması ve sorgulanabilir olması gereken yerleşik roller içerir. Yönetim gruplarının üyesi olan hesapları bulmaya yönelik geçici sorgular gerçekleştirmek için Azure AD PowerShell modülünü kullanın.
- [Azure AD 'de PowerShell ile dizin rolü alma](/powershell/module/azuread/get-azureaddirectoryrole)
- [Azure AD 'de PowerShell ile bir dizin rolünün üyelerini alma](/powershell/module/azuread/get-azureaddirectoryrolemember)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="32-change-default-passwords-where-applicable"></a>3,2: uygun yerlerde varsayılan parolaları değiştirme
**Rehberlik**: denetim düzlemi erişimi, Event Hubs Azure Active Directory (Azure AD) ile denetlenir. Azure AD varsayılan parola kavramına sahip değildir.
Event Hubs veri düzlemi erişimi, Yönetilen kimlikler veya Uygulama kayıtları ile paylaşılan erişim imzaları ile Azure AD aracılığıyla denetlenir. Paylaşılan erişim imzaları, Olay Hub 'larınızı bağlayan istemciler tarafından kullanılır ve herhangi bir zamanda yeniden oluşturulabilir.
- [Event Hubs için paylaşılan erişim imzalarını anlayın](authenticate-shared-access-signature.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="33-use-dedicated-administrative-accounts"></a>3,3: adanmış yönetim hesapları kullanın
**Rehberlik**: adanmış yönetim hesaplarının kullanımı etrafında standart işletim yordamları oluşturun. Yönetim hesaplarının sayısını izlemek için Azure Güvenlik Merkezi kimlik ve erişim yönetimi 'ni kullanın.
Ayrıca, özel yönetim hesaplarını izlemenize yardımcı olmak için Azure Güvenlik Merkezi veya yerleşik Azure Ilkeleri önerilerini kullanabilirsiniz; örneğin:
- Aboneliğinize birden fazla sahip atanmalıdır
- Sahip izinleri olan kullanım dışı hesaplar aboneliğinizden kaldırılmalıdır
- Sahip izinleri olan dış hesaplar aboneliğinizden kaldırılmalıdır
Ek bilgiler başvurulan bağlantılarda bulunabilir.
- [Kimlik ve erişim (Önizleme) izlemek için Azure Güvenlik Merkezi 'ni kullanma](../security-center/security-center-identity-access.md)
- [Azure Ilkesini kullanma](../governance/policy/tutorials/create-and-manage.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="34-use-azure-active-directory-single-sign-on-sso"></a>3,4: Azure Active Directory çoklu oturum açma kullan (SSO)
**Rehberlik**: Microsoft Azure, Azure Active Directory (Azure AD) tabanlı kaynaklar ve uygulamalar için tümleşik erişim denetimi yönetimi sağlar. Azure AD 'yi Azure Event Hubs kullanmanın önemli bir avantajı, kimlik bilgilerinizi artık kodda depolamanızı gerektirmez. Bunun yerine, Microsoft Identity platform 'dan bir OAuth 2,0 erişim belirteci isteyebilirsiniz. Belirteç istemek için kaynak adı https: \/ /eventhubs.Azure.net/. Azure AD, uygulamayı çalıştıran güvenlik sorumlusu (bir Kullanıcı, Grup veya hizmet sorumlusu) kimliğini doğrular. Kimlik doğrulaması başarılı olursa, Azure AD uygulamaya bir erişim belirteci döndürür ve uygulama Azure Event Hubs kaynaklarına istek yetkilendirmek için erişim belirtecini kullanabilir.
- [Event Hubs kaynaklarına erişmek için Azure AD ile bir uygulamanın kimliğini doğrulama](authenticate-application.md)
- [Azure AD ile SSO 'yu anlama](../active-directory/manage-apps/what-is-single-sign-on.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="35-use-multi-factor-authentication-for-all-azure-active-directory-based-access"></a>3,5: tüm Azure Active Directory tabanlı erişim için Multi-Factor Authentication kullanın
**Rehberlik**: Azure Active Directory (Azure AD) çok faktörlü kimlik doğrulamasını etkinleştirin ve Azure Güvenlik Merkezi kimlik ve erişim yönetimi önerilerini Izleyerek Olay Hub 'ı özellikli kaynaklarınızı korumaya yardımcı olun.
- [Azure 'da çok faktörlü kimlik doğrulamasını etkinleştirme](../active-directory/authentication/howto-mfa-getstarted.md)
- [Azure Güvenlik Merkezi 'nde kimliği ve erişimi izleme](../security-center/security-center-identity-access.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="36-use-dedicated-machines-privileged-access-workstations-for-all-administrative-tasks"></a>3,6: tüm yönetim görevleri için adanmış makineler (ayrıcalıklı erişim Iş Istasyonları) kullanın
**Rehberlik**: Olay Hub 'ı etkin kaynakları açmak ve yapılandırmak için yapılandırılmış çok faktörlü kimlik doğrulaması ile ayrıcalıklı erişim iş istasyonları (Paw) kullanın.
- [Ayrıcalıklı erişim Iş Istasyonları hakkında bilgi edinin](/security/compass/privileged-access-devices)
- [Azure 'da çok faktörlü kimlik doğrulamasını etkinleştirme](../active-directory/authentication/howto-mfa-getstarted.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="37-log-and-alert-on-suspicious-activities-from-administrative-accounts"></a>3,7: yönetim hesaplarından şüpheli etkinliklerle ilgili günlüğe kaydet ve uyar
**Rehberlik**: ortamda şüpheli veya güvenli olmayan bir etkinlik olduğunda günlüklerin ve uyarıların üretilmesi için Azure Active Directory (Azure AD) Privileged Identity Management kullanın. Riskli Kullanıcı davranışında uyarıları ve raporları görüntülemek için Azure AD risk algılamalarını kullanın. Ek günlük kaydı için Azure Güvenlik Merkezi risk algılama uyarılarını Azure Izleyicisine gönderin ve eylem gruplarını kullanarak özel uyarı/bildirim yapılandırın.
- [Azure AD risk algılamalarını anlama](../active-directory/identity-protection/overview-identity-protection.md)
- [Özel uyarı ve bildirim için eylem gruplarını yapılandırma](../azure-monitor/alerts/action-groups.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="38-manage-azure-resources-from-only-approved-locations"></a>3,8: Azure kaynaklarını yalnızca onaylanan konumlardan yönetme
**Rehberlik**: IP adresi aralıklarının veya ülkelerin/bölgelerin yalnızca belirli mantıksal gruplarından erişime izin vermek Için adlandırılmış konumlar kullanın.
- [Azure 'da adlandırılmış konumları yapılandırma](../active-directory/reports-monitoring/quickstart-configure-named-locations.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="39-use-azure-active-directory"></a>3,9: Azure Active Directory kullanın
**Rehberlik**: Event Hubs gibi Azure kaynakları için merkezi kimlik doğrulama ve yetkilendirme sistemi olarak Azure Active Directory (Azure AD) kullanın. Bu, Azure rol tabanlı erişim denetimi (Azure RBAC) ile yönetici duyarlı kaynaklara izin verir.
- [ Azure AD örneği oluşturma ve yapılandırma](../active-directory/fundamentals/active-directory-access-create-new-tenant.md)
- [Azure AD kullanarak Event Hubs kaynaklarına erişim yetkisi verme](authorize-access-azure-active-directory.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="310-regularly-review-and-reconcile-user-access"></a>3,10: Kullanıcı erişimini düzenli olarak gözden geçirin ve karşılaştırın
**Rehberlik**: Azure Active Directory (Azure AD) eski hesapları keşfetmenize yardımcı olacak Günlükler sağlar. Ayrıca, grup üyeliklerini etkin bir şekilde yönetmek, kurumsal uygulamalara erişmek ve rol atamaları için Azure kimlik erişimi Incelemelerini kullanın. Yalnızca doğru kullanıcıların erişmeye devam ettiğinden emin olmak için, Kullanıcı erişimi düzenli olarak incelenebilir.
Ayrıca, Event Hubs ' paylaşılan erişim imzalarınızı düzenli olarak döndürün.
- [Azure AD raporlamayı anlama](../active-directory/reports-monitoring/index.yml)
- [Azure kimlik erişimi Incelemelerini kullanma](../active-directory/governance/access-reviews-overview.md)
- [Event Hubs için paylaşılan erişim imzalarını anlama](authenticate-shared-access-signature.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="311-monitor-attempts-to-access-deactivated-credentials"></a>3,11: devre dışı bırakılmış kimlik bilgilerine erişme girişimlerini izleme
**Rehberlik**: herhangi bir üçüncü taraf sistem bilgileri ve olay yönetimi çözümü veya izleme aracı ile tümleştirmenize olanak tanıyan Azure Active Directory (Azure AD) oturum açma etkinliğine, denetim ve risk olay günlüğü kaynaklarına erişiminiz vardır.
Bu işlemi, Azure AD Kullanıcı hesapları için Tanılama ayarları oluşturarak ve Log Analytics çalışma alanına denetim günlüklerini ve oturum açma günlüklerini göndererek kolaylaştırabilirsiniz. Log Analytics içinde, istenen günlük uyarılarını yapılandırabilirsiniz.
- [Azure Etkinlik Günlüklerini Azure İzleyici ile tümleştirme](../active-directory/reports-monitoring/howto-integrate-activity-logs-with-log-analytics.md)
- [Azure AD kullanarak Event Hubs kaynaklarına erişim yetkisi verme](authorize-access-azure-active-directory.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="312-alert-on-account-sign-in-behavior-deviation"></a>3,12: hesap oturum açma davranışı sapması üzerinde uyarı
**Rehberlik**: Event Hubs etkin kaynaklarınızla ilişkili şüpheli eylemler için otomatik yanıtlar yapılandırmak üzere Azure Active Directory (Azure AD) Içindeki kimlik koruması ve risk algılama özelliklerini kullanın. Kuruluşunuzun güvenlik yanıtlarını uygulamak için Azure Sentinel aracılığıyla otomatikleştirilmiş yanıtları etkinleştirmeniz gerekir.
- [Azure AD riskli oturum açma işlemlerini görüntüleme](../active-directory/identity-protection/overview-identity-protection.md)
- [Kimlik koruması risk ilkelerini yapılandırma ve etkinleştirme](../active-directory/identity-protection/howto-identity-protection-configure-risk-policies.md)
- [Azure Sentinel 'i ekleme](../sentinel/quickstart-onboard.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="313-provide-microsoft-with-access-to-relevant-customer-data-during-support-scenarios"></a>3,13: destek senaryoları sırasında Microsoft 'un ilgili müşteri verilerine erişimini sağlama
**Rehberlik**: Şu anda kullanılamıyor; Müşteri Kasası, Event Hubs için henüz desteklenmiyor.
- [Müşteri Kasası tarafından desteklenen hizmetler listesi](../security/fundamentals/customer-lockbox-overview.md#supported-services-and-scenarios-in-general-availability)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
## <a name="data-protection"></a>Veri Koruma
*Daha fazla bilgi için bkz. [Azure Güvenlik Karşılaştırması: Veri Koruma](../security/benchmarks/security-control-data-protection.md).*
### <a name="41-maintain-an-inventory-of-sensitive-information"></a>4,1: hassas bilgilerin envanterini tutma
**Rehberlik**: hassas bilgileri depolayan veya işleyen Azure kaynaklarını izlemeye yardımcı olmak için Event Hubs ilişkili kaynaklarda Etiketler kullanın.
- [Etiketler oluşturma ve kullanma](../azure-resource-manager/management/tag-resources.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="42-isolate-systems-storing-or-processing-sensitive-information"></a>4,2: hassas bilgileri depolayan veya işleyen sistemleri yalıtma
**Rehberlik**: isteğe bağlı olarak, geliştirme, test ve üretim için yönetim gruplarıyla ayrı abonelikler uygulayın. Event Hubs ad alanları, hizmet uç noktaları etkinleştirilmiş ve uygun şekilde etiketlenmiş sanal ağ ile ayrılmalıdır.
Azure Event Hubs ad alanınızı güvenlik duvarları kullanarak da güvence altına alabilirsiniz. Azure Event Hubs, gelen güvenlik duvarı desteği için IP tabanlı erişim denetimlerini destekler. Azure portal, Azure Resource Manager şablonlarını veya Azure CLı veya Azure PowerShell aracılığıyla güvenlik duvarı kuralları belirleyebilirsiniz.
- [Ek Azure abonelikleri oluşturma](../cost-management-billing/manage/create-subscription.md)
- [Yönetim Grupları oluşturma](../governance/management-groups/create-management-group-portal.md)
- [Azure Event Hubs ad alanları için IP güvenlik duvarı kurallarını yapılandırma](event-hubs-ip-filtering.md)
- [Etiketler oluşturma ve kullanma](../azure-resource-manager/management/tag-resources.md)
- [Sanal ağ oluşturma](../virtual-network/quick-create-portal.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="43-monitor-and-block-unauthorized-transfer-of-sensitive-information"></a>4,3: hassas bilgilerin yetkisiz aktarımını izleme ve engelleme
**Rehberlik**: Olay Hub 'larınıza erişmek için sanal makineleri kullanırken, veri kaybı olasılığını azaltmak için sanal ağlar, hizmet uç noktaları, Event Hubs güvenlik duvarı, ağ güvenlik grupları ve hizmet etiketleri kullanın.
Microsoft, Azure Event Hubs için temel altyapıyı yönetir ve müşteri verilerinin kaybını veya açıklanmasını engellemek için katı denetimler uygulamıştır.
- [Azure Event Hubs ad alanları için IP güvenlik duvarı kurallarını yapılandırma](event-hubs-ip-filtering.md)
- [Azure Event Hubs sanal ağ hizmet uç noktalarını anlayın](event-hubs-service-endpoints.md)
- [Azure Event Hubs Azure özel bağlantısı ile tümleştirme](private-link-service.md)
- [Ağ güvenlik gruplarını ve hizmet etiketlerini anlayın](../virtual-network/network-security-groups-overview.md)
- [Azure’da müşteri verilerinin korunmasını anlama](../security/fundamentals/protection-customer-data.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="45-use-an-active-discovery-tool-to-identify-sensitive-data"></a>4,5: hassas verileri belirlemek için etkin bir keşif aracı kullanın
**Rehberlik**: veri tanımlama, sınıflandırma ve kayıp önleme özellikleri Azure Event Hubs için henüz kullanılamıyor. Uyumluluk amacıyla gerekliyse üçüncü taraf çözümünü uygulayın.
Microsoft tarafından yönetilen temel alınan platform için, Microsoft tüm müşteri içeriklerini gizli olarak değerlendirir ve müşteri veri kaybına ve açığa çıkmasına karşı koruma sağlamak için harika uzunluklara gider. Azure 'daki müşteri verilerinin güvende kalmasını sağlamak için Microsoft, bir dizi güçlü veri koruma denetimi ve özelliği uygulamıştır ve bakımını yapar.
- [Azure’da müşteri verilerinin korunmasını anlama](../security/fundamentals/protection-customer-data.md)
**Sorumluluk**: Paylaşılan
**Azure Güvenlik Merkezi izleme**: yok
### <a name="46-use-role-based-access-control-to-control-access-to-resources"></a>4,6: kaynaklara erişimi denetlemek için rol tabanlı erişim denetimi kullanma
**Kılavuz**: Azure Event Hubs, istekleri Event Hubs kaynaklara yetkilendirmek için Azure Active Directory (Azure AD) kullanımını destekler. Azure AD ile, bir kullanıcı veya uygulama hizmeti sorumlusu olabilecek bir güvenlik sorumlusu için izin vermek üzere Azure rol tabanlı erişim denetimi 'ni (Azure RBAC) kullanabilirsiniz.
- [Azure RBAC ve kullanılabilir Azure Event Hubs rollerini anlama](authorize-access-azure-active-directory.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="48-encrypt-sensitive-information-at-rest"></a>4,8: hassas bilgileri Rest 'te şifreleyin
**Kılavuz**: Azure Event Hubs, bekleyen verileri Microsoft tarafından yönetilen anahtarlarla veya müşteri tarafından yönetilen anahtarlarla şifreleme seçeneğini destekler. Bu özellik, Azure Event Hubs verilerini bekleyen bir şekilde şifrelemek için kullanılan müşteri tarafından yönetilen anahtarlara erişimi oluşturmanıza, döndürmenize, devre dışı bırakmanızı ve iptal etmenize olanak sağlar.
- [Azure Event Hubs şifrelemek için müşteri tarafından yönetilen anahtarları yapılandırma](configure-customer-managed-key.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="49-log-and-alert-on-changes-to-critical-azure-resources"></a>4,9: kritik Azure kaynaklarında yapılan değişikliklerle ilgili günlük ve uyarı
**Kılavuz**: Azure izleyici 'Yi Azure etkinlik günlüğü ile birlikte kullanarak Azure Event Hubs 'in üretim örneklerine ve diğer önemli veya ilgili kaynaklara yönelik değişikliklerin ne zaman gerçekleştiği hakkında uyarılar oluşturun.
- [Azure etkinlik günlüğü olayları için uyarı oluşturma](../azure-monitor/alerts/alerts-activity-log.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
## <a name="inventory-and-asset-management"></a>Envanter ve Varlık Yönetimi
*Daha fazla bilgi için bkz. [Azure Güvenlik kıyaslaması: envanter ve varlık yönetimi](../security/benchmarks/security-control-inventory-asset-management.md).*
### <a name="61-use-automated-asset-discovery-solution"></a>6,1: otomatik varlık bulma çözümünü kullanma
**Rehberlik**: abonelikleriniz dahilinde tüm kaynakları (Azure Event Hubs ad alanları dahil) sorgulamak ve saptamak Için Azure Kaynak grafiğini kullanın. Kiracınızda uygun (okuma) izinleriniz olduğundan ve aboneliklerinizdeki kaynakların yanı sıra tüm Azure aboneliklerinin listesini belirleyebildiğinizden emin olun.
- [Azure Kaynak Graf ile sorgu oluşturma](../governance/resource-graph/first-query-portal.md)
- [Azure aboneliklerinizi görüntüleme](/powershell/module/az.accounts/get-azsubscription)
- [Azure RBAC 'yi anlama](../role-based-access-control/overview.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="62-maintain-asset-metadata"></a>6,2: varlık meta verilerini koruma
**Kılavuz**: Azure kaynaklarına Etiketler uygulayarak bunları bir taksonomi halinde mantıksal olarak organize etmek için meta veriler verirsiniz.
- [Etiketler oluşturma ve kullanma](../azure-resource-manager/management/tag-resources.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="63-delete-unauthorized-azure-resources"></a>6,3: yetkisiz Azure kaynaklarını silme
**Rehberlik**: Azure Event Hubs ad alanlarını ve ilgili kaynakları düzenlemek ve izlemek için uygun yerlerde etiketleme, yönetim grupları ve ayrı abonelikler kullanın. Envanterin düzenli olarak mutabakatını yapın ve yetkisiz kaynakların aboneliğin zamanında silindiğinden emin olun.
- [Ek Azure abonelikleri oluşturma](../cost-management-billing/manage/create-subscription.md)
- [Yönetim Grupları oluşturma](../governance/management-groups/create-management-group-portal.md)
- [Etiketler oluşturma ve kullanma](../azure-resource-manager/management/tag-resources.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="65-monitor-for-unapproved-azure-resources"></a>6,5: onaylanmamış Azure kaynakları için izleyici
**Rehberlik**: aşağıdaki yerleşik ilke tanımlarını kullanarak müşteri aboneliklerinde oluşturulabilen kaynak türlerine kısıtlamalar koymak Için Azure ilkesini kullanın:
- İzin verilmeyen kaynak türleri
- İzin verilen kaynak türleri
Ayrıca, aboneliklerdeki kaynakları sorgulamak/öğrenmek için Azure Kaynak Grafiği ' ni kullanın.
- [Azure İlkesi'ni yapılandırma ve yönetme](../governance/policy/tutorials/create-and-manage.md)
- [Azure Graph ile sorgu oluşturma](../governance/resource-graph/first-query-portal.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="69-use-only-approved-azure-services"></a>6,9: yalnızca onaylanan Azure hizmetlerini kullanın
**Rehberlik**: aşağıdaki yerleşik ilke tanımlarını kullanarak müşteri aboneliklerinde oluşturulabilen kaynak türlerine kısıtlamalar koymak Için Azure ilkesini kullanın:
- İzin verilmeyen kaynak türleri
- İzin verilen kaynak türleri
Ek bilgiler başvurulan bağlantılarda bulunabilir.
- [Azure İlkesi'ni yapılandırma ve yönetme](../governance/policy/tutorials/create-and-manage.md)
- [Azure Ilkesiyle belirli bir kaynak türünü reddetme](../governance/policy/samples/built-in-policies.md#general)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="611-limit-users-ability-to-interact-with-azure-resource-manager"></a>6,11: kullanıcıların Azure Resource Manager etkileşime geçme yeteneğini sınırlayın
**Rehberlik**: "Microsoft Azure yönetimi" uygulaması için "erişimi engelle" yapılandırarak kullanıcıların Azure Resource Manager etkileşime geçmesini sınırlamak üzere Azure koşullu erişimini yapılandırın.
- [Azure Resource Manager erişimi engellemek için koşullu erişimi yapılandırma](../role-based-access-control/conditional-access-azure-management.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
## <a name="secure-configuration"></a>Güvenli Yapılandırma
*Daha fazla bilgi için bkz. [Azure Güvenlik kıyaslaması: güvenli yapılandırma](../security/benchmarks/security-control-secure-configuration.md).*
### <a name="71-establish-secure-configurations-for-all-azure-resources"></a>7,1: tüm Azure kaynakları için güvenli yapılandırma oluşturma
**Rehberlik**: Azure Event Hubs dağıtımlarınız için standart güvenlik yapılandırması tanımlayın ve uygulayın. Konfigürasyonları denetlemek veya zorlamak üzere özel ilkeler oluşturmak için **Microsoft. EventHub** ad alanındaki Azure ilke diğer adlarını kullanın. Azure Event Hubs için yerleşik ilke tanımlarından da yararlanabilirsiniz:
- Olay Hub 'ındaki tanılama günlükleri etkinleştirilmelidir
- Olay Hub 'ı bir sanal ağ hizmeti uç noktası kullanmalıdır
Ek bilgiler başvurulan bağlantılarda bulunabilir.
- [Event Hubs ad alanı için Azure yerleşik Ilkesi](../governance/policy/samples/built-in-policies.md#event-hub)
- [Kullanılabilir Azure Ilkesi diğer adlarını görüntüleme](/powershell/module/az.resources/get-azpolicyalias)
- [Azure İlkesi'ni yapılandırma ve yönetme](../governance/policy/tutorials/create-and-manage.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="73-maintain-secure-azure-resource-configurations"></a>7,3: güvenli Azure Kaynak yapılandırmalarının bakımını yapma
**Rehberlik**: Event Hubs etkinleştirilmiş kaynaklarınız genelinde güvenli ayarları zorlamak Için Azure ilkesi [reddetme] ve [dağıtım yoksa dağıt] etkileri kullanın.
- [Azure İlkesi'ni yapılandırma ve yönetme](../governance/policy/tutorials/create-and-manage.md)
- [Azure Ilke etkileri hakkında daha fazla bilgi için](../governance/policy/concepts/effects.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="77-deploy-configuration-management-tools-for-azure-resources"></a>7,7: Azure kaynakları için yapılandırma yönetimi araçları dağıtma
**Rehberlik**: sistem yapılandırmalarına uyarı vermek, denetlemek ve zorlamak için özel ilkeler oluşturmak üzere "Microsoft. EventHub" ad alanındaki Azure ilke diğer adlarını kullanın. Ayrıca, ilke özel durumlarını yönetmek için bir işlem ve işlem hattı geliştirin.
- [Azure İlkesi'ni yapılandırma ve yönetme](../governance/policy/tutorials/create-and-manage.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="79-implement-automated-configuration-monitoring-for-azure-resources"></a>7,9: Azure kaynakları için otomatik yapılandırma izlemeyi uygulama
**Rehberlik**: sistem yapılandırmalarına uyarı vermek, denetlemek ve zorlamak için özel ilkeler oluşturmak üzere "Microsoft. EventHub" ad alanındaki Azure ilke diğer adlarını kullanın. Azure Event Hubs dağıtımlarınız ve ilgili kaynaklarınızın yapılandırmasını otomatik olarak zorlamak için [Denetim], [reddetme] ve [dağıtım yoksa dağıt] etkileri kullanın.
- [Azure İlkesi'ni yapılandırma ve yönetme](../governance/policy/tutorials/create-and-manage.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="711-manage-azure-secrets-securely"></a>7,11: Azure gizli dizilerini güvenli bir şekilde yönetin
**Kılavuz**: Azure sanal makineleri veya Olay Hub 'larınıza erişmek için kullanılan Azure App Service çalışan Web uygulamaları Için, Azure Event Hubs dağıtımlarınız için paylaşılan erişim imza yönetimini basitleştirmek ve güvenli hale getirmek üzere Azure Key Vault ile birlikte yönetilen hizmet kimliği kullanın. Key Vault, geçici silme etkin ile yapılandırıldığından emin olun.
- [Event Hubs kaynaklara erişmek için Azure Active Directory (Azure AD) ile yönetilen bir kimliğin kimliğini doğrulama](./authenticate-managed-identity.md?tabs=latest)
- [Event Hubs için müşteri tarafından yönetilen anahtarları yapılandırma](configure-customer-managed-key.md)
- [Azure yönetilen kimliklerle tümleştirme](../azure-app-configuration/howto-integrate-azure-managed-service-identity.md)
- [Key Vault oluşturma](../key-vault/secrets/quick-create-portal.md)
- [Yönetilen kimlik ile Key Vault kimlik doğrulaması sağlama](../key-vault/general/assign-access-policy-portal.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="712-manage-identities-securely-and-automatically"></a>7,12: kimlikleri güvenli ve otomatik olarak yönetme
**Kılavuz**: Azure sanal makineleri veya Olay Hub 'larınız için kullanılan Azure App Service çalışan Web uygulamaları Için, Azure Event Hubs 'yi basitleştirmek ve güvenli hale getirmek için Azure Key Vault birlikte yönetilen hizmet kimliği kullanın. Key Vault, geçici silme etkin ile yapılandırıldığından emin olun.
Azure Active Directory (Azure AD) içinde otomatik olarak yönetilen bir kimlik ile Azure hizmetleri sağlamak için Yönetilen kimlikler kullanın. Yönetilen kimlikler, kodunuzda kimlik bilgileri olmadan Azure Key Vault dahil olmak üzere Azure AD kimlik doğrulamasını destekleyen herhangi bir hizmette kimlik doğrulaması yapmanıza olanak sağlar.
- [Event Hubs kaynaklarına erişmek için Azure AD ile yönetilen bir kimliğin kimliğini doğrulama](./authenticate-managed-identity.md?tabs=latest)
- [Event Hubs için müşteri tarafından yönetilen anahtarları yapılandırma](configure-customer-managed-key.md)
- [Yönetilen kimlikleri yapılandırma](../active-directory/managed-identities-azure-resources/qs-configure-portal-windows-vm.md)
- [Azure yönetilen kimliklerle tümleştirme](../azure-app-configuration/howto-integrate-azure-managed-service-identity.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="713-eliminate-unintended-credential-exposure"></a>7,13: istenmeyen kimlik bilgisi pozlamasını ortadan kaldırın
**Rehberlik**: kod içinde kimlik bilgilerini tanımlamak Için kimlik bilgisi tarayıcısı uygulayın. Kimlik Bilgisi Tarayıcısı ayrıca bulunan kimlik bilgilerinin Azure Key Vault gibi daha güvenlik konumlara aktarılmasını sağlar.
- [Kimlik bilgisi tarayıcısı kurulumu](https://secdevtools.azurewebsites.net/helpcredscan.html)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
## <a name="malware-defense"></a>Kötü Amaçlı Yazılımdan Koruma
*Daha fazla bilgi için bkz. [Azure Güvenlik kıyaslaması: kötü amaçlı yazılımdan koruma](../security/benchmarks/security-control-malware-defense.md).*
### <a name="82-pre-scan-files-to-be-uploaded-to-non-compute-azure-resources"></a>8,2: işlem dışı Azure kaynaklarına yüklenecek dosyaları önceden Tara
**Kılavuz**: Azure Event Hubs, App Service, Data Lake Storage, BLOB depolama, PostgreSQL Için Azure veritabanı vb. gibi Işlem dışı Azure kaynaklarına yüklenen tüm içerikleri önceden tarayın. Microsoft bu örneklerdeki verilerinize erişemez.
Microsoft 'un kötü amaçlı yazılımdan koruma özelliği, Azure hizmetlerini destekleyen temel ana bilgisayar üzerinde etkinleştirilmiştir (örneğin, Reddır için Azure önbelleği), ancak müşteri içeriği üzerinde çalışmaz.
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
## <a name="data-recovery"></a>Veri Kurtarma
*Daha fazla bilgi için bkz. [Azure Güvenlik kıyaslaması: veri kurtarma](../security/benchmarks/security-control-data-recovery.md).*
### <a name="91-ensure-regular-automated-back-ups"></a>9,1: düzenli otomatik arka pencerelere emin olun
**Kılavuz**: Azure Event Hubs için coğrafi olağanüstü durum kurtarmayı yapılandırma. Azure bölgelerinin veya veri merkezlerinin (hiçbir kullanılabilirlik alanı kullanılmıyorsa) çalışma süresi kapalı kalma süresi, veri işlemenin farklı bir bölgede veya veri merkezinde çalışmaya devam edebilmesi için kritik öneme sahiptir. Bu nedenle, coğrafi olağanüstü durum kurtarma ve coğrafi çoğaltma, herhangi bir kuruluş için önemli özelliklerdir. Azure Event Hubs, ad alanı düzeyinde hem coğrafi olağanüstü durum kurtarmayı hem de Coğrafi çoğaltmayı destekler.
- [Azure Event Hubs coğrafi olağanüstü durum kurtarmayı anlama](./event-hubs-geo-dr.md#availability-zones)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="92-perform-complete-system-backups-and-backup-any-customer-managed-keys"></a>9,2: tam sistem yedeklemeleri gerçekleştirin ve müşterinin yönettiği tüm anahtarları yedekleyin
**Kılavuz**: Azure Event Hubs, Azure depolama hizmeti şifrelemesi (Azure SSE) ile bekleyen verilerin şifrelenmesini sağlar. Event Hubs, verileri depolamak için Azure depolama 'yı kullanır ve varsayılan olarak, Azure Storage ile depolanan tüm veriler Microsoft tarafından yönetilen anahtarlar kullanılarak şifrelenir. Müşteri tarafından yönetilen anahtarları depolamak için Azure Key Vault kullanıyorsanız, anahtarlarınızın düzenli otomatik yedeklemelerini sağlayın.
Aşağıdaki PowerShell komutuyla Key Vault Sırlarınızın düzenli otomatik yedeklemelerini sağlayın: Backup-AzKeyVaultSecret
- [Bekleyen Azure Event Hubs verilerini şifrelemek için müşteri tarafından yönetilen anahtarları yapılandırma](configure-customer-managed-key.md)
- [Key Vault gizli dizileri yedekleme](/powershell/module/azurerm.keyvault/backup-azurekeyvaultsecret)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="93-validate-all-backups-including-customer-managed-keys"></a>9,3: müşteri tarafından yönetilen anahtarlar dahil tüm yedeklemeleri doğrulama
**Rehberlik**: yedeklenen müşteri tarafından yönetilen anahtarların sınamasını geri yükleme.
- [Azure 'da Anahtar Kasası anahtarlarını geri yükleme](/powershell/module/az.keyvault/restore-azkeyvaultkey)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="94-ensure-protection-of-backups-and-customer-managed-keys"></a>9,4: yedeklemelerin ve müşteri tarafından yönetilen anahtarların korunmasını sağlayın
**Rehberlik**: anahtarları yanlışlıkla veya kötü amaçlı silmeye karşı korumak için Key Vault geçici silme özelliğini etkinleştirin. Azure Event Hubs, müşteri tarafından yönetilen anahtarların geçici silme ve bu şekilde temizlenme gerektirir.
Event Hubs verileri yakalamak için kullanılan Azure depolama hesabı için geçici silme yapılandırın. Bu özelliğin henüz Azure Data Lake Storage Gen 2 için desteklenmediğini unutmayın.
- [Key Vault 'da geçici silme nasıl etkinleştirilir](../storage/blobs/soft-delete-blob-overview.md?tabs=azure-portal)
- [Anahtarlar içeren bir Anahtar Kasası ayarlama](configure-customer-managed-key.md)
- [Azure Depolama blobları için geçici silme](/azure/storage/blobs/soft-delete-blob-overview)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
## <a name="incident-response"></a>Olay Yanıtı
*Daha fazla bilgi için bkz. [Azure Güvenlik Karşılaştırması: Olay Yanıtı](../security/benchmarks/security-control-incident-response.md).*
### <a name="101-create-an-incident-response-guide"></a>10,1: olay yanıtı kılavuzu oluşturma
**Rehberlik**: personel rollerinin yanı sıra olay işleme/yönetim aşamalarını tanımlayan yazılı olay yanıt planları olduğundan emin olun.
- [Azure Güvenlik Merkezi 'nde Iş akışı otomasyonlarını yapılandırma](../security-center/security-center-planning-and-operations-guide.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="102-create-an-incident-scoring-and-prioritization-procedure"></a>10,2: olay Puanlama ve öncelik belirlemesi prosedürü oluşturma
**Rehberlik**: Güvenlik Merkezi, her uyarıya katılma sırasını önceliklendirmenize yardımcı olmak için uyarılara önem derecesi atar. böylece, bir kaynak tehlikeye girdiğinde, hemen bu işe başlayabilirsiniz. Önem derecesi, güvenlik merkezi 'nin uyarıyı vermek için kullanılan bulma veya analizte ne kadar önemli olduğunu ve uyarıya yönelik etkinliğin arkasında kötü amaçlı bir amaç olduğunu bilmenin yanı sıra güven düzeyini temel alır.
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="103-test-security-response-procedures"></a>10,3: test Güvenliği Yanıt yordamları
**Rehberlik**: sistem olay yanıt yeteneklerini düzenli bir temposunda test etmek için alıştırmaları gerçekleştirin. Zayıf noktaları ve açıkları belirleyip planı gerektiği şekilde gözden geçirin.
- [NıST 'nin yayını: BT planları ve özellikleri için test, eğitim ve alıştırma programlarını inceleyin](https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-84.pdf)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="104-provide-security-incident-contact-details-and-configure-alert-notifications-for-security-incidents"></a>10,4: güvenlik olaylarına ilişkin iletişim ayrıntılarını sağlayın ve güvenlik olayları için uyarı bildirimleri yapılandırın
**Rehberlik**: Microsoft Güvenlik Yanıt MERKEZI (MSRC), müşterinin verilerine izinsiz veya yetkisiz bir taraf tarafından erişildiğini belirlerse, Microsoft tarafından sizinle iletişim kurmak için güvenlik olayı iletişim bilgileri kullanılacaktır. Sorunların çözümlendiğinden emin olmak için gerçesonra olayları gözden geçirin.
- [Azure Güvenlik Merkezi güvenlik Ilgili kişisini ayarlama](../security-center/security-center-provide-security-contact-details.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="105-incorporate-security-alerts-into-your-incident-response-system"></a>10,5: güvenlik uyarılarını olay yanıt sisteminizle birleştirme
**Rehberlik**: sürekli dışa aktarma özelliğini kullanarak Azure Güvenlik Merkezi uyarılarınızı ve önerilerinizi dışarı aktarın. Sürekli dışa aktarma, uyarıları ve önerileri el ile veya devam eden sürekli bir biçimde dışa aktarmanız sağlar. Azure Güvenlik Merkezi veri bağlayıcısını kullanarak uyarıları Azure Sentinel 'e akışını sağlayabilirsiniz.
- [Sürekli dışarı aktarmayı yapılandırma](../security-center/continuous-export.md)
- [Uyarıların Azure Sentinel’e akışını yapma](../sentinel/connect-azure-security-center.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
### <a name="106-automate-the-response-to-security-alerts"></a>10,6: güvenlik uyarılarına yanıtı otomatikleştirme
**Rehberlik**: güvenlik uyarılarında ve önerilerinde "Logic Apps" aracılığıyla yanıtları otomatik olarak tetiklemek Için Azure Güvenlik Merkezi 'Nde Iş akışı Otomasyonu özelliğini kullanın.
- [Iş akışı otomasyonu ve Logic Apps yapılandırma](../security-center/workflow-automation.md)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
## <a name="penetration-tests-and-red-team-exercises"></a>Sızma Testleri ve Red Team Alıştırmaları
*Daha fazla bilgi için bkz. [Azure Güvenlik kıyaslaması: Penetme testleri ve Red ekibi alıştırmaları](../security/benchmarks/security-control-penetration-tests-red-team-exercises.md).*
### <a name="111-conduct-regular-penetration-testing-of-your-azure-resources-and-ensure-remediation-of-all-critical-security-findings"></a>11,1: Azure kaynaklarınızın düzenli olarak sızma testini gerçekleştirin ve tüm kritik güvenlik bulgularını düzeltmeye dikkat edin
**Rehberlik**: Penettim testlerinizin Microsoft ilkelerini ihlal etmediğinden emin olmak Için Microsoft bulut Penme test kurallarını izleyin. Microsoft 'un, Microsoft tarafından yönetilen bulut altyapısına, hizmetlerine ve uygulamalarına karşı kırmızı ekip oluşturma ve canlı site sızma testi stratejisini kullanın.
- [Sızma Testi Etkileşim Kuralları](https://www.microsoft.com/msrc/pentest-rules-of-engagement?rtc=1)
- [Microsoft Bulut ile Kırmızı Takım Oluşturma](https://gallery.technet.microsoft.com/Cloud-Red-Teaming-b837392e)
**Sorumluluk**: Müşteri
**Azure Güvenlik Merkezi izleme**: yok
## <a name="next-steps"></a>Sonraki adımlar
- Bkz. [Azure Güvenlik Karşılaştırması 2.0 sürümüne genel bakış](../security/benchmarks/overview.md)
- [Azure güvenlik temelleri](../security/benchmarks/security-baselines-overview.md) hakkında daha fazla bilgi edinin
| 61.425837 | 731 | 0.805188 | tur_Latn | 0.999766 |
d3bb5785d3cd05a5231dc509403cd8ef538fbfd7 | 2,591 | md | Markdown | developer/hosting/host-application-samples.md | jwmoss/PowerShell-Docs | 25ae434ae90eaa2b64f16a721d557d790972c331 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-10-07T16:12:50.000Z | 2019-10-07T16:12:50.000Z | developer/hosting/host-application-samples.md | jwmoss/PowerShell-Docs | 25ae434ae90eaa2b64f16a721d557d790972c331 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2016-12-28T14:28:54.000Z | 2016-12-28T14:28:54.000Z | developer/hosting/host-application-samples.md | jwmoss/PowerShell-Docs | 25ae434ae90eaa2b64f16a721d557d790972c331 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-07-13T22:28:06.000Z | 2020-07-13T22:28:06.000Z | ---
title: "Host Application Samples | Microsoft Docs"
ms.custom: ""
ms.date: "09/13/2016"
ms.reviewer: ""
ms.suite: ""
ms.tgt_pltfrm: ""
ms.topic: "article"
ms.assetid: 2b4a41cc-2e22-49a0-b375-2e2447967751
caps.latest.revision: 11
---
# Host Application Samples
This section includes sample code that is provided in the Windows PowerShell 2.0 SDK.
You can copy the full sample code from the topics in this section, or use the source files installed with the SDK. The [Windows PowerShell 2.0 Software Development Kit (SDK)](https://www.microsoft.com/en-us/download/details.aspx?id=2560) provides ReadMe files, source files, and Visual Studio project files for each sample.
You can copy the full sample code from the topics in this section, or use the source files installed with the SDK. The [Windows PowerShell 2.0 Software Development Kit (SDK)](https://www.microsoft.com/en-us/download/details.aspx?id=2560) provides ReadMe files, source files, and Visual Studio project files for each sample.
## In This Section
[PowerShell API Samples](./windows-powershell-api-samples.md)
This section includes sample code that shows how to create runspaces that restrict functionality, and how to asynchronously run commands using a runspace pool to supply the runspaces.
[Custom Host Samples](./custom-host-samples.md)
Includes sample code for writing a custom host. The host is the component of Windows PowerShell that provides communications between the user and the Windows PowerShell engine. For more information about custom hosts, see [Custom Host](https://msdn.microsoft.com/en-us/library/ee706563(v=vs.85).aspx).
Includes sample code for writing a custom host. The host is the component of Windows PowerShell that provides communications between the user and the Windows PowerShell engine. For more information about custom hosts, see [Custom Host](https://msdn.microsoft.com/en-us/library/ee706563(v=vs.85).
[Runspace Samples](./runspace-samples.md)
Includes sample code for creating runspaces. For more information about how runspaces are used, see [Host Application Runspaces](https://msdn.microsoft.com/en-us/library/ee706563(v=vs.85).aspx).
Includes sample code for creating runspaces. For more information about how runspaces are used, see [Host Application Runspaces](https://msdn.microsoft.com/en-us/library/ee706563(v=vs.85).
[Remote Runspace Samples](./remote-runspace-samples.md)
This section includes sample code that shows how to create runspaces that can be used to connect to a computer by using WS-Management-based Windows PowerShell remoting.
## See Also
| 71.972222 | 324 | 0.786955 | eng_Latn | 0.977745 |
d3bce51a8e6e197e74d847d21206d0ef74799760 | 1,128 | md | Markdown | README.md | simonlindstedt/boomblox | 4d94419f6124619d4e9d291fada77b84bc705b56 | [
"MIT"
] | null | null | null | README.md | simonlindstedt/boomblox | 4d94419f6124619d4e9d291fada77b84bc705b56 | [
"MIT"
] | 3 | 2021-11-24T10:57:51.000Z | 2021-11-25T14:14:33.000Z | README.md | simonlindstedt/boomblox | 4d94419f6124619d4e9d291fada77b84bc705b56 | [
"MIT"
] | 1 | 2022-03-25T15:00:01.000Z | 2022-03-25T15:00:01.000Z | # Boomblox
<img src="./epicdj.gif" width="100%" />
## Description
An interactive canvas on which you can create music using web audio sound objects. There are oscillators, LFOs, recording functionality, effects such as reverb, filter and delay, a drum machine, and sequencers. Visit the project [here](https://boomblox.vercel.app).
<details><summary><b>Installation</b></summary>
- Clone repository from Github
- Run `npm install` in the root of the project to install the required dependencies.
- Run `npm run dev` in the root of the project to start a local server.
- Visit `localhost:3000` in your browser. Preferably Firefox or Chrome.
</details>
## Built with
- [Pixi.js](https://pixijs.com/)
- [Web Audio](https://developer.mozilla.org/en-US/docs/Web/API/Web_Audio_API)
- [ReactJS](https://reactjs.org/)
- [Framer motion](https://www.framer.com/motion/)
- [Styled Components](https://styled-components.com/)
- [Vite](https://vitejs.dev/)
## Created by
- [Moa Berg](https://github.com/moasannacatharina)
- [Rikard Segerkvist](https://github.com/rikardseg)
- [Simon Lindstedt](https://github.com/simonlindstedt)
| 35.25 | 265 | 0.73227 | eng_Latn | 0.695157 |
d3bd15b9e6c0c0c657dfb97179f299a5129b8afe | 966 | md | Markdown | README.md | eliah4real/Kahootflood.weebly.com | 29b8cfc51ff6407d2e753973f0203fdb65935153 | [
"Unlicense"
] | 1 | 2021-11-24T17:34:08.000Z | 2021-11-24T17:34:08.000Z | README.md | eliah4real/Kahootflood.weebly.com | 29b8cfc51ff6407d2e753973f0203fdb65935153 | [
"Unlicense"
] | null | null | null | README.md | eliah4real/Kahootflood.weebly.com | 29b8cfc51ff6407d2e753973f0203fdb65935153 | [
"Unlicense"
] | 7 | 2021-04-23T21:21:12.000Z | 2022-02-16T12:06:55.000Z | # Kahootflood.weebly.com
(Not the actual site, but the code of the download)
Kahootflood is a program especially designed to make people confused.
Great for April fools pranks and jokes.
## Installation
If you want the exe for quick use, go to https://kahootflood.weebly.com/d
To run the source on your computer or you are not on windows, do the following:
- Download node.js
- Download the source if you have not already
- Run your computer's terminal and cd to the file you saved the source in
- Type npm i (if you have not done so already)
- Type node flood.js
- Good to go!
## Contributing
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.
Please make sure to update tests as appropriate.
## Credit
If you are redistributing this, edited or not, please credit [me](https://www.youtube.com/c/StephenNobleIsAPerson).
It will make me very happy.
## License
[Unlicense](https://unlicense.org)
| 32.2 | 115 | 0.763975 | eng_Latn | 0.997394 |
d3bd8c746e79d1c5365f7d4b0d015cff5adf5524 | 3,778 | md | Markdown | README.md | orfar1994/nmos-js | dbe6a99b7f4be53cacc6b36c0c43c18c681854e0 | [
"Apache-2.0"
] | null | null | null | README.md | orfar1994/nmos-js | dbe6a99b7f4be53cacc6b36c0c43c18c681854e0 | [
"Apache-2.0"
] | null | null | null | README.md | orfar1994/nmos-js | dbe6a99b7f4be53cacc6b36c0c43c18c681854e0 | [
"Apache-2.0"
] | null | null | null | # An NMOS Client in JavaScript [][build-test]
[build-test]: https://github.com/sony/nmos-js/actions?query=workflow%3Abuild-test
## Introduction
This repository contains a client implementation of the [AMWA Networked Media Open Specifications](https://github.com/AMWA-TV/nmos) in JavaScript, [licensed](LICENSE) under the terms of the Apache License 2.0.
- [AMWA IS-04 NMOS Discovery and Registration Specification](https://amwa-tv.github.io/nmos-discovery-registration)
- [AMWA IS-05 NMOS Device Connection Management Specification](https://amwa-tv.github.io/nmos-device-connection-management)
For more information about AMWA, NMOS and the Networked Media Incubator, please refer to http://amwa.tv/.
The [repository structure](Documents/Repository-Structure.md), and the [external dependencies](Documents/Dependencies.md), are outlined in the documentation.
### Getting Started With NMOS
The [Easy-NMOS](https://github.com/rhastie/easy-nmos) starter kit allows the user to launch a simple NMOS setup with minimal installation steps.
It relies on nmos-js to provide an NMOS Client that works with an NMOS Registry and a virtual NMOS Node in a Docker Compose network, along with the AMWA NMOS Testing Tool and supporting services.
### Getting Started For Developers
Easy-NMOS is also a great first way to explore the relationship between NMOS services.
The nmos-js codebase is intended to work with any NMOS Registry, but can take advantage of the features of the [nmos-cpp](https://github.com/sony/nmos-cpp) implementation.
After setting up the dependencies, follow these [instructions](Documents/Getting-Started.md) to build and deploy the nmos-js client itself.
The web application can also be packaged and deployed with the [nmos-cpp-registry application](https://github.com/sony/nmos-cpp).
Copy the contents of the nmos-js build directory into the admin directory next to the nmos-cpp-registry executable.
## Agile Development
[<img alt="JT-NM Tested 03/20 NMOS & TR-1001-1 Controller" src="Documents/images/jt-nm-tested-03-20-controller.png?raw=true" height="135" align="right"/>](https://jt-nm.org/jt-nm_tested/)
The nmos-js client, like the NMOS Specifications, is intended to be always ready, but steadily developing.
The nmos-js client works as both an NMOS Registry browser, using the IS-04 Query API, and provides connection management, using the IS-05 Connection API.
When used with the nmos-cpp-registry, it also provides access to registry log messages.
It has been successfully tested in many AMWA Networked Media Incubator workshops, and in the [JT-NM Tested](https://jt-nm.org/jt-nm_tested/) programme.
### Recent Activity
The implementation is designed to be extended. Development is ongoing, following the evolution of the NMOS specifications in the AMWA Networked Media Incubator.
Recent activity on the project (newest first):
- Prototype implementation of BCP-004-01 Receiver Capabilities
- JT-NM Tested 03/20 badge (packaged and deployed on a Mellanox SN2010 Switch)
- Improved and simplified connection management
- Periodic refresh
- Lots of other incremental improvements
- Added support for multi-homed Nodes
- Added connection management support for RTP, WebSocket and MQTT transports
- Added a dark theme
- Switched to [react-admin](https://github.com/marmelab/react-admin) framework from [ng-admin](https://github.com/marmelab/ng-admin)
## Contributing
We welcome bug reports, feature requests and contributions to the implementation and documentation.
Please have a look at the simple [Contribution Guidelines](CONTRIBUTING.md).
Thank you for your interest!
| 59.03125 | 209 | 0.789836 | eng_Latn | 0.963744 |
d3be83463dfb1023a023d556ec30fc2f0df6b269 | 607 | md | Markdown | README.md | waheeduk/project_timer | 9ee394953225cc0b7ea51b3423ba47ae11635a96 | [
"MIT"
] | null | null | null | README.md | waheeduk/project_timer | 9ee394953225cc0b7ea51b3423ba47ae11635a96 | [
"MIT"
] | 4 | 2021-08-31T11:31:35.000Z | 2021-09-08T11:45:24.000Z | README.md | waheeduk/project_timer | 9ee394953225cc0b7ea51b3423ba47ae11635a96 | [
"MIT"
] | null | null | null | # PYTHON TIMER
This is a simple timer built using python that runs in your terminal.
## Running the timer
Clone the code onto your machine.
Navigate to the directory where the code was listed, and from your terminal on Mac, or cmd on Windows type:
```console
user@dir:~ python main.py
```
This will start the programme.
A helpful list of all possible commands can be found by typing --help.
## Dependencies
The programme runs on python 3, and uses a few standard python modules.
## Licence
The code is licensed under the [MIT License](https://github.com/waheeduk/project_timer/blob/main/LICENSE).
| 27.590909 | 108 | 0.759473 | eng_Latn | 0.998992 |
d3be8794b6554a63464b323f04935166daa15f40 | 13 | md | Markdown | README.md | MaoDenden/SFLive | aa0a47d437f94ba01b651a90c5b4c0b61a4beef4 | [
"MIT"
] | null | null | null | README.md | MaoDenden/SFLive | aa0a47d437f94ba01b651a90c5b4c0b61a4beef4 | [
"MIT"
] | null | null | null | README.md | MaoDenden/SFLive | aa0a47d437f94ba01b651a90c5b4c0b61a4beef4 | [
"MIT"
] | null | null | null | # SFLive
四不像
| 4.333333 | 8 | 0.692308 | deu_Latn | 0.309511 |
d3bf907d4d08c965c07a7fd2d433755ed1e9f9df | 802 | md | Markdown | overflow/git.md | joinpursuit/ac-curriculum-web | b2d85976660d8a41ec3185f50a0bb0242badf97d | [
"MIT"
] | 1 | 2019-04-26T08:19:27.000Z | 2019-04-26T08:19:27.000Z | overflow/git.md | joinpursuit/ac-curriculum-web | b2d85976660d8a41ec3185f50a0bb0242badf97d | [
"MIT"
] | null | null | null | overflow/git.md | joinpursuit/ac-curriculum-web | b2d85976660d8a41ec3185f50a0bb0242badf97d | [
"MIT"
] | null | null | null | <p><b>Author:</b> <span class="author-tag">Alex</span></p>
<p><b>Language:</b> <span class="language-tag">JavaScript</span></p>
<p><b>Topics:</b> <span class="topics-tags">for-loop, continue</span></p>
<p><b>Difficulty:</b> <span class="difficulty-tag">4</span></p>
<p><b>Format:</b> <span class="format-tag">coding</span></p>
<h3 class='question-header'>Question</h3>
<p class='question-text'>Write a `for` loop that counts down from 100 to 10 by 10, and then from 10 to 1 by 1. The loop should print a single number on each line. Use a single loop; do not use multiple loops.</p>
<h3 class='answer-header'>Answer</h3>
<pre><code class='answer-text'>
for(var i = 100; i >= 1; i -= 1) {
if(i > 10 && i % 10 === 0) {
console.log(i)
} else if(i <= 10){
console.log(i)
}
}
</code></pre> | 40.1 | 214 | 0.630923 | eng_Latn | 0.707127 |
d3c07cd8e58a78707771c9d4d795e604d2161949 | 2,967 | md | Markdown | README.md | samWson/rusty-ruby | 43878320bb9ab2be634aa52429c4d24b86652577 | [
"MIT"
] | 2 | 2018-12-20T03:58:51.000Z | 2019-10-19T15:08:09.000Z | README.md | samWson/rusty-ruby | 43878320bb9ab2be634aa52429c4d24b86652577 | [
"MIT"
] | null | null | null | README.md | samWson/rusty-ruby | 43878320bb9ab2be634aa52429c4d24b86652577 | [
"MIT"
] | null | null | null | # Rusty Ruby
Learn how Ruby works by implementing it in Rust.
## Description
A good way to understand how something works is to make it. The goal of this project is to implement a Ruby interpreter using the Rust programming language.
### Interpreting Ruby
Source code for any language goes through several stages before any instructions are executed. A *lexer* analyses the source code and produces tokens, which are the *parts* of the language. A *parser* will parse the tokens into an *abstract syntax tree* or *AST* which represents the syntax of a program. An *interpreter* will then interpret the AST and execute the instructions required by the program.
## Dependencies
Make sure you have [Rust](https://www.rust-lang.org/en-US/install.html) installed.
## Usage
The program is an attempt to do the first stage of interpreting a Ruby program: Tokenization. A ruby file provided as an argument and the program outputs the resulting tokens.
```
$ cargo run sample_ruby.rb
```
If the program is run without arguments it will enter a Read Eval Print loop. Arbitrary code can be entered at the command line and the tokens will be produced as output.
### Limitations
Currently only the most basic syntax will be supported. The example program `sample_ruby.rb` gives an indication of what can be tokenized. As the supported syntax grows more expressions can be added to `sample_ruby.rb`.
```
x = 2 + 3
five = 5
TEN = 10
def add(x, y)
return x + y
end
result = add(five, TEN)
boolean_result = !(5 < 10 > 5)
if (5 < 10)
return true
else
return false
end
10 == 10
10 != 9
```
Note that it is not the responsibility of the Tokenizer to spot syntax errors. Any unrecognized character will be output as an illegal token.
## Code Layout
The source code is broken down into separate files based on responsibility.
### Main
`main.rs` is the entry point of the program.
### Lexer
`lexer.rs` is responsible for lexical analysis. A lexer scans each character in Ruby source code and produces appropriate tokens based on the values it scans.
### REPL
`repl.rs` is responsible for the Read Eval Print Loop. This can evaluate arbitrary code from the standard input, evaluate it, and print the result to the standard output. Currently it only outputs tokens.
### Token
`token.rs` is responsible for defining the tokens of the Ruby language. A token is a part of a language such as keywords, operators, identifiers etc.
## Licence
This project is Open Sourced under the MIT licence. Although this project is personal learning exercise, it has been made using company time at [Flux Federation](http://fluxfederation.com/) during our hack days. All copyright and IP belongs to Flux Federation.
## Contributions
Contributions are welcome as long as the contributor is happy with the licencing and copyright as described above.
| 40.094595 | 403 | 0.76879 | eng_Latn | 0.998539 |
d3c0ab85fbb774351525106c103b79e5830b8628 | 5,519 | md | Markdown | articles/virtual-machines/linux/sizes-hpc.md | p770820/azure-docs.zh-tw | dd2bd917784a4df8b52787a299a3df42e05642fe | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/virtual-machines/linux/sizes-hpc.md | p770820/azure-docs.zh-tw | dd2bd917784a4df8b52787a299a3df42e05642fe | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/virtual-machines/linux/sizes-hpc.md | p770820/azure-docs.zh-tw | dd2bd917784a4df8b52787a299a3df42e05642fe | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Azure Linux VM 大小-HPC
description: 列出 Azure 中可用的不同 Linux 高效能運算虛擬機器大小。 列出 vCPU 數目、資料磁碟和 NIC 的相關資訊，以及此服務中各種大小之儲存體輸送量和網路頻寬的相關資訊。
services: virtual-machines-linux
documentationcenter: ''
author: jonbeck7
manager: gwallace
editor: ''
tags: azure-resource-manager,azure-service-management
ms.assetid: ''
ms.service: virtual-machines-linux
ms.topic: article
ms.tgt_pltfrm: vm-linux
ms.workload: infrastructure-services
ms.date: 10/12/2018
ms.author: jonbeck
ms.openlocfilehash: 214ab48b6b0dca37eff3b3f155aaa92afc7fee16
ms.sourcegitcommit: 49cf9786d3134517727ff1e656c4d8531bbbd332
ms.translationtype: MT
ms.contentlocale: zh-TW
ms.lasthandoff: 11/13/2019
ms.locfileid: "74034901"
---
# <a name="high-performance-compute-virtual-machine-sizes"></a>高效能運算的虛擬機器大小
[!INCLUDE [virtual-machines-common-sizes-hpc](../../../includes/virtual-machines-common-sizes-hpc.md)]
[!INCLUDE [virtual-machines-common-sizes-table-defs](../../../includes/virtual-machines-common-sizes-table-defs.md)]
[!INCLUDE [virtual-machines-common-a8-a9-a10-a11-specs](../../../includes/virtual-machines-common-a8-a9-a10-a11-specs.md)]
### <a name="mpi"></a>MPI
Azure 上已啟用 SR-IOV 的 VM 大小幾乎可讓您使用任何 MPI 的類別。
在未啟用 SR-IOV 的 Vm 上，只支援 Intel MPI 5.x 版本。 Intel MPI 執行時間程式庫的較新版本（2017、2018）可能會與 Azure Linux RDMA 驅動程式不相容。
### <a name="supported-os-images"></a>支援的作業系統映像
Azure Marketplace 有許多支援 RDMA 連線能力的 Linux 散發套件：
* **CentOS 為基礎的 hpc** -針對非 sr-iov 啟用的 Vm，CentOS 型版本 6.5 HPC 或更新版本，最多可達7.5。 針對 H 系列 Vm，建議使用7.1 到7.5 版。 已在 VM 上安裝 RDMA 驅動程式和 Intel MPI 5.1。
針對 SR-IOV Vm，CentOS-HPC 7.6 已針對 RDMA 驅動程式和安裝的各種 MPI 套件進行優化和預先載入。
若為其他 RHEL/CentOS VM 映射，請新增 InfiniBandLinux 延伸模組以啟用 [未使用]。 此 Linux VM 擴充功能會安裝適用于 RDMA 連線的 Mellanox OFED 驅動程式（在 SR-IOV Vm 上）。 下列 PowerShell Cmdlet 會在現有具備 RDMA 功能的 VM 上安裝 InfiniBandDriverLinux 延伸模組的最新版本（版本1.0）。 具備 RDMA 功能的 VM 會命名為*myVM* ，並部署在*美國西部*區域中名為*myResourceGroup*的資源群組中，如下所示：
```powershell
Set-AzVMExtension -ResourceGroupName "myResourceGroup" -Location "westus" -VMName "myVM" -ExtensionName "InfiniBandDriverLinux" -Publisher "Microsoft.HpcCompute" -Type "InfiniBandDriverLinux" -TypeHandlerVersion "1.0"
```
或者，您可以將 VM 擴充功能包含在 Azure Resource Manager 範本中，以便使用下列 JSON 元素進行輕鬆部署：
```json
"properties":{
"publisher": "Microsoft.HpcCompute",
"type": "InfiniBandDriverLinux",
"typeHandlerVersion": "1.0",
}
```
下列命令會在名為*myResourceGroup*的資源群組中名為*MYVMSS*的現有 VM 擴展集內的所有支援 RDMA 的 vm 上，安裝最新版本 1.0 InfiniBandDriverLinux 延伸模組：
```powershell
$VMSS = Get-AzVmss -ResourceGroupName "myResourceGroup" -VMScaleSetName "myVMSS"
Add-AzVmssExtension -VirtualMachineScaleSet $VMSS -Name "InfiniBandDriverLinux" -Publisher "Microsoft.HpcCompute" -Type "InfiniBandDriverLinux" -TypeHandlerVersion "1.0"
Update-AzVmss -ResourceGroupName "myResourceGroup" -VMScaleSetName "MyVMSS" -VirtualMachineScaleSet $VMSS
Update-AzVmssInstance -ResourceGroupName "myResourceGroup" -VMScaleSetName "myVMSS" -InstanceId "*"
```
> [!NOTE]
> 在 CentOS 型 HPC 映像上， **yum** 組態檔中已停用核心更新。 這是因為 Linux RDMA 驅動程式是以 RPM 套件的形式散發，如果核心已更新，驅動程式更新可能無法正常執行。
>
* **SUSE Linux Enterprise Server** -SLES 12 SP3 for HPC、SLES 12 SP3 for Hpc （premium）、SLES 12 SP1 for HPC、SLES 12 SP1 for Hpc （Premium）、SLES 12 SP4 和 sles 15。 已在 VM 上安裝 RDMA 驅動程式並散發 Intel MPI 套件。 執行下列命令來安裝 MPI：
```bash
sudo rpm -v -i --nodeps /opt/intelMPI/intel_mpi_packages/*.rpm
```
* **Ubuntu** -ubuntu SERVER 16.04 LTS、18.04 LTS。 設定 VM 上的 RDMA 驅動程式，並向 Intel 註冊以下載 Intel MPI：
[!INCLUDE [virtual-machines-common-ubuntu-rdma](../../../includes/virtual-machines-common-ubuntu-rdma.md)]
如需有關啟用「未[使用](../workloads/hpc/enable-infiniband.md)」的詳細資訊，請參閱設定 MPI。
### <a name="cluster-configuration-options"></a>叢集組態選項
Azure 提供數個選項來建立 Linux HPC VM 的叢集，而這些 VM 可以使用 RDMA 網路進行通訊，包括：
* **虛擬機器** - 在相同的可用性設定組中部署支援 RDMA 的 HPC VM (當您使用 Azure Resource Manager 部署模型時)。 如果您使用傳統部署模型，請將 VM 部署在相同的雲端服務中。
* **虛擬機器擴展集**-在虛擬機器擴展集中，請確定您將部署限制為單一放置群組。 例如，在 Resource Manager 範本中，將 `singlePlacementGroup` 屬性設定為 `true`。
* **虛擬機器之間的 mpi** -如果虛擬機器（vm）之間需要 mpi 通訊，請確定 vm 位於相同的可用性設定組或虛擬機器相同的擴展集內。
* **Azure CycleCloud** - 在 [Azure CycleCloud](/azure/cyclecloud/) 中建立 HPC 叢集，以在 Linux 節點上執行 MPI 作業。
* **Azure Batch** -建立 [Azure Batch](/azure/batch/)集區以在 Linux 計算節點上執行 MPI 工作負載。 如需詳細資訊，請參閱[在 Batch 集區中使用支援 RDMA 或已啟用 GPU 功能的執行個體](../../batch/batch-pool-compute-intensive-sizes.md)。 另請參閱 [Batch Shipyard](https://github.com/Azure/batch-shipyard) 專案，以便在 Batch 上執行以容器為基礎的工作負載。
* **Microsoft HPC Pack** - [HPC Pack](https://docs.microsoft.com/powershell/high-performance-computing/overview) 支援讓數個 Linux 散發套件在部署於支援 RDMA 的 Azure VM 中、由 Windows Server 前端節點管理的計算節點上執行。 如需範例部署，請參閱[在 Azure 中建立 HPC Pack Linux RDMA 叢集](https://docs.microsoft.com/powershell/high-performance-computing/hpcpack-linux-openfoam)。
### <a name="network-considerations"></a>網路考量
* 在非 SR-IOV 的 Azure 中啟用 RDMA 的 Linux Vm 上，eth1 會保留給 RDMA 網路流量。 請勿變更任何 eth1 設定或參考此網路之設定檔中的任何資訊。
* 在啟用 SR-IOV 的 Vm （HB 和 HC 系列）上，ib0 會保留給 RDMA 網路流量。
* Azure 中的 RDMA 網路會保留位址空間 172.16.0.0/16。 若要在 Azure 虛擬網路中已部署的執行個體上執行 MPI 應用程式，請確定虛擬網路位址空間不會與 RDMA 網路重疊。
* 視您選擇的叢集管理工具而定，可能需要額外系統設定才能執行 MPI 作業。 例如，在 Vm 叢集上，您可能需要藉由產生 SSH 金鑰或建立無密碼 SSH 登入，在叢集節點之間建立信任。
## <a name="other-sizes"></a>其他大小
- [一般用途](sizes-general.md)
- [計算最佳化](sizes-compute.md)
- [記憶體最佳化](sizes-memory.md)
- [儲存體最佳化](sizes-storage.md)
- [GPU](../windows/sizes-gpu.md)
- [前幾代](sizes-previous-gen.md)
## <a name="next-steps"></a>後續步驟
- 深入瞭解如何在 Azure 上設定、優化和調整[HPC 工作負載](../workloads/hpc/configure.md)。
- 深入了解 [Azure 計算單位 (ACU)](acu.md) 如何協助您比較各個 Azure SKU 的計算效能。
| 45.61157 | 323 | 0.747237 | yue_Hant | 0.976057 |
d3c131855e9f8192aa477109110a027e8a087d31 | 3,049 | md | Markdown | WindowsServerDocs/administration/windows-commands/wbadmin-restore-catalog.md | eltociear/windowsserverdocs.pt-br | c545b674a2e6c17cb3b83bca28474b7f5a9a6637 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | WindowsServerDocs/administration/windows-commands/wbadmin-restore-catalog.md | eltociear/windowsserverdocs.pt-br | c545b674a2e6c17cb3b83bca28474b7f5a9a6637 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | WindowsServerDocs/administration/windows-commands/wbadmin-restore-catalog.md | eltociear/windowsserverdocs.pt-br | c545b674a2e6c17cb3b83bca28474b7f5a9a6637 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Wbadmin restore catalog
description: O tópico de comandos do Windows para Wbadmin restore catalog, que recupera um catálogo de backup para o computador local de um local de armazenamento que você especificar.
ms.prod: windows-server
ms.technology: manage-windows-commands
ms.topic: article
ms.assetid: ce1e24a0-821d-4353-b09d-8f82c5c4ad56
author: coreyp-at-msft
ms.author: coreyp
manager: dongill
ms.date: 10/16/2017
ms.openlocfilehash: 0ce9182e4e405b1538277db25f06b6a49d7240f9
ms.sourcegitcommit: b00d7c8968c4adc8f699dbee694afe6ed36bc9de
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 04/08/2020
ms.locfileid: "80829699"
---
# <a name="wbadmin-restore-catalog"></a>Wbadmin restore catalog
Recupera um catálogo de backup do computador local de um local de armazenamento que você especificar.
Para recuperar um catálogo de backup com este subcomando, você deve ser um membro do grupo **operadores de backup** ou do grupo **Administradores** ou ter recebido as permissões apropriadas. Além disso, você deve executar o **Wbadmin** em um prompt de comandos com privilégios elevados. (Para abrir um prompt de comando com privilégios elevados, clique com o botão direito do mouse em **prompt de comando**e clique em **Executar como administrador**.)
Para obter exemplos de como usar esse subcomando, consulte [exemplos](#BKMK_examples).
## <a name="syntax"></a>Sintaxe
```
wbadmin restore catalog
-backupTarget:{<BackupDestinationVolume> | <NetworkShareHostingBackup>}
[-machine:<BackupMachineName>]
[-quiet]
```
### <a name="parameters"></a>Parâmetros
|Parâmetro|Descrição|
|---------|-----------|
|-backupTarget|Especifica o local do catálogo de backup do sistema como ele estava no ponto em que o backup foi criado.|
|-computador|Especifica o nome do computador para o qual você deseja recuperar o catálogo de backup. Use quando os backups de vários computadores tiverem sido armazenados no mesmo local. Deve ser usado quando **-backupTarget** é especificado.|
|-quiet|Executa o subcomando sem prompts para o usuário.|
## <a name="remarks"></a>Comentários
Se o local (disco, DVD ou pasta compartilhada remota) em que você armazena seus backups estiver danificado ou perdido e não puder ser usado para restaurar o catálogo de backup, use **Wbadmin Delete Catalog** para excluir o catálogo corrompido. Nesse caso, você deve criar um novo backup depois que o catálogo de backup for excluído.
## <a name="examples"></a><a name=BKMK_examples></a>Disso
Para restaurar um catálogo de um backup armazenado em disco d:, digite:
```
wbadmin restore catalog -backupTarget:d
```
Para restaurar um catálogo de um backup armazenado na pasta compartilhada \\\\servername\share de Server01, digite:
```
wbadmin restore catalog -backupTarget:\\servername\share -machine:server01
```
## <a name="additional-references"></a>Referências adicionais
- - [Chave da sintaxe de linha de comando](command-line-syntax-key.md)
- [Wbadmin](wbadmin.md)
- Cmdlet [Restore-WBCatalog](https://technet.microsoft.com/library/jj902437.aspx) | 46.907692 | 451 | 0.775336 | por_Latn | 0.988721 |
d3c132911adfff7a6187a85ce9d85f5ecbff3691 | 929 | md | Markdown | README.md | chenrz925/tasker | d41aa1bd76b2f2f834d14b92183da3aa8179721e | [
"Apache-2.0"
] | 2 | 2020-07-17T16:55:21.000Z | 2020-07-19T02:34:46.000Z | README.md | chenrz925/tasker | d41aa1bd76b2f2f834d14b92183da3aa8179721e | [
"Apache-2.0"
] | null | null | null | README.md | chenrz925/tasker | d41aa1bd76b2f2f834d14b92183da3aa8179721e | [
"Apache-2.0"
] | null | null | null | # Tasker
[](https://pypi.org/project/waterch-tasker/)
A scalable and extendable experiment task scheduler framework. [Documentation](http://tasker.waterch.cn)
## Install
You can install waterch-tasker using `pip`.
```shell
pip install waterch-tasker
```
And if you want a more simple and robust version of waterch-tasker, please install v0.2.10.
```shell
pip install waterch-tasker==0.2.10
```
## Usage
When waterch-tasker is installed, please use `--help` command.
```shell
waterch-tasker --help
```
or
```shell
tasker --help
```
| 23.820513 | 118 | 0.745963 | eng_Latn | 0.47515 |
d3c2ac4f428803ffef99337adce339dfc38ee5f6 | 25,484 | md | Markdown | articles/load-balancer/move-across-regions-external-load-balancer-portal.md | KreizIT/azure-docs.fr-fr | dfe0cb93ebc98e9ca8eb2f3030127b4970911a06 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-03-12T23:37:08.000Z | 2021-03-12T23:37:08.000Z | articles/load-balancer/move-across-regions-external-load-balancer-portal.md | KreizIT/azure-docs.fr-fr | dfe0cb93ebc98e9ca8eb2f3030127b4970911a06 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/load-balancer/move-across-regions-external-load-balancer-portal.md | KreizIT/azure-docs.fr-fr | dfe0cb93ebc98e9ca8eb2f3030127b4970911a06 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Déplacer un équilibreur de charge externe Azure vers une autre région Azure à l’aide du portail Azure
description: Utilisez un modèle Azure Resource Manager pour déplacer un équilibreur de charge externe Azure d’une région Azure vers une autre à l’aide du portail Azure.
author: asudbring
ms.service: load-balancer
ms.topic: how-to
ms.date: 09/17/2019
ms.author: allensu
ms.openlocfilehash: b9eabb4f49a533c97177dc0598e425ab63b20ec5
ms.sourcegitcommit: 692382974e1ac868a2672b67af2d33e593c91d60
ms.translationtype: HT
ms.contentlocale: fr-FR
ms.lasthandoff: 10/22/2021
ms.locfileid: "130258712"
---
# <a name="move-an-external-load-balancer-to-another-region-by-using-the-azure-portal"></a>Déplacer un équilibreur de charge externe vers une autre région à l’aide du portail Azure
Il existe différents scénarios dans lesquels vous pouvez avoir à déplacer un équilibreur de charge externe d’une région à une autre. Par exemple, vous souhaiterez peut-être créer un autre équilibreur de charge externe avec la même configuration à des fins de test. Vous pouvez également déplacer un équilibreur de charge externe vers une autre région dans le cadre de la planification de la reprise d’activité après sinistre.
Vous ne pouvez pas à proprement parler déplacer un équilibreur de charge externe Azure d’une région vers une autre. Toutefois, vous pouvez utiliser un modèle Azure Resource Manager pour exporter la configuration existante et l’adresse IP publique d’un équilibreur de charge externe. Vous pouvez ensuite déplacer la ressource dans une autre région en exportant l’équilibreur de charge et l’adresse IP publique vers un modèle, en modifiant les paramètres pour qu’ils correspondent à la région de destination, puis en déployant les modèles dans la nouvelle région. Pour plus d’informations sur Resource Manager et les modèles, consultez [Exporter des groupes de ressources vers des modèles](../azure-resource-manager/management/manage-resource-groups-powershell.md#export-resource-groups-to-templates).
## <a name="prerequisites"></a>Prérequis
- Vérifiez que l’équilibreur de charge externe se trouve dans la région Azure à partir de laquelle vous souhaitez effectuer le déplacement.
- Les équilibreurs de charge externes Azure ne peuvent pas être déplacés entre les régions. Vous devez associer le nouvel équilibreur de charge à des ressources de la région cible.
- Pour exporter une configuration d’équilibreur de charge externe et déployer un modèle afin de créer un équilibreur de charge externe dans une autre région, vous devez disposer au moins du rôle Contributeur de réseaux.
- Identifiez la topologie du réseau source et toutes les ressources que vous utilisez actuellement. Cette disposition comprend notamment les équilibreurs de charge, les groupes de sécurité réseau, les adresses IP publiques et les réseaux virtuels.
- Vérifiez que votre abonnement Azure vous permet de créer des équilibreurs de charge externes dans la région cible. Contactez le support pour activer le quota requis.
- Vérifiez que votre abonnement dispose de suffisamment de ressources pour prendre en charge l’ajout d’équilibreurs de charge. Consultez [Abonnement Azure et limites, quotas et contraintes de service](../azure-resource-manager/management/azure-subscription-service-limits.md#networking-limits).
## <a name="prepare-and-move"></a>Préparer et déplacer
Les procédures suivantes montrent comment préparer l’équilibreur de charge externe pour le déplacement à l’aide d’un modèle Resource Manager, et déplacer la configuration de l’équilibreur de charge externe vers la région cible à l’aide du portail Azure. Vous devez commencer par exporter la configuration d’adresse IP publique de l’équilibreur de charge externe.
[!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
### <a name="export-the-public-ip-template-and-deploy-the-public-ip-from-the-portal"></a>Exporter le modèle d’adresse IP publique et déployer l’adresse IP publique à partir du portail
1. Connectez-vous au [portail Azure](https://portal.azure.com), puis sélectionnez **Groupes de ressources**.
2. Recherchez le groupe de ressources qui contient l’adresse IP publique source et sélectionnez-le.
3. Sélectionnez **Paramètres** > **Exporter le modèle**.
4. Sélectionnez **Déployer** sous **Exporter le modèle**.
5. Sélectionnez **MODÈLE** > **Modifier les paramètres** pour ouvrir le fichier parameters.json dans l’éditeur en ligne.
8. Pour modifier le paramètre du nom d’adresse IP publique, remplacez la propriété **value** sous **parameters** par le nom de votre adresse IP publique cible. Veillez à placer le nom entre guillemets.
```json
{
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
"contentVersion": "1.0.0.0",
"parameters": {
"publicIPAddresses_myVM1pubIP_name": {
"value": "<target-publicip-name>"
}
}
}
```
Sélectionnez **Enregistrer** dans l’éditeur.
9. Sélectionnez **MODÈLE** > **Modifier le modèle** pour ouvrir le fichier template.json dans l’éditeur en ligne.
10. Pour modifier la région cible vers laquelle l’adresse IP publique sera déplacée, changez la propriété **location** sous **resources** :
```json
"resources": [
{
"type": "Microsoft.Network/publicIPAddresses",
"apiVersion": "2019-06-01",
"name": "[parameters('publicIPAddresses_myPubIP_name')]",
"location": "<target-region>",
"sku": {
"name": "Basic",
"tier": "Regional"
},
"properties": {
"provisioningState": "Succeeded",
"resourceGuid": "7549a8f1-80c2-481a-a073-018f5b0b69be",
"ipAddress": "52.177.6.204",
"publicIPAddressVersion": "IPv4",
"publicIPAllocationMethod": "Dynamic",
"idleTimeoutInMinutes": 4,
"ipTags": []
}
}
]
```
Pour obtenir les codes d’emplacement des régions, consultez [Emplacements Azure](https://azure.microsoft.com/global-infrastructure/locations/). Le code d’une région est le nom de la région sans espace. Par exemple, le code pour Central US (USA Centre) est **centralus**.
12. Vous pouvez également changer d’autres paramètres dans le modèle, en fonction de vos besoins :
* **Référence (SKU)** : vous pouvez permuter la référence SKU de l’adresse IP publique dans la configuration entre les valeurs basic et standard en modifiant la propriété **name** sous **sku** dans le fichier template.json :
```json
"resources": [
{
"type": "Microsoft.Network/publicIPAddresses",
"apiVersion": "2019-06-01",
"name": "[parameters('publicIPAddresses_myPubIP_name')]",
"location": "<target-region>",
"sku": {
"name": "Basic",
"tier": "Regional"
},
```
Pour plus d’informations sur les différences entre les adresses IP publiques des références SKU basic et standard, consultez [Créer, modifier ou supprimer une adresse IP publique](../virtual-network/ip-services/virtual-network-public-ip-address.md).
* **Méthode d’allocation des adresses IP publiques** et **Délai d’inactivité**. Vous pouvez modifier la méthode d’allocation des adresses IP publiques en changeant la valeur de la propriété **publicIPAllocationMethod** de **Dynamic** à **Static** ou de **Static** à **Dynamic**. Vous pouvez modifier le délai d’inactivité en indiquant la valeur souhaitée dans la propriété **idleTimeoutInMinutes**. La valeur par défaut est **4**.
```json
"resources": [
{
"type": "Microsoft.Network/publicIPAddresses",
"apiVersion": "2019-06-01",
"name": "[parameters('publicIPAddresses_myPubIP_name')]",
"location": "<target-region>",
"sku": {
"name": "Basic",
"tier": "Regional"
},
"properties": {
"provisioningState": "Succeeded",
"resourceGuid": "7549a8f1-80c2-481a-a073-018f5b0b69be",
"ipAddress": "52.177.6.204",
"publicIPAddressVersion": "IPv4",
"publicIPAllocationMethod": "Dynamic",
"idleTimeoutInMinutes": 4,
"ipTags": []
```
Pour plus d’informations sur les méthodes d’allocation et les valeurs de délai d’inactivité, consultez [Créer, modifier ou supprimer une adresse IP publique](../virtual-network/ip-services/virtual-network-public-ip-address.md).
13. Sélectionnez **Enregistrer** dans l’éditeur en ligne.
14. Sélectionnez **OPTIONS DE BASE** > **Abonnement** pour choisir l’abonnement dans lequel l’adresse IP publique cible sera déployée.
15. Sélectionnez **OPTIONS DE BASE** > **Groupe de ressources** pour choisir le groupe de ressources dans lequel l’adresse IP publique cible sera déployée. Vous pouvez sélectionner **Créer** afin de créer un groupe de ressources pour l’adresse IP publique cible. Vérifiez que le nom n’est pas identique à celui du groupe de ressources source de l’adresse IP publique cible existante.
16. Vérifiez que **OPTIONS DE BASE** > **Emplacement** est défini sur l’emplacement cible où vous souhaitez déployer l’adresse IP publique.
17. Sous **PARAMÈTRES**, vérifiez que le nom correspond à celui que vous avez entré précédemment dans l’éditeur de paramètres.
18. Cochez la case **CONDITIONS GÉNÉRALES**.
19. Sélectionnez **Acheter** pour déployer l’adresse IP publique cible.
20. Si vous avez une autre adresse IP publique utilisée pour la traduction d’adresses réseau pour le trafic sortant pour l’équilibreur de charge en cours de déplacement, répétez les étapes ci-dessus pour exporter et déployer la deuxième adresse IP publique sortante vers la région cible.
### <a name="export-the-external-load-balancer-template-and-deploy-the-load-balancer-from-the-azure-portal"></a>Exporter le modèle d’équilibreur de charge externe et déployer l’équilibreur de charge à partir du portail Azure
1. Connectez-vous au [portail Azure](https://portal.azure.com), puis sélectionnez **Groupes de ressources**.
2. Recherchez le groupe de ressources qui contient l’équilibreur de charge externe source, puis sélectionnez-le.
3. Sélectionnez **Paramètres** > **Exporter le modèle**.
4. Sélectionnez **Déployer** sous **Exporter le modèle**.
5. Sélectionnez **MODÈLE** > **Modifier les paramètres** pour ouvrir le fichier parameters.json dans l’éditeur en ligne.
5. Pour modifier le paramètre du nom de l’équilibreur de charge externe, remplacez la propriété **value** du nom de l’équilibreur de charge externe source par le nom de votre équilibreur de charge externe cible. Veillez à placer le nom entre guillemets.
```json
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
"contentVersion": "1.0.0.0",
"parameters": {
"loadBalancers_myLoadbalancer_ext_name": {
"value": "<target-external-lb-name>"
},
"publicIPAddresses_myPubIP_in_externalid": {
"value": "<target-publicIP-resource-ID>"
},
```
6. Pour modifier la valeur de l’adresse IP publique cible que vous avez déplacée au cours des étapes précédentes, vous devez d’abord obtenir l’ID de ressource, puis le coller dans le fichier parameters.json. Pour obtenir l’ID :
1. Dans un autre onglet ou une autre fenêtre de navigateur, connectez-vous au [portail Azure](https://portal.azure.com) et sélectionnez **Groupes de ressources** .
2. Recherchez le groupe de ressources cible contenant l’adresse IP publique déplacée au cours des étapes précédentes. Sélectionnez-le.
3. Sélectionnez **Paramètres** > **Propriétés**.
4. Dans le panneau de droite, mettez en surbrillance l’**ID de ressource** et copiez-le dans le Presse-papiers. Vous pouvez également sélectionner **Copier dans le Presse-papiers** à droite du chemin de l’**ID de ressource**.
5. Collez l’ID de ressource dans la propriété **value** dans l’éditeur **Modifier les paramètres** ouvert dans l’autre fenêtre ou onglet de navigateur :
```json
```json
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
"contentVersion": "1.0.0.0",
"parameters": {
"loadBalancers_myLoadbalancer_ext_name": {
"value": "<target-external-lb-name>"
},
"publicIPAddresses_myPubIP_in_externalid": {
"value": "<target-publicIP-resource-ID>"
},
```
6. Sélectionnez **Enregistrer** dans l’éditeur en ligne.
7. Si vous avez configuré la traduction d’adresses réseau pour le trafic sortant et des règles de trafic sortant pour l’équilibreur de charge, une troisième entrée sera présente dans ce fichier pour l’ID externe de l’adresse IP publique sortante. Répétez les étapes précédentes dans la **région cible** pour obtenir l’ID de l’adresse IP publique sortante. Collez cet ID dans le fichier parameters.json :
```json
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
"contentVersion": "1.0.0.0",
"parameters": {
"loadBalancers_myLoadbalancer_ext_name": {
"value": "<target-external-lb-name>",
},
"publicIPAddresses_myPubIP_in_externalid": {
"value": "<target-publicIP-resource-ID>",
},
"publicIPAddresses_myPubIP_out_externalid": {
"defaultValue": "<target-publicIP-outbound-resource-ID>",
}
},
```
8. Sélectionnez **MODÈLE** > **Modifier le modèle** pour ouvrir le fichier template.json dans l’éditeur en ligne.
9. Pour modifier la région cible dans laquelle la configuration de l’équilibreur de charge externe sera déplacée, modifiez la propriété **location** sous **resources** dans le fichier template.json :
```json
"resources": [
{
"type": "Microsoft.Network/loadBalancers",
"apiVersion": "2019-06-01",
"name": "[parameters('loadBalancers_myLoadBalancer_name')]",
"location": "<target-external-lb-region>",
"sku": {
"name": "Standard",
"tier": "Regional"
},
```
10. Pour obtenir les codes d’emplacement des régions, consultez [Emplacements Azure](https://azure.microsoft.com/global-infrastructure/locations/). Le code d’une région est le nom de la région sans espace. Par exemple, le code pour Central US (USA Centre) est **centralus**.
11. Vous pouvez également changer d’autres paramètres dans le modèle, en fonction de vos besoins :
* **Référence (SKU)** : vous pouvez permuter la référence SKU de l’équilibreur de charge externe dans la configuration entre les valeurs basic et standard en modifiant la propriété **name** sous **sku** dans le fichier template.json :
```json
"resources": [
{
"type": "Microsoft.Network/loadBalancers",
"apiVersion": "2019-06-01",
"name": "[parameters('loadBalancers_myLoadBalancer_name')]",
"location": "<target-external-lb-region>",
"sku": {
"name": "Standard",
"tier": "Regional"
},
```
Pour plus d’informations sur les différences entre les équilibreurs de charge des références SKU basic et standard, consultez [Présentation d’Azure Standard Load Balancer](./load-balancer-overview.md).
* **Règles d’équilibrage de charge** : vous pouvez ajouter ou supprimer des règles d’équilibrage de charge dans la configuration en ajoutant ou en supprimant des entrées dans la section **loadBalancingRules** du fichier template.json :
```json
"loadBalancingRules": [
{
"name": "myInboundRule",
"etag": "W/\"39e5e9cd-2d6d-491f-83cf-b37a259d86b6\"",
"properties": {
"provisioningState": "Succeeded",
"frontendIPConfiguration": {
"id": "[concat(resourceId('Microsoft.Network/loadBalancers', parameters('loadBalancers_myLoadBalancer_name')), '/frontendIPConfigurations/myfrontendIPinbound')]"
},
"frontendPort": 80,
"backendPort": 80,
"enableFloatingIP": false,
"idleTimeoutInMinutes": 4,
"protocol": "Tcp",
"enableTcpReset": false,
"loadDistribution": "Default",
"disableOutboundSnat": true,
"backendAddressPool": {
"id": "[concat(resourceId('Microsoft.Network/loadBalancers', parameters('loadBalancers_myLoadBalancer_name')), '/backendAddressPools/myBEPoolInbound')]"
},
"probe": {
"id": "[concat(resourceId('Microsoft.Network/loadBalancers', parameters('loadBalancers_myLoadBalancer_name')), '/probes/myHTTPProbe')]"
}
}
}
]
```
Pour plus d’informations sur les règles d’équilibrage de charge, consultez [Qu’est-ce qu’Azure Load Balancer ?](load-balancer-overview.md).
* **Sondes** : vous pouvez ajouter ou supprimer une sonde pour l’équilibreur de charge dans la configuration en ajoutant ou en supprimant des entrées dans la section **probes** du fichier template.json :
```json
"probes": [
{
"name": "myHTTPProbe",
"etag": "W/\"39e5e9cd-2d6d-491f-83cf-b37a259d86b6\"",
"properties": {
"provisioningState": "Succeeded",
"protocol": "Http",
"port": 80,
"requestPath": "/",
"intervalInSeconds": 15,
"numberOfProbes": 2
}
}
],
```
Pour plus d’informations, consultez [Sondes d’intégrité Load Balancer](load-balancer-custom-probe-overview.md).
* **Règles NAT de trafic entrant** : vous pouvez ajouter ou supprimer des règles NAT de trafic entrant pour l’équilibreur de charge en ajoutant ou en supprimant des entrées dans la section **inboundNatRules** du fichier template.json :
```json
"inboundNatRules": [
{
"name": "myInboundNATRule",
"etag": "W/\"39e5e9cd-2d6d-491f-83cf-b37a259d86b6\"",
"properties": {
"provisioningState": "Succeeded",
"frontendIPConfiguration": {
"id": "[concat(resourceId('Microsoft.Network/loadBalancers', parameters('loadBalancers_myLoadBalancer_name')), '/frontendIPConfigurations/myfrontendIPinbound')]"
},
"frontendPort": 4422,
"backendPort": 3389,
"enableFloatingIP": false,
"idleTimeoutInMinutes": 4,
"protocol": "Tcp",
"enableTcpReset": false
}
}
]
```
Pour terminer l’ajout ou la suppression d’une règle NAT de trafic entrant, il faut que la règle soit présente ou supprimée en tant que propriété **type** à la fin du fichier template.json :
```json
{
"type": "Microsoft.Network/loadBalancers/inboundNatRules",
"apiVersion": "2019-06-01",
"name": "[concat(parameters('loadBalancers_myLoadBalancer_name'), '/myInboundNATRule')]",
"dependsOn": [
"[resourceId('Microsoft.Network/loadBalancers', parameters('loadBalancers_myLoadBalancer_name'))]"
],
"properties": {
"provisioningState": "Succeeded",
"frontendIPConfiguration": {
"id": "[concat(resourceId('Microsoft.Network/loadBalancers', parameters('loadBalancers_myLoadBalancer_name')), '/frontendIPConfigurations/myfrontendIPinbound')]"
},
"frontendPort": 4422,
"backendPort": 3389,
"enableFloatingIP": false,
"idleTimeoutInMinutes": 4,
"protocol": "Tcp",
"enableTcpReset": false
}
}
```
Pour plus d’informations sur les règles NAT de trafic entrant, consultez [Qu’est-ce qu’Azure Load Balancer ?](load-balancer-overview.md).
* **Règles de trafic sortant** : vous pouvez ajouter ou supprimer des règles de trafic sortant dans la configuration en modifiant la propriété **outboundRules** dans le fichier template.json :
```json
"outboundRules": [
{
"name": "myOutboundRule",
"etag": "W/\"39e5e9cd-2d6d-491f-83cf-b37a259d86b6\"",
"properties": {
"provisioningState": "Succeeded",
"allocatedOutboundPorts": 10000,
"protocol": "All",
"enableTcpReset": false,
"idleTimeoutInMinutes": 15,
"backendAddressPool": {
"id": "[concat(resourceId('Microsoft.Network/loadBalancers', parameters('loadBalancers_myLoadBalancer_name')), '/backendAddressPools/myBEPoolOutbound')]"
},
"frontendIPConfigurations": [
{
"id": "[concat(resourceId('Microsoft.Network/loadBalancers', parameters('loadBalancers_myLoadBalancer_name')), '/frontendIPConfigurations/myfrontendIPoutbound')]"
}
]
}
}
]
```
Pour plus d’informations, consultez [Règles de trafic sortant dans Load Balancer](./load-balancer-outbound-connections.md#outboundrules).
12. Sélectionnez **Enregistrer** dans l’éditeur en ligne.
13. Sélectionnez **OPTIONS DE BASE** > **Abonnement** pour choisir l’abonnement dans lequel l’équilibreur de charge externe cible sera déployé.
15. Sélectionnez **OPTIONS DE BASE** > **Groupe de ressources** pour choisir le groupe de ressources dans lequel l’équilibreur de charge cible sera déployé. Vous pouvez sélectionner **Créer** afin de créer un groupe de ressources pour l’équilibreur de charge externe cible. Vous pouvez également choisir le groupe de ressources existant que vous avez créé précédemment pour l’adresse IP publique. Vérifiez que le nom n’est pas identique à celui du groupe de ressources source de l’équilibreur de charge externe source existant.
16. Vérifiez que **OPTIONS DE BASE** > **Emplacement** est défini sur l’emplacement cible où vous souhaitez déployer l’équilibreur de charge externe.
17. Sous **PARAMÈTRES**, vérifiez que le nom correspond à celui que vous avez entré précédemment dans l’éditeur de paramètres. Vérifiez que les ID de ressources sont renseignés pour toutes les adresses IP publiques de la configuration.
18. Cochez la case **CONDITIONS GÉNÉRALES**.
19. Sélectionnez **Acheter** pour déployer l’adresse IP publique cible.
## <a name="discard"></a>Abandonner
Si vous souhaitez ignorer l’adresse IP publique cible et l’équilibreur de charge externe, supprimez le groupe de ressources qui les contient. Pour ce faire, sélectionnez le groupe de ressources à partir de votre tableau de bord dans le portail, puis sélectionnez **Supprimer** en haut de la page de vue d’ensemble.
## <a name="clean-up"></a>Nettoyage
Pour valider les modifications et terminer le déplacement de l’adresse IP publique et de l’équilibreur de charge externe, supprimez l’adresse IP publique source et le groupe de ressources ou l’équilibreur de charge externe source. Pour ce faire, sélectionnez le groupe de ressources à partir de votre tableau de bord dans le portail, puis sélectionnez **Supprimer** en haut de chaque page.
## <a name="next-steps"></a>Étapes suivantes
Dans ce tutoriel, vous avez déplacé un équilibreur de charge externe Azure d’une région à une autre et vous avez nettoyé les ressources sources. Pour plus d’informations sur le déplacement de ressources entre régions et la reprise d’activité dans Azure, consultez :
- [Déplacer des ressources vers un nouveau groupe de ressource ou un nouvel abonnement](../azure-resource-manager/management/move-resource-group-and-subscription.md)
- [Déplacer des machines virtuelles Azure vers une autre région](../site-recovery/azure-to-azure-tutorial-migrate.md) | 60.966507 | 799 | 0.647504 | fra_Latn | 0.95623 |
d3c4da107980fb2cdd9f92b2b14de7b121e32205 | 1,369 | md | Markdown | docs/Model/UpdateFulfillmentOrderItem.md | sellerlegend/amazon-sp-api-php | d6eb4325847b6ceb27a6382a99e08b47dd24d17c | [
"MIT"
] | null | null | null | docs/Model/UpdateFulfillmentOrderItem.md | sellerlegend/amazon-sp-api-php | d6eb4325847b6ceb27a6382a99e08b47dd24d17c | [
"MIT"
] | null | null | null | docs/Model/UpdateFulfillmentOrderItem.md | sellerlegend/amazon-sp-api-php | d6eb4325847b6ceb27a6382a99e08b47dd24d17c | [
"MIT"
] | null | null | null | # UpdateFulfillmentOrderItem
## Properties
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**seller_sku** | **string** | The seller SKU of the item. | [optional]
**seller_fulfillment_order_item_id** | **
string** | Identifies the fulfillment order item to update. Created with a previous call to the createFulfillmentOrder operation. |
**quantity** | [**\Swagger\Client\Models\Quantity**](Quantity.md) | |
**gift_message** | **string** | A message to the gift recipient, if applicable. | [optional]
**displayable_comment** | **
string** | Item-specific text that displays in recipient-facing materials such as the outbound shipment packing slip. | [optional]
**fulfillment_network_sku** | **string** | Amazon's fulfillment network SKU of the item. | [optional]
**order_item_disposition** | **string** | Indicates whether the item is sellable or unsellable. | [optional]
**per_unit_declared_value** | [**\Swagger\Client\Models\Currency**](Currency.md) | | [optional]
**per_unit_price** | [**\Swagger\Client\Models\Currency**](Currency.md) | | [optional]
**per_unit_tax** | [**\Swagger\Client\Models\Currency**](Currency.md) | | [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)
| 62.227273 | 170 | 0.680789 | eng_Latn | 0.512447 |
d3c52b27cbb7f2008110e9fcd619b5642b2ff7e5 | 12,119 | md | Markdown | docs/content/guides/security/auth/extauth/oauth/access_token/_index.md | tmojlupo/gloo | eb6664f60d410f32ec42c8a8033048b144f9566d | [
"Apache-2.0"
] | 3,506 | 2018-03-05T07:07:59.000Z | 2022-03-31T08:38:09.000Z | docs/content/guides/security/auth/extauth/oauth/access_token/_index.md | tmojlupo/gloo | eb6664f60d410f32ec42c8a8033048b144f9566d | [
"Apache-2.0"
] | 5,539 | 2018-03-05T19:33:01.000Z | 2022-03-31T23:02:26.000Z | docs/content/guides/security/auth/extauth/oauth/access_token/_index.md | tmojlupo/gloo | eb6664f60d410f32ec42c8a8033048b144f9566d | [
"Apache-2.0"
] | 387 | 2018-03-05T19:25:01.000Z | 2022-03-25T21:19:49.000Z | ---
title: Authenticate with an Access Token
weight: 30
description: Integrating Gloo Edge and Access Tokens
---
{{% notice note %}}
{{< readfile file="static/content/enterprise_only_feature_disclaimer" markdown="true">}}
{{% /notice %}}
You may already have an OIDC compliant authentication system in place at your organization which can issue and validate access tokens. In that case, Gloo Edge can rely on your existing system by accepting requests with an access token and validating that token against an introspection endpoint.
In this guide we will deploy ORY Hydra, a simple OpenID Connect Provider. Hydra will serve as our existing OIDC compliant authentication system. We will generate a valid access token from the Hydra deployment and have Gloo Edge validate that token using Hyrda's introspection endpoint.
## Setup
{{< readfile file="/static/content/setup_notes" markdown="true">}}
### Deploy sample application
{{% notice warning %}}
The sample `petclinic` application deploys a MySql server. If you are using `minikube` v1.5 to run this guide, this service is likely to crash due a `minikube` [issue](https://github.com/kubernetes/minikube/issues/5751). To get around this, you can start `minikube` with the following flag:
```shell
minikube start --docker-opt="default-ulimit=nofile=102400:102400"
```
{{% /notice %}}
Let's deploy a sample web application that we will use to demonstrate these features:
```shell
kubectl apply -f https://raw.githubusercontent.com/solo-io/gloo/v0.8.4/example/petclinic/petclinic.yaml
```
### Creating a Virtual Service
Now we can create a Virtual Service that routes all requests (note the `/` prefix) to the `petclinic` service.
```yaml
apiVersion: gateway.solo.io/v1
kind: VirtualService
metadata:
name: petclinic
namespace: gloo-system
spec:
virtualHost:
domains:
- '*'
routes:
- matchers:
- prefix: /
routeAction:
single:
kube:
ref:
name: petclinic
namespace: default
port: 80
```
To verify that the Virtual Service has been accepted by Gloo Edge, let's port-forward the Gateway Proxy service so that it is
reachable from your machine at `localhost:8080`:
```
kubectl -n gloo-system port-forward svc/gateway-proxy 8080:80
```
If you open your browser and navigate to [http://localhost:8080](http://localhost:8080) you should see the following page (you might need to wait a minute for the containers to start):
![Pet Clinic app homepage]({{% versioned_link_path fromRoot="/img/petclinic-home.png" %}})
## Securing the Virtual Service
As we just saw, we were able to reach our application without having to provide any credentials. This is because by default Gloo Edge allows any request on routes that do not specify authentication configuration. Let's change this behavior.
We will update the Virtual Service so that each request to the sample application is authenticated using an **OpenID Connect** flow.
### Install Hydra
To implement the authentication flow, we need an OpenID Connect provider available to Gloo Edge. For demonstration purposes, will deploy the [Hydra](https://www.ory.sh/hydra/docs/) provider in the same cluster, as it easy to install and configure.
Let's start by adding the Ory helm repository.
```bash
helm repo add ory https://k8s.ory.sh/helm/charts
helm repo update
```
Now we are going to deploy Hydra using the helm chart:
```bash
helm install \
--set 'hydra.config.secrets.system=$(LC_ALL=C tr -dc 'A-Za-z0-9' < /dev/urandom | base64 | head -c 32)' \
--set 'hydra.config.dsn=memory' \
--set 'hydra.config.urls.self.issuer=http://public.hydra.localhost/' \
--set 'hydra.config.urls.login=http://example-idp.localhost/login' \
--set 'hydra.config.urls.consent=http://example-idp.localhost/consent' \
--set 'hydra.config.urls.logout=http://example-idp.localhost/logout' \
--set 'ingress.public.enabled=true' \
--set 'ingress.admin.enabled=true' \
--set 'hydra.dangerousForceHttp=true' \
hydra-example \
ory/hydra --version 0.4.5
```
In the above command, we are using an in-memory database of Hydra and setting `hydra.dangerousForceHttp` to `true`, disabling SSL. This is for demonstration purposes and should not be used outside of a development context.
We should now see the two Hydra pods running in the default namespace:
```bash
NAME READY STATUS RESTARTS AGE
hydra-example-58cd5bf699-9jgz5 1/1 Running 0 10m
hydra-example-maester-75c985dd5b-s4b27 1/1 Running 0 10m
petclinic-0 1/1 Running 1 25h
petclinic-db-0 1/1 Running 0 25h
```
The administrative endpoint is running on port 4445 and the public endpoint is running on port 4444. We will be using the former to create a client id and password and validate the token, and then the latter to generate an access token.
#### Create the Client and Access Token
Now that we have Hydra up and running, we need to create a client id and client secret by interfacing with the administrative endpoint on Hydra. First we will make the administrative endpoint accessible by forwarding port 4445 of the Hydra pod to our localhost.
```bash
kubectl port-forward deploy/hydra-example 4445 &
portForwardPid1=$! # Store the port-forward pid so we can kill the process later
```
```bash
[1] 1417
~ >Forwarding from 127.0.0.1:4445 -> 4445
```
Now we can use `curl` to interact with the administration endpoint and create a client id and client secret.
```bash
curl -X POST http://127.0.0.1:4445/clients \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
-d '{"client_id": "my-client", "client_secret": "secret", "grant_types": ["client_credentials"]}'
```
You should see output similar to this:
```json
{"client_id":"my-client","client_name":"","client_secret":"secret","redirect_uris":null,"grant_types":["client_credentials"],"response_types":null,"scope":"offline_access offline openid","audience":null,"owner":"","policy_uri":"","allowed_cors_origins":null,"tos_uri":"","client_uri":"","logo_uri":"","contacts":null,"client_secret_expires_at":0,"subject_type":"public","token_endpoint_auth_method":"client_secret_basic","userinfo_signed_response_alg":"none","created_at":"2020-10-01T19:46:51Z","updated_at":"2020-10-01T19:46:51Z"}
```
Now we will using the public endpoint to generate our access token. First we will port-forward the hydra pod on port 4444.
```bash
kubectl port-forward deploy/hydra-example 4444 &
portForwardPid2=$! # Store the port-forward pid so we can kill the process later
```
```bash
[2] 1431
~ >Forwarding from 127.0.0.1:4444 -> 4444
```
Let's use curl again to create our access token using the client id and secret we just registered on the administrative endpoint.
```bash
curl -X POST http://127.0.0.1:4444/oauth2/token \
-H 'Content-Type: application/x-www-form-urlencoded' \
-H 'Accept: application/json' \
-u my-client:secret \
-d 'grant_type=client_credentials' | jq .access_token -r
```
The command should render the access token as output which we can set as a variable:
```bash
#OUTPUT
vn83zER2AjyOPbzoVXS3A3S65OCC2LvdGcsz3i5CxlY.NWWWsEixtTLSxN7E0Yk5NsWEZvVZEIjlOCtre0T-s4Q
#SET VARIABLE
ACCESS_TOKEN=vn83zER2AjyOPbzoVXS3A3S65OCC2LvdGcsz3i5CxlY.NWWWsEixtTLSxN7E0Yk5NsWEZvVZEIjlOCtre0T-s4Q
```
We can validate the token using the introspection path of the administrative endpoint:
```bash
curl -X POST http://127.0.0.1:4445/oauth2/introspect \
-H 'Content-Type: application/x-www-form-urlencoded' \
-H 'Accept: application/json' \
-d "token=$ACCESS_TOKEN" | jq
```
This is the same path that Gloo Edge will use to check on the validity of tokens. The next step is to take the introspection URL and add it to an *AuthConfig* and then associate that AuthConfig with the Virtual Service we created earlier.
#### Create an AuthConfig
{{% notice warning %}}
{{% extauth_version_info_note %}}
{{% /notice %}}
Now that all the necessary resources are in place we can create the `AuthConfig` resource that we will use to secure our Virtual Service.
{{< highlight shell "hl_lines=8-10" >}}
apiVersion: enterprise.gloo.solo.io/v1
kind: AuthConfig
metadata:
name: oidc-hydra
namespace: gloo-system
spec:
configs:
- oauth2:
accessTokenValidation:
introspectionUrl: http://hydra-example-admin.default:4445/oauth2/introspect
{{< /highlight >}}
The above configuration instructs Gloo Edge to use the `introspectionUrl` to validate access tokens that are submitted with the request. If the token is missing or invalid, Gloo Edge will deny the request. We can use the internal hostname of the Hydra administrative service, since the request will come from Gloo Edge's exauth pod which has access to Kubernetes DNS.
#### Update the Virtual Service
Once the AuthConfig has been created, we can use it to secure our Virtual Service:
{{< highlight yaml "hl_lines=20-24" >}}
apiVersion: gateway.solo.io/v1
kind: VirtualService
metadata:
name: petclinic
namespace: gloo-system
spec:
virtualHost:
domains:
- '*'
routes:
- matchers:
- prefix: /
routeAction:
single:
kube:
ref:
name: petclinic
namespace: default
port: 80
options:
extauth:
configRef:
name: oidc-hydra
namespace: gloo-system
{{< /highlight >}}
### Testing our configuration
The authentication flow to get the access token happens outside of Gloo Edge's purview. To access the petclinic site, we will simply include the access token in our request. Gloo Edge will validate that the token is active using the URL we specified in the AuthConfig.
1. Port-forward the Gloo Edge Proxy service so that it is reachable from your machine at `localhost:8080`:
```
kubectl -n gloo-system port-forward svc/gateway-proxy 8080:80 &
portForwardPid3=$! # Store the port-forward pid so we can kill the process later
```
Now we are ready to test our complete setup! We are going to use `curl` instead of the browser to access the petclinic page, since we need to include the access token in the request.
First let's try and access the site without a token value set:
```bash
curl http://localhost:8080 -v
```
We will receive a 403 (Forbidden) message letting us know that our access was not authorized. Now let's try an invalid access token value:
```bash
curl http://localhost:8080 \
-H "Authorization: Bearer qwertyuio23456789" -v
```
Again we will receive a 403 message. Finally, let's try using the access token we generated earlier. Be sure to paste in your proper access token value:
```bash
curl http://localhost:8080 \
-H "Authorization: Bearer $ACCESS_TOKEN" -v
```
You will receive a 200 HTTP response and the body of the petclinic homepage.
### Logging
If Gloo Edge is running on kubernetes, the extauth server logs can be viewed with:
```
kubectl logs -n gloo-system deploy/extauth -f
```
If the auth config has been received successfully, you should see the log line:
```
"logger":"extauth","caller":"runner/run.go:179","msg":"got new config"
```
### Cleanup
You can clean up the resources created in this guide by running:
```
kill $portForwardPid1
kill $portForwardPid2
kill $portForwardPid3
helm delete --purge hydra-example
kubectl delete virtualservice -n gloo-system petclinic
kubectl delete authconfig -n gloo-system oidc-hydra
kubectl delete -f https://raw.githubusercontent.com/solo-io/gloo/v0.8.4/example/petclinic/petclinic.yaml
```
## Summary and Next Steps
In this guide you saw how Gloo Edge could be used with an existing OIDC system to validate access tokens and grant access to a VirtualService. You may want to also check out the authentication guides that use [Dex]({{< versioned_link_path fromRoot="/guides/security/auth/extauth/oauth/dex/" >}}) and [Google]({{< versioned_link_path fromRoot="/guides/security/auth/extauth/oauth/dex/" >}}) for more alternatives when it comes to OAuth-based authentication. | 40.667785 | 531 | 0.730588 | eng_Latn | 0.966993 |
d3c645ef7bb1920f6945392ce7876df955febb59 | 12,165 | md | Markdown | articles/storage/blobs/data-lake-storage-performance-tuning-storm.md | peder-andfrankly/azure-docs.sv-se | 49435a06686fc72ca9cd8c83883c3c3704a6ec72 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/storage/blobs/data-lake-storage-performance-tuning-storm.md | peder-andfrankly/azure-docs.sv-se | 49435a06686fc72ca9cd8c83883c3c3704a6ec72 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/storage/blobs/data-lake-storage-performance-tuning-storm.md | peder-andfrankly/azure-docs.sv-se | 49435a06686fc72ca9cd8c83883c3c3704a6ec72 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'Justera prestanda: storm, HDInsight & Azure Data Lake Storage Gen2 | Microsoft Docs'
description: Rikt linjer för prestanda justering Azure Data Lake Storage Gen2 Storm
author: normesta
ms.subservice: data-lake-storage-gen2
ms.service: storage
ms.topic: conceptual
ms.date: 11/18/2019
ms.author: normesta
ms.reviewer: stewu
ms.openlocfilehash: 125c583512f6bae34c2dd3c3dd76a1b96a181ac1
ms.sourcegitcommit: b77e97709663c0c9f84d95c1f0578fcfcb3b2a6c
ms.translationtype: MT
ms.contentlocale: sv-SE
ms.lasthandoff: 11/22/2019
ms.locfileid: "74327906"
---
# <a name="tune-performance-storm-hdinsight--azure-data-lake-storage-gen2"></a>Justera prestanda: storm, HDInsight & Azure Data Lake Storage Gen2
Förstå faktorerna som bör övervägas när du justerar prestandan för en Azure Storm-topologi. Det är till exempel viktigt att förstå egenskaperna hos det arbete som utförs av kanaler och bultarna (oavsett om arbetet är I/O eller minnes krävande). Den här artikeln beskriver ett antal rikt linjer för prestanda justering, inklusive fel sökning av vanliga problem.
## <a name="prerequisites"></a>Krav
* **En Azure-prenumeration**. Se [Hämta en kostnadsfri utvärderingsversion av Azure](https://azure.microsoft.com/pricing/free-trial/).
* **Ett Azure Data Lake Storage Gen2 konto**. Anvisningar om hur du skapar ett finns i [snabb start: skapa ett lagrings konto för analys](data-lake-storage-quickstart-create-account.md).
* **Azure HDInsight-kluster** med åtkomst till ett data Lake Storage Gen2-konto. Se [Använda Azure Data Lake Storage Gen2 med Azure HDInsight-kluster](https://docs.microsoft.com/azure/hdinsight/hdinsight-hadoop-use-data-lake-storage-gen2). Se till att aktivera fjärr skrivbord för klustret.
* **Köra ett Storm-kluster på data Lake Storage Gen2**. Mer information finns i [storm på HDInsight](https://docs.microsoft.com/azure/hdinsight/hdinsight-storm-overview).
* **Rikt linjer för prestanda justering på data Lake Storage Gen2**. Allmänna prestanda koncept finns i [rikt linjer för data Lake Storage Gen2 prestanda justering](data-lake-storage-performance-tuning-guidance.md).
## <a name="tune-the-parallelism-of-the-topology"></a>Justera topologins parallellitet
Du kanske kan förbättra prestandan genom att öka samtidigheten för I/O till och från Data Lake Storage Gen2. En Storm-topologi har en uppsättning konfigurationer som fastställer parallellitet:
* Antal arbets processer (arbets tagarna är jämnt fördelade på de virtuella datorerna).
* Antal kanalen utförar-instanser.
* Antal bult utförar-instanser.
* Antal kanalen-uppgifter.
* Antal bult-aktiviteter.
Till exempel, i ett kluster med 4 virtuella datorer och 4 arbets processer, 32 kanalen-körningar och 32 kanalen-uppgifter, samt 256 bult-körningar och 512 bult-uppgifter, bör du tänka på följande:
Varje ansvarig, som är en arbetsnod, har en enda Worker Java Virtual Machine (JVM)-process. Den här JVM-processen hanterar 4 kanalen-trådar och 64 bult-trådar. I varje tråd körs aktiviteter sekventiellt. Med föregående konfiguration har varje kanalen-tråd 1 uppgift och varje bult-tråd har två uppgifter.
I storm är här de olika komponenterna som berörs och hur de påverkar graden av parallellitet som du har:
* Head-noden (kallas Nimbus i Storm) används för att skicka och hantera jobb. Dessa noder påverkar inte graden av parallellitet.
* De överordnade noderna. I HDInsight motsvarar detta en arbetsnods Azure VM.
* Arbets uppgifterna är Storm-processer som körs i de virtuella datorerna. Varje arbets uppgift motsvarar en JVM-instans. Storm distribuerar det antal arbets processer som du anger till arbetsnoderna så jämnt som möjligt.
* Kanalen-och bult utförar-instanser. Varje utförar-instans motsvarar en tråd som körs i arbets tagarna (JVMs).
* Storm-aktiviteter. Detta är logiska uppgifter som var och en av dessa trådar körs. Detta påverkar inte graden av parallellitet, så du bör utvärdera om du behöver flera aktiviteter per utförar eller inte.
### <a name="get-the-best-performance-from-data-lake-storage-gen2"></a>Få bästa möjliga prestanda från Data Lake Storage Gen2
När du arbetar med Data Lake Storage Gen2 får du bästa möjliga prestanda om du gör följande:
* Slå samman dina små tillägg i större storlekar.
* Gör så många samtidiga förfrågningar som du kan. Eftersom varje bult-tråd blockerar läsningar, vill du ha någonstans i intervallet 8-12 trådar per kärna. Detta skyddar NÄTVERKSKORTet och den processor som används mycket. En större virtuell dator möjliggör fler samtidiga begär Anden.
### <a name="example-topology"></a>Exempel sto pol Ogin
Vi antar att du har ett 8 Work Node-kluster med en D13v2 Azure VM. Den här virtuella datorn har 8 kärnor, så mellan de 8 arbetsnoderna har du 64 total kärnor.
Låt oss säga att vi har åtta bult-trådar per kärna. Med 64 kärnor innebär det att vi vill ha 512 totalt utförar-instanser för bult (det vill säga trådar). I det här fallet antar vi att vi börjar med en JVM per virtuell dator och använder i huvudsak tråd samtidigheten i JVM för att uppnå samtidighet. Det innebär att vi behöver 8 arbets uppgifter (en per virtuell Azure-dator) och 512 bult-körningar. Med hänsyn till den här konfigurationen försöker Storm att distribuera arbets tagarna jämnt över arbetsnoderna (även kallade tillsynsmyndigheter), vilket ger varje arbetsnod 1-JVM. Storm försöker nu att distribuera körningarna jämnt mellan supervisor, vilket ger varje ansvarig (det vill säga JVM) 8 trådar var som helst.
## <a name="tune-additional-parameters"></a>Justera ytterligare parametrar
När du har en grundläggande topologi kan du fundera över om du vill ändra någon av parametrarna:
* **Antal JVMs per arbets nod.** Om du har en stor data struktur (till exempel en uppslags tabell) som du är värd för i minnet, kräver varje JVM en separat kopia. Du kan också använda data strukturen för många trådar om du har färre JVMs. För bultens I/O gör antalet JVMs inte lika mycket av skillnaden som antalet trådar som har lagts till i JVMs. För enkelhetens skull är det en bra idé att ha en JVM per arbets tagare. Du kan behöva ändra det här värdet, beroende på vad din bult gör eller vilken program bearbetning du behöver.
* **Antal kanalen-körningar.** Eftersom föregående exempel använder bultar för att skriva till Data Lake Storage Gen2, är antalet kanaler inte direkt relevant för bultens prestanda. Beroende på mängden bearbetning eller I/O-åtgärder i kanalen är det dock en bra idé att justera kanaler för bästa prestanda. Se till att du har tillräckligt många kanaler för att kunna hålla bultarna upptagna. De utgående frekvenserna för kanaler bör matcha bultens data flöde. Den faktiska konfigurationen beror på kanalen.
* **Antal aktiviteter.** Varje bult körs som en enda tråd. Ytterligare aktiviteter per bult ger ingen ytterligare samtidighet. Den enda tiden de är av förmånen är om din process att bekräfta att tuppeln tar en stor del av din bult-körnings tid. Det är en bra idé att gruppera många tupler i ett större tillägg innan du skickar ett bekräftelse från bulten. I de flesta fall ger flera aktiviteter ingen ytterligare förmån.
* **Lokal eller blandad gruppering.** När den här inställningen är aktive rad skickas tupler till bultar inom samma arbets process. Detta minskar kommunikation mellan processer och nätverks anrop. Detta rekommenderas för de flesta topologier.
Det här grundläggande scenariot är en lämplig start punkt. Testa med dina egna data för att justera föregående parametrar för att uppnå optimala prestanda.
## <a name="tune-the-spout"></a>Finjustera kanalen
Du kan ändra följande inställningar för att finjustera kanalen.
- **Tupel-timeout: topologi. Message. timeout. sekunder**. Den här inställningen anger hur lång tid ett meddelande tar att slutföra och får bekräftelse innan det betraktas som misslyckat.
- **Högsta mängd minne per arbets process: Worker. childopts**. Med den här inställningen kan du ange ytterligare kommando rads parametrar för Java-arbetarna. Den vanligaste inställningen här är XmX, som avgör den maximala mängd minne som allokerats till en JVM-heap.
- **Max kanalen väntar: topologi. max. kanalen. väntar**. Den här inställningen avgör antalet tupler som kan vara flyg (ännu inte accepterade på alla noder i topologin) per kanalen-tråd när som helst.
En lämplig beräkning är att beräkna storleken på varje tupel. Räkna sedan upp hur mycket minne en kanalen tråd har. Det totala minne som allokerats till en tråd, dividerat med det här värdet, ska ge dig den övre bindningen för den maximala kanalen-parametern som väntar.
Standard Data Lake Storage Gen2 Storm bult har en princip parameter för fileBufferSize (size) som kan användas för att finjustera den här parametern.
I i/O-intensiva topologier är det en bra idé att låta varje bult-tråd skriva till sin egen fil och att ange en fil rotations princip (fileRotationSize). När filen når en viss storlek, töms strömmen automatiskt och en ny fil skrivs till. Den rekommenderade fil storleken för rotation är 1 GB.
## <a name="monitor-your-topology-in-storm"></a>Övervaka din topologi i storm
När topologin körs kan du övervaka den i storm-användargränssnittet. Följande är de viktigaste parametrarna för att titta på:
* **Total fördröjning för process körning.** Detta är den genomsnittliga tiden som en tupel tar att genereras av kanalen, bearbetas av blixten och bekräftas.
* **Total blixt process svars tid.** Detta är den genomsnittliga tiden som tuppeln tar i bulten tills den får en bekräftelse.
* **Körnings fördröjning för total bult.** Detta är den genomsnittliga tiden som bulten har använt i Execute-metoden.
* **Antal felaktiga försök.** Detta avser antalet tupler som inte kunde bearbetas fullständigt innan tids gränsen uppnåddes.
* **Kapaciteten.** Detta är ett mått på hur upptagen systemet är. Om det här värdet är 1 fungerar bultarna så snabbt som de kan. Om det är mindre än 1 ökar du parallellt. Om det är större än 1 minskar du parallellt.
## <a name="troubleshoot-common-problems"></a>Felsök vanliga problem
Här följer några vanliga fel söknings scenarier.
* **Tids gränsen har nåtts för många tupler.** Ta reda på var Flask halsen är genom att titta på varje nod i topologin. Den vanligaste orsaken till detta är att bultarna inte kan hålla sig med kanaler. Detta leder till tupler clogging de interna buffertarna medan de väntar på att bearbetas. Överväg att öka timeout-värdet eller minska det högsta antalet kanalen som väntar.
* **Det finns en hög total process körnings fördröjning, men en svars tid för låg bult.** I det här fallet är det möjligt att tuplerna inte bekräftas tillräckligt snabbt. Kontrol lera att det finns tillräckligt många bekräftelser. En annan möjlighet är att de väntar i kön för länge innan bultarna börjar bearbeta dem. Minska Max kanalen.
* **Det finns en hög bult-körnings fördröjning.** Det innebär att metoden Execute () för din bult tar för lång tid. Optimera koden eller titta på Skriv storlek och tömnings beteende.
### <a name="data-lake-storage-gen2-throttling"></a>Data Lake Storage Gen2 begränsning
Om du når gränserna för bandbredden som tillhandahålls av Data Lake Storage Gen2 kan du se aktivitets felen. Kontrol lera aktivitets loggarna för att begränsa fel. Du kan minska parallellheten genom att öka behållarens storlek.
Om du vill kontrol lera om du får en begränsning aktiverar du fel söknings loggning på klient sidan:
1. I **Ambari** > **Storm** > **config** > **Advanced Storm-Work-log4j**, ändra **<root level = "info">** till **<rot nivå = "Felsök">** . Starta om alla noder/tjänster för att konfigurationen ska börja gälla.
2. Övervaka loggfilerna för Storm-topologin på arbetsnoder (under/var/log/Storm/Worker-Artifacts/<TopologyName>/<port>/Worker.log) för Data Lake Storage Gen2 begränsnings undantag.
## <a name="next-steps"></a>Nästa steg
Ytterligare prestanda justering för Storm kan refereras till i [den här bloggen](https://blogs.msdn.microsoft.com/shanyu/2015/05/14/performance-tuning-for-hdinsight-storm-and-microsoft-azure-eventhubs/).
Ytterligare ett exempel på hur du kör finns i [den här GitHub](https://github.com/hdinsight/storm-performance-automation).
| 101.375 | 722 | 0.79515 | swe_Latn | 0.999937 |
d3c6b9d39e0f5ad1e97e33321e8ef2e2fc1a46f7 | 924 | md | Markdown | lib/lono/cli/help/configsets.md | tongueroo/lono | d4ab9b16a3ff429d2aeb1abece4cb36657928df7 | [
"Apache-2.0"
] | 104 | 2015-03-21T16:06:47.000Z | 2020-06-16T14:39:17.000Z | lib/lono/cli/help/configsets.md | tongueroo/lono | d4ab9b16a3ff429d2aeb1abece4cb36657928df7 | [
"Apache-2.0"
] | 14 | 2015-10-12T23:12:49.000Z | 2019-07-19T18:36:23.000Z | lib/lono/cli/help/configsets.md | tongueroo/lono | d4ab9b16a3ff429d2aeb1abece4cb36657928df7 | [
"Apache-2.0"
] | 18 | 2015-02-05T19:25:23.000Z | 2020-04-01T19:03:47.000Z | ## Examples
When the `lono configsets` command is passed the blueprint will list the configsets for the blueprint.
$ lono configsets ec2
Configsets used by ec2 blueprint:
+-------+----------------------+---------+---------+
| Name | Path | Type | From |
+-------+----------------------+---------+---------+
| httpd | app/configsets/httpd | project | project |
+-------+----------------------+---------+---------+
$
When there are no arguments passed to the `lono configsets` command it will list the project configsets.
$ lono configsets
Project configsets:
+-------+------------------------+---------+
| Name | Path | Type |
+-------+------------------------+---------+
| httpd | app/configsets/httpd | project |
| ruby | vendor/configsets/ruby | vendor |
+-------+------------------------+---------+
$ | 38.5 | 104 | 0.409091 | eng_Latn | 0.543259 |
d3c6d1e015b4c5375ff20dbf886f529fc272dd14 | 1,534 | md | Markdown | doc/kaggle_y_googleColab.md | alcazar90/CC5205-3-proyecto | 61985f9877a54a15de8648cf3ccb57201dc55d7d | [
"CECILL-B"
] | 2 | 2022-03-16T01:49:29.000Z | 2022-03-17T20:03:42.000Z | doc/kaggle_y_googleColab.md | alcazar90/CC5205-3-proyecto | 61985f9877a54a15de8648cf3ccb57201dc55d7d | [
"CECILL-B"
] | 8 | 2022-03-14T17:57:57.000Z | 2022-03-29T22:20:51.000Z | doc/kaggle_y_googleColab.md | alcazar90/CC5205-3-proyecto | 61985f9877a54a15de8648cf3ccb57201dc55d7d | [
"CECILL-B"
] | null | null | null | # ¿Cómo cargar datos de Kaggle directamente a Google Colab?
<a href="https://colab.research.google.com/drive/1zvyMKfu_SdXnPcF7fXhyeRauK_X4_4qI?usp=sharing" target="_blank">
<img src="https://colab.research.google.com/assets/colab-badge.svg" alt="Open In Colab"/>
</a>
**Requisitos previo a ejecutar el notebook:**
1. Se debe tener una cuenta en Kaggle
1. Ir al menu en esquina superior derecha en _account_
1. En la subsección API, dar _click_ en _Create New API Token_
1. Se descargará en sus computadores el archivo `kaggle.json`, el cual contiene sus credenciales
**Instrucciones a realizar una vez que se haya descargado el archivo con las credenciales:**
1. Crear en el directorio home del disco virtual una carpeta con el nombre: `.kaggle`, se puede utilizar el siguiente comando: `!mkdir ~/.kaggle` _(*)_
2. Usar la libreria `google.colab` para cargar archivos de nuestro computador al disco remoto en colab, subiremos el archivo `kaggle.json` que contiene nuestras credenciales:
```python
from google.colab import files
files.upload()
```
3. Mover el archivo `kaggle.json` recién subido a la carpeta creada al principio: `!mv kaggle.json ~/.kaggle/`
4. Debemos cambiar los permisos del archivo `kaggle.json` para que la API pueda acceder a las credenciales: `!chmod 600 ~/.kaggle/kaggle.json`
5. Ahora podemos usar los comandos para acceder a kaggle directamente desde Colab, ver el notebook para continuar con el ejemplo
_(*): Se puede ejecutar comandos de terminal en google colab usando el caracter `!` al inicio_
| 56.814815 | 174 | 0.770535 | spa_Latn | 0.98471 |
d3c70a9effdf271a507a83741ec74917ef715502 | 617 | md | Markdown | 2013/CVE-2013-6058.md | justinforbes/cve | 375c65312f55c34fc1a4858381315fe9431b0f16 | [
"MIT"
] | 2,340 | 2022-02-10T21:04:40.000Z | 2022-03-31T14:42:58.000Z | 2013/CVE-2013-6058.md | justinforbes/cve | 375c65312f55c34fc1a4858381315fe9431b0f16 | [
"MIT"
] | 19 | 2022-02-11T16:06:53.000Z | 2022-03-11T10:44:27.000Z | 2013/CVE-2013-6058.md | justinforbes/cve | 375c65312f55c34fc1a4858381315fe9431b0f16 | [
"MIT"
] | 280 | 2022-02-10T19:58:58.000Z | 2022-03-26T11:13:05.000Z | ### [CVE-2013-6058](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-6058)
### Description
SQL injection vulnerability in appRain CMF 3.0.2 and earlier allows remote attackers to execute arbitrary SQL commands via the PATH_INFO to blog-by-cat/.
### POC
#### Reference
- http://packetstormsecurity.com/files/123929
#### Github
No PoCs found on GitHub currently.
| 34.277778 | 153 | 0.747164 | eng_Latn | 0.276123 |
d3c759538a00bc7372ac8fa1b3686f06f05c55f4 | 785 | md | Markdown | posts/2011/2011-03-01-sortie-de-chive-0-4-1.md | kianby/blog | 225a4ff35b8c6bff19f5233a8047ac1566678692 | [
"MIT"
] | null | null | null | posts/2011/2011-03-01-sortie-de-chive-0-4-1.md | kianby/blog | 225a4ff35b8c6bff19f5233a8047ac1566678692 | [
"MIT"
] | 1 | 2022-02-19T11:38:50.000Z | 2022-02-19T11:38:50.000Z | posts/2011/2011-03-01-sortie-de-chive-0-4-1.md | kianby/blog | 225a4ff35b8c6bff19f5233a8047ac1566678692 | [
"MIT"
] | 1 | 2020-02-08T17:45:12.000Z | 2020-02-08T17:45:12.000Z | <!-- title: Sortie de Chive 0.4.1 -->
<!-- category: Archlinux -->
Une version mineure de [Chive](http://www.chive-project.com/), l'outil
d'administration mySQL, est sortie la semaine dernière<!-- more --> ; elle corrige un
certains nombre de bugs. Voici le change log officiel.
Chive 0.4.1 is out, a minor bug-fix release for the 0.4 series.
Bug-Fixes in this release:
- FileImport broken
- Explain not working with groupby
- no server infos without selecting a schema first
- class HttpRequest conflict with pecl http module
- get error after login of version 0.4.0
- it is better to use class CJSON instead of json_encode/json_decode
J'ai mis à jour le [paquet AUR](http://aur.archlinux.org/packages.php?ID=45734)
correspondant pour Archlinux :-)
| 41.315789 | 85 | 0.715924 | eng_Latn | 0.47624 |
d3c7aa8c3fecd7629201c0c6ab2a9b5a52cda0f8 | 214 | md | Markdown | content/sermon/the-da-vinci-code-the-new-testament-and-the-gospels-of-thomas-and-judas.md | lwec/lwechurch.com | d2d4d1c82ff31c68c4f9519bf2e0c75f1c930711 | [
"MIT"
] | null | null | null | content/sermon/the-da-vinci-code-the-new-testament-and-the-gospels-of-thomas-and-judas.md | lwec/lwechurch.com | d2d4d1c82ff31c68c4f9519bf2e0c75f1c930711 | [
"MIT"
] | null | null | null | content/sermon/the-da-vinci-code-the-new-testament-and-the-gospels-of-thomas-and-judas.md | lwec/lwechurch.com | d2d4d1c82ff31c68c4f9519bf2e0c75f1c930711 | [
"MIT"
] | null | null | null | ---
title: "The Da Vinci Code, The New Testament, and the Gospels of Thomas and Judas"
speaker: "Paul Copan"
date: "2010-03-06"
sermonUrl: "//cdn.lwechurch.com/sermons/20100306_saturday_paul_copan_davinci.mp3"
---
| 30.571429 | 82 | 0.752336 | eng_Latn | 0.280588 |
d3c7f16a9f281914b744fff6cf7f3cf6f00e3ec8 | 933 | md | Markdown | README.md | vivekwisdom/MLSessionPre | f491014ccc1cb2faeb11db92034835cae7c60b5a | [
"MIT"
] | null | null | null | README.md | vivekwisdom/MLSessionPre | f491014ccc1cb2faeb11db92034835cae7c60b5a | [
"MIT"
] | null | null | null | README.md | vivekwisdom/MLSessionPre | f491014ccc1cb2faeb11db92034835cae7c60b5a | [
"MIT"
] | null | null | null | # ML Datasets and Notebooks
This repository will be hosting my notebooks for popular datsets practice.
One dataset can have multiple notebooks so hierarchy will based on dataset name.
## Tech Stack
- Python 3.6
- Python libraries like `numpy, pandas, matplotlib`
- ML library `scikit-learn`
- And other supporting libraries mentioned in requirements.txt like `jupyter`
## System Setup
### Setup a Virtual env
Install Virtual Environment
- `pip install virtualenv`
Create Virtual Environment
- `virtualenv <directory-name> -p python3.6`
Activate Virtual Environment
- `source <directory-name ref>/bin/activate`
### Install Dependencies
Install all dependencies using pip and requirements file after activating virtual environment.
`pip install -r requirement.txt`
### Start Project
run `jupyter notebook` from inside your project root.
Follow the Jupyter UI and open the particular notebook from the dataset.
| 25.216216 | 94 | 0.772776 | eng_Latn | 0.960596 |
d3c857826131f2739d35f93b10f3ef663fbf6dd4 | 4,330 | markdown | Markdown | _posts/2020-04-21-new-beginning.markdown | Alfo5123/Alfo5123.github.io | bf89eb3f1109eca8f8051a1050f851046265d630 | [
"MIT"
] | null | null | null | _posts/2020-04-21-new-beginning.markdown | Alfo5123/Alfo5123.github.io | bf89eb3f1109eca8f8051a1050f851046265d630 | [
"MIT"
] | 3 | 2020-04-07T01:15:15.000Z | 2022-02-26T03:52:34.000Z | _posts/2020-04-21-new-beginning.markdown | Alfo5123/Alfo5123.github.io | bf89eb3f1109eca8f8051a1050f851046265d630 | [
"MIT"
] | null | null | null | ---
layout: post
title: New beginning
date: 2020-04-21 11:12:00-0400
description: Steps to return
tags: music
categories: idea
hidden: true
---
<div class="img_row">
<img class="col three" src="{{ site.baseurl }}/assets/img/guitar.jpeg" alt="" title="Guitar"/>
</div>
<div class="col three caption">
Side effects of having an amazing girlfriend. Yes, a Martin Acoustic-Electric Guitar.
</div>
<br />
<br />
{: .text-justify}
#### How to easily start again in music after a long break?
{: .text-justify}
<br />
- Get access to the instrument you loved.
- Embrace depression. You can always practice scales meanwhile.
- Realize [how essential art is in life](https://www.youtube.com/watch?v=aS1esgRV4Rc). Avoid forgetting that life is more than work.
- Find places where you have never felt lost before. Both, inside and outside.
- Keep learning music theory. Books, classical music, friends, everything counts.
- Seize the opportunity of isolation. Any pandemic scenario can help.
- Take the best from those occasional and brief creative moments.
- Listen to music you would not "normally" include in your playlist.
- Share your progress with a close group of people you trust. Bore them with your multiple records until they start disagreeing.
- Let multiple friends recommend you Garage Band. Don't listen to them immediately. Regret it later. Enjoy the learning curve.
- Understand how little you know.
You can find here some of my recent attempts. Excluding Garden of Eden, which is a cover, the rest is original work.
<iframe width="100%" height="100" scrolling="no" frameborder="no" allow="autoplay" src="https://w.soundcloud.com/player/?url=https%3A//api.soundcloud.com/tracks/765569443&color=%23ff5500&auto_play=false&hide_related=false&show_comments=true&show_user=true&show_reposts=false&show_teaser=true&visual=true"></iframe><div style="font-size: 10px; color: #cccccc;line-break: anywhere;word-break: normal;overflow: hidden;white-space: nowrap;text-overflow: ellipsis; font-family: Interstate,Lucida Grande,Lucida Sans Unicode,Lucida Sans,Garuda,Verdana,Tahoma,sans-serif;font-weight: 100;"><a href="https://soundcloud.com/alfredo-de-la-fuente512" title="Alfredo De la Fuente" target="_blank" style="color: #cccccc; text-decoration: none;">Alfredo De la Fuente</a> · <a href="https://soundcloud.com/alfredo-de-la-fuente512/times" title="Times" target="_blank" style="color: #cccccc; text-decoration: none;">Times</a></div>
<iframe width="100%" height="100" scrolling="no" frameborder="no" allow="autoplay" src="https://w.soundcloud.com/player/?url=https%3A//api.soundcloud.com/tracks/783363727&color=%23ff5500&auto_play=false&hide_related=false&show_comments=true&show_user=true&show_reposts=false&show_teaser=true&visual=true"></iframe><div style="font-size: 10px; color: #cccccc;line-break: anywhere;word-break: normal;overflow: hidden;white-space: nowrap;text-overflow: ellipsis; font-family: Interstate,Lucida Grande,Lucida Sans Unicode,Lucida Sans,Garuda,Verdana,Tahoma,sans-serif;font-weight: 100;"><a href="https://soundcloud.com/alfredo-de-la-fuente512" title="Alfredo De la Fuente" target="_blank" style="color: #cccccc; text-decoration: none;">Alfredo De la Fuente</a> · <a href="https://soundcloud.com/alfredo-de-la-fuente512/garden-of-eden" title="Garden Of Eden" target="_blank" style="color: #cccccc; text-decoration: none;">Garden Of Eden</a></div>
<iframe width="100%" height="100" scrolling="no" frameborder="no" allow="autoplay" src="https://w.soundcloud.com/player/?url=https%3A//api.soundcloud.com/tracks/778712911&color=%23ff5500&auto_play=false&hide_related=false&show_comments=true&show_user=true&show_reposts=false&show_teaser=true&visual=true"></iframe><div style="font-size: 10px; color: #cccccc;line-break: anywhere;word-break: normal;overflow: hidden;white-space: nowrap;text-overflow: ellipsis; font-family: Interstate,Lucida Grande,Lucida Sans Unicode,Lucida Sans,Garuda,Verdana,Tahoma,sans-serif;font-weight: 100;"><a href="https://soundcloud.com/alfredo-de-la-fuente512" title="Alfredo De la Fuente" target="_blank" style="color: #cccccc; text-decoration: none;">Alfredo De la Fuente</a> · <a href="https://soundcloud.com/alfredo-de-la-fuente512/komorebi" title="Komorebi" target="_blank" style="color: #cccccc; text-decoration: none;">Komorebi</a></div>
| 74.655172 | 940 | 0.761663 | eng_Latn | 0.563055 |
d3c881417637349d976d9a65c0b019883f0a4f7b | 11,540 | md | Markdown | docs/relational-databases/system-dynamic-management-views/sys-dm-db-file-space-usage-transact-sql.md | luis-cazares-sql/sql-docs.es-es | 6ec4a5eef65cee8f0e495083de92176be1d92819 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/relational-databases/system-dynamic-management-views/sys-dm-db-file-space-usage-transact-sql.md | luis-cazares-sql/sql-docs.es-es | 6ec4a5eef65cee8f0e495083de92176be1d92819 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/relational-databases/system-dynamic-management-views/sys-dm-db-file-space-usage-transact-sql.md | luis-cazares-sql/sql-docs.es-es | 6ec4a5eef65cee8f0e495083de92176be1d92819 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
description: sys.dm_db_file_space_usage (Transact-SQL)
title: sys.dm_db_file_space_usage (Transact-SQL) | Microsoft Docs
ms.custom: ''
ms.date: 03/16/2017
ms.prod: sql
ms.prod_service: database-engine, sql-database, sql-data-warehouse, pdw
ms.reviewer: ''
ms.technology: system-objects
ms.topic: language-reference
f1_keywords:
- dm_db_file_space_usage
- sys.dm_db_file_space_usage_TSQL
- sys.dm_db_file_space_usage
- dm_db_file_space_usage_TSQL
dev_langs:
- TSQL
helpviewer_keywords:
- sys.dm_db_file_space_usage dynamic management view
ms.assetid: 148a5276-a8d5-49d2-8146-3c63d24c2144
author: WilliamDAssafMSFT
ms.author: wiassaf
monikerRange: '>=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current'
ms.openlocfilehash: 93bbb10cd8274b79aca1b40217f15b1ea19f65f4
ms.sourcegitcommit: f29f74e04ba9c4d72b9bcc292490f3c076227f7c
ms.translationtype: MT
ms.contentlocale: es-ES
ms.lasthandoff: 01/13/2021
ms.locfileid: "98172137"
---
# <a name="sysdm_db_file_space_usage-transact-sql"></a>sys.dm_db_file_space_usage (Transact-SQL)
[!INCLUDE [sql-asdb-asdbmi-asa-pdw](../../includes/applies-to-version/sql-asdb-asdbmi-asa-pdw.md)]
Devuelve información de uso de espacio para cada archivo de datos de la base de datos.
> [!NOTE]
> Para llamar a este método desde [!INCLUDE[ssSDWfull](../../includes/sssdwfull-md.md)] o [!INCLUDE[ssPDW](../../includes/sspdw-md.md)] , use el nombre **Sys.dm_pdw_nodes_db_file_space_usage**.
|Nombre de la columna|Tipo de datos|Descripción|
|-----------------|---------------|-----------------|
|database_id|**smallint**|Id. de la base de datos.|
|file_id|**smallint**|Identificador de archivo.<br /><br /> file_id se asigna a file_id de [Sys.dm_io_virtual_file_stats](../../relational-databases/system-dynamic-management-views/sys-dm-io-virtual-file-stats-transact-sql.md) y a fileid en [sys.sysarchivos](../../relational-databases/system-compatibility-views/sys-sysfiles-transact-sql.md).|
|filegroup_id|**smallint**|**Válido para** : [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)] y versiones posteriores.<br /><br /> Identificador de grupo de archivos|
|total_page_count|**bigint**|**Válido para** : [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)] y versiones posteriores.<br /><br /> Número total de páginas en el archivo de datos.|
|allocated_extent_page_count|**bigint**|**Válido para** : [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)] y versiones posteriores.<br /><br /> Número total de páginas en las extensiones asignadas en el archivo de datos.|
|unallocated_extent_page_count|**bigint**|Número total de páginas en las extensiones sin asignar del archivo de datos.<br /><br /> No se incluyen las páginas no utilizadas en extensiones asignadas.|
|version_store_reserved_page_count|**bigint**|Número total de páginas en las extensiones uniformes asignadas para el almacén de versiones. Las páginas de almacén de la versión nunca se asignan desde extensiones mixtas.<br /><br /> No se incluyen las páginas IAM porque siempre se asignan desde extensiones mixtas. Se incluyen las páginas PFS si están asignadas desde una extensión uniforme.<br /><br /> Para obtener más información, consulte [sys.dm_tran_version_store (Transact-SQL)](../../relational-databases/system-dynamic-management-views/sys-dm-tran-version-store-transact-sql.md).|
|user_object_reserved_page_count|**bigint**|Número total de páginas asignadas desde extensiones uniformes para objetos de usuario en la base de datos. En el recuento se incluyen las páginas no utilizadas de una extensión asignada.<br /><br /> No se incluyen las páginas IAM porque siempre se asignan desde extensiones mixtas. Se incluyen las páginas PFS si están asignadas desde una extensión uniforme.<br /><br /> Puede utilizar la total_pages columna de la vista de catálogo [Sys.allocation_units](../../relational-databases/system-catalog-views/sys-allocation-units-transact-sql.md) para devolver el recuento de páginas reservadas de cada unidad de asignación en el objeto de usuario. No obstante, tenga en cuenta que la columna total_pages incluye las páginas IAM.|
|internal_object_reserved_page_count|**bigint**|Número total de páginas en extensiones uniformes asignadas para objetos internos en el archivo. En el recuento se incluyen las páginas no utilizadas de una extensión asignada.<br /><br /> No se incluyen las páginas IAM porque siempre se asignan desde extensiones mixtas. Se incluyen las páginas PFS si están asignadas desde una extensión uniforme.<br /><br /> No existe ninguna vista de catálogo ni objeto de administración dinámica que devuelva el recuento de páginas de cada objeto interno.|
|mixed_extent_page_count|**bigint**|Número total de páginas asignadas y no asignadas en extensiones mixtas asignadas en el archivo. Las extensiones mixtas contienen páginas asignadas a diferentes objetos. Este recuento no incluye todas las páginas IAM del archivo.|
|modified_extent_page_count|**bigint**|**Se aplica a**: [!INCLUDE[ssSQL15](../../includes/sssql16-md.md)] SP2 y versiones posteriores<br /><br />Número total de páginas modificadas en extensiones asignadas del archivo desde la última copia de seguridad completa de la base de datos. El recuento de páginas modificado se puede usar para realizar un seguimiento de la cantidad de cambios diferenciales en la base de datos desde la última copia de seguridad completa, para decidir si se necesita una copia de seguridad diferencial.|
|pdw_node_id|**int**|**Se aplica a**: [!INCLUDE[ssSDWfull](../../includes/sssdwfull-md.md)] , [!INCLUDE[ssPDW](../../includes/sspdw-md.md)]<br /><br /> Identificador del nodo en el que se encuentra esta distribución.|
|distribution_id|**int**|**Se aplica a**: [!INCLUDE[ssSDWfull](../../includes/sssdwfull-md.md)] , [!INCLUDE[ssPDW](../../includes/sspdw-md.md)]<br /><br /> Identificador numérico único asociado a la distribución.|
## <a name="remarks"></a>Comentarios
Los recuentos de páginas siempre son en el nivel de extensión. Por tanto, los valores de recuento de páginas siempre serán un múltiplo de ocho. Las extensiones que contienen páginas de asignación del Mapa de asignación global (GAM) y del Mapa de asignación global compartido (SGAM) se asignan a extensiones uniformes. No se incluyen en los recuentos de páginas descritos anteriormente. Para obtener más información acerca de las páginas y las extensiones, vea [Guía de arquitectura de páginas y extensiones](../../relational-databases/pages-and-extents-architecture-guide.md).
El contenido del almacén de versiones actual está en [Sys.dm_tran_version_store](../../relational-databases/system-dynamic-management-views/sys-dm-tran-version-store-transact-sql.md). El seguimiento de las páginas del almacén de la versión se realiza en el nivel de archivo en vez de en el nivel de sesión y tarea porque son recursos globales. Una sesión puede generar versiones, pero las versiones no pueden quitarse cuando finaliza la sesión. Debe tenerse en cuenta una limpieza del almacén de versiones cuando se tengan que ejecutar transacciones prolongadas que necesiten acceso a la versión determinada. La transacción de ejecución más larga relacionada con la limpieza del almacén de versiones se puede detectar viendo la elapsed_time_seconds columna en [Sys.dm_tran_active_snapshot_database_transactions](../../relational-databases/system-dynamic-management-views/sys-dm-tran-active-snapshot-database-transactions-transact-sql.md).
Los cambios frecuentes en la columna mixed_extent_page_count pueden indicar un uso exhaustivo de páginas SGAM. Cuando ocurre esto, puede ver muchas esperas de PAGELATCH_UP en las que el recurso esperado es una página SGAM. Para obtener más información, vea [sys.dm_os_waiting_tasks (Transact-sql)](../../relational-databases/system-dynamic-management-views/sys-dm-os-waiting-tasks-transact-sql.md), [Sys.dm_os_wait_stats (transact-sql)](../../relational-databases/system-dynamic-management-views/sys-dm-os-wait-stats-transact-sql.md)y [Sys.dm_os_latch_stats (Transact-SQL ](../../relational-databases/system-dynamic-management-views/sys-dm-os-latch-stats-transact-sql.md).
## <a name="user-objects"></a>Objetos de usuario
Los objetos siguientes se incluyen en los contadores de páginas de objetos de usuario:
- Índices y tablas definidos por el usuario
- Índices y tablas del sistema
- Índices y tablas temporales globales
- Índices y tablas temporales locales
- Variables de tabla
- Tablas devueltas en las funciones con valores de tabla.
## <a name="internal-objects"></a>Objetos internos
Los objetos internos están solo en tempdb. Los objetos siguientes se incluyen en los contadores de páginas de objetos internos:
- Tablas de trabajo para operaciones de cola o cursor y almacenamiento de objetos grandes (LOB) temporales
- Archivos de trabajo para operaciones como la combinación hash
- Ordenaciones
## <a name="relationship-cardinalities"></a>Cardinalidades de relación
|From|En|Relación|
|----------|--------|------------------|
|sys.dm_db_file_space_usage.database_id, file_id|sys.dm_io_virtual_file_stats.database_id, file_id|Uno a uno|
## <a name="permissions"></a>Permisos
En [!INCLUDE[ssNoVersion_md](../../includes/ssnoversion-md.md)] , requiere el `VIEW SERVER STATE` permiso.
En SQL Database objetivos de servicio Basic, S0 y S1, y para las bases de datos de grupos elásticos, `Server admin` `Azure Active Directory admin` se requiere la cuenta o. En el resto de los objetivos del servicio SQL Database, `VIEW DATABASE STATE` se requiere el permiso en la base de datos.
## <a name="examples"></a>Ejemplos
### <a name="determing-the-amount-of-free-space-in-tempdb"></a>Determinar la cantidad de espacio disponible en tempdb
La consulta siguiente devuelve el número total de páginas libres y el espacio disponible total en megabytes (MB) disponible en todos los archivos de datos de **tempdb**.
```sql
USE tempdb;
GO
SELECT SUM(unallocated_extent_page_count) AS [free pages],
(SUM(unallocated_extent_page_count)*1.0/128) AS [free space in MB]
FROM sys.dm_db_file_space_usage;
```
### <a name="determining-the-amount-of-space-used-by-user-objects"></a>Determinar la cantidad de espacio utilizado por objetos de usuario
La consulta siguiente devuelve el número total de páginas utilizadas por los objetos de usuario y el espacio total utilizado por los objetos de usuario en tempdb.
```sql
USE tempdb;
GO
SELECT SUM(user_object_reserved_page_count) AS [user object pages used],
(SUM(user_object_reserved_page_count)*1.0/128) AS [user object space in MB]
FROM sys.dm_db_file_space_usage;
```
## <a name="see-also"></a>Consulte también
[Funciones y vistas de administración dinámica (Transact-SQL)](~/relational-databases/system-dynamic-management-views/system-dynamic-management-views.md)
[Vistas de administración dinámica relacionadas con bases de datos (Transact-SQL)](../../relational-databases/system-dynamic-management-views/database-related-dynamic-management-views-transact-sql.md)
[sys.dm_db_task_space_usage ()de Transact-SQL ](../../relational-databases/system-dynamic-management-views/sys-dm-db-task-space-usage-transact-sql.md)
[sys.dm_db_session_space_usage (Transact-SQL)](../../relational-databases/system-dynamic-management-views/sys-dm-db-session-space-usage-transact-sql.md)
| 91.587302 | 941 | 0.766464 | spa_Latn | 0.952041 |
d3c91173d461ed0fe4e527f973ddfc77349f6029 | 1,801 | md | Markdown | content/project/botnetemulator/index.md | kshankar/academic-shankar | 9a41391c7224fd98cc2b721d4da1d91880f7116a | [
"MIT"
] | null | null | null | content/project/botnetemulator/index.md | kshankar/academic-shankar | 9a41391c7224fd98cc2b721d4da1d91880f7116a | [
"MIT"
] | null | null | null | content/project/botnetemulator/index.md | kshankar/academic-shankar | 9a41391c7224fd98cc2b721d4da1d91880f7116a | [
"MIT"
] | null | null | null | ---
title: An advanced network manipulation method to (re)establish Peer to Peer botnet overlays within isolated Internet emulation testbeds
summary: A USM short-term research grant to investigate methods to bootstrap real-life P2P botnets in an isolated testbed for further analysis.
tags:
- Cyber Security
date: "2021-09-12T00:00:00Z"
# Optional external URL for project (replaces project detail page).
external_link: ""
image:
focal_point: Smart
links:
url_code: ""
url_pdf: ""
url_slides: ""
url_video: ""
# Slides (optional).
# Associate this project with Markdown slides.
# Simply enter your slide deck's filename without extension.
# E.g. `slides = "example-slides"` references `content/slides/example-slides.md`.
# Otherwise, set `slides = ""`.
slides: example
---
The main objectives defined to achieve the goal of this research are:
1. To investigate and propose a method to (re)establish a P2P botnet overlay using real-world malware samples
2. To collect realistic P2P botnet datasets for further investigations and analysis
Project Duration: **01/09/2021-31/08/2023**
Grant No: **USM Short Term Grant 304/PNAV/6313332**
### Project Members:
- Dr. Shankar Karuppayah (PI)
- Assoc. Prof. Dr. Selvakumar Manickam
### Collaborators (TU Darmstadt):
- Prof. Dr. Max Mühlhäuser
- M.Sc. Leon Böck
### Open Positions:
- MSc by Research (Full Time) - Stipend Available (Sept 2021 - Aug 2023)
- Requirements:
- Bachelor's degree in Computer Science/Electric & Electronic Engineering, Computer Engineering/Information Technology or equivalent.
- A minimum CGPA of 2.75/4.0 or equivalent.
- Good understanding of the fundamentals of (computer) networking
- \[Optional\] Experience in Reverse Engineering and/or OpenStack deployments are advantageous
| 33.981132 | 144 | 0.747918 | eng_Latn | 0.934236 |
d3ca7b8849cdcf224abcf5be79b316cea2d7dbc2 | 642 | md | Markdown | 2-Ambiente/4-Dicas-gerais.md | sidarkelse/php4noobs | d5d905de53c65740f16b80f62efdc3e2b4a420c0 | [
"MIT"
] | 1 | 2021-03-14T18:08:35.000Z | 2021-03-14T18:08:35.000Z | 2-Ambiente/4-Dicas-gerais.md | sidarkelse/php4noobs | d5d905de53c65740f16b80f62efdc3e2b4a420c0 | [
"MIT"
] | null | null | null | 2-Ambiente/4-Dicas-gerais.md | sidarkelse/php4noobs | d5d905de53c65740f16b80f62efdc3e2b4a420c0 | [
"MIT"
] | null | null | null | ## 2.4 Dicas Gerais
Aqui está uma lista de dicas que não necessariamente serão usadas no desenvolvimento com PHP mas também para melhor aprendizado como desenvolvedor.
- Para cada **Error**, **Warning**, **Fatal** ou qualquer bug que apareça no seu console/tela e você não ter uma solução aparente, eu aconselho que você copie a saída/erro e jogue no google pois outras pessoas claramente já passaram pelo mesmo problema e já pediram ajuda em algum fórum como o **StackOverflow**
- Aprenda a pesquisar dúvidas no site **StackOverflow** pois ele é de longe o melhor amigo de qualquer desenvolvedor, seja o mais iniciante até o mais sênior.
| 80.25 | 311 | 0.781931 | por_Latn | 1.000008 |
d3cb4bfde8bce79ee2ecba055ed008a79fa08cae | 62 | md | Markdown | README.md | miarothberg/assignment_05_110421 | c28908f8fd803e52302c0803e540c246242e9471 | [
"MIT"
] | null | null | null | README.md | miarothberg/assignment_05_110421 | c28908f8fd803e52302c0803e540c246242e9471 | [
"MIT"
] | null | null | null | README.md | miarothberg/assignment_05_110421 | c28908f8fd803e52302c0803e540c246242e9471 | [
"MIT"
] | null | null | null | # assignment_05_110421
Assignment 5 for Advanced Data Science
| 20.666667 | 38 | 0.854839 | kor_Hang | 0.354732 |
d3cc3de51700e741d3078116a2d4a5a50ab77e62 | 3,664 | md | Markdown | packages/ace/README.md | Shubham567/Operational-Transformation | d0e82a385f3a0c20be49827ba2aea3dfa9142b89 | [
"MIT"
] | 16 | 2021-08-30T11:24:59.000Z | 2022-03-11T11:55:10.000Z | packages/ace/README.md | Shubham567/Operational-Transformation | d0e82a385f3a0c20be49827ba2aea3dfa9142b89 | [
"MIT"
] | 59 | 2021-08-30T19:48:55.000Z | 2021-10-16T21:13:56.000Z | packages/ace/README.md | Shubham567/Operational-Transformation | d0e82a385f3a0c20be49827ba2aea3dfa9142b89 | [
"MIT"
] | 6 | 2021-08-30T18:07:42.000Z | 2021-10-06T10:44:44.000Z | # `@otjs/ace`
[](https://www.npmjs.com/package/@otjs/ace)
[](https://www.npmjs.com/package/@otjs/ace)
[](https://www.npmjs.com/package/@otjs/ace)
[](https://www.npmjs.com/package/@otjs/ace)
[](https://github.com/Progyan1997/Operational-Transformation/blob/main/packages/ace/LICENSE)
[](https://www.npmjs.com/package/@otjs/ace)
[](https://www.npmjs.com/package/@otjs/ace)
[](https://github.com/Progyan1997/Operational-Transformation/blob/main/.github/SECURITY.md)
[](https://github.com/Progyan1997/Operational-Transformation)
[](https://github.com/Progyan1997/Operational-Transformation)
[](https://github.com/Progyan1997/Operational-Transformation/discussions)
## Description
> Editor Adapter implementation for Ace.
## Installation
- To install using [Yarn](https://yarnpkg.com) _(recommended)_:
```sh
$ yarn add @otjs/ace
```
- To install using [Npm](https://www.npmjs.com):
```sh
$ npm i @otjs/ace
```
### Peer Dependencies
Make sure to install all the peer dependencies beforehand:
[](https://ace.c9.io)
## Usage
---
```ts
import { AceAdapter } from "@otjs/ace";
const aceAdapter = new AceAdapter({
editor: // Ace Editor Instance
announcementDuration: // Duration (in ms) of User Name Announcement beside Cursor (optional)
bindEvents: // Boolean on whether or not to emit events from Adapter (optional)
});
```
**Note**: An API documentation will be shipped along with the package. This will power intellisense in the editor of your choice.
## Testing
We don't have any Unit Test Suite for `@otjs/ace`. Please refer to root [README](https://github.com/Progyan1997/Operational-Transformation/blob/main/README.md) for details regarding Integration Test Suite that concerns ace.
## Reporting a Bug
Head on to [**Discussion**](https://github.com/Progyan1997/Operational-Transformation/discussions) section to report a bug or to ask for any feature. Use this [template](https://github.com/Progyan1997/Operational-Transformation/discussions/30) to make it structural and helpful for the maintainer and the contributors. Feel to add your queries about using this library as well under _Q & A_ section of it. Remember, do not create any Issues by yourself, maintainers of this repository will open one if deemed necessary.
## Changelog
See [CHANGELOG](https://github.com/Progyan1997/Operational-Transformation/blob/main/CHANGELOG.md) for more details on what has been changed in the latest release.
## Contributing
See [Contributing Guidelines](https://github.com/Progyan1997/Operational-Transformation/blob/main/.github/CONTRIBUTING.md).
## License
This project is licensed under the terms of the MIT license, see [LICENSE](https://github.com/Progyan1997/Operational-Transformation/blob/main/packages/ace/LICENSE) for more details.
| 49.513514 | 519 | 0.755186 | yue_Hant | 0.375158 |
d3cd24501f57c3470efb34cdea7e5de7e62e63a6 | 261 | md | Markdown | docs/vs-2015/includes/wf-md.md | klmnden/visualstudio-docs.tr-tr | 82aa1370dab4ae413f5f924dad3e392ecbad0d02 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-09-01T20:45:52.000Z | 2020-09-01T20:45:52.000Z | docs/vs-2015/includes/wf-md.md | klmnden/visualstudio-docs.tr-tr | 82aa1370dab4ae413f5f924dad3e392ecbad0d02 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vs-2015/includes/wf-md.md | klmnden/visualstudio-docs.tr-tr | 82aa1370dab4ae413f5f924dad3e392ecbad0d02 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
ms.openlocfilehash: 13cf82e9ce8709fed4cca7135989f96e4100dc18
ms.sourcegitcommit: 748d9cd7328a30f8c80ce42198a94a4b5e869f26
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 07/15/2019
ms.locfileid: "68142816"
---
Windows Workflow Foundation (WF) | 29 | 60 | 0.83908 | yue_Hant | 0.349573 |
d3ce78d94e8271f7866ea6667b6920bb6a3606ae | 924 | md | Markdown | README.md | Elbandi/proxmox-spice-quickconnect | c20dd83db2ffdb1215974f4502f24dd00e96a705 | [
"MIT"
] | 9 | 2019-05-13T14:21:19.000Z | 2021-09-06T10:09:54.000Z | README.md | Elbandi/proxmox-spice-quickconnect | c20dd83db2ffdb1215974f4502f24dd00e96a705 | [
"MIT"
] | null | null | null | README.md | Elbandi/proxmox-spice-quickconnect | c20dd83db2ffdb1215974f4502f24dd00e96a705 | [
"MIT"
] | 6 | 2019-05-17T15:30:25.000Z | 2022-02-05T08:14:29.000Z | # proxmox-spice-quickconnect
Proxmox spice quickconnect
## How to build executable on Linux
Build and install: `go get -u github.com/Elbandi/proxmox-spice-quickconnect`
Download and build only: `wget https://raw.githubusercontent.com/Elbandi/proxmox-spice-quickconnect/master/main.go` and `go build -o proxmox-vm-connect .`
Build command for a windows executable: `env GOOS=windows GOARCH=amd64 go build -o proxmox-vm-connect.exe .`
[Source](https://www.digitalocean.com/community/tutorials/how-to-build-go-executables-for-multiple-platforms-on-ubuntu-16-04)
---
## Command line parameters
`-host pvenodeip -user foobar@pve -pass secret -vmid 123`
or from a config file:
```
host=pvenodeip
user=foobar@pve
pass=secret
vmid=123
viewer=path/to/remote-viewer.exe
```
use: `-config path/to/configfile`
[Source](https://forum.proxmox.com/threads/remote-spice-access-without-using-web-manager.16561/post-255078)
---
| 25.666667 | 154 | 0.766234 | eng_Latn | 0.468406 |
d3ce87a1e2425258f9de85ea8340e6e433409408 | 2,174 | md | Markdown | README.md | ggwiebe/dbx-data-quality | 7e4d1e398eedf448fb3029b603bc288c96d22363 | [
"Apache-2.0"
] | null | null | null | README.md | ggwiebe/dbx-data-quality | 7e4d1e398eedf448fb3029b603bc288c96d22363 | [
"Apache-2.0"
] | null | null | null | README.md | ggwiebe/dbx-data-quality | 7e4d1e398eedf448fb3029b603bc288c96d22363 | [
"Apache-2.0"
] | null | null | null | # dbx-data-quality - Databricks Data Quality
Prototype solution for tracking the quality and lineage of data/files ingested into Databricks.
## Project Ogranization
This project demonstrates an approach to organizing a project that:
- Includes Python library components
- Leverages common config via JSON or Secrets
- Accounts for interactive setup and automated execution
These elements in the broader Databricks DevOps landscape is shown in the following diagram:
## Components
This prototype solution is separated into:
- config - a directory for holding a separate & external config (a build manager could replace and inject a config per environment)
- utils - a directory for a set of python libraries that perform useful information
## Initialization & Configuration
This prototype dynamically determines current information like user_name and notebook name to be used for subsequent tracking.
Subsequent to environmental initialization, one can use a persistent config, separate and external to this notebook. Two options are provided:
- JSON config located in config/setup.json
- Secrets key/value pairs (defaulting to using ggw_quality as the secret scope)
### Secrets setup
The following commands need to be run to setup a secret scope and then to add the necessary config values to be used to configure this prototype:
```
databricks secrets create-scope --scope ggw_scope
```
Then to your chosen scope add the necessary config values:
```
databricks secrets put --scope ggw_scope --key store_loc --string-value /users/glenn.wiebe@databricks.com/
databricks secrets put --scope ggw_scope --key db_name --string-value ggw_wine
databricks secrets put --scope ggw_scope --key track_table_name --string-value load_track
```
To confirm your setup, run this DB CLI secrets command:
```
databricks secrets list --scope ggw_scope
databricks secrets get --scope ggw_scope -key store_loc
databricks secrets get --scope ggw_scope -key db_name
databricks secrets get --scope ggw_scope -key track_table_name
```
| 42.627451 | 147 | 0.775989 | eng_Latn | 0.983935 |
d3ce8bbf6d8a011ba22648de00ac05a0313a8508 | 67,294 | md | Markdown | docs/mfc/reference/cfiledialog-class.md | OpenLocalizationTestOrg/cpp-docs.it-it | 05d8d2dcc95498d856f8456e951d801011fe23d1 | [
"CC-BY-4.0"
] | 1 | 2020-05-21T13:09:13.000Z | 2020-05-21T13:09:13.000Z | docs/mfc/reference/cfiledialog-class.md | OpenLocalizationTestOrg/cpp-docs.it-it | 05d8d2dcc95498d856f8456e951d801011fe23d1 | [
"CC-BY-4.0"
] | null | null | null | docs/mfc/reference/cfiledialog-class.md | OpenLocalizationTestOrg/cpp-docs.it-it | 05d8d2dcc95498d856f8456e951d801011fe23d1 | [
"CC-BY-4.0"
] | null | null | null | ---
title: CFileDialog Class | Microsoft Docs
ms.custom:
ms.date: 11/04/2016
ms.reviewer:
ms.suite:
ms.technology:
- devlang-cpp
ms.tgt_pltfrm:
ms.topic: reference
f1_keywords:
- CFileDialog
dev_langs:
- C++
helpviewer_keywords:
- CFileDialog class
- common file dialog boxes
- dialog boxes, common
ms.assetid: fda4fd3c-08b8-4ce0-8e9d-7bab23f8c6c0
caps.latest.revision: 47
author: mikeblome
ms.author: mblome
manager: ghogen
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
translationtype: Human Translation
ms.sourcegitcommit: 5c6fbfc8699d7d66c40b0458972d8b6ef0dcc705
ms.openlocfilehash: b63da707c8fd5574663dcd1e037d45cb67c36f94
---
# CFileDialog Class
Encapsulates the common dialog box that is used for file open or file save operations.
## Syntax
```
class CFileDialog : public CCommonDialog
```
## Members
### Public Constructors
|Name|Description|
|----------|-----------------|
|[CFileDialog::CFileDialog](#cfiledialog__cfiledialog)|Constructs a `CFileDialog` object.|
### Public Methods
|Name|Description|
|----------|-----------------|
|[CFileDialog::AddCheckButton](#cfiledialog__addcheckbutton)|Adds a check button to the dialog.|
|[CFileDialog::AddComboBox](#cfiledialog__addcombobox)|Adds a combo box to the dialog.|
|[CFileDialog::AddControlItem](#cfiledialog__addcontrolitem)|Adds an item to a container control in the dialog.|
|[CFileDialog::AddEditBox](#cfiledialog__addeditbox)|Adds an edit box to the dialog.|
|[CFileDialog::AddMenu](#cfiledialog__addmenu)|Adds a menu to the dialog.|
|[CFileDialog::AddPlace](#cfiledialog__addplace)|Overloaded. Adds a folder to the list of places available for the user to open or save items.|
|[CFileDialog::AddPushButton](#cfiledialog__addpushbutton)|Adds a button to the dialog.|
|[CFileDialog::AddRadioButtonList](#cfiledialog__addradiobuttonlist)|Adds an option button (also known as radio button) group to the dialog.|
|[CFileDialog::AddSeparator](#cfiledialog__addseparator)|Adds a separator to the dialog.|
|[CFileDialog::AddText](#cfiledialog__addtext)|Adds text content to the dialog.|
|[CFileDialog::ApplyOFNToShellDialog](#cfiledialog__applyofntoshelldialog)|Updates the state of the `CFileDialog` to match the parameters and flags stored in the `m_ofn` member variable.|
|[CFileDialog::DoModal](#cfiledialog__domodal)|Displays the dialog box and enables the user to make a selection.|
|[CFileDialog::EnableOpenDropDown](#cfiledialog__enableopendropdown)|Enables a drop-down list on the **Open** or **Save** button in the dialog.|
|[CFileDialog::EndVisualGroup](#cfiledialog__endvisualgroup)|Stops the addition of elements to a visual group in the dialog.|
|[CFileDialog::GetCheckButtonState](#cfiledialog__getcheckbuttonstate)|Gets the current state of a check button (check box) in the dialog.|
|[CFileDialog::GetControlItemState](#cfiledialog__getcontrolitemstate)|Gets the current state of an item in a container control found in the dialog.|
|[CFileDialog::GetControlState](#cfiledialog__getcontrolstate)|Gets the current visibility and enabled states of a given control.|
|[CFileDialog::GetEditBoxText](#cfiledialog__geteditboxtext)|Gets the current text in an edit box control.|
|[CFileDialog::GetFileExt](#cfiledialog__getfileext)|Returns the extension of the selected file.|
|[CFileDialog::GetFileName](#cfiledialog__getfilename)|Returns the file name of the selected file.|
|[CFileDialog::GetFileTitle](#cfiledialog__getfiletitle)|Returns the title of the selected file.|
|[CFileDialog::GetFolderPath](#cfiledialog__getfolderpath)|Retrieves the path of the currently open folder or directory for an Explorer-style **Open** or **Save As** common dialog box.|
|[CFileDialog::GetIFileDialogCustomize](#cfiledialog__getifiledialogcustomize)|Retrieves the internal COM object for a customized `CFileDialog` object.|
|[CFileDialog::GetIFileOpenDialog](#cfiledialog__getifileopendialog)|Retrieves the internal COM object for a `CFileDialog` that is used as an **Open** file dialog box.|
|[CFileDialog::GetIFileSaveDialog](#cfiledialog__getifilesavedialog)|Retrieves the internal COM object for a `CFileDialog` that is used as a **Save** file dialog box.|
|[CFileDialog::GetNextPathName](#cfiledialog__getnextpathname)|Returns the full path of the next selected file.|
|[CFileDialog::GetOFN](#cfiledialog__getofn)|Retrieves the `OPENFILENAME` structure of the `CFileDialog` object.|
|[CFileDialog::GetPathName](#cfiledialog__getpathname)|Returns the full path of the selected file.|
|[CFileDialog::GetReadOnlyPref](#cfiledialog__getreadonlypref)|Returns the read-only status of the selected file.|
|[CFileDialog::GetResult](#cfiledialog__getresult)|Gets the choice that the user made in the dialog.|
|[CFileDialog::GetResults](#cfiledialog__getresults)|Gets the user's choices in a dialog that allows multiple selection.|
|[CFileDialog::GetSelectedControlItem](#cfiledialog__getselectedcontrolitem)|Gets a particular item from specified container controls in the dialog.|
|[CFileDialog::GetStartPosition](#cfiledialog__getstartposition)|Returns the position of the first element of the file name list.|
|[CFileDialog::HideControl](#cfiledialog__hidecontrol)|Hides the specified control in an Explorer-style **Open** or **Save As** common dialog box.|
|[CFileDialog::IsPickFoldersMode](#cfiledialog__ispickfoldersmode)|Determines if the current dialog in folder picker mode.|
|[CFileDialog::MakeProminent](#cfiledialog__makeprominent)|Places a control in the dialog so that it stands out compared to other added controls.|
|[CFileDialog::RemoveControlItem](#cfiledialog__removecontrolitem)|Removes an item from a container control in the dialog.|
|[CFileDialog::SetCheckButtonState](#cfiledialog__setcheckbuttonstate)|Sets the current state of a check button (check box) in the dialog.|
|[CFileDialog::SetControlItemState](#cfiledialog__setcontrolitemstate)|Sets the current state of an item in a container control found in the dialog.|
|[CFileDialog::SetControlItemText](#cfiledialog__setcontrolitemtext)|Sets the text of a control item. For example, the text that accompanies a radio button or an item in a menu.|
|[CFileDialog::SetControlLabel](#cfiledialog__setcontrollabel)|Sets the text associated with a control, such as button text or an edit box label.|
|[CFileDialog::SetControlState](#cfiledialog__setcontrolstate)|Sets the current visibility and enabled states of a given control.|
|[CFileDialog::SetControlText](#cfiledialog__setcontroltext)|Sets the text for the specified control in an Explorer-style **Open** or **Save As** common dialog box.|
|[CFileDialog::SetDefExt](#cfiledialog__setdefext)|Sets the default file name extension for an Explorer-style **Open** or **Save As** common dialog box.|
|[CFileDialog::SetEditBoxText](#cfiledialog__seteditboxtext)|Sets the current text in an edit box control.|
|[CFileDialog::SetProperties](#cfiledialog__setproperties)|Provides a property store that defines the default values to be used for the item being saved.|
|[CFileDialog::SetSelectedControlItem](#cfiledialog__setselectedcontrolitem)|Sets the selected state of a particular item in an option button group or a combo box found in the dialog.|
|[CFileDialog::SetTemplate](#cfiledialog__settemplate)|Sets the dialog box template for the `CFileDialog` object.|
|[CFileDialog::StartVisualGroup](#cfiledialog__startvisualgroup)|Declares a visual group in the dialog. Subsequent calls to any "add" method add those elements to this group.|
|[CFileDialog::UpdateOFNFromShellDialog](#cfiledialog__updateofnfromshelldialog)|Updates the data stored in the `m_ofn` member variable to match the current state of the file dialog box.|
### Protected Methods
|Name|Description|
|----------|-----------------|
|[CFileDialog::OnButtonClicked](#cfiledialog__onbuttonclicked)|Called when the button is clicked.|
|[CFileDialog::OnCheckButtonToggled](#cfiledialog__oncheckbuttontoggled)|Called when the check box is checked/unchecked.|
|[CFileDialog::OnControlActivating](#cfiledialog__oncontrolactivating)|Called when the control is being active.|
|[CFileDialog::OnFileNameChange](#cfiledialog__onfilenamechange)|Handles the `WM_NOTIFY CDN_SELCHANGE` message.|
|[CFileDialog::OnFileNameOK](#cfiledialog__onfilenameok)|Validates the file name entered in the dialog box.|
|[CFileDialog::OnFolderChange](#cfiledialog__onfolderchange)|Handles the `WM_NOTIFY CDN_FOLDERCHANGE` message.|
|[CFileDialog::OnInitDone](#cfiledialog__oninitdone)|Handles the `WM_NOTIFY CDN_INITDONE` message.|
|[CFileDialog::OnItemSelected](#cfiledialog__onitemselected)|Called when the container item is being selected.|
|[CFileDialog::OnLBSelChangedNotify](#cfiledialog__onlbselchangednotify)|Allows you to perform custom actions when the file selection changes.|
|[CFileDialog::OnShareViolation](#cfiledialog__onshareviolation)|Handles share violations.|
|[CFileDialog::OnTypeChange](#cfiledialog__ontypechange)|Handles the `WM_NOTIFY CDN_TYPECHANGE` message.|
### Public Data Members
|Name|Description|
|----------|-----------------|
|[CFileDialog::m_ofn](#cfiledialog__m_ofn)|The Windows `OPENFILENAME` structure. Provides access to basic file dialog box parameters.|
## Remarks
Common file dialog boxes let you implement file-selection dialog boxes, for example, **Open File** and **Save As**, in a manner that is consistent with Windows standards.
You can use [CFileDialog](../../mfc/reference/cfiledialog-class.md) as is with the constructor provided, or you can derive your own dialog box class from `CFileDialog` and write a constructor to suit your needs. In either case, these dialog boxes will behave like standard MFC dialog boxes because they are derived from the [CCommonDialog Class](../../mfc/reference/ccommondialog-class.md). `CFileDialog` relies on the COMMDLG.DLL file that is included in Windows.
Both the appearance and the functionality of the `CFileDialog` with [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)] differ from the earlier versions of Windows. The default `CFileDialog` automatically uses the new [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)] style without code changes if a program is compiled and run under [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)]. Use the `bVistaStyle` parameter in the constructor to manually override this automatic update. The exception to the automatic update is customized dialog boxes. They will not be converted to the new style. For more information about the constructor, see [CFileDialog::CFileDialog](#cfiledialog__cfiledialog).
> [!NOTE]
> The control ID system differs in [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)] from earlier versions of Windows when you use a `CFileDialog`. You must update all references to `CFileDialog` controls in code before you can port your project from an earlier version of Windows.
Some `CFileDialog` methods are not supported under [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)]. Check the individual method topic for information about whether the method is supported. In addition, the following inherited functions are not supported under [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)]:
- [CDialog::OnInitDialog](../../mfc/reference/cdialog-class.md#cdialog__oninitdialog)
- [CDialog::OnSetFont](../../mfc/reference/cdialog-class.md#cdialog__onsetfont)
The windows messages for the `CFileDialog` class vary based on what operating system you are using. For example, Windows XP does not support [CDialog::OnCancel](../../mfc/reference/cdialog-class.md#cdialog__oncancel) and [CDialog::OnOK](../../mfc/reference/cdialog-class.md#cdialog__onok) for the `CFileDialog` class. However, [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)] does support them. For more information about the different messages that are generated and the order in which they are received, see [CFileDialog Sample: Logging Event Order](../../visual-cpp-samples.md).
To use a `CFileDialog` object, first create the object by using the `CFileDialog` constructor. After the dialog box has been constructed, you can set or modify any values in the [CFileDialog::m_ofn](#cfiledialog__m_ofn) structure to initialize the values or states of the dialog box controls. The `m_ofn` structure is of type `OPENFILENAME`. For more information, see the [OPENFILENAME](http://msdn.microsoft.com/library/windows/desktop/ms646839) structure in the [!INCLUDE[winSDK](../../atl/includes/winsdk_md.md)].
After you initialize the dialog box controls, call the [CFileDialog::DoModal](#cfiledialog__domodal) method to display the dialog box so that the user can type the path and file name. `DoModal` returns whether the user clicked the OK (IDOK) or the Cancel (IDCANCEL) button. If `DoModal` returns IDOK, you can use one of the `CFileDialog` public member functions to retrieve the information put in by the user.
> [!NOTE]
> Under [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)], multiple calls to [IFileDialog::SetFileTypes](http://msdn.microsoft.com/library/windows/desktop/bb775980) causes an error. The second call to `SetFileTypes` for any instance of a `CFileDialog` will return `E_UNEXPECTED` in [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)]. Some `CFileDialog` method functions call `SetFileTypes`. For example, two calls to `CFileDialog::DoModal` for the same instance of a `CFileDialog` generates [ASSERT](http://msdn.microsoft.com/library/1e70902d-d58c-4e7b-9f69-2aeb6cbe476c).
`CFileDialog` includes several protected members that let you do custom handling of share violations, file name validation, and list-box change notification. These protected members are callback functions that most applications do not have to use because default handling is performed automatically. Message-map entries for these functions are not required because they are standard virtual functions.
You can use the Windows [CommDlgExtendedError](http://msdn.microsoft.com/library/windows/desktop/ms646916) function to determine whether an error occurred during initialization of the dialog box and to learn more about the error.
The destruction of `CFileDialog` objects is handled automatically. You do not have to call [CDialog::EndDialog](../../mfc/reference/cdialog-class.md#cdialog__enddialog).
To let the user select multiple files, set the `OFN_ALLOWMULTISELECT` flag before you call `DoModal`. You must supply your own file name buffer to accommodate the returned list of multiple file names. Do this by replacing `m_ofn.lpstrFile` with a pointer to a buffer you have allocated, after you construct the `CFileDialog`, but before you call `DoModal`.
Additionally, you must set `m_ofn.nMaxFile` by using the number of characters in the buffer pointed to by `m_ofn.lpstrFile`. If you set the maximum number of files to be selected to `n`, the required buffer size is `n * (_MAX_PATH + 1) + 1`. The first item returned in the buffer is the path to the folder where the files were selected. For [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)]-style dialog boxes, the directory and file name strings are null-terminated, with an extra null character after the last file name. This format enables the Explorer-style dialog boxes to return long file names that include spaces. For old-style dialog boxes, the directory and file name strings are separated by spaces and the function uses short file names for file names with spaces.
The following example demonstrates how to use a buffer to retrieve and list multiple file names.
[!code-cpp[NVC_MFCFiles#23](../../atl-mfc-shared/reference/codesnippet/cpp/cfiledialog-class_1.cpp)]
To change the buffer size in response to the user selecting multiple file names, you must derive a new class from `CFileDialog` and override the [CFileDialog::OnFileNameChange](#cfiledialog__onfilenamechange) method.
If you derive a new class from `CFileDialog`, you can use a message map to handle any messages. To extend the default message handling, derive a class from `CFileDialog`, add a message map to the new class, and provide member functions for the new messages. You do not have to provide a hook function to customize the dialog box.
To customize the dialog box, derive a class from `CFileDialog`, provide a custom dialog box template, and add a message map to process the notification messages from the extended controls. Pass any unprocessed messages to the base class. You do not have to customize the hook function.
When you are using the [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)] style of the `CFileDialog`, you cannot use message maps and dialog box templates. Instead, you must use the COM interfaces for similar functionality.
For more information about how to use `CFileDialog`, see [Common Dialog Classes](../../mfc/common-dialog-classes.md).
## Inheritance Hierarchy
[CObject](../../mfc/reference/cobject-class.md)
[CCmdTarget](../../mfc/reference/ccmdtarget-class.md)
[CWnd](../../mfc/reference/cwnd-class.md)
[CDialog](../../mfc/reference/cdialog-class.md)
[CCommonDialog](../../mfc/reference/ccommondialog-class.md)
`CFileDialog`
## Requirements
**Header:** afxdlgs.h
## <a name="cfiledialog__addcheckbutton"></a> CFileDialog::AddCheckButton
Adds a check button to the dialog.
```
HRESULT AddCheckButton(
DWORD dwIDCtl,
const CString& strLabel,
BOOL bChecked);
```
### Parameters
`dwIDCtl`
The ID of the check button to add.
`strLabel`
The check button name.
`bChecked`
A Boolean indicating the current state of the check button. `TRUE` if checked; `FALSE` otherwise
### Remarks
## <a name="cfiledialog__addcombobox"></a> CFileDialog::AddComboBox
Adds a combo box to the dialog.
```
HRESULT AddComboBox(DWORD dwIDCtl);
```
### Parameters
`dwIDCtl`
The ID of the combo box to add.
### Remarks
## <a name="cfiledialog__addcontrolitem"></a> CFileDialog::AddControlItem
Adds an item to a container control in the dialog.
```
HRESULT AddControlItem(
DWORD dwIDCtl,
DWORD dwIDItem,
const CString& strLabel);
```
### Parameters
`dwIDCtl`
The ID of the container control to add the item to.
`dwIDItem`
The ID of the item.
`strLabel`
Item's text.
### Remarks
## <a name="cfiledialog__addeditbox"></a> CFileDialog::AddEditBox
Adds an edit box to the dialog.
```
HRESULT AddEditBox(
DWORD dwIDCtl,
const CString& strText);
```
### Parameters
`dwIDCtl`
The ID of the edit box to add.
`strText`
The edit box name.
### Remarks
## <a name="cfiledialog__addmenu"></a> CFileDialog::AddMenu
Adds a menu to the dialog.
```
HRESULT AddMenu(
DWORD dwIDCtl,
const CString& strLabel);
```
### Parameters
`dwIDCtl`
The ID of the menu to add.
`strLabel`
The menu name.
### Remarks
## <a name="cfiledialog__addplace"></a> CFileDialog::AddPlace
Adds a folder to the list of places available for the user to open or save items.
```
void AddPlace(
LPCWSTR lpszFolder,
FDAP fdap = FDAP_TOP) throw();
void AddPlace(
IShellItem* psi,
FDAP fdap = FDAP_TOP) throw();
```
### Parameters
`lpszFolder`
A path to the folder to be made available to the user. This can only be a folder.
`fdap`
Specifies where the folder is placed within the list.
`psi`
A pointer to an IShellItem that represents the folder to be made available to the user. This can only be a folder.
### Remarks
## <a name="cfiledialog__addpushbutton"></a> CFileDialog::AddPushButton
Adds a button to the dialog.
```
HRESULT AddPushButton(
DWORD dwIDCtl,
const CString& strLabel);
```
### Parameters
`dwIDCtl`
The ID of the button to add.
`strLabel`
The button name.
### Remarks
## <a name="cfiledialog__addradiobuttonlist"></a> CFileDialog::AddRadioButtonList
Adds an option button (also known as radio button) group to the dialog.
```
HRESULT AddRadioButtonList(DWORD dwIDCtl);
```
### Parameters
`dwIDCtl`
The ID of the option button group to add.
### Remarks
## <a name="cfiledialog__addseparator"></a> CFileDialog::AddSeparator
Adds a separator to the dialog.
```
HRESULT AddSeparator(DWORD dwIDCtl);
```
### Parameters
`dwIDCtl`
The ID of the separator add.
### Remarks
## <a name="cfiledialog__addtext"></a> CFileDialog::AddText
Adds text to the dialog.
```
HRESULT AddText(
DWORD dwIDCtl,
const CString& strText);
```
### Parameters
`dwIDCtl`
The ID of the text to add.
`strText`
The text name.
### Remarks
## <a name="cfiledialog__applyofntoshelldialog"></a> CFileDialog::ApplyOFNToShellDialog
Updates the current state of the [CFileDialog](../../mfc/reference/cfiledialog-class.md) based on the values stored in the `m_ofn` data structure.
```
void ApplyOFNToShellDialog();
```
### Remarks
In versions of Windows before [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)], the member [OPENFILENAME](https://msdn.microsoft.com/library/ms911906.aspx) data structure was continuously synchronized with the state of the `CFileDialog`. Any changes to the [m_ofn](#cfiledialog__m_ofn) member variable were immediately reflected in the state of the dialog box. Also, any changes to the state of the dialog box immediately update the `m_ofn` member variable.
In [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)], the values in the `m_ofn` member variable and state of the `CFileDialog` are not guaranteed to be synchronized. This function forces the state of the `CFileDialog` to be updated to match the `m_ofn` structure. Windows calls this function automatically during [CFileDialog::DoModal](#cfiledialog__domodal).
For more information about how to use the `CFileDialog` class under [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)], see [CFileDialog Class](../../mfc/reference/cfiledialog-class.md).
### Example
See the example for [CFileDialog::UpdateOFNFromShellDialog](#cfiledialog__updateofnfromshelldialog).
## <a name="cfiledialog__cfiledialog"></a> CFileDialog::CFileDialog
Call this function to construct a standard Windows file dialog box.
```
explicit CFileDialog(
BOOL bOpenFileDialog,
LPCTSTR lpszDefExt = NULL,
LPCTSTR lpszFileName = NULL,
DWORD dwFlags = OFN_HIDEREADONLY | OFN_OVERWRITEPROMPT,
LPCTSTR lpszFilter = NULL,
CWnd* pParentWnd = NULL,
DWORD dwSize = 0,
BOOL bVistaStyle = TRUE);
```
### Parameters
[in] `bOpenFileDialog`
The parameter that specifies what type of dialog box to create. Set it to `TRUE` to construct a **File Open** dialog box. Set it to `FALSE` to construct a **File Save As** dialog box.
[in] `lpszDefExt`
The default file name extension. If the user does not include a known extension (one that has an association on the user’s computer) in the Filename box, the extension specified by `lpszDefExt` is automatically appended to the file name. If this parameter is `NULL`, no extension is appended.
[in] `lpszFileName`
The initial file name that appears in the Filename box. If `NULL`, no initial file name appears.
[in] `dwFlags`
A combination of one or more flags that you can use to customize the dialog box. For a description of these flags, see the [OPENFILENAME](http://msdn.microsoft.com/library/windows/desktop/ms646839) structure in the [!INCLUDE[winSDK](../../atl/includes/winsdk_md.md)]. If you modify the `m_ofn.Flags` structure member, use a bitwise-OR operator in your changes to keep the default behavior intact.
[in] `lpszFilter`
A series of string pairs that specify filters you can apply to the file. If you specify file filters, only files that match filter criteria will appear in the Files list. See the Remarks section for more information about how to work with file filters.
[in] `pParentWnd`
A pointer to the parent or owner window of the file dialog box.
[in] `dwSize`
The size of the `OPENFILENAME` structure. This value depends on the operating system version. MFC used this parameter to determine the appropriate kind of dialog box to create (for example, new [!INCLUDE[Win2kFamily](../../c-runtime-library/includes/win2kfamily_md.md)] dialog boxes instead of NT4 dialog boxes). The default size of 0 means that the MFC code will determine the correct dialog box size to use based on the operating system version on which the program is run.
[in] `bVistaStyle`
**Note** This parameter is available in Visual Studio 2008 and later and is will cause the new-style dialog to be used only if you are running in [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)] or later.
The parameter that specifies the style of the file dialog. Set it to `TRUE` to use the new Vista style file dialogs. Otherwise, the old style of dialog boxes will be used. See the Remarks section for more information about running under Vista.
### Remarks
Either a **File Open** or **File Save As** dialog box is constructed, depending on the value of `bOpenFileDialog`.
Specifying a default extension using `lpszDefExt` may not produce the behavior that you expect, because it is seldom predictable what extensions have file associations on the user’s computer. If you need more control over the appending of a default extension, you can derive your own class from `CFileDialog`, and override the `CFileDialog::OnFileNameOK` method to perform your own extension handling.
To enable the user to select multiple files, set the `OFN_ALLOWMULTISELECT` flag before you call [DoModal](#cfiledialog__domodal). You must supply your own file name buffer to store the returned list of multiple file names. Do this by replacing `m_ofn.lpstrFile` with a pointer to a buffer you have allocated, after you construct the [CFileDialog](../../mfc/reference/cfiledialog-class.md), but before you call `DoModal`. Additionally, you must set `m_ofn.nMaxFile` with the number of characters in the buffer pointed to by `m_ofn.lpstrFile`. If you set the maximum number of files to be selected to `n`, the necessary buffer size is `n`*(_MAX_PATH + 1) + 1. For example:
[!code-cpp[NVC_MFCFiles#23](../../atl-mfc-shared/reference/codesnippet/cpp/cfiledialog-class_1.cpp)]
To enable the user to resize an Explorer-style dialog box by using either the mouse or keyboard, set the `OFN_ENABLESIZING` flag. Setting this flag is necessary only if you provide a hook procedure or custom template. The flag works only with an Explorer-style dialog box; old-style dialog boxes cannot be resized.
The `lpszFilter` parameter is used to determine the type of file name a file must have to be displayed in the file list. The first string in the string pair describes the filter; the second string indicates the file name extension to use. Multiple extensions may be specified by using a semicolon (the ';' character) as the delimiter. The string ends with two '|' characters, followed by a `NULL` character. You can also use a [CString](../../atl-mfc-shared/using-cstring.md) object for this parameter.
For example, [!INCLUDE[ofprexcel](../../mfc/reference/includes/ofprexcel_md.md)] allows users to open files that have extensions .xlc (chart) or .xls (worksheet), among others. The filter for Excel could be written as:
[!code-cpp[NVC_MFCFiles#24](../../atl-mfc-shared/reference/codesnippet/cpp/cfiledialog-class_2.cpp)]
However, if you plan to use this string to directly update the `OPENFILENAME` structure, you should delimit your strings with the null character, '\0', instead of the vertical bars ('|').
The `bVistaStyle` parameter is applicable only when running under [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)]. Under earlier versions of Windows, this parameter is ignored. If `bVistaStyle` is set to `TRUE`, when you compile a program with [!INCLUDE[vs_orcas_long](../../atl/reference/includes/vs_orcas_long_md.md)] or later, the new Vista style **File Dialog** will be used. Otherwise, the previous MFC style **File Dialog** will be used. See [CFileDialog Class](../../mfc/reference/cfiledialog-class.md) for more information.
Dialog templates are not supported on dialogs based on `bVistaStyle`
### Example
See the example for [CFileDialog::DoModal](#cfiledialog__domodal).
## <a name="cfiledialog__domodal"></a> CFileDialog::DoModal
Call this function to display the Windows common file dialog box and allow the user to browse files and directories and enter a filename.
```
virtual INT_PTR DoModal();
```
### Return Value
**IDOK** or **IDCANCEL**. If **IDCANCEL** is returned, call the Windows [CommDlgExtendedError](http://msdn.microsoft.com/library/windows/desktop/ms646916) function to determine whether an error occurred.
**IDOK** and **IDCANCEL** are constants that indicate whether the user selected the OK or Cancel button.
### Remarks
If you want to initialize the various file dialog-box options by setting members of the **m_ofn** structure, you should do this before calling `DoModal`, but after the dialog object is constructed.
For example, if you want to allow the user to select multiple files, set the `OFN_ALLOWMULTISELECT` flag before calling `DoModal`, as shown in the code example in [CFileDialog Class](../../mfc/reference/cfiledialog-class.md).
When the user clicks the dialog box's OK or Cancel buttons, or selects the Close option from the dialog box's control menu, control is returned to your application. You can then call other member functions to retrieve the settings or information the user inputs into the dialog box.
`DoModal` is a virtual function overridden from class `CDialog`.
### Example
[!code-cpp[NVC_MFCFiles#25](../../atl-mfc-shared/reference/codesnippet/cpp/cfiledialog-class_3.cpp)]
## <a name="cfiledialog__enableopendropdown"></a> CFileDialog::EnableOpenDropDown
Enables a drop-down list on the Open or Save button in the dialog.
```
HRESULT EnableOpenDropDown(DWORD dwIDCtl);
```
### Parameters
`dwIDCtl`
The ID of the drop-down list.
### Remarks
## <a name="cfiledialog__endvisualgroup"></a> CFileDialog::EndVisualGroup
Stops the addition of elements to a visual group in the dialog.
```
HRESULT EndVisualGroup();
```
### Return Value
Returns S_OK if successful; an error value otherwise.
### Remarks
## <a name="cfiledialog__getcheckbuttonstate"></a> CFileDialog::GetCheckButtonState
Retrieves the current state of a check button (check box) in the dialog.
```
HRESULT GetCheckButtonState(
DWORD dwIDCtl,
BOOL& bChecked);
```
### Parameters
`dwIDCtl`
The ID of the check box.
`bChecked`
The state of the check box. `TRUE` indicates checked; `FALSE` indicates unchecked.
### Remarks
## <a name="cfiledialog__getcontrolitemstate"></a> CFileDialog::GetControlItemState
Retrieves the current state of an item in a container control found in the dialog.
```
HRESULT GetControlItemState(
DWORD dwIDCtl,
DWORD dwIDItem,
CDCONTROLSTATEF& dwState);
```
### Parameters
`dwIDCtl`
The ID of the container control.
`dwIDItem`
The ID of the item.
`dwState`
A reference to a variable that receives one of more values from the CDCONTROLSTATE enumeration that indicates the current state of the control.
### Remarks
## <a name="cfiledialog__getcontrolstate"></a> CFileDialog::GetControlState
Retrieves the current visibility and enabled states of a given control.
```
HRESULT GetControlState(
DWORD dwIDCtl,
CDCONTROLSTATEF& dwState);
```
### Parameters
`dwIDCtl`
The ID of the control.
`dwState`
A reference to a variable that receives one or more values from the CDCONTROLSTATE enumeration that indicates the current state of the control.
### Remarks
## <a name="cfiledialog__geteditboxtext"></a> CFileDialog::GetEditBoxText
Retrieves the current text in an edit box control.
```
HRESULT GetEditBoxText(
DWORD dwIDCtl,
CString& strText);
```
### Parameters
`dwIDCtl`
The ID of the edit box.
`strText`
The text value.
### Remarks
## <a name="cfiledialog__getfileext"></a> CFileDialog::GetFileExt
Call this function to retrieve the extension of the filename entered into the dialog box.
```
CString GetFileExt() const;
```
### Return Value
The extension of the filename.
### Remarks
For example, if the name of the file entered is DATA.TXT, `GetFileExt` returns "TXT".
If `m_ofn.Flags` has the `OFN_ALLOWMULTISELECT` flag set, this string contains a sequence of null-terminated strings, with the first string being the directory path of the file group selected, followed by the names of all files selected by the user. To retrieve file pathnames, use the [GetStartPosition](#cfiledialog__getstartposition) and [GetNextPathName](#cfiledialog__getnextpathname) member functions.
## <a name="cfiledialog__getfilename"></a> CFileDialog::GetFileName
Call this function to retrieve the name of the filename entered in the dialog box.
```
CString GetFileName() const;
```
### Return Value
The name of the file.
### Remarks
The name of the file includes both the prefix and the extension. For example, `GetFileName` will return "TEXT.DAT" for the file C:\FILES\TEXT.DAT.
If `m_ofn.Flags` has the `OFN_ALLOWMULTISELECT` flag set, you should call [GetStartPosition](#cfiledialog__getstartposition) and [GetNextPathName](#cfiledialog__getnextpathname) to retrieve a file pathname.
## <a name="cfiledialog__getfiletitle"></a> CFileDialog::GetFileTitle
Call this function to retrieve the title of the file entered in the dialog box.
```
CString GetFileTitle() const;
```
### Return Value
The title of the file.
### Remarks
The title of the file includes only its prefix, without the path or the extension. For example, `GetFileTitle` will return "TEXT" for the file C:\FILES\TEXT.DAT.
If `m_ofn.Flags` has the `OFN_ALLOWMULTISELECT` flag set, this string contains a sequence of null-terminated strings, with the first string being the directory path of the file group selected, followed by the names of all files selected by the user. For this reason, use the [GetStartPosition](#cfiledialog__getstartposition) and [GetNextPathName](#cfiledialog__getnextpathname) member functions to retrieve the next file name in the list.
### Example
See the example for [CFileDialog::DoModal](#cfiledialog__domodal).
## <a name="cfiledialog__getfolderpath"></a> CFileDialog::GetFolderPath
Call this member function to retrieve the path of the currently open folder or directory for an Explorer-style Open or Save As common dialog box.
```
CString GetFolderPath() const;
```
### Return Value
A [CString](../../atl-mfc-shared/reference/cstringt-class.md) object containing the currently open folder or directory.
### Remarks
The dialog box must have been created with the **OFN_EXPLORER** style; otherwise, the method will fail with an assertion.
You can call this method only while the dialog box is being displayed. After the dialog box has been closed, this function will no longer work, and the method will fail with an assertion.
## <a name="cfiledialog__getifiledialogcustomize"></a> CFileDialog::GetIFileDialogCustomize
Retrieves a pointer to the internal COM object for a given [CFileDialog](../../mfc/reference/cfiledialog-class.md).
```
IFileDialogCustomize* GetIFileDialogCustomize();
```
### Return Value
The pointer to the internal COM object for the `CFileDialog`. It is your responsibility to release this pointer appropriately.
### Remarks
Use this function only under [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)] with an object that has `bVistaStyle` set to `true`. If you use this function when `bVistaStyle` is `false`, it will return `NULL` in release mode and throw an assertion in debug mode.
For more information about the `IFileDialogCustomize` interface, see [IFileDialogCustomize](http://msdn.microsoft.com/library/windows/desktop/bb775912).
### Example
This example retrieves the internal COM object. To run this code example, you must compile it under [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)].
[!code-cpp[NVC_MFC_CFileDialog#4](../../mfc/reference/codesnippet/cpp/cfiledialog-class_4.cpp)]
## <a name="cfiledialog__getifileopendialog"></a> CFileDialog::GetIFileOpenDialog
Retrieves a pointer to the internal COM object for a given `CFileDialog`.
```
IFileOpenDialog* GetIFileOpenDialog();
```
### Return Value
The pointer to the internal COM object for the `CFileDialog`. It is your responsibility to release this pointer appropriately.
### Remarks
Use this function only under [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)] with an object that has `bVistaStyle` set to `true`. This function returns `NULL` if the `CFileDialog` is not an **Open** dialog box or if `bVistaStyle` is set to `false`. In this final case, the function only returns `NULL` in release mode - in debug mode it will throw an assertion.
For more information about the `IFileOpenDialog` interface, see [IFileOpenDialog](http://msdn.microsoft.com/library/windows/desktop/bb775834).
### Example
This example retrieves the internal COM object. To run this code, you must compile it under [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)].
[!code-cpp[NVC_MFC_CFileDialog#2](../../mfc/reference/codesnippet/cpp/cfiledialog-class_5.cpp)]
## <a name="cfiledialog__getifilesavedialog"></a> CFileDialog::GetIFileSaveDialog
Retrieves a pointer to the internal COM object for a given `CFileDialog`.
```
IFileSaveDialog* GetIFileSaveDialog();
```
### Return Value
The pointer to the internal COM object for the `CFileDialog`. It is your responsibility to release this pointer appropriately.
### Remarks
Use this function only under [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)] with an object that has `bVistaStyle` set to `true`. This function will return `NULL` if the `CFileDialog` is not a **Save** dialog box or if `bVistaStyle` is set to `false`. In this final case, the function only returns `NULL` in release mode - in debug mode it will throw an assertion.
For more information about the `IFileSaveDialog` interface, see [IFileSaveDialog](http://msdn.microsoft.com/library/windows/desktop/bb775688).
### Example
This example retrieves the internal COM object. To run this code example, you must compile it under [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)].
[!code-cpp[NVC_MFC_CFileDialog#3](../../mfc/reference/codesnippet/cpp/cfiledialog-class_6.cpp)]
## <a name="cfiledialog__getnextpathname"></a> CFileDialog::GetNextPathName
Call this function to retrieve the next filename from the group selected in the dialog box.
```
CString GetNextPathName(POSITION& pos) const;
```
### Parameters
`pos`
A reference to a **POSITION** value returned by a previous `GetNextPathName` or `GetStartPosition` function call. **NULL** if the end of the list has been reached.
### Return Value
The full path of the file.
### Remarks
The path of the filename includes the file's title plus the entire directory path. For example, `GetNextPathName` will return "C:\FILES\TEXT.DAT" for the file C:\FILES\TEXT.DAT. You can use `GetNextPathName` in a forward iteration loop if you establish the initial position with a call to `GetStartPosition`.
If the selection consists of only one file, that file name will be returned.
## <a name="cfiledialog__getofn"></a> CFileDialog::GetOFN
Retrieves the associated **OPENFILENAME** structure.
```
const OPENFILENAME& GetOFN() const;
OPENFILENAME& GetOFN();
```
### Return Value
An [OPENFILENAME](http://msdn.microsoft.com/library/windows/desktop/ms646839) structure.
### Remarks
Use the second version of this function to initialize the appearance of a **File Open** or **File Save As** dialog box after it is constructed but before it is displayed with the `DoModal` member function. For example, you can set the **lpstrTitle** member of **m_ofn** to the caption you want the dialog box to have.
## <a name="cfiledialog__getpathname"></a> CFileDialog::GetPathName
Call this function to retrieve the full path of the file entered in the dialog box.
```
CString GetPathName() const;
```
### Return Value
The full path of the file.
### Remarks
The path of the filename includes the file's title plus the entire directory path. For example, `GetPathName` will return "C:\FILES\TEXT.DAT" for the file C:\FILES\TEXT.DAT.
If `m_ofn.Flags` has the `OFN_ALLOWMULTISELECT` flag set, this string contains a sequence of null-teminated strings, with the first string being the directory path of the file group selected, followed by the names of all files selected by the user. For this reason, use the [GetStartPosition](#cfiledialog__getstartposition) and [GetNextPathName](#cfiledialog__getnextpathname) member functions to retrieve the next file name in the list.
### Example
See the example for [CFileDialog::DoModal](#cfiledialog__domodal).
## <a name="cfiledialog__getreadonlypref"></a> CFileDialog::GetReadOnlyPref
Call this function to determine whether the Read Only check box has been selected in the Windows standard File Open and File Save As dialog boxes.
```
BOOL GetReadOnlyPref() const;
```
### Return Value
Non-zero if the Read Only check box in the dialog box is selected; otherwise 0.
### Remarks
You can hide the Read Only check box by setting the `OFN_HIDEREADONLY` style in the [CFileDialog](../../mfc/reference/cfiledialog-class.md) constructor.
> [!NOTE]
> [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)] style `CFileDialog` objects do not support this function. Attempting to use this function on a [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)] style `CFileDialog` will throw [CNotSupportedException](../../mfc/reference/cnotsupportedexception-class.md). See [CFileDialog Class](../../mfc/reference/cfiledialog-class.md) for more information.
## <a name="cfiledialog__getresult"></a> CFileDialog::GetResult
Retrieves the choice that the user made in the dialog.
```
IShellItem* GetResult() throw();
```
### Return Value
A pointer to an IShellItem that represents the user's choice.
### Remarks
## <a name="cfiledialog__getresults"></a> CFileDialog::GetResults
Retrieves the user's choices in a dialog that allows multiple selection.
```
IShellItemArray* GetResults() throw();
```
### Return Value
A pointer to an IShellItemArray through which the items selected in the dialog can be accessed.
### Remarks
## <a name="cfiledialog__getselectedcontrolitem"></a> CFileDialog::GetSelectedControlItem
Retrieves a particular item from the specified container control in the dialog.
```
HRESULT GetSelectedControlItem(
DWORD dwIDCtl,
DWORD& dwIDItem);
```
### Parameters
`dwIDCtl`
The ID of the container control.
`dwIDItem`
The ID of the item that the user selected in the control.
### Remarks
## <a name="cfiledialog__getstartposition"></a> CFileDialog::GetStartPosition
Call this member function to retrieve the position of the first file pathname in the list, if `m_ofn.Flags` has the `OFN_ALLOWMULTISELECT` flag set.
```
POSITION GetStartPosition() const;
```
### Return Value
A **POSITION** value that can be used for iteration; **NULL** if the list is empty.
## <a name="cfiledialog__hidecontrol"></a> CFileDialog::HideControl
Call this member function to hide the specified control in an Explorer-style Open or Save As common dialog box.
```
void HideControl(int nID);
```
### Parameters
`nID`
The ID of the control to hide.
### Remarks
The dialog box must have been created with the **OFN_EXPLORER** style; otherwise, the function will fail with an assertion.
## <a name="cfiledialog__ispickfoldersmode"></a> CFileDialog::IsPickFoldersMode
Determines if the current dialog is in folder picker mode.
```
BOOL IsPickFoldersMode() const;
```
### Return Value
`TRUE` if the dialog is in folder picker mode; otherwise `FALSE`.
### Remarks
## <a name="cfiledialog__m_ofn"></a> CFileDialog::m_ofn
`m_ofn` is a structure of type `OPENFILENAME`. The data in this structure represents the current state of the `CFileDialog`.
### Remarks
Use this structure to initialize the appearance of a **File Open** or **File Save As** dialog box after you construct it but before you display it with the [DoModal](#cfiledialog__domodal) method. For example, you can set the `lpstrTitle` member of `m_ofn` to the caption you want the dialog box to have.
With the [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)] style of [CFileDialog](../../mfc/reference/cfiledialog-class.md), `m_ofn` is not guaranteed to always match the state of the dialog box. It is synchronized with the dialog box in earlier versions of Windows. See [CFileDialog::ApplyOFNToShellDialog](#cfiledialog__applyofntoshelldialog) and [CFileDialog::UpdateOFNFromShellDialog](#cfiledialog__updateofnfromshelldialog) for more information about synchronizing the `m_ofn` structure and the `CFileDialog` state under [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)].
[!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)] style file dialogs do not support certain members and flags of the `CFileDialog`. As a result, these will have no effect.
The following is a list of the members that are not supported by [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)]:
- `lpstrCustomFilter`
- `lpstrInitialDir`
- `lCustData`
- `lpfnHook`
- `lpTemplateName`
The following flags are not supported and therefore have no effect when you use the [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)] style of `CFileDialog`:
- OFN_ENABLEHOOK
- OFN_ENABLEINCLUDENOTIFY
- OFN_ENABLETEMPLATE
- OFN_ENABLETEMPLATEHANDLE
- OFN_EXPLORER
- OFN_EXTENSIONDIFFERENT
- OFN_HIDEREADONLY
- OFN_LONGNAMES - effectively always on in [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)]
- OFN_NOLONGNAMES - effectively always off in [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)]
- OFN_NONETWORKBUTTON - effectively always on in [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)]
- OFN_READONLY
- OFN_SHOWHELP
For more information about this structure, see the [OPENFILENAME](http://msdn.microsoft.com/library/windows/desktop/ms646839) structure in the [!INCLUDE[winSDK](../../atl/includes/winsdk_md.md)]. For more information about the different behavior of the `CFileDialog` under [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)], see [CFileDialog Class](../../mfc/reference/cfiledialog-class.md).
## <a name="cfiledialog__makeprominent"></a> CFileDialog::MakeProminent
Places a control in the dialog so that it stands out compared to other controls.
```
HRESULT MakeProminent(DWORD dwIDCtl);
```
### Parameters
`dwIDCtl`
The ID of the control.
### Remarks
## <a name="cfiledialog__onbuttonclicked"></a> CFileDialog::OnButtonClicked
Called when the button is clicked.
```
virtual void OnButtonClicked(DWORD dwIDCtl);
```
### Parameters
`dwIDCtl`
The ID of the button.
### Remarks
## <a name="cfiledialog__oncheckbuttontoggled"></a> CFileDialog::OnCheckButtonToggled
Called when the check box is checked or unchecked.
```
virtual void OnCheckButtonToggled(
DWORD dwIDCtl,
BOOL bChecked);
```
### Parameters
`dwIDCtl`
The ID of the check box.
`bChecked`
Checked or unchecked.
### Remarks
## <a name="cfiledialog__oncontrolactivating"></a> CFileDialog::OnControlActivating
Called when the control is activated.
```
virtual void OnControlActivating(DWORD dwIDCtl);
```
### Parameters
`dwIDCtl`
The ID of the control.
### Remarks
## <a name="cfiledialog__onfilenamechange"></a> CFileDialog::OnFileNameChange
Override this method if you want to handle the `WM_NOTIFY``CDN_SELCHANGE` message.
```
virtual void OnFileNameChange();
```
### Remarks
The system sends the `CDN_SELCHANGE` message when the user selects a new file or folder in the file list of the **Open** or **Save As** dialog box. Override this method if you want to perform any actions in response to this message.
The system sends this message only if the dialog box was created with the OFN_EXPLORER flag turned on. For more information about the notification, see [CDN_SELCHANGE](http://msdn.microsoft.com/library/windows/desktop/ms646865). For information about the OFN_EXPLORER flag, see the [OPENFILENAME](http://msdn.microsoft.com/library/windows/desktop/ms646839) structure and [Open and Save As Dialog Boxes](http://msdn.microsoft.com/library/windows/desktop/ms646960).
## <a name="cfiledialog__onfilenameok"></a> CFileDialog::OnFileNameOK
Override this function only if you want to provide custom validation of filenames that are entered into a common file dialog box.
```
virtual BOOL OnFileNameOK();
```
### Return Value
1 if the filename is not a valid filename; otherwise 0.
### Remarks
This function allows you to reject a filename for any application-specific reason. Normally, you do not need to use this function because the framework provides default validation of filenames and displays a message box if an invalid filename is entered.
If 1 is returned, the dialog box will remain displayed for the user to enter another filename. The dialog procedure dismisses the dialog if the return is 0. Other nonzero return values are currently reserved and should not be used.
## <a name="cfiledialog__onfolderchange"></a> CFileDialog::OnFolderChange
Override this function to handle the **WM_NOTIFYCDN_FOLDERCHANGE** message.
```
virtual void OnFolderChange();
```
### Remarks
The notification message is sent when a new folder is opened in the Open or Save As dialog box.
Notification is sent only if the dialog box was created with the OFN_EXPLORER style. For more information about the notification, see [CDN_FOLDERCHANGE](http://msdn.microsoft.com/library/windows/desktop/ms646859). For information about the OFN_EXPLORER style, see the [OPENFILENAME](http://msdn.microsoft.com/library/windows/desktop/ms646839) structure and [Open and Save As Dialog Boxes](http://msdn.microsoft.com/library/windows/desktop/ms646960).
## <a name="cfiledialog__oninitdone"></a> CFileDialog::OnInitDone
Override this function to handle the `WM_NOTIFY``CDN_INITDONE` message.
```
virtual void OnInitDone();
```
### Remarks
The system sends this notification message when the system has finished arranging controls in the **Open** or **Save As** dialog box to make room for the controls of the child dialog box.
The system sends this only if the dialog box was created with the OFN_EXPLORER style. For more information about the notification, see [CDN_INITDONE](http://msdn.microsoft.com/library/windows/desktop/ms646863). For information about the OFN_EXPLORER style, see the [OPENFILENAME](http://msdn.microsoft.com/library/windows/desktop/ms646839) structure and [Open and Save As Dialog Boxes](http://msdn.microsoft.com/library/windows/desktop/ms646960).
> [!NOTE]
> [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)] style file dialogs do not support this function. Attempting to use this function on a [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)] style file dialog will throw [CNotSupportedException](../../mfc/reference/cnotsupportedexception-class.md). See [CFileDialog Class](../../mfc/reference/cfiledialog-class.md) for more information.
## <a name="cfiledialog__onitemselected"></a> CFileDialog::OnItemSelected
Called when the container item is selected.
```
virtual void OnItemSelected(
DWORD dwIDCtl,
DWORD dwIDItem);
```
### Parameters
`dwIDCtl`
The ID of the container control.
`dwIDItem`
The ID of the item.
### Remarks
## <a name="cfiledialog__onlbselchangednotify"></a> CFileDialog::OnLBSelChangedNotify
This function is called whenever the current selection in a list box is about to change.
```
virtual void OnLBSelChangedNotify(
UINT nIDBox,
UINT iCurSel,
UINT nCode);
```
### Parameters
*nIDBox*
The ID of the list box or combo box in which the selection occurred.
`iCurSel`
The index of the current selection.
`nCode`
The control notification code. This parameter must have one of the following values:
- **CD_LBSELCHANGE** Specifies `iCurSel` is the selected item in a single-selection list box.
- **CD_LBSELSUB** Specifies that `iCurSel` is no longer selected in a multiselection list box.
- **CD_LBSELADD** Specifies that `iCurSel` is selected in a multiselection list box.
- **CD_LBSELNOITEMS** Specifies that no selection exists in a multiselection list box.
### Remarks
Override this function to provide custom handling of selection changes in the list box. For example, you can use this function to display the access rights or date-last-modified of each file the user selects.
## <a name="cfiledialog__onshareviolation"></a> CFileDialog::OnShareViolation
Override this function to provide custom handling of share violations.
```
virtual UINT OnShareViolation(LPCTSTR lpszPathName);
```
### Parameters
`lpszPathName`
The path of the file on which the share violation occurred.
### Return Value
One of the following values:
- **OFN_SHAREFALLTHROUGH** The filename is returned from the dialog box.
- **OFN_SHARENOWARN** No further action needs to be taken.
- **OFN_SHAREWARN** The user receives the standard warning message for this error.
### Remarks
Normally, you do not need to use this function because the framework provides default checking of share violations and displays a message box if a share violation occurs.
If you want to disable share violation checking, use the bitwise OR operator to combine the flag **OFN_SHAREAWARE** with `m_ofn.Flags`.
## <a name="cfiledialog__ontypechange"></a> CFileDialog::OnTypeChange
Override this function to handle the **WM_NOTIFYCDN_TYPECHANGE** message.
```
virtual void OnTypeChange();
```
### Remarks
The notification message is sent when the user selects a new file type from the list of file types in the Open or Save As dialog box.
Notification is sent only if the dialog box was created with the OFN_EXPLORER style. For more information about the notification, see [CDN_TYPECHANGE](http://msdn.microsoft.com/library/windows/desktop/ms646868). For information about the OFN_EXPLORER style, see the [OPENFILENAME](http://msdn.microsoft.com/library/windows/desktop/ms646839) structure and [Open and Save As Dialog Boxes](http://msdn.microsoft.com/library/windows/desktop/ms646960).
## <a name="cfiledialog__removecontrolitem"></a> CFileDialog::RemoveControlItem
Removes an item from a container control in the dialog.
```
HRESULT RemoveControlItem(
DWORD dwIDCtl,
DWORD dwIDItem);
```
### Parameters
`dwIDCtl`
The ID of the container control to remove the item from.
`dwIDItem`
The ID of the item.
### Remarks
## <a name="cfiledialog__setcheckbuttonstate"></a> CFileDialog::SetCheckButtonState
Sets the current state of a check button (check box) in the dialog.
```
HRESULT SetCheckButtonState(
DWORD dwIDCtl,
BOOL bChecked);
```
### Parameters
`dwIDCtl`
The ID of the check box.
`bChecked`
The state of the check box. `TRUE` indicates checked; `FALSE` indicates Unchecked.
### Remarks
## <a name="cfiledialog__setcontrolitemstate"></a> CFileDialog::SetControlItemState
Sets the current state of an item in a container control found in the dialog.
```
HRESULT SetControlItemState(
DWORD dwIDCtl,
DWORD dwIDItem,
CDCONTROLSTATEF dwState);
```
### Parameters
`dwIDCtl`
The ID of the container control.
`dwIDItem`
The ID of the item.
`dwState`
One or more values from the CDCONTROLSTATE enumeration that indicate the new state of the control.
### Remarks
## <a name="cfiledialog__setcontrolitemtext"></a> CFileDialog::SetControlItemText
Sets the text of a control item. For example, the text that accompanies a radio button or an item in a menu.
```
HRESULT SetControlItemText(
DWORD dwIDCtl,
DWORD dwIDItem,
const CString& strLabel);
```
### Parameters
`dwIDCtl`
The ID of the container control.
`dwIDItem`
The ID of the item.
`strLabel`
Item's text.
### Remarks
## <a name="cfiledialog__setcontrollabel"></a> CFileDialog::SetControlLabel
Sets the text associated with a control, such as button text or an edit box label.
```
HRESULT SetControlLabel(
DWORD dwIDCtl,
const CString& strLabel);
```
### Parameters
`dwIDCtl`
The ID of the control.
`strLabel`
The control name.
### Remarks
## <a name="cfiledialog__setcontrolstate"></a> CFileDialog::SetControlState
Sets the current visibility and enabled states of a given control.
```
HRESULT SetControlState(
DWORD dwIDCtl,
CDCONTROLSTATEF dwState);
```
### Parameters
`dwIDCtl`
The ID of the control.
`dwState`
One or more values from the CDCONTROLSTATE enumeration that indicate the current state of the control.
### Remarks
## <a name="cfiledialog__setcontroltext"></a> CFileDialog::SetControlText
Call this method to set the text for the specified control in an Explorer-style **Open** or **Save As** dialog box.
```
void SetControlText(
int nID,
LPCSTR lpsz);
void SetControlText(
int nID,
const wchar_t *lpsz);
```
### Parameters
[in] `nID`
The ID of the control for which to set the text.
[in] `lpsz`
A pointer to the string that contains the text to set for the control.
### Remarks
Both versions of this function are valid for applications that use Unicode. However, only the version with the LPCSTR type is valid for applications that use [!INCLUDE[vcpransi](../../atl-mfc-shared/reference/includes/vcpransi_md.md)].
To use this method, you must create the dialog box with the OFN_EXPLORER style. Otherwise, the function will fail with an assertion.
## <a name="cfiledialog__setdefext"></a> CFileDialog::SetDefExt
Call this function to set the default file name extension for an Explorer-style Open or Save As common dialog box.
```
void SetDefExt(LPCSTR lpsz);
```
### Parameters
`lpsz`
A pointer to a string containing the default extension to use for the dialog box object. This string must not contain a period (.).
### Remarks
The dialog box must have been created with the **OFN_EXPLORER** style; otherwise, the function will fail with an assertion.
## <a name="cfiledialog__seteditboxtext"></a> CFileDialog::SetEditBoxText
Sets the current text in an edit box control.
```
HRESULT SetEditBoxText(
DWORD dwIDCtl,
const CString& strText);
```
### Parameters
`dwIDCtl`
The ID of the edit box.
`strText`
The text value.
### Remarks
## <a name="cfiledialog__setproperties"></a> CFileDialog::SetProperties
Provides a property store that defines the default values to be used for the item being saved.
```
BOOL SetProperties(LPCWSTR lpszPropList);
```
### Parameters
`lpszPropList`
A list of predefined properties separated by ";". For a list of the flags, see the `Flags` section of [OPENFILENAME](http://msdn.microsoft.com/en-us/8cecfd45-f7c1-4f8d-81a0-4e7fecc3b104).
### Remarks
## <a name="cfiledialog__setselectedcontrolitem"></a> CFileDialog::SetSelectedControlItem
Sets the selected state of a particular item in an option button group or a combo box found in the dialog.
```
HRESULT SetSelectedControlItem(
DWORD dwIDCtl,
DWORD dwIDItem);
```
### Parameters
`dwIDCtl`
The ID of the container control.
`dwIDItem`
The ID of the item that the user selected in the control.
### Remarks
## <a name="cfiledialog__settemplate"></a> CFileDialog::SetTemplate
Sets the dialog box template for the [CFileDialog](../../mfc/reference/cfiledialog-class.md) object.
```
void SetTemplate(
UINT nWin3ID,
UINT nWin4ID);
void SetTemplate(
LPCTSTR lpWin3ID,
LPCTSTR lpWin4ID);
```
### Parameters
[in] `nWin3ID`
Contains the ID number of the template resource for the non-Explorer `CFileDialog` object. This template is only used on Windows NT 3.51 or when the OFN_EXPLORER style is not present.
[in] `nWin4ID`
Contains the ID number of the template resource for the Explorer `CFileDialog` object. This template is used only on [!INCLUDE[WinNt4Family](../../mfc/reference/includes/winnt4family_md.md)] and later versions, Windows 95 and later versions, or when the OFN_EXPLORER style is present.
[in] `lpWin3ID`
Contains the name of the template resource for the non-Explorer `CFileDialog` object. This template is only used on Windows NT 3.51 or when the OFN_EXPLORER style is not present.
[in] `lpWin4ID`
Contains the name of the template resource of the Explorer `CFileDialog` object. This template is used only on [!INCLUDE[WinNt4Family](../../mfc/reference/includes/winnt4family_md.md)] and later versions, Windows 95 and later versions, or when the OFN_EXPLORER style is present.
### Remarks
The system will use only one of the specified templates. The system determines which template to use based on the presence of the OFN_EXPLORER style and the operating system that the application is running on. By specifying both a non-Explorer and Explorer-style template, it is easy to support Windows NT 3.51, [!INCLUDE[WinNt4Family](../../mfc/reference/includes/winnt4family_md.md)] and later versions, and Windows 95 and later versions.
> [!NOTE]
> [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)] style file dialog boxes do not support this function. Attempting to use this function on a [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)] style file dialog box will throw [CNotSupportedException](../../mfc/reference/cnotsupportedexception-class.md). See [CFileDialog Class](../../mfc/reference/cfiledialog-class.md) for more information. An alternative is to use a customized dialog. For more information about using a custom `CFileDialog`, see [IFileDialogCustomize](http://msdn.microsoft.com/library/windows/desktop/bb775912).
## <a name="cfiledialog__startvisualgroup"></a> CFileDialog::StartVisualGroup
Declares a visual group in the dialog. Subsequent calls to any "add" method add those elements to this group.
```
HRESULT StartVisualGroup(
DWORD dwIDCtl,
const CString& strLabel);
```
### Parameters
`dwIDCtl`
The ID of the visual group.
`strLabel`
The group name.
### Remarks
## <a name="cfiledialog__updateofnfromshelldialog"></a> CFileDialog::UpdateOFNFromShellDialog
Updates the `m_ofn` data structure of the [CFileDialog](../../mfc/reference/cfiledialog-class.md) based on the current state of the internal object.
```
void UpdateOFNFromShellDialog();
```
### Remarks
In versions of Windows before [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)], the member [OPENFILENAME](https://msdn.microsoft.com/library/ms911906.aspx) data structure was continuously synchronized with the state of the `CFileDialog`. Any changes to the [m_ofn](#cfiledialog__m_ofn) member variable directly affected the state of the dialog box. Also, any changes to the state of the dialog immediately updated the m_ofn member variable.
In [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)], the `m_ofn` data structure is not automatically updated. To guarantee the accuracy of the data in the `m_ofn` member variable, you should call the `UpdateOFNFromShellDialog` function before accessing the data. Windows calls this function automatically during the processing of [IFileDialog::OnFileOK](http://msdn.microsoft.com/library/windows/desktop/bb775879).
For more information about how to use the `CFileDialog` class under [!INCLUDE[wiprlhext](../../c-runtime-library/reference/includes/wiprlhext_md.md)], see [CFileDialog Class](../../mfc/reference/cfiledialog-class.md).
### Example
This example updates the `CFileDialog` before displaying it. Before updating the `m_ofn` member variable, we need to synchronize it to the current state of the dialog box.
[!code-cpp[NVC_MFC_CFileDialog#1](../../mfc/reference/codesnippet/cpp/cfiledialog-class_7.cpp)]
## See Also
[CCommonDialog Class](../../mfc/reference/ccommondialog-class.md)
[Hierarchy Chart](../../mfc/hierarchy-chart.md)
<!--HONumber=Jan17_HO2-->
| 47.591231 | 811 | 0.735296 | eng_Latn | 0.873622 |
d3cee249cb5396712771424346219127bb5ac97a | 1,655 | md | Markdown | README.md | nrkno/svg-to-js | 3c5049d46eefb1089dcf1183b904599b89115604 | [
"MIT"
] | 3 | 2019-03-25T07:37:51.000Z | 2021-01-20T17:48:41.000Z | README.md | nrkno/svg-to-js | 3c5049d46eefb1089dcf1183b904599b89115604 | [
"MIT"
] | 10 | 2017-09-15T18:31:13.000Z | 2022-01-06T07:20:12.000Z | README.md | nrkno/svg-to-js | 3c5049d46eefb1089dcf1183b904599b89115604 | [
"MIT"
] | 4 | 2020-05-08T13:30:56.000Z | 2021-08-28T10:56:28.000Z | # @nrk/svg-to-js
> Module for concatenating SVG files into JavaScript.
##### Why load icons as JavaScript?
SVG symbols are great for styling and accessibility, but can not load cross domain, or from external file and in IE (9,10,11). Javascript provides us a cacheable, cross-domain method to load the icons, without adding extra overhead to each html-file.
## Installation
```sh
npm install @nrk/svg-to-js
```
## Usage
```js
import svgtojs from '@nrk/svg-to-js'
const options = {
input: 'src/' // Required. Folder with SVG files
banner: 'Copyright NRK', // Optional. Text to add as comment in top of file
scale: 1, // Optional. Scale factor for width/height attributes in em
// svgtojs always returns Object of outputs,
// but can optionally also write files:
esm: 'core-icons.esm.js', // ES module for bundlers exposing `export const iconName = '<svg...'`
cjs: 'core-icons.js', // CommonJS for Node exposing `module.exports = { iconName: '<svg...' }`
esmx: 'core-icons.esm.jsx', // JSX ES module, exposing React components with `export`
cjsx: 'core-icons.cjs.jsx', // JSX CommonJS, exposing React components with `module.exports`
iife: 'core-icons.min.js' // Self executing <script>, exposing all icons as symbols on page,
dts: 'core-icons.d.ts', // Exposes typescript definitions with `export declare const`
dtsx: 'core-icons-jsx.d.ts' // Exposes typescript definitions for JSX with `export declare const`
}
svgtojs(options)
// => Returns {
// esm: String,
// cjs: String,
// esmx: String,
// cjsx: String,
// iife: String,
// dts: String,
// dtsx: String
//}
```
| 36.777778 | 250 | 0.676737 | eng_Latn | 0.708686 |
d3d02eb0a9196fa0c049c37fd1ac8e629a388b5b | 25 | md | Markdown | README.md | Sakura1221/QtStudy | 34d24affada2a10c901fb9571473a33c871201fa | [
"MIT"
] | 4 | 2021-06-17T02:58:18.000Z | 2021-11-09T11:40:37.000Z | README.md | Sakura1221/QtStudy | 34d24affada2a10c901fb9571473a33c871201fa | [
"MIT"
] | null | null | null | README.md | Sakura1221/QtStudy | 34d24affada2a10c901fb9571473a33c871201fa | [
"MIT"
] | 1 | 2021-06-26T07:42:20.000Z | 2021-06-26T07:42:20.000Z | # QtStudy
Qt Study Notes
| 8.333333 | 14 | 0.76 | kor_Hang | 0.994113 |
d3d05c572ad4576c36f84ddb499a5160ddd37d2d | 59 | md | Markdown | History.md | DemocracyOS/corner-ribbon | 7f6e7cc093a3f7dcb05fc7780cf4c9b6336e47e9 | [
"MIT"
] | 4 | 2015-03-16T00:00:13.000Z | 2019-04-20T22:09:49.000Z | History.md | DemocracyOS/corner-ribbon | 7f6e7cc093a3f7dcb05fc7780cf4c9b6336e47e9 | [
"MIT"
] | null | null | null | History.md | DemocracyOS/corner-ribbon | 7f6e7cc093a3f7dcb05fc7780cf4c9b6336e47e9 | [
"MIT"
] | null | null | null |
0.0.1 / 2015-03-03
==================
* Initial commit
| 9.833333 | 18 | 0.40678 | oci_Latn | 0.671977 |
d3d0bd65723d5926c0a212f182a554ba6c330079 | 1,268 | md | Markdown | docs/node/api-linter/executors/eslint.md | duncan-G/nx | 7372920befe6c2a403d9269e454600b058fa2399 | [
"MIT"
] | 3 | 2020-09-18T08:40:33.000Z | 2021-11-09T10:50:59.000Z | docs/node/api-linter/executors/eslint.md | duncan-G/nx | 7372920befe6c2a403d9269e454600b058fa2399 | [
"MIT"
] | 1 | 2021-02-15T01:13:12.000Z | 2021-03-29T13:59:29.000Z | docs/node/api-linter/executors/eslint.md | duncan-G/nx | 7372920befe6c2a403d9269e454600b058fa2399 | [
"MIT"
] | null | null | null | # eslint
Run ESLint on a project
Properties can be configured in workspace.json when defining the executor, or when invoking it.
Read more about how to use executors and the CLI here: https://nx.dev/node/guides/cli.
## Properties
### cache
Default: `false`
Type: `boolean`
Only check changed files.
### cacheLocation
Type: `string`
Path to the cache file or directory.
### eslintConfig
Type: `string`
The name of the ESLint configuration file.
### fix
Default: `false`
Type: `boolean`
Fixes linting errors (may overwrite linted files).
### force
Default: `false`
Type: `boolean`
Succeeds even if there was linting errors.
### format
Default: `stylish`
Type: `string`
ESLint Output formatter (https://eslint.org/docs/user-guide/formatters).
### ignorePath
Type: `string`
The path of the .eslintignore file.
### lintFilePatterns
Type: `array`
One or more files/dirs/globs to pass directly to ESLint's lintFiles() method.
### maxWarnings
Default: `-1`
Type: `number`
Number of warnings to trigger nonzero exit code - default: -1
### outputFile
Type: `string`
File to write report to.
### quiet
Default: `false`
Type: `boolean`
Report errors only - default: false
### silent
Default: `false`
Type: `boolean`
Hide output text.
| 13.347368 | 95 | 0.713722 | eng_Latn | 0.901509 |
d3d18119b6ac4e4c86b78a90e0ef07b19a414da8 | 3,224 | md | Markdown | packages/dandi/core/logging/README.md | just-dandi/dandi | 60cbc10b76a7151d899b924188f7267cf87c8de0 | [
"MIT"
] | 5 | 2019-09-30T14:18:38.000Z | 2021-04-06T22:01:40.000Z | packages/dandi/core/logging/README.md | just-dandi/dandi | 60cbc10b76a7151d899b924188f7267cf87c8de0 | [
"MIT"
] | 57 | 2019-02-19T23:36:16.000Z | 2022-01-22T10:21:00.000Z | packages/dandi/core/logging/README.md | just-dandi/dandi | 60cbc10b76a7151d899b924188f7267cf87c8de0 | [
"MIT"
] | 1 | 2018-10-18T18:14:44.000Z | 2018-10-18T18:14:44.000Z | # @dandi/core/logging
Dandi's splits the responsibilities of logging into two primary parts:
- `Logger` is the primary interface that developers will interact with - implementations of `Logger` are used to generate
the log entries themselves, and can draw in contextual metadata about where they are called from. An app will have a
single `Logger` instance. If no provider for `Logger` is available, the app will use `NoopLogger` by default.
- `LogListener` implementations receive the log data generated by the `Logger`. What they do with that data depends on
the implementation - `ConsoleLogListener`, for example, formats the log data and sends it to the program's `console`
output. Other implementations could store the data locally, or transmit it to a remote API. An app may use any number
of `LogListener` implementations simultaneously.
By default, this pattern is implemented using an RxJS `Subject`. The `Subject` instance is defined using the `LogStream`
injection token. The `Logger` instance calls `next()` on the `LogStream` for each log entry. `LogListener` instances
subscribe to the `LogStream` as an `Observable`.
_Note:_ The DI system in `@dandi/core` uses `Logger` internally, which is why `Logger` is part of the root `@dandi/core`
package and not `@dandi/core/logging`.
## Implementations
### Logger
#### ContexualLogger
- **Package:** [@dandi/core/logging](.)
- **Module:** `LoggingModule` in [@dandi/core/logging](.)
- Includes a reference the consuming service in the logging data
```typescript
// main.ts
import { DandiApplication } from '@dandi/core'
import { LoggingModule } from '@dandi/core/logging' // includes ContextualLogger
const container = new DandiApplication({
providers: [
LoggingModule,
/* other providers */
],
})
// my-service.ts
import { Inject, Injectable, Logger } from '@dandi/core'
@Injectable()
export class MyService {
constructor(@Inject(Logger) private logger: Logger) {
this.logger.debug('Constructed!')
}
}
```
In the above example, when the instances are created, the `ContextualLogger` instance uses the `InjectionContext` token
provided by the Dandi DI system to receive a reference to the instance of `MyService` that caused it to be created. It
then includes that reference when creating log entries like the call to `debug()`.
#### NoopLogger
- **Package:** [@dandi/core](.)
- **Module:** n/a - used as a fallback by `@dandi/core`
- As the name suggests, `NoopLogger` does not generate log entries
When no `Logger` implementation is configured, `NoopLogger` is used by default.
#### ConsoleLogListener
- **Package:** [@dandi/core/logging](.)
- **Module:** n/a
- Outputs formatted log data to the environment's `console`
Include `ConsoleLogListener` by calling the `use` method on `LoggingModule`.
```typescript
import { DandiApplication } from '@dandi/core'
import { ConsoleLogListener, LoggingModule } from '@dandi/core/logging'
const container = new DandiApplication({
providers: [
LoggingModule.use(ConsoleLogListener),
/* other providers */
],
})
```
##### Formatting
`ConsoleLogListener` can be customized to format the log data as desired.
TODO
## API Documentation
TODO
### Logger
TODO
| 32.565657 | 121 | 0.737283 | eng_Latn | 0.977073 |
d3d18e50a6cbbca5f48b0b578f6b6196c96cda68 | 1,664 | md | Markdown | problems/substrings-that-begin-and-end-with-the-same-letter/README.md | openset/leetcode | caa9a98aca28c4de5022a0b420dce7edf5150034 | [
"MIT"
] | 198 | 2018-12-14T11:11:21.000Z | 2021-11-22T17:31:48.000Z | problems/substrings-that-begin-and-end-with-the-same-letter/README.md | openset/leetcode | caa9a98aca28c4de5022a0b420dce7edf5150034 | [
"MIT"
] | 779 | 2018-12-15T11:04:06.000Z | 2021-11-19T08:42:40.000Z | problems/substrings-that-begin-and-end-with-the-same-letter/README.md | openset/leetcode | caa9a98aca28c4de5022a0b420dce7edf5150034 | [
"MIT"
] | 85 | 2019-01-10T02:20:04.000Z | 2021-11-26T08:01:42.000Z | <!--|This file generated by command(leetcode description); DO NOT EDIT. |-->
<!--+----------------------------------------------------------------------+-->
<!--|@author awesee <openset.wang@gmail.com> |-->
<!--|@link https://github.com/awesee |-->
<!--|@home https://github.com/awesee/leetcode |-->
<!--+----------------------------------------------------------------------+-->
[< Previous](../the-number-of-rich-customers "The Number of Rich Customers")
[Next >](../drop-type-1-orders-for-customers-with-type-0-orders "Drop Type 1 Orders for Customers With Type 0 Orders")
## [2083. Substrings That Begin and End With the Same Letter (Medium)](https://leetcode.com/problems/substrings-that-begin-and-end-with-the-same-letter "")
### Hints
<details>
<summary>Hint 1</summary>
In the string "abacad", the letter "a" appears 3 times. How many substrings begin with the first "a" and end with any "a"?
</details>
<details>
<summary>Hint 2</summary>
There are 3 substrings ("a", "aba", and "abaca"). How many substrings begin with the second "a" and end with any "a"? How about the third?
</details>
<details>
<summary>Hint 3</summary>
2 substrings begin with the second "a" ("a", and "aca") and 1 substring begins with the third "a" ("a").
</details>
<details>
<summary>Hint 4</summary>
There is a total of 3 + 2 + 1 = 6 substrings that begin and end with "a".
</details>
<details>
<summary>Hint 5</summary>
If a character appears i times in the string, there are i * (i + 1) / 2 substrings that begin and end with that character.
</details>
| 40.585366 | 155 | 0.581731 | eng_Latn | 0.94604 |
d3d311001367422c74f65ab15aeb347e4ff690ad | 543 | md | Markdown | RuboCop/Lint-ReturnInVoidContext.md | r3yn0ld4/docs-for-code-review-tools | a1590fce3b30891679373ec284787b227b21df05 | [
"MIT"
] | 4 | 2019-07-17T18:16:06.000Z | 2021-03-28T23:53:10.000Z | RuboCop/Lint-ReturnInVoidContext.md | Acidburn0zzz/docs-for-code-review-tools | 9659492c76b988e14363dced6c2ab5f86fcdd6e0 | [
"MIT"
] | null | null | null | RuboCop/Lint-ReturnInVoidContext.md | Acidburn0zzz/docs-for-code-review-tools | 9659492c76b988e14363dced6c2ab5f86fcdd6e0 | [
"MIT"
] | 5 | 2018-09-29T17:02:14.000Z | 2021-12-26T16:53:04.000Z | Pattern: `return` in void context
Issue: -
## Description
This rule checks for the use of a `return `with a value in a context
where the value will be ignored (initialize and setter methods).
## Examples
```ruby
# bad
def initialize
foo
return :qux if bar?
baz
end
def foo=(bar)
return 42
end
```
```ruby
# good
def initialize
foo
return if bar?
baz
end
def foo=(bar)
return
end
```
## Further Reading
* [RuboCop - Lint/ReturnInVoidContext](https://rubocop.readthedocs.io/en/latest/cops_lint/#lintreturninvoidcontext)
| 13.575 | 115 | 0.709024 | eng_Latn | 0.826997 |
d3d36256865dc89c40f24a67a939e2b049718de7 | 63 | md | Markdown | ChangeLog.md | Cmdv/Haskell-Interview-Tests | 787bf5e07fdfd37f9eeb8c5a3570b99840d00d4c | [
"BSD-3-Clause"
] | 11 | 2019-08-29T10:04:49.000Z | 2022-02-23T16:53:17.000Z | ChangeLog.md | Cmdv/Haskell-Interview-Tests | 787bf5e07fdfd37f9eeb8c5a3570b99840d00d4c | [
"BSD-3-Clause"
] | null | null | null | ChangeLog.md | Cmdv/Haskell-Interview-Tests | 787bf5e07fdfd37f9eeb8c5a3570b99840d00d4c | [
"BSD-3-Clause"
] | null | null | null | # Changelog for Haskell-Interview-Tests
## Unreleased changes
| 15.75 | 39 | 0.793651 | eng_Latn | 0.934263 |
d3d3e88d01bf84f22b77c5c5f962b6895d4a6baa | 13,527 | md | Markdown | content/components/overlays/modals.md | scottanthonymurray/rivet-docs | 3210f797e708f4ea42d9c41e942b1de01d45d8d4 | [
"BSD-3-Clause"
] | null | null | null | content/components/overlays/modals.md | scottanthonymurray/rivet-docs | 3210f797e708f4ea42d9c41e942b1de01d45d8d4 | [
"BSD-3-Clause"
] | null | null | null | content/components/overlays/modals.md | scottanthonymurray/rivet-docs | 3210f797e708f4ea42d9c41e942b1de01d45d8d4 | [
"BSD-3-Clause"
] | null | null | null | ---
title: "Modals"
asOf: 1.0.0
description: "A modal is a smaller window that is displayed on top of the main application/site window. The main page is still visible, but the background is darkened to direct focus to the content of the modal window."
requiresJs: true
status: "Ready"
methods:
-
title: "Modal.init(context)"
description: |
- Initializes the `Modal` component
- Accepts an optional DOM element. If no element is provided in the argument it defaults to the `document` element.
- NOTE: the `init()` method is called automatically when `rivet.js` is loaded.
-
title: "Modal.destroy(context)"
description: |
- Destroys any currently initialized Modals and removes their event listeners.
- Accepts a optional DOM element. If no element is provided in the argument it defaults to the `document` element. **NOTE**: the optional `context` argument only needs to be passed into `.destroy()` if a DOM element was passed into the `.init()` method. If so, it must be the DOM element that was passed into `.init()` when the Modal was initialized.
-
title: "Modal.open(id, callback)"
description: |
- `id` - The unique id of the Modal. This corresponds to the value `data-modal-trigger`/`id` attributes of the modal you want to **open**. **NOTE**: In previous versions of Rivet, the `Modal.open()` method accepted a Modal DOM Element. The `.open()` method will still work if you pass it a DOM element (the modal element itself), but **this functionality will be deprecated in the next major version of Rivet**.
- `callback` - An optional callback function that is executed after the modal is opened.
-
title: "Modal.close(id, callback)"
description: |
- `id` - The unique id of the modal. This corresponds to the value `data-modal-trigger`/`id` attributes of the modal you want to **close**.
- `callback` - An optional callback function that is executed after the modal is opened.
- **NOTE**: In previous versions of Rivet, the `Modal.close()` method accepted a Modal DOM Element. The `.close()` method will still work if you pass it a DOM element (the Modal element itself), but **this functionality will be deprecated in the next major version of Rivet**.
-
title: "Modal.focusModal(id)"
description: |
Moves focus the currently active/open modal. This is a helper method that can be used to focus modals that have been opened programmatically via the `Modal.open()` method. It takes one argument, the unique id (String) of the modal you wan to move focus to. This method can be used as the callback to the `Modal.open()` method to move focus to the modal after it has been opened via your own scripts.
-
title: "Modal.focusTrigger(id)"
description: |
Moves focus to the trigger (`data-modal-trigger`) that opened the currently active modal, if it exists.
events:
-
title: "modalOpen"
description: |
Emitted when the Modal is opened (using the `Modal.open()` method, or the `data-modal-trigger` attribute). The value of the modal `id` attribute is also passed along via the custom event’s detail property and is available to use in your scripts as `event.detail.name()`
-
title: "modalClose"
description: |
Emitted when the Modal is closed (using the `Modal.close()` method, or the `data-modal-trigger` attribute). The value of the modal `id` attribute is also passed along via the custom event’s detail property and is available to use in your scripts as `event.detail.name()`
---
{{< alert variant="warning" title="Migrating to Rivet 2" >}}
This version of Rivet is deprecated. [View the modal documentation on the Rivet 2 website](https://v2.rivet.iu.edu/docs/components/modal/).
{{< /alert >}}
## Modal example
{{< example lang="html" >}}<button type="button" class="rvt-button" data-modal-trigger="modal-example-basic">Open modal example</button>
<div class="rvt-modal"
id="modal-example-basic"
role="dialog"
aria-labelledby="modal-example-title"
aria-hidden="true"
tabindex=-1>
<div class="rvt-modal__inner">
<header class="rvt-modal__header">
<h1 class="rvt-modal__title" id="modal-example-title">Modal title</h1>
</header>
<div class="rvt-modal__body">
<p>Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor <a href="#">incididunt ut labore</a> et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</p>
</div>
<div class="rvt-modal__controls">
<button type="button" class="rvt-button">OK</button>
<button type="button" class="rvt-button rvt-button--secondary" data-modal-close="modal-example-basic">Cancel</button>
</div>
<button type="button" class="rvt-button rvt-modal__close" data-modal-close="modal-example-basic">
<span class="rvt-sr-only">Close</span>
<svg aria-hidden="true" xmlns="http://www.w3.org/2000/svg" width="16" height="16" viewBox="0 0 16 16">
<path fill="currentColor" d="M9.41,8l5.29-5.29a1,1,0,0,0-1.41-1.41L8,6.59,2.71,1.29A1,1,0,0,0,1.29,2.71L6.59,8,1.29,13.29a1,1,0,1,0,1.41,1.41L8,9.41l5.29,5.29a1,1,0,0,0,1.41-1.41Z"/>
</svg>
</button>
</div>
</div>
{{< /example >}}
## When to use
- For single specific tasks related to a goal on the main page of the application
- To help users determine information needed in their main workflow e.g. calculating a number, looking up a code
## When to consider something else
- When you need to display an error message consider using an [alert]({{< relref "alerts.md" >}}) on the page in which the error occurred.
- When you need to display large amounts of information for multiple tasks consider using a dedicated page instead.
## Implementation notes
The modal component is made up of the following elements:
- `.rvt-modal` and `.rvt-modal__inner` - An overlay and inner container, which wraps all other elements
- `.rvt-modal__header` — A header with a title that is used to label the modal
- `.rvt-modal__body` — A modal body that holds the main content of the modal
- `.rvt-modal__controls` — An optional footer element that holds modal controls, like "Save" and "Cancel"
- `.rvt-modal__close` — An optional close button at the top of the modal
### Required elements
The only elements required in order for the modal to work are the `.rvt-modal`, `.rvt-modal__inner`, and `.rvt-modal__body`, but it is advisable to use the `.rvt-modal__header` element to help describe what the modal is use for. Likewise, the `.rvt-modal__controls` element provides an easy way to add additional actions to the modal like "Save" and "Close".
### Modal controls
The `.rvt-modal__controls` element provides a space to add additional controls like buttons. It is advisable to **stick to one or two buttons** action buttons in a modal. The primary action should **always appear as the left-most button** in the group with secondary actions, like "Cancel" appearing after.
### Modal set up
To use the modal component you'll need to do a few things. First, add the markup to your document.
{{< code lang="html" >}}<button type="button" class="rvt-button" data-modal-trigger="my-modal-id">Open the modal</button>
<div class="rvt-modal" id="my-modal-id">
modal markup here...
<button type="button" class="rvt-button rvt-button--plain rvt-modal__close" data-modal-close="my-modal-id">
button markup here...
</button>
</div>
{{< /code >}}
In the code above, `my-modal-id` should correspond to the `id` attribute on the the `.rvt-modal` container and the `data-modal-trigger` attribute on a `<button>` element that triggers the modal.
The `data-modal-close` attribute is used as a hook to close the modal. You can add the `data-modal-close` attribute to other buttons in the modal like a "**Cancel**" button if you need to allow users other options for closing the modal. The value of `data-modal-close` should be the same as the `id` attribute of the modal it closes.
Multiple modals can be placed on the same page, as long as each has a unique `id` and corresponding `data-modal-trigger` element.
## Modal dialog
We use the generic term "Modal" to mean any smaller window that is displayed on top of the main application, but there are some subtle differences between a modal and a dialog.
A modal dialog is similar to a regular modal except that **it requires the user to interact with it** before continuing any interaction with the main application. The user must select from the available actions in the dialog—they cannot disregard and simply close the window.
{{< example lang="html" >}}<button type="button" class="rvt-button" data-modal-trigger="modal-dialog-example">Open modal dialog</button>
<div class="rvt-modal"
id="modal-dialog-example"
role="dialog"
aria-labelledby="modal-dialog-title"
aria-hidden="true"
tabindex=-1
data-modal-dialog="true">
<div class="rvt-modal__inner">
<header class="rvt-modal__header">
<h1 class="rvt-modal__title" id="modal-dialog-title">Modal Dialog</h1>
</header>
<div class="rvt-modal__body">
<p>A modal dialog:</p>
<ul>
<li>Is not dismissible i.e. doesn't have an (X) button</li>
<li>Requires user input before they continue their work</li>
</ul>
</div>
<div class="rvt-modal__controls">
<button type="button" class="rvt-button">Yes</button>
<button type="button" class="rvt-button rvt-button--secondary" data-modal-close="modal-dialog-example">No, thanks</button>
</div>
</div>
</div>
{{< /example >}}
### When to use a dialog
- Confirmation dialogs are used to verify the action a user selected, especially when that action will result in the loss of data. For example, ‘All files in this folder will be deleted. Do you want to continue?’
- Provide the user with clarifying information before they continue with a task or action. For example, "A 10% fee will be charged to your account. Do you want to continue?"
### When to consider something else
- Do not use to second guess the users’ choice of actions when no destruction or loss of data will occur.
- When you need to create a focused space for users to complete a small subtask, use a regular modal instead.
## Accessibility notes
- When a modal is opened the modal itself receives focus, so that screen readers begin at the top of the modal content.
- When the modal is closed the focus should be returned to the button/trigger that was used to open the modal so that keyboard only users and those using assistive technologies do not lose their place in the document.
- A modal should trap focus inside of itself so that when a keyboard-only user navigates from the last focusable element in the modal it returns back to the first focusable element.
## Microcopy notes
Follow [UX Planet’s recommendations for modal text](https://uxplanet.org/best-practices-for-modals-overlays-dialog-windows-c00c66cddd8c):
- The button that launches the modal should clearly describe the action (“Submit feedback”)
- Use the launch button text as the modal title. This reminds the user what to do, within the context of the overall page.
## JavaScript API
If you use the appropriate data attribute/id combination in your markup, modals will work without the need for any additional JavaScript. But if you need to control the modal programmatically, there are a handful of methods from the Rivet modal’s API you can use:
{{< apidocs type="methods" >}}{{< /apidocs >}}
### Managing focus
When a modal is triggered using the default data attribute method via a click event on the modal trigger (`data-modal-trigger`), the modal script will store a reference to the element that triggered it, and return focus to that element when the modal is closed.
**Please note**: If you open the modal programmatically using `Modal.open()` based on some other event, it is your responsibility to return focus to the appropriate element after the modal is closed. The `.focusTrigger()` method can be combined with the `.close()` method's callback function to accomplish this.
{{< code lang="javascript" >}}Modal.close('my-modal-id', function() {
Modal.focusTrigger('my-modal-id');
});
{{< /code >}}
### Custom Events
The Rivet Modal also emits various custom events that you can listen for in your own scripts.
{{< apidocs type="events" >}}{{< /apidocs >}}
#### Custom event example
Note here that the `event.detail.name()` property of the `customEvent` object is a function that returns a String. Read more about custom events on the [MDN web docs](https://developer.mozilla.org/en-US/docs/Web/API/CustomEvent/CustomEvent).
{{< code lang="js" >}}// Listen for a custom "modalOpen" event
document.addEventListener('modalOpen', event => {
if (event.detail.name() === 'my-modal') {
alert('Hey, you opened the modal!')
}
// Maybe send some data via an AJAX request, etc...
}, false);
{{< /code >}}
| 65.033654 | 481 | 0.707991 | eng_Latn | 0.991778 |
d3d57e86d9fa30c94bb41f0e96948256a8d10397 | 7,909 | md | Markdown | k-distribution/k-tutorial/1_basic/06_ints_and_bools/README.md | vasil-sd/k | 8015ee7dde042a83d7f945d914c693e753bda73e | [
"BSD-3-Clause"
] | 23 | 2017-02-26T10:49:29.000Z | 2022-03-22T20:32:10.000Z | k-distribution/k-tutorial/1_basic/06_ints_and_bools/README.md | vasil-sd/k | 8015ee7dde042a83d7f945d914c693e753bda73e | [
"BSD-3-Clause"
] | 112 | 2016-01-20T16:23:47.000Z | 2022-03-31T21:54:59.000Z | k-distribution/k-tutorial/1_basic/06_ints_and_bools/README.md | vasil-sd/k | 8015ee7dde042a83d7f945d914c693e753bda73e | [
"BSD-3-Clause"
] | 6 | 2016-02-23T19:12:26.000Z | 2022-03-31T01:53:24.000Z | # Lesson 1.6: Integers and Booleans
The purpose of this lesson is to explain the two most basic types of builtin
sorts in K, the `Int` sort and the `Bool` sort, representing
**arbitrary-precision integers** and **Boolean algebra**.
## Builtin sorts in K
K provides definitions of some useful sorts in
[domains.md](../../../include/kframework/builtin/domains.md), found in the
`include/kframework/builtin` directory of the K installation. This file is
defined via a
[Literate programming](https://en.wikipedia.org/wiki/Literate_programming)
style that we will discuss in a future lesson. We will not cover all of the
sorts found there immediately, however, this lesson discusses some of the
details surrounding integers and Booleans, as well as providing information
about how to look up more detailed knowledge about builtin functions in K's
documentation.
## Booleans in K
The most basic builtin sort K provides is the `Bool` sort, representing
Boolean values (i.e., `true` and `false`). You have already seen how we were
able to create this type ourselves using K's parsing and disambiguation
features. However, in the vast majority of cases, we prefer instead to import
the version of Boolean algebra defined by K itself. Most simply, you can do
this by importing the module `BOOL` in your definition. For example
(`lesson-06-a.k`):
```k
module LESSON-06-A
imports BOOL
syntax Fruit ::= Blueberry() | Banana()
syntax Bool ::= isBlue(Fruit) [function]
rule isBlue(Blueberry()) => true
rule isBlue(Banana()) => false
endmodule
```
Here we have defined a simple **predicate**, i.e., a function returning a
Boolean value. We are now able to perform the usual Boolean operations of
and, or, and not over these values. For example (`lesson-06-b.k`):"
```k
module LESSON-06-B
imports BOOL
syntax Fruit ::= Blueberry() | Banana()
syntax Bool ::= isBlue(Fruit) [function]
rule isBlue(Blueberry()) => true
rule isBlue(Banana()) => false
syntax Bool ::= isYellow(Fruit) [function]
| isBlueOrYellow(Fruit) [function]
rule isYellow(Banana()) => true
rule isYellow(Blueberry()) => false
rule isBlueOrYellow(F) => isBlue(F) orBool isYellow(F)
endmodule
```
In the above example, Boolean **inclusive or** is performed via the `orBool`
function, which is defined in the `BOOL` module. As a matter of convention,
many functions over builtin sorts in K are suffixed with the name of the
primary sort over which those functions are defined. This happens so that the
syntax of K does not (generally) conflict with the syntax of any other
programming language, which would make it harder to define that programming
language in K.
### Exercise
Write a function `isBlueAndNotYellow` which computes the appropriate Boolean
expression. If you are unsure what the appropriate syntax is to use, you
can refer to the `BOOL` module in
[domains.md](../../../include/kframework/builtin/domains.md). Add a term of
sort `Fruit` for which `isBlue` and `isYellow` both return true, and test that
the `isBlueAndNotYellow` function behaves as expected on all three `Fruit`s.
### Syntax Modules
For most sorts in `domains.md`, K defines more than one module that can be
imported by users. For example, for the `Bool` sort, K defines the `BOOL`
module that has previously already been discussed, but also provides the
`BOOL-SYNTAX` module. This module, unlike the `BOOL` module, only declares the
values `true` and `false`, but not any of the functions that operate over the
`Bool` sort. The rationale is that you may want to import this module into the
main syntax module of your definition in some cases, whereas you generally do
not want to do this with the version of the module that includes all the
functions over the `Bool` sort. For example, if you were defining the semantics
of C++, you might import `BOOL-SYNTAX` into the syntax module of your
definition, because `true` and `false` are part of the grammar of C++, but
you would only import the `BOOL` module into the main semantics module, because
C++ defines its own syntax for and, or, and not that is different from the
syntax defined in the `BOOL` module.
Here, for example, is how we might redefine our Boolean expression calculator
to use the `Bool` sort while maintaining an idiomatic structure of modules
and imports, for the first time including the rules to calculate the values of
expressions themselves (`lesson-06-c.k`):
```k
module LESSON-06-C-SYNTAX
imports BOOL-SYNTAX
syntax Bool ::= "(" Bool ")" [bracket]
> "!" Bool [function]
> left:
Bool "&&" Bool [function]
| Bool "^" Bool [function]
| Bool "||" Bool [function]
endmodule
module LESSON-06-C
imports LESSON-06-C-SYNTAX
imports BOOL
rule ! B => notBool B
rule A && B => A andBool B
rule A ^ B => A xorBool B
rule A || B => A orBool B
endmodule
```
Note the encapsulation of syntax: the `LESSON-06-C-SYNTAX` module contains
exactly the syntax of our Boolean expressions, and no more, whereas any other
syntax needed to implement those functions is in the `LESSON-06-C` module
instead.
#### Exercise
Add an "implies" function to the above Boolean expression calculator, using the
`->` symbol to represent implication. You can look up K's builtin "implies"
function in the `BOOL` module in `domains.md`.
## Integers in K
Unlike most programming languages, where the most basic integer type is a
fixed-precision integer type, the most commonly used integer sort in K is
the `Int` sort, which represents the **mathematical** integers, ie,
arbitrary-precision integers.
K provides three main modules for import when using the `Int` sort. The first,
containing all the syntax of integers as well as all of the functions over
integers, is the `INT` module. The second, which provides just the syntax
of integer literals themselves, is the `INT-SYNTAX` module. However, unlike
most builtin sorts in K, K also provides a third module for the `Int` sort:
the `UNSIGNED-INT-SYNTAX` module. This module provides only the syntax of
**non-negative integers**, i.e., whole numbers. The reasons for this involve
lexical ambiguity. Generally speaking, in most programming languages, `-1` is
not a literal, but instead a literal to which the unary negation operator is
applied. K thus provides this module to ease in specifying the syntax of such
languages.
For detailed information about the functions available over the `Int` sort,
refer to `domains.md`. Note again how we append `Int` to the end of most of the
integer operations to ensure they do not collide with the syntax of other
programming languages.
## Exercises
1. Extend your solution from lesson 1.4, problem 2 to implement the rules
that define the behavior of addition, subtraction, multiplication, and
division. Do not worry about the case when the user tries to divide by zero
at this time. Use `/Int` to implement division. Test your new calculator
implementation by executing the arithmetic expressions you wrote as part of
lesson 1.3, problem 2. Check to make sure each computes the value you expected.
2. Combine the Boolean expression calculator from this lesson with your
solution to problem 1, and then extend the combined calculator with the `<`,
`<=`, `>`, `>=`, `==`, and `!=` expressions. Write some Boolean expressions
that combine integer and Boolean operations, and test to ensure that these
expressions return the expected truth value.
3. Compute the following expressions using your solution from problem 2:
`7 / 3`, `7 / -3`, `-7 / 3`, `-7 / -3`. Then replace the `/Int` function in
your definition with `divInt` instead, and observe how the value of the above
expressions changes. Why does this occur?
## Next lesson
Once you have completed the above exercises, you can continue to
[Lesson 1.7: Side Conditions and Rule Priority](../07_side_conditions/README.md).
| 42.294118 | 81 | 0.746871 | eng_Latn | 0.998696 |
d3d57f4f08f9645c449c35776916f235265e63b6 | 7,952 | md | Markdown | docs/customizing.md | mojojoji/release-please | 1c1f869a6e7e5f4e86bf05d108aa69fbdbef5e7e | [
"Apache-2.0"
] | null | null | null | docs/customizing.md | mojojoji/release-please | 1c1f869a6e7e5f4e86bf05d108aa69fbdbef5e7e | [
"Apache-2.0"
] | null | null | null | docs/customizing.md | mojojoji/release-please | 1c1f869a6e7e5f4e86bf05d108aa69fbdbef5e7e | [
"Apache-2.0"
] | null | null | null | # Customizing Releases
release-please provides several configuration options to allow customizing
your release process.
## Strategy (Language) types supported
Release Please automates releases for the following flavors of repositories:
| release type | description
|-------------------|---------------------------------------------------------|
| `dart` | A repository with a pubspec.yaml and a CHANGELOG.md |
| `elixir` | A repository with a mix.exs and a CHANGELOG.md |
| `go` | A repository with a CHANGELOG.md |
| `helm` | A repository with a Chart.yaml and a CHANGELOG.md |
| `krm-blueprint` | [A kpt package, with 1 or more KRM files and a CHANGELOG.md](https://github.com/GoogleCloudPlatform/blueprints/tree/main/catalog/project) |
| `node` | [A Node.js repository, with a package.json and CHANGELOG.md](https://github.com/yargs/yargs) |
| `ocaml` | [An OCaml repository, containing 1 or more opam or esy files and a CHANGELOG.md](https://github.com/grain-lang/binaryen.ml) |
| `php` | A repository with a composer.json and a CHANGELOG.md |
| `python` | [A Python repository, with a setup.py, setup.cfg, CHANGELOG.md](https://github.com/googleapis/python-storage) and optionally a pyproject.toml and a <project>/\_\_init\_\_.py |
| `ruby` | A repository with a version.rb and a CHANGELOG.md |
| `rust` | A Rust repository, with a Cargo.toml (either as a crate or workspace) and a CHANGELOG.md |
| `simple` | [A repository with a version.txt and a CHANGELOG.md](https://github.com/googleapis/gapic-generator) |
| `terraform-module` | [A terraform module, with a version in the README.md, and a CHANGELOG.md](https://github.com/terraform-google-modules/terraform-google-project-factory) |
### Adding additional strategy types
To add a new release type, simply use the existing [strategies](https://github.com/googleapis/release-please/tree/main/src/strategies) and [updaters](https://github.com/googleapis/release-please/tree/main/src/updaters)
as a starting point.
## Versioning Strategies
A versioning strategy's job is to determine how to increment a SemVer
version given a list of parsed commits.
| Versioning Strategy | Description |
| ------------------- | ----------- |
| `default` | Breaking changes bump the major version, features bump the minor version, bugfixes bump the patch version |
| `always-bump-patch` | Always bump patch version. This is useful for backporting bugfixes to previous major/minor release branches |
| `service-pack` | Designed for Java backport fixes. Uses Maven's specification for service pack versions (e.g. 1.2.3-sp.1) |
### Adding additional versioning strategy types
To add a new versioning strategy, create a new class that implements the
[`VersioningStrategy` interface](/src/versioning-strategy.ts).
## Subdirectories (paths) in a repository
Release Please can operate on a subdirectory of a repository. If you configure a `path`,
Release Please will only consider commits that touch files on that path. The format of the
`path` configuration option should be a simple path segment (`.`, `..`, etc are not allowed)
relative to the repository root.
To configure multiple components on different paths, configure a
[manifest release](/docs/manifest-releaser).
## Changelog Types
A changelog type's job is to build the CHANGELOG notes given a list
of parsed commits.
| Changelog Type | Description |
| -------------- | ----------- |
| `default` | Default CHANGELOG notes builder. Groups by commit type and links to pull requests and commits |
| `github` | Uses the GitHub API to generate notes |
### Adding additional changelog types
To add a new changelog type, create a new class that implements the
[`ChangelogNotes` interface](/src/changelog-notes.ts).
## Pull Requests
### Opening as a draft pull request
If you would like to open the release pull request as a draft, you can
use the `--draft-pull-request` CLI flag or the `draft-pull-request` option
in the manifest configuration.
### Pull Request Title
If you would like to customize the pull request title, you can use the
`--pull-request-title-pattern` CLI option or the `pull-request-title-pattern`
option in the manifest configuration.
The pattern uses string replacement and regular expressions to build and
parse the pull request title. Note that we must be able to parse out the
component and version from the pull request (either via the pull request
title or body format).
The default pull request title uses this pattern:
`chore${scope}: release${component} ${version}` so a common release pull
request title would be `chore(main): release foo-bar v1.2.3`.
| Pattern | Description |
| ------- | ----------- |
| `${scope}` | This pattern is used for specifying the conventional commit scope (e.g. `chore(scope): some message`). We expect that the target branch name is used for the scope value |
| `${component}` | The name of the component being released |
| `${version}` | The version of the component being released |
| `${branch?}` | The target branch of the pull request. If you have multiple release branches, this helps identify which release branch we are working on |
## Release Lifecycle Labels
By default, we open release pull requests with the `autorelease: pending`
label. This label along with the branch name of the release pull request
helps us identify merged release pull requests that need to be tagged with a
release.
After we have tagged the release, we remove the `autorelease: pending` label
and add the `autorelease: tagged` label.
You can customize the "pending" pull request label(s) via the `--label` CLI
option or the `label` option in the manifest configuration.
You can customize the "tagged" pull request label(s) via the
`--release-label` CLI option or the `release-label` option in the manifest
configuration.
## Updating arbitrary files
For most release strategies, you can provide additional files to update
using the [Generic](/src/updaters/generic.ts) updater. You can specify
a comma separated list of file paths with the `--extra-files` CLI option
or the `extra-files` option in the manifest configuration.
To mark versions needing update in those files, you will add annotations
(usually in comments).
You can annotate a line (inline) via:
* `x-release-please-version`
* `x-release-please-major`
* `x-release-please-minor`
* `x-release-please-patch`
For these annotations, we will try to replace the value on that line only.
You can annotate a block by starting with a line containing:
* `x-release-please-start-version`
* `x-release-please-start-major`
* `x-release-please-start-minor`
* `x-release-please-start-patch`
and close the block with a line containing `x-release-please-end`. Within
the block, we will attempt to replace version values.
## Updating arbitrary JSON files
For most release strategies, you can provide additional files to update
using the [GenericJson](/src/updaters/generic-json.ts) updater. You can
specify a configuration object in the `extra-files` option in the manifest
configuration.
```json
{
"extra-files": [
{
"type": "json",
"path": "path/to/file.json",
"jsonpath": "$.json.path.to.field"
}
]
}
```
[JSONPath](https://goessner.net/articles/JsonPath/) is a simple query syntax
for JSON that is similar to XPath for XML. The `jsonpath` configuration
informs release-please on which JSON field to update with the new version.
## Updating arbitrary XML files
For most release strategies, you can provide additional files to update
using the [GenericXml](/src/updaters/generic-xml.ts) updater. You can
specify a configuration object in the `extra-files` option in the manifest
configuration.
```json
{
"extra-files": [
{
"type": "xml",
"path": "path/to/file.xml",
"xpath": "//xpath/to/field"
}
]
}
```
| 42.074074 | 218 | 0.720825 | eng_Latn | 0.98796 |
d3d5884d410752fd3027c296e657c0ec3523efb8 | 13,476 | md | Markdown | articles/virtual-machines/troubleshooting/understand-vm-reboot.md | RobAaldijk/azure-docs.nl-nl | 519c7fc80075795af2670d665d1d93078faf7a87 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/virtual-machines/troubleshooting/understand-vm-reboot.md | RobAaldijk/azure-docs.nl-nl | 519c7fc80075795af2670d665d1d93078faf7a87 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/virtual-machines/troubleshooting/understand-vm-reboot.md | RobAaldijk/azure-docs.nl-nl | 519c7fc80075795af2670d665d1d93078faf7a87 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Het opnieuw opstarten van een systeem voor een virtuele Azure-machine begrijpen | Microsoft Docs
description: Een lijst met gebeurtenissen die ertoe kunnen leiden dat een VM opnieuw wordt opgestart
services: virtual-machines
documentationcenter: ''
author: genlin
manager: dcscontentpm
editor: ''
tags: ''
ms.service: virtual-machines
ms.topic: troubleshooting
ms.tgt_pltfrm: na
ms.workload: infrastructure-services
ms.date: 10/31/2018
ms.author: genli
ms.openlocfilehash: 4694b6ac829c42f20c6783810c248ee18d220433
ms.sourcegitcommit: d103a93e7ef2dde1298f04e307920378a87e982a
ms.translationtype: MT
ms.contentlocale: nl-NL
ms.lasthandoff: 10/13/2020
ms.locfileid: "91965757"
---
# <a name="understand-a-system-reboot-for-azure-vm"></a>Meer informatie over het opnieuw opstarten van het systeem voor Azure VM
Azure virtual machines (Vm's) kunnen soms niet opnieuw worden opgestart, zonder dat er een bewijs van de opstart bewerking is gestart. In dit artikel worden de acties en gebeurtenissen vermeld waarmee Vm's opnieuw kunnen worden opgestart en inzicht krijgen in de manier om onverwachte herstart problemen te voor komen of de impact van dergelijke problemen te verminderen.
## <a name="configure-the-vms-for-high-availability"></a>Configureer de Vm's voor hoge Beschik baarheid
De beste manier om een toepassing die wordt uitgevoerd op Azure te beveiligen tegen het opnieuw opstarten van de VM en uitval tijd is het configureren van de virtuele machines voor maximale Beschik baarheid.
U wordt aangeraden twee of meer virtuele machines in een beschikbaarheidsset te groeperen om dit niveau van redundantie voor uw toepassing te bieden. Deze configuratie zorgt ervoor dat tijdens een geplande of ongeplande onderhouds gebeurtenis ten minste één virtuele machine beschikbaar is en voldoet aan het 99,95 procent van [Azure Sla](https://azure.microsoft.com/support/legal/sla/virtual-machines/v1_5/).
Zie [de beschik baarheid van virtuele machines beheren](../manage-availability.md) voor meer informatie over beschikbaarheids sets.
## <a name="resource-health-information"></a>Resource Health informatie
Azure Resource Health is een service die de status van afzonderlijke Azure-resources weergeeft en praktische richt lijnen biedt voor het oplossen van problemen. In een cloud omgeving waar het niet mogelijk is om rechtstreeks toegang te krijgen tot servers of infrastructuur elementen, is het doel van Resource Health om de tijd te verminderen die u besteedt aan het oplossen van problemen. Met name het doel is om de tijd te verkorten die nodig is om te bepalen of de hoofdmap van het probleem zich in de toepassing bevindt of in een gebeurtenis binnen het Azure-platform. Zie [resource Health begrijpen en gebruiken](../../service-health/resource-health-overview.md)voor meer informatie.
## <a name="actions-and-events-that-can-cause-the-vm-to-reboot"></a>Acties en gebeurtenissen die ertoe kunnen leiden dat de VM opnieuw wordt opgestart
### <a name="planned-maintenance"></a>Gepland onderhoud
Microsoft Azure regel matig updates uitvoeren over de hele wereld om de betrouw baarheid, prestaties en beveiliging te verbeteren van de host-infra structuur die gebruikmaakt van Vm's. Veel van deze updates, waaronder updates op geheugen behoud, worden uitgevoerd zonder dat dit van invloed is op uw virtuele machines of Cloud Services.
Voor sommige updates is het echter nood zakelijk dat de computer opnieuw wordt opgestart. In dergelijke gevallen worden de Vm's afgesloten terwijl de infra structuur wordt bijgewerkt, waarna de Vm's opnieuw worden gestart.
Zie de artikelen die hier worden vermeld als u wilt weten wat het geplande onderhoud van Azure is en hoe dit kan van invloed zijn op de beschik baarheid van uw virtuele Linux-machines. Deze artikelen bieden achtergrondinformatie over het proces van gepland onderhoud in Azure, en over hoe u gepland onderhoud kunt inplannen om de impact ervan nog verder te beperken.
- [Gepland onderhoud voor VM's in Azure](../maintenance-and-updates.md?bc=/azure/virtual-machines/windows/breadcrumb/toc.json&toc=/azure/virtual-machines/windows/toc.json)
- [Gepland onderhoud inplannen voor Azure-VM's](../maintenance-and-updates.md?bc=/azure/virtual-machines/windows/breadcrumb/toc.json&toc=/azure/virtual-machines/windows/toc.json)
### <a name="memory-preserving-updates"></a>Updates met geheugenbehoud
Voor deze klasse van updates in Microsoft Azure hebben gebruikers geen invloed op hun actieve Vm's. Dit zijn veelal updates van onderdelen of services die kunnen worden bijgewerkt zonder de actieve sessie te verstoren. Sommige zijn platform infrastructuur updates op het hostbesturingssysteem dat kan worden toegepast zonder dat de virtuele machines opnieuw moeten worden opgestart.
Deze updates met geheugenbehoud worden uitgevoerd met technologie die in-place livemigratie mogelijk maakt. Wanneer de virtuele machine wordt bijgewerkt, wordt deze in de status *onderbroken* gezet. In deze status blijft de geheugeninhoud in het RAM behouden. Ondertussen ontvangt het besturingssysteem van de onderliggende host de noodzakelijke updates en patches. De VM wordt 30 seconden na het onderbreken weer hervat. Op dat moment wordt de klok van de VM automatisch gesynchroniseerd.
Als gevolg van de korte pauze periode, vermindert het implementeren van updates via dit mechanisme de impact op de Vm's aanzienlijk. Niet alle updates kunnen echter op deze manier worden geïmplementeerd.
Updates voor meerdere exemplaren (voor VM's in een beschikbaarheidsset) worden telkens voor één updatedomein tegelijk toegepast.
> [!NOTE]
> Linux-machines met oude kernel-versies worden beïnvloed door een kernel-paniek tijdens deze update methode. Als u dit probleem wilt voor komen, werkt u bij met de kernel-versie 3.10.0-327.10.1 of hoger. Voor meer informatie, Zie [een Azure Linux-machine op een 3,10-kernel paniek na een upgrade van een host-knoop punt](https://support.microsoft.com/help/3212236).
### <a name="user-initiated-reboot-or-shutdown-actions"></a>Door de gebruiker geïnitieerde acties voor opnieuw opstarten of afsluiten
Als u de computer opnieuw opstart vanaf de Azure Portal, Azure PowerShell, opdracht regel interface of REST API, kunt u de gebeurtenis vinden in het [Azure-activiteiten logboek](../../azure-monitor/platform/platform-logs-overview.md).
Als u de actie uitvoert vanuit het besturings systeem van de virtuele machine, kunt u de gebeurtenis in de systeem logboeken vinden.
Andere scenario's die doorgaans ertoe leiden dat de virtuele machine opnieuw wordt opgestart, omvat het meerdere acties voor configuratie wijziging. Normaal gesp roken wordt een waarschuwing weer gegeven dat aangeeft dat het uitvoeren van een bepaalde actie resulteert in het opnieuw opstarten van de virtuele machine. Voor beelden zijn onder andere het wijzigen van VM-bewerkingen, het aanpassen van het wacht woord van het beheerders account en het instellen van een statisch IP-adres.
### <a name="azure-security-center-and-windows-update"></a>Azure Security Center en Windows Update
Azure Security Center bewaakt dagelijks Windows-en Linux-Vm's voor ontbrekende updates van het besturings systeem. Security Center haalt een lijst met beschik bare beveiligings-en essentiële updates op van Windows Update of Windows Server Update Services (WSUS), afhankelijk van welke service is geconfigureerd op een Windows-VM. Security Center controleert ook op de nieuwste updates voor Linux-systemen. Als op uw virtuele machine een systeem update ontbreekt, wordt Security Center aanbevolen om systeem updates toe te passen. De toepassing van deze systeem updates wordt beheerd via de Security Center in de Azure Portal. Nadat u een aantal updates hebt toegepast, is het mogelijk dat het opnieuw opstarten van de VM vereist is. Zie [systeem updates Toep assen in azure Security Center](../../security-center/asset-inventory.md)voor meer informatie.
Net als bij on-premises servers pusht Azure geen updates van Windows Update naar Windows-Vm's, omdat deze machines zijn bedoeld om te worden beheerd door hun gebruikers. U wordt echter aangemoedigd om de instelling automatische Windows Update ingeschakeld te laten. Automatische installatie van updates van Windows Update kan er ook voor zorgen dat de computer opnieuw wordt opgestart nadat de updates zijn toegepast. Zie [Windows Update Veelgestelde vragen](https://support.microsoft.com/help/12373/windows-update-faq)voor meer informatie.
### <a name="other-situations-affecting-the-availability-of-your-vm"></a>Andere situaties die van invloed zijn op de beschik baarheid van uw virtuele machine
Er zijn andere gevallen waarin Azure het gebruik van een virtuele machine actief kan opschorten. U ontvangt e-mail meldingen voordat deze actie wordt uitgevoerd, zodat u de onderliggende problemen kunt oplossen. Voor beelden van problemen die van invloed zijn op de VM-Beschik baarheid, zijn beveiligings schendingen en de verval datum van betalings methoden.
### <a name="host-server-faults"></a>Fouten met hostservers
De virtuele machine wordt gehost op een fysieke server die binnen een Azure-Data Center wordt uitgevoerd. Naast enkele andere onderdelen van Azure voert de fysieke server een agent uit die de Hosta Gent wordt genoemd. Wanneer deze onderdelen van Azure-software op de fysieke server niet meer reageren, activeert het bewakings systeem het opnieuw opstarten van de hostserver om te proberen het herstel uit te voeren. De virtuele machine is doorgaans binnen vijf minuten opnieuw beschikbaar en blijft actief op dezelfde host als voorheen.
Server fouten worden meestal veroorzaakt door hardwarestoringen, zoals het mislukken van een harde schijf of een Solid-State station. Azure bewaakt deze instanties voortdurend, identificeert de onderliggende bugs en implementeert updates nadat de oplossing is geïmplementeerd en getest.
Omdat sommige hostserver fouten specifiek kunnen zijn voor die server, kan een herhaalde VM-opstart situatie worden verbeterd door de virtuele machine hand matig opnieuw te implementeren op een andere hostserver. Deze bewerking kan worden geactiveerd met behulp van de optie opnieuw **implementeren** op de pagina Details van de virtuele machine, of door de virtuele machine te stoppen en opnieuw op te starten in de Azure Portal.
### <a name="auto-recovery"></a>Automatisch herstel
Als de hostserver om welke reden dan ook niet opnieuw kan worden opgestart, initieert het Azure-platform een actie voor automatisch herstel om de defecte hostserver uit te wisselen voor verdere onderzoek.
Alle Vm's op die host worden automatisch verplaatst naar een andere, gezonde hostserver. Dit proces is meestal binnen vijf tien minuten voltooid. Zie [automatisch herstel van virtuele machines](https://azure.microsoft.com/blog/service-healing-auto-recovery-of-virtual-machines)voor meer informatie over het automatische herstel proces.
### <a name="unplanned-maintenance"></a>Niet-gepland onderhoud
In zeldzame gevallen moet het Azure Operations-team mogelijk onderhouds activiteiten uitvoeren om te zorgen voor de algehele status van het Azure-platform. Dit gedrag kan van invloed zijn op de beschik baarheid van de virtuele machine en resulteert doorgaans in dezelfde automatische herstel actie zoals eerder beschreven.
Niet-gepland onderhoud omvat het volgende:
- Defragmentatie van urgente knoop punten
- Updates voor dringende netwerk switch
### <a name="vm-crashes"></a>VM loopt vast
Vm's worden mogelijk opnieuw opgestart vanwege problemen binnen de VM zelf. De werk belasting of rol die op de virtuele machine wordt uitgevoerd, kan een fout controle activeren binnen het gast besturingssysteem. Raadpleeg de systeem-en toepassings logboeken voor Windows-Vm's en de seriële logboeken voor Linux Vm's voor meer informatie over het bepalen van de reden voor het vastlopen.
### <a name="storage-related-forced-shutdowns"></a>Aan opslag gerelateerd geforceerd afsluiten
Vm's in azure zijn afhankelijk van virtuele schijven voor besturings systeem en gegevens opslag die worden gehost op de Azure Storage-infra structuur. Wanneer de beschik baarheid of de verbinding tussen de virtuele machine en de bijbehorende schijven langer dan 120 seconden van invloed is op het Azure-platform, worden de Vm's geforceerd afgesloten om beschadiging van gegevens te voor komen. De Vm's worden automatisch ingeschakeld nadat de opslag verbinding is hersteld.
De duur van de afsluiting kan korter zijn dan vijf minuten, maar kan aanzienlijk langer duren. Hier volgt een van de specifieke gevallen die zijn gekoppeld aan opslag gerelateerd geforceerde afsluitingen:
**Overschrijden IO-limieten**
Vm's kunnen tijdelijk worden afgesloten wanneer I/O-aanvragen consistent worden beperkt omdat het volume van I/O-bewerkingen per seconde (IOPS) de I/O-limieten voor de schijf overschrijdt. (Standaard schijf opslag is beperkt tot 500 IOPS.) U kunt dit probleem oplossen door schijf striping te gebruiken of de opslag ruimte in de gast-VM te configureren, afhankelijk van de werk belasting.
### <a name="other-incidents"></a>Andere incidenten
In zeldzame gevallen kan een algemeen probleem van invloed zijn op meerdere servers in een Azure-Data Center. Als dit probleem optreedt, verzendt het Azure-team e-mail meldingen naar de betrokken abonnementen. U kunt het [Azure service Health-dash board](https://azure.microsoft.com/status/) en de Azure Portal controleren op de status van lopende storingen en eerdere incidenten. | 110.459016 | 853 | 0.815301 | nld_Latn | 0.999898 |
d3d5b958e30ed7b2d6034fad5bf720e549a5aab8 | 7,450 | md | Markdown | _posts/2016/2016-12-14-ojala-hubiese-tenido-un-mentor.md | rubenfa/rubenfa.github.io | ccf8aaace33e1ccd5ddb16fe5cebcd28f59be3c0 | [
"MIT"
] | null | null | null | _posts/2016/2016-12-14-ojala-hubiese-tenido-un-mentor.md | rubenfa/rubenfa.github.io | ccf8aaace33e1ccd5ddb16fe5cebcd28f59be3c0 | [
"MIT"
] | null | null | null | _posts/2016/2016-12-14-ojala-hubiese-tenido-un-mentor.md | rubenfa/rubenfa.github.io | ccf8aaace33e1ccd5ddb16fe5cebcd28f59be3c0 | [
"MIT"
] | null | null | null | ---
layout: post
title: Ojalá hubiese tenido un mentor
---
Tengo un primo que este año ha empezado un ciclo formativo de desarrollo de aplicaciones informáticas. El caso es que a veces me pregunta cosas sobre el mundillo. Eso me hace pensar en mi yo del pasado, y en el tiempo que pasé en la Universidad, **y en lo mucho que me habría ayudado tener un mentor**.
Yo estudié la extinta Ingeniería Técnica en Informática de Gestión, en la Universidad de Alcalá de Henares, y pasados los años he sabido valorar los conocimientos que allí recibí. Y la sensación es agridulce. De hecho si ahora tuviera que decidir si estudiar una carrera o no, probablemente decidiría no estudiarla. Aunque eso sí, con matices.
## La Universidad
Yo llegé a la UAH de rebote. No saqué una gran nota en selectividad, así que acabé allí como último recurso. No pude elegir. Y fue duro, porque para llegar hasta el campus de Alcalá, tenía que gastar dos horas y media de mi vida en el transporte público. Eso para la ida. Para la vuelta gastaba otro tanto. Tantas horas en el Cercanías dan para leer muchos libros. Una pena que por aquel entonces no existiera el Kindle.
Independientemente de la distancia, honestamente creo que perdí mucho tiempo estudiando cosas que no me han servido de mucho. Y lo que es peor, dejé de estudiar muchas otras que me hubiesen venido muy bien.
Allí estudié muchas matemáticas. Está claro que todos los fundamentos de desarrollo de software, se basan en conceptos matemáticos, pero creo que en las Universidades españolas esto no se explica demasiado bien. Estudié asignaturas como Cálculo, Matemática discreta o Estadística, pero nadie me explicó la relación que tenían con el desarrollo de software. Pasados los años soy capaz de ver algunas de esas relaciones, pero lo que estudié es apenas un recuerdo, y ahora sería incapaz de aplicarlo sin tener que estudiarlo otra vez.
Perdí muchísimo tiempo estudiando Contabilidad y Economía de la empresa, porque algún iluminado pensó que nos pasaríamos el día desarrollando clones de Contaplus. Recuerdo vagamente como hacer un asiento de retorno de envases y embalajes, pero jamás lo he aplicado en nada.
Es cierto que también aprendí cosas útiles (a parte de programación claro). Aprendí mucho sobre arquitectura de computadores. Aprender sobre los conjuntos de instrucciones de los x86 o los SPARC, por ejemplo, fue algo muy divertido. Aprender a realizar operaciones binarias con mantisas y exponentes, no lo fue tanto, pero guardo buen recuerdo de ello. También aprendí mucho de redes, con un profesor que era una maravilla. Jamás he visto una red token ring, y tampoco he tenido nunca que particionar una red en subredes, aunque es cierto que todo ese me ha ayudado a comprender como funcionan ciertas cosas. Lo mismo con el modelo OSI (que tiempos). Aprendí bastante de bases de datos, porque el profe también se lo curraba y nos enseñó bien a hacer diagramas de Entidad-Relación.
## Existen otros caminos
Estudiar en la Universidad, es una manera de adquirir conocimientos que no tienes, haciendo que alguien te los enseñe. Es una manera totalmente lógica y es a la que estamos acostumbrados desde pequeños. Vamos a un centro educativo (colegio, instituto o Universidad) y escuchamos a diferentes profesores, explicarnos lo que saben sobre unas materias que alguien ha decidido que tienes que aprender. Así ha sido siempre. Pero el mundo ha cambiado mucho desde entonces, y creo que hay otras posibles maneras de adquirir esos conocimientos.
Internet está lleno de cursos, vídeos, tutoriales, libros y blogs que te pueden enseñar todo lo que necesites saber para programar. El problema, es que hay tanta información, y tan variada, que es difícil saber que elegir. No tienes un temario, ni unas materias preestablecidas, porlo que es fácil perderse. Y siempre con el riesgo de [ser presa de un hype](https://charlascylon.com/2016-11-07-los-hypes-la-especializaci%C3%B3n-y-que-aprender). Y aunque sepamos qué es lo que queremos aprender, nos podemos encontrar con cursos de dudosa calidad, o tutoriales de esos que solo rascan en la superficie de una tecnología o plataforma.
Así que, con tanta cantidad de información, se hace indispensable la figura de un mentor.
## Ojalá hubiese tenido un mentor
Según la RAE un mentor es *un consejero o guía*. Es alguien que probablemente ha pasado por dónde tú estás ahora, y desde la experiencia, es capaz de aconsejarte para orientar tu formación y desarrollo profesional.
Yo no he tenido un mentor, y no tengo dudas que **de haber tenido uno, ahora sería mucho mejor desarrollador de software**. Un mentor me hubiese dicho que no me preocupase por el dinero a cobrar, que trabajase en sitios donde pudiera aprender (que me rodeara de buenos profesionales). Un mentor me habría dicho que hiciera más cosas por mi mismo, que programase más en casa, que colaborara en proyectos Open Source. Un mentor me habría presentado (física o virtualmente) a otros desarolladores, y me habría recomendado libros que debería leer. En definitiva un mentor me habría orientado en la dirección correcta para ser mucho mejor profesional de lo que soy ahora.
## La idea de la mentoría
Pensando en esto se me ocurrio preguntar por Twitter, si los desarrolladores *senior* me podían decir, qué es lo que ellos creían que alguien debería saber para ser un buen programador. Así que [en un repo de GitHub](https://github.com/rubenfa/mentoria), algunos buenos samaritanos como [Juanma](https://github.com/rubenfa/mentoria/blob/master/juan_maria_hernandez_a/juan_maria_hernandez_a.md), [Sergio](https://github.com/rubenfa/mentoria/blob/master/sergio_leon_g/sergio_leon_g.md), [José Antonio](https://github.com/rubenfa/mentoria/blob/master/jose_antonio_dongil_s/jose_antonio_dongil_s.md) o [Javier](https://github.com/rubenfa/mentoria/blob/master/javier_ros_m/javier_ros_m.md), han contado qué cosas creen que un desarrollador debería aprender. Espero seguir haciendo presión por Twitter para que más gente se una, pero mi poder de convocatoria no es demasiado alto, así que la cosa irá despacio. De todas formas si eres alguien que está empezando, no dudes en leer las impresiones de estos cracks, porque creeme, sus consejos valen muchísimo (y te ahorrarán perder tiempo).
Aun así esto no es suficiente, y sigo dándole vueltas al tema. Yo creo que nuestra profesión mejoraría mucho si todos tuviéramos un mentor, en especial cuando estamos empezando. Y da igual si estamos en la uni, en un ciclo formativo o somos autodidactas. Un buen consejo siempre viene bien. Ando buscando alguna buena idea para gestionar esto, pero de momento sin nada concreto. He estado haciendo busquedas en Google, y he visto que hay muchas aplicaciones específicas para realizar programas de mentoría. También he visto que [hay plataformas](https://www.codementor.io/) en las que puedes encontrar un mentor pagando una cantidad de dinero. No lo he probado, pero así a bote pronto, me parecen más bien clases particulares para aprender alguna tecnología o lenguaje. Y este artículo no va de esto.
De momento, y aunque yo no soy nadie importante, y tampoco soy ningún crack, yo me ofrezco para ser tu mentor. Así que si has conseguido leer este ladrillo hasta el final y quieres alguien te guíe un poco sobre las cosas que puedes aprender, yo me ofrezco. Si necesitas un mentor ponte en contacto conmigo ([aquí puedes ver como](https://charlascylon.com/aboutme)).
| 140.566038 | 1,082 | 0.801342 | spa_Latn | 0.999313 |
d3d5c708567ad4a09af32e48c33ea1a22790a157 | 401 | md | Markdown | pages/contact.md | Ballisticannon/ballisticannon.github.io | 965d7ddc59d65bd2a0480ef7a7c9c872c01be6c9 | [
"MIT"
] | null | null | null | pages/contact.md | Ballisticannon/ballisticannon.github.io | 965d7ddc59d65bd2a0480ef7a7c9c872c01be6c9 | [
"MIT"
] | null | null | null | pages/contact.md | Ballisticannon/ballisticannon.github.io | 965d7ddc59d65bd2a0480ef7a7c9c872c01be6c9 | [
"MIT"
] | null | null | null | ---
layout: page
title: "Contact"
meta_title: "Get in contact"
subheadline: "Now accepting e-mail, snail mail, message-in-a-bottle, sky writing, and carrier pigeon"
teaser: "On second thought, just shoot me an e-mail."
permalink: "/contact/"
---
You can reach me by e-mail through the address maximillian.virani at gmail.com. I'll do my best to reply quickly to any questions or concerns you may have. | 44.555556 | 155 | 0.750623 | eng_Latn | 0.994954 |
d3d6095ccbbb0e64c734836cb8840aa65313bae6 | 36 | md | Markdown | Libraries/Readme.md | Caius-Lu/Savior | 47c22e06c38cc9b5f7007d79f791015c8b2b76aa | [
"BSD-2-Clause"
] | 108 | 2021-03-19T03:45:48.000Z | 2022-03-29T12:19:38.000Z | Libraries/Readme.md | Caius-Lu/Savior | 47c22e06c38cc9b5f7007d79f791015c8b2b76aa | [
"BSD-2-Clause"
] | 2 | 2021-05-12T07:26:21.000Z | 2021-07-16T12:53:52.000Z | Libraries/Readme.md | Caius-Lu/Savior | 47c22e06c38cc9b5f7007d79f791015c8b2b76aa | [
"BSD-2-Clause"
] | 27 | 2021-03-19T05:50:26.000Z | 2021-12-28T07:13:09.000Z | # Libraries
用来放置将ncnn转换出来的模型的动态链接库。 | 12 | 23 | 0.861111 | yue_Hant | 0.588096 |
d3d65228d097b1efbcb3a87fdb012cab78930cd2 | 2,820 | markdown | Markdown | xap102/cassandra-hector-client.markdown | barakb/gigaspaces-wiki-jekyll | 7d18c84c0ae68b36d6e82a94b340bc06b8f01297 | [
"Apache-2.0"
] | null | null | null | xap102/cassandra-hector-client.markdown | barakb/gigaspaces-wiki-jekyll | 7d18c84c0ae68b36d6e82a94b340bc06b8f01297 | [
"Apache-2.0"
] | null | null | null | xap102/cassandra-hector-client.markdown | barakb/gigaspaces-wiki-jekyll | 7d18c84c0ae68b36d6e82a94b340bc06b8f01297 | [
"Apache-2.0"
] | null | null | null | ---
layout: post102
title: Hector Client
categories: XAP102
parent: cassandra-space-persistency.html
weight: 300
---
A wrapper around the [Hector Library](http://hector-client.github.com/hector/build/html/index.html) used for communicating with Cassandra.
This component is used by both the [Cassandra Space Synchronization Endpoint](./cassandra-space-synchronization-endpoint.html) and the [Cassandra Space Data Source](./cassandra-space-data-source.html). The main usage is related to metadata operations (such as creating column families, adding secondary indexes, reading column families metadata, etc...).
# Configuration
## Library Dependencies
See [Hector library dependencies](./cassandra-space-synchronization-endpoint.html#Library dependencies) for required dependencies.
## Setup
{% inittab Configuration Examples %}
{% tabcontent Spring %}
{% highlight xml %}
<bean id="hectorClient"
class="org.openspaces.persistency.cassandra.HectorCassandraClientFactoryBean">
<!-- comma separated seed list -->
<property name="hosts" value="${cassandra.host}" />
<!-- cassandra rpc communication port -->
<property name="port" value="${cassandra.port}" />
<!-- keyspace name to work with -->
<property name="keyspaceName" value="${cassandra.keyspace}" />
</bean>
{% endhighlight %}
{% endtabcontent %}
{% tabcontent Code %}
{% highlight java %}
HectorCassandraClient hectorClient = new HectorCassandraClientConfigurer()
.hosts(cassandraHosts)
.port(cassandraPort)
.keyspaceName(cassandraKeyspaceName)
.create();
{% endhighlight %}
{% endtabcontent %}
{% endinittab %}
## `HectorCassandraClient` Properties
{: .table .table-bordered}
|Property|Description|Default|
|:-------|:----------|:------|
|hosts|A comma separated list of seeds in the Cassandra cluster| |
|port|The rpc port for Cassandra client communication|9160|
|keyspaceName|The name of the keyspace to work with| |
|clusterName|If there is need to connect to more than one Cassandra cluster within the same JVM, each cluster should be references by a different name.|cluster|
|readConsistencyLevel|The [CassandraConsistencyLevel](http://www.gigaspaces.com/docs/JavaDoc{% currentversion %}/index.html?org/openspaces/persistency/cassandra/CassandraConsistencyLevel.html) in which read operations should be performed|QUORUM|
|writeConsistencyLevel|The [CassandraConsistencyLevel](http://www.gigaspaces.com/docs/JavaDoc{% currentversion %}/index.html?org/openspaces/persistency/cassandra/CassandraConsistencyLevel.html) in which write operations should be performed|QUORUM|
|columnFamilyGcGraceSeconds|See [Distributed deletes](http://wiki.apache.org/cassandra/DistributedDeletes) |10 Days (Derived from Cassandra's default value)|
| 41.470588 | 355 | 0.743972 | eng_Latn | 0.760681 |
d3d7252a37ad7a3a0d72b28cf6d8a04261e18145 | 89 | md | Markdown | xbox-live-docs-pr/get-started/setup-ide/managed-partners/xcode-ios/TOC-xcode-ios.md | jkcoxson/xbox-live-docs | e071834ee6e7339808bd613be011d28ce0518b8f | [
"CC-BY-4.0",
"MIT"
] | 26 | 2019-05-06T17:04:33.000Z | 2022-03-24T10:48:26.000Z | xbox-live-docs-pr/get-started/setup-ide/managed-partners/xcode-ios/TOC-xcode-ios.md | jkcoxson/xbox-live-docs | e071834ee6e7339808bd613be011d28ce0518b8f | [
"CC-BY-4.0",
"MIT"
] | 77 | 2019-03-28T09:31:18.000Z | 2022-03-19T20:35:34.000Z | xbox-live-docs-pr/get-started/setup-ide/managed-partners/xcode-ios/TOC-xcode-ios.md | jkcoxson/xbox-live-docs | e071834ee6e7339808bd613be011d28ce0518b8f | [
"CC-BY-4.0",
"MIT"
] | 38 | 2019-07-17T17:58:06.000Z | 2022-02-14T03:14:21.000Z | # live-mp-xcode-ios-nav.md
## live-xcode-ios-mp.md
## _include_ other/TOC-ios-other.md
| 14.833333 | 35 | 0.696629 | eng_Latn | 0.429656 |
d3d755de8ff1d95173b977614fc02d1097d16d12 | 3,410 | md | Markdown | README.md | metaborg/util | 40d16e5dc74b459a81f92b0e5e26e56a122b2695 | [
"Apache-2.0"
] | null | null | null | README.md | metaborg/util | 40d16e5dc74b459a81f92b0e5e26e56a122b2695 | [
"Apache-2.0"
] | null | null | null | README.md | metaborg/util | 40d16e5dc74b459a81f92b0e5e26e56a122b2695 | [
"Apache-2.0"
] | null | null | null | [](https://github.com/metaborg/log/blob/master/LICENSE)
[](https://github.com/metaborg/log/actions/workflows/build.yml)
[](https://buildfarm.metaborg.org/job/metaborg/job/log/job/master/lastBuild)
[](https://mvnrepository.com/artifact/org.metaborg/log.api?repo=metaborg-releases)
# Metaborg logging abstraction
A logging abstraction for `org.metaborg` projects.
## Development Guide
### Building
This repository is built with Gradle, which requires a JDK of at least version 8 to be installed. Higher versions may work depending on [which version of Gradle is used](https://docs.gradle.org/current/userguide/compatibility.html).
To build this repository, run `./gradlew buildAll` on Linux and macOS, or `gradlew buildAll` on Windows.
### Automated Builds
All branches and tags of this repository are built on:
- [GitHub actions](https://github.com/metaborg/log/actions/workflows/build.yml) via `.github/workflows/build.yml`.
- Our [Jenkins buildfarm](https://buildfarm.metaborg.org/view/Devenv/job/metaborg/job/log/) via `Jenkinsfile` which uses our [Jenkins pipeline library](https://github.com/metaborg/jenkins.pipeline/).
### Publishing
This repository is published via Gradle and Git with the [Gitonium](https://github.com/metaborg/gitonium) and [Gradle Config](https://github.com/metaborg/gradle.config) plugins.
It is published to our [artifact server](https://artifacts.metaborg.org) in the [releases repository](https://artifacts.metaborg.org/content/repositories/releases/).
First update `CHANGELOG.md` with your changes, create a new release entry, and update the release links at the bottom of the file.
Then, commit your changes.
To make a new release, create a tag in the form of `release-*` where `*` is the version of the release you'd like to make.
Then first build the project with `./gradlew buildAll` to check if building succeeds.
If you want our buildfarm to publish this release, just push the tag you just made, and our buildfarm will build the repository and publish the release.
If you want to publish this release locally, you will need an account with write access to our artifact server, and tell Gradle about this account.
Create the `./gradle/gradle.properties` file if it does not exist.
Add the following lines to it, replacing `<username>` and `<password>` with those of your artifact server account:
```
publish.repository.metaborg.artifacts.username=<username>
publish.repository.metaborg.artifacts.password=<password>
```
Then run `./gradlew publishAll` to publish all built artifacts.
You should also push the release tag you made such that this release is reproducible by others.
## Copyright and License
Copyright © 2018-2022 Delft University of Technology
The files in this repository are licensed under the [Apache License, Version 2.0](https://www.apache.org/licenses/LICENSE-2.0).
You may use the files in this repository in compliance with the license.
| 64.339623 | 280 | 0.784164 | eng_Latn | 0.930811 |
d3d84fafea175f3392d8193b0c3e312387330cad | 2,108 | md | Markdown | docs/framework/wcf/feature-details/wcf-web-http-programming-model.md | OpportunityLiu/docs.zh-cn | eac29360831c86e94fd24e3d2948bde016c0463c | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-06-26T12:46:03.000Z | 2021-06-26T12:46:03.000Z | docs/framework/wcf/feature-details/wcf-web-http-programming-model.md | OpportunityLiu/docs.zh-cn | eac29360831c86e94fd24e3d2948bde016c0463c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wcf/feature-details/wcf-web-http-programming-model.md | OpportunityLiu/docs.zh-cn | eac29360831c86e94fd24e3d2948bde016c0463c | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-03-11T08:16:26.000Z | 2019-03-11T08:16:26.000Z | ---
title: WCF Web HTTP 编程模型
ms.date: 03/30/2017
helpviewer_keywords:
- web services programming model [WCF]
- POX
- REST
ms.assetid: 2312a8d3-b66e-4623-ba42-978434300c7f
ms.openlocfilehash: e063cdba74af9ee90b41d829a2a8b251a5cc96e7
ms.sourcegitcommit: 3d5d33f384eeba41b2dff79d096f47ccc8d8f03d
ms.translationtype: MT
ms.contentlocale: zh-CN
ms.lasthandoff: 05/04/2018
ms.locfileid: "33498005"
---
# <a name="wcf-web-http-programming-model"></a>WCF Web HTTP 编程模型
Windows Communication Foundation (WCF) Web HTTP 编程模型允许开发人员公开向非 SOAP 终结点的 WCF 服务操作。 本节中的主题详细研究此功能。
## <a name="in-this-section"></a>本节内容
[WCF Web HTTP 编程模型概述](../../../../docs/framework/wcf/feature-details/wcf-web-http-programming-model-overview.md)
提供 Windows Communication Foundation (WCF) Web HTTP 编程模型的概述。
[WCF Web HTTP 编程对象模型](../../../../docs/framework/wcf/feature-details/wcf-web-http-programming-object-model.md)
讨论 Windows Communication Foundation (WCF) Web HTTP 编程模型及其工作原理。
[如何：创建基本 WCF Web HTTP 服务](../../../../docs/framework/wcf/feature-details/how-to-create-a-basic-wcf-web-http-service.md)
说明如何编写公开非 SOAP 终结点的基本服务。
[如何：向 SOAP 和 Web 客户端公开协定](../../../../docs/framework/wcf/feature-details/how-to-expose-a-contract-to-soap-and-web-clients.md)
说明如何编写向 SOAP 和非 SOAP 客户端公开同一协定的基本服务。
[UriTemplate 和 UriTemplateTable](../../../../docs/framework/wcf/feature-details/uritemplate-and-uritemplatetable.md)
说明如何使用 <xref:System.UriTemplate> 和 <xref:System.UriTemplateTable> 控制 URI。
[对 WCF Web HTTP 服务的缓存支持](../../../../docs/framework/wcf/feature-details/caching-support-for-wcf-web-http-services.md)
说明如何指定 WCF Web HTTP 服务的缓存行为。
[WCF Web HTTP 格式设置](../../../../docs/framework/wcf/feature-details/wcf-web-http-formatting.md)
说明如何指定 WCF Web HTTP 服务响应的格式。
[WCF Web HTTP 错误处理](../../../../docs/framework/wcf/feature-details/wcf-web-http-error-handling.md)
说明如何将错误返回 WCF Web 客户端，包括 HTTP 状态代码和用户定义的其他错误数据。
[从 WCF 服务调用 REST 样式服务](../../../../docs/framework/wcf/feature-details/calling-a-rest-style-service-from-a-wcf-service.md)
说明如何从 WCF 服务内部来调用 REST 样式服务。
| 45.826087 | 128 | 0.723909 | yue_Hant | 0.767828 |
d3d85bb6f283b014107fa2829837de2c0d3e1c1c | 1,693 | md | Markdown | build/docs/BuAgentScheduleActivity.md | MyPureCloud/platform-client-sdk-ruby | 1e1d246efda13222f3dc9b81f358795812666e45 | [
"MIT"
] | 1 | 2020-03-03T15:10:55.000Z | 2020-03-03T15:10:55.000Z | build/docs/BuAgentScheduleActivity.md | MyPureCloud/platform-client-sdk-ruby | 1e1d246efda13222f3dc9b81f358795812666e45 | [
"MIT"
] | 3 | 2019-06-19T19:36:20.000Z | 2020-12-03T15:14:58.000Z | build/docs/BuAgentScheduleActivity.md | MyPureCloud/platform-client-sdk-ruby | 1e1d246efda13222f3dc9b81f358795812666e45 | [
"MIT"
] | 7 | 2018-01-05T03:10:57.000Z | 2022-02-17T09:24:42.000Z | ---
title: BuAgentScheduleActivity
---
:::error
**The Ruby SDK is deprecated as of 9/16/2020**
The Genesys Cloud Ruby SDK (v96.0.0) will be frozen at its current version level. Any new enhancements to our API or bug fixes will not be backported. If you do need to take advantage of new features or bug fixes outside the Genesys Cloud Ruby SDK, you will need to use the Genesys Cloud REST endpoints directly. More information can be found in the [Official Announcement](https://developer.mypurecloud.com/forum/t/announcement-genesys-cloud-ruby-sdk-end-of-life/8850).
:::
## PureCloud::BuAgentScheduleActivity
## Properties
|Name | Type | Description | Notes|
|------------ | ------------- | ------------- | -------------|
| **start_date** | **DateTime** | The start date/time of this activity. Date time is represented as an ISO-8601 string. For example: yyyy-MM-ddTHH:mm:ss.SSSZ | [optional] |
| **length_minutes** | **Integer** | The length of this activity in minutes | [optional] |
| **description** | **String** | The description of this activity | [optional] |
| **activity_code_id** | **String** | The ID of the activity code associated with this activity | [optional] |
| **paid** | **BOOLEAN** | Whether this activity is paid | [optional] |
| **time_off_request_id** | **String** | The ID of the time off request associated with this activity, if applicable | [optional] |
| **external_activity_id** | **String** | The ID of the external activity associated with this activity, if applicable | [optional] |
| **external_activity_type** | **String** | The type of the external activity associated with this activity, if applicable | [optional] |
{: class="table table-striped"}
| 58.37931 | 470 | 0.69935 | eng_Latn | 0.949667 |
d3d9203b5aa2d55bd6062786c92ef61573b30a6e | 6,661 | md | Markdown | 流行/Lose Yourself-8 Mile OST/README.md | hsdllcw/everyonepiano-music-database | d440544ad31131421c1f6b5df0f039974521eb8d | [
"MIT"
] | 17 | 2020-12-01T05:27:50.000Z | 2022-03-28T05:03:34.000Z | 流行/Lose Yourself-8 Mile OST/README.md | hsdllcw/everyonepiano-music-database | d440544ad31131421c1f6b5df0f039974521eb8d | [
"MIT"
] | null | null | null | 流行/Lose Yourself-8 Mile OST/README.md | hsdllcw/everyonepiano-music-database | d440544ad31131421c1f6b5df0f039974521eb8d | [
"MIT"
] | 2 | 2021-08-24T08:58:58.000Z | 2022-02-08T08:22:52.000Z |
**Lose Yourself** （迷失自我）选自嘻哈电影《8 Mile》同名原声带《8 Mile》
这首歌当时是轰动性的！它创造了一个奇迹！全美流行榜12周冠军、UK流行榜冠军、饶舌榜亚军、2003年第75届奥斯卡最佳电影主题曲奖、2003MTV音乐录影带奖“最佳电影主题曲影带”、2004格莱美奖2项大奖得奖作、格莱美史上首支入围'年度最佳歌曲'之饶舌歌、在《滚石评选500有史最伟大的歌》里，lose
yourself 排在第166位。
_
Lose Yourself_ 由美国的说唱歌手Eminem演唱。其风格类型为：Hardcore
Rap（硬核说唱）。Eminem最大的突破就是证明白人也能介入到黑人一统天下的说唱（RAP）界中，而且获得巨大的成功。同时他的叛逆不仅长期以来深受美国青少年喜爱，也让他在舆论中始终遭到抨击。Eminem获得的奖杯总数窜至历史第三位，居麦当娜和皮特-
加布里埃尔之后。
歌词下方是 _Lose Yourself钢琴谱_ ，希望大家喜欢。
### Lose Yourself歌词：
Look,if you had one shot,or one opportunity
瞧着，如果你拥有 一次，一次机会
To seize everything you ever wanted…In one moment
去完成你曾经梦想拥有的一切...此时此刻
Would you capture it or just let it slip?
你是抓住它还是仅仅让它溜走？
His palms are sweaty,knees weak,arms are heavy.
他的手掌在出汗，膝盖发软，双臂沉重
There's vomit on his sweater already,mom's spaghetti.
妈妈做的意大利面已经吐在了他的毛衣上
He's nervous,but on the surface he looks calm and ready To drop bombs,
他紧张，但在表面上他看上去却很冷静 并且是准备好引爆全场.
but he keeps on forgetting What he wrote down,
但他却一直在忘记他写下的，
the whole crowd goes so loud
所有人群的起哄声、嘘声是那么的大
He opens his mouth,but the words won't come out
他张开他的嘴巴，但一词也说不出来。
He’s choking how,everybody’s joking now
他窒息了，此时所有人都在嘲笑他，
The clock's run out,time's up over,bloah!
表针走过，结束时间已到，天啊！（这对他来说就像世界末日!)
Snap back to reality,Oh there goes gravity
迅速回到现实中来，oh 失去重力般！
Oh,there goes Rabbit,he choked
oh，这里的Rabbit，他哑巴了.
He's so mad,but he won't give up that easy
他是如此疯狂，但他却没那样地放弃，不是吗? 对
No,he won't have it,he knows his whole back's to these ropes
他没有，他知道这整个背后的阴谋（种族歧视)
It don't matter,he's dope
没关系，他是很强的
He knows that,but he’s broke .He's so sad that he knows
他知道那些，但他却身无分文 他如此悲伤因为他知道这
When he goes back to his mobile home,that's when it's
当他回到自己的活动房屋时（拖车），那就是他的时间了。
Back to the lab again yo .This whole rhapsody
再次回到实验中.整个这个狂想曲
He‘d better go capture this moment and hope it don't pass him. （3s)
他最好是去抓住这个时刻且希望它不要再从他身边溜过。
Chorus X2
（You'd better) lose yourself in the music,the moment .
你最好在音乐中忘记自我，在这个时刻。
You own it. You'd better never let it go(go..)
你赢得它，你最好永远不要放走它，
You only get one shot,do not miss your chance to blow,
你只有这一次机会，不要错过引爆众人的机会，
This opportunity comes once in a lifetime yo.
这种机会人生只有一次，哟。
（You 'd better) lose yourself in the music,the moment .
你最好在音乐中忘记自我，在这个时刻。
You own it. You'd better never let it go(go..)
你赢得它，你最好永远不要放走它，
You only get one shot,do not miss your chance to blow,
你只有这一次机会，不要错过引爆众人的机会，
This opportunity comes once in a lifetime yo.
这种机会人生只有一次，哟。
The soul's escaping,through this hole that it's gaping.
他的灵魂正在通过这个打开的缺口中溜走
This world is mine for the taking.
这个世界是我说的算的.
Make me king!as we move toward a,new world order .
让我为王！让我们共同移向一个 新世界的秩序
A normal life is boring,but super-stardom's close to post mortar(post mort em)
一个平凡的人生是无聊的，但明星之路却让人接近死亡
It only grows harder,homie grows hotter
这条道路会越来越艰苦，家人也越来越热情
He blows us all over,these hoes is all on him
他把我们全都引爆了，这些女人都为他发狂
Coast to coast shows,he's know as the globe trotter.
全美的演出，他知道自己就像世界观光旅行家
Lonely roads,God only knows.
只有上帝才知道他的道路是多么的孤独.
He's grown farther from home,he's no father.
他的成长之路背井离乡，他没有父亲.
He goes home and barely knows his own daughter.
他回到家他勉强才认出他自己的女儿。
But hold your nose,cuz here goes the cold water.
堵住你的鼻子吧，因为这里有冷水。
His hoes don't want him no mo',he's cold product.
这些女人们不在需要他，（因为）他是冷血动物。
They moved on to the next schmo who flows.He nose dove and sold nada.
他们到了下一个随波逐流的傻瓜那里.他鼻子潜入水中却什么都没有
So the soap opera is told and unfolds I suppose it's old ,Poona（partner）,but
the beat goes on
所以故事从此展开。我觉得它实在老掉牙了，伙计，但是我还会跟着节拍继续
Da da dum da dum da da da da...
哒 哒 咚 嗒 咚 哒 哒 哒 哒...
（You'd better) lose yourself in the music,the moment .
你最好在音乐中忘记自我，在这个时刻。
You own it. You 'd better never let it go(go..)
你赢得它，你最好永远不要放走它，
You only get one shot,do not miss your chance to blow,
你只有这一次机会，不要错过引爆众人的机会，
This opportunity comes once in a lifetime yo.
这种机会人生只有一次，哟。
（You'd better) lose yourself in the music,the moment .
你最好在音乐中忘记自我，在这个时刻。
You own it. You'd better never let it go(go..)
你赢得它，你最好永远不要放走它，
You only get one shot,do not miss your chance to blow,
你只有这一次机会，不要错过引爆众人的机会，
This opportunity comes once in a lifetime yo.
这种机会人生只有一次，哟。
No more games,I'm change what you call rage
不再是游戏了，我改变了 就是你们称之为的愤怒
Tear this motherfucking roof off like 2 dogs caged
我就他妈的像两只被关起的狗 掀翻狗笼一样
I was playing in the beginning,
开始我是在玩，
The mood all changed.
（但是现在）风格却却全部变了。
I been chewed up and spit out and booed off stage.
我像口香糖一样被人咀嚼，再吐出来，被嘘下台
But I kept rhyming and step writing the next cypher.
但尽管那样我还得保持镇定而且继续我的下一个节拍。
Best believe somebody's paying the pied piper.
最好坚信被某人挖掘。
All the pain inside amplified by the-.
我所有的内心痛苦被不可逃避的事实放大。
-Fact.that I can't get by with my 9 to -
事实上我再也不能度过这朝九晚五的生活。
-5.And I can't provide the right type of life for my family
还有我不能为我的家庭提供生活的过正常的生活
Cuz man,these goddam food stamps don't buy diapers
所以说 伙计，这些该死的粮票连尿布都买不起。
And it's no movie,there’s no Mekhi Phifer,this is my life
然而这不是电影，这里没有Mekhi Phifer（黑人 8英里 里边的电影演员），这就是我的生活。
And these times are so hard.And it's getting even harder trying to feed and
water my seed plus.
这些时间是如此的艰难，让我的种子开花结果变的越来越困难
teeter-totter Caught up between bein' a father and a prima donna
我的角色在一个父亲和一个自负的家伙之间艰难蹒跚的徘徊，
Baby mama drama's screaming on and too much for me to wanna(want).
孩子 妈妈 尖声喊叫着 太多关于我想要的
Stay in one spot,Another day or not
停留在一个场所，千篇一律的每一天
Has gotten me to the point,I'm like a snail I've got .
他为做到这一点，我有时象个蜗牛。
So formulate a plot or I end up in jail or shot
所以要想出个计划了，否则我的结局就是坐牢或被射杀。
Success is my only motherfucking option,failure's not
成功是我他妈的唯一的选择，不可以失败
Mom,I love U,but this trail has got to go.
妈妈我爱你，但这拖车真应该滚蛋。
I cannot grow old in Salem's Lot.
我不能一直在撒冷镇长大（Salem' Lot是斯蒂芬金的著名恐怖小说中的吸血鬼镇，
说明Eminem对自己成长环境的痛恨）。
So here I go is my shot.
所以我把握我的这次机会。
Feet fail me not cuz maybe the only opportunity that I got
我不能失足或者失败 因为也许这是我唯一拥有的 这仅有一次的机会
（You'd better) lose yourself in the music,the moment .
你最好在音乐中忘记自我，在这个时刻。
You own it. You'd better never let it go(go..)
你赢得它，你最好永远不要放走它，
You only get one shot,do not miss your chance to blow,
你只有这一次机会，不要错过引爆众人的机会，
This opportunity comes once in a lifetime yo.
这种机会人生只有一次，哟。
（You'd better) lose yourself in the music,the moment .
你最好在音乐中忘记自我，在这个时刻。
You own it. You'd better never let it go(go..)
你赢得它，你最好永远不要放走它，(走)
You only get one shot,do not miss your chance to blow,
你只有这一次机会，不要错过引爆众人的机会，
This opportunity comes once in a lifetime yo.
这种机会人生只有一次，哟。
You can do anything you set your mind to,man
你只要坚持头脑中的信念，任何事情都能成功，伙计
| 35.430851 | 152 | 0.751989 | eng_Latn | 0.970876 |
d3d97a8c8afbb8d31f9b49f6fed30e8ea1ef4f95 | 21 | md | Markdown | README.md | ahadxo/Ahadxo | f847b459d2e54b2c9539e3d5f9911a966765060b | [
"Apache-2.0"
] | null | null | null | README.md | ahadxo/Ahadxo | f847b459d2e54b2c9539e3d5f9911a966765060b | [
"Apache-2.0"
] | null | null | null | README.md | ahadxo/Ahadxo | f847b459d2e54b2c9539e3d5f9911a966765060b | [
"Apache-2.0"
] | null | null | null | # Ahadxo
Testing Git
| 7 | 11 | 0.761905 | eng_Latn | 0.640643 |
d3da82ee9ee45e25d203306278c77e0a73d33676 | 20,555 | md | Markdown | docs/framework/winforms/advanced/application-settings-architecture.md | homard/docs.fr-fr | 1ea296656ac8513433dd186266b80b1d04487190 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/winforms/advanced/application-settings-architecture.md | homard/docs.fr-fr | 1ea296656ac8513433dd186266b80b1d04487190 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/winforms/advanced/application-settings-architecture.md | homard/docs.fr-fr | 1ea296656ac8513433dd186266b80b1d04487190 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Architecture des paramètres d'application
ms.date: 03/30/2017
dev_langs:
- csharp
- vb
helpviewer_keywords:
- application settings [Windows Forms], architecture
ms.assetid: c8eb2ad0-fac6-4ea2-9140-675a4a44d562
ms.openlocfilehash: 769077ddbe42d4d774d359de75417bdca6bcaeb5
ms.sourcegitcommit: 3d5d33f384eeba41b2dff79d096f47ccc8d8f03d
ms.translationtype: MT
ms.contentlocale: fr-FR
ms.lasthandoff: 05/04/2018
ms.locfileid: "33520001"
---
# <a name="application-settings-architecture"></a>Architecture des paramètres d'application
Cette rubrique décrit le fonctionnement de l’architecture Paramètres d’application et explore des fonctionnalités avancées de l’architecture telles que les paramètres groupés et les clés de paramètres.
L’architecture des paramètres d’application prend en charge la définition des paramètres fortement typés avec l’application ou la portée utilisateur, et la persistance des paramètres entre les sessions d’application. L’architecture fournit un moteur de persistance par défaut pour enregistrer les paramètres et les charger à partir du système de fichiers local. L’architecture définit également les interfaces qui fournissent un moteur de persistance personnalisé.
Des interfaces sont fournies afin de permettre aux composants personnalisés de conserver leurs propres paramètres lorsqu’ils sont hébergés dans une application. À l’aide de clés de paramètres, les composants peuvent séparer les paramètres pour plusieurs instances du composant.
## <a name="defining-settings"></a>Définition des paramètres
L’architecture des paramètres d’application est utilisée dans à la fois dans [!INCLUDE[vstecasp](../../../../includes/vstecasp-md.md)] et les Windows Forms, et contient un certain nombre de classes de base qui sont partagées entre les deux environnements. Le plus important est <xref:System.Configuration.SettingsBase>, qui fournit l’accès aux paramètres via une collection et fournit des méthodes de bas niveau pour le chargement et l’enregistrement des paramètres. Chaque environnement implémente sa propre classe dérivée de <xref:System.Configuration.SettingsBase> pour fournir des fonctionnalités de paramètres supplémentaires pour cet environnement. Dans une application Windows Forms, tous les paramètres de l’application doivent être définies sur une classe dérivée de la <xref:System.Configuration.ApplicationSettingsBase> classe, qui ajoute les fonctionnalités suivantes à la classe de base :
- Chargement et enregistrement d’opérations de plus haut niveau
- Prise en charge des paramètres de portée utilisateur
- Rétablissement des paramètres d’un utilisateur aux valeurs par défaut
- Mise à niveau des paramètres à partir d’une version précédente de l’application
- Validation des paramètres, avant leur modification ou leur enregistrement
Les paramètres peuvent être décrits à l’aide d’un nombre d’attributs définis dans le <xref:System.Configuration> espace de noms ; ceux-ci sont décrits dans [attributs des paramètres d’Application](../../../../docs/framework/winforms/advanced/application-settings-attributes.md). Lorsque vous définissez un paramètre, vous devez l’appliquer avec l’option <xref:System.Configuration.ApplicationScopedSettingAttribute> ou <xref:System.Configuration.UserScopedSettingAttribute>, qui décrit si le paramètre s’applique à l’application entière ou uniquement à l’utilisateur actuel.
L’exemple de code suivant définit une classe de paramètres personnalisés avec un paramètre unique, `BackgroundColor`.
[!code-csharp[ApplicationSettings.Create#1](../../../../samples/snippets/csharp/VS_Snippets_Winforms/ApplicationSettings.Create/CS/MyAppSettings.cs#1)]
[!code-vb[ApplicationSettings.Create#1](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/ApplicationSettings.Create/VB/MyAppSettings.vb#1)]
## <a name="settings-persistence"></a>Persistance des paramètres
Le <xref:System.Configuration.ApplicationSettingsBase> classe de ne pas lui-même conserver ou de charger les paramètres ; cette tâche incombe au fournisseur de paramètres, une classe qui dérive de <xref:System.Configuration.SettingsProvider>. Si une classe dérivée de <xref:System.Configuration.ApplicationSettingsBase> ne spécifie pas de fournisseur de paramètres via le <xref:System.Configuration.SettingsProviderAttribute>, le fournisseur par défaut, <xref:System.Configuration.LocalFileSettingsProvider>, est utilisé.
Le système de configuration fourni initialement avec [!INCLUDE[dnprdnshort](../../../../includes/dnprdnshort-md.md)] prend en charge les données de configuration d’application statiques via le fichier machine.config de l’ordinateur local ou dans un fichier `app.`exe.config que vous déployez avec votre application. La <xref:System.Configuration.LocalFileSettingsProvider> classe étend cette prise en charge native des manières suivantes :
- Les paramètres de portée d’application peuvent être stockés dans des fichiers machine.config ou `app.`exe.config. Machine.config est toujours en lecture seule, tandis que `app`.exe.config est limité par des considérations de sécurité en lecture seule pour la plupart des applications.
- Les paramètres de portée utilisateur peuvent être stockés dans des fichiers `app`.exe.config, fichiers, auquel cas ils sont traités comme des valeurs par défaut statiques.
- Les paramètres de portée utilisateur non définis par défaut sont stockés dans un nouveau fichier, *user*.config, où *user* est le nom d’utilisateur de la personne qui exécute actuellement l’application. Vous pouvez spécifier une valeur par défaut pour un paramètre de portée utilisateur avec <xref:System.Configuration.DefaultSettingValueAttribute>. Étant donné que les paramètres de portée utilisateur changent souvent pendant l’exécution d’applications, `user`.config est toujours accessible en lecture/écriture.
Ces trois fichiers de configuration stockent les paramètres au format XML. L’élément XML de niveau supérieur pour les paramètres de portée d’application est `<appSettings>`, tandis que `<userSettings>` est utilisé pour les paramètres de portée utilisateur. Un fichier `app`.exe.config contenant les paramètres de portée d’application et les valeurs par défaut pour les paramètres de portée utilisateur ressemblerait à ceci :
```xml
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<configSections>
<sectionGroup name="applicationSettings" type="System.Configuration.ApplicationSettingsGroup, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" >
<section name="WindowsApplication1.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
</sectionGroup>
<sectionGroup name="userSettings" type="System.Configuration.UserSettingsGroup, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" >
<section name="WindowsApplication1.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowExeDefinition="MachineToLocalUser" />
</sectionGroup>
</configSections>
<applicationSettings>
<WindowsApplication1.Properties.Settings>
<setting name="Cursor" serializeAs="String">
<value>Default</value>
</setting>
<setting name="DoubleBuffering" serializeAs="String">
<value>False</value>
</setting>
</WindowsApplication1.Properties.Settings>
</applicationSettings>
<userSettings>
<WindowsApplication1.Properties.Settings>
<setting name="FormTitle" serializeAs="String">
<value>Form1</value>
</setting>
<setting name="FormSize" serializeAs="String">
<value>595, 536</value>
</setting>
</WindowsApplication1.Properties.Settings>
</userSettings>
</configuration>
```
Pour une définition des éléments dans la section Paramètres d’application d’un fichier de configuration, consultez [Schéma des paramètres d'application](../../../../docs/framework/configure-apps/file-schema/application-settings-schema.md).
### <a name="settings-bindings"></a>Liaisons de paramètres
Les paramètres d’application utilisent l’architecture de liaison de données Windows Forms pour fournir une communication bidirectionnelle pour les mises à jour des paramètres entre les composants et l’objet de paramètres. Si vous utilisez Visual Studio pour créer des paramètres d’application et les affecter aux propriétés du composant, ces liaisons sont générées automatiquement.
Vous pouvez uniquement lier un paramètre d’application à un composant qui prend en charge la <xref:System.Windows.Forms.IBindableComponent> interface. En outre, le composant doit implémenter un événement de modification pour une propriété liée spécifique ou informer les paramètres d’application que la propriété est modifiée par le biais du <xref:System.ComponentModel.INotifyPropertyChanged> interface. Si le composant n’implémente pas <xref:System.Windows.Forms.IBindableComponent> et que vous établissez une liaison via Visual Studio, les propriétés liées définira la première fois, mais ne met pas à jour. Si le composant implémente <xref:System.Windows.Forms.IBindableComponent> mais ne notifications de modification non prise en charge de propriété, la liaison ne met pas à jour dans le fichier de paramètres lorsque la propriété est modifiée.
Certains composants Windows Forms, telles que <xref:System.Windows.Forms.ToolStripItem>, ne prennent pas en charge les liaisons de paramètres.
### <a name="settings-serialization"></a>Sérialisation de paramètres
Lorsque <xref:System.Configuration.LocalFileSettingsProvider> doit enregistrer des paramètres sur le disque, il effectue les actions suivantes :
1. Utilise la réflexion pour examiner toutes les propriétés définies sur votre <xref:System.Configuration.ApplicationSettingsBase> classe dérivée, recherche de celles qui sont appliquées avec l’option <xref:System.Configuration.ApplicationScopedSettingAttribute> ou <xref:System.Configuration.UserScopedSettingAttribute>.
2. Sérialise la propriété sur le disque. Il tente d’appeler le <xref:System.ComponentModel.TypeConverter.ConvertToString%2A> ou <xref:System.ComponentModel.TypeConverter.ConvertFromString%2A> sur le type associé à <xref:System.ComponentModel.TypeConverter>. Si cela ne réussit pas, la sérialisation XML est utilisée à la place.
3. Détermine quels paramètres vont dans quels fichiers, selon l’attribut du paramètre.
Si vous implémentez votre propre classe de paramètres, vous pouvez utiliser la <xref:System.Configuration.SettingsSerializeAsAttribute> pour marquer un paramètre pour la sérialisation binaire ou personnalisée à l’aide du <xref:System.Configuration.SettingsSerializeAs> énumération. Pour plus d’informations sur la création de votre propre classe de paramètres en code, consultez [Guide pratique : Créer des paramètres d'application](../../../../docs/framework/winforms/advanced/how-to-create-application-settings.md).
### <a name="settings-file-locations"></a>Emplacements des fichiers de paramètres
L’emplacement des fichiers `app`.exe.config et *user*.config varie en fonction de la façon dont l’application est installée. Pour une application Windows Forms copiée sur l’ordinateur local, `app`. exe.config résidera dans le même répertoire que le répertoire de base du fichier exécutable principal de l’application, et *utilisateur*.config résidera dans le emplacement spécifié par le <xref:System.Windows.Forms.Application.LocalUserAppDataPath%2A?displayProperty=nameWithType> propriété. Pour une application installée au moyen de [!INCLUDE[ndptecclick](../../../../includes/ndptecclick-md.md)], ces deux fichiers résident dans le répertoire de données [!INCLUDE[ndptecclick](../../../../includes/ndptecclick-md.md)] situé sous %InstallRoot%\Documents and Settings\\*nom d’utilisateur*\Local Settings.
L’emplacement de stockage de ces fichiers est légèrement différent si un utilisateur a activé les profils itinérants, ce qui permet à un utilisateur de définir différents paramètres d’application et Windows lorsqu’il utilise d’autres ordinateurs dans un domaine. Dans ce cas, les applications [!INCLUDE[ndptecclick](../../../../includes/ndptecclick-md.md)] et non [!INCLUDE[ndptecclick](../../../../includes/ndptecclick-md.md)] auront leurs fichiers `app`.exe.config et *user*.config stockés sous %InstallRoot%\Documents and Settings\\*nom d’utilisateur*\Application Data.
Pour plus d’informations sur le fonctionnement de la fonctionnalité Paramètres d’application avec la nouvelle technologie de déploiement, consultez [ClickOnce et paramètres d’application](/visualstudio/deployment/clickonce-and-application-settings). Pour plus d'informations sur le répertoire de données [!INCLUDE[ndptecclick](../../../../includes/ndptecclick-md.md)], consultez [Accès aux données locales et distantes dans les applications ClickOnce](/visualstudio/deployment/accessing-local-and-remote-data-in-clickonce-applications).
## <a name="application-settings-and-security"></a>Paramètres d’application et sécurité
Les paramètres d’application sont conçus pour fonctionner en mode de confiance partielle, un environnement restreint qui est la configuration par défaut pour les applications Windows Forms hébergées sur Internet ou sur un intranet. Aucune autorisation spéciale au-delà de la confiance partielle n’est nécessaire pour utiliser les paramètres d’application avec le fournisseur de paramètres par défaut.
Lorsque les paramètres d’application sont utilisés dans une application [!INCLUDE[ndptecclick](../../../../includes/ndptecclick-md.md)], le fichier `user`.config est stocké dans le répertoire de données [!INCLUDE[ndptecclick](../../../../includes/ndptecclick-md.md)]. La taille du fichier `user`.config de l’application ne peut pas dépasser le quota de répertoire de données défini par [!INCLUDE[ndptecclick](../../../../includes/ndptecclick-md.md)]. Pour plus d'informations, consultez [ClickOnce et paramètres d’application](/visualstudio/deployment/clickonce-and-application-settings).
## <a name="custom-settings-providers"></a>Fournisseurs de paramètres personnalisés
Dans l’architecture de paramètres d’Application, il est un couplage lâche entre les paramètres des applications classe wrapper, dérivée de <xref:System.Configuration.ApplicationSettingsBase>, et le fournisseur de paramètres associé ou des fournisseurs, dérivés <xref:System.Configuration.SettingsProvider>. Cette association est définie uniquement par le <xref:System.Configuration.SettingsProviderAttribute> appliqués à la classe wrapper ou à ses propriétés individuelles. Si les paramètres de fournisseur n’est pas explicitement spécifié, le fournisseur par défaut, <xref:System.Configuration.LocalFileSettingsProvider>, est utilisé. Par conséquent, cette architecture prend en charge la création et l’utilisation de fournisseurs de paramètres personnalisés.
Par exemple, supposons que vous souhaitez développer et utiliser `SqlSettingsProvider`, un fournisseur qui stockera toutes les données de paramètres dans une base de données Microsoft SQL Server. Votre <xref:System.Configuration.SettingsProvider>-classe dérivée reçoit ces informations dans sa `Initialize` méthode en tant que paramètre de type <xref:System.Collections.Specialized.NameValueCollection?displayProperty=nameWithType>. Vous implémentez ensuite la <xref:System.Configuration.SettingsProvider.GetPropertyValues%2A> pour récupérer vos paramètres du magasin de données, et <xref:System.Configuration.SettingsProvider.SetPropertyValues%2A> à les enregistrer. Votre fournisseur peut utiliser le <xref:System.Configuration.SettingsPropertyCollection> fourni à <xref:System.Configuration.SettingsProvider.GetPropertyValues%2A> pour déterminer le nom de la propriété, de type et de portée, ainsi que tout autre attribut de paramètres défini pour cette propriété.
Votre fournisseur devra implémenter une propriété et une méthode dont les implémentations peuvent ne pas être évidentes. Le <xref:System.Configuration.SettingsProvider.ApplicationName%2A> propriété est une propriété abstraite de <xref:System.Configuration.SettingsProvider>; vous devez la programmer pour retourner les éléments suivants :
[!code-csharp[ApplicationSettings.Architecture#2](../../../../samples/snippets/csharp/VS_Snippets_Winforms/ApplicationSettings.Architecture/CS/DummyClass.cs#2)]
[!code-vb[ApplicationSettings.Architecture#2](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/ApplicationSettings.Architecture/VB/DummyProviderClass.vb#2)]
Votre classe dérivée doit également implémenter une méthode `Initialize` qui n’accepte aucun argument et ne retourne aucune valeur. Cette méthode n’est pas définie par <xref:System.Configuration.SettingsProvider>.
Enfin, vous implémentez <xref:System.Configuration.IApplicationSettingsProvider> sur votre fournisseur pour prendre en charge l’actualisation des paramètres, rétablir leurs valeurs par défaut et la mise à niveau des paramètres à partir d’une version d’application à l’autre.
Une fois que vous avez implémenté et compilé votre fournisseur, vous devez demander à votre classe de paramètres d’utiliser ce fournisseur au lieu de la valeur par défaut. Cela via le <xref:System.Configuration.SettingsProviderAttribute>. Si l’application à une classe de paramètres, le fournisseur est utilisé pour chaque paramètre de la classe définit ; Si appliqué aux paramètres individuels, l’architecture des paramètres d’Application utilise ce fournisseur pour ces paramètres uniquement et <xref:System.Configuration.LocalFileSettingsProvider> pour le reste. L’exemple de code suivant montre comment indiquer à la classe de paramètres d’utiliser votre fournisseur personnalisé.
[!code-csharp[ApplicationSettings.Architecture#1](../../../../samples/snippets/csharp/VS_Snippets_Winforms/ApplicationSettings.Architecture/CS/DummyClass.cs#1)]
[!code-vb[ApplicationSettings.Architecture#1](../../../../samples/snippets/visualbasic/VS_Snippets_Winforms/ApplicationSettings.Architecture/VB/DummyProviderClass.vb#1)]
Un fournisseur peut être appelé à partir de plusieurs threads simultanément, mais il écrira toujours au même emplacement de stockage. Par conséquent, l’architecture de paramètres d’application n’instanciera jamais qu’une seule instance de votre classe de fournisseur.
> [!IMPORTANT]
> Vous devez vous assurer que votre fournisseur est thread-safe et autorise un seul thread à la fois à écrire dans les fichiers de configuration.
Votre fournisseur n’a pas besoin de prend en charge tous les paramètres d’attributs définis dans le <xref:System.Configuration?displayProperty=nameWithType> espace de noms, même s’il doit à une prise en charge minimale <xref:System.Configuration.ApplicationScopedSettingAttribute> et <xref:System.Configuration.UserScopedSettingAttribute>et doit prennent également en charge <xref:System.Configuration.DefaultSettingValueAttribute>. Pour les attributs qu’il ne prend pas en charge, votre fournisseur doit simplement échouer sans notification. Il ne doit pas lever une exception. Si la classe de paramètres utilise une combinaison non valide d’attributs, toutefois, telles que l’application <xref:System.Configuration.ApplicationScopedSettingAttribute> et <xref:System.Configuration.UserScopedSettingAttribute> sur le même paramètre, votre fournisseur doit lever une exception et s’arrêter.
## <a name="see-also"></a>Voir aussi
<xref:System.Configuration.ApplicationSettingsBase>
<xref:System.Configuration.SettingsProvider>
<xref:System.Configuration.LocalFileSettingsProvider>
[Vue d'ensemble des paramètres d'application](../../../../docs/framework/winforms/advanced/application-settings-overview.md)
[Paramètres d'application pour les contrôles personnalisés](../../../../docs/framework/winforms/advanced/application-settings-for-custom-controls.md)
[ClickOnce et paramètres d’application](/visualstudio/deployment/clickonce-and-application-settings)
[Schéma des paramètres d'application](../../../../docs/framework/configure-apps/file-schema/application-settings-schema.md)
| 130.923567 | 970 | 0.79387 | fra_Latn | 0.926454 |
d3dafdc3d00d36e432fcd4db814d1bf29526dc98 | 13 | md | Markdown | README.md | zakhra/GSI-cour1- | 7e2331fbd837aad8134e1439f115ed44796088cb | [
"CC0-1.0"
] | null | null | null | README.md | zakhra/GSI-cour1- | 7e2331fbd837aad8134e1439f115ed44796088cb | [
"CC0-1.0"
] | null | null | null | README.md | zakhra/GSI-cour1- | 7e2331fbd837aad8134e1439f115ed44796088cb | [
"CC0-1.0"
] | null | null | null | # GSI-cour1-
| 6.5 | 12 | 0.615385 | vie_Latn | 0.501551 |
d3dbfb8de07618470ed27f7695a45741277de457 | 1,384 | md | Markdown | .github/ISSUE_TEMPLATE/bug_report.md | Yasuke/plutus-apps | 2e4e5e4291bc356aebf6865306e8f12c21afd7b4 | [
"Apache-2.0"
] | null | null | null | .github/ISSUE_TEMPLATE/bug_report.md | Yasuke/plutus-apps | 2e4e5e4291bc356aebf6865306e8f12c21afd7b4 | [
"Apache-2.0"
] | null | null | null | .github/ISSUE_TEMPLATE/bug_report.md | Yasuke/plutus-apps | 2e4e5e4291bc356aebf6865306e8f12c21afd7b4 | [
"Apache-2.0"
] | null | null | null | ---
name: Bug report
about: Report a bug
title: ""
labels: bug
assignees: ''
---
## Summary
A clear and specific description of what the bug is.
## Steps to reproduce
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
## Expected behavior
A clear and concise description of what you expected to happen.
## What have you tried to resolve this error?
What steps have you taken to try and understand the issue? Context will enable
us to help you faster, or, even better, will help you solve it yourself!
- Have you looked over our [readme](https://github.com/input-output-hk/plutus-apps/blob/main/README.adoc), [documentation](https://plutus-apps.readthedocs.io/en/latest/), and [technical report](https://github.com/input-output-hk/plutus-apps/blob/main/README.adoc#specifications-and-design)?
- Have you tried searching on [cardano stackexchange](https://cardano.stackexchange.com/)?
## System info (please complete the following information):
- OS: [e.g. Ubuntu]
- Version [e.g. 20.04]
- Plutus version or commit hash
## Screenshots and attachments
- If applicable, add screenshots, config files and/or logs to help explain the problem.
- If the issue is related to the Plutus Playground, please include a link to a gist that reproduces the issue
## Additional context
Add any other context about the problem here.
| 29.446809 | 290 | 0.741329 | eng_Latn | 0.983804 |
d3dc6a1292e391c26db77cf92be5773b62bf58a2 | 2,928 | md | Markdown | entities/Systems.Core.TextTranslations.md | NTBIS-user/model | 833cc999bb6b908a16fed3e5676da74bc6254cf1 | [
"CC-BY-4.0"
] | null | null | null | entities/Systems.Core.TextTranslations.md | NTBIS-user/model | 833cc999bb6b908a16fed3e5676da74bc6254cf1 | [
"CC-BY-4.0"
] | null | null | null | entities/Systems.Core.TextTranslations.md | NTBIS-user/model | 833cc999bb6b908a16fed3e5676da74bc6254cf1 | [
"CC-BY-4.0"
] | null | null | null | ---
uid: Systems.Core.TextTranslations
---
# Systems.Core.TextTranslations Entity
**Namespace:** [Systems.Core](Systems.Core.md)
Obsolete. Not used. Entity: Gen_Text_Translations
## Default Visualization
Default Display Text Format:
_{ColumnName:T}_
Default Search Member:
__
## Aggregate
An [aggregate](https://docs.erp.net/tech/advanced/concepts/aggregates.html) is a cluster of domain objects that can be treated as a single unit.
Aggregate Tree
* [Systems.Core.TextTranslations](Systems.Core.TextTranslations.md)
## Attributes
| Name | Type | Description |
| ---- | ---- | --- |
| [ColumnName](Systems.Core.TextTranslations.md#columnname) | string (128) | Obsolete. Not used. `Required` `Filter(eq)`
| [Id](Systems.Core.TextTranslations.md#id) | guid |
| [Language](Systems.Core.TextTranslations.md#language) | string (50) | Obsolete. Not used. `Required` `Filter(eq)`
| [RowId](Systems.Core.TextTranslations.md#rowid) | guid | Obsolete. Not used. `Required` `Filter(multi eq)`
| [TableName](Systems.Core.TextTranslations.md#tablename) | string (128) | Obsolete. Not used. `Required` `Filter(eq)` `ORD` `ReadOnly`
| [TranslatedText](Systems.Core.TextTranslations.md#translatedtext) | string (254) __nullable__ | Obsolete. Not used. `Filter(eq)`
## Attribute Details
### ColumnName
Obsolete. Not used. `Required` `Filter(eq)`
_Type_: **string (128)**
_Supported Filters_: **Equals**
_Supports Order By_: **False**
_Maximum Length_: **128**
### Id
_Type_: **guid**
_Indexed_: **True**
_Supported Filters_: **Equals, EqualsIn**
_Default Value_: **NewGuid**
### Language
Obsolete. Not used. `Required` `Filter(eq)`
_Type_: **string (50)**
_Supported Filters_: **Equals**
_Supports Order By_: **False**
_Maximum Length_: **50**
### RowId
Obsolete. Not used. `Required` `Filter(multi eq)`
_Type_: **guid**
_Supported Filters_: **Equals, EqualsIn**
### TableName
Obsolete. Not used. `Required` `Filter(eq)` `ORD` `ReadOnly`
_Type_: **string (128)**
_Indexed_: **True**
_Supported Filters_: **Equals**
_Supports Order By_: **True**
_Maximum Length_: **128**
### TranslatedText
Obsolete. Not used. `Filter(eq)`
_Type_: **string (254) __nullable__**
_Supported Filters_: **Equals**
_Supports Order By_: **False**
_Maximum Length_: **254**
## Business Rules
[!list limit=1000 erp.entity=Systems.Core.TextTranslations erp.type=business-rule default-text="None"]
## Front-End Business Rules
[!list limit=1000 erp.entity=Systems.Core.TextTranslations erp.type=front-end-business-rule default-text="None"]
## API
Domain API Query:
<https://demodb.my.erp.net/api/domain/odata/Systems_Core_TextTranslations?$top=10>
Domain API Query Builder:
<https://demodb.my.erp.net/api/domain/querybuilder#Systems_Core_TextTranslations?$top=10>
| 27.885714 | 147 | 0.681352 | yue_Hant | 0.342145 |
d3dc78839802048c57440ea133d8218c8616f340 | 3,239 | md | Markdown | docs/odbc/reference/develop-app/determining-the-target-dbmss-and-drivers.md | KochertNinja/sql-docs | 04c031f7411aa33e2174be11dfced7feca8fbcda | [
"CC-BY-4.0",
"MIT"
] | 2 | 2019-02-08T05:59:39.000Z | 2019-02-12T03:27:49.000Z | docs/odbc/reference/develop-app/determining-the-target-dbmss-and-drivers.md | KochertNinja/sql-docs | 04c031f7411aa33e2174be11dfced7feca8fbcda | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/odbc/reference/develop-app/determining-the-target-dbmss-and-drivers.md | KochertNinja/sql-docs | 04c031f7411aa33e2174be11dfced7feca8fbcda | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-04-02T15:42:37.000Z | 2019-04-02T15:42:37.000Z | ---
title: "Determining the Target DBMSs and Drivers | Microsoft Docs"
ms.custom: ""
ms.date: "01/19/2017"
ms.prod: sql
ms.prod_service: connectivity
ms.reviewer: ""
ms.technology: connectivity
ms.topic: conceptual
helpviewer_keywords:
- "target DBMSs and drivers in interoperability [ODBC]"
- "interoperability [ODBC], target dbmss and drivers"
ms.assetid: 23bee0f6-e12a-4598-b34e-df11a8086829
author: MightyPen
ms.author: genemi
manager: craigg
---
# Determining the Target DBMSs and Drivers
The next question to consider is, what are the target DBMSs for the application, and what drivers are available that support those DBMSs? Because generic applications tend to be highly interoperable, the question of target DBMSs is most applicable to custom and vertical applications. However, the question of target drivers applies to all applications, because drivers vary widely in speed, quality, feature support, and availability. Also, if drivers are to be redistributed with the application, the cost and availability of licensing plans need to be considered.
For many custom applications, the target DBMSs are obvious: They are existing DBMSs that the application is designed to access. DBMSs to which future migration is planned should also be considered. However, the major question for these applications is which driver or drivers to use with them. For other custom applications - those which are not designed to access an existing DBMS - the target DBMSs can be chosen based on feature support, concurrent user support, driver availability, and affordability.
For vertical applications, the target DBMSs are usually chosen based on feature support, driver availability, and market. For example, a vertical application designed for small businesses must target DBMSs that are affordable to those businesses; a vertical application designed as an add-on to existing DBMSs must target widely used DBMSs.
When choosing target DBMSs, the differences between desktop and server databases should be considered. Desktop databases such as dBASE, Paradox, and Btrieve are less powerful than server databases. Because they are generally accessed through the less powerful SQL engines found in most file-based drivers, they often lack full transaction support, support fewer concurrent users, and have limited SQL. However, they are inexpensive and have a large installed base.
Server databases such as Oracle, DB2, and SQL Server provide full transaction support, support many concurrent users, and have rich SQL. They are much more expensive and have a smaller installed base. On the other hand, software prices tend to be higher, somewhat offsetting a smaller potential market.
Thus, target DBMSs sometimes can be chosen based on the features required by the application and the application's target market. For example, an order entry system for large corporations might not target desktop databases because these lack adequate transaction support. A similar system designed for small businesses might exclude most server databases on the basis of cost. And developers of generic applications might target both but avoid using the advanced features found in server databases.
| 107.966667 | 569 | 0.800864 | eng_Latn | 0.999384 |
d3dcd57a4567aee1a5e072bf214e2259fbc0de1f | 1,640 | md | Markdown | README.md | esqu1/Rusty-Rubik | 1e32829e83c662816bd85f6c37d6f774a15e3aea | [
"MIT"
] | 2 | 2020-06-16T00:53:42.000Z | 2020-08-01T00:15:27.000Z | README.md | esqu1/Rusty-Rubik | 1e32829e83c662816bd85f6c37d6f774a15e3aea | [
"MIT"
] | null | null | null | README.md | esqu1/Rusty-Rubik | 1e32829e83c662816bd85f6c37d6f774a15e3aea | [
"MIT"
] | 1 | 2020-11-21T10:47:59.000Z | 2020-11-21T10:47:59.000Z | Rusty Rubik
==
[](https://circleci.com/gh/esqu1/Rusty-Rubik)
**Rusty Rubik** is a Rubik's Cube solving program implemented in Rust.
[Documentation](https://docs.rs/rusty-rubik/) · [crates.io](http://crates.io/crates/rusty-rubik)
Downloading
===
You can get this repo via cloning through Git:
```
git clone https://github.com/esqu1/Rusty-Rubik
```
Running
===
It is preferable to run the program in release mode, since this will dramatically speed up the search time for a solution. First, build the project:
```
cargo build --release
```
If you don't want to run it in release mode, simply leave out the `--release` flag. You will first need to generate the pruning tables necessary for the IDA solver to run:
```
cargo run --release -- -p
```
This will create pruning tables `corners.pt`, `edges_o.pt`, and `edges_p.pt` in the root directory of the project. To verify that these were generated correctly, run the verification script:
```
./scripts/verify_checksum.sh
```
On my CPU (AMD Ryzen 5 3600 @ 3.6 GHz, 6 cores) the pruning tables take about 10 minutes to generate, so I'm expecting most modern processors should take around 15-20 minutes to finish.
Then you can run the executable in `target/release/rusty-rubik`. You can see the available options using the `--help` flag:
```
./target/release/rusty-rubik --help
```
Documentation
===
The document requires the KaTeX header file to be built with it to
render properly. You can build the documentation for this project via:
```
RUSTDOCFLAGS="--html-in-header header.html" cargo doc --no-deps --open
```
| 34.166667 | 190 | 0.736585 | eng_Latn | 0.977572 |
d3dcef44e23ee1dd862c8b248176b0d1f039e7cc | 519 | md | Markdown | packages/lite/README.md | sigfrido45/greenter | 57d223928db2115c1c2c459f3f7f8581e760f9ff | [
"MIT"
] | 110 | 2017-09-16T04:08:32.000Z | 2020-04-17T20:39:36.000Z | packages/lite/README.md | sigfrido45/greenter | 57d223928db2115c1c2c459f3f7f8581e760f9ff | [
"MIT"
] | 101 | 2017-07-19T14:38:54.000Z | 2020-04-23T01:13:22.000Z | packages/lite/README.md | sigfrido45/greenter | 57d223928db2115c1c2c459f3f7f8581e760f9ff | [
"MIT"
] | 85 | 2017-07-17T17:11:05.000Z | 2020-04-12T08:07:19.000Z | # Greenter Lite
[](https://github.com/thegreenter/greenter)
Versión de Greenter que solo incluye los paquetes minimos requeridos para generar y enviar comprobantes electrónicos.
## Recursos
- [Documentación](https://greenter.dev/)
- [Reportar un error](https://github.com/thegreenter/greenter/issues) o enviar un [pull request](https://github.com/thegreenter/greenter/pulls) al [repositorio principal de greenter](https://github.com/thegreenter/greenter).
| 51.9 | 224 | 0.7842 | spa_Latn | 0.447186 |
d3dd00d3e16af3a6a079e1c7fa3f3c4a2bc66827 | 35 | md | Markdown | README.md | Darkstrumn/public | eb3b835234aba6c8de27ae4d3a7ae9f6bc893235 | [
"MIT"
] | null | null | null | README.md | Darkstrumn/public | eb3b835234aba6c8de27ae4d3a7ae9f6bc893235 | [
"MIT"
] | null | null | null | README.md | Darkstrumn/public | eb3b835234aba6c8de27ae4d3a7ae9f6bc893235 | [
"MIT"
] | null | null | null | # public
primary public repo-space
| 11.666667 | 25 | 0.8 | eng_Latn | 0.96741 |
d3de131db3162ec392de2d287e9e60ccc5d02a56 | 675 | md | Markdown | README.md | bibekuchiha/Predict-Titanic-Survival | dd937374809bcb50d1518f102ecd3054cceacfb2 | [
"MIT"
] | null | null | null | README.md | bibekuchiha/Predict-Titanic-Survival | dd937374809bcb50d1518f102ecd3054cceacfb2 | [
"MIT"
] | null | null | null | README.md | bibekuchiha/Predict-Titanic-Survival | dd937374809bcb50d1518f102ecd3054cceacfb2 | [
"MIT"
] | null | null | null | # Predict Titanic Survival
The RMS Titanic set sail on its maiden voyage in 1912, crossing the Atlantic from Southampton, England to New York City. The ship never completed the voyage, sinking to the bottom of the Atlantic Ocean after hitting an iceberg, bringing down 1,502 of 2,224 passengers onboard.
In this project we will create a Logistic Regression model that predicts which passengers survived the sinking of the Titanic, based on features like age and class.
The data we will be using for training our model is provided by [Kaggle](https://www.kaggle.com/c/titanic). Feel free to make the model better on your own and submit it to the Kaggle Titanic competition!
| 96.428571 | 276 | 0.8 | eng_Latn | 0.999196 |
d3de268393935cd707b83a49eadabd43009878ad | 571 | md | Markdown | catalog/planet-blood/en-US_planet-blood.md | htron-dev/baka-db | cb6e907a5c53113275da271631698cd3b35c9589 | [
"MIT"
] | 3 | 2021-08-12T20:02:29.000Z | 2021-09-05T05:03:32.000Z | catalog/planet-blood/en-US_planet-blood.md | zzhenryquezz/baka-db | da8f54a87191a53a7fca54b0775b3c00f99d2531 | [
"MIT"
] | 8 | 2021-07-20T00:44:48.000Z | 2021-09-22T18:44:04.000Z | catalog/planet-blood/en-US_planet-blood.md | zzhenryquezz/baka-db | da8f54a87191a53a7fca54b0775b3c00f99d2531 | [
"MIT"
] | 2 | 2021-07-19T01:38:25.000Z | 2021-07-29T08:10:29.000Z | # Planet Blood
- **type**: manhwa
- **volumes**: 10
## Tags
- action
- fantasy
- sci-fi
## Authors
- Kim
- Tae Hyung (Story & Art)
## Sinopse
After the 5th World War comes to an end, 46% of humans have been wiped off the face of the earth. Because of contamination, the survivors of this war colonize the moon and Mars with plans to move back to Earth after they purify the planet.
(Source: Tokyopop)
## Links
- [My Anime list](https://myanimelist.net/manga/479/Planet_Blood)
| 20.392857 | 239 | 0.690018 | eng_Latn | 0.945269 |
d3de795f28d38601001289dd3c12555a59f97822 | 635 | md | Markdown | README.md | ormanli/agitr-examples | d0ec22144548c6e9e4b47ce28abae9622af045bc | [
"WTFPL"
] | 17 | 2015-02-13T10:34:34.000Z | 2021-03-23T13:24:34.000Z | README.md | ormanli/agitr-examples | d0ec22144548c6e9e4b47ce28abae9622af045bc | [
"WTFPL"
] | null | null | null | README.md | ormanli/agitr-examples | d0ec22144548c6e9e4b47ce28abae9622af045bc | [
"WTFPL"
] | 7 | 2015-12-28T23:00:52.000Z | 2020-03-29T13:39:20.000Z | agitr-examples
==============
### A Gentle Introduction to ROS Examples in Rospy.
I begin studying ROS for my master thesis. This fantastic book called [A Gentle Introduction to ROS](http://www.cse.sc.edu/~jokane/agitr/) was very helping for me. Examples in this written in C++. I am going to code in Python. So I rewrite examples in Python. I tried to not change variable and function names. Also keep same statement order to make codes understandable by looking C++ versions.
Don't forget to make python script executable or ros can't run python code. Also don't forget .py suffix.
```
rosrun package-name executable-name.py
```
| 48.846154 | 395 | 0.748031 | eng_Latn | 0.990097 |
d3deaa37e3557b77b8b390fc33cd022d868c22dd | 4,525 | md | Markdown | docs/pipelines/tasks/deploy/azure-powershell.md | simoneb/azure-devops-docs | ea167e04c715d9cb21e0ae31ec7d7aea5686f8e6 | [
"CC-BY-4.0",
"MIT"
] | 3 | 2021-06-03T06:50:02.000Z | 2021-08-13T13:43:32.000Z | docs/pipelines/tasks/deploy/azure-powershell.md | simoneb/azure-devops-docs | ea167e04c715d9cb21e0ae31ec7d7aea5686f8e6 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-05-25T14:17:27.000Z | 2021-05-25T14:17:27.000Z | docs/pipelines/tasks/deploy/azure-powershell.md | simoneb/azure-devops-docs | ea167e04c715d9cb21e0ae31ec7d7aea5686f8e6 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-04-18T02:35:18.000Z | 2021-04-18T02:35:18.000Z | ---
title: Azure PowerShell task
description: Run a PowerShell script within an Azure environment
ms.topic: reference
ms.assetid: 72A1931B-EFFB-4D2E-8FD8-F8472A07CB62
ms.custom: seodec18
ms.author: ronai
author: RoopeshNair
ms.date: 04/22/2020
monikerRange: 'azure-devops'
---
# Azure PowerShell task
**Azure Pipelines**
Use this task to run a PowerShell script within an Azure environment. The Azure context is authenticated with the provided Azure Resource Manager service connection.
::: moniker range="> tfs-2018"
## YAML snippet
[!INCLUDE [temp](../includes/yaml/AzurePowerShellV5.md)]
::: moniker-end
## Arguments
|Argument|Description|
|--- |--- |
|`ConnectedServiceNameARM`<br/>Azure Subscription|(Required) name of an Azure Resource Manager service connection for authentication. <br/>Argument alias: `azureSubscription`|
|`ScriptType`<br/>Script Type|(Optional) Type of the script: filePath or inlineScript <br/>Default value: `FilePath`|
|`ScriptPath`<br/>Script Path|(Optional) Path of the script. Should be fully qualified path or relative to the default working directory.|
|`Inline`<br/>Inline Script|(Optional) Enter the script to execute. <br/>Default value: <br/># You can write your Azure PowerShell scripts inline here.<br/> # You can also pass predefined and custom variables to this script using arguments|
|`ScriptArguments`<br/>Script Arguments|(Optional) Additional parameters to pass to PowerShell. Can be either ordinal or named parameters. Not applicable for inline script option.|
|`errorActionPreference`<br/>ErrorActionPreference|(Optional) Select the value of the ErrorActionPreference variable for executing the script. <br/>Default value: `stop`|
|`FailOnStandardError`<br/>Fail on Standard Error|(Optional) If this is true, this task will fail if any errors are written to the error pipeline, or if any data is written to the Standard Error stream. <br/>Default value: `false`|
|`TargetAzurePs`<br/>Azure PowerShell Version|(Required) In case of Microsoft-hosted agents, the supported Azure PowerShell version. To pick the latest version available on the agent, select `Latest installed version.` <br/>For self-hosted agents, you can specify preferred version of Azure PowerShell using "Specify version" <br/>Default value: `OtherVersion` <br/>Argument alias: `azurePowerShellVersion`|
|`CustomTargetAzurePs`<br/>preferredAzurePowerShellVersion|(Required when TargetAzurePs = OtherVersion) <br/>Preferred Azure PowerShell Version needs to be a proper semantic version. For example, 1.2.3. Regex like 2.\*,2.3.\* is not supported. <br/>Argument alias: `preferredAzurePowerShellVersion`|
|`pwsh`<br />Use PowerShell Core|(Optional) If this is true, on Windows, the task will use pwsh.exe from your PATH instead of powershell.exe.|
|`workingDirectory`<br />Working Directory|(Optional) Working directory where the script is run.|
## Samples
[!INCLUDE [temp](../includes/yaml/AzurePowerShellV5Sample.md)]
## Troubleshooting
### Script worked locally, but failed in the pipeline
This typically occurs when the service connection used in the pipeline has insufficient permissions to run the script. Locally, the script runs with your credentials and would succeed as you may have the required access.
To resolve this issue, ensure the service principle/ authentication credentials have the required permissions. For more information, see
[Use Role-Based Access Control to manage access to your Azure subscription resources](/azure/role-based-access-control/role-assignments-portal).
### Error: Could not find the modules: '\<module name\>' with Version: '\<version\>'. If the module was recently installed, retry after restarting the Azure Pipelines task agent
Azure PowerShell task uses Azure/AzureRM/Az PowerShell Module to interact with Azure Subscription. This issue occurs when the PowerShell module is not available on the Hosted Agent. Hence, for a particular task version, *Preferred Azure PowerShell version* must be specified in the **Azure PowerShell version options** from the list of available versions. The installed software can be found in the [Software](../../agents/hosted.md#software) table in [Microsoft-hosted agents](../../agents/hosted.md).
### Service Connection Issues
To troubleshoot issues related to service connections, see [Service Connection troubleshooting](../../release/azure-rm-endpoint.md).
## Open source
This task is open source [on GitHub](https://github.com/Microsoft/azure-pipelines-tasks). Feedback and contributions are welcome.
| 69.615385 | 502 | 0.782541 | eng_Latn | 0.95283 |
d3df061e7b7de7ec377afc0427cae43690545e08 | 220 | md | Markdown | stories_old/2014-05-08-2014-05-08-13-40.md | JuanIgnacioGil/3_belle | a131266ac8f7c873ebd34aafbc6f0415cd1cdb86 | [
"MIT"
] | null | null | null | stories_old/2014-05-08-2014-05-08-13-40.md | JuanIgnacioGil/3_belle | a131266ac8f7c873ebd34aafbc6f0415cd1cdb86 | [
"MIT"
] | 1 | 2021-12-06T17:21:47.000Z | 2021-12-06T17:21:47.000Z | stories_old/2014-05-08-2014-05-08-13-40.md | JuanIgnacioGil/3_belle | a131266ac8f7c873ebd34aafbc6f0415cd1cdb86 | [
"MIT"
] | null | null | null | ---
layout: post
title: "2014-05-08"
date: 2014-05-08 13:40:22
description:
image: "/assets/photos/201405/02a1931a6be3332db9c37aa11c0a2354.jpg"
author: Elise Plain
excerpt: 295. Sol
tags:
- all
---
295. Sol
<p></p>
| 14.666667 | 67 | 0.7 | eng_Latn | 0.094521 |
d3e0089280686988417e77d542b4e6fdeac03a50 | 703 | md | Markdown | _posts/2019-09-10-sera-que-os-indios-querem-se-tornar-garimpeiros.md | tatudoquei/tatudoquei.github.io | a3a3c362424fda626d7d0ce2d9f4bead6580631c | [
"MIT"
] | null | null | null | _posts/2019-09-10-sera-que-os-indios-querem-se-tornar-garimpeiros.md | tatudoquei/tatudoquei.github.io | a3a3c362424fda626d7d0ce2d9f4bead6580631c | [
"MIT"
] | null | null | null | _posts/2019-09-10-sera-que-os-indios-querem-se-tornar-garimpeiros.md | tatudoquei/tatudoquei.github.io | a3a3c362424fda626d7d0ce2d9f4bead6580631c | [
"MIT"
] | 1 | 2022-01-13T07:57:24.000Z | 2022-01-13T07:57:24.000Z | ---
layout: post
item_id: 2722301412
title: >-
Será que os índios querem se tornar garimpeiros?
author: Tatu D'Oquei
date: 2019-09-10 02:20:01
pub_date: 2019-09-10 02:20:01
time_added: 2019-09-11 20:54:24
category:
tags: []
---
Um editorial d’A Crítica, de Manaus, fala sobre a invasão de Terras Indígenas e sobre o discurso governamental segundo o qual os índios querem desenvolvimento: “Antes de qualquer coisa, é preciso abrir o diálogo com as Comunidades Indígenas, reconhecendo, também, toda sua diversidade.
**Link:** [http://climainfo.org.br/2019/09/10/sera-que-os-indios-querem-se-tornar-garimpeiros/](http://climainfo.org.br/2019/09/10/sera-que-os-indios-querem-se-tornar-garimpeiros/)
| 39.055556 | 285 | 0.758179 | por_Latn | 0.974977 |
d3e01b6a42c3d3fd36d423a62509b5daa791efc5 | 281 | md | Markdown | src/projects/blog-post.md | korangi3/E-portfolio | a0a38a221d87c8670456091bfd401b44f08b128d | [
"0BSD"
] | 1 | 2021-12-03T04:28:24.000Z | 2021-12-03T04:28:24.000Z | src/projects/blog-post.md | korangi3/E-portfolio | a0a38a221d87c8670456091bfd401b44f08b128d | [
"0BSD"
] | 17 | 2021-12-10T14:13:45.000Z | 2021-12-27T06:04:32.000Z | src/projects/blog-post.md | korangi3/E-portfolio | a0a38a221d87c8670456091bfd401b44f08b128d | [
"0BSD"
] | null | null | null | ---
title: Blog Post
stack: Django, HTML & CSS
slug: blog-post
date: 2021-01-02
url: https://github.com/korangi3/blog_post
imgsrc: blog.JPG
---
A blog application built using django with features like Login, Logout, User profile, Updating profile and overall CRUD functionalities. | 28.1 | 136 | 0.768683 | kor_Hang | 0.452707 |
d3e086dc4cf89013c7a0792f5c52122f6654dcb7 | 1,023 | md | Markdown | README.md | Gholtes/Keras-Deep-Dream | 91827183b835c27e3e46785462860cfe3a1131bd | [
"MIT"
] | null | null | null | README.md | Gholtes/Keras-Deep-Dream | 91827183b835c27e3e46785462860cfe3a1131bd | [
"MIT"
] | null | null | null | README.md | Gholtes/Keras-Deep-Dream | 91827183b835c27e3e46785462860cfe3a1131bd | [
"MIT"
] | null | null | null | # Keras-Deep-Dream
An implementation of Deep Dream in Keras, with examples. A bare bones version is also included for ease of understanding.
Method:
1) Load and preprocess image. Save 2 more copies.
2) Select a layer(s) in the network. The sum of this layer (the activations at this depth in the network) is to be maximised.
The loss is the negtaive of this sum.
3) Shrink the image down, and one of the copies.
4) For successivly larger image sizes:
4.1)Enlarge the input image and copy.
4.2)Shrink the second copy down to the current size.
4.3)The difference between the two copies is the information lost through enlarging the image.
4.4)Add this lost information back to the input image
4.5)For a few interations:
4.5.1) Get the gradient of the loss with respect to the input image.
4.5.2)Perform gradient accent by adding this gradient (multiplied by a constant) to the input image.
5) Resize the image back to its original dimensions, adding back any final lost information
6) Convert to RBG and save
| 36.535714 | 126 | 0.768328 | eng_Latn | 0.999458 |
d3e092a737078c566759b54d7150595550a61930 | 1,057 | md | Markdown | AlchemyInsights/outlook-com-create-folder.md | isabella232/OfficeDocs-AlchemyInsights-pr.sl-SI | 11a4d6bfb0580342f538adc12818d1a86ddcdac3 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-05-19T19:07:51.000Z | 2020-05-19T19:07:51.000Z | AlchemyInsights/outlook-com-create-folder.md | MicrosoftDocs/OfficeDocs-AlchemyInsights-pr.sl-SI | feeebbc38a3aeca0b2a03f49e3cab735f0ea4069 | [
"CC-BY-4.0",
"MIT"
] | 3 | 2020-06-02T23:33:13.000Z | 2022-02-09T06:51:06.000Z | AlchemyInsights/outlook-com-create-folder.md | isabella232/OfficeDocs-AlchemyInsights-pr.sl-SI | 11a4d6bfb0580342f538adc12818d1a86ddcdac3 | [
"CC-BY-4.0",
"MIT"
] | 3 | 2019-10-11T19:12:12.000Z | 2021-10-09T10:38:29.000Z | ---
title: Ustvarjanje mape v Outlook.com
ms.author: daeite
author: daeite
manager: joallard
ms.date: 04/21/2020
ms.audience: Admin
ms.topic: article
ms.service: o365-administration
ROBOTS: NOINDEX, NOFOLLOW
localization_priority: Normal
ms.collection: Adm_O365
ms.custom:
- "219"
- "8000009"
ms.assetid: 3b8d2755-e80b-47fb-9c1a-35fe9cb30c04
ms.openlocfilehash: 2df6749cac63e1f2dfbc0caacd5872abf31eadedb7819efaa2d4a05be56f8e4f
ms.sourcegitcommit: b5f7da89a650d2915dc652449623c78be6247175
ms.translationtype: MT
ms.contentlocale: sl-SI
ms.lasthandoff: 08/05/2021
ms.locfileid: "54111992"
---
# <a name="create-a-folder-in-outlookcom"></a>Ustvarjanje mape v Outlook.com
1. Na dnu podokna z mapami izberite **Nova mapa**. Morda se boste morali pomakniti navzdol v podoknu z mapami, da boste videli **gumb Nova** mapa.
2. V polje z besedilom vnesite ime mape in pritisnite tipko Enter.
Če želite izvedeti več, [glejte Ustvarjanje mape v Outlook.com.](https://support.office.com/article/6bb0723a-f39f-4a8d-bb3f-fab5dcc2510a?wt.mc_id=Office_Outlook_com_Alchemy) | 36.448276 | 173 | 0.803217 | slv_Latn | 0.249283 |
d3e13aecf1a87688c6c75aadfdcf6d51fd8b3b86 | 24 | md | Markdown | README.md | Rochet2/sentry-cli-docker-test | 5384a2639176932da254a1ae91d8734f6c4958fc | [
"MIT"
] | null | null | null | README.md | Rochet2/sentry-cli-docker-test | 5384a2639176932da254a1ae91d8734f6c4958fc | [
"MIT"
] | null | null | null | README.md | Rochet2/sentry-cli-docker-test | 5384a2639176932da254a1ae91d8734f6c4958fc | [
"MIT"
] | null | null | null | # sentry-cli-docker-test | 24 | 24 | 0.791667 | nob_Latn | 0.270937 |
d3e1ee07b92ecb2182def65e618eb4aeb7ec640c | 3,176 | md | Markdown | sdk-api-src/content/dwrite/nf-dwrite-idwritetextanalysissink-setnumbersubstitution.md | amorilio/sdk-api | 54ef418912715bd7df39c2561fbc3d1dcef37d7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | sdk-api-src/content/dwrite/nf-dwrite-idwritetextanalysissink-setnumbersubstitution.md | amorilio/sdk-api | 54ef418912715bd7df39c2561fbc3d1dcef37d7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | sdk-api-src/content/dwrite/nf-dwrite-idwritetextanalysissink-setnumbersubstitution.md | amorilio/sdk-api | 54ef418912715bd7df39c2561fbc3d1dcef37d7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
UID: NF:dwrite.IDWriteTextAnalysisSink.SetNumberSubstitution
title: IDWriteTextAnalysisSink::SetNumberSubstitution (dwrite.h)
description: Sets the number substitution on the text range affected by the text analysis.
helpviewer_keywords: ["IDWriteTextAnalysisSink interface [Direct Write]","SetNumberSubstitution method","IDWriteTextAnalysisSink.SetNumberSubstitution","IDWriteTextAnalysisSink::SetNumberSubstitution","SetNumberSubstitution","SetNumberSubstitution method [Direct Write]","SetNumberSubstitution method [Direct Write]","IDWriteTextAnalysisSink interface","directwrite.idwritetextanalysissink_setnumbersubstitution","dwrite/IDWriteTextAnalysisSink::SetNumberSubstitution"]
old-location: directwrite\idwritetextanalysissink_setnumbersubstitution.htm
tech.root: DirectWrite
ms.assetid: 09b00b49-702e-4cef-bf1c-397c5d572513
ms.date: 12/05/2018
ms.keywords: IDWriteTextAnalysisSink interface [Direct Write],SetNumberSubstitution method, IDWriteTextAnalysisSink.SetNumberSubstitution, IDWriteTextAnalysisSink::SetNumberSubstitution, SetNumberSubstitution, SetNumberSubstitution method [Direct Write], SetNumberSubstitution method [Direct Write],IDWriteTextAnalysisSink interface, directwrite.idwritetextanalysissink_setnumbersubstitution, dwrite/IDWriteTextAnalysisSink::SetNumberSubstitution
req.header: dwrite.h
req.include-header:
req.target-type: Windows
req.target-min-winverclnt: Windows 7, Windows Vista with SP2 and Platform Update for Windows Vista [desktop apps \| UWP apps]
req.target-min-winversvr: Windows Server 2008 R2, Windows Server 2008 with SP2 and Platform Update for Windows Server 2008 [desktop apps \| UWP apps]
req.kmdf-ver:
req.umdf-ver:
req.ddi-compliance:
req.unicode-ansi:
req.idl:
req.max-support:
req.namespace:
req.assembly:
req.type-library:
req.lib: Dwrite.lib
req.dll: Dwrite.dll
req.irql:
targetos: Windows
req.typenames:
req.redist:
ms.custom: 19H1
f1_keywords:
- IDWriteTextAnalysisSink::SetNumberSubstitution
- dwrite/IDWriteTextAnalysisSink::SetNumberSubstitution
dev_langs:
- c++
topic_type:
- APIRef
- kbSyntax
api_type:
- COM
api_location:
- dwrite.dll
api_name:
- IDWriteTextAnalysisSink.SetNumberSubstitution
---
# IDWriteTextAnalysisSink::SetNumberSubstitution
## -description
Sets the number substitution on the text range affected by the text analysis.
## -parameters
### -param textPosition
Type: <b>UINT32</b>
The starting position from which to report.
### -param textLength
Type: <b>UINT32</b>
The number of UTF16 units of the reported range.
### -param numberSubstitution
Type: <b><a href="/windows/win32/DirectWrite/idwritenumbersubstitution">IDWriteNumberSubstitution</a>*</b>
An object that holds the appropriate digits and numeric punctuation for a given locale. Use <a href="/windows/win32/api/dwrite/nf-dwrite-idwritefactory-createnumbersubstitution">IDWriteFactory::CreateNumberSubstitution</a> to create this object.
## -returns
Type: <b>HRESULT</b>
If this method succeeds, it returns <b>S_OK</b>. Otherwise, it returns an <b>HRESULT</b> error code.
## -see-also
<a href="/windows/win32/api/dwrite/nn-dwrite-idwritetextanalysissink">IDWriteTextAnalysisSink</a>
| 37.364706 | 469 | 0.813287 | yue_Hant | 0.469168 |
d3e26283b7e2fbc18bd3012005c5f77917aa92e7 | 154 | md | Markdown | README.md | mehrdadnasiri/terraform-maas-demo | 2c4be2454a3bc167209efd799a79abd4f136d951 | [
"Apache-2.0"
] | null | null | null | README.md | mehrdadnasiri/terraform-maas-demo | 2c4be2454a3bc167209efd799a79abd4f136d951 | [
"Apache-2.0"
] | null | null | null | README.md | mehrdadnasiri/terraform-maas-demo | 2c4be2454a3bc167209efd799a79abd4f136d951 | [
"Apache-2.0"
] | null | null | null | This is terraform for deploy a machine on maas
###ENV###
MAAS_API_URL="Your MAAS URL"
MAAS_API_KEY="Your MAAS API key"
@dwsclass dws-ops-002-terraform
| 19.25 | 47 | 0.753247 | eng_Latn | 0.415739 |
d3e271288fc0d79341128966811e2cadde039a64 | 4,284 | md | Markdown | schedule.md | jehopark/TEAM-repo-materials | f229fa7362a8d1ded13eae5f8333f2b3b8af28f2 | [
"MIT"
] | 1 | 2019-08-18T20:05:30.000Z | 2019-08-18T20:05:30.000Z | schedule.md | jehopark/TEAM-repo-materials | f229fa7362a8d1ded13eae5f8333f2b3b8af28f2 | [
"MIT"
] | 2 | 2019-01-28T22:44:38.000Z | 2019-01-28T22:45:38.000Z | schedule.md | jehopark/TEAM-repo-materials | f229fa7362a8d1ded13eae5f8333f2b3b8af28f2 | [
"MIT"
] | 10 | 2019-01-28T22:25:41.000Z | 2019-01-29T22:37:50.000Z | # CS121 (Spring 2018)
Welcome to CS 121 (Software Development) at Harvey Mudd College.
Canvas link: https://canvas.instructure.com/courses/1269330
Piazza link: https://canvas.instructure.com/courses/1269330
## Legend
What do the symbols on the calendar mean?
* :gem: Dev status report
* :mailbox_with_mail: PM project report
* :speech_balloon: PM presentation
* :star: In-class activity / draft due
* :star2: Assignment due
* :smile: Phase eval
* :heart: Client-dev meeting
| Phase | MON | TUES | WED | THUR | FRI | SAT | SUN |
|---------|------------------------------|-----------------------------------------------------|-----------------------------|-----------------------------------------------------------|-------------------------------------|-----------|----------|
| P3-1 | | | | | | | 4/1<br> |
| P3-2 | 4/2<br> :mailbox_with_mail: | 4/3<br>Ethics | 4/4 <br> | 4/5<br>:star: User testing (in-class) | 4/6 <br>:heart: | 4/7 | 4/8<br> :gem: |
| P4-1 | 4/9<br> :mailbox_with_mail: | 4/10<br> :speech_balloon: [PM3 presentation](https://canvas.instructure.com/courses/1269330/assignments/7799468 "Canvas submission link") | 4/11 <br> | 4/12<br> :star: [Functionality draft](https://canvas.instructure.com/courses/1269330/assignments/7799435 "Canvas submission link") (in-class peer review) | 4/13 <br> Open source + licensing | 4/14<br> | 4/15<br>:gem: |
| P4-2 | 4/16<br> :mailbox_with_mail: | 4/17 <br> Posters (discussion) <br> :star2: [Functionality](https://canvas.instructure.com/courses/1269330/assignments/7799434) | 4/18 <br> | 4/19 <br> :star: [Poster draft](https://canvas.instructure.com/courses/1269330/assignments/7799448) (in-class peer-review) | 4/20 <br>:heart: | 4/21 <br> | 4/22<br> :gem: |
| Week 15 | 4/23<br> :mailbox_with_mail: | 4/24 <br>:speech_balloon: [PM4 presentation](https://canvas.instructure.com/courses/1269330/assignments/7799468 "Canvas submission link") | 4/25<br> :star2: [Final Poster](https://canvas.instructure.com/courses/1269330/assignments/7799447) due | 4/26 <br>:clap: Course celebration :tada: :star: [Final writeup draft](https://canvas.instructure.com/courses/1269330/assignments/7799430) (offline peer review due) | 4/27 <br> :heart: :speech_balloon: [Poster session](https://canvas.instructure.com/courses/1269330/assignments/7799449) | 4/28 :star2: [Final README for handoff meeting](https://canvas.instructure.com/courses/1269330/assignments/7799436) <br> | 4/29<br> :gem: (all) |
| Week 16 | 4/30<br> [Handoff meetings](https://docs.google.com/document/d/105r_IqQmWwYpH9SGKbUMFfDAOab8cTda6cViLsz9cXE) | 5/1<br> | 5/2<br> [Handoff meetings](https://docs.google.com/document/d/105r_IqQmWwYpH9SGKbUMFfDAOab8cTda6cViLsz9cXE) | 5/3<br> | 5/4<br> :star2: [Final writeup](https://canvas.instructure.com/courses/1269330/assignments/7799431) <br> :star2: [Portfolio](https://canvas.instructure.com/courses/1269330/assignments/7799426) <br> :star2: (Extra credit) [Open source exercise](https://canvas.instructure.com/courses/1269330/assignments/8318209) | 5/5<br> :smile: [Postmortem](https://canvas.instructure.com/courses/1269330/assignments/7799433) <br> | 5/6<br> |
## Contributing
1. Fork it!
2. Create your feature branch: `git checkout -b my-new-feature`
3. Commit your changes: `git commit -am 'Add some feature'`
4. Push to the branch: `git push origin my-new-feature`
5. Submit a pull request :D
## Copyright and Licensing
These materials build on the resources shared by the previous CS 121 instructors and the HMC Clinic staff.
<a rel="license" href="http://creativecommons.org/licenses/by-nc-sa/4.0/"><img alt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by-nc-sa/4.0/88x31.png" /></a> This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-nc-sa/4.0/">Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License</a>.
This license lets others remix, tweak, and build upon this work non-commercially, as long as they credit this work and license their new creations under the identical terms. Read more about <a href="https://creativecommons.org/licenses/">available licenses</a>.
Original GitHub course link: https://github.com/hmc-cs121-admin/hmc-cs121-s2018 (created by Yekaterina Kharitonova)
| 97.363636 | 724 | 0.692344 | eng_Latn | 0.28855 |
d3e32be34a2b4b98f172f2962c9906ed6bf95139 | 3,280 | md | Markdown | docs/visual-basic/developing-apps/programming/drives-directories-files/file-access.md | badbadc0ffee/docs.de-de | 50a4fab72bc27249ce47d4bf52dcea9e3e279613 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/visual-basic/developing-apps/programming/drives-directories-files/file-access.md | badbadc0ffee/docs.de-de | 50a4fab72bc27249ce47d4bf52dcea9e3e279613 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/visual-basic/developing-apps/programming/drives-directories-files/file-access.md | badbadc0ffee/docs.de-de | 50a4fab72bc27249ce47d4bf52dcea9e3e279613 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Dateizugriff
ms.date: 07/20/2015
helpviewer_keywords:
- file access
- files [Visual Basic], input and output
- file access, Visual Basic
- files [Visual Basic], I/O
- file I/O classes
- data [Visual Basic], accessing from files
- files [Visual Basic], accessing
- file access, using components
- My.Computer.FileSystem object, accessing files
- I/O [Visual Basic]
- sequential access
ms.assetid: 231533bf-d049-4345-befa-3fb78fe6517d
ms.openlocfilehash: 22bcd0f1f3acb0c0ad899b83ad2d879ead948f12
ms.sourcegitcommit: 17ee6605e01ef32506f8fdc686954244ba6911de
ms.translationtype: HT
ms.contentlocale: de-DE
ms.lasthandoff: 11/22/2019
ms.locfileid: "74348900"
---
# <a name="file-access-with-visual-basic"></a>Dateizugriff mit Visual Basic
Das `My.Computer.FileSystem`-Objekt bietet Tools zum Arbeiten mit Dateien und Ordnern. Seine Eigenschaften, Methoden und Ereignisse erlauben es Ihnen, Dateien und Ordner zu erstellen, zu kopieren, zu verschieben, zu untersuchen und zu löschen. `My.Computer.FileSystem` bietet eine bessere Leistung als die von Visual Basic bereitgestellten älteren Funktionen (`FileOpen`, `FileClose`, `Input`, `InputString`, `LineInput` usw.), um Abwärtskompatibilität zu gewährleisten.
## <a name="in-this-section"></a>In diesem Abschnitt
[Lesen aus Dateien](../../../../visual-basic/developing-apps/programming/drives-directories-files/reading-from-files.md)
Listet Themen im Zusammenhang mit der Verwendung des `My.Computer.FileSystem`-Objekts zum Lesen aus Dateien auf
[Schreiben in Dateien](../../../../visual-basic/developing-apps/programming/drives-directories-files/writing-to-files.md)
Listet Themen im Zusammenhang mit der Verwendung des `My.Computer.FileSystem`-Objekts zum Schreiben in Dateien auf
[Erstellen, Löschen und Verschieben von Dateien und Verzeichnissen](../../../../visual-basic/developing-apps/programming/drives-directories-files/creating-deleting-and-moving-files-and-directories.md)
Listet Themen im Zusammenhang mit der Verwendung des `My.Computer.FileSystem`-Objekts zum Erstellen, Kopieren, Löschen und Verschieben von Dateien und Ordnern auf.
[Analysieren von Textdateien mit dem TextFieldParser-Objekt](../../../../visual-basic/developing-apps/programming/drives-directories-files/parsing-text-files-with-the-textfieldparser-object.md)
Erläutert, wie `TextFieldReader` verwendet wird, um Textdateien wie z.B. Protokolle zu analysieren.
[Dateicodierungen](../../../../visual-basic/developing-apps/programming/drives-directories-files/file-encodings.md)
Beschreibt Dateicodierungen und deren Verwendung.
[Exemplarische Vorgehensweise: Bearbeiten von Dateien und Verzeichnissen in Visual Basic](../../../../visual-basic/developing-apps/programming/drives-directories-files/walkthrough-manipulating-files-and-directories.md)
Veranschaulicht, wie ein Dienstprogramm erstellt wird, das Informationen zu Dateien und Ordnern meldet.
[Problembehandlung: Lesen aus und Schreiben in Textdateien](../../../../visual-basic/developing-apps/programming/drives-directories-files/troubleshooting-reading-from-and-writing-to-text-files.md)
Listet häufige Probleme beim Lesen und Schreiben in Textdateien auf, und gibt Vorschläge zu entsprechenden Lösungsmöglichkeiten.
| 65.6 | 472 | 0.785061 | deu_Latn | 0.849061 |
d3e348d1384d011d81f4ec2f157da5e6c4e97235 | 1,504 | md | Markdown | README.md | shady2k/ioBroker.js2fs-community | 5e63f2951c78297da95fcb23d3a1ddf0b3cb2130 | [
"MIT"
] | null | null | null | README.md | shady2k/ioBroker.js2fs-community | 5e63f2951c78297da95fcb23d3a1ddf0b3cb2130 | [
"MIT"
] | 35 | 2019-03-10T07:12:23.000Z | 2021-07-26T12:03:45.000Z | README.md | shady2k/ioBroker.js2fs-community | 5e63f2951c78297da95fcb23d3a1ddf0b3cb2130 | [
"MIT"
] | 6 | 2019-04-01T09:23:47.000Z | 2022-01-07T14:54:17.000Z | 
### ioBroker.js2fs
 
[](https://www.npmjs.com/package/iobroker.js2fs)
[](https://travis-ci.org/soef/iobroker.js2fs)
[](https://ci.appveyor.com/project/soef/iobroker-js2fs)
[](https://github.com/soef/iobroker.js2fs/blob/master/LICENSE)
This adapter allows you to edit your ioBroker javascript files with your preferred IDE/editor.
### Info
- Only for developers and for backup purposes (scripts are then files on disk and therefor can be included in backup)
- This is a pre-release and only for test purposes
- Currently debugging is restricted
### Initial Creation
This adapter was initialy created by @soef at https://github.com/soef/iobroker.js2fs but not maintained any more, so we moved it to iobroker-community so that bugs could be fixed. thanks @soef for his work.
### Benefits
- use your preferred environment ide
- debugging
- breakpoints
### Usage
e.g.: Webstorm:
#### Installation
Execute the following command in the iobroker root directory (e.g. in /opt/iobroker)
```
npm install iobroker.js2fs
```
| 44.235294 | 206 | 0.763298 | eng_Latn | 0.744631 |
d3e3998faa65b4911f6072d5a1b8e974b577f56a | 5,327 | md | Markdown | README.md | perry-mitchell/iocane | 286e0045472b39cc315ee80edfcf8eb1d4b0eb3a | [
"MIT"
] | 44 | 2016-09-26T11:06:19.000Z | 2022-03-09T21:58:08.000Z | README.md | perry-mitchell/iocane | 286e0045472b39cc315ee80edfcf8eb1d4b0eb3a | [
"MIT"
] | 24 | 2016-03-28T20:39:28.000Z | 2021-05-06T11:00:25.000Z | README.md | perry-mitchell/iocane | 286e0045472b39cc315ee80edfcf8eb1d4b0eb3a | [
"MIT"
] | 10 | 2017-10-03T05:30:57.000Z | 2020-01-16T23:20:04.000Z | 
A powerful and easy-to-use **text** and **data** encryption library for **NodeJS** and the **web**.
[](https://buttercup.pw) [](https://www.npmjs.com/package/iocane/) [](https://www.npmjs.com/package/iocane/)
## About
iocane makes text and data encryption and decryption easy by bundling all the complicated processes into one succinct library. Encrypt and decrypt **strings** and **buffers** easily by using iocane's encryption format - string->string / buffer->buffer. Encrypt and decrypt **streams** in NodeJS.
This library uses "sessions" for encryption and decryption. A session describes one encryption/decryption action, and can also have options be further overridden at the time of execution. Check the examples below for a better idea of how this process works.
iocane works in the browser, too. Both a **node version** and a **web version** are available:
```javascript
const iocane = require("iocane"); // node
```
```javascript
import * as iocane from "iocane/web" // web
```
### Features
**iocane** by default boasts the following features:
* AES-CBC / AES-GCM encryption:
* Text
* Buffers
* Streams _(only in NodeJS)_
* 256bit keys
* PBKDF2 key derivation (with 250k/custom iterations)
* 35KB minified web version (10KB gzipped)
* Overridable encryption/derivation/packing functionality to allow for adaptation to yet-unsupported environments
## Installation
Install `iocane` as a dependency using `npm`:
```shell
npm install iocane --save
```
## Usage
**iocane** can be easily used to encrypt text:
```typescript
import { createAdapter } from "iocane";
createAdapter()
.encrypt("some secret text", "myPassword")
.then(encryptedString => {
// do something with the encrypted text
});
```
Decryption is even simpler, as instructions on _how_ to decrypt the payload is included in the payload itself:
```typescript
import { createAdapter } from "iocane";
createAdapter()
.decrypt(encryptedString, "myPassword")
.then(decryptedString => {
// ...
});
```
During encryption, you can override a variety of options:
```typescript
import { EncryptionAlgorithm, createAdapter } from "iocane";
const encrypted = await createAdapter()
.setAlgorithm(EncryptionAlgorithm.GCM) // use GCM encryption
.setDerivationRounds(300000)
.encrypt(target, password);
```
Each cryptographic function can be overridden by simply replacing it on the adapter
```typescript
import { createAdapter } from "iocane";
const adapter = createAdapter();
adapter.deriveKey = async (password: string, salt: string) => { /* ... */ };
await adapter.encrypt(/* ... */);
```
_Note that the default encryption mode is `EncryptionAlgorithm.CBC` (AES-CBC encryption)._
### Encrypting and decrypting data buffers
Iocane can handle buffers the same way it handles strings - just pass them into the same encrypt/decrypt functions:
```typescript
import { createAdapter } from "iocane";
import fs from "fs";
createAdapter()
.setAlgorithm(EncryptionAlgorithm.CBC)
.encrypt(fs.readFileSync("./test.bin"), "passw0rd")
.then(data => fs.writeFileSync("./test.bin.enc", data));
```
_The same can be performed on the web, with array buffers in place of standard buffers._
### Encrypting and decrypting using streams
_Available on the Node version only._
Iocane can create encryption and decryption streams, which is very useful for encrypting large amounts of data:
```typescript
import { createAdapter } from "iocane";
import fs from "fs";
import zlib from "zlib";
// Encrypt
fs
.createReadStream("/my-file.dat")
.pipe(zlib.createGzip())
.pipe(createAdapter().createEncryptStream("passw0rd"))
.pipe(fs.createWriteStream("/destination.dat.enc"));
// Decrypt
fs
.createReadStream("/destination.dat.enc")
.pipe(createAdapter().createDecryptStream("passw0rd"))
.pipe(zlib.createGunzip())
.pipe(fs.createWriteStream("/my-file-restored.dat"));
```
### Web usage
When building a project for the web, make sure to use the web-based version of iocane. Bundling the node version will create super-large bundles and result in slow encryption and decryption. iocane for the web uses UMD so it can be imported or simply loaded straight in the browser as a `<script>`.
If you load iocane directly in the browser, it will create a global namespace at `window.iocane` (eg. `window.iocane.createAdapter`).
## Supported environments
iocane supports NodeJS version 10 and above. Node 8 was supported in `3.x` and versions prior to 8 were supported in `1.x`.
iocane is used in the browser as well - it works everywhere that `SubtleCrypto`, `ArrayBuffer` and `Promise` are available.
_Note: iocane is written in TypeScript, though versions before v2 where written in JavaScript._
## Buttercup
iocane was originally part of the [Buttercup](https://github.com/buttercup) suite. Buttercup is a supported dependent of iocane and efforts are made to align iocane with Buttercup's target platforms and uses.
| 34.816993 | 345 | 0.737188 | eng_Latn | 0.96835 |
d3e3a91145a303e91a9966c929cac36110e634cb | 1,612 | md | Markdown | docs/extensibility/debugger/reference/idebugportsupplier2-getport.md | ManuSquall/visualstudio-docs.fr-fr | 87f0072eb292673de4a102be704162619838365f | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-08-15T11:25:55.000Z | 2021-08-15T11:25:55.000Z | docs/extensibility/debugger/reference/idebugportsupplier2-getport.md | ManuSquall/visualstudio-docs.fr-fr | 87f0072eb292673de4a102be704162619838365f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/extensibility/debugger/reference/idebugportsupplier2-getport.md | ManuSquall/visualstudio-docs.fr-fr | 87f0072eb292673de4a102be704162619838365f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
description: Obtient un port à partir d’un fournisseur de ports.
title: 'IDebugPortSupplier2 :: GetPort | Microsoft Docs'
ms.date: 11/04/2016
ms.topic: reference
f1_keywords:
- IDebugPortSupplier2::GetPort
helpviewer_keywords:
- IDebugPortSupplier2::GetPort
ms.assetid: d55d5055-7386-4037-bf22-4c3e434a99ca
author: leslierichardson95
ms.author: lerich
manager: jmartens
ms.workload:
- vssdk
dev_langs:
- CPP
- CSharp
ms.openlocfilehash: 3c5626ce41181a711aafb7dbf26bbe5a65f218c9
ms.sourcegitcommit: f2916d8fd296b92cc402597d1d1eecda4f6cccbf
ms.translationtype: MT
ms.contentlocale: fr-FR
ms.lasthandoff: 03/25/2021
ms.locfileid: "105072167"
---
# <a name="idebugportsupplier2getport"></a>IDebugPortSupplier2::GetPort
Obtient un port à partir d’un fournisseur de ports.
## <a name="syntax"></a>Syntaxe
```cpp
HRESULT GetPort(
REFGUID guidPort,
IDebugPort2** ppPort
);
```
```csharp
int GetPort(
ref Guid guidPort,
out IDebugPort2 ppPort
);
```
## <a name="parameters"></a>Paramètres
`guidPort`\
dans Identificateur global unique (GUID) du port.
`ppPort`\
à Retourne un objet [IDebugPort2](../../../extensibility/debugger/reference/idebugport2.md) qui représente le port.
## <a name="return-value"></a>Valeur renvoyée
En cas de réussite, retourne `S_OK` , sinon, retourne un code d'erreur. Retourne `E_PORTSUPPLIER_NO_PORT` si aucun port n’existe avec l’identificateur donné.
## <a name="see-also"></a>Voir aussi
- [IDebugPortSupplier2](../../../extensibility/debugger/reference/idebugportsupplier2.md)
- [IDebugPort2](../../../extensibility/debugger/reference/idebugport2.md)
| 27.793103 | 158 | 0.754963 | yue_Hant | 0.187664 |
d3e3b3f4cc94b902c925ad3a475343789f84342f | 74 | md | Markdown | README.md | KarolToledo/PI | 2c912166ed84be3462bf89f839d680d58428c338 | [
"MIT"
] | null | null | null | README.md | KarolToledo/PI | 2c912166ed84be3462bf89f839d680d58428c338 | [
"MIT"
] | null | null | null | README.md | KarolToledo/PI | 2c912166ed84be3462bf89f839d680d58428c338 | [
"MIT"
] | null | null | null | # PI
Carteira Digital de Vacina com Flask, HTML, CSS, Visual Studio Code
| 24.666667 | 68 | 0.756757 | por_Latn | 0.438503 |
d3e3c1aef8f1a939fd03905001415be277c16cde | 4,419 | md | Markdown | docs/image_loaders.md | edenman/coil | b73d416c2531241fc1e3cb26ea651f7ac995fa93 | [
"Apache-2.0"
] | null | null | null | docs/image_loaders.md | edenman/coil | b73d416c2531241fc1e3cb26ea651f7ac995fa93 | [
"Apache-2.0"
] | null | null | null | docs/image_loaders.md | edenman/coil | b73d416c2531241fc1e3cb26ea651f7ac995fa93 | [
"Apache-2.0"
] | null | null | null | # Image Loaders
`ImageLoader`s are [service objects](https://publicobject.com/2019/06/10/value-objects-service-objects-and-glue/) that execute [`ImageRequest`](image_requests.md)s. They handle caching, data fetching, image decoding, request management, bitmap pooling, memory management, and more. New instances can be created and configured using a builder:
```kotlin
val imageLoader = ImageLoader.Builder(context)
.availableMemoryPercentage(0.25)
.crossfade(true)
.build()
```
Coil performs best when you create a single `ImageLoader` and share it throughout your app. This is because each `ImageLoader` has its own memory cache, bitmap pool, and network observer.
It's recommended, though not required, to call [`shutdown`](../api/coil-base/coil-base/coil/-image-loader/shutdown.html) when you've finished using an image loader. This preemptively frees its memory and cleans up any observers. If you only create and use one `ImageLoader`, you do not need to shut it down as it will be freed when your app is killed.
## Caching
Each `ImageLoader` keeps a memory cache of recently decoded `Bitmap`s as well as a reusable pool of `Bitmap`s to decode into.
`ImageLoader`s rely on an `OkHttpClient` to handle disk caching. **By default, every `ImageLoader` is already set up for disk caching** and will set a max cache size of between 10-250MB depending on the remaining space on the user's device.
However, if you set a custom `OkHttpClient`, you'll need to add the disk cache yourself. To get a `Cache` instance that's optimized for Coil, you can use [`CoilUtils.createDefaultCache`](../api/coil-base/coil-base/coil.util/-coil-utils/create-default-cache.html). Optionally, you can create your own `Cache` instance with a different size + location. Here's an example:
```kotlin
val imageLoader = ImageLoader.Builder(context)
.okHttpClient {
OkHttpClient.Builder()
.cache(CoilUtils.createDefaultCache(context))
.build()
}
.build()
```
## Singleton vs. Dependency Injection
Coil performs best when you create a single `ImageLoader` and share it throughout your app. This is because each `ImageLoader` has its own memory cache and bitmap pool.
If you use a dependency injector like [Dagger](https://github.com/google/dagger), then you should create a single `ImageLoader` instance and inject it throughout your app.
However, if you'd prefer a singleton the `io.coil-kt:coil` artifact provides a singleton `ImageLoader` instance that can be accessed using the `Context.imageLoader` extension function. [Read here](../getting_started/#singleton) for how to initialize the singleton `ImageLoader` instance.
!!! Note
Use the `io.coil-kt:coil-base` artifact if you are using dependency injection.
## Testing
`ImageLoader` is an interface, which you can replace with a fake implementation.
For instance, you could inject a fake `ImageLoader` implementation which always returns the same `Drawable` synchronously:
```kotlin
val fakeImageLoader = object : ImageLoader {
private val disposable = object : Disposable {
override val isDisposed get() = true
override fun dispose() {}
override suspend fun await() {}
}
override val defaults = DefaultRequestOptions()
// Optionally, you can add a custom fake memory cache implementation.
override val memoryCache get() = throw UnsupportedOperationException()
override val bitmapPool = BitmapPool(0)
override fun enqueue(request: ImageRequest): Disposable {
// Always call onStart before onSuccess.
request.target?.onStart(placeholder = ColorDrawable(Color.BLACK))
request.target?.onSuccess(result = ColorDrawable(Color.BLACK))
return disposable
}
override suspend fun execute(request: ImageRequest): ImageResult {
return SuccessResult(
drawable = ColorDrawable(Color.BLACK),
request = request,
metadata = ImageResult.Metadata(
memoryCacheKey = MemoryCache.Key(""),
isSampled = false,
dataSource = DataSource.MEMORY_CACHE,
isPlaceholderMemoryCacheKeyPresent = false
)
)
}
override fun shutdown() {}
override fun newBuilder() = ImageLoader.Builder(context)
}
```
This is perfect for screenshot and instrumentation tests where you want consistent rendering behavior.
| 47.010638 | 369 | 0.72754 | eng_Latn | 0.95766 |
d3e3f9d2313b4b429aa0ddf122170e414eec4299 | 228 | md | Markdown | _posts/2017-07-27-welcome.md | BreadmanBlog/breadmanblog.github.io | 1ee807dfc8b8bafd163575c970b6f863b91defd8 | [
"MIT"
] | null | null | null | _posts/2017-07-27-welcome.md | BreadmanBlog/breadmanblog.github.io | 1ee807dfc8b8bafd163575c970b6f863b91defd8 | [
"MIT"
] | null | null | null | _posts/2017-07-27-welcome.md | BreadmanBlog/breadmanblog.github.io | 1ee807dfc8b8bafd163575c970b6f863b91defd8 | [
"MIT"
] | null | null | null | ---
layout: post
current: post
cover: assets/images/rye.jpeg
navigation: True
title: Bread bread bread
date: 2017-07-27 10:00:00
tags: [Bread]
class: post-template
subclass: 'post tag-bread'
author: tony
---
bread bread bread
| 15.2 | 30 | 0.736842 | eng_Latn | 0.694888 |
d3e4eceb40880100fa0f1731ad38e80f3161455d | 894 | md | Markdown | src/zh/2021-04/07/07.md | ArthurMota9/sabbath-school-lessons | a51fcdecb05cfbbfdacf201ccba9ba768b245885 | [
"MIT"
] | 68 | 2016-10-30T23:17:56.000Z | 2022-03-27T11:58:16.000Z | src/zh/2021-04/07/07.md | ArthurMota9/sabbath-school-lessons | a51fcdecb05cfbbfdacf201ccba9ba768b245885 | [
"MIT"
] | 367 | 2016-10-21T03:50:22.000Z | 2022-03-28T23:35:25.000Z | src/zh/2021-04/07/07.md | ArthurMota9/sabbath-school-lessons | a51fcdecb05cfbbfdacf201ccba9ba768b245885 | [
"MIT"
] | 109 | 2016-08-02T14:32:13.000Z | 2022-03-31T10:18:41.000Z | ---
title: 进修资料
date: 12/11/2021
---
「在天上公然反抗上帝律法的基督的死敌，已经像是技巧娴熟、训练有素的将军，他使出浑身解数，用尽各种欺骗的手段，为要让上帝的律法作废，而律法正是罪恶唯一的侦测器，公义的独一标准。」（怀爱伦，《评阅宣报》，1890年11月18日）
浩瀚的宇宙中闪耀着两万亿个星系。每个星系中有一千亿颗恒星。那可是100,000,000,000颗啊！两万亿个星系，每个星系一千亿颗恒星，算起来宇宙中就有200,000,000,000,000,000,000,000颗恒星。
我们已知一个有关存在的原则：能作出构想和创造行为的个体，必定是大过或超越所设想和创造的东西。比如，毕卡索肯定比他的画作更伟大。同理，那位构想并创造了这个宇宙的上帝，肯定是大过宇宙，并远远超越这个宇宙。
带着这样的思考，我们来重温这段经文：「太初有道，道与上帝同在，道就是上帝。这道太初与上帝同在。万物都是借着祂造的；凡被造的，没有一样不是借着祂造的。」（约1：1–3）也就是说，那位创造万有的上帝，创造了200,000,000,000,000,000,000,000颗星星和其他一切所有的─祂做了什么呢？祂「虚己」成了婴孩，度过无罪的一生，然后死在十字架上，承担了我们因罪恶所当受的刑罚，使我们得到永生的应许。
摆在我们面前的就是这伟大的真理：这恩典透过那被钉十字架的耶稣基督赐给我们。那么上帝要我们做什么当作回报呢？「这些事都已听见了，总意就是敬畏上帝，谨守祂的诫命，这是人所当尽的本分。」（传12：13）
**讨论问题**
`1. 请在讨论时复习星期一课程结尾所提出的问题，有关相信并遵守律法―即十诫（包括第四条）的人，如何避免掉入律法主义的陷阱？ 顺服―严格且坚定的顺服，与律法主义有什么不同？我们如何看出两者之间的区别？`
`2. 你曾经听过（或亲身经历过）哪些关于人们因违反十诫而遭受可怕后果的事？从中我们能学到哪些关于律法如何反映上帝对我们的爱的教训？`
`3. 为什么说十字架向我们显明，想靠自己的行为赚取天国是徒劳无功的？` | 40.636364 | 204 | 0.826622 | zho_Hans | 0.253894 |
d3e5222704bf8021ea4e2b2e8cece695bd6ce484 | 24,289 | md | Markdown | docs/exchange-web-services/email-properties-and-elements-in-ews-in-exchange.md | isabella232/office-developer-exchange-docs.ja-JP | d2d2f4e3861e8a3495b7c1acfe7f3784a246423f | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-05-19T18:53:49.000Z | 2020-05-19T18:53:49.000Z | docs/exchange-web-services/email-properties-and-elements-in-ews-in-exchange.md | isabella232/office-developer-exchange-docs.ja-JP | d2d2f4e3861e8a3495b7c1acfe7f3784a246423f | [
"CC-BY-4.0",
"MIT"
] | 2 | 2021-12-08T02:37:43.000Z | 2021-12-08T02:37:59.000Z | docs/exchange-web-services/email-properties-and-elements-in-ews-in-exchange.md | isabella232/office-developer-exchange-docs.ja-JP | d2d2f4e3861e8a3495b7c1acfe7f3784a246423f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Exchange における EWS でのメールのプロパティと要素
manager: sethgros
ms.date: 09/17/2015
ms.audience: Developer
ms.assetid: 5266ff9f-d828-4ef4-b8ec-7b27d355c4c5
description: Exchange で EWS マネージ API または EWS を使用して、メール メッセージで取得できるファースト クラスと他のプロパティと要素について説明します。
localization_priority: Priority
ms.openlocfilehash: d7f5c5e68dcd0c4fc481afa37b338a47b1fd2e96
ms.sourcegitcommit: 88ec988f2bb67c1866d06b361615f3674a24e795
ms.translationtype: HT
ms.contentlocale: ja-JP
ms.lasthandoff: 05/31/2020
ms.locfileid: "44455437"
---
# <a name="email-properties-and-elements-in-ews-in-exchange"></a>Exchange における EWS でのメールのプロパティと要素
Exchange で EWS マネージ API または EWS を使用して、メール メッセージで取得できるファースト クラスと他のプロパティと要素について説明します。
メール メッセージには 50 を超えるプロパティがあるので、検索する場所が分からないと、必要なプロパティを必要な時に取得する場合に混乱する可能性があります。 メールのプロパティと要素の操作方法を理解するうえで最も重要なことは、主な取得方法と操作によって返されるファースト クラスのプロパティおよび要素のセットにどれが含まれているかということです。 返されるファースト クラスのプロパティのセットは、どの方法で取得するかによって異なります。 また、[BaseShape](https://msdn.microsoft.com/library/42c04f3b-abaa-4197-a3d6-d21677ffb1c0%28Office.15%29.aspx) EWS 要素の AllProperties 値に惑わされないことも重要です。この値は EWS マネージ API の [BasePropertySet.FirstClassMessageProperties](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.basepropertyset%28v=exchg.80%29.aspx) 列挙値に対応します。 この値には、実際にすべてのプロパティが含まれているわけではなく、ファースト クラスのプロパティのみが含まれます。
## <a name="first-class-properties-and-elements-for-email-messages"></a>メール メッセージのファースト クラスのプロパティと要素
<a name="bk_firstclass"> </a>
EWS マネージ API の [EmailMessage.Bind](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.emailmessage.bind%28v=exchg.80%29.aspx) メソッドと EWS の [GetItem](https://msdn.microsoft.com/library/e8492e3b-1c8d-4b14-8070-9530f8306edd%28Office.15%29.aspx) 操作によって返されるファースト クラスのプロパティと要素のセットは、EWS マネージ API の [ExchangeService.FindItems](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.exchangeservice.finditems%28v=exchg.80%29.aspx) メソッドと EWS の [FindItem](https://msdn.microsoft.com/library/ebad6aae-16e7-44de-ae63-a95b24539729%28Office.15%29.aspx) 操作によって返されるファースト クラスのプロパティと要素のセットとは、若干異なります。 **FindItems** メソッドと **FindItem** 操作によって返されるファースト クラスのプロパティは、**Bind** メソッドと **GetItem** 操作によって返されるプロパティのサブセットです。 表 1 に、**Bind** メソッドと **GetItem** 操作によって返されるすべてのファースト クラスのプロパティと、そのうちどのプロパティが **FindItems** メソッドまたは **FindItem** 操作によって返されないのかを示します。 **ToRecipients**、**CcRecipients**、**BccRecipients** などの他のプロパティや要素を取得するように **FindItems** メソッドまたは **FindItem** 操作を拡張することはできません。 これらの値を取得するには、**FindItems** メソッドまたは **FindItem** 操作を使用してメールのアイテム ID を取得してから、**Bind** メソッドまたは **GetItem** 操作を使用して必要なプロパティを取得します。 **Bind** メソッドまたは **FindItems** メソッドを使用してアイテムを取得する方法を示すコード例については、「[EWS マネージ API を使用してアイテムを取得する](how-to-work-with-exchange-mailbox-items-by-using-ews-in-exchange.md#bk_getewsma)」を参照してください。 **GetItem** 操作または **FindItem** 操作を使用してアイテムを取得する方法を示すコード例については、「[EWS を使用してアイテムを取得する](how-to-work-with-exchange-mailbox-items-by-using-ews-in-exchange.md#bk_getews)」を参照してください。
次の表に、応答で表示される順序でファースト クラスのプロパティと要素を記載します。
**表 1. ファースト クラスのメールのプロパティと要素**
|**EWS マネージ API のプロパティ**|**EWS の要素**|****FindItems** メソッドまたは **FindItem** 操作のファースト クラスのプロパティか**|**読み取り/書き込み、または読み取り専用**|
|:-----|:-----|:-----|:-----|
|[Id](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.id%28v=exchg.80%29.aspx) <br/> |[ItemId](https://msdn.microsoft.com/library/3350b597-57a0-4961-8f44-8624946719b4%28Office.15%29.aspx) <br/> |はい <br/> |読み取り専用 <br/> |
|[ParentFolderId](https://msdn.microsoft.com/library/office/microsoft.exchange.webservices.data.item.parentfolderid%28v=exchg.80%29.aspx) <br/> |[ParentFolderId](https://msdn.microsoft.com/library/258f4b1f-367e-4c7d-9c29-eb775a2398c7%28Office.15%29.aspx) <br/> |はい <br/> |読み取り専用 <br/> |
|[ItemClass](https://msdn.microsoft.com/library/office/microsoft.exchange.webservices.data.item.itemclass%28v=exchg.80%29.aspx) <br/> |[ItemClass](https://msdn.microsoft.com/library/56020078-50b4-4880-894a-a9f234033cfb%28Office.15%29.aspx) <br/> |はい <br/> |読み取り/書き込み <br/> |
|[Subject](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.subject%28v=exchg.80%29.aspx) <br/> |[Subject](https://msdn.microsoft.com/library/c140d6c2-deb1-4f67-a908-9397197c4ae7%28Office.15%29.aspx) <br/> |はい <br/> |読み取り/書き込み <br/> |
|[Sensitivity](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.sensitivity%28v=exchg.80%29.aspx) <br/> |[Sensitivity](https://msdn.microsoft.com/library/d872423a-c26e-4675-9028-23361fb4a43d%28Office.15%29.aspx) <br/> |はい <br/> |読み取り専用 <br/> |
|[Body](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.body%28v=exchg.80%29.aspx) <br/> |[Body](https://msdn.microsoft.com/library/7851ea9b-9f87-4adc-a26f-7a27df4a9bca%28Office.15%29.aspx) <br/> |いいえ <br/> |読み取り/書き込み <br/> |
|[Attachments](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.attachments%28v=exchg.80%29.aspx) <br/> |[Attachments](https://msdn.microsoft.com/library/b470e614-34bb-44f0-8790-7ddbdcbbd29d%28Office.15%29.aspx) <br/> |いいえ <br/> |読み取り/書き込み <br/> |
|[DateTimeReceived](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.datetimereceived%28v=exchg.80%29.aspx) <br/> |[DateTimeReceived](https://msdn.microsoft.com/library/8f489bd4-2434-4d0a-91fe-1b5ba7eb5765%28Office.15%29.aspx) <br/> |はい <br/> |読み取り専用 <br/> |
|[Size](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.size%28v=exchg.80%29.aspx) <br/> |[Size](https://msdn.microsoft.com/library/966f4daf-c20e-49f8-aeb6-965f3e2da7c3%28Office.15%29.aspx) <br/> |はい <br/> |読み取り専用 <br/> |
|[Categories](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.categories%28v=exchg.80%29.aspx) <br/> |[Categories](https://msdn.microsoft.com/library/d84d4927-b524-4e62-bf3d-1f12fec8c21a%28Office.15%29.aspx) <br/> |いいえ <br/> |読み取り/書き込み <br/> |
|[Importance](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.importance%28v=exchg.80%29.aspx) <br/> |[Importance](https://msdn.microsoft.com/library/1557f59a-41f2-43fb-9ded-88f3ec5c76cb%28Office.15%29.aspx) <br/> |はい <br/> |読み取り/書き込み <br/> |
|[InReplyTo](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.inreplyto%28v=exchg.80%29.aspx) <br/> |[InReplyTo](https://msdn.microsoft.com/library/561b8941-1c26-4bbe-aa0f-b49ec8a79af5%28Office.15%29.aspx) <br/> |はい <br/> |読み取り/書き込み <br/> |
|[IsSubmitted](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.issubmitted%28v=exchg.80%29.aspx) <br/> |[IsSubmitted](https://msdn.microsoft.com/library/2399e27e-bd8c-46b6-a3aa-674842e098c9%28Office.15%29.aspx) <br/> |はい <br/> |読み取り専用 <br/> |
|[IsDraft](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.isdraft%28v=exchg.80%29.aspx) <br/> |[IsDraft](https://msdn.microsoft.com/library/8b8d9cc9-a512-458a-94e4-af210ac83bd7%28Office.15%29.aspx) <br/> |はい <br/> |読み取り専用 <br/> |
|[IsFromMe](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.isfromme%28v=exchg.80%29.aspx) <br/> |[IsFromMe](https://msdn.microsoft.com/library/d3c5fbf0-a95c-46e5-890f-953e50ac49d6%28Office.15%29.aspx) <br/> |はい <br/> |読み取り専用 <br/> |
|[IsResend](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.isresend%28v=exchg.80%29.aspx) <br/> |[IsResend](https://msdn.microsoft.com/library/8f758b6b-dcee-4f95-9d39-e4be2bd92961%28Office.15%29.aspx) <br/> |はい <br/> |読み取り専用 <br/> |
|[IsUnmodified](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.isunmodified%28v=exchg.80%29.aspx) <br/> |[IsUnmodified](https://msdn.microsoft.com/library/8f758b6b-dcee-4f95-9d39-e4be2bd92961%28Office.15%29.aspx) <br/> |はい <br/> |読み取り専用 <br/> |
|[InternetMessageHeaders](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.internetmessageheaders%28v=exchg.80%29.aspx) <br/> |[InternetMessageHeaders](https://msdn.microsoft.com/library/4dcf8671-96df-4a2d-9836-7e8e3a67e0db%28Office.15%29.aspx) <br/> |いいえ <br/> |読み取り専用 <br/> |
|[DateTimeSent](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.datetimesent%28v=exchg.80%29.aspx) <br/> |[DateTimeSent](https://msdn.microsoft.com/library/81784ef3-8912-4d63-8502-73419a906999%28Office.15%29.aspx) <br/> |はい <br/> |読み取り専用 <br/> |
|[DateTimeCreated](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.datetimecreated%28v=exchg.80%29.aspx) <br/> |[DateTimeCreated](https://msdn.microsoft.com/library/42ae0067-4688-49d9-93c5-c4dbeb54cee1%28Office.15%29.aspx) <br/> |はい <br/> |読み取り専用 <br/> |
|[AllowedResponseActions](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.allowedresponseactions%28v=exchg.80%29.aspx) <br/> |[ResponseObjects](https://msdn.microsoft.com/library/ad29e064-3f3d-4b7b-aa4c-9ec27326381d%28Office.15%29.aspx) <br/> |いいえ <br/> |読み取り専用 <br/> |
|[ReminderDueBy](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.reminderdueby%28v=exchg.80%29.aspx) <br/> |[ReminderDueBy](https://msdn.microsoft.com/library/e28a0485-86af-4a4e-a2ba-3ad2d4ebff6f%28Office.15%29.aspx) <br/> |はい <br/> |読み取り/書き込み <br/> |
|[IsReminderSet](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.isreminderset%28v=exchg.80%29.aspx) <br/> |[ReminderIsSet](https://msdn.microsoft.com/library/fa366afe-77a0-4c14-9edb-ffc9699131ba%28Office.15%29.aspx) <br/> |はい <br/> |読み取り/書き込み <br/> |
|[ReminderMinutesBeforeStart](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.reminderminutesbeforestart%28v=exchg.80%29.aspx) <br/> |[ReminderMinutesBeforeStart](https://msdn.microsoft.com/library/65ea14bc-5f19-48cc-aef1-46227e06f5f5%28Office.15%29.aspx) <br/> |はい <br/> |読み取り/書き込み <br/> |
|[DisplayCc](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.displaycc%28v=exchg.80%29.aspx) <br/> |[DisplayCc](https://msdn.microsoft.com/library/af386e06-80f3-42c7-8b3c-1f7993c49d10%28Office.15%29.aspx) <br/> |はい <br/> |読み取り専用 <br/> |
|[DisplayTo](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.displayto%28v=exchg.80%29.aspx) <br/> |[DisplayTo](https://msdn.microsoft.com/library/16a0b22d-063b-417c-8aba-efcf9490b072%28Office.15%29.aspx) <br/> |はい <br/> |読み取り専用 <br/> |
|[HasAttachments](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.hasattachments%28v=exchg.80%29.aspx) <br/> |[HasAttachments](https://msdn.microsoft.com/library/538b7a85-11d7-4daa-8458-09b540760e8b%28Office.15%29.aspx) <br/> |はい <br/> |読み取り専用 <br/> |
|[Culture](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.culture%28v=exchg.80%29.aspx) <br/> |[Culture](https://msdn.microsoft.com/library/71bd62c6-3fec-48db-9a5e-02121e9bc20b%28Office.15%29.aspx) <br/> |はい <br/> |読み取り/書き込み <br/> |
|[EffectiveRights](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.effectiverights%28v=exchg.80%29.aspx) <br/> |[EffectiveRights](https://msdn.microsoft.com/library/bf5278eb-3a1a-4d27-9d16-b8be043bb023%28Office.15%29.aspx) <br/> |はい <br/> |読み取り専用 <br/> |
|[LastModifiedName](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.lastmodifiedname%28v=exchg.80%29.aspx) <br/> |[LastModifiedName](https://msdn.microsoft.com/library/4f1a90c1-e27e-4e16-93c3-e79d4cb720d1%28Office.15%29.aspx) <br/> |はい <br/> |読み取り専用 <br/> |
|[LastModifiedTime](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.lastmodifiedtime%28v=exchg.80%29.aspx) <br/> |[LastModifiedTime](https://msdn.microsoft.com/library/6db2cabc-e7f4-4d71-962b-789de6a192a4%28Office.15%29.aspx) <br/> |はい <br/> |読み取り専用 <br/> |
|[IsAssociated](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.isassociated%28v=exchg.80%29.aspx) <br/> |[IsAssociated](https://msdn.microsoft.com/library/637f0798-6680-487f-bcbf-aaddc4a74186%28Office.15%29.aspx) <br/> |はい <br/> |読み取り/書き込み <br/> |
|[WebClientReadFormQueryString](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.webclientreadformquerystring%28v=exchg.80%29.aspx) <br/> |[WebClientReadFormQueryString](https://msdn.microsoft.com/library/13e8871a-32a6-4bb9-9493-864c4c07efff%28Office.15%29.aspx) <br/> |はい <br/> |読み取り専用 <br/> |
|[WebClientEditFormQueryString](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.webclienteditformquerystring%28v=exchg.80%29.aspx) <br/> |[WebClientEditFormQueryString](https://msdn.microsoft.com/library/9e571021-d58f-424b-8db2-48cf683533dc%28Office.15%29.aspx) <br/> |はい <br/> |読み取り専用 <br/> |
|[ConversationId](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.conversationid%28v=exchg.80%29.aspx) <br/> |[ConversationId](https://msdn.microsoft.com/library/d5f1ddb3-9af3-4677-a6ba-111b304a951e%28Office.15%29.aspx) <br/> |はい <br/> |読み取り専用 <br/> |
|[Flag](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.flag%28v=exchg.80%29.aspx) <br/> |[Flag](https://msdn.microsoft.com/library/7b47bc74-a60d-4308-8674-5d52444a1753%28Office.15%29.aspx) <br/> |はい <br/> |読み取り/書き込み <br/> |
|[InstanceKey](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.instancekey%28v=exchg.80%29.aspx) <br/> |[InstanceKey](https://msdn.microsoft.com/library/bb4dbe9b-aea0-4527-b7d6-e928066caf38%28Office.15%29.aspx) <br/> |はい <br/> |読み取り専用 <br/> |
|[EntityExtractionResult](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.entityextractionresult%28v=exchg.80%29.aspx) <br/> |[EntityExtractionResult](https://msdn.microsoft.com/library/643b99ab-ff90-4411-864c-1077623028d6%28Office.15%29.aspx) <br/> |いいえ <br/> |読み取り専用 <br/> |
|[Sender](https://msdn.microsoft.com/library/office/microsoft.exchange.webservices.data.emailmessage.sender%28v=exchg.80%29.aspx) <br/> |[Sender](https://msdn.microsoft.com/library/26d1a46e-e1d3-44b8-a02d-fa6f83aa5cda%28Office.15%29.aspx) <br/> |はい <br/> |読み取り/書き込み <br/> |
|[ToRecipients](https://msdn.microsoft.com/library/office/microsoft.exchange.webservices.data.emailmessage.torecipients%28v=exchg.80%29.aspx) <br/> |[ToRecipients](https://msdn.microsoft.com/library/72dc3be8-30bb-4ae1-acf4-fb94ff490631%28Office.15%29.aspx) <br/> |いいえ <br/> |読み取り専用 <br/> |
|[CcRecipients](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.emailmessage.ccrecipients%28v=exchg.80%29.aspx) <br/> |[CcRecipients](https://msdn.microsoft.com/library/5c20ec3a-0bee-4e67-b220-586ed0d601c9%28Office.15%29.aspx) <br/> |いいえ <br/> |読み取り専用 <br/> |
|[BccRecipients](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.emailmessage.bccrecipients%28v=exchg.80%29.aspx) <br/> |[BccRecipients](https://msdn.microsoft.com/library/c4e05168-d36b-4740-a526-4b7da53553c1%28Office.15%29.aspx) <br/> |いいえ <br/> |読み取り専用 <br/> |
|[IsReadReceiptRequested](https://msdn.microsoft.com/library/office/microsoft.exchange.webservices.data.emailmessage.isreadreceiptrequested%28v=exchg.80%29.aspx) <br/> |[IsReadReceiptRequested](https://msdn.microsoft.com/library/7ab6edd5-c7ed-4701-8de3-d7dc7ecfa9c2%28Office.15%29.aspx) <br/> |はい <br/> |読み取り/書き込み <br/> |
|[IsDeliveryReceiptRequested](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.emailmessage.isdeliveryreceiptrequested%28v=exchg.80%29.aspx) <br/> |[IsDeliveryReceiptRequested](https://msdn.microsoft.com/library/97776b7e-942c-4663-8277-165d64364daa%28Office.15%29.aspx) <br/> |はい <br/> |読み取り/書き込み <br/> |
|[ConversationIndex](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.emailmessage.conversationindex%28v=exchg.80%29.aspx) <br/> |[ConversationIndex](https://msdn.microsoft.com/library/fdf47e22-8d93-4ae4-883b-0c9f07f48724%28Office.15%29.aspx) <br/> |はい <br/> |読み取り専用 <br/> |
|[ConversationTopic](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.emailmessage.conversationtopic%28v=exchg.80%29.aspx) <br/> |[ConversationTopic](https://msdn.microsoft.com/library/46cacf42-4039-4c8a-9b20-c42cdd9f2760%28Office.15%29.aspx) <br/> |はい <br/> |読み取り専用 <br/> |
|[From](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.emailmessage.from%28v=exchg.80%29.aspx) <br/> |[From](https://msdn.microsoft.com/library/5a52d644-3677-4049-874c-12bd5c3080dc%28Office.15%29.aspx) <br/> |はい <br/> |読み取り/書き込み <br/> |
|[InternetMessageId](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.emailmessage.internetmessageid%28v=exchg.80%29.aspx) <br/> |[InternetMessageId](https://msdn.microsoft.com/library/a5a9563f-e761-4658-9957-0e13566f6a35%28Office.15%29.aspx) <br/> |はい <br/> |読み取り専用 <br/> |
|[IsRead](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.emailmessage.isread%28v=exchg.80%29.aspx) <br/> |[IsRead](https://msdn.microsoft.com/library/161455d5-a870-4c99-b2eb-c759c538f1bc%28Office.15%29.aspx) <br/> |はい <br/> |読み取り/書き込み <br/> |
|[IsResponseRequested](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.emailmessage.isresponserequested%28v=exchg.80%29.aspx) <br/> |[IsResponseRequested](https://msdn.microsoft.com/library/8cb874ed-a538-4de6-ab22-2631092dcdd0%28Office.15%29.aspx) <br/> |はい <br/> |読み取り/書き込み <br/> |
|[ReplyTo](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.emailmessage.replyto%28v=exchg.80%29.aspx) <br/> |[ReplyTo](https://msdn.microsoft.com/library/6b6ae792-e2c4-4aa0-95cb-b49b446f1e08%28Office.15%29.aspx) <br/> |いいえ <br/> |読み取り専用 <br/> |
|[References](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.emailmessage.references%28v=exchg.80%29.aspx) <br/> |[References](https://msdn.microsoft.com/library/d78f9a48-cd24-452f-af65-4c01933227ce%28Office.15%29.aspx) <br/> |はい <br/> |読み取り/書き込み <br/> |
|[ReceivedBy](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.emailmessage.receivedby%28v=exchg.80%29.aspx) <br/> |[ReceivedBy](https://msdn.microsoft.com/library/ac84c9c5-d2fe-4b6f-bf4d-0444131d835b%28Office.15%29.aspx) <br/> |はい <br/> |読み取り専用 <br/> |
|[ReceivedRepresenting](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.emailmessage.receivedrepresenting%28v=exchg.80%29.aspx) <br/> |[ReceivedRepresenting](https://msdn.microsoft.com/library/1157b042-6dce-4cdc-9700-e22b749da39f%28Office.15%29.aspx) <br/> |はい <br/> |読み取り専用 <br/> |
## <a name="other-properties-and-elements-for-email-messages"></a>メール メッセージのその他のプロパティと要素
<a name="bk_notfirstclass"> </a>
すべての重要なメールのプロパティと要素が、ファースト クラスのプロパティと要素であるわけではありません。 その他のプロパティまたは要素を取得するには、それらを [PropertySet](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.propertyset%28v=exchg.80%29.aspx) に追加するか (EWS マネージ API を使用している場合)、またはプロパティ パスを使用して EWS 操作呼び出しに追加する必要があります。 たとえば、メッセージのテキスト本文と MIME コンテンツを取得するには、**Bind** または **Load** メソッドで示すように **PropertySet** を作成します。
```cs
PropertySet(BasePropertySet.IdOnly, ItemSchema.TextBody, ItemSchema.MimeContent);
```
または、EWS を使用している場合は、次に示すように、該当する要素を **GetItem** 操作要求の [AdditionalProperties](https://msdn.microsoft.com/library/7a269aed-dcfd-4c3e-9e14-094e53828101%28Office.15%29.aspx) 要素に追加します。
```XML
<t:AdditionalProperties>
<t:FieldURI FieldURI="item:TextBody" />
<t:FieldURI FieldURI="item:MimeContent" />
</t:AdditionalProperties>
```
EWS マネージ API の [ServiceObject](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.serviceobject%28v=exchg.80%29.aspx) オブジェクトから継承されている **EmailMessage** プロパティを、**Bind** メソッドのプロパティ セットに含めることはできません。ただし、すべての **ServiceObject** プロパティは **EmailMessage** オブジェクト上で読み取ることができ、**Bind** メソッドによって取得されます。
**表 2. メールのその他のプロパティと要素**
|**EWS マネージ API のプロパティ**|**EWS の要素**|**読み取り/書き込み、または読み取り専用**|
|:-----|:-----|:-----|
|[ArchiveTag](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.archivetag%28v=exchg.80%29.aspx) <br/> |[ArchiveTag](https://msdn.microsoft.com/library/c4cb0718-37cd-41aa-86e7-b492c4bb86aa%28Office.15%29.aspx) <br/> |読み取り/書き込み <br/> |
|[ExtendedProperties](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.extendedproperties%28v=exchg.80%29.aspx) <br/> |[ExtendedProperty](https://msdn.microsoft.com/library/f9701409-b620-4afe-b9ee-4c1e95507af7%28Office.15%29.aspx) <br/> |読み取り専用 <br/> |
|[IconIndex](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.iconindex%28v=exchg.80%29.aspx) <br/> |[IconIndex](https://msdn.microsoft.com/library/92020822-2a86-4dfc-aee1-3067af4d4edf%28Office.15%29.aspx) <br/> |読み取り専用 <br/> |
|[IsAttachment](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.isattachment%28v=exchg.80%29.aspx) <br/> |使用不可 <br/> |読み取り専用 <br/> |
|[IsDirty](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.serviceobject.isdirty%28v=exchg.80%29.aspx) <br/> |使用不可 <br/> |読み取り専用 <br/> |
|[IsNew](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.isnew%28v=exchg.80%29.aspx) <br/> |使用不可 <br/> |読み取り専用 <br/> |
|[Item](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.serviceobject.item%28v=exchg.80%29.aspx) <br/> |[Item](https://msdn.microsoft.com/library/4dfe8f48-e7b4-444d-bdf9-a34e180f598b%28Office.15%29.aspx) <br/> |読み取り専用 <br/> |
|[MimeContent](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.mimecontent%28v=exchg.80%29.aspx) <br/> |[MimeContent](https://msdn.microsoft.com/library/4f472a08-5653-4c54-ba65-831dfe32f20f%28Office.15%29.aspx) <br/> |読み取り専用 <br/> |
|利用不可 <br/> |[MimeContentUTF8](https://msdn.microsoft.com/library/31544c95-5231-4b57-958c-2a689464d29b%28Office.15%29.aspx) <br/> |読み取り専用 <br/> |
|[NormalizedBody](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.normalizedbody%28v=exchg.80%29.aspx) <br/> |[NormalizedBody](https://msdn.microsoft.com/library/bfb813e4-642d-4f1b-9e91-1fee89dbd083%28Office.15%29.aspx) <br/> |読み取り専用 <br/> |
|[PolicyTag](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.policytag%28v=exchg.80%29.aspx) <br/> |[PolicyTag](https://msdn.microsoft.com/library/fa4b1447-dc7b-47ad-a677-78fcee443dc6%28Office.15%29.aspx) <br/> |読み取り/書き込み <br/> |
|[Preview](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.preview%28v=exchg.80%29.aspx) <br/> |[Preview](https://msdn.microsoft.com/library/5d33f557-c9d5-4f7f-82c0-d800412f8b7e%28Office.15%29.aspx) <br/> |読み取り/書き込み <br/> |
|[RetentionDate](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.retentiondate%28v=exchg.80%29.aspx) <br/> |[RetentionDate](https://msdn.microsoft.com/library/0c1df5e2-b56a-4947-a047-2b73b32e5fb7%28Office.15%29.aspx) <br/> |読み取り専用 <br/> |
|[Schema](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.serviceobject.schema%28v=exchg.80%29.aspx) <br/> |使用不可 <br/> |読み取り専用 <br/> |
|[Service](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.serviceobject.service%28v=exchg.80%29.aspx) <br/> |使用不可 <br/> |読み取り専用 <br/> |
|[StoreEntryId](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.storeentryid%28v=exchg.80%29.aspx) <br/> |[StoreEntryId](https://msdn.microsoft.com/library/f536e264-8c4d-4cc5-bab8-22a4fa38de39%28Office.15%29.aspx) <br/> |読み取り専用 <br/> |
|[TextBody](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.textbody%28v=exchg.80%29.aspx) <br/> |[TextBody](https://msdn.microsoft.com/library/bd0c0bce-3e7c-47c7-af7f-5ee5f5ad9820%28Office.15%29.aspx) <br/> |読み取り専用 <br/> |
|[UniqueBody](https://msdn.microsoft.com/library/microsoft.exchange.webservices.data.item.uniquebody%28v=exchg.80%29.aspx) <br/> |[UniqueBody](https://msdn.microsoft.com/library/06bc95d7-121c-433b-bd27-c2b0eb8c011f%28Office.15%29.aspx) <br/> |読み取り専用 <br/> |
## <a name="see-also"></a>関連項目
- [Exchange のメールと EWS](email-and-ews-in-exchange.md)
- [Exchange における EWS のプロパティと拡張プロパティ](properties-and-extended-properties-in-ews-in-exchange.md)
- [Exchange の EWS でのプロパティ セットと応答の図形](property-sets-and-response-shapes-in-ews-in-exchange.md)
- [Exchange で EWS を使用して Exchange メールボックス アイテムを操作する](how-to-work-with-exchange-mailbox-items-by-using-ews-in-exchange.md)
| 169.853147 | 1,474 | 0.763556 | yue_Hant | 0.638209 |
d3e55d9ab07cd0f2b582ce12bfbc8c2d8cf7ee4e | 481 | md | Markdown | articles/includes/cloud-edge-privacy-notice.md | MicrosoftDocs/Dynamics-365-Operations.ja-jp | 821ba731df05b9c1d0b0947b8d7e66ae9a34c0b4 | [
"CC-BY-4.0",
"MIT"
] | 4 | 2020-05-18T17:14:25.000Z | 2021-11-13T07:27:21.000Z | articles/includes/cloud-edge-privacy-notice.md | MicrosoftDocs/Dynamics-365-Operations.ja-jp | 821ba731df05b9c1d0b0947b8d7e66ae9a34c0b4 | [
"CC-BY-4.0",
"MIT"
] | 37 | 2017-12-13T17:53:18.000Z | 2021-03-16T19:04:28.000Z | articles/includes/cloud-edge-privacy-notice.md | MicrosoftDocs/Dynamics-365-Operations.ja-jp | 821ba731df05b9c1d0b0947b8d7e66ae9a34c0b4 | [
"CC-BY-4.0",
"MIT"
] | 8 | 2017-11-06T03:10:26.000Z | 2020-03-21T18:08:51.000Z | ---
ms.openlocfilehash: 98afc8e2bc85f15d7191170d09272ff1488bc67d3abbf811de0e6c04b73b117b
ms.sourcegitcommit: 42fe9790ddf0bdad911544deaa82123a396712fb
ms.translationtype: HT
ms.contentlocale: ja-JP
ms.lasthandoff: 08/05/2021
ms.locfileid: "6721442"
---
> [!Important]
> **プライバシー通知:** クラウド スケール ユニットを有効にすると、個人データを含む特定の顧客データを、クラウド スケール ユニットが配置されている地域的領域に転送できます。 Microsoft にとってお客様のプライバシーは重要です。 詳細については、Microsoft [プライバシー ステートメント](https://go.microsoft.com/fwlink/?LinkId=521839)をお読みください。 | 48.1 | 214 | 0.835759 | yue_Hant | 0.703668 |
d3e5bdb75bb86650895ac85efd382444e63a5a86 | 12,082 | md | Markdown | docs/xamarin-forms/user-interface/tableview.md | DeeplyRecursive/xamarin-docs | 0c2745c1593eee3ecb40ab882e854a13ca72bc86 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/xamarin-forms/user-interface/tableview.md | DeeplyRecursive/xamarin-docs | 0c2745c1593eee3ecb40ab882e854a13ca72bc86 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/xamarin-forms/user-interface/tableview.md | DeeplyRecursive/xamarin-docs | 0c2745c1593eee3ecb40ab882e854a13ca72bc86 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "Xamarin.Forms TableView"
description: "This article explains how to use the Xamarin.Forms TableView class to present scrolling menus, settings and input forms in applications."
ms.prod: xamarin
ms.assetid: D1619D19-A74F-40DF-8E53-B1B7DFF7A3FB
ms.technology: xamarin-forms
author: davidbritch
ms.author: dabritch
ms.date: 12/14/2018
---
# Xamarin.Forms TableView
[ Download the sample](https://developer.xamarin.com/samples/xamarin-forms/UserInterface/TableView)
[`TableView`](xref:Xamarin.Forms.TableView) is a view for displaying scrollable lists of data or choices where there are rows that don't share the same template. Unlike [ListView](~/xamarin-forms/user-interface/listview/index.md), `TableView` does not have the concept of an `ItemsSource`, so items must be manually added as children.
<a name="Use_Cases" />
## Use cases
[`TableView`](xref:Xamarin.Forms.TableView) is useful when:
- presenting a list of settings,
- collecting data in a form, or
- showing data that is presented differently from row to row (e.g. numbers, percentages and images).
[`TableView`](xref:Xamarin.Forms.TableView) handles scrolling and laying out rows in attractive sections, a common need for the above scenarios. The `TableView` control uses each platform's underlying equivalent view when available, creating a native look for each platform.
<a name="TableView_Structure" />
## Structure
Elements in a [`TableView`](xref:Xamarin.Forms.TableView) are organized into sections. At the root of the `TableView` is the [`TableRoot`](xref:Xamarin.Forms.TableRoot), which is parent to one or more [`TableSection`](xref:Xamarin.Forms.TableSection) instances. Each [`TableSection`](xref:Xamarin.Forms.TableSection) consists of a heading and one or more [`ViewCell`](xref:Xamarin.Forms.ViewCell) instances:
```xaml
<TableView Intent="Settings">
<TableRoot>
<TableSection Title="Ring">
<SwitchCell Text="New Voice Mail" />
<SwitchCell Text="New Mail" On="true" />
</TableSection>
</TableRoot>
</TableView>
```
The equivalent C# code is:
```csharp
Content = new TableView
{
Root = new TableRoot
{
new TableSection("Ring")
{
// TableSection constructor takes title as an optional parameter
new SwitchCell { Text = "New Voice Mail" },
new SwitchCell { Text = "New Mail", On = true }
}
},
Intent = TableIntent.Settings
};
```
<a name="TableView_Appearance" />
## Appearance
[`TableView`](xref:Xamarin.Forms.TableView) exposes the [`Intent`](xref:Xamarin.Forms.TableView.Intent) property, which can be set to any of the [`TableIntent`](xref:Xamarin.Forms.TableIntent) enumeration members:
- `Data` – for use when displaying data entries. Note that [ListView](~/xamarin-forms/user-interface/listview/index.md) may be a better option for scrolling lists of data.
- `Form` – for use when the TableView is acting as a Form.
- `Menu` – for use when presenting a menu of selections.
- `Settings` – for use when displaying a list of configuration settings.
The [`TableIntent`](xref:Xamarin.Forms.TableIntent) value you choose may impact how the [`TableView`](xref:Xamarin.Forms.TableView) appears on each platform. Even if there are not clear differences, it is a best practice to select the `TableIntent` that most closely matches how you intend to use the table.
In addition, the color of the text displayed for each [`TableSection`](xref:Xamarin.Forms.TableSection) can be changed by setting the `TextColor` property to a [`Color`](xref:Xamarin.Forms.Color).
<a name="Built-In_Cells" />
## Built-in cells
Xamarin.Forms comes with built-in cells for collecting and displaying information. Although [`ListView`](xref:Xamarin.Forms.ListView) and [`TableView`](xref:Xamarin.Forms.TableView) can use all of the same cells, [`SwitchCell`](xref:Xamarin.Forms.SwitchCell) and [`EntryCell`](xref:Xamarin.Forms.EntryCell) are the most relevant for a `TableView` scenario.
See [ListView Cell Appearance](~/xamarin-forms/user-interface/listview/customizing-cell-appearance.md) for a detailed description of [TextCell](~/xamarin-forms/user-interface/listview/customizing-cell-appearance.md#TextCell) and [ImageCell](~/xamarin-forms/user-interface/listview/customizing-cell-appearance.md#ImageCell).
<a name="switchcell" />
### SwitchCell
[`SwitchCell`](xref:Xamarin.Forms.SwitchCell) is the control to use for presenting and capturing an on/off or `true`/`false` state. It defines the following properties:
- `Text` – text to display beside the switch.
- `On` – whether the switch is displayed as on or off.
- `OnColor` – the [`Color`](xref:Xamarin.Forms.Color) of the switch when it's in the on position.
All of these properties are bindable.
[`SwitchCell`](xref:Xamarin.Forms.SwitchCell) also exposes the `OnChanged` event, allowing you to respond to changes in the cell's state.
<a name="entrycell" />
### EntryCell
[`EntryCell`](xref:Xamarin.Forms.EntryCell) is useful when you need to display text data that the user can edit. It defines the following properties:
- `Keyboard` – The keyboard to display while editing. There are options for things like numeric values, email, phone numbers, etc. [See the API docs](xref:Xamarin.Forms.Keyboard).
- `Label` – The label text to display to the right of the text entry field.
- `LabelColor` – The color of the label text.
- `Placeholder` – Text to display in the entry field when it is null or empty. This text disappears when text entry begins.
- `Text` – The text in the entry field.
- `HorizontalTextAlignment` – The horizontal alignment of the text. Can be center, left, or right aligned. [See the API docs](xref:Xamarin.Forms.TextAlignment).
[`EntryCell`](xref:Xamarin.Forms.EntryCell) also exposes the `Completed` event, which is fired when the user hits the 'done' button on the keyboard while editing text.
<a name="Custom_Cells" />
## Custom cells
When the built-in cells aren't enough, custom cells can be used to present and capture data in the way that makes sense for your app. For example, you may want to present a slider to allow a user to choose the opacity of an image.
All custom cells must derive from [`ViewCell`](xref:Xamarin.Forms.ViewCell), the same base class that all of the built-in cell types use.
This is an example of a custom cell:
The following example shows the XAML used to create the [`TableView`](xref:Xamarin.Forms.TableView) in the screenshots above:
```xaml
<?xml version="1.0" encoding="UTF-8"?>
<ContentPage xmlns="http://xamarin.com/schemas/2014/forms"
xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
x:Class="DemoTableView.TablePage"
Title="TableView">
<TableView Intent="Settings">
<TableRoot>
<TableSection Title="Getting Started">
<ViewCell>
<StackLayout Orientation="Horizontal">
<Image Source="bulb.png" />
<Label Text="left"
TextColor="#f35e20" />
<Label Text="right"
HorizontalOptions="EndAndExpand"
TextColor="#503026" />
</StackLayout>
</ViewCell>
</TableSection>
</TableRoot>
</TableView>
</ContentPage>
```
The equivalent C# code is:
```csharp
var table = new TableView();
table.Intent = TableIntent.Settings;
var layout = new StackLayout() { Orientation = StackOrientation.Horizontal };
layout.Children.Add (new Image() { Source = "bulb.png"});
layout.Children.Add (new Label()
{
Text = "left",
TextColor = Color.FromHex("#f35e20"),
VerticalOptions = LayoutOptions.Center
});
layout.Children.Add (new Label ()
{
Text = "right",
TextColor = Color.FromHex ("#503026"),
VerticalOptions = LayoutOptions.Center,
HorizontalOptions = LayoutOptions.EndAndExpand
});
table.Root = new TableRoot ()
{
new TableSection("Getting Started")
{
new ViewCell() {View = layout}
}
};
Content = table;
```
The root element under the [`TableView`](xref:Xamarin.Forms.TableView) is the [`TableRoot`](xref:Xamarin.Forms.TableRoot), and there is a [`TableSection`](xref:Xamarin.Forms.TableSection) immediately underneath the `TableRoot`. The [`ViewCell`](xref:Xamarin.Forms.ViewCell) is defined directly under the `TableSection`, and a [`StackLayout`](xref:Xamarin.Forms.StackLayout) is used to manage the layout of the custom cell, although any layout could be used here.
> [!NOTE]
> Unlike [`ListView`](xref:Xamarin.Forms.ListView), [`TableView`](xref:Xamarin.Forms.TableView) does not require that custom (or any) cells are defined in an `ItemTemplate`.
## Row height
The [`TableView`](xref:Xamarin.Forms.TableView) class has two properties that can be used to change the row height of cells:
- [`RowHeight`](xref:Xamarin.Forms.TableView.RowHeight) – sets the height of each row to an `int`.
- [`HasUnevenRows`](xref:Xamarin.Forms.TableView.HasUnevenRows) – rows have varying heights if set to `true`. Note that when setting this property to `true`, row heights will automatically be calculated and applied by Xamarin.Forms.
When the height of content in a cell in a [`TableView`](xref:Xamarin.Forms.TableView) is changed, the row height is implicitly updated on Android and the Universal Windows Platform (UWP). However, on iOS it must be forced to update by setting the [`HasUnevenRows`](xref:Xamarin.Forms.TableView.HasUnevenRows) property to `true` and by calling the [`Cell.ForceUpdateSize`](xref:Xamarin.Forms.Cell.ForceUpdateSize) method.
The following XAML example shows a [`TableView`](xref:Xamarin.Forms.TableView) that contains a [`ViewCell`](xref:Xamarin.Forms.ViewCell):
```xaml
<ContentPage ...>
<TableView ...
HasUnevenRows="true">
<TableRoot>
...
<TableSection ...>
...
<ViewCell x:Name="_viewCell"
Tapped="OnViewCellTapped">
<Grid Margin="15,0">
<Grid.RowDefinitions>
<RowDefinition Height="Auto" />
<RowDefinition Height="Auto" />
</Grid.RowDefinitions>
<Label Text="Tap this cell." />
<Label x:Name="_target"
Grid.Row="1"
Text="The cell has changed size."
IsVisible="false" />
</Grid>
</ViewCell>
</TableSection>
</TableRoot>
</TableView>
</ContentPage>
```
When the [`ViewCell`](xref:Xamarin.Forms.ViewCell) is tapped, the `OnViewCellTapped` event handler is executed:
```csharp
void OnViewCellTapped(object sender, EventArgs e)
{
_target.IsVisible = !_target.IsVisible;
_viewCell.ForceUpdateSize();
}
```
The `OnViewCellTapped` event handler shows or hides the second [`Label`](xref:Xamarin.Forms.Label) in the [`ViewCell`](xref:Xamarin.Forms.ViewCell), and explicitly updates the cell's size by calling the [`Cell.ForceUpdateSize`](xref:Xamarin.Forms.Cell.ForceUpdateSize) method.
The following screenshots show the cell prior to being tapped upon:
The following screenshots show the cell after being tapped upon:
> [!IMPORTANT]
> There is a strong possibility of performance degradation if this feature is overused.
## Related links
- [TableView (sample)](https://developer.xamarin.com/samples/xamarin-forms/UserInterface/TableView)
| 46.114504 | 462 | 0.697567 | eng_Latn | 0.904751 |
d3e5cded200b9d619a95967b2b5f20405eacfa43 | 243 | md | Markdown | README.md | ZhiHaotomokou/Tetris-CortexM0 | 94bbd4b0d90d65dc606dd2acf8604f90842181a6 | [
"MIT"
] | null | null | null | README.md | ZhiHaotomokou/Tetris-CortexM0 | 94bbd4b0d90d65dc606dd2acf8604f90842181a6 | [
"MIT"
] | null | null | null | README.md | ZhiHaotomokou/Tetris-CortexM0 | 94bbd4b0d90d65dc606dd2acf8604f90842181a6 | [
"MIT"
] | null | null | null | # Tetris-CortexM0
Tetris game under Cortex-M0 Learning Board
Warning: If you want to use this repository for your own project, please refer to https://www.nuvoton.com/export/resource-files/AN0001_NuMicro_Cortex-M_Code_Protection_EN_V1.00.pdf
| 48.6 | 180 | 0.82716 | yue_Hant | 0.489871 |
d3e5d4227c185c6fae95da8a795cd054c4e4d6df | 669 | md | Markdown | _posts/java/C/CRLException/2021-01-01-CRLException.md | w3api/w3api | 681462ece7265723031a88bec5285209d0e125bf | [
"MIT"
] | 1 | 2021-09-15T20:32:10.000Z | 2021-09-15T20:32:10.000Z | _posts/java/C/CRLException/2021-01-01-CRLException.md | w3api/w3api | 681462ece7265723031a88bec5285209d0e125bf | [
"MIT"
] | 20 | 2021-01-17T01:13:46.000Z | 2021-06-20T21:16:02.000Z | _posts/java/C/CRLException/2021-01-01-CRLException.md | w3api/w3api | 681462ece7265723031a88bec5285209d0e125bf | [
"MIT"
] | 2 | 2021-09-15T20:32:08.000Z | 2022-02-20T16:57:46.000Z | ---
title: CRLException
permalink: /Java/CRLException/
date: 2021-01-11
key: Java.C.CRLException
category: Java
tags: ['java se', 'java.security.cert', 'java.base', 'clase java', 'Java 1.2']
sidebar:
nav: java
---
## Descripción
{{site.data.Java.C.CRLException.description }}
## Sintaxis
~~~java
public class CRLException extends GeneralSecurityException
~~~
## Constructores
* [CRLException()](/Java/CRLException/CRLException/)
## Ejemplo
~~~java
{{ site.data.Java.C.CRLException.code}}
~~~
## Artículos
<ul>
{%- for _ldc in site.data.Java.C.CRLException.ldc -%}
<li>
<a href="{{_ldc['url'] }}">{{ _ldc['nombre'] }}</a>
</li>
{%- endfor -%}
</ul>
| 18.583333 | 78 | 0.654709 | kor_Hang | 0.173625 |
d3e628a95c03b025bf74386dad0a58947d56aded | 25,258 | md | Markdown | _posts/2022-01-22-info-2017-423603-28260.md | seed-info/apt-info-sub | 5d3a83a8da1bd659d7d4392146f97ddbbaf7633f | [
"MIT"
] | null | null | null | _posts/2022-01-22-info-2017-423603-28260.md | seed-info/apt-info-sub | 5d3a83a8da1bd659d7d4392146f97ddbbaf7633f | [
"MIT"
] | null | null | null | _posts/2022-01-22-info-2017-423603-28260.md | seed-info/apt-info-sub | 5d3a83a8da1bd659d7d4392146f97ddbbaf7633f | [
"MIT"
] | null | null | null | ---
layout: post
comments: true
title: 루원시티센트럴타운
categories: [아파트정보]
permalink: /apt/인천광역시서구신현동루원시티센트럴타운
---
루원시티센트럴타운 실거래 상세정보
<script type="text/javascript">
google.charts.load('current', {'packages':['line', 'corechart']});
google.charts.setOnLoadCallback(drawChart);
function drawChart() {
var data = new google.visualization.DataTable();
data.addColumn('date', '거래일');
data.addColumn('number', "매매");
data.addColumn('number', "전세");
data.addColumn('number', "전매");
data.addRows([[new Date(Date.parse("2022-01-18")), null, 27825, null], [new Date(Date.parse("2022-01-15")), null, 31500, null], [new Date(Date.parse("2022-01-15")), null, 27300, null], [new Date(Date.parse("2022-01-10")), null, 35000, null], [new Date(Date.parse("2022-01-08")), null, 24100, null], [new Date(Date.parse("2022-01-06")), null, 34000, null], [new Date(Date.parse("2022-01-04")), null, 30000, null], [new Date(Date.parse("2021-12-29")), null, null, null], [new Date(Date.parse("2021-12-26")), null, 28000, null], [new Date(Date.parse("2021-12-20")), null, 23000, null], [new Date(Date.parse("2021-12-18")), null, 34000, null], [new Date(Date.parse("2021-12-16")), null, 33000, null], [new Date(Date.parse("2021-12-15")), null, null, null], [new Date(Date.parse("2021-12-10")), null, 27300, null], [new Date(Date.parse("2021-12-06")), 57500, null, null], [new Date(Date.parse("2021-11-22")), 63500, null, null], [new Date(Date.parse("2021-11-17")), null, 29900, null], [new Date(Date.parse("2021-11-10")), null, 35000, null], [new Date(Date.parse("2021-11-07")), null, 35000, null], [new Date(Date.parse("2021-11-07")), null, null, null], [new Date(Date.parse("2021-10-27")), 63000, null, null], [new Date(Date.parse("2021-10-24")), null, 41000, null], [new Date(Date.parse("2021-10-19")), null, 30000, null], [new Date(Date.parse("2021-10-17")), null, 35000, null], [new Date(Date.parse("2021-10-16")), null, 38000, null], [new Date(Date.parse("2021-10-06")), 59600, null, null], [new Date(Date.parse("2021-10-04")), null, 37000, null], [new Date(Date.parse("2021-10-02")), null, 35000, null], [new Date(Date.parse("2021-09-25")), null, 25700, null], [new Date(Date.parse("2021-09-19")), 67650, null, null], [new Date(Date.parse("2021-09-15")), null, 26250, null], [new Date(Date.parse("2021-09-14")), 60000, null, null], [new Date(Date.parse("2021-09-11")), null, null, null], [new Date(Date.parse("2021-09-10")), null, 39000, null], [new Date(Date.parse("2021-09-10")), null, null, null], [new Date(Date.parse("2021-09-07")), null, 35000, null], [new Date(Date.parse("2021-09-04")), null, 43000, null], [new Date(Date.parse("2021-08-21")), null, 26000, null], [new Date(Date.parse("2021-08-21")), null, 36000, null], [new Date(Date.parse("2021-08-21")), null, 35000, null], [new Date(Date.parse("2021-08-14")), 65000, null, null], [new Date(Date.parse("2021-08-13")), 65000, null, null], [new Date(Date.parse("2021-08-11")), null, null, null], [new Date(Date.parse("2021-08-09")), 62000, null, null], [new Date(Date.parse("2021-08-07")), 63700, null, null], [new Date(Date.parse("2021-08-05")), null, 35000, null], [new Date(Date.parse("2021-07-31")), 56000, null, null], [new Date(Date.parse("2021-07-24")), 61800, null, null], [new Date(Date.parse("2021-07-22")), 51000, null, null], [new Date(Date.parse("2021-07-21")), 50700, null, null], [new Date(Date.parse("2021-07-20")), 59500, null, null], [new Date(Date.parse("2021-07-18")), 54400, null, null], [new Date(Date.parse("2021-07-14")), 51500, null, null], [new Date(Date.parse("2021-07-08")), null, 34000, null], [new Date(Date.parse("2021-07-03")), null, 25700, null], [new Date(Date.parse("2021-07-03")), null, 35000, null], [new Date(Date.parse("2021-06-30")), null, null, null], [new Date(Date.parse("2021-06-16")), 55500, null, null], [new Date(Date.parse("2021-06-09")), 49400, null, null], [new Date(Date.parse("2021-06-05")), null, 40000, null], [new Date(Date.parse("2021-05-26")), null, null, null], [new Date(Date.parse("2021-05-22")), null, 25700, null], [new Date(Date.parse("2021-05-18")), 48000, null, null], [new Date(Date.parse("2021-05-16")), 52700, null, null], [new Date(Date.parse("2021-05-15")), 49000, null, null], [new Date(Date.parse("2021-05-13")), null, 40000, null], [new Date(Date.parse("2021-05-12")), null, 37000, null], [new Date(Date.parse("2021-05-06")), 54500, null, null], [new Date(Date.parse("2021-05-06")), null, 40000, null], [new Date(Date.parse("2021-04-28")), 56500, null, null], [new Date(Date.parse("2021-04-28")), 57300, null, null], [new Date(Date.parse("2021-04-27")), null, 28900, null], [new Date(Date.parse("2021-04-16")), 52500, null, null], [new Date(Date.parse("2021-04-14")), 45700, null, null], [new Date(Date.parse("2021-04-09")), 45300, null, null], [new Date(Date.parse("2021-04-01")), null, 37000, null], [new Date(Date.parse("2021-03-30")), null, 36500, null], [new Date(Date.parse("2021-03-28")), 54500, null, null], [new Date(Date.parse("2021-03-27")), null, 28000, null], [new Date(Date.parse("2021-03-23")), 47700, null, null], [new Date(Date.parse("2021-03-20")), 54000, null, null], [new Date(Date.parse("2021-03-18")), 42500, null, null], [new Date(Date.parse("2021-03-18")), null, 35000, null], [new Date(Date.parse("2021-03-10")), null, 37000, null], [new Date(Date.parse("2021-03-09")), null, 36000, null], [new Date(Date.parse("2021-03-06")), 49300, null, null], [new Date(Date.parse("2021-03-04")), 58500, null, null], [new Date(Date.parse("2021-03-03")), 57000, null, null], [new Date(Date.parse("2021-03-02")), 45500, null, null], [new Date(Date.parse("2021-02-27")), 54100, null, null], [new Date(Date.parse("2021-02-27")), 58000, null, null], [new Date(Date.parse("2021-02-27")), null, 39000, null], [new Date(Date.parse("2021-02-23")), 52700, null, null], [new Date(Date.parse("2021-02-20")), 53000, null, null], [new Date(Date.parse("2021-02-15")), 52000, null, null], [new Date(Date.parse("2021-01-30")), 53000, null, null], [new Date(Date.parse("2021-01-30")), null, 43000, null], [new Date(Date.parse("2021-01-29")), 43500, null, null], [new Date(Date.parse("2021-01-28")), null, 26000, null]]);
var options = {
hAxis: {
format: 'yyyy/MM/dd'
},
lineWidth: 0,
pointsVisible: true,
title: '최근 1년간 유형별 실거래가 분포',
legend: { position: 'bottom' }
};
var formatter = new google.visualization.NumberFormat({pattern:'###,###'} );
formatter.format(data, 1);
formatter.format(data, 2);
setTimeout(function() {
var chart = new google.visualization.LineChart(document.getElementById('columnchart_material'));
chart.draw(data, (options));
document.getElementById('loading').style.display = 'none';
}, 200);
}
</script>
<div id="loading" style="z-index:20; display: block; margin-left: 0px">"그래프를 그리고 있습니다"</div>
<div id="columnchart_material" style="width: 95%; margin-left: 0px; display: block"></div>
<!-- contents start -->
<b>역대 전용면적, 거래별 최고가</b>
<table class="sortable">
<tr>
<td>거래</td>
<td>가격</td>
<td>면적</td>
<td>층</td>
<td>거래일</td>
</tr>
<tr>
<td><a style="color: blue">매매</a></td>
<td>67,650</td>
<td>74.98</td>
<td>12</td>
<td>2021-09-19</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>65,000</td>
<td>84.66</td>
<td>12</td>
<td>2021-08-13</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>63,500</td>
<td>74.89</td>
<td>18</td>
<td>2021-11-22</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>60,000</td>
<td>59.96</td>
<td>18</td>
<td>2021-09-14</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>59,600</td>
<td>59.84</td>
<td>10</td>
<td>2021-10-06</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>48,500</td>
<td>74.96</td>
<td>14</td>
<td>2020-12-19</td>
</tr>
<tr>
<td><a style="color: darkgreen">전세</a></td>
<td>43,000</td>
<td>84.66</td>
<td>2</td>
<td>2021-09-04</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>39,000</td>
<td>74.89</td>
<td>20</td>
<td>2021-09-10</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>37,000</td>
<td>74.98</td>
<td>1</td>
<td>2021-10-04</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>36,000</td>
<td>59.96</td>
<td>11</td>
<td>2021-08-21</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>35,000</td>
<td>59.84</td>
<td>11</td>
<td>2021-08-05</td>
</tr>
</table>
<b>최근 1년간 거래 내역</b>
<table class="sortable">
<tr>
<td>거래</td>
<td>가격</td>
<td>면적</td>
<td>층</td>
<td>거래일</td>
</tr>
<tr>
<td><a style="color: darkgreen">전세</a></td>
<td>27,825</td>
<td>74.98</td>
<td>15</td>
<td>2022-01-18</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>31,500</td>
<td>59.96</td>
<td>18</td>
<td>2022-01-15</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>27,300</td>
<td>59.96</td>
<td>17</td>
<td>2022-01-15</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>35,000</td>
<td>84.66</td>
<td>5</td>
<td>2022-01-10</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>24,100</td>
<td>74.98</td>
<td>23</td>
<td>2022-01-08</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>34,000</td>
<td>74.98</td>
<td>4</td>
<td>2022-01-06</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>30,000</td>
<td>59.96</td>
<td>16</td>
<td>2022-01-04</td>
</tr> <tr>
<td><a style="color: darkgoldenrod">월세</a></td>
<td>125 (5,000)</td>
<td>74.96</td>
<td>12</td>
<td>2021-12-29</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>28,000</td>
<td>74.98</td>
<td>2</td>
<td>2021-12-26</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>23,000</td>
<td>59.96</td>
<td>1</td>
<td>2021-12-20</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>34,000</td>
<td>74.89</td>
<td>22</td>
<td>2021-12-18</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>33,000</td>
<td>59.84</td>
<td>7</td>
<td>2021-12-16</td>
</tr> <tr>
<td><a style="color: darkgoldenrod">월세</a></td>
<td>100 (2,000)</td>
<td>59.96</td>
<td>8</td>
<td>2021-12-15</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>27,300</td>
<td>74.98</td>
<td>2</td>
<td>2021-12-10</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>57,500</td>
<td>59.96</td>
<td>14</td>
<td>2021-12-06</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>63,500</td>
<td>74.89</td>
<td>18</td>
<td>2021-11-22</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>29,900</td>
<td>84.66</td>
<td>6</td>
<td>2021-11-17</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>35,000</td>
<td>59.96</td>
<td>6</td>
<td>2021-11-10</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>35,000</td>
<td>74.98</td>
<td>18</td>
<td>2021-11-07</td>
</tr> <tr>
<td><a style="color: darkgoldenrod">월세</a></td>
<td>100 (3,000)</td>
<td>59.96</td>
<td>10</td>
<td>2021-11-07</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>63,000</td>
<td>74.98</td>
<td>7</td>
<td>2021-10-27</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>41,000</td>
<td>84.66</td>
<td>3</td>
<td>2021-10-24</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>30,000</td>
<td>84.66</td>
<td>9</td>
<td>2021-10-19</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>35,000</td>
<td>59.84</td>
<td>8</td>
<td>2021-10-17</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>38,000</td>
<td>84.66</td>
<td>3</td>
<td>2021-10-16</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>59,600</td>
<td>59.84</td>
<td>10</td>
<td>2021-10-06</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>37,000</td>
<td>74.98</td>
<td>1</td>
<td>2021-10-04</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>35,000</td>
<td>59.84</td>
<td>6</td>
<td>2021-10-02</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>25,700</td>
<td>59.84</td>
<td>11</td>
<td>2021-09-25</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>67,650</td>
<td>74.98</td>
<td>12</td>
<td>2021-09-19</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>26,250</td>
<td>59.84</td>
<td>12</td>
<td>2021-09-15</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>60,000</td>
<td>59.96</td>
<td>18</td>
<td>2021-09-14</td>
</tr> <tr>
<td><a style="color: darkgoldenrod">월세</a></td>
<td>30 (35,000)</td>
<td>84.66</td>
<td>14</td>
<td>2021-09-11</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>39,000</td>
<td>74.89</td>
<td>20</td>
<td>2021-09-10</td>
</tr> <tr>
<td><a style="color: darkgoldenrod">월세</a></td>
<td>100 (3,000)</td>
<td>59.96</td>
<td>10</td>
<td>2021-09-10</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>35,000</td>
<td>59.96</td>
<td>14</td>
<td>2021-09-07</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>43,000</td>
<td>84.66</td>
<td>2</td>
<td>2021-09-04</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>26,000</td>
<td>59.84</td>
<td>10</td>
<td>2021-08-21</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>36,000</td>
<td>59.96</td>
<td>11</td>
<td>2021-08-21</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>35,000</td>
<td>59.96</td>
<td>7</td>
<td>2021-08-21</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>65,000</td>
<td>84.66</td>
<td>4</td>
<td>2021-08-14</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>65,000</td>
<td>84.66</td>
<td>12</td>
<td>2021-08-13</td>
</tr> <tr>
<td><a style="color: darkgoldenrod">월세</a></td>
<td>120 (5,000)</td>
<td>74.98</td>
<td>10</td>
<td>2021-08-11</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>62,000</td>
<td>84.66</td>
<td>19</td>
<td>2021-08-09</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>63,700</td>
<td>74.98</td>
<td>6</td>
<td>2021-08-07</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>35,000</td>
<td>59.84</td>
<td>11</td>
<td>2021-08-05</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>56,000</td>
<td>59.96</td>
<td>11</td>
<td>2021-07-31</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>61,800</td>
<td>84.66</td>
<td>20</td>
<td>2021-07-24</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>51,000</td>
<td>74.89</td>
<td>1</td>
<td>2021-07-22</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>50,700</td>
<td>59.96</td>
<td>2</td>
<td>2021-07-21</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>59,500</td>
<td>84.66</td>
<td>13</td>
<td>2021-07-20</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>54,400</td>
<td>59.84</td>
<td>10</td>
<td>2021-07-18</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>51,500</td>
<td>59.84</td>
<td>11</td>
<td>2021-07-14</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>34,000</td>
<td>59.96</td>
<td>9</td>
<td>2021-07-08</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>25,700</td>
<td>59.96</td>
<td>7</td>
<td>2021-07-03</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>35,000</td>
<td>59.96</td>
<td>6</td>
<td>2021-07-03</td>
</tr> <tr>
<td><a style="color: darkgoldenrod">월세</a></td>
<td>130 (3,000)</td>
<td>84.66</td>
<td>15</td>
<td>2021-06-30</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>55,500</td>
<td>74.98</td>
<td>6</td>
<td>2021-06-16</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>49,400</td>
<td>59.84</td>
<td>9</td>
<td>2021-06-09</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>40,000</td>
<td>84.66</td>
<td>6</td>
<td>2021-06-05</td>
</tr> <tr>
<td><a style="color: darkgoldenrod">월세</a></td>
<td>100 (2,000)</td>
<td>59.96</td>
<td>6</td>
<td>2021-05-26</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>25,700</td>
<td>59.96</td>
<td>7</td>
<td>2021-05-22</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>48,000</td>
<td>59.84</td>
<td>13</td>
<td>2021-05-18</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>52,700</td>
<td>84.66</td>
<td>1</td>
<td>2021-05-16</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>49,000</td>
<td>74.89</td>
<td>1</td>
<td>2021-05-15</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>40,000</td>
<td>74.98</td>
<td>6</td>
<td>2021-05-13</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>37,000</td>
<td>74.98</td>
<td>16</td>
<td>2021-05-12</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>54,500</td>
<td>74.98</td>
<td>15</td>
<td>2021-05-06</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>40,000</td>
<td>74.98</td>
<td>15</td>
<td>2021-05-06</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>56,500</td>
<td>84.66</td>
<td>18</td>
<td>2021-04-28</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>57,300</td>
<td>84.66</td>
<td>13</td>
<td>2021-04-28</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>28,900</td>
<td>74.98</td>
<td>18</td>
<td>2021-04-27</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>52,500</td>
<td>84.66</td>
<td>5</td>
<td>2021-04-16</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>45,700</td>
<td>59.96</td>
<td>1</td>
<td>2021-04-14</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>45,300</td>
<td>59.96</td>
<td>5</td>
<td>2021-04-09</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>37,000</td>
<td>74.98</td>
<td>17</td>
<td>2021-04-01</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>36,500</td>
<td>84.66</td>
<td>2</td>
<td>2021-03-30</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>54,500</td>
<td>84.66</td>
<td>16</td>
<td>2021-03-28</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>28,000</td>
<td>59.96</td>
<td>15</td>
<td>2021-03-27</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>47,700</td>
<td>59.96</td>
<td>15</td>
<td>2021-03-23</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>54,000</td>
<td>84.66</td>
<td>17</td>
<td>2021-03-20</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>42,500</td>
<td>59.84</td>
<td>1</td>
<td>2021-03-18</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>35,000</td>
<td>59.84</td>
<td>1</td>
<td>2021-03-18</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>37,000</td>
<td>84.66</td>
<td>4</td>
<td>2021-03-10</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>36,000</td>
<td>84.66</td>
<td>4</td>
<td>2021-03-09</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>49,300</td>
<td>74.98</td>
<td>19</td>
<td>2021-03-06</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>58,500</td>
<td>84.66</td>
<td>11</td>
<td>2021-03-04</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>57,000</td>
<td>84.66</td>
<td>12</td>
<td>2021-03-03</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>45,500</td>
<td>59.96</td>
<td>11</td>
<td>2021-03-02</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>54,100</td>
<td>74.98</td>
<td>16</td>
<td>2021-02-27</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>58,000</td>
<td>84.66</td>
<td>18</td>
<td>2021-02-27</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>39,000</td>
<td>84.66</td>
<td>10</td>
<td>2021-02-27</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>52,700</td>
<td>74.98</td>
<td>9</td>
<td>2021-02-23</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>53,000</td>
<td>84.66</td>
<td>2</td>
<td>2021-02-20</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>52,000</td>
<td>74.89</td>
<td>17</td>
<td>2021-02-15</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>53,000</td>
<td>74.98</td>
<td>17</td>
<td>2021-01-30</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>43,000</td>
<td>74.98</td>
<td>17</td>
<td>2021-01-30</td>
</tr> <tr>
<td><a style="color: blue">매매</a></td>
<td>43,500</td>
<td>59.96</td>
<td>15</td>
<td>2021-01-29</td>
</tr> <tr>
<td><a style="color: darkgreen">전세</a></td>
<td>26,000</td>
<td>74.98</td>
<td>16</td>
<td>2021-01-28</td>
</tr> </table>
<!-- contents end -->
| 34.27137 | 5,654 | 0.462388 | kor_Hang | 0.194651 |
d3e6c6c0b62b35226946137028c59f0c1b31dde8 | 4,848 | md | Markdown | README.md | bhbryant/multipart_parser | b0afdf3a3267053ed13fc1dbc378c5ffb07dbf20 | [
"MIT"
] | 2 | 2015-08-09T04:34:08.000Z | 2016-01-15T06:38:26.000Z | README.md | bhbryant/multipart_parser | b0afdf3a3267053ed13fc1dbc378c5ffb07dbf20 | [
"MIT"
] | null | null | null | README.md | bhbryant/multipart_parser | b0afdf3a3267053ed13fc1dbc378c5ffb07dbf20 | [
"MIT"
] | null | null | null | # MultipartParser
A c backed multipart/form-data parser.
Ruby extenstion for https://github.com/iafonov/multipart-parser-c, modeled after http_parser.rb
Multipart-parser C has been modfied to have a more consistent callback structure with http_parser.rb
## Installation
Add this line to your application's Gemfile:
```ruby
gem 'multipart_parser'
```
And then execute:
$ bundle
Or install it yourself as:
$ gem install multipart_parser
## Usage
```ruby
require 'multipart_parser'
parser = MultipartParser.new("Boundary+17376C87E2579930")
# Setups callbacks
parser.on_message_begin = proc { puts "# => on_message_begin"}
parser.on_part_begin = proc { puts "# => on_part_begin"}
parser.on_headers_complete = proc {|headers| puts "# => on_headers_complete: #{headers.inspect}"}
parser.on_data = proc {|data| puts "# => on_data: #{data}"}
parser.on_part_complete = proc {puts "# => on_part_complete"}
parser.on_message_complete = proc {puts "# => on_message_complete"}
parser << "--Boundary+17376C87E2579930\r\n"
# => on_message_begin
# => on_part_begin
parser << "Content-Disposition: form-data; name=ID1\r\n"
parser << "Content-Type: text/plain\r\n\r\n"
parser << "This is the first part.\r\n"
# => on_headers_complete: {"Content-Disposition"=>"form-data; name=ID1", "Content-Type"=>"text/plain"}
# => on_data: This is the first part.
parser << "--Boundary+17376C87E2579930\r\n"
# => on_part_complete
# => on_part_begin
# =>
parser << "Content-Disposition: form-data; name=ID2\r\n"
parser << "Content-Type: text/plain\r\n\r\n"
parser << "This is the second part.\r\n";
parser << "--Boundary+17376C87E2579930--\r\n"
# => on_headers_complete: {"Content-Disposition"=>"form-data; name=ID2", "Content-Type"=>"text/plain"}
# => on_data: This is the second part.
# => on_part_complete
# => on_message_complete
```
```ruby
# Also allows you to pass a callback object
class Handler
def on_message_begin; puts "# => on_message_begin"; end
def on_part_begin; puts "# => on_part_begin"; end
def on_headers_complete(headers); puts "# => on_headers_complete: #{headers.inspect}"; end
def on_data(data); puts "# => on_data: #{data}"; end
def on_part_complete; puts "# => on_part_complete"; end
def on_message_complete; puts "# => on_message_complete"; end
end
parser = MultipartParser.new("Boundary+17376C87E2579930", Handler.new)
parser << "--Boundary+17376C87E2579930\r\n"
# => on_message_begin
# => on_part_begin
parser << "Content-Disposition: form-data; name=ID1\r\n"
parser << "Content-Type: text/plain\r\n\r\n"
parser << "This is the first part.\r\n"
# => on_headers_complete: {"Content-Disposition"=>"form-data; name=ID1", "Content-Type"=>"text/plain"}
# => on_data: This is the first part.
parser << "--Boundary+17376C87E2579930\r\n"
# => on_part_complete
# => on_part_begin
parser << "Content-Disposition: form-data; name=ID2\r\n"
parser << "Content-Type: text/plain\r\n\r\n"
parser << "This is the second part.\r\n";
parser << "--Boundary+17376C87E2579930--\r\n"
# => on_headers_complete: {"Content-Disposition"=>"form-data; name=ID2", "Content-Type"=>"text/plain"}
# => on_data: This is the second part.
# => on_part_complete
# => on_message_complete
```
```ruby
# Accepts a config paramter to modify how the headers are returned
parser = MultipartParser.new("Boundary+17376C87E2579930", Handler.new, :arrays)
# valid values are :arrays, :strings, :mixed
parser << "--Boundary+17376C87E2579930\r\n"
parser << "Content-Disposition: form-data; name=ID_A\r\n"
parser << "Content-Disposition: form-data; name=ID_B\r\n"
parser << "Content-Type: text/plain\r\n\r\n"
parser << "This is the first part.\r\n"
# => on_headers_complete: {"Content-Disposition"=>["form-data; name=ID_A", "form-data; name=ID_B"], "Content-Type"=>["text/plain"]}
parser = MultipartParser.new("Boundary+17376C87E2579930", Handler.new, :strings)
# => on_headers_complete: {"Content-Disposition"=>"form-data; name=ID_A, form-data; name=ID_B", "Content-Type"=>"text/plain"}
parser = MultipartParser.new("Boundary+17376C87E2579930", Handler.new, :mixed)
# => on_headers_complete: {"Content-Disposition"=>["form-data; name=ID_A", "form-data; name=ID_B"], "Content-Type"=>"text/plain"}
```
```ruby
# Set the default(:mixed)
MultipartParser.default_header_value_type = :arrays
parser = MultipartParser.new("Boundary+17376C87E2579930", Handler.new)
# => on_headers_complete: {"Content-Disposition"=>["form-data; name=ID_A", "form-data; name=ID_B"], "Content-Type"=>["text/plain"]}
```
## Contributing
1. Fork it ( https://github.com/[my-github-username]/multipart_parser/fork )
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Add some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create a new Pull Request
| 26.491803 | 131 | 0.708127 | eng_Latn | 0.297355 |
d3e6f67d77b8f1592711ca002fbff24da7dc477d | 1,332 | md | Markdown | README.md | seratch/hackernews4s | 6873117d4aaac190734bffa5a66ee1b652613928 | [
"MIT"
] | 4 | 2015-04-09T02:42:55.000Z | 2016-10-13T10:02:41.000Z | README.md | seratch/hackernews4s | 6873117d4aaac190734bffa5a66ee1b652613928 | [
"MIT"
] | null | null | null | README.md | seratch/hackernews4s | 6873117d4aaac190734bffa5a66ee1b652613928 | [
"MIT"
] | null | null | null | # HackerNews API Client in Scala
[](https://travis-ci.org/seratch/hackernews4s)
[](https://maven-badges.herokuapp.com/maven-central/com.github.seratch/hackernews4s_2.11)
This library is made for Scala hackers.
## HackerNews API?
- http://blog.ycombinator.com/hacker-news-api
- https://hacker-news.firebaseio.com/
- https://github.com/HackerNews/API
## How to use
```scala
libraryDependencies += "com.github.seratch" %% "hackernews4s" % "0.6.0"
```
## APIs
See the scaladocs: [hackernews4s.v0.HackerNews](https://oss.sonatype.org/service/local/repositories/releases/archive/com/github/seratch/hackernews4s_2.11/0.6.0/hackernews4s_2.11-0.6.0-javadoc.jar/!/index.html#hackernews4s.v0.HackerNews)
## Examples
```scala
import hackernews4s.v0._
val topStories: Seq[Item] = HackerNews.getTopStories()
topStories.foreach(println)
```
See [HackerNews.scala](https://github.com/seratch/hackernews4s/blob/master/src/main/scala/hackernews4s/v0/HackerNews.scala) for details:
You can try the code examples in comments. We confirm they're valid code by using [sbt-doctest](https://github.com/tkawachi/sbt-doctest).
## License
The MIT License
| 34.153846 | 236 | 0.767267 | yue_Hant | 0.678978 |
d3e7bb52af705f2473b756045098ae6fb41ddabc | 1,928 | md | Markdown | Instructions/Labs/LAB_AK_06_Lab1_Ex4_Connect_Threat_Intel.md | MicrosoftLearning/SC-200T00A-Microsoft-Security-Operations-Analyst.ja-jp | d1843838a4db1bb8ecd15de354b25afd717bece8 | [
"MIT"
] | null | null | null | Instructions/Labs/LAB_AK_06_Lab1_Ex4_Connect_Threat_Intel.md | MicrosoftLearning/SC-200T00A-Microsoft-Security-Operations-Analyst.ja-jp | d1843838a4db1bb8ecd15de354b25afd717bece8 | [
"MIT"
] | null | null | null | Instructions/Labs/LAB_AK_06_Lab1_Ex4_Connect_Threat_Intel.md | MicrosoftLearning/SC-200T00A-Microsoft-Security-Operations-Analyst.ja-jp | d1843838a4db1bb8ecd15de354b25afd717bece8 | [
"MIT"
] | null | null | null | ---
lab:
title: 演習 4 ‐ データ コネクタを使用して Microsoft Sentinel に脅威インテリジェンスを接続する
module: Module 6 - Connect logs to Microsoft Sentinel
ms.openlocfilehash: c106b8d5c651727d942e59ed4da7a45d0a5d18a5
ms.sourcegitcommit: 175df7de88c9a609f8caf39840664bf992c5b6dc
ms.translationtype: HT
ms.contentlocale: ja-JP
ms.lasthandoff: 02/05/2022
ms.locfileid: "138025484"
---
# <a name="module-6---lab-1---exercise-4---connect-threat-intelligence-to-microsoft-sentinel-using-data-connectors"></a>モジュール 6 - ラボ 1 - 演習 4 - データ コネクタを使用して脅威インテリジェンスを Microsoft Sentinel に接続する
## <a name="lab-scenario"></a>ラボのシナリオ
あなたは、Microsoft Sentinel を実装した会社で働いているセキュリティ運用アナリストです。 組織内の多くのデータ ソースからのログ データを接続する方法について学習する必要があります。 最後に、既知の脅威を検出して優先順位を付ける機能を強化するために、脅威インテリジェンス フィードを接続します。
### <a name="task-1-connect-threat-intelligence"></a>タスク 1:脅威インテリジェンスの接続
このタスクでは、脅威インテリジェンス プロバイダーを脅威インテリジェンス - TAXII コネクタに接続します。
1. 管理者として WIN1 仮想マシンにログインします。パスワードは **Pa55w.rd**。
1. Edge ブラウザーで、Azure portal (https://portal.azure.com) ) に移動します。
1. **[サインイン]** ダイアログ ボックスで、ラボ ホスティング プロバイダーから提供された **テナントの電子メール** アカウントをコピーして貼り付け、 **[次へ]** を選択します。
1. **[パスワードの入力]** ダイアログ ボックスで、ラボ ホスティング プロバイダーから提供された **テナントのパスワード** をコピーして貼り付け、 **[サインイン]** を選択します。
1. Azure portal の検索バーに「*Sentinel*」と入力してから、 **[Microsoft Sentinel]** を選択します。
1. 先ほど作成した Microsoft Sentinel ワークスペースを選択します。
1. [データ コネクタ] タブで、 **[脅威インテリジェンス - TAXII]** コネクタを検索します。
1. コネクタ情報ブレードで「**コネクタページを開く**」を選択します。
1. *[構成]* 領域の **[フレンドリ名 (サーバー)]** フィールドに「*PhishURLs*」と入力します。
1. API ルートの URL に「 https://limo.anomali.com/api/v1/taxii2/feeds/ 」と入力します。
1. コレクションIDに「**107**」を入力します。
1. ユーザー名に「**ゲスト**」を入力します。
1. パスワードに「**ゲスト**」と入力します。
1. ここで **[追加]** ボタンを選択します。 フィッシング URL はプルされ、ThreatIntelligenceIndicator テーブルに入力されます。
>**注:** 別のコレクションを追加する場合は、Edge ブラウザーで https://limo.anomali.com/api/v1/taxii2/feeds/collections/ を開き、ゲスト ユーザー名とパスワードを使用して、使用可能な別の ID を確認します。
## <a name="you-have-completed-the-lab"></a>これでラボは完了です。
| 35.703704 | 193 | 0.75 | yue_Hant | 0.517882 |
d3e86d9b24d32b3338d432c09029a4d0c55e8480 | 41,228 | md | Markdown | repos/postgres/remote/10-alpine.md | giridharkota/repo-info | 4544efd679054003cf76e3cce0980757e4391490 | [
"Apache-2.0"
] | null | null | null | repos/postgres/remote/10-alpine.md | giridharkota/repo-info | 4544efd679054003cf76e3cce0980757e4391490 | [
"Apache-2.0"
] | null | null | null | repos/postgres/remote/10-alpine.md | giridharkota/repo-info | 4544efd679054003cf76e3cce0980757e4391490 | [
"Apache-2.0"
] | 1 | 2019-12-12T12:30:49.000Z | 2019-12-12T12:30:49.000Z | ## `postgres:10-alpine`
```console
$ docker pull postgres@sha256:d09024b892b57663cb22e466fe0d1281bc19565affe7ab2796dc3c307cb0317b
```
- Manifest MIME: `application/vnd.docker.distribution.manifest.list.v2+json`
- Platforms:
- linux; amd64
- linux; arm variant v6
- linux; arm64 variant v8
- linux; 386
- linux; ppc64le
- linux; s390x
### `postgres:10-alpine` - linux; amd64
```console
$ docker pull postgres@sha256:d89ec9b53b2f1a55ccc4d33811778dd071c84ba8a12fae7b2165442fafb4a835
```
- Docker Version: 17.06.2-ce
- Manifest MIME: `application/vnd.docker.distribution.manifest.v2+json`
- Total Size: **29.5 MB (29478195 bytes)**
(compressed transfer size, not on-disk size)
- Image ID: `sha256:5df4f9af771f31b44478e7092d7e2a440d6b1628a33b199183792ce80164b0c0`
- Entrypoint: `["docker-entrypoint.sh"]`
- Default Command: `["postgres"]`
```dockerfile
# Fri, 06 Jul 2018 14:14:06 GMT
ADD file:25f61d70254b9807a40cd3e8d820f6a5ec0e1e596de04e325f6a33810393e95a in /
# Fri, 06 Jul 2018 14:14:06 GMT
CMD ["/bin/sh"]
# Wed, 11 Jul 2018 00:47:50 GMT
RUN set -ex; postgresHome="$(getent passwd postgres)"; postgresHome="$(echo "$postgresHome" | cut -d: -f6)"; [ "$postgresHome" = '/var/lib/postgresql' ]; mkdir -p "$postgresHome"; chown -R postgres:postgres "$postgresHome"
# Wed, 11 Jul 2018 00:47:50 GMT
ENV LANG=en_US.utf8
# Wed, 11 Jul 2018 00:47:51 GMT
RUN mkdir /docker-entrypoint-initdb.d
# Wed, 11 Jul 2018 00:50:58 GMT
ENV PG_MAJOR=10
# Fri, 10 Aug 2018 22:11:17 GMT
ENV PG_VERSION=10.5
# Fri, 10 Aug 2018 22:11:17 GMT
ENV PG_SHA256=6c8e616c91a45142b85c0aeb1f29ebba4a361309e86469e0fb4617b6a73c4011
# Fri, 10 Aug 2018 22:13:39 GMT
RUN set -ex && apk add --no-cache --virtual .fetch-deps ca-certificates openssl tar && wget -O postgresql.tar.bz2 "https://ftp.postgresql.org/pub/source/v$PG_VERSION/postgresql-$PG_VERSION.tar.bz2" && echo "$PG_SHA256 *postgresql.tar.bz2" | sha256sum -c - && mkdir -p /usr/src/postgresql && tar --extract --file postgresql.tar.bz2 --directory /usr/src/postgresql --strip-components 1 && rm postgresql.tar.bz2 && apk add --no-cache --virtual .build-deps bison coreutils dpkg-dev dpkg flex gcc libc-dev libedit-dev libxml2-dev libxslt-dev make openssl-dev perl-utils perl-ipc-run util-linux-dev zlib-dev icu-dev && cd /usr/src/postgresql && awk '$1 == "#define" && $2 == "DEFAULT_PGSOCKET_DIR" && $3 == "\"/tmp\"" { $3 = "\"/var/run/postgresql\""; print; next } { print }' src/include/pg_config_manual.h > src/include/pg_config_manual.h.new && grep '/var/run/postgresql' src/include/pg_config_manual.h.new && mv src/include/pg_config_manual.h.new src/include/pg_config_manual.h && gnuArch="$(dpkg-architecture --query DEB_BUILD_GNU_TYPE)" && wget -O config/config.guess 'https://git.savannah.gnu.org/cgit/config.git/plain/config.guess?id=7d3d27baf8107b630586c962c057e22149653deb' && wget -O config/config.sub 'https://git.savannah.gnu.org/cgit/config.git/plain/config.sub?id=7d3d27baf8107b630586c962c057e22149653deb' && ./configure --build="$gnuArch" --enable-integer-datetimes --enable-thread-safety --enable-tap-tests --disable-rpath --with-uuid=e2fs --with-gnu-ld --with-pgport=5432 --with-system-tzdata=/usr/share/zoneinfo --prefix=/usr/local --with-includes=/usr/local/include --with-libraries=/usr/local/lib --with-openssl --with-libxml --with-libxslt --with-icu && make -j "$(nproc)" world && make install-world && make -C contrib install && runDeps="$( scanelf --needed --nobanner --format '%n#p' --recursive /usr/local | tr ',' '\n' | sort -u | awk 'system("[ -e /usr/local/lib/" $1 " ]") == 0 { next } { print "so:" $1 }' )" && apk add --no-cache --virtual .postgresql-rundeps $runDeps bash su-exec tzdata && apk del .fetch-deps .build-deps && cd / && rm -rf /usr/src/postgresql /usr/local/share/doc /usr/local/share/man && find /usr/local -name '*.a' -delete
# Fri, 10 Aug 2018 22:13:42 GMT
RUN sed -ri "s!^#?(listen_addresses)\s*=\s*\S+.*!\1 = '*'!" /usr/local/share/postgresql/postgresql.conf.sample
# Fri, 10 Aug 2018 22:13:43 GMT
RUN mkdir -p /var/run/postgresql && chown -R postgres:postgres /var/run/postgresql && chmod 2777 /var/run/postgresql
# Fri, 10 Aug 2018 22:13:43 GMT
ENV PGDATA=/var/lib/postgresql/data
# Fri, 10 Aug 2018 22:13:44 GMT
RUN mkdir -p "$PGDATA" && chown -R postgres:postgres "$PGDATA" && chmod 777 "$PGDATA" # this 777 will be replaced by 700 at runtime (allows semi-arbitrary "--user" values)
# Fri, 10 Aug 2018 22:13:44 GMT
VOLUME [/var/lib/postgresql/data]
# Fri, 10 Aug 2018 22:13:45 GMT
COPY file:ea83254240307acb41cff4ba67980cb25f52871869af6e6c49a729ba283f82ed in /usr/local/bin/
# Fri, 10 Aug 2018 22:13:45 GMT
RUN ln -s usr/local/bin/docker-entrypoint.sh / # backwards compat
# Fri, 10 Aug 2018 22:13:46 GMT
ENTRYPOINT ["docker-entrypoint.sh"]
# Fri, 10 Aug 2018 22:13:46 GMT
EXPOSE 5432/tcp
# Fri, 10 Aug 2018 22:13:46 GMT
CMD ["postgres"]
```
- Layers:
- `sha256:8e3ba11ec2a2b39ab372c60c16b421536e50e5ce64a0bc81765c2e38381bcff6`
Last Modified: Fri, 06 Jul 2018 04:15:58 GMT
Size: 2.2 MB (2206542 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:fbb9adb8cff82fca4ee56d72d6f8084c02ba5ef008039979a1379e9162703cc6`
Last Modified: Wed, 11 Jul 2018 01:05:01 GMT
Size: 149.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:aa8817b9e00daac6d86d105d480aa5c8ef78b76903e15283154197774f718e7e`
Last Modified: Wed, 11 Jul 2018 01:05:01 GMT
Size: 115.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:53941c55569fdc3fbb42e6108e59949220ccb3cd1f131b6ec66889d4143838c8`
Last Modified: Fri, 10 Aug 2018 22:36:11 GMT
Size: 27.3 MB (27261471 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:f66d499835407dfca77ef2ae16684682a2c182ca6a9354e0849cd0ee5f52d6a7`
Last Modified: Fri, 10 Aug 2018 22:36:00 GMT
Size: 7.3 KB (7268 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:d94e4c4de54db6fdee183118b42d86660783559798702580fa2fceb07e0ac1a9`
Last Modified: Fri, 10 Aug 2018 22:35:59 GMT
Size: 128.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:480f0e20fdcc6b966366f9f25de01a36eeddf028ad249c4f0b86f163bcd90a3b`
Last Modified: Fri, 10 Aug 2018 22:35:59 GMT
Size: 168.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:949d41f63bfb1de8694f1a5b2fc332ec3a8bc7cffb6984203336dfa7fdbb2c61`
Last Modified: Fri, 10 Aug 2018 22:35:59 GMT
Size: 2.2 KB (2233 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:1dd1895e17aed31bc0980ee677ed5ac9b714fcc3c464ce731a778c221c091816`
Last Modified: Fri, 10 Aug 2018 22:36:01 GMT
Size: 121.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
### `postgres:10-alpine` - linux; arm variant v6
```console
$ docker pull postgres@sha256:a05d25543d6fba321eb23e42b9a7c96995a17e0b0959d77dd4f27c71d47b1eb8
```
- Docker Version: 17.06.2-ce
- Manifest MIME: `application/vnd.docker.distribution.manifest.v2+json`
- Total Size: **28.4 MB (28392017 bytes)**
(compressed transfer size, not on-disk size)
- Image ID: `sha256:ce37fba281e9f4c9d90b6d6518e29c03160ea59ba8edf1e2d614d7873b8bf6ee`
- Entrypoint: `["docker-entrypoint.sh"]`
- Default Command: `["postgres"]`
```dockerfile
# Fri, 06 Jul 2018 07:53:29 GMT
ADD file:122e3422d9afa971806601812374fdd9d00c8edc8e9a6df7256e2caa85fab6d1 in /
# Fri, 06 Jul 2018 07:53:30 GMT
COPY file:0f1d36dd7d8d53613b275660a88c5bf9b608ea8aa73a8054cb8bdbd73fd971ac in /etc/localtime
# Fri, 06 Jul 2018 07:53:30 GMT
CMD ["/bin/sh"]
# Sat, 14 Jul 2018 07:49:44 GMT
RUN set -ex; postgresHome="$(getent passwd postgres)"; postgresHome="$(echo "$postgresHome" | cut -d: -f6)"; [ "$postgresHome" = '/var/lib/postgresql' ]; mkdir -p "$postgresHome"; chown -R postgres:postgres "$postgresHome"
# Sat, 14 Jul 2018 07:49:45 GMT
ENV LANG=en_US.utf8
# Sat, 14 Jul 2018 07:49:49 GMT
RUN mkdir /docker-entrypoint-initdb.d
# Sat, 14 Jul 2018 08:30:08 GMT
ENV PG_MAJOR=10
# Sat, 11 Aug 2018 08:30:33 GMT
ENV PG_VERSION=10.5
# Sat, 11 Aug 2018 08:30:33 GMT
ENV PG_SHA256=6c8e616c91a45142b85c0aeb1f29ebba4a361309e86469e0fb4617b6a73c4011
# Sat, 11 Aug 2018 09:10:31 GMT
RUN set -ex && apk add --no-cache --virtual .fetch-deps ca-certificates openssl tar && wget -O postgresql.tar.bz2 "https://ftp.postgresql.org/pub/source/v$PG_VERSION/postgresql-$PG_VERSION.tar.bz2" && echo "$PG_SHA256 *postgresql.tar.bz2" | sha256sum -c - && mkdir -p /usr/src/postgresql && tar --extract --file postgresql.tar.bz2 --directory /usr/src/postgresql --strip-components 1 && rm postgresql.tar.bz2 && apk add --no-cache --virtual .build-deps bison coreutils dpkg-dev dpkg flex gcc libc-dev libedit-dev libxml2-dev libxslt-dev make openssl-dev perl-utils perl-ipc-run util-linux-dev zlib-dev icu-dev && cd /usr/src/postgresql && awk '$1 == "#define" && $2 == "DEFAULT_PGSOCKET_DIR" && $3 == "\"/tmp\"" { $3 = "\"/var/run/postgresql\""; print; next } { print }' src/include/pg_config_manual.h > src/include/pg_config_manual.h.new && grep '/var/run/postgresql' src/include/pg_config_manual.h.new && mv src/include/pg_config_manual.h.new src/include/pg_config_manual.h && gnuArch="$(dpkg-architecture --query DEB_BUILD_GNU_TYPE)" && wget -O config/config.guess 'https://git.savannah.gnu.org/cgit/config.git/plain/config.guess?id=7d3d27baf8107b630586c962c057e22149653deb' && wget -O config/config.sub 'https://git.savannah.gnu.org/cgit/config.git/plain/config.sub?id=7d3d27baf8107b630586c962c057e22149653deb' && ./configure --build="$gnuArch" --enable-integer-datetimes --enable-thread-safety --enable-tap-tests --disable-rpath --with-uuid=e2fs --with-gnu-ld --with-pgport=5432 --with-system-tzdata=/usr/share/zoneinfo --prefix=/usr/local --with-includes=/usr/local/include --with-libraries=/usr/local/lib --with-openssl --with-libxml --with-libxslt --with-icu && make -j "$(nproc)" world && make install-world && make -C contrib install && runDeps="$( scanelf --needed --nobanner --format '%n#p' --recursive /usr/local | tr ',' '\n' | sort -u | awk 'system("[ -e /usr/local/lib/" $1 " ]") == 0 { next } { print "so:" $1 }' )" && apk add --no-cache --virtual .postgresql-rundeps $runDeps bash su-exec tzdata && apk del .fetch-deps .build-deps && cd / && rm -rf /usr/src/postgresql /usr/local/share/doc /usr/local/share/man && find /usr/local -name '*.a' -delete
# Sat, 11 Aug 2018 09:10:37 GMT
RUN sed -ri "s!^#?(listen_addresses)\s*=\s*\S+.*!\1 = '*'!" /usr/local/share/postgresql/postgresql.conf.sample
# Sat, 11 Aug 2018 09:10:42 GMT
RUN mkdir -p /var/run/postgresql && chown -R postgres:postgres /var/run/postgresql && chmod 2777 /var/run/postgresql
# Sat, 11 Aug 2018 09:10:42 GMT
ENV PGDATA=/var/lib/postgresql/data
# Sat, 11 Aug 2018 09:10:46 GMT
RUN mkdir -p "$PGDATA" && chown -R postgres:postgres "$PGDATA" && chmod 777 "$PGDATA" # this 777 will be replaced by 700 at runtime (allows semi-arbitrary "--user" values)
# Sat, 11 Aug 2018 09:10:47 GMT
VOLUME [/var/lib/postgresql/data]
# Sat, 11 Aug 2018 09:10:48 GMT
COPY file:ea83254240307acb41cff4ba67980cb25f52871869af6e6c49a729ba283f82ed in /usr/local/bin/
# Sat, 11 Aug 2018 09:10:53 GMT
RUN ln -s usr/local/bin/docker-entrypoint.sh / # backwards compat
# Sat, 11 Aug 2018 09:10:54 GMT
ENTRYPOINT ["docker-entrypoint.sh"]
# Sat, 11 Aug 2018 09:10:54 GMT
EXPOSE 5432/tcp
# Sat, 11 Aug 2018 09:10:55 GMT
CMD ["postgres"]
```
- Layers:
- `sha256:ee7d700abbf209aa401ef5d53f86af298a25e8154b3259036e9307d08f255c5d`
Last Modified: Fri, 06 Jul 2018 07:53:45 GMT
Size: 2.1 MB (2145998 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:a1653f4692c1ccea69cd46121d4f1371957f66e97a20141371dd4da10ebaec19`
Last Modified: Fri, 06 Jul 2018 07:53:45 GMT
Size: 175.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:be89c0bdfe21471b24dd28c380bc35cebe521da2e9615c5be939deafd734624c`
Last Modified: Sat, 14 Jul 2018 11:40:24 GMT
Size: 180.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:852d2cfc5d822ef2846113436b3d9d9264722ad578117a2e770ea982600c9511`
Last Modified: Sat, 14 Jul 2018 11:40:22 GMT
Size: 149.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:16e39e434588e28fe9226bb7946a0bd3e6b3766c0dfa36ba375f60eaefb2a68f`
Last Modified: Sat, 11 Aug 2018 11:29:26 GMT
Size: 26.2 MB (26235521 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:5b940d8a242778c947bf8bf5b7e73ce26c3fc13639318de6cf32c345ce4024cc`
Last Modified: Sat, 11 Aug 2018 11:28:46 GMT
Size: 7.3 KB (7276 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:ae8268304b4827361932ff170c91bccdbf87fdc49585cc08b73579e9fe4d0f9f`
Last Modified: Sat, 11 Aug 2018 11:28:45 GMT
Size: 161.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:89fe6a6701b9952e1dc4d3814d985f72bf631166e772756b0295e30ed7371fc9`
Last Modified: Sat, 11 Aug 2018 11:28:46 GMT
Size: 202.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:577ea1a5a8066a147fdcdb7961d66b8fe0e6f202d733582b1814646a0a271238`
Last Modified: Sat, 11 Aug 2018 11:28:46 GMT
Size: 2.2 KB (2234 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:4133f44c1361300dc8a08a4a5171155bf8bc245e9d4c9eebc733478ff98886d6`
Last Modified: Sat, 11 Aug 2018 11:28:46 GMT
Size: 121.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
### `postgres:10-alpine` - linux; arm64 variant v8
```console
$ docker pull postgres@sha256:b012dd8f4e6365e29b4ea60591038bf5fcb7d8bd24bf21cbffcfacc65dfe31b5
```
- Docker Version: 17.06.2-ce
- Manifest MIME: `application/vnd.docker.distribution.manifest.v2+json`
- Total Size: **28.2 MB (28167091 bytes)**
(compressed transfer size, not on-disk size)
- Image ID: `sha256:87f24e45bb928d47349026dad90b2b582a228f8e63c91f62086cb9269147efea`
- Entrypoint: `["docker-entrypoint.sh"]`
- Default Command: `["postgres"]`
```dockerfile
# Fri, 06 Jul 2018 08:41:03 GMT
ADD file:199a5a48bddabaf1f649f58f3b17c323a1aa1a50e939dfdea3542e4041e91b7b in /
# Fri, 06 Jul 2018 08:41:03 GMT
COPY file:0f1d36dd7d8d53613b275660a88c5bf9b608ea8aa73a8054cb8bdbd73fd971ac in /etc/localtime
# Fri, 06 Jul 2018 08:41:04 GMT
CMD ["/bin/sh"]
# Wed, 11 Jul 2018 08:58:15 GMT
RUN set -ex; postgresHome="$(getent passwd postgres)"; postgresHome="$(echo "$postgresHome" | cut -d: -f6)"; [ "$postgresHome" = '/var/lib/postgresql' ]; mkdir -p "$postgresHome"; chown -R postgres:postgres "$postgresHome"
# Wed, 11 Jul 2018 08:58:15 GMT
ENV LANG=en_US.utf8
# Wed, 11 Jul 2018 08:58:17 GMT
RUN mkdir /docker-entrypoint-initdb.d
# Wed, 11 Jul 2018 09:03:33 GMT
ENV PG_MAJOR=10
# Sat, 11 Aug 2018 10:49:51 GMT
ENV PG_VERSION=10.5
# Sat, 11 Aug 2018 10:49:54 GMT
ENV PG_SHA256=6c8e616c91a45142b85c0aeb1f29ebba4a361309e86469e0fb4617b6a73c4011
# Sat, 11 Aug 2018 10:54:13 GMT
RUN set -ex && apk add --no-cache --virtual .fetch-deps ca-certificates openssl tar && wget -O postgresql.tar.bz2 "https://ftp.postgresql.org/pub/source/v$PG_VERSION/postgresql-$PG_VERSION.tar.bz2" && echo "$PG_SHA256 *postgresql.tar.bz2" | sha256sum -c - && mkdir -p /usr/src/postgresql && tar --extract --file postgresql.tar.bz2 --directory /usr/src/postgresql --strip-components 1 && rm postgresql.tar.bz2 && apk add --no-cache --virtual .build-deps bison coreutils dpkg-dev dpkg flex gcc libc-dev libedit-dev libxml2-dev libxslt-dev make openssl-dev perl-utils perl-ipc-run util-linux-dev zlib-dev icu-dev && cd /usr/src/postgresql && awk '$1 == "#define" && $2 == "DEFAULT_PGSOCKET_DIR" && $3 == "\"/tmp\"" { $3 = "\"/var/run/postgresql\""; print; next } { print }' src/include/pg_config_manual.h > src/include/pg_config_manual.h.new && grep '/var/run/postgresql' src/include/pg_config_manual.h.new && mv src/include/pg_config_manual.h.new src/include/pg_config_manual.h && gnuArch="$(dpkg-architecture --query DEB_BUILD_GNU_TYPE)" && wget -O config/config.guess 'https://git.savannah.gnu.org/cgit/config.git/plain/config.guess?id=7d3d27baf8107b630586c962c057e22149653deb' && wget -O config/config.sub 'https://git.savannah.gnu.org/cgit/config.git/plain/config.sub?id=7d3d27baf8107b630586c962c057e22149653deb' && ./configure --build="$gnuArch" --enable-integer-datetimes --enable-thread-safety --enable-tap-tests --disable-rpath --with-uuid=e2fs --with-gnu-ld --with-pgport=5432 --with-system-tzdata=/usr/share/zoneinfo --prefix=/usr/local --with-includes=/usr/local/include --with-libraries=/usr/local/lib --with-openssl --with-libxml --with-libxslt --with-icu && make -j "$(nproc)" world && make install-world && make -C contrib install && runDeps="$( scanelf --needed --nobanner --format '%n#p' --recursive /usr/local | tr ',' '\n' | sort -u | awk 'system("[ -e /usr/local/lib/" $1 " ]") == 0 { next } { print "so:" $1 }' )" && apk add --no-cache --virtual .postgresql-rundeps $runDeps bash su-exec tzdata && apk del .fetch-deps .build-deps && cd / && rm -rf /usr/src/postgresql /usr/local/share/doc /usr/local/share/man && find /usr/local -name '*.a' -delete
# Sat, 11 Aug 2018 10:54:15 GMT
RUN sed -ri "s!^#?(listen_addresses)\s*=\s*\S+.*!\1 = '*'!" /usr/local/share/postgresql/postgresql.conf.sample
# Sat, 11 Aug 2018 10:54:33 GMT
RUN mkdir -p /var/run/postgresql && chown -R postgres:postgres /var/run/postgresql && chmod 2777 /var/run/postgresql
# Sat, 11 Aug 2018 10:54:33 GMT
ENV PGDATA=/var/lib/postgresql/data
# Sat, 11 Aug 2018 10:54:35 GMT
RUN mkdir -p "$PGDATA" && chown -R postgres:postgres "$PGDATA" && chmod 777 "$PGDATA" # this 777 will be replaced by 700 at runtime (allows semi-arbitrary "--user" values)
# Sat, 11 Aug 2018 10:54:36 GMT
VOLUME [/var/lib/postgresql/data]
# Sat, 11 Aug 2018 10:54:37 GMT
COPY file:ea83254240307acb41cff4ba67980cb25f52871869af6e6c49a729ba283f82ed in /usr/local/bin/
# Sat, 11 Aug 2018 10:54:38 GMT
RUN ln -s usr/local/bin/docker-entrypoint.sh / # backwards compat
# Sat, 11 Aug 2018 10:54:39 GMT
ENTRYPOINT ["docker-entrypoint.sh"]
# Sat, 11 Aug 2018 10:54:56 GMT
EXPOSE 5432/tcp
# Sat, 11 Aug 2018 10:54:57 GMT
CMD ["postgres"]
```
- Layers:
- `sha256:47e04371c99027fae42871b720fdc6cdddcb65062bfa05f0c3bb0a594cb5bbbd`
Last Modified: Wed, 27 Jun 2018 19:15:35 GMT
Size: 2.1 MB (2099514 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:b4103359e1ecd9a7253d8b8a041d4e81db1ff4a5e1950bc0e02305d221c9e6c2`
Last Modified: Fri, 06 Jul 2018 08:42:09 GMT
Size: 176.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:437d5ea65f8f13faa3042893bc9dd0a4e5b68562c0eb1f9aeaf258936fe72140`
Last Modified: Wed, 11 Jul 2018 09:26:40 GMT
Size: 148.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:cf835df21096513cbddcf69a9b532c79832f2cd1c8b47e78e9776fc76eb24340`
Last Modified: Wed, 11 Jul 2018 09:26:41 GMT
Size: 115.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:29b4e744483cc77038930b8fb4a44ab762ee1bb797a69fb2096e28cc3ef46e96`
Last Modified: Sat, 11 Aug 2018 13:07:28 GMT
Size: 26.1 MB (26057221 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:754968dc29e2f3c1377a2f10894b4710076dcc75f0ca210d339b7ece8b8cc2d8`
Last Modified: Sat, 11 Aug 2018 13:07:17 GMT
Size: 7.3 KB (7269 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:d201cca107eb5796e3c00743e6623381535a085a7352e4cf721d73ab95a2361f`
Last Modified: Sat, 11 Aug 2018 13:07:17 GMT
Size: 129.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:e88b1cfc6485b8b4e3693a2254bee99be74988aaf7aea95a48b1d61999a2c6df`
Last Modified: Sat, 11 Aug 2018 13:07:17 GMT
Size: 170.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:95ec9bc2a7a450ab7c2712e8d268a7d74b4a93e4d282d6a26fc2d753d8d49414`
Last Modified: Sat, 11 Aug 2018 13:07:17 GMT
Size: 2.2 KB (2228 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:6c3ace28c13f82b7d65200807fbba18cd3c7ad8bd0046b3a925ccae72dd39574`
Last Modified: Sat, 11 Aug 2018 13:07:17 GMT
Size: 121.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
### `postgres:10-alpine` - linux; 386
```console
$ docker pull postgres@sha256:fb50656a2733df8c4d06f864904e44b8f87817ec9c3a91d5e8a559c5dce41697
```
- Docker Version: 17.06.2-ce
- Manifest MIME: `application/vnd.docker.distribution.manifest.v2+json`
- Total Size: **30.2 MB (30206915 bytes)**
(compressed transfer size, not on-disk size)
- Image ID: `sha256:0b6ad4b55bab3d474fd413d8b7d925e5147c5537c71405c14699b8a246cf294e`
- Entrypoint: `["docker-entrypoint.sh"]`
- Default Command: `["postgres"]`
```dockerfile
# Fri, 06 Jul 2018 15:02:06 GMT
ADD file:ebd40cda2f6087daf4d14e6dc1ee0b4a0fb5dc96c70129be8e07de0e5c628312 in /
# Fri, 06 Jul 2018 15:02:07 GMT
COPY file:0f1d36dd7d8d53613b275660a88c5bf9b608ea8aa73a8054cb8bdbd73fd971ac in /etc/localtime
# Fri, 06 Jul 2018 15:02:07 GMT
CMD ["/bin/sh"]
# Wed, 11 Jul 2018 10:50:41 GMT
RUN set -ex; postgresHome="$(getent passwd postgres)"; postgresHome="$(echo "$postgresHome" | cut -d: -f6)"; [ "$postgresHome" = '/var/lib/postgresql' ]; mkdir -p "$postgresHome"; chown -R postgres:postgres "$postgresHome"
# Wed, 11 Jul 2018 10:50:42 GMT
ENV LANG=en_US.utf8
# Wed, 11 Jul 2018 10:50:42 GMT
RUN mkdir /docker-entrypoint-initdb.d
# Wed, 11 Jul 2018 10:53:45 GMT
ENV PG_MAJOR=10
# Sat, 11 Aug 2018 11:23:37 GMT
ENV PG_VERSION=10.5
# Sat, 11 Aug 2018 11:23:37 GMT
ENV PG_SHA256=6c8e616c91a45142b85c0aeb1f29ebba4a361309e86469e0fb4617b6a73c4011
# Sat, 11 Aug 2018 11:26:21 GMT
RUN set -ex && apk add --no-cache --virtual .fetch-deps ca-certificates openssl tar && wget -O postgresql.tar.bz2 "https://ftp.postgresql.org/pub/source/v$PG_VERSION/postgresql-$PG_VERSION.tar.bz2" && echo "$PG_SHA256 *postgresql.tar.bz2" | sha256sum -c - && mkdir -p /usr/src/postgresql && tar --extract --file postgresql.tar.bz2 --directory /usr/src/postgresql --strip-components 1 && rm postgresql.tar.bz2 && apk add --no-cache --virtual .build-deps bison coreutils dpkg-dev dpkg flex gcc libc-dev libedit-dev libxml2-dev libxslt-dev make openssl-dev perl-utils perl-ipc-run util-linux-dev zlib-dev icu-dev && cd /usr/src/postgresql && awk '$1 == "#define" && $2 == "DEFAULT_PGSOCKET_DIR" && $3 == "\"/tmp\"" { $3 = "\"/var/run/postgresql\""; print; next } { print }' src/include/pg_config_manual.h > src/include/pg_config_manual.h.new && grep '/var/run/postgresql' src/include/pg_config_manual.h.new && mv src/include/pg_config_manual.h.new src/include/pg_config_manual.h && gnuArch="$(dpkg-architecture --query DEB_BUILD_GNU_TYPE)" && wget -O config/config.guess 'https://git.savannah.gnu.org/cgit/config.git/plain/config.guess?id=7d3d27baf8107b630586c962c057e22149653deb' && wget -O config/config.sub 'https://git.savannah.gnu.org/cgit/config.git/plain/config.sub?id=7d3d27baf8107b630586c962c057e22149653deb' && ./configure --build="$gnuArch" --enable-integer-datetimes --enable-thread-safety --enable-tap-tests --disable-rpath --with-uuid=e2fs --with-gnu-ld --with-pgport=5432 --with-system-tzdata=/usr/share/zoneinfo --prefix=/usr/local --with-includes=/usr/local/include --with-libraries=/usr/local/lib --with-openssl --with-libxml --with-libxslt --with-icu && make -j "$(nproc)" world && make install-world && make -C contrib install && runDeps="$( scanelf --needed --nobanner --format '%n#p' --recursive /usr/local | tr ',' '\n' | sort -u | awk 'system("[ -e /usr/local/lib/" $1 " ]") == 0 { next } { print "so:" $1 }' )" && apk add --no-cache --virtual .postgresql-rundeps $runDeps bash su-exec tzdata && apk del .fetch-deps .build-deps && cd / && rm -rf /usr/src/postgresql /usr/local/share/doc /usr/local/share/man && find /usr/local -name '*.a' -delete
# Sat, 11 Aug 2018 11:26:30 GMT
RUN sed -ri "s!^#?(listen_addresses)\s*=\s*\S+.*!\1 = '*'!" /usr/local/share/postgresql/postgresql.conf.sample
# Sat, 11 Aug 2018 11:26:31 GMT
RUN mkdir -p /var/run/postgresql && chown -R postgres:postgres /var/run/postgresql && chmod 2777 /var/run/postgresql
# Sat, 11 Aug 2018 11:26:31 GMT
ENV PGDATA=/var/lib/postgresql/data
# Sat, 11 Aug 2018 11:26:32 GMT
RUN mkdir -p "$PGDATA" && chown -R postgres:postgres "$PGDATA" && chmod 777 "$PGDATA" # this 777 will be replaced by 700 at runtime (allows semi-arbitrary "--user" values)
# Sat, 11 Aug 2018 11:26:33 GMT
VOLUME [/var/lib/postgresql/data]
# Sat, 11 Aug 2018 11:26:33 GMT
COPY file:ea83254240307acb41cff4ba67980cb25f52871869af6e6c49a729ba283f82ed in /usr/local/bin/
# Sat, 11 Aug 2018 11:26:34 GMT
RUN ln -s usr/local/bin/docker-entrypoint.sh / # backwards compat
# Sat, 11 Aug 2018 11:26:47 GMT
ENTRYPOINT ["docker-entrypoint.sh"]
# Sat, 11 Aug 2018 11:26:47 GMT
EXPOSE 5432/tcp
# Sat, 11 Aug 2018 11:26:48 GMT
CMD ["postgres"]
```
- Layers:
- `sha256:ef15772113129a5330876ce10683bbf6509a4c4c99b3a99894dcbc7560975052`
Last Modified: Fri, 06 Jul 2018 15:02:46 GMT
Size: 2.3 MB (2270920 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:6df692b84cf35e6038d677f9ab7de2a3c671c57671043da1d20d99252e0d9c42`
Last Modified: Fri, 06 Jul 2018 15:02:43 GMT
Size: 175.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:68f1f64a5de43fc9cf3d68cbe05f2a18e17a39e44d1512ce0b3911f2bc59f77e`
Last Modified: Wed, 11 Jul 2018 11:09:05 GMT
Size: 148.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:72347c8a13f638fd36f586cfa21f37b4da1dd04bab6b6204d3ce2dc8f04d98e8`
Last Modified: Wed, 11 Jul 2018 11:09:04 GMT
Size: 115.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:5d77d752dd8d5285c3b238b977bfb904880664a418631ed82823bd09a740fc82`
Last Modified: Sat, 11 Aug 2018 11:49:20 GMT
Size: 27.9 MB (27925636 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:a0888ccd39fdd5bc8f9ae6f9405fe08686f800b49a5462ee6b44b6130bd9001c`
Last Modified: Sat, 11 Aug 2018 11:49:06 GMT
Size: 7.3 KB (7268 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:ed8ebbfcefc9f01d6aaee0fde94081d52e04753de08d42d4dfd1f6d6a9eae1eb`
Last Modified: Sat, 11 Aug 2018 11:49:06 GMT
Size: 130.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:4d8e4c3fa9c8b3fe05b713947a3f6f58609f7225c7ccd22871497ead758a1496`
Last Modified: Sat, 11 Aug 2018 11:49:06 GMT
Size: 170.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:a830561d4bd81db660ec806dc70c7805dd91a2ec63cc0b355637444541313758`
Last Modified: Sat, 11 Aug 2018 11:49:06 GMT
Size: 2.2 KB (2232 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:4dab066c68264b468f1fa23c9e4157d2d1585617a80bcb561205cfe8e60ace70`
Last Modified: Sat, 11 Aug 2018 11:49:06 GMT
Size: 121.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
### `postgres:10-alpine` - linux; ppc64le
```console
$ docker pull postgres@sha256:a7dd2577142086b3bb0846881ac0f44692dc7d789bf004ef1dc398ca0fa66982
```
- Docker Version: 17.06.2-ce
- Manifest MIME: `application/vnd.docker.distribution.manifest.v2+json`
- Total Size: **29.2 MB (29151341 bytes)**
(compressed transfer size, not on-disk size)
- Image ID: `sha256:01e10ca0489826380bd647e3290100a1bd39a0053c1cc29c873f65df577c88d5`
- Entrypoint: `["docker-entrypoint.sh"]`
- Default Command: `["postgres"]`
```dockerfile
# Fri, 06 Jul 2018 08:18:09 GMT
ADD file:4ff20d593b16518d45b1b1d6efdab141199316dba7a53ce7459249f5de690dfd in /
# Fri, 06 Jul 2018 08:18:10 GMT
COPY file:0f1d36dd7d8d53613b275660a88c5bf9b608ea8aa73a8054cb8bdbd73fd971ac in /etc/localtime
# Fri, 06 Jul 2018 08:18:11 GMT
CMD ["/bin/sh"]
# Wed, 11 Jul 2018 10:01:28 GMT
RUN set -ex; postgresHome="$(getent passwd postgres)"; postgresHome="$(echo "$postgresHome" | cut -d: -f6)"; [ "$postgresHome" = '/var/lib/postgresql' ]; mkdir -p "$postgresHome"; chown -R postgres:postgres "$postgresHome"
# Wed, 11 Jul 2018 10:01:29 GMT
ENV LANG=en_US.utf8
# Wed, 11 Jul 2018 10:01:32 GMT
RUN mkdir /docker-entrypoint-initdb.d
# Wed, 11 Jul 2018 10:07:00 GMT
ENV PG_MAJOR=10
# Sat, 11 Aug 2018 09:40:32 GMT
ENV PG_VERSION=10.5
# Sat, 11 Aug 2018 09:40:35 GMT
ENV PG_SHA256=6c8e616c91a45142b85c0aeb1f29ebba4a361309e86469e0fb4617b6a73c4011
# Sat, 11 Aug 2018 09:46:47 GMT
RUN set -ex && apk add --no-cache --virtual .fetch-deps ca-certificates openssl tar && wget -O postgresql.tar.bz2 "https://ftp.postgresql.org/pub/source/v$PG_VERSION/postgresql-$PG_VERSION.tar.bz2" && echo "$PG_SHA256 *postgresql.tar.bz2" | sha256sum -c - && mkdir -p /usr/src/postgresql && tar --extract --file postgresql.tar.bz2 --directory /usr/src/postgresql --strip-components 1 && rm postgresql.tar.bz2 && apk add --no-cache --virtual .build-deps bison coreutils dpkg-dev dpkg flex gcc libc-dev libedit-dev libxml2-dev libxslt-dev make openssl-dev perl-utils perl-ipc-run util-linux-dev zlib-dev icu-dev && cd /usr/src/postgresql && awk '$1 == "#define" && $2 == "DEFAULT_PGSOCKET_DIR" && $3 == "\"/tmp\"" { $3 = "\"/var/run/postgresql\""; print; next } { print }' src/include/pg_config_manual.h > src/include/pg_config_manual.h.new && grep '/var/run/postgresql' src/include/pg_config_manual.h.new && mv src/include/pg_config_manual.h.new src/include/pg_config_manual.h && gnuArch="$(dpkg-architecture --query DEB_BUILD_GNU_TYPE)" && wget -O config/config.guess 'https://git.savannah.gnu.org/cgit/config.git/plain/config.guess?id=7d3d27baf8107b630586c962c057e22149653deb' && wget -O config/config.sub 'https://git.savannah.gnu.org/cgit/config.git/plain/config.sub?id=7d3d27baf8107b630586c962c057e22149653deb' && ./configure --build="$gnuArch" --enable-integer-datetimes --enable-thread-safety --enable-tap-tests --disable-rpath --with-uuid=e2fs --with-gnu-ld --with-pgport=5432 --with-system-tzdata=/usr/share/zoneinfo --prefix=/usr/local --with-includes=/usr/local/include --with-libraries=/usr/local/lib --with-openssl --with-libxml --with-libxslt --with-icu && make -j "$(nproc)" world && make install-world && make -C contrib install && runDeps="$( scanelf --needed --nobanner --format '%n#p' --recursive /usr/local | tr ',' '\n' | sort -u | awk 'system("[ -e /usr/local/lib/" $1 " ]") == 0 { next } { print "so:" $1 }' )" && apk add --no-cache --virtual .postgresql-rundeps $runDeps bash su-exec tzdata && apk del .fetch-deps .build-deps && cd / && rm -rf /usr/src/postgresql /usr/local/share/doc /usr/local/share/man && find /usr/local -name '*.a' -delete
# Sat, 11 Aug 2018 09:46:50 GMT
RUN sed -ri "s!^#?(listen_addresses)\s*=\s*\S+.*!\1 = '*'!" /usr/local/share/postgresql/postgresql.conf.sample
# Sat, 11 Aug 2018 09:46:52 GMT
RUN mkdir -p /var/run/postgresql && chown -R postgres:postgres /var/run/postgresql && chmod 2777 /var/run/postgresql
# Sat, 11 Aug 2018 09:46:53 GMT
ENV PGDATA=/var/lib/postgresql/data
# Sat, 11 Aug 2018 09:46:56 GMT
RUN mkdir -p "$PGDATA" && chown -R postgres:postgres "$PGDATA" && chmod 777 "$PGDATA" # this 777 will be replaced by 700 at runtime (allows semi-arbitrary "--user" values)
# Sat, 11 Aug 2018 09:46:58 GMT
VOLUME [/var/lib/postgresql/data]
# Sat, 11 Aug 2018 09:47:00 GMT
COPY file:ea83254240307acb41cff4ba67980cb25f52871869af6e6c49a729ba283f82ed in /usr/local/bin/
# Sat, 11 Aug 2018 09:47:02 GMT
RUN ln -s usr/local/bin/docker-entrypoint.sh / # backwards compat
# Sat, 11 Aug 2018 09:47:04 GMT
ENTRYPOINT ["docker-entrypoint.sh"]
# Sat, 11 Aug 2018 09:47:06 GMT
EXPOSE 5432/tcp
# Sat, 11 Aug 2018 09:47:07 GMT
CMD ["postgres"]
```
- Layers:
- `sha256:e642bcb5b1890a07dd2fc8be2bc35edf5e2b651d4993e71caef03b4b43ace970`
Last Modified: Fri, 06 Jul 2018 08:18:44 GMT
Size: 2.2 MB (2194861 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:2e09410b1fce4c4630b3bc57c6ee158ee9821ec415d0acaa1607b9e0bcf76d91`
Last Modified: Fri, 06 Jul 2018 08:18:43 GMT
Size: 176.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:99cf65db7a2a46b10230d6919606d6370a8f89f4126cb2e72c0e8e2b817cc9bd`
Last Modified: Wed, 11 Jul 2018 10:24:59 GMT
Size: 180.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:831e22a24061ee9561c3ce50ae211d56c4d735d93bc6f6ba82661c69ebaaea94`
Last Modified: Wed, 11 Jul 2018 10:24:59 GMT
Size: 149.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:cc13d067e3243929f148769ea65e730415b345aa69030b69dc3af2e47072e37a`
Last Modified: Sat, 11 Aug 2018 10:18:22 GMT
Size: 26.9 MB (26945998 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:7959398ec44a859dfad07a4810bcfc0dac843b47c34be3681fd799582bb92b7e`
Last Modified: Sat, 11 Aug 2018 10:18:03 GMT
Size: 7.3 KB (7263 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:e3dc869c82e2c858f2febd6ed77d5e144090f89b4da520b3c34f1fe5d29a5c55`
Last Modified: Sat, 11 Aug 2018 10:18:03 GMT
Size: 161.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:a54076e44479aa2f70828aa758dbc2157f8edba9b731cade4f0861393b53012d`
Last Modified: Sat, 11 Aug 2018 10:18:03 GMT
Size: 202.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:4c447f3285a6ff327ac040a073aa3d2e323ebab8f617e7ab6f7b46eeca5d61ce`
Last Modified: Sat, 11 Aug 2018 10:18:03 GMT
Size: 2.2 KB (2230 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:d347d85f86e1e6750af2c558a5cb39fde83b859cf015283bdb37489fb3169031`
Last Modified: Sat, 11 Aug 2018 10:18:03 GMT
Size: 121.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
### `postgres:10-alpine` - linux; s390x
```console
$ docker pull postgres@sha256:8075a85ede2a17a5a9df21936478a743e10c7e70b2654164238fe6be3167c1fb
```
- Docker Version: 17.06.2-ce
- Manifest MIME: `application/vnd.docker.distribution.manifest.v2+json`
- Total Size: **29.5 MB (29474214 bytes)**
(compressed transfer size, not on-disk size)
- Image ID: `sha256:acc9b1d7247b2e9969a74c52c602246f0c5cd451ffe1c6de6bbf186895b6b8ab`
- Entrypoint: `["docker-entrypoint.sh"]`
- Default Command: `["postgres"]`
```dockerfile
# Fri, 06 Jul 2018 11:41:42 GMT
ADD file:376dd7fc34ad39570d2e20f3704305e788ae613c589445b3e8fb880147c3eb59 in /
# Fri, 06 Jul 2018 11:41:43 GMT
COPY file:0f1d36dd7d8d53613b275660a88c5bf9b608ea8aa73a8054cb8bdbd73fd971ac in /etc/localtime
# Fri, 06 Jul 2018 11:41:43 GMT
CMD ["/bin/sh"]
# Wed, 11 Jul 2018 11:52:46 GMT
RUN set -ex; postgresHome="$(getent passwd postgres)"; postgresHome="$(echo "$postgresHome" | cut -d: -f6)"; [ "$postgresHome" = '/var/lib/postgresql' ]; mkdir -p "$postgresHome"; chown -R postgres:postgres "$postgresHome"
# Wed, 11 Jul 2018 11:52:46 GMT
ENV LANG=en_US.utf8
# Wed, 11 Jul 2018 11:52:47 GMT
RUN mkdir /docker-entrypoint-initdb.d
# Wed, 11 Jul 2018 11:55:40 GMT
ENV PG_MAJOR=10
# Sat, 11 Aug 2018 12:25:22 GMT
ENV PG_VERSION=10.5
# Sat, 11 Aug 2018 12:25:22 GMT
ENV PG_SHA256=6c8e616c91a45142b85c0aeb1f29ebba4a361309e86469e0fb4617b6a73c4011
# Sat, 11 Aug 2018 12:27:57 GMT
RUN set -ex && apk add --no-cache --virtual .fetch-deps ca-certificates openssl tar && wget -O postgresql.tar.bz2 "https://ftp.postgresql.org/pub/source/v$PG_VERSION/postgresql-$PG_VERSION.tar.bz2" && echo "$PG_SHA256 *postgresql.tar.bz2" | sha256sum -c - && mkdir -p /usr/src/postgresql && tar --extract --file postgresql.tar.bz2 --directory /usr/src/postgresql --strip-components 1 && rm postgresql.tar.bz2 && apk add --no-cache --virtual .build-deps bison coreutils dpkg-dev dpkg flex gcc libc-dev libedit-dev libxml2-dev libxslt-dev make openssl-dev perl-utils perl-ipc-run util-linux-dev zlib-dev icu-dev && cd /usr/src/postgresql && awk '$1 == "#define" && $2 == "DEFAULT_PGSOCKET_DIR" && $3 == "\"/tmp\"" { $3 = "\"/var/run/postgresql\""; print; next } { print }' src/include/pg_config_manual.h > src/include/pg_config_manual.h.new && grep '/var/run/postgresql' src/include/pg_config_manual.h.new && mv src/include/pg_config_manual.h.new src/include/pg_config_manual.h && gnuArch="$(dpkg-architecture --query DEB_BUILD_GNU_TYPE)" && wget -O config/config.guess 'https://git.savannah.gnu.org/cgit/config.git/plain/config.guess?id=7d3d27baf8107b630586c962c057e22149653deb' && wget -O config/config.sub 'https://git.savannah.gnu.org/cgit/config.git/plain/config.sub?id=7d3d27baf8107b630586c962c057e22149653deb' && ./configure --build="$gnuArch" --enable-integer-datetimes --enable-thread-safety --enable-tap-tests --disable-rpath --with-uuid=e2fs --with-gnu-ld --with-pgport=5432 --with-system-tzdata=/usr/share/zoneinfo --prefix=/usr/local --with-includes=/usr/local/include --with-libraries=/usr/local/lib --with-openssl --with-libxml --with-libxslt --with-icu && make -j "$(nproc)" world && make install-world && make -C contrib install && runDeps="$( scanelf --needed --nobanner --format '%n#p' --recursive /usr/local | tr ',' '\n' | sort -u | awk 'system("[ -e /usr/local/lib/" $1 " ]") == 0 { next } { print "so:" $1 }' )" && apk add --no-cache --virtual .postgresql-rundeps $runDeps bash su-exec tzdata && apk del .fetch-deps .build-deps && cd / && rm -rf /usr/src/postgresql /usr/local/share/doc /usr/local/share/man && find /usr/local -name '*.a' -delete
# Sat, 11 Aug 2018 12:27:58 GMT
RUN sed -ri "s!^#?(listen_addresses)\s*=\s*\S+.*!\1 = '*'!" /usr/local/share/postgresql/postgresql.conf.sample
# Sat, 11 Aug 2018 12:27:59 GMT
RUN mkdir -p /var/run/postgresql && chown -R postgres:postgres /var/run/postgresql && chmod 2777 /var/run/postgresql
# Sat, 11 Aug 2018 12:27:59 GMT
ENV PGDATA=/var/lib/postgresql/data
# Sat, 11 Aug 2018 12:27:59 GMT
RUN mkdir -p "$PGDATA" && chown -R postgres:postgres "$PGDATA" && chmod 777 "$PGDATA" # this 777 will be replaced by 700 at runtime (allows semi-arbitrary "--user" values)
# Sat, 11 Aug 2018 12:27:59 GMT
VOLUME [/var/lib/postgresql/data]
# Sat, 11 Aug 2018 12:28:00 GMT
COPY file:ea83254240307acb41cff4ba67980cb25f52871869af6e6c49a729ba283f82ed in /usr/local/bin/
# Sat, 11 Aug 2018 12:28:00 GMT
RUN ln -s usr/local/bin/docker-entrypoint.sh / # backwards compat
# Sat, 11 Aug 2018 12:28:00 GMT
ENTRYPOINT ["docker-entrypoint.sh"]
# Sat, 11 Aug 2018 12:28:01 GMT
EXPOSE 5432/tcp
# Sat, 11 Aug 2018 12:28:01 GMT
CMD ["postgres"]
```
- Layers:
- `sha256:cdf21ace94188d512903eea53ea8559677e0e6ffd5d6a180a1d88c118abc96fc`
Last Modified: Fri, 06 Jul 2018 11:42:01 GMT
Size: 2.3 MB (2307471 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:ea178433f2f09080fbbf77f09da1b16d588b7ced380d495a2f2ad00d28468338`
Last Modified: Fri, 06 Jul 2018 11:42:00 GMT
Size: 175.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:398fccf2ffccf7250c1715d26143118893acb524a48bced68b09ea5b8eec51d5`
Last Modified: Wed, 11 Jul 2018 12:07:23 GMT
Size: 149.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:9218ec3eacdd51c0198b5043ce0115b269b534e8da4fd8aa0f07d1b7e3f1f1ab`
Last Modified: Wed, 11 Jul 2018 12:07:23 GMT
Size: 115.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:c2af030b6361a1d210429175e5a975de83ff31121439a1a5c257b86600568145`
Last Modified: Sat, 11 Aug 2018 13:11:19 GMT
Size: 27.2 MB (27156391 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:14aa2a2eaed2fc2aa0b6ec951f7c0a46b58dc5bf1de5e4a34b6744b304d52431`
Last Modified: Sat, 11 Aug 2018 13:11:13 GMT
Size: 7.3 KB (7265 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:44df75bb4398e3b231b785311bc7fd8087cbd79c6657441010272c76502eeb4f`
Last Modified: Sat, 11 Aug 2018 13:11:13 GMT
Size: 128.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:36e4e319c24f736dd1d16ef53895387e1afc424fe2d9c16f9b43f73d525f38c5`
Last Modified: Sat, 11 Aug 2018 13:11:13 GMT
Size: 169.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:70df74b34f6c1ca4b552c4f6616818d9dd2a7a19e762563c3b9b3e78c9518122`
Last Modified: Sat, 11 Aug 2018 13:11:15 GMT
Size: 2.2 KB (2230 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:b99046badd7ef4212b271889e05aa431ef3a981cfe60c265856eda4325c2dd4c`
Last Modified: Sat, 11 Aug 2018 13:11:13 GMT
Size: 121.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
| 68.371476 | 2,302 | 0.72526 | yue_Hant | 0.148443 |