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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
9ad5fc41151768f7e7a2952c714d1d619eb7c107 | 2,554 | md | Markdown | controls/radlayoutcontrol/features/layoutgroups/layoutcontrolgroup.md | emididam/xaml-docs | 3d12be96f9da56b45ce5512adb5cf34d84c55e5c | [
"Unlicense",
"MIT"
] | null | null | null | controls/radlayoutcontrol/features/layoutgroups/layoutcontrolgroup.md | emididam/xaml-docs | 3d12be96f9da56b45ce5512adb5cf34d84c55e5c | [
"Unlicense",
"MIT"
] | null | null | null | controls/radlayoutcontrol/features/layoutgroups/layoutcontrolgroup.md | emididam/xaml-docs | 3d12be96f9da56b45ce5512adb5cf34d84c55e5c | [
"Unlicense",
"MIT"
] | null | null | null | ---
title: LayoutControlGroup
page_title: LayoutControlGroup
description: LayoutControlGroup
slug: radlayoutcontrol-features-layougroups-layoutcontrolgroup
tags: feature, displaymode, display, mode, layoutcontrolgroup
published: True
position: 1
---
# LayoutControlGroup
__LayoutControlGroup__ is one of the few layout groups supported by the __RadLayoutControl__. When it comes to visual appearance __LayoutControlGroup__ is the most simple of the groups. It displays only a border around its items.
> You can read the [Layout Panel]({%slug radlayoutcontrol-getting-started-layoutpanel%}) article to get better understanding on how the layout groups are arranging their children.
__Figure 1__ shows how a LayoutControlGroup with few children looks. And __Example 1__ demonstrates how to set up a group.
#### __[XAML] Example 1: Setting up LayoutControlGroup__
{{region layoutcontrol-features-layoutcontrolgroup-01}}
<telerik:RadLayoutControl>
<telerik:LayoutControlGroup >
<Button Content="Item 1" />
<Button Content="Item 2" />
<Button Content="Item 3" />
<Button Content="Item 4" />
</telerik:LayoutControlGroup>
</telerik:RadLayoutControl>
{{endregion}}
#### __Figure 1: LayoutControlGroup__
You can add __LayoutControlGroup__ into another layout group (see __Example 2__).
#### __[XAML] Example 2: Nesting LayoutControlGroups__
{{region layoutcontrol-features-layoutcontrolgroup-02}}
<telerik:RadLayoutControl>
<telerik:LayoutControlGroup>
<telerik:LayoutControlGroup Orientation="Vertical">
<Button Content="Item 1" />
<Button Content="Item 2" />
<telerik:LayoutControlGroup>
<Button Content="Item 1" />
<Button Content="Item 2" />
</telerik:LayoutControlGroup>
<Button Content="Item 3" />
</telerik:LayoutControlGroup>
<Button Content="Item 4" />
<Button Content="Item 5" />
<Button Content="Item 6" />
</telerik:LayoutControlGroup>
</telerik:RadLayoutControl>
{{endregion}}
#### __Figure 2: Nested LayoutControlGroups__
## See Also
* [Getting Started]({%slug radlayoutcontrol-getting-started%})
* [Layout Groups Overview]({%slug radlayoutcontrol-features-layoutgroups-overview%})
* [LayoutControlTabGroup]({%slug radlayoutcontrol-features-layoutgroups-layoutcontroltabgroup%})
* [LayoutControlExpanderGroup]({%slug radlayoutcontrol-features-layoutgroups-layoutcontrolexpandergroup%}) | 40.539683 | 230 | 0.752153 | eng_Latn | 0.728744 |
9ad6d91f56e78d5a48d63af80e3ba0e2e1d54ca3 | 318 | md | Markdown | PHUSION_DEPLOYMENT.md | phusion/support_central | 618230e5caa478c71c45f8894d89086c32ae3668 | [
"MIT"
] | 7 | 2018-04-19T10:46:05.000Z | 2021-09-19T16:33:41.000Z | PHUSION_DEPLOYMENT.md | phusion/support_central | 618230e5caa478c71c45f8894d89086c32ae3668 | [
"MIT"
] | 10 | 2015-10-30T09:19:16.000Z | 2018-05-12T10:11:34.000Z | PHUSION_DEPLOYMENT.md | phusion/support_central | 618230e5caa478c71c45f8894d89086c32ae3668 | [
"MIT"
] | 3 | 2018-05-09T14:26:05.000Z | 2021-09-19T16:33:45.000Z | # Deploying to production (for Phusion employees)
_This guide is for Phusion employees. If you are not a Phusion employee, please read the [general deployment guide.](GENERAL_DEPLOYMENT.md)_
You can deploy Support Central as follows:
1. Commit and push all your changes.
2. Run: `bundle exec cap phusion deploy`.
| 35.333333 | 140 | 0.77673 | eng_Latn | 0.993818 |
9ad77f6a04088eba840c228e19c4583d5fabb4fb | 2,657 | md | Markdown | wdk-ddi-src/content/iddcx/nc-iddcx-pfn_iddcxswapchaingetphysicallycontiguousaddress.md | henke37/windows-driver-docs-ddi | 787885908a0474b7e2c3d2f8a47355dee62c7aec | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-08-16T13:05:36.000Z | 2021-08-16T13:05:36.000Z | wdk-ddi-src/content/iddcx/nc-iddcx-pfn_iddcxswapchaingetphysicallycontiguousaddress.md | henke37/windows-driver-docs-ddi | 787885908a0474b7e2c3d2f8a47355dee62c7aec | [
"CC-BY-4.0",
"MIT"
] | null | null | null | wdk-ddi-src/content/iddcx/nc-iddcx-pfn_iddcxswapchaingetphysicallycontiguousaddress.md | henke37/windows-driver-docs-ddi | 787885908a0474b7e2c3d2f8a47355dee62c7aec | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
UID: NC:iddcx.PFN_IDDCXSWAPCHAINGETPHYSICALLYCONTIGUOUSADDRESS
title: PFN_IDDCXSWAPCHAINGETPHYSICALLYCONTIGUOUSADDRESS
ms.date: 10/20/2020
tech.root: display
ms.topic: language-reference
targetos: Windows
description: PFN_IDDCXSWAPCHAINGETPHYSICALLYCONTIGUOUSADDRESS is a pointer to an OS callback function through which to get the physical contiguous address of a swapchain.
req.assembly:
req.construct-type: function
req.ddi-compliance:
req.dll:
req.header: iddcx.h
req.idl:
req.include-header:
req.irql:
req.kmdf-ver:
req.lib:
req.max-support:
req.namespace:
req.redist:
req.target-min-winverclnt: Windows 10, version 21H1
req.target-min-winversvr:
req.target-type:
req.type-library:
req.umdf-ver:
req.unicode-ansi:
topic_type:
- apiref
api_type:
- LibDef
api_location:
- iddcx.h
api_name:
- PFN_IDDCXSWAPCHAINGETPHYSICALLYCONTIGUOUSADDRESS
f1_keywords:
- PFN_IDDCXSWAPCHAINGETPHYSICALLYCONTIGUOUSADDRESS
- iddcx/PFN_IDDCXSWAPCHAINGETPHYSICALLYCONTIGUOUSADDRESS
dev_langs:
- c++
---
## -description
> [!NOTE]
> Some information on this page relates to a pre-released product which may be substantially modified before it is commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
**PFN_IDDCXSWAPCHAINGETPHYSICALLYCONTIGUOUSADDRESS** is a pointer to an OS callback function through which to retrieve the physical address of the specified swapchain's currently acquired surface.
## -parameters
### -param DriverGlobals
[in] Pointer to an [**IDD_DRIVER_GLOBALS**](/windows-hardware/drivers/ddi/iddcx/ns-iddcx-idd_driver_globals) structure containing system-defined per-driver data.
### -param SwapChainObject
[in] The [IDDCX_SWAPCHAIN](/windows-hardware/drivers/display/iddcx-objects) object passed to the [**EVT_IDD_CX_MONITOR_ASSIGN_SWAPCHAIN**](nc-iddcx-evt_idd_cx_monitor_assign_swapchain.md) call.
### -param pSurfaceAddresss
[out] Output arguments. On success, **pSurfaceAddress** is filled with the physical address of the surface.
## -returns
If the routine succeeds it return S_OK. If the surface was not allocated in physically contiguous memory this routine will return E_NOINTERFACE.
## -remarks
An indirect display driver (IDD) should not use this pointer to directly call the function that it points to. IDDs should instead call [**IddCxSwapChainGetPhysicallyContiguousAddress**](nf-iddcx-iddcxswapchaingetphysicallycontiguousaddress.md).
## -see-also
[**IddCxSwapChainGetPhysicallyContiguousAddress**](nf-iddcx-iddcxswapchaingetphysicallycontiguousaddress.md)
| 35.426667 | 245 | 0.785096 | eng_Latn | 0.827502 |
9ad823b510ee6e7abc3ed639c3975fc74645f17b | 5,454 | md | Markdown | k8s/helm-chart/redis-commander/README.md | themizzi/redis-commander | b6a12056fd2e86ab4f3f59615dc3daea51691408 | [
"MIT"
] | null | null | null | k8s/helm-chart/redis-commander/README.md | themizzi/redis-commander | b6a12056fd2e86ab4f3f59615dc3daea51691408 | [
"MIT"
] | 49 | 2019-01-14T17:01:35.000Z | 2022-03-10T16:27:15.000Z | k8s/helm-chart/redis-commander/README.md | themizzi/redis-commander | b6a12056fd2e86ab4f3f59615dc3daea51691408 | [
"MIT"
] | 1 | 2022-02-28T21:45:27.000Z | 2022-02-28T21:45:27.000Z | # redis-commander
A Helm chart for redis-commander
  
**Install**
Install using this repo after local git checkout itself with setting redis server host value
to `redis`
```sh
cd <git-repo>
helm -n myspace install redis-web-ui ./k8s/helm-chart/redis-commander --set redis.host=redis
```
## Values
| Key | Type | Default | Description |
|-----|------|---------|-------------|
| affinity | object | `{}` | |
| autoscaling | object | `{"enabled":false,"maxReplicas":1,"minReplicas":1,"targetCPUUtilizationPercentage":80}` | Autoscaling configuration for k8s deployment |
| env | list | `[]` | Extra env vars for the main container redis-commander in array structure ([{name: ... , value: ...}, {name: ... , value: ...}]). |
| fullnameOverride | string | `""` | |
| httpAuth.password | string | `""` | Specify http basic password for the web ui |
| httpAuth.username | string | `""` | Specify http basic username and password to protect access to redis commander web ui |
| image.apparmorProfile | string | `"runtime/default"` | Enable AppArmor per default when available on k8s host, change to "unconfined" to disable -- either AppArmor or SecComp may be enabled by the container runtime |
| image.pullPolicy | string | `"Always"` | Deployment pull policy, either "Always" or "IfNotPresent" |
| image.repository | string | `"rediscommander/redis-commander"` | Docker image for deployment |
| image.seccompProfile | string | `"runtime/default"` | Enable SecComp profile when used by cluster, change to "unconfined" to disable -- either AppArmor or SecComp may be enabled by the container runtime |
| image.tag | string | `""` | Overrides the image tag whose default is the chart appVersion. |
| imagePullSecrets | list | `[]` | Optional image pull secrets for private docker registries |
| ingress.annotations | object | `{}` | Add additional annotations for the ingess spec Example: 'kubernetes.io/ingress.class: nginx' or 'kubernetes.io/tls-acme: "true"' |
| ingress.enabled | bool | `false` | Enable Ingress for the service |
| ingress.hosts[0] | object | `{"host":"chart-example.local","paths":[]}` | Host name to use for the ingress definition |
| ingress.hosts[0].paths | list | `[]` | Optional list of paths within the given host for path-based routing |
| ingress.tls | list | `[]` | |
| nameOverride | string | `""` | |
| nodeSelector | object | `{}` | |
| podAnnotations | object | `{}` | |
| podSecurityContext | object | `{}` | |
| redis.host | string | `"redis-master"` | Specifies a single Redis host |
| redis.hosts | string | `""` | Alternative: Specifies multiple redis endpoints <label:host:port>,... instead of one in "redis.host" Example: "local:localhost:6379,myredis:10.10.20.30" |
| redis.password | string | `""` | Specifies redis password |
| replicaCount | int | `1` | |
| resources | object | `{}` | We usually recommend not to specify default resources and to leave this as a conscious choice for the user. This also increases chances charts run on environments with little resources, such as Minikube. If you do want to specify resources, uncomment the following lines, adjust them as necessary, and remove the curly braces after 'resources:'. |
| securityContext | object | `{"allowPrivilegeEscalation":false,"capabilities":{"drop":["ALL"]},"readOnlyRootFilesystem":false,"runAsNonRoot":true}` | Configuration of the linux security context for the docker image. This restricts the rights of the running docker image as far as possible. "readOnlyRootFilesystem" must be set to false to auto-generate a config file with multiple redis hosts or sentinel hosts |
| service.port | int | `80` | External port where service is available |
| service.type | string | `"ClusterIP"` | Type of k8s service to export |
| serviceAccount.annotations | object | `{}` | Annotations to add to the service account |
| serviceAccount.create | bool | `false` | Specifies whether a service account should be created When no service account is created the account credentials of the default account are also not automatically mounted into the pod (automountServiceAccountToken: false), tokens only mounted when service account is used but Redis-Commander itself does not use the k8s api server token |
| serviceAccount.name | string | `""` | The name of the service account to use. If not set and create is true, a name is generated using the fullname template |
| tolerations | list | `[]` | |
**Example**
Another alternative is the usage of the helm repo hosted at the github pages site.
```sh
# add repo
helm repo add redis-commander https://joeferner.github.io/redis-commander/
# custom values
cat > myvalues.yaml <<EOF
redis.host: redis-master
# env:
# - name: FOLDING_CHAR
# value: "/"
ingress:
enabled: true
annotations:
kubernetes.io/ingress.class: nginx
hosts:
- host: redis-ui.example.com
paths: ["/"]
EOF
# install helm chart with the custom values
helm install \
redis-web-ui \
redis-commander/redis-commander \
-f myvalues.yaml
```
----------------------------------------------
Autogenerated from chart metadata using [helm-docs v1.5.0](https://github.com/norwoodj/helm-docs/releases/v1.5.0)
| 62.689655 | 413 | 0.712321 | eng_Latn | 0.935053 |
9ad8c1a0ac55273f2acbec9b295bbd3d1bfc58ae | 1,497 | md | Markdown | 03-IBM_Storage_System/05-XIV_Storage/01-XIV-日志查看及收集.md | bond-huang/ebook | aa9c5ed6d2cb7b5398a27720fbc8fe59fd59641e | [
"Apache-2.0"
] | 1 | 2021-03-14T13:24:29.000Z | 2021-03-14T13:24:29.000Z | 03-IBM_Storage_System/05-XIV_Storage/01-XIV-日志查看及收集.md | bond-huang/ebook | aa9c5ed6d2cb7b5398a27720fbc8fe59fd59641e | [
"Apache-2.0"
] | null | null | null | 03-IBM_Storage_System/05-XIV_Storage/01-XIV-日志查看及收集.md | bond-huang/ebook | aa9c5ed6d2cb7b5398a27720fbc8fe59fd59641e | [
"Apache-2.0"
] | 1 | 2022-02-24T10:02:08.000Z | 2022-02-24T10:02:08.000Z | # XIV-日志查看及收集
XIV System Data类似于DS8000的PEpackage，在XIV里面称作XRAY。
## XIV GUI日志查看
通过XIV GUI查看很方便，在左侧“系统”菜单中可以查看：
- 所有系统警报
- 所有系统事件
在左侧“监视”菜单中可以查看：
- 系统：菜单点击后可以看到整个AIV存储3D视图，鼠标指向某个设备（例如硬盘）就会显示对应的信息，包括状态和事件
- 统计信息：菜单可以看到系统性能概况
- 警报：系统警报信息
- 事件：系统事件
- Qos性能类：性能限制组信息
## 数据收集
XIV System Data类似于DS8000的PEpackage，在XIV里面称作XRAY。
### 老版本收集XRAY
  老版本GUI中没有收集XRAY的选项，需要通过终端（需安装XCLI，在IBM fix central中有下载）连上存储通过运行收集日志的程序进行收集。收集步骤如下：
- 将laptop网口IP获取设置成DHCP模式
- 将laptop链接到Patch panel上module 5 的laptop port
- 会自动获取一个14.10.202.xx的地址，如果没用，手动设置laptop地址
- 检查是否能ping通地址14.10.202.250，不可以继续检查网络
- 在laptop上的命令行执行收集程序，运行命令：`xary collect 14.10.202.250`
- 收集完成后会自动Offload到laptop上运行xray_collect.exe的目录下
注意：
- 如果XIV的微码是10.1或以上，使用xray_collect_v2.0.1.exe文件
- 如果低于此版本，使用xray_collect.exe文件
- 两个文件在对于的微码的包里面，微码下载也是在IBM fix central
### XIV GUI收集XRAY
  从XIV GUI2.4.1版本开始，XIV支持用GUI的方式收集XRAY。XIV的GUI在IBM fix central中有下载，里面包含XCLI，下载安装完成后发现还有演示模式，这是个很不错的功能，可以在模拟环境下对XIV进行一些操作，方便学习及测试操作。收集步骤如下：
- 启动XIV GUI程序，然后登录，用户：technician，密码：teChn1cian
- 选中需要收集XRAY的XIV系统
- 在菜单栏选中并点击“Help”
- 下拉菜单中选中并点击“Support Logs...”
- 弹出对话框“Get Support Logs”，点击“Collect”
- 收集完成后，对话框中“System Log File Name”里面会列出当前系统里面的日志信息
- 选择刚才时间点收集的日志，点击“Browse”选择存放位置
- 最后点击“Get”即完成收集
在一些新的GUI版本中，收集选项有所改变，但是大致上差不多：
- 登录到AIV GUI 选中对应XIV系统后
- 在菜单栏选中并点击“工具（t）”
- 在展开菜单中选择“收集支持日志”点击后弹出对话框“收集并发送支持日志”
- 点击“启动”开始收集XARY
### XIV GUI收集容量报告
步骤如下：
- 登录到AIV GUI 选中对应XIV系统后
- 在菜单栏选中并点击“工具（t）”
- 在展开菜单中选择“生成容量报告”点击
- 点击“启动”开始收集
## TA tool使用
IBM XIV存储工程师使用，不作详述。
| 26.263158 | 150 | 0.798263 | yue_Hant | 0.893259 |
9ad9051e4b25617d34e09f390e5c439ee581576f | 69,662 | md | Markdown | _posts/2021-03-31-time_series_3rd.md | qhdwktm363554/qhdwktm363554.github.io | 4cd9f250441094f3ad27f861fc0a53398241dbe6 | [
"MIT"
] | null | null | null | _posts/2021-03-31-time_series_3rd.md | qhdwktm363554/qhdwktm363554.github.io | 4cd9f250441094f3ad27f861fc0a53398241dbe6 | [
"MIT"
] | null | null | null | _posts/2021-03-31-time_series_3rd.md | qhdwktm363554/qhdwktm363554.github.io | 4cd9f250441094f3ad27f861fc0a53398241dbe6 | [
"MIT"
] | null | null | null | # Tensorflow Deveoper Certification
## Time Series_Exercise_3_Mean Absolute Error
** tensorflow version: 2.0.0-alpha0 **
synthetic data set use and write the code to pick the learning rate
Train on it to get an MAE of < 3
```python
import tensorflow as tf
import numpy as np
import matplotlib.pyplot as plt
```
```python
def plot_series(time, series, format = '-', start = 0, end = None):
plt.plot(time[start:end], series[start:end], format)
plt.xlabel('Time')
plt.ylabel('Value')
plt.grid(False)
def trend(time, slope = 0):
return slope * time
def seasonal_pattern(season_time):
return np.where(season_time < 0.1,
np.cos(season_time *6 * np.pi),
2 / np.exp(9*season_time))
def seasonality(time, period, amplitude = 1, phase = 0):
season_time = ((time + phase) % period) / period
return amplitude * seasonal_pattern(season_time)
def noise(time, noise_level = 1, seed = None):
rnd = np.random.RandomState(seed)
return rnd.randn(len(time)) * noise_level
time = np.arange(10*365 +1, dtype = 'float32')
baseline = 10
series = trend(time, 0.1)
baseline = 10
amplitude = 40
slope = 0.005
noise_level = 3
series = baseline + trend(time, slope) + seasonality(time, period = 365, amplitude = amplitude)
series += noise(time, noise_level, seed=51)
split_time = 3000
time_train = time[:split_time]
x_train = series[:split_time]
time_valid = time[split_time:]
x_valid = series[split_time:]
window_size = 20
batch_size = 32
shuffle_buffer_size = 1000
plot_series(time, series)
```
#### data pipeline 구축한다.
tf.data.Dataset이라는 Dataset class를 사용한다.
window size = 5는 5일치 data를 train으로 사용한다.
```python
def windowed_dataset(series, window_size, batch_size, shuffle_buffer):
dataset = tf.data.Dataset.from_tensor_slices(series)
dataset = dataset.window(window_size + 1, shift = 1, drop_remainder = True)
# 결과를 flat하게 준다. 예를 들어 2차원을 1차원으로 준다.
dataset = dataset.flat_map(lambda window: window.batch(window_size + 1))
dataset = dataset.shuffle(shuffle_buffer).map(lambda window: (window[:-1], window[-1]))
# prefetch는 미리 data를 fetch하는 개수 ==> 학습 속도를 개선시키는 효과가 있다.
dataset = dataset.batch(batch_size).prefetch(1)
return dataset
```
the data from earlier in the window can have a greater impact on the overall projection than in the case of RNNs.
```python
tf.keras.backend.clear_session() # this clears any internal variables
tf.random.set_seed(51)
np.random.seed(51)
tf.keras.backend.clear_session()
dataset = windowed_dataset(x_train, window_size, batch_size, shuffle_buffer_size)
model = tf.keras.models.Sequential([
tf.keras.layers.Lambda(lambda x: tf.expand_dims(x, axis =-1), input_shape = [None]),
tf.keras.layers.Bidirectional(tf.keras.layers.LSTM(32, return_sequences = True)),
tf.keras.layers.Bidirectional(tf.keras.layers.LSTM(32)),
tf.keras.layers.Dense(1),
tf.keras.layers.Lambda(lambda x: x * 10.0)
])
# based on the epoch number, lr changes
lr_schedule =tf.keras.callbacks.LearningRateScheduler(lambda epoch: 1e-8 * 10 **(epoch/20))
optimizer = tf.keras.optimizers.SGD(lr=1e-8, momentum = 0.9)
model.compile(loss = tf.keras.losses.Huber(), optimizer = optimizer, metrics = ['mae'])
history = model.fit(dataset, epochs = 100, callbacks = [lr_schedule])
```
Epoch 1/100
94/94 [==============================] - 7s 76ms/step - loss: 20.5121 - mae: 20.8828
Epoch 2/100
94/94 [==============================] - 2s 26ms/step - loss: 20.4822 - mae: 20.8543: 1s - loss
Epoch 3/100
94/94 [==============================] - 2s 26ms/step - loss: 20.4497 - mae: 20.8218
Epoch 4/100
94/94 [==============================] - 3s 29ms/step - loss: 20.4130 - mae: 20.7851
Epoch 5/100
94/94 [==============================] - 2s 25ms/step - loss: 20.3714 - mae: 20.7436
Epoch 6/100
94/94 [==============================] - 2s 26ms/step - loss: 20.3242 - mae: 20.6964
Epoch 7/100
94/94 [==============================] - 2s 26ms/step - loss: 20.2706 - mae: 20.6429
Epoch 8/100
94/94 [==============================] - 3s 28ms/step - loss: 20.2098 - mae: 20.5822
Epoch 9/100
94/94 [==============================] - 3s 30ms/step - loss: 20.1414 - mae: 20.5139
Epoch 10/100
94/94 [==============================] - 3s 30ms/step - loss: 20.0659 - mae: 20.4384
Epoch 11/100
94/94 [==============================] - 3s 33ms/step - loss: 19.9858 - mae: 20.3584
Epoch 12/100
94/94 [==============================] - 3s 28ms/step - loss: 19.9050 - mae: 20.2777
Epoch 13/100
94/94 [==============================] - 3s 30ms/step - loss: 19.8240 - mae: 20.1967
Epoch 14/100
94/94 [==============================] - 3s 27ms/step - loss: 19.7381 - mae: 20.1109
Epoch 15/100
94/94 [==============================] - 3s 28ms/step - loss: 19.6434 - mae: 20.0163
Epoch 16/100
94/94 [==============================] - 3s 31ms/step - loss: 19.5379 - mae: 19.9108: 0s - loss: 18.0386
Epoch 17/100
94/94 [==============================] - 4s 42ms/step - loss: 19.4203 - mae: 19.7932
Epoch 18/100
94/94 [==============================] - 3s 37ms/step - loss: 19.2888 - mae: 19.6618
Epoch 19/100
94/94 [==============================] - 3s 35ms/step - loss: 19.1418 - mae: 19.5149
Epoch 20/100
94/94 [==============================] - 3s 36ms/step - loss: 18.9772 - mae: 19.3503
Epoch 21/100
94/94 [==============================] - 3s 34ms/step - loss: 18.7926 - mae: 19.1657
Epoch 22/100
94/94 [==============================] - 3s 36ms/step - loss: 18.5854 - mae: 18.9584
Epoch 23/100
94/94 [==============================] - 3s 35ms/step - loss: 18.3523 - mae: 18.7251: 1s - los
Epoch 24/100
94/94 [==============================] - 3s 36ms/step - loss: 18.0897 - mae: 18.4624
Epoch 25/100
94/94 [==============================] - 3s 34ms/step - loss: 17.7933 - mae: 18.1659
Epoch 26/100
94/94 [==============================] - 3s 35ms/step - loss: 17.4589 - mae: 17.8317
Epoch 27/100
94/94 [==============================] - 4s 39ms/step - loss: 17.0827 - mae: 17.4559: 2s -
Epoch 28/100
94/94 [==============================] - 3s 33ms/step - loss: 16.6627 - mae: 17.0362: 1s - loss: 14.
Epoch 29/100
94/94 [==============================] - 3s 33ms/step - loss: 16.1987 - mae: 16.5722
Epoch 30/100
94/94 [==============================] - 3s 33ms/step - loss: 15.6909 - mae: 16.0642
Epoch 31/100
94/94 [==============================] - 3s 34ms/step - loss: 15.1390 - mae: 15.5119
Epoch 32/100
94/94 [==============================] - 3s 35ms/step - loss: 14.5423 - mae: 14.9154
Epoch 33/100
94/94 [==============================] - 3s 36ms/step - loss: 13.9008 - mae: 14.2738: 0s - loss: 13.1468 - m
Epoch 34/100
94/94 [==============================] - 3s 35ms/step - loss: 13.2187 - mae: 13.5903
Epoch 35/100
94/94 [==============================] - 3s 36ms/step - loss: 12.5063 - mae: 12.8763
Epoch 36/100
94/94 [==============================] - 3s 35ms/step - loss: 11.7799 - mae: 12.1493
Epoch 37/100
94/94 [==============================] - 3s 35ms/step - loss: 11.0548 - mae: 11.4261
Epoch 38/100
94/94 [==============================] - 4s 38ms/step - loss: 10.3480 - mae: 10.7180
Epoch 39/100
94/94 [==============================] - 3s 37ms/step - loss: 9.6888 - mae: 10.0574
Epoch 40/100
94/94 [==============================] - 3s 35ms/step - loss: 9.1046 - mae: 9.4763: 0s - loss: 8.8336 - mae:
Epoch 41/100
94/94 [==============================] - 3s 35ms/step - loss: 8.6019 - mae: 8.9766
Epoch 42/100
94/94 [==============================] - 3s 35ms/step - loss: 8.1799 - mae: 8.5587
Epoch 43/100
94/94 [==============================] - 3s 33ms/step - loss: 7.8391 - mae: 8.2200
Epoch 44/100
94/94 [==============================] - 3s 34ms/step - loss: 7.5752 - mae: 7.9594
Epoch 45/100
94/94 [==============================] - 4s 40ms/step - loss: 7.3736 - mae: 7.7614
Epoch 46/100
94/94 [==============================] - 4s 38ms/step - loss: 7.2159 - mae: 7.6073
Epoch 47/100
94/94 [==============================] - 4s 41ms/step - loss: 7.0868 - mae: 7.4794
Epoch 48/100
94/94 [==============================] - 3s 37ms/step - loss: 6.9748 - mae: 7.3678
Epoch 49/100
94/94 [==============================] - 3s 36ms/step - loss: 6.8686 - mae: 7.2622
Epoch 50/100
94/94 [==============================] - 3s 35ms/step - loss: 6.7591 - mae: 7.1534
Epoch 51/100
94/94 [==============================] - 3s 36ms/step - loss: 6.6365 - mae: 7.0309
Epoch 52/100
94/94 [==============================] - 4s 37ms/step - loss: 6.4336 - mae: 6.8258
Epoch 53/100
94/94 [==============================] - 3s 37ms/step - loss: 5.9699 - mae: 6.3533
Epoch 54/100
94/94 [==============================] - 3s 37ms/step - loss: 5.7730 - mae: 6.1570
Epoch 55/100
94/94 [==============================] - 4s 45ms/step - loss: 5.5697 - mae: 5.9520
Epoch 56/100
94/94 [==============================] - 3s 34ms/step - loss: 5.3743 - mae: 5.7533
Epoch 57/100
94/94 [==============================] - 3s 36ms/step - loss: 5.2037 - mae: 5.5832
Epoch 58/100
94/94 [==============================] - 3s 35ms/step - loss: 5.0553 - mae: 5.4325
Epoch 59/100
94/94 [==============================] - 3s 36ms/step - loss: 4.9181 - mae: 5.2958
Epoch 60/100
94/94 [==============================] - 3s 34ms/step - loss: 4.8254 - mae: 5.2030
Epoch 61/100
94/94 [==============================] - 3s 34ms/step - loss: 4.7633 - mae: 5.1414
Epoch 62/100
94/94 [==============================] - 3s 33ms/step - loss: 4.7403 - mae: 5.1174
Epoch 63/100
94/94 [==============================] - 3s 37ms/step - loss: 4.6225 - mae: 5.0035
Epoch 64/100
94/94 [==============================] - 3s 34ms/step - loss: 4.5346 - mae: 4.9191
Epoch 65/100
94/94 [==============================] - 3s 34ms/step - loss: 4.5217 - mae: 4.9148
Epoch 66/100
94/94 [==============================] - 3s 34ms/step - loss: 4.4580 - mae: 4.8540
Epoch 67/100
94/94 [==============================] - 3s 36ms/step - loss: 4.3487 - mae: 4.7386: 0s - loss: 4.2447 - ma
Epoch 68/100
94/94 [==============================] - 4s 38ms/step - loss: 4.2742 - mae: 4.6633
Epoch 69/100
94/94 [==============================] - 3s 34ms/step - loss: 4.1996 - mae: 4.5918
Epoch 70/100
94/94 [==============================] - 3s 35ms/step - loss: 4.1285 - mae: 4.5233
Epoch 71/100
94/94 [==============================] - 3s 34ms/step - loss: 4.0718 - mae: 4.4664: 1s - loss: 3.9328 - mae: - ETA: 0s - loss: 3.9904 -
Epoch 72/100
94/94 [==============================] - 3s 35ms/step - loss: 3.9948 - mae: 4.3899: 0s - loss: 3.9110 - mae:
Epoch 73/100
94/94 [==============================] - 3s 34ms/step - loss: 3.9212 - mae: 4.3143
Epoch 74/100
94/94 [==============================] - 3s 35ms/step - loss: 3.8412 - mae: 4.2338
Epoch 75/100
94/94 [==============================] - 4s 40ms/step - loss: 3.7183 - mae: 4.1160
Epoch 76/100
94/94 [==============================] - 3s 34ms/step - loss: 3.6124 - mae: 4.0152
Epoch 77/100
94/94 [==============================] - 3s 34ms/step - loss: 3.4729 - mae: 3.8833
Epoch 78/100
94/94 [==============================] - 3s 33ms/step - loss: 3.3898 - mae: 3.8017
Epoch 79/100
94/94 [==============================] - 3s 35ms/step - loss: 3.2607 - mae: 3.6675
Epoch 80/100
94/94 [==============================] - 3s 35ms/step - loss: 3.1747 - mae: 3.5816
Epoch 81/100
94/94 [==============================] - 3s 35ms/step - loss: 3.1387 - mae: 3.5435
Epoch 82/100
94/94 [==============================] - 4s 38ms/step - loss: 3.0668 - mae: 3.4718
Epoch 83/100
94/94 [==============================] - 3s 36ms/step - loss: 3.0631 - mae: 3.4674
Epoch 84/100
94/94 [==============================] - 3s 35ms/step - loss: 2.9895 - mae: 3.3919
Epoch 85/100
94/94 [==============================] - 3s 33ms/step - loss: 3.0249 - mae: 3.4270
Epoch 86/100
94/94 [==============================] - ETA: 0s - loss: 2.9512 - mae: 3.4127- ETA: 1s - lo - ETA: 0s - loss: 2.9580 - mae: 3.4 - 3s 32ms/step - loss: 3.0118 - mae: 3.4120
Epoch 87/100
94/94 [==============================] - 3s 32ms/step - loss: 2.9802 - mae: 3.3834
Epoch 88/100
94/94 [==============================] - 3s 32ms/step - loss: 2.9982 - mae: 3.3996
Epoch 89/100
94/94 [==============================] - 3s 34ms/step - loss: 3.0188 - mae: 3.4192
Epoch 90/100
94/94 [==============================] - 3s 31ms/step - loss: 2.9989 - mae: 3.3999
Epoch 91/100
94/94 [==============================] - 3s 31ms/step - loss: 2.9755 - mae: 3.3754
Epoch 92/100
94/94 [==============================] - 3s 34ms/step - loss: 2.9597 - mae: 3.3575
Epoch 93/100
94/94 [==============================] - 4s 45ms/step - loss: 2.9285 - mae: 3.3312
Epoch 94/100
94/94 [==============================] - 3s 36ms/step - loss: 2.9965 - mae: 3.3974
Epoch 95/100
94/94 [==============================] - 3s 35ms/step - loss: 3.0097 - mae: 3.4144
Epoch 96/100
94/94 [==============================] - 3s 35ms/step - loss: 2.8086 - mae: 3.2096
Epoch 97/100
94/94 [==============================] - 3s 34ms/step - loss: 2.8579 - mae: 3.2619
Epoch 98/100
94/94 [==============================] - 4s 47ms/step - loss: 2.9719 - mae: 3.3744
Epoch 99/100
94/94 [==============================] - 3s 37ms/step - loss: 2.8707 - mae: 3.2755
Epoch 100/100
94/94 [==============================] - 3s 34ms/step - loss: 2.9779 - mae: 3.3866
```python
plt.semilogx(history.history['lr'], history.history['loss'])
plt.axis([1e-8, 1e-4, 0, 30])
plt.grid(b = True, which = 'both', axis = 'both')
```
```python
tf.keras.backend.clear_session()
tf.random.set_seed(51)
np.random.seed(51)
tf.keras.backend.clear_session()
dataset = windowed_dataset(x_train, window_size, batch_size, shuffle_buffer_size)
model = tf.keras.models.Sequential([
tf.keras.layers.Lambda(lambda x: tf.expand_dims(x, axis=-1),
input_shape = [None]),
tf.keras.layers.Bidirectional(tf.keras.layers.LSTM(32, return_sequences = True)),
tf.keras.layers.Bidirectional(tf.keras.layers.LSTM(32)),
tf.keras.layers.Dense(1),
tf.keras.layers.Lambda(lambda x: x * 100.0)
])
model.compile(loss = 'mse', optimizer = tf.keras.optimizers.SGD(lr=1e-5, momentum = 0.9), metrics = ['mae'])
history = model.fit(dataset, epochs = 500, verbose = 1)
```
Epoch 1/500
94/94 [==============================] - 8s 83ms/step - loss: 317.3266 - mae: 10.6099
Epoch 2/500
94/94 [==============================] - 3s 30ms/step - loss: 43.9131 - mae: 4.3734
Epoch 3/500
94/94 [==============================] - 4s 39ms/step - loss: 38.1663 - mae: 4.0789
Epoch 4/500
94/94 [==============================] - 3s 27ms/step - loss: 35.4674 - mae: 3.9329
Epoch 5/500
94/94 [==============================] - 2s 25ms/step - loss: 34.3146 - mae: 3.8666
Epoch 6/500
94/94 [==============================] - 2s 25ms/step - loss: 35.0763 - mae: 3.9453
Epoch 7/500
94/94 [==============================] - 2s 25ms/step - loss: 32.9887 - mae: 3.7930
Epoch 8/500
94/94 [==============================] - 2s 25ms/step - loss: 33.0334 - mae: 3.8177
Epoch 9/500
94/94 [==============================] - 2s 25ms/step - loss: 31.9545 - mae: 3.7345
Epoch 10/500
94/94 [==============================] - 2s 24ms/step - loss: 31.5508 - mae: 3.7091
Epoch 11/500
94/94 [==============================] - 2s 25ms/step - loss: 31.1413 - mae: 3.6787
Epoch 12/500
94/94 [==============================] - 2s 25ms/step - loss: 30.8509 - mae: 3.6543
Epoch 13/500
94/94 [==============================] - 2s 25ms/step - loss: 30.6272 - mae: 3.6355
Epoch 14/500
94/94 [==============================] - 2s 25ms/step - loss: 30.3973 - mae: 3.6174
Epoch 15/500
94/94 [==============================] - 2s 26ms/step - loss: 30.1500 - mae: 3.6011
Epoch 16/500
94/94 [==============================] - 2s 25ms/step - loss: 29.9113 - mae: 3.5892
Epoch 17/500
94/94 [==============================] - 2s 25ms/step - loss: 29.7562 - mae: 3.5830
Epoch 18/500
94/94 [==============================] - 2s 25ms/step - loss: 29.6475 - mae: 3.5781
Epoch 19/500
94/94 [==============================] - 2s 25ms/step - loss: 29.5469 - mae: 3.5734
Epoch 20/500
94/94 [==============================] - 2s 25ms/step - loss: 29.4719 - mae: 3.5719
Epoch 21/500
94/94 [==============================] - 2s 25ms/step - loss: 29.4321 - mae: 3.5725
Epoch 22/500
94/94 [==============================] - 2s 25ms/step - loss: 29.4229 - mae: 3.5742
Epoch 23/500
94/94 [==============================] - 2s 25ms/step - loss: 29.4267 - mae: 3.5779
Epoch 24/500
94/94 [==============================] - 2s 25ms/step - loss: 29.4382 - mae: 3.5822
Epoch 25/500
94/94 [==============================] - 2s 25ms/step - loss: 29.5223 - mae: 3.5912
Epoch 26/500
94/94 [==============================] - 2s 25ms/step - loss: 29.6347 - mae: 3.6010 0s - loss: 26.8979 -
Epoch 27/500
94/94 [==============================] - 2s 26ms/step - loss: 29.6155 - mae: 3.5992
Epoch 28/500
94/94 [==============================] - 3s 27ms/step - loss: 29.5391 - mae: 3.5931
Epoch 29/500
94/94 [==============================] - 2s 25ms/step - loss: 29.4527 - mae: 3.5858
Epoch 30/500
94/94 [==============================] - 2s 26ms/step - loss: 29.3841 - mae: 3.5799
Epoch 31/500
94/94 [==============================] - 2s 25ms/step - loss: 29.4006 - mae: 3.5841
Epoch 32/500
94/94 [==============================] - 2s 26ms/step - loss: 29.2876 - mae: 3.5746
Epoch 33/500
94/94 [==============================] - 2s 25ms/step - loss: 29.3532 - mae: 3.5877
Epoch 34/500
94/94 [==============================] - 2s 26ms/step - loss: 29.1492 - mae: 3.5642
Epoch 35/500
94/94 [==============================] - 2s 25ms/step - loss: 29.2015 - mae: 3.5674
Epoch 36/500
94/94 [==============================] - 2s 26ms/step - loss: 29.1970 - mae: 3.5718
Epoch 37/500
94/94 [==============================] - 2s 26ms/step - loss: 29.0993 - mae: 3.5567
Epoch 38/500
94/94 [==============================] - 2s 26ms/step - loss: 28.9917 - mae: 3.5437
Epoch 39/500
94/94 [==============================] - 2s 26ms/step - loss: 28.8653 - mae: 3.5254
Epoch 40/500
94/94 [==============================] - 2s 26ms/step - loss: 28.7841 - mae: 3.5152
Epoch 41/500
94/94 [==============================] - 2s 25ms/step - loss: 28.6569 - mae: 3.5005
Epoch 42/500
94/94 [==============================] - 2s 26ms/step - loss: 28.5466 - mae: 3.4886
Epoch 43/500
94/94 [==============================] - 2s 26ms/step - loss: 28.4455 - mae: 3.4774
Epoch 44/500
94/94 [==============================] - 2s 26ms/step - loss: 28.3408 - mae: 3.4665
Epoch 45/500
94/94 [==============================] - 2s 26ms/step - loss: 28.2470 - mae: 3.4572
Epoch 46/500
94/94 [==============================] - 2s 26ms/step - loss: 28.1524 - mae: 3.4479
Epoch 47/500
94/94 [==============================] - 2s 26ms/step - loss: 28.0586 - mae: 3.4390
Epoch 48/500
94/94 [==============================] - 4s 38ms/step - loss: 27.9657 - mae: 3.4302
Epoch 49/500
94/94 [==============================] - 5s 53ms/step - loss: 27.8739 - mae: 3.4218
Epoch 50/500
94/94 [==============================] - 5s 49ms/step - loss: 27.7837 - mae: 3.4138
Epoch 51/500
94/94 [==============================] - 5s 49ms/step - loss: 27.6952 - mae: 3.4059
Epoch 52/500
94/94 [==============================] - 4s 48ms/step - loss: 27.6085 - mae: 3.3983
Epoch 53/500
94/94 [==============================] - 4s 44ms/step - loss: 27.5238 - mae: 3.3909
Epoch 54/500
94/94 [==============================] - 4s 47ms/step - loss: 27.4412 - mae: 3.3837
Epoch 55/500
94/94 [==============================] - 4s 38ms/step - loss: 27.3606 - mae: 3.3768
Epoch 56/500
94/94 [==============================] - 3s 34ms/step - loss: 27.2821 - mae: 3.3701
Epoch 57/500
94/94 [==============================] - 4s 46ms/step - loss: 27.2058 - mae: 3.3636
Epoch 58/500
94/94 [==============================] - 4s 42ms/step - loss: 27.1316 - mae: 3.3573
Epoch 59/500
94/94 [==============================] - 4s 39ms/step - loss: 27.0594 - mae: 3.3511
Epoch 60/500
94/94 [==============================] - 3s 34ms/step - loss: 26.9893 - mae: 3.3452
Epoch 61/500
94/94 [==============================] - 4s 41ms/step - loss: 26.9211 - mae: 3.3395
Epoch 62/500
94/94 [==============================] - 4s 37ms/step - loss: 26.8547 - mae: 3.3340
Epoch 63/500
94/94 [==============================] - 3s 32ms/step - loss: 26.7901 - mae: 3.3287
Epoch 64/500
94/94 [==============================] - 3s 33ms/step - loss: 26.7272 - mae: 3.3236
Epoch 65/500
94/94 [==============================] - 3s 33ms/step - loss: 26.6660 - mae: 3.3188
Epoch 66/500
94/94 [==============================] - 3s 34ms/step - loss: 26.6064 - mae: 3.3141
Epoch 67/500
94/94 [==============================] - 3s 33ms/step - loss: 26.5483 - mae: 3.3097 0s -
Epoch 68/500
94/94 [==============================] - 3s 33ms/step - loss: 26.4919 - mae: 3.3055
Epoch 69/500
94/94 [==============================] - 3s 33ms/step - loss: 26.4371 - mae: 3.3015
Epoch 70/500
94/94 [==============================] - 3s 31ms/step - loss: 26.3842 - mae: 3.2977
Epoch 71/500
94/94 [==============================] - 3s 33ms/step - loss: 26.3334 - mae: 3.2942
Epoch 72/500
94/94 [==============================] - 3s 34ms/step - loss: 26.2852 - mae: 3.2908 0s - l
Epoch 73/500
94/94 [==============================] - 3s 33ms/step - loss: 26.2404 - mae: 3.2878
Epoch 74/500
94/94 [==============================] - 3s 32ms/step - loss: 26.1975 - mae: 3.2848
Epoch 75/500
94/94 [==============================] - 3s 32ms/step - loss: 26.1497 - mae: 3.2811
Epoch 76/500
94/94 [==============================] - 3s 33ms/step - loss: 26.1005 - mae: 3.2776
Epoch 77/500
94/94 [==============================] - 3s 35ms/step - loss: 26.0535 - mae: 3.2743
Epoch 78/500
94/94 [==============================] - 3s 32ms/step - loss: 26.0086 - mae: 3.2711
Epoch 79/500
94/94 [==============================] - 3s 36ms/step - loss: 25.9662 - mae: 3.2682
Epoch 80/500
94/94 [==============================] - 3s 32ms/step - loss: 25.9272 - mae: 3.2655
Epoch 81/500
94/94 [==============================] - 3s 35ms/step - loss: 25.8917 - mae: 3.2631
Epoch 82/500
94/94 [==============================] - 3s 32ms/step - loss: 25.8565 - mae: 3.2608
Epoch 83/500
94/94 [==============================] - 3s 32ms/step - loss: 25.8191 - mae: 3.2583
Epoch 84/500
94/94 [==============================] - 3s 34ms/step - loss: 25.7823 - mae: 3.2560
Epoch 85/500
94/94 [==============================] - 3s 31ms/step - loss: 25.7452 - mae: 3.2535
Epoch 86/500
94/94 [==============================] - 3s 29ms/step - loss: 25.7079 - mae: 3.2511
Epoch 87/500
94/94 [==============================] - 3s 29ms/step - loss: 25.6697 - mae: 3.2485
Epoch 88/500
94/94 [==============================] - 3s 31ms/step - loss: 25.6305 - mae: 3.2458
Epoch 89/500
94/94 [==============================] - 3s 30ms/step - loss: 25.5976 - mae: 3.2439
Epoch 90/500
94/94 [==============================] - 3s 31ms/step - loss: 25.6663 - mae: 3.2499
Epoch 91/500
94/94 [==============================] - 3s 30ms/step - loss: 25.4246 - mae: 3.2309
Epoch 92/500
94/94 [==============================] - 3s 31ms/step - loss: 25.5075 - mae: 3.2387
Epoch 93/500
94/94 [==============================] - 3s 32ms/step - loss: 25.5491 - mae: 3.2424
Epoch 94/500
94/94 [==============================] - 3s 31ms/step - loss: 25.2794 - mae: 3.2208
Epoch 95/500
94/94 [==============================] - 3s 30ms/step - loss: 25.3938 - mae: 3.2311
Epoch 96/500
94/94 [==============================] - 3s 29ms/step - loss: 25.4222 - mae: 3.2340 0s - loss: 22. - ETA: 0s - loss: 22.5221 - mae: 3.22
Epoch 97/500
94/94 [==============================] - 3s 32ms/step - loss: 25.1861 - mae: 3.2146
Epoch 98/500
94/94 [==============================] - 3s 30ms/step - loss: 25.2927 - mae: 3.2242
Epoch 99/500
94/94 [==============================] - 3s 31ms/step - loss: 25.3023 - mae: 3.2260
Epoch 100/500
94/94 [==============================] - 3s 30ms/step - loss: 25.1009 - mae: 3.2087
Epoch 101/500
94/94 [==============================] - 3s 29ms/step - loss: 25.2269 - mae: 3.2205
Epoch 102/500
94/94 [==============================] - 3s 30ms/step - loss: 25.1002 - mae: 3.2095
Epoch 103/500
94/94 [==============================] - 3s 31ms/step - loss: 25.2664 - mae: 3.2262
Epoch 104/500
94/94 [==============================] - 3s 31ms/step - loss: 24.9164 - mae: 3.1941
Epoch 105/500
94/94 [==============================] - 3s 29ms/step - loss: 25.1535 - mae: 3.2171
Epoch 106/500
94/94 [==============================] - 3s 29ms/step - loss: 24.9276 - mae: 3.1959
Epoch 107/500
94/94 [==============================] - 3s 29ms/step - loss: 25.0783 - mae: 3.2113
Epoch 108/500
94/94 [==============================] - 3s 30ms/step - loss: 24.9069 - mae: 3.1947
Epoch 109/500
94/94 [==============================] - 3s 30ms/step - loss: 25.0443 - mae: 3.2097
Epoch 110/500
94/94 [==============================] - 3s 36ms/step - loss: 24.8153 - mae: 3.1871
Epoch 111/500
94/94 [==============================] - 4s 43ms/step - loss: 24.9429 - mae: 3.1994
Epoch 112/500
94/94 [==============================] - 4s 39ms/step - loss: 24.9549 - mae: 3.2035
Epoch 113/500
94/94 [==============================] - 4s 44ms/step - loss: 24.7396 - mae: 3.1813
Epoch 114/500
94/94 [==============================] - 3s 31ms/step - loss: 24.8585 - mae: 3.1926
Epoch 115/500
94/94 [==============================] - 3s 32ms/step - loss: 24.8395 - mae: 3.1918 0s - loss: 21.4100
Epoch 116/500
94/94 [==============================] - 3s 34ms/step - loss: 24.8017 - mae: 3.1894 0s - loss:
Epoch 117/500
94/94 [==============================] - 3s 30ms/step - loss: 24.7371 - mae: 3.1828
Epoch 118/500
94/94 [==============================] - 3s 31ms/step - loss: 24.7568 - mae: 3.1854
Epoch 119/500
94/94 [==============================] - 3s 29ms/step - loss: 24.7166 - mae: 3.1819
Epoch 120/500
94/94 [==============================] - 3s 29ms/step - loss: 24.7006 - mae: 3.1807
Epoch 121/500
94/94 [==============================] - 3s 31ms/step - loss: 24.6800 - mae: 3.1791
Epoch 122/500
94/94 [==============================] - 3s 29ms/step - loss: 24.6611 - mae: 3.1776
Epoch 123/500
94/94 [==============================] - 3s 30ms/step - loss: 24.6421 - mae: 3.1760
Epoch 124/500
94/94 [==============================] - 3s 29ms/step - loss: 24.6230 - mae: 3.1745
Epoch 125/500
94/94 [==============================] - 3s 29ms/step - loss: 24.6038 - mae: 3.1730
Epoch 126/500
94/94 [==============================] - 3s 29ms/step - loss: 24.5844 - mae: 3.1715
Epoch 127/500
94/94 [==============================] - 3s 30ms/step - loss: 24.5647 - mae: 3.1700
Epoch 128/500
94/94 [==============================] - 3s 29ms/step - loss: 24.5446 - mae: 3.1686
Epoch 129/500
94/94 [==============================] - 3s 29ms/step - loss: 24.5241 - mae: 3.1672
Epoch 130/500
94/94 [==============================] - 3s 31ms/step - loss: 24.5030 - mae: 3.1658
Epoch 131/500
94/94 [==============================] - 3s 28ms/step - loss: 24.4817 - mae: 3.1643
Epoch 132/500
94/94 [==============================] - 3s 30ms/step - loss: 24.4601 - mae: 3.1630
Epoch 133/500
94/94 [==============================] - 3s 31ms/step - loss: 24.4388 - mae: 3.1616
Epoch 134/500
94/94 [==============================] - 3s 29ms/step - loss: 24.4183 - mae: 3.1604
Epoch 135/500
94/94 [==============================] - 3s 29ms/step - loss: 24.3995 - mae: 3.1596
Epoch 136/500
94/94 [==============================] - 3s 29ms/step - loss: 24.3834 - mae: 3.1591
Epoch 137/500
94/94 [==============================] - 3s 29ms/step - loss: 24.3707 - mae: 3.1591 0s
Epoch 138/500
94/94 [==============================] - 3s 29ms/step - loss: 24.3611 - mae: 3.1595 0s - loss: 21.18
Epoch 139/500
94/94 [==============================] - 3s 31ms/step - loss: 24.3524 - mae: 3.1603
Epoch 140/500
94/94 [==============================] - 3s 29ms/step - loss: 24.3426 - mae: 3.1611
Epoch 141/500
94/94 [==============================] - 3s 29ms/step - loss: 24.3315 - mae: 3.1613
Epoch 142/500
94/94 [==============================] - 3s 30ms/step - loss: 24.3181 - mae: 3.1598
Epoch 143/500
94/94 [==============================] - 3s 29ms/step - loss: 24.2963 - mae: 3.1559
Epoch 144/500
94/94 [==============================] - 3s 29ms/step - loss: 24.2581 - mae: 3.1521
Epoch 145/500
94/94 [==============================] - 3s 29ms/step - loss: 24.2306 - mae: 3.1490
Epoch 146/500
94/94 [==============================] - 3s 31ms/step - loss: 24.2129 - mae: 3.1469
Epoch 147/500
94/94 [==============================] - 3s 29ms/step - loss: 24.1976 - mae: 3.1451
Epoch 148/500
94/94 [==============================] - 3s 31ms/step - loss: 24.1856 - mae: 3.1439
Epoch 149/500
94/94 [==============================] - 3s 29ms/step - loss: 24.1774 - mae: 3.1432
Epoch 150/500
94/94 [==============================] - 3s 30ms/step - loss: 24.1709 - mae: 3.1426
Epoch 151/500
94/94 [==============================] - 3s 30ms/step - loss: 24.1653 - mae: 3.1419
Epoch 152/500
94/94 [==============================] - 3s 29ms/step - loss: 24.1604 - mae: 3.1411
Epoch 153/500
94/94 [==============================] - 3s 29ms/step - loss: 24.1560 - mae: 3.1403
Epoch 154/500
94/94 [==============================] - 3s 29ms/step - loss: 24.1520 - mae: 3.1395
Epoch 155/500
94/94 [==============================] - 3s 30ms/step - loss: 24.1481 - mae: 3.1386
Epoch 156/500
94/94 [==============================] - 3s 29ms/step - loss: 24.1442 - mae: 3.1378
Epoch 157/500
94/94 [==============================] - 3s 31ms/step - loss: 24.1401 - mae: 3.1369
Epoch 158/500
94/94 [==============================] - 3s 29ms/step - loss: 24.1356 - mae: 3.1357
Epoch 159/500
94/94 [==============================] - 3s 30ms/step - loss: 24.1304 - mae: 3.1343
Epoch 160/500
94/94 [==============================] - 3s 31ms/step - loss: 24.1244 - mae: 3.1327
Epoch 161/500
94/94 [==============================] - 3s 31ms/step - loss: 24.1173 - mae: 3.1311
Epoch 162/500
94/94 [==============================] - 3s 30ms/step - loss: 24.1094 - mae: 3.1291
Epoch 163/500
94/94 [==============================] - 3s 31ms/step - loss: 24.1020 - mae: 3.1268
Epoch 164/500
94/94 [==============================] - 4s 41ms/step - loss: 24.0991 - mae: 3.1241
Epoch 165/500
94/94 [==============================] - 3s 37ms/step - loss: 24.1267 - mae: 3.1212
Epoch 166/500
94/94 [==============================] - 3s 34ms/step - loss: 24.2798 - mae: 3.1223
Epoch 167/500
94/94 [==============================] - 3s 31ms/step - loss: 24.2862 - mae: 3.1285
Epoch 168/500
94/94 [==============================] - 2s 26ms/step - loss: 24.1669 - mae: 3.1222
Epoch 169/500
94/94 [==============================] - 3s 35ms/step - loss: 24.2686 - mae: 3.1252
Epoch 170/500
94/94 [==============================] - 3s 35ms/step - loss: 24.1808 - mae: 3.1172
Epoch 171/500
94/94 [==============================] - 3s 28ms/step - loss: 24.1209 - mae: 3.1115
Epoch 172/500
94/94 [==============================] - 3s 29ms/step - loss: 24.2097 - mae: 3.1187
Epoch 173/500
94/94 [==============================] - 4s 39ms/step - loss: 24.1257 - mae: 3.1118
Epoch 174/500
94/94 [==============================] - 3s 28ms/step - loss: 24.1124 - mae: 3.1070
Epoch 175/500
94/94 [==============================] - 3s 28ms/step - loss: 24.1746 - mae: 3.1157
Epoch 176/500
94/94 [==============================] - 2s 25ms/step - loss: 24.0774 - mae: 3.1067
Epoch 177/500
94/94 [==============================] - 4s 38ms/step - loss: 24.0509 - mae: 3.1010
Epoch 178/500
94/94 [==============================] - 4s 44ms/step - loss: 24.1352 - mae: 3.1113
Epoch 179/500
94/94 [==============================] - 3s 35ms/step - loss: 24.0326 - mae: 3.1018
Epoch 180/500
94/94 [==============================] - 3s 33ms/step - loss: 24.0220 - mae: 3.0997
Epoch 181/500
94/94 [==============================] - 3s 34ms/step - loss: 24.0183 - mae: 3.0982
Epoch 182/500
94/94 [==============================] - 3s 31ms/step - loss: 24.0289 - mae: 3.1012
Epoch 183/500
94/94 [==============================] - 3s 33ms/step - loss: 23.9616 - mae: 3.0920
Epoch 184/500
94/94 [==============================] - 3s 28ms/step - loss: 24.0379 - mae: 3.1017
Epoch 185/500
94/94 [==============================] - 4s 39ms/step - loss: 23.9499 - mae: 3.0931
Epoch 186/500
94/94 [==============================] - 3s 36ms/step - loss: 23.9342 - mae: 3.0895
Epoch 187/500
94/94 [==============================] - 3s 32ms/step - loss: 23.9956 - mae: 3.0977
Epoch 188/500
94/94 [==============================] - 3s 30ms/step - loss: 23.9097 - mae: 3.0892
Epoch 189/500
94/94 [==============================] - 3s 29ms/step - loss: 23.8876 - mae: 3.0852
Epoch 190/500
94/94 [==============================] - 3s 29ms/step - loss: 23.9684 - mae: 3.0951
Epoch 191/500
94/94 [==============================] - 3s 29ms/step - loss: 23.8776 - mae: 3.0862
Epoch 192/500
94/94 [==============================] - 3s 29ms/step - loss: 23.8681 - mae: 3.0838
Epoch 193/500
94/94 [==============================] - 3s 29ms/step - loss: 23.8901 - mae: 3.0882
Epoch 194/500
94/94 [==============================] - 3s 29ms/step - loss: 23.8244 - mae: 3.0792
Epoch 195/500
94/94 [==============================] - 3s 31ms/step - loss: 23.9032 - mae: 3.0891
Epoch 196/500
94/94 [==============================] - 3s 29ms/step - loss: 23.8209 - mae: 3.0810
Epoch 197/500
94/94 [==============================] - 3s 30ms/step - loss: 23.8050 - mae: 3.0776
Epoch 198/500
94/94 [==============================] - 3s 29ms/step - loss: 23.8627 - mae: 3.0857
Epoch 199/500
94/94 [==============================] - 3s 30ms/step - loss: 23.7861 - mae: 3.0779
Epoch 200/500
94/94 [==============================] - 3s 29ms/step - loss: 23.7720 - mae: 3.0749
Epoch 201/500
94/94 [==============================] - 3s 29ms/step - loss: 23.8309 - mae: 3.0829
Epoch 202/500
94/94 [==============================] - 3s 29ms/step - loss: 23.7572 - mae: 3.0755
Epoch 203/500
94/94 [==============================] - 3s 28ms/step - loss: 23.7414 - mae: 3.0724
Epoch 204/500
94/94 [==============================] - 3s 28ms/step - loss: 23.8009 - mae: 3.0804
Epoch 205/500
94/94 [==============================] - 3s 29ms/step - loss: 23.7288 - mae: 3.0732
Epoch 206/500
94/94 [==============================] - 3s 29ms/step - loss: 23.7151 - mae: 3.0706
Epoch 207/500
94/94 [==============================] - 3s 28ms/step - loss: 23.7680 - mae: 3.0778
Epoch 208/500
94/94 [==============================] - 3s 30ms/step - loss: 23.7013 - mae: 3.0710
Epoch 209/500
94/94 [==============================] - 3s 34ms/step - loss: 23.6959 - mae: 3.0699
Epoch 210/500
94/94 [==============================] - 3s 33ms/step - loss: 23.7237 - mae: 3.0744
Epoch 211/500
94/94 [==============================] - 3s 30ms/step - loss: 23.6715 - mae: 3.0678
Epoch 212/500
94/94 [==============================] - 3s 30ms/step - loss: 23.7148 - mae: 3.0739
Epoch 213/500
94/94 [==============================] - 3s 29ms/step - loss: 23.6599 - mae: 3.0674 0s - loss: 19.7459 -
Epoch 214/500
94/94 [==============================] - 3s 30ms/step - loss: 23.6944 - mae: 3.0725
Epoch 215/500
94/94 [==============================] - 3s 30ms/step - loss: 23.6418 - mae: 3.0660
Epoch 216/500
94/94 [==============================] - 3s 32ms/step - loss: 23.6992 - mae: 3.0730
Epoch 217/500
94/94 [==============================] - 3s 32ms/step - loss: 23.6395 - mae: 3.0668
Epoch 218/500
94/94 [==============================] - 2s 26ms/step - loss: 23.6476 - mae: 3.0681
Epoch 219/500
94/94 [==============================] - 2s 26ms/step - loss: 23.6302 - mae: 3.0661
Epoch 220/500
94/94 [==============================] - 2s 26ms/step - loss: 23.6383 - mae: 3.0677 1s
Epoch 221/500
94/94 [==============================] - 2s 25ms/step - loss: 23.6011 - mae: 3.0631
Epoch 222/500
94/94 [==============================] - 2s 25ms/step - loss: 23.6612 - mae: 3.0696
Epoch 223/500
94/94 [==============================] - 2s 25ms/step - loss: 23.6017 - mae: 3.0639
Epoch 224/500
94/94 [==============================] - 2s 24ms/step - loss: 23.6025 - mae: 3.0639
Epoch 225/500
94/94 [==============================] - 2s 24ms/step - loss: 23.5991 - mae: 3.0639
Epoch 226/500
94/94 [==============================] - 2s 25ms/step - loss: 23.5771 - mae: 3.0612
Epoch 227/500
94/94 [==============================] - 2s 25ms/step - loss: 23.6034 - mae: 3.0646
Epoch 228/500
94/94 [==============================] - 2s 25ms/step - loss: 23.5534 - mae: 3.0590
Epoch 229/500
94/94 [==============================] - 2s 27ms/step - loss: 23.6109 - mae: 3.0649
Epoch 230/500
94/94 [==============================] - 2s 25ms/step - loss: 23.5513 - mae: 3.0591
Epoch 231/500
94/94 [==============================] - 2s 25ms/step - loss: 23.5609 - mae: 3.0603
Epoch 232/500
94/94 [==============================] - 3s 28ms/step - loss: 23.5380 - mae: 3.0575 2s - loss: 21.97
Epoch 233/500
94/94 [==============================] - 3s 27ms/step - loss: 23.5581 - mae: 3.0602
Epoch 234/500
94/94 [==============================] - 3s 27ms/step - loss: 23.5129 - mae: 3.0552
Epoch 235/500
94/94 [==============================] - 2s 25ms/step - loss: 23.5681 - mae: 3.0609
Epoch 236/500
94/94 [==============================] - 2s 24ms/step - loss: 23.5100 - mae: 3.0550
Epoch 237/500
94/94 [==============================] - 2s 25ms/step - loss: 23.5251 - mae: 3.0569
Epoch 238/500
94/94 [==============================] - 2s 25ms/step - loss: 23.4944 - mae: 3.0533
Epoch 239/500
94/94 [==============================] - 2s 25ms/step - loss: 23.5279 - mae: 3.0573
Epoch 240/500
94/94 [==============================] - 2s 25ms/step - loss: 23.4783 - mae: 3.0518
Epoch 241/500
94/94 [==============================] - 2s 25ms/step - loss: 23.5193 - mae: 3.0564
Epoch 242/500
94/94 [==============================] - 2s 25ms/step - loss: 23.4676 - mae: 3.0508
Epoch 243/500
94/94 [==============================] - 2s 25ms/step - loss: 23.5017 - mae: 3.0548
Epoch 244/500
94/94 [==============================] - 2s 25ms/step - loss: 23.4540 - mae: 3.0495
Epoch 245/500
94/94 [==============================] - 2s 25ms/step - loss: 23.4933 - mae: 3.0540 0s - loss:
Epoch 246/500
94/94 [==============================] - 2s 25ms/step - loss: 23.4436 - mae: 3.0485
Epoch 247/500
94/94 [==============================] - 2s 25ms/step - loss: 23.4766 - mae: 3.0524
Epoch 248/500
94/94 [==============================] - 3s 27ms/step - loss: 23.4311 - mae: 3.0473
Epoch 249/500
94/94 [==============================] - 2s 25ms/step - loss: 23.4671 - mae: 3.0514
Epoch 250/500
94/94 [==============================] - 2s 24ms/step - loss: 23.4203 - mae: 3.0463
Epoch 251/500
94/94 [==============================] - 2s 24ms/step - loss: 23.4526 - mae: 3.0500
Epoch 252/500
94/94 [==============================] - 2s 24ms/step - loss: 23.4089 - mae: 3.0452
Epoch 253/500
94/94 [==============================] - 2s 26ms/step - loss: 23.4416 - mae: 3.0489
Epoch 254/500
94/94 [==============================] - 2s 26ms/step - loss: 23.3981 - mae: 3.0442
Epoch 255/500
94/94 [==============================] - 2s 24ms/step - loss: 23.4289 - mae: 3.0477
Epoch 256/500
94/94 [==============================] - 2s 25ms/step - loss: 23.3874 - mae: 3.0431
Epoch 257/500
94/94 [==============================] - 2s 24ms/step - loss: 23.4173 - mae: 3.0465
Epoch 258/500
94/94 [==============================] - 2s 25ms/step - loss: 23.3770 - mae: 3.0421
Epoch 259/500
94/94 [==============================] - 2s 24ms/step - loss: 23.4055 - mae: 3.0454
Epoch 260/500
94/94 [==============================] - 3s 29ms/step - loss: 23.3668 - mae: 3.0411
Epoch 261/500
94/94 [==============================] - 3s 33ms/step - loss: 23.3941 - mae: 3.0443
Epoch 262/500
94/94 [==============================] - 3s 31ms/step - loss: 23.3568 - mae: 3.0401
Epoch 263/500
94/94 [==============================] - 3s 30ms/step - loss: 23.3829 - mae: 3.0431
Epoch 264/500
94/94 [==============================] - 3s 29ms/step - loss: 23.3471 - mae: 3.0391
Epoch 265/500
94/94 [==============================] - 3s 32ms/step - loss: 23.3719 - mae: 3.0420
Epoch 266/500
94/94 [==============================] - 3s 29ms/step - loss: 23.3377 - mae: 3.0382
Epoch 267/500
94/94 [==============================] - 3s 29ms/step - loss: 23.3613 - mae: 3.0410
Epoch 268/500
94/94 [==============================] - 3s 31ms/step - loss: 23.3285 - mae: 3.0373
Epoch 269/500
94/94 [==============================] - 3s 28ms/step - loss: 23.3508 - mae: 3.0399 0s - loss:
Epoch 270/500
94/94 [==============================] - 2s 25ms/step - loss: 23.3194 - mae: 3.0363
Epoch 271/500
94/94 [==============================] - 2s 25ms/step - loss: 23.3407 - mae: 3.0388
Epoch 272/500
94/94 [==============================] - 2s 26ms/step - loss: 23.3106 - mae: 3.0354
Epoch 273/500
94/94 [==============================] - 2s 25ms/step - loss: 23.3307 - mae: 3.0378
Epoch 274/500
94/94 [==============================] - 2s 25ms/step - loss: 23.3020 - mae: 3.0345
Epoch 275/500
94/94 [==============================] - 2s 24ms/step - loss: 23.3210 - mae: 3.0368
Epoch 276/500
94/94 [==============================] - 2s 25ms/step - loss: 23.2935 - mae: 3.0337
Epoch 277/500
94/94 [==============================] - 4s 39ms/step - loss: 23.3115 - mae: 3.0358
Epoch 278/500
94/94 [==============================] - 3s 28ms/step - loss: 23.2852 - mae: 3.0328
Epoch 279/500
94/94 [==============================] - 2s 26ms/step - loss: 23.3022 - mae: 3.0348
Epoch 280/500
94/94 [==============================] - 2s 26ms/step - loss: 23.2770 - mae: 3.0320
Epoch 281/500
94/94 [==============================] - 2s 25ms/step - loss: 23.2931 - mae: 3.0339
Epoch 282/500
94/94 [==============================] - 2s 25ms/step - loss: 23.2691 - mae: 3.0311
Epoch 283/500
94/94 [==============================] - 2s 24ms/step - loss: 23.2842 - mae: 3.0330
Epoch 284/500
94/94 [==============================] - 2s 24ms/step - loss: 23.2612 - mae: 3.0303
Epoch 285/500
94/94 [==============================] - 2s 24ms/step - loss: 23.2755 - mae: 3.0321
Epoch 286/500
94/94 [==============================] - 2s 25ms/step - loss: 23.2535 - mae: 3.0296
Epoch 287/500
94/94 [==============================] - 2s 26ms/step - loss: 23.2669 - mae: 3.0312
Epoch 288/500
94/94 [==============================] - 2s 25ms/step - loss: 23.2459 - mae: 3.0288
Epoch 289/500
94/94 [==============================] - 3s 29ms/step - loss: 23.2584 - mae: 3.0304
Epoch 290/500
94/94 [==============================] - 3s 31ms/step - loss: 23.2385 - mae: 3.0281
Epoch 291/500
94/94 [==============================] - 3s 33ms/step - loss: 23.2502 - mae: 3.0295
Epoch 292/500
94/94 [==============================] - 3s 33ms/step - loss: 23.2312 - mae: 3.0273
Epoch 293/500
94/94 [==============================] - 3s 32ms/step - loss: 23.2420 - mae: 3.0287
Epoch 294/500
94/94 [==============================] - 3s 30ms/step - loss: 23.2240 - mae: 3.0266
Epoch 295/500
94/94 [==============================] - 3s 29ms/step - loss: 23.2340 - mae: 3.0279
Epoch 296/500
94/94 [==============================] - 3s 29ms/step - loss: 23.2170 - mae: 3.0259
Epoch 297/500
94/94 [==============================] - 3s 29ms/step - loss: 23.2261 - mae: 3.0271
Epoch 298/500
94/94 [==============================] - 3s 29ms/step - loss: 23.2100 - mae: 3.0252
Epoch 299/500
94/94 [==============================] - 3s 30ms/step - loss: 23.2184 - mae: 3.0264
Epoch 300/500
94/94 [==============================] - 3s 30ms/step - loss: 23.2032 - mae: 3.0245
Epoch 301/500
94/94 [==============================] - 3s 28ms/step - loss: 23.2108 - mae: 3.0256
Epoch 302/500
94/94 [==============================] - 3s 29ms/step - loss: 23.1964 - mae: 3.0239
Epoch 303/500
94/94 [==============================] - 3s 29ms/step - loss: 23.2033 - mae: 3.0249 0s - loss: 2
Epoch 304/500
94/94 [==============================] - 3s 29ms/step - loss: 23.1898 - mae: 3.0232
Epoch 305/500
94/94 [==============================] - 3s 31ms/step - loss: 23.1959 - mae: 3.0242
Epoch 306/500
94/94 [==============================] - 3s 31ms/step - loss: 23.1833 - mae: 3.0226
Epoch 307/500
94/94 [==============================] - 3s 29ms/step - loss: 23.1886 - mae: 3.0234
Epoch 308/500
94/94 [==============================] - 3s 29ms/step - loss: 23.1768 - mae: 3.0220
Epoch 309/500
94/94 [==============================] - 3s 29ms/step - loss: 23.1814 - mae: 3.0227
Epoch 310/500
94/94 [==============================] - 3s 31ms/step - loss: 23.1705 - mae: 3.0214
Epoch 311/500
94/94 [==============================] - 3s 30ms/step - loss: 23.1744 - mae: 3.0221
Epoch 312/500
94/94 [==============================] - 3s 30ms/step - loss: 23.1642 - mae: 3.0208
Epoch 313/500
94/94 [==============================] - 3s 30ms/step - loss: 23.1674 - mae: 3.0214
Epoch 314/500
94/94 [==============================] - 3s 29ms/step - loss: 23.1580 - mae: 3.0202
Epoch 315/500
94/94 [==============================] - 3s 29ms/step - loss: 23.1606 - mae: 3.0208
Epoch 316/500
94/94 [==============================] - 3s 29ms/step - loss: 23.1519 - mae: 3.0197 0s - loss: 19.75
Epoch 317/500
94/94 [==============================] - 3s 29ms/step - loss: 23.1538 - mae: 3.0201
Epoch 318/500
94/94 [==============================] - 3s 30ms/step - loss: 23.1459 - mae: 3.0192
Epoch 319/500
94/94 [==============================] - 3s 31ms/step - loss: 23.1472 - mae: 3.0195
Epoch 320/500
94/94 [==============================] - 3s 35ms/step - loss: 23.1400 - mae: 3.0186
Epoch 321/500
94/94 [==============================] - 2s 26ms/step - loss: 23.1407 - mae: 3.0189
Epoch 322/500
94/94 [==============================] - 3s 27ms/step - loss: 23.1341 - mae: 3.0181
Epoch 323/500
94/94 [==============================] - 2s 25ms/step - loss: 23.1343 - mae: 3.0183
Epoch 324/500
94/94 [==============================] - 2s 25ms/step - loss: 23.1283 - mae: 3.0176 0s - los
Epoch 325/500
94/94 [==============================] - 2s 26ms/step - loss: 23.1280 - mae: 3.0177
Epoch 326/500
94/94 [==============================] - 2s 25ms/step - loss: 23.1225 - mae: 3.0171
Epoch 327/500
94/94 [==============================] - 2s 25ms/step - loss: 23.1218 - mae: 3.0172
Epoch 328/500
94/94 [==============================] - 2s 25ms/step - loss: 23.1168 - mae: 3.0166 0s - l
Epoch 329/500
94/94 [==============================] - 2s 25ms/step - loss: 23.1158 - mae: 3.0166
Epoch 330/500
94/94 [==============================] - 2s 25ms/step - loss: 23.1111 - mae: 3.0161
Epoch 331/500
94/94 [==============================] - 2s 25ms/step - loss: 23.1098 - mae: 3.0161
Epoch 332/500
94/94 [==============================] - 2s 25ms/step - loss: 23.1055 - mae: 3.0156
Epoch 333/500
94/94 [==============================] - 2s 25ms/step - loss: 23.1039 - mae: 3.0156
Epoch 334/500
94/94 [==============================] - 2s 24ms/step - loss: 23.1000 - mae: 3.0152
Epoch 335/500
94/94 [==============================] - 2s 25ms/step - loss: 23.0981 - mae: 3.0151
Epoch 336/500
94/94 [==============================] - 2s 24ms/step - loss: 23.0945 - mae: 3.0147
Epoch 337/500
94/94 [==============================] - 2s 24ms/step - loss: 23.0924 - mae: 3.0146
Epoch 338/500
94/94 [==============================] - 2s 24ms/step - loss: 23.0890 - mae: 3.0142 0s - loss: 18.9323 - mae:
Epoch 339/500
94/94 [==============================] - 2s 24ms/step - loss: 23.0868 - mae: 3.0141
Epoch 340/500
94/94 [==============================] - 2s 24ms/step - loss: 23.0836 - mae: 3.0138
Epoch 341/500
94/94 [==============================] - 2s 24ms/step - loss: 23.0813 - mae: 3.0136
Epoch 342/500
94/94 [==============================] - 2s 24ms/step - loss: 23.0782 - mae: 3.0133
Epoch 343/500
94/94 [==============================] - 2s 24ms/step - loss: 23.0759 - mae: 3.0132
Epoch 344/500
94/94 [==============================] - 2s 26ms/step - loss: 23.0729 - mae: 3.0129 0s - loss: 19.5530
Epoch 345/500
94/94 [==============================] - 2s 26ms/step - loss: 23.0705 - mae: 3.0127
Epoch 346/500
94/94 [==============================] - 2s 25ms/step - loss: 23.0677 - mae: 3.0125
Epoch 347/500
94/94 [==============================] - 2s 24ms/step - loss: 23.0652 - mae: 3.0123
Epoch 348/500
94/94 [==============================] - 2s 24ms/step - loss: 23.0625 - mae: 3.0120
Epoch 349/500
94/94 [==============================] - 2s 24ms/step - loss: 23.0600 - mae: 3.0118
Epoch 350/500
94/94 [==============================] - 2s 24ms/step - loss: 23.0573 - mae: 3.0116
Epoch 351/500
94/94 [==============================] - 2s 24ms/step - loss: 23.0549 - mae: 3.0114
Epoch 352/500
94/94 [==============================] - 2s 24ms/step - loss: 23.0522 - mae: 3.0112
Epoch 353/500
94/94 [==============================] - 2s 26ms/step - loss: 23.0498 - mae: 3.0110
Epoch 354/500
94/94 [==============================] - 2s 25ms/step - loss: 23.0472 - mae: 3.0108
Epoch 355/500
94/94 [==============================] - 2s 24ms/step - loss: 23.0448 - mae: 3.0106
Epoch 356/500
94/94 [==============================] - 2s 25ms/step - loss: 23.0422 - mae: 3.0104
Epoch 357/500
94/94 [==============================] - 2s 24ms/step - loss: 23.0398 - mae: 3.0102
Epoch 358/500
94/94 [==============================] - 2s 24ms/step - loss: 23.0373 - mae: 3.0099
Epoch 359/500
94/94 [==============================] - 2s 24ms/step - loss: 23.0349 - mae: 3.0097
Epoch 360/500
94/94 [==============================] - 2s 25ms/step - loss: 23.0324 - mae: 3.0095
Epoch 361/500
94/94 [==============================] - 2s 24ms/step - loss: 23.0300 - mae: 3.0093
Epoch 362/500
94/94 [==============================] - 2s 24ms/step - loss: 23.0276 - mae: 3.0091
Epoch 363/500
94/94 [==============================] - 2s 24ms/step - loss: 23.0252 - mae: 3.0090
Epoch 364/500
94/94 [==============================] - 2s 24ms/step - loss: 23.0228 - mae: 3.0088
Epoch 365/500
94/94 [==============================] - 2s 25ms/step - loss: 23.0205 - mae: 3.0086
Epoch 366/500
94/94 [==============================] - 2s 25ms/step - loss: 23.0181 - mae: 3.0084
Epoch 367/500
94/94 [==============================] - 2s 25ms/step - loss: 23.0158 - mae: 3.0082
Epoch 368/500
94/94 [==============================] - 2s 24ms/step - loss: 23.0135 - mae: 3.0080
Epoch 369/500
94/94 [==============================] - 2s 24ms/step - loss: 23.0112 - mae: 3.0078
Epoch 370/500
94/94 [==============================] - 2s 24ms/step - loss: 23.0089 - mae: 3.0076
Epoch 371/500
94/94 [==============================] - 2s 26ms/step - loss: 23.0066 - mae: 3.0075 0s - los
Epoch 372/500
94/94 [==============================] - 2s 24ms/step - loss: 23.0043 - mae: 3.0073
Epoch 373/500
94/94 [==============================] - 2s 24ms/step - loss: 23.0020 - mae: 3.0071
Epoch 374/500
94/94 [==============================] - 2s 24ms/step - loss: 22.9998 - mae: 3.0069
Epoch 375/500
94/94 [==============================] - 2s 25ms/step - loss: 22.9975 - mae: 3.0067
Epoch 376/500
94/94 [==============================] - 2s 25ms/step - loss: 22.9953 - mae: 3.0066
Epoch 377/500
94/94 [==============================] - 2s 24ms/step - loss: 22.9931 - mae: 3.0064
Epoch 378/500
94/94 [==============================] - 2s 24ms/step - loss: 22.9909 - mae: 3.0062
Epoch 379/500
94/94 [==============================] - 2s 24ms/step - loss: 22.9887 - mae: 3.0061
Epoch 380/500
94/94 [==============================] - 2s 24ms/step - loss: 22.9865 - mae: 3.0059
Epoch 381/500
94/94 [==============================] - 2s 24ms/step - loss: 22.9844 - mae: 3.0057
Epoch 382/500
94/94 [==============================] - 2s 25ms/step - loss: 22.9822 - mae: 3.0056
Epoch 383/500
94/94 [==============================] - 2s 24ms/step - loss: 22.9801 - mae: 3.0054
Epoch 384/500
94/94 [==============================] - 2s 25ms/step - loss: 22.9779 - mae: 3.0053
Epoch 385/500
94/94 [==============================] - 2s 25ms/step - loss: 22.9758 - mae: 3.0051
Epoch 386/500
94/94 [==============================] - 2s 25ms/step - loss: 22.9737 - mae: 3.0049
Epoch 387/500
94/94 [==============================] - 2s 25ms/step - loss: 22.9716 - mae: 3.0048
Epoch 388/500
94/94 [==============================] - 2s 26ms/step - loss: 22.9695 - mae: 3.0046
Epoch 389/500
94/94 [==============================] - 2s 25ms/step - loss: 22.9674 - mae: 3.0045
Epoch 390/500
94/94 [==============================] - 2s 25ms/step - loss: 22.9654 - mae: 3.0044
Epoch 391/500
94/94 [==============================] - 2s 25ms/step - loss: 22.9633 - mae: 3.0042
Epoch 392/500
94/94 [==============================] - 2s 25ms/step - loss: 22.9613 - mae: 3.0041 0s - loss: 20.
Epoch 393/500
94/94 [==============================] - 2s 25ms/step - loss: 22.9592 - mae: 3.0039
Epoch 394/500
94/94 [==============================] - 2s 25ms/step - loss: 22.9572 - mae: 3.0038
Epoch 395/500
94/94 [==============================] - 2s 24ms/step - loss: 22.9552 - mae: 3.0036
Epoch 396/500
94/94 [==============================] - 2s 25ms/step - loss: 22.9532 - mae: 3.0035
Epoch 397/500
94/94 [==============================] - 2s 25ms/step - loss: 22.9512 - mae: 3.0033
Epoch 398/500
94/94 [==============================] - 2s 25ms/step - loss: 22.9492 - mae: 3.0032
Epoch 399/500
94/94 [==============================] - 2s 26ms/step - loss: 22.9473 - mae: 3.0031
Epoch 400/500
94/94 [==============================] - 3s 28ms/step - loss: 22.9453 - mae: 3.0029
Epoch 401/500
94/94 [==============================] - 2s 25ms/step - loss: 22.9433 - mae: 3.0028
Epoch 402/500
94/94 [==============================] - 2s 25ms/step - loss: 22.9414 - mae: 3.0026
Epoch 403/500
94/94 [==============================] - 2s 25ms/step - loss: 22.9395 - mae: 3.0025
Epoch 404/500
94/94 [==============================] - 2s 26ms/step - loss: 22.9376 - mae: 3.0024
Epoch 405/500
94/94 [==============================] - 2s 25ms/step - loss: 22.9356 - mae: 3.0022
Epoch 406/500
94/94 [==============================] - 2s 26ms/step - loss: 22.9337 - mae: 3.0021 0s - loss: 19.0217 -
Epoch 407/500
94/94 [==============================] - 4s 38ms/step - loss: 22.9319 - mae: 3.0019
Epoch 408/500
94/94 [==============================] - 3s 32ms/step - loss: 22.9300 - mae: 3.0018
Epoch 409/500
94/94 [==============================] - 3s 31ms/step - loss: 22.9281 - mae: 3.0017
Epoch 410/500
94/94 [==============================] - 3s 31ms/step - loss: 22.9262 - mae: 3.0015
Epoch 411/500
94/94 [==============================] - 3s 30ms/step - loss: 22.9244 - mae: 3.0014
Epoch 412/500
94/94 [==============================] - 3s 31ms/step - loss: 22.9225 - mae: 3.0013
Epoch 413/500
94/94 [==============================] - 3s 32ms/step - loss: 22.9207 - mae: 3.0012
Epoch 414/500
94/94 [==============================] - 3s 31ms/step - loss: 22.9189 - mae: 3.0010
Epoch 415/500
94/94 [==============================] - 3s 28ms/step - loss: 22.9171 - mae: 3.0009
Epoch 416/500
94/94 [==============================] - 3s 28ms/step - loss: 22.9153 - mae: 3.0008
Epoch 417/500
94/94 [==============================] - 3s 28ms/step - loss: 22.9135 - mae: 3.0006
Epoch 418/500
94/94 [==============================] - 3s 29ms/step - loss: 22.9117 - mae: 3.0005
Epoch 419/500
94/94 [==============================] - 2s 25ms/step - loss: 22.9099 - mae: 3.0004
Epoch 420/500
94/94 [==============================] - 2s 25ms/step - loss: 22.9081 - mae: 3.0003
Epoch 421/500
94/94 [==============================] - 2s 24ms/step - loss: 22.9064 - mae: 3.0001
Epoch 422/500
94/94 [==============================] - 2s 26ms/step - loss: 22.9046 - mae: 3.0000
Epoch 423/500
94/94 [==============================] - 2s 24ms/step - loss: 22.9029 - mae: 2.9999
Epoch 424/500
94/94 [==============================] - 2s 24ms/step - loss: 22.9011 - mae: 2.9998
Epoch 425/500
94/94 [==============================] - 2s 24ms/step - loss: 22.8994 - mae: 2.9996
Epoch 426/500
94/94 [==============================] - 2s 24ms/step - loss: 22.8977 - mae: 2.9995
Epoch 427/500
94/94 [==============================] - 2s 24ms/step - loss: 22.8960 - mae: 2.9994
Epoch 428/500
94/94 [==============================] - 2s 26ms/step - loss: 22.8943 - mae: 2.9993 0s - loss:
Epoch 429/500
94/94 [==============================] - 2s 26ms/step - loss: 22.8926 - mae: 2.9992
Epoch 430/500
94/94 [==============================] - 2s 24ms/step - loss: 22.8909 - mae: 2.9990
Epoch 431/500
94/94 [==============================] - 2s 25ms/step - loss: 22.8893 - mae: 2.9989
Epoch 432/500
94/94 [==============================] - 2s 25ms/step - loss: 22.8876 - mae: 2.9988
Epoch 433/500
94/94 [==============================] - 2s 25ms/step - loss: 22.8859 - mae: 2.9987
Epoch 434/500
94/94 [==============================] - 2s 25ms/step - loss: 22.8843 - mae: 2.9986
Epoch 435/500
94/94 [==============================] - 2s 25ms/step - loss: 22.8826 - mae: 2.9985
Epoch 436/500
94/94 [==============================] - 2s 25ms/step - loss: 22.8810 - mae: 2.9984
Epoch 437/500
94/94 [==============================] - 2s 24ms/step - loss: 22.8794 - mae: 2.9983
Epoch 438/500
94/94 [==============================] - 2s 24ms/step - loss: 22.8778 - mae: 2.9982 1s
Epoch 439/500
94/94 [==============================] - 2s 24ms/step - loss: 22.8762 - mae: 2.9981
Epoch 440/500
94/94 [==============================] - 4s 40ms/step - loss: 22.8746 - mae: 2.9980
Epoch 441/500
94/94 [==============================] - 3s 30ms/step - loss: 22.8730 - mae: 2.9979
Epoch 442/500
94/94 [==============================] - 3s 30ms/step - loss: 22.8714 - mae: 2.9978
Epoch 443/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8698 - mae: 2.9977
Epoch 444/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8682 - mae: 2.9976
Epoch 445/500
94/94 [==============================] - 3s 28ms/step - loss: 22.8667 - mae: 2.9975
Epoch 446/500
94/94 [==============================] - 3s 30ms/step - loss: 22.8651 - mae: 2.9975 0s -
Epoch 447/500
94/94 [==============================] - 3s 30ms/step - loss: 22.8636 - mae: 2.9974
Epoch 448/500
94/94 [==============================] - 3s 34ms/step - loss: 22.8620 - mae: 2.9973
Epoch 449/500
94/94 [==============================] - 3s 32ms/step - loss: 22.8605 - mae: 2.9972
Epoch 450/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8590 - mae: 2.9971
Epoch 451/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8575 - mae: 2.9970
Epoch 452/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8560 - mae: 2.9969
Epoch 453/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8545 - mae: 2.9969
Epoch 454/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8530 - mae: 2.9968 2s -
Epoch 455/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8515 - mae: 2.9967
Epoch 456/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8500 - mae: 2.9966
Epoch 457/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8485 - mae: 2.9965 0s - loss: 19.0661
Epoch 458/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8471 - mae: 2.9964
Epoch 459/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8456 - mae: 2.9964
Epoch 460/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8442 - mae: 2.9963
Epoch 461/500
94/94 [==============================] - 3s 31ms/step - loss: 22.8427 - mae: 2.9962
Epoch 462/500
94/94 [==============================] - 3s 30ms/step - loss: 22.8413 - mae: 2.9961
Epoch 463/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8399 - mae: 2.9961
Epoch 464/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8384 - mae: 2.9960
Epoch 465/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8370 - mae: 2.9959
Epoch 466/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8356 - mae: 2.9958
Epoch 467/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8342 - mae: 2.9958
Epoch 468/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8328 - mae: 2.9957
Epoch 469/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8314 - mae: 2.9956
Epoch 470/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8300 - mae: 2.9955
Epoch 471/500
94/94 [==============================] - 3s 30ms/step - loss: 22.8287 - mae: 2.9955
Epoch 472/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8273 - mae: 2.9954
Epoch 473/500
94/94 [==============================] - 3s 30ms/step - loss: 22.8259 - mae: 2.9953
Epoch 474/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8246 - mae: 2.9953
Epoch 475/500
94/94 [==============================] - 3s 30ms/step - loss: 22.8232 - mae: 2.9952
Epoch 476/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8219 - mae: 2.9951 0s - loss:
Epoch 477/500
94/94 [==============================] - 3s 28ms/step - loss: 22.8205 - mae: 2.9950
Epoch 478/500
94/94 [==============================] - 3s 30ms/step - loss: 22.8192 - mae: 2.9950
Epoch 479/500
94/94 [==============================] - 4s 42ms/step - loss: 22.8179 - mae: 2.9949
Epoch 480/500
94/94 [==============================] - 3s 32ms/step - loss: 22.8166 - mae: 2.9948 0s - loss:
Epoch 481/500
94/94 [==============================] - 3s 30ms/step - loss: 22.8152 - mae: 2.9948
Epoch 482/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8139 - mae: 2.9947
Epoch 483/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8126 - mae: 2.9946
Epoch 484/500
94/94 [==============================] - 3s 30ms/step - loss: 22.8113 - mae: 2.9945
Epoch 485/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8101 - mae: 2.9945
Epoch 486/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8088 - mae: 2.9944 0s - loss: 19.2434 - mae
Epoch 487/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8075 - mae: 2.9943
Epoch 488/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8062 - mae: 2.9943
Epoch 489/500
94/94 [==============================] - 3s 30ms/step - loss: 22.8050 - mae: 2.9942
Epoch 490/500
94/94 [==============================] - 3s 32ms/step - loss: 22.8037 - mae: 2.9942
Epoch 491/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8024 - mae: 2.9941
Epoch 492/500
94/94 [==============================] - 3s 29ms/step - loss: 22.8012 - mae: 2.9940
Epoch 493/500
94/94 [==============================] - 3s 30ms/step - loss: 22.7999 - mae: 2.9940
Epoch 494/500
94/94 [==============================] - 3s 33ms/step - loss: 22.7987 - mae: 2.9939
Epoch 495/500
94/94 [==============================] - 3s 31ms/step - loss: 22.7975 - mae: 2.9939
Epoch 496/500
94/94 [==============================] - 3s 30ms/step - loss: 22.7962 - mae: 2.9938
Epoch 497/500
94/94 [==============================] - 3s 29ms/step - loss: 22.7950 - mae: 2.9937
Epoch 498/500
94/94 [==============================] - 3s 30ms/step - loss: 22.7938 - mae: 2.9937
Epoch 499/500
94/94 [==============================] - 3s 29ms/step - loss: 22.7926 - mae: 2.9936
Epoch 500/500
94/94 [==============================] - 3s 28ms/step - loss: 22.7914 - mae: 2.9936
```python
forecast = []
results = []
for time in range(len(series) - window_size):
forecast.append(model.predict(series[time:time+window_size][np.newaxis]))
forecast = forecast[split_time-window_size:]
results = np.array(forecast)[:, 0,0]
plt.figure(figsize = (10,6))
plot_series(time_valid, x_valid)
plot_series(time_valid, results)
```
```python
tf.keras.metrics.mean_absolute_error(x_valid, results).numpy()
```
3.3873708
```python
import matplotlib.image as mpimg
import matplotlib.pyplot as plt
mae = history.history['mae']
loss = history.history['loss']
epochs = range(len(loss))
plt.plot(epochs, mae, 'r')
plt.plot(epochs ,loss, 'b')
plt.title('MAE and Loss')
plt.xlabel('Epochs')
plt.ylabel('Accuracy')
plt.legend(['MAE', 'Loss'])
plt.figure()
epochs_zoom = epochs[200:]
mae_zoom = mae[200:]
loss_zoom = loss[200:]
plt.plot(epochs_zoom, mae_zoom, 'r')
plt.plot(epochs_zoom, loss_zoom, 'b')
plt.title('MAE and Loss')
plt.xlabel('Epochs')
plt.ylabel('Accuracy')
plt.legend(['MAE', 'Loss'])
plt.figure()
```
<Figure size 432x288 with 0 Axes>
<Figure size 432x288 with 0 Axes>
```python
```
| 48.477383 | 175 | 0.427809 | oci_Latn | 0.785515 |
9ad9500b8ad3ac9a681589532d913dafe9892f0c | 3,254 | md | Markdown | docs/framework/configure-apps/file-schema/cryptography/oidmap-element.md | SilverBuzzard/docs.pl-pl | a3cda910e7b4b30f2c3c449c742dce1be42067b5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/configure-apps/file-schema/cryptography/oidmap-element.md | SilverBuzzard/docs.pl-pl | a3cda910e7b4b30f2c3c449c742dce1be42067b5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/configure-apps/file-schema/cryptography/oidmap-element.md | SilverBuzzard/docs.pl-pl | a3cda910e7b4b30f2c3c449c742dce1be42067b5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: '<oidmap —> — Element'
ms.date: 03/30/2017
f1_keywords:
- http://schemas.microsoft.com/.NetConfiguration/v2.0#oidMap
- http://schemas.microsoft.com/.NetConfiguration/v2.0#configuration/mscorlib/cryptographySettings/oidMap
helpviewer_keywords:
- <oidMap> element
- oidMap element
ms.assetid: 7f0c2246-c070-4748-b96a-2f66a296c539
author: mcleblanc
ms.author: markl
ms.openlocfilehash: badab8200a4b10fdc13987dfe39ebfebd4d1f7cf
ms.sourcegitcommit: ccd8c36b0d74d99291d41aceb14cf98d74dc9d2b
ms.translationtype: MT
ms.contentlocale: pl-PL
ms.lasthandoff: 12/10/2018
ms.locfileid: "53143171"
---
# <a name="ltoidmapgt-element"></a><oidmap —> — Element
Zawiera mapowania identyfikatora (OID) obiektów ASN.1 do klas.
\<Konfiguracja >
\<mscorlib >
\<cryptographysettings — >
\<oidmap — >
## <a name="syntax"></a>Składnia
```xml
<oidMap>
</oidMap>
```
## <a name="attributes-and-elements"></a>Atrybuty i elementy
W poniższych sekcjach opisano atrybuty, elementy podrzędne i elementy nadrzędne.
### <a name="attributes"></a>Atrybuty
Brak.
### <a name="child-elements"></a>Elementy podrzędne
|Element|Opis|
|-------------|-----------------|
|[\<oidentry — >](../../../../../docs/framework/configure-apps/file-schema/cryptography/oidentry-element.md)|Mapuje ASN.1 OID przyjazną nazwę.|
### <a name="parent-elements"></a>Elementy nadrzędne
|Element|Opis|
|-------------|-----------------|
|`configuration`|Element główny w każdym pliku konfiguracji używanym przez środowisko uruchomieniowe języka wspólnego i aplikacje programu .NET Framework.|
|`cryptographySettings`|Zawiera ustawienia szyfrowania.|
|`mscorlib`|Zawiera `cryptographySettings` elementu.|
## <a name="example"></a>Przykład
Poniższy przykład pokazuje, jak używać **\<oidmap — >** element zawiera mapowanie identyfikatora OID dla algorytmu wyznaczania wartości skrótu RIPEMD 160 implementacji tego algorytmu wyznaczania wartości skrótu.
```xml
<configuration>
<mscorlib>
<cryptographySettings>
<cryptoNameMapping>
<cryptoClasses>
<cryptoClass MyCrypto="MyCryptoClass, MyAssembly
Culture=neutral, PublicKeyToken=a5d015c7d5a0b012,
Version=1.0.0.0"/>
</cryptoClasses>
<nameEntry name="RIPEMD-160" class="MyCrypto"/>
</cryptoNameMapping>
<oidMap>
<oidEntry OID="1.3.36.3.2.1" name="MyCryptoClass"/>
</oidMap>
</cryptographySettings>
</mscorlib>
</configuration>
```
## <a name="see-also"></a>Zobacz też
- [Schemat pliku konfiguracji](../../../../../docs/framework/configure-apps/file-schema/index.md)
- [Schemat ustawień kryptografii](../../../../../docs/framework/configure-apps/file-schema/cryptography/index.md)
- [Usługi kryptograficzne](../../../../../docs/standard/security/cryptographic-services.md)
- [Konfigurowanie klas kryptografii](../../../../../docs/framework/configure-apps/configure-cryptography-classes.md)
- [Mapowanie identyfikatorów obiektów na algorytmy kryptografii](../../../../../docs/framework/configure-apps/map-object-identifiers-to-cryptography-algorithms.md)
| 38.738095 | 215 | 0.673018 | pol_Latn | 0.803492 |
9ada47bdc361e3eff22349ab69fc43ebae07b3af | 14,448 | md | Markdown | CHANGELOG.md | ghacupha/book-keeper | a56e497a3ccff1573e80d9679c73d030f20469bd | [
"Apache-2.0"
] | 8 | 2018-04-11T06:09:03.000Z | 2021-10-31T16:17:29.000Z | CHANGELOG.md | ghacupha/book-keeper | a56e497a3ccff1573e80d9679c73d030f20469bd | [
"Apache-2.0"
] | 2 | 2018-03-23T17:30:45.000Z | 2019-12-16T04:28:48.000Z | CHANGELOG.md | ghacupha/book-keeper | a56e497a3ccff1573e80d9679c73d030f20469bd | [
"Apache-2.0"
] | 4 | 2018-06-17T22:12:29.000Z | 2021-03-05T06:29:43.000Z |
# Changelog
Changelog for ghacupha book-keeper.
## Unreleased
### No issue
**Added time and money libraries**
[4ed3b7a6c6194c5](https://github.com/ghacupha/book-keeper/commit/4ed3b7a6c6194c5) Edwin Njeru *2018-06-06 10:11:23*
**removed units of time and money from the library**
[652495155b2fe87](https://github.com/ghacupha/book-keeper/commit/652495155b2fe87) Edwin Njeru *2018-06-06 09:59:46*
**updated the license in the unix startup script**
[12dcab7cb96d2c1](https://github.com/ghacupha/book-keeper/commit/12dcab7cb96d2c1) Edwin Njeru *2018-06-06 09:57:15*
**Fixed checkstyle issues with the tags**
[48267f98e1a9fa1](https://github.com/ghacupha/book-keeper/commit/48267f98e1a9fa1) Edwin Njeru *2018-06-06 09:44:21*
**Configured mycilia header styles**
[b493f2f551873e4](https://github.com/ghacupha/book-keeper/commit/b493f2f551873e4) Edwin Njeru *2018-06-06 09:36:35*
**Removed mycilia license plugin version and removed license header checking from the checkstyle config**
[d6e1b9d6d7583dc](https://github.com/ghacupha/book-keeper/commit/d6e1b9d6d7583dc) Edwin Njeru *2018-06-06 09:10:22*
**Added jitpack repository**
[f5f5cf7c47afb7f](https://github.com/ghacupha/book-keeper/commit/f5f5cf7c47afb7f) Edwin Njeru *2018-06-06 09:05:35*
**Removed additional unnecessary plugins**
[d10c170440a7ec5](https://github.com/ghacupha/book-keeper/commit/d10c170440a7ec5) Edwin Njeru *2018-06-06 09:02:33*
**Removed unnecessary plugin management**
[5ef71a0aa8ebab0](https://github.com/ghacupha/book-keeper/commit/5ef71a0aa8ebab0) Edwin Njeru *2018-06-06 08:52:24*
**Removed maven site plugin**
[1db7c579635fa03](https://github.com/ghacupha/book-keeper/commit/1db7c579635fa03) Edwin Njeru *2018-06-06 08:43:46*
## 1.2.0
### No issue
**preparing for version 1.2.0**
[8bb58d9ec32ffaa](https://github.com/ghacupha/book-keeper/commit/8bb58d9ec32ffaa) Edwin Njeru *2018-04-12 08:38:59*
**preparing for version 1.2.0**
[8ce478151d20ca0](https://github.com/ghacupha/book-keeper/commit/8ce478151d20ca0) Edwin Njeru *2018-04-12 08:37:29*
**preparing for version 1.2.0**
[6896ce16916e5b8](https://github.com/ghacupha/book-keeper/commit/6896ce16916e5b8) Edwin Njeru *2018-04-12 08:37:04*
**Replaced multiple IFs in the AccountAppraisalDelegate by implementing State pattern to represent the AccountSide of the Account implementation**
[6023932b2c45152](https://github.com/ghacupha/book-keeper/commit/6023932b2c45152) Edwin Njeru *2018-04-11 16:29:54*
**Additional comments and review of aggregation algorithms getCredits() and getDebits()**
[5ecf210986080b9](https://github.com/ghacupha/book-keeper/commit/5ecf210986080b9) Edwin Njeru *2018-04-11 15:03:38*
**finalised ammendments to the delegate. ToDo checkstyle checks**
[a8e1e3a94dc02af](https://github.com/ghacupha/book-keeper/commit/a8e1e3a94dc02af) ghacupha *2018-04-02 08:17:21*
**finalised ammendments to the delegate. ToDo checkstyle checks**
[01d68fdda7a2bf8](https://github.com/ghacupha/book-keeper/commit/01d68fdda7a2bf8) ghacupha *2018-04-02 08:13:02*
**created the AssignableCollectionAccount and also a constructor allowing assignment of the Collection in the simpleAccount laying the ground work for assignment of the underlying collection for the account and further allow implementation of persistent Entries into the Account**
[9a6a176598a563b](https://github.com/ghacupha/book-keeper/commit/9a6a176598a563b) ghacupha *2018-04-01 14:11:58*
**created the AssignableCollectionAccount and also a constructor allowing assignment of the Collection in the simpleAccount laying the ground work for assignment of the underlying collection for the account and further allow implementation of persistent Entries into the Account**
[70eaa86b902ab55](https://github.com/ghacupha/book-keeper/commit/70eaa86b902ab55) ghacupha *2018-04-01 14:10:15*
**created the AssignableCollectionAccount and also a constructor allowing assignment of the Collection in the simpleAccount laying the ground work for assignment of the underlying collection for the account and further allow implementation of persistent Entries into the Account**
[dc753f5f07db654](https://github.com/ghacupha/book-keeper/commit/dc753f5f07db654) ghacupha *2018-04-01 14:09:03*
**created the AccountAppraisalDelegate and refactored the Account#balance method into the delegate allowing other Account implementations of the Account interface to reuse this method. This makes a way to implement the PersistentAccount I have been thinking about, without so much repetition**
[5969b9075cd3495](https://github.com/ghacupha/book-keeper/commit/5969b9075cd3495) ghacupha *2018-04-01 13:53:33*
**created the AccountAppraisalDelegate and refactored the Account#balance method into the delegate allowing other Account implementations of the Account interface to reuse this method. This makes a way to implement the PersistentAccount I have been thinking about, without so much repetition**
[9768b159c1522a7](https://github.com/ghacupha/book-keeper/commit/9768b159c1522a7) ghacupha *2018-04-01 13:27:36*
**Made the SimpleAccount and the SimpleTransaction more thread-safe by adding volatile fields**
[64891fe42fdb467](https://github.com/ghacupha/book-keeper/commit/64891fe42fdb467) ghacupha *2018-04-01 12:33:21*
**Made the SimpleAccount and the SimpleTransaction more thread-safe by adding volatile fields**
[ad094fa9fe28690](https://github.com/ghacupha/book-keeper/commit/ad094fa9fe28690) ghacupha *2018-04-01 10:31:35*
**configured builds to ensure the commands are working**
[d6a3390ae8ade68](https://github.com/ghacupha/book-keeper/commit/d6a3390ae8ade68) Edwin Njeru *2018-03-29 16:51:41*
**removed deleted classes from the Exception classes' comments**
[cb712d5171910f4](https://github.com/ghacupha/book-keeper/commit/cb712d5171910f4) Edwin Njeru *2018-03-29 16:46:24*
**added currency parameter to SimpleTransaction**
[67cf8253b53bd26](https://github.com/ghacupha/book-keeper/commit/67cf8253b53bd26) Edwin Njeru *2018-03-29 16:34:05*
**added currency parameter to SimpleTransaction**
[a972b7f4334c5cd](https://github.com/ghacupha/book-keeper/commit/a972b7f4334c5cd) Edwin Njeru *2018-03-29 16:08:07*
**simplified account pattern to only implement directed accounting transaction pattern**
[bf67a14b0a76fd8](https://github.com/ghacupha/book-keeper/commit/bf67a14b0a76fd8) Edwin Njeru *2018-03-29 15:35:58*
**simplified account pattern to only implement directed accounting transaction pattern**
[adf6ba14643217b](https://github.com/ghacupha/book-keeper/commit/adf6ba14643217b) Edwin Njeru *2018-03-29 15:07:25*
**Used filtered streams to capture debits abd credits in the DirectedTransaction. Created more intuitive naming for Account implementation**
[08b8f29d9446f36](https://github.com/ghacupha/book-keeper/commit/08b8f29d9446f36) Edwin Njeru *2018-03-28 12:23:15*
**failed account-reversal test. To review later using spotbugs**
[09709770ed39efa](https://github.com/ghacupha/book-keeper/commit/09709770ed39efa) Edwin Njeru *2018-03-26 15:15:47*
**added configurations for maven reversing java version to 1.8_162 to resolve maven-integration issues**
[7674e3d3da5e389](https://github.com/ghacupha/book-keeper/commit/7674e3d3da5e389) Edwin Njeru *2018-03-26 13:22:58*
**release preparation**
[50481501be3c3c9](https://github.com/ghacupha/book-keeper/commit/50481501be3c3c9) ghacupha *2018-03-25 14:32:31*
**Amended bugs in the DirectedJournal and DirectedTrnsaction, enhanced exception messages and added test coverage**
[6618c8053f81b8f](https://github.com/ghacupha/book-keeper/commit/6618c8053f81b8f) ghacupha *2018-03-25 13:38:51*
**Amended bugs in the DirectedJournal and DirectedTrnsaction, enhanced exception messages and added test coverage**
[67f3f3dc3d7573f](https://github.com/ghacupha/book-keeper/commit/67f3f3dc3d7573f) ghacupha *2018-03-25 13:38:29*
**commited changes to Isolate DirectedJournal for unit testing**
[238ca4d6c09966c](https://github.com/ghacupha/book-keeper/commit/238ca4d6c09966c) Edwin Njeru *2018-03-23 17:44:23*
**created tests for the Directed Journal and the DirectedTransaction**
[b6180cad7513c7f](https://github.com/ghacupha/book-keeper/commit/b6180cad7513c7f) Edwin Njeru *2018-03-23 17:02:16*
**completed implementation of the DirectedJournal**
[61b72c6103b4e22](https://github.com/ghacupha/book-keeper/commit/61b72c6103b4e22) Edwin Njeru *2018-03-23 12:50:51*
**Created criteria to wrap journal side for Entry and Account**
[b19cd27824c2333](https://github.com/ghacupha/book-keeper/commit/b19cd27824c2333) Edwin Njeru *2018-03-22 06:53:19*
**Added classes to supprt Journalized entry workflows**
[7581789936350ac](https://github.com/ghacupha/book-keeper/commit/7581789936350ac) Edwin Njeru *2018-03-21 16:07:29*
**Migrated the first parameer used in Entry interface from AccountImpl to Account**
[9c14d636aaaf61e](https://github.com/ghacupha/book-keeper/commit/9c14d636aaaf61e) Edwin Njeru *2018-03-21 15:22:37*
**automated changelogs**
[3987b5da26a76ce](https://github.com/ghacupha/book-keeper/commit/3987b5da26a76ce) Edwin Njeru *2018-03-21 14:24:26*
## 1.2-SNAPSHOT
### No issue
**fixed group-import in the mismatchedCurrencyException**
[8fe2893499389e4](https://github.com/ghacupha/book-keeper/commit/8fe2893499389e4) Edwin Njeru *2018-03-21 13:43:54*
**merged local branches with master**
[a8053eebad48705](https://github.com/ghacupha/book-keeper/commit/a8053eebad48705) Edwin Njeru *2018-03-21 13:34:03*
**merging changes from new-pom**
[967382b75f9236c](https://github.com/ghacupha/book-keeper/commit/967382b75f9236c) Edwin Njeru *2018-03-21 13:16:43*
**reconfiguration of the project object model**
[89ba7c8106eb68d](https://github.com/ghacupha/book-keeper/commit/89ba7c8106eb68d) Edwin Njeru *2018-03-21 12:29:59*
**added missing module**
[eee13eb5552c496](https://github.com/ghacupha/book-keeper/commit/eee13eb5552c496) Edwin Njeru *2018-03-21 11:55:33*
**added missing files**
[edd8db658c121ca](https://github.com/ghacupha/book-keeper/commit/edd8db658c121ca) Edwin Njeru *2018-03-21 08:10:59*
**rearranging files for proper java9 exports**
[0e1d1d6c76e1dab](https://github.com/ghacupha/book-keeper/commit/0e1d1d6c76e1dab) Edwin Njeru *2018-03-21 06:27:26*
**Added AccountingTransaction and Transaction**
[ad154d7768ccedd](https://github.com/ghacupha/book-keeper/commit/ad154d7768ccedd) Edwin Njeru *2018-03-20 16:20:55*
**created AccountAttributes interface**
[d88312bfc413d05](https://github.com/ghacupha/book-keeper/commit/d88312bfc413d05) Edwin Njeru *2018-03-20 12:45:50*
**minor amendments to the tests**
[7b010cdaeaf4d37](https://github.com/ghacupha/book-keeper/commit/7b010cdaeaf4d37) Edwin Njeru *2018-03-20 11:55:36*
**used maven instead of the wrapper for the CI**
[4cfb6977d5c1385](https://github.com/ghacupha/book-keeper/commit/4cfb6977d5c1385) Edwin Njeru *2018-03-20 11:31:32*
**fixed failing CI tests**
[513ba96d8286270](https://github.com/ghacupha/book-keeper/commit/513ba96d8286270) Edwin Njeru *2018-03-20 11:24:37*
**Fixed checkstyle issues**
[bef8647d2326d72](https://github.com/ghacupha/book-keeper/commit/bef8647d2326d72) Edwin Njeru *2018-03-20 10:54:29*
**added cash as interface for monetary representation and removed unused dependencies**
[769ebfac3fce399](https://github.com/ghacupha/book-keeper/commit/769ebfac3fce399) Edwin Njeru *2018-03-20 07:05:06*
**final maven workflows configurations**
[14b44114cd608d5](https://github.com/ghacupha/book-keeper/commit/14b44114cd608d5) Edwin Njeru *2018-03-19 15:52:38*
**amended errors in the CI config**
[10f5f7bf571459b](https://github.com/ghacupha/book-keeper/commit/10f5f7bf571459b) Edwin Njeru *2018-03-19 13:37:30*
**amended errors in the CI config**
[182e061106ddb58](https://github.com/ghacupha/book-keeper/commit/182e061106ddb58) Edwin Njeru *2018-03-19 11:37:22*
**additional configs for deployment**
[ee7395191af8f81](https://github.com/ghacupha/book-keeper/commit/ee7395191af8f81) Edwin Njeru *2018-03-19 11:30:16*
**additional project configurations settings**
[1f515e6c248cc2d](https://github.com/ghacupha/book-keeper/commit/1f515e6c248cc2d) Edwin Njeru *2018-03-19 10:40:07*
**added maven-versions-plugin**
[9087a845a4396f3](https://github.com/ghacupha/book-keeper/commit/9087a845a4396f3) Edwin Njeru *2018-03-19 09:32:44*
**additional release configs and downloading missing plugins**
[1d1d9248c364276](https://github.com/ghacupha/book-keeper/commit/1d1d9248c364276) Edwin Njeru *2018-03-19 09:07:42*
**additional release configs and downloading missing plugins**
[1b9d4bd677290f3](https://github.com/ghacupha/book-keeper/commit/1b9d4bd677290f3) Edwin Njeru *2018-03-19 08:59:11*
**additional release configs and downloading missing plugins**
[88d33516547e3ee](https://github.com/ghacupha/book-keeper/commit/88d33516547e3ee) Edwin Njeru *2018-03-19 08:55:35*
**downloaded missing maven plugins from maven central**
[dd8fbf9ea9efa3f](https://github.com/ghacupha/book-keeper/commit/dd8fbf9ea9efa3f) Edwin Njeru *2018-03-19 08:43:40*
**release preparations**
[29dd05c93ef51c3](https://github.com/ghacupha/book-keeper/commit/29dd05c93ef51c3) Edwin Njeru *2018-03-19 07:40:24*
**amended illustration in the readme file**
[c366bc1cdb1e91f](https://github.com/ghacupha/book-keeper/commit/c366bc1cdb1e91f) ghacupha *2018-03-18 09:02:18*
**amended wrong type in the account**
[9f80fed5aabbb7d](https://github.com/ghacupha/book-keeper/commit/9f80fed5aabbb7d) ghacupha *2018-03-18 08:58:38*
**added tests for the account**
[23bbdf320d952d3](https://github.com/ghacupha/book-keeper/commit/23bbdf320d952d3) ghacupha *2018-03-18 08:57:42*
**moved packages for Time and Money into the unit package**
[91bff1c6d8a7e6d](https://github.com/ghacupha/book-keeper/commit/91bff1c6d8a7e6d) ghacupha *2018-03-18 08:43:48*
**added ExtendedMoney class**
[b8318df90f88599](https://github.com/ghacupha/book-keeper/commit/b8318df90f88599) ghacupha *2018-03-18 08:39:21*
**rearranged the directory structure for release**
[36875f73710a416](https://github.com/ghacupha/book-keeper/commit/36875f73710a416) Edwin Njeru *2018-03-16 17:53:09*
**Create README.md**
[23c617b221449ff](https://github.com/ghacupha/book-keeper/commit/23c617b221449ff) Edwin Njeru *2018-03-16 15:06:30*
**add license**
[8739a2efbbaa3ce](https://github.com/ghacupha/book-keeper/commit/8739a2efbbaa3ce) Edwin Njeru *2018-03-16 15:00:40*
| 36.210526 | 293 | 0.785783 | eng_Latn | 0.3669 |
9ada64608af969b611b48e8d765eccdd4abd4d01 | 411 | md | Markdown | _posts/2017-04-15-tsfw-that-smug-feeling-when-you-can-properly.md | lildude/colinseymour.co.uk | b4db947b165d7b5797c9841e97f5637e32c95ce8 | [
"MIT"
] | 1 | 2021-01-10T18:20:22.000Z | 2021-01-10T18:20:22.000Z | _posts/2017-04-15-tsfw-that-smug-feeling-when-you-can-properly.md | lildude/colinseymour.co.uk | b4db947b165d7b5797c9841e97f5637e32c95ce8 | [
"MIT"
] | 2 | 2017-11-18T19:13:58.000Z | 2020-04-26T17:36:50.000Z | _posts/2017-04-15-tsfw-that-smug-feeling-when-you-can-properly.md | lildude/colinseymour.co.uk | b4db947b165d7b5797c9841e97f5637e32c95ce8 | [
"MIT"
] | 1 | 2022-02-01T01:59:52.000Z | 2022-02-01T01:59:52.000Z | ---
layout: photo
date: 2017-04-15 17:14:37 +0000
title: "TSFW (that smug feeling when) you can properly…"
type: post
tags:
- instagram
instagram_url: https://www.instagram.com/p/BS6fvPol9dY/
---
{:class="instagram"}
TSFW (that smug feeling when) you can properly pronounce the name of a wine in the UK. Who'd have thought Afrikaans would be useful outside 🇿🇦?
| 29.357143 | 143 | 0.737226 | eng_Latn | 0.955774 |
9ada7f81711f8de3a7241f8d60745a234ec7b339 | 2,791 | md | Markdown | documents/configuration/macOS_Android.md | gustavosinbandera1/locha-mesh-chat | 0311ef097c733cd1fc3a1ddf116b50fad546fcc5 | [
"Apache-2.0"
] | 31 | 2019-11-24T10:39:35.000Z | 2022-03-07T05:45:38.000Z | documents/configuration/macOS_Android.md | gustavosinbandera1/locha-mesh-chat | 0311ef097c733cd1fc3a1ddf116b50fad546fcc5 | [
"Apache-2.0"
] | 112 | 2019-11-09T15:15:30.000Z | 2022-03-24T11:01:07.000Z | documents/configuration/macOS_Android.md | xkevin190/locha-mesh-chat | 551aaa66d8a604f5534004b508dc06fd958a55dd | [
"Apache-2.0"
] | 17 | 2019-11-24T10:39:42.000Z | 2022-01-07T06:12:24.000Z | <img src="files/logo.png" width="20%">
## Using macOS to compile Locha Mesh Chat for Android devices
### 1. Install Android Studio
- Download and install [Android Studio](https://developer.android.com/studio/index.html)
When prompted for the instalation type, select _Custom_ and make sure the next components will be installed:
- Android SDK
- Android SDK Platform
- Performance (Intel ® HAXM) [(See for AMD)](https://android-developers.googleblog.com/2018/07/android-emulator-amd-processor-hyper-v.html)
- Android Virtual Device
### 2. Install the Android SDK
The android sdk manager can be accessed via the Welcome window
- Click on `Configure` > `SDK Manager`
<img src="files/SDK_selection.png" width="75%"/>
- Select the package for the platform that you want to install, Locha Mesh Chat is intended to be used on affordable mobile devices, and can be installed in Android KitKat 4.4, it also can be installed in the latest Android versions.
In the tab SDK manager. e.g. select `Android 4.4 (KitKat)`-`API Level: 19` and click `Apply`.
The SDK and related tools will be downloaded, when it finishes click `OK`.
<img src="files/API_selection.png" width="75%"/>
### 3. Configure the ANDROID_HOME environment variable
We need to add the next environment variables to your `$HOME/.bash_profile` or `$HOME/.bashrc` config file:
```bash
export ANDROID_HOME=$HOME/Library/Android/sdk
export PATH=$PATH:$ANDROID_HOME/emulator
export PATH=$PATH:$ANDROID_HOME/tools
export PATH=$PATH:$ANDROID_HOME/tools/bin
export PATH=$PATH:$ANDROID_HOME/platform-tools
```
### 4. Run the Locha Mesh Chat application.
You can run the application in the android emulator or in your mobile phone.
#### Use your mobile phone
You can use your physical device plugging it to your computer using a USB cable and following the [next steps](https://facebook.github.io/react-native/docs/next/running-on-device)
#### Use a virtual device
If you don't have any virtual device yet you need to create almost one following the [next steps](https://developer.android.com/studio/run/managing-avds.html)
___
Now, inside the locha-mesh-chat folder we can run the application:
```bash
react-native run-android
```
That's all :wink:
___
Copyright (c) 2019 Bitcoin Venezuela and Locha Mesh developers.
Licensed under the **Apache License, Version 2.0**
**A text quote is shown below**
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
___
Read the full text:
[Locha Mesh Apache License 2.0](https://github.com/btcven/LochaMesh-Chat/blob/master/LICENSE) | 38.763889 | 234 | 0.767467 | eng_Latn | 0.926752 |
9adae3fd635d6fe6e98612e17270536d889d480c | 438 | md | Markdown | 影视/流浪地球组曲/README.md | hsdllcw/everyonepiano-music-database | d440544ad31131421c1f6b5df0f039974521eb8d | [
"MIT"
] | 17 | 2020-12-01T05:27:50.000Z | 2022-03-28T05:03:34.000Z | 影视/流浪地球组曲/README.md | hsdllcw/everyonepiano-music-database | d440544ad31131421c1f6b5df0f039974521eb8d | [
"MIT"
] | null | null | null | 影视/流浪地球组曲/README.md | hsdllcw/everyonepiano-music-database | d440544ad31131421c1f6b5df0f039974521eb8d | [
"MIT"
] | 2 | 2021-08-24T08:58:58.000Z | 2022-02-08T08:22:52.000Z |
**流浪地球组曲双手简谱** 是网友提供的，由网友 **腾飞kelly** 制作，感谢腾飞kelly对EOP的支持！
_流浪地球组曲_
是2019年郭帆执导的电影《流浪地球》中的不同背景音乐。《流浪地球》剧情中的种种反套路设置，是对于末世危机面前人类命运共同体更为科学合理的设想，并做出了中国特色。山挡路了移走，海成灾了填掉，天破了补起来，愚公移山、精卫填海、女娲补天，这些融于中国人血脉中与天地抗争的豪情，与面对末世争生机、寻希望的电影主题异常合拍。影片凸显不惧牺牲的集体主义精神的饱和式救援。首先在于它掐中了观众痛点，成为中国科幻电影攀登世界先进水平的重要标志，满足了中国观众对国产科幻大片多年的期待。更重要的是，影片具有中国特色，是富有中国气质的独特创新。
这里我们提供 _流浪地球组曲钢琴谱_ ，大家可以免费下载学习。
同时，网站还为大家提供了《[流浪地球主题音乐](Music-10075-流浪地球主题音乐.html "流浪地球主题音乐")》的曲谱下载
| 36.5 | 263 | 0.849315 | yue_Hant | 0.649057 |
9adb46be82f25d692c499345d4283783b6cbcf41 | 6,753 | md | Markdown | CHANGELOG.md | davidcmoulton/thema | ef3ce5a45e0426e08dbe4680c986eb5ce0c41c6f | [
"Apache-2.0"
] | null | null | null | CHANGELOG.md | davidcmoulton/thema | ef3ce5a45e0426e08dbe4680c986eb5ce0c41c6f | [
"Apache-2.0"
] | null | null | null | CHANGELOG.md | davidcmoulton/thema | ef3ce5a45e0426e08dbe4680c986eb5ce0c41c6f | [
"Apache-2.0"
] | null | null | null | ## [1.5.6](https://github.com/stencila/thema/compare/v1.5.5...v1.5.6) (2019-10-11)
### Bug Fixes
* **Stencila:** Fix vertical spacing for nested lists after paragraphs ([2ef401a](https://github.com/stencila/thema/commit/2ef401a))
## [1.5.5](https://github.com/stencila/thema/compare/v1.5.4...v1.5.5) (2019-10-09)
### Bug Fixes
* **Examples:** Update Simple example with new component tag names ([e1b738e](https://github.com/stencila/thema/commit/e1b738e))
* **Stencila:** Fix short paragraphs being centre aligned ([236f1e7](https://github.com/stencila/thema/commit/236f1e7))
* **Stencila:** Reduce max-width of CodeChunk components ([5ee20b0](https://github.com/stencila/thema/commit/5ee20b0))
## [1.5.4](https://github.com/stencila/thema/compare/v1.5.3...v1.5.4) (2019-10-07)
### Bug Fixes
* **Pre:** Fix Safari bug with rendering Pre elements inside iFrames ([6b5c8b0](https://github.com/stencila/thema/commit/6b5c8b0))
## [1.5.3](https://github.com/stencila/thema/compare/v1.5.2...v1.5.3) (2019-10-07)
### Bug Fixes
* **Citations:** Handle race condition with formatReferences ([38c6386](https://github.com/stencila/thema/commit/38c6386))
* **CodeChunk:** Show x-scrollbars for overflowing codechunks ([5039d15](https://github.com/stencila/thema/commit/5039d15))
* **Common Styles:** Move description/abstract from themes to common.css ([b2eab4b](https://github.com/stencila/thema/commit/b2eab4b))
* **CreativeWork:** Don't add extraneous commas in reference authors ([3967e65](https://github.com/stencila/thema/commit/3967e65))
* **eLife:** Handle YAML frontmatter for authors, organizations, abstract ([375f54c](https://github.com/stencila/thema/commit/375f54c))
* **Nature:** Adjust theme to handle YAML frontmatter + CodeChunks ([802cfcf](https://github.com/stencila/thema/commit/802cfcf))
* **Themes:** Refinements for eLife, Nature, PLOS themes ([80dac6d](https://github.com/stencila/thema/commit/80dac6d))
* **Themes:** Use semantic selectors, comment setTimeout usage ([9b2da0c](https://github.com/stencila/thema/commit/9b2da0c))
## [1.5.2](https://github.com/stencila/thema/compare/v1.5.1...v1.5.2) (2019-09-29)
### Bug Fixes
* **Selectors:** Fix custom selectors ([7bd1398](https://github.com/stencila/thema/commit/7bd1398))
* **Selectors:** Rename code-chunk to CodeChunk ([70e669f](https://github.com/stencila/thema/commit/70e669f))
## [1.5.1](https://github.com/stencila/thema/compare/v1.5.0...v1.5.1) (2019-09-12)
### Bug Fixes
* **Demo:** Reflect active theme/article in dropdown when reloading ([8e050b9](https://github.com/stencila/thema/commit/8e050b9))
* **JS:** Initalize JS even if script is loaded after DOMContentLoaded ([7639b4b](https://github.com/stencila/thema/commit/7639b4b))
* **Stencila:** Add common theme dependencies ([4c856bd](https://github.com/stencila/thema/commit/4c856bd))
# [1.5.0](https://github.com/stencila/thema/compare/v1.4.3...v1.5.0) (2019-09-12)
### Features
* Add & refine styles for CodeChunk component ([14b2f19](https://github.com/stencila/thema/commit/14b2f19))
## [1.4.3](https://github.com/stencila/thema/compare/v1.4.2...v1.4.3) (2019-09-10)
### Bug Fixes
* **Build:** Refactor TS modules and fix build task ([4f0815b](https://github.com/stencila/thema/commit/4f0815b))
## [1.4.2](https://github.com/stencila/thema/compare/v1.4.1...v1.4.2) (2019-09-10)
### Bug Fixes
* Fix selectors used in references for chnages in Encoda ([854f427](https://github.com/stencila/thema/commit/854f427))
* Use headline custom selector ([9864393](https://github.com/stencila/thema/commit/9864393))
* **Selectors:** Update selectors ([50c14a9](https://github.com/stencila/thema/commit/50c14a9))
* **Stencila theme:** Ensure init function ([602550a](https://github.com/stencila/thema/commit/602550a))
## [1.4.1](https://github.com/stencila/thema/compare/v1.4.0...v1.4.1) (2019-08-30)
### Bug Fixes
* **TypeScript:** Fix getTheme function logic ([39652d6](https://github.com/stencila/thema/commit/39652d6))
# [1.4.0](https://github.com/stencila/thema/compare/v1.3.0...v1.4.0) (2019-08-30)
### Features
* **TypeScript:** Generate TS declarations & export theme names ([be71bd0](https://github.com/stencila/thema/commit/be71bd0))
# [1.3.0](https://github.com/stencila/thema/compare/v1.2.0...v1.3.0) (2019-08-30)
### Bug Fixes
* **Demos:** Clean up demos, move script from .html to .ts ([446794e](https://github.com/stencila/thema/commit/446794e))
* **ELife:** Update markup based on microdata discussion ([dd2e11e](https://github.com/stencila/thema/commit/dd2e11e))
* **ELife Theme:** Add theme switcher ([51b5c49](https://github.com/stencila/thema/commit/51b5c49))
* **ELife Theme:** Fix regressions with `converted-article.html` ([ea0ca02](https://github.com/stencila/thema/commit/ea0ca02))
* **ELife Theme:** Render citations in eLife theme by default ([fed4c61](https://github.com/stencila/thema/commit/fed4c61))
* **Nature Theme:** Tweaks to Nature theme markup and styles ([cea4860](https://github.com/stencila/thema/commit/cea4860))
* **PLoS theme:** Tweaks to table, references, and markup ([184ede6](https://github.com/stencila/thema/commit/184ede6))
* **PLoS theme:** Update references style + table markup ([136b4f3](https://github.com/stencila/thema/commit/136b4f3))
* **Reference Styles:** Fix regressions in Nature theme ([2cc7861](https://github.com/stencila/thema/commit/2cc7861))
* **References, eLife:** Add MLA, APA citations to references.html ([806a1f3](https://github.com/stencila/thema/commit/806a1f3))
* **Styles:** Clean up eLife and Nature styles ([903d86a](https://github.com/stencila/thema/commit/903d86a))
* **Themes:** Clean up common styles, eLife, Nature, Plos, Stencila themes ([3ac0897](https://github.com/stencila/thema/commit/3ac0897))
* **Update Demos:** Update HTML encoded example (converted-article.html) ([3c56e0a](https://github.com/stencila/thema/commit/3c56e0a))
### Features
* **Microdata:** Use microdata-based CSS selectors for references. ([a7b690d](https://github.com/stencila/thema/commit/a7b690d))
* **PLoS Theme:** Add PLoS WIP theme ([c4819f9](https://github.com/stencila/thema/commit/c4819f9))
# [1.2.0](https://github.com/stencila/thema/compare/v1.1.0...v1.2.0) (2019-07-24)
### Bug Fixes
* **Build:** Simplify build command and fix output directory structure ([c0793bf](https://github.com/stencila/thema/commit/c0793bf))
* **Stencila Theme:** Refine some spacing and layouts ([97c12b9](https://github.com/stencila/thema/commit/97c12b9))
* **Syntax Highlighting:** Fix syntax highlighting for JSON code blocks ([57cd42a](https://github.com/stencila/thema/commit/57cd42a))
### Features
* **Stencila Theme:** Refactor styles to be mobile first ([bf9336d](https://github.com/stencila/thema/commit/bf9336d))
| 51.549618 | 136 | 0.723086 | yue_Hant | 0.453317 |
9adb5c02e06d9a0f687c1e518220eea7e7e3e4d4 | 72 | md | Markdown | Robot/Run.md | Microshak/Micronotes_MS | 6efb864f4bbfae2a04205c686c4df044f45869df | [
"Apache-2.0"
] | null | null | null | Robot/Run.md | Microshak/Micronotes_MS | 6efb864f4bbfae2a04205c686c4df044f45869df | [
"Apache-2.0"
] | null | null | null | Robot/Run.md | Microshak/Micronotes_MS | 6efb864f4bbfae2a04205c686c4df044f45869df | [
"Apache-2.0"
] | null | null | null | . ~/catkin_ws/devel/setup.bash
roscore
. ~/catkin_ws/devel/setup.bash
| 12 | 30 | 0.736111 | eng_Latn | 0.267385 |
9adc2c34e68f06182389cac91d36a1cc31b56387 | 104 | md | Markdown | README.md | sergeplatonov/Prototypio | d1991bfe299d18b4462785347f1a7dfb49fd507f | [
"Apache-2.0"
] | null | null | null | README.md | sergeplatonov/Prototypio | d1991bfe299d18b4462785347f1a7dfb49fd507f | [
"Apache-2.0"
] | null | null | null | README.md | sergeplatonov/Prototypio | d1991bfe299d18b4462785347f1a7dfb49fd507f | [
"Apache-2.0"
] | null | null | null | # Prototypio
An example Android/iOS App that uses gRPC to communicate with Backend and Kivy as frontend
| 34.666667 | 90 | 0.817308 | eng_Latn | 0.991281 |
9adc45588560b30b225abd384ffccffe57463967 | 521 | md | Markdown | README.md | phaus/pleasure | 02856830b3c5993c22b559c7ede5ac74ce6498f8 | [
"Apache-2.0"
] | 8 | 2016-10-15T19:58:04.000Z | 2017-12-04T17:29:46.000Z | README.md | pedrohidalgo/pleasure | 02856830b3c5993c22b559c7ede5ac74ce6498f8 | [
"Apache-2.0"
] | 7 | 2016-10-15T17:25:10.000Z | 2017-09-25T22:07:26.000Z | README.md | phaus/pleasure | 02856830b3c5993c22b559c7ede5ac74ce6498f8 | [
"Apache-2.0"
] | 4 | 2017-03-31T21:45:28.000Z | 2018-10-02T07:36:47.000Z | Create, run, debug and test your app directly in the IDE
===
Support both Java and Scala.
Test single files, activator templates integrated, customize your commands, etc. No Command line needed at all.
<h5>Motivates this work with <a href="https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=7FUCWX98NEUAL">
<img src="https://www.paypalobjects.com/en_US/i/btn/btn_donate_SM.gif" alt="btn_donate_SM.gif"></a></h5>
<h5>Pull Requests and bug reports, feature/enhancement requests are very welcome!</h5> | 52.1 | 122 | 0.769674 | eng_Latn | 0.829331 |
9adcb01ca5aeba688897a44e503e6bc86e21677f | 5,430 | markdown | Markdown | _posts/2019-07-05-recursive-vim-macros-on-multiple-files-using-arglist.markdown | brainlessdeveloper/brainlessdeveloper | 93fd2ad06d31b0da821ffc8f06ef5402549d2ae4 | [
"MIT"
] | 1 | 2022-01-10T12:21:26.000Z | 2022-01-10T12:21:26.000Z | _posts/2019-07-05-recursive-vim-macros-on-multiple-files-using-arglist.markdown | brainlessdeveloper/brainlessdeveloper | 93fd2ad06d31b0da821ffc8f06ef5402549d2ae4 | [
"MIT"
] | 2 | 2021-02-05T22:31:38.000Z | 2021-12-28T20:54:30.000Z | _posts/2019-07-05-recursive-vim-macros-on-multiple-files-using-arglist.markdown | brainlessdeveloper/brainlessdeveloper.github.io | 93fd2ad06d31b0da821ffc8f06ef5402549d2ae4 | [
"MIT"
] | 3 | 2020-06-25T19:30:34.000Z | 2021-09-04T05:59:32.000Z | ---
layout: post
title: 'Recursive vim macros on multiple files using arglist'
comments: true
date: 2019-07-05 11:10:00 +0200
excerpt: 'I use vim macros to implement a repeated code change in a relatively big codebase. I learn of a way to apply macros that exhaust occurrences in one file across multiple files using only vim.'
---
For readers in a hurry:
```bash
qq
# Record your macro and make it exhaust all instances in a file by making it recursive
q
# This populates the argument list
:args `grep -lr 'match lines in the files you are interested in'`
# This runs your macro on each file in the argument list
:argdo norm @q
# This saves all open buffers
:wa
```
---
Yesterday I learned some useful things about vim. I had this:
```typescript
import styles = require('./styles.scss')
import colors = require('./colors.json')
```
And my goal was to turn it into ES6 imports:
```typescript
import styles from './styles.scss'
import colors from './colors.json'
```
Why we used the initial syntax has to do with Webpack and TypeScript, but that's for another post.
```diff
- import styles = require('./styles.scss')
+ import styles from './styles.scss'
- import colors = require('./colors.json')
+ import colors from './colors.json'
```
I thought it wouldn't be too terrible to do it manually with a vim macro, so I went ahead and made one that works on a line. Started recording with `qq`:
```vim
0f=ct(from<Esc>lds(i<Space><Esc>0
```
And stopped recording with `q`. That's very sloppy but it's my daily reality. Here's a breakdown:
- `0`: go to the start of the line.
- `f=`: move the cursor to where the next `=` is.
- `ct(from`: change until the next `(` and insert "from".
- `<Esc>lds(`: change to normal mode, move the cursor to where the next `(` is, and delete the surrounding parentheses.
- `i<Space><Esc>`: insert a space and go back to normal mode.
- `0`: go back to the start of the line. I think this helps me navigating after using a macro.
After the second or third file, I decided to assess the task better. I wanted a list of files with lines matching `import.*= require`, so `grep` seemed like an obvious choice. It could have been The Silver Searcher or ripgrep as well.
```bash
man grep
```
```
-l, --files-with-matches
Suppress normal output; instead print the name of each input file from
which output would normally have been printed. The scanning will stop on
the first match.
-r, --recursive
Read all files under each directory, recursively, following symbolic links
only if they are on the command line. Note that if no file operand is
given, grep searches the working directory. This is equivalent to the -d
recurse option.
```
Perfect!
```bash
grep -lr 'import.*= require' app
```
Around two hundred files used that, and some had three or four matching lines. Some solutions came to mind:
- Use something similar to `codemod`, or `jscodeshift` but for TypeScript.
- Use `sed` in "edit in-place" mode with a regular expression with capture groups.
- Bite the bullet and just go ahead using my macro on every line.
But I was feeling adventurous so I decided to find out if I could apply a macro on all the files that matched. After all, I already had that list of files (the result of the previous `grep`) and I had a macro that worked on one line. This looked like a great learning opportunity.
## Making a macro recursive
This is the idea I tried to follow: first I would search for a matches of my pattern using `/`. Then, I needed to apply the previous macro I created, and move on to the next occurrence from my `/` search until vim returned an error code because there are no more matches, in which case the macro would stop calling itself.
First, I did a search on the buffer:
```vim
/import.*= require<Enter>
```
And then I recorded the same macro I had before on `q`:
```vim
n0f=ct(from<Esc>lds(i<Space><Esc>0@q
```
But with two changes. The new one first finds the next search result with `n`. If this fails because there are no more results, the macro stops. After applying the macro, it calls itself with `@q`.
And that's it! I tried it on one file and was very happy to see my imports modernize for me.
## Using a macro on a list of files
All documentation snippets here are taken from `:help arglist`.
```
The argument list
If you give more than one file name when starting Vim, this list is remembered
as the argument list. You can jump to each file in this list.
```
The documentation had an answer to all my questions:
How can I add things to my argument list?
```
:ar :args
:ar[gs]
Print the argument list, with the current file in square brackets.
:ar[gs] [++opt] [+cmd] {arglist}
Define {arglist} as the new argument list and edit the first one.
```
How can I do things on files in the argument list?
```
:argdo :[range]argdo[!] {cmd}
Execute {cmd} for each file in the argument list or, if [range] is specified,
only for arguments in that range.
```
So that means `args` will return the current argument list and `args {arglist}` will set it. Here we go, then!
```bash
:args `grep -lr 'import.*= require' app`
:args # Huge list of files
:argdo norm @q
:wa # Save all affected buffers
```
It took a while for vim to do its thing. Was it the best way possible? Probably not. Was it a worthwhile experience, and did I learn? Definitely. Am I going to do this again? Yes! Next time I'll be faster and wiser.
| 33.518519 | 322 | 0.726519 | eng_Latn | 0.999202 |
9adcb2f7ebcb3e3680fcfffde914f464a71b4ba8 | 2,149 | md | Markdown | _articles/jp/builds/build-artifacts-online.md | BanyikAnna/devcenter-last-modified | 982d105096e896f7ef8fee1f7fbb1fa9a2e9efd7 | [
"MIT"
] | null | null | null | _articles/jp/builds/build-artifacts-online.md | BanyikAnna/devcenter-last-modified | 982d105096e896f7ef8fee1f7fbb1fa9a2e9efd7 | [
"MIT"
] | 2 | 2021-09-28T01:53:47.000Z | 2022-02-26T07:20:57.000Z | _articles/jp/builds/build-artifacts-online.md | BanyikAnna/devcenter-last-modified | 982d105096e896f7ef8fee1f7fbb1fa9a2e9efd7 | [
"MIT"
] | 1 | 2020-04-21T13:33:18.000Z | 2020-04-21T13:33:18.000Z | ---
published_at:
last_modified_at:
title: オンラインでのビルドアーティファクト
menu:
builds-main:
weight: 22
---
アプリのビルドを選択する場合、ビルドページの`APPS & Artifacts`タブにてビルド中に生成されたアーティファクト（例えば、ファイルやレポート）の確認が行なえます。すべてのファイルはビルド終了時点で破壊されるので、もしファイルを見たりダウンロードする場合、ワークフローへ`Deploy to bitrise.io`ステップを挿入すればアーティファクトへのアクセスが可能になります。
## アーティファクトへのファイルのデプロイ
`Deploy to Bitrise.io`ステップを使うことによりビルドページ内の`APPS & Artifacts`セクションへアーティファクトがデプロイされます。ビルド中に生成されたすべてのファイルをデプロイし、`$BITRISE_DEPLOY_DIR` ディレクトリへ保存されます。ステップの`Config`セクションの下にある`Deploy directory or file path` 欄内にあるターゲットディレクトリパスの変更が可能です。
1. アーティファクトを生成するステップの後に`Deploy to Bitrise.io`を挿入するか、**ワークフローの一番最後**（推奨）に`Deploy to Bitrise.io`を挿入してください。詳しい情報は、[Attach any file as an Artifact to the Build](https://devcenter.bitrise.io/tips-and-tricks/attach-any-file-to-build/)を参照してください。
{% include message_box.html type="important" title=" `Deploy to Bitrise.io`の挿入場所" content=" My message" content=" 正しい場所に`Deploy to Bitrise.io`を追加してください。ビルド中にファイルを生成する他のステップの前に挿入してしまうと`Deploy to Bitrise.io`は何もデプロイしないのでご注意ください。 "%}
デプロイディレクトリ内にあるどのサブディレクトリの内容も、ビルドの`APPS and Artifacts`セクションには表示されないのでご注意ください。しかし、`Deploy to Bitrise.io`ステップにある`Compress the artifacts into one file`欄のデフォルト`false`値を`true`に修正すると、zipファイルに**アーティファクトを圧縮する**ことができます。これはサブディレクトリを含む全てのディレクトリを圧縮し、`APPS & Artifacts`にデプロイします。
### ターゲットディレクトリパスの修正
他のパスに**ターゲットディレクトリパスを修正する**ことができますが、ワークフローの他のステップ内の同じディレクトリパスを参照して、そのディレクトリに生成されたファイルが収集されていることを確認してください。
### ビルドが失敗したらアーティファクトを調べてください
`Run if previous Step failed`トグルが有効であると、ビルドが失敗しても、ビルドの（生成に成功した）アーティファクトへアクセスができます。例えば、生成されたテストレポートファイルをチェックして失敗したビルドのバグを検知することができます。
### ビルドのアーティファクトへは誰がアクセスできますか？
`APPS & Artifacts`のアーティファクトはアプリのオーナー、管理人、開発者、テスター・QAであれば誰でもアクセスできます。`Enable public page fot the App`のデフォルト構成を保つ場合、URLを持つ人なら誰でもアプリとアーティファクトにアクセスすることができます。詳しい情報は [Public App install page](https://devcenter.bitrise.io/tutorials/deploy/bitrise-app-deployment/#public-app-install-page)をご覧ください。
## ファイルの種類と制限
すべてのファイルの種類は`APPS & Artifacts`でサポートされており利用可能です。ファイルの種類にもよりますが、`eye`アイコンをクリックするかファイルをローカルコンピュータにダウンロードするとアーティファクトをオンラインで確認することもできます。
ビルド毎に`APPS & Artifacts`にデプロイされるファイルの数についての制限はありません。ただし、ファイルのサイズの制限については**ファイルごとに2GBまで**となっています。 | 56.552632 | 288 | 0.843648 | yue_Hant | 0.345031 |
9addde2d46f887788c7ea9afead1bf16eb16ee8d | 2,521 | md | Markdown | aspnetcore/client-side/libman/index.md | dmcory/Docs.es-es | 0f3889660822cf14c7cce4cadb13204643baf0fe | [
"CC-BY-4.0",
"MIT"
] | null | null | null | aspnetcore/client-side/libman/index.md | dmcory/Docs.es-es | 0f3889660822cf14c7cce4cadb13204643baf0fe | [
"CC-BY-4.0",
"MIT"
] | null | null | null | aspnetcore/client-side/libman/index.md | dmcory/Docs.es-es | 0f3889660822cf14c7cce4cadb13204643baf0fe | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Adquisición de bibliotecas del lado cliente en ASP.NET Core con LibMan
author: scottaddie
description: Obtenga información sobre cómo instalar los recursos de bibliotecas del lado cliente en un proyecto de ASP.NET Core mediante Library Manager (LibMan).
ms.author: scaddie
ms.custom: mvc
ms.date: 08/14/2018
uid: client-side/libman/index
ms.openlocfilehash: a6ff0cc3342cfac74739387aa17046ed5050232f
ms.sourcegitcommit: ecf2cd4e0613569025b28e12de3baa21d86d4258
ms.translationtype: HT
ms.contentlocale: es-ES
ms.lasthandoff: 08/30/2018
ms.locfileid: "43312364"
---
# <a name="client-side-library-acquisition-in-aspnet-core-with-libman"></a>Adquisición de bibliotecas del lado cliente en ASP.NET Core con LibMan
Por [Scott Addie](https://twitter.com/Scott_Addie)
Library Manager (LibMan) es una herramienta ligera para la adquisición de bibliotecas del lado cliente. Asimismo, LibMan permite descargar bibliotecas y marcos populares de sistemas de archivos o [redes de entrega de contenido (CDN)](https://wikipedia.org/wiki/Content_delivery_network). Entre las CDN admitidas se incluyen [CDNJS](https://cdnjs.com/) y [unpkg](https://unpkg.com/#/). Los archivos de biblioteca seleccionados se capturan y se colocan en la ubicación adecuada dentro del proyecto de ASP.NET Core.
## <a name="libman-use-cases"></a>Casos de uso de LibMan
LibMan ofrece las ventajas siguientes:
* Solo se descargan los archivos de biblioteca necesarios.
* No es necesario usar otras herramientas como [Node.js](https://nodejs.org), [npm](https://www.npmjs.com) o [WebPack](https://webpack.js.org) para adquirir un subconjunto de archivos de una biblioteca.
* Los archivos se pueden colocar en una ubicación específica sin tener que usar tareas de compilación ni copiar archivos manualmente.
Para obtener más información sobre las ventajas del LibMan, vea [Modern front-end web development in Visual Studio 2017: LibMan segment](https://channel9.msdn.com/Events/Build/2017/B8073#time=43m34s) (Desarrollo web front-end moderno en Visual Studio 2017: segmento LibMan).
LibMan no es un sistema de administración de paquetes. Si ya usa un administrador de paquetes, por ejemplo, npm o [yarn](https://yarnpkg.com), le recomendamos que sigua haciéndolo. LibMan no se ha desarrollado para reemplazar dichas herramientas.
## <a name="additional-resources"></a>Recursos adicionales
* <xref:client-side/libman/libman-vs>
* <xref:client-side/libman/libman-cli>
* [Repositorio de LibMan en GitHub](https://github.com/aspnet/LibraryManager)
| 64.641026 | 512 | 0.793336 | spa_Latn | 0.923311 |
9adde4c37cbc6f471d399fb6b33f8bbbe97a1297 | 345 | md | Markdown | _definitions/bld-araho.md | digitallawyer/openlegaldictionary | a318d6c73c3d8e33756d947add397dac7f25cca2 | [
"MIT"
] | 5 | 2018-08-07T21:57:01.000Z | 2022-02-26T13:29:20.000Z | _definitions/bld-araho.md | digitallawyer/openlegaldictionary | a318d6c73c3d8e33756d947add397dac7f25cca2 | [
"MIT"
] | 1 | 2018-08-07T22:29:07.000Z | 2018-08-07T22:45:46.000Z | _definitions/bld-araho.md | digitallawyer/openlegaldictionary | a318d6c73c3d8e33756d947add397dac7f25cca2 | [
"MIT"
] | 2 | 2020-12-26T17:22:04.000Z | 2021-02-12T21:35:50.000Z | ---
title: Araho
letter: A
permalink: "/definitions/bld-araho.html"
body: In feudal law. To make oath in the church or some other holy place. All oaths
were made in the church upon the rel-ics of saints, according to the Ripuarian laws.
Cowell; Spelman
published_at: '2018-07-07'
source: Black's Law Dictionary 2nd Ed (1910)
layout: post
--- | 31.363636 | 86 | 0.744928 | eng_Latn | 0.991985 |
9adebf60c9b848c1920df20b912aca5ca17159d5 | 138 | md | Markdown | README.md | ChrisPolewiak/AzureWorkshop | f83cba2b1d12782f50eac715fe268de1f82211cd | [
"MIT"
] | null | null | null | README.md | ChrisPolewiak/AzureWorkshop | f83cba2b1d12782f50eac715fe268de1f82211cd | [
"MIT"
] | null | null | null | README.md | ChrisPolewiak/AzureWorkshop | f83cba2b1d12782f50eac715fe268de1f82211cd | [
"MIT"
] | null | null | null | # AzureWorkshop
Azure Workshop Materials
Direct link to Office Word document
https://1drv.ms/w/s!Agvg9jknV8E8rsRkc63KDJsbHk8P8A?e=UsSxs8
| 23 | 59 | 0.833333 | yue_Hant | 0.63336 |
9ae148e7bb292bbe893d61fe7187ab7d864840c4 | 12,185 | md | Markdown | memdocs/configmgr/core/servers/deploy/configure/monitor-content-you-have-distributed.md | Mdlglobal-atlassian-net/memdocs.pt-pt | 5ee72251572da436f8c758346a3505f167a85c9a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | memdocs/configmgr/core/servers/deploy/configure/monitor-content-you-have-distributed.md | Mdlglobal-atlassian-net/memdocs.pt-pt | 5ee72251572da436f8c758346a3505f167a85c9a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | memdocs/configmgr/core/servers/deploy/configure/monitor-content-you-have-distributed.md | Mdlglobal-atlassian-net/memdocs.pt-pt | 5ee72251572da436f8c758346a3505f167a85c9a | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-05-28T15:46:01.000Z | 2020-05-28T15:46:01.000Z | ---
title: Monitorizar conteúdo
titleSuffix: Configuration Manager
description: Compreenda como monitorizar os conteúdos distribuídos utilizando a consola 'Gestor de Configuração'.
ms.date: 07/26/2019
ms.prod: configuration-manager
ms.technology: configmgr-core
ms.topic: conceptual
ms.assetid: 82e8a693-9adf-4ca3-8484-7e101c34c7c1
author: aczechowski
ms.author: aaroncz
manager: dougeby
ms.openlocfilehash: fafcbffe3231af78ae3a079061accc9f112a181c
ms.sourcegitcommit: 2cafbba6073edca555594deb99ae29e79cd0bc79
ms.translationtype: MT
ms.contentlocale: pt-PT
ms.lasthandoff: 04/24/2020
ms.locfileid: "82110020"
---
# <a name="monitor-content-you-distribute-with-configuration-manager"></a>Monitorize o conteúdo que distribui com o Gestor de Configuração
*Aplica-se a: Gestor de Configuração (ramo atual)*
Utilize a consola 'Gestor de Configuração' para monitorizar os conteúdos distribuídos, incluindo:
- O estado de todos os tipos de pacotes para os pontos de distribuição associados.
- O estado de validação do conteúdo do conteúdo num pacote.
- O estado dos conteúdos atribuídos a um grupo específico de pontos de distribuição.
- O estado de conteúdo atribuído a um ponto de distribuição.
- O estado das funcionalidades opcionais para cada ponto de distribuição (validação de conteúdos, PXE e multicast).
> [!NOTE]
> O Gestor de Configuração apenas monitoriza o conteúdo num ponto de distribuição que está na biblioteca de conteúdos. Não monitoriza os conteúdos armazenados no ponto de distribuição em pacotes ou ações personalizadas.
## <a name="content-status-monitoring"></a><a name="BKMK_ContentStatus"></a>Monitorização do estado do conteúdo
O nó **Estado do Conteúdo** da área de trabalho **Monitorização** disponibiliza informações sobre pacotes de conteúdos. Na consola Do Gestor de Configuração, reveja informações como:
- Nome, tipo e ID do pacote
- Quantos pontos de distribuição um pacote foi enviado para
- Taxa de conformidade
- Quando o pacote foi criado
- Versão fonte
Também encontra informações detalhadas sobre o estado de qualquer pacote, incluindo:
- Estado de distribuição
- O número de falhas
- Distribuição pendente
- O número de instalações
Também pode gerir distribuições que permanecem em curso até um ponto de distribuição, ou que não conseguiram distribuir conteúdo com sucesso para um ponto de distribuição:
- A opção de cancelar ou redistribuir conteúdo está disponível quando visualiza a mensagem de estado de implementação de um trabalho de distribuição para um ponto de distribuição no painel de Detalhes do **Ativo.** Este painel pode ser encontrado no separador **In Progress** ou no separador **Error** do nó de **Status Status.**
- Além disso, os detalhes do trabalho mostram a percentagem do trabalho que completou quando vê os detalhes de um trabalho no separador **In Progress.** Os detalhes do trabalho também mostram o número de repetições que permanecem para um trabalho. Quando vê os detalhes de um trabalho no separador **Error,** mostra quanto tempo até que ocorra o próximo novo retry.
Quando cancela uma implementação que ainda não esteja concluída, o trabalho de distribuição para transferir esse conteúdo para:
- O estado da implementação atualiza-se então para indicar que a distribuição falhou e que foi cancelada por uma ação do utilizador.
- Este novo estado aparece no separador **Error.**
> [!NOTE]
> Quando uma implementação está quase concluída, é possível que a ação para cancelar essa distribuição não seja processada antes da distribuição para o ponto de distribuição estar concluída. Quando isto ocorre, a ação de cancelamento da implantação é ignorada e o estado dos ecrãs de implantação é bem sucedido.
>
> Embora possa selecionar a opção de cancelar uma distribuição para um ponto de distribuição que está localizado num servidor de site, isso não tem qualquer efeito. Este comportamento deve-se ao facto de o servidor do site e o ponto de distribuição num servidor de site partilharem a mesma loja de conteúdos de instância única. Não há nenhum trabalho de distribuição para cancelar.
Quando redistribui conteúdo que anteriormente não foi transferido para um ponto de distribuição, o Gestor de Configuração começa imediatamente a reimplantar esse conteúdo para o ponto de distribuição. O Gestor de Configuração atualiza o estado da implementação para refletir o estado em curso dessa reimplantação.
### <a name="tasks-to-monitor-content"></a>Tarefas para monitorizar o conteúdo
1. Na consola 'Gestor de Configuração', vá ao espaço de trabalho **de monitorização,** expanda o Estado de **Distribuição**e, em seguida, selecione o nó de Status de **Conteúdo.** Este nó exibe as embalagens.
2. Selecione o pacote que pretende gerir.
3. No separador **Casa** da fita, no grupo **Conteúdo,** selecione **'Ver Status**. A consola apresenta informações detalhadas sobre o estado do pacote.
Continue a uma das seguintes secções para ações adicionais:
#### <a name="cancel-a-distribution-that-remains-in-progress"></a>Cancelar uma distribuição que continua em curso
1. Mude para o separador **In Progress.**
2. No painel de Detalhes do **Ativo,** clique à direita na entrada para a distribuição que pretende cancelar e selecione **Cancelar**.
3. Selecione **Sim** para confirmar a ação e cancelar o trabalho de distribuição para esse ponto de distribuição.
#### <a name="redistribute-content-that-failed-to-distribute"></a>Redistribuir conteúdo que não distribuiu
1. Mude para o separador **Error.**
2. No painel de Detalhes do **Ativo,** clique à direita na entrada para a distribuição que pretende redistribuir e selecione **Redistribuir**.
3. Selecione **Sim** para confirmar a ação e iniciar o processo de redistribuição nesse ponto de distribuição.
## <a name="distribution-point-group-status"></a> Estado do grupo de pontos de distribuição
O nó **Estado do Grupo de Pontos de Distribuição** na área de trabalho **Monitorização** fornece informações acerca dos grupos de pontos de distribuição. Pode rever informações como:
- O nome, descrição e estado do grupo de pontos de distribuição
- Quantos pontos de distribuição são membros do grupo de pontos de distribuição
- Quantos pacotes foram atribuídos ao grupo
- A taxa de conformidade
Também visualiza as seguintes informações detalhadas sobre o estado:
- Erros para o grupo de pontos de distribuição
- Quantas distribuições estão em andamento
- Quantos foram distribuídos com sucesso
### <a name="monitor-distribution-point-group-status"></a>Monitorizar o estado do grupo de pontos de distribuição
1. Na consola 'Gestor de Configuração', vá ao espaço de trabalho **de monitorização,** expanda o Estado de **Distribuição**e, em seguida, selecione o nó de Estado do Grupo de Ponto de **Distribuição.** Exibe os grupos de pontos de distribuição.
2. Selecione o grupo de pontos de distribuição para o qual pretende informações detalhadas sobre o estado.
3. No separador **Casa** da fita, selecione **'Ver Status**. Apresenta informações detalhadas sobre o estado do grupo de pontos de distribuição.
## <a name="distribution-point-configuration-status"></a>Estado da configuração do ponto de distribuição
O nó **Estado da Configuração do Ponto de Distribuição** na área de trabalho **Monitorização** fornece informações acerca do ponto de distribuição. Pode rever quais os atributos que estão habilitados para o ponto de distribuição, como o PXE, multicast, validação de conteúdos. Consulte também o estado de distribuição do ponto de distribuição.
> [!WARNING]
> O estado de configuração do ponto de distribuição é relativo às últimas 24 horas. Se o ponto de distribuição tiver um erro e recuperar, o estado de erro pode ser apresentado até 24 horas após a recuperação do ponto de distribuição.
### <a name="monitor-distribution-point-configuration-status"></a>Monitorizar o estado de configuração do ponto de distribuição
1. Na consola 'Gestor de Configuração', vá ao espaço de trabalho **de monitorização,** expanda o Estado de **Distribuição**e, em seguida, selecione o nó de configuração do ponto de **distribuição.**
2. Selecione um ponto de distribuição.
3. No painel de resultados, mude para o separador **Detalhes.** Exibe informações sobre o estado para o ponto de distribuição.
## <a name="client-data-sources-dashboard"></a>Painel de dados de dados do cliente
Utilize o dashboard **Fontes** de Dados do Cliente para entender melhor de onde os clientes obtêm conteúdo no seu ambiente. O dashboard começa a exibir dados depois de os clientes descarregarem conteúdo e reportarem essa informação de volta ao site. Este processo pode demorar até 24 horas.
> [!Note]
> O Gestor de Configuração não ativa esta funcionalidade opcional por padrão. Tem de ativar a função **De Cache de Pares do Cliente** antes de a utilizar. Para mais informações, consulte [Enable optional features from updates](../../manage/install-in-console-updates.md#bkmk_options).
Na consola Do Gestor de Configuração, vá ao espaço de trabalho **de Monitorização,** expanda o Estado de **Distribuição**e selecione o nó de Fontes de Dados do **Cliente.** Selecione um período de tempo para aplicar ao painel de instrumentos. Em seguida, selecione o grupo de limites para o qual pretende visualizar informações. Pode pairar sobre os azulejos do rato para ver mais detalhes sobre os diferentes conteúdos ou fontes políticas.
Utilize também o relatório, **Fontes**de Dados do Cliente - Resumo , para visualizar um resumo das fontes de dados do cliente para cada grupo de fronteiras.
### <a name="dashboard-tiles"></a>Os mosaicos do dashboard
O painel inclui os seguintes azulejos:
#### <a name="client-content-sources"></a>Fontes de Conteúdo do Cliente
Exibe as fontes a partir das quais os clientes obtiveram conteúdo:
- Ponto de distribuição
- [Ponto de distribuição em nuvem](../../../plan-design/hierarchy/use-a-cloud-based-distribution-point.md)
- [BranchCache](../../../plan-design/configs/support-for-windows-features-and-networks.md#bkmk_branchcache)
- [Peer Cache](../../../plan-design/hierarchy/client-peer-cache.md)
- [Otimização de Entrega](../../../plan-design/hierarchy/fundamental-concepts-for-content-management.md#delivery-optimization) (a partir da versão 1906)<sup>[Nota 1](#bkmk_note1)</sup>
- Microsoft Update: Os dispositivos reportam esta fonte quando o cliente do Gestor de Configuração descarrega atualizações de software a partir de serviços de nuvem da Microsoft. Estes serviços incluem microsoft update e Microsoft 365 Apps para empresa.
<a name="bkmk_note1"></a>
> [!Note]
> Começando na versão 1906<!--3555759-->, para incluir a Otimização de Entrega neste dashboard, faça as seguintes ações:
>
> - Configure a definição do cliente, Ative a **instalação de Atualizações Expressas em clientes** no grupo Deatualizações de Software
>
> - Implementar atualizações expressas do Windows 10
>
> Para mais informações, consulte os ficheiros de [instalação do Manage Express para atualizações do Windows 10](../../../../sum/deploy-use/manage-express-installation-files-for-windows-10-updates.md).
#### <a name="distribution-points"></a>Pontos de distribuição
Apresenta o número de pontos de distribuição que fazem parte do grupo de fronteira selecionado.
#### <a name="clients-that-used-a-distribution-point"></a>Clientes que usaram um ponto de distribuição
Do número de clientes que estão no grupo de fronteira selecionado, este azulejo mostra quantos usaram um ponto de distribuição para obter conteúdo.
#### <a name="peer-cache-sources"></a>Fontes de Cache peer
Para o grupo de fronteira selecionado, este azulejo mostra quantas fontes de cache de pares reportaram o histórico de descarregamento.
#### <a name="clients-that-used-a-peer"></a>Clientes que usaram um par
Do número de clientes que estão no grupo de fronteira selecionado, este azulejo mostra quantos usaram uma fonte de cache para obter conteúdo.
#### <a name="top-distributed-content"></a>Conteúdo distribuído de topo
Os pacotes mais distribuídos por tipo de origem
| 62.809278 | 440 | 0.779975 | por_Latn | 0.999915 |
9ae15411a9b11140a7ee8c1ae4ffa0c59c727e8b | 5,648 | md | Markdown | _hibahcme/080.md | hixio-mh/website-4 | 943b8ecdb1f7e507abbb404051afbd40d0a855d3 | [
"MIT"
] | 4 | 2018-03-23T08:55:53.000Z | 2018-03-24T15:10:22.000Z | _hibahcme/080.md | hixio-mh/website-4 | 943b8ecdb1f7e507abbb404051afbd40d0a855d3 | [
"MIT"
] | 3 | 2021-12-20T17:56:32.000Z | 2021-12-20T17:59:59.000Z | _hibahcme/080.md | hixio-mh/website-4 | 943b8ecdb1f7e507abbb404051afbd40d0a855d3 | [
"MIT"
] | 5 | 2020-01-01T09:54:05.000Z | 2021-11-23T15:49:11.000Z | ---
nomor: 80
nama: Larasati
foto:
filename: 0121bw.jpg
type: image/jpeg
size: 433494
url: >-
http://5c4cf848f6454dc02ec8-c49fe7e7355d384845270f4a7a0a7aa1.r53.cf2.rackcdn.com/582fa7c8-8e06-4db3-a0e3-742860663232/0121bw.jpg
seni: sastra
pengalaman: 4 tahun
website: www.kaleidoscopeofjavatour.com
sosmed: >-
youtube: Nawung Teaser Animation, Nawung Book Trailer, Facebook: Galuh
Larasati
file:
filename: COVER NOVEL3ok.jpg
type: image/jpeg
size: 1657814
url: >-
http://5c4cf848f6454dc02ec8-c49fe7e7355d384845270f4a7a0a7aa1.r53.cf2.rackcdn.com/96d36dd6-547f-4b84-8344-bd8791f8b430/COVER%20NOVEL3ok.jpg
proyek: 'Dunia Nawung, putri malu dari Jawa '
lokasi: Kota Yogyakarta/Yogyakarta
lokasi_id: ''
deskripsi: >-
Saya ingin mewujudkan cerita dalam novel yang saya tulis, Nawung, putri malu
dari Jawa, dalam bentuk pameran kolaborasi. Idealnya membuat sebuah desa
sesuai gambaran dalam novel yang berlokasi di sekitar Candi Borobudur, Jawa
Tengah. Namun untuk saat ini saya ingin mewujudkannya di rumah yang saya sewa
di Yogyakarta. Dalam pelaksanaannya saya berkolaborasi dengan semua bentuk
seni. Seni interior untuk kamar-kamar tokoh dalam cerita, seni landscape untuk
display karya seni patung, seni ilustrasi untuk ruang pamer, seni fashion dan
merchandise untuk giftshop, seni pertunjukan untuk seni tari dan seni musik
(album sudah ada), hiburan layar tancep untuk seni film trailer animasi
Nawung, seni tata boga untuk makanan yang tertulis dalam novel, seni batik
untuk workshop, pengetahuan proses pembuatan animasi, Pameran buku Nawung
dalam bentuk seni Pop-up art book, seni photography dan seni story telling.
Pameran kolaborasi novel ini untuk mengenalkan budaya Jawa melalui sastra dan
seni kepada siswa SMP dan SMA dan wisatawan. Dalam sehari kunjungan para
siswa ataupun tamu bisa menikmati pameran semua karya seni sambil belajar
budaya Jawa. Dalam tiap event, akan diadakan seminar kecil tentang bagaimana
proses penulisan novel Nawung, putri malu dari Jawa mulai dari ide hingga
menjadi buku dan workshop membatik.
kategori: kerjasama_kolaborasi
latar_belakang: "Awalnya saya merasa prihatin karena budaya Jawa sudah mulai terkikis. Dengan menulis novel saya berharap bisa memberikan sumbangan pemikiran untuk mempertahankan budaya yang mulai luntur ini. Namun saya baru menyadari bahwa minat baca belum begitu besar. Kemudian saya beralih ke karya animasi. Kendala yang saya alami adalah pembiayaan. Sementara ini saya hanya mampu membuat trailer. Kegiatan yang lain yang saya lakukan di saat saya libur adalah membangkitkan minat baca anak-anak dan para ibu muda di desa untuk mengembalikan budaya mendongeng. Saya juga merintis membuat perpustakaan kecil bagi anak-anak di desa. \r\nDengan konsep yang akan saya wujudkan ini, akan menjadi lebih efisien dan menguntungkan banyak pihak. Bagi pengunjung, dalam sehari bisa mengenal kembali budaya yang mulai luntur, para seniman terdukung dalam bentuk royalty hasil penjualan merchandise yang nantinya akan dibagikan untuk para seniman yang berkolaborasi dalam wadah koperasi seniman. Apabila program ini bisa berjalan dengan baik, maka budaya-budaya di wilayah lain juga bisa dibuat dengan konsep yang sama.\r\nUntuk membiayai proyek saya selama ini, saya membuat program 'Kaleidoscope of Java tour' ke Borobudur dan di sekitarnya. Tour saya ini sudah mendapat pengakuan dan masuk dalam 10 besar di situs wisata Trip Advisor. "
masalah: "Dalam tulisan novel saya, sebenarnya sudah mewakili semua permasalahan yang akan diangkat. \r\n1. Lunturnya budaya Jawa. Dengan mengenalkan budaya Jawa dalam bentuk karya seni akan menjadi daya tarik tersendiri. \r\n2. Mengenai kurangnya minat baca, dengan program ini akan memberi inspirasi bagaimana meningkatkan minat baca kembali dari workshop tentang proses penulisan novel tersebut. Kalau terinspirasi menjadi penulis, harus banyak membaca dulu.\r\n3. Hidup sembrono : Pengaturan kamar tokoh dalam novel yang rapi dan teratur akan menginspirasi \r\n4. Pengelolaan sampah rumah tangga: Kebersihan taman dari sampah plastik dan keindahan bunga-bunga di taman juga akan memberikan pengetahuan.\r\n5. Memahami seni dari perspektif lain\r\n6. Mengenal kembali masakan tradisional yang sehat dan mulai hilang. \r\n7. Mengenalkan bentuk etika umum (dalam berkendara dan dalam kehidupan sehari-hari)\r\n8. Pendidikan : ide-ide inspiratif dalam cerita untuk belajar apapun tanpa biaya besar. \r\n"
durasi: 5 bulan
sukses: "1. Pelestarian seni dan budaya : Dari isi novel pembaca akan bangga dengan kekayaan budaya sendiri.\r\n2. Pendidikan : Melalui seminar kecil dan workshop menjadi oleh-oleh pengetahuan tambahan untuk di bawa pulang. Novel saya sudah diteliti oleh mahasiswi UNS Solo, sebagai novel yang bisa dijadikan referensi untuk pendidikan karakter\r\n3. Seni : Semua bentuk seni yang dikolaborasikan dengan indah yang dipamerkan akan memberikan nuansa yang artistik dan tidak membosankan. \r\n4. Ekonomi : Perputaran ekonomi yang terbentuk dari penjualan hasil karya dan merchandise, nantinya akan meningkatkan kesejahteraan hidup para seniman yang tergabung. Selanjutnya akan saya bentuk sebuah koperasi seniman yang mengelola penerimaan royalti dan tabungan para seniman.\r\nSaya sangat berharap even ini bisa berlangsung terus menerus, karena saya ingin mewujudkan mimpi saya yang lebih besar yaitu : Membuat cerita trilogi Putri malu dari Jawa (Cakra Manggilingan, Sangkan Paraning Dumadi dan Hamemayu Hayuning Jagad), membuat Desa putri malu dari Jawa, dan membuat film layar lebar dan animasinya. "
dana: '185'
submission_id: 5a5dfc7435c5152d8f083dea
---
| 108.615385 | 1,334 | 0.814802 | ind_Latn | 0.971891 |
9ae2847db0ef6d2013d19843c727e789c9505557 | 1,488 | md | Markdown | README.md | JerryLingjieMei/FastMultipleMethod | e90e212452370906aa9923885e725cc2c9a31f22 | [
"MIT"
] | null | null | null | README.md | JerryLingjieMei/FastMultipleMethod | e90e212452370906aa9923885e725cc2c9a31f22 | [
"MIT"
] | null | null | null | README.md | JerryLingjieMei/FastMultipleMethod | e90e212452370906aa9923885e725cc2c9a31f22 | [
"MIT"
] | null | null | null | # Fast Multiple Method
[Fast Multiple Method](https://en.wikipedia.org/wiki/Fast_multipole_method) (FMM) is a fast technique to calculate forces in multiple positions of a n-body system. This project is an implementation of FMM in 1D. An brief introduction to this method can be found in [this short course](https://www.math.nyu.edu/faculty/greengar/shortcourse_fmm.pdf).
## File Descriptions
### FMM.h
[FMM.h](FMM.h) is the header containing necessary classes for implementing FFM in 1D. The ```FMM1d``` gives a class to intialize a n-body system with an array of weights in differnt places, as well as a parameter ```h``` and maximal error ```eps```.
```cpp
FMM1d(double *begin, double *end, double *weightBegin, double *weightEnd, double h, double eps)
```
This class has equipped with a method ```FMM1d::evaluate(double x)``` to evalute the total force at position ```x```.
### main.cpp & RadialBasis.pdf
[main.cpp](main.cpp) contains test to meet the technical requirements in [RadialBasis.pdf](Radial Basis.pdf). It shows that the FMM has a run time complexity of $O(n\log(1/\varepsilon))$ with the maximal error $\varepsilon$, compared to a $O(n^2)$ of the brute force.
### 18_330_Final.pdf
[18_330_Final.pdf ](18_330_Final.pdf ) is a detailed report on how the algorithm is implemented and comparative results.
## Acknowledgements
This project is inspired by [Matthias Taus](taus@mit.edu) from MIT Mathematics in the 18.330 class during the fall term in 2017. | 55.111111 | 349 | 0.745296 | eng_Latn | 0.988816 |
9ae2c54dcf186c361ca56bbcfe5ae07701efcf71 | 753 | md | Markdown | src/third_party/harviewer/requirejs/build/jslib/uglifyjs/README.md | ashumeow/pcaphar | 68d20b74bb16fa1b4183ebe04753ffcecf9daedf | [
"Apache-2.0"
] | 22 | 2015-03-11T05:45:28.000Z | 2021-05-07T15:56:15.000Z | src/third_party/harviewer/requirejs/build/jslib/uglifyjs/README.md | ashumeow/pcaphar | 68d20b74bb16fa1b4183ebe04753ffcecf9daedf | [
"Apache-2.0"
] | 1 | 2020-10-18T04:19:50.000Z | 2020-10-18T04:19:50.000Z | src/third_party/harviewer/requirejs/build/jslib/uglifyjs/README.md | ashumeow/pcaphar | 68d20b74bb16fa1b4183ebe04753ffcecf9daedf | [
"Apache-2.0"
] | 8 | 2015-01-23T11:38:50.000Z | 2019-11-16T20:34:57.000Z | This is a copy of UglifyJS from the following location around Jan 17, 2011, 9pm Pacific:
https://github.com/mishoo/UglifyJS
UglifyJS is under the BSD license, and it a third-party package.
* The contents of the package were modified to wrap the modules in a define() wrapper.
* The scripts in the original lib directory were just placed alongside index.js to allow for an easier path mapping.
* index.js was modified to use the ./ path instead of the ./lib/ path.
* In parse-js.js, in function JS_Parse_Error, the try/catch to generate a stack is disabled.
If UglifyJS is updated, be sure to run a Java-backed optimizer test to be sure
it still works in that environment. Array.prototype.reduce needed to be added
to get the existing version to work. | 57.923077 | 116 | 0.77822 | eng_Latn | 0.999499 |
9ae2eb74581ed76d2e8bd85e9a6cff93bb491f1b | 9,805 | md | Markdown | src/docs/testing-a-geospatial-app/3-testing-ui.md | NikkiLoveGod/vis-academy | caa9dd3df7b4cac2048cc9a2898eb3e1d984e1e6 | [
"MIT"
] | 7 | 2017-08-30T09:17:55.000Z | 2017-09-18T22:10:00.000Z | src/docs/testing-a-geospatial-app/3-testing-ui.md | NikkiLoveGod/vis-academy | caa9dd3df7b4cac2048cc9a2898eb3e1d984e1e6 | [
"MIT"
] | 1 | 2017-08-16T23:48:19.000Z | 2017-08-16T23:48:19.000Z | src/docs/testing-a-geospatial-app/3-testing-ui.md | NikkiLoveGod/vis-academy | caa9dd3df7b4cac2048cc9a2898eb3e1d984e1e6 | [
"MIT"
] | 1 | 2017-08-29T23:28:01.000Z | 2017-08-29T23:28:01.000Z | <ul class='insert learning-objectives'>
<li>See how components can be tested in a simulated browser environment</li>
<li>Learn how to test attributes of elements created by components</li>
<li>Simulate events such as clicks on our test components</li>
<li>Setup spy functions</li>
</ul>
## Testing UI
In this section, we're going to go deeper than simply trying to call component constructors.
We're going to use Enzyme to test how actual components behave once rendered. That should be difficult, because when testing, we are not in a browswer environment and we don't have a DOM in which to actually render the component. This is why Enzyme comes with a companion module, JSDOM, which can simulate the DOM while testing.
To make this work, we're going to have to add quite a few things:
```
npm install babel-polyfill enzyme enzyme-adapter-react-15 jsdom jsdom-global sinon --save-dev
```
What do they all do?
* babel-polyfill is so that some ES6 JS features will be available during testing. That's typically not a problem when using the application that we want to test in a browser, because we use build systems and transpilers. But the testing environment doesn't have that.
* enzyme is the main module which will let us test our components in the DOM.
* enzyme-adapter-react-15: enzyme needs to be configured to work in a certain environment, through "adapters".
* jsdom is the javascript "headless browser" that will be used to simulate the DOM.
* jsdom-global will inject the parts of the DOM API you need for testing in your node.js environment.
* sinon is a module we will use to build spy functions.
We're not done yet!
Create a new file in src/test called 'setup-browser-env' and paste this:
```
/* setup.js */
import 'babel-polyfill';
import JSDOM from 'jsdom';
const Adapter = require('enzyme-adapter-react-15');
const { configure } = require('enzyme');
require('jsdom-global')();
configure({ adapter: new Adapter() });
```
Go back to your package.json file and modify the "test" script like so:
```
"test": "NODE_ENV=test tape -r babel-register -r ./src/test/setup-browser-env.js ./src/test/",
```
create another file in /src/test called components.js. It can be left empty for now.
Finally, we're going to add it to our /src/test/index.js:
```
import "./components";
import "./smoke-screens";
```
Are you ready? Let's test!
## Shallow mounting
Let's open our src/test/component.js file.
```
import React from "react";
import { shallow } from "enzyme";
import test from "tape-catch";
import App from "../app";
test("Mounting the app", assert => {
const app = shallow(<App />);
assert.ok(app.exists(), "App mounted");
assert.end();
});
```
And try npm run test.
That test doesn't pass! why? Because App requires an init prop and a changeViewport prop. We're try to shallow-mount our component in the DOM. That means that the constructor and componentDidMount methods are going to be called. That's different from our smoke screens!
In Enzyme parlance, app (that is, the output of shallow(<App />)) is a wrapper. A wrapper contains a tree of nodes.
So let's modify our test:
```
test("Mounting the app", assert => {
const app = shallow(<App init={() => {}} changeViewport={() => {}} />);
assert.ok(app.exists(), "App mounted");
assert.end();
});
```
Now this passes.
Let's take a closer look at what we're testing. exists() is a method from Enzyme which tests if a node exists. If applied to a wrapper, it tests whether it contains one node.
Let's make our tests a little bit more interesting with spy functions.
We're going to import sinon, and add the following to our test:
```
import React from "react";
import { shallow } from "enzyme";
import test from "tape-catch";
import App from "../app";
import sinon from "sinon";
test("Mounting the app", assert => {
const init = sinon.spy();
const changeViewport = sinon.spy();
const app = shallow(<App init={init} changeViewport={changeViewport} />);
assert.ok(app.exists(), "App mounted");
assert.equals(init.called, true, "init called");
assert.equals(changeViewport.calledOnce, true, "changeViewport called once");
app.unmount();
assert.ok(true, "App unmounted");
assert.end();
});
```
A spy function is a function which collects information about how, whwn and how often it's called.
Let's try a few ways to use them:
Here, we verify that init has been called - once, ten times, one hundred times? this test doesn't tell. At least once.
Then, we verify that changeViewport has been called exactly once.
Finally, we're going to unmount our wrapper. Doing so calls its componentDidUnmount method.
## Full mounting and using fixtures
Next, we're going to test the Charts component.
```
test("mounting the charts", assert => {
const chartsWithoutData = shallow(<Charts />);
assert.equals(
chartsWithoutData.find("div").children().length,
0,
"without data no chart is rendered"
);
asset.end();
});
```
Unfortunatalely, tests need a pickups prop to render anything else than a div - without that, it just renders an empty div.
This is what this test checks: the wrapper contains a div, but it has 0 children.
To do anything more interesting, we're going to need data. We don't actually have to use real data, but we might as well.
So let's create a fixtures.js file in /src/test, and paste this inside:
```
module.exports = {
pickups: [
{ hour: 0, x: 0.5, y: 246 },
{ hour: 1, x: 1.5, y: 173 },
{ hour: 2, x: 2.5, y: 98 },
{ hour: 3, x: 3.5, y: 59 },
{ hour: 4, x: 4.5, y: 53 },
{ hour: 5, x: 5.5, y: 102 },
{ hour: 6, x: 6.5, y: 294 },
{ hour: 7, x: 7.5, y: 466 },
{ hour: 8, x: 8.5, y: 574 },
{ hour: 9, x: 9.5, y: 542 },
{ hour: 10, x: 10.5, y: 434 },
{ hour: 11, x: 11.5, y: 510 },
{ hour: 12, x: 12.5, y: 468 },
{ hour: 13, x: 13.5, y: 435 },
{ hour: 14, x: 14.5, y: 526 },
{ hour: 15, x: 15.5, y: 453 },
{ hour: 16, x: 16.5, y: 400 },
{ hour: 17, x: 17.5, y: 503 },
{ hour: 18, x: 18.5, y: 602 },
{ hour: 19, x: 19.5, y: 645 },
{ hour: 20, x: 20.5, y: 647 },
{ hour: 21, x: 21.5, y: 662 },
{ hour: 22, x: 22.5, y: 609 },
{ hour: 23, x: 23.5, y: 498 }
]
};
```
Let's make sure to import that in our 'components.js' file -
```
import { pickups } from "./fixtures";
```
now, we're going to try to count the bars that are created by Charts. We pass an array that has 24 items, so we expect 24 bars. In the app, Charts uses react-vis to create a BarSeries component, which, in turns, generates a certain number of rect SVG elements. So let's try this:
```
test("mounting the charts", assert => {
const chartsWithoutData = shallow(<Charts />);
assert.equals(
chartsWithoutData.find("div").children().length,
0,
"without data no chart is rendered"
);
const charts = shallow(
<Charts
pickups={pickups}
highlight={highlight}
select={select}
highlightedHour={1}
selectedHour={2}
/>
);
const bars = charts.find("rect");
assert.equals(bars.length, 24, "charts has 24 rect elements");
asset.end();
})
```
But this test doesn't work. That's because when shallow mounting, we can only see what happens one element deep. That's already super useful and faster than fully rendering the elements. But for this, shallow isn't enough, so let's use Enzyme's fuller API: mount().
Let's make sure to import it:
```
import { mount, shallow } from "enzyme";
```
now let's try this:
```
test("mounting the charts", assert => {
const highlight = sinon.spy();
const select = sinon.spy();
const chartsWithoutData = shallow(<Charts />);
assert.equals(
chartsWithoutData.find("div").children().length,
0,
"without data no chart is rendered"
);
const charts = mount(
<Charts
pickups={pickups}
highlight={highlight}
select={select}
highlightedHour={1}
selectedHour={2}
/>
);
const bars = charts.find("rect");
assert.equals(bars.length, 24, "charts has 24 rect elements");
assert.equals(
bars.first().props().style.fill,
"#125C77",
"unselected bar has normal color"
);
assert.equals(
bars.at(1).props().style.fill,
"#17B8BE",
"highlighted bar has special color"
);
assert.equals(
bars.at(2).props().style.fill,
"#19CDD7",
"selected bar has special color"
);
bars.first().simulate("mouseover");
bars.first().simulate("click");
assert.equals(highlight.callCount, 1, "highlight has been called once");
assert.equals(select.callCount, 1, "select has been called once");
charts.unmount();
assert.end();
});
```
Our previous test passes. We can effectively see the 24 elements.
For the next set of tests, we're going to explore another really useful method of Enzyme: props(). We are going to select nodes, then test their properties, in this case, their style. Charts is supposed to render the highlighted and the selected bar with certain colors, and normal bars with another one.
But how to select a specific node out of many? we can use the at(n) method to select the nth method. For the first node of a series, we can use first() instead.
Next, we are going to simulate events, in this case mousing over a node and clicking on it.
Finally, we're going to use spy functions again to see that those events had an effect. This time we're using the more generic syntax, callCount, which stores the number of times a function has been called.
Let's continue to the next section: [testing actions](#testing-a-geospatial-app/4-testing-actions).
<ul class='insert takeaways'>
<li>Once the proper testing environment is set up, we can go well beyond smoke screens.</li>
<li>We can test and simulate how our components look but also how they react to events.</li>
</ul>
| 33.927336 | 328 | 0.685365 | eng_Latn | 0.993982 |
9ae39c88a03b0c023bb9f44c1424458f1c41f2e2 | 1,341 | md | Markdown | 2020/08/24/2020-08-24 05:20.md | zhzhzhy/WeiBoHot_history | 32ce4800e63f26384abb17d43e308452c537c902 | [
"MIT"
] | 3 | 2020-07-14T14:54:15.000Z | 2020-08-21T06:48:24.000Z | 2020/08/24/2020-08-24 05:20.md | zhzhzhy/WeiBoHot_history | 32ce4800e63f26384abb17d43e308452c537c902 | [
"MIT"
] | null | null | null | 2020/08/24/2020-08-24 05:20.md | zhzhzhy/WeiBoHot_history | 32ce4800e63f26384abb17d43e308452c537c902 | [
"MIT"
] | null | null | null | 2020年08月24日05时数据
Status: 200
1.巴黎 拜仁
微博热度:455646
2.浙江舟山持刀伤人案致2人死亡
微博热度:203864
3.拜仁夺得欧冠冠军
微博热度:159514
4.小橙子受不了陈婷
微博热度:132678
5.央视专访误入武汉战疫的大连小伙
微博热度:82692
6.李现 他们最近自力更生得很好
微博热度:82547
7.凌霄亲李尖尖
微博热度:79425
8.琉璃
微博热度:73962
9.特朗普83岁姐姐录音
微博热度:70298
10.云南被抱走男孩父亲发声
微博热度:70165
11.拜仁进球
微博热度:63890
12.天天向上
微博热度:54311
13.科曼突破被放倒
微博热度:52060
14.美国新冠感染病例出现年轻化趋势
微博热度:49139
15.秘鲁首都夜店发生踩踏事故
微博热度:48664
16.以家人之名
微博热度:48052
17.贺梅
微博热度:48022
18.欧冠
微博热度:47372
19.丽江3岁男孩被坐白色车女子抱走
微博热度:46458
20.点痣专家褚璇玑
微博热度:46402
21.寒门姐弟同时考上哈工大
微博热度:45022
22.酒桌文化
微博热度:44213
23.半泽直树
微博热度:38928
24.大爷大妈把共享单车当运动器材锻炼
微博热度:37787
25.岳云鹏P图迪士尼在逃王子
微博热度:37246
26.摩天大楼
微博热度:35849
27.阴阳怪气小技巧
微博热度:34483
28.内马尔心态
微博热度:34300
29.乌克兰前总理季莫申科感染新冠肺炎
微博热度:33747
30.喝西北风居然是成语
微博热度:33569
31.司凤璇玑九生九世
微博热度:33373
32.吴亦凡说做主持太难了
微博热度:32330
33.航班延误大叔机场泡2小时茶
微博热度:32183
34.十九届中央第五轮巡视完成反馈
微博热度:31818
35.兄妹之间可以有多塑料
微博热度:31638
36.许久未见一个飞奔蹦到爸爸身上
微博热度:31281
37.北京大雨
微博热度:30834
38.准研究生虐狗事件狗主人不接受道歉
微博热度:30387
39.伊能静写小作文夸李斯丹妮组
微博热度:30154
40.逝者家属感谢救人无效遭恶评的医学生
微博热度:27094
41.三峡成功抵御建库以来最大洪峰
微博热度:26121
42.杨祐宁得女
微博热度:26068
43.Faker被换下
微博热度:25628
44.大长腿滤镜下的央视主持人
微博热度:24634
45.欧豪被粉丝送香肠
微博热度:23837
46.导演陈木胜去世
微博热度:23259
47.叶舒华胖了
微博热度:23073
48.记者进入国产新冠疫苗生产车间
微博热度:22508
49.满记甜品等知名餐饮品牌吃罚单
微博热度:22118
50.肖战士兵造型
微博热度:21696
| 6.573529 | 20 | 0.771066 | yue_Hant | 0.43113 |
9ae3c3ea6f5ff305de3f9c29ab75c1cb93c33966 | 934 | md | Markdown | examples/react-router-prototyping/README.md | lalobot/react-sketchapp | 29f48d8ebfc7d10b4bdaee7a3c19e4acfaebb68a | [
"MIT"
] | 15,957 | 2017-04-25T16:54:44.000Z | 2022-03-31T06:18:16.000Z | examples/react-router-prototyping/README.md | lalobot/react-sketchapp | 29f48d8ebfc7d10b4bdaee7a3c19e4acfaebb68a | [
"MIT"
] | 398 | 2017-04-25T17:20:58.000Z | 2021-11-13T21:30:41.000Z | examples/react-router-prototyping/README.md | lalobot/react-sketchapp | 29f48d8ebfc7d10b4bdaee7a3c19e4acfaebb68a | [
"MIT"
] | 1,059 | 2017-04-25T18:17:33.000Z | 2022-03-24T10:55:13.000Z | # React Router setup
## How to use
Download the example or [clone the repo](http://github.com/airbnb/react-sketchapp):
```bash
curl https://codeload.github.com/airbnb/react-sketchapp/tar.gz/master | tar -xz --strip=2 react-sketchapp-master/examples/react-router-prototyping
cd react-router-prototyping
```
Install the dependencies
```bash
npm install
```
Then, open Sketch and navigate to `Plugins → react-sketchapp: React Router prototyping`
Run with live reloading in Sketch, need a new sketch doc open
```bash
npm run render
```
## The idea behind the example
`react-sketchapp` allows you to build prototypes with navigation. This example shows how you build a Sketch prototype with `react-sketchapp-router`, while being able to share your routing code with your React web or React Native app.
| 30.129032 | 233 | 0.773019 | eng_Latn | 0.946006 |
9ae3fe3299bf2d4a8d8750e1aea64ff148dae32b | 12,653 | md | Markdown | docs/vsto/excel-solutions.md | LouisFr81/visualstudio-docs.fr-fr | e673e36b5b37ecf1f5eb97c42af84eed9c303200 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vsto/excel-solutions.md | LouisFr81/visualstudio-docs.fr-fr | e673e36b5b37ecf1f5eb97c42af84eed9c303200 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vsto/excel-solutions.md | LouisFr81/visualstudio-docs.fr-fr | e673e36b5b37ecf1f5eb97c42af84eed9c303200 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: solutions Excel
ms.date: 02/02/2017
ms.topic: conceptual
dev_langs:
- VB
- CSharp
helpviewer_keywords:
- application-level add-ins [Office development in Visual Studio], Excel
- Excel [Office development in Visual Studio], application-level add-ins
- Office solutions [Office development in Visual Studio], Excel
- solutions [Office development in Visual Studio], Excel
- add-ins [Office development in Visual Studio], Excel
- Excel [Office development in Visual Studio], about Excel solutions
- Excel [Office development in Visual Studio]
- documents [Office development in Visual Studio], Excel
- Office documents [Office development in Visual Studio, Excel
- projects [Office development in Visual Studio], Excel
- Excel [Office development in Visual Studio], document-level customizations
- user interfaces [Office development in Visual Studio], Excel
- Office development in Visual Studio, Excel solutions
- document-level customizations [Office development in Visual Studio], Excel
- Office projects [Office development in Visual Studio], Excel
author: John-Hart
ms.author: johnhart
manager: jillfra
ms.workload:
- office
ms.openlocfilehash: f96543c3f2cca5c067eea4af4b14bc67d7d129c7
ms.sourcegitcommit: d0425b6b7d4b99e17ca6ac0671282bc718f80910
ms.translationtype: MT
ms.contentlocale: fr-FR
ms.lasthandoff: 02/21/2019
ms.locfileid: "56600538"
---
# <a name="excel-solutions"></a>solutions Excel
Visual Studio fournit des modèles de projet à l'aide desquels vous pouvez créer des personnalisations de niveau document et des compléments VSTO pour Microsoft Office Excel. Vous pouvez utiliser ces solutions pour automatiser Excel, étendre les fonctionnalités Excel et personnaliser l'interface utilisateur Excel. Pour plus d’informations sur les différences entre personnalisations au niveau du document et des Compléments VSTO, consultez [présentation du développement de solutions Office (VSTO)](../vsto/office-solutions-development-overview-vsto.md).
[!INCLUDE[appliesto_xlalldocapp](../vsto/includes/appliesto-xlalldocapp-md.md)]
> [!NOTE]
> Vous souhaitez développer des solutions qui étendent l’expérience Office sur [plusieurs plateformes](https://dev.office.com/add-in-availability)? Découvrez le nouvel [modèle de compléments Office](https://dev.office.com/docs/add-ins/overview/office-add-ins). Compléments Office peu encombrantes par rapport aux compléments VSTO et de solutions, et vous pouvez les créer à l’aide de presque toutes les technologies, telles que HTML5, JavaScript, CSS3 et XML de programmation web.
Cette rubrique fournit les informations suivantes :
- [Automatiser Excel](#automating).
- [Développer des personnalisations au niveau du document pour Excel](#doclevel).
- [Développer des Compléments VSTO pour Excel](#applevel).
- [Personnaliser l’interface utilisateur d’Excel](#UI).
## <a name="automating"></a> Automatiser Excel
Le modèle objet Excel expose de nombreux types que vous pouvez utiliser pour automatiser Excel. Par exemple, vous pouvez créer des graphiques par programmation, mettre en forme des feuilles de calcul et définir les valeurs de plages et de cellules. Pour plus d’informations, consultez [vue d’ensemble du modèle d’objet Excel](../vsto/excel-object-model-overview.md).
Lorsque vous développez des solutions Excel dans Visual Studio, vous pouvez également utiliser les *éléments hôtes* et les *contrôles hôtes* dans vos solutions. Il s'agit d'objets qui étendent certains objets couramment utilisés dans le modèle objet Excel, tels que les objets <xref:Microsoft.Office.Interop.Excel.Worksheet> et <xref:Microsoft.Office.Interop.Excel.Range> . Les objets étendus se comportent comme les objets Excel dont ils dépendent, mais ils ajoutent des événements supplémentaires et des fonctionnalités de liaison de données aux objets. Pour plus d’informations, consultez [automatisation d’Excel à l’aide d’objets étendus](../vsto/automating-excel-by-using-extended-objects.md).
## <a name="doclevel"></a> Développer des personnalisations au niveau du document pour Excel
Une personnalisation au niveau du document pour Microsoft Office Excel se compose d'un assembly qui est associé à un classeur spécifique. L'assembly augmente généralement les fonctionnalités du classeur en personnalisant l'interface utilisateur et en automatisant Excel. Contrairement à un complément VSTO, qui est associé à Excel lui-même, les fonctionnalités que vous implémentez dans une personnalisation sont disponibles uniquement lorsque le classeur associé est ouvert dans Excel.
Pour créer un projet de personnalisation au niveau du document pour Excel, utilisez le classeur Excel ou les modèles de projet de modèle Excel dans le **nouveau projet** boîte de dialogue de Visual Studio. Pour plus d'informations, voir [Procédure : Créer des projets Office dans Visual Studio](../vsto/how-to-create-office-projects-in-visual-studio.md).
Pour plus d’informations sur comment au niveau du document personnalisations, consultez [Architecture des personnalisations au niveau du document](../vsto/architecture-of-document-level-customizations.md).
### <a name="excel-customization-programming-model"></a>Modèle de programmation de personnalisation Excel
Lorsque vous créez un projet au niveau du document pour Excel, Visual Studio génère plusieurs classes qui constituent la base de votre solution : `ThisWorkbook`, `Sheet1`, `Sheet2`et `Sheet3`. Ces classes représentent le classeur et les feuilles de calcul qui sont associés à votre solution et fournissent un point de départ pour écrire votre code.
Pour plus d’informations sur ces classes générées et autres fonctionnalités que vous pouvez utiliser dans un projet au niveau du document, consultez [programmer des personnalisations au niveau du document](../vsto/programming-document-level-customizations.md).
## <a name="applevel"></a> Développer des Compléments VSTO pour Excel
Un complément VSTO pour Microsoft Office Excel se compose d'un assembly qui est chargé par Excel. L'assembly augmente généralement les fonctionnalités Excel en personnalisant l'interface utilisateur et en automatisant Excel. Contrairement à une personnalisation au niveau du document, qui est associée à un classeur spécifique, les fonctionnalités que vous implémentez dans un complément, VSTO ne sont pas limitées à un seul classeur.
Pour créer un projet de complément VSTO pour Excel, utilisez le classeur Excel ou les modèles de projet de modèle Excel dans le **nouveau projet** boîte de dialogue de Visual Studio. Pour plus d'informations, voir [Procédure : Créer des projets Office dans Visual Studio](../vsto/how-to-create-office-projects-in-visual-studio.md).
Pour obtenir des informations générales sur le fonctionnement des compléments VSTO, consultez [Architecture of VSTO Add-ins](../vsto/architecture-of-vsto-add-ins.md).
### <a name="excel-add-in-programming-model"></a>Excel Add-in modèle de programmation
Lorsque vous créez un projet de complément VSTO Excel, Visual Studio génère une classe, nommée `ThisAddIn`, qui est le fondement de votre solution. Cette classe fournit un point de départ pour écrire votre code et elle expose également le modèle objet d’Excel à votre complément VSTO.
Pour plus d’informations sur la `ThisAddIn` classe et autres fonctionnalités de Visual Studio que vous pouvez utiliser dans un complément VSTO, consultez [programme VSTO Add-Ins](../vsto/programming-vsto-add-ins.md).
## <a name="UI"></a> Personnaliser l’interface utilisateur d’Excel
Il existe différentes façons de personnaliser l'interface utilisateur d'Excel. Certaines options sont disponibles pour tous les types de projets, tandis que d'autres options sont disponibles uniquement pour les compléments VSTO ou les personnalisations au niveau du document.
### <a name="options-for-all-project-types"></a>Options pour tous les types de projet
Le tableau suivant répertorie les options de personnalisation qui sont disponibles pour les personnalisations au niveau du document et les compléments VSTO.
|Tâche|Pour plus d'informations|
|----------|--------------------------|
|Personnaliser le ruban.|[Vue d’ensemble du ruban](../vsto/ribbon-overview.md)|
|Ajouter des contrôles Windows Forms ou contrôles Excel étendus à une feuille de calcul dans le classeur personnalisé pour une personnalisation au niveau du document ou d'un classeur ouvert pour un complément VSTO.|[Guide pratique pour Ajouter des contrôles Windows forms aux documents Office](../vsto/how-to-add-windows-forms-controls-to-office-documents.md)<br /><br /> [Guide pratique pour Ajouter des contrôles Chart aux feuilles de calcul](../vsto/how-to-add-chart-controls-to-worksheets.md)<br /><br /> [Guide pratique pour Ajouter des contrôles ListObject aux feuilles de calcul](../vsto/how-to-add-listobject-controls-to-worksheets.md)<br /><br /> [Guide pratique pour Ajouter des contrôles NamedRange aux feuilles de calcul](../vsto/how-to-add-namedrange-controls-to-worksheets.md)|
### <a name="options-for-document-level-customizations"></a>Options pour les personnalisations au niveau du document
Le tableau suivant répertorie les options de personnalisation qui sont disponibles uniquement pour les personnalisations au niveau du document.
|Tâche|Pour plus d'informations|
|----------|--------------------------|
|Ajouter un volet Actions au classeur.|[Vue d’ensemble du volet Actions](../vsto/actions-pane-overview.md)<br /><br /> [Guide pratique pour Ajouter un volet actions à des documents Word ou des classeurs Excel](../vsto/how-to-add-an-actions-pane-to-word-documents-or-excel-workbooks.md)|
|Ajoutez des contrôles de plage étendue mappés aux nœuds XML d'une feuille de calcul.|[Guide pratique pour Ajouter des contrôles XMLMappedRange aux feuilles de calcul](../vsto/how-to-add-xmlmappedrange-controls-to-worksheets.md)|
### <a name="options-for-vsto-add-ins"></a>Options pour les compléments VSTO
Le tableau suivant répertorie les options de personnalisation qui sont disponibles uniquement pour les compléments VSTO.
|Tâche|Pour plus d'informations|
|----------|--------------------------|
|Créer un volet des tâches personnalisé.|[Volets Office personnalisés](../vsto/custom-task-panes.md)|
### <a name="related-topics"></a>Rubriques connexes
| Titre | Description |
| - | - |
| [Vue d’ensemble du modèle d’objet Excel](../vsto/excel-object-model-overview.md) | Fournit une vue d'ensemble des principaux types fournis par le modèle objet Excel. |
| [Automatiser Excel à l’aide d’objets étendus](../vsto/automating-excel-by-using-extended-objects.md) | Fournit des informations sur les objets étendus (fournis par le [!INCLUDE[vsto_runtime](../vsto/includes/vsto-runtime-md.md)]) que vous pouvez utiliser dans les solutions Excel. |
| [Globalisation et localisation de solutions Excel](../vsto/globalization-and-localization-of-excel-solutions.md) | Contient des informations sur les considérations spéciales pour les solutions Excel qui seront exécutées sur les ordinateurs ayant des paramètres autres qu'anglais pour Windows. |
| [Contrôles Windows Forms dans les documents Office](../vsto/windows-forms-controls-on-office-documents-overview.md) | Décrit comment ajouter des contrôles Windows Forms aux feuilles de calcul Excel. |
| [Procédure pas à pas : Créer votre première personnalisation au niveau du document pour Excel](../vsto/walkthrough-creating-your-first-document-level-customization-for-excel.md) | Montre comment créer une personnalisation de base au niveau du document pour Excel. |
| [Procédure pas à pas : Créer votre premier complément pour Excel](../vsto/walkthrough-creating-your-first-vsto-add-in-for-excel.md) | Montre comment créer un complément VSTO de base pour Excel. |
| [Procédure pas à pas : Ajouter des contrôles à une feuille de calcul lors de l’exécution dans un projet de complément VSTO](../vsto/walkthrough-adding-controls-to-a-worksheet-at-run-time-in-vsto-add-in-project.md) | Montre comment ajouter un contrôle button Windows Forms, un <xref:Microsoft.Office.Tools.Excel.NamedRange>et un <xref:Microsoft.Office.Tools.Excel.ListObject> à une feuille de calcul lors de l’exécution en utilisant un complément, VSTO. |
| [Comprendre la co-création et Add-ins](./understanding-coauthoring-and-addins.md) | Décrit les ajustements, que vous devrez peut-être apporter à vos solutions pour prendre en compte la cocréation. |
| [Excel 2010 dans le développement Office](http://go.microsoft.com/fwlink/?LinkId=199011) | Fournit des liens vers des articles et une documentation de référence sur le développement de solutions Excel. Ils ne sont pas spécifiques au développement Office avec Visual Studio. |
| 103.713115 | 791 | 0.789536 | fra_Latn | 0.959545 |
9ae4da5dfbebe21eec199ffbf1653c7024aaee2d | 5,991 | md | Markdown | articles/container-registry/container-registry-get-started-powershell.md | rahulvmarathe/azure-docs | 061b944ded79c437800a72dcf5ca18e38c6e3339 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/container-registry/container-registry-get-started-powershell.md | rahulvmarathe/azure-docs | 061b944ded79c437800a72dcf5ca18e38c6e3339 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/container-registry/container-registry-get-started-powershell.md | rahulvmarathe/azure-docs | 061b944ded79c437800a72dcf5ca18e38c6e3339 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Azure container registry repositories | Microsoft Docs
description: How to use Azure Container Registry repositories for Docker images
services: container-registry
documentationcenter: ''
author: cristy
manager: balans
editor: dlepow
ms.service: container-registry
ms.devlang: na
ms.topic: how-to-article
ms.tgt_pltfrm: na
ms.workload: na
ms.date: 05/30/2017
ms.author: cristyg
---
# Create a private Docker container registry using the Azure PowerShell
Use commands in [Azure PowerShell](https://docs.microsoft.com/en-us/powershell/azure/overview) to create a container registry and manage its settings from your Windows computer. You can also create and manage container registries using the [Azure portal](container-registry-get-started-portal.md), the [Azure CLI](container-registry-get-started-azure-cli.md), or programmatically with the Container Registry [REST API](https://go.microsoft.com/fwlink/p/?linkid=834376).
* For background and concepts, see [the overview](container-registry-intro.md)
* For a full list of supported cmdlets, see [Azure Container Registry Management Cmdlets](https://docs.microsoft.com/en-us/powershell/module/azurerm.containerregistry/).
## Prerequisites
* **Azure PowerShell**: To install and get started with Azure PowerShell, see the [installation instructions](https://docs.microsoft.com/en-us/powershell/azure/install-azurerm-ps). Log in to your Azure subscription by running `Login-AzureRMAccount`. For more information, see [Get started with Azure PowerShell](https://docs.microsoft.com/en-us/powershell/azure/get-started-azurep).
* **Resource group**: Create a [resource group](../azure-resource-manager/resource-group-overview.md#resource-groups) before creating a container registry, or use an existing resource group. Make sure the resource group is in a location where the Container Registry service is [available](https://azure.microsoft.com/regions/services/). To create a resource group using Azure PowerShell, see [the PowerShell reference](https://docs.microsoft.com/en-us/powershell/azure/get-started-azureps#create-a-resource-group).
* **Storage account** (optional): Create a standard Azure [storage account](../storage/common/storage-introduction.md) to back the container registry in the same location. If you don't specify a storage account when creating a registry with `New-AzureRMContainerRegistry`, the command creates one for you. To create a storage account using PowerShell, see [the PowerShell reference](https://docs.microsoft.com/en-us/powershell/module/azure/new-azurestorageaccount). Currently Premium Storage is not supported.
* **Service principal** (optional): When you create a registry with PowerShell, by default it is not set up for access. Depending on your needs, you can assign an existing Azure Active Directory service principal to a registry or create and assign a new one. Alternatively, you can enable the registry's admin user account. See the sections later in this article. For more information about registry access, see [Authenticate with the container registry](container-registry-authentication.md).
## Create a container registry
Run the `New-AzureRMContainerRegistry` command to create a container registry.
> [!TIP]
> When you create a registry, specify a globally unique top-level domain name, containing only letters and numbers. The registry name in the examples is `MyRegistry`, but substitute a unique name of your own.
>
>
The following command uses the minimal parameters to create container registry `MyRegistry` in the resource group `MyResourceGroup` in the South Central US location:
```PowerShell
$Registry = New-AzureRMContainerRegistry -ResourceGroupName "MyResourceGroup" -Name "MyRegistry"
```
* `-StorageAccountName` is optional. If not specified, a storage account is created with a name consisting of the registry name and a timestamp in the specified resource group.
## Assign a service principal
Use PowerShell commands to assign an Azure Active Directory [service principal](../azure-resource-manager/resource-group-authenticate-service-principal.md) to a registry. The service principal in these examples is assigned the Owner role, but you can assign [other roles](../active-directory/role-based-access-control-configure.md) if you want.
### Create a service principal
In the following command, a new service principal is created. Specify a strong password with the `-Password` parameter.
```PowerShell
$ServicePrincipal = New-AzureRMADServicePrincipal -DisplayName ApplicationDisplayName -Password "MyPassword"
```
### Assign a new or existing service principal
You can assign a new or an existing service principal to a registry. To assign it Owner role access to the registry, run a command similar to the following example:
```PowerShell
New-AzureRMRoleAssignment -RoleDefinitionName Owner -ServicePrincipalName $ServicePrincipal.ApplicationId -Scope $Registry.Id
```
##Sign in to the registry with the service principal
After assigning the service principal to the registry, you can sign in using the following command:
```PowerShell
docker login -u $ServicePrincipal.ApplicationId -p myPassword
```
## Manage admin credentials
An admin account is automatically created for each container registry and is disabled by default. The following examples show PowerShell commands to manage the admin credentials for your container registry.
### Obtain admin user credentials
```PowerShell
Get-AzureRMContainerRegistryCredential -ResourceGroupName "MyResourceGroup" -Name "MyRegistry"
```
### Enable admin user for an existing registry
```PowerShell
Update-AzureRMContainerRegistry -ResourceGroupName "MyResourceGroup" -Name "MyRegistry" -EnableAdminUser
```
### Disable admin user for an existing registry
```PowerShell
Update-AzureRMContainerRegistry -ResourceGroupName "MyResourceGroup" -Name "MyRegistry" -DisableAdminUser
```
## Next steps
* [Push your first image using the Docker CLI](container-registry-get-started-docker-cli.md)
| 63.063158 | 514 | 0.799366 | eng_Latn | 0.938784 |
9ae4ddf907c10050e7628cc362376614d038eb9c | 478 | md | Markdown | ocamldoc-json-generator/readme.md | idkjs/tablecloth | d0561894b4446969b28c559a62b291089c12ee72 | [
"MIT"
] | null | null | null | ocamldoc-json-generator/readme.md | idkjs/tablecloth | d0561894b4446969b28c559a62b291089c12ee72 | [
"MIT"
] | null | null | null | ocamldoc-json-generator/readme.md | idkjs/tablecloth | d0561894b4446969b28c559a62b291089c12ee72 | [
"MIT"
] | null | null | null | # Ocamldoc Json Generator
JsonGenerator.ml is responsible for taking the `/native` source files and turning them into a single json file (`website/model.json`) which the website project then turns into the `/api` page.
## Setup
The generator requires version 4.08 of the ocaml compiler
```
opam switch create 4.08
```
Then install the dependencies
```sh
make deps
```
## Usage
After making any changes to interface files run `make doc` to regenerate `website/model.json` | 23.9 | 192 | 0.753138 | eng_Latn | 0.982036 |
9ae61bd1a2ed04fd2e1652551969cb2ddab58a1f | 118 | md | Markdown | packages/jsend/README.md | MitDevBr/onhand-common | 2483f437ac67ac28ad25454db6d31c5849501df8 | [
"MIT"
] | null | null | null | packages/jsend/README.md | MitDevBr/onhand-common | 2483f437ac67ac28ad25454db6d31c5849501df8 | [
"MIT"
] | null | null | null | packages/jsend/README.md | MitDevBr/onhand-common | 2483f437ac67ac28ad25454db6d31c5849501df8 | [
"MIT"
] | null | null | null | # `jsend`
> TODO: description
## Usage
```typescript
const jsend = require('jsend');
// TODO: DEMONSTRATE API
```
| 9.833333 | 31 | 0.635593 | kor_Hang | 0.663778 |
9ae64681cd6e972c2f856f6cf09ea69a0b4a32da | 429 | md | Markdown | docs/content/releases/5.14.0.md | barchart/marketdata-api-js | ab90619418af726ff37a334970572fbeab5628fc | [
"MIT"
] | 19 | 2015-03-26T22:04:28.000Z | 2021-02-23T05:05:54.000Z | docs/content/releases/5.14.0.md | barchart/marketdata-api-js | ab90619418af726ff37a334970572fbeab5628fc | [
"MIT"
] | 6 | 2015-04-28T05:38:47.000Z | 2022-01-10T06:13:00.000Z | docs/content/releases/5.14.0.md | barchart/marketdata-api-js | ab90619418af726ff37a334970572fbeab5628fc | [
"MIT"
] | 14 | 2015-12-22T04:13:09.000Z | 2022-01-05T13:10:52.000Z | **New Features**
* In some cases, the default price formatting rules (based on the `UnitCode` class) need to be tweaked. In a prior version, we added the `Profile.setPriceFormatterCustom` function which allows the consumer to specify their own price-formatting delegate. This version adds an implementation of that delegate that is intended for use with the [cmdtyView](https://www.barchart.com/cmdty/trading/cmdtyview) product. | 143 | 411 | 0.799534 | eng_Latn | 0.995998 |
9ae64759cbc3ae33106a43080cdb4fd49c6cb526 | 7 | md | Markdown | quarkc/test/ffi/expected/rb/signatures/lib/generics/constructors/README.md | datawire/quark | df0058a148b077c0aff535eb6ee382605c556273 | [
"Apache-2.0"
] | 112 | 2015-10-02T19:51:51.000Z | 2022-03-07T06:29:44.000Z | quarkc/test/ffi/expected/js/signatures/generics/constructors/README.md | datawire/quark | df0058a148b077c0aff535eb6ee382605c556273 | [
"Apache-2.0"
] | 181 | 2015-10-01T20:23:38.000Z | 2016-12-07T17:21:26.000Z | quarkc/test/ffi/expected/rb/signatures/lib/generics/constructors/README.md | datawire/quark | df0058a148b077c0aff535eb6ee382605c556273 | [
"Apache-2.0"
] | 31 | 2015-10-13T22:10:00.000Z | 2020-08-03T02:50:12.000Z | ## Box
| 3.5 | 6 | 0.428571 | vie_Latn | 0.520907 |
9ae66e2d2c2e0c6b17f3dc03da3e134d12ed26ea | 268 | md | Markdown | _captures/TLP5_20200127.md | Meteoros-Floripa/meteoros.floripa.br | 7d296fb8d630a4e5fec9ab1a3fb6050420fc0dad | [
"MIT"
] | 5 | 2020-05-19T17:04:49.000Z | 2021-03-30T03:09:14.000Z | _captures/TLP5_20200127.md | Meteoros-Floripa/site | 764cf471d85a6b498873610e4f3b30efd1fd9fae | [
"MIT"
] | null | null | null | _captures/TLP5_20200127.md | Meteoros-Floripa/site | 764cf471d85a6b498873610e4f3b30efd1fd9fae | [
"MIT"
] | 2 | 2020-05-19T17:06:27.000Z | 2020-09-04T00:00:43.000Z | ---
layout: capture
label: 20200127
station: TLP5
date: 2020-01-28 01:51:50
preview: TLP5/2020/202001/20200127/stack.jpg
capturas:
- imagem: TLP5/2020/202001/20200127/M20200128_015150_TLP_5P.jpg
- imagem: TLP5/2020/202001/20200127/M20200128_031102_TLP_5P.jpg
---
| 24.363636 | 65 | 0.776119 | por_Latn | 0.051304 |
9ae6a9d15a4bb79e0fbc3dc6a8f135fcf14f7712 | 588 | md | Markdown | _slides/01-05.md | TaxFoundation/nc-chartbook | 7a5a1b8475ff759880ec386bd5b8011f8558abb3 | [
"MIT"
] | null | null | null | _slides/01-05.md | TaxFoundation/nc-chartbook | 7a5a1b8475ff759880ec386bd5b8011f8558abb3 | [
"MIT"
] | null | null | null | _slides/01-05.md | TaxFoundation/nc-chartbook | 7a5a1b8475ff759880ec386bd5b8011f8558abb3 | [
"MIT"
] | null | null | null | ---
title: "Different Tax Types Respond Differently to the Business Cycle"
subtitle: "Annual Percent Change in Tax Collections by Tax Type, North Carolina State Government (1951-2014)"
chart: 1-5.png
chart_layout: wide
---
Revenue stability over the business cycle is an important facet of state tax policy. Different types of taxes react differently to changes in the economy. In North Carolina, corporate income taxes fluctuate the most, exhibiting pronounced year-to-year changes in collections over the past twenty years.
> Source: Census Bureau, *State Government Tax Collections*.
| 58.8 | 302 | 0.79932 | eng_Latn | 0.994765 |
9ae6c01b82655ed43c591608ef1cd21a2b80d3b9 | 4,126 | md | Markdown | README.md | k0nG/ngx-order-pipe | 8385dc6d9f0d5a874ce2b867838e689a0fdebdf7 | [
"MIT"
] | null | null | null | README.md | k0nG/ngx-order-pipe | 8385dc6d9f0d5a874ce2b867838e689a0fdebdf7 | [
"MIT"
] | 1 | 2022-03-02T04:10:49.000Z | 2022-03-02T04:10:49.000Z | README.md | pranav550/AngularCustomOrderBy | 277ab73b34e655f4792bc21cb4f8788ecaaf509d | [
"MIT"
] | null | null | null | # Angular 5+ Order Pipe [](https://travis-ci.org/VadimDez/ngx-order-pipe)   [](https://deepscan.io/dashboard/#view=project&pid=1752&bid=7519)
> Order your collection by a field
<img src="https://cloud.githubusercontent.com/assets/3748453/22164327/08764608-df57-11e6-9c90-075aeca26fd6.gif" width="300">
### Demo page
[https://vadimdez.github.io/ngx-order-pipe/](https://vadimdez.github.io/ngx-order-pipe/)
or see code example
[https://stackblitz.com/edit/ngx-order-pipe](https://stackblitz.com/edit/ngx-order-pipe?embed=1&file=app/app.component.ts)
## Install
```
npm install ngx-order-pipe --save
```
*For Angular lower than 5 use version `1.1.3`*
## Setup
In case you're using `systemjs` - see configuration [here](https://github.com/VadimDez/ngx-order-pipe/blob/master/SYSTEMJS.md). Otherwise skip this part.
## Usage
##### In HTML template
```html
{{ collection | orderBy: expression : reverse : caseInsensitive : comparator }}
```
### Arguments
| Param | Type | Default Value | Details |
| --- | --- | --- | --- |
| collection | `array` or `object` | | The collection or object to sort |
| expression | `string` or `string array` | | The key or collection of keys to determinate order |
| reverse *(optional)* | `boolean`| false | Reverse sorting order |
| caseInsensitive *(optional)* | `boolean`| false | Case insensitive compare for sorting |
| comparator *(optional)* | `Function`| | Custom comparator function to determine order of value pairs. Example: `(a, b) => { return a > b ? 1 : -1; }` [`See how to use comparator`](https://github.com/VadimDez/ngx-order-pipe/issues/39) |
<br/>
Import `OrderModule` to your module
```typescript
import { NgModule } from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';
import { AppComponent } from './app';
import { OrderModule } from 'ngx-order-pipe';
@NgModule({
imports: [BrowserModule, OrderModule],
declarations: [AppComponent],
bootstrap: [AppComponent]
})
export class AppModule {}
```
And use pipe in your component
```typescript
import { Component } from '@angular/core';
@Component({
selector: 'example',
template: `
<ul>
<li *ngFor="let item of array | orderBy: order">
{{ item.name }}
</li>
</ul>
`
})
export class AppComponent {
array: any[] = [{ name: 'John'} , { name: 'Mary' }, { name: 'Adam' }];
order: string = 'name';
}
```
### Deep sorting
Use dot separated path for deep properties when passing object.
```html
<div>{{ { prop: { list: [3, 2, 1] } } | orderBy: 'prop.list' | json }}</div>
```
Result:
```html
<div>{ prop: { list: [1, 2, 3] } }</div>
```
### Use OrderPipe in the component
Import `OrderPipe` to your component:
```typescript
import { OrderPipe } from 'ngx-order-pipe';
```
Add `OrderPipe` to the constructor of your component and you're ready to use it:
```typescript
constructor(private orderPipe: OrderPipe) {
console.log(this.orderPipe.transform(this.array, this.order)); // both this.array and this.order are from above example AppComponent
}
```
### Case insensitive / Case sensitive
Case insensitive flag is the *third* parameter passed to the pipe. Can be `true` to make comparison *case insensitive* and `false` to make comparison case sensitive.
By default value is set to false.
* Make case insensitive order (Third parameter is `true`)
```html
<li *ngFor="let item of array | orderBy: order : false : true">
{{ item.name }}
</li>
```
* Switching third parameter to `false` will do case sensitive comparison to order collection:
```html
<li *ngFor="let item of array | orderBy: order : false : false">
{{ item.name }}
</li>
```
## License
[MIT](https://tldrlegal.com/license/mit-license) © [Vadym Yatsyuk](https://github.com/vadimdez)
| 32.234375 | 523 | 0.687833 | eng_Latn | 0.568101 |
9ae7258b0a316f320c713bb582abc534b2f442fa | 32,100 | md | Markdown | sdk/resourcemanager/botservice/armbotservice/CHANGELOG.md | v-andreaco/azure-sdk-for-go | 74fb5f9343822dc0c001bc5f98b909a5de7d8c26 | [
"MIT"
] | null | null | null | sdk/resourcemanager/botservice/armbotservice/CHANGELOG.md | v-andreaco/azure-sdk-for-go | 74fb5f9343822dc0c001bc5f98b909a5de7d8c26 | [
"MIT"
] | null | null | null | sdk/resourcemanager/botservice/armbotservice/CHANGELOG.md | v-andreaco/azure-sdk-for-go | 74fb5f9343822dc0c001bc5f98b909a5de7d8c26 | [
"MIT"
] | null | null | null | # Release History
## 0.2.1 (2022-02-22)
### Other Changes
- Remove the go_mod_tidy_hack.go file.
## 0.2.0 (2022-01-13)
### Breaking Changes
- Function `*ChannelsClient.Update` parameter(s) have been changed from `(context.Context, string, string, ChannelName, BotChannel, *ChannelsUpdateOptions)` to `(context.Context, string, string, ChannelName, BotChannel, *ChannelsClientUpdateOptions)`
- Function `*ChannelsClient.Update` return value(s) have been changed from `(ChannelsUpdateResponse, error)` to `(ChannelsClientUpdateResponse, error)`
- Function `*ChannelsClient.Create` parameter(s) have been changed from `(context.Context, string, string, ChannelName, BotChannel, *ChannelsCreateOptions)` to `(context.Context, string, string, ChannelName, BotChannel, *ChannelsClientCreateOptions)`
- Function `*ChannelsClient.Create` return value(s) have been changed from `(ChannelsCreateResponse, error)` to `(ChannelsClientCreateResponse, error)`
- Function `*BotsClient.List` parameter(s) have been changed from `(*BotsListOptions)` to `(*BotsClientListOptions)`
- Function `*BotsClient.List` return value(s) have been changed from `(*BotsListPager)` to `(*BotsClientListPager)`
- Function `*OperationsClient.List` parameter(s) have been changed from `(*OperationsListOptions)` to `(*OperationsClientListOptions)`
- Function `*OperationsClient.List` return value(s) have been changed from `(*OperationsListPager)` to `(*OperationsClientListPager)`
- Function `*BotConnectionClient.ListByBotService` parameter(s) have been changed from `(string, string, *BotConnectionListByBotServiceOptions)` to `(string, string, *BotConnectionClientListByBotServiceOptions)`
- Function `*BotConnectionClient.ListByBotService` return value(s) have been changed from `(*BotConnectionListByBotServicePager)` to `(*BotConnectionClientListByBotServicePager)`
- Function `*PrivateEndpointConnectionsClient.Delete` parameter(s) have been changed from `(context.Context, string, string, string, *PrivateEndpointConnectionsDeleteOptions)` to `(context.Context, string, string, string, *PrivateEndpointConnectionsClientDeleteOptions)`
- Function `*PrivateEndpointConnectionsClient.Delete` return value(s) have been changed from `(PrivateEndpointConnectionsDeleteResponse, error)` to `(PrivateEndpointConnectionsClientDeleteResponse, error)`
- Function `*ChannelsClient.ListWithKeys` parameter(s) have been changed from `(context.Context, string, string, ChannelName, *ChannelsListWithKeysOptions)` to `(context.Context, string, string, ChannelName, *ChannelsClientListWithKeysOptions)`
- Function `*ChannelsClient.ListWithKeys` return value(s) have been changed from `(ChannelsListWithKeysResponse, error)` to `(ChannelsClientListWithKeysResponse, error)`
- Function `*ChannelsClient.ListByResourceGroup` parameter(s) have been changed from `(string, string, *ChannelsListByResourceGroupOptions)` to `(string, string, *ChannelsClientListByResourceGroupOptions)`
- Function `*ChannelsClient.ListByResourceGroup` return value(s) have been changed from `(*ChannelsListByResourceGroupPager)` to `(*ChannelsClientListByResourceGroupPager)`
- Function `*BotsClient.GetCheckNameAvailability` parameter(s) have been changed from `(context.Context, CheckNameAvailabilityRequestBody, *BotsGetCheckNameAvailabilityOptions)` to `(context.Context, CheckNameAvailabilityRequestBody, *BotsClientGetCheckNameAvailabilityOptions)`
- Function `*BotsClient.GetCheckNameAvailability` return value(s) have been changed from `(BotsGetCheckNameAvailabilityResponse, error)` to `(BotsClientGetCheckNameAvailabilityResponse, error)`
- Function `*BotConnectionClient.ListServiceProviders` parameter(s) have been changed from `(context.Context, *BotConnectionListServiceProvidersOptions)` to `(context.Context, *BotConnectionClientListServiceProvidersOptions)`
- Function `*BotConnectionClient.ListServiceProviders` return value(s) have been changed from `(BotConnectionListServiceProvidersResponse, error)` to `(BotConnectionClientListServiceProvidersResponse, error)`
- Function `*PrivateEndpointConnectionsClient.List` parameter(s) have been changed from `(context.Context, string, string, *PrivateEndpointConnectionsListOptions)` to `(context.Context, string, string, *PrivateEndpointConnectionsClientListOptions)`
- Function `*PrivateEndpointConnectionsClient.List` return value(s) have been changed from `(PrivateEndpointConnectionsListResponse, error)` to `(PrivateEndpointConnectionsClientListResponse, error)`
- Function `*PrivateLinkResourcesClient.ListByBotResource` parameter(s) have been changed from `(context.Context, string, string, *PrivateLinkResourcesListByBotResourceOptions)` to `(context.Context, string, string, *PrivateLinkResourcesClientListByBotResourceOptions)`
- Function `*PrivateLinkResourcesClient.ListByBotResource` return value(s) have been changed from `(PrivateLinkResourcesListByBotResourceResponse, error)` to `(PrivateLinkResourcesClientListByBotResourceResponse, error)`
- Function `*BotsClient.ListByResourceGroup` parameter(s) have been changed from `(string, *BotsListByResourceGroupOptions)` to `(string, *BotsClientListByResourceGroupOptions)`
- Function `*BotsClient.ListByResourceGroup` return value(s) have been changed from `(*BotsListByResourceGroupPager)` to `(*BotsClientListByResourceGroupPager)`
- Function `*PrivateEndpointConnectionsClient.Create` parameter(s) have been changed from `(context.Context, string, string, string, PrivateEndpointConnection, *PrivateEndpointConnectionsCreateOptions)` to `(context.Context, string, string, string, PrivateEndpointConnection, *PrivateEndpointConnectionsClientCreateOptions)`
- Function `*PrivateEndpointConnectionsClient.Create` return value(s) have been changed from `(PrivateEndpointConnectionsCreateResponse, error)` to `(PrivateEndpointConnectionsClientCreateResponse, error)`
- Function `*BotsClient.Create` parameter(s) have been changed from `(context.Context, string, string, Bot, *BotsCreateOptions)` to `(context.Context, string, string, Bot, *BotsClientCreateOptions)`
- Function `*BotsClient.Create` return value(s) have been changed from `(BotsCreateResponse, error)` to `(BotsClientCreateResponse, error)`
- Function `*HostSettingsClient.Get` parameter(s) have been changed from `(context.Context, *HostSettingsGetOptions)` to `(context.Context, *HostSettingsClientGetOptions)`
- Function `*HostSettingsClient.Get` return value(s) have been changed from `(HostSettingsGetResponse, error)` to `(HostSettingsClientGetResponse, error)`
- Function `*BotsClient.Update` parameter(s) have been changed from `(context.Context, string, string, Bot, *BotsUpdateOptions)` to `(context.Context, string, string, Bot, *BotsClientUpdateOptions)`
- Function `*BotsClient.Update` return value(s) have been changed from `(BotsUpdateResponse, error)` to `(BotsClientUpdateResponse, error)`
- Function `*OperationResultsClient.BeginGet` parameter(s) have been changed from `(context.Context, string, *OperationResultsBeginGetOptions)` to `(context.Context, string, *OperationResultsClientBeginGetOptions)`
- Function `*OperationResultsClient.BeginGet` return value(s) have been changed from `(OperationResultsGetPollerResponse, error)` to `(OperationResultsClientGetPollerResponse, error)`
- Function `*ChannelsClient.Get` parameter(s) have been changed from `(context.Context, string, string, string, *ChannelsGetOptions)` to `(context.Context, string, string, string, *ChannelsClientGetOptions)`
- Function `*ChannelsClient.Get` return value(s) have been changed from `(ChannelsGetResponse, error)` to `(ChannelsClientGetResponse, error)`
- Function `*BotsClient.Delete` parameter(s) have been changed from `(context.Context, string, string, *BotsDeleteOptions)` to `(context.Context, string, string, *BotsClientDeleteOptions)`
- Function `*BotsClient.Delete` return value(s) have been changed from `(BotsDeleteResponse, error)` to `(BotsClientDeleteResponse, error)`
- Function `*ChannelsClient.Delete` parameter(s) have been changed from `(context.Context, string, string, string, *ChannelsDeleteOptions)` to `(context.Context, string, string, string, *ChannelsClientDeleteOptions)`
- Function `*ChannelsClient.Delete` return value(s) have been changed from `(ChannelsDeleteResponse, error)` to `(ChannelsClientDeleteResponse, error)`
- Function `*BotConnectionClient.Create` parameter(s) have been changed from `(context.Context, string, string, string, ConnectionSetting, *BotConnectionCreateOptions)` to `(context.Context, string, string, string, ConnectionSetting, *BotConnectionClientCreateOptions)`
- Function `*BotConnectionClient.Create` return value(s) have been changed from `(BotConnectionCreateResponse, error)` to `(BotConnectionClientCreateResponse, error)`
- Function `*BotConnectionClient.ListWithSecrets` parameter(s) have been changed from `(context.Context, string, string, string, *BotConnectionListWithSecretsOptions)` to `(context.Context, string, string, string, *BotConnectionClientListWithSecretsOptions)`
- Function `*BotConnectionClient.ListWithSecrets` return value(s) have been changed from `(BotConnectionListWithSecretsResponse, error)` to `(BotConnectionClientListWithSecretsResponse, error)`
- Function `*DirectLineClient.RegenerateKeys` parameter(s) have been changed from `(context.Context, string, string, RegenerateKeysChannelName, SiteInfo, *DirectLineRegenerateKeysOptions)` to `(context.Context, string, string, RegenerateKeysChannelName, SiteInfo, *DirectLineClientRegenerateKeysOptions)`
- Function `*DirectLineClient.RegenerateKeys` return value(s) have been changed from `(DirectLineRegenerateKeysResponse, error)` to `(DirectLineClientRegenerateKeysResponse, error)`
- Function `*BotsClient.Get` parameter(s) have been changed from `(context.Context, string, string, *BotsGetOptions)` to `(context.Context, string, string, *BotsClientGetOptions)`
- Function `*BotsClient.Get` return value(s) have been changed from `(BotsGetResponse, error)` to `(BotsClientGetResponse, error)`
- Function `*PrivateEndpointConnectionsClient.Get` parameter(s) have been changed from `(context.Context, string, string, string, *PrivateEndpointConnectionsGetOptions)` to `(context.Context, string, string, string, *PrivateEndpointConnectionsClientGetOptions)`
- Function `*PrivateEndpointConnectionsClient.Get` return value(s) have been changed from `(PrivateEndpointConnectionsGetResponse, error)` to `(PrivateEndpointConnectionsClientGetResponse, error)`
- Function `*BotConnectionClient.Update` parameter(s) have been changed from `(context.Context, string, string, string, ConnectionSetting, *BotConnectionUpdateOptions)` to `(context.Context, string, string, string, ConnectionSetting, *BotConnectionClientUpdateOptions)`
- Function `*BotConnectionClient.Update` return value(s) have been changed from `(BotConnectionUpdateResponse, error)` to `(BotConnectionClientUpdateResponse, error)`
- Function `*BotConnectionClient.Get` parameter(s) have been changed from `(context.Context, string, string, string, *BotConnectionGetOptions)` to `(context.Context, string, string, string, *BotConnectionClientGetOptions)`
- Function `*BotConnectionClient.Get` return value(s) have been changed from `(BotConnectionGetResponse, error)` to `(BotConnectionClientGetResponse, error)`
- Function `*BotConnectionClient.Delete` parameter(s) have been changed from `(context.Context, string, string, string, *BotConnectionDeleteOptions)` to `(context.Context, string, string, string, *BotConnectionClientDeleteOptions)`
- Function `*BotConnectionClient.Delete` return value(s) have been changed from `(BotConnectionDeleteResponse, error)` to `(BotConnectionClientDeleteResponse, error)`
- Function `*Bot.UnmarshalJSON` has been removed
- Function `*BotsListPager.Err` has been removed
- Function `*BotsListPager.NextPage` has been removed
- Function `*BotConnectionListByBotServicePager.NextPage` has been removed
- Function `*BotConnectionListByBotServicePager.Err` has been removed
- Function `*OperationsListPager.NextPage` has been removed
- Function `*OperationsListPager.PageResponse` has been removed
- Function `*ConnectionSetting.UnmarshalJSON` has been removed
- Function `*ChannelsListByResourceGroupPager.PageResponse` has been removed
- Function `*BotsListByResourceGroupPager.Err` has been removed
- Function `*BotsListByResourceGroupPager.NextPage` has been removed
- Function `*ChannelsListByResourceGroupPager.Err` has been removed
- Function `*OperationsListPager.Err` has been removed
- Function `*Channel.UnmarshalJSON` has been removed
- Function `Error.Error` has been removed
- Function `*OperationResultsGetPoller.FinalResponse` has been removed
- Function `*OperationResultsGetPollerResponse.Resume` has been removed
- Function `*Resource.UnmarshalJSON` has been removed
- Function `*OperationResultsGetPoller.Done` has been removed
- Function `*BotsListPager.PageResponse` has been removed
- Function `*OperationResultsGetPoller.Poll` has been removed
- Function `*OperationResultsGetPoller.ResumeToken` has been removed
- Function `*BotsListByResourceGroupPager.PageResponse` has been removed
- Function `*BotConnectionListByBotServicePager.PageResponse` has been removed
- Function `*ChannelsListByResourceGroupPager.NextPage` has been removed
- Function `OperationResultsGetPollerResponse.PollUntilDone` has been removed
- Struct `BotConnectionCreateOptions` has been removed
- Struct `BotConnectionCreateResponse` has been removed
- Struct `BotConnectionCreateResult` has been removed
- Struct `BotConnectionDeleteOptions` has been removed
- Struct `BotConnectionDeleteResponse` has been removed
- Struct `BotConnectionGetOptions` has been removed
- Struct `BotConnectionGetResponse` has been removed
- Struct `BotConnectionGetResult` has been removed
- Struct `BotConnectionListByBotServiceOptions` has been removed
- Struct `BotConnectionListByBotServicePager` has been removed
- Struct `BotConnectionListByBotServiceResponse` has been removed
- Struct `BotConnectionListByBotServiceResult` has been removed
- Struct `BotConnectionListServiceProvidersOptions` has been removed
- Struct `BotConnectionListServiceProvidersResponse` has been removed
- Struct `BotConnectionListServiceProvidersResult` has been removed
- Struct `BotConnectionListWithSecretsOptions` has been removed
- Struct `BotConnectionListWithSecretsResponse` has been removed
- Struct `BotConnectionListWithSecretsResult` has been removed
- Struct `BotConnectionUpdateOptions` has been removed
- Struct `BotConnectionUpdateResponse` has been removed
- Struct `BotConnectionUpdateResult` has been removed
- Struct `BotsCreateOptions` has been removed
- Struct `BotsCreateResponse` has been removed
- Struct `BotsCreateResult` has been removed
- Struct `BotsDeleteOptions` has been removed
- Struct `BotsDeleteResponse` has been removed
- Struct `BotsGetCheckNameAvailabilityOptions` has been removed
- Struct `BotsGetCheckNameAvailabilityResponse` has been removed
- Struct `BotsGetCheckNameAvailabilityResult` has been removed
- Struct `BotsGetOptions` has been removed
- Struct `BotsGetResponse` has been removed
- Struct `BotsGetResult` has been removed
- Struct `BotsListByResourceGroupOptions` has been removed
- Struct `BotsListByResourceGroupPager` has been removed
- Struct `BotsListByResourceGroupResponse` has been removed
- Struct `BotsListByResourceGroupResult` has been removed
- Struct `BotsListOptions` has been removed
- Struct `BotsListPager` has been removed
- Struct `BotsListResponse` has been removed
- Struct `BotsListResult` has been removed
- Struct `BotsUpdateOptions` has been removed
- Struct `BotsUpdateResponse` has been removed
- Struct `BotsUpdateResult` has been removed
- Struct `ChannelsCreateOptions` has been removed
- Struct `ChannelsCreateResponse` has been removed
- Struct `ChannelsCreateResult` has been removed
- Struct `ChannelsDeleteOptions` has been removed
- Struct `ChannelsDeleteResponse` has been removed
- Struct `ChannelsGetOptions` has been removed
- Struct `ChannelsGetResponse` has been removed
- Struct `ChannelsGetResult` has been removed
- Struct `ChannelsListByResourceGroupOptions` has been removed
- Struct `ChannelsListByResourceGroupPager` has been removed
- Struct `ChannelsListByResourceGroupResponse` has been removed
- Struct `ChannelsListByResourceGroupResult` has been removed
- Struct `ChannelsListWithKeysOptions` has been removed
- Struct `ChannelsListWithKeysResponse` has been removed
- Struct `ChannelsListWithKeysResult` has been removed
- Struct `ChannelsUpdateOptions` has been removed
- Struct `ChannelsUpdateResponse` has been removed
- Struct `ChannelsUpdateResult` has been removed
- Struct `DirectLineRegenerateKeysOptions` has been removed
- Struct `DirectLineRegenerateKeysResponse` has been removed
- Struct `DirectLineRegenerateKeysResult` has been removed
- Struct `HostSettingsGetOptions` has been removed
- Struct `HostSettingsGetResponse` has been removed
- Struct `HostSettingsGetResult` has been removed
- Struct `OperationResultsBeginGetOptions` has been removed
- Struct `OperationResultsGetPoller` has been removed
- Struct `OperationResultsGetPollerResponse` has been removed
- Struct `OperationResultsGetResponse` has been removed
- Struct `OperationResultsGetResult` has been removed
- Struct `OperationsListOptions` has been removed
- Struct `OperationsListPager` has been removed
- Struct `OperationsListResponse` has been removed
- Struct `OperationsListResult` has been removed
- Struct `PrivateEndpointConnectionsCreateOptions` has been removed
- Struct `PrivateEndpointConnectionsCreateResponse` has been removed
- Struct `PrivateEndpointConnectionsCreateResult` has been removed
- Struct `PrivateEndpointConnectionsDeleteOptions` has been removed
- Struct `PrivateEndpointConnectionsDeleteResponse` has been removed
- Struct `PrivateEndpointConnectionsGetOptions` has been removed
- Struct `PrivateEndpointConnectionsGetResponse` has been removed
- Struct `PrivateEndpointConnectionsGetResult` has been removed
- Struct `PrivateEndpointConnectionsListOptions` has been removed
- Struct `PrivateEndpointConnectionsListResponse` has been removed
- Struct `PrivateEndpointConnectionsListResult` has been removed
- Struct `PrivateLinkResourcesListByBotResourceOptions` has been removed
- Struct `PrivateLinkResourcesListByBotResourceResponse` has been removed
- Struct `PrivateLinkResourcesListByBotResourceResult` has been removed
- Field `Channel` of struct `KikChannel` has been removed
- Field `Channel` of struct `SmsChannel` has been removed
- Field `Channel` of struct `MsTeamsChannel` has been removed
- Field `IsIsolated` of struct `BotProperties` has been removed
- Field `Channel` of struct `LineChannel` has been removed
- Field `Channel` of struct `WebChatChannel` has been removed
- Field `Channel` of struct `FacebookChannel` has been removed
- Field `Channel` of struct `AlexaChannel` has been removed
- Field `Resource` of struct `Bot` has been removed
- Field `PrivateLinkResourceBase` of struct `PrivateLinkResource` has been removed
- Field `PrivateLinkResourceBase` of struct `PrivateEndpointConnection` has been removed
- Field `Resource` of struct `BotChannel` has been removed
- Field `Channel` of struct `TelegramChannel` has been removed
- Field `Channel` of struct `EmailChannel` has been removed
- Field `Channel` of struct `SlackChannel` has been removed
- Field `Channel` of struct `DirectLineChannel` has been removed
- Field `Channel` of struct `DirectLineSpeechChannel` has been removed
- Field `Resource` of struct `ConnectionSetting` has been removed
- Field `Channel` of struct `SkypeChannel` has been removed
- Field `InnerError` of struct `Error` has been removed
### Features Added
- New const `PublicNetworkAccessEnabled`
- New const `PublicNetworkAccessDisabled`
- New function `*OperationsClientListPager.Err() error`
- New function `*SmsChannel.GetChannel() *Channel`
- New function `*OperationResultsClientGetPollerResponse.Resume(context.Context, *OperationResultsClient, string) error`
- New function `*ChannelsClientListByResourceGroupPager.NextPage(context.Context) bool`
- New function `OperationResultsClientGetPollerResponse.PollUntilDone(context.Context, time.Duration) (OperationResultsClientGetResponse, error)`
- New function `*BotsClientListPager.PageResponse() BotsClientListResponse`
- New function `*AlexaChannel.GetChannel() *Channel`
- New function `*FacebookChannel.GetChannel() *Channel`
- New function `*BotConnectionClientListByBotServicePager.NextPage(context.Context) bool`
- New function `*OperationResultsClientGetPoller.FinalResponse(context.Context) (OperationResultsClientGetResponse, error)`
- New function `*BotsClientListByResourceGroupPager.Err() error`
- New function `*OperationResultsClientGetPoller.Poll(context.Context) (*http.Response, error)`
- New function `*BotConnectionClientListByBotServicePager.Err() error`
- New function `PossiblePublicNetworkAccessValues() []PublicNetworkAccess`
- New function `*WebChatChannel.GetChannel() *Channel`
- New function `*ChannelsClientListByResourceGroupPager.PageResponse() ChannelsClientListByResourceGroupResponse`
- New function `*BotConnectionClientListByBotServicePager.PageResponse() BotConnectionClientListByBotServiceResponse`
- New function `*BotsClientListPager.Err() error`
- New function `*ChannelsClientListByResourceGroupPager.Err() error`
- New function `*DirectLineSpeechChannel.GetChannel() *Channel`
- New function `*LineChannel.GetChannel() *Channel`
- New function `*OperationsClientListPager.PageResponse() OperationsClientListResponse`
- New function `*OperationResultsClientGetPoller.ResumeToken() (string, error)`
- New function `*ListChannelWithKeysResponse.UnmarshalJSON([]byte) error`
- New function `*OperationResultsClientGetPoller.Done() bool`
- New function `*BotsClientListPager.NextPage(context.Context) bool`
- New function `*SkypeChannel.GetChannel() *Channel`
- New function `Site.MarshalJSON() ([]byte, error)`
- New function `*SlackChannel.GetChannel() *Channel`
- New function `PublicNetworkAccess.ToPtr() *PublicNetworkAccess`
- New function `ListChannelWithKeysResponse.MarshalJSON() ([]byte, error)`
- New function `*OperationsClientListPager.NextPage(context.Context) bool`
- New function `*DirectLineChannel.GetChannel() *Channel`
- New function `*TelegramChannel.GetChannel() *Channel`
- New function `*KikChannel.GetChannel() *Channel`
- New function `*EmailChannel.GetChannel() *Channel`
- New function `*MsTeamsChannel.GetChannel() *Channel`
- New function `*BotsClientListByResourceGroupPager.NextPage(context.Context) bool`
- New function `*BotsClientListByResourceGroupPager.PageResponse() BotsClientListByResourceGroupResponse`
- New function `ChannelSettings.MarshalJSON() ([]byte, error)`
- New struct `BotConnectionClientCreateOptions`
- New struct `BotConnectionClientCreateResponse`
- New struct `BotConnectionClientCreateResult`
- New struct `BotConnectionClientDeleteOptions`
- New struct `BotConnectionClientDeleteResponse`
- New struct `BotConnectionClientGetOptions`
- New struct `BotConnectionClientGetResponse`
- New struct `BotConnectionClientGetResult`
- New struct `BotConnectionClientListByBotServiceOptions`
- New struct `BotConnectionClientListByBotServicePager`
- New struct `BotConnectionClientListByBotServiceResponse`
- New struct `BotConnectionClientListByBotServiceResult`
- New struct `BotConnectionClientListServiceProvidersOptions`
- New struct `BotConnectionClientListServiceProvidersResponse`
- New struct `BotConnectionClientListServiceProvidersResult`
- New struct `BotConnectionClientListWithSecretsOptions`
- New struct `BotConnectionClientListWithSecretsResponse`
- New struct `BotConnectionClientListWithSecretsResult`
- New struct `BotConnectionClientUpdateOptions`
- New struct `BotConnectionClientUpdateResponse`
- New struct `BotConnectionClientUpdateResult`
- New struct `BotsClientCreateOptions`
- New struct `BotsClientCreateResponse`
- New struct `BotsClientCreateResult`
- New struct `BotsClientDeleteOptions`
- New struct `BotsClientDeleteResponse`
- New struct `BotsClientGetCheckNameAvailabilityOptions`
- New struct `BotsClientGetCheckNameAvailabilityResponse`
- New struct `BotsClientGetCheckNameAvailabilityResult`
- New struct `BotsClientGetOptions`
- New struct `BotsClientGetResponse`
- New struct `BotsClientGetResult`
- New struct `BotsClientListByResourceGroupOptions`
- New struct `BotsClientListByResourceGroupPager`
- New struct `BotsClientListByResourceGroupResponse`
- New struct `BotsClientListByResourceGroupResult`
- New struct `BotsClientListOptions`
- New struct `BotsClientListPager`
- New struct `BotsClientListResponse`
- New struct `BotsClientListResult`
- New struct `BotsClientUpdateOptions`
- New struct `BotsClientUpdateResponse`
- New struct `BotsClientUpdateResult`
- New struct `ChannelSettings`
- New struct `ChannelsClientCreateOptions`
- New struct `ChannelsClientCreateResponse`
- New struct `ChannelsClientCreateResult`
- New struct `ChannelsClientDeleteOptions`
- New struct `ChannelsClientDeleteResponse`
- New struct `ChannelsClientGetOptions`
- New struct `ChannelsClientGetResponse`
- New struct `ChannelsClientGetResult`
- New struct `ChannelsClientListByResourceGroupOptions`
- New struct `ChannelsClientListByResourceGroupPager`
- New struct `ChannelsClientListByResourceGroupResponse`
- New struct `ChannelsClientListByResourceGroupResult`
- New struct `ChannelsClientListWithKeysOptions`
- New struct `ChannelsClientListWithKeysResponse`
- New struct `ChannelsClientListWithKeysResult`
- New struct `ChannelsClientUpdateOptions`
- New struct `ChannelsClientUpdateResponse`
- New struct `ChannelsClientUpdateResult`
- New struct `DirectLineClientRegenerateKeysOptions`
- New struct `DirectLineClientRegenerateKeysResponse`
- New struct `DirectLineClientRegenerateKeysResult`
- New struct `HostSettingsClientGetOptions`
- New struct `HostSettingsClientGetResponse`
- New struct `HostSettingsClientGetResult`
- New struct `ListChannelWithKeysResponse`
- New struct `OperationResultsClientBeginGetOptions`
- New struct `OperationResultsClientGetPoller`
- New struct `OperationResultsClientGetPollerResponse`
- New struct `OperationResultsClientGetResponse`
- New struct `OperationResultsClientGetResult`
- New struct `OperationsClientListOptions`
- New struct `OperationsClientListPager`
- New struct `OperationsClientListResponse`
- New struct `OperationsClientListResult`
- New struct `PrivateEndpointConnectionsClientCreateOptions`
- New struct `PrivateEndpointConnectionsClientCreateResponse`
- New struct `PrivateEndpointConnectionsClientCreateResult`
- New struct `PrivateEndpointConnectionsClientDeleteOptions`
- New struct `PrivateEndpointConnectionsClientDeleteResponse`
- New struct `PrivateEndpointConnectionsClientGetOptions`
- New struct `PrivateEndpointConnectionsClientGetResponse`
- New struct `PrivateEndpointConnectionsClientGetResult`
- New struct `PrivateEndpointConnectionsClientListOptions`
- New struct `PrivateEndpointConnectionsClientListResponse`
- New struct `PrivateEndpointConnectionsClientListResult`
- New struct `PrivateLinkResourcesClientListByBotResourceOptions`
- New struct `PrivateLinkResourcesClientListByBotResourceResponse`
- New struct `PrivateLinkResourcesClientListByBotResourceResult`
- New struct `ServiceProviderParameterMetadata`
- New struct `ServiceProviderParameterMetadataConstraints`
- New struct `Site`
- New field `Location` in struct `Channel`
- New field `ProvisioningState` in struct `Channel`
- New field `Location` in struct `TelegramChannel`
- New field `ChannelName` in struct `TelegramChannel`
- New field `Etag` in struct `TelegramChannel`
- New field `Etag` in struct `DirectLineChannel`
- New field `Location` in struct `DirectLineChannel`
- New field `ChannelName` in struct `DirectLineChannel`
- New field `Location` in struct `KikChannel`
- New field `ProvisioningState` in struct `KikChannel`
- New field `ChannelName` in struct `KikChannel`
- New field `Etag` in struct `KikChannel`
- New field `Etag` in struct `LineChannel`
- New field `Location` in struct `LineChannel`
- New field `ProvisioningState` in struct `LineChannel`
- New field `ChannelName` in struct `LineChannel`
- New field `ChannelName` in struct `EmailChannel`
- New field `Etag` in struct `EmailChannel`
- New field `Location` in struct `EmailChannel`
- New field `IsStreamingSupported` in struct `BotProperties`
- New field `CmekEncryptionStatus` in struct `BotProperties`
- New field `Parameters` in struct `BotProperties`
- New field `ProvisioningState` in struct `BotProperties`
- New field `PublishingCredentials` in struct `BotProperties`
- New field `PublicNetworkAccess` in struct `BotProperties`
- New field `AllSettings` in struct `BotProperties`
- New field `StorageResourceID` in struct `BotProperties`
- New field `ManifestURL` in struct `BotProperties`
- New field `ChannelName` in struct `AlexaChannel`
- New field `Etag` in struct `AlexaChannel`
- New field `Location` in struct `AlexaChannel`
- New field `ProvisioningState` in struct `AlexaChannel`
- New field `AcceptedTerms` in struct `MsTeamsChannelProperties`
- New field `DeploymentEnvironment` in struct `MsTeamsChannelProperties`
- New field `ProvisioningState` in struct `SkypeChannel`
- New field `ChannelName` in struct `SkypeChannel`
- New field `Etag` in struct `SkypeChannel`
- New field `Location` in struct `SkypeChannel`
- New field `ChannelName` in struct `MsTeamsChannel`
- New field `Etag` in struct `MsTeamsChannel`
- New field `Location` in struct `MsTeamsChannel`
- New field `Location` in struct `ConnectionSetting`
- New field `Tags` in struct `ConnectionSetting`
- New field `Type` in struct `ConnectionSetting`
- New field `SKU` in struct `ConnectionSetting`
- New field `ID` in struct `ConnectionSetting`
- New field `Zones` in struct `ConnectionSetting`
- New field `Kind` in struct `ConnectionSetting`
- New field `Etag` in struct `ConnectionSetting`
- New field `Name` in struct `ConnectionSetting`
- New field `ChannelName` in struct `SmsChannel`
- New field `Etag` in struct `SmsChannel`
- New field `Location` in struct `SmsChannel`
- New field `ProvisioningState` in struct `SmsChannel`
- New field `ProvisioningState` in struct `SlackChannel`
- New field `ChannelName` in struct `SlackChannel`
- New field `Etag` in struct `SlackChannel`
- New field `ChannelName` in struct `DirectLineSpeechChannel`
- New field `Etag` in struct `DirectLineSpeechChannel`
- New field `Location` in struct `DirectLineSpeechChannel`
- New field `Metadata` in struct `ServiceProviderParameter`
- New field `Location` in struct `Bot`
- New field `SKU` in struct `Bot`
- New field `Tags` in struct `Bot`
- New field `Type` in struct `Bot`
- New field `Kind` in struct `Bot`
- New field `Etag` in struct `Bot`
- New field `Zones` in struct `Bot`
- New field `ID` in struct `Bot`
- New field `Name` in struct `Bot`
- New field `Error` in struct `Error`
- New field `Tags` in struct `BotChannel`
- New field `Name` in struct `BotChannel`
- New field `Etag` in struct `BotChannel`
- New field `SKU` in struct `BotChannel`
- New field `Location` in struct `BotChannel`
- New field `ID` in struct `BotChannel`
- New field `Zones` in struct `BotChannel`
- New field `Type` in struct `BotChannel`
- New field `Kind` in struct `BotChannel`
- New field `Name` in struct `PrivateEndpointConnection`
- New field `Type` in struct `PrivateEndpointConnection`
- New field `ID` in struct `PrivateEndpointConnection`
- New field `ChannelName` in struct `FacebookChannel`
- New field `Etag` in struct `FacebookChannel`
- New field `ChannelName` in struct `WebChatChannel`
- New field `Etag` in struct `WebChatChannel`
- New field `ProvisioningState` in struct `WebChatChannel`
- New field `ID` in struct `PrivateLinkResource`
- New field `Name` in struct `PrivateLinkResource`
- New field `Type` in struct `PrivateLinkResource`
- New field `ID` in struct `ConnectionSettingProperties`
- New field `Name` in struct `ConnectionSettingProperties`
- New field `ProvisioningState` in struct `ConnectionSettingProperties`
## 0.1.0 (2021-11-16)
- Initial preview release.
| 72.134831 | 324 | 0.815421 | yue_Hant | 0.606308 |
9ae811aafb41fba94c35515136cf19af93b9ef20 | 109 | md | Markdown | README.md | Abhayakara/SecKeyDump | 2fb1aac30b9d4cb9407ae84b05c732ed5ade291b | [
"BSD-2-Clause"
] | null | null | null | README.md | Abhayakara/SecKeyDump | 2fb1aac30b9d4cb9407ae84b05c732ed5ade291b | [
"BSD-2-Clause"
] | null | null | null | README.md | Abhayakara/SecKeyDump | 2fb1aac30b9d4cb9407ae84b05c732ed5ade291b | [
"BSD-2-Clause"
] | 1 | 2019-02-03T19:56:26.000Z | 2019-02-03T19:56:26.000Z | # SecKeyDump
Stupid little app to generate a private key and dump it to hex using Apple's Security framework
| 36.333333 | 95 | 0.807339 | eng_Latn | 0.985042 |
9ae870f537b989d47971148b4edfd5f38bcc83c5 | 17,122 | md | Markdown | docs/deployment/server-and-client-configuration-issues-in-clickonce-deployments.md | Simran-B/visualstudio-docs.de-de | 0e81681be8dbccb2346866f432f541b97d819dac | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/deployment/server-and-client-configuration-issues-in-clickonce-deployments.md | Simran-B/visualstudio-docs.de-de | 0e81681be8dbccb2346866f432f541b97d819dac | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/deployment/server-and-client-configuration-issues-in-clickonce-deployments.md | Simran-B/visualstudio-docs.de-de | 0e81681be8dbccb2346866f432f541b97d819dac | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Probleme mit der Server-/Clientkonfiguration in ClickOnce-bereit Stellungen
ms.date: 11/04/2016
ms.topic: conceptual
dev_langs:
- VB
- CSharp
- C++
helpviewer_keywords:
- deploying applications, ClickOnce
- troubleshooting ClickOnce deployments
- ClickOnce deployment, troubleshooting
- Windows applications, ClickOnce deployments
ms.assetid: 929e5fcc-dd56-409c-bb57-00bd9549b20b
author: mikejo5000
ms.author: mikejo
manager: jillfra
ms.workload:
- multiple
ms.openlocfilehash: 794b53a71a0a8215ae6bc9af47f9fe2a0ff911b5
ms.sourcegitcommit: 8589d85cc10710ef87e6363a2effa5ee5610d46a
ms.translationtype: MT
ms.contentlocale: de-DE
ms.lasthandoff: 10/23/2019
ms.locfileid: "72806877"
---
# <a name="server-and-client-configuration-issues-in-clickonce-deployments"></a>Probleme mit der Server- und Clientkonfiguration in ClickOnce-Bereitstellungen
Wenn Sie Internetinformationsdienste (IIS) unter Windows Server verwenden und die Bereitstellung einen Dateityp enthält, den Windows nicht erkennt (z. b. eine Microsoft Word-Datei), lehnt IIS die Übertragung dieser Datei ab, und die Bereitstellung kann nicht erfolgreich ausgeführt werden.
Darüber hinaus enthalten einige Webserver und Webanwendungs Software, z. b. [!INCLUDE[vstecasp](../code-quality/includes/vstecasp_md.md)], eine Liste von Dateien und Dateitypen, die Sie nicht herunterladen können. Beispielsweise wird durch [!INCLUDE[vstecasp](../code-quality/includes/vstecasp_md.md)] verhindert, dass alle *Web. config* -Dateien heruntergeladen werden. Diese Dateien können vertrauliche Informationen enthalten, wie z. b. Benutzernamen und Kenn Wörter.
Obwohl diese Einschränkung keine Probleme beim Herunterladen von Kern [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] Dateien (z. b. Manifeste und Assemblys) verursachen sollte, kann diese Einschränkung verhindern, dass Sie Datendateien herunterladen, die als Teil ihrer [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] Anwendung enthalten In [!INCLUDE[vstecasp](../code-quality/includes/vstecasp_md.md)]können Sie diesen Fehler beheben, indem Sie den Handler entfernen, der das Herunterladen solcher Dateien aus dem IIS-Konfigurations-Manager untersagt. Weitere Informationen finden Sie in der Dokumentation zum IIS-Server.
Einige Webserver blockieren möglicherweise Dateien mit Erweiterungen wie " *. dll*", " *. config*" und " *. mdf*". Windows-basierte Anwendungen enthalten in der Regel Dateien mit einigen dieser Erweiterungen. Wenn ein Benutzer versucht, eine [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] Anwendung auszuführen, die auf eine blockierte Datei auf einem Webserver zugreift, führt dies zu einem Fehler. Anstatt alle Dateierweiterungen zu entsperren, veröffentlicht [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] jede Anwendungsdatei standardmäßig mit einer Dateierweiterung *.* Daher muss der Administrator den Webserver nur so konfigurieren, dass die Blockierung der folgenden drei Dateierweiterungen blockiert wird:
- *.application*
- *.manifest*
- *.deploy*
Sie können diese Option jedoch deaktivieren, indem Sie im [Dialog Feld "Veröffentlichungs Optionen](/previous-versions/visualstudio/visual-studio-2010/7z83t16a(v=vs.100))" die Option **". Bereitstellungs Dateierweiterung verwenden** " deaktivieren. in diesem Fall müssen Sie den Webserver so konfigurieren, dass alle in der Anwendung verwendeten Dateierweiterungen entsperrt werden.
Sie müssen die *. Manifest*-, *Application*-und *.* -Bereitstellung konfigurieren, z. b. Wenn Sie IIS verwenden, bei dem Sie die .NET Framework nicht installiert haben, oder wenn Sie einen anderen Webserver (z. b. Apache) verwenden.
## <a name="clickonce-and-secure-sockets-layer-ssl"></a>ClickOnce und Secure Sockets Layer (SSL)
Eine [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] Anwendung funktioniert problemlos über SSL, außer wenn Internet Explorer eine Aufforderung zum SSL-Zertifikat auslöst. Die Eingabeaufforderung kann ausgelöst werden, wenn ein Problem mit dem Zertifikat vorliegt, z. b. wenn die Standortnamen nicht stimmen oder das Zertifikat abgelaufen ist. Stellen Sie sicher, dass das Zertifikat auf dem neuesten Stand ist und dass die Zertifikat Daten mit den Standortdaten übereinstimmen, um [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] über eine SSL-Verbindung zu arbeiten.
## <a name="clickonce-and-proxy-authentication"></a>ClickOnce und Proxy Authentifizierung
[!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] bietet Unterstützung für die integrierte Windows-Proxy Authentifizierung ab .NET Framework 3,5. Bestimmte Machine. config-Direktiven sind nicht erforderlich. [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] bietet keine Unterstützung für andere Authentifizierungsprotokolle, wie z. b. Basic oder Digest.
Sie können auch einen Hotfix auf .NET Framework 2,0 anwenden, um dieses Feature zu aktivieren. Weitere Informationen finden Sie unter http://go.microsoft.com/fwlink/?LinkId=158730.
Weitere Informationen finden Sie unter [\<defaultProxy >-Element (Netzwerkeinstellungen)](/dotnet/framework/configure-apps/file-schema/network/defaultproxy-element-network-settings).
## <a name="clickonce-and-web-browser-compatibility"></a>ClickOnce und Webbrowser Kompatibilität
Zurzeit werden [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] Installationen nur gestartet, wenn die URL des Bereitstellungs Manifests mithilfe von Internet Explorer geöffnet wird. Eine Bereitstellung, deren URL von einer anderen Anwendung, z. b. Microsoft Office Outlook, gestartet wird, wird nur dann erfolgreich gestartet, wenn Internet Explorer als Standard Webbrowser festgelegt ist.
> [!NOTE]
> Mozilla Firefox wird unterstützt, wenn der Bereitstellungs Anbieter nicht leer ist oder die Erweiterung des Microsoft .NET Framework-Assistenten installiert ist. Diese Erweiterung ist mit .NET Framework 3,5 SP1 verpackt. Bei der XBAP-Unterstützung wird das npwpf-Plug-in bei Bedarf aktiviert.
## <a name="activate-clickonce-applications-through-browser-scripting"></a>Aktivieren von ClickOnce-Anwendungen mithilfe von Browser Skripts
Wenn Sie eine benutzerdefinierte Webseite entwickelt haben, die eine [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] Anwendung mithilfe von Active Scripting startet, werden Sie möglicherweise feststellen, dass die Anwendung auf einigen Computern nicht gestartet wird. Internet Explorer enthält eine Einstellung, die als **Automatische Eingabeaufforderung für Dateidownloads**bezeichnet wird, was sich auf dieses Verhalten auswirkt. Diese Einstellung ist im Menü **Optionen** auf der Registerkarte **Sicherheit** verfügbar und wirkt sich auf dieses Verhalten aus. Sie wird als **Automatische Aufforderung zum Herunterladen von Dateien**bezeichnet und unterhalb der Kategorie **Downloads** aufgeführt. Die-Eigenschaft ist so festgelegt, dass Sie für Intranetwebseiten standardmäßig **aktiviert** und für Internet Webseiten standardmäßig **deaktiviert** wird. Wenn diese Einstellung auf **Deaktivieren**festgelegt ist, wird jeder Versuch, eine [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] Anwendung Programm gesteuert zu aktivieren (z. b. durch Zuweisen der URL zur `document.location`-Eigenschaft) blockiert. Unter diesen Umständen können Benutzer Anwendungen nur über einen vom Benutzer initiierten Download starten, indem Sie beispielsweise auf einen Hyperlink klicken, der auf die URL der Anwendung festgelegt ist.
## <a name="additional-server-configuration-issues"></a>Zusätzliche Probleme bei der Serverkonfiguration
##### <a name="administrator-permissions-required"></a>Administrator Berechtigungen erforderlich
Wenn Sie mit http veröffentlichen, müssen Sie über Administrator Berechtigungen auf dem Zielserver verfügen. IIS erfordert diese Berechtigungsstufe. Wenn Sie nicht mit http veröffentlichen, benötigen Sie nur die Schreib Berechtigung für den Zielpfad.
##### <a name="server-authentication-issues"></a>Probleme mit der Server Authentifizierung
Wenn Sie auf einem Remote Server veröffentlichen, auf dem "Anonymer Zugriff" deaktiviert ist, erhalten Sie die folgende Warnung:
```
"The files could not be downloaded from http://<remoteserver>/<myapplication>/. The remote server returned an error: (401) Unauthorized."
```
> [!NOTE]
> Sie können die NTLM-Authentifizierung (NT Challenge-Response) aktivieren, wenn der Standort andere Anmelde Informationen als die Standard Anmelde Informationen anfordert, und Sie im Dialogfeld Sicherheit auf **OK** klicken, wenn Sie dazu aufgefordert werden, die angegebenen Anmelde Informationen zu speichern. zukünftige Sitzungen. Diese Problem Umgehung funktioniert jedoch nicht bei der Standard Authentifizierung.
## <a name="use-third-party-web-servers"></a>Verwenden von Drittanbieter-Webservern
Wenn Sie eine [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] Anwendung von einem anderen Webserver als IIS bereitstellen, tritt möglicherweise ein Problem auf, wenn der Server den falschen Inhaltstyp für Schlüssel [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] Dateien zurückgibt, wie z. b. das Bereitstellungs Manifest und das Anwendungs Manifest. Um dieses Problem zu beheben, finden Sie in der Hilfe Dokumentation Ihres Webservers Informationen zum Hinzufügen neuer Inhaltstypen zum Server, und stellen Sie sicher, dass alle in der folgenden Tabelle aufgeführten Dateinamen-Erweiterungs Zuordnungen vorhanden sind.
|Dateinamenerweiterung|Inhaltstyp|
|-------------------------|------------------|
|`.application`|`application/x-ms-application`|
|`.manifest`|`application/x-ms-manifest`|
|`.deploy`|`application/octet-stream`|
|`.msu`|`application/octet-stream`|
|`.msp`|`application/octet-stream`|
## <a name="clickonce-and-mapped-drives"></a>ClickOnce und zugeordnete Laufwerke
Wenn Sie Visual Studio verwenden, um eine ClickOnce-Anwendung zu veröffentlichen, können Sie kein zugeordnetes Laufwerk als Installations Speicherort angeben. Sie können jedoch die ClickOnce-Anwendung so ändern, dass Sie von einem zugeordneten Laufwerk aus mithilfe des Manifest-Generators und des Editors ("Mage. exe" und "MageUI. exe") installiert wird. Weitere Informationen finden Sie unter [Mage.exe (Tool zum Generieren und Bearbeiten von Manifesten)](/dotnet/framework/tools/mage-exe-manifest-generation-and-editing-tool) und [MageUI.exe (Tool zum Generieren und Bearbeiten von Manifesten, grafischer Client)](/dotnet/framework/tools/mageui-exe-manifest-generation-and-editing-tool-graphical-client).
## <a name="ftp-protocol-not-supported-for-installing-applications"></a>FTP-Protokoll wird für die Installation von Anwendungen nicht unterstützt
[!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] unterstützt die Installation von Anwendungen von einem beliebigen HTTP 1,1-Webserver oder-Dateiserver. FTP, die Dateiübertragungsprotokoll, wird für die Installation von Anwendungen nicht unterstützt. Sie können FTP nur zum Veröffentlichen von Anwendungen verwenden. In der folgenden Tabelle werden diese Unterschiede zusammengefasst:
| URL-Typ | Beschreibung |
|----------| - |
| ftp:// | Sie können eine [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] Anwendung mithilfe dieses Protokolls veröffentlichen. |
| http:// | Mithilfe dieses Protokolls können Sie eine [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] Anwendung installieren. |
| https:// | Mithilfe dieses Protokolls können Sie eine [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] Anwendung installieren. |
| file:// | Mithilfe dieses Protokolls können Sie eine [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] Anwendung installieren. |
## <a name="windows-xp-sp2-windows-firewall"></a>Windows XP SP2: Windows Firewall
Standardmäßig wird die Windows-Firewall von Windows XP SP2 aktiviert. Wenn Sie Ihre Anwendung auf einem Computer entwickeln, auf dem Windows XP installiert ist, können Sie [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] Anwendungen weiterhin auf dem lokalen Server veröffentlichen und ausführen, auf dem IIS ausgeführt wird. Sie können jedoch nicht auf den Server zugreifen, auf dem IIS von einem anderen Computer ausgeführt wird, sofern Sie nicht die Windows-Firewall öffnen. Anweisungen zur Verwaltung der Windows-Firewall finden Sie in der Windows-Hilfe.
## <a name="windows-server-enable-frontpage-server-extensions"></a>Windows Server: FrontPage-Server Erweiterungen aktivieren
Zum Veröffentlichen von Anwendungen auf einem Windows-Webserver, der HTTP verwendet, sind FrontPage-Servererweiterungen von Microsoft erforderlich.
Standardmäßig ist auf Windows Server keine FrontPage-Servererweiterungen installiert. Wenn Sie [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] verwenden möchten, um auf einem Windows Server-Webserver zu veröffentlichen, der HTTP mit FrontPage-Servererweiterungen verwendet, müssen Sie zuerst FrontPage-Servererweiterungen installieren. Sie können die Installation mithilfe des Verwaltungs Tools Server verwalten in Windows Server ausführen.
## <a name="windows-server-locked-down-content-types"></a>Windows Server: gesperrte Inhaltstypen
IIS auf [!INCLUDE[WinXPSvr](../debugger/includes/winxpsvr_md.md)] sperrt alle Dateitypen außer für bestimmte bekannte Inhaltstypen (z *. b. htm*, *HTML*, *txt*usw.). Um die Bereitstellung von [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] Anwendungen mit diesem Server zu ermöglichen, müssen Sie die IIS-Einstellungen ändern, um das Herunterladen von Dateien vom Typ " *. Application*", " *Manifest*" und anderen von der Anwendung verwendeten benutzerdefinierten Dateitypen zuzulassen.
Wenn Sie die Bereitstellung über einen IIS-Server durchführen, führen Sie *inetmgr. exe* aus, und fügen Sie neue Dateitypen für die Standard Webseite hinzu:
- Für die Erweiterungen " *. Application* " und " *. Manifest* " sollte der MIME-Typ "application/x-ms-application" lauten. Bei anderen Dateitypen sollte der MIME-Typ "Application/Octett-Stream" lauten.
- Wenn Sie einen MIME-Typ mit der Erweiterung "<em>" und dem MIME-Typ "Application/Octett-Stream" erstellen, können Dateien des nicht blockierten Dateityps heruntergeladen werden. (Blockierte Dateitypen wie "*. aspx</em> " und " *. asmx* " können jedoch nicht heruntergeladen werden.)
Spezifische Anweisungen zum Konfigurieren von MIME-Typen unter Windows Server finden Sie im Microsoft Knowledge Base-Artikel KB326965, "IIS 6,0 bedient keine unbekannten MIME-Typen" unter [http://support.microsoft.com/default.aspx?scid=kb; en-US; 326965](http://support.microsoft.com/default.aspx?scid=kb;en-us;326965).
## <a name="content-type-mappings"></a>Inhaltstyp Zuordnungen
Beim Veröffentlichen über HTTP sollte der Inhaltstyp (auch als MIME-Typ bezeichnet) für die *Anwendungs* Datei "application/x-ms-application" lauten. Wenn Sie .NET Framework 2,0 auf dem Server installiert haben, wird dieser automatisch für Sie festgelegt. Wenn dies nicht installiert ist, müssen Sie eine MIME-Typzuordnung für den [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] Application vroot (oder den gesamten Server) erstellen.
Wenn Sie die Bereitstellung über einen IIS-Server ausführen, führen Sie <em>inetmgr aus.</em> exe, und fügen Sie den neuen Inhaltstyp "application/x-ms-application" für die Erweiterung " *. Application* " hinzu.
## <a name="http-compression-issues"></a>HTTP-Komprimierungs Probleme
Mit [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)]können Sie Downloads ausführen, die die HTTP-Komprimierung verwenden, eine Webserver Technologie, die den gzip-Algorithmus zum Komprimieren eines Datenstroms verwendet, bevor der Datenstrom an den Client gesendet wird. Der Client – in diesem Fall, [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)]– den Stream vor dem Lesen der Dateien dekomprimiert.
Wenn Sie IIS verwenden, können Sie die HTTP-Komprimierung problemlos aktivieren. Wenn Sie die HTTP-Komprimierung aktivieren, ist Sie jedoch nur für bestimmte Dateitypen aktiviert – HTML-und Textdateien. Um die Komprimierung für Assemblys ( *. dll*), XML (*XML),* Bereitstellungs Manifeste ( *. Application*) und Anwendungs*Manifeste (. Manifest*) zu aktivieren, müssen Sie diese Dateitypen der Liste der Typen hinzufügen, die von IIS komprimiert werden sollen. Bis Sie die Dateitypen der Bereitstellung hinzufügen, werden nur Text-und HTML-Dateien komprimiert.
Ausführliche Anweisungen für IIS finden Sie unter [Angeben zusätzlicher Dokumenttypen für die HTTP-Komprimierung](https://support.microsoft.com/help/234497).
## <a name="see-also"></a>Siehe auch
- [Problembehandlung bei ClickOnce-Bereitstellungen](../deployment/troubleshooting-clickonce-deployments.md)
- [Auswählen einer Strategie für die ClickOnce-Bereitstellung](../deployment/choosing-a-clickonce-deployment-strategy.md)
- [Vorbedingungen für die Anwendungsbereitstellung](../deployment/application-deployment-prerequisites.md) | 124.072464 | 1,355 | 0.805397 | deu_Latn | 0.987384 |
9ae928f61e7982533427a488f4fb7cf2d8a8a278 | 10,200 | md | Markdown | pdf-docset/docs/gauntletdocs/gauntlet-dogfood.md | angelwen1396/pdftest | ff296372eef68be8de0fa49205a8ebaf3442d2b8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | pdf-docset/docs/gauntletdocs/gauntlet-dogfood.md | angelwen1396/pdftest | ff296372eef68be8de0fa49205a8ebaf3442d2b8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | pdf-docset/docs/gauntletdocs/gauntlet-dogfood.md | angelwen1396/pdftest | ff296372eef68be8de0fa49205a8ebaf3442d2b8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | # Gauntlet VS Code Extension and Services (Dogfood)
The Gauntlet VS Code extension for OPS authoring provides Markdown authoring assistance to writers working in OPS and publishing to docs.microsoft.com. It includes several functions, including applying templates to new Markdown files, applying common formatting to strings, and inserting links, images, tokens, snippets, tables, and lists, as well as previewing content using the OPS build logic.
This topic describes the current Gauntlet dogfood version, 1.8.2, which contains new functionality not yet broadly released and is only available to a limited UAT group. If you would like to join, please email gauntletPM@microsoft.com.
New in 1.8.2:
- Metadata validation. You can check your files to confirm that required metadata is complete and values are valid, based on rules defined by the BI and SEO teams. See **Validation** in [Toolbar quick reference](#toolbar-quick-reference) below for how to validate your files in VS Code. See [Gauntlet Validation Service](gauntlet-validation.md) for how to administer validation rules (business owners only).
- Insert bookmarks. See **Insert Link**, in [Toolbar quick reference](#toolbar-quick-reference) below.
- New OPS build-based preview. The new preview uses OPS build logic to more accurately render content. This preview also includes updates in real-time as you type, and if you scroll the preview window the authoring pane scrolls along with you.
- Various bug fixes and DCRs.
## Installation: Upgrade from previous UAT build
If you have a previously installed Gauntlet UAT build, such as 1.7.2, you will be prompted to upgrade to 1.7.5 when you open VS Code:
1. Agree to open the installer folder.
2. Double-click GauntletExtensionInstaller.exe.
3. The installer will uninstall the old version and install 1.8.2.
## Installation: First time install or upgrade from production release
Requires Windows on corpnet with Edge or IE:
1. If you haven't already, install [VS Code](https://code.visualstudio.com/Download).
2. If you have a previously installed production release of Gauntlet, such as 1.7.0, uninstall it first and reload VS Code.
3. Go to http://aka.ms/GauntletStage on Edge or IE.
4. Click **Download and Run the Installer**.
5. Save and run GauntletExtensionInstaller.exe.
6. If you see a security warning, select **More info**:
...then select **Run anyway**:
7. A command line will pop up, providing status as the extension installs.
8. When complete, you will see the new Gauntlet toolbar, including the validation checkmark, at the bottom of your VS Code window:
## Installation: Install manually from VSIX
Use this option to install on Mac or Linux, or on Windows with an unsupported browser. If your machine is not on corpnet, you will need to copy the VSIX manually, e.g. via thumb drive.
1. If you haven't already, install [VS Code](https://code.visualstudio.com/Download).
2. If you have a previously installed version of Gauntlet, uninstall it first.
3. Click the square icon on the left panel to open the **Extensions** menu.
4. Click the three dots for **More** and select **Install from VSIX...**.
5. Paste the path `\\dpspub\Gauntlet-Extension-Staging\gauntlet-1.8.2.vsix` into the **File name** box and click **Open**.
6. VS Code will install the extension and prompt you to restart.
## Prerequisites and assumptions
To effectively use the authoring extension, you must clone your entire repo to your local machine and keep it in sync. Functions such as link and image insertion are not reliable if the repo is out of sync.
## Known issues
- The new preview creates a local environment that can leave a process, DfMHttpService, running in the background, preventing full uninstallation. If you need to uninstall Gauntlet and get strange errors, this is likely the cause. Just close and reopen VS Code and uninstallation should succeed.
- The new preview renders some items, such as alerts, includes, code, and images, inconsistently. Sometimes this is because the environment is still building in the background, sometimes if you edit the text the items stop previewing correctly. Closing and reopening the preview may fix the issue. These bugs are under investigation and will be fixed before the new preview releases to production - let us know if you find other issues!
- Hotkeys may conflict with other applications. We have chosen an unusual convention, `Ctrl+Shift+Alt`, to minimize conflicts - but we cannot predict what hotkeys may be assigned by other applications installed on your machine. If a hotkey does not work as documented, it probably means you have a conflict. To assign a different hotkey, see [Customizing Shortcuts](https://code.visualstudio.com/docs/customization/keybindings#_customizing-shortcuts) in the VS Code docs. You can also do this if you just find our convention too clumsy!
## Toolbar quick reference
|Tool Bar Icon |Description |
|---------|---------|
|| **Create New File** - Use to create a new unsaved document tab, that you can author directly or copy a template into. Hotkey: `Ctrl+Shift+Alt+N`. |
||**Apply Template** - Use to apply a template, such as the standard docs.microsoft.com metadata template. If your document already has content the template will be inserted in place. Hotkey: `Ctrl+Shif+Alt+M`. For more information, see [Gauntlet Template Service](gauntlet-templates.md). |
||**Bold Text** - Use to bold a string or block of text. Hotkey `Ctrl+Shift+Alt+B`. |
||**Italic Text** - Use to style a string or block of text as italic. Hotkey: `Ctrl+Shift+Alt+I`. |
| |**Code** - Use to style a string or block of text as code. If you select a line or less of text, then click the button or use the `Ctrl+Shift+Alt+C` hotkey, the Gauntlet extension will style the string as code inline. If you select more than one line, it will be styled as fenced code. |
||**Insert Alert** - Use to insert a note, warning, important, or tip. After clicking the button, choose the alert type from the quick pick menu. If you need to add additional paragraphs to your alert, be sure to add a `>` after each line break, including the blank line between paragraphs. Hotkey: `Ctrl+Shift+Alt+1`.|
||**Insert Numbered List** - Use to insert an ordered (numbered) list. Hotkey: `Ctrl+Shift+Alt+O`.|
| |**Insert Bulleted List** - Use to insert an unordered (bulleted) list. Hotkey: `Ctrl+Shift+Alt+U`.|
||**Insert Table** - Use to insert a table. The number of rows and columns are entered in `C:R` format, for example `3:5` indicates a table with three columns and five rows. Per content guidelines, tables inserted via Gauntlet are limited to a maximum of four columns and fewer than one hundred rows, although you can add more manually. Hotkey: `Ctrl+Shift+Alt+T`.|
||**Insert Link** - In your Markdown file, type the link text and select it, or put your cursor where you want to add a link. Click the button or use the `Ctrl+Shift+Alt+L` hotkey to open the quick pick menu, then select **External**, **Internal**, **Bookmark in this file**, or **Bookmark in another file**. <br><br>For internal relative links, choose the link target from the quick pick menu that appears. You can either scroll through the list or start typing in the text box to filter search results.<br><br> For bookmarks in the same topic, choose from a the list of headings in the topic. <br><br>For bookmarks in another topic, first find the topic you want to link to, just like inserting an internal relative link, then choose the heading in that topic.<br><br> For external links, type or paste the full URI, including `http://` or `https://`. |
||**Insert Image** - Type alt text and select it or put your cursor where you want to insert art. Press the button or use the `Ctrl+Shift+Alt+ A` hotkey, then choose the link target from the quick pick menu that appears. You can either scroll through the list or start typing in the text box to filter search results. |
||**Insert Include** - Use to insert included files (tokens). Hotkey: `Ctrl+Shift+Alt+E`. |
||**Insert Snippet** - Use to insert a code snippet. Hotkey: `Ctrl+Shifft+Alt+S`. |
| |**Preview Content** - Provides more accurate Markdown preview based on the OPS build logic. Hotkey: `Ctrl+Shift+Alt+P`. |
||**Validate** - Validates the current file against the ruleset associated with your repo. Hotkey: `Ctrl+Shift+Alt+V`.|
||**File Bug or Feature** - You can now submit feedback directly from the Gauntlet toolbar! Click to submit your feedback through VSTS. The Gauntlet team will triage your bug, DCR, or feature request for possible implementation in a future release. Hotkey: `Ctrl+Shift+Alt+F`.|
## Gauntlet services
The Gauntlet VS Code extension is the front-end to services that help manage and validate content. In general, only content admins will need to interact with Gauntlet outside of VS Code; for more information about using and administering these services, see:
- [Template Service](gauntlet-templates.md)
- [Validation Service](gauntlet-validation.md)
- [PR Merger](prmerger-overview.md)
| 96.226415 | 905 | 0.768137 | eng_Latn | 0.990064 |
9ae96d87602c5bee4dbe7b9d98c650435b927c96 | 1,901 | md | Markdown | readme.md | EBM2018/blogebm | 0db48ed7c487ae639f7244a95c8fbb03478b3ef1 | [
"MIT"
] | 1 | 2019-01-23T08:44:11.000Z | 2019-01-23T08:44:11.000Z | readme.md | EBM2018/blogebm | 0db48ed7c487ae639f7244a95c8fbb03478b3ef1 | [
"MIT"
] | null | null | null | readme.md | EBM2018/blogebm | 0db48ed7c487ae639f7244a95c8fbb03478b3ef1 | [
"MIT"
] | null | null | null | # Blogebm
Une incroyable application pour gérer des articles.
# Installation
* Cloner le repo
* Installer ```Composer``` et ```npm``` si ce n'est déjà fait
* Se rendre à la racine du repo cloné
* Exécuter ```composer install``` pour installer les dépendances ```PHP```
* Exécuter ```npm install``` pour installer les dépendances ```js```
* Mettre en place une base de données ```MariaDB``` hébergée localement
* Choisir le nom que l'on souhaite pour cette BDD et [lui créer un utilisateur avec les permissions nécessaires](http://www.daniloaz.com/en/how-to-create-a-user-in-mysql-mariadb-and-grant-permissions-on-a-specific-database/)
* Créer un fichier ```.env``` à la racine du projet
* Utiliser le fichier ```.env.example``` comme template
* Le remplir avec ses propres paramètres :
* ```DB_DATABASE``` le nom de la BDD
* ```DB_USERNAME``` l'utilisateur de la BDD
* ```DB_PASSWORD``` le mot de passe de l'utilisateur
* Exécuter ```php artisan migrate --seed``` pour migrer la base de données
* Exécuter ```php artisan serve``` pour servir l'application
* Exécuter ```npm run watch``` pour bundle les ressources ```js```
* Se rendre à ```localhost:8000``` avec un navigateur web
# Utilisation
* Déployé en développement, le site contient déjà quelques articles créé par l'utilisateur "EBM"
* Pour se connecter au nom de cet utilisateur :
* Email : EBM@EBM.ebm
* Password : hamzaoutai
* Pour écrire un article, il suffit de se connecter avec un compte, il est possible d'en créer de nouveaux.
* Pour modifier des articles, il faut se connecter avec le compte de la personne ayant écrit l'article.
* En mode édition d'articles, il est possible de glisser-déposer les paragraphes d'un article pour le ré-arranger.
* Ce n'est possible que si aucun paragraphe n'est en cours d'édition.
# Authors
Lenophie & MaxouLégal
# Licence
MIT | 45.261905 | 228 | 0.712783 | fra_Latn | 0.978896 |
9ae97168f07656ebfbec6158da60abf4257fd7a4 | 2,600 | md | Markdown | README.md | Abstractigakis/sudoku-solver | 0c48858833a52a242ba76bb606aa1069f2a829cb | [
"MIT"
] | null | null | null | README.md | Abstractigakis/sudoku-solver | 0c48858833a52a242ba76bb606aa1069f2a829cb | [
"MIT"
] | null | null | null | README.md | Abstractigakis/sudoku-solver | 0c48858833a52a242ba76bb606aa1069f2a829cb | [
"MIT"
] | null | null | null | # Sudoku Sovler
## Problem Statement
For the rules of sudoku, google it, and play some games! A sudoku problem can be represented by a $9$ x $9$ tensor called $X$ where $X_{i,j}$ is an integer between $0$ and $9$. $X_{i,j} = 0$ is the case where the tile is empty. To keep track of where we can add numbers, we will create a $9$ x $9$ x $9$ boolean tensor called $D$. This is to be thought of as the domains of possibilites for each $X_{i,j}$, where $D_{i,j,k}$ is $1$ if it is possible to insert $k$ intp $X_{i,j}$ without breaking the rules of Sudoku, and $0$ otherwise. Some facts to realize is that if we know a number on a tile conclusively, we can know that the entire tensor for $D_{i,j}$ should be filled with falses, because no value can be inserted in that space. Conversly, if a tile is not known yet, then at least one of the entries in the associated domain should be true. More susinctly,
$$X_{i,j} \neq 0 \iff D_{i,j,k} = 0 \ \forall k$$
Also Notice that given a gamestate $X$ we can uniquley compute the Domains $D$
## Strategies
We will create 3 diffeerent strategies (and possibly more) to solve the sudoku puzzles, each with greater degrees of effecincy. NOTE: when we say effeciency, we are referring to the number of attempts the puzzle sover must make, where an attempt is a square that it tries to fill. THe goa is to minimize the number of attempts.
First we will try a naive brute force approach, where we just guess number in a depth first search until we solve the problem. Then we will implement forward checking, in where when we try and insert a number into the puzzle, we chekc to see if this makes any other square on the board impossible before proceeding. Finally, we will look at a better method for selecting tiles, rather than selecting the tile that is the next in the list, we will look for the variable with the least contraints, and aim to fill this first. we will then try the same thing with the most constrained tile, and compare resutls.
## Design Choices
For the sake of this algorithm we will be implementing all of our logic into a single class `SudokuSolve` where the puzzle and domains are stored as mutable objects. We will be passing everything as reference. This has the trade off of being very memory effecint, but does not easily lend itslef to concurrent solutions, i.e. forking the gamestate and trying to insert 2 nunmbers in parrelell. This would require a more functional approach. Perhaps in the future, we can rebuild with a better systems language like rust or C++, and adopt a more functional, memory hungry paradigm.
| 144.444444 | 869 | 0.760385 | eng_Latn | 0.999899 |
9aea42c63a118da1fae6e6d8c18a75d8a59279a9 | 6,215 | md | Markdown | README.md | Programmable-Air/Code | 53d65f1cdea6769f91d42509c50f3d4c594e3b7f | [
"MIT"
] | 38 | 2018-11-05T18:37:39.000Z | 2022-03-07T04:11:03.000Z | README.md | Programmable-Air/Code | 53d65f1cdea6769f91d42509c50f3d4c594e3b7f | [
"MIT"
] | 15 | 2018-12-03T23:47:04.000Z | 2022-01-05T20:01:11.000Z | README.md | Programmable-Air/Code | 53d65f1cdea6769f91d42509c50f3d4c594e3b7f | [
"MIT"
] | 9 | 2019-05-08T08:40:05.000Z | 2022-01-29T23:38:48.000Z | # Code
Arduino library for Programmable-Air
## Crowdfunded on [CrowdSupply](https://www.crowdsupply.com/tinkrmind/programmable-air)
[](https://www.crowdsupply.com/tinkrmind/programmable-air)
## Getting started:
As a first step you should read the [README](https://github.com/Programmable-Air/PCB/) file in the PCB section to get acquainted with the hardware. This is not necessary as such, but highly recommended.
### Software
* Download and install the [latest Arduino IDE](https://www.arduino.cc/en/software)
* Download the Programmable-Air library at https://github.com/Programmable-Air/Code Instructions on how to install a new library in Arduino [here](https://www.arduino.cc/en/Guide/Libraries#toc4)
* Now there should be a programmable_air folder in File>examples
* If you do not have Adafruit Neopixel library already installed, you will need to install it as well. [Instructions](https://learn.adafruit.com/adafruit-neopixel-uberguide/arduino-library-installation#install-adafruit-neopixel-via-library-manager-13-2).
* You might need to install CH340 drivers to get the Arduino nano board to be recognized as a serial device. Follow instructions specific to your OS.
### Hardware
* Power up the Programmable-Air unit by connecting 12V adapter. Then connect the USB cable to your computer.
### Uploading code
* Select Tools>Board>Arduino Nano
* If you are on a new version of Arduino >=1.8.7 select Processor: AtMega328(Old bootloader)
* Select the corresponding Port (if no new port shows up you’ll have to download and install the CH340 drivers- [Mac](http://www.wch.cn/downloads/CH341SER_MAC_ZIP.html) [Windows](https://sparks.gogo.co.nz/ch340.html) [Linux](http://www.wch.cn/downloads/CH341SER_LINUX_ZIP.html) ) The link looks sketchy and in Chinese, but it is the manufacturer’s website with the most updated version of the driver. Refrain from downloading drivers from any other source!
That's it! Try uploading the pressureSensor example and launch the Serial plotter to see the pressure plot. Blow into the output tube, or suck the air out to see the change in pressure.
### Description of functions:
`initializePins()`
Initializes the pins as INPUT or OUTPUT and starts the Serial port at 9600 baud. If you want to use pins to attach external hardware, set their pinMode after calling this.
* Does not return anything.
`blow(int i = 1);`
Used to blow air into the output tube. Engages valve #2 and disengages valve #1 and #3.
* Does not return anything.
* Accepts integer value of the slave board. Acceptable values 1, 2, or 3. Defaults to 1(the slave board below the master board).
`vent(int i = 1);`
Used to vent air from output tube to the atmosphere. Engages valve #1 and disengages valve #2 and #3.
* Does not return anything.
* Accepts integer value of the slave board. Acceptable values 1, 2, or 3. Defaults to 1(the slave board below the master board).
`ventQuick(int i = 1);`
Used to release air quickly out of the output tube. Engages valve #1, and #3 and disengages valve #1.
* Does not return anything.
* Accepts integer value of the slave board. Acceptable values 1, 2, or 3. Defaults to 1(the slave board below the master board).
`suck(int i = 1);`
Used to suck air out of the output tube. Engages valve #3 and disengages valve #1 and #2.
* Does not return anything.
* Accepts integer value of the slave board. Acceptable values 1, 2, or 3. Defaults to 1(the slave board below the master board).
`readBtn(int i);`
Returns 1 if the button is pressed, 0 if not.
* Return type : int
* Accepts button number or color. RED is button #1, BLUE is button #2
`readPressure(int num = 1, int times = 1);`
Returns the pressure value. The value is ~508 for atmospheric pressure. Greater for more pressure and lesser for less pressure.
* Return type : int
* Accepts up to two integer parameters.
* num - integer value of the slave board. Acceptable values 1, 2, or 3. Defaults to 1(the slave board below the master board).
* times - the number of times you want the reading to be taken and averaged. Acceptable value >1. Defaults to 1.
`setAllValves(int position);`
Set all of the valves to a the position provided. (All the valves on all the slave boards)
* Does not return anything.
* Accepts int 0 or 1(OPEN/OPENED/ENGAGE/ENGAGED or CLOSE/CLOSED/DISENGAGE/DISENGAGED)
`setValve(int number, int position);`
Sets valve number provided to position provided
* Does not return anything.
* Accepts valve number and position
* number - int 1 to 9 for valve number.
* position - Accepts int 0 or 1(OPEN/OPENED/ENGAGE/ENGAGED or CLOSE/CLOSED/DISENGAGE/DISENGAGED)
`closeAllValves();`
Closes(dis-engages) all valves on all slave boards.
* Does not return anything.
`switchOnPump(int num, int percentagePower = 100);`
Switches on pump motor # num to PWM percentage percentagePower.
* Does not return anything.
* Accepts two parameters
* num - int motor number 1 or 2
* percentagePower - int 0 to 100. Note that for value <30 the motor might not turn on. Defaults to 100% PWM.
`switchOffPump(int num);`
Switches off motor number num
* Does not return anything.
* num - int 1 or 2
`switchOnPumps(int percentagePower = 100);`
Switches on both motors to PWM percentage percentagePower
* Does not return anything.
* percentagePower - int 0 to 100. Note that for value <30 the motor might not turn on. Defaults to 100% PWM.
`switchOffPumps();`
Switches off both motors
* Does not return anything.
* Does not accept any parameter.
`switchOnLoad(int percentagePower = 100);`
Switches on load to PWM percentagePower. Note that the load pin gets connected to ground when switched on. So, connect the external device between power and load.
* Does not return anything.
* percentagePower - int 0 to 100. Note that for value <30 the motor might not turn on. Defaults to 100% PWM.
`switchOffLoad();`
Switches off load.
* Does not return anything.
* Does not accept any parameter.
| 43.461538 | 457 | 0.740949 | eng_Latn | 0.970641 |
9aea5eb8b49bf2f660c14d09fd72bff8f2156608 | 272 | md | Markdown | CHANGELOG.md | valerino/vscode-workspace-terminals | 073263727df4b14673ed62157316cd1e6318cf54 | [
"ISC"
] | null | null | null | CHANGELOG.md | valerino/vscode-workspace-terminals | 073263727df4b14673ed62157316cd1e6318cf54 | [
"ISC"
] | null | null | null | CHANGELOG.md | valerino/vscode-workspace-terminals | 073263727df4b14673ed62157316cd1e6318cf54 | [
"ISC"
] | null | null | null | # Changelog
## 0.2
- Per default, terminals only open automatically in multi-root workspaces.
**BREAKING CHANGE:**
`workspace-terminals.auto` setting changes from boolean to an enum with the options `always`, `multi-root` (default) and `never`.
## 0.1
Initial Release | 22.666667 | 129 | 0.738971 | eng_Latn | 0.962488 |
9aeaef33fd195e853b13fa168a7bd841e583c4e7 | 1,995 | md | Markdown | guide/spanish/machine-learning/unsupervised-learning/index.md | Niruthiya/freeCodeCamp | 76ac81219c0bc9d777ea385047ba62e2730b3185 | [
"BSD-3-Clause"
] | 2 | 2019-08-16T21:35:10.000Z | 2020-08-12T06:09:54.000Z | guide/spanish/machine-learning/unsupervised-learning/index.md | mpdo2017/freeCodeCamp | ddd6c228ada3bdc7469b7c26eb8fa67aca0b15a2 | [
"BSD-3-Clause"
] | null | null | null | guide/spanish/machine-learning/unsupervised-learning/index.md | mpdo2017/freeCodeCamp | ddd6c228ada3bdc7469b7c26eb8fa67aca0b15a2 | [
"BSD-3-Clause"
] | 1 | 2019-10-10T15:55:56.000Z | 2019-10-10T15:55:56.000Z | ---
title: Unsupervised Learning
localeTitle: Aprendizaje sin supervisión
---
#### Lectura sugerida:
* https://en.wikipedia.org/wiki/Unsupervised\_learning
* https://stackoverflow.com/a/1854449/6873133
* http://mlg.eng.cam.ac.uk/zoubin/papers/ul.pdf
* https://machinelearningmastery.com/supervised-and-unsupervised-machine-learning-algorithms/
#### Proyecto de artículo:
¿Qué es el aprendizaje no supervisado?
El aprendizaje no supervisado nos permite abordar los problemas con poca o ninguna idea de cómo deberían ser nuestros resultados. Podemos derivar la estructura de datos donde no necesariamente sabemos el efecto de las variables.
Tipos de aprendizaje no supervisado
Agrupación en clúster: se utiliza para el análisis exploratorio de datos para encontrar patrones ocultos o agrupación en datos. Tome una colección de 1,000,000 de genes diferentes, y encuentre una manera de agrupar automáticamente estos genes en grupos que de alguna manera sean similares o estén relacionados por diferentes variables, como la duración de la vida, la ubicación, los roles, etc.
Asociación: se utiliza cuando queremos descubrir reglas que describan una porción significativa de los datos. Un ejemplo de esto sería aprender que la gente que compra X producto también suele comprar un producto Y.
Los enfoques para el aprendizaje no supervisado incluyen:
Agrupamiento k-significa. modelos de mezcla. Clustering jerárquico, detección de anomalías. Redes neuronales. Aprendizaje Hebbiano. Redes adversas generativas. Enfoques para aprender modelos de variables latentes como. Algoritmo de expectativa-maximización (EM) Método de los momentos.
Algunos ejemplos más: Supongamos que tiene datos para un sitio de comercio electrónico. Tiene una lista de personas y cosas que ordenaron en línea la semana pasada. Ahora puede usar los algoritmos de agrupación en clústeres y encontrar el patrón en los datos, predecir la tendencia de compra y formular la estrategia comercial según la tendencia.
| 68.793103 | 394 | 0.81203 | spa_Latn | 0.995561 |
9aeb14a816755250645b142645313b2390c80ae9 | 27 | md | Markdown | README.md | PJChristian/pjChristian.github.io | 66d290ca450349921b9dd6d3b38d3f880afd9c11 | [
"MIT"
] | null | null | null | README.md | PJChristian/pjChristian.github.io | 66d290ca450349921b9dd6d3b38d3f880afd9c11 | [
"MIT"
] | null | null | null | README.md | PJChristian/pjChristian.github.io | 66d290ca450349921b9dd6d3b38d3f880afd9c11 | [
"MIT"
] | null | null | null | # pjChristian
My Portfolio
| 9 | 13 | 0.814815 | eng_Latn | 0.668101 |
9aebb54cb5307c00be75a32f16106b6880797983 | 2,883 | md | Markdown | AlchemyInsights/office-content-search-tool.md | isabella232/OfficeDocs-AlchemyInsights-pr.fr-FR | b23fe97cbba1674ad1f59978ca5080bb00d217cb | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-05-19T19:06:33.000Z | 2020-05-19T19:06:33.000Z | AlchemyInsights/office-content-search-tool.md | isabella232/OfficeDocs-AlchemyInsights-pr.fr-FR | b23fe97cbba1674ad1f59978ca5080bb00d217cb | [
"CC-BY-4.0",
"MIT"
] | 2 | 2022-02-09T06:56:37.000Z | 2022-02-09T06:56:51.000Z | AlchemyInsights/office-content-search-tool.md | isabella232/OfficeDocs-AlchemyInsights-pr.fr-FR | b23fe97cbba1674ad1f59978ca5080bb00d217cb | [
"CC-BY-4.0",
"MIT"
] | 2 | 2019-10-11T18:36:10.000Z | 2021-10-09T11:34:48.000Z | ---
title: 1491-search-not-returning-expected-results
ms.author: pebaum
author: pebaum
manager: pamgreen
ms.audience: Admin
ms.topic: article
ms.service: o365-administration
ROBOTS: NOINDEX, NOFOLLOW
localization_priority: Normal
ms.collection: Adm_O365
ms.custom: 1491
ms.assetid: ''
ms.openlocfilehash: 8e926db0d43f7586809ab78db66e861b8908a0ce61fb84498d1993bcc301d5f4
ms.sourcegitcommit: b5f7da89a650d2915dc652449623c78be6247175
ms.translationtype: MT
ms.contentlocale: fr-FR
ms.lasthandoff: 08/05/2021
ms.locfileid: "53985539"
---
# <a name="content-search-tool-to-find-relevant-info"></a>Outil de recherche de contenu pour trouver des informations pertinentes
Utilisez l’outil de recherche de contenu dans le Centre de sécurité & conformité pour trouver rapidement des messages électroniques dans des boîtes aux lettres Exchange, des documents dans des sites SharePoint et des emplacements OneDrive, ainsi que des conversations de messagerie instantanée dans Skype Entreprise. Vous pouvez utiliser l’outil de recherche de contenu pour rechercher des messages électroniques, des documents et des conversations de messagerie instantanée dans Microsoft 365 outils de collaboration tels que Microsoft Teams et Microsoft 365 groupes.
Avant [](https://sip.protection.office.com/contentsearchbeta?ContentOnly=1) d’utiliser la recherche de contenu à partir du Centre de sécurité [&](https://sip.protection.office.com/homepage)conformité, vous devez remplir les paramètres de configuration, y compris configurer les [autorisations,](https://docs.microsoft.com/microsoft-365/compliance/permissions-filtering-for-content-search)définir les [vitesses](https://docs.microsoft.com/microsoft-365/compliance/increase-download-speeds-when-exporting-ediscovery-results) de téléchargement et exporter les [paramètres.](https://docs.microsoft.com/microsoft-365/compliance/disable-reports-when-you-export-content-search-results)
Pour en savoir plus sur la recherche de contenu, examinez les exigences et les [limites,](https://docs.microsoft.com/microsoft-365/compliance/limits-for-content-search)examinez les éléments partiellement [indexés](https://docs.microsoft.com/microsoft-365/compliance/investigating-partially-indexed-items-in-ediscovery) et d’autres résultats à connaître.
Après avoir passé en revue les paramètres de configuration et les restrictions de la recherche de contenu, [ </a> reportez-vous](https://docs.microsoft.com/microsoft-365/compliance/content-search)à l’utilisation de la recherche de contenu pour rechercher des éléments sur place tels que le courrier électronique, les documents et les conversations de messagerie instantanée dans votre organisation.
Pour une recherche pas à pas complète de la recherche de contenu, voir Rechercher du contenu [dans Microsoft 365](https://docs.microsoft.com/microsoft-365/compliance/search-for-content) pour plus d’informations.
| 87.363636 | 678 | 0.825529 | fra_Latn | 0.85341 |
9aebd44e232eda1bbf7dfe13748ef04f2d179b4a | 8,398 | md | Markdown | README.md | MinceMan/DeepLinkDispatch | 6ab057642a6933d665b67fbc70d4874c98e0a763 | [
"Apache-2.0"
] | null | null | null | README.md | MinceMan/DeepLinkDispatch | 6ab057642a6933d665b67fbc70d4874c98e0a763 | [
"Apache-2.0"
] | null | null | null | README.md | MinceMan/DeepLinkDispatch | 6ab057642a6933d665b67fbc70d4874c98e0a763 | [
"Apache-2.0"
] | null | null | null | # DeepLinkDispatch
[](https://travis-ci.org/airbnb/DeepLinkDispatch)
DeepLinkDispatch provides a declarative, annotation-based API to define application deep links.
You can register an `Activity` to handle specific deep links by annotating it with `@DeepLink` and a URI.
DeepLinkDispatch will parse the URI and dispatch the deep link to the appropriate `Activity`, along
with any parameters specified in the URI.
### Example
Here's an example where we register `SampleActivity` to pull out an ID from a deep link like
`example://example.com/deepLink/123`. We annotated with `@DeepLink` and specify there will be a
parameter that we'll identify with `id`.
```java
@DeepLink("foo://example.com/deepLink/{id}")
public class MainActivity extends Activity {
@Override protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
Intent intent = getIntent();
if (intent.getBooleanExtra(DeepLink.IS_DEEP_LINK, false)) {
Bundle parameters = intent.getExtras();
String idString = parameters.getString("id");
// Do something with the ID...
}
...
}
}
```
### Multiple Deep Links
Sometimes you'll have an Activity that handles several kinds of deep links:
```java
@DeepLink({"foo://example.com/deepLink/{id}", "foo://example.com/anotherDeepLink"})
public class MainActivity extends Activity {
@Override protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
Intent intent = getIntent();
if (intent.getBooleanExtra(DeepLink.IS_DEEP_LINK, false)) {
Bundle parameters = intent.getExtras();
String idString = parameters.getString("id");
// Do something with the ID...
}
...
}
}
```
### Method Annotations
You can also annotate static methods that take a `Context` and return an `Intent`. `DeepLinkDispatch` will call that
method to create that `Intent` and use it when starting your Activity via that registered deep link:
```java
@DeepLink("foo://example.com/methodDeepLink/{param1}")
public static Intent intentForDeepLinkMethod(Context context) {
return new Intent(context, MainActivity.class).setAction(ACTION_DEEP_LINK_METHOD);
}
```
### Query Parameters
Query parameters are parsed and passed along automatically, and are retrievable like any
other parameter. For example, we could retrieve the query parameter passed along in the URI
`example://example.com/deepLink?qp=123`:
```java
@DeepLink("foo://example.com/deepLink")
public class MainActivity extends Activity {
@Override protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
Intent intent = getIntent();
if (intent.getBooleanExtra(DeepLink.IS_DEEP_LINK, false)) {
Bundle parameters = intent.getExtras();
if (parameters != null && parameters.getString("qp") != null) {
String queryParameter = parameters.getString("qp");
// Do something with the query parameter...
}
}
}
}
```
### Callbacks
You can optionally register a `BroadcastReceiver` to be called on any incoming deep link into your
app. `DeepLinkActivity` will use `LocalBroadcastManager` to broadcast an `Intent` with any success
or failure when deep linking. The intent will be populated with these extras:
* `DeepLinkActivity.EXTRA_URI`: The URI of the deep link.
* `DeepLinkActivity.EXTRA_SUCCESSFUL`: Whether the deep link was fired successfully.
* `DeepLinkActivity.EXTRA_ERROR_MESSAGE`: If there was an error, the appropriate error message.
You can register a receiver to receive this intent. An example of such a use is below:
```java
public class DeepLinkReceiver extends BroadcastReceiver {
private static final String TAG = DeepLinkReceiver.class.getSimpleName();
@Override
public void onReceive(Context context, Intent intent) {
String deepLinkUri = intent.getStringExtra(DeepLinkActivity.EXTRA_URI);
if (intent.getBooleanExtra(DeepLinkActivity.EXTRA_SUCCESSFUL, false)) {
Log.i(TAG, "Success deep linking: " + deepLinkUri);
} else {
String errorMessage = intent.getStringExtra(DeepLinkActivity.EXTRA_ERROR_MESSAGE);
Log.e(TAG, "Error deep linking: " + deepLinkUri + " with error message +" + errorMessage);
}
}
}
public class YourApplication extends Application {
@Override public void onCreate() {
super.onCreate();
IntentFilter intentFilter = new IntentFilter(DeepLinkActivity.ACTION);
LocalBroadcastManager.getInstance(this).registerReceiver(new DeepLinkReceiver(), intentFilter);
}
}
```
## Usage
Add to your project `build.gradle` file:
```groovy
buildscript {
dependencies {
classpath 'com.neenbedankt.gradle.plugins:android-apt:1.8'
}
}
apply plugin: 'android-apt'
dependencies {
compile 'com.airbnb:deeplinkdispatch:2.0.1'
apt 'com.airbnb:deeplinkdispatch-processor:2.0.1'
}
```
Register `DeepLinkActivity` with the scheme you'd like in your `AndroidManifest.xml` file (using
`airbnb` as an example):
```xml
<activity
android:name=".DeepLinkActivity"
android:theme="@android:style/Theme.NoDisplay">
<intent-filter>
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<data android:scheme="airbnb" />
</intent-filter>
</activity>
```
Note: Intent filters may only contain a single data element for a URI pattern. Create separate
intent filters to capture additional URI patterns.
That's it. The library will generate the class `DeepLinkActivity` during compilation.
Starting with version 2.0.0, you no longer need to add the `DeepLinkActivity` to your manifest.
Just annotate one of your existing activities with `@DeepLinkHandler`. If you do that, DeepLinkDispatch
will not generate the `DeepLinkActivity` for you. Instead, you'll be responsible for handling the
deep links yourself. This is useful if you want to do any custom handling before the deep link is
launched, like logging, sign-up, etc. Example:
```java
@DeepLinkHandler
public class CustomDeepLinkHandler extends Activity {
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
// perform your application-specific logic (eg.: logging, launch sign-in, etc.)
// ...
// Let DeepLinkDispatch handle the Intent and finish this Activity
DeepLinkDelegate.dispatchFrom(this);
finish();
}
}
```
Snapshots of the development version are available in
[Sonatype's `snapshots` repository](https://oss.sonatype.org/content/repositories/snapshots/).
## Proguard Rules
```
-keep class com.airbnb.deeplinkdispatch.** { *; }
-keepclasseswithmembers class * {
@com.airbnb.deeplinkdispatch.DeepLink <methods>;
}
```
## Testing the sample app
Use adb to launch deep links (in the terminal type: `adb shell`).
This fires a standard deep link. Source annotation `@DeepLink("dld://example.com/deepLink")`
`am start -W -a android.intent.action.VIEW -d "dld://example.com/deepLink" com.airbnb.deeplinkdispatch.sample`
This fires a deep link associated with a method, and also passes along a path parameter. Source annotation `@DeepLink("dld://methodDeepLink/{param1}")`
`am start -W -a android.intent.action.VIEW -d "dld://methodDeepLink/abc123" com.airbnb.deeplinkdispatch.sample`
You can include multiple path parameters (also you don't have to include the sample app's package name). Source annotation `@DeepLink("http://example.com/deepLink/{id}/{name}")`
`am start -W -a android.intent.action.VIEW -d "http://example.com/deepLink/123abc/myname"`
Note it is possible to call directly `adb shell am ...` however this seems to miss the URI sometimes so better to call from within shell.
## License
```
Copyright 2015 Airbnb, Inc.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
```
| 35.584746 | 177 | 0.74482 | eng_Latn | 0.843377 |
9aebd495a1d1c3ca8f44f9303ca5c624056c18e9 | 1,639 | md | Markdown | docs/integration-services/system-views/catalog-worker-agents-ssisdb-database.md | kuniteru/sql-docs.ja-jp | 3fe27875882b987f4dc2f7a402859a754ed1a6bb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/integration-services/system-views/catalog-worker-agents-ssisdb-database.md | kuniteru/sql-docs.ja-jp | 3fe27875882b987f4dc2f7a402859a754ed1a6bb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/integration-services/system-views/catalog-worker-agents-ssisdb-database.md | kuniteru/sql-docs.ja-jp | 3fe27875882b987f4dc2f7a402859a754ed1a6bb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: catalog.worker_agents (SSISDB データベース) | Microsoft Docs
ms.custom: ''
ms.date: 12/16/2016
ms.prod: sql
ms.prod_service: integration-services
ms.reviewer: ''
ms.technology: integration-services
ms.topic: conceptual
ms.assetid: 0bd0d827-e2f1-44fe-aa90-6bf922d68d16
author: chugugrace
ms.author: chugu
ms.openlocfilehash: 5f8c494e135764ddca11985f3036068c848f818b
ms.sourcegitcommit: c8e1553ff3fdf295e8dc6ce30d1c454d6fde8088
ms.translationtype: HT
ms.contentlocale: ja-JP
ms.lasthandoff: 07/22/2020
ms.locfileid: "86912428"
---
# <a name="catalogworker_agents-ssisdb-database"></a>catalog.worker_agents (SSISDB データベース)
[!INCLUDE[sqlserver-ssis](../../includes/applies-to-version/sqlserver-ssis.md)]
[!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] Scale Out Worker の情報を表示します。
|列名|データ型|説明|
|-----------------|---------------|-----------------|
|WorkerAgentId|**uniqueidentifier**|Scale Out Worker の worker エージェント ID。|
|IsEnabled|**bit**|Scale Out Worker が有効になっているかどうか。|
|DisplayName|**nvarchar (256)**|Scale Out Worker の表示名。|
|説明|**nvarchar (256)**|Scale Out Worker の説明。|
|MachineName|**nvarchar (256)**|Scale Out Worker のコンピューター名。|
|Tags|**nvarchar(max)**|Scale Out Worker のタグ。|
|UserAccount|**nvarchar (256)**|Scale Out Worker サービスを実行するユーザー アカウント。|
|LastOnlineTime|**datetimeoffset(7)**|最後に Scale Out Worker がオンラインになった日時。|
## <a name="remarks"></a>解説
このビューには、SSISDB カタログと連動している Scale Out Master に接続している各 Scale Out Worker の行が表示されます。
## <a name="permissions"></a>アクセス許可
このビューには、次の権限のいずれかが必要です。
- **ssis_admin** データベース ロールのメンバーシップ
- **ssis_cluster_executor** データベース ロールのメンバーシップ
- **sysadmin** サーバー ロールのメンバーシップ
| 34.145833 | 90 | 0.740085 | yue_Hant | 0.376028 |
9aebdca442ce48c954c925c719045d48cf89e4a3 | 15 | md | Markdown | README.md | mrprompt/arduino-tone | 181c0351abf027eb42db08b67204a6295c536797 | [
"MIT"
] | null | null | null | README.md | mrprompt/arduino-tone | 181c0351abf027eb42db08b67204a6295c536797 | [
"MIT"
] | null | null | null | README.md | mrprompt/arduino-tone | 181c0351abf027eb42db08b67204a6295c536797 | [
"MIT"
] | null | null | null | # arduino-tone
| 7.5 | 14 | 0.733333 | gle_Latn | 0.1994 |
9aec1a6d84ebdeca3e8d7ca1918cb01808258dda | 514 | md | Markdown | api/Excel.XmlSchema.XML.md | ryanmajidi/VBA-Docs | 8b07050f4ff38fcabda606284ec5f6f6634e9569 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | api/Excel.XmlSchema.XML.md | ryanmajidi/VBA-Docs | 8b07050f4ff38fcabda606284ec5f6f6634e9569 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | api/Excel.XmlSchema.XML.md | ryanmajidi/VBA-Docs | 8b07050f4ff38fcabda606284ec5f6f6634e9569 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: XmlSchema.XML property (Excel)
keywords: vbaxl10.chm750074
f1_keywords:
- vbaxl10.chm750074
ms.prod: excel
api_name:
- Excel.XmlSchema.XML
ms.assetid: 1291eecc-71a8-bcfd-44d2-5f4d92dc8b77
ms.date: 06/08/2017
---
# XmlSchema.XML property (Excel)
Returns a **String** value that represents the content of the specified schema.
## Syntax
_expression_. `XML`
_expression_ A variable that represents a [XmlSchema](./Excel.XmlSchema.md) object.
## See also
[XmlSchema Object](Excel.XmlSchema.md)
| 16.580645 | 83 | 0.750973 | eng_Latn | 0.499381 |
9aec4808ca8a3b5bde9eee86a058aa4898eae2f8 | 90 | md | Markdown | softfly-integ-samples/softfly-integ-samples-invoice/softfly-integ-samples-invoice-jaxws-thorntail-flow-client/README.md | softfly/softfly-integration | 677566dc1ac08cc9fc60f9287d91fca0ff31088e | [
"MIT"
] | 1 | 2019-07-04T20:22:11.000Z | 2019-07-04T20:22:11.000Z | softfly-integ-samples/softfly-integ-samples-invoice/softfly-integ-samples-invoice-jaxws-thorntail-flow-client/README.md | softfly/softfly-integration | 677566dc1ac08cc9fc60f9287d91fca0ff31088e | [
"MIT"
] | null | null | null | softfly-integ-samples/softfly-integ-samples-invoice/softfly-integ-samples-invoice-jaxws-thorntail-flow-client/README.md | softfly/softfly-integration | 677566dc1ac08cc9fc60f9287d91fca0ff31088e | [
"MIT"
] | null | null | null | # Softfly Samples Invoice Flows JAX-WS Client
`mvn clean install -Pgenerate-jaxws-client` | 30 | 45 | 0.8 | eng_Latn | 0.550048 |
9aed564a7b1724c800a58a587fd13a3e5cd409cf | 10,265 | md | Markdown | articles/active-directory/saas-apps/rolepoint-tutorial.md | klmnden/azure-docs.tr-tr | 8e1ac7aa3bb717cd24e1bc2612e745aa9d7aa6b6 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2019-08-10T02:23:39.000Z | 2019-08-10T02:23:40.000Z | articles/active-directory/saas-apps/rolepoint-tutorial.md | klmnden/azure-docs.tr-tr | 8e1ac7aa3bb717cd24e1bc2612e745aa9d7aa6b6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/saas-apps/rolepoint-tutorial.md | klmnden/azure-docs.tr-tr | 8e1ac7aa3bb717cd24e1bc2612e745aa9d7aa6b6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'Öğretici: Azure Active Directory Tümleştirmesi ile RolePoint | Microsoft Docs'
description: Bu öğreticide, Azure Active Directory ve RolePoint arasında çoklu oturum açmayı yapılandırma öğreneceksiniz.
services: active-directory
documentationCenter: na
author: jeevansd
manager: mtillman
ms.reviewer: barbkess
ms.assetid: 68d37f40-15da-45f5-a9e1-d53f78e786d1
ms.service: active-directory
ms.subservice: saas-app-tutorial
ms.workload: identity
ms.tgt_pltfrm: na
ms.devlang: na
ms.topic: tutorial
ms.date: 03/15/2019
ms.author: jeedes
ms.openlocfilehash: 0b6fd17d2f8577532778733866260f43e9ac7685
ms.sourcegitcommit: d4dfbc34a1f03488e1b7bc5e711a11b72c717ada
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 06/13/2019
ms.locfileid: "67092728"
---
# <a name="tutorial-azure-active-directory-integration-with-rolepoint"></a>Öğretici: RolePoint ile Azure Active Directory Tümleştirme
Bu öğreticide, Azure Active Directory (Azure AD) ile RolePoint tümleştirme öğreneceksiniz.
Bu tümleştirme aşağıdaki avantajları sağlar:
* Azure AD RolePoint erişimi denetlemek için kullanabilirsiniz.
* Kullanıcılarınız için RolePoint (çoklu oturum açma) ile Azure AD hesaplarına otomatik olarak oturum açmanız etkinleştirebilirsiniz.
* Hesaplarınızı tek bir merkezi konumda yönetebilir: Azure portalı.
Azure AD SaaS uygulama tümleştirmesi hakkında daha fazla bilgi için bkz. [Azure Active Directory'de uygulamalar için çoklu oturum açma](https://docs.microsoft.com/azure/active-directory/active-directory-appssoaccess-whatis).
Azure aboneliğiniz yoksa başlamadan önce [ücretsiz bir hesap oluşturun](https://azure.microsoft.com/free/).
## <a name="prerequisites"></a>Önkoşullar
Azure AD Tümleştirmesi ile RolePoint yapılandırmak için sahip olmanız gerekir:
* Azure AD aboneliğiniz. Bir Azure AD ortamını yoksa alabileceğiniz bir [ücretsiz bir hesap](https://azure.microsoft.com/free/).
* Çoklu oturum etkin açma RolePoint abonelik.
## <a name="scenario-description"></a>Senaryo açıklaması
Bu öğreticide, yapılandırma ve Azure AD çoklu oturum açma bir test ortamında test edin.
* RolePoint SP tarafından başlatılan SSO'yu destekler.
## <a name="add-rolepoint-from-the-gallery"></a>Galeriden RolePoint Ekle
Azure AD'de RolePoint tümleştirmesini ayarlamak için yönetilen SaaS uygulamaları listenize Galeriden RolePoint eklemeniz gerekir.
1. İçinde [Azure portalında](https://portal.azure.com), sol bölmede seçin **Azure Active Directory**:
2. Git **kurumsal uygulamalar** > **tüm uygulamaları**:
3. Bir uygulama eklemek için seçin **yeni uygulama** pencerenin üst kısmındaki:
4. Arama kutusuna **RolePoint**. Seçin **RolePoint** seçin ve arama sonuçlarını **Ekle**.
## <a name="configure-and-test-azure-ad-single-sign-on"></a>Yapılandırma ve Azure AD çoklu oturum açmayı test etme
Bu bölümde, yapılandırın ve Azure AD çoklu oturum açma ile RolePoint Britta Simon adlı bir test kullanıcısı kullanarak test edin.
Çoklu oturum açmayı etkinleştirmek için RolePoint içinde bir Azure AD kullanıcısı ile ilgili kullanıcı arasında bir ilişki yapmanız gerekir.
Yapılandırma ve Azure AD çoklu oturum açma RolePoint ile test etmek için bu adımları tamamlamak gerekir:
1. **[Azure AD çoklu oturum açmayı yapılandırma](#configure-azure-ad-single-sign-on)** kullanıcılarınız için özelliği etkinleştirmek için.
2. **[RolePoint çoklu oturum açmayı yapılandırma](#configure-rolepoint-single-sign-on)** uygulama tarafında.
3. **[Bir Azure AD test kullanıcısı oluşturma](#create-an-azure-ad-test-user)** Azure AD çoklu oturum açmayı test etmek için.
4. **[Azure AD test kullanıcı atama](#assign-the-azure-ad-test-user)** Azure AD çoklu oturum açma için kullanıcı etkinleştirmek için.
5. **[RolePoint test kullanıcısı oluşturma](#create-a-rolepoint-test-user)** kullanıcı Azure AD gösterimini bağlı.
6. **[Çoklu oturum açmayı test](#test-single-sign-on)** yapılandırma çalıştığını doğrulayın.
### <a name="configure-azure-ad-single-sign-on"></a>Azure AD çoklu oturum açmayı yapılandırın
Bu bölümde, Azure AD çoklu oturum açma Azure portalındaki etkinleştirmeniz.
Azure AD çoklu oturum açma ile RolePoint yapılandırmak için şu adımları uygulayın:
1. İçinde [Azure portalında](https://portal.azure.com/), RolePoint uygulama tümleştirme sayfasında **çoklu oturum açma**:
2. İçinde **tek bir oturum açma yönteminizi seçmeniz** Seç iletişim kutusunda **SAML/WS-Federasyon** modu, çoklu oturum açmayı etkinleştirmek için:
3. Üzerinde **yukarı çoklu oturum açma SAML ile ayarlayın** sayfasında **Düzenle** açmak için simgeyi **temel SAML yapılandırma** iletişim kutusunda:
4. İçinde **temel SAML yapılandırma** iletişim kutusunda, aşağıdaki adımları uygulayın.
1. İçinde **oturum açma URL'si** kutusuna, bu düzende bir URL girin:
`https://<subdomain>.rolepoint.com/login`
1. İçinde **tanımlayıcı (varlık kimliği)** kutusuna, bu düzende bir URL girin:
`https://app.rolepoint.com/<instancename>`
> [!NOTE]
> Bu değerler yer tutuculardır. Gerçek oturum açma URL'si ve tanımlayıcı kullanmanız gerekir. Benzersiz bir dize değeri tanımlayıcıda kullanmanızı öneririz. İlgili kişi [RolePoint Destek ekibine](mailto:info@rolepoint.com) bu değerleri almak için. Gösterilen desenleri de başvurabilirsiniz **temel SAML yapılandırma** Azure portalında iletişim kutusu.
5. Üzerinde **yukarı çoklu oturum açma SAML ile ayarlanmış** sayfasında **SAML imzalama sertifikası** bölümünden **indirme** yanındaki bağlantı **Federasyon meta veri XML** , gereksinimlerinize göre ve bilgisayarınızda dosyayı kaydedin.
6. İçinde **RolePoint kümesi** bölümünde, gereksinimlerinize göre uygun URL'ler kopyalayın:
1. **Oturum açma URL'si**.
1. **Azure AD tanımlayıcısı**.
1. **Oturum kapatma URL'si**.
### <a name="configure-rolepoint-single-sign-on"></a>RolePoint çoklu oturum açmayı yapılandırın
Çalışmak istediğiniz RolePoint tarafında çoklu oturum açmayı ayarlamak için [RolePoint Destek ekibine](mailto:info@rolepoint.com). Bu ekip, Federasyon meta veri XML dosyasında ve Azure portalından aldığınız URL'leri gönderin. Bunlar, SAML SSO bağlantının her iki kenarı da düzgün ayarlandığından emin olmak için RolePoint yapılandıracaksınız.
### <a name="create-an-azure-ad-test-user"></a>Bir Azure AD test kullanıcısı oluşturma
Bu bölümde, Azure portalında Britta Simon adlı bir test kullanıcısı oluşturacaksınız.
1. Azure portalında **Azure Active Directory** seçin sol bölmede **kullanıcılar**ve ardından **tüm kullanıcılar**:
2. Seçin **yeni kullanıcı** pencerenin üst kısmındaki:
3. İçinde **kullanıcı** iletişim kutusunda, aşağıdaki adımları uygulayın.
1. İçinde **adı** kutusuna **BrittaSimon**.
1. İçinde **kullanıcı adı** kutusuna **@ BrittaSimon\<yourcompanydomain >.\< Uzantı >** . (Örneğin, BrittaSimon@contoso.com.)
1. Seçin **Göster parola**ve ardından içinde bir değer yazın **parola** kutusu.
1. **Oluştur**’u seçin.
### <a name="assign-the-azure-ad-test-user"></a>Azure AD test kullanıcısı atayın
Bu bölümde, Azure çoklu oturum açma kullanmak için RolePoint erişim vererek Britta Simon tıklatmalarını sağlarsınız.
1. Azure portalında **kurumsal uygulamalar**seçin **tüm uygulamaları**ve ardından **RolePoint**.
2. Uygulamalar listesinde seçin **RolePoint**.
3. Sol bölmede seçin **kullanıcılar ve gruplar**:
4. Seçin **Kullanıcı Ekle**ve ardından **kullanıcılar ve gruplar** içinde **atama Ekle** iletişim kutusu.
5. İçinde **kullanıcılar ve gruplar** iletişim kutusunda **Britta Simon** kullanıcıların listesini ve ardından **seçin** pencerenin alt kısmındaki düğmesi.
6. SAML onaylaması rol değeri de beklediğiniz **rolü Seç** iletişim kutusunda, listeden bir kullanıcı için uygun rolü seçin. Tıklayın **seçin** pencerenin alt kısmındaki düğmesi.
7. İçinde **atama Ekle** iletişim kutusunda **atama**.
### <a name="create-a-rolepoint-test-user"></a>RolePoint test kullanıcısı oluşturma
Sonra Britta Simon RolePoint içinde adlı bir kullanıcı oluşturmanız gerekir. Çalışmak [RolePoint Destek ekibine](mailto:info@rolepoint.com) RolePoint için kullanıcıları eklemek için. Kullanıcıların oluşturulabilir ve çoklu oturum açma kullanabilmek için önce etkinleştirmeniz gerekir.
### <a name="test-single-sign-on"></a>Çoklu oturum açma testi
Şimdi Azure AD çoklu oturum açma yapılandırmanızı erişim panelini kullanarak test gerekir.
Erişim Paneli'nde RolePoint kutucuğu seçtiğinizde, otomatik olarak SSO'yu ayarlama RolePoint örneği için oturum açmanız. Erişim paneli hakkında daha fazla bilgi için bkz: [erişim ve kullanım uygulamaları uygulamalarım portalında](https://docs.microsoft.com/azure/active-directory/active-directory-saas-access-panel-introduction).
## <a name="additional-resources"></a>Ek kaynaklar
- [SaaS uygulamaları Azure Active Directory ile tümleştirme hakkında öğreticiler](https://docs.microsoft.com/azure/active-directory/active-directory-saas-tutorial-list)
- [Azure Active Directory ile uygulama erişimi ve çoklu oturum açma özellikleri nelerdir?](https://docs.microsoft.com/azure/active-directory/active-directory-appssoaccess-whatis)
- [Azure Active Directory'de koşullu erişim nedir?](https://docs.microsoft.com/azure/active-directory/conditional-access/overview)
| 50.318627 | 355 | 0.781296 | tur_Latn | 0.998957 |
9aed889b8330d1c93289575bb2518d169c05ee5e | 1,522 | md | Markdown | _cards/cdogs.md | loneil/common-service-showcase | 44987b6442825cc828ba3db34bdf0682a7021da6 | [
"Apache-2.0"
] | null | null | null | _cards/cdogs.md | loneil/common-service-showcase | 44987b6442825cc828ba3db34bdf0682a7021da6 | [
"Apache-2.0"
] | 1 | 2020-08-14T18:12:47.000Z | 2020-08-14T18:12:47.000Z | _cards/cdogs.md | loneil/common-service-showcase | 44987b6442825cc828ba3db34bdf0682a7021da6 | [
"Apache-2.0"
] | null | null | null | ---
name: CDOGS
title: Common Document Generation Service
type: service
order: 10
permalink: /cdogs.html
img:
path: /assets/images/cdogs.svg
alt: CDOGS
urls:
github: https://github.com/bcgov/common-document-generation-service
docs: https://cdogs-master-idcqvl-prod.pathfinder.gov.bc.ca/api/v2/docs
---
<div class="row">
<div class="col-lg-12 text-center">
{% if page.img %}
<img class="img-fluid" src="{{ site.baseurl }}{{page.img.path }}" alt="{{ page.img.alt }}">
{% endif %}
</div>
<div class="col-md-12">
<div><p>Leverage your structured datasets and your business templates to automatically populate printable documents, spreadsheets, presentations, or PDFs using the Common Document Generation Service.
</p></div>
<div class="h5">Capabilities</div>
<div><p>
The API can generate any PDF or XML-based documents such as docx, xlsx, pptx, odt, ods, odp, and html. Examples of XML-based editors include Microsoft Office™, LibreOffice™ or OpenOffice™.
</p>
<p>The CDOGS API is capable of doing the following:<ol>
<li>Merge complex datasets into document templates</li>
<li>Supports any XML-based document templates including but not limited to Microsoft Office™, LibreOffice™ or OpenOffice™</li>
<li>Rich templating library support leveraging the <a href="https://carbone.io" target="_blank">Carbone JS library</a></li>
</ol>
</p>
</div>
</div>
</div>
| 41.135135 | 209 | 0.67477 | eng_Latn | 0.494661 |
9aed978a915babe5947541e01306313e96e559ea | 1,502 | md | Markdown | doc/install.md | sry309/asset-scan | 1ff36177a2225420d9b0515efac2b0c7170e5aa8 | [
"MIT"
] | null | null | null | doc/install.md | sry309/asset-scan | 1ff36177a2225420d9b0515efac2b0c7170e5aa8 | [
"MIT"
] | null | null | null | doc/install.md | sry309/asset-scan | 1ff36177a2225420d9b0515efac2b0c7170e5aa8 | [
"MIT"
] | 1 | 2020-04-02T15:44:34.000Z | 2020-04-02T15:44:34.000Z | # 安装文档
## 机器配置
由于Es运行比较吃内存，建议Es和Kibana放在一台机器上（内存4G及以上）
若Es、Kibana和asset-scan放置在一台机器，建议内存8G及以上（最少6G）
## nmap和masscan安装
**nmap建议安装最新的7.8版本，较之前有明显的提升**
### nmap安装
```wget https://nmap.org/dist/nmap-7.80-1.x86_64.rpm && rpm -ivh nmap-7.80-1.x86_64.rpm```
### masscan安装
```yum install -y masscan```
## 安装 Elasticsearch 5.6.8版本(暂不支持6.x及以上版本版本)
- Centos安装java环境
```yum -y install java-1.8.0-openjdk*```
- 下载Es并解压
```
wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-5.6.8.tar.gz && tar -zxvf elasticsearch-5.6.8.tar.gz -C /opt
```
- 新建一个非 root 权限用户，-p 后跟设定的密码，ES就使用这个用户起。
```
groupadd elasticsearch && useradd elasticsearch -g elasticsearch -p Es12345678
```
- 修改文件夹所属用户和组为 elasticsearch:elasticsearch
```
chown -R elasticsearch:elasticsearch /opt/elasticsearch-5.6.8
```
- Centos7以下系统在config/elasticsearch.yml中添加
```
bootstrap.system_call_filter: false
```
- 启动Es
```
su - elasticsearch -c '/opt/elasticsearch-5.6.8/bin/elasticsearch -d'
```
- curl下确认Es启动成功
```
curl -XGET -s "http://localhost:9200/_cluster/health?pretty"
```
## 安装 Kibana 5.6.8版本
- 下载Kibana并解压
```
wget https://artifacts.elastic.co/downloads/kibana/kibana-5.6.8-linux-x86_64.tar.gz && tar -zxvf kibana-5.6.8-linux-x86_64.tar.gz -C /opt
```
- 在/opt/kibana-5.6.8-linux-x86_64/config/kibana.yml中增加以下配置
```
server.host: "0.0.0.0"
```
- 浏览器中输入：http://xx.xx.xx.xx:5601（kibana所在ip地址），访问成功后，点击左侧菜单栏`Management`,配置索引。
`Index pattern`中输入`scan-*`，`Time Filter field name`下拉框选择`time`字段，即完成kibana的配置
| 19.25641 | 137 | 0.714381 | yue_Hant | 0.15179 |
9aedcc0f4b9679e8a6e3698a4e1c74648f4c6339 | 358 | md | Markdown | src/pages/doodlebook/book-1/8.md | nbunner-personal/wupadupa-gatsbyjs | 20bfff697d8cbb0724b097d1fbc4213e7cd3adc1 | [
"MIT"
] | null | null | null | src/pages/doodlebook/book-1/8.md | nbunner-personal/wupadupa-gatsbyjs | 20bfff697d8cbb0724b097d1fbc4213e7cd3adc1 | [
"MIT"
] | 6 | 2021-03-09T10:36:14.000Z | 2022-02-26T14:35:00.000Z | src/pages/doodlebook/book-1/8.md | nbunner-personal/wupadupa-gatsbyjs | 20bfff697d8cbb0724b097d1fbc4213e7cd3adc1 | [
"MIT"
] | null | null | null | ---
layout: doodlebook
title: Wupadupa doodlebook - doodle 8 from book 1
description: Doodle 8 from book 1 - Comments and doodles that capture the essence of this event
slug: /doodlebook/book-1/doodle-8.html
book: 1
doodle_image: ../../../images/doodlebook/210204_08.jpg
ref: 8
---
| 35.8 | 97 | 0.589385 | eng_Latn | 0.35963 |
9aee7f5f927a1abb8aa0e741b4bc93af80ef78c1 | 738 | md | Markdown | content/catalogue/22.md | thegetty/cva10 | 0202a573b4b696f91bc54d4fb78703e1094581db | [
"CC-BY-4.0"
] | null | null | null | content/catalogue/22.md | thegetty/cva10 | 0202a573b4b696f91bc54d4fb78703e1094581db | [
"CC-BY-4.0"
] | 12 | 2019-07-18T20:01:30.000Z | 2022-02-10T18:43:17.000Z | content/catalogue/22.md | thegetty/cva10 | 0202a573b4b696f91bc54d4fb78703e1094581db | [
"CC-BY-4.0"
] | null | null | null | ---
label: 22
weight: 122
object:
- id: 22
type: entry
---
## Provenance
–1976, Max and Linda Palevsky (Los Angeles, California); 1976, donated to the J. Paul Getty Museum.
## Shape and Ornament
Single fragment from the body of a vessel.
## Subject
Part of a chariot, with the upper section of the wheel.
## Attribution and Date
Unattributed. Fifth century B.C.
## Dimensions and Condition
Maximum preserved dimension 3.65 cm. Surface worn, especially interior. Nicks and scratches; chips missing. Interior black.
## Technical Features
Preliminary sketch. Relief contour. Dilute glaze inside.
## Bibliography
Not previously published.
## Comparanda
For chariots, see {{< q-abbr "Manakidou, *Parastaseis me armata*" >}}.
| 18.45 | 123 | 0.734417 | eng_Latn | 0.954043 |
9aefd941db4cb6770a953eee74bca3a86c2a8931 | 1,540 | md | Markdown | VBA/Access-VBA/articles/application-loadpicture-method-access.md | oloier/VBA-content | 6b3cb5769808b7e18e3aff55a26363ebe78e4578 | [
"CC-BY-4.0",
"MIT"
] | 584 | 2015-09-01T10:09:09.000Z | 2022-03-30T15:47:20.000Z | VBA/Access-VBA/articles/application-loadpicture-method-access.md | oloier/VBA-content | 6b3cb5769808b7e18e3aff55a26363ebe78e4578 | [
"CC-BY-4.0",
"MIT"
] | 585 | 2015-08-28T20:20:03.000Z | 2018-08-31T03:09:51.000Z | VBA/Access-VBA/articles/application-loadpicture-method-access.md | oloier/VBA-content | 6b3cb5769808b7e18e3aff55a26363ebe78e4578 | [
"CC-BY-4.0",
"MIT"
] | 590 | 2015-09-01T10:09:09.000Z | 2021-09-27T08:02:27.000Z | ---
title: Application.LoadPicture Method (Access)
keywords: vbaac10.chm12555
f1_keywords:
- vbaac10.chm12555
ms.prod: access
api_name:
- Access.Application.LoadPicture
ms.assetid: d7e64367-c8f2-22c3-6e6e-18eaae9ed07a
ms.date: 06/08/2017
---
# Application.LoadPicture Method (Access)
The **LoadPicture** method loads a graphic into an ActiveX control.
## Syntax
_expression_. **LoadPicture**( ** _FileName_** )
_expression_ A variable that represents an **Application** object.
### Parameters
|**Name**|**Required/Optional**|**Data Type**|**Description**|
|:-----|:-----|:-----|:-----|
| _FileName_|Required|**String**|The file name of the graphic to be loaded. The graphic can be a bitmap file (.bmp), icon file (.ico), run-length encoded file (.rle), or metafile (.wmf).|
### Return Value
Object
## Remarks
Assign the return value of the **LoadPicture** method to the **Picture** property of an ActiveX control to dynamically load a graphic into the control. The following example loads a bitmap into a control called OLECustomControl on an Orders form:
```vb
Set Forms!Orders!OLECustomControl.Picture = _
LoadPicture("Stars.bmp")
```
**Note** You can't use the **LoadPicture** method to set the **Picture** property of an image control. This method works with ActiveX controls only. To set the **Picture** property of an image control, simply assign to it a string specifying the file name and path of the desired graphic.
## See also
#### Concepts
[Application Object](application-object-access.md)
| 25.245902 | 291 | 0.721429 | eng_Latn | 0.776766 |
9af0476537912dbff20cb2b24bd964a106a3c502 | 559 | md | Markdown | instructors_notes.md | olendorf/github_for_researchers | a562e84138274d708d785b35383da2ef11688bef | [
"MIT"
] | null | null | null | instructors_notes.md | olendorf/github_for_researchers | a562e84138274d708d785b35383da2ef11688bef | [
"MIT"
] | 4 | 2019-10-28T14:18:57.000Z | 2022-02-26T05:37:36.000Z | instructors_notes.md | olendorf/github_for_researchers | a562e84138274d708d785b35383da2ef11688bef | [
"MIT"
] | null | null | null | ---
# Found in _layouts/instructors_notes.html
layout: instructors_notes
# Override the workshop title if you want it to be different
# The :title value in your _config.yml will be used by default.
title: Instructors' Notes
setup:
- title: Computing
description: |
Attendees should have computers. They should also have a bash style terminal.
Those with Macs should be fine. Those with windows will need to download
[Git for Windows](https://git-scm.com/download/win) and use the GitBash program
that comes with that.
---
| 26.619048 | 85 | 0.728086 | eng_Latn | 0.998293 |
9af052dea586077db3d4ca0429758613f50a72e7 | 918 | md | Markdown | content/neta/2019-03-04-190303-45325888.md | tcgriffith/owaraisite | 31254bf7f3fbeece1bd68698f9d020069cc74fb1 | [
"MIT"
] | 5 | 2019-02-28T04:52:09.000Z | 2020-05-25T11:34:13.000Z | content/neta/2019-03-04-190303-45325888.md | tcgriffith/owaraisite | 31254bf7f3fbeece1bd68698f9d020069cc74fb1 | [
"MIT"
] | 26 | 2017-10-24T16:10:44.000Z | 2019-10-14T04:30:35.000Z | content/neta/2019-03-04-190303-45325888.md | tcgriffith/owaraisite | 31254bf7f3fbeece1bd68698f9d020069cc74fb1 | [
"MIT"
] | 8 | 2017-10-02T06:51:19.000Z | 2022-03-07T21:12:38.000Z | ---
combi: 镰鼬
title: 如果把短剧改编成电视剧的话 20190303 花子&镰鼬&コロコロチキチキペッパーズ
author:
- nonkotori字幕组
- nonkotori
zmz: nonkotori字幕组
publishdate: '2019-03-03'
bangumi: 段子
date: '2019-03-14'
slug: 2019-03-04-190303-45325888
description: 段子•190303
weight: 9686.0
bangumis:
- 段子
tags:
- コロコロチキチキペッパーズ
- 镰鼬
- 花子
- ~
categories:
- nonkotori字幕组
- nonkotori
brief: 日tv特番 ネタドラ ～漫才･コントを原作にドラマ化～ .明明是自己拍的短片秋山还是看哭了w .米津玄师的lemon超催泪（我也（。 .滨家真的好帅气><
.山ちゃん的脑洞还是一如既往的不思议hhh .纳达尔这家伙果然还是超级惹人生气 .一边翻一边想着纳达尔这个谁能得到好处啊
---
# 简介
日tv特番 ネタドラ ～漫才･コントを原作にドラマ化～
.明明是自己拍的短片秋山还是看哭了w
.米津玄师的lemon超催泪（我也（。
.滨家真的好帅气><
.山ちゃん的脑洞还是一如既往的不思议hhh
.纳达尔这家伙果然还是超级惹人生气
.一边翻一边想着纳达尔这个谁能得到好处啊
[去B站观看](https://www.bilibili.com/video/av45325888/)
<div class ="resp-container"><iframe class="testiframe" src="//player.bilibili.com/player.html?aid=45325888"", scrolling="no", allowfullscreen="true" > </iframe></div>
| 23.538462 | 168 | 0.738562 | yue_Hant | 0.19159 |
9af10aa564cbae9a1a3c934408d4cf39967ccd9e | 1,986 | md | Markdown | Documentation/GitHelp.md | khangthk/ITK | f3c12edaf9cef07dbc34107e1a8aec9859204116 | [
"Apache-2.0"
] | null | null | null | Documentation/GitHelp.md | khangthk/ITK | f3c12edaf9cef07dbc34107e1a8aec9859204116 | [
"Apache-2.0"
] | null | null | null | Documentation/GitHelp.md | khangthk/ITK | f3c12edaf9cef07dbc34107e1a8aec9859204116 | [
"Apache-2.0"
] | null | null | null | Git Help
========
Additional information about [Git] may be obtained at these sites:
* ITK Git cheat sheet
* [ITK Git PDF desk reference](./GitCheatSheet.pdf)
* General resources
* [Git Homepage][Git]
* [GitHub Try Git In Your Browser](https://try.github.io/)
* [Git Documentation Wiki](https://git.wiki.kernel.org/index.php/GitDocumentation)
* [Everyday Git](https://www.kernel.org/pub/software/scm/git/docs/giteveryday.html)
* [GitHub Services](https://services.github.com/)
* Development models with Git
* [A Visual Git Reference](marklodato.github.io/visual-git-guide/)
* [A successful Git branching model](https://nvie.com/posts/a-successful-git-branching-model/)
* [PDF](github.com/downloads/nvie/gitflow/Git-branching-model.pdf) version.
* [LearnGitBranching - Web application designed to help beginners grasp the powerful concepts behind branching](https://learngitbranching.js.org/)
* Cheat sheets
* [Git sheat sheet](http://cheat.errtheblog.com/s/git)
* [GitHub Git cheat sheet](https://services.github.com/on-demand/downloads/github-git-cheat-sheet/)
* [PDF](https://services.github.com/on-demand/downloads/github-git-cheat-sheet.pdf) version.
* Git books
* [Pro Git book](https://git-scm.com/book/en/v2)
* [Pro Git: Setup](https://git-scm.com/book/en/v2/Getting-Started-First-Time-Git-Setup)
* [Pro Git: Basic Branching](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging)
* [Pro Git: Recording Changes](https://git-scm.com/book/en/Git-Basics-Recording-Changes-to-the-Repository)
* [Pro Git: Changing the Last Commit](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History#Changing-the-Last-Commit)
* [Pro Git: Changing Multiple Commits](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History#Changing-Multiple-Commit-Messages)
* [Pro Git: Rebasing](https://git-scm.com/book/en/v2/Git-Branching-Rebasing)
[Git]: https://git-scm.com/
| 56.742857 | 150 | 0.710977 | yue_Hant | 0.414239 |
9af1400dd1a6a17362c97ff0309f94b751fbe10b | 368 | md | Markdown | README.md | L4ngu0r/audio-desktop-cast | f3dca4561e014a895afc50124c8c4731cddd6ac8 | [
"MIT"
] | null | null | null | README.md | L4ngu0r/audio-desktop-cast | f3dca4561e014a895afc50124c8c4731cddd6ac8 | [
"MIT"
] | null | null | null | README.md | L4ngu0r/audio-desktop-cast | f3dca4561e014a895afc50124c8c4731cddd6ac8 | [
"MIT"
] | null | null | null | # desktop-audio-cast
Based on [mafintosh@chromecasts](https://github.com/mafintosh/chromecasts).
A tiny interface in Node to control Google cast devices.
```
npm install
node index
```
## Link
To use along with [audio-streamer] (https://github.com/L4ngu0r/audio-streamer)
## Todos
- keep data in form
- standalone packaging
- use of notification
## License
MIT | 16 | 78 | 0.73913 | eng_Latn | 0.508605 |
9af2019e16d4aff8b229206d423661a1761ba13a | 724 | md | Markdown | docs/packages/tcl/README.md | dustdfg/book | 48e03969819469d77c0c9d93d0561afc2381c03c | [
"MIT"
] | 76 | 2021-04-26T15:45:49.000Z | 2021-07-08T02:05:58.000Z | docs/packages/tcl/README.md | dustdfg/book | 48e03969819469d77c0c9d93d0561afc2381c03c | [
"MIT"
] | 307 | 2021-04-21T19:14:00.000Z | 2021-07-08T20:45:50.000Z | docs/packages/tcl/README.md | dustdfg/book | 48e03969819469d77c0c9d93d0561afc2381c03c | [
"MIT"
] | 13 | 2021-04-20T14:16:00.000Z | 2021-07-03T16:19:01.000Z | # tcl
Пакет содержит 'командный язык инструментов' - скриптовый язык высокого уровня. Он необходим для выполнения тестов некоторых пакетов, и будет установлен только во временный инструментарий.
Версия: **8.6.12**
Размер: **9.87Mb**
Приоритет: **Необязательный**
Оригинальное расположение: [https://downloads.sourceforge.net/tcl/tcl8.6.12-src.tar.gz](https://downloads.sourceforge.net/tcl/tcl8.6.12-src.tar.gz)
Ссылка для загрузки: [https://lx4u.ru/downloads/packages/tcl8.6.12-src.tar.gz](https://lx4u.ru/downloads/packages/tcl8.6.12-src.tar.gz)
MD5: **87ea890821d2221f2ab5157bc5eb885f**
Домашняя страница: [https://sourceforge.net/projects/tcl](https://sourceforge.net/projects/tcl)
SBU: **3.8** | 38.105263 | 189 | 0.747238 | rus_Cyrl | 0.535369 |
9af2a67e8076b7468db7002a7d749e03d3b28833 | 1,004 | md | Markdown | exampleSite/content/en/documentation/reference/functions/tpl/images/images/index.md | gohugoio/gohugoioTheme2 | 7d1ba30918e723576558b8340b761e5b6f71a758 | [
"Apache-2.0"
] | 6 | 2022-03-03T12:32:51.000Z | 2022-03-11T13:55:23.000Z | exampleSite/content/en/documentation/reference/functions/tpl/images/images/index.md | gohugoio/gohugoioTheme2 | 7d1ba30918e723576558b8340b761e5b6f71a758 | [
"Apache-2.0"
] | 29 | 2022-03-03T11:55:04.000Z | 2022-03-16T18:16:11.000Z | exampleSite/content/en/documentation/reference/functions/tpl/images/images/index.md | gohugoio/gohugoioTheme2 | 7d1ba30918e723576558b8340b761e5b6f71a758 | [
"Apache-2.0"
] | 4 | 2022-03-03T12:34:02.000Z | 2022-03-07T18:39:26.000Z |
---
title: "images"
linkTitle: "images"
description: "Images is Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. "
hugoSymbol: TODO
tags:
- images
---
## images.Config {#images_namespace_config}
\(path [any](/documentation/reference/gotypes/#any)\) → [Config](/documentation/reference/objects/image/config)
{.funcsig}
Config returns the image.Config for the specified `path` relative to the
working directory.
{{< docs/func-aliases "images.Config" >}}
{{< docs/func-examples "images.Config" >}}
## images.Filter {#images_namespace_filter}
\(args [...any](/documentation/reference/gotypes/#any)\) → [ImageResource](/documentation/reference/objects/resources/images/imageresource)
{.funcsig}
{{< docs/func-aliases "images.Filter" >}}
{{< docs/func-examples "images.Filter" >}}
| 14.985075 | 257 | 0.72012 | yue_Hant | 0.458879 |
9af2b353f8d49965475274ad3b087bf145324072 | 568 | md | Markdown | README.md | Symontoclay/demo1_linear_code | 321fbaa1e5333c25d989aee466f35f37cebf651c | [
"MIT"
] | null | null | null | README.md | Symontoclay/demo1_linear_code | 321fbaa1e5333c25d989aee466f35f37cebf651c | [
"MIT"
] | null | null | null | README.md | Symontoclay/demo1_linear_code | 321fbaa1e5333c25d989aee466f35f37cebf651c | [
"MIT"
] | null | null | null | # demo1_linear_code
[](https://symontoclay.github.io/docs/index.html)
In the demoscene you can see a simplest NPC behaviour. An NPC walks by a path which is defined on SymOntoClay DSL.
[Video on YouTube](https://youtu.be/XB80vRnGoy4)
<hr/>
It is a demoscene of [SymOntoClay](https://symontoclay.github.io).
Main repositories:
* [Core](https://github.com/Symontoclay/SymOntoClay)
* [Components for Unity](https://github.com/Symontoclay/SymOntoClayAsset)
| 33.411765 | 122 | 0.769366 | yue_Hant | 0.516518 |
9af4f4f3e78cdce9781ed6d354a7a357a214f0c5 | 624 | md | Markdown | _posts/2010-02-27-tobb_avi_osszefuzese.md | asalamon74/commandlineblog | 420004f18d4ee107aa0510d4fcc8cb060b0034ef | [
"CC0-1.0"
] | null | null | null | _posts/2010-02-27-tobb_avi_osszefuzese.md | asalamon74/commandlineblog | 420004f18d4ee107aa0510d4fcc8cb060b0034ef | [
"CC0-1.0"
] | null | null | null | _posts/2010-02-27-tobb_avi_osszefuzese.md | asalamon74/commandlineblog | 420004f18d4ee107aa0510d4fcc8cb060b0034ef | [
"CC0-1.0"
] | null | null | null | ---
layout: post
title: 'Több avi összefűzése'
permalink: /2010/02/27/tobb_avi_osszefuzese
post_id: 1734760
categories:
- avi
- mencoder
- transcode
---
Több avi fájlt ( azonos felbontás, kódolás,... ) igen könnyen egymás után kapcsolhatunk újrakonvertálás nélkül az
```
avimerge
```
paranccsal ( a
[transcode](http://tcforge.berlios.de/) programcsomag része ):
```
avimerge -o nagy.avi -i kis1.avi kis2.avi kis3.avi
```
Ha inkább
[mencoder](http://www.mplayerhq.hu/)t szeretnénk használni, akkor a következő parancsot használhatjuk:
```
mencoder -ovc copy -oac copy -o nagy.avi kis1.avi kis2.avi kis3.avi
```
| 23.111111 | 114 | 0.722756 | hun_Latn | 0.999049 |
9af55088c2933c6c630946c6bc7fabdf8a07a8e5 | 162 | md | Markdown | SUPPORT.md | D3strukt0r/dotfiles | 7a808eb83be52ac038b99351972fc0104c202126 | [
"MIT"
] | null | null | null | SUPPORT.md | D3strukt0r/dotfiles | 7a808eb83be52ac038b99351972fc0104c202126 | [
"MIT"
] | null | null | null | SUPPORT.md | D3strukt0r/dotfiles | 7a808eb83be52ac038b99351972fc0104c202126 | [
"MIT"
] | null | null | null | # How to get support
If you need help please try to solve it by creating an issue on the [discussions page](https://github.com/D3strukt0r/dotfiles/discussions).
| 40.5 | 139 | 0.777778 | eng_Latn | 0.989941 |
9af60de929d2aae7f7283a63a707f15e203fceaf | 163 | md | Markdown | _posts/0000-01-02-kgr980.md | kgr980/github-slideshow | 8c453671c6deb5f4742476fb584d490c68631fd2 | [
"MIT"
] | null | null | null | _posts/0000-01-02-kgr980.md | kgr980/github-slideshow | 8c453671c6deb5f4742476fb584d490c68631fd2 | [
"MIT"
] | 3 | 2021-03-17T03:16:23.000Z | 2021-03-18T01:35:02.000Z | _posts/0000-01-02-kgr980.md | kgr980/github-slideshow | 8c453671c6deb5f4742476fb584d490c68631fd2 | [
"MIT"
] | null | null | null | ---
layout: slide
title: "Welcome to our second slide!"
---
Hello this is the first change apply to this file per lab suggestions
Use the left arrow to go back!
| 23.285714 | 69 | 0.730061 | eng_Latn | 0.999792 |
9af69e4aa4c903f92d8fd538b9a490d7860ae1e8 | 710 | md | Markdown | .github/RELEASE_TEMPLATE.md | Kadino/YarnSpinner | 78448d6b3af52ca58e443717ffef256959356c38 | [
"MIT"
] | 762 | 2016-02-10T11:34:40.000Z | 2019-09-17T05:48:09.000Z | .github/RELEASE_TEMPLATE.md | Kadino/YarnSpinner | 78448d6b3af52ca58e443717ffef256959356c38 | [
"MIT"
] | 158 | 2016-02-08T20:55:29.000Z | 2019-09-17T04:41:40.000Z | .github/RELEASE_TEMPLATE.md | Kadino/YarnSpinner | 78448d6b3af52ca58e443717ffef256959356c38 | [
"MIT"
] | 127 | 2016-02-12T19:23:56.000Z | 2019-09-02T07:53:13.000Z | <!-- RELEASE_TEMPLATE.md is not a formally supported file used by GitHub. This file is used by .github/workflows/release.yml to add a release notes preface. -->
This is the compiler for Yarn Spinner. If you want to use Yarn Spinner in a Unity game, please see [the releases page for Yarn Spinner for Unity](https://github.com/YarnSpinnerTool/YarnSpinner-Unity/releases/)!
Yarn Spinner is made possible by your generous patronage. Please consider supporting Yarn Spinner's development by [becoming a patron](https://patreon.com/secretlab)!
<a href="https://patreon.com/secretlab"><img width="200" src="https://user-images.githubusercontent.com/901768/71883373-6f40ff80-318a-11ea-9d3a-01f1f58cb39e.png"></a>
| 78.888889 | 210 | 0.780282 | eng_Latn | 0.96539 |
9af7271b605873f9db6316fc0c721cdf0bd870b0 | 23 | md | Markdown | CHANGELOG.md | jlaso/variable-iterator | f7353d587a475c62f839545f49f9dc5a086721a5 | [
"MIT"
] | null | null | null | CHANGELOG.md | jlaso/variable-iterator | f7353d587a475c62f839545f49f9dc5a086721a5 | [
"MIT"
] | null | null | null | CHANGELOG.md | jlaso/variable-iterator | f7353d587a475c62f839545f49f9dc5a086721a5 | [
"MIT"
] | null | null | null | # 1.0 creation
* * *
| 5.75 | 15 | 0.434783 | eng_Latn | 0.897365 |
9af7c1fdcff95d3aa2146838efbd1d96449752e4 | 1,785 | md | Markdown | AlchemyInsights/got-a-parameter-cannot-be-found-error.md | pebaum/OfficeDocs-AlchemyInsights-pr.el-GR | f2f469292bc0b615c3f81ba45b95269e1e10cdd0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | AlchemyInsights/got-a-parameter-cannot-be-found-error.md | pebaum/OfficeDocs-AlchemyInsights-pr.el-GR | f2f469292bc0b615c3f81ba45b95269e1e10cdd0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | AlchemyInsights/got-a-parameter-cannot-be-found-error.md | pebaum/OfficeDocs-AlchemyInsights-pr.el-GR | f2f469292bc0b615c3f81ba45b95269e1e10cdd0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Έχετε ένα σφάλμα "Δεν είναι δυνατή η ανήκυξη της παραμέτρου";
ms.author: pebaum
author: pebaum
ms.date: 04/21/2020
ms.audience: ITPro
ms.topic: article
ROBOTS: NOINDEX, NOFOLLOW
localization_priority: Normal
ms.custom:
- "683"
- "3500008"
ms.assetid: 5070ca31-9ccf-4408-865c-d36912450196
ms.openlocfilehash: 8f07a2dc92315e5466ea126243adf46cff192934
ms.sourcegitcommit: 55eff703a17e500681d8fa6a87eb067019ade3cc
ms.translationtype: MT
ms.contentlocale: el-GR
ms.lasthandoff: 04/22/2020
ms.locfileid: "43722232"
---
# <a name="migrating-email-from-imap-email-system-to-microsoft-365"></a>Μετεγκατάσταση ηλεκτρονικού ταχυδρομείου από το σύστημα ηλεκτρονικού ταχυδρομείου IMAP στο Microsoft 365
Για να μετεγκαταστήσετε μηνύματα ηλεκτρονικού ταχυδρομείου από ένα σύστημα αλληλογραφίας IMAP, ακολουθήστε αυτήν τη διαδικασία: [Μετεγκατάσταση IMAP στο κέντρο διαχείρισης της Microsoft 365](https://docs.microsoft.com/Exchange/mailbox-migration/migrating-imap-mailboxes/imap-migration-in-the-admin-center)
Πολλοί μεγάλοι οργανισμοί θα πρέπει να προγραμματίσουν προσεκτικά για να διαχειριστούν τις προσδοκίες χρηστών. Το [άρθρο Τι πρέπει να γνωρίζετε σχετικά με τη μετεγκατάσταση των γραμματοκιβωτίων IMAP στο άρθρο Microsoft 365](https://docs.microsoft.com/Exchange/mailbox-migration/migrating-imap-mailboxes/migrating-imap-mailboxes) θα σας βοηθήσει να διαχειριστείτε την αλλαγή.
Ελέγξτε επίσης τη σελίδα [Υιοθέτηση του Microsoft 365 με το FastTrack](https://www.microsoft.com/fasttrack/microsoft-365/office-365) για βοήθεια σχετικά με τη μετεγκατάσταση, εάν είναι κατάλληλη.
Ελέγξτε επίσης τη σελίδα [Υιοθέτηση του Microsoft 365 με το FastTrack](https://www.microsoft.com/fasttrack/microsoft-365/office-365) για βοήθεια σχετικά με τη μετεγκατάσταση, εάν είναι κατάλληλη.
| 57.580645 | 374 | 0.820728 | ell_Grek | 0.988518 |
9af9fc266a9c1768247b8504ab45ce87c0594bfd | 2,070 | md | Markdown | maven_dependency.md | liujingxing/okhttp-RxHttp | 3cd441c6369e9cd077d9787166468a3b5a92189d | [
"Apache-2.0"
] | 1,919 | 2019-12-28T03:38:33.000Z | 2021-05-10T02:47:46.000Z | maven_dependency.md | liujingxing/okhttp-RxHttp | 3cd441c6369e9cd077d9787166468a3b5a92189d | [
"Apache-2.0"
] | 197 | 2020-01-02T11:43:15.000Z | 2021-05-08T05:32:38.000Z | maven_dependency.md | liujingxing/okhttp-RxHttp | 3cd441c6369e9cd077d9787166468a3b5a92189d | [
"Apache-2.0"
] | 246 | 2019-12-28T07:58:06.000Z | 2021-04-27T08:53:35.000Z | ## 注意
- RxHttp支持`RxJava2和RxJava3`，依赖时需要选择对应的注解处理器，如不需要支持RxJava，则可不选择注解处理器
```xml
<dependencies>
<!--必须-->
<dependency>
<groupId>com.squareup.okhttp3</groupId>
<artifactId>okhttp</artifactId>
<version>4.9.1</version>
</dependency>
<!--必须-->
<dependency>
<groupId>com.github.liujingxing.rxhttp</groupId>
<artifactId>rxhttp</artifactId>
<version>2.7.2</version>
</dependency>
<!-- 非必须 RxJava2/RxJava3 二选一或都不选 -->
<!-- <dependency>
<groupId>io.reactivex.rxjava2</groupId>
<artifactId>rxjava</artifactId>
<version>2.2.8</version>
</dependency> -->
<dependency>
<groupId>io.reactivex.rxjava3</groupId>
<artifactId>rxjava</artifactId>
<version>3.1.1</version>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.8.1</version>
<configuration>
<source>1.8</source>
<target>1.8</target>
<!--必须-->
<annotationProcessorPaths>
<path>
<groupId>com.github.liujingxing.rxhttp</groupId>
<artifactId>rxhttp-compiler</artifactId>
<version>2.7.2</version>
</path>
</annotationProcessorPaths>
<!--RxJava注解处理器，非必须-->
<annotationProcessors>
<!--以下两个注解处理器，分别对应RxJava2/RxJava3，二选一即可 -->
<!-- <annotationProcessor>
com.rxhttp.compiler.maven.AnnotationRxJava2Processor
</annotationProcessor> -->
<annotationProcessor>
com.rxhttp.compiler.maven.AnnotationRxJava3Processor
</annotationProcessor>
</annotationProcessors>
</configuration>
</plugin>
</plugins>
</build>
```
| 29.571429 | 76 | 0.528019 | yue_Hant | 0.34186 |
9afa01e98ff810af9980f4d241f7bbe9b7bcf250 | 224 | md | Markdown | datasourcemanager/README.md | subinsoman/seahorse | 7b48dc3849512cd27be6cbd8a16ca97a51cc7fab | [
"Apache-2.0"
] | 111 | 2017-09-12T16:17:02.000Z | 2021-09-13T18:37:07.000Z | datasourcemanager/README.md | subinsoman/seahorse | 7b48dc3849512cd27be6cbd8a16ca97a51cc7fab | [
"Apache-2.0"
] | 78 | 2017-09-19T09:13:17.000Z | 2021-06-23T13:31:50.000Z | datasourcemanager/README.md | sfahad1414/seahorse | a3293e6f5d354d61f8c4e0dec00ed8a888e969f6 | [
"Apache-2.0"
] | 46 | 2017-09-15T20:25:05.000Z | 2022-01-03T03:54:50.000Z | ## DEV MANUAL
# Run datasourcemanager in dev:
```
sbt datasourcemanager/runtime:run
wget http://localhost:8080/datasourcemanager/v1/datasources
# Swagger UI
go to http://localhost:8080/datasourcemanager/v1/swagger-ui
```
| 18.666667 | 59 | 0.772321 | kor_Hang | 0.464782 |
9afaa485c768e85470ff323dddd6c1220935f532 | 657 | md | Markdown | en/functions/quickstart/create-trigger/index.md | OlesyaAkimova28/docs | 08b8e09d3346ec669daa886a8eda836c3f14a0b0 | [
"CC-BY-4.0"
] | 1 | 2022-01-16T21:56:33.000Z | 2022-01-16T21:56:33.000Z | en/functions/quickstart/create-trigger/index.md | OlesyaAkimova28/docs | 08b8e09d3346ec669daa886a8eda836c3f14a0b0 | [
"CC-BY-4.0"
] | null | null | null | en/functions/quickstart/create-trigger/index.md | OlesyaAkimova28/docs | 08b8e09d3346ec669daa886a8eda836c3f14a0b0 | [
"CC-BY-4.0"
] | null | null | null | ---
title: Creating a trigger in Yandex Cloud Functions
description: "Create a trigger in Yandex Cloud Functions that will launch a function on an event or schedule. Examples of triggers — creating a timer, creating a trigger for Yandex Message Queue, Object Storage, Container Registry, Cloud Logs and Yandex IoT Core."
---
# Creating a trigger
Create a trigger that will run a function when a certain event occurs or on a schedule.
- [{#T}](timer-quickstart.md)
- [{#T}](ymq-trigger-quickstart.md)
- [{#T}](os-trigger-quickstart.md)
- [{#T}](cr-trigger-quickstart.md)
- [{#T}](cloudlogs-trigger-quickstart.md)
- [{#T}](iot-core-trigger-quickstart.md)
| 38.647059 | 264 | 0.73516 | eng_Latn | 0.847501 |
9afaba6bfe9e66d6cc6d3eb5c278a33d30897af8 | 1,030 | md | Markdown | src/__tests__/fixtures/unfoldingWord/en_tw/bible/other/barley.md | unfoldingWord/content-checker | 7b4ca10b94b834d2795ec46c243318089cc9110e | [
"MIT"
] | null | null | null | src/__tests__/fixtures/unfoldingWord/en_tw/bible/other/barley.md | unfoldingWord/content-checker | 7b4ca10b94b834d2795ec46c243318089cc9110e | [
"MIT"
] | 226 | 2020-09-09T21:56:14.000Z | 2022-03-26T18:09:53.000Z | src/__tests__/fixtures/unfoldingWord/en_tw/bible/other/barley.md | unfoldingWord/content-checker | 7b4ca10b94b834d2795ec46c243318089cc9110e | [
"MIT"
] | 1 | 2022-01-10T21:47:07.000Z | 2022-01-10T21:47:07.000Z | # barley
## Definition:
The term “barley” refers to a kind of grain that is used to make bread.
* The barley plant has a long stalk with a head at the top where the seeds or grains grow.
* Barley does well in warmer weather so it is often harvested in spring or summer.
* When barley is threshed, the edible seeds are separated from the worthless chaff.
* Barley grain is ground up into flour, which is then mixed with water or oil to make bread.
* If barley is not known, this could be translated as “grain called barley” or “barley grain.”
(See also: [How to Translate Unknowns](rc://en/ta/man/translate/translate-unknown))
(See also: [grain](../other/grain.md), [thresh](../other/thresh.md), [wheat](../other/wheat.md))
## Bible References:
* [1 Chronicles 11:12-14](rc://en/tn/help/1ch/11/12)
* [Job 31:40](rc://en/tn/help/job/31/40)
* [Judges 07:14](rc://en/tn/help/jdg/07/14)
* [Numbers 05:15](rc://en/tn/help/num/05/15)
* [Revelation 06:06](rc://en/tn/help/rev/06/06)
## Word Data:
* Strong’s: H8184, G2915, G2916
| 36.785714 | 96 | 0.703883 | eng_Latn | 0.99724 |
9afbb8093d4bedf97a9de7c8d418ffcbe0ca6598 | 296 | md | Markdown | docs/go/switch.md | jakoubek/Technotes | 7748d20100706e408e1d89c841098f987d0e1492 | [
"MIT"
] | null | null | null | docs/go/switch.md | jakoubek/Technotes | 7748d20100706e408e1d89c841098f987d0e1492 | [
"MIT"
] | 3 | 2022-03-27T08:37:43.000Z | 2022-03-30T15:23:46.000Z | docs/go/switch.md | jakoubek/Technotes | 7748d20100706e408e1d89c841098f987d0e1492 | [
"MIT"
] | null | null | null | ---
title: Switch-Statement in Go
section: go
slug: switch
---
# Switch-Statement
```go
switch modus {
case "createJsonFile":
createJsonFile()
case "httpWebserviceTest":
httpWebserviceTest()
}
```
{{ feedback(page.meta.title, page.meta.section, page.meta.slug) }}
| 14.8 | 66 | 0.64527 | kor_Hang | 0.326735 |
9afbb9d27f4605a782c59d3d3f3936d18fc9a663 | 2,314 | md | Markdown | README.md | AJ9/Swift-101-Guard-Statement | b757a01c014eb712fab93ce7b52de7890bcb869b | [
"MIT"
] | null | null | null | README.md | AJ9/Swift-101-Guard-Statement | b757a01c014eb712fab93ce7b52de7890bcb869b | [
"MIT"
] | null | null | null | README.md | AJ9/Swift-101-Guard-Statement | b757a01c014eb712fab93ce7b52de7890bcb869b | [
"MIT"
] | null | null | null | # Swift 101 - Guard Statement
The supplementary Swift Playground to [Swift 101 - Guard Statement](https://medium.com/pretty-swifty/swift-101-guard-statement-9ff5725d4876).
## Playground source
```swift
/*:
# Swift 101 - nil
https://medium.com/pretty-swifty/swift-101-guard-statement-9ff5725d4876
I love working with `guard` statements in my Swift code and you should too, let’s take a closer look…
*/
import UIKit
//Baskets in this example are an array of Items.
typealias Item = String
typealias Basket = [Item]
var basket: Basket = []
func addToBasket(item: Item) {
guard basket.count < 5 else {
print("Basket is full, Item: \(item) not added")
return
}
basket.append(item)
print("Item: \(item) added to basket")
}
addToBasket(item: "Apple")
addToBasket(item: "Orange")
addToBasket(item: "Grapes")
addToBasket(item: "Pear")
addToBasket(item: "Banana")
addToBasket(item: "Strawberry") // Will not be added to the basket as it's already full
// How to avoid silly divide by zero errors
func divide(lhs: Int, rhs: Int) {
guard rhs > 0 else {
print("Without this guard statement, you would be in a pickle")
return
}
let result = lhs / rhs
print("Result: \(result)")
}
divide(lhs: 10, rhs: 0)
divide(lhs: 10, rhs: 2)
// Using guards as super charged if-let statements
//Uncomment the line below to see what happens when an input value is optional
let input: Any? = nil
//Uncomment the line below to see what happens when an input value is not optional
//let input: Any? = 1
func guardIfLetExample(optionalValue: Any?) {
guard let unwrappedValue = optionalValue else {
print("That optional value was nil")
return
}
print("You can now use unwrappedValue safe in the knowledge that it will never be nil. It was \(unwrappedValue)")
}
guardIfLetExample(optionalValue: input)
// A real world example
var favouriteColour: UIColor? //Because not everyone has a favourite (GB) colour (also GB) you know! Yes, I tend to avoid those people too...
func printColour(_ colour: UIColor?) {
guard let unwrappedColour = colour else {
print("Sorry, the colour you provided was nil")
return
}
print(unwrappedColour) //unwrappedColour is not nil!
}
printColour(favouriteColour)
```
| 26.906977 | 141 | 0.695765 | eng_Latn | 0.937784 |
9afccf5884289910b4e0e8529cac89d778b04f9b | 9,863 | md | Markdown | _posts/2010-8-26-考研.md | backup53/1984bbs | 152406c37afab79176f0d094de5ac4cb0c780730 | [
"MIT"
] | 18 | 2020-01-02T21:43:02.000Z | 2022-02-14T02:40:34.000Z | _posts/2010-8-26-考研.md | wzxwj/1984bbs | 152406c37afab79176f0d094de5ac4cb0c780730 | [
"MIT"
] | 3 | 2020-01-01T16:53:59.000Z | 2020-01-05T10:14:11.000Z | _posts/2010-8-26-考研.md | backup53/1984bbs | 152406c37afab79176f0d094de5ac4cb0c780730 | [
"MIT"
] | 13 | 2020-01-20T14:27:39.000Z | 2021-08-16T02:13:21.000Z | ---
layout: default
date: 2010-8-26
title: 考研
categories: 罗马假日公寓
---
# 考研 还是瞎混？
路上没有惊慌
1楼 大 中 小 发表于 2010-8-26 09:28 只看该作者
考研 还是瞎混？
刚刚从一所不入流大学数学系本科毕业，这是一个只能当中小学教师的专业，同班的要么考研走了，要么考上中小学数学教师。由于之前对未来没什么概念，没有规划，从来没有想过当一个教师，导致到现在还没有工作。
我想听听你们的建议，是坚持一下跨专业考研呢？（大概要跨到经济金融类），还是莽撞的进入社会做一些我认为不靠谱的工作呢？
注：1程序员就免了，不想大把大把的掉头发。2之所以认为现在找的工作不靠谱，是因为没有专业基本就只能做一些销售之类的。3不要说“真的猛士敢于直面惨淡的人生正视淋漓的鲜血”这种话，我不是猛士；也不要说“再累再苦就当自己是二百五，再难再险就当自己是二皮脸”，我不是韩寒；也不用说“人生没有迈不过去的坎儿”或者唱“阳光总在风雨后”来安慰我，我还硬朗着呢。
总之，我需要切实可行的建议，谢谢。
---
[Terminusbot](https://github.com/TerminusBot) 整理，讨论请前往 [2049bbs.xyz](http://2049bbs.xyz/)
---
蒋牛牛
带着梦想，滚床单撕内衣
2楼 大 中 小 发表于 2010-8-26 09:45 只看该作者
建议不要瞎混，人生没有目标，就废了。
可以考研，但不要在中国，去国外读。
ilikecunny
只反对不受制约的权力
3楼 大 中 小 发表于 2010-8-26 09:51 只看该作者
别瞎混 没意义，找个工作把，有的发展就好
偷鸡盗8
4楼 大 中 小 发表于 2010-8-26 09:55 只看该作者
学习无止境。
不学无术就有直径了。
nicky_hk
烤鸭党粉丝，十二点党粉丝.
5楼 大 中 小 发表于 2010-8-26 10:08 只看该作者
不知道你考研究生的目的是什么？你已经糊糊涂涂的被别人安排和设置了20几年的生活了，应该去寻找自己真正喜欢做的事情了，如果你不知道喜欢做什么，那就慢慢去尝试呗。简简单单的随大流，只会浪费时间，大学毕业，已经没有多少时间了
蒋牛牛比较厉害,能有人生目标,我没什么大目标,只想做自己喜欢做的事情,让自己的生活变得更好一点
路上没有惊慌
6楼 大 中 小 发表于 2010-8-26 10:25 只看该作者
回复 5楼 nicky_hk 的话题
目的是找到一个方向。高中是自己选的，大学的专业也是自己选的，我并不糊涂，我的大学过得简直快乐死了，我不认为这是浪费时间，也没必要把自己搞的跟苦逼犯一样。另外，我觉得喜欢做的事情和职业不是一回事，毕竟这不是一个让年轻人有安全感的年代，你去做喜欢的事情就意味着你可能填不饱肚子，所以喜欢的事和职业是两码事。
我觉得我太他妈年轻了，干嘛告诉我我已经没有多少时间了？
对啊，我喜欢的事情就是让自己生活变得更好一点。
vincentfon
IT边缘人.
7楼 大 中 小 发表于 2010-8-26 10:32 只看该作者
引用:
> 原帖由 路上没有惊慌 于 2010-8-26 10:25 发表
> 
>
> 目的是找到一个方向。高中是自己选的，大学的专业也是自己选的，我并不糊涂，我的大学过得简直快乐死了，我不认为这是浪费时间，也没必要把自己搞的跟苦逼犯一样。另外，我觉得喜欢做的事情和职业不是一回事，毕竟这
> ...
你太有才了,能够把如此好脾气的人都给搞的有一种强烈的想喷你几句的欲望.
要么好好活,要么你就去死,这里没有人是你妈也没有人愿意当你妈也更加没有人愿意去当你妈去帮你做选择.
都他妈毕业了还有如此情绪和如此混乱的头脑.服了你.
路上没有惊慌
8楼 大 中 小 发表于 2010-8-26 10:46 只看该作者
回复 7楼 vincentfon 的话题
我情绪还不错，而且人家也没喷我几句。
谢谢你，我会好好活的。
核子力量
Twitter.com/hzpower
9楼 大 中 小 发表于 2010-8-26 10:46 只看该作者
感觉能考上就考研
考不上就先找工作干着
佐佐鼬鼬
想怎么说就怎么说
10楼 大 中 小 发表于 2010-8-26 11:29 只看该作者
当老师挺不错的
追梦
有需要充值的组员，请支持下小店，谢谢。店铺地址：http://wangxiaolin5688.taobao.com
11楼 大 中 小 发表于 2010-8-26 11:52 只看该作者
引用:
> 原帖由 佐佐鼬鼬 于 2010-8-26 11:29 发表
> 
> 当老师挺不错的
目前的经验里，老师都很BT。
尤其是行为……
灼眼のSABER
“君有疾在蛋上，不治将疼” “操，滚！”
12楼 大 中 小 发表于 2010-8-26 11:56 只看该作者
老师现在可是公务员待遇
maming1003
13楼 大 中 小 发表于 2010-8-26 12:12 只看该作者
跟LZ差不多，也是数学专业，师范类。我今年大三，我想我还是考研吧，金融类的，不算是跨专业。
要是没有目标的话我建议你读书，一直读到有目标为止。
我很讨厌老师的，所以出来能不干老师就不干。
路上没有惊慌
14楼 大 中 小 发表于 2010-8-26 12:19 只看该作者
回复 13楼 maming1003 的话题
本科专业是数理金融？
maming1003
15楼 大 中 小 发表于 2010-8-26 12:22 只看该作者
回复 14楼 路上没有惊慌 的话题
不是，就是纯数学。出来就是只能当教师的那种。
路上没有惊慌
16楼 大 中 小 发表于 2010-8-26 12:27 只看该作者
回复 15楼 maming1003 的话题
纯数学的考研一定不能考本专业，出来还是当老师。转经济类算是比较靠谱点的。
M弹
17楼 大 中 小 发表于 2010-8-26 13:45 只看该作者
出来搞点小生意，都比现在上班强，关键还很自由。神马世道
蒋牛牛
带着梦想，滚床单撕内衣
18楼 大 中 小 发表于 2010-8-26 14:28 只看该作者
你是数学专业，以后邻居小胖再来问我中学应用题，我可以来问你吗。不会做，很没面子的
佐佐鼬鼬
想怎么说就怎么说
19楼 大 中 小 发表于 2010-8-26 15:23 只看该作者
引用:
> 原帖由 追梦 于 2010-8-26 11:52 发表 
>
> 目前的经验里，老师都很BT。
> 尤其是行为……
这个因人而异啊
菜爹
湿傅
20楼 大 中 小 发表于 2010-8-26 15:23 只看该作者
考个研，再考个CFA 去银行工作。
教师如果你没那理想就算了，省得误人子弟。
Winkay
21楼 大 中 小 发表于 2010-8-26 15:43 只看该作者
引用:
> 原帖由 菜爹 于 2010-8-26 15:23 发表 
> 考个研，再考个CFA 去银行工作。
> 教师如果你没那理想就算了，省得误人子弟。
考CFA，容易么？
Angelo
22楼 大 中 小 发表于 2010-8-26 16:36 只看该作者
樓主，我覺得你是恐懼即將要逐步面對的經濟獨立。
人生居然能被你規劃成一道二元選擇題——A考研 B瞎混
如果選A，結果失敗了難道還要換成A自殺 B瞎混不成？
不做程序員就不做了，成千上萬種工作，選擇餘地很大。
“之所以认为现在找的工作不靠谱，是因为没有专业基本就只能做一些销售之类的。”
做銷售的在你眼中很低級是吧？你做過了？請問業績如何啊？
而且誰告訴你非得從事專業對口的工作了？
你見過烹飪學校畢業的設計師嗎？見過學果木栽培的數據結構師嗎？見過學電焊出身的廚師長嗎？見過英語專業的會計師嗎？見過學地質勘探的設計總監嗎？見過學財會的電視節目編導嗎？見過學幼師的地產老闆嗎？見過學通信的高級經紀人嗎？見過學音樂的健身教練嗎？
見過警校畢業的歷史學者嗎？見過買古董的策劃總監嗎？見過學釀酒的木材商嗎？
想要看名人跨行成功的例子，請自行google。
以上說的都是我的朋友和同事，你的這套理論在我看來簡直就是歪理邪說。
但是是普遍的、常見的理論。
不才，在下做了一段時間的招聘顧問，每天的工作就是面對大學生。
你這樣的人太多，雖然我說你是歪理邪說。但是請放心，和你同樣邏輯的大學生大有人在。所以也請不要過分抬高自己，能把你的這些理論演化成長篇大論，並從頭論證的學生大有人在。
但是你也有比他們強的地方，至少你的第一條不是“出身說”，看你也沒說打算參與“拼爹遊戲”。
建議面對現實吧～
1.經濟獨立是必然的，不管怎麼逃避，大學時代結束了，以後泡妞、做愛、喝酒、打遊戲得自己付賬了。
2.別再故作清高狀了，認真的思考一下，那些你看不起的（用你的話說是不靠譜的）工作，你就保證能勝任嗎？
3.別拿文憑和專業說事了，你改變不了了（你總不能穿越吧？）。也許你不知道，在招聘顧問面前哭訴自己學歷和專業如何如何不如意的多了去了——但是這並不能提高他們的競爭力。
4.別和錢過不去，是人就離不開柴米油鹽。教師的待遇其實算不了什麼，如果只是為了賺錢而選擇這個工作的話，沒太大的發展空間。不要誤以為大街上開奔馳寶馬的都是富商，其中有很多都是你覺得不靠譜的銷售——一個出色的置業顧問（就是買房子的）一個月賺幾萬是很常見的，一個二線城市買經濟型家具的每月賺不到5000塊都面臨被淘汰的危險。
5.不知道你有沒有踏踏實實的從事過一份工作？所謂騎驢找馬，踏實的從事一份工作不僅不會影響你對自己的提升，反而會讓你發現更多的機會。
說的有點多，但絕沒有噴你意思，希望能對你有幫助。
核子力量
Twitter.com/hzpower
23楼 大 中 小 发表于 2010-8-26 17:05 只看该作者
楼上的回帖很认真，建议楼主慎思
Angelo
24楼 大 中 小 发表于 2010-8-26 17:07 只看该作者
引用:
> 原帖由 路上没有惊慌 于 2010-8-26 10:25 发表
> 
>
> 目的是找到一个方向。高中是自己选的，大学的专业也是自己选的，我并不糊涂，我的大学过得简直快乐死了，我不认为这是浪费时间，也没必要把自己搞的跟苦逼犯一样。另外，我觉得喜欢做的事情和职业不是一回事，毕竟这
> ...
你這個邏輯不是一時半會能變通的，舉太多的例子反倒會讓你反感。
很不幸，在下十幾歲出來社會瞎混，至今：
1.學歷和背景沒有影響到我求職，包括第一份工作，將來也不會影響我求職（對於有這麼多工作經歷的人 沒人會在意你學什麽玩意的）。
2.工作換了很多，居住城市也換了幾個，不過一直是從事我喜歡的工作。我求職的標準就是，做我感興趣的，我不喜歡的，赚再多我也不做。
3.收入狀態穩定，肚子從一開始就能填飽，現在的精力轉移到健身房，和合理安排每年三次的自駕遊上。
我絕沒有向你誇耀的想法，要知道，如果一個工作了多年的人向剛走出校門的大學生誇耀，丟人的是前者。
只是想告訴你，你現在的這些困難都是自己臆想的。最大的阻力來自自己。
你應該換個角度看問題——那些沒學歷，沒專業，家庭條件也不好的人還都在努力的活著呢，我有什麼理由止步不前啊？
darrenlee
25楼 大 中 小 发表于 2010-8-26 17:17 只看该作者
在一个功利的社会里，你能很好的适应并保持心理功能健全，说明你是一个非常功利的人。
中国现在的社会，就是一个既功利、又土鳖的社会，如果楼主愿意成为这样的人，大可以按照#22,#24的建议进行，但你将会失去的是什么，自己想好了。
乐游
广告位：推特 @miaoshiyu 长期求fo
26楼 大 中 小 发表于 2010-8-26 18:33 只看该作者
想不出来要做什么，那就随便找点什么事情做吧。做着做着就知道了。
别考研。考研是给有目标的人准备的。你现在不知道该做什么，读了研也一样不知道。君不见多少研究生也跟本科生一样天天窝在宿舍打游戏。这样读研纯属浪费青春。
路上没有惊慌
27楼 大 中 小 发表于 2010-8-26 21:33 只看该作者
回复 18楼 蒋牛牛 的话题
您的问题充分体现了我的能耐，就是能辅导中小学生。
路上没有惊慌
28楼 大 中 小 发表于 2010-8-26 21:55 只看该作者
回复 24楼 Angelo 的话题
非常感谢Angelo老师，您说的这些我的确欠考虑。您一点就透，莫非是做人力资源管理的或者是大学生就业指导处的主任？要是早有这样一个明白人出来指点一下，那真是省事多了。
Angelo
29楼 大 中 小 发表于 2010-8-27 01:26 只看该作者
回复 28楼 路上没有惊慌 的话题
老師可不敢當（也確實沒學歷）說的話能對你有幫助就好。
確實是負責人力資源工作的，而且做過相當一段時間的招聘顧問——那份工作80%的時間都是用來幫助雇主面試剛走出校門的大學生（也有一些剛走出校門的碩士）。
雖然我沒有經歷這個階段（因為不愛上學），但是每天接觸幾十個，也明白了些。
蒋牛牛
带着梦想，滚床单撕内衣
30楼 大 中 小 发表于 2010-8-27 10:05 只看该作者
引用:
> 原帖由 路上没有惊慌 于 2010-8-26 21:33 发表
> 
> 您的问题充分体现了我的能耐，就是能辅导中小学生。
好的。谢谢你啊。我被中学应用题折磨的，要自杀了，关键是对我有极大的挫败感。
dididadi
31楼 大 中 小 发表于 2010-8-27 15:21 只看该作者
二流学校+CFA考试通过有个鸟用啊。名牌大学的硕士考个CFA还是很有用的，再说有证书和光考试那是天差地别。
光那cfa的考试内容来说，也就大学期末考试的难度。跟硕士课程比起来那深入程度简直是差的一塌糊涂。
当然也不是一无是处，你考过CFA，不管几级，至少让人觉得你是认真的，我是真的想进入这个领域，态度问题，愿意去花金钱和时间。学校差，加上CFA也没用，再说了你硕士毕业顶多3级，拿证还是虚无缥缈的事情。
CFA这种投资分析类的，最大的出路就是分析师，可是现在分析师基本都是校校相护啦，一个不入流的，去了都不好意思开口。。。
去投个好点的单位简历都过不了，去本地商业银行，还考毛CFA啊。留下那1万5，开150次房，毕业了随便进。
核桃还有林子
32楼 大 中 小 发表于 2010-8-27 16:23 只看该作者
我这儿正招人呢。做外贸的。（上海）
vincentfon
IT边缘人.
33楼 大 中 小 发表于 2010-8-27 18:02 只看该作者
引用:
> 原帖由 路上没有惊慌 于 2010-8-26 10:46 发表
> 
> 我情绪还不错，而且人家也没喷我几句。
> 谢谢你，我会好好活的。
呵呵,原来很不错的一个小伙嘛.
DuGuQiuBai
34楼 大 中 小 发表于 2010-8-27 18:31 只看该作者
引用:
> 原帖由 核子力量 于 2010-8-26 10:46 发表
> 
> 感觉能考上就考研
> 考不上就先找工作干着
+1
什么都能荒废，唯一不能荒废的就是生活
houman
35楼 大 中 小 发表于 2010-8-27 19:26 只看该作者
楼主，22楼说的很对，但是你看他使用的繁体字，就应该知道他说的和你生活的环境不是一类地方，所以是不适用的。
你现在有两个选择，教师或者自己找别的工作。这两个选择中只有能选教师，因为你是在中国，低级别的体制外工作是很不稳定而且辛苦的。不是每个体制外的人都在Google，微软的。大部分人只能在一个很小公司。而高级别的体制外人士几乎很少是由低级别的体制外人士干出来的，例如媒体界的很多自由媒体人实际上人家一毕业都是在政府办的报纸上班。偶尔有几个成功的例子，这些人也是积极的向体制靠拢，例如你很难解释一个大型的私营证券公司算是体制内还是体制外。总的来说，在国内体制外几乎没戏，低级别的体制外更加没戏。
但是做教师尽管在体制内，很稳定，可惜发展的范围很小，你去当教师的第一天，看看同一个办公室的40多岁的教师，你就可以知道你40多岁的样子了。
所以如果年龄和时间合适，考研在中国是一项很不错的选择。首先，你上了研究生就算是在校学生，那么你可以选择一直念书，最后留校，不管是硕士留校当教工，还是博士留校当教师显然都比中小学老师要好。第二，毕业你可以选择进入其他体制内的单位，因为这些单位显然不会随便的从社会上招人，他们大都只要在校学生。甚至因为是毕业生的身份，只要找到单位，很多大城市的户口也很容易搞定。要知道，如果按照社会人士落户北京，上海可是很难的。最后，即使以上两个你都没达到，你再重新开始寻找体制外的工作，那相信多了一个学历的你显然比现在的你要更加具有优势。
我不是在唯学历论，只不过由于我国目前的现状就是这样罢了。自由的国家你可以自己单干然后创造一个twitter，但是在中国你单干创造一个饭否只能被封。只有sina，腾讯这种已经进入体制内“体制外创业神话”才能生存。作为个体，很多时候不要鸡蛋碰石头。
Anguu
我也爱你们
36楼 大 中 小 发表于 2010-8-27 22:51 只看该作者
考虑过出国么?
路上没有惊慌
37楼 大 中 小 发表于 2010-8-27 23:02 只看该作者
回复 36楼 Anguu 的话题
没有，因为没有钱。
DuGuQiuBai
38楼 大 中 小 发表于 2010-8-27 23:52 只看该作者
愚见，
现在或将来 可是以新加坡或HK什么的当跳板，
还有，LZqq号暴露了，不安全啊
路上没有惊慌
39楼 大 中 小 发表于 2010-8-28 00:03 只看该作者
回复 38楼 DuGuQiuBai 的话题
没有考虑过出国，就打算在国内。
谢谢你，除了QQ号，名字也可以暴露，我叫杜孝凯。嘘。。。
malonso
40楼 大 中 小 发表于 2010-8-28 00:14 只看该作者
Don't be a graduate, if you don't like what you are studying. Do what you
like. Maybe, at the beginning you will have a lot of pain, but it doesn't
matter if you really like it. Just think about it, doing a job which you don't
like for all your life, which is really a disaster.
路上没有惊慌
41楼 大 中 小 发表于 2010-8-28 00:21 只看该作者
回复 40楼 malonso 的话题
谢谢
| 7.126445 | 262 | 0.6715 | yue_Hant | 0.932947 |
9afd08f97f3785937b19dab8c87d0aa4dd670f28 | 47 | md | Markdown | PyMC3QnA/README.md | junpenglao/Planet_Sakaar_Data_Science | 73d9605b91b774a56d18c193538691521f679f16 | [
"MIT"
] | 51 | 2018-04-08T19:53:15.000Z | 2021-11-24T21:08:25.000Z | PyMC3QnA/README.md | junpenglao/Planet_Sakaar_Data_Science | 73d9605b91b774a56d18c193538691521f679f16 | [
"MIT"
] | 2 | 2018-05-29T20:50:37.000Z | 2020-09-12T07:14:08.000Z | PyMC3QnA/README.md | junpenglao/Planet_Sakaar_Data_Science | 73d9605b91b774a56d18c193538691521f679f16 | [
"MIT"
] | 13 | 2018-07-21T09:53:10.000Z | 2021-06-07T19:06:26.000Z | Helping the community, one question at a time.
| 47 | 47 | 0.787234 | eng_Latn | 0.999759 |
9afd835304850e8d1698379d769d90763db537d0 | 4,797 | md | Markdown | docs/src/index.md | JuliaTagBot/TimeSeriesClustering.jl | bb25ae46195c2fe426113d4c8a9ed45b7ee316e1 | [
"MIT"
] | 46 | 2019-08-23T13:46:52.000Z | 2022-03-25T13:10:22.000Z | docs/src/index.md | JuliaTagBot/TimeSeriesClustering.jl | bb25ae46195c2fe426113d4c8a9ed45b7ee316e1 | [
"MIT"
] | 42 | 2019-02-26T16:59:18.000Z | 2019-08-18T22:50:14.000Z | docs/src/index.md | JuliaTagBot/TimeSeriesClustering.jl | bb25ae46195c2fe426113d4c8a9ed45b7ee316e1 | [
"MIT"
] | 12 | 2019-08-20T16:15:39.000Z | 2022-03-11T20:21:47.000Z | 
===
[](https://holgerteichgraeber.github.io/TimeSeriesClustering.jl/stable)
[](https://holgerteichgraeber.github.io/TimeSeriesClustering.jl/dev)
[](LICENSE)
[](https://travis-ci.com/holgerteichgraeber/TimeSeriesClustering.jl)
[](https://codecov.io/gh/holgerteichgraeber/TimeSeriesClustering.jl)
[](https://doi.org/10.21105/joss.01573)
[TimeSeriesClustering](https://github.com/holgerteichgraeber/TimeSeriesClustering.jl) is a [Julia](https://www.juliaopt.com) implementation of unsupervised learning methods for time series datasets. It provides functionality for clustering and aggregating, detecting motifs, and quantifying similarity between time series datasets.
The software provides a type system for temporal data, and provides an implementation of the most commonly used clustering methods and extreme value selection methods for temporal data.
It provides simple integration of multi-dimensional time-series data (e.g. multiple attributes such as wind availability, solar availability, and electricity demand) in a single aggregation process.
The software is applicable to general time series datasets and lends itself well to a multitude of application areas within the field of time series data mining.
The TimeSeriesClustering package was originally developed to perform time series aggregation for energy systems optimization problems. By reducing the number of time steps used in the optimization model, using representative periods leads to significant reductions in computational complexity of these problems.
The packages was previously known as `ClustForOpt.jl`.
The package has three main purposes:
1) Provide a simple process of finding representative periods (reducing the number of observations) for time-series input data, with implementations of the most commonly used clustering methods and extreme value selection methods.
2) Provide an interface between representative period data and application (e.g. optimization problem) by having representative period data stored in a generalized type system.
3) Provide a generalized import feature for time series, where variable names, attributes, and node names are automatically stored and can then be used later when the reduced time series is used in the application at hand (e.g. in the definition of sets of the optimization problem).
In the domain of energy systems optimization, an example problem that uses TimeSeriesClustering for its input data is the package [CapacityExpansion](https://github.com/YoungFaithful/CapacityExpansion.jl), which implements a scalable generation and transmission capacity expansion problem.
The TimeSeriesClustering package follows the clustering framework presented in [Teichgraeber and Brandt, 2019](https://doi.org/10.1016/j.apenergy.2019.02.012).
The package is actively developed, and new features are continuously added.
For a reproducible version of the methods and data of the original paper by [Teichgraeber and Brandt, 2019](https://doi.org/10.1016/j.apenergy.2019.02.012), please refer to [v0.1](https://github.com/holgerteichgraeber/TimeSeriesClustering.jl/tree/v0.1) (including shape based methods such as `k-shape` and `dynamic time warping barycenter averaging`).
This package is developed by Holger Teichgraeber [@holgerteichgraeber](https://github.com/holgerteichgraeber) and Elias Kuepper [@YoungFaithful](https://github.com/youngfaithful).
## Installation
This package runs under julia v1.0 and higher.
Install using:
```julia
import Pkg
Pkg.add("TimeSeriesClustering")
```
## Citing TimeSeriesClustering
If you find TimeSeriesClustering useful in your work, we kindly request that you cite the following paper ([link](https://doi.org/10.21105/joss.01573)):
```
@article{Teichgraeber2019joss,
author = {Teichgraeber, Holger and Kuepper, Lucas Elias and Brandt, Adam R},
doi = {https://doi.org/10.21105/joss.01573},
journal = {Journal of Open Source Software},
number = {41},
pages = {1573},
title = {TimeSeriesClustering : An extensible framework in Julia},
volume = {4},
year = {2019}
}
```
If you find this package useful, our [paper](https://doi.org/10.1016/j.apenergy.2019.02.012) on comparing clustering methods for energy systems optimization problems may additionally be of interest.
| 84.157895 | 351 | 0.801126 | eng_Latn | 0.925095 |
9afdbd6e080920133a9c7543999681a368106d3a | 1,581 | md | Markdown | docs/ado/reference/ado-api/saveoptionsenum.md | L3onard80/sql-docs.it-it | f73e3d20b5b2f15f839ff784096254478c045bbb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/ado/reference/ado-api/saveoptionsenum.md | L3onard80/sql-docs.it-it | f73e3d20b5b2f15f839ff784096254478c045bbb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/ado/reference/ado-api/saveoptionsenum.md | L3onard80/sql-docs.it-it | f73e3d20b5b2f15f839ff784096254478c045bbb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: SaveOptionsEnum | Microsoft Docs
ms.prod: sql
ms.prod_service: connectivity
ms.technology: connectivity
ms.custom: ''
ms.date: 01/19/2017
ms.reviewer: ''
ms.topic: conceptual
apitype: COM
f1_keywords:
- SaveOptionsEnum
helpviewer_keywords:
- SaveOptionsEnum enumeration [ADO]
ms.assetid: 59339100-6e29-48d1-aea3-6873796d186b
author: MightyPen
ms.author: genemi
ms.openlocfilehash: 807a8d7e5757a2caf76f100a1ae51c4a8a3f4e98
ms.sourcegitcommit: b87d36c46b39af8b929ad94ec707dee8800950f5
ms.translationtype: MT
ms.contentlocale: it-IT
ms.lasthandoff: 02/08/2020
ms.locfileid: "67931140"
---
# <a name="saveoptionsenum"></a>SaveOptionsEnum
Specifica se un file deve essere creato o sovrascritto durante il salvataggio da un oggetto [flusso](../../../ado/reference/ado-api/stream-object-ado.md) . I valori possono essere **adSaveCreateNotExist** o **adSaveCreateOverwrite**.
|Costante|valore|Descrizione|
|--------------|-----------|-----------------|
|**adSaveCreateNotExist**|1|Default. Crea un nuovo file se il file specificato dal parametro *filename* non esiste già.|
|**adSaveCreateOverWrite**|2|Sovrascrive il file con i dati dell'oggetto **flusso** attualmente aperto, se il file specificato dal parametro *filename* esiste già. Se il file specificato dal parametro *filename* non esiste, viene creato un nuovo file.|
## <a name="adowfc-equivalent"></a>Equivalente ADO/WFC
Queste costanti non dispongono di equivalenti ADO/WFC.
## <a name="applies-to"></a>Si applica a
[Metodo SaveToFile](../../../ado/reference/ado-api/savetofile-method.md)
| 41.605263 | 254 | 0.748261 | ita_Latn | 0.594546 |
9afe703b15d5494619ab719160d001299a19c1e4 | 777 | md | Markdown | Strategy/README.md | alexfederlin/widerdesk | 5a18f29405f6f0c83f78cfb89681913dd5aa348c | [
"MIT"
] | null | null | null | Strategy/README.md | alexfederlin/widerdesk | 5a18f29405f6f0c83f78cfb89681913dd5aa348c | [
"MIT"
] | null | null | null | Strategy/README.md | alexfederlin/widerdesk | 5a18f29405f6f0c83f78cfb89681913dd5aa348c | [
"MIT"
] | null | null | null | # Place individual specific strategies here.
How
------
### Download and unzip
Download additional [strategies](https://github.com/uzyn/opauth/wiki/List-of-strategies) and place them in directories here.
Remember to name the directory name as the actual name of the strategy. For example, place [Facebook strategy](https://github.com/opauth/facebook) files in `./Facebook/` so that `FacebookStrategy.php` can be found at `./Facebook/FacebookStrategy.php`.
### Git clone
If you prefer `git clone`, you can simply run the following at this dir without worrying about renaming:
```bash
git clone git://github.com/opauth/facebook.git Facebook
```
More strategies
---------------
Check out the wiki for [more strategies](https://github.com/uzyn/opauth/wiki/List-of-strategies). | 43.166667 | 251 | 0.750322 | eng_Latn | 0.891646 |
9afe8686e5d7dccab40ba8c83b5a406b5609372f | 2,581 | md | Markdown | _posts/winapi/2021-06-23-winapi-engine-core.md | moonseokchoi-kr/moonseokchoi-kr.github.io | 6a975b6ef96d15a3ab06a0101b4d29b40498531f | [
"MIT"
] | null | null | null | _posts/winapi/2021-06-23-winapi-engine-core.md | moonseokchoi-kr/moonseokchoi-kr.github.io | 6a975b6ef96d15a3ab06a0101b4d29b40498531f | [
"MIT"
] | null | null | null | _posts/winapi/2021-06-23-winapi-engine-core.md | moonseokchoi-kr/moonseokchoi-kr.github.io | 6a975b6ef96d15a3ab06a0101b4d29b40498531f | [
"MIT"
] | null | null | null | ---
layout: post
title: "[C++][WinAPI] Create Game Engine -1 Core Class"
summary: "winapi game engine"
author: moon
date: '2021-06-23 12:35:23 +0900'
category: WinAPI
thumbnail: /assets/img/posts/bitoper.PNG
keywords: cpp, oop, winapi, ui, grapic,engine
permalink: /blog/cpp/winapi/engine/core
usemathjax: true
---
## 엔진코어 제작
---
- 게임에서 중요한 역할을 하는 코어 클래스를 제작
- 객체가 여러개 생성되면 안된다. 코어클래스는 게임에서의 중추이기 때문에
- 따라서 Singleton pattern을 기반으로 제작한다.
- Singleton Pattern
- 객체가 1개만 생성가능함을 보증하고 싶을때 사용하는 패턴이다.
- 생성자를 숨겨 생성자를 사용자가 호출 할 수 없도록 한다.
- 대신 객체를 생성하는 함수를 만들어 제공한다. 아래와 같이 작성해서 사용한다.
동적할당을 이용한 방법
```cpp
class Singleton
{
public:
static Singleton GetInstance()
{
static Singleton* singleton= nullptr;
if(nullptr == singleton)
{
sigleton = new Singleton();
}
return sigleton;
}
private:
Singleton();
~Singleton();
}
//사용
Singleton single = Sigleton.GetInstance();
```
데이터영역을 이용한 방법
```cpp
// 데이터영역을 이용한 싱글톤 구조
// 해제를 신경쓰지 않아도 알아서 사라진다.
// 대부분 매니저 형태를 싱글톤으로 만들기 때문에 이 방법을 많이 사용할 수 있음
class Singleton
{
public:
static Singleton* GetInst()
{
static Singleton core;
return &core;
}
private:
Singleton() {}
~Singleton() {}
};
```
- 왜 함수 정적변수로 동적할당을 안하나요?
- 함수로 정적변수로 제작을 하게되면 메모리를 해제할 때 문제가 된다.
- 함수를 통해 메모리를 해제하게 되는데 정적변수의 메모리는 해제가 안되기 때문에 다시 필요할때 생성이되는게 아닌 이미해제되버린 메모리를 반환해준다.
- 미리 컴파일된 헤더
- 윈도우에서 제공되는 기능으로 컴파일이 완료된 헤더들을 모아놓은 헤더를 말한다.
- 컴파일시 미리컴파일된 헤더는 체크를 안하게 된다.
- 미리컴파일된 헤더를 사용하면 cpp에서 자동으로 참초하게된다.
## 생성된 코어 클래스
---
```cpp
class CCore
{
SINGLE(CCore);
public:
//코어클래스를 초기화
int InitCore(HWND _hwnd, POINT _resolution);
//초기화후 처리할 과정을 진행
void Progress();
private:
CCore();
~CCore();
private:
HWND m_hWnd;
POINT m_ptResolution;
};
```
## 초기화처리 방법
---
```cpp
if (FAILED(CCore::GetInst()->InitCore(g_hwnd, POINT{ 1280, 768 })))
{
MessageBox(nullptr, L"Core 객체 초기화 실패", L"ERROR", MB_OK);
return FALSE;
}
```
- 기존의 boolean 타입이 아닌 HRESULT 타입을 이용하여 진행(windows.h를 포함해야사용가능)
- 이제 앞으로 이용될 라이브러리들이 대부분 HRESULT를 사용하기 때문에이용
- 만약 에러발생시 메세지 박스가 나오도록 설정 | 21.689076 | 99 | 0.526153 | kor_Hang | 0.999998 |
9affa53d281b3c7a9c1846e6f84681f01e4f03ef | 926 | md | Markdown | README.md | dwaring87/rtm-cli-plugin-example | d83d06c368e3ab144adc52a8004c61861c107898 | [
"MIT"
] | null | null | null | README.md | dwaring87/rtm-cli-plugin-example | d83d06c368e3ab144adc52a8004c61861c107898 | [
"MIT"
] | null | null | null | README.md | dwaring87/rtm-cli-plugin-example | d83d06c368e3ab144adc52a8004c61861c107898 | [
"MIT"
] | null | null | null | # RTM-CLI Plugin Example
This repository can be used to serve as a template for creating a command plugin for
[rtm-cli](https://github.com/dwaring87/rtm-cli).
This example is set up as a Node module that will export two commands: `hello` and `settings`.
Each command lives as a separtate file (`hello.js` and `settings.js`, respectively) and are
exported together by the `index.js` file, which serves as the main entry point for the
entire Node module.
### hello
This example command shows how to set up and use a required argument, an optional list argument,
and an optional flag value with the command.
### settings
This example command shows how to obtain the authenticated RTM User instance and how to use this
instance to make RTM API requests.
## Usage & Installation
For more information on the plugin architecture installing a plugin, see the
[rtm-cli Wiki](https://github.com/dwaring87/rtm-cli/wiki).
| 37.04 | 97 | 0.764579 | eng_Latn | 0.998554 |
b1005c7e20670c01e8c6d79b85f00ac48f62b1bf | 17,963 | md | Markdown | docs/ko/technical/view-hierarchy.md | lamia100/yona | 77b1fda9ecb4232f01547e7547e44648ba675b96 | [
"Apache-2.0"
] | 503 | 2016-01-19T09:03:06.000Z | 2022-03-22T09:15:49.000Z | docs/ko/technical/view-hierarchy.md | lamia100/yona | 77b1fda9ecb4232f01547e7547e44648ba675b96 | [
"Apache-2.0"
] | 715 | 2016-01-22T00:10:08.000Z | 2022-03-31T23:57:12.000Z | docs/ko/technical/view-hierarchy.md | lamia100/yona | 77b1fda9ecb4232f01547e7547e44648ba675b96 | [
"Apache-2.0"
] | 235 | 2016-01-20T06:46:22.000Z | 2022-03-19T12:27:43.000Z | # View Hierarchy
Yobi의 view hierarchy를 각 기능별로 정리한 문서입니다.
## Yobi Home
* *http://[Yobi URL]/*
* views.layout.scala.html
* views.siteLayout.scala.html
* views.common.usermenu.scala.html
* if
* views.index.partial_intro.scala.html
* views.common.alert.scala.html
* **views.index.index.scala.html**
* if
* views.index.partial_notifications.scala.html
* views.index.myprojectList.scala.html
## 계정
### 로그인
* *http://[Yobi URL]/users/loginform*
* views.layout.scala.html
* views.siteLayout.scala.html
* views.common.usermenu.scala.html
* views.common.alert.scala.html
* **views.user.login.scala.html**
### 회원가입
* *http://[Yobi URL]/users/signupform*
* views.layout.scala.html
* views.siteLayout.scala.html
* views.common.usermenu.scala.html
* views.common.alert.scala.html
* **views.user.signup.scala.html**
### 아바타 > 프로필
* *http://[Yobi URL]/[UserName]?daysAgo=&selected=*
* views.layout.scala.html
* views.siteLayout.scala.html
* views.common.usermenu.scala.html
* views.common.alert.scala.html
* **views.user.view.scala.html**
* views.user.partial_projectlist.scala.html
* views.user.partial_postings.scala.html
* views.user.partial_issues.scala.html
* views.user.partial_pullRequests.scala.html
* views.user.partial_milestones.scala.html
### 아바타 > 설정
* *http://[Yobi URL]/user/editform*
* views.layout.scala.html
* views.siteLayout.scala.html
* views.common.usermenu.scala.html
* views.common.alert.scala.html
* **views.user.edit.scala.html**
## 도움말
* *http://[Yobi URL]/help*
* views.layout.scala.html
* views.siteLayout.scala.html
* views.common.usermenu.scala.html
* views.common.alert.scala.html
* **views.help.toc.scala.html**
## 프로젝트
### 프로젝트 목록
* *http://[Yobi URL]/projects*
* views.layout.scala.html
* views.siteLayout.scala.html
* views.common.usermenu.scala.html
* views.common.alert.scala.html
* **views.project.list.scala.html**
### 새 프로젝트 만들기
* *http://[Yobi URL]/projectform*
* views.layout.scala.html
* views.siteLayout.scala.html
* views.common.usermenu.scala.html
* views.common.alert.scala.html
* **views.project.create.scala.html**
#### 새 프로젝트 만들기 > Git 저장소에서 코드 가져오기
* *http://[Yobi URL]/import*
* views.layout.scala.html
* views.siteLayout.scala.html
* views.common.usermenu.scala.html
* views.common.alert.scala.html
* **views.project.importing.scala.html**
### 프로젝트 홈
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* **views.project.overview.scala.html**
* views.projectMenu.scala.html
* views.common.markdown.scala.html
## 게시판
### 게시판 홈
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]/posts*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* **views.board.list.scala.html**
* views.projectMenu.scala.html
* views.board.partial_list.scala.html
* views.help.keymap.scala.html
### 게시판 > 글쓰기
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]/postsform*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* **views.board.create.scala.html**
* views.projectMenu.scala.html
* views.help.markdown.scala.html
* if
* views.common.fileUploader.scala.html
* views.common.markdown.scala.html
### 게시판 > 항목선택
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]/post/[post id]*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* **views.board.view.scala.html**
* views.projectMenu.scala.html
* views.common.commentForm.scala.html
* views.help.markdown.scala.html
* if
* views.common.fileUploader.scala.html
* views.help.keymap.scala.html
* views.common.markdown.scala.html
### 게시판 > 항목선택 > 수정
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]/post/[post id]/editform*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* **views.board.edit.scala.html**
* views.projectMenu.scala.html
* views.common.commentForm.scala.html
* views.help.markdown.scala.html
* if
* views.common.fileUploader.scala.html
* views.common.markdown.scala.html
## 코드
### 코드 > 파일
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]/code/master*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* **views.code.view.scala.html**
* views.code.partial_branchitem.scala.html
### 코드 > 파일 > 파일선택
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]/code/[branch]/[path]*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* **views.code.view.scala.html**
* views.code.partial_branchitem.scala.html
### 코드 > 파일 > 파일선택 > 변경이력 ( > [파일보기] )
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]/commits/[branch]/[path]*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* **views.code.history.scala.html**
* views.projectMenu.scala.html
* views.code.partial_branchitem.scala.html
### 코드 > 파일 > 파일선택 > 변경이력 > 항목선택
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]/commit/[commit id]?branch=[branch]?path=[path]*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* if
* **views.code.svnDiff.scala.html**
* views.projectMenu.scala.html
* views.common.commentForm.scala.html
* views.help.markdown.scala.html
* if
* views.common.fileUploader.scala.html
* views.common.markdown.scala.html
* else
* **views.code.diff.scala.html**
* views.projectMenu.scala.html
* views.code.partial_branchitem.scala.html
* views.partial_diff.scala.html
* views.partial_filediff.scala.html
* views.common.mergely.scala.html
* views.common.commentForm.scala.html
* views.help.markdown.scala.html
* if
* views.common.fileUploader.scala.html
* views.common.markdown.scala.html
* views.common.mergely.scala.html
### 코드 > 커밋
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]/commits/[branch]*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* **views.code.history.scala.html**
* views.projectMenu.scala.html
* views.code.partial_branchitem.scala.html
### 코드 > 커밋 > 항목선택
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]/commit/[commit id]?branch=[branch]*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* if
* **views.code.svnDiff.scala.html**
* views.projectMenu.scala.html
* views.common.commentForm.scala.html
* views.help.markdown.scala.html
* if
* views.common.fileUploader.scala.html
* views.common.markdown.scala.html
* else
* **views.code.diff.scala.html**
* views.projectMenu.scala.html
* views.code.partial_branchitem.scala.html
* views.partial_diff.scala.html
* views.partial_filediff.scala.html
* views.common.mergely.scala.html
* views.common.commentForm.scala.html
* views.help.markdown.scala.html
* if
* views.common.fileUploader.scala.html
* views.common.markdown.scala.html
* views.common.mergely.scala.html
## 코드주고받기
### 코드주고받기 홈
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]/pullRequests*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* **views.git.list.scala.html**
* views.projectMenu.scala.html
* views.git.partial_recentlry_pushed_branches.scala.html
* views.git.partial_list.scala.html
### 코드주고받기 > 이 프로젝트에 코드 보내기
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]/newPullRequestForm*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* **views.git.create.scala.html**
* views.projectMenu.scala.html
* views.git.partial_diff.scala.html
* views.common.fileUploader.scala.html
* views.common.markdown.scala.html
* if
* views.partial_diff.scala.html
* views.partial_filediff.scala.html
* views.common.mergely.scala.html
### 코드주고받기 > 항목선택 > 개요
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]/pullRequest/[pullrequest id]*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* **views.git.view.scala.html**
* views.projectMenu.scala.html
* views.git.partial_info.scala.html
* views.git.partial_state.scala.html
* views.common.commentForm.scala.html
* views.help.markdown.scala.html
* if
* views.common.fileUploader.scala.html
* views.common.markdown.scala.html
### 코드주고받기 > 항목선택 > 커밋
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]/pullRequest/[pullrequest id]/commits*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* **views.git.viewCommits.scala.html**
* views.projectMenu.scala.html
* views.git.partial_info.scala.html
* views.common.markdown.scala.html
### 코드주고받기 > 항목선택 > 커밋 > 항목선택
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]/pullRequest/[pullrequest id]/commit/[commit id]*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* **views.git.diff.scala.html**
* views.partial_diff.scala.html
* views.partial_filediff.scala.html
* views.common.mergely.scala.html
* views.common.commentForm.scala.html
* views.help.markdown.scala.html
* if
* views.common.fileUploader.scala.html
* views.common.markdown.scala.html
* views.common.mergely.scala.html
### 코드주고받기 > 항목선택 > 변경내역
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]/pullRequest/[id]/changes*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* **views.git.viewChanges.scala.html**
* views.projectMenu.scala.html
* views.git.partial_info.scala.html
* if
* views.partial_diff.scala.html
* views.partial_filediff.scala.html
* views.common.mergely.scala.html
* else
* views.git.partial_state.scala.html
* views.common.commentForm.scala.html
* views.help.markdown.scala.html
* if
* views.common.fileUploader.scala.html
* views.common.markdown.scala.html
* views.common.mergely.scala.html
## 이슈
### 이슈 홈
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]/issues?state=open*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* **views.issue.list.scala.html**
* views.projectMenu.scala.html
* views.issue.partial_search.scala.html
* views.milestone.partial_status.scala.html
* if
* views.issue.partial_massupdate.scala.html
* views.issue.partial_list.scala.html
* views.help.keymap.scala.html
* else
* views.help.keymap.scala.html
### 이슈 > 새 이슈
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]/issueform*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* **views.issue.create.scala.html**
* views.projectMenu.scala.html
* views.help.markdown.scala.html
* views.help.experimental.scala.html
* if
* views.common.fileUploader.scala.html
* views.common.markdown.scala.html
### 이슈 > 항목선택
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]/issue/[issue id]*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* **views.issue.view.scala.html**
* views.projectMenu.scala.html
* views.common.commentForm.scala.html
* views.help.markdown.scala.html
* if
* views.common.fileUploader.scala.html
* views.help.keymap.scala.html
* views.common.markdown.scala.html
### 이슈 > 항목선택 > 수정
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]/issue/[issue id]/editform*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* **views.issue.edit.scala.html**
* views.projectMenu.scala.html
* views.help.markdown.scala.html
* views.help.experimental.scala.html
* if
* views.common.fileUploader.scala.html
* views.common.markdown.scala.html
## 마일스톤
### 마일스톤
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]/milestones*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* **views.milestone.list.scala.html**
* views.projectMenu.scala.html
### 마일스톤 > 새 마일스톤
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]/newMilestoneForm*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* **views.milestone.create.scala.html**
* views.projectMenu.scala.html
* views.common.fileUploader.scala.html
* views.common.markdown.scala.html
### 마일스톤 > 항목선택
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]/milestone/[milestone id]*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* **views.milestone.view.scala.html**
* views.projectMenu.scala.html
* views.issue.partial_massupdate.scala.html
* views.issue.partial_list.scala.html
* views.common.markdown.scala.html
### 마일스톤 > 수정
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]/milestone/[milestone id]/editform*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* **views.milestone.edit.scala.html**
* views.projectMenu.scala.html
* views.help.markdown.scala.html
* views.help.experimental.scala.html
* if
* views.common.fileUploader.scala.html
* views.common.markdown.scala.html
## 프로젝트 설정
### 프로젝트 > 설정
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]/settingform*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* **views.project.setting.scala.html**
* views.projectMenu.scala.html
* views.project.partial_settingmenu.scala.html
### 프로젝트 > 멤버
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]/members*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* **views.project.members.scala.html**
* views.projectMenu.scala.html
* views.project.partial_settingmenu.scala.html
### 프로젝트 > 프로젝트 삭제
* *http://[Yobi URL]/[ProjectCreator]/[ProjectName]/deleteform*
* views.layout.scala.html
* views.projectLayout.scala.html
* views.project.navbar.scala.html
* views.project.header.scala.html
* **views.project.delete.scala.html**
* views.projectMenu.scala.html
* views.project.partial_settingmenu.scala.html
| 34.085389 | 100 | 0.611479 | yue_Hant | 0.614691 |
b100e5540f39220293dc93b6fb6be249dd663b9b | 1,235 | md | Markdown | _posts/2018-02-19-elixir-beam.md | tap349/tap349.github.io | 3bba0fb234586b6c84e87f4f7c22386c0c42d600 | [
"MIT"
] | null | null | null | _posts/2018-02-19-elixir-beam.md | tap349/tap349.github.io | 3bba0fb234586b6c84e87f4f7c22386c0c42d600 | [
"MIT"
] | null | null | null | _posts/2018-02-19-elixir-beam.md | tap349/tap349.github.io | 3bba0fb234586b6c84e87f4f7c22386c0c42d600 | [
"MIT"
] | null | null | null | ---
layout: post
title: Elixir - BEAM
date: 2018-02-19 00:12:25 +0300
access: public
comments: true
categories: [elixir]
---
<!-- more -->
<!-- prettier-ignore -->
* TOC
{:toc}
<hr>
memory management
-----------------
<https://stackoverflow.com/a/46869400/3632318>:
> In principle everything is copied. Every process has its own heap.
>
> In reality there are a few underlying speed hacks. The most notable are:
>
> - Literals known at compile time are referenced from the global heap
> (which is some cases is a huge performance gain)
> - Binaries larger than 64 bytes are referenced from the global heap
> (which also causes binaries to be a leaky abstraction, hence `binary:copy/1,2`)
> - Updates to most structures do not actually require copying the whole
> structure (of particular interest is what goes on inside maps) - but
> how much and when copying is necessary is ever changing as more efficiency
> work goes into the runtime
> - Garbage collection occurs per process which is why Erlang appears to have
> a magically advanced incremental GC scheme, but actually has quite boring
> generational heap collection underneath (in the general case, that is; the
> approach is actually somewhat of a hybrid)
| 32.5 | 83 | 0.731984 | eng_Latn | 0.99917 |
b1010647055c918156d6f7983819afb464721d45 | 23,632 | md | Markdown | docs/code-quality/security-warnings.md | monkey3310/visualstudio-docs.pl-pl | adc80e0d3bef9965253897b72971ccb1a3781354 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/code-quality/security-warnings.md | monkey3310/visualstudio-docs.pl-pl | adc80e0d3bef9965253897b72971ccb1a3781354 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/code-quality/security-warnings.md | monkey3310/visualstudio-docs.pl-pl | adc80e0d3bef9965253897b72971ccb1a3781354 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Ostrzeżenia o zabezpieczeniach
ms.date: 11/04/2016
ms.prod: visual-studio-dev15
ms.technology: vs-ide-code-analysis
ms.topic: reference
f1_keywords:
- vs.codeanalysis.securityrules
helpviewer_keywords:
- security [Visual Studio ALM], Enterprise Templates
- security warnings
- managed code analysis warnings, security warnings
- warnings, security
ms.assetid: 60d4e8ea-230a-494f-aa6a-b91db77540e4
author: gewarren
ms.author: gewarren
manager: douge
ms.workload:
- multiple
ms.openlocfilehash: 93fc473550db227fe51eeeadc14c3006653c7e07
ms.sourcegitcommit: 96a6d1f16d06ca28d309d05b6e9fbd52f628cdbc
ms.translationtype: MT
ms.contentlocale: pl-PL
ms.lasthandoff: 08/09/2018
ms.locfileid: "40008372"
---
# <a name="security-warnings"></a>Ostrzeżenia o zabezpieczeniach
Ostrzeżenia o zabezpieczeniach obsługują bezpieczniejsze biblioteki i aplikacje. Ostrzeżenia te pomagają zapobiec usterkom w zabezpieczeniach w programie. Przyczynę wyłączenia któregokolwiek z tych ostrzeżeń należy wyraźnie oznaczyć w kodzie i poinformować o tym osobę odpowiedzialną za bezpieczeństwo w projekcie.
## <a name="in-this-section"></a>W tej sekcji
|Reguła|Opis|
|----------|-----------------|
|[CA2100: Sprawdź zapytania SQL pod kątem luk w zabezpieczeniach](../code-quality/ca2100-review-sql-queries-for-security-vulnerabilities.md)|Metoda ustawia właściwość System.Data.IDbCommand.CommandText przez użycie ciągu, który jest zbudowany z argumentem ciągu do metody. Zasada ta zakłada, że argument ciągu zawiera dane wejściowe użytkownika. Ciąg polecenia SQL zbudowany z danych wejściowych użytkownika jest narażony na ataki przez wstrzyknięcie kodu SQL.|
|[CA2102: Przechwytuj wyjątki bez atrybutu CLSCompliant w ogólnych procedurach obsługi](../code-quality/ca2102-catch-non-clscompliant-exceptions-in-general-handlers.md)|Element członkowski w zestawie, który nie jest oznaczony za pomocą atrybutu RuntimeCompatibilityAttribute lub jest oznaczony jako RuntimeCompatibility(WrapNonExceptionThrows = false), zawiera blok catch obsługujący wyjątek System.Exception i nie zawiera bezpośrednio następującego ogólnego bloku catch.|
|[CA2103: Przejrzyj zabezpieczenia imperatywne](../code-quality/ca2103-review-imperative-security.md)|Metoda używa imperatywnych zabezpieczeń i może konstruować uprawnienia za pomocą informacji o stanie lub wartości zwrotnych, które można zmienić, podczas gdy żądanie jest aktywne. Należy używać zabezpieczeń deklaracyjnych wszędzie, gdzie to możliwe.|
|[CA2104: Nie deklaruj modyfikowalnych typów referencyjnych tylko do odczytu](../code-quality/ca2104-do-not-declare-read-only-mutable-reference-types.md)|Typ widoczny z zewnątrz zawiera widoczne na zewnątrz pole tylko do odczytu, które jest typu referencji zmiennej. Typ zmienny to typ, którego dane wystąpienia mogą być modyfikowane.|
|[CA2105: Pola tablicy nie powinny być tylko do odczytu](../code-quality/ca2105-array-fields-should-not-be-read-only.md)|Jeśli zastosujesz modyfikator tylko do odczytu (ReadOnly w języku Visual Basic) do pola, które zawiera tablicę, pola nie można zmienić w taki sposób, aby odwoływać się do innej tablicy. Można jednak zmienić elementy tablicy przechowywane w polu tylko do odczytu.|
|[CA2106: Zabezpiecz asercje](../code-quality/ca2106-secure-asserts.md)|Metoda potwierdza uprawnienia i żadne sprawdzenia zabezpieczeń nie są wykonywane na obiekcie wywołującym. Potwierdzanie uprawnienia zabezpieczeń bez sprawdzania zabezpieczeń może pozostawić zdatną do wykorzystania słabość zabezpieczeń w kodzie.|
|[CA2107: Przejrzyj użycie akcji Deny i Permit Only](../code-quality/ca2107-review-deny-and-permit-only-usage.md)|Metoda PermitOnly i akcje zabezpieczeń CodeAccessPermission.Deny powinny być używane tylko przez tych, którzy mają zaawansowaną wiedzę o zabezpieczeniach .NET Framework. Kod, który używa tych akcji zabezpieczeń, należy poddać przeglądowi zabezpieczeń.|
|[CA2108: Przejrzyj zabezpieczenia deklaratywne typów wartości](../code-quality/ca2108-review-declarative-security-on-value-types.md)|Publiczny lub chroniony typ wartości jest zabezpieczony przez dostęp do danych lub zapotrzebowanie na łącza.|
|[CA2109: Przejrzyj widoczne procedury obsługi zdarzeń](../code-quality/ca2109-review-visible-event-handlers.md)|Wykryto publiczną lub chronioną metodę obsługi zdarzeń. Metody obsługi zdarzeń nie powinny być udostępnione, chyba że jest to absolutnie konieczne.|
|[CA2111: Wskaźniki nie powinny być widoczne](../code-quality/ca2111-pointers-should-not-be-visible.md)|Wskaźnik nie jest prywatny, wewnętrzny ani tylko do odczytu. Złośliwy kod może zmienić wartość wskaźnika, potencjalnie umożliwiając dostęp do dowolnego miejsca w pamięci lub powodując błędy aplikacji bądź systemu.|
|[CA2112: Typy zabezpieczone nie powinny ujawniać pól](../code-quality/ca2112-secured-types-should-not-expose-fields.md)|Typ publiczny lub chroniony zawiera pola publiczne i jest zabezpieczony przez zapotrzebowania na łącza. Jeśli kod ma dostęp do wystąpienia typu zabezpieczonego przez żądanie łącza, kod nie musi spełniać zapotrzebowania na łącza, aby uzyskać dostęp do pól typu.|
|[CA2114: Zabezpieczenie metody powinno być nadzbiorem typu](../code-quality/ca2114-method-security-should-be-a-superset-of-type.md)|Metoda nie powinna mieć zabezpieczeń deklaratywnych zarówno na poziomie metody, jak i na poziomie typu dla tej samej akcji.|
|[CA2115: Wywołaj funkcję GC.KeepAlive w przypadku korzystania z zasobów natywnych](../code-quality/ca2115-call-gc-keepalive-when-using-native-resources.md)|Ta reguła wykrywa błędy, które mogą wystąpić, ponieważ kończy się działanie niezarządzanego zasobu, a wciąż jest on używany w kodzie niezarządzanym.|
|[CA2116: Metody z atrybutem APTCA powinny wywoływać tylko metody z atrybutem APTCA](../code-quality/ca2116-aptca-methods-should-only-call-aptca-methods.md)|Gdy atrybut APTCA (AllowPartiallyTrustedCallers) jest obecny w zestawie całkowicie zaufanym i wykonuje kod w innym zestawie, który nie zezwala na dostęp częściowo zaufanych wywołań, mogą zostać wykorzystane luki w zabezpieczeniach.|
|[CA2117: Typy z atrybutem APTCA powinny rozszerzać tylko typy podstawowe z atrybutem APTCA](../code-quality/ca2117-aptca-types-should-only-extend-aptca-base-types.md)|Gdy atrybut APTCA (AllowPartiallyTrustedCallers) jest obecny w całkowicie zaufanym zestawie i typ w zestawie dziedziczy z typu, który nie zezwala na dostęp częściowo zaufanych wywołań, mogą zostać wykorzystane luki w zabezpieczeniach.|
|[CA2118: Przejrzyj przypadki użycia atrybutu SuppressUnmanagedCodeSecurityAttribute](../code-quality/ca2118-review-suppressunmanagedcodesecurityattribute-usage.md)|SuppressUnmanagedCodeSecurityAttribute zmienia domyślne zachowanie systemu zabezpieczeń dla elementów członkowskich wykonujących kod niezarządzany, który używa wywołań międzyoperacyjnych COM lub platformy. Atrybut ten jest używany głównie w celu zwiększenia wydajności; jednak wzrost wydajności powoduje znaczące zagrożenia dla bezpieczeństwa.|
|[CA2119: Pieczętuj metody, które spełniają wymagania interfejsów prywatnych](../code-quality/ca2119-seal-methods-that-satisfy-private-interfaces.md)|Dziedziczny typ publiczny dostarcza zastępowalną implementację metody wewnętrznego interfejsu (Friend w języku Visual Basic). Aby naprawić naruszenie tej zasady, należy zapobiegać zastąpieniu metody poza zestawem.|
|[CA2120: Zabezpiecz konstruktory serializacji](../code-quality/ca2120-secure-serialization-constructors.md)|Typ ten ma konstruktor, który przyjmuje obiekt System.Runtime.Serialization.SerializationInfo i obiekt System.Runtime.Serialization.StreamingContext (podpis konstruktora serializacji). Ten konstruktor nie jest zabezpieczony przez sprawdzanie zabezpieczeń, ale jeden lub kilka regularnych konstruktorów typu jest zabezpieczonych.|
|[CA2121: Konstruktory statyczne powinny być prywatne](../code-quality/ca2121-static-constructors-should-be-private.md)|System wywołuje statyczny konstruktor przed utworzeniem pierwszego wystąpienia typu lub przed odwołaniem do któregokolwiek ze statycznych elementów członkowskich. Jeśli konstruktor statyczny nie jest prywatny, może być wywołany przez kod inny niż system. W zależności od operacji, które są wykonywane w konstruktorze, może to spowodować nieoczekiwane zachowanie.|
|[CA2122: Nie ujawniaj pośrednio metod żądaniami LinkDemand](../code-quality/ca2122-do-not-indirectly-expose-methods-with-link-demands.md)|Element członkowski publiczny lub chroniony ma zapotrzebowanie na łącza i jest wywoływany przez element członkowski, który nie sprawdza zabezpieczeń. Zapotrzebowanie na łącza sprawdza uprawnienia tylko bezpośredniego wywołującego.|
|[CA2123: Przesłonięcia żądań konsolidacji powinny być identyczne z podstawowymi](../code-quality/ca2123-override-link-demands-should-be-identical-to-base.md)|Ta reguła dopasowuje metodę do jej metody podstawowej, która jest interfejsem lub metodą wirtualną innego typu, a następnie porównuje zapotrzebowania na łącza na każdym z nich. Jeśli zasada ta jest naruszona, złośliwy wywołujący może pominąć zapotrzebowanie na łącza przez wywołanie niezabezpieczonej metody.|
|[CA2124: Opakuj podatne na przejęcie klauzule finally w zewnętrzny blok try](../code-quality/ca2124-wrap-vulnerable-finally-clauses-in-outer-try.md)|Metoda publiczna lub chroniona zawiera blok try/finally. Wygląda na to, że blok finally resetuje stan zabezpieczeń i sam nie jest ujęty w bloku finally.|
|[CA2126: Żądania LinkDemand dla typu wymagają żądań dziedziczenia](../code-quality/ca2126-type-link-demands-require-inheritance-demands.md)|Niezamknięty typ publiczny jest chroniony za pomocą zapotrzebowania na łącza i ma metodę, którą można zastąpić. Ani typ, ani metoda nie są chronione za pomocą żądania dziedziczenia.|
|[CA2130: Stałe krytyczne pod względem zabezpieczeń powinny być przezroczyste](../code-quality/ca2130-security-critical-constants-should-be-transparent.md)|Wymuszanie przezroczystości nie jest wymuszane dla wartości stałych, ponieważ kompilatory wbudowują stałe wartości, tak aby nie było wymagane żadne wyszukiwanie w czasie wykonywania. Stałe pola powinny być przezroczyste dla zabezpieczeń, tak aby recenzenci kodu nie zakładali, że przezroczysty kod nie może uzyskać dostępu do stałej.|
|[CA2131: Typy krytyczne pod względem zabezpieczeń nie mogą brać udziału w określaniu równoważności typów](../code-quality/ca2131-security-critical-types-may-not-participate-in-type-equivalence.md)|Typ uczestniczy w równoważniku typu i sam typ lub element członkowski lub pole o typie, jest oznaczona za pomocą atrybutu SecurityCriticalAttribute. Ta reguła jest uruchamiana na wszystkich typach krytycznych lub typach zawierających metody krytyczne lub pola, które uczestniczą w równoważeniu typu. Gdy CLR wykryje taki typ, uniemożliwia jego załadowanie, wywołując w czasie wykonywania wyjątek TypeLoadException. Zazwyczaj ta reguła uruchamiana jest tylko wtedy, gdy użytkownicy implementują równoważenie typu ręcznie, zamiast wykonać je, opierając się na otokach tlbimp i kompilatorach.|
|[CA2132: Konstruktory domyślne muszą być co najmniej tak krytyczne jak konstruktory domyślne typu podstawowego](../code-quality/ca2132-default-constructors-must-be-at-least-as-critical-as-base-type-default-constructors.md)|Typy i elementy członkowskie, które mają atrybut SecurityCriticalAttribute, nie mogą być używane przez kod aplikacji Silverlight. Krytyczne dla bezpieczeństwa typy i składowe mogą być używane tylko przez zaufany kod w środowisku .NET Framework dla biblioteki klas Silverlight. Ze względu na to, że publiczna lub chroniona konstrukcja w klasie pochodnej musi mieć taką samą lub większą przejrzystość jak jej klasa bazowa, klasy w aplikacji nie mogą pochodzić z klasy oznaczonej jako SecurityCritical.|
|[CA2133: Delegaci muszą być powiązani z metodami ze spójną przezroczystością](../code-quality/ca2133-delegates-must-bind-to-methods-with-consistent-transparency.md)|To ostrzeżenie uruchamiane jest na metodzie wiążącej obiekt delegowany, oznaczony za pomocą atrybutu SecurityCriticalAttribute, do metody, która jest przezroczysta lub oznaczona za pomocą atrybutu SecuritySafeCriticalAttribute. Ostrzeżenie jest także uruchamiane na metodzie wiążącej obiekt delegowany, który jest przezroczysty lub bezpieczny-krytyczny dla metody krytycznej.|
|[CA2134: Metody muszą zachowywać spójną przezroczystość podczas nadpisywania metod bazowych](../code-quality/ca2134-methods-must-keep-consistent-transparency-when-overriding-base-methods.md)|Ta reguła jest uruchamiana, gdy metoda oznaczona za pomocą atrybutu SecurityCriticalAttribute zastępuje metodę, która jest przezroczysta lub oznaczona za pomocą atrybutu SecuritySafeCriticalAttribute. Reguła ta jest również uruchamiana, gdy metoda przezroczysta lub oznaczona atrybutem SecuritySafeCriticalAttribute zastępuje metodę oznaczoną atrybutem SecurityCriticalAttribute. Reguła jest stosowana podczas zastępowania metody wirtualnej lub implementującej interfejs.|
|[CA2135: Zestawy poziomu 2 nie powinny zawierać żądań LinkDemand](../code-quality/ca2135-level-2-assemblies-should-not-contain-linkdemands.md)|LinkDemands są przestarzałe w zestawie reguł zabezpieczeń poziomu 2. Zamiast używania LinkDemands do wymuszenia zabezpieczeń w czasie kompilacji just in time (JIT), należy oznaczyć metody, typy i pola za pomocą atrybutu SecurityCriticalAttribute.|
|[CA2136: Adnotacje przezroczystości składowych nie powinny powodować konfliktu](../code-quality/ca2136-members-should-not-have-conflicting-transparency-annotations.md)|Atrybuty przezroczystości są stosowane od elementów kodu o większym zakresie do elementów o mniejszym zakresie. Atrybuty przezroczystości elementów kodu z większym zakresem mają pierwszeństwo przed atrybutami przejrzystości elementów kodu, które są zawarte w pierwszym elemencie. Na przykład klasa, która jest oznaczona za pomocą atrybutu SecurityCriticalAttribute, nie może zawierać metody oznaczonej atrybutem SecuritySafeCriticalAttribute.|
|[CA2137: Metody przezroczyste muszą zawierać tylko weryfikowalny język pośredni](../code-quality/ca2137-transparent-methods-must-contain-only-verifiable-il.md)|Metoda zawiera nieweryfikowalny kod lub zwraca typ przez odwołanie. Ta reguła jest uruchamiana podczas próby wykonywania przez kod przezroczysty pod względem zabezpieczeń nieweryfikowalnego MSIL (Microsoft Intermediate Language). Jednak reguła nie zawiera pełnej weryfikacji IL i używa heurystyki do wykrywania większości naruszeń weryfikacji MSIL.|
|[CA2138: Metody przezroczyste nie mogą wywoływać metod z atrybutem SuppressUnmanagedCodeSecurity](../code-quality/ca2138-transparent-methods-must-not-call-methods-with-the-suppressunmanagedcodesecurity-attribute.md)|Metoda przezroczysta pod względem bezpieczeństwa wywołuje metodę, która jest oznaczona za pomocą atrybutu SuppressUnmanagedCodeSecurityAttribute.|
|[CA2139: Metody przezroczyste nie mogą używać atrybutu HandleProcessCorruptingExceptions](../code-quality/ca2139-transparent-methods-may-not-use-the-handleprocesscorruptingexceptions-attribute.md)|Ta reguła jest uruchamiana na dowolną metodę, która jest przejrzysta i próbuje obsłużyć wyjątek uszkadzający proces przy użyciu atrybutu HandleProcessCorruptedStateExceptionsAttribute. Wyjątek uszkadzający proces to klasyfikacja wyjątków CLR w wersji 4.0 wyjątków, taki jak <xref:System.AccessViolationException>. Atrybut HandleProcessCorruptedStateExceptionsAttribute może być używany tylko przez metody krytyczne pod względem bezpieczeństwa i będzie ignorowany, jeśli zostanie zastosowany do metody przezroczystej.|
|[CA2140: Kod przezroczysty nie może przywoływać elementów krytycznych pod względem zabezpieczeń](../code-quality/ca2140-transparent-code-must-not-reference-security-critical-items.md)|Metody, które są oznaczone przez atrybut SecurityTransparentAttribute, wywołują niepubliczne elementy członkowskie, które są oznaczone jako SecurityCritical. Ta reguła analizuje wszystkie metody i typy w zestawie mieszanym przejrzyste i krytyczne i oznacza wszelkie wywołania w zakresie z przezroczystego kodu do niepublicznego krytycznego kodu, który nie jest oznaczony jako SecurityTreatAsSafe.|
|[CA2141: Metody przezroczyste nie mogą spełniać żądań LinkDemand](../code-quality/ca2141-transparent-methods-must-not-satisfy-linkdemands.md)|Metoda przezroczysta pod względem zabezpieczeń wywołuje metodę z zestawu, która nie jest oznaczona atrybutem AllowPartiallyTrustedCallersAttribute (APTCA), lub metoda przezroczysta pod względem zabezpieczeń spełnia żądanie LinkDemand dla typu lub metody.|
|[CA2142: Kod przezroczysty nie powinien być chroniony za pomocą żądań LinkDemand](../code-quality/ca2142-transparent-code-should-not-be-protected-with-linkdemands.md)|Ta reguła jest uruchamiana na przezroczystych metodach wymagających żądania LinkDemands, aby uzyskać do nich dostęp. Przezroczysty kod zabezpieczeń nie powinien być odpowiedzialny za weryfikację zabezpieczeń operacji, a zatem nie powinien wymagać uprawnień.|
|[CA2143: Metody przezroczyste nie powinny używać żądań zabezpieczeń](../code-quality/ca2143-transparent-methods-should-not-use-security-demands.md)|Przezroczysty kod zabezpieczeń nie powinien być odpowiedzialny za weryfikację zabezpieczeń operacji, a zatem nie powinien wymagać uprawnień. Przejrzysty pod względem bezpieczeństwa kod powinien używać pełnych żądań do podejmowania decyzji związanych z zabezpieczeniami, a kod krytyczny pod względem zabezpieczeń nie powinien opierać się na kodzie przezroczystym do wykonywania pełnego żądania.|
|[CA2144: Kod przezroczysty nie powinien ładować zestawów z tablic bajtowych](../code-quality/ca2144-transparent-code-should-not-load-assemblies-from-byte-arrays.md)|Przegląd zabezpieczeń dla kodu przezroczystego nie jest tak dokładny jak kodu krytycznego pod względem bezpieczeństwa, ponieważ przezroczysty kod nie może wykonywać czynności wrażliwych pod względem bezpieczeństwa. Zestawy, ładowane z tablicy bajtowej, mogą nie być niezauważone w przezroczystym kodzie, a ta tablica bajtów może zawierać krytyczny albo, co ważniejsze, krytyczny dla bezpieczeństwa kod, który powinien być poddany inspekcji.|
|[CA2145: Metody przezroczyste nie powinny być dekorowane za pomocą atrybutu SuppressUnmanagedCodeSecurityAttribute](../code-quality/ca2145-transparent-methods-should-not-be-decorated-with-the-suppressunmanagedcodesecurityattribute.md)|Metody, które są oznaczone przez atrybut SuppressUnmanagedCodeSecurityAttribute, mają niejawne żądanie LinkDemand umieszczone na dowolnej metodzie, która je wywołuje. Ten element LinkDemand wymaga, aby kod wywołujący był krytyczny dla bezpieczeństwa. Oznaczanie metody, która używa zabezpieczenia SuppressUnmanagedCodeSecurity poprzez użycie atrybutu SecurityCriticalAttribute, sprawia, że wymóg ten jest bardziej oczywisty dla obiektów wywołujących metodę.|
|[CA2146: Typy muszą być co najmniej tak krytyczne jak ich typy i interfejsy podstawowe](../code-quality/ca2146-types-must-be-at-least-as-critical-as-their-base-types-and-interfaces.md)|Ta reguła jest uruchamiana, gdy typ pochodny ma atrybut przezroczystości pod względem zabezpieczeń, który nie jest tak krytyczny, jak jego typ podstawowy lub zaimplementowany interfejs. Tylko typy krytyczne pod względem zabezpieczeń mogą pochodzić od podstawowych typów krytycznych lub implementować interfejsy krytyczne, a tylko typy krytyczne lub krytyczne dla bezpieczeństwa mogą pochodzić od podstawowych typów krytycznych dla bezpieczeństwa lub implementować interfejsy krytyczne dla bezpieczeństwa.|
|[CA2147: Metody przezroczyste nie mogą używać asercji zabezpieczeń](../code-quality/ca2147-transparent-methods-may-not-use-security-asserts.md)|Reguła ta analizuje wszystkie metody i typy w zestawie, który jest w 100% przezroczysty lub mieszany przezroczysto-krytyczny i zaznacza deklaratywne lub imperatywne użycie potwierdzenia.|
|[CA2149: Metody przezroczyste nie mogą wywoływać kodu natywnego](../code-quality/ca2149-transparent-methods-must-not-call-into-native-code.md)|Ta reguła jest uruchamiana na każdej przezroczystej metody metodę, która wywołuje bezpośrednio kod natywny, na przykład za pośrednictwem metody P/Invoke. Naruszenie tej zasady prowadzi do wyjątku MethodAccessException w poziomie 2 modelu przezroczystości i pełnego żądania dla UnmanagedCode w modelu przezroczystości poziomu 1.|
|[CA2151: Pola typu krytycznego powinny być krytyczne pod względem zabezpieczeń](../code-quality/ca2151-fields-with-critical-types-should-be-security-critical.md)|Aby używać typów krytycznych pod względem zabezpieczeń, kod odwołujący się do typu musi być albo krytyczny pod względem zabezpieczeń, albo bezpieczny-krytyczny pod względem zabezpieczeń. Ta zasada obowiązuje nawet w przypadku odwołania pośredniego. Dlatego pole mające zabezpieczenia przezroczyste lub pole bezpieczne-krytyczne pod względem zabezpieczeń jest mylące, ponieważ przezroczysty kod nadal nie będzie mógł uzyskać dostępu do pola.|
|[Deklaracje CA5122 P/Invoke nie powinny być bezpieczne-krytyczne](../code-quality/ca5122-p-invoke-declarations-should-not-be-safe-critical.md)|Metody są oznaczone jako SecuritySafeCritical, gdy wykonują operacje zależne od zabezpieczeń, ale mogą być również bezpiecznie używane przez kod przezroczystości. Kod przezroczystości może nigdy bezpośrednio nie wywołać kodu natywnego za pośrednictwem metody P/Invoke. Dlatego oznakowanie metody P/Invoke jako bezpiecznej-krytycznej pod względem zabezpieczeń nie umożliwi jej wywołania kodu przezroczystości i jest mylące dla analizy zabezpieczeń.|
|[CA2153: Unikaj obsługiwania uszkodzonych wyjątków stanu](../code-quality/ca2153-avoid-handling-corrupted-state-exceptions.md)|[Uszkodzony stan wyjątków (rozszerzenie klienta)](https://msdn.microsoft.com/magazine/dd419661.aspx) wskazać, że pamięć uszkodzenie istnieje w procesie. Przechwytywanie tych zamiast zezwalać awarię procesu może prowadzić do luk w zabezpieczeniach, jeśli osoba atakująca może wykorzystać do regionu pamięci uszkodzony.|
|[CA3075: Niezabezpieczone przetwarzanie definicji DTD](../code-quality/ca3075-insecure-dtd-processing.md)|Jeśli używasz niezabezpieczone wystąpień XmlReaderSettings lub odwoływać się do jednostek zewnętrznych źródeł, analizator może zaakceptować niezaufane dane wejściowe i ujawnienia poufnych informacji dla osób atakujących.|
|[CA3076: Niezabezpieczone wykonywanie skryptu XSLT](../code-quality/ca3076-insecure-xslt-script-execution.md)|Jeżeli insecurely wykonać Extensible arkuszy stylów języka przekształcenia (XSLT) w aplikacjach platformy .NET, procesor może zostać rozwiązany niezaufanych odwołań do identyfikatora URI, które można ujawnić poufne informacje do osoby atakujące, co prowadzi do "odmowa usługi" i Cross-Site ataki.|
|[CA3077: Niezabezpieczone przetwarzanie w elemencie Design interfejsu API, dokumencie XML i czytniku tekstu dla kodu XML](../code-quality/ca3077-insecure-processing-in-api-design-xml-document-and-xml-text-reader.md)|Podczas projektowania interfejsu API pochodną klasy XMLDocument i klasy XMLTextReader, być w trosce o XmlReaderSettings. Za pomocą niezabezpieczonego wystąpień XmlReaderSettings, gdy odwołuje się do rozpoznawania jednostek zewnętrznych źródeł lub ustawiania wartości niebezpieczne w XML może prowadzić do ujawnienia informacji.|
|[CA3147: Oznacz zlecenie obsługi za pomocą ValidateAntiForgeryToken](../code-quality/ca3147-mark-verb-handlers-with-validateantiforgerytoken.md)|Podczas projektowania kontroler składnika ASP.NET MVC, należy zachować ostrożność, fałszerstwo żądania międzywitrynowego ataków. Ataku polegającego na fałszerstwo żądania międzywitrynowego można wysyłać złośliwymi żądaniami z uwierzytelnionego użytkownika do kontrolera ASP.NET MVC.| | 284.722892 | 788 | 0.840386 | pol_Latn | 0.999877 |
b101102b70dd87ac8213f8246294082ebe47e99f | 7,069 | markdown | Markdown | blog/_posts/2014/2014-08-13-an-alle-unterstuetzer-danke-dass-ihr-jugend-hackt-moeglich-macht.markdown | schlos/okfnde | 73080177564c6387c6bdcd4df3ccd9ba6f9eaa27 | [
"MIT"
] | 20 | 2015-02-22T20:08:16.000Z | 2020-11-24T14:07:34.000Z | blog/_posts/2014/2014-08-13-an-alle-unterstuetzer-danke-dass-ihr-jugend-hackt-moeglich-macht.markdown | schlos/okfnde | 73080177564c6387c6bdcd4df3ccd9ba6f9eaa27 | [
"MIT"
] | 86 | 2015-01-14T16:21:34.000Z | 2021-09-16T13:28:17.000Z | blog/_posts/2014/2014-08-13-an-alle-unterstuetzer-danke-dass-ihr-jugend-hackt-moeglich-macht.markdown | schlos/okfnde | 73080177564c6387c6bdcd4df3ccd9ba6f9eaa27 | [
"MIT"
] | 40 | 2015-02-12T12:56:08.000Z | 2022-02-03T22:19:46.000Z | ---
author: Helene Hahn
date: 2014-08-13 13:09:36
image:
src: /files/blog/2014/08/fill_618x322_9732249824_28f9b493cc_b.jpg
layout: post
tags: []
title: 'An alle Unterstützer: Danke, dass ihr Jugend hackt möglich macht!'
type: post
---
Eigentlich wollte ja niemand wieder weg - Abschiedfoto nach Jugend hackt 2013
Für die zweite Ausgabe von [Jugend hackt](http://jugendhackt.de/) vom 12.-14. September 2014 werden aus allen Bundesländern insgesamt 120 Jugendliche nach Berlin kommen! Die Eventvorbereitungen laufen auf Hochtouren, und dazu machen uns die freiwilligen Mentor/innen mit ihrer Lust auf die Zusammenarbeit mit den Junghacker/innen noch mehr Vorfreude, als wir sowieso schon haben.
Das Event ist aber auch für Interessierte offen: Wir laden alle Neugierigen herzlich zur _öffentlichen Projektpräsentation am Sonntag, den 14.9 ab 11.30 Uhr_ ins Jugendhaus Königsstadt ein. Die Teilnahme ist kostenlos, [wir freuen uns aber über eine kleine Eintrittsspende](https://www.betterplace.org/de/projects/19214-jugend-hackt-forderprogramm-fur-programmierbegeisterte-jugendliche).
**Da Jugend hackt aber ohne finanzielle Unterstützung nicht denkbar wäre, möchten wir an dieser Stelle die Gelegenheit nutzen, unsere Partner vorzustellen:**
Die **[BSR ](http://www.bsr.de/)**ist eines der führenden Entsorgungsunternehmen Europas. Mit rund 5.300 Beschäftigten ist die BSR der größte kommunale Entsorger Deutschlands, ein wichtiger Arbeitgeber Berlins und auch ein vorbildliches Ausbildungsunternehmen. In insgesamt acht Berufen und drei Dualen Studiengängen – darunter auch Informatikkaufleute und das Studium der Wirtschaftsinformatik - bietet die BSR jungen Menschen eine fundierte Ausbildung.
**[Capgemini ](http://www.de.capgemini.com/)**ist eine globale IT- und Managementberatung mit weltweit rund 130.000 Mitarbeitern. Allein in Deutschland arbeiten mehrere Tausend Menschen tagtäglich, um unseren Kunden die besten Lösungen für ihre IT-Systeme, Prozesse und das Management zu bieten.
Das Ziel von **[Google ](https://www.google.de/)**ist es, die Informationen der Welt zu organisieren und für alle zu jeder Zeit zugänglich und nutzbar zu machen.
**[iteratec ](http://iteratec.de/)**ist der Software- und IT-Dienstleister mit der höchsten Kompetenzdichte und aktuell 200 Mitarbeitern an sechs Standorten. Das Aufgabenspektrum reicht von der Entwicklung der IT-Strategie über technologische und methodische Beratung bis hin zur individuellen Programmierung von kompletten Softwaresystemen. iteratec ist ausgezeichnet – z.B. mit 5 Sternen bei „Hamburgs beste Arbeitgeber“ und auf kununu als Top-Arbeitgeber mit einer der besten Work-Life-Balances in Deutschland.
Der **Jugend-Demokratiefonds Berlin** setzt sich mit dem Förderprogramm „[STARK gemacht!](http://www.stark-gemacht.de/de/index.php)“ für demokratische Strukturen sowie Partizipation ein und unterstützt Jugend hackt finanziell schon im zweiten Jahr.
Die **[kreuzwerker ](http://kreuzwerker.de/)**gestalten und begleiten IT-Prozesse mit viel Leidenschaft. Sie betreuen alle Phasen der Software-Entwicklung, leisten klassisches IT-Consulting, Architektur- und Technologieberatung, bieten DevOps und Testing und übernehmen die Projekt- und Entwicklungsleitung. Sie sind zertifizierte Scrum Master und Product Owner, Atlassian Experts-, Magnolia- und Amazon Web Services Partner.
Die **[mabb ](http://www.mabb.de/)**ist die gemeinsame Medienanstalt der Länder Berlin und Brandenburg. Sie fördert die Vielfalt im privaten Rundfunk und wirkt an der Entwicklung der audiovisuellen Medien in der Region Berlin-Brandenburg mit. Neben Regulierungs- und Förderungsaufgaben erfüllt die mabb zunehmend Informations- und Moderationsaufgaben. Als neutrale Institution mit öffentlichem Auftrag ist sie unabhängiger Berater für Akteure aus Politik und Wirtschaft.
Der **[O’Reilly Verlag](http://www.oreilly.de/)** bietet spannende Literatur für Bastler, Hacker, Nerds & Geeks und setzt sich mit uns gemeinsam für die Nachwuchsförderung ein. Das Team von O’Reilly engagiert sich schon seit vielen Jahren insbesondere an IT-Veranstaltungen und -Wettbewerben für Schüler und junge Erwachsene. Mit dem Thema “Frauen in der IT” stellt das Team außerdem im oreillyblog verschiedene Zugänge zur technischen Welt insbesondere für Frauen dar.
[Projekt Zukunft](http://www.berlin.de/projektzukunft/) – angesiedelt bei der **Berliner Senatsverwaltung für Wirtschaft, Technologie und Forschung** – ist die Berliner Landesinitiative zur Förderung des Wachstumsfeldes IKT, Medien, Kreativwirtschaft. Das Projekt Zukunft erarbeitet Strategien für den Standort, baut Plattformen auf, initiiert Netzwerke, organisiert den Austausch mit den Unternehmen, entwickelt neue Förderinstrumente, erstellt Studien und realisiert innovative Projekte für Wirtschaft und Gesellschaft.
Vielfalt, Chancengleichheit und lokale Entwicklung befördern und so dazu beitragen, das Gemeinwesen und dessen Zusammenhalt nachhaltig zu stärken - darin sieht die **[Stiftung Pfefferwerk](http://www.stpw.org)** ihre Aufgabe. Schwerpunktmäßig setzt sie ihre Ressourcen dafür ein, dass neue Arbeitsplätze entstehen und/oder die Chancen Benachteiligter auf einen Einstieg in das Erwerbsleben verbessert werden.
Die **[Technologiestiftung Berlin](http://www.tsb-berlin.de/)** steht für Innovation und Technologieentwicklung in der Hauptstadtregion. Sie fördert die Wissenschaft und unterstützt die Wirtschaft. Schwerpunkte der Arbeit sind Strategieentwicklung, Bildung und Wissenschaftskommunikation.
Es ist das Ziel von **[Wikimedia Deutschland](http://wikimedia.de/wiki/Hauptseite)**, dass die Idee des Freien Wissens Teil unseres Alltags wird. Wir wollen, dass kollaboratives Lernen mit frei nutzbaren Inhalten in Klassenräumen und Hörsälen selbstverständlich wird. Wir wollen, dass diese Art zu arbeiten kein gesellschaftliches Nischenthema bleibt. Wir überzeugen Museen, Wissenschafts- und andere Kulturinstitutionen davon, ihre Inhalte als Vorreiter freizugeben. Wir fordern sichere gesetzliche Rahmenbedingungen, sodass Projekte wie Wikipedia auch in Zukunft entstehen können.
**[zigzag ](http://www.zigzag.is)**ist eine international tätige Designagentur mit dem Schwerpunkt User Interface Design. Neben User Research, Interaction und Visual Design spielt die Prototyp- und Software-Entwicklung für die in Stuttgart ansässige Agentur eine immer wichtigere Rolle. Um auch den Nachwuchs fürs kreative Programmieren zu begeistern, unterstützt zigzag Jugend hackt und schickt acht junge Programmiertalente aus dem Südwesten nach Berlin.
**120 Jugendliche, 25 Mentor/innen und das Orgateam von Jugend hackt danken allen Sponsoren und Spendern ganz herzlich für ihre Unterstützung!**
**Wer ebenso wie wir und unsere Partner daran interessiert ist, den Programmiernachwuchs in Deutschland zu fördern und Interessierte für Informatik und Technologie in einem außerschulischen Rahmen zu begeistern, darf uns jederzeit kontaktieren. Wir freuen uns über Ihre [E-Mail](mailto:info@jugendhackt.de)!**
 | 135.942308 | 582 | 0.819494 | deu_Latn | 0.997629 |
b101736e28277884ec3a3e1317bbbb82fd2d6138 | 7,088 | md | Markdown | docs/ide/reference/options-text-editor-xaml-formatting.md | monkey3310/visualstudio-docs.pl-pl | adc80e0d3bef9965253897b72971ccb1a3781354 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/ide/reference/options-text-editor-xaml-formatting.md | monkey3310/visualstudio-docs.pl-pl | adc80e0d3bef9965253897b72971ccb1a3781354 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/ide/reference/options-text-editor-xaml-formatting.md | monkey3310/visualstudio-docs.pl-pl | adc80e0d3bef9965253897b72971ccb1a3781354 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Opcje, edytor tekstu, XAML, formatowanie
ms.date: 01/17/2017
ms.prod: visual-studio-dev15
ms.technology: vs-ide-general
ms.topic: reference
f1_keywords:
- VS.ToolsOptionsPages.Text_Editor.XAML.Formatting.General
- VS.ToolsOptionsPages.Text_Editor.XAML.Miscellaneous
- VS.ToolsOptionsPages.Text_Editor.XAML.Formatting.Spacing
helpviewer_keywords:
- element spacing, XAML view settings
- attribute spacing, XAML view settings
- XAML view settings, auto-formatting events
- auto-formatting events, XAML view settings
- XAML view settings, tag wrapping
- XAML view settings, auto insert
- quotation mark style, XAML view settings
- XAML formatting, WPF Designer
- XAML view settings, Toolbox
- XAML view settings, element spacing
- default view, XAML view settings
- auto insert, XAML view settings
- XAML view settings, default view
- XAML view settings, quotation mark style
- tag wrapping, XAML view settings
- WPF Designer, XAML formatting
- XAML view settings, attribute spacing
ms.assetid: ad3820b1-0d94-4807-a74c-c3467ed973a2
author: gewarren
ms.author: gewarren
manager: douge
ms.workload:
- uwp
ms.openlocfilehash: 59b161c1f2dedd0b9c14f9949cfcc164f39b26ea
ms.sourcegitcommit: e13e61ddea6032a8282abe16131d9e136a927984
ms.translationtype: MT
ms.contentlocale: pl-PL
ms.lasthandoff: 04/26/2018
ms.locfileid: "31950036"
---
# <a name="options-text-editor-xaml-formatting"></a>Opcje, edytor tekstu, XAML, formatowanie
Użyj **formatowanie** strony właściwości, aby określić sposób formatowania elementów i atrybutów w dokumencie XAML. Aby otworzyć **opcje** okno dialogowe, kliknij przycisk **narzędzia** menu, a następnie kliknij przycisk **opcje**. Aby uzyskać dostęp do **formatowanie** właściwości rozwiń pozycję **Edytor tekstu**, **XAML**, **formatowanie** węzła.
> [!NOTE]
> Okna dialogowe i polecenia menu mogą się różnić od tych opisanych w Pomocy, w zależności od ustawień aktywnych lub wydania. Aby zmienić ustawienia, wybierz **Import i eksport ustawień** na **narzędzia** menu. Aby uzyskać więcej informacji, zobacz [personalizowanie środowiska IDE programu Visual Studio](../../ide/personalizing-the-visual-studio-ide.md).
## <a name="auto-formatting-events"></a>Automatyczne formatowanie zdarzeń
Automatyczne formatowanie może wystąpić, gdy dowolne z następujących zdarzeń wykryciu.
- Zakończenie tagu końcowego lub prostego.
- Zakończeniu tagu początkowego.
- Wklejanie ze Schowka.
- Formatowanie polecenia klawiatury.
Można określić zdarzenia, które powodują automatyczne formatowanie.
|||
|-|-|
|**Po zakończeniu tagu końcowego lub prostego**|Automatyczne formatowanie występuje po zakończeniu wpisywania tagu końcowego lub prostego tagu. Prostych tagów nie ma atrybutów, na przykład `<Button />`.|
|**Po zakończeniu tagu początkowego**|Automatyczne formatowanie występuje po zakończeniu wpisywania tagu początkowego.|
|**Po wklejeniu ze Schowka**|Automatyczne formatowanie występuje podczas wklejania XAML ze Schowka do widoku XAML.|
## <a name="quotation-mark-style"></a>Styl znaku cudzysłowu
To ustawienie wskazuje, czy wartości atrybutów są ujęte w cudzysłów pojedynczym lub podwójnym. Program formatujący automatycznie i automatycznego uzupełniania IntelliSense Użyj tego ustawienia.
Po ustawieniu tej opcji tylko atrybuty później dodane przy użyciu narzędzia Projektant lub ręcznie w widoku XAML dotyczy problem.
|||
|-|-|
|**Podwójny cudzysłów (")**|Wartości atrybutów są ujęte w cudzysłów.<br /><br /> `<Button Name="button1">Hello</Button>`|
|**Pojedynczych cudzysłowów (')**|Wartości atrybutów są ujęte w apostrofy.<br /><br /> `<Button Name='button1'>Hello</Button>`|
## <a name="tag-wrapping"></a>Zawijanie taga
Można podać długość wiersza zawijanie znacznika. Po włączeniu zawijanie tagów żadnych XAML dodane przy użyciu projektanta będzie odpowiednio zawijany.
|||
|-|-|
|**Zawijaj tagi przekraczające określoną długość**|Określa, czy wiersze są ujęte w wierszu długości określonej przez **długość**.|
|**długość**|Liczba znaków, które mogą zawierać wiersza. W razie potrzeby wiersze XAML może przekraczać długości określonej linii.|
## <a name="attribute-spacing"></a>Odstępy atrybutów
Użyj tego ustawienia, aby kontrolować sposób rozmieszczenia atrybutów w dokumencie XAML
|||
|-|-|
|**Zachowaj newlines i spacji między atrybutami**|Nowe wiersze i spacji między atrybutami nie dotyczy automatyczne formatowanie.<br /><br /> `<Button Height="23" Name="button1"`<br /><br /> `Width="75">Hello</Button>`|
|**Wstaw odstęp między atrybutami**|Atrybuty zajmują jeden wiersz z jednego miejsca oddzielanie atrybuty sąsiadujących ze sobą. Ustawienia zawijania tagów są stosowane.<br /><br /> `<Button Height="23" Name="button1" Width="75">Hello</Button>`|
|**Umieść każdy atrybut w osobnym wierszu**|Każdy atrybut zajmuje w osobnym wierszu. Jest to przydatne, gdy wiele atrybutów są obecne.<br /><br /> `<Button`<br /><br /> `Height="23"`<br /><br /> `Name="button1"`<br /><br /> `Width="75">Hello</Button>`|
|**Pozycja pierwszego atrybutu w tym samym wierszu co tag początkowy**|Po zaznaczeniu tej opcji, zostanie wyświetlony pierwszy atrybut w tym samym wierszu co tag początkowy elementu.<br /><br /> `<Button Height="23"`<br /><br /> `Name="button1"`<br /><br /> `Width="75">Hello</Button>`|
## <a name="element-spacing"></a>Odstępy elementów
Użyj tego ustawienia, aby kontrolować sposób rozmieszczenia elementów w dokumencie XAML
|||
|-|-|
|**Zachowaj nowe wiersze w zawartości**|Puste wiersze w zawartości elementu nie są usuwane.<br /><br /> `<Grid>`<br /><br /> ``<br /><br /> ``<br /><br /> `<Button Name="button1">Hello</Button>`<br /><br /> ``<br /><br /> `</Grid>`|
|**Zwiń wiele puste wiersze w zawartości do jednej linii**|Puste wiersze w zawartości elementu są zwijane do jednego wiersza.<br /><br /> `<Grid>`<br /><br /> ``<br /><br /> `<Button Name="button1">Hello</Button>`<br /><br /> ``<br /><br /> `</Grid>`|
|**Usuń puste wiersze w zawartości**|Zostaną usunięte wszystkie puste wiersze w zawartości elementu.<br /><br /> `<Grid>`<br /><br /> `<Button Name="button1">Hello</Button>`<br /><br /> `</Grid>`|
## <a name="miscellaneous-section-auto-insert"></a>Różne części, automatyczne wstawianie
To ustawienie służy do kontrolowania, kiedy tagów i cudzysłowy są generowane automatycznie.
|||
|-|-|
|**Zamykanie tagów**|Określa, czy tagu zamykającego element jest generowany automatycznie podczas zamykania otwierający tag o większej niż znaku (>).|
|**Cudzysłowy atrybutu**|Określa, czy otaczającego cudzysłowy są generowane w przypadku wybrania wartości atrybutu z listy rozwijanej uzupełniania instrukcji.|
|**Klamrowe nawiasy zamykające do wyrażenia MarkupExtension**|Określa, czy rozszerzenie znacznika zamykającego nawiasu (}) jest generowana automatycznie po wpisaniu otwarcia nawiasy znak ({}).|
|**Oddzielać parametry wyrażeń MarkupExtension**|Określa, czy przecinkami są generowane po wpisaniu więcej niż jeden parametr w rozszerzeniu znaczników.|
## <a name="see-also"></a>Zobacz także
- [XAML w WPF](/dotnet/framework/wpf/advanced/xaml-in-wpf)
| 60.067797 | 356 | 0.754233 | pol_Latn | 0.999589 |
b101eb36dc94c9fd80671bc71ef0a3c011fd6143 | 2,009 | md | Markdown | README.md | txus/fuby | 1adcdb04dffe5f387417d4b7a27b6879123b7a3a | [
"MIT"
] | 25 | 2015-01-01T13:39:29.000Z | 2021-05-16T17:44:51.000Z | README.md | txus/fuby | 1adcdb04dffe5f387417d4b7a27b6879123b7a3a | [
"MIT"
] | null | null | null | README.md | txus/fuby | 1adcdb04dffe5f387417d4b7a27b6879123b7a3a | [
"MIT"
] | 2 | 2015-02-15T06:54:26.000Z | 2016-10-11T17:05:09.000Z | # fuby [](http://travis-ci.org/txus/fuby)
### Functional Ruby
Fuby is a hybrid functional/object-oriented programming language with the same
syntax as Ruby, although pretty different semantics in many aspects.
It targets the Rubinius VM, so you need to install Rubinius to run it.
It is just an idea for now. Some of its features might or might not be:
* Pervasive immutability
* Controlled IO
* Methods as first-class functions
* [Some] laziness
* Monads
Keep checking this repository for new ideas, code examples and so on :)
## Features
Fuby starts out as a fully compliant Ruby interpreter, and as I develop more and
more, its semantics will differ more and more from Ruby, normally in backwards
incompatible ways. Here's what's implemented for now:
### Immutable strings
All strings are instances of Fuby::String, which is an immutable kind of String.
### Variables are not reassignable
Variables cannot be reassigned a different value.
```ruby
a = 3
a = 5 # will raise a Fuby::CompileError
```
### Real pattern matching
Pattern matching is implemented in `case` statements. If you want to match in
the old ruby style, with procs or regexes or classes, you still can:
```ruby
case 1
when Integer
3
else
10
end
# => 3
```
But the interesting part is matching **predicates** that will bind variables
inside the `when` body:
```ruby
case 1
when x.odd?
x + 2
else
10
end
# => 3
```
And the best is that it works with any destructurable sequence. And you can
ignore a certain value with `_`:
```ruby
case [100, 2, :foo]
when Integer, x.even?, _
x + 1
else
10
end
# => 3
```
## Installation
After installing Rubinius, install Fuby as a gem:
$ gem install fuby
## Usage
$ fuby my_program.fb
## Who's this
This was made by [Josep M. Bach (Txus)](http://txustice.me) under the MIT
license. I'm [@txustice][twitter] on twitter (where you should probably follow
me!).
[twitter]: https://twitter.com/txustice
| 20.71134 | 100 | 0.725734 | eng_Latn | 0.997155 |
b101fcb40d3652c70c5be24e5a9e9e4fbf584b58 | 50 | md | Markdown | README.md | raul-arrabales/machismo | 391e94b52dd49bbafcbbd1ef2706669e6100efeb | [
"Apache-2.0"
] | null | null | null | README.md | raul-arrabales/machismo | 391e94b52dd49bbafcbbd1ef2706669e6100efeb | [
"Apache-2.0"
] | null | null | null | README.md | raul-arrabales/machismo | 391e94b52dd49bbafcbbd1ef2706669e6100efeb | [
"Apache-2.0"
] | null | null | null | # machismo
Crowdsourcing Male Chauvinism Dataset
| 16.666667 | 38 | 0.84 | yue_Hant | 0.947595 |
b102819c277ac30c99632a49d51849e46065f43a | 3,943 | md | Markdown | docs/configure/babel.md | SACHINnANYAKKARA/storybook | a7b57d4e71960bafb5c34ccfa393e1abcde6cd8e | [
"MIT"
] | 34,857 | 2019-05-30T22:29:14.000Z | 2022-03-31T22:36:01.000Z | docs/configure/babel.md | SACHINnANYAKKARA/storybook | a7b57d4e71960bafb5c34ccfa393e1abcde6cd8e | [
"MIT"
] | 10,039 | 2019-05-30T23:23:09.000Z | 2022-03-31T23:47:28.000Z | docs/configure/babel.md | SACHINnANYAKKARA/storybook | a7b57d4e71960bafb5c34ccfa393e1abcde6cd8e | [
"MIT"
] | 5,457 | 2019-05-30T22:33:54.000Z | 2022-03-31T17:29:50.000Z | ---
title: 'Babel'
---
Storybook’s webpack config by [default](#default-configuration) sets up [Babel](https://babeljs.io/) for ES6 transpiling.
It has three different modes:
- **CRA** - the mode for Create React App apps specifically
- **V6** - the default mode for version 6.x and below
- **V7** - a new mode slated to become the default in SB7.x
## CRA mode
CRA apps configured with `@storybook/preset-create-react-app` use CRA's babel handling to behave as close as possible to your actual application. None of the other documentation on this page applies.
## V6 mode
Storybook works with evergreen browsers by default.
If you want to run Storybook in IE11, make sure to [disable](../essentials/introduction#disabling-addons) the docs-addon that is part of `@storybook/addon-essentials`, as this currently [causes issues in IE11](https://github.com/storybookjs/storybook/issues/8884).
Here are some key features of Storybook's Babel configurations.
### Default configuration
We have added ES2016 support with Babel for transpiling your JS code.
In addition to that, we've added a few additional features, like object spreading and async await.
Check out our [source](https://github.com/storybookjs/storybook/blob/next/lib/core-common/src/utils/babel.ts) to learn more about these plugins.
### Custom config file
If your project has a `.babelrc` file, we'll use that instead of the default config file.
You can also place a `.storybook/.babelrc` file to use a special configuration for Storybook only.
### Custom configuration
If you need to further configure/extend the babel config Storybook uses, you can use the `babel` field of [`.storybook/main.js`](./overview#configure-your-storybook-project):
```js
// .storybook/main.js
module.exports = {
//...
babel: async (options) => ({
...options,
// any extra options you want to set
}),
};
```
## V7 Mode
V7 mode is a new option available in Storybook 6.4+ behind a feature flag.
Its goal is to make Babel configuration simpler, less buggy, easier to troubleshoot, and more consistent with the rest of the JS ecosystem.
In V7 mode, you are responsible for configuring Babel using your `.babelrc` file and Storybook does not provide any default. Storybook's frameworks and addons may provide small programmatic modifications to the babel configuration.
### Activating
To activate V7 mode, set the feature flag in your `.storybook/main.js` config:
```js
module.exports = {
// ... your existing config
features: {
babelModeV7: true,
},
};
```
### Migrating from V6
For detailed instructions on how to migrate from `V6` mode please see [MIGRATION.md](https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#babel-mode-v7).
### Generate a babelrc
If your app does not use a babelrc and you need one, you can generate a babelrc file by running the following command in your project directory:
```sh
npx sb@next babelrc
```
This will create a `.babelrc.json` file. You may need to add package dependencies.
### Troubleshooting
To troubleshoot your babel configuration, set the `BABEL_SHOW_CONFIG_FOR` environment variable.
For example, to see how Storybook is transpiling your `.storybook/preview.js` config:
```sh
BABEL_SHOW_CONFIG_FOR=.storybook/preview.js yarn storybook
```
This will print out the babel configuration for `.storybook/preview.js`, which can be used to debug when files fail to transpile or transpile incorrectly.
> NOTE: Due to what appears to be a Babel bug, setting this flag causes Babel transpilation to fail on the file provided. Thus you cannot actually _RUN_ storybook using this command. However, it will print out the configuration information as advertised and thus you can use this to debug your Storybook. You'll need to remove the flag to actually run your Storybook.
For more info, please refer to the [Babel documentation](https://babeljs.io/docs/en/configuration#print-effective-configs).
| 37.552381 | 367 | 0.758306 | eng_Latn | 0.991102 |
b1037023eb5bcd564cb1a3b810d56276b892a403 | 42 | md | Markdown | README.md | khsi12345/www | 3e5cca5a5ac26f0df6d883307b8c9a17c494b20c | [
"MIT"
] | null | null | null | README.md | khsi12345/www | 3e5cca5a5ac26f0df6d883307b8c9a17c494b20c | [
"MIT"
] | null | null | null | README.md | khsi12345/www | 3e5cca5a5ac26f0df6d883307b8c9a17c494b20c | [
"MIT"
] | null | null | null | # HTML / CSS
> 2주차 HTML / CSS 강의 실습 및 이론. | 14 | 28 | 0.571429 | kor_Hang | 1.00001 |
b10445c01864ff37fc5d19e5c421219a2203d94e | 2,422 | md | Markdown | nlp/obp_api/README.md | shivdeep-singh/conversational-ai-chatbot | b67802a96b3fe3d64457931a8cbf8bf03442fd0d | [
"BSD-3-Clause"
] | 11 | 2021-09-09T16:16:48.000Z | 2022-03-31T21:25:46.000Z | nlp/obp_api/README.md | shivdeep-singh/conversational-ai-chatbot | b67802a96b3fe3d64457931a8cbf8bf03442fd0d | [
"BSD-3-Clause"
] | 1 | 2022-02-10T06:08:11.000Z | 2022-02-10T06:08:11.000Z | nlp/obp_api/README.md | shivdeep-singh/conversational-ai-chatbot | b67802a96b3fe3d64457931a8cbf8bf03442fd0d | [
"BSD-3-Clause"
] | 12 | 2021-09-19T10:39:27.000Z | 2022-03-09T05:17:05.000Z | # obp_api
It is a client sdk/library to connect to [openbankingproject](https://www.openbankproject.com/) api server. It is possible to use this library to connect to a server hosted at `https://apisandbox.openbankproject.com`. The server can however be run locally also after following instructions from [openbanking api github]( https://github.com/OpenBankProject/OBP-API.git) repo.
This component has a library which is extensible to support all endpoints of obp api server. The `accounts.py` implements a class to support accounts obp api. Similarly all apis will be supported by extending `base.py` which handles all http request infrastructure. The api supported and to be supported is [here](https://apiexplorersandbox.openbankproject.com/)
## Pre-Requisites
- python3
- a running openbanking server instance
- openbanking server credentials.
## Install
```bash
$ python setup.py install
or
$ pip3 install .
```
## Config for Login
The library support `config.yml` in the following format. It can be a file or a string in the memory.
```yaml
credentials:
URL: https://apisandbox.openbankproject.com
API: v4.0.0
username: someusernamehere
password: somepasswordhere
consumer_key: mthisisatokehgdogqhba22lp2dfbs3qg5rmutx2
```
### `config.yml` as a file
Create a file `config.yml` with the data above.
```python
from obp_api import base
config_file = 'config.yml'
connection_helper = base.Connector(config_file)
connection_helper.login()
```
### `config.yml` as an in memory string
```python
from obp_api import base
import io
import yaml
def _prepare_login_config(user, pwd, apikey):
yaml_str = '''credentials:
URL: https://apisandbox.openbankproject.com
API: v4.0.0
username:
password:
consumer_key:
'''
data = yaml.safe_load(yaml_str)
data['credentials']['username'] = user
data['credentials']['password'] = pwd
data['credentials']['consumer_key'] = apikey
configyam = io.StringIO()
yaml.dump(data, configyam)
return io.StringIO(configyam.getvalue())
config_file = _prepare_login_config('someuser', 'somepass', 'someapikey')
connection_helper = base.Connector(config_file)
connection_helper.login()
```
## Run Example
```
# create a config for credentials as `config.yml`
cd examples
python list_banks.py -c config.yml
```
## Limitations
- It is not exhaustive, all apis are not implemented.
- Only `Direct Login` is supported.
| 25.494737 | 374 | 0.745252 | eng_Latn | 0.922337 |
b104693491a8b9dfd4940eb3b867705b3d0110cf | 1,391 | md | Markdown | _posts/2016-03-19-MongoDB-Universitesi-1.Hafta.md | oguzdag/oguzdag.github.io | 897310d0ff09ad971029f279109c6b026820122d | [
"MIT"
] | null | null | null | _posts/2016-03-19-MongoDB-Universitesi-1.Hafta.md | oguzdag/oguzdag.github.io | 897310d0ff09ad971029f279109c6b026820122d | [
"MIT"
] | null | null | null | _posts/2016-03-19-MongoDB-Universitesi-1.Hafta.md | oguzdag/oguzdag.github.io | 897310d0ff09ad971029f279109c6b026820122d | [
"MIT"
] | null | null | null | ---
published: true
layout: post
title: "MongoDB University - Week 1"
categories:
- mongodb
---
Yes, first week started, approximately 2 hours video and homeworks completed :)
**"MongoDB for Developers"** dersi, MongoDB'nin kurulması, Python, PyMongo, Bottle kurulması üzerineydi. Bunları kurduysanız ve çalışır durumdaysa, homework yapmakta sıkıntı yok. Hazır verilen python'ları çalıştırıp sonuçları yazıyorsunuz. Özellikle Python array ve dict üzerinde durup, bunun MongoDB'deki JSON doc'ları ile nasıl benzerlik gösterdiği ön plana çıkan kısımlardı.
**"MongoDB for DBA"** dersi, mongo shell ile sorguların çekilmesi, limit, skip, filter konuları ile tamamlandı. Ayrıca, mimariden bahsedildi, yani yatay ve dikey genişlemede MongoDB nasıl davranır falan bunlardan bahsedildi. Burada ise yine monogdb kurulu ise ve verilen json dosyasını mongoimport ile import etti iseniz, bazı sonuçların çıktılarını göndermeniz ile sona eriyor.
**Not :** Ubuntu üzerinde MongoDB kurarken en son versiyonu kurmak için bu [linki] (https://docs.mongodb.org/manual/tutorial/install-mongodb-on-ubuntu/) kullanın. Eğer ```direk sudo apt-get install mongodb-server``` derseniz, mongodb'nin 2.x versiyonunu kuruyor.
İlk hafta için şunu söyleyebilirim, güzel ve mantıklı bir uygulama, sonunda ne verdiği değil, süreçte neleri öğretebildiği çok daha önemlidir ve gördüğüm kadarı ile bir hayli öğretiyor.
| 73.210526 | 378 | 0.800863 | tur_Latn | 0.999956 |
b104c44eefe0c1a046185b43e9b63bbbc79e375d | 139 | md | Markdown | common/graph/README.md | Loks-/competitions | 3bb231ba9dd62447048832f45b09141454a51926 | [
"MIT"
] | 4 | 2018-06-05T14:15:52.000Z | 2022-02-08T05:14:23.000Z | common/graph/README.md | Loks-/competitions | 3bb231ba9dd62447048832f45b09141454a51926 | [
"MIT"
] | null | null | null | common/graph/README.md | Loks-/competitions | 3bb231ba9dd62447048832f45b09141454a51926 | [
"MIT"
] | 1 | 2018-10-21T11:01:35.000Z | 2018-10-21T11:01:35.000Z | # Graph
* Algorithms in plane subdirectory assume:
* Graph is connected
* Edges in the graph are sorted in counter clockwise order
| 27.8 | 62 | 0.741007 | eng_Latn | 0.999324 |
b1054f061d99957bb1d3617fe48b7a5e56e35052 | 3,633 | md | Markdown | README.md | PNoryk/django-filter-grouped | 39a096a65121aefe989700896cd348ebcd7216c0 | [
"BSD-3-Clause"
] | 3 | 2021-10-14T05:59:32.000Z | 2022-01-20T09:32:13.000Z | README.md | PNoryk/django-filter-groups | 39a096a65121aefe989700896cd348ebcd7216c0 | [
"BSD-3-Clause"
] | null | null | null | README.md | PNoryk/django-filter-groups | 39a096a65121aefe989700896cd348ebcd7216c0 | [
"BSD-3-Clause"
] | null | null | null | # django filter groups
This package groups filters generated by django-filter.
The main reason to use it - show only selected filters.
It groups filters by their `field_name`.
The filter lookup will be subtracted from `filter_name`.
That's why `int_field` and `int_field__isnull` in example above, will be placed in ine group
```python
class MyFilterSet(django_filters.FilterSet):
int_field = django_filters.NumberFilter()
int_field__isnull = django_filters.NumberFilter(lookup_expr="isnull")
```
A group name resolution goes the next way:
- finding `filter_group_label` in any filter in current group
- if multiple were found, the first would be selected
- it's not good idea to add multiple `filter_group_label`'s
- the ways to add `filter_group_label` you can find [here](#change_group_name)
- if `filter_group_label` wasn't added, it's finding label declared in a filter with `exact` lookup expression
- if it isn't presented, it'll get the first declared filter for this group and take its label
- if no label is found, it'll get the field verbose_name from model
- otherwise, it'll set `"[invalid name]"` group name, and it won't be able to choose such group
## how to use
```
pip install django-filter-groups
```
add to your `INSTALLED_APPS` after `django-filter`
```python
INSTALLED_APPS = [
...
"django_filters",
"django_filters_groups",
...
]
```
use it in your template:
- add `{% add_select_filter_form_to_context %}` to the top of your template.
It allows you to place `{{ select_filter_form.media }}` anywhere you want
- add `{% filters_by_groups %}`
- add `{{ select_filter_form.media }}`
If FilterSet name is not 'filter' -> add filterset to both tags \
`{% add_select_filter_form_to_context my_custom_filterset %}`\
`{% filters_by_groups my_custom_filterset %}`
or filterset name
`{% filters_by_groups "my_custom_filterset" %}`
`{% add_select_filter_form_to_context "my_custom_filterset" %}`
## warning
- It's necessary to add values to `exact` and `iexact` [VERBOSE_LOOKUPS](https://django-filter.readthedocs.io/en/stable/ref/settings.html?highlight=verbose_lookups#filters-verbose-lookups). \
Filter choice will be empty if the lookups isn't presented
- It's important to add filter verbose lookup in the end of declared filter label
if `filter_group_label` wasn't added in any filter,
and it's a filter with exact lookup or the first in a group\
Default groups of model fields declared in `FilterSet._meta.fields` have normal labels
```python
# settings.py
# FILTERS_VERBOSE_LOOKUPS = {"exact": "match"}
class F(django_filters.FilterSet):
my_number_filter = django_filters.NumberFilter(label="number match") # good
my_number_filter = django_filters.NumberFilter(label="number") # bad
```
## default settings
```
# django settings
FILTERS_GROUPS_SELECT_FILTER_FORM_LABEL = "Select a label"
```
```js
// static/django_filters_groups/filter-defaults.js
let filterDefaults = {
filterWrapperSelector: "p", // p is necessary when you use {{ form.as_p }}
submitOnFilterDelete: false,
};
```
## <a name="change_group_name"></a> change group name
You can set group name directly in 2 ways:
- add `filter_group_label` to your filter
```python
class FFieldCountFilter(django_filters.NumberFilter):
filter_group_label = "custom_group_label"
```
- use `get_filter_class_with_custom_label`
```python
from django_filters_groups.utils import get_filter_class_with_group_label
class MyFilterSet(django_filters.FilterSet):
custom_filter = get_filter_class_with_group_label(django_filters.NumberFilter, "custom_group_label")(method="custom_filter_method")
```
| 36.33 | 191 | 0.761905 | eng_Latn | 0.931911 |
b106348bf4529d168e19d88bd56c6773b3cebed1 | 9,542 | md | Markdown | articles/connectors/connectors-create-api-office365-outlook.md | Jontii/azure-docs.sv-se | d2551c12e17b442dc0b577205d034dcd6c73cff9 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/connectors/connectors-create-api-office365-outlook.md | Jontii/azure-docs.sv-se | d2551c12e17b442dc0b577205d034dcd6c73cff9 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/connectors/connectors-create-api-office365-outlook.md | Jontii/azure-docs.sv-se | d2551c12e17b442dc0b577205d034dcd6c73cff9 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Integrera med Office 365 Outlook
description: Automatisera uppgifter och arbets flöden som hanterar e-post, kontakter och kalendrar i Office 365 Outlook med hjälp av Azure Logic Apps
services: logic-apps
ms.suite: integration
ms.reviewer: logicappspm
ms.topic: article
ms.date: 11/13/2020
tags: connectors
ms.openlocfilehash: 790879894c3b268fcd55aafc96507319b29fe1e5
ms.sourcegitcommit: d1e56036f3ecb79bfbdb2d6a84e6932ee6a0830e
ms.translationtype: MT
ms.contentlocale: sv-SE
ms.lasthandoff: 01/29/2021
ms.locfileid: "99055084"
---
# <a name="manage-email-contacts-and-calendars-in-office-365-outlook-by-using-azure-logic-apps"></a>Hantera e-post, kontakter och kalendrar i Office 365 Outlook med hjälp av Azure Logic Apps
Med [Azure Logic Apps](../logic-apps/logic-apps-overview.md) och [Office 365 Outlook Connector](/connectors/office365connector/)kan du skapa automatiserade uppgifter och arbets flöden som hanterar ditt arbets-eller skol konto genom att skapa Logi Kap par. Du kan till exempel automatisera dessa uppgifter:
* Hämta, skicka och svara på e-post.
* Schemalägg möten i din kalender.
* Lägg till och redigera kontakter.
Du kan använda en utlösare för att starta arbets flödet, till exempel när ett nytt e-postmeddelande tas emot, när ett Kalender objekt uppdateras eller när en händelse inträffar i en skillnads tjänst, till exempel Salesforce. Du kan använda åtgärder som svarar på utlösnings händelsen, till exempel skicka ett e-postmeddelande eller skapa en ny kalender händelse.
## <a name="prerequisites"></a>Förutsättningar
* Ett Outlook-konto där du loggar in med ett [arbets-eller skol konto](https://www.office.com/). Om du har ett @outlook.com @hotmail.com -eller-konto kan du använda [Outlook.com-anslutaren](../connectors/connectors-create-api-outlook.md) i stället. Om du vill ansluta till Outlook med ett annat användar konto, till exempel ett tjänst konto, se [Anslut med andra konton](#connect-using-other-accounts).
* Ett Azure-konto och prenumeration. Om du heller inte har någon Azure-prenumeration kan du [registrera ett kostnadsfritt Azure-konto](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
* Den Logic app där du vill komma åt ditt Outlook-konto. För att starta arbets flödet med en Office 365 Outlook-utlösare måste du ha en [Tom Logic-app](../logic-apps/quickstart-create-first-logic-app-workflow.md). För att lägga till en Office 365 Outlook-åtgärd i ditt arbets flöde måste din Logic app redan ha en utlösare.
## <a name="add-a-trigger"></a>Lägga till en utlösare
En [utlösare](../logic-apps/logic-apps-overview.md#logic-app-concepts) är en händelse som startar arbets flödet i din Logic app. I den här exempel Logic-appen används en "avsöknings utlösare" som söker efter uppdaterade Kalender händelser i ditt e-postkonto baserat på angivet intervall och frekvens.
1. I [Azure Portal](https://portal.azure.com)öppnar du din tomma Logic-app i Logic App Designer.
1. I rutan Sök anger `office 365 outlook` du som filter. Det här exemplet väljer **när en kommande händelse börjar snart**.
1. Om du inte har en aktiv anslutning till ditt Outlook-konto uppmanas du att logga in och skapa anslutningen. Om du vill ansluta till Outlook med ett annat användar konto, till exempel ett tjänst konto, se [Anslut med andra konton](#connect-using-other-accounts). Annars anger du informationen för utlösarens egenskaper.
> [!NOTE]
> Din anslutning upphör inte förrän den har återkallats, även om du ändrar dina inloggnings uppgifter. Mer information finns i [konfigurations bara livs längder för token i Azure Active Directory](../active-directory/develop/active-directory-configurable-token-lifetimes.md).
I det här exemplet väljs den kalender som utlösaren kontrollerar, till exempel:
1. Ange **frekvens** -och **intervall** värden i utlösaren. Om du vill lägga till andra tillgängliga Utlösar egenskaper, t. ex. **tidszon**, väljer du dessa egenskaper i listan **Lägg till ny parameter** .
Om du till exempel vill att utlösaren ska kontrol lera kalendern var 15: e minut, ange **frekvens** till **minut** och ange **intervall** till `15` .
1. I verktygsfältet designer väljer du **Spara**.
Lägg nu till en åtgärd som körs när utlösaren utlöses. Du kan till exempel lägga till åtgärden Twilio **Skicka meddelande** , som skickar en text när en kalender händelse startar om 15 minuter.
## <a name="add-an-action"></a>Lägga till en åtgärd
En [åtgärd](../logic-apps/logic-apps-overview.md#logic-app-concepts) är en åtgärd som körs av arbets flödet i din Logic app. Den här exempel på Logic-appen skapar en ny kontakt i Office 365 Outlook. Du kan använda utdata från en annan utlösare eller åtgärd för att skapa kontakten. Anta till exempel att din Logic app använder Dynamics 365-utlösaren **när en post skapas**. Du kan lägga till Office 365 Outlook-åtgärden för att **skapa kontakter** och använda utdata från Salesforce-utlösaren för att skapa den nya kontakten.
1. I [Azure Portal](https://portal.azure.com)öppnar du din Logic app i Logic Apps designer.
1. Om du vill lägga till en åtgärd som sista steg i arbets flödet väljer du **nytt steg**.
Om du vill lägga till en åtgärd mellan stegen flyttar du pekaren över pilen mellan stegen. Välj plus tecknet ( **+** ) som visas och välj sedan **Lägg till en åtgärd**.
1. I rutan Sök anger `office 365 outlook` du som filter. I det här exemplet väljer du **skapa kontakt**.
1. Om du inte har en aktiv anslutning till ditt Outlook-konto uppmanas du att logga in och skapa anslutningen. Om du vill ansluta till Outlook med ett annat användar konto, till exempel ett tjänst konto, se [Anslut med andra konton](#connect-using-other-accounts). Annars anger du informationen för åtgärdens egenskaper.
> [!NOTE]
> Din anslutning upphör inte förrän den har återkallats, även om du ändrar dina inloggnings uppgifter. Mer information finns i [konfigurations bara livs längder för token i Azure Active Directory](../active-directory/develop/active-directory-configurable-token-lifetimes.md).
Det här exemplet väljer mappen kontakter där åtgärden skapar den nya kontakten, till exempel:
Om du vill lägga till andra tillgängliga åtgärds egenskaper väljer du dessa egenskaper i listan **Lägg till ny parameter** .
1. I verktygsfältet designer väljer du **Spara**.
<a name="connect-using-other-accounts"></a>
## <a name="connect-using-other-accounts"></a>Anslut med andra konton
Om du försöker ansluta till Outlook genom att använda ett annat konto än det som för närvarande är inloggat på Azure kan du få [enkel inloggning (SSO)](../active-directory/manage-apps/what-is-single-sign-on.md) -fel. Det här problemet uppstår när du loggar in på Azure Portal med ett konto, men använder ett annat konto för att skapa anslutningen. Designern förväntar dig att du använder kontot som är inloggat på Azure Portal. För att lösa det här problemet har du följande alternativ:
* Konfigurera det andra kontot med **deltagar** rollen i din Logic Apps resurs grupp.
1. Välj **åtkomst kontroll (IAM)** på din Logic Apps resurs grupps meny. Konfigurera det andra kontot med **deltagar** rollen.
Mer information finns i [Lägga till eller ta bort Azure-rolltilldelningar med hjälp av Azure-portalen](../role-based-access-control/role-assignments-portal.md).
1. När du har konfigurerat den här rollen loggar du in på Azure Portal med kontot som har deltagar behörighet. Nu kan du använda det här kontot för att skapa anslutningen till Outlook.
* Konfigurera det andra kontot så att ditt arbets-eller skol konto har behörigheten "Skicka som".
Om du har administratörs behörighet för tjänst kontots post låda konfigurerar du ditt arbets-eller skol konto med antingen **Skicka som** eller **Skicka åt** behörigheter. Mer information finns i [ge Mailbox-behörigheter till en annan användar administratörs hjälp](/microsoft-365/admin/add-users/give-mailbox-permissions-to-another-user). Du kan sedan skapa anslutningen med hjälp av ditt arbets-eller skol konto. Du kan nu använda tjänst kontots e-postadress i utlösare eller åtgärder där du kan ange avsändaren.
Till exempel har åtgärden **Skicka ett e-postmeddelande** en valfri parameter **från (skicka som)** som du kan lägga till i åtgärden och använda tjänst kontots e-postadress som avsändare. Följ dessa steg om du vill lägga till den här parametern:
1. I åtgärden **Skicka ett e-postmeddelande** öppnar du listan **Lägg till en parameter** och väljer parametern **från (Send As)** .
1. När parametern visas i åtgärden anger du tjänst kontots e-postadress.
## <a name="connector-reference"></a>Referens för anslutningsapp
Teknisk information om den här anslutningen, till exempel utlösare, åtgärder och gränser, som beskrivs av kopplingens Swagger-fil, finns på [kopplingens referens sida](/connectors/office365/).
## <a name="next-steps"></a>Nästa steg
* Lär dig mer om andra [Logic Apps anslutningar](../connectors/apis-list.md)
| 78.213115 | 525 | 0.779396 | swe_Latn | 0.999686 |
b106624201d61d3c01b7c3d8ecdedb637a85adbc | 1,351 | md | Markdown | README.md | brunoramonn/markdown | bea2ff07cf36c8d0c0dba17bd41a29e45d187229 | [
"MIT"
] | null | null | null | README.md | brunoramonn/markdown | bea2ff07cf36c8d0c0dba17bd41a29e45d187229 | [
"MIT"
] | null | null | null | README.md | brunoramonn/markdown | bea2ff07cf36c8d0c0dba17bd41a29e45d187229 | [
"MIT"
] | null | null | null | # markdown
Repositorio para teste de MarkDown
**Ellen Cristina Santos da Silva**
**Apelido: Ellen**
**Email Trybe: ellen@gmail.com**
**Linkedin: https://www.linkedin.com/in/ellensanttis/**
**Introdução**
Oi pessoal, bom dia!
Meu nome é Ellen, sou de Manaus e atualmente estou morando em Campos, no Rio de Janeiro. Ontem foi meu primeiro dia na Trybe e me sinto bem animada.
Estou entrando para o time de fundamentos como pessoa instrutora. Sou formada em Sistemas de Informação e pós graduada em Gestão de Projetos e Docência do Ensino Superior – em andamento.
<p>Acredito que a educação transforma vidas, e saber que, de alguma forma estou contribuindo para o aprendizado de pessoas me mantém motivada a sempre buscar conhecimento.
Sou incentivadora de mulheres na tecnologia, participo de uma grande e acolhedora comunidade de mulheres desenvolvedoras, é lindo.
<p>No meu tempo livre gosto de assitir filmes, séries e Property Brothers, gosto de estar entre amigos, reunir família e boa conversa. Curto uma boa leitura, fotografia e -tento ter- plantainhas. <3
<p>Apaixonada por viagens, natureza e vinho. Gosto de música, e na minha playlist não pode faltar Metallica, Raça Negra e Alceu Valença.
Uma bizarrice: Ando e falo dormindo. É o que dizem ahaha.
<p>Se quiser conversar eu sempre animo!
<p>É isso, feliz por estar aqui.
<3
| 48.25 | 198 | 0.775722 | por_Latn | 0.999692 |
b106e0ec812c751dbad952e807b1f343c4e79845 | 9,883 | md | Markdown | docs/azure-data-studio/extensions/dashboard-extension.md | PowerBee-AK/sql-docs.de-de | f6f4854db855a89c4e49dc0557fa456da060b3c7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/azure-data-studio/extensions/dashboard-extension.md | PowerBee-AK/sql-docs.de-de | f6f4854db855a89c4e49dc0557fa456da060b3c7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/azure-data-studio/extensions/dashboard-extension.md | PowerBee-AK/sql-docs.de-de | f6f4854db855a89c4e49dc0557fa456da060b3c7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Erstellen einer Dashboarderweiterung
description: Dieses Tutorial veranschaulicht, wie Sie eine Dashboarderweiterung erstellen, um Azure Data Studio benutzerdefinierte Funktionen hinzuzufügen.
ms.prod: azure-data-studio
ms.technology: azure-data-studio
ms.topic: conceptual
author: yualan
ms.author: alayu
ms.reviewer: alayu, maghan
ms.custom: ''
ms.date: 08/28/2020
ms.openlocfilehash: d933f9bdff4279b841522f8a0e09f66e01364630
ms.sourcegitcommit: fa63019cbde76dd981b0c5a97c8e4d57e8d5ca4e
ms.translationtype: HT
ms.contentlocale: de-DE
ms.lasthandoff: 02/03/2021
ms.locfileid: "99495754"
---
# <a name="create-an-azure-data-studio-dashboard-extension"></a>Erstellen einer Azure Data Studio-Dashboarderweiterung
In diesem Tutorial wird veranschaulicht, wie Sie eine neue Azure Data Studio-Dashboarderweiterung erstellen. Die Erweiterung trägt zum Azure Data Studio-Verbindungsdashboard bei, sodass Sie die Funktionalität von Azure Data Studio so erweitern können, dass Sie für Benutzer leicht zu erkennen sind.
In diesem Artikel wird Folgendes behandelt:
> [!div class="checklist"]
> - Installieren des Erweiterungs-Generators
> - Erstellen der Erweiterung
> - Beitragen zum Dashboard in der Erweiterung
> - Testen der Erweiterung
> - Packen der Erweiterung
> - Veröffentlichen der Erweiterung im Marketplace
## <a name="prerequisites"></a>Voraussetzungen
Azure Data Studio ist auf dem gleichen Framework wie Visual Studio Code aufgebaut, sodass Erweiterungen für Azure Data Studio mithilfe von Visual Studio Code erstellt werden. Sie benötigen die folgenden Komponenten:
- [Node.js](https://nodejs.org) – installiert und in Ihrem `$PATH` verfügbar. Node.js enthält [npm](https://www.npmjs.com/), den Node.js-Paket-Manager, der zum Installieren des Erweiterungsgenerators verwendet wird.
- [Visual Studio Code](https://code.visualstudio.com) zum Debuggen der Erweiterung.
- Die [Debugerweiterung](https://marketplace.visualstudio.com/items?itemName=ms-mssql.sqlops-debug) von Azure Data Studio (optional). Mit der Debugerweiterung können Sie Ihre Erweiterung testen, ohne sie zu packen und in Azure Data Studio zu installieren.
- Stellen Sie sicher, dass sich `azuredatastudio` in Ihrem Pfad befindet. Wenn Sie unter Windows arbeiten, wählen Sie in „setup.exe“ die Option **Zu PATH hinzufügen** aus. Führen Sie unter macOS oder Linux über die Befehlspalette in Azure Data Studio **Befehl 'azuredatastudio' in PATH installieren** aus.
## <a name="install-the-extension-generator"></a>Installieren des Erweiterungsgenerators
Um den Prozess der Erstellung von Erweiterungen zu vereinfachen, haben wir einen [Erweiterungsgenerator](https://code.visualstudio.com/docs/extensions/yocode) erstellt, der Yeoman verwendet. Um diesen zu installieren, führen Sie an der Eingabeaufforderung den folgenden Befehl aus:
```console
npm install -g yo generator-azuredatastudio
```
## <a name="create-your-dashboard-extension"></a>Erstellen Ihrer Dashboarderweiterung
### <a name="introduction-to-the-dashboard"></a>Einführung in das Dashboard
Das Verbindungsdashboard von Azure Data Studio ist ein leistungsstarkes Tool, das die Verbindungen eines Benutzers zusammenfasst und Einblick in diese gibt.
Es sind zwei Varianten des Dashboards verfügbar. Im *Serverdashboard* wird der gesamte Server zusammengefasst, während auf dem *Datenbankdashboard* eine einzelne Datenbank zusammengefasst wird. Der Zugriff auf beide Dashboards erfolgt, indem Sie mit der rechten Maustaste im Viewlet **Verbindungen** von Azure Data Studio auf einen Server oder eine Datenbank und dann auf **Verwalten** klicken:
:::image type="content" source="media/dashboard-extension/dashboard-summary.gif" alt-text="Screenshot: Einführung in Dashboards":::
Es gibt drei wichtige Bereiche, in denen Erweiterungen dem Dashboard Funktionalität hinzufügen können:
1. **Registerkarte mit dem vollständigen Dashboard:** Eine separate Registerkarte im Dashboard für Ihre Erweiterung. Kann einem Server- oder einem Datenbankdashboard hinzugefügt werden. Anpassbar mit Widgets, einer Symbolleiste und einem Navigationsabschnitt.
2. **Homepageaktionen**: Aktionsschaltflächen am oberen Rand der Verbindungssymbolleiste.
3. **Widgets**: Diagramme, die für Ihre SQL Server-Instanz ausgeführt werden.
:::image type="content" source="media/dashboard-extension/dashboard-contrib-points.png" alt-text="Screenshot: Bereiche, deren Funktionalität durch Erweiterungen erweitert werden kann":::
### <a name="run-the-extension-generator"></a>Ausführen des Erweiterungsgenerators
So erstellen Sie eine Erweiterung:
1. Starten Sie den Erweiterungs-Generator mit dem folgenden Befehl:
`yo azuredatastudio`
1. Wählen Sie **Neues Dashboard** aus der Liste der Erweiterungstypen aus.
1. Füllen Sie die Eingabeaufforderungen wie gezeigt aus, um eine Erweiterung zu erstellen, die dem Serverdashboard eine Registerkarte hinzufügt.
:::image type="content" source="media/dashboard-extension/dashboard-generator.png" alt-text="Screenshot: Erweiterungs-Generator":::
Nachstehend werden die angezeigten Eingabeaufforderungen etwas detaillierter erläutert:
:::image type="content" source="media/dashboard-extension/dashboard-flowchart.png" alt-text="Screenshot: Flussdiagramm für das Dashboard":::
Durch Ausführen der oben genannten Schritte wird ein neuer Ordner erstellt. Öffnen Sie den Ordner in Visual Studio Code, und schon sind Sie bereit, selbst eine Dashboarderweiterung zu erstellen.
### <a name="run-the-extension"></a>Ausführen der Erweiterung
Sehen wir uns nun an, was die Dashboardvorlage bietet, indem wir die Erweiterung ausführen. Stellen Sie vor der Ausführung sicher, dass die **Azure Data Studio-Debugerweiterung** in Visual Studio Code installiert ist.
Drücken Sie **F5** in Visual Studio Code, um Azure Data Studio mit ausgeführter Erweiterung im Debugmodus zu starten. Anschließend können Sie anzeigen, wie diese Standardvorlage zum Dashboard beiträgt.
Als nächstes sehen wir uns an, wie dieses Standarddashboard geändert werden kann.
### <a name="develop-the-dashboard"></a>Entwickeln des Dashboards
Die wichtigste Datei für den Einstieg in die Erweiterungsentwicklung ist `package.json`. Dies ist die Manifestdatei, in der die Dashboardbeiträge registriert werden. Beachten Sie die Abschnitte `dashboard.tabs`, `dashboard.insights` und `dashboard.containers`.
Im Folgenden sind einige Änderungen aufgeführt, die Sie ausprobieren sollten:
- Experimentieren Sie mit den Einblicktypen, zu denen auch „bar“, „horizontalBar“ und „timeSeries“ gehören.
- Schreiben Sie eigene Abfragen, um sie für Ihre SQL Server-Verbindung auszuführen.
- Tutorials zu spezifischen Einblicken finden Sie in diesem [Einblickbeispiel](../tutorial-qds-sql-server.md) oder [unter diesem Link](../tutorial-table-space-sql-server.md).
## <a name="package-your-extension"></a>Packen der Erweiterung
Um Ihre Erweiterung für andere Benutzer freizugeben, müssen Sie sie in eine einzelne Datei packen. Ihre Erweiterung kann im Marketplace für Azure Data Studio-Erweiterungen veröffentlicht oder für Ihr Team oder Ihre Community freigegeben werden. Zu diesem Zweck müssen Sie über die Befehlszeile ein weiteres npm-Paket installieren.
```console
npm install -g vsce
```
Bearbeiten Sie die `README.md`-Datei nach Ihren Wünschen. Navigieren Sie anschließend zum Basisverzeichnis der Erweiterung, und führen Sie `vsce package` aus. Optional können Sie ein Repository mit ihrer Erweiterung verknüpfen oder den Vorgang ohne Repository fortsetzen. Um ein Repository hinzuzufügen, fügen Sie der Datei `package.json` eine ähnliche Zeile hinzu.
```json
"repository": {
"type": "git",
"url": "https://github.com/anjalia/my-test-extension.git"
}
```
Nachdem diese Zeilen hinzugefügt wurden, wird die Datei `my-test-extension-0.0.1.vsix` erstellt und ist nun für die Installation in Azure Data Studio bereit.
:::image type="content" source="media/dashboard-extension/install-vsix.png" alt-text="Screenshot: Installation von VSIX":::
## <a name="publish-your-extension-to-the-marketplace"></a>Veröffentlichen der Erweiterung im Marketplace
Da sich der Marketplace für Azure Data Studio-Erweiterungen noch in Bearbeitung befindet, wird die VSIX-Erweiterung an einem beliebigen Ort, z. B. auf einer GitHub-Releaseseite gehostet. Anschließend Sie senden einen Pull Request, der [diese JSON-Datei](https://github.com/Microsoft/azuredatastudio/blob/release/extensions/extensionsGallery.json) mit Ihren Erweiterungsinformationen aktualisiert.
## <a name="next-steps"></a>Nächste Schritte
In diesem Tutorial haben Sie Folgendes gelernt:
> [!div class="checklist"]
> - Installieren des Erweiterungs-Generators
> - Erstellen der Erweiterung
> - Beitragen zum Dashboard in der Erweiterung
> - Testen der Erweiterung
> - Packen der Erweiterung
> - Veröffentlichen der Erweiterung im Marketplace
Hoffentlich hat Sie dieser Artikel dazu inspiriert, selbst eine Erweiterung für Azure Data Studio zu erstellen. Azure Data Studio bietet Unterstützung für Dashboardeinblicke (ansprechende Diagramme, die gegen Ihre SQL Server-Instanz ausgeführt werden), verschiedene SQL-spezifische APIs sowie eine Vielzahl von vorhandenen Erweiterungspunkten, die aus Visual Studio Code übernommen wurden.
Wenn Sie eine Idee haben, aber nicht sicher sind, wie Sie anfangen sollen, eröffnen Sie ein Issue, oder senden Sie einen Tweet an das Team unter [azuredatastudio](https://twitter.com/azuredatastudio).
Weitere Informationen finden Sie im [Visual Studio Code-Erweiterungsleitfaden](https://code.visualstudio.com/docs/extensions/overview). Dieser deckt alle vorhandenen APIs und Muster ab.
Um zu erfahren, wie Sie mit T-SQL in Azure Data Studio arbeiten, führen Sie das Tutorial zum T-SQL-Editor aus:
> [!div class="nextstepaction"]
> [Verwenden des Transact-SQL-Editors zum Erstellen von Datenbankobjekten](../tutorial-sql-editor.md)
| 65.019737 | 396 | 0.802287 | deu_Latn | 0.994746 |